[
https://issues.apache.org/jira/browse/AMQ-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264898#comment-13264898
]
Timothy Bish commented on AMQ-3816:
-----------------------------------
Recommend you try and create a JUnit test that demonstrates the issue, testing
here indicates that things are working as expected.
> Broker does not retain messages for a STOMP durable consumer if the broker
> restarts while the consumer was running
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-3816
> URL: https://issues.apache.org/jira/browse/AMQ-3816
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, stomp
> Affects Versions: 5.5.1
> Environment: Perl STOMP clients on UNIX OS.
> Reporter: Buchi Reddy B
>
> We have noticed that the broker does not deliver some messages to a durable
> consumer in the following scenario.
> 1/ Start ActiveMQ broker, Perl STOMP producer on topics with persistence and
> Perl STOMP consumer with durable topics.
> 2/ Kill the broker while the consumer and producer are running.
> 3/ Kill the consumer. We have kept the producer running all these while.
> 4/ Restart the broker and producer will connect to it and continue to send
> the messages.
> 5/ Restart the consumer. We have noticed that the consumer was missing big
> chunk of messages sent by the producer when the consumer was down. But, we
> expect the consumer to receive these messages since it's a durable consumer
> and did not unsubscribe from these topics.
> I have enabled TRACE level logging for the broker and checked that the broker
> is recovering the durable subscription information from the kaha db logs when
> it restarts and marks the durable consumer as inactive durable subscription.
> However, broker does not seem to retain the messages for this durable
> consumer until the consumer comes up again.
> Is this expected? Does not broker guarantee message redelivery for durable
> consumers when the broker itself restarts?
> Please let me know if we have any configurations on the broker/client side to
> avoid these kind of issues.
--
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
