JON is being tested on EAP 6.3 DR6 and I see that https://issues.jboss.org/browse/WFLY-3124 being a problem. Here's what JON is seeing (this error causes problems, not least of which is the agents can't talk to the servers since JMX via JBoss/Remoting is involved in such communications): Caused by: java.util.NoSuchElementException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:897) [rt.jar:1.7.0_11] at java.util.HashMap$KeyIterator.next(HashMap.java:928) [rt.jar:1.7.0_11] at org.jboss.as.jmx.PluggableMBeanServerImpl$LogAction.getCallerUserId(PluggableMBeanServerImpl.java:1249) at org.jboss.as.jmx.PluggableMBeanServerImpl$LogAction.doLog(PluggableMBeanServerImpl.java:1232) This is identical to WFLY-3124. This is a blocker for JON.
There is some discussion on https://github.com/wildfly/wildfly/pull/6043 for https://issues.jboss.org/browse/WFLY-3124. Since Brian has been involved in that discussion I'd like him to take a look before dev-acking.
Just tested JON with the latest JBEAP-6.3.0.ER1 build from April 4, 2014 and still getting this error, which is a blocker for JON 3.3 (see bug 1069606). This error causes, among other problems, agents unable to talk to servers.
https://github.com/jbossas/jboss-eap/pull/1240
Moving to ER4 since ER3 is the new beta candidate, and is ER2+beta blockers only
Verified on EAP 6.3.0.ER4.