Hello,
Any idea what would cause this exception (stack trace below)? ActiveMQ
5.5.0 *embedded* broker, fwiw (I'm reluctantly using 5.5.0 despite this
error and the ConcurrentModificationException, since there's no 5.5.1
yet...hint hint). Connection URL to two independent (non-networked) brokers
I always forget to mention something...possibly relevant bits of info:
a. This wasn't happening with 5.4.2, but is happening regularly
(intermittently) with 5.5.0.
b. The pattern this application uses is rapid-fire producing -- no consuming
on that connection.
Thanks!
-Dan Checkoway
Hello,
Not being familiar with the MQ code itself but experienced in Java,
InterruptedException typically occurs with a thread is interrupted for various
reasons, but most commonly thread cancellation/shutdown.
From the stack trace it looks like this occurred during the shutdown procedure
for
Justin,
If you look further down the stack trace, you can see it's doing failover
disposal after some sort of wire format exception...or perhaps inactivity on
the wire (which is extremely unlikely in my app, which is in a constant mode
of producing messages). I'm looking for ActiveMQ experts to
Understood.
My point in commenting on InterruptedException is that it shouldn't be getting
caught in that manner. It means that the executor service is likely not
getting shutdown properly. This would be true for any application and isn't
specific to ActiveMQ.
I'll leave it to the
Cool. For the ActiveMQ developers, I just want to reiterate/clarify, this
is NOT happening at app or context or broker or executor shutdown time as
Justin suggested. This is happening mid-run, sporadically. 5.5.0 only.
Dan
On Sun, May 1, 2011 at 3:34 PM, Justin Randall[via ActiveMQ]
Any help please ? the gc feature is very important for me, I really want to
make it works so if I make something wrong please tell me.
Thanks.
William.
--
View this message in context:
