activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3838) Stomp-Transport: Multiple error frames generated
Date Mon, 21 May 2012 21:02:40 GMT

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

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

The reason you continue to get an error frame is due to changes made for: https://issues.apache.org/jira/browse/AMQ-3294
which will cause the connection to closed after a delay to prevent denial of service attacks.
 Since the client has produced a security exception its connection is now invalid and will
be terminated after a delay so that the error can be propagated to the client but the client
cannot flood the broker with large numbers of additional erroneous commands.
                
> 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

       

Mime
View raw message