-
1. Re: JBoss crashes with no errors on Seam application initial
peterj Oct 21, 2008 6:09 PM (in response to dolanp)Operating system? I ask because if the java process is going away, you will need to use operating-system specific tools to debug this.
Also, are you running JBossEAP from a command line or as a service? -
2. Re: JBoss crashes with no errors on Seam application initial
dolanp Oct 21, 2008 9:26 PM (in response to dolanp)It's RHEL 4. I tried attaching strace to the process but this is all I get:
futex(0x8145b94, FUTEX_WAIT, 1, NULL = -1 EINTR (Interrupted system call) PANIC: attached pid 21048 exited Process 21048 detached
-
3. Re: JBoss crashes with no errors on Seam application initial
dolanp Oct 22, 2008 10:58 AM (in response to dolanp)I get a few of these messages, maybe this is related...
DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@53f89f, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@1e81ab3{ url=null ,addedOrder=0}
-
4. Re: JBoss crashes with no errors on Seam application initial
peterj Oct 22, 2008 11:08 AM (in response to dolanp)I am not that familiar with process debugging tools on Linux, maybe someone else can help with that. I would suspect that there is some setting that will cause the OS to take a dump of the process when it crashes, and some tool to read that dump.
One thing you can try is to run the same app on another box. Often, a particular box will have a problem - bad hardware, a broken device driver, or a problematic system library. Any of those can cause a crash. Trying on another box will at least eliminate application issues. -
5. Re: JBoss crashes with no errors on Seam application initial
dolanp Oct 22, 2008 3:24 PM (in response to dolanp)Oddly enough this turned out to be an issue with X forwarding through SSH. I had gotten this message 'X connection to localhost:10.0 broken (explicit kill or server shutdown)' whenever it crashed but I figured it was incidental to the process being killed. Turns out it is actually the cause. Once I disabled X forwarding on my SSH client the application works as expected...
:)