OK, many thanks. I'll check back with bugzilla later.
Shapira, Yoav wrote:
Hi, Bugzilla is having a tough day: its admins ([EMAIL PROTECTED]) are aware of the problem and working on it.
There's an open issue with what you describe: destroy not being called when Tomcat is run as a Windows service for Tomcat 5.0.28. The issue was first reported in an early 5.0 version, fixed for 5.0.16 or 5.0.19, and now apparently has re-appeared.
Yoav Shapira http://www.yoavshapira.com
-----Original Message----- From: Paul Christmann [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 3:53 PM To: [EMAIL PROTECTED] Subject: 5.0.28 Service Shutdown problem on Windows
I just upgraded from 4.1.30 to 5.0.28 on two windows machines: one XP and one W2K. Both of them are having the same problem:
When I stop the installed Tomcat service, the destroy() method on my servlets does not appear to get called. I do not get my logging information from my destroy methods, and file handles that should get closed are left open.
The last message in my Tomcat stdout.log is:
INFO: Pausing Coyote HTTP/1.1 on http-8081
When I run Tomcat standalone (using bin/startup and bin/shutdown), this message is then followed by additional logging information and the destroy() method of my service gets called.
When I run bin/shutdown, it returns before the full Tomcat shutdown is completed. In fact, to my untrained eye it appears to return shortly after the "Pausing" log message.
So it appears that when running Tomcat as a service, the service is getting halted when shutdown finishes - which has Paused the service. But the remainder of the shutdown process is not invoked.
I've used the Windows installer, and made only four modifications to
the
installed service: + I replaced tomcat-users.xml + I changed the unpackWARS from true to false + I installed my webapp + I changed the service to run under a specific user account
I've exhausted my google skills searching for answers, but to no avail. I tried to search bugzilla but got SQL errors (is that a known problem? I followed the instructions on the error page and sent an email with the error message to [EMAIL PROTECTED], which seems too generic for that type of error message).
-- PC
Paul Christmann Prior Artisans, LLC mailto:[EMAIL PROTECTED] 504-587-9072
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- PC
Paul Christmann Prior Artisans, LLC mailto:[EMAIL PROTECTED] 504-587-9072
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
