[jbosstools-issues] [JBoss JIRA] (JBIDE-24965) Server adapter: fails to "Restart in Debug"

Josef Kopriva (JIRA) issues at jboss.org
Fri Sep 22 05:17:00 EDT 2017


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

Josef Kopriva closed JBIDE-24965.
---------------------------------


Debugging is working without errors. Verified in: 
Red Hat JBoss Developer Studio
Version: 11.1.0.AM2
Build id: AM2-v20170914-1647-B1060
Build date: 20170914-1647

> Server adapter: fails to "Restart in Debug"
> -------------------------------------------
>
>                 Key: JBIDE-24965
>                 URL: https://issues.jboss.org/browse/JBIDE-24965
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.5.1.AM2
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>            Priority: Critical
>              Labels: openshift_v3, server_adapter
>             Fix For: 4.5.1.AM2
>
>         Attachments: image-2017-09-02-01-06-58-751.png
>
>
> steps:
> # EXEC: Create a nodejs-mongo-persistent application
> # EXEC/ASSERT: Create a server adapter for the service nodejs-mongo-persistent
> # EXEC: start the server adapter via "Debug"
> # ASSERT: debugging works
> # EXEC: restart the server adapter via "Restart in Debug"
> Result:
> Debugging fails, you get the following error:
>  !image-2017-09-02-01-06-58-751.png! 
> In the log you find the following entry:
> {code}
> org.eclipse.core.runtime.CoreException: Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> 	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.mapPortForwarding(OpenShiftLaunchController.java:357)
> 	at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.access$0(OpenShiftNodejsLaunchController.java:1)
> 	at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController$1.onDebugChange(OpenShiftNodejsLaunchController.java:83)
> 	at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:221)
> 	at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.launch(OpenShiftNodejsLaunchController.java:52)
> 	at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> 	at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> 	at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> 	at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> !SUBENTRY 1 org.jboss.tools.openshift.core 4 0 2017-09-02 00:32:34.031
> !MESSAGE Could not find running pod to forward to in server adapter "nodejs-mongo-persistent (Service) at OpenShift 3 (192.168.64.2)"
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbosstools-issues mailing list