You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2012/08/23 18:40:42 UTC
[jira] [Assigned] (QPID-4053) Performance Test Framework:
QueueDelete can timeout if test ends when too many unprocessed messages
remain on test queue
[ https://issues.apache.org/jira/browse/QPID-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy reassigned QPID-4053:
--------------------------------
Assignee: Alex Rudyy (was: Philip Harvey)
> Performance Test Framework: QueueDelete can timeout if test ends when too many unprocessed messages remain on test queue
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-4053
> URL: https://issues.apache.org/jira/browse/QPID-4053
> Project: Qpid
> Issue Type: Bug
> Components: Java Performance Tests
> Affects Versions: 0.17
> Reporter: Keith Wall
> Assignee: Alex Rudyy
> Attachments: 0001-QPID-4053-Change-performance-test-qpid-queue-creator.patch
>
>
> There is a problem in the new Performance Test Framework. If a test utilising the maxiumumDuration feature completes with too many messages left on a queue (as would be the case where number of producers out-number consumers), the QueueDelete command issued by the framework can apparently fail owing to a timeout exception. The command does in fact complete successfully server side, it is just the client gives up awaiting the response. This can cause a spurious test failure.
> I see this with VaryingNumberOfParticipants.json when maximumDuration is set to 100seconds.
> {code}
> org.apache.qpid.AMQTimeoutException: Server did not respond in a timely fashion [error code 408: Request Timeout]
> at org.apache.qpid.client.util.BlockingWaiter.block(BlockingWaiter.java:177)
> at org.apache.qpid.client.protocol.BlockingMethodFrameListener.blockForFrame(BlockingMethodFrameListener.java:122)
> at org.apache.qpid.client.protocol.AMQProtocolHandler.writeCommandFrameAndWaitForReply(AMQProtocolHandler.java:656)
> at org.apache.qpid.client.protocol.AMQProtocolHandler.syncWrite(AMQProtocolHandler.java:677)
> at org.apache.qpid.client.protocol.AMQProtocolHandler.syncWrite(AMQProtocolHandler.java:671)
> at org.apache.qpid.client.AMQSession_0_8.sendQueueDelete(AMQSession_0_8.java:429)
> at org.apache.qpid.disttest.jms.QpidQueueCreator.deleteQueue(QpidQueueCreator.java:88)
> at org.apache.qpid.disttest.jms.QpidQueueCreator.deleteQueues(QpidQueueCreator.java:55)
> at org.apache.qpid.disttest.jms.ControllerJmsDelegate.deleteQueues(ControllerJmsDelegate.java:198)
> at org.apache.qpid.disttest.controller.TestRunner.deleteQueues(TestRunner.java:232)
> at org.apache.qpid.disttest.controller.TestRunner.runParts(TestRunner.java:139)
> at org.apache.qpid.disttest.controller.TestRunner.run(TestRunner.java:103)
> at org.apache.qpid.disttest.controller.Controller.runAllTests(Controller.java:172)
> at org.apache.qpid.disttest.ControllerRunner.runTest(ControllerRunner.java:120)
> at org.apache.qpid.disttest.ControllerRunner.runTests(ControllerRunner.java:105)
> at org.apache.qpid.disttest.ControllerRunner.runController(ControllerRunner.java:80)
> at org.apache.qpid.disttest.ControllerRunner.main(ControllerRunner.java:69)
> {code}
--
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