[jira] Resolved: (QPID-163) Client ID should not be resettable

["Robert Greig (JIRA)" <qp...@incubator.apache.org>]

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

Robert Greig resolved QPID-163.
-------------------------------

    Resolution: Fixed

We now check client id cannot be reset.

> Client ID should not be resettable
> ----------------------------------
>
>                 Key: QPID-163
>                 URL: https://issues.apache.org/jira/browse/QPID-163
>             Project: Qpid
>          Issue Type: Bug
>          Components: JMS Compliance
>    Affects Versions: M1
>            Reporter: Robert Greig
>         Assigned To: Robert Greig
>            Priority: Minor
>             Fix For: M2
>
>
> The JMS specification does not allow the resetting of the client id. Currently we do not throw any exception.
> A closely related issue is that with AMQP it is not possible to create a connection without a client id - if one if not specified the system generates one that is unique. However it is not entirely clear from the documentation of Connection whether to be JMS compliant you need to be able to set the client id separately from connection creation (it does indicate that the client id if set separately must be done before any other operation on the connection).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira