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/05/25 11:39:24 UTC
[jira] [Updated] (QPID-4018) AMQP 0-10: AMQSession.getQueueDepth()
timed out because of "Received a response to a command that's no longer
valid"
[ https://issues.apache.org/jira/browse/QPID-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-4018:
-----------------------------
Description:
When testing the disk quota functionality added in QPID-3986, our test program failed because AMQSession.getQueueDepth() timed out.
This problem occured after the test program had been running successfully for about 45 minutes. We have run the same test for many hours using protocol 0-9 without seeing this problem.
Our client log contained this warning:
{noformat}
"Received a response to a command that's no longer valid on the client side . [ command id : 429958, result : QueueQueryDepthResult ..."
{noformat}
... which is presumably the reason for getQueueDepth() timing out.
The broker log suggests that the queue query command was received, and a response promptly returned to the client.
was:
When testing the disk quota functionality added in QPID-3986, our test program failed because AMQSession.getQueueDepth() timed out.
Our client log contained this warning:
{noformat}
"Received a response to a command that's no longer valid on the client side . [ command id : 429958, result : QueueQueryDepthResult ..."
{noformat}
... which is presumably the reason for getQueueDepth() timing out.
> AMQP 0-10: AMQSession.getQueueDepth() timed out because of "Received a response to a command that's no longer valid"
> --------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-4018
> URL: https://issues.apache.org/jira/browse/QPID-4018
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.16
> Reporter: Alex Rudyy
> Priority: Minor
> Fix For: 0.17
>
>
> When testing the disk quota functionality added in QPID-3986, our test program failed because AMQSession.getQueueDepth() timed out.
> This problem occured after the test program had been running successfully for about 45 minutes. We have run the same test for many hours using protocol 0-9 without seeing this problem.
> Our client log contained this warning:
> {noformat}
> "Received a response to a command that's no longer valid on the client side . [ command id : 429958, result : QueueQueryDepthResult ..."
> {noformat}
> ... which is presumably the reason for getQueueDepth() timing out.
> The broker log suggests that the queue query command was received, and a response promptly returned to the client.
--
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