activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Randall" <>
Subject Re: InterruptedException with embedded 5.5.0 broker
Date Sun, 01 May 2011 19:33:42 GMT

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 developers to explain why the code is behaving this way.


Justin Randall
Sent from my BlackBerry device

-----Original Message-----
From: dcheckoway <>
Date: Sun, 1 May 2011 12:13:08 
To: <>
Subject: Re: InterruptedException with embedded 5.5.0 broker


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 let me know if
this is typical in 5.5.0 and onward, since I've never seen it occur in prior


On Sun, May 1, 2011 at 2:19 PM, Justin Randall[via ActiveMQ] <> wrote:

> 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 the TCP pooled executor service.
> The fact that InterruptedException occurred is normal and should be
> expected (anytime you shutdown an executor service InterruptedException
> occurs on all active threads in the executor service), but it is not typical
> to catch InterruptedException and print a stack trace.   Usually you should
> allow InterruptedException to propagate through so that the executor service
> can properly shutdown all threads.  If it is being caught and printed in the
> manner as indicated below, it would cause improper thread shutdown.  Common
> practices can also include catching InterruptedException, then performing
> cleanup work and then re-throwing the exception or calling
> Thread.currentThread().interrupt() when complete (allowing the interruption
> to "bubble up" to the executor service).
> That said, if this is only occurring when you are shutting down MQ, while
> it may not be a sign of good handling of InterruptedException, it is
> unlikely to cause any problems.
> Regards,
> Justin Randall
> ------Original Message------
> From: dcheckoway
> To: [hidden email]<http://user/SendEmail.jtp?type=node&node=3488262&i=0&by-user=t>
> ReplyTo: [hidden email]<http://user/SendEmail.jtp?type=node&node=3488262&i=1&by-user=t>
> Subject: Re: InterruptedException with embedded 5.5.0 broker
> Sent: May 1, 2011 12:04
> 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
> dcheckoway gmail com--
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at
> Sent from my BlackBerry device
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>  To unsubscribe from InterruptedException with embedded 5.5.0 broker, click
> here<>.

-----Dan Checkoway
dcheckoway gmail com--
View this message in context:
Sent from the ActiveMQ - User mailing list archive at
View raw message