activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From JordanC <jordanchang...@gmail.com>
Subject Configuring peer transport with shared data directory
Date Tue, 06 Dec 2016 17:20:11 GMT
I need some help configuring ActiveMQ to work with my clustered Java
application. What I want is to be able to run a variable number of nodes and
have messages distributed among the nodes and have high availability such
that if a node goes down, messaged queued on that node will be processed by
other nodes.

The configuration I have tried to use is Peer transport. Messages were
distributed among the nodes which was what I wanted. However, because each
broker had its own data directory, if a node went down, messages that were
queued on that node do not get consumed until the node is brought back up. I
thought using a shared directory should fix this however the problem I run
into is that any nodes whose brokers are waiting to acquire the file lock
are blocked from processing so only messages sent on a single node can be
consumed by that node. All other nodes can only queue messages and nothing
else.

Does using peer transport with a shared data directory not do what I need it
to do? If not, what should the configuration be?



--
View this message in context: http://activemq.2283324.n4.nabble.com/Configuring-peer-transport-with-shared-data-directory-tp4719809.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message