You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2011/01/28 14:09:43 UTC
[jira] Created: (AMQ-3167) possible skipped Queue messages in
memory limited configuration with fast consumers
possible skipped Queue messages in memory limited configuration with fast consumers
-----------------------------------------------------------------------------------
Key: AMQ-3167
URL: https://issues.apache.org/jira/browse/AMQ-3167
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.4.2
Reporter: Gary Tully
Assignee: Gary Tully
Fix For: 5.5.0
regression in test from https://issues.apache.org/jira/browse/AMQ-2413 required some investigation. Symptom was missing messages, turned out to be in the middle of the sequence. Issue with the priority kahadb cursors and setbatch. Set batch is invoked when the cursor memory is exhausted such that replay from the store can start at the correct point. If a call to setBatch was followed by a call to recover when there was still no memory space available, the cursor could skip the next pending message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-3167) possible skipped Queue messages in
memory limited configuration with fast consumers
Posted by "Arthur Naseef (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arthur Naseef updated AMQ-3167:
-------------------------------
Attachment: patch.amq3167.activemq-5.4.2
Patch against 5.4.2 that resolves this issue, created from a subset of the changes made on the trunk for this bug report.
> possible skipped Queue messages in memory limited configuration with fast consumers
> -----------------------------------------------------------------------------------
>
> Key: AMQ-3167
> URL: https://issues.apache.org/jira/browse/AMQ-3167
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.2
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.5.0
>
> Attachments: AMQ3167Test.java, patch.amq3167.activemq-5.4.2
>
>
> regression in test from https://issues.apache.org/jira/browse/AMQ-2413 required some investigation. Symptom was missing messages, turned out to be in the middle of the sequence. Issue with the priority kahadb cursors and setbatch. Set batch is invoked when the cursor memory is exhausted such that replay from the store can start at the correct point. If a call to setBatch was followed by a call to recover when there was still no memory space available, the cursor could skip the next pending message.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-3167) possible skipped Queue messages in
memory limited configuration with fast consumers
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-3167.
-----------------------------
Resolution: Fixed
fix in r1064660
URL: http://svn.apache.org/viewvc?rev=1064660&view=rev
> possible skipped Queue messages in memory limited configuration with fast consumers
> -----------------------------------------------------------------------------------
>
> Key: AMQ-3167
> URL: https://issues.apache.org/jira/browse/AMQ-3167
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.2
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.5.0
>
>
> regression in test from https://issues.apache.org/jira/browse/AMQ-2413 required some investigation. Symptom was missing messages, turned out to be in the middle of the sequence. Issue with the priority kahadb cursors and setbatch. Set batch is invoked when the cursor memory is exhausted such that replay from the store can start at the correct point. If a call to setBatch was followed by a call to recover when there was still no memory space available, the cursor could skip the next pending message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-3167) possible skipped Queue messages in
memory limited configuration with fast consumers
Posted by "Arthur Naseef (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992569#comment-12992569 ]
Arthur Naseef commented on AMQ-3167:
------------------------------------
In the process of creating a bug report for the test case attached above, this bug report appeared to capture the problem. Trying to backport this fix to 5.4.2, there appears to be a number of changes on which this patch depends. Any guidance on a shorter workaround until we can upgrade to 5.5 would be appreciated.
The test case attached represents a use pattern we need to support, but has been narrowed down to detect a lost message in the timeframe it takes to trigger this issue.
> possible skipped Queue messages in memory limited configuration with fast consumers
> -----------------------------------------------------------------------------------
>
> Key: AMQ-3167
> URL: https://issues.apache.org/jira/browse/AMQ-3167
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.2
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.5.0
>
> Attachments: AMQ3167Test.java
>
>
> regression in test from https://issues.apache.org/jira/browse/AMQ-2413 required some investigation. Symptom was missing messages, turned out to be in the middle of the sequence. Issue with the priority kahadb cursors and setbatch. Set batch is invoked when the cursor memory is exhausted such that replay from the store can start at the correct point. If a call to setBatch was followed by a call to recover when there was still no memory space available, the cursor could skip the next pending message.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-3167) possible skipped Queue messages in
memory limited configuration with fast consumers
Posted by "Arthur Naseef (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arthur Naseef updated AMQ-3167:
-------------------------------
Attachment: AMQ3167Test.java
Test use case which reproduces the problem consistently by using a small memory limit and short time delay between production and consumption.
A license header as been included; feel free to replace it as-needed.
> possible skipped Queue messages in memory limited configuration with fast consumers
> -----------------------------------------------------------------------------------
>
> Key: AMQ-3167
> URL: https://issues.apache.org/jira/browse/AMQ-3167
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.2
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.5.0
>
> Attachments: AMQ3167Test.java
>
>
> regression in test from https://issues.apache.org/jira/browse/AMQ-2413 required some investigation. Symptom was missing messages, turned out to be in the middle of the sequence. Issue with the priority kahadb cursors and setbatch. Set batch is invoked when the cursor memory is exhausted such that replay from the store can start at the correct point. If a call to setBatch was followed by a call to recover when there was still no memory space available, the cursor could skip the next pending message.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-3167) possible skipped Queue messages in
memory limited configuration with fast consumers
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993510#comment-12993510 ]
Gary Tully commented on AMQ-3167:
---------------------------------
committed your test case so we can protect your use case it into the future. thanks.
> possible skipped Queue messages in memory limited configuration with fast consumers
> -----------------------------------------------------------------------------------
>
> Key: AMQ-3167
> URL: https://issues.apache.org/jira/browse/AMQ-3167
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.2
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.5.0
>
> Attachments: AMQ3167Test.java, patch.amq3167.activemq-5.4.2
>
>
> regression in test from https://issues.apache.org/jira/browse/AMQ-2413 required some investigation. Symptom was missing messages, turned out to be in the middle of the sequence. Issue with the priority kahadb cursors and setbatch. Set batch is invoked when the cursor memory is exhausted such that replay from the store can start at the correct point. If a call to setBatch was followed by a call to recover when there was still no memory space available, the cursor could skip the next pending message.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira