activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-1777) Access to ConnectionEventListeners in RA's ActiveMQManagedConnection is not synchronized
Date Wed, 11 Jun 2008 23:16:00 GMT

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

Rob Davies resolved AMQ-1777.
-----------------------------

    Fix Version/s: 5.2.0
       Resolution: Fixed

Fixed by SVN revision 666887

> Access to ConnectionEventListeners in RA's ActiveMQManagedConnection is not synchronized
> ----------------------------------------------------------------------------------------
>
>                 Key: AMQ-1777
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1777
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JCA Container
>    Affects Versions: 5.0.0, 5.1.0
>            Reporter: Kai Hudalla
>            Assignee: Rob Davies
>            Priority: Minor
>             Fix For: 5.2.0
>
>         Attachments: amq-1777.patch
>
>
> When the RA's connection to the broker fails and the <i>ActiveMQManagedConnection.onException()</i>
method is called, all the registered <i>ConnectionEventListener</i>s are notified.
> At least in Glassfish, the registered listener then calls the <i>ActiveMQManagedConnection.removeConnectionEventListener()</i>
to unregister itself. This causes a <i>java.util.ConcurrentModificationException</i>
to be thrown since the <i>ConnectionEventListener</i> collection is modified while
the <i>onException()</i> iterates over it.
> Kai

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


Mime
View raw message