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 a cold boot, I didn't set the heap size/MaxPermSize at all. When I touched the config and restarted, it died again. Apparently whatever it is gets unstable after a while.
Stefan: Haven't thought of that yet, though we have VM's on the same host running Win2k3 + Tomcat without a problem. Thank you to everyone that has contributed so far... -----Original Message----- From: Caldarale, Charles R <chuck.caldar...@unisys.com> To: Tomcat Users List <users@tomcat.apache.org> Sent: Wed, May 4, 2011 1:46 pm Subject: RE: Tomcat 6.0.32 on 64-bit 2008 server - "Event 1000, Application Error" > From: fsman...@netscape.net [mailto:fsman...@netscape.net] > Subject: Re: Tomcat 6.0.32 on 64-bit 2008 server - "Event 1000, Application Error" > Faulting module name: jvm.dll, version: 20.0.0.11, time stamp: 0x4da6d3c2 > Exception code: 0xc0000094 > Fault offset: 0x0000000000308eef That appears to be a divide fault. Check your options (especially heap sizes) in the tomcat6w.exe window to make sure that they make sense. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org