[
https://issues.jboss.org/browse/JBIDE-26407?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-26407:
------------------------------------------
[~dbocharov] hm, sounds weird. It looks like you have oc on the path?
Thanks for testing but not sure that there's added value to further dig into
what's wrong for you given that [~odockal] could confirm my finding.
Server adapter: fails with a NPE if there's no oc configured
-------------------------------------------------------------
Key: JBIDE-26407
URL:
https://issues.jboss.org/browse/JBIDE-26407
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.9.0.Final
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Major
Labels: oc_binary, server_adapter
Fix For: 4.10.0.AM1
Attachments: screenshot-1.png, screenshot-2.png
steps:
# ASSERT: start with a workspace where's no preference that points to an oc binary
# ASSERT: have the connection *NOT* overriding the oc binary location
# EXEC: create a new application (ex. by using the *nodejs-mongo-persistent* template),
have the project imported to your workspace and the server adapter created
# EXEC: start the server adapter
Result:
you get an error dialog reporting an NPE
!screenshot-1.png!
The following can be spotted in the Eclipse log:
{code}
java.lang.NullPointerException
at java.base/java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1022)
at java.base/java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1017)
at com.openshift.restclient.OpenShiftContext.put(OpenShiftContext.java:51)
at
org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:27)
at
org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:156)
at
org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
at
com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94)
at
org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:148)
at
org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:402)
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:36)
at
org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252)
at
org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186)
at
org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:147)
at
org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:96)
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:859)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717)
at
org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712)
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:60)
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)