[ 
https://issues.apache.org/jira/browse/AMQ-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280929#comment-13280929
 ] 

Timothy Bish commented on AMQ-3838:
-----------------------------------

The only error that will cause this connection close is the SecurityException. 
Once the client violates a security constraint then the TransportConnection 
retains the exception as the error that's caused the eventual transport stop 
and future commands all receive this same error frame back.  Upon reconnection 
you would not receive this error frame again useless the client again attempts 
to send a message to a destination for which its not authorized, or it attempts 
to subscribe to one its not authorized to etc.
                
> Stomp-Transport: Multiple error frames generated
> ------------------------------------------------
>
>                 Key: AMQ-3838
>                 URL: https://issues.apache.org/jira/browse/AMQ-3838
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.6.0
>         Environment: Win7Enterprise;Java7;ActiveMQ 5.6
>            Reporter: Andreas Ländle
>              Labels: activemq, stomp, transport
>         Attachments: ActiveMq55.txt, ActiveMq56.png, ActiveMq56.txt, 
> Reproduce_AMQ3838_StompTest.java.patch
>
>
> I tried to update ActiveMQ 5.5 to 5.6 and discovered a behavioral change if 
> you try to send a message to an invalid queue with stomp. While v5.5 just 
> rejects the message and returns one ERROR frame, v5.6 sends multiple error 
> frames. I'll attach two network captures showing the conversation between 
> client/server in 5.5 and 5.6 - in 5.6 you'll see the repeated error frames. 
> Please let me know if I was unclear of if you need more information. Thanks 
> in advance for any assistance or hint that will help me to get around this 
> problem.

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


Reply via email to