I know that crashing implies unexpected, but anyways. We are running this version of JBoss on 200 different servers (windows 2008 server, 4GB mem), each configured alike and individually (none talk to another). About 5% of these are having JBoss crash on a daily basis. We are only running 1 application, a web app, about 70 EJBs, and use of JMS. There are only up to 10 client request per server and most likely not concurrent, meaning the server stays idle a lot. Ive checked the server.log and see no logging leading up to the crashes. I only know the app has crashed because I get alerts on the service not being started. So yes, we are running as a configured service and each server and its clients are behind a very locked down firewall (ie. no internet access).
I know that with even all this information, no one can help me pinpoint the issue, but what can I configure to allow some more server side logging as to what is happening during the crash? I don't really want to, but I may have to configure the windows service to start it on failure, but that is just sweeping the dirt under the rug.
Any help would be appreciated.
Enable TRACE logging, wat exactly happens when ur server "crashes". Look at boot.log to determine whether you server actually did boot up successfully
Is your EJB app using any logging framework, if so, wat is in the applications log files. Also look at server.log