ppalaga commented on issue #772: URL: https://github.com/apache/maven-mvnd/issues/772#issuecomment-1545531757
> > It would be nice to see in which state is the daemon process when client gives up trying to connect. Is the daemon process alive at all - to check that , you could add some sort of windows counterpart of ps | grep java to your GH actions script. Is it listening on the requested port (I'd do netstat -tulpen | grep java on linux)? > > I am not sure that is something we can test inside GitHub Actions CI as it runs one process after another and is non-interactive. You can put those commands right after the mvnd invocation, possibly in an "on failure" block. GH actions has some special syntax for that. I am really curious, whether the daemon process is still up when the client gives up waiting. If it is not up then you need to find out what prevents it from starting, e.g. by trying to invoke that logged `java.exe -classpath ...` command directly. If it is up, it would be interesting to see what state is it in, e.g. by inspecting its heapdump. Is it blocked by something? Is it just too slow (because the GHA machine is so underpowered)? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
