Hey Chuck,
I have rebooted a few times, and reinstalled the u25 JDK on two occasions (on
the same restored VM snapshot). I have been going back to the u24 JDK as my
starting point, so I'll try to rip that out as well and put it back in.
Per my previous email a few minutes ago, I'll see how it
After some waiting with Tomcat still down, I tried startup.bat again, and so
far I'm not getting any errors. I've been starting and stopping Tomcat with
the .bat scripts, and can't seem to get it to break. Time has been my enemy
the past few days with this, so I'm expecting it to break at some
Andre: I followed your idea and did the following - uninstalled the .exe
install of 6.0.32, extracted the 64-bit zip, and copied my old "conf" folder
back on top of the one that the zip created. Added the environment variable
JAVA_HOME in Windows. Ran startup.bat - Tomcat tries to start, but
Chuck: Before I encountered this, I had "Maximum memory pool" at 2048 (and
-XX:MaxPermSize=256m), as that's what the app I am looking to install wants.
It worked fine then, but after the stop/start, failed. When Tomcat decided to
finally come back to life earlier today after a power down and
Also upgraded the 64-bit JDK, as Konstantin mentioned there was a new update.
Still throws the same error in the Windows' Application log, but just a new
faulting module path (changed it to the JDK version of jvm.dll):
Faulting application name: tomcat6.exe, version: 1.0.5.0, time stamp: 0x
You are correct - through the system tray GUI/tomcat6w.exe.
Just a question : where/how are you actually changing the JVM parameters ?
(I presume it is by using the GUI tomcat6w.exe, but it doesn't hurt to ask)
-Original Message-
From: André Warnier
To: Tomcat Users List
It could - haven't figured that one out yet :)
More info: After a couple starts and stops of the service, it was fine, so I
decided to start "customizing" Tomcat for the application I need to install.
Stopped Tomcat, added "-XX:MaxPermSize=256m" and "-Xmx2048m" to the JVM
options, and it won'
Hi Konstantin,
Thanks for your reply. For the info you requested:
-No, no other log messages generated. It looks like the JVM itself just fails
to start.
-I didn't see any hs_err*.log files anywhere.
-Positive on the hardware - it is 64-bit.
-The "Native" connector is disabled for now - I h
Hi all,
Did a vanilla Tomcat 6.0.32 install (.exe package) on a 64-bit Windows 2008 R2
server. The service starts and stops fine, but after a while (say, roughly one
day), I get the following error message in Windows' Application log when trying
to start Tomcat from a st
