[
https://issues.apache.org/jira/browse/QPID-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470194#comment-13470194
]
Robbie Gemmell commented on QPID-4359:
--------------------------------------
This seems to be because whilst the client is using an SSLEngine for SSL over a
Socket the broker is using an SSLSocket produced by its SSLServerSocket and its
behaviour for a final read attempt when also closing down the connection is
different, such that the IOReceivers final attempt to read the socket causes
the SocketException to occur which it then reports. As a workaround, a check
will be added to suppress this particular SocketException in the case we have
just closed the IoReceiver.
> [Java Broker] an IOException is logged when closing a connection which is SSL
> -----------------------------------------------------------------------------
>
> Key: QPID-4359
> URL: https://issues.apache.org/jira/browse/QPID-4359
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Robbie Gemmell
> Fix For: 0.19
>
>
> When closing a connection which is using SSL, an IOException is logged by the
> broker.
> E.g "ERROR \[qpid.server.protocol.AMQProtocolEngine\] IOException caught
> inlocalhost.localdomain/127.0.0.1:60015(guest), session closed implictly:
> java.net.SocketException: Socket is closed"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
