You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2010/01/28 11:35:34 UTC
[jira] Created: (QPID-2369) TTR-Qpid-03-TX logs 'Got unexpected
message with correlationId: xx'
TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx'
-------------------------------------------------------------------
Key: QPID-2369
URL: https://issues.apache.org/jira/browse/QPID-2369
Project: Qpid
Issue Type: Bug
Components: Java Performance Tests, Java Tests
Affects Versions: 0.5, 0.6
Reporter: Martin Ritchie
Priority: Minor
When running through the perftest package of tests (Using perftests/bin/RunCore.sh) there was a warning logged:
Dispatcher-Channel-1 2010-01-25 14:42:54,218 WARN [apache.qpid.requestreply.PingPongProducer] Got unexpected message with correlationId: 52
This came from the TTR-Qpid-03-TX test.
The cause of this failure is that messages from a previous test cycle have been left behind and are unknown to the current cycle.
This is logged as a warning and does not constitute a failure of the test. IIRC this check was added to ensure that data not generated by this test did not interfere with the current test run.
However, this warning is not normally seen and has only started occuring consistently recently. Investigation into the exact cause and why it is only this test that shows the warnings would be helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2369) TTR-Qpid-03-TX logs 'Got unexpected
message with correlationId: xx'
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-2369:
---------------------------------
Attachment: QPID-2369-Restore-5k-prefetch.out
Add patch that ensures the perftests all run with a 5000 prefetch. Should we be doing this for all tests? Only TTR-Qpid3-Tx has failed as a result of the new lower, 500, prefetch. Should we have some way of setting System properties or additional values in the scripts.xml file?
> TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx'
> -------------------------------------------------------------------
>
> Key: QPID-2369
> URL: https://issues.apache.org/jira/browse/QPID-2369
> Project: Qpid
> Issue Type: Bug
> Components: Java Performance Tests, Java Tests
> Affects Versions: 0.5, 0.6
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Priority: Minor
> Attachments: QPID-2369-Restore-5k-prefetch.out
>
>
> When running through the perftest package of tests (Using perftests/bin/RunCore.sh) there was a warning logged:
> Dispatcher-Channel-1 2010-01-25 14:42:54,218 WARN [apache.qpid.requestreply.PingPongProducer] Got unexpected message with correlationId: 52
> This came from the TTR-Qpid-03-TX test.
> The cause of this failure is that messages from a previous test cycle have been left behind and are unknown to the current cycle.
> This is logged as a warning and does not constitute a failure of the test. IIRC this check was added to ensure that data not generated by this test did not interfere with the current test run.
> However, this warning is not normally seen and has only started occuring consistently recently. Investigation into the exact cause and why it is only this test that shows the warnings would be helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Resolved: (QPID-2369) TTR-Qpid-03-TX logs 'Got unexpected
message with correlationId: xx'
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie resolved QPID-2369.
----------------------------------
Resolution: Fixed
Setting the max_prefetch to 5000 resolved the issue.
Created a new JIRA to hold the patch to expose the queue purge change: QPID-2390.
> TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx'
> -------------------------------------------------------------------
>
> Key: QPID-2369
> URL: https://issues.apache.org/jira/browse/QPID-2369
> Project: Qpid
> Issue Type: Bug
> Components: Java Performance Tests, Java Tests
> Affects Versions: 0.5, 0.6
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Priority: Minor
> Attachments: QPID-2369-clear-queue.diff, QPID-2369-Restore-5k-prefetch.out
>
>
> When running through the perftest package of tests (Using perftests/bin/RunCore.sh) there was a warning logged:
> Dispatcher-Channel-1 2010-01-25 14:42:54,218 WARN [apache.qpid.requestreply.PingPongProducer] Got unexpected message with correlationId: 52
> This came from the TTR-Qpid-03-TX test.
> The cause of this failure is that messages from a previous test cycle have been left behind and are unknown to the current cycle.
> This is logged as a warning and does not constitute a failure of the test. IIRC this check was added to ensure that data not generated by this test did not interfere with the current test run.
> However, this warning is not normally seen and has only started occuring consistently recently. Investigation into the exact cause and why it is only this test that shows the warnings would be helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-2369) TTR-Qpid-03-TX logs 'Got unexpected
message with correlationId: xx'
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806312#action_12806312 ]
Martin Ritchie commented on QPID-2369:
--------------------------------------
The recent change to use 500 as the max_prefetch default has caused the consume rate to drop sufficiently for this test to fail.
Setting max_prefetch back to 5000 resolves this issue.
> TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx'
> -------------------------------------------------------------------
>
> Key: QPID-2369
> URL: https://issues.apache.org/jira/browse/QPID-2369
> Project: Qpid
> Issue Type: Bug
> Components: Java Performance Tests, Java Tests
> Affects Versions: 0.5, 0.6
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Priority: Minor
>
> When running through the perftest package of tests (Using perftests/bin/RunCore.sh) there was a warning logged:
> Dispatcher-Channel-1 2010-01-25 14:42:54,218 WARN [apache.qpid.requestreply.PingPongProducer] Got unexpected message with correlationId: 52
> This came from the TTR-Qpid-03-TX test.
> The cause of this failure is that messages from a previous test cycle have been left behind and are unknown to the current cycle.
> This is logged as a warning and does not constitute a failure of the test. IIRC this check was added to ensure that data not generated by this test did not interfere with the current test run.
> However, this warning is not normally seen and has only started occuring consistently recently. Investigation into the exact cause and why it is only this test that shows the warnings would be helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2369) TTR-Qpid-03-TX logs 'Got unexpected
message with correlationId: xx'
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-2369:
---------------------------------
Attachment: QPID-2369-clear-queue.diff
Patch to clear queues at the end of a perftest run. Only clears queues not autodelete queues. Exposes QueuePurge so needs additional test to validate QueuePurge functionality on all protocol versions.
> TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx'
> -------------------------------------------------------------------
>
> Key: QPID-2369
> URL: https://issues.apache.org/jira/browse/QPID-2369
> Project: Qpid
> Issue Type: Bug
> Components: Java Performance Tests, Java Tests
> Affects Versions: 0.5, 0.6
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Priority: Minor
> Attachments: QPID-2369-clear-queue.diff, QPID-2369-Restore-5k-prefetch.out
>
>
> When running through the perftest package of tests (Using perftests/bin/RunCore.sh) there was a warning logged:
> Dispatcher-Channel-1 2010-01-25 14:42:54,218 WARN [apache.qpid.requestreply.PingPongProducer] Got unexpected message with correlationId: 52
> This came from the TTR-Qpid-03-TX test.
> The cause of this failure is that messages from a previous test cycle have been left behind and are unknown to the current cycle.
> This is logged as a warning and does not constitute a failure of the test. IIRC this check was added to ensure that data not generated by this test did not interfere with the current test run.
> However, this warning is not normally seen and has only started occuring consistently recently. Investigation into the exact cause and why it is only this test that shows the warnings would be helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Reopened: (QPID-2369) TTR-Qpid-03-TX logs 'Got unexpected
message with correlationId: xx'
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reopened QPID-2369:
----------------------------------
Assignee: (was: Martin Ritchie)
The scripts.xml needs to be updated to specify the prefetch on the tests that require a higher value or this error will occur on all subsequent builds.
> TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx'
> -------------------------------------------------------------------
>
> Key: QPID-2369
> URL: https://issues.apache.org/jira/browse/QPID-2369
> Project: Qpid
> Issue Type: Bug
> Components: Java Performance Tests, Java Tests
> Affects Versions: 0.5, 0.6
> Reporter: Martin Ritchie
> Priority: Minor
> Attachments: QPID-2369-clear-queue.diff, QPID-2369-Restore-5k-prefetch.out
>
>
> When running through the perftest package of tests (Using perftests/bin/RunCore.sh) there was a warning logged:
> Dispatcher-Channel-1 2010-01-25 14:42:54,218 WARN [apache.qpid.requestreply.PingPongProducer] Got unexpected message with correlationId: 52
> This came from the TTR-Qpid-03-TX test.
> The cause of this failure is that messages from a previous test cycle have been left behind and are unknown to the current cycle.
> This is logged as a warning and does not constitute a failure of the test. IIRC this check was added to ensure that data not generated by this test did not interfere with the current test run.
> However, this warning is not normally seen and has only started occuring consistently recently. Investigation into the exact cause and why it is only this test that shows the warnings would be helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-2369) TTR-Qpid-03-TX logs 'Got unexpected
message with correlationId: xx'
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-2369:
------------------------------------
Assignee: Martin Ritchie
> TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx'
> -------------------------------------------------------------------
>
> Key: QPID-2369
> URL: https://issues.apache.org/jira/browse/QPID-2369
> Project: Qpid
> Issue Type: Bug
> Components: Java Performance Tests, Java Tests
> Affects Versions: 0.5, 0.6
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Priority: Minor
>
> When running through the perftest package of tests (Using perftests/bin/RunCore.sh) there was a warning logged:
> Dispatcher-Channel-1 2010-01-25 14:42:54,218 WARN [apache.qpid.requestreply.PingPongProducer] Got unexpected message with correlationId: 52
> This came from the TTR-Qpid-03-TX test.
> The cause of this failure is that messages from a previous test cycle have been left behind and are unknown to the current cycle.
> This is logged as a warning and does not constitute a failure of the test. IIRC this check was added to ensure that data not generated by this test did not interfere with the current test run.
> However, this warning is not normally seen and has only started occuring consistently recently. Investigation into the exact cause and why it is only this test that shows the warnings would be helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2369) TTR-Qpid-03-TX logs 'Got unexpected
message with correlationId: xx'
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-2369:
---------------------------------
Status: Ready To Review (was: In Progress)
> TTR-Qpid-03-TX logs 'Got unexpected message with correlationId: xx'
> -------------------------------------------------------------------
>
> Key: QPID-2369
> URL: https://issues.apache.org/jira/browse/QPID-2369
> Project: Qpid
> Issue Type: Bug
> Components: Java Performance Tests, Java Tests
> Affects Versions: 0.5, 0.6
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Priority: Minor
> Attachments: QPID-2369-clear-queue.diff, QPID-2369-Restore-5k-prefetch.out
>
>
> When running through the perftest package of tests (Using perftests/bin/RunCore.sh) there was a warning logged:
> Dispatcher-Channel-1 2010-01-25 14:42:54,218 WARN [apache.qpid.requestreply.PingPongProducer] Got unexpected message with correlationId: 52
> This came from the TTR-Qpid-03-TX test.
> The cause of this failure is that messages from a previous test cycle have been left behind and are unknown to the current cycle.
> This is logged as a warning and does not constitute a failure of the test. IIRC this check was added to ensure that data not generated by this test did not interfere with the current test run.
> However, this warning is not normally seen and has only started occuring consistently recently. Investigation into the exact cause and why it is only this test that shows the warnings would be helpful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org