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: users@activemq.apache.org ReplyTo: users@activemq.apache.org 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: http://activemq.2283324.n4.nabble.com/InterruptedException-with-embedded-5-5-0-broker-tp3487950p3487959.html Sent from the ActiveMQ - User mailing list archive at Nabble.com. Sent from my BlackBerry device
