org.jboss.jmx.connector.invoker.InvokerAdaptorService.java

If multiple Threads concurrently try to add a NotificationListener to the same MBean then a put to the HashMap "remoteListeners"
is done concurrently (unsynchronized).

This leads in some cases (e.g. HashMap has to grow) to endless loops of this threads and they are consuming CPU.

I know that the initial reason was a programming mistake on our side (missing removeNotificationListener() which causes the
growing of the HashMap) but nevertheless this is a bug in InvokerAdaptorService.java.

I required i can supply the stacktrace of a Thread dump.