Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <16834603.post@talk.nabble.com>
Date: Wed, 23 Apr 2008 06:26:40 -0700 (PDT)
From: DominicTulley <dominic.tulley@telelogic.com>
To: users@activemq.apache.org
Subject: Tomcat doesn't shutdown when amq client used within webapp
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


When we shut down our tomcat server the java process does not terminate and
it turns out that the culprit is a couple of threads belonging to the amq
client library.
The threads are "InactivityMonitor WriteCheck" and "InactivityMonitor
ReadCheck".

Having had a look at it there seem to be two possibilities.  Either there is
some client shutdown method we need to call which will ultimately call
InactivityMonitor.stop(), or the two threads should be daemon threads so
that they just evaporate.

I put in a change to make them daemon threads (trivial change) and tomcat
then shuts down correctly.  So, my question is, do we need this change in
AMQ or is there some shutdown call I should be making into the libraries?  I
am (as far as I can tell!) already closing all the connections we have open.

Thanks,

-Dominic
-- 
View this message in context: http://www.nabble.com/Tomcat-doesn%27t-shutdown-when-amq-client-used-within-webapp-tp16834603s2354p16834603.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.