Calling remote JMX server method such as getMBeanCount() by several remote clients leads to random NullPointerExceptions on the server side such as: [0m[33m18:38:11,612 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-2-thread-12) Unexpected internal error: java.lang.NullPointerException at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:49) at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55) at org.jboss.as.jmx.model.RootResourceIterator.doIterate(RootResourceIterator.java:55) at org.jboss.as.jmx.model.RootResourceIterator.iterate(RootResourceIterator.java:39) at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getMBeanCount(ModelControllerMBeanHelper.java:103) at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getMBeanCount(ModelControllerMBeanServerPlugin.java:116) at org.jboss.as.jmx.PluggableMBeanServerImpl.getMBeanCount(PluggableMBeanServerImpl.java:220) at org.jboss.remotingjmx.protocol.v2.ServerProxy$GetMBeanCountHandler.handle(ServerProxy.java:618) at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:152) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_13] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_13] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_13]
Given that the newly found NPE is tracked under BZ 1192181, closing this. The original NPE is fixed in EAP 6.4.0.ER2.