[
https://issues.jboss.org/browse/JBIDE-25611?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-25611 at 1/24/18 12:55 PM:
--------------------------------------------------------------------
This is quite odd.
When launching into an existing pod that is set to debugging the tooling will error
complaining about a missing debug port:
!port-missing.png!
When looking into the pod I see it launching node with the debug flag and port
{code}
PID TTY STAT TIME COMMAND
1 ? Ssl 0:00 node /opt/rh/rh-nodejs6/root/usr/bin/nodemon --debug=5858
{code}
The port is *NOT* exposed by the REST service though:
!pod-ports-online.png!
Accordingly the port forwarding in the tooling wont have the debugging port and cannot
start forwarding to it which explains the above error.
If I launch the port forwarding manually via "oc" and launch the nodejs debugger
in Eclipse I see the debugging fine.
In comparison in the CDK the pod is exposing the debugging port:
!pod-ports-cdk.png!
[~jeffmaury] ideas?
was (Author: adietish):
This is quite odd.
When launching into an existing pod that is set to debugging the tooling will error
complaining about a missing debug port:
!port-missing.png!
When looking into the pod I see it launching node with the debug flag and port
{code}
PID TTY STAT TIME COMMAND
1 ? Ssl 0:00 node /opt/rh/rh-nodejs6/root/usr/bin/nodemon --debug=5858
{code}
The port is not exposed by the REST service though:
!pod-ports-online.png!
Accordingly the port forwarding in the tooling wont have the debugging port and cannot
start forwarding to it.
If I launch the port forwarding manually via "oc" and launch the nodejs debugger
in Eclipse I see the debugging fine.
In comparison in the CDK the pod is exposing the debugging port:
!pod-ports-cdk.png!
[~jeffmaury] ideas?
Server adapter: timeouts when starting into "Debug" on
OpenShift Online
-----------------------------------------------------------------------
Key: JBIDE-25611
URL:
https://issues.jboss.org/browse/JBIDE-25611
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.5.2.Final
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.5.3.AM1
Attachments: error-waiting-for-new-pod.png, pod-ports-cdk.png,
pod-ports-online.png, port-missing.png
# ASSERT: have an account on OpenShift Online
# EXEC: create a new application via template nodejs-mongo-persistent
# EXEC: have the project imported into the workspace and the server adapter for it
created
# ASSERT: you have a new server adapter for your app in state [stopped]
# EXEC: start the adapter into "Debug"
Result:
The adapter takes a lot of time to start but wont succeed eventually. You get the
following error dialog:
!error-waiting-for-new-pod.png!
In the Eclipse log you'll find the following:
{code}
org.eclipse.core.runtime.CoreException: Failed to detect new deployed Pod for
nodejs-mongo-persistent
at
org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitFor(OpenShiftDebugMode.java:403)
at
org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.waitForNewPod(OpenShiftDebugMode.java:395)
at
org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.getPod(OpenShiftDebugMode.java:226)
at
org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:170)
at
org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
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)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)