-
Bug
-
Resolution: Done
-
Major
-
4.5.3.AM2
-
devex #146 March 2018
steps:
- ASSERT: have a server adapter running for an existing application/service
- EXEC: stop the adapter
- EXEC: delete the service
- EXEC: start the adapter or publish it (which implicitly starts it)
Result:
You get an error telling you that the server could not publish because it didnt find the service to publish to. But it wont tell you what resource it was looking for.
Matching output is to be found in the Eclipse log:
!MESSAGE Could not publish to the server. !STACK 0 java.lang.NullPointerException at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.syncUp(OpenShiftPublishController.java:162) at org.jboss.tools.openshift.core.server.behavior.OpenShiftPublishController.publishFinish(OpenShiftPublishController.java:154) at org.jboss.tools.openshift.core.server.behavior.springboot.OpenShiftSpringBootPublishController.publishFinish(OpenShiftSpringBootPublishController.java:41) at org.jboss.ide.eclipse.as.wtp.core.server.behavior.CachedPublisherProfileBehavior.publishFinish(CachedPublisherProfileBehavior.java:54) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:1011) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3182) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:355) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) !ENTRY org.jboss.tools.openshift.core 4 0 2018-03-14 00:59:01.671 !MESSAGE Server camel-ose-springboot-xml (Service) at OpenShift 3 (192.168.64.38) could not determine the service to publish to.
