Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1082072

Summary: need WFLY-3124 backported to fix "JXM PluggableMBeanServerImpl assumes RealmUser principal"
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: John Mazzitelli <mazz>
Component: JMXAssignee: Kabir Khan <kkhan>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: hrupp, kkhan, pkremens, rhatlapa
Target Milestone: ER4   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-28 15:37:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1069606, 1224257    

Description John Mazzitelli 2014-03-28 15:44:10 UTC
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.

Comment 1 Kabir Khan 2014-03-28 16:00:07 UTC
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.

Comment 2 John Mazzitelli 2014-04-15 14:30:18 UTC
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.

Comment 3 Kabir Khan 2014-04-15 17:29:41 UTC
https://github.com/jbossas/jboss-eap/pull/1240

Comment 4 Kabir Khan 2014-04-25 15:12:55 UTC
Moving to ER4 since ER3 is the new beta candidate, and is ER2+beta blockers only

Comment 5 Petr Kremensky 2014-05-23 09:39:08 UTC
Verified on EAP 6.3.0.ER4.