You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Michael Andre Pearce (JIRA)" <ji...@apache.org> on 2017/06/17 08:25:01 UTC

[jira] [Resolved] (ARTEMIS-1207) [Core JMS Client] Align order of when setClientId can be called with AcitveMQ5 and QPID

     [ https://issues.apache.org/jira/browse/ARTEMIS-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Andre Pearce resolved ARTEMIS-1207.
-------------------------------------------
       Resolution: Fixed
         Assignee: Michael Andre Pearce
    Fix Version/s: 2.2.0

> [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
>            Assignee: Michael Andre Pearce
>             Fix For: 2.2.0
>
>
> 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.4.14#64029)