You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/08/10 23:30:00 UTC

[jira] [Commented] (ARTEMIS-3929) Changing OpenWireProtocolManager::clientIDs to a concurrent Hash Map

    [ https://issues.apache.org/jira/browse/ARTEMIS-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578182#comment-17578182 ] 

ASF subversion and git services commented on ARTEMIS-3929:
----------------------------------------------------------

Commit 568eb70fcda9737b38871a3bff1e111bad784091 in activemq-artemis's branch refs/heads/main from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=568eb70fcd ]

ARTEMIS-3929 Improving OpenWire clientIDSet

I have seen this contention while I was testing ARTEMIS-3928

This does change any semantics and current tests should be enough to validate this change


> Changing OpenWireProtocolManager::clientIDs to a concurrent Hash Map
> --------------------------------------------------------------------
>
>                 Key: ARTEMIS-3929
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3929
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>
> as I was testing ARTEMIS-3928 I found this contention with the clientID hashMap, what was causing the entire broker to freeze when every client was failing.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)