Forgive me if I'm missing something daft - its been a while since I read the JMS spec - but I'm pretty sure an uncaught exception isn't meant to kill a subscription...
Here is the simplest code sample to reproduce the problem. <<TestMessageSenderer.java>> This is running against AMQ 5.3.0. Can someone confirm this is a bug? I'll raise an issue in Jira. Cheers, thanks, Nick > _____________________________________________ > From: Minutello, Nick > Sent: 24 May 2010 16:27 > To: 'users@activemq.apache.org' > Subject: Uncaught exception in subscriber ends subscription > > > Hi chaps/chappettes, > > We are seeing an issue with ActiveMQ Topic subscription when there is > an uncaught exception. > > It appears to be related to an old report (but who knows) : > http://mail-archives.apache.org/mod_mbox/activemq-users/200805.mbox/<1 > 7189972.p...@talk.nabble.com> > <http://mail-archives.apache.org/mod_mbox/activemq-users/200805.mbox/% > 3c17189972.p...@talk.nabble.com%3e> > > Basically, what happens is our Consumer (onMessage) was throwing an > NPE. After that happens, the consumer no longer receives any more > messages. > > Following it through in the debugger - when the exception is thrown, > what we see is the the "ActiveMQ Session Task" thread completes... > After that, it never seems to execute again. Seems some state in the > PooledTaskRunner gets borked? Investigating further - but at first > glance it appears it thinks the connection is shutting down... > > -Nick =============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ===============================================================================
