[jbosstools-issues] [JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application

[Andre Dietisheim (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-22075:
-------------------------------------
            Issue Type: Enhancement  (was: Bug)
           Description: 
If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically.
If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message
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}


  was:
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.

    Steps to Reproduce: 
ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace.
EXEC: Select "Restart in Debug" in context menu of server adapter.
ASSERT: Server adapter is in state debugging ("[Debugging, Started]").
EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging.

RESULT: Error is shown.
!error-in-launching-remote-debugger.png!

EXPECTED RESULT: The error should tell you that there already is an entry that's running.

  was:
ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace.
EXEC: Select "Restart in Debug" in context menu of server adapter.
ASSERT: Server adapter is in state debugging.
EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging.

RESULT: Error is shown.
!error-in-launching-remote-debugger.png!
EXPECTED RESULT: Debugger works.



> Cannot debug OpenShift application
> ----------------------------------
>
>                 Key: JBIDE-22075
>                 URL: https://issues.jboss.org/browse/JBIDE-22075
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 4.3.1.CR1
>            Reporter: Marián Labuda
>            Assignee: Fred Bricon
>            Priority: Critical
>              Labels: openshift_v3
>             Fix For: 4.4.0.Alpha1
>
>         Attachments: error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, remote-debugger-already-launched.png
>
>
> If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically.
> If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message
> 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}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)