There are two integration issues between procrun and JBoss bootstrap process after further investigation: 1) With procrun launcher, the initial context class loader is null, causing JBoss to set a null parent class loader on its URL bootstrap class loader - this explains why subsequently classes from run.jar are not visible within the bootstrap process. Setting the context class loader to the class loader of org.jboss.Main when it is null solves this problem. This is the setup found when running through java.exe 2) Termination of the main thread (which does nothing but spawning the bootstrap thread) causes the JVM to exit with procrun while the bootstrap thread is loading the server. With java.exe, termination of the main thread does not have any effect, the JVM will continue to run. Does anybody have insight into or any info regarding these two issues and what the best fix would be? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4245018#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...