Just a note for those who are keeping score at home. I found a
workaround to this problem -- we renamed the JAVA_HOME\jre\bin\server\
folder so that the service.bat file would not find it and would
therefore use the jvm.dll found in JAVA_HOME\jre\bin\client, and the
service became stable. I'm still not entirely sure what the problem
was, but having a workaround is good enough for the time being.
Especially since we install the JRE instead of the JDK on production
machines, and the JRE only comes with the client version of the JVM.
Thanks to any who pondered this question. And if you happen to
encounter a similar problem and learn more about the explanation, I'd
love to know what you find.
Thanks,
Roger Alix-Gaudreau
-----Original Message-----
From: Roger Alix-Gaudreau
Sent: Wednesday, January 04, 2006 5:11 PM
To: users@tomcat.apache.org
Subject: Tomcat 5.5.9 on Win2003 crashes as service but runs from
startup.bat
Hi everyone,
I've encountered a problem while installing Tomcat and deploying my
company's JSF application, and I'm hoping someone can help point me
toward a solution, as I've not had much luck digging through Google thus
far.
I'm using Tomcat 5.5.9 and Java 1.5.0_02. Until today, we've been
starting and stopping Tomcat manually, using startup.bat and
shutdown.bat, and everything works as expected in both my Windows 2000
SP4 development environment and our Windows 2003 Enterprise Edition SP1
services/test environment. The only modification to server.xml is to
include a Realm element for my database, to log the credentials and
other necessary data for container-managed security.
Today, I used service.bat (included in Tomcat\bin) to install Tomcat as
a service, so that manual startup and shutdown would not be necessary.
I made one change to service.bat - I had to add a jar file to the
PR_CLASSPATH variable so that the installed service would have access to
a class that is normally identified in the CLASSPATH environment
variable. In all other respects, service.bat is the same as was
packaged in the original Tomcat 5.5.9 zip.
When I install Tomcat as a service on my Windows 2000 SP4 machine, the
service starts up and I'm able to load the Tomcat page, load my
application and work as expected. When I install Tomcat as a server on
my Windows 2003 SP1 machine, however, the service terminates
unexpectedly within a few moments.
The Event Viewer shows an event ID of 7034. Running "sc query Tomcat5"
to get more details shows me a WIN32_EXIT_CODE of 1067, which translates
to "The service terminated unexpectedly" in the Windows SDK docs.
Looking in the Tomcat logs, I find the following error message related
to initializing the JVM:
JVMPI not supported with this garbage collector; please
refer to the GC/JVMPI documentation
I'm using whatever garbage collector settings are default for the
1.5.0_02 JVM, so I'm at a loss to explain why it works on one machine
but not the other, unless it's got something to do with an operating
system incompatibility.
Has anyone else seen this problem? If so, is there a solution? Am I
required to upgrade Java or Tomcat?
Thanks in advance for any help and advice you might be able to offer.
__________________________________________________
Roger Alix-Gaudreau | Senior Analyst, RFID Development
Manhattan Associates, Inc.
Phone: +1 678-597-6881
Cell: +1 401-368-9980
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
http://www.manh.com <http://www.manh.com>
MOMENTUM 2006
Supply Chain Know How. Right Now.
Want to make your supply chain better... and your job easier?
Join us for Momentum 2006, May 21-24, in Orlando, Florida. Visit
www.manh-momentum.com <BLOCKED::http://www.manh-momentum.com/> today
and register early for best rates.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
