See the stacktrace bellow and https://jira.jboss.org/jira/browse/JBPROFILE-6. From the nature of the bug, it's not easy to reproduce, but this is how it happened: 1) Start the default profile 2) Log in to the AS console 3) Deploy some Ear with embedded war 4) When AS console page is rendering (and RHQ is scanning the ProfileService), this CMEx occurs. 05:26:29,016 ERROR [StandaloneManagedDeploymentDiscoveryComponent] Unable to get deployment for type ejb2x java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) at java.util.HashMap$ValueIterator.next(HashMap.java:822) at org.jboss.profileservice.management.ManagementViewImpl.getDeploymentNamesForType(ManagementViewImpl.java:1104) at org.rhq.plugins.jbossas5.AbstractManagedDeploymentDiscoveryComponent.discoverResources(AbstractManagedDeploymentDiscoveryComponent.java:69) at sun.reflect.GeneratedMethodAccessor249.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:266) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) 05:26:29,017 WARN [InventoryManager] Failure during discovery for [EJB2 JAR] Resources - failed after 2809 ms. java.lang.Exception: Discovery component invocation failed. at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:270) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NullPointerException at org.rhq.plugins.jbossas5.AbstractManagedDeploymentDiscoveryComponent.discoverResources(AbstractManagedDeploymentDiscoveryComponent.java:76) at sun.reflect.GeneratedMethodAccessor249.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:266) ... 5 more
Ozizka We need to get to the bottom of the java.util.ConcurrentModificationException from AS, please raise a JBAS jira for this and assign to Scott. Thanks Charles
The NPE has been fixed in RHQ w/ commit f5bf932 which has been pushed to the release-3.0.0 branch. A JBAS JIRA still needs to be opened for the underlying CME.
Done: https://jira.jboss.org/browse/JBAS-8271
So far, no work done on JBAS-8271.
I'm re-opening this as I see no reference that this issue has actually be QE'd in the master branch
Removing dependency on jon241 bug
Verified on build #170 (Version: 4.1.0-SNAPSHOT Build Number: 67e6127) Discovered JBoss-EAP-5.1 and uploaded ear with embedded war (jboss-seam-booking.ear) The ear with embedded war is deployed successfully. No error is observed in UI and server log. Marking as verified.
Bulk closing of old issues that are in VERIFIED state.