-
Bug
-
Resolution: Duplicate
-
Major
-
4.2.0.CR1
-
None
-
-
Workaround Exists
-
After starting and stopping port forwarding there happens something wrong with session / ssh calling. I found it in Environment variables shell after creating env. variable and clicking on Refresh button. Following error has shown in log and environment variable from table was not removed, although it should be (Refresh button update local environment variables to environment variable of an existing OpenShift application).
com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eap"
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:871)
at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:840)
at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:614)
at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: com.jcraft.jsch.JSchException: session is down
at com.jcraft.jsch.Session.openChannel(Session.java:843)
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:865)
... 6 more
- duplicates
-
JBIDE-19851 Cannot refresh environment variable(s) for an OpenShift application
- Closed
- is related to
-
JBIDE-12164 Port forwarding wizard: dialog does not detect when SSH session stops
- Closed
- relates to
-
JBIDE-16951 Update code that uses the OSJC ssh sessions to use the new ApplicationSSHSession class
- Closed