[JBoss JIRA] (JBIDE-19843) Missing org.eclipse.jetty.client: - Cannot install JBT Apache Cordova Simulator & FH Integration
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19843?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19843:
---------------------------------------------
scratch that - missed the last paragraph.
Yes, our nightly updatesite url should point to something as close to most likely working rather than point to previously released parts.
I still find it weird why central now suddenly is the "root" of everything, seems backwards, but that is separate discussion.
Yes, for sure our nightly updatesites should be something that actually works and use the latest that our nightly builds actually rely on.
> Missing org.eclipse.jetty.client: - Cannot install JBT Apache Cordova Simulator & FH Integration
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19843
> URL: https://issues.jboss.org/browse/JBIDE-19843
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, updatesite
> Affects Versions: 4.3.0.Beta1
> Environment: eclipse-mars-M7
> JBT nigtly from 2015-05-24
> Reporter: Pavol Srna
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Tools Apache Cordova Simulator 3.7.0.Beta1-v20150507-2109-B442 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.Beta1-v20150507-2109-B442)
> Missing requirement: Eclipse integrations of BrowserSim 3.7.0.Beta1-v20150507-2109-B442 (org.jboss.tools.cordovasim.eclipse 3.7.0.Beta1-v20150507-2109-B442) requires 'bundle org.eclipse.jetty.client [9.0.0,10.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: JBoss Tools Apache Cordova Simulator 3.7.0.Beta1-v20150507-2109-B442 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.Beta1-v20150507-2109-B442)
> To: org.jboss.tools.cordovasim.eclipse [3.7.0.Beta1-v20150507-2109-B442]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19843) Missing org.eclipse.jetty.client: - Cannot install JBT Apache Cordova Simulator & FH Integration
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19843?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19843:
---------------------------------------------
[~nickboldt] we have this case every new milestone.
Why can we not provide a nightly updatesite that actually point to working bits out of the box ?
> Missing org.eclipse.jetty.client: - Cannot install JBT Apache Cordova Simulator & FH Integration
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19843
> URL: https://issues.jboss.org/browse/JBIDE-19843
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, updatesite
> Affects Versions: 4.3.0.Beta1
> Environment: eclipse-mars-M7
> JBT nigtly from 2015-05-24
> Reporter: Pavol Srna
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Tools Apache Cordova Simulator 3.7.0.Beta1-v20150507-2109-B442 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.Beta1-v20150507-2109-B442)
> Missing requirement: Eclipse integrations of BrowserSim 3.7.0.Beta1-v20150507-2109-B442 (org.jboss.tools.cordovasim.eclipse 3.7.0.Beta1-v20150507-2109-B442) requires 'bundle org.eclipse.jetty.client [9.0.0,10.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: JBoss Tools Apache Cordova Simulator 3.7.0.Beta1-v20150507-2109-B442 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.Beta1-v20150507-2109-B442)
> To: org.jboss.tools.cordovasim.eclipse [3.7.0.Beta1-v20150507-2109-B442]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19835) 'JPA Tools -> Generate Tables from Entities' does not work for Hibernate 4.0
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19835?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19835:
------------------------------
Description:
This issue is a result of further investigation of JBIDE-19431 and JBIDE-19535. This investigation showed me that the generation of DDL works fine (wether a defined console configuration is used or not) unless version 4.0 of Hibernate is used.
So for JPA 2.0 (which uses Hibernate 4.0 under the covers) the DDL generation does not work if the console configuration is used, nor when the use of a console configuration is disabled and Hibernate 4.0 is selected in the DDL generation dialog. It works however for Hibernate 3.5, 3.6 and 4.3.
For a JPA 1.0 project, DDL generation works with the console configuration and when console configuration is disabled and Hibernate 3.5, 3.6 or 4.3 are selected in the DDL generation dialog.
For JPA 2.1, only Hibernate 4.3 is a compatible Hibernate version and DDL generation works in this case both with and without using the console configuration.
was:
This issue is a result of further investigation of JBIDE-19431. This investigation showed me that the generation of DDL works fine (wether a defined console configuration is used or not) unless version 4.0 of Hibernate is used.
So for JPA 2.0 (which uses Hibernate 4.0 under the covers) the DDL generation does not work if the console configuration is used, nor when the use of a console configuration is disabled and Hibernate 4.0 is selected in the DDL generation dialog. It works however for Hibernate 3.5, 3.6 and 4.3.
For a JPA 1.0 project, DDL generation works with the console configuration and when console configuration is disabled and Hibernate 3.5, 3.6 or 4.3 are selected in the DDL generation dialog.
For JPA 2.1, only Hibernate 4.3 is a compatible Hibernate version and DDL generation works in this case both with and without using the console configuration.
> 'JPA Tools -> Generate Tables from Entities' does not work for Hibernate 4.0
> ----------------------------------------------------------------------------
>
> Key: JBIDE-19835
> URL: https://issues.jboss.org/browse/JBIDE-19835
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: Koen Aers
> Assignee: Koen Aers
>
> This issue is a result of further investigation of JBIDE-19431 and JBIDE-19535. This investigation showed me that the generation of DDL works fine (wether a defined console configuration is used or not) unless version 4.0 of Hibernate is used.
> So for JPA 2.0 (which uses Hibernate 4.0 under the covers) the DDL generation does not work if the console configuration is used, nor when the use of a console configuration is disabled and Hibernate 4.0 is selected in the DDL generation dialog. It works however for Hibernate 3.5, 3.6 and 4.3.
> For a JPA 1.0 project, DDL generation works with the console configuration and when console configuration is disabled and Hibernate 3.5, 3.6 or 4.3 are selected in the DDL generation dialog.
> For JPA 2.1, only Hibernate 4.3 is a compatible Hibernate version and DDL generation works in this case both with and without using the console configuration.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable(s) for an OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19851?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-19851:
----------------------------------
Steps to Reproduce:
ASSERT: Have an OpenShift application
EXEC: Start and stop port forwarding on the application.
EXEC: Open Manage env. vars dialog
EXEC: Hit Refresh button
RESULT: Error dialog is shown and there is error in log.
EXPECTED RESULT: Environment variables are refreshed successfully.
> Cannot refresh environment variable(s) for an OpenShift application
> -------------------------------------------------------------------
>
> Key: JBIDE-19851
> URL: https://issues.jboss.org/browse/JBIDE-19851
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: environment_variables
>
> In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
> {code}
> com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
> at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
> at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
> 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.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.jcraft.jsch.JSchException: session is down
> at com.jcraft.jsch.Session.openChannel(Session.java:844)
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
> ... 6 more
> {code}
> Otherwise adding, editing and removing environment variables work OK.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable(s) for an OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19851?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-19851:
----------------------------------
Description:
In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
{code}
com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
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.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.jcraft.jsch.JSchException: session is down
at com.jcraft.jsch.Session.openChannel(Session.java:844)
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
... 6 more
{code}
Otherwise adding, editing and removing environment variables work OK.
was:
In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
{code}
com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
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.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.jcraft.jsch.JSchException: session is down
at com.jcraft.jsch.Session.openChannel(Session.java:844)
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
... 6 more
{code}
Otherwise adding, editing and removing environment variables work OK.
This is happening only some times. I have created EAP application where this is happening. Looking for a way to reproduce it with 100 % chance.
> Cannot refresh environment variable(s) for an OpenShift application
> -------------------------------------------------------------------
>
> Key: JBIDE-19851
> URL: https://issues.jboss.org/browse/JBIDE-19851
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: environment_variables
>
> In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
> {code}
> com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
> at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
> at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
> 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.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.jcraft.jsch.JSchException: session is down
> at com.jcraft.jsch.Session.openChannel(Session.java:844)
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
> ... 6 more
> {code}
> Otherwise adding, editing and removing environment variables work OK.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19574) Add API so that downloaded runtimes can be installed via java -jar command
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19574?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-19574.
------------------------------
Verified in JBT 4.3.0.Alpha2. I saw some usability issues and I've created new jira for that: https://issues.jboss.org/browse/JBIDE-19852
> Add API so that downloaded runtimes can be installed via java -jar command
> --------------------------------------------------------------------------
>
> Key: JBIDE-19574
> URL: https://issues.jboss.org/browse/JBIDE-19574
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: runtime-detection, server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: need-info
> Fix For: 4.3.0.Alpha2
>
>
> Runtime detection currently supports only 'extraction' as a method of installation. It was recently expanded to include not just unzipping of jars, but also extracting .tar.gz files / .tar files / etc. But there's still no API for completely alternate methods of installation.
> This JIRA should add an extension point for (basically the plumbing) to allow for alternate installation types in general, as well as add a default java -jar installation method as well.
> It will be up to other runtimes (ie teiid etc) to USE this functionality in their own products, but it is up to jbt-base to make sure it is feasible at the API level.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19852) Set default path for runtimes downloaded and installed via java -jar
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-19852:
----------------------------------
Summary: Set default path for runtimes downloaded and installed via java -jar
Key: JBIDE-19852
URL: https://issues.jboss.org/browse/JBIDE-19852
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: runtime-detection, server
Affects Versions: 4.3.0.Alpha2
Reporter: Radim Hopp
I'm not sure if this is possible, but it would be nice if the installer would fill the installation path from Download Runtime wizard.
The same for runtime detection after the download and installation is finished.
Example scenario:
1. Select JBoss DV 6.1 for download&installation
2. On "Download Runtime" page of wizard fill some install folder (for example /home/<user>/downloadedDV)
3. Click Finish - DV is downloaded and it's installer executed
ASSERT: /home/<user>/downloadedDV is default installation path in installer
4. In the installer select different installation folder (for example /home/<user>/DV)
5. Finish installer
ASSERT: /home/<user>/DV is added to runtime-detection paths instead of /home/<user>/downloadedDV
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable(s) for an OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19851?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-19851:
----------------------------------
Description:
In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
{code}
com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
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.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.jcraft.jsch.JSchException: session is down
at com.jcraft.jsch.Session.openChannel(Session.java:844)
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
... 6 more
{code}
Otherwise adding, editing and removing environment variables work OK.
This is happening only some times. I have created EAP application where this is happening. Looking for a way to reproduce it with 100 % chance.
was:
In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
{code}
com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
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.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.jcraft.jsch.JSchException: session is down
at com.jcraft.jsch.Session.openChannel(Session.java:844)
at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
... 6 more
{code}
Otherwise adding, editing and removing environment variables work OK.
This is happening only some times. I have created EAP application where this is happening.
> Cannot refresh environment variable(s) for an OpenShift application
> -------------------------------------------------------------------
>
> Key: JBIDE-19851
> URL: https://issues.jboss.org/browse/JBIDE-19851
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: environment_variables
>
> In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
> {code}
> com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
> at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
> at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
> 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.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.jcraft.jsch.JSchException: session is down
> at com.jcraft.jsch.Session.openChannel(Session.java:844)
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
> ... 6 more
> {code}
> Otherwise adding, editing and removing environment variables work OK.
> This is happening only some times. I have created EAP application where this is happening. Looking for a way to reproduce it with 100 % chance.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19851) Cannot refresh environment variable(s) for an OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19851?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-19851:
----------------------------------
Priority: Minor (was: Major)
> Cannot refresh environment variable(s) for an OpenShift application
> -------------------------------------------------------------------
>
> Key: JBIDE-19851
> URL: https://issues.jboss.org/browse/JBIDE-19851
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: environment_variables
>
> In Manage Application Environment Variable shell opened either via servers adapter or OpenShift Explorer view are listed environment variables for a specific application. Refresh button should refresh state of variables according to state on a server, but click on Refresh button shows following error dialog with following stack in log:
> {code}
> com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eapapp"
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:892)
> at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:860)
> at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:634)
> 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.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.jcraft.jsch.JSchException: session is down
> at com.jcraft.jsch.Session.openChannel(Session.java:844)
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:885)
> ... 6 more
> {code}
> Otherwise adding, editing and removing environment variables work OK.
> This is happening only some times. I have created EAP application where this is happening.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months