[
https://issues.apache.org/jira/browse/ARTEMIS-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16580000#comment-16580000
]
ASF GitHub Bot commented on ARTEMIS-2024:
-----------------------------------------
Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/2246
The spec also says that the preferred way to set the client id is via the
CF. I think we just have to chalk this one up as the spec being ambiguous. I
can see how people may interpret one way or the other.
> 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)
