[ https://issues.jboss.org/browse/JBIDE-9442?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-9442: ------------------------------------ Ok... I found the string (which I probably should have searched for earlier). It's in the method where we no longer hard-code localhost, but I didn't update the error message string. {code} debugUtils.setupRemoteDebuggerLaunchConfiguration(workingCopy, null, localDebugPort, server.getHost()); debuggerLaunchConfig = workingCopy.doSave(); boolean launched = false; try { ret = debuggerLaunchConfig.launch("debug", new NullProgressMonitor()); launched = true; } catch (Exception e) { e.printStackTrace(); } if (!launched){ throw toCoreException("Unable to start a remote debugger to localhost:"+localDebugPort); } {code} I can improve the error messaging here to also include the root exception (which we seem to just print out and ignore). This may help us discover what else is wrong. Question: if you go set up a "remote java application" launch configuration manually, can you seriously just use host "marvin" ? I'm able to get a raw remote java app launch config to fail if I don't have a project path added... but I'm not able to replicate when running against a remote jboss / wf / eap... -- This message was sent by Atlassian JIRA (v6.4.11#64026)