[jbosstools-issues] [JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
[
https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-22075 at 4/5/16 11:52 AM:
-------------------------------------------------------------------
So the reason for this is that the remote debugger *IS already STARTED*. There is no need
to manually start it. The manual launch fails because there already is a remote debugger
sitting on those ports.
To verify this its quite easy: switch to the debugging perspective and check if
there's a remote debugger active, which it is since it's launched when you
"Restart in Debug" on the adapter.
!remote-debugger-already-launched.png!
This issue is a NON-ISSUE but we should think about improving the error message, it's
all non-obvious that there already is a remote debugger active and why the new launch
fails.
was (Author: adietish):
So the reason for this is that the remote debugger *IS already STARTED*. There is no need
to manually start it. The manual launch fails because there already is a remote debugger
sitting on those ports
Cannot debug OpenShift application
----------------------------------
Key: JBIDE-22075
URL: https://issues.jboss.org/browse/JBIDE-22075
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Assignee: Fred Bricon
Priority: Critical
Labels: openshift_v3
Attachments: error-in-launching-remote-debugger.png,
error-launching-remote-debugger.png
When I am trying to run remote debugging of an application on OpenShift I get following
error
{code}
Failed to connect to remote VM
com.sun.jdi.connect.spi.ClosedConnectionException
at
org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222)
at
org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214)
at
org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185)
at java.lang.Thread.run(Thread.java:745)
{code}
I guess this is something related to port forwarding. Even the port for debugging is
forwarded on a free port and it looks like started, it fails. When I stop port forwarding,
start it again and use a port, which is used as a forwarded port for remote debug port, in
debug configuration, it works.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)