tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From QM <qm...@brandxdev.net>
Subject Re: Scripted shutdown does not force JVM exit
Date Sat, 01 Jan 2005 14:08:21 GMT
On Sat, Jan 01, 2005 at 07:45:52PM +1100, Brett Randall wrote:
: I'm wondering if this is intentional?  The result is that any
: application-spawned Thread-s that are not well managed (i.e. are allowed
: to continue to run or block after the context is removed) continue to
: run, and the JVM does not exit.

Yes.  This has been discussed several times before; see the archives for
details.


: This presents a problem for application deployers, when faced with
: applications that spawn threads and do not clean them up.  The only
: shutdown option in these cases is to send a SIGINTR to the JVM, as the
: scripted shutdown does not call exit.

I'd disagree; it puts responsibility on developers and architects to
make sure their applications handle threads properly.  There's no need
for a container to compensate for poor design. =)

Think of "Tomcat hanging on shutdown" as a clue that someone hasn't
cleaned up their threads.

-QM


-- 

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message