You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered this issue also. It stalled on kexinit and timed out. This only happened in Docker (but not even all Docker runtimes, because it worked on Docker on macOS but not on Linux).
If this occurs only in some dockerized runs it stands to reason that the OS inside the docker container as well as the Java version inside the container might have an influence.
@rgarciapariente , @proprietary : What OS is running inside your docker containers, and what Java version is being used?
The interesting thing in the failing logs is that between encoding the KEX_INIT message and actually sending it a lot of time passes. If we take just one session, we have in the failing server log
2024-12-09T10:49:00.0263107Z 09 Dec 2024 10:48:59,997 sendKexInit
2024-12-09T10:49:18.4370606Z 09 Dec 2024 10:49:18,415 encode
2024-12-09T10:49:50.2022979Z 09 Dec 2024 10:49:50,146 writeBuffer
That is... strange. Could that be because of using a strong random since to commit 3cc9d48?
Version
2.14.0
Bug description
We upgrade from 2.13.2 to 2.14.0, after that we see timeout in the connections. If we downgrade to 2.13.2 the issue dissapear
Actual behavior
Main log
ClientLog
ServerLog
Expected behavior
With 2.13.2 we have the next logs
Main log
Client Log
Server Log
Relevant log output
No response
Other information
We also test to disable SunJCEWrapper to check if the new feature is related
But we see the timeout and it seem not related to the issue.
The issue only happend in Docker image execution. In local with windows or wsl2 is not reproduced
The text was updated successfully, but these errors were encountered: