[
https://issues.apache.org/jira/browse/AMQ-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-3792.
-----------------------------
Resolution: Fixed
fixed in http://svn.apache.org/viewvc?rev=1307142&view=rev
> use of the failover transport incorrectly suppresses
> javax.jms.InvalidClientIDException when clientId is already in use
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-3792
> URL: https://issues.apache.org/jira/browse/AMQ-3792
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.5.1
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: InvalidClientIDException, failover
> Fix For: 5.6.0
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
