Warning: Github issues are not an official support channel for Recurly. If you have an urgent request we suggest you contact us through an official channel: support@recurly.com or https://recurly.zendesk.com
Describe the bug
After upgrading to 0.100.0, we are seeing a new exception intermittently but frequently, as often as 50%:
...
Caused by: java.net.SocketException: Connection reset at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
Because this is not in the list of IOException subtypes that are re-thrown as ConnectionErrorException, it swallowed and returned as null so that it can't be handled by retry logic in the calling code.
To Reproduce
The behavior is occurring across all endpoints. Reverting to 0.34.0 fixes the issue.
Expected behavior
Either:
- There are fewer
SSLException instances or
ConnectionErrorException is thrown on SSLException
Your Environment
- Lib Version: 0.100.0
- Java Version: 1.8
- Kotlin Version: 1.3.20
Warning: Github issues are not an official support channel for Recurly. If you have an urgent request we suggest you contact us through an official channel: support@recurly.com or https://recurly.zendesk.com
Describe the bug
After upgrading to 0.100.0, we are seeing a new exception intermittently but frequently, as often as 50%:
Because this is not in the list of
IOExceptionsubtypes that are re-thrown asConnectionErrorException, it swallowed and returned as null so that it can't be handled by retry logic in the calling code.To Reproduce
The behavior is occurring across all endpoints. Reverting to 0.34.0 fixes the issue.
Expected behavior
Either:
SSLExceptioninstances orConnectionErrorExceptionis thrown onSSLExceptionYour Environment