You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2015/03/18 16:41:38 UTC
[jira] [Updated] (QPID-6458) Clients sends channel flow or message
stop even if channel is already closed
[ https://issues.apache.org/jira/browse/QPID-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-6458:
-----------------------------
Description:
The Qpid Client has a seemingly longstanding defect that allows it to send frames such as channel.flow (0-8..0-91) or message.flow/stop (0-10) even after the application has closed the JMS Session.
This has been highlighted by test ExceptionListenerTest that has begun to sporadically fail. Investigation showed that the client continues to send commands for the channel following its sending of channel.close. This was causing the Broker to close the connection thus causing the test to fail.
{noformat}
2015-03-18 11:02:20,203 DEBUG [main] (qpid.protocol) - SEND: [org.apache.qpid.client.protocol.AMQProtocolHandler@66ef393c] Frame channelId: 3, bodyFrame: [ChannelCloseBodyImpl: replyCode=200, replyText=JMS client closing channel, classId=0, methodId=0]
2015-03-18 11:02:20,203 DEBUG [pool-610-thread-1] (client.AMQSession) - Setting channel flow : suspended
2015-03-18 11:02:20,203 DEBUG [pool-610-thread-1] (qpid.protocol) - SEND: [org.apache.qpid.client.protocol.AMQProtocolHandler@66ef393c] Frame channelId: 3, bodyFrame: [ChannelFlowBodyImpl: active=false]
{noformat}
This was potentially exposed by QPID-6374.
was:
The Qpid Client has a seemingly longstanding defect that allows it to send frames such as channel.flow (0-8..0-91) or message.flow/stop even after the application has closed the JMS Session.
This has been highlighted by test ExceptionListenerTest that has begun to sporadically fail. Investigation showed that the client continues to send commands for the channel following its sending of channel.close. This was causing the Broker to close the connection thus causing the test to fail.
{noformat}
2015-03-18 11:02:20,203 DEBUG [main] (qpid.protocol) - SEND: [org.apache.qpid.client.protocol.AMQProtocolHandler@66ef393c] Frame channelId: 3, bodyFrame: [ChannelCloseBodyImpl: replyCode=200, replyText=JMS client closing channel, classId=0, methodId=0]
2015-03-18 11:02:20,203 DEBUG [pool-610-thread-1] (client.AMQSession) - Setting channel flow : suspended
2015-03-18 11:02:20,203 DEBUG [pool-610-thread-1] (qpid.protocol) - SEND: [org.apache.qpid.client.protocol.AMQProtocolHandler@66ef393c] Frame channelId: 3, bodyFrame: [ChannelFlowBodyImpl: active=false]
{noformat}
This was potentially exposed by QPID-6374.
> Clients sends channel flow or message stop even if channel is already closed
> ----------------------------------------------------------------------------
>
> Key: QPID-6458
> URL: https://issues.apache.org/jira/browse/QPID-6458
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.32
> Reporter: Keith Wall
> Fix For: 6.0 [Java]
>
>
> The Qpid Client has a seemingly longstanding defect that allows it to send frames such as channel.flow (0-8..0-91) or message.flow/stop (0-10) even after the application has closed the JMS Session.
> This has been highlighted by test ExceptionListenerTest that has begun to sporadically fail. Investigation showed that the client continues to send commands for the channel following its sending of channel.close. This was causing the Broker to close the connection thus causing the test to fail.
> {noformat}
> 2015-03-18 11:02:20,203 DEBUG [main] (qpid.protocol) - SEND: [org.apache.qpid.client.protocol.AMQProtocolHandler@66ef393c] Frame channelId: 3, bodyFrame: [ChannelCloseBodyImpl: replyCode=200, replyText=JMS client closing channel, classId=0, methodId=0]
> 2015-03-18 11:02:20,203 DEBUG [pool-610-thread-1] (client.AMQSession) - Setting channel flow : suspended
> 2015-03-18 11:02:20,203 DEBUG [pool-610-thread-1] (qpid.protocol) - SEND: [org.apache.qpid.client.protocol.AMQProtocolHandler@66ef393c] Frame channelId: 3, bodyFrame: [ChannelFlowBodyImpl: active=false]
> {noformat}
> This was potentially exposed by QPID-6374.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org