[
https://issues.apache.org/jira/browse/ARTEMIS-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038857#comment-16038857
]
Justin Bertram commented on ARTEMIS-1207:
-----------------------------------------
As it stands currently these are the methods from each broker that cause the
javax.jms.Connection implementation to become "dirty" such that the clientID
can't be set...
Artemis:
* getExceptionListener
* setExceptionListener
* getMetaData
* start
* stop
* createSession
Qpid Java:
* createSession
* start
ActiveMQ 5.x:
* createSession
* start
> [Core JMS Client] Align order of when setClientId can be called with
> AcitveMQ5 and QPID
> ---------------------------------------------------------------------------------------
>
> Key: ARTEMIS-1207
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1207
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Michael Andre Pearce
>
> There is a difference in behaviour of when it is valid to be able to set
> clientId though it seems the behaviour isn't clear in JMS spec, where QPID
> and ActiveMQ5 allow you to set an exception listener first, where as
> currently Artemis requires the very first call to setClientId if you wish to
> set it.
> As discussed will create and align the clients so even so not detailed in
> spec, a user of ActiveMQ5 client or QPID client can expect the same behaviour.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
