[ https://issues.apache.org/jira/browse/ARTEMIS-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118706#comment-16118706 ]
ASF GitHub Bot commented on ARTEMIS-1332: ----------------------------------------- Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/1450 @cshannon ahaaa!!! thanks a lot... you just saved me a task ! 👍 Someone reported me an issue at Red Hat.. I think this is the cause. > 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)