[jbosstools-issues] [JBoss JIRA] (JBIDE-25672) Server adapter: spring-boot-camel-xml adapter throws "null" error when starting (open.paas.redhat.com)
Jeff MAURY (JIRA)
issues at jboss.org
Wed Mar 28 05:52:03 EDT 2018
[ https://issues.jboss.org/browse/JBIDE-25672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff MAURY updated JBIDE-25672:
-------------------------------
Sprint: devex #146 March 2018, devex #147 April 2018 (was: devex #146 March 2018)
> Server adapter: spring-boot-camel-xml adapter throws "null" error when starting (open.paas.redhat.com)
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25672
> URL: https://issues.jboss.org/browse/JBIDE-25672
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: server_adapter
> Fix For: 4.5.3.Final
>
> Attachments: image-2018-01-29-15-48-29-101.png
>
>
> # ASSERT: have a connection to open.paas.redhat.com
> # EXEC: create a new app based on the "s2i-spring-boot-camel-xml" template. Have the project imported to your workspace and the server adapter created
> # ASSERT: a server adapter "s2i-spring-boot-camel-xml" is created
> # EXEC: wait for the adapter to get "[started]"
> Result:
> After some waiting time the adapter throws the following error:
> !image-2018-01-29-15-48-29-101.png!
> In the Eclipse log you find the following:
> {code}
> !MESSAGE Could not launch server s2i-spring-boot-camel-xml (DeploymentConfig) at OpenShift 3 (open.paas.redhat.com)
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.jboss.tools.openshift.internal.core.server.debug.DebugContext.<init>(DebugContext.java:64)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.createDebugContext(OpenShiftLaunchController.java:199)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:93)
> 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)
More information about the jbosstools-issues
mailing list