Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

JMX error when running Jedis on JBoss 5.2.

See original GitHub issue

The following exception is thrown when Jedis 2.6.2 on JBoss 5.2:

javax.management.NotCompliantMBeanException: Cannot obtain mxbean interface for: class org.apache.commons.pool2.impl.GenericObjectPool

The full stack trace is:

javax.management.NotCompliantMBeanException: Cannot obtain mxbean interface for: class org.apache.commons.pool2.impl.GenericObjectPool
    at org.jboss.mx.mxbean.MXBeanMetaData.<init>(MXBeanMetaData.java:174)
    at org.jboss.mx.mxbean.MXBeanDelegate.buildMBeanInfo(MXBeanDelegate.java:456)
    at org.jboss.mx.mxbean.MXBeanDelegate.getMBeanInfo(MXBeanDelegate.java:334)
    at org.jboss.mx.server.RawDynamicInvoker.getMBeanInfo(RawDynamicInvoker.java:187)
    at org.jboss.mx.server.RawDynamicInvoker.preRegister(RawDynamicInvoker.java:205)
    at org.jboss.mx.server.registry.BasicMBeanRegistry.invokePreRegister(BasicMBeanRegistry.java:700)
    at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:227)
    at sun.reflect.GeneratedMethodAccessor102.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
    at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1431)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1426)
    at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:376)
    at org.apache.commons.pool2.impl.BaseGenericObjectPool.jmxRegister(BaseGenericObjectPool.java:947)
    at org.apache.commons.pool2.impl.BaseGenericObjectPool.<init>(BaseGenericObjectPool.java:132)
    at org.apache.commons.pool2.impl.GenericObjectPool.<init>(GenericObjectPool.java:107)
    at redis.clients.util.Pool.initPool(Pool.java:43)
    at redis.clients.util.Pool.<init>(Pool.java:31)
    at redis.clients.jedis.JedisPool.<init>(JedisPool.java:73)
    at redis.clients.jedis.JedisPool.<init>(JedisPool.java:15)

I’ve tried to upgrade commons-pool2 to the latest version but had no success.

Issue Analytics

State:
Created 8 years ago
Comments:29

Top GitHub Comments

1reaction

jianzlicommented, Jun 6, 2018

@nemo97 would you mind sharing your fix for this?

0reactions

pkgoncalvescommented, Sep 17, 2020

Hi guys! I know this is an old issue, but I had to do a little maintenance on the legacy system that I got the error a couple of years ago and even after upgrading Jedis to version 3.3.0 the error still happens on JBoss EAP 5.2 but I was able to avoid it setting the property jxmEnabled to false on JedisPoolConfig.

JedisPoolConfig config = JedisPoolConfig(); config.setJmxEnabled(false);

Don’t know if disabling JMX is a viable workaround to everyone using JBoss EAP 5.2. But it’s quite an old server version, maybe it’s not worth anymore supporting it. 💁