I have been watching another thread where the user has a similar problem on JBoss. The user came back with a reply saying that he got it working by swapping the position of address=8787 (in your case the port is 8011) and server=y
The server=y comes before the "address". It might just be a coincidence that it started working after this change. I am still trying to understand how the positioning works. You might want to give this a try.
Sun's VM implementations require command line options to load the JDWP agent for debugging. From 5.0 onwards the -agentlib:jdwp option is used to load and specify options to the JDWP agent. For releases prior to 5.0, the -Xdebug and -Xrunjdwp options are used (the 5.0 implementation also supports the -Xdebug and -Xrunjdwp options but the newer -agentlib:jdwp option is preferable as the JDWP agent in 5.0 uses the JVMTI interface to the VM rather than the older JVMDI interface).
So if none of the suggested options, in my earlier posts, work for you then you might want to try using
Originally posted by Jaikiran Pai: I am still trying to understand how the positioning works.
After spending sometime on trying to understand this and reproduce this issue on my local setup, i now know what the real problem was. It had nothing to do with the order in which the "server" and "address" parameters were specified.
Originally posted by Meir Yan:
this is the tomcat confuguration for the remote debugging -Xdebug -Xrunjdwp:transport=dt_socket,address=8011 ,server=y,suspend=n
Observer closely, there's a space between 8011 and the comma. I use JBoss on which i have been successfully configuring debugger using the following parameters:
In order to reproduce this issue, i too added a space after 8787 and the comma:
and started getting the same exception as you. Removing that space fixed the problem. There should not be any space before or after (any of) those comma separated JDPA parameters. The order of "server" and "address" had nothing to with the issue. It was just a coincidence that the space was removed from the parameters when you swapped those parameters. So if you go back and undo the changes and remove the space from that configuration, i bet you too will be able to get this working.
I used to use remote debug configuration in IDE (Eclipse or IntelliJ) to be a client so I forgot to run debugger first. Hence, please run the debugger first and ensure that the chosen port is opened. That info can be obtained via netstat utility either in Windows or in Unix.
Poop goes in a willow feeder. Wipe with this tiny ad:
how do I do my own kindle-like thing - without amazon