[ 
https://issues.apache.org/jira/browse/ARTEMIS-4523?focusedWorklogId=893706&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-893706
 ]

ASF GitHub Bot logged work on ARTEMIS-4523:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Dec/23 10:24
            Start Date: 04/Dec/23 10:24
    Worklog Time Spent: 10m 
      Work Description: gtully commented on code in PR #4700:
URL: https://github.com/apache/activemq-artemis/pull/4700#discussion_r1413658950


##########
artemis-protocols/artemis-openwire-protocol/src/main/java/org/apache/activemq/artemis/core/protocol/openwire/OpenWireConnection.java:
##########
@@ -779,11 +782,18 @@ private void doFail(ActiveMQException me, String message) 
{
       }
       try {
          if (this.getConnectionInfo() != null) {
-            protocolManager.removeConnection(this.getConnectionInfo(), me);
+            
protocolManager.removeConnection(this.getConnectionInfo().getClientId(), this);
          }
-      } catch (InvalidClientIDException e) {
-         logger.warn("Couldn't close connection because invalid clientID", e);
       } finally {
+         try {
+            // doing the disconnect on the finally for extra caution.
+            // if removeConnection throws an exception of any kind, this 
should still happen

Review Comment:
   I think delete this comment, it is clear by the use of finally





Issue Time Tracking
-------------------

    Worklog Id:     (was: 893706)
    Time Spent: 50m  (was: 40m)

> Failover leaving consumers and producers behind
> -----------------------------------------------
>
>                 Key: ARTEMIS-4523
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4523
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.31.2
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>             Fix For: 2.32.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Failover in OpenWire could leave consumers, producers and internal sessions 
> hanging behind.
> If the failover happened in a race condition where the new connection 
> (reconnection) happened before the client failure.. you could end with 
> consumers without connections.



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

Reply via email to