[JBoss JIRA] (JBIDE-26311) EAP 7.1 fails to stop when connected over ssh
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26311:
-------------------------------
Sprint: devex #155 September 2018
> EAP 7.1 fails to stop when connected over ssh
> ---------------------------------------------
>
> Key: JBIDE-26311
> URL: https://issues.jboss.org/browse/JBIDE-26311
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.9.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: regression
> Fix For: 4.9.0.Final
>
> Attachments: JBIDE-26311.local.ogv
>
>
> I have an EAP 7.1 setup up over ssh. It's running on my localhost, so it's the most basic test of an ssh server. When I click the stop button on the server, it says:
> Server Red Hat JBoss EAP 7.1 ssh failed to stop.
> An exception stack trace is not available.
> It will stop on second attempt. On a local server this would mean killing the server java process. I'm not sure exactly what happens on a remote server, but it works.
> I'm pretty sure this worked last time (previous milestone).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-26311) EAP 7.1 fails to stop when connected over ssh
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26311?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26311:
-------------------------------
Fix Version/s: 4.9.0.Final
> EAP 7.1 fails to stop when connected over ssh
> ---------------------------------------------
>
> Key: JBIDE-26311
> URL: https://issues.jboss.org/browse/JBIDE-26311
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.9.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: regression
> Fix For: 4.9.0.Final
>
> Attachments: JBIDE-26311.local.ogv
>
>
> I have an EAP 7.1 setup up over ssh. It's running on my localhost, so it's the most basic test of an ssh server. When I click the stop button on the server, it says:
> Server Red Hat JBoss EAP 7.1 ssh failed to stop.
> An exception stack trace is not available.
> It will stop on second attempt. On a local server this would mean killing the server java process. I'm not sure exactly what happens on a remote server, but it works.
> I'm pretty sure this worked last time (previous milestone).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-26355) Fuse on openshift project does not work on CDK CDK v3.6.0-alpha.2-1
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26355?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-26355:
---------------------------------------
[~jeffmaury] thx for pointing out - moving to FUSETOOLS
> Fuse on openshift project does not work on CDK CDK v3.6.0-alpha.2-1
> -------------------------------------------------------------------
>
> Key: JBIDE-26355
> URL: https://issues.jboss.org/browse/JBIDE-26355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.9.0.AM3
> Environment: F28
> CDK v3.6.0-alpha.2-1
> Red Hat Developer Studio
> Version: 12.9.0.AM3
> Build id: AM3-v20180906-1322-B3331
> Build date: 20180906-1322
> Reporter: Josef Kopriva
>
> I have tried to reproduce JIRA https://issues.jboss.org/browse/JBIDE-25303 , but during deploy to OpenShift on CDK I get an error.
> Full log of build:
> {code:java}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for org.mycompany:camel-ose-springboot-xml:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.springframework.boot:spring-boot-maven-plugin @ line 172, column 15
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
> [WARNING]
> [INFO]
> [INFO] ---------------< org.mycompany:camel-ose-springboot-xml >---------------
> [INFO] Building Fabric8 :: Quickstarts :: Spring-Boot :: Camel XML 1.0.0-SNAPSHOT
> [INFO] --------------------------------[ jar ]---------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ camel-ose-springboot-xml ---
> [INFO] Deleting /home/jkopriva/fuse-on-openshift/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ camel-ose-springboot-xml ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- fabric8-maven-plugin:3.1.80.redhat-000019:resource (default) @ camel-ose-springboot-xml ---
> [INFO] F8: Running in OpenShift mode
> [INFO] F8: Using docker image name of namespace: myproject
> [INFO] F8: spring-boot: Using fat jar packaging as the spring boot plugin is using `repackage` goal execution
> [INFO] F8: Running generator spring-boot
> [INFO] F8: spring-boot: Using Docker image fabric8/s2i-java as base / builder
> [INFO] F8: Using resource templates from /home/jkopriva/fuse-on-openshift/src/main/fabric8
> 2018-09-10 14:36:03 INFO Version:30 - HV000001: Hibernate Validator 5.2.4.Final
> [INFO] F8: fmp-service: Adding a default Service with ports [8080]
> [INFO] F8: spring-boot-health-check: Adding readiness probe on port 8081, path='/health', with initial delay 10 seconds
> [INFO] F8: spring-boot-health-check: Adding liveness probe on port 8081, path='/health', with initial delay 180 seconds
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [INFO]
> [INFO] --- maven-compiler-plugin:3.6.0:compile (default-compile) @ camel-ose-springboot-xml ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 2 source files to /home/jkopriva/fuse-on-openshift/target/classes
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ camel-ose-springboot-xml ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory /home/jkopriva/fuse-on-openshift/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.6.0:testCompile (default-testCompile) @ camel-ose-springboot-xml ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ camel-ose-springboot-xml ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ camel-ose-springboot-xml ---
> [INFO] Building jar: /home/jkopriva/fuse-on-openshift/target/camel-ose-springboot-xml-1.0.0-SNAPSHOT.jar
> [INFO]
> [INFO] --- spring-boot-maven-plugin:1.4.1.RELEASE:repackage (default) @ camel-ose-springboot-xml ---
> [INFO]
> [INFO] >>> fabric8-maven-plugin:3.1.80.redhat-000019:build (default) > initialize @ camel-ose-springboot-xml >>>
> [INFO]
> [INFO] <<< fabric8-maven-plugin:3.1.80.redhat-000019:build (default) < initialize @ camel-ose-springboot-xml <<<
> [INFO]
> [INFO]
> [INFO] --- fabric8-maven-plugin:3.1.80.redhat-000019:build (default) @ camel-ose-springboot-xml ---
> [INFO] F8: Using OpenShift build with strategy S2I
> [INFO] F8: spring-boot: Using fat jar packaging as the spring boot plugin is using `repackage` goal execution
> [INFO] F8: Running generator spring-boot
> [INFO] F8: spring-boot: Using Docker image fabric8/s2i-java as base / builder
> [INFO] Copying files to /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/build/maven
> [INFO] Building tar: /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/tmp/docker-build.tar
> [INFO] F8: [camel-ose-springboot-xml:latest] "spring-boot": Created docker source tar /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/tmp/docker-build.tar
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 18.250 s
> [INFO] Finished at: 2018-09-10T14:36:19+02:00
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:3.1.80.redhat-000019:build (default) on project camel-ose-springboot-xml: Execution default of goal io.fabric8:fabric8-maven-plugin:3.1.80.redhat-000019:build failed: An error has occurred. timeout: Socket closed -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
> I have also tried this project with oc cluster up(version 3.9.0) and it went without errors.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-26355) Fuse on openshift project does not work on CDK CDK v3.6.0-alpha.2-1
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26355?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-26355:
------------------------------------
You not using the OpenShift tooling, are you ? Should rather be a FUSETOOLS issue or a CDK one ?
> Fuse on openshift project does not work on CDK CDK v3.6.0-alpha.2-1
> -------------------------------------------------------------------
>
> Key: JBIDE-26355
> URL: https://issues.jboss.org/browse/JBIDE-26355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.9.0.AM3
> Environment: F28
> CDK v3.6.0-alpha.2-1
> Red Hat Developer Studio
> Version: 12.9.0.AM3
> Build id: AM3-v20180906-1322-B3331
> Build date: 20180906-1322
> Reporter: Josef Kopriva
>
> I have tried to reproduce JIRA https://issues.jboss.org/browse/JBIDE-25303 , but during deploy to OpenShift on CDK I get an error.
> Full log of build:
> {code:java}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for org.mycompany:camel-ose-springboot-xml:jar:1.0.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.springframework.boot:spring-boot-maven-plugin @ line 172, column 15
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
> [WARNING]
> [INFO]
> [INFO] ---------------< org.mycompany:camel-ose-springboot-xml >---------------
> [INFO] Building Fabric8 :: Quickstarts :: Spring-Boot :: Camel XML 1.0.0-SNAPSHOT
> [INFO] --------------------------------[ jar ]---------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ camel-ose-springboot-xml ---
> [INFO] Deleting /home/jkopriva/fuse-on-openshift/target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ camel-ose-springboot-xml ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- fabric8-maven-plugin:3.1.80.redhat-000019:resource (default) @ camel-ose-springboot-xml ---
> [INFO] F8: Running in OpenShift mode
> [INFO] F8: Using docker image name of namespace: myproject
> [INFO] F8: spring-boot: Using fat jar packaging as the spring boot plugin is using `repackage` goal execution
> [INFO] F8: Running generator spring-boot
> [INFO] F8: spring-boot: Using Docker image fabric8/s2i-java as base / builder
> [INFO] F8: Using resource templates from /home/jkopriva/fuse-on-openshift/src/main/fabric8
> 2018-09-10 14:36:03 INFO Version:30 - HV000001: Hibernate Validator 5.2.4.Final
> [INFO] F8: fmp-service: Adding a default Service with ports [8080]
> [INFO] F8: spring-boot-health-check: Adding readiness probe on port 8081, path='/health', with initial delay 10 seconds
> [INFO] F8: spring-boot-health-check: Adding liveness probe on port 8081, path='/health', with initial delay 180 seconds
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [WARNING] F8: fmp-git: No .git/config file could be found so cannot annotate kubernetes resources with git commit SHA and branch
> [INFO]
> [INFO] --- maven-compiler-plugin:3.6.0:compile (default-compile) @ camel-ose-springboot-xml ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 2 source files to /home/jkopriva/fuse-on-openshift/target/classes
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ camel-ose-springboot-xml ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory /home/jkopriva/fuse-on-openshift/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.6.0:testCompile (default-testCompile) @ camel-ose-springboot-xml ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ camel-ose-springboot-xml ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ camel-ose-springboot-xml ---
> [INFO] Building jar: /home/jkopriva/fuse-on-openshift/target/camel-ose-springboot-xml-1.0.0-SNAPSHOT.jar
> [INFO]
> [INFO] --- spring-boot-maven-plugin:1.4.1.RELEASE:repackage (default) @ camel-ose-springboot-xml ---
> [INFO]
> [INFO] >>> fabric8-maven-plugin:3.1.80.redhat-000019:build (default) > initialize @ camel-ose-springboot-xml >>>
> [INFO]
> [INFO] <<< fabric8-maven-plugin:3.1.80.redhat-000019:build (default) < initialize @ camel-ose-springboot-xml <<<
> [INFO]
> [INFO]
> [INFO] --- fabric8-maven-plugin:3.1.80.redhat-000019:build (default) @ camel-ose-springboot-xml ---
> [INFO] F8: Using OpenShift build with strategy S2I
> [INFO] F8: spring-boot: Using fat jar packaging as the spring boot plugin is using `repackage` goal execution
> [INFO] F8: Running generator spring-boot
> [INFO] F8: spring-boot: Using Docker image fabric8/s2i-java as base / builder
> [INFO] Copying files to /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/build/maven
> [INFO] Building tar: /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/tmp/docker-build.tar
> [INFO] F8: [camel-ose-springboot-xml:latest] "spring-boot": Created docker source tar /home/jkopriva/fuse-on-openshift/target/docker/camel-ose-springboot-xml/latest/tmp/docker-build.tar
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 18.250 s
> [INFO] Finished at: 2018-09-10T14:36:19+02:00
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:3.1.80.redhat-000019:build (default) on project camel-ose-springboot-xml: Execution default of goal io.fabric8:fabric8-maven-plugin:3.1.80.redhat-000019:build failed: An error has occurred. timeout: Socket closed -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
> I have also tried this project with oc cluster up(version 3.9.0) and it went without errors.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25000:
-------------------------------
Sprint: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018, devex #155 September 2018 (was: devex #138 September 2017, devex #152 July 2018, devex #153 August 2018, devex #154 September 2018)
> Server adapter: starting into debugging fails initially (succeeds on a latter try)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-25000
> URL: https://issues.jboss.org/browse/JBIDE-25000
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.9.x
>
> Attachments: failed-to-connect-v8-vm.png
>
>
> # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* based on the "nodejs-mongo-persistent" template
> # ASSERT: have a server adapter for it
> # EXEC/ASSERT: have the adapter started in non-debugging/normal mode
> # EXEC: restart the adapter debugging
> Result:
> !failed-to-connect-v8-vm.png!
> {code}
> java.io.IOException: Failed to get version
> at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207)
> at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74)
> at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
> 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.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127)
> ... 9 more
> Caused by: java.io.IOException: End of stream
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104)
> at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158)
> {code}
> ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-26230) Implement Tycho build
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26230?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26230:
-------------------------------
Sprint: devex #153 August 2018, devex #154 September 2018, devex #155 September 2018 (was: devex #153 August 2018, devex #154 September 2018)
> Implement Tycho build
> ---------------------
>
> Key: JBIDE-26230
> URL: https://issues.jboss.org/browse/JBIDE-26230
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-server-protocol
> Affects Versions: 4.9.0.AM1
> Reporter: Jeff MAURY
> Assignee: Dmitrii Bocharov
> Fix For: 4.9.x
>
>
> Switch the Maven build to Tycho for:
> * centralized management of dependencies
> * unit tests in OSGI env
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (JBIDE-26159) Server adapter: debugging is not stopped if you delete the pod
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26159?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26159:
-------------------------------
Sprint: devex #154 September 2018, devex #155 September 2018 (was: devex #154 September 2018)
> Server adapter: debugging is not stopped if you delete the pod
> --------------------------------------------------------------
>
> Key: JBIDE-26159
> URL: https://issues.jboss.org/browse/JBIDE-26159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Priority: Minor
> Labels: port_forwarding, server_adapter
> Fix For: 4.9.x
>
>
> steps:
> Screencast: https://youtu.be/XMA--S9zj6s
> # EXEC: create an application (via ex. nodejs-mongo-persistent template)
> # ASSERT: pod for service is running
> # EXEC: select pod and pick "Port Forwarding..." and start the forwarding
> # ASSERT: forwarding is running
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> # EXEC: in Explorer: select the pod for your service and pick "Delete"
> # ASSERT: pod gets deleted and recreated
> # EXEC: verify on the cmd-line that the forwarding is running
> {code}
> $ ps ax | grep oc
> 47793 ?? S 0:00.25 /Users/adietish/Downloads/oc_341 port-forward --token=XXXXX --server=https://open.paas.redhat.com --insecure-skip-tls-verify=true -n jbide25000 -p nodejs-mongo-persistent-7-rsmlr 5858:5858 8080:8080
> {code}
> Result:
> The port forwarding is still running.
> In Eclipse there's no way for you to see this since you have to select the new pod and pick "Port Forwarding..." on this new pod. It'll then tell you that the port forwarding is *NOT* running, since we're asking about port-forwarding for the new pod (not the old one that was killed).
> PS. it looks like there's a timeout somewhere, oc stops port-forwarding at some point (many minutes later) and the process disappears.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months