-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeout in client #733
Comments
It may just be a coincidence that two keep alive messages have more than 3 seconds between them, but we need to investigate that it does not cause the failure.
|
I don't really see how there could be a delay, so in my example, there must be another gap between the last message and the exception (on which there's no timestamp). |
We have the same error in our project too. Fails in the Jenkins environment. It seems that the daemon really dies, that's why we get that error. When running mvnd --status there is no daemon listed. Shouldn't they be idle? |
i'm too Exception in thread "main" org.mvndaemon.mvnd.common.DaemonException$StaleAddressException: Could not receive a message from the daemon.
Caused by: java.io.IOException: No message received within 3000ms, daemon may have crashed. You may want to check its status using mvnd --status |
The client sometimes assumes that the daemon has died because of the elapsed time between messages, while messages have been received after the last keep alive.
The text was updated successfully, but these errors were encountered: