maven-mvnd: Connection timeout when trying to execute any build
Hello,
I am getting this error every time I am trying to run a build:
“mvnd clean install”
I am running the software on a VPN, don’t know if that may be the issue.
WARNING: Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
[main] INFO org.jboss.fuse.mvnd.common.DaemonRegistry - Removing 0 daemon stop events from registry
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Previous Daemon (df642d73-ad18-43a0-9821-0ad3b45610d1) stopped at 1599465245603 by user or operating system
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Starting a Maven Daemon, 1 stopped Daemon could not be reused, use --status for details
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Removing daemon from the registry due to communication failure. Daemon information: DaemonInfo{uid=9e37e4ec-8243-43e3-9a18-8e33fd9a6de1javaHome=C:\Program Files\Java\jdk1.8.0_251\jre, options=[], mavenHome=C:\apps\mvnd-0.0.4-windows-amd64, pid=35024, address=50141, idleTimeout=10800000, locale=en-US, state=Busy, lastIdle=1599465354751, lastBusy=1599465354751}
Exception in thread "main" org.jboss.fuse.mvnd.common.DaemonException$ConnectException: Could not connect to the Maven daemon.
Daemon uid: 9e37e4ec-8243-43e3-9a18-8e33fd9a6de1
log file: C:\apps\mvnd-0.0.4-windows-amd64\daemon\daemon-9e37e4ec-8243-43e3-9a18-8e33fd9a6de1.log
----- Last 20 lines from daemon log file - C:\apps\mvnd-0.0.4-windows-amd64\daemon\daemon-9e37e4ec-8243-43e3-9a18-8e33fd9a6de1.log -----
09:55:54.759 I Daemon started
09:55:54.762 D daemon is running. Sleeping until state changes.----- End of the daemon log -----
at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:302)
at org.jboss.fuse.mvnd.client.DaemonConnector.startDaemon(DaemonConnector.java:233)
at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:114)
at org.jboss.fuse.mvnd.client.DefaultClient.execute(DefaultClient.java:188)
at org.jboss.fuse.mvnd.client.DefaultClient.main(DefaultClient.java:71)
Caused by: org.jboss.fuse.mvnd.common.DaemonException$ConnectException: Could not connect to server 0.0.0.0/0.0.0.0:50141.
at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:359)
at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemon(DaemonConnector.java:312)
at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:299)
... 4 more
Caused by: java.net.SocketTimeoutException
at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:129)
at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:349)
... 6 more
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 33 (20 by maintainers)
You got it!, good job!
@galegofer https://github.com/mvndaemon/mvnd/commit/0656e1337ad75982f07df1acf2805a5f4fdce62c fixed it for me. So in case you want to try it out before 0.0.9 is released, you can try the SNAPSHOT: https://github.com/mvndaemon/mvnd/suites/1382179406/artifacts/22751642
Just checked this on my business laptop (which is using Checkpoint VPN) and it works for me! TBH I would have expected to see the same problem. Anway, it might help if one could tell
mvndto bind to and connect to127.0.0.1instead of0.0.0.0.@ppalaga Could also be Git Bash.
Thanks, that fixed it for me on macOS! 👍