You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Daniel Blyth (Created) (JIRA)" <ji...@apache.org> on 2011/11/14 23:03:52 UTC
[jira] [Created] (AMQ-3594) Stuck messages in topic after restart
of ActiveMQ
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
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
[jira] [Closed] (AMQ-3594) Stuck messages in topic after restart of
ActiveMQ
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Issue Comment Edited] (AMQ-3594) Stuck messages in topic
after restart of ActiveMQ
Posted by "Daniel Blyth (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149986#comment-13149986 ]
Daniel Blyth edited comment on AMQ-3594 at 11/14/11 10:08 PM:
--------------------------------------------------------------
Attached unit test for reproducing the problem
was (Author: daniel.blyth):
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 issue occurs with out of the box ActiveMQ. The only changes I made were to maxPageSize and the adding the destination to the activemq.xml.
> I attached a unit that can be used to reproduce the 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
[jira] [Updated] (AMQ-3594) Stuck messages in topic after restart
of ActiveMQ
Posted by "Daniel Blyth (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Blyth updated AMQ-3594:
------------------------------
Description:
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 issue occurs with out of the box ActiveMQ. The only changes I made were to maxPageSize and the adding the destination to the activemq.xml.
I attached a unit that can be used to reproduce the problem.
was:
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
> 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 issue occurs with out of the box ActiveMQ. The only changes I made were to maxPageSize and the adding the destination to the activemq.xml.
> I attached a unit that can be used to reproduce the 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
[jira] [Updated] (AMQ-3594) Stuck messages in topic after restart
of ActiveMQ
Posted by "Daniel Blyth (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Blyth updated AMQ-3594:
------------------------------
Description:
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. 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.
was:
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 issue occurs with out of the box ActiveMQ. The only changes I made were to maxPageSize and the adding the destination to the activemq.xml.
I attached a unit that can be used to reproduce 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 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. 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.
--
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
[jira] [Updated] (AMQ-3594) Stuck messages in topic after restart
of ActiveMQ
Posted by "Daniel Blyth (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Blyth updated AMQ-3594:
------------------------------
Description:
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.
was:
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.
> 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 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
[jira] [Updated] (AMQ-3594) Stuck messages in topic after restart
of ActiveMQ
Posted by "Daniel Blyth (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (AMQ-3594) Stuck messages in topic after restart
of ActiveMQ
Posted by "Daniel Blyth (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Blyth updated AMQ-3594:
------------------------------
Description:
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.
was:
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. 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.
> 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 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.
--
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