| Debugging remote server through external launch? [message #229419] |
Mon, 23 March 2009 15:41  |
 Anders Olsson
Messages: 21
Registered: July 2009 |
Junior Member |
|
|
Hello,
I have created a generic server adapter, launching through an external
script. Starting it normally works fine, but starting it in debug mode
doesn't seem to do anything more than a normal start.
I've activated debugging in the Appserver (based on Glassfish). I've set
<debugPort> to 9009 in the start-element of the serverdef. But when I set
a breakpoint in a JSP's dynamic part, launch the server in debug mode,
republish and visit the page, no brake is made.
To confirm that debugging is activated I've created a "Remote Java
Application" Debug Launch Configuration connecting to my remote server, on
port 9009 through "Socket Attach". Doing that worked instantly, and I got
a break on the right line with the fitting code as soon as I reloaded the
page.
Is there something more than specifying a debugPort and launching in debug
mode for this to work?
I just debugged
org.eclipse.jst.server.generic.core.internal.ExternalDebugLa unchConfigurationDelegate
R3_0_3 and found that on line 66, a map is fetched:
Map argMap =
configuration.getAttribute(IJavaLaunchConfigurationConstants .ATTR_CONNECT_MAP,
(Map)null);
The content of this map is the port number (set correctly) and the
hostname to debug against, which is set to "localhost". This certainly
seems like a bug, since my server adapter is set to run against a remote
IP. I've modified the hostname when debugging, to the port my server is
at, and then debugging works as it should.
From my perspective this seems to be a bug, where the launcher expects to
only connect locally, when that certainly isn't always the case. Can
someone confirm that they have been able to debug against a remote
externally launched server? If that isn't the case, I'll file a bug report.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03154 seconds
] 
Search
Help
Register
Login
Home
