Build crashes due to timeout or deamon not responding in time
- Dominant language
- Java
- Stars
- 3.5k
- Forks
- 250
- Avg merge
- 16h 22m
- Merged PRs (30d)
- 36
Description
Hi there,
when building a rather large project (395 maven modules), mvnd runs for few minutes and then radomly "crashes" with the following error.
```
Exception in thread "main" org.jboss.fuse.mvnd.common.DaemonException$StaleAddressException: Could not receive a message from the daemon.
at org.jboss.fuse.mvnd.client.DaemonClientConnection.receive(DaemonClientConnection.java:107)
at org.jboss.fuse.mvnd.client.DefaultClient.execute(DefaultClient.java:198)
at org.jboss.fuse.mvnd.client.DefaultClient.main(DefaultClient.java:72)
Caused by: java.io.IOException: No message received within 3000ms, daemon may have crashed
at org.jboss.fuse.mvnd.client.DaemonClientConnection.receive(DaemonClientConnection.java:100)
... 2 more
```
However if I check the running processes, I can still see mvnd building the project in the background. Is there a setting for the timeout to the deamon process?
Thanks for the nice tool and your support!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the timeout path in org.jboss.fuse.mvnd.client.DaemonClientConnection, especially receive, and its callers in DefaultClient. Reproduce the failure with a large Maven multi-module build while checking whether the daemon continues running. Done means the cause and expected handling of the 3000ms no-message condition are established and covered by an appropriate test or configuration change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100