Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
JBoss 4.2.3 issue because of JNDI lookup #123
See the forum for details.
A JNDI lookup during the server detection phase (done in the Weblogic Detector when collecting MBean Servers) borks the JNDI subsystem in JBoss 4.2.3 so that it is not usable anymore.
The solution would be to add a guard in addMBeanServer which checks via a class lookup whether it is really running in a Weblogic environment and only then doe the JNDI lookup.
added a commit
Apr 10, 2014
Sorry, took some time. I decided to check in the Weblogic detector whether we are running in JBoss and the avoid an JNDI lookup. This couples somewhat the Weblogic detector to JBoss but this is the fastest solution. And this extra check shouldn't harm anyway (its called only once).
@pliljenberg , could you please check, whether this works for you ? I've added this to 1.2.1 which will be released in about a week, so no hurry. If it doesn't work, we can reopen this issue and fix it for the next version.