[ https://issues.apache.org/jira/browse/AMQ-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Blyth updated AMQ-3594:
------------------------------
Attachment: StuckMessagesTest.java
Unit test for reproducing the problem
> Stuck messages in topic after restart of ActiveMQ
> -------------------------------------------------
>
> Key: AMQ-3594
> URL: https://issues.apache.org/jira/browse/AMQ-3594
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.5.0
> Environment: Windows
> Reporter: Daniel Blyth
> Attachments: StuckMessagesTest.java
>
>
> If topic contains message and ActiveMQ is restarted, then the number of message equal to the maxPageSize will be stuck in the topic. A subscriber will only received n - maxPagSize messages. The messages will be stuck until a new message is published to the topic. Queues seems to work fine with this same scenario.
> This problem only occurs for topics that were created at startup of ActiveMQ. This issue does not occur for topics created dynamically. This problem does not exist in ActiveMQ 5.3.1.
> Here are the steps to repeating the problem I am seeing:
> 1. Subscriber registers with topic
> 2. Bring subscriber offline
> 3. Publish n messages to topic
> 4. Restart ActiveMQ
> 5. Bring subscriber online
--
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