Cannot remote debug Wildfly

[Olivier Masseau]

Hello,

I'm running Wildfly 23 on a remote machine and I would like to remote debug it from my local IDE (IntelliJ) but it does not work and I don't undertand why.

First in standalone.xml of Wildfly I added :

-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:8080

After starting standalone.bat I can clearly see it is listening on the debugging port 8080 :

Listening for transport dt_socket at address: 8080

In IntelliJ I've set a new Remote JVM Debug configuration with:

• Debugger mode : 'Attach to remote JVM'
• Transport: Socket
• Host: my_host
• Port: 8080

But it does not work.

I see that Widfly receives something as I can see this error message logged in Wildfly logs when I start the IntelliJ debug session :

ERROR: transport error 202: recv error: Connection timed out

followed immediately by :

Listening for transport dt_socket at address: 8080

Then the debugging session ends in IntelliJ.

Aside from this error message in Wildfly logs I see no error on the client side (IntelliJ) or the server side (Wildfly).

Any idea what could lead to this error and what it means ?

Thanks a lot.

[Richard Opalka]

Hello Olivier,

   You'll need to use different port for remote debugging.

Port 8080 is already used by WildFly HTTP server.

Richard

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/948b6041-6317-47d0-bcda-a79b86301f40n%40googlegroups.com.

[Olivier Masseau]

Hello,

Actually my Wildfly is configured to bind http to port 9000. So port 8080 is free.

I'm using it instead of the default debug port 8787 because I know our firewall does not open port 8787, but 8080 is always opened.

[Richard Opalka]

Hello Olivier,

   Actually that firewall might be the cause of your debugging problem.

Richard