activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jakub Korab <jakub.ko...@gmail.com>
Subject Re: Active MQ and High Availability Manager
Date Sun, 01 Apr 2012 19:23:02 GMT
Hi Zagan,

When you use JMS, your client uses makes use of the JMS API, but underneath
it the provider/implementation is ActiveMQ. What this means is that even
though you are using JMS, the client library that is used is actually the
ActiveMQ one. The reason for this is that the client and message broker need
to speak the same wire format - OpenWire in ActiveMQ's case. It is not
possible to use the JMS client library from another broker provider.

What you would do is provide an ActiveMQConnectionFactory as the concrete
implementation of a ConnectionFactory. The connection string, with all the
failover details gets passed in to that. As such, you can make use of all
the standard master/slave stuff that ActiveMQ provides
(http://activemq.apache.org/masterslave.html).

Jakub


Zagan wrote
> 
> Hello,
> 
> I need the possibility to run Apache Active MQ highly available. At the
> moment I would use Shared Filesystem Master/Slave but I have the problem,
> that IP/Hostname of Master and Slave have to be the same.
> The sender application is  only a JMS compliant client, which isn't using
> Apache Active MQ libraries. So he can't use failover protocol. Is there
> any preferred solution to the problem, like using a High Availability
> manager? At the moment I use Debian Linux as operating system.
> 
> Thanks for your help in advance!
> 


--
View this message in context: http://activemq.2283324.n4.nabble.com/Active-MQ-and-High-Availability-Manager-tp4523904p4524170.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message