Just as an update, I was able to find a solution to the problem. In order to spawn a native Process from an MBean required 3 threads and a signal handler. One thread handled the exec() and destroy() of the Process and implemented a signal handler to catch SIGTERM. The other two threads were typical stdout/stderr consumers to grab the output of the Process.
The key to the resolution was the introduction of a signal handler. I thought JBoss AS would object, but it seemed to work fine. I can either call Process.destroy() and kill the spawned process without affecting JBoss, or externally just "kill -9" the PID of the process without affecting JBoss. The signal handler for the thread which exec'd the Process catches the SIGTERM and my JBoss AS no longer exits with a sudden shutdown hook call. Thanks for the feedback. Regards, Keith View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952625#3952625 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952625 All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
