Hi Gary
I have exactly the same problem.
Did you find a solution?

I look forward hearing from you soon.

Regards,
Carlo

I'm having the same problem. I'm using IDEA (IntelliJ is the company - and YES, they do make the best IDE on the market). Debugging works great with Weblogic, Websmere, and any other remote java process I invoke. I'm having a problem with JBoss, however, and it's exactly as described above.

I've searched google, sun, bea, and oracle sites, but to no avail. Please email me if you find the solution. Looks like it's Sys.out for me tonight!

:op

I'm using JBoss 3.0.2 with IDEA 3.0 (build 648).
I have no problem when I run JBoss with following parameters

set JAVA_OPTS=-classic -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y %JAVA_OPTS%

This setting is already in the run.bat but commented out.

On IDEA side, I only changed port number from 5000 to 8787.

Are you guys using JBoss 2.x?

Miki

I am using the following parameters in my run.bat

set JAVA_OPTS=-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8787 %JAVA_OPTS%

And I am using inside IntelliJ the following -

-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8787

It does not attach. At lease I do not see it stopping at breakpoints.

If instead I start it in the .bat file with suspend=y parameter, it does not proceed in the console window, just hangs.

Is anything wrong?

It does not stop either on my startup class (mentioned in user-service.xml), or in my MBean methods (which are called from startupl class visa invoke)

ItelliJ sais:
"Connecting to the target VM at 'localhost:8787' using socket transport"

Does that mean it has been connected?
Or does that mean it is trying to connect? I am using IntelliJ 3.0.5

Does that actually matter that I built my project not in IntelliJ, but by ant (through ant build in IntelliJ)?

Yes, if not connected you will see an error msg within an error dialog and in your output window.
No matter where you are compiling, you can debug as long as you compiled with debug information.
BTW, IntelliJ supports ANT, but it is not really built in, e.g. IntelliJ can't check compiled classes when tracking for "only compiling changed dependent classes" when the classes are compiled with anything different from the IntelliJ javac, even if this is javac in your build.xml .

Greetings,
Frito

Hmmm. I do not see error messages. But it does not stop on breakpoints. I used debug="true" in my ant javac statement.

"arabin" wrote:
Hmmm. I do not see error messages. But it does not stop on breakpoints. I used debug="true" in my ant javac statement.