Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-26251

Server adapter: cannot start in Debug using oc 3.11

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 4.9.0.AM2
    • 4.9.0.AM1
    • openshift
    • None
    • devex #153 August 2018
    • Hide

      1. Create EAP application on cdk based on template (eap 70 basic).
      2. Import project in workspace, and create server adapter.
      3. Restart server adapter in debug.
      Result: Start fails with error message.

      Show
      1. Create EAP application on cdk based on template (eap 70 basic). 2. Import project in workspace, and create server adapter. 3. Restart server adapter in debug. Result: Start fails with error message.
    • Workaround Exists
    • Hide

      Use older version of OC client: like 3.7.1 etc.

      Show
      Use older version of OC client: like 3.7.1 etc.

    Description

      eclipse.buildId=12.9.0.AM1-v20180726-1026-B3091
      java.version=1.8.0_181
      java.vendor=Oracle Corporation
      BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
      Framework arguments:  -product com.jboss.devstudio.core.product
      Command-line arguments:  -data file:/home/jkopriva/devstudio_B3091_testing/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
      
      org.jboss.tools.openshift.core
      Error
      Mon Jul 30 12:53:55 CEST 2018
      Could not launch server eap-app (Service) at OpenShift 3 (192.168.42.218)
      
      com.openshift.restclient.OpenShiftException: OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p
      
      
      Usage:
        oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags]
      
      Examples:
        # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod
        oc port-forward mypod 5000 6000
        
        # Listens on port 8888 locally, forwarding to 5000 in the pod
        oc port-forward mypod 8888:5000
        
        # Listens on a random port locally, forwarding to 5000 in the pod
        oc port-forward mypod :5000
        
        # Listens on a random port locally, forwarding to 5000 in the pod
        oc port-forward mypod 0:5000
      
      Options:
            --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running
      
      Use "oc options" for a list of global command-line options (applies to all commands).
      
      
      	at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.checkProcessIsAlive(AbstractOpenShiftBinaryCapability.java:219)
      	at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.startProcess(AbstractOpenShiftBinaryCapability.java:182)
      	at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:176)
      	at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:112)
      	at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1$1.runOCBinary(PortForwardingUtils.java:148)
      	at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:29)
      	at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:150)
      	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:142)
      	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:366)
      	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:267)
      	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:111)
      	at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:90)
      	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)
      
      
      

      Attachments

        Issue Links

          Activity

            People

              adietish@redhat.com André Dietisheim
              jkopriva@redhat.com Josef Kopriva
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: