[
https://issues.apache.org/jira/browse/APLO-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400402#comment-13400402
]
Lionel Cons commented on APLO-215:
----------------------------------
In this scenario, you are right that adding a receipt header on the DISCONNECT
frame does fix the problem. I will trigger a discussion on the STOMP spec list
to draw more attention to this practice.
However, I still have similar problems with topics that do not go away that
easily. I will open a new issue for these.
> Broker may send queued messages multiple time over SSL
> ------------------------------------------------------
>
> Key: APLO-215
> URL: https://issues.apache.org/jira/browse/APLO-215
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-99-trunk-20120621.153441-53
> Reporter: Lionel Cons
> Attachments: APLO-215.pl
>
>
> When putting messages in a queue and removing them with client side
> acknowledgments, Apollo may send some messages multiple times. Here is an
> example test output:
> $ perl test.pl
> producing 3000 messages... done
> consuming 1000 messages... done
> consuming 1000 messages... done
> consuming 1000 messages... done
> draining... drained 13 messages
> message 1000 received 2 times!
> message 1994 received 2 times!
> message 1995 received 2 times!
> message 1996 received 2 times!
> message 1997 received 2 times!
> message 1998 received 2 times!
> message 2988 received 2 times!
> message 2989 received 2 times!
> message 2990 received 2 times!
> message 2991 received 2 times!
> message 2992 received 2 times!
> message 2993 received 2 times!
> message 999 received 2 times!
> done checking
> The consumers are careful with client side acknowledgment so there should be
> nothing left for the final drainer.
> Please see the attached script for more details. You may need to play with
> the number of messages or the number of consumers.
> Note that the test script seems to work fine over STOMP. I've only seen
> problems with STOMP+SSL.
--
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
