Failover support for activemq REST api

[martinsimon <ma...@gmail.com>]

I have set up activeMQ as a master/slave configuration using shared storage
for enabling high availability of data. My application consumes messages
from activemq using ActveMQ's REST API. How can I configure my system such
that these REST API calls will also adhere to the master/slave failover
strategy?

A workaround I could find was to

1) Copy and deploy the API web application and the libraries from ActiveMQ's
embedded jetty server and deploy it as a WAR on an independent JETTY server.
2) Modify the web.xml of the API web application to pass the failover URL as
a context parameter org.apache.activemq.brokerURL
3) My application now communicates with this jetty server which would in
turn route the requests to ActiveMQ.

The reason why I copied the API web application to a seperate server was
because the embedded Jetty server was giving preference to its own broker
over the servlet context parameter.

Is there some configuration for ensuring that the failover URL gets picked
by the embedded jetty server or is there a better approach for handling the
Rest calls with failover support?



--
View this message in context: http://activemq.2283324.n4.nabble.com/Failover-support-for-activemq-REST-api-tp4701700.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.