[
https://issues.apache.org/jira/browse/QPIDJMS-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462727#comment-17462727
]
ASF subversion and git services commented on QPIDJMS-557:
---------------------------------------------------------
Commit 94c3b59299708b4a3997f0781d57306f0c55c0eb in qpid-jms's branch
refs/heads/0.x from Robbie Gemmell
[ https://gitbox.apache.org/repos/asf?p=qpid-jms.git;h=94c3b59 ]
QPIDJMS-557: gate log message on whether closure was already requested
(cherry picked from commit 1fc1fdba0d56860cb2958f672954411902b8165b)
> ocassional connection failure log despite successfull requested connection
> closure
> ----------------------------------------------------------------------------------
>
> Key: QPIDJMS-557
> URL: https://issues.apache.org/jira/browse/QPIDJMS-557
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.59.0, 1.0.0, 1.1.0, 1.2.0, 1.3.0, 0.60.1, 1.4.1
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Trivial
> Fix For: 1.5.0, 0.61.0
>
>
> QPIDJMS-528 added some additional logging around connection interruption and
> failure. It has recently been seen to occasionally log connection failure
> even in cases where the connection was successfully closed as requested.
> This looks to be from a race between notification of the remote side closing
> the socket and the client cleaning the provider/transport locally following a
> Close frame. This has likely always been the case and doesnt cause any other
> issue besides the spurious log message, so the simplest and least intrusive
> approach is just to ensure the new logging is gated when closure has been
> specifically requested.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
