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

Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2017/08/08 17:09:00 UTC

[jira] [Created] (ARTEMIS-1332) The broker should always return a response when a client adds metadata

Christopher L. Shannon created ARTEMIS-1332:
-----------------------------------------------

             Summary: The broker should always return a response when a client adds metadata
                 Key: ARTEMIS-1332
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1332
             Project: ActiveMQ Artemis
          Issue Type: Bug
    Affects Versions: 2.2.0
            Reporter: Christopher L. Shannon
            Assignee: Christopher L. Shannon
             Fix For: 2.3.0


When adding metadata to a session (such as when a JMS client adds a clientId) the client will never receive a response if there is an exception (other than duplicate client id) on the broker side and the client will just hang.  This scenario could happen if a broker plugin throws an ActiveMQException during the beforeSessionMetadataAdded() method call.  An example use case when an exception could be thrown is if a plugin writer wants to add extra security or put restrictions on a clientId name (length, type of characters, etc).




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)