spring-cloud / spring-cloud/spring-cloud-gateway

Gateway-mvc stops responding after ~3 hours of deployment; threads in TIMED_WAITING, no downstream service calls

Open
#3,841 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

waiting-for-triage
Dominant language
Java
Stars
4.9k
Forks
3.5k
Avg merge
20h 57m
Merged PRs (30d)
8

Description

after deploying the gateway service, it works fine initially. However, after approximately 3 hours, it stops forwarding requests to downstream services. The gateway itself continues to respond to endpoint calls, but no traffic reaches the downstream services, even though they are live and healthy.
 
Observed Behavior:
 
Gateway responds to incoming requests.
No calls are made to downstream services.
All threads in the gateway go into TIMED_WAITING state.
No errors or exceptions are logged.
Downstream services are confirmed to be up and running.

Contributor guide

Open the contributing guide

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.

Research direction

Start with the Gateway-mvc deployment and reproduce the failure after the reported interval, then inspect the gateway's thread state when requests stop reaching downstream services. Confirm the gateway still answers endpoint calls while all threads are in TIMED_WAITING and no errors are logged; done means identifying the cause and restoring downstream forwarding.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.