[
https://issues.apache.org/jira/browse/AMQ-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17107936#comment-17107936
]
ASF subversion and git services commented on AMQ-7463:
------------------------------------------------------
Commit 8b58228ca58d7111ce9715b9e8a3cb11cc76bc57 in activemq's branch
refs/heads/activemq-5.15.x from anushaCoder
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=8b58228 ]
[AMQ-7463] Use ConcurrentHashMap in client connection state to avoid
ConcurrentModificationException
(cherry picked from commit a5e70fa2d7195f4de12dc3fbc14c9bcf0890d43c)
> ActiveMQ throws concurrentModificationException in failovertransport class
> --------------------------------------------------------------------------
>
> Key: AMQ-7463
> URL: https://issues.apache.org/jira/browse/AMQ-7463
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.7.0
> Reporter: Anusha
> Assignee: Jean-Baptiste Onofré
> Priority: Blocker
> Fix For: 5.16.0, 5.15.13
>
> Attachments: activemq.jpg
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In production server, we are getting concurrent modification exception every
> 10 minutes
> at FailOverTransport class method: connectionIterruptionProcessingComplete
> Other Jira tasks have resolved concurrent Modification exception in
> different class.
> Please help. Attached screenshot of log.
>
> Thanks,
> Anusha
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
