Skip to content
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

Running maven daemon fails on windows #35

Closed
Dunemaster opened this issue Jun 29, 2020 · 6 comments
Closed

Running maven daemon fails on windows #35

Dunemaster opened this issue Jun 29, 2020 · 6 comments
Labels
wontfix This will not be worked on

Comments

@Dunemaster
Copy link

Dunemaster commented Jun 29, 2020

Running maven daemong fails on windows

Releases 0.0.0
Windows 10

E:\dev\g5rt\runtime>"E:\Program Files\mvnd\mvnd-windows-amd64"
Jun 29, 2020 12:57:30 PM org.jline.utils.Log logr
WARNING: Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
[main] INFO org.jboss.fuse.mvnd.client.DaemonRegistry - Removing 0 daemon stop events from registry
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Starting a Maven Daemon (subsequent builds will be faster)
[main] INFO org.jboss.fuse.mvnd.client.DaemonConnector - Removing daemon from the registry due to communication failure. Daemon information: DaemonInfo{uid=192ee0bd-5fac-404a-9726-6e8b75cbac61javaHome=C:\Program Files\BellSoft\LibericaJDK-11, options=[], mavenHome=E:\mvnd, pid=27040, address=52076, idleTimeout=10800000, locale=ru-RU, state=Busy, lastIdle=1593424651736, lastBusy=1593424651736}
Exception in thread "main" org.jboss.fuse.mvnd.client.DaemonException$ConnectException: Could not connect to the Maven daemon.
Daemon uid: 192ee0bd-5fac-404a-9726-6e8b75cbac61
  log file: E:\mvnd\daemon\daemon-192ee0bd-5fac-404a-9726-6e8b75cbac61.log
----- Last  20 lines from daemon log file - E:\mvnd\daemon\daemon-192ee0bd-5fac-404a-9726-6e8b75cbac61.log -----
12:57:31.744 I Daemon started
12:57:31.747 D daemon is running. Sleeping until state changes.----- End of the daemon log -----

        at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:286)
        at org.jboss.fuse.mvnd.client.DaemonConnector.startDaemon(DaemonConnector.java:215)
        at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:97)
        at org.jboss.fuse.mvnd.client.DefaultClient.execute(DefaultClient.java:218)
        at org.jboss.fuse.mvnd.client.DefaultClient.main(DefaultClient.java:69)
Caused by: org.jboss.fuse.mvnd.client.DaemonException$ConnectException: Could not connect to server 0.0.0.0/0.0.0.0:52076.
        at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:341)
        at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemon(DaemonConnector.java:295)
        at org.jboss.fuse.mvnd.client.DaemonConnector.connectToDaemonWithId(DaemonConnector.java:283)
        ... 4 more
Caused by: java.net.SocketException: Permission denied: no further information
        at com.oracle.svm.jni.JNIJavaCallWrappers.jniInvoke_ARRAY:Ljava_net_SocketException_2_0002e_0003cinit_0003e_00028Ljava_lang_String_2_00029V(JNIJavaCallWrappers.java:0)
        at com.oracle.svm.jni.functions.JNIFunctions$NewObjectWithObjectArrayArgFunctionPointer.invoke(JNIFunctions.java)
        at com.oracle.svm.jni.functions.JNIFunctions.ThrowNew(JNIFunctions.java:801)
        at sun.nio.ch.SocketChannelImpl.checkConnect(SocketChannelImpl.java)
        at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:776)
        at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:120)
        at org.jboss.fuse.mvnd.client.DaemonConnector.connect(DaemonConnector.java:331)
        ... 6 more
@ppalaga
Copy link
Contributor

ppalaga commented Jun 29, 2020

Have you been able to run mvnd --install before you got the above?

Could you please paste the content of E:\mvnd\daemon\daemon-192ee0bd-5fac-404a-9726-6e8b75cbac61.log ?

@ppalaga
Copy link
Contributor

ppalaga commented Jun 29, 2020

Thanks for the report, BTW :)

@Dunemaster
Copy link
Author

Dunemaster commented Jun 29, 2020

Have you been able to run mvnd --install before you got the above?

Yes, it ran ok.

@Dunemaster
Copy link
Author

@ppalaga
Copy link
Contributor

ppalaga commented Jul 30, 2020

I was able to run mvnd -v (which connects to a daemon) successfully on windows.

image

Maybe you have too restrictive firewall settings? Windows defender asked me about the network access of java.exe when I have run it for the first time. I allowed both local and remote.

@ppalaga
Copy link
Contributor

ppalaga commented Jul 30, 2020

Closing as "Can't reproduce"

@ppalaga ppalaga closed this as completed Jul 30, 2020
@ppalaga ppalaga added this to the Black hole milestone Jul 30, 2020
@gnodet gnodet added the wontfix This will not be worked on label Dec 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants