[
https://issues.apache.org/jira/browse/ARTEMIS-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579995#comment-16579995
]
ASF GitHub Bot commented on ARTEMIS-2024:
-----------------------------------------
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/2246
@michaelandrepearce on the connection.. yeah! On the connectionFactory.
.that's a broker-specific extension. you set it on the CF as an utility for the
user.
That's just that! An utility. Setting it on the CF or on the connection it
should have the same effect.
> Enable backwards compatability of shared client ID across ConnectionFactories
> -----------------------------------------------------------------------------
>
> Key: ARTEMIS-2024
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2024
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Martyn Taylor
> Priority: Critical
>
> The fix around the JMS violation to ensure Client IDs are not shared across
> connections breaks compatability with existing users in particular usages
> within the WildFly application server. In order to continue support we
> should add a configuration option to enable the old behaviour across the
> ConnectionFactories and within the RA.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
