June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22650) When starting an OS3 server adapter from scratch, error is reported although connection can be established

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22650?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22650: ------------------------------- Description: ASSERT: create an OS3 connection without password saved ASSERT: create an OS3 server adapter EXEC: restart Eclipse EXEC: start the OS3 server adapter and give correct password ASSERT: error is reported [^screenshot-1.png] was: ASSERT: create an OS3 connection without password saved ASSERT: create an OS3 server adapter EXEC: restart Eclipse EXEC: start the OS3 server adapter and give correct password ASSERT: error is reported > When starting an OS3 server adapter from scratch, error is reported although connection can be established > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22650 > URL: https://issues.jboss.org/browse/JBIDE-22650 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Fix For: 4.4.1.M2 > > Attachments: screenshot-1.png > > > ASSERT: create an OS3 connection without password saved > ASSERT: create an OS3 server adapter > EXEC: restart Eclipse > EXEC: start the OS3 server adapter and give correct password > ASSERT: error is reported [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22603: --------------------------------------- Ok, finally there is a nightly build with JBIDE-21828 applied, but it does not resolve this problem. I still see it happening. Filled in steps to reproduce. > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Priority: Critical > Labels: explorer, openshift_v3 > Attachments: watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22603: ---------------------------------- Steps to Reproduce: ASSERT: Have running CDK (I am using CDK 2.1 with virtualbox box on Fedora 22, Vagrant version 1.7.2) *This is mandatory, because it is not happening when using remote OS3 server* EXEC: Create a new connection to CDK OpenShift (openshift-dev username). EXEC: Create a project under the connection (it's enough to have just project, no resources are necessary). RESULT: There is plenty of OpenShift WatchManager jobs periodically created, running and getting finished. EXPECTED RESULT: There are OpenShift WatchManager jobs spawned and finished. > Sometimes multiple OpenShift watch managers are periodically created and finished > --------------------------------------------------------------------------------- > > Key: JBIDE-22603 > URL: https://issues.jboss.org/browse/JBIDE-22603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Priority: Critical > Labels: explorer, openshift_v3 > Attachments: watchers.png > > > Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template. > !watchers.png! > It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22649) When importing an OS2 app, the Git import does not use the default import folder used while importing OS3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22649?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22649: ---------------------------------- Assignee: Jeff MAURY > When importing an OS2 app, the Git import does not use the default import folder used while importing OS3 > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22649 > URL: https://issues.jboss.org/browse/JBIDE-22649 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.4.1.M2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22649) When importing an OS2 app, the Git import does not use the default import folder used while importing OS3

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-22649: ---------------------------------- Summary: When importing an OS2 app, the Git import does not use the default import folder used while importing OS3 Key: JBIDE-22649 URL: https://issues.jboss.org/browse/JBIDE-22649 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Final Reporter: Jeff MAURY Fix For: 4.4.1.M2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22648) RSE launches stick around in debug view forever

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22648?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22648: -------------------------------- Story Points: 6 Sprint: devex #116 June 2016 > RSE launches stick around in debug view forever > ----------------------------------------------- > > Key: JBIDE-22648 > URL: https://issues.jboss.org/browse/JBIDE-22648 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.M1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.M1 > > > When launching remote rse wildfly / eap / etc, launches get stuck and left behind, never cleaned up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22648) RSE launches stick around in debug view forever

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-22648: ----------------------------------- Summary: RSE launches stick around in debug view forever Key: JBIDE-22648 URL: https://issues.jboss.org/browse/JBIDE-22648 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Affects Versions: 4.4.1.M1 Reporter: Rob Stryker When launching remote rse wildfly / eap / etc, launches get stuck and left behind, never cleaned up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22648) RSE launches stick around in debug view forever

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22648?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-22648: ----------------------------------- Assignee: Rob Stryker > RSE launches stick around in debug view forever > ----------------------------------------------- > > Key: JBIDE-22648 > URL: https://issues.jboss.org/browse/JBIDE-22648 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.M1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.M1 > > > When launching remote rse wildfly / eap / etc, launches get stuck and left behind, never cleaned up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22648) RSE launches stick around in debug view forever

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22648?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22648: -------------------------------- Fix Version/s: 4.4.1.M1 > RSE launches stick around in debug view forever > ----------------------------------------------- > > Key: JBIDE-22648 > URL: https://issues.jboss.org/browse/JBIDE-22648 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.M1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.M1 > > > When launching remote rse wildfly / eap / etc, launches get stuck and left behind, never cleaned up. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-795) JBDSIS 9.0.0 beta1 / Early Access is giving an Id to Camel routes by default

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBTIS-795?page=com.atlassian.jira.plugin.... ] Lars Heinemann commented on JBTIS-795: -------------------------------------- It is in the camel editor. We now set ID values if they are missing. That is wanted behaviour from our side. I can't say more about the performance issue. Aurelien has done some improvements here lately so this might be already solved in the latest codebase. > JBDSIS 9.0.0 beta1 / Early Access is giving an Id to Camel routes by default > ---------------------------------------------------------------------------- > > Key: JBTIS-795 > URL: https://issues.jboss.org/browse/JBTIS-795 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE > Affects Versions: 9.0.0.Beta1 > Environment: JBDS 9.1 with devstudio-integration-stack-9.0.0.Beta1-earlyaccess.zip > Reporter: Rick Wagner > > A user has noted that Camel routes used in SwitchYard are now being given an Id without user input. This is a changed behavior. > The same user complains of very slow loading of SwitchYard/Camel component routes, but this is still under investigation in the cited support ticket. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 June 2016