okhttp3 doesn't restart in an application container context.

[aracataca]

When restarting okhttp3 in an EE 10 container, Tomcat, the following error issues, "java.io.InterruptedIOException: executor rejected", resulting in this being in effect a one shot library, which is fine for Android, okhttp3's intended target. What can be done, if anything. Kind regards.

[theo-s68]

Hello,

Which version of the dependency are you using ? Could you please give the steps to reproduce ?

We will try to reproduce the issue and fix it.
Thank you.

[aracataca]

Hello Theo, Thanks for your prompt reply. I've attached the top of the offending stack trace from the Tomcat server in a PDF, okhttp3.pdf. In answer to your question, I'm using okhttp3 version 4.12, with your legacy library, much as your recent library does. To my mind it is faulty, a bit. In order to reproduce the fault: - connect up an API session, with APIKEY and secret PEM file - disconnected, then... - reconnect with the same session credentials In the context of the Android, this is not a fault, as app's are dismissed entirely once used. But in an application container, it's a bit of a problem. Shutdown needs to be cleaner. Happy hunting, and kind regards, Bill On Monday, May 19, 2025 at 03:35:47 AM UTC, theo-s68 ***@***.***> wrote: theo-s68 left a comment (binance/binance-connector-java#154) Hello, Which version of the dependency are you using ? Could you please give the steps to reproduce ? We will try to reproduce the issue and fix it. Thank you. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[theo-s68]

Hello,

Could you please send the full error stack trace as well ?

Thanks.

[aracataca]

Hello, Oops, sorry. Full stack trace attached. It's a bit long, as am running one framework inside another. Vaadin, in Spring. Good luck. Kind regards, Bill On Tuesday, May 20, 2025 at 04:28:25 AM UTC, theo-s68 ***@***.***> wrote: theo-s68 left a comment (binance/binance-connector-java#154) Hello, Could you please send the full error stack trace as well ? Thanks. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>