[
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:[email protected]
