Remote Debugging, connetion refused !!

[gallark]

Hi all, I would like to help me with a

problem I have, this is an application created

sigiuente under the environment:

• jdk 1.6.0_26
• Helios Eclipse
• Ejb project
• SA Jboss 5.0
• OS Windows XP - firewall disabled

The thing is trying to do remote debugging

invariably throws the following error:

Failed to connect to remote VM. Connection refused.

Connection refused: connect!

To try to achieve the remote debug did the following

Changing file of jboss 5.0.1 ga RUN.CONF

JAVA_OPTS = "$ JAVA_OPTS -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server =y,suspend=n,address=8002"

Setting the debug

• Project: NombreDeMiProyecto
• connection type: standart (Socket Attach)
• host: localhost
• port: 8002

would appreciate your feedback to solve this problem.

[wdfink]

How do you start the JBoss? Do you use the bind option '-b' in this case you might bind against a different IP address as localhost.

Also I recommend to use 5.1.0 instead of a 5.0 version.

[gallark]

Hey thanks for replying, and switch to version 5.1 GA,

I connect on windows option eclipse / preferences / server / addjbossComunity Runtime Environment - 5.0,

but even this fails with the debug remote

I just noticed that failure to the debug out two messages on the console, they say:

03:01:39,171 WARN  [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container

03:01:39,171 WARN  [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container

and simultaneously shows the error message

Failed to connect to remote VM. Connection refused.

Connection refused: connect

another thing is that when I try to Initiate the jboss jboss from files,run.bat, does not lift the server and therefore I can not get into theweb console, this means something?

Saludos

----------------------------------------------------------------------------

updated:

After some (many) hours of trial and error was

solved the problem. Goodbye.