gwt-plugins / gwt-plugins/gwt-eclipse-plugin
Getting internal jetty server TimeoutException when service call exeeds 30 seconds
- Dominant language
- Java
- Stars
- 116
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
Caused by: java.util.concurrent.TimeoutException: Idle timeout expired: 30000/30000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:161)
at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file, test, or entry point is identified; start by reproducing a service call that exceeds 30 seconds and trace the internal Jetty server through the reported org.eclipse.jetty.io.IdleTimeout stack trace. Done requires clarifying the intended behavior for long-running calls and verifying it against the observed 30000 ms timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100