maven-mvnd: Build crashes due to timeout or deamon not responding in time

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!

About this issue

Original URL
State: open
Created 4 years ago
Reactions: 2
Comments: 30 (18 by maintainers)

Most upvoted comments

@deradam the daemon.keepAliveMs also effects the client refresh rate in case there are no other messages, so you may prefer keeping daemon.keepAliveMs=1000 and raise daemon.maxLostKeepAlive=10.

The global properties location is ~/.m2/mvnd.properties.

gnodet on Oct 28, 2020

Yes, I also see it as the main suspect 😃 But it would still be nice to get a witness who sees a GC happening at that time via some monitoring tool.

Of course. I try to collect data and then post them.

DoPaNik on Feb 22, 2021