activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wwang2016 <wayne.w...@impactmobile.com>
Subject paging directory not accessible to cluster member
Date Wed, 09 Aug 2017 13:43:38 GMT
Hi,

I set up two wildfly instances (activemq is imbeded) in a cluster using
shared-store approach. I was testing the messaging high availability by
allow one wildfly instance (#1) to create all messages, and both instances
were able to process the messages. In the middle, I shut down instance #1,
and check if all messages can be processed by the remaining live wildfly
instances.

When I let the application to create 3000 to 5000 messages in one shot in
instance #1, and allow both instances to process messages (save into
database), then shut down instance #1, I can see all messages were
eventually processed by instance #2, indicating the cluster queue was
configured properly. In addition, no paging directory was created

When I let the application to create 10000 messages in one shot in instance
#1, and allow both instances to process messages. I saw a paging directory
was created. I then shut down instance #1, and let instance #2 to continue
to process the remaining messages. However, not all messages were processed.
I had to restart instance #1 to consume all remaining messages in the paging
directory. It looks like the paging directory was not accessible to cluster
members

Is there any additional configuration that is required to allow cluster
member to access paging directory?

Thanks



--
View this message in context: http://activemq.2283324.n4.nabble.com/paging-directory-not-accessible-to-cluster-member-tp4729527.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message