August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-822) Create a test for manipulatin with 2 routes

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-822: --------------------------------------- Summary: Create a test for manipulatin with 2 routes Key: JBTIS-822 URL: https://issues.jboss.org/browse/JBTIS-822 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-822) Create a test for manipulating with 2 routes

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-822?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-822: ------------------------------------ Summary: Create a test for manipulating with 2 routes (was: Create a test for manipulatin with 2 routes) > Create a test for manipulating with 2 routes > -------------------------------------------- > > Key: JBTIS-822 > URL: https://issues.jboss.org/browse/JBTIS-822 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22818) vagrant service-manager call experiences timeout after output

by Navid Shaikh (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22818?page=com.atlassian.jira.plugi... ] Navid Shaikh commented on JBIDE-22818: -------------------------------------- [~rob.stryker]: is there any more update on the bug ? To test if the the issue is from vagrant-service-manager side, can you please tell the environment details to reproduce the issue ? > vagrant service-manager call experiences timeout after output > -------------------------------------------------------------- > > Key: JBIDE-22818 > URL: https://issues.jboss.org/browse/JBIDE-22818 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.1.AM2 > Reporter: Rob Stryker > > {noformat} > !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:48:26.869 > !MESSAGE Unable to successfully complete a call to vagrant service-manager. > !STACK 0 > java.util.concurrent.TimeoutException: Process output: > ^[[0m # docker env:^[[0m # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # run following command to configure your shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:185) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:174) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:154) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:133) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:250) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:242) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:235) > !ENTRY org.jboss.tools.openshift.cdk.server 4 0 2016-07-21 09:49:07.139 > !MESSAGE Unable to successfully complete a call to vagrant service-manager. > !STACK 0 > java.util.concurrent.TimeoutException: Process output: > ^[[0m # docker env:^[[0m # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.1.2.2:2376 export DOCKER_CERT_PATH='C:\Pedro\Software\Openshift_RHCDK_suite10\cdk\components\rhel\rhel-ose\.vagrant\machines\default\virtualbox\docker\' export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.21 ^[[0m^[[0m ^[[0m # openshift env:^[[0m ^[[0m# You can access the OpenShift console on: https://10.1.2.2:8443/console # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 export OPENSHIFT_URL=https://10.1.2.2:8443 export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io^[[0m ^[[0m # run following command to configure your shell: # eval "$(VAGRANT_NO_COLOR=1 vagrant service-manager env | tr -d '\r')"^[[0m > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:186) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.call(VagrantLaunchUtility.java:153) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:108) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.loadServiceManagerEnvironment(ServiceManagerEnvironment.java:85) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:67) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ServiceManagerEnvironment.getOrLoadServiceManagerEnvironment(ServiceManagerEnvironment.java:59) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:53) > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:43) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21857: ------------------------------------- Priority: Major (was: Blocker) > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.x > > Attachments: HCRFailure.zip > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22869) Server adapter: Publishing code changes (via rsync) is buggy

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22869?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22869: ------------------------------------- Description: Across the platform we have quite a few serious issues when publishing code via the server editor. This shows us that_ - we don't test well enough - we lack time > Server adapter: Publishing code changes (via rsync) is buggy > ------------------------------------------------------------ > > Key: JBIDE-22869 > URL: https://issues.jboss.org/browse/JBIDE-22869 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Fix For: 4.4.1.AM3 > > > Across the platform we have quite a few serious issues when publishing code via the server editor. This shows us that_ > - we don't test well enough > - we lack time -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22869) Server adapter: Publishing code changes (via rsync) is buggy

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-22869: ---------------------------------------- Summary: Server adapter: Publishing code changes (via rsync) is buggy Key: JBIDE-22869 URL: https://issues.jboss.org/browse/JBIDE-22869 Project: Tools (JBoss Tools) Issue Type: Epic Components: openshift Affects Versions: 4.4.1.AM2 Reporter: Andre Dietisheim Fix For: 4.4.1.AM3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22653 at 8/2/16 8:33 AM: ------------------------------------------------------------------ [~fbricon] [~jeffmaury] I cant replicate this. I can scale down to 0 and back again to some other number. I see in both cases the pods being terminated & removed and relaunched again. The only missing piece I can spot is that the refresh wont happen automatically. If you refresh manually you see the changes happening: https://youtu.be/RGiibHCgaeA The other part we're missing is the warning like in Web-UI was (Author: adietish): [~fbricon] [~jeffmaury] I cant replicate this. I can scale down to 0 and back again to some other number. I see in both cases the pods being terminated & removed and relaunched again. The only missing piece I can spot is that the refresh wont happen automatically. If you refresh manually you see the changes happening: https://youtu.be/RGiibHCgaeA > Can't scale pods down to 0 > -------------------------- > > Key: JBIDE-22653 > URL: https://issues.jboss.org/browse/JBIDE-22653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > > The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. > The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." > My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22653: ------------------------------------------ [~jeffmaury] thx for confirming. Very possible that the missing refresh is JBIDE-22861 > Can't scale pods down to 0 > -------------------------- > > Key: JBIDE-22653 > URL: https://issues.jboss.org/browse/JBIDE-22653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > > The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. > The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." > My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22653) Can't scale pods down to 0

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22653?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22653: ------------------------------------ Agree works on my conf. For the update you are perhaps hitting JBIDE-22861 > Can't scale pods down to 0 > -------------------------- > > Key: JBIDE-22653 > URL: https://issues.jboss.org/browse/JBIDE-22653 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > > The scale to... menu lets you scale to any number of replicas, but you can't go down to 0. > The webconsoles allows it, albeit with a big warning: "Are you sure you want to scale deploymentname to 0 replicas? This will stop all pods for the deployment." > My take is we should have the same behavior in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22711) NoSuchMethodError in GettingStartedHtmlPage.resetWizards

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22711?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22711. --------------------------------- Closing. AERI problem should be reopened automatically if this keeps occurring in future versions. > NoSuchMethodError in GettingStartedHtmlPage.resetWizards > -------------------------------------------------------- > > Key: JBIDE-22711 > URL: https://issues.jboss.org/browse/JBIDE-22711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Fred Bricon > Fix For: 4.4.1.AM2 > > > The following problem was reported via the automated error reporting: > Message: An internal error occurred during: "Update project wizard list". > {noformat} > java.lang.NoSuchMethodError: org.jboss.tools.discovery.core.internal.connectors.JBossDiscoveryUi.isEarlyAccessEnabled()Z > at org.jboss.tools.central.editors.GettingStartedHtmlPage.resetWizards(GettingStartedHtmlPage.java:470) > at org.jboss.tools.central.editors.GettingStartedHtmlPage.onProxyWizardUpdate(GettingStartedHtmlPage.java:484) > at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.notifyListeners(ProxyWizardManager.java:276) > at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:116) > at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:45) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 | > | org.jboss.tools.central | 2.0.1.Final-v20160401-1059-B103 | 2.0.1.Final-v20160401-1059-B103 | > Operating Systems: > | Windows | 6.1.0 | 6.1.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/574da4fee4b06056d2...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2016