Both JBoss and Jetty force a proper shutdown. I'll
probably go for 2/ and patch for myself.
Cheers
Brett
--- QM <[EMAIL PROTECTED]> wrote:
> On Sun, Jan 02, 2005 at 10:10:02AM +1100, Brett
> Randall wrote:
> : Yes, responsibility has been placed on developers
> and
> : architects, but a Tomcat
On Sun, Jan 02, 2005 at 10:10:02AM +1100, Brett Randall wrote:
: Yes, responsibility has been placed on developers and
: architects, but a Tomcat admin who deploys
: applications may not be in a position to hold them all
: individually to account.
This is a policy/political problem, then, and not
Hi Tim, QM, thanks for your replies.
Tim Funk:
> Calling System.exit() has been discussed on
tomcat-dev and by vetoed.
Yes, thanks, I subsequently found zilla 17000 and the
discussion.
Tim Funk:
> If the JVM does not shut down - it is due to bad 3rd
party code which creates non-daemon threads an
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 n
The JVM exits when there are 0 non-daemon threads running. Tomcat itself
shuts down fine with this constraint.
If the JVM does not shut down - it is due to bad 3rd party code which creates
non-daemon threads and fail to detect a shutdown.
The UNIX scripts allow you to capture the process id of
This email [EMAIL PROTECTED] is no longer available due to heavy spamming.
Please visit our website http://www.alestron.com for contact info.
Thank you!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-
This email [EMAIL PROTECTED] is no longer available due to heavy spamming.
Please visit our website http://www.alestron.com for contact info.
Thank you!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-
