activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <>
Subject Re: ExceptionListener not getting fired on the client side when using JmsTemplate
Date Mon, 04 Nov 2013 23:56:34 GMT
Well you could force the connection to always sync send or always
async send and deal with it in each respective way (on the connecting
thread, or on the exception listener).


Otherwise, the exceptionListener is the callback for asynchronous
scenarios. This is what the failoverTransport uses to detect breakages
in the connection.

On Tue, Oct 29, 2013 at 10:06 PM, Steven Turner
<> wrote:
> Thanks Christian. Yes, I do see the exception in my logs which I had already
> mentioned in my first post in this thread. I wanted to handle all exceptions
> in a generic way in ExceptionListener instead of handling async and sync
> exceptions differently. Is there any support in ActiveMQ to get callback for
> any exception on the connection between client and broker (especially the
> ones thrown by broker plugins)
> org.springframework.jms.UncategorizedJmsException: Uncategorized exception
> occured during JMS processing; nested exception is javax.jms.JMSException:
> common.jms.ActiveMQAuth$ActiveMQAuthException: Could not establish server
> context
>         at
>         at
>         at
> org.springframework.jms.core.JmsTemplate.execute(
>         at
> org.springframework.jms.core.JmsTemplate.send(
>         at common.jms.test.JMSProducer.start(
>         at common.jms.test.JMSProducer.access$900(
>         at common.jms.test.JMSProducer$
>         at
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

Christian Posta
twitter: @christianposta

View raw message