If you want brokers to resume sending messages when other brokers fail, you
want master/slave pairs (http://activemq.apache.org/masterslave.html);
simply writing the messages to a JDBC database doesn't mean other brokers
will automatically start reading/sending them.
KahaDB is generally considered
What else is holding that lock? (You haven't posted this most recent
thread dump and that stack trace doesn't appear in the first one, so it's
hard to know what's going on without more information.)
Looking at your first thread dump, there are a number of NIO threads trying
to acquire a connectio
I ran into same situation again. When I reboot database service, and
activemq service. AMQ starts delivering messages for a while, and it stops
doing that.
Thread dump is showing all stomp threads are waiting on a lock - not sure
if it's normal scenario?
I'm using nio for openwire, and stomp+nio
