[
https://issues.apache.org/jira/browse/AMQ-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278660#comment-13278660
]
Andreas Ländle commented on AMQ-3838:
-------------------------------------
Hi Timothy. You are right, I use NMS.Stomp - but I couldn't believe that this
should be a bug in the .Net client for two reasons.
a) I used the same client to record the network streams as attached in
ActiveMQ55/56.txt
b) The log files really show RAW network communication (captured with
WireShark) - and even a buggy client shouldn't be able to make the broker
sending two error frames in a row (I'll attach a screenshot for better
explanation).
If you've already tried to reproduce this issue with a test - could you maybe
attach the test-stub here as a patch? So I would have a good place to start and
maybe I'm able to reproduce the issue in a test (at least at my system).
> 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
>
>
> 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
