You could use a broker plugin nd override the addconnection method, to do a
different check.
That exception implements part of the jms spec so it may be better to
understand nd tackle the root cause.
If you really need to change behaviour the broker plugin is the way to go.
On 21 Apr 2011 19:43,
Hi,
We were stressing activemq 5.4.2 with few persistent queues, few
non-persistent queues with TimeToLive (TTL) of 2 mins, and few non
persistent queues without any TTL. We came across 2 issues from which we
couldn’t recover to normal state without cleaning tmp-store and restarting
activemq.
Hi all,
we have switched to activemq and we are using automated webtests. Some of
these tests put messages in a queue and we have to wait for these messages
to be processed before we can go on with the tests.
Messages gets redelivered on failures. Currently I use jmx in a loop with a
sleep and
Hey, just curious what the strategy for the next release is. I can't use
5.5.0 in production because this ConcurrentModificationException bug (full
stack trace below) is causing message loss.
Will there be a 5.5.1 very soon, pretty please?! When 5.5.0 comes out and
there is a known issue that
how embarrassing, I read that page of course, and I read it upside down...
thanks, it works perfectly now.
On Wed, Apr 20, 2011 at 12:41 PM, Gary Tully gary.tu...@gmail.com wrote:
for 2.2 you need to use the default features url:
mvn:org.apache.activemq/activemq-karaf/5.5.0/xml/features
the
