There have been some reports of the OS causing this problem. The suggested solution is to reduce the use of OS signals - this might stop the OS from sending a spurious signal that the JVM interprets as a shutdown.
This was for 1.3.x JDKs but it might work for you.
I am seeing a very similar issue. I was wondering if you were able to resolve the problem.
Were you using JDK 1.3 or 1.4? The reply to your original message hints it is a 1.3 issue.
Any help would be great!
I tried the -Xrs but it didn't seem to work (on sco openserver)
I've found that the only sure fire way for me is to start jboss via the unix at functionality, this effectively divorces the jvm process from the shell that started it. This works fine on sco and aix.