Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-3792

use of the failover transport incorrectly suppresses javax.jms.InvalidClientIDException when clientId is already in use

    XMLWordPrintableJSON

    Details

      Description

      Chucking an javax.jms.InvalidClientIDException is currently conditional on the connection not being fault tolerant and not being a network connector which seems incorrect.
      In both cases, a duplicate connection is still a duplicate and we should wait till it is cleaned up/disposed.

      A failover variant of the test from https://issues.apache.org/jira/browse/AMQ-463 demonstrates.

      This change was introduced in http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/region/RegionBroker.java?annotate=633800 but it looks like suppression of a duplicate connectionId in TransportConnector is sufficient for the reconnect case.

        Attachments

          Activity

            People

            • Assignee:
              gtully Gary Tully
              Reporter:
              gtully Gary Tully
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: