Hide Forgot
Steps to Reproduce: - Install clean deployment of JBoss SOA-P 5.0.1 - Disable JMX authentication [1] - Run the attached unit test. [1] http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.1/html/Installation_Guide/Disabling_Authentication.html project_key: SOA Originally found that maven-jboss-plugin doesn't detect JBoss SOA-P startup correctly. I created a unit test that reproduces the behaviour. Basically, the plugin starts JBoss, creates JMX connection, and polls "jboss.system:type=Server" for the "Started" attribute to become true. When launching JBoss this way, it'll start deploying services fine until (just before or after) jbrules.esb. Just before logging deployment start of jbrules.esb, the JBoss process halts (pauses) completely. After the unit test times out, and the JMX connection is broken, JBoss resumes startup, and finishes startup correctly. Forcibly terminating the unit test earlier has JBoss resume earlier as well. The JMX poll calls themselves are not blocking in the unit test. So it's the active JMX connection itself that causes JBoss SOA-P to hang around somewhere near deployment of jbrules.esb.
Test case that reproduces the defect
Attachment: Added: JBossEAPTimeout.java
Not defect in jboss, but in maven-jboss-plugin. Consule buffer isn't periodically flushed on linux, causing jboss to halt after a certain amount of output is generated and a buffer is full (probably ??kbytes).