Github user tabish121 commented on the issue:

    https://github.com/apache/activemq-artemis/pull/2423
  
    I'd say none of them are really the right way to go.  I'd suggest your 
organization create a custom broker plugin that does whatever protocol 
violating things are acceptable to you and your team and not allow for the 
inevitable issues that arise from violating the specification from being 
dropped directly into the broker.  You could also (if you really care about the 
message user id no matching) reject incoming messages there are close the 
connection of the offending client.  


---

Reply via email to