]
Andre Dietisheim edited comment on JBIDE-25611 at 1/29/18 4:01 AM:
-------------------------------------------------------------------
Some of the problems with non-matching pods are apparently related to bad setup: btw. 2
"sessions" i use "Delete Resources" which it turns out incompletely
removes resources: JBIDE-25670
was (Author: adietish):
Some of the problems with non-matching pods are apparently related to bad setup: btw. 2
"sessions" i use "Delete Resources" which it turns out incompletely
removes resources: JBIDE-25611
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, image-2018-01-24-18-58-29-159.png,
image-2018-01-25-10-49-09-369.png, image-2018-01-26-00-49-39-691.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}