activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim McCabe <...@jmccabe.com>
Subject Re: Consumer client stops after failover
Date Thu, 06 May 2010 14:54:21 GMT

I think the problem is that the failover thread must be flagged as being a
daemon thread.  So when the the application doesn't have any other threads
to keep the VM alive, the VM shuts down while the failover thread is trying
to do its work.

In many programs this bug would not be noticed because there is often
another thread doing work - for example in a web application where you have
a thread listening for new HTTP connections, or you are using Quartz to
schedule periodic tasks, etc.  But when you have a simple standalone app
that doesn't have any of those services, this bug becomes visible.

This should be pretty easy fix, just to make sure the failover thread does
not call setDaemon(true).

- Jim

-- 
View this message in context: http://old.nabble.com/Consumer-client-stops-after-failover-tp27778246p28474886.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message