I have JBoss 4.2.2.GA running on a box with Win 2003 Server SP2. The Java version is 1.6.0_07-b06. JBoss is set up to run as a service along with mySQL and Apache HTTP.
When looking at the event viewer for system messages I am seeing quite a few errors with the JBoss service terminating unexpectedly. It automatically restarts the service so it's not causing a significant issue for the users as it restart pretty quick. But I really need to determine what is causing this.
My problem is I don't see ANYTHING on the logs that tells me why it stopped in the first place. After looking at all the logs I don't know where to start trying to determine the cause.
I would appreciate some suggestions as to how to go about determining the cause of the terminations.
What mechanism are you using to run JBossAS as a service (full name and URL, please)?
By "looking at all the logs" do you mean the operating system logs or the JBossAS logs? I doubt that the OS logs would give any clues.
This could be a difficult issue to track down. I know because I have tried to help with similar posts before. The app server will shut down if it receives a SIGQUIT signal or if someone invokes the shutdown operation on the ?? MBean (sorry, to lazy to look up the MBean name right now). Unfortunately, both shutdown mechanisms look about the same in the logs. Something like this:
2008-09-09 10:46:26,461 INFO [org.jboss.system.server.Server] Runtime shutdown hook called, forceHalt: true 2008-09-09 10:46:26,461 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Notified to shutdown 2008-09-09 10:46:26,461 INFO [org.jboss.system.server.Server] JBoss SHUTDOWN: Undeploying all packages
If the server log shows no errors that resulted in a shutdown, about all you can do is coordinate the time of when the shutdown process started with other events happening on the system.
I have checked all the JBoss logs. Both for my application and the log that JBoss keeps itself. There is nothing. The only reason we know this is happening is because of the messages in the system event log. No other logs, system or otherwise, show any problems. The only thing that is related is that the boot.log in the JBoss log directory has the same creation time stamp as the last failed event in the event log.
It's really weird. In investigating this I found that there are other programs that have known failures like this. IIS is known to have interruptions similar to this that are caused by anti-virus packages. I have the support programmer looking into that as a possible cause here.