[
https://issues.apache.org/jira/browse/TAP5-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984829#action_12984829
]
Howard M. Lewis Ship commented on TAP5-1422:
--------------------------------------------
I believe I added another issue w.r.t. having mulitple phases of shutdown; this
unregistering belongs in the early phase (before proxies are deactivated, which
should happen last).
> 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.
