wildfly-maven-plugin project in debug

[Adriano Aguiar]

I'm trying to run the wildfly-maven-plugin project in debug mode and I'm doing it according to the documentation, but without success.

<plugin>

<groupId>org.wildfly.plugins</groupId>

<artifactId>wildfly-maven-plugin</artifactId>

<version>4.2.0.Final</version>

<configuration>

<debug>true</debug>

<debugPort>5005</debugPort>

<debugSuspend>true</debugSuspend>

<startupTimeout>120</startupTimeout>

[James Perkins]

What goal are you attempting to run?

[Adriano Aguiar]

I want to debug my project under development in the same way and when running mvn clean wildfly:dev I can't breakpoint and check

--
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/4241ac79-459d-4c53-90d9-177634a7365an%40googlegroups.com.

--

Adriano Aguiar
Desenvolvedor em Tecnologia da Informação
Desenvolvimento Web (PHP, Javascript, AJAX, Java EE, JSP);

Frameworks ( jQuery, JSF)
Arquiteto de Sistemas (UML, RUP)
Administrador e Programador em SGDB (Oracle PL/SQL, MySQL, SQL ANSI, PostgreSQL);
Servidores de Aplicações (Apache, Tomcat e Glassfish);

[James Perkins]

The dev goal should work with those settings. I regularly use this feature. Are you running the command from the command like like mvn wildfly:dev? That is the only way I've ever ran it. 

[Adriano Aguiar]

Yes, but when listening (Listening for transport dt_socket at address: 5005) there is a timeout

To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/3337a693-08df-47d3-a9a6-021d2f44fcd3n%40googlegroups.com.

[James Perkins]

Have you remotely connected to the debugger? By setting debugSuspend to true you're telling the process to pause until a debugger is connected. This happens before WildFly starts, so the startupTimeout would come into play if you haven't attached a remote debugger. If you just want remote debugging to be available, leave the debugSuspended set to false.

[Adriano Aguiar]

I set debugSuspend to false and it worked, but debug doesn't work when putting one and breakpoint passes straight through

To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/453c41cb-21fc-4adb-a032-704f45cb752bn%40googlegroups.com.

[James Perkins]

Are you connecting with a remote debugger? What IDE are you using?

[Adriano Aguiar]

I want to use local running my development machine and I'm using vscode

To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/e6e78ec0-3742-4f90-8f80-b90a242d282bn%40googlegroups.com.

[James Perkins]

When you run wildfly:dev in debug mode it requires a remote debugger to be attached. You can still connect from your local IDE, it just happens over a socket. There is no way I'm aware of to debug the process without a remote debugger. For VSCode have a look at https://code.visualstudio.com/docs/java/java-debugging#_attach. 

What happens is the wildfly-maven-plugin starts a new process with the effective JVM argument of -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=*:5005.

[Adriano Aguiar]

I switched to intellij IDEA, but it didn't work out very well

To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/c475708a-cf25-428c-8fb9-dd7ea211aeffn%40googlegroups.com.

[James Perkins]

Can you explain a bit the steps you're doing? This works quite well for me and I use it regularly.

My typical workflow would be something like:

mvn clean wildfly:dev -Dwildfly.debug -Dwildfly.debug.port=5005

Once started in IDEA I use SHIFT+F9, on Linux that is the keyboard shortcut, then it attaches to WildFly and I'm able to debug. 

[Adriano Aguiar]

How strange, I ran this same terminal command inside intellij, and it doesn't work

To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/e98f7582-8240-4adc-88d4-6aaebc62df5an%40googlegroups.com.

[Adriano Aguiar]

See my settings as is and even running this command didn't work

[James Perkins]

I'm not too sure what the issue could be. The configuration looks correct. You could try upgrading the plugin to 4.2.2.Final, but I don't recall any issues around the debug configuration.