You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2012/05/31 22:38:23 UTC

[jira] [Closed] (AMQ-3594) Stuck messages in topic after restart of ActiveMQ

     [ https://issues.apache.org/jira/browse/AMQ-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-3594.
-----------------------------

       Resolution: Cannot Reproduce
    Fix Version/s: 5.7.0

Could not reproduce this, recommend moving the 5.6.0
                
> 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
>             Fix For: 5.7.0
>
>         Attachments: StuckMessagesTest.java
>
>
> If a 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:
> 1.  Subscriber registers with topic
> 2.  Bring subscriber offline
> 3.  Publish n messages to topic
> 4.  Restart ActiveMQ
> 5.  Bring subscriber online
> This issue occurs with out of the box ActiveMQ 5.5.0 and 5.5.1.  The only changes I made were to maxPageSize and adding the destination to the activemq.xml.
> I attached a unit that can be used to reproduce the problem.
> The unit test is using the DefaultMessageListenerContainer for the subscriber.  If the default cache level for the DMLC of CACHE_CONSUMER is not used this problem does not occur.

--
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