Ah, right. I forgot qpid has multiple implementations. I agree that it's like that in JMS spec since one of the session control modes is to "acknowledge message if listener returned without an error".
Thanks for clarifying. On Mon, Jul 12, 2021 at 3:36 PM Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > > You dont say which client you are using but I expect its one of the > JMS clients and regardless which that the answer is no. I dont believe > it would matter if it were possible though, as the client is almost > certainly handling the exception. Perhaps it should log something if > it doesn't, but that also shouldnt really matter as per the JMS spec > it is a "programming error for a MessageListener to throw an > exception". > > On Mon, 12 Jul 2021 at 14:54, Mantas Gridinas <mgridi...@gmail.com> wrote: > > > > Yo! > > > > I'm using asynchronous message consumption method for my topics and > > sometimes the consumption throws an exception, but that exception does > > not get reported by qpid or anything else. I suspect it's because > > created threads (by default) use thread group's exception handler, > > which only checks if the exception was ThreadDeath. Is there a way to > > specify thread factory for qpid? > > > > -- > > // Mantas > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > > For additional commands, e-mail: users-h...@qpid.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > -- // Mantas --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
