-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the ssl connection can not be closed when the status is NEED_UNWRAP #11256
Comments
Yes, the connection will eventually idle timeout and be closed. |
The connection will in ESTABLISHED for 10 minutes, then it will get closed. |
Actually, the connection is not closed |
We need hard evidence that this is not the case. The server will idle timeout and will try to send the client a TLS close alert and a TCP FIN. If the client does not answer the TCP FIN, after another idle timeout the server will close the connection. If you have hard evidence that this is not the case, please report the server's DEBUG logs. |
But only from a supported version of Jetty. |
The DEBUG logs:
|
Please collect the ENTIRE DEBUG logs from a supported version of Jetty, do not remove lines, but feel free to change/edit out sensitive data in a line, or remove lines not from |
This class does not exist in Jetty 12 (the only community supported version of Jetty right now) - that class was reworked and moved to a new location. Upgrade and try again with a supported version of Jetty, if the problem persists collect the ENTIRE DEBUG LOGS and report back. |
I am closing this issue due to it being on an unsupported version of Jetty. When you have upgraded, and if you are still having the issue, either comment here and we will reopen this issue, or open a new issue. |
@luffy1949 I opened #11259 to fix this issue, which I think affects later versions as well. |
Jetty version(s)
Jetty 9.4.48.v20220622
Jetty Environment
Java version/vendor
(use: java -version)
JDK8
OS type/version
suse 12.5
Description
4.252.83.81 is client
11.19.120.119 is server
when the server send the "server hello" ,we hope the client replay a "key exchange" package ,but the client just replayed an ACK ,so The SSL connection on the server is suspended.
we looked at the dump file ,all pending connections are in the "NEED_UNWRAP" state.
we want to know if jetty has a protection mechanism for this scenario
How to reproduce?
The text was updated successfully, but these errors were encountered: