[
https://issues.apache.org/jira/browse/QPID-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8185:
-----------------------------
Attachment: 0001-JMS-AMQP-0-x-AMQP-0-8.0-91-Make-sure-that-client-clo.patch
> [JMS AMQP 0-x][AMQP 0-8..0-91] Make sure that client closes TCP connection on
> failure with sending connection.close
> -------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-8185
> URL: https://issues.apache.org/jira/browse/QPID-8185
> Project: Qpid
> Issue Type: Improvement
> Components: JMS AMQP 0-x
> Affects Versions: qpid-java-6.1.6, 0.18, 0.20, 0.22, 0.24, 0.26, 0.28,
> 0.30, 0.32, qpid-java-6.0.8, qpid-java-client-0-x-6.3.0
> Reporter: Alex Rudyy
> Priority: Major
> Fix For: qpid-java-client-0-x-6.3.1
>
> Attachments:
> 0001-JMS-AMQP-0-x-AMQP-0-8.0-91-Make-sure-that-client-clo.patch
>
>
> Sending connection.close as part of {{Connection#close}} can end-up in
> timeout exception. The underlying TCP connection remains open and Broker can
> continue sending data to the client when session close ends up in timeout as
> well. The incoming frames cannot be associated with the sessions, as the
> client removes session information on connection close. As result, a number
> of confusing exceptions is reported
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
