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 have enabled it and disabled it
when I have the problem, and don't see any change. No other connectors
installed - it is whatever the default .exe install provides.
After playing with it for the past 2 hours, and shutting the virtual machine
off and turning it back on, I now get this:
[2011-05-04 11:33:31] [debug] ( prunsrv.c:1494) Commons Daemon procrun log
initialized
[2011-05-04 11:33:31] [info] ( :0 ) Commons Daemon procrun (1.0.5.0
64-bit) started
[2011-05-04 11:33:31] [info] ( :0 ) Running 'Tomcat6' Service...
[2011-05-04 11:33:31] [debug] ( prunsrv.c:1246) Inside ServiceMain...
[2011-05-04 11:33:31] [info] ( :0 ) Starting service...
[2011-05-04 11:33:31] [debug] ( javajni.c:206 ) loading jvm 'C:\Program
Files\Java\jre6\bin\server\jvm.dll'
[2011-05-04 11:33:32] [debug] ( javajni.c:660 ) Jvm Option[0]
-Dcatalina.home=C:\Program Files\Apache Software Foundation\Tomcat 6.0
[2011-05-04 11:33:32] [debug] ( javajni.c:660 ) Jvm Option[1]
-Dcatalina.base=C:\Program Files\Apache Software Foundation\Tomcat 6.0
[2011-05-04 11:33:32] [debug] ( javajni.c:660 ) Jvm Option[2]
-Djava.endorsed.dirs=C:\Program Files\Apache Software Foundation\Tomcat
6.0\endorsed
[2011-05-04 11:33:32] [debug] ( javajni.c:660 ) Jvm Option[3]
-Djava.io.tmpdir=C:\Program Files\Apache Software Foundation\Tomcat 6.0\temp
[2011-05-04 11:33:32] [debug] ( javajni.c:660 ) Jvm Option[4]
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
[2011-05-04 11:33:32] [debug] ( javajni.c:660 ) Jvm Option[5]
-Djava.util.logging.config.file=C:\Program Files\Apache Software
Foundation\Tomcat 6.0\conf\logging.properties
[2011-05-04 11:33:32] [debug] ( javajni.c:660 ) Jvm Option[6]
-Djava.class.path=C:\Program Files\Apache Software Foundation\Tomcat
6.0\bin\bootstrap.jar
[2011-05-04 11:31:12] [debug] ( javajni.c:844 ) argv[0] = start
[2011-05-04 11:31:12] [debug] ( javajni.c:891 ) Java Worker thread started
org/apache/catalina/startup/Bootstrap:main
[2011-05-04 11:31:14] [debug] ( prunsrv.c:1058) Java started
org/apache/catalina/startup/Bootstrap
[2011-05-04 11:31:14] [info] ( :0 ) Service started in -1161496934
ms.
[2011-05-04 11:31:14] [debug] ( prunsrv.c:1369) Waiting for worker to finish...
Compared to before, this time it actually did start (though the
timestamps/order of events seem to be a bit off). I'm positive this is going
to happen again though, as I didn't change anything. Is there any other way to
enable more verbose logging for this problem?
Also, do the out-of-order timestamps (and the server startup time of
-1161496934 ms) hint at anything?
-----Original Message-----
From: Konstantin Kolinko <[email protected]>
To: Tomcat Users List <[email protected]>
Sent: Wed, May 4, 2011 11:35 am
Subject: Re: Tomcat 6.0.32 on 64-bit 2008 server - "Event 1000, Application
Error"
2011/5/4 <[email protected]>:
> 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 stopped state. The title of the error is "Event 1000,
Application Error":
>
>
>
> Faulting application name: tomcat6.exe, version: 1.0.5.0, time stamp:
0x4d245ac2
> Faulting module name: jvm.dll, version: 19.1.0.2, time stamp: 0x4d4a214c
> Exception code: 0xc0000094
> Fault offset: 0x000000000051f48f
> Faulting process id: 0x9d0
> Faulting application start time: 0x01cc0a5acc256cf0
> Faulting application path: C:\Program Files\Apache Software Foundation\Tomcat
6.0\bin\tomcat6.exe
> Faulting module path: C:\Program Files\Java\jre6\bin\server\jvm.dll
> Report Id: 09f73d92-764e-11e0-af4a-005056a10003
When it happens? Is there anything in the other logs? Does Tomcat
tries to start (initialize its connectors, web applications, etc.),
or just the JVM itself plainly fails to start. Anyway, it looks like
the error happens in the JVM itself. There can be
"hs_err_pid<number>.log" files somewhere (in the currect working
directory when the crash occurred) with thread dumps in them.
Are you sure in your hardware?
What connectors do you use?
Have you installed "Tomcat Native" connector, or not?
> Latest 64-bit JDK (jdk-6u24-windows-x64.exe) is also installed,
Note, that there is 6u25 already.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
