[
https://issues.apache.org/jira/browse/ARTEMIS-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578473#comment-16578473
]
ASF GitHub Bot commented on ARTEMIS-2024:
-----------------------------------------
Github user clebertsuconic commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/2246#discussion_r209658818
--- Diff:
artemis-jms-client/src/main/java/org/apache/activemq/artemis/jms/client/ActiveMQConnection.java
---
@@ -673,12 +673,16 @@ protected final void checkClosed() throws
JMSException {
}
}
- public void authorize() throws JMSException {
+ public void authorize(boolean validateClientId) throws JMSException {
--- End diff --
@michaelandrepearce that's internal API though
> 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)
