Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

okhttp3 doesn't restart in an application container context.

Open
  • Is something wrong?
#154 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
api, backend

Research direction

Reproduce the okhttp3 restart failure in an EE 10 Tomcat application container and capture the full executor-rejection path. The issue names no source files or tests, so first identify the connector entry point that creates and shuts down okhttp3 resources. Done means restart behavior is understood and the connector no longer fails on a supported container lifecycle, with regression coverage.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Java
Stars
580
Forks
258
Avg merge
30m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from binance/binance-connector-java

All issues in binance/binance-connector-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.