https://bz.apache.org/bugzilla/show_bug.cgi?id=60555
--- Comment #3 from hiki <dracu...@hotmail.com> ---
(In reply to Mark Thomas from comment #1)
>
> *** This bug has been marked as a duplicate of bug 60035 ***
Thanks ,the problem is solved,
but I don't think the relationship with r1746551 is direct
I think the main solution to this problem is the following code
org.apache.tomcat.util.net.NioEndpoint
if (socket.isHandshakeComplete()) {
// No TLS handshaking required. Let the handler
// process this socket / event combination.
handshake = 0;
} else if (event == SocketEvent.STOP || event ==
SocketEvent.DISCONNECT ||
event == SocketEvent.ERROR) {
// Unable to complete the TLS handshake. Treat it
as
// if the handshake failed.
handshake = -1;
} else {
handshake = socket.handshake(key.isReadable(),
key.isWritable());
// The handshake process reads/writes from/to the
// socket. status may therefore be OPEN_WRITE once
// the handshake completes. However, the handshake
// happens when the socket is opened so the status
// must always be OPEN_READ after it completes. It
// is OK to always set this as it is only used if
// the handshake completes.
event = SocketEvent.OPEN_READ;
}
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
