[
https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-22075 at 4/4/16 8:27 AM:
------------------------------------------------------------------
[~mlabuda] can you explain the above, it's not obvious at all what your netstat output
stands for.
[~fbricon] is this something you could look at since you're the one that's most
intimate with the debugging tooling?
was (Author: adietish):
[~fbricon] is this something you could look at since you're the one that's most
intimate with the debugging tooling?
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
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)