This is an extremely well known problem with Sun's JDK 1.3. The most
obvious workaround is to downgrade to JDK 1.2, or if you happen to be really
friendly with Sun, get the alpha of the next JDK release. Alternatively,
you could search the archive for this list and find the previous messages
about this problem - there are several wrapper programs that wrap the JDK
and capture the system events and don't pass the logoff event to the JVM.
(Or you could write your own, all they are doing is using jvm.dll)
Randy
-----Original Message-----
From: Siebenmann, Joe [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 12, 2001 3:16 PM
To: '[EMAIL PROTECTED]'
Subject: Problems with Tomcat service on NT and W2K servers..
We are running Tomcat 3.2.1, standalone, with JDK1.3.0_01 under Windows NT
and 2000 Server. The service will not survive a reboot. We have followed
the service install to the letter, and have not used directory paths with
embedded spaces etc.
We have tried to run Tomcat's "startup" at system startup, using "autoexnt",
but Tomcat dies after a Logoff/login.
Does any of the later Milestone builds solve the service problem? This is a
big issue and I have yet to see any real solutions to this...
Please respond to [EMAIL PROTECTED]
Thanks,
Joe Siebenmann
Inciscent
Phone: 703-205-5927
Fax: 703-876-5973
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
