You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Josh Canfield (JIRA)" <ji...@apache.org> on 2011/01/21 03:15:43 UTC
[jira] Created: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server if
more than one bean is registered
java.util.ConcurrentModificationException when shutting down jmx server if more than one bean is registered
-----------------------------------------------------------------------------------------------------------
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
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server
Posted by "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:
In MBeanSupportImpl the registryDidShutdown handler tries to remove items from a set that it's iterating over 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
> 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
>
> In MBeanSupportImpl the registryDidShutdown handler tries to remove items from a set that it's iterating over causing the exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989947#comment-12989947 ]
Hudson commented on TAP5-1422:
------------------------------
Integrated in tapestry-5.2-freestyle #260 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/260/])
Fix for TAP5-1422 - pulled the registeredBeans into another data structure to iterate over so we can remove them from the set.
> 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
> Fix For: 5.3.0
>
>
> In MBeanSupportImpl the registryDidShutdown handler tries to remove items from a set that it's iterating over causing the exception.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server
Posted by "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.
[jira] Commented: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server
Posted by "Josh Canfield (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984842#action_12984842 ]
Josh Canfield commented on TAP5-1422:
-------------------------------------
Sorry, this wasn't a very good defect report. The issue is with the MBeanSupportImpl in the jmx package The code above grabs an iterator and then removes items from the underlying set.
We'll probably see other errors if the registered beans depend on services.
> 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.
[jira] Resolved: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server
Posted by "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 resolved TAP5-1422.
---------------------------------
Resolution: Fixed
Fix Version/s: 5.3.0
> 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
> Fix For: 5.3.0
>
>
> In MBeanSupportImpl the registryDidShutdown handler tries to remove items from a set that it's iterating over causing the exception.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server
Posted by "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 resolved TAP5-1422.
---------------------------------
Resolution: Fixed
Fix Version/s: 5.3.0
> 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
> Fix For: 5.3.0
>
>
> In MBeanSupportImpl the registryDidShutdown handler tries to remove items from a set that it's iterating over causing the exception.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server if
more than one bean is registered
Posted by "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 reassigned TAP5-1422:
-----------------------------------
Assignee: Josh Canfield
> java.util.ConcurrentModificationException when shutting down jmx server if more than one bean is registered
> -----------------------------------------------------------------------------------------------------------
>
> 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 when more than one item is present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server
Posted by "Josh Canfield (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984842#action_12984842 ]
Josh Canfield commented on TAP5-1422:
-------------------------------------
Sorry, this wasn't a very good defect report. The issue is with the MBeanSupportImpl in the jmx package The code above grabs an iterator and then removes items from the underlying set.
We'll probably see other errors if the registered beans depend on services.
> 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.
[jira] Commented: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989947#comment-12989947 ]
Hudson commented on TAP5-1422:
------------------------------
Integrated in tapestry-5.2-freestyle #260 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/260/])
Fix for TAP5-1422 - pulled the registeredBeans into another data structure to iterate over so we can remove them from the set.
> 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
> Fix For: 5.3.0
>
>
> In MBeanSupportImpl the registryDidShutdown handler tries to remove items from a set that it's iterating over causing the exception.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server
Posted by "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.
[jira] Updated: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server
Posted by "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:
In MBeanSupportImpl the registryDidShutdown handler tries to remove items from a set that it's iterating over 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
> 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
>
> In MBeanSupportImpl the registryDidShutdown handler tries to remove items from a set that it's iterating over causing the exception.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TAP5-1422)
java.util.ConcurrentModificationException when shutting down jmx server if
more than one bean is registered
Posted by "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 reassigned TAP5-1422:
-----------------------------------
Assignee: Josh Canfield
> java.util.ConcurrentModificationException when shutting down jmx server if more than one bean is registered
> -----------------------------------------------------------------------------------------------------------
>
> 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 when more than one item is present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.