[jira] Updated: (TAP5-1422) java.util.ConcurrentModificationException when shutting down jmx server

["Josh Canfield (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Canfield updated TAP5-1422:
--------------------------------

    Description: 
The registryDidShutdown handler contains the code:

 for (final ObjectName name : this.registeredBeans)
        {
            doUnregister(name);
        }

doUnregister calls 
                    registeredBeans.remove(objectName);

thus causing the exception

  was:
The registryDidShutdown handler contains the code:

 for (final ObjectName name : this.registeredBeans)
        {
            doUnregister(name);
        }

doUnregister calls 
                    registeredBeans.remove(objectName);

thus causing the exception when more than one item is present.

        Summary: java.util.ConcurrentModificationException when shutting down jmx server  (was: java.util.ConcurrentModificationException when shutting down jmx server if more than one bean is registered)

> java.util.ConcurrentModificationException when shutting down jmx server
> -----------------------------------------------------------------------
>
>                 Key: TAP5-1422
>                 URL: https://issues.apache.org/jira/browse/TAP5-1422
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-jmx
>    Affects Versions: 5.2.0
>            Reporter: Josh Canfield
>            Assignee: Josh Canfield
>
> The registryDidShutdown handler contains the code:
>  for (final ObjectName name : this.registeredBeans)
>         {
>             doUnregister(name);
>         }
> doUnregister calls 
>                     registeredBeans.remove(objectName);
> thus causing the exception

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.