6.1 Rollup 2 patches cause JMX initialization errors on Windows
Environment
- JBoss Fuse 6.1 R2 and above
- Windows
Issue
After installing a patch higher than 6.1 Rollup 2 we now regularly see the following error at the startup of JBoss Fuse.
Please wait while JBoss Fuse is loading...
84% [============================================================> ]
Exception in thread "JMX Connector Thread [service:jmx:rmi://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-root]" java.lang.RuntimeException:
Port already in use: 44444;
You may have started two containers. If you need to start a second container or the default ports
are already in use update the config file etc/org.apache.karaf.management.cfg and change the
Registry Port and Server Port to unused ports.
This error may be logged multiple times, in rare cases constantly. If raised constantly, then the container fails to start up fully.
Resolution
Upgrade to patch level 6.1 R4P1 to get this bug fixed.
A possible workaround:
It seems there are two instances of the bundle org.apache.karaf.management.server installed when the problem reproduces, but they are of different versions (patched and unpatched):
bundle71
mvn:org.apache.karaf.management/org.apache.karaf.management.server/2.3.0.redhat-610379
bundle24
mvn:org.apache.karaf.management/org.apache.karaf.management.server/2.3.0.redhat-611436
Uninstalling the older version of the two bundles (i.e. 2.3.0.redhat-610379) using osgi:uninstall should work around the issue on subsequent restarts.
Root Cause
Bug ENTESB-3034.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
