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
We hit javax.net.ssl.SSLException: Connection reset multiple times on our long running application and we found a bug with the following scenario:
the application makes a call
the application keeps running for minutes without making any call
the application makes another call but it gets a Connection reset exception
We found out that the step 3 was reusing the connection created at step one (from the connection pool) but it was closed on server side. This means that the sdk is set up with different values for the timeout.
I confirm that this issue happens in the generated code. I think we should log that on openapi generator repository instead. Since other requirements might need us to move out of this client I think we can
move to native client only for connectors.
Let your team test it properly
We hit
javax.net.ssl.SSLException: Connection reset
multiple times on our long running application and we found a bug with the following scenario:Connection reset
exceptionWe found out that the step 3 was reusing the connection created at step one (from the connection pool) but it was closed on server side. This means that the sdk is set up with different values for the timeout.
Here's a reproducer
The execution of it leads to
The text was updated successfully, but these errors were encountered: