Please have a look at updateClusterClients, updateClusterClientsOnRemove
Bruce Snyder's Blog may also help you::
http://bsnyderblog.blogspot.com/2010/10/new-features-in-activemq-54-automatic.html
New Features in ActiveMQ 5.4.x
Hi,
looking at http://activemq.apache.org/message-redelivery-and-dlq-handling.html
it is possible to discard expired messages using a deadletterstrategy.
deadLetterStrategy
sharedDeadLetterStrategy processExpired=false /
/deadLetterStrategy
Is it possible to do the
Hi all,
we seem to have a deadlock situation when a broker shutdown happens.
We're in the middle of onMessage callback and trying to call commit.
The ActiveMQConsumer::dispatch method holds the unconsumedMessages
lock and waits for the reconnectMutex when committing. The failover
transport calls
This bug was reported some time ago. If you want to make a workaround, if
you are consuming messages in asynchronous (by callback), change to
synchronous consuming mode. In my case its resolved it.
2011/3/14 chris em...@christianhoffmann.info
Hi all,
we seem to have a deadlock situation when
To give more clear clarity explanation I am attaching my scenario in a word
file and uploading to this post
http://activemq.2283324.n4.nabble.com/file/n3354761/Message_Struck_-_Scenario.doc
Message_Struck_-_Scenario.doc
Thank You,
Nag.
--
View this message in context:
ActiveMQ 5.2.0, Persistent, Failover transport over tcp, Oracle 10g, windows
2003 server R2 SP2.
Test Program, non persistent, windows xp sp 3.
Explaining the scenario in short:
1. message -1067 was posted to master ActiveMQ to 61716 Consumer was
listening on Master ActivveMQ
2. Something
