[
https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424318#comment-13424318
]
Keith Wall edited comment on QPID-4014 at 7/28/12 10:55 AM:
------------------------------------------------------------
Another instance of this test failure from build 419. Hopefully Phil's extra
logging will help us understand the underlying cause. Log file attached to
JIRA.
Error Message
The last message sent for each key should match the last message received for
that key expected:<{1=399, 0=398}> but was:<{1=397, 0=398}>
Stacktrace
{noformat}
junit.framework.AssertionFailedError: The last message sent for each key should
match the last message received for that key expected:<{1=399, 0=398}> but
was:<{1=397, 0=398}>
at
org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption(ConflationQueueTest.java:414)
at
org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:244)
at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
{noformat}
was (Author: k-wall):
Another instance of this test failure from build 419. Hopefully Phil's
extra logging will help us understand the underlying cause:
Error Message
The last message sent for each key should match the last message received for
that key expected:<{1=399, 0=398}> but was:<{1=397, 0=398}>
Stacktrace
junit.framework.AssertionFailedError: The last message sent for each key should
match the last message received for that key expected:<{1=399, 0=398}> but
was:<{1=397, 0=398}>
at
org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption(ConflationQueueTest.java:414)
at
org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:244)
at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:137)
> System test ConflationQueueTest.testParallelProductionAndConsumption failed
> ---------------------------------------------------------------------------
>
> Key: QPID-4014
> URL: https://issues.apache.org/jira/browse/QPID-4014
> Project: Qpid
> Issue Type: Bug
> Components: Java Tests
> Reporter: Philip Harvey
> Assignee: Philip Harvey
> Priority: Minor
> Fix For: 0.17
>
> Attachments:
> 0001-QPID-4014-increase-debug-logging-in-ConflationQueueL.patch,
> TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out.2nd-occurence.gz,
>
> TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out.build291.gz,
>
> TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out.build419.bz2,
>
> TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out.gz
>
>
> Unit test ConflationQueueTest.testParallelProductionAndConsumption has failed
> on Jenkins at least twice:
> * [Build
> 206|https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-BDB-TestMatrix/jdk=JDK%201.6%20(latest),label=Ubuntu,profile=java-bdb.0-9-1/206/testReport/org.apache.qpid.server.queue/ConflationQueueTest/testParallelProductionAndConsumption/]
> * [Build
> 291|https://builds.apache.org/job/Qpid-Java-Java-BDB-TestMatrix/291/jdk=JDK%201.6%20(latest),label=Ubuntu,profile=java-bdb.0-9-1/testReport/junit/org.apache.qpid.server.queue/ConflationQueueTest/testParallelProductionAndConsumption/]
> This test has previously run successfully.
> On first glance, the test doesn't appear to have any inherent race
> conditions, therefore it is possible that this represents a genuine problem.
> In this test, two producers each each 400 messages with alternating
> conflation key values, followed by special "shutdown" messages. A single
> consumer remembers the latest message for each conflation key value.
> Each producer's last few messages should be:
> * Message 397 (conflation key '1')
> * Message 398 (conflation key '0')
> * Message 399 (conflation key '1')
> * Shutdown message
> The assertion in question checks the last message received for each
> conflation key value. In this case, the last message with key '1' is message
> 397, not the expected message 399.
> Examination of the test output (attached) indicates that the consumer
> received message 399 once (it must have been conflated), and that -
> surprisingly - it arrived *after* the two shutdown messages.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
