[
https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281037#comment-13281037
]
Philip Harvey edited comment on QPID-4014 at 5/22/12 3:51 PM:
--------------------------------------------------------------
Here is a summary of the events in the attached log file
{noformat}
line event
--------------------------------------------------------
10474 sender2 sends 399-2 (timestamp 1337682147990, id
dc2aaab4-9cd7-3d56-8e27-a1687458d2ed)
10504 sender2 sends SHUTDOWN-2 (timestamp 1337682147990, id
be63fcc4-6266-3189-b72b-ddff7bebb071)
10906 sender1 sends 399-1 (timestamp 1337682147999, id
86d7a88c-160c-3e09-b297-43ee7e3aca3b, message store id 801)
10927 sender1 sends SHUTDOWN-1 (same timstamp id
cd4ff12b-5591-3e3d-ae67-4ff0a27bfe78, message store id 802)
30815 broker receives 399-2
38040 broker receives SHUTDOWN-2
38249 broker sends SHUTDOWN-2
38269 client receives SHUTDOWN-2
39349 broker receives 399-1
39398 broker receives SHUTDOWN-1
39529 broker sends SHUTDOWN-1 from thread "pool-3-thread-1141" *oops we haven't
sent 399-1 yet*
39541 client receives SHUTDOWN-1
39582 broker sends 399-1 from thread "pool-3-thread-1139"
tearDown
39601 client receives 399-1 *oops*
{noformat}
was (Author: philharveyonline):
Here is a summary of the events in the attached log file
{noformat}
line event
--------------------------------------------------------
10474 sender2 sends 399-2 (timestamp 1337682147990, id
dc2aaab4-9cd7-3d56-8e27-a1687458d2ed)
10504 sender2 sends SHUTDOWN-2 (timestamp 1337682147990, id
be63fcc4-6266-3189-b72b-ddff7bebb071)
10906 sender1 sends 399-1 (timestamp 1337682147999, id
86d7a88c-160c-3e09-b297-43ee7e3aca3b)
10927 sender1 sends SHUTDOWN-1 (same timstamp id
cd4ff12b-5591-3e3d-ae67-4ff0a27bfe78)
30815 broker receives 399-2
38040 broker receives SHUTDOWN-2
38249 broker sends SHUTDOWN-2
38269 client receives SHUTDOWN-2
39349 broker receives 399-1
39398 broker receives SHUTDOWN-1
39529 broker sends SHUTDOWN-1 from thread "pool-3-thread-1141" *oops we haven't
sent 399-1 yet*
39541 client receives SHUTDOWN-1
39582 broker sends 399-1 from thread "pool-3-thread-1139"
tearDown
39601 client receives 399-1 *oops*
{noformat}
> 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: Keith Wall
> Priority: Minor
> Fix For: 0.17
>
> Attachments:
> TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out.gz
>
>
> Unit test ConflationQueueTest.testParallelProductionAndConsumption has failed
> on Jenkins:
> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-BDB-TestMatrix/jdk=JDK%201.6%20%28latest%29,label=Ubuntu,profile=java-bdb.0-10/lastCompletedBuild/testReport/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
