activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: Fw: AMQ-cpp problem with ExceptionListener, receive and lost connection
Date Thu, 17 Jun 2010 12:42:43 GMT
On Thu, 2010-06-17 at 09:48 +0100, andrew.marlow@uk.bnpparibas.com
wrote:
> Many thanks for the various offers of help I got. I think I have solved 
> the problem. The weird core dumping was due to a bad build, due to some 
> spurious copies of header files of mine that were out of step with the 
> proper ones. Fixed. Now the build is clean I do see the behaviour I expect 
> from AMQ. The ExceptionListener works on the server side and I can now 
> cope with the Q mgr being restarted. This makes me think that the MQSeries 
> behaviour is actually wrong. I think the JMS spec says that the error 
> handling mechanim should be to deliver exceptions via the registered 
> ExceptionListener.
> 
> I wonder if I should use an ExceptionListener on the client side. It is 
> not nice to test the connection by writing a spurious message (heartbeat) 
> to the request queue, it is rather crude and could clog the Q up. What do 
> people think? Is anyone else using ExceptionListeners on the client side?
> 

Yes, the ExceptionListener should be your point of notification that a
transport error has occured, since you have opted not to use the
Failover Transport the ExceptionListener will be called when the
Inactivity Monitor fires a KeepAlive message to the broker and that
operation fails.


-- 
Tim Bish

Open Source Integration: http://fusesource.com
ActiveMQ in Action: http://www.manning.com/snyder/

Follow me on Twitter: http://twitter.com/tabish121
My Blog: http://timbish.blogspot.com/


Mime
View raw message