Uploaded image for project: 'JBoss Enterprise SOA Platform'
  1. JBoss Enterprise SOA Platform
  2. SOA-2143

Active JMX connection causes deadlock/race in jbrules.esb startup

    Details

      Description

      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.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jypma Jan Ypma
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: