Addition: the jbosssvc.exe process also exists with the jboss java process. It seems the Windows Service Management does not know the service has been stopped.
hm it seems your jboss shutdown hangs. You should start it in the console and stop it to see what goes wrong.
Also check the server.log file may be there is some clues there too.
No. My JBoss did not hang. the JBoss java process and the jbosssvc.exe process both exit in 100s. But after 125s, windows service managment console pop up the error.
Check in event logs. If jboss finishes ok your will have "Stopping service ..."
if you have "Service terminated..." or nothing there is something wrong.
Probably 100 sec is still not enough for a clean shutdown and the processes are terminated by jboss service, the service terminates too and you get the error message.
My last lines are below. Will the exception cause the error? I find the jboss java process and jbosssvc.exe exit in 40s, so they are terminated by jboss service.
2010-06-10 09:26:44,639 INFO [org.apache.catalina.core.StandardService] Stopping service jboss.web
2010-06-10 09:26:44,655 INFO [org.apache.coyote.http11.Http11Protocol] Stopping Coyote HTTP/1.1 on http-0.0.0.0-8080
2010-06-10 09:26:44,655 INFO [org.apache.coyote.ajp.AjpProtocol] Stopping Coyote AJP/1.3 on ajp-0.0.0.0-8009
2010-06-10 09:26:44,686 WARN [org.jboss.resource.adapter.mail.inflow.NewMsgsWorker] Interrupted waiting for new msg check
at java.lang.Object.wait(Native Method)
Will the exception cause the error?
I don't think it should , but you should check your code to make sure the exception doesn't cause other troubles in application.