You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Philip Harvey (JIRA)" <ji...@apache.org> on 2012/05/22 15:45:41 UTC
[jira] [Created] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Philip Harvey created QPID-4014:
-----------------------------------
Summary: 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
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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Harvey updated QPID-4014:
--------------------------------
Attachment: TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out.gz
attached the output of the failing test
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Assigned] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Harvey reassigned QPID-4014:
-----------------------------------
Assignee: Philip Harvey (was: Keith Wall)
> 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: TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out.2nd-occurence.gz, 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281037#comment-13281037 ]
Philip Harvey commented on QPID-4014:
-------------------------------------
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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Comment Edited] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Harvey updated QPID-4014:
--------------------------------
Attachment: 0001-QPID-4014-increase-debug-logging-in-ConflationQueueL.patch
attached proposed patch to increase debug logging in ConflationQueueList to aid diagnosis of the occasional test failure.
> 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.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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-4014:
-----------------------------
Attachment: TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out.build419.bz2
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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Comment Edited] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ 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 4:15 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)
38015 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, 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}
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424543#comment-13424543 ]
Keith Wall commented on QPID-4014:
----------------------------------
I think I understand the underlying cause, see QPID-4171.
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Robbie Gemmell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292561#comment-13292561 ]
Robbie Gemmell commented on QPID-4014:
--------------------------------------
Patch applied.
> 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.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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Harvey updated QPID-4014:
--------------------------------
Description:
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.
was:
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.
> 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: TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out.2nd-occurence.gz, 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Comment Edited] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ 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 4:16 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, message store id 777)
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)
38015 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, message store id 801)
10927 sender1 sends SHUTDOWN-1 (same timstamp id cd4ff12b-5591-3e3d-ae67-4ff0a27bfe78, message store id 802)
38015 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Harvey updated QPID-4014:
--------------------------------
Attachment: TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out.build291.gz
attached log file from test that failed in [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/org.apache.qpid.server.queue/ConflationQueueTest/testParallelProductionAndConsumption/]
> 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: 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.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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Closed] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall closed QPID-4014.
----------------------------
Resolution: Fixed
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Updated] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Philip Harvey updated QPID-4014:
--------------------------------
Attachment: TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out.2nd-occurence.gz
test output from the second occurrence of this test failure.
> 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.2nd-occurence.gz, 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281584#comment-13281584 ]
Philip Harvey commented on QPID-4014:
-------------------------------------
I've just seen this problem occur again. I repeatedly ran the test on my PC and eventually saw it fail on the 406th attempt.
I've attached the test output as TODO.
To filter the test output to only show the relevant messages (i.e. message 399 and the SHUTDOWN messages), use this Linux command:
{noformat}
egrep -n -a2 '(msg=399|SHUTDOWN)' TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out
{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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Comment Edited] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281584#comment-13281584 ]
Philip Harvey edited comment on QPID-4014 at 5/23/12 1:15 PM:
--------------------------------------------------------------
I've just seen this problem occur again. I repeatedly ran the test on my PC and eventually saw it fail on the 406th attempt.
I've attached the test output as TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out.2nd-occurence.gz.
To filter the test output to only show the relevant messages (i.e. message 399 and the SHUTDOWN messages), use this Linux command:
{noformat}
egrep -n -a2 '(msg=399|SHUTDOWN)' TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out
{noformat}
was (Author: philharveyonline):
I've just seen this problem occur again. I repeatedly ran the test on my PC and eventually saw it fail on the 406th attempt.
I've attached the test output as TODO.
To filter the test output to only show the relevant messages (i.e. message 399 and the SHUTDOWN messages), use this Linux command:
{noformat}
egrep -n -a2 '(msg=399|SHUTDOWN)' TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out
{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.2nd-occurence.gz, 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Commented] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Keith Wall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426617#comment-13426617 ]
Keith Wall commented on QPID-4014:
----------------------------------
Fixed by QPID-4171.
> 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Comment Edited] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280957#comment-13280957 ]
Philip Harvey edited comment on QPID-4014 at 6/7/12 6:56 PM:
-------------------------------------------------------------
attached the output of the failing test (build 206)
was (Author: philharveyonline):
attached the output of the failing test
> 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: TEST-org.apache.qpid.server.queue.ConflationQueueTest.testParallelProductionAndConsumption.out.2nd-occurence.gz, 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
[jira] [Comment Edited] (QPID-4014) System test
ConflationQueueTest.testParallelProductionAndConsumption failed
Posted by "Philip Harvey (JIRA)" <ji...@apache.org>.
[ 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org