June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22612) Explorer: OpenShift v3 connections are missing from the explorer on startup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22612?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22612: ------------------------------------- Labels: explorer openshift_v3 (was: ) > Explorer: OpenShift v3 connections are missing from the explorer on startup > --------------------------------------------------------------------------- > > Key: JBIDE-22612 > URL: https://issues.jboss.org/browse/JBIDE-22612 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Alpha1 > Reporter: Fred Bricon > Labels: explorer, openshift_v3 > Fix For: 4.4.1.Alpha1 > > > After applying the fix for JBIDE-21828, it appears that, on workspace restart, the OpenShift 3 connections are missing from the OpenShift Explorer. > This is caused by the OpenShift 3 core plugin not being started when the OpenShiftExplorerContentProvider is called. As a consequence, no connections are loaded. > Before JBIDE-21828, [getExplorerElements|https://github.com/jbosstools/jbosstools-openshift/co...] would return all the OpenShift3 connections. With the new code, the UI Model is expected to be already loaded -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22612) Explorer: OpenShift v3 connections are missing from the explorer on startup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22612?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22612: ------------------------------------- Fix Version/s: 4.4.1.Alpha1 > Explorer: OpenShift v3 connections are missing from the explorer on startup > --------------------------------------------------------------------------- > > Key: JBIDE-22612 > URL: https://issues.jboss.org/browse/JBIDE-22612 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Alpha1 > Reporter: Fred Bricon > Labels: explorer, openshift_v3 > Fix For: 4.4.1.Alpha1 > > > After applying the fix for JBIDE-21828, it appears that, on workspace restart, the OpenShift 3 connections are missing from the OpenShift Explorer. > This is caused by the OpenShift 3 core plugin not being started when the OpenShiftExplorerContentProvider is called. As a consequence, no connections are loaded. > Before JBIDE-21828, [getExplorerElements|https://github.com/jbosstools/jbosstools-openshift/co...] would return all the OpenShift3 connections. With the new code, the UI Model is expected to be already loaded -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22612) Explorer: OpenShift v3 connections are missing from the explorer on startup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22612?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22612: ------------------------------------- Summary: Explorer: OpenShift v3 connections are missing from the explorer on startup (was: OpenShift connections are missing from the explorer on startup) > Explorer: OpenShift v3 connections are missing from the explorer on startup > --------------------------------------------------------------------------- > > Key: JBIDE-22612 > URL: https://issues.jboss.org/browse/JBIDE-22612 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Alpha1 > Reporter: Fred Bricon > > After applying the fix for JBIDE-21828, it appears that, on workspace restart, the OpenShift 3 connections are missing from the OpenShift Explorer. > This is caused by the OpenShift 3 core plugin not being started when the OpenShiftExplorerContentProvider is called. As a consequence, no connections are loaded. > Before JBIDE-21828, [getExplorerElements|https://github.com/jbosstools/jbosstools-openshift/co...] would return all the OpenShift3 connections. With the new code, the UI Model is expected to be already loaded -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3953) JBoss Studio Developer crash at startup on Fedora 24

by Donato Marrazzo (JIRA)

[ https://issues.jboss.org/browse/JBDS-3953?page=com.atlassian.jira.plugin.... ] Donato Marrazzo edited comment on JBDS-3953 at 6/17/16 5:07 AM: ---------------------------------------------------------------- Using just SWT_WEBKIT2=1 works around the problem of crashing at the start up. Thank you! As side effect the Red Hat Central / Getting Started view does not work. !Selection_003.png|thumbnail! was (Author: dmarrazzo): Using just SWT_WEBKIT2=1 works around the problem of crashing at the start up. Thank you! As side effect the Red Hat Central / Getting Started view does not work. > JBoss Studio Developer crash at startup on Fedora 24 > ---------------------------------------------------- > > Key: JBDS-3953 > URL: https://issues.jboss.org/browse/JBDS-3953 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 9.1.0.GA > Environment: Fedora 24 > openjdk full version "1.8.0_92-b14" > Reporter: Donato Marrazzo > Assignee: Snjezana Peco > Priority: Critical > Fix For: 10.x > > Attachments: hs_err_pid12689.log, hs_err_pid3836.log.zip, Selection_003.png > > > After installation, as I launch JBS, it just display the eclipse workbench for few second that it crash. > Despite the console message, no core dump is generated. > This is the cmd line output: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in [bundleresource://1072.fwk923366543:1/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in [bundleresource://1072.fwk923366543:2/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. > SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder] > 14:09:55.604 [Worker-2] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh request: [/RemoteSystemsTempFiles/pom.xml] > openjdk version "1.8.0_92" > OpenJDK Runtime Environment (build 1.8.0_92-b14) > OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode) > 14:09:57.115 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.142 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.143 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: [L/RemoteSystemsTempFiles/pom.xml] > 14:09:57.156 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: [L/RemoteSystemsTempFiles/pom.xml] > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007f521a6d7bfe, pid=12689, tid=0x00007f52cf5a3700 > # > # JRE version: OpenJDK Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14) > # Java VM: OpenJDK 64-Bit Server VM (25.92-b14 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [libjavascriptcoregtk-3.0.so.0+0x4d4bfe] JSC::VM::throwException(JSC::ExecState*, JSC::JSValue)+0x236e > # > # Core dump written. Default location: /home/donato/core or core.12689 > # > # An error report file with more information is saved as: > # /home/donato/hs_err_pid12689.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.java.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3953) JBoss Studio Developer crash at startup on Fedora 24

by Donato Marrazzo (JIRA)

[ https://issues.jboss.org/browse/JBDS-3953?page=com.atlassian.jira.plugin.... ] Donato Marrazzo updated JBDS-3953: ---------------------------------- Attachment: Selection_003.png > JBoss Studio Developer crash at startup on Fedora 24 > ---------------------------------------------------- > > Key: JBDS-3953 > URL: https://issues.jboss.org/browse/JBDS-3953 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 9.1.0.GA > Environment: Fedora 24 > openjdk full version "1.8.0_92-b14" > Reporter: Donato Marrazzo > Assignee: Snjezana Peco > Priority: Critical > Fix For: 10.x > > Attachments: hs_err_pid12689.log, hs_err_pid3836.log.zip, Selection_003.png > > > After installation, as I launch JBS, it just display the eclipse workbench for few second that it crash. > Despite the console message, no core dump is generated. > This is the cmd line output: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in [bundleresource://1072.fwk923366543:1/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in [bundleresource://1072.fwk923366543:2/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. > SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder] > 14:09:55.604 [Worker-2] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh request: [/RemoteSystemsTempFiles/pom.xml] > openjdk version "1.8.0_92" > OpenJDK Runtime Environment (build 1.8.0_92-b14) > OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode) > 14:09:57.115 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.142 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.143 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: [L/RemoteSystemsTempFiles/pom.xml] > 14:09:57.156 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: [L/RemoteSystemsTempFiles/pom.xml] > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007f521a6d7bfe, pid=12689, tid=0x00007f52cf5a3700 > # > # JRE version: OpenJDK Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14) > # Java VM: OpenJDK 64-Bit Server VM (25.92-b14 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [libjavascriptcoregtk-3.0.so.0+0x4d4bfe] JSC::VM::throwException(JSC::ExecState*, JSC::JSValue)+0x236e > # > # Core dump written. Default location: /home/donato/core or core.12689 > # > # An error report file with more information is saved as: > # /home/donato/hs_err_pid12689.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.java.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3953) JBoss Studio Developer crash at startup on Fedora 24

by Donato Marrazzo (JIRA)

[ https://issues.jboss.org/browse/JBDS-3953?page=com.atlassian.jira.plugin.... ] Donato Marrazzo commented on JBDS-3953: --------------------------------------- Using just SWT_WEBKIT2=1 works around the problem of crashing at the start up. Thank you! As side effect the Red Hat Central / Getting Started view does not work. > JBoss Studio Developer crash at startup on Fedora 24 > ---------------------------------------------------- > > Key: JBDS-3953 > URL: https://issues.jboss.org/browse/JBDS-3953 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 9.1.0.GA > Environment: Fedora 24 > openjdk full version "1.8.0_92-b14" > Reporter: Donato Marrazzo > Assignee: Snjezana Peco > Priority: Critical > Fix For: 10.x > > Attachments: hs_err_pid12689.log, hs_err_pid3836.log.zip > > > After installation, as I launch JBS, it just display the eclipse workbench for few second that it crash. > Despite the console message, no core dump is generated. > This is the cmd line output: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in [bundleresource://1072.fwk923366543:1/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in [bundleresource://1072.fwk923366543:2/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. > SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder] > 14:09:55.604 [Worker-2] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh request: [/RemoteSystemsTempFiles/pom.xml] > openjdk version "1.8.0_92" > OpenJDK Runtime Environment (build 1.8.0_92-b14) > OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode) > 14:09:57.115 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.142 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.143 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: [L/RemoteSystemsTempFiles/pom.xml] > 14:09:57.156 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: [L/RemoteSystemsTempFiles/pom.xml] > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007f521a6d7bfe, pid=12689, tid=0x00007f52cf5a3700 > # > # JRE version: OpenJDK Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14) > # Java VM: OpenJDK 64-Bit Server VM (25.92-b14 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [libjavascriptcoregtk-3.0.so.0+0x4d4bfe] JSC::VM::throwException(JSC::ExecState*, JSC::JSValue)+0x236e > # > # Core dump written. Default location: /home/donato/core or core.12689 > # > # An error report file with more information is saved as: > # /home/donato/hs_err_pid12689.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.java.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-22613: ---------------------------------- Summary: When a connection is configured with a stored token, switching back with basic will fail if token is invalid Key: JBIDE-22613 URL: https://issues.jboss.org/browse/JBIDE-22613 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Final Reporter: Jeff MAURY Fix For: 4.4.x If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22604) CDK server adapter stuck at starting

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22604?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22604: --------------------------------------- I just noticed that the RC4 update to vagrant-sshfs plugin (version bump to 1.1.1) was reverted in RC5. So now all platforms are equal - sshfs setup (now in separate Vagrantfile) won't work in devstudio on any platform. > CDK server adapter stuck at starting > ------------------------------------ > > Key: JBIDE-22604 > URL: https://issues.jboss.org/browse/JBIDE-22604 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.0.Final > Environment: development-suite-1.0.0-GA-20160615-188-bundle-installer.exe > devstudio 10.0.0.GA-a > CDK 2.1.RC3 > Reporter: Jan Richter > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > I have installed the development suite using the all-in-1 installer (on 3 different windows machines now). Every time I try to start CDK using the server adapter it gets stuck on 'starting'. > In fact the CDK does start up, openshift is running, but no connection is created + the server adapter is marked as starting and the job (starting CDK) is spinning until it hits the timeout. > Strange thing is - stopping the job/server adapter at this point will first create the desired openshift connection and then CDK wil stop. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-633) Add tests for global elements in Camel Editor

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-633?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-633: ------------------------------------ Affects Version/s: 4.3.0.Final (was: 4.0.0) > Add tests for global elements in Camel Editor > --------------------------------------------- > > Key: JBTIS-633 > URL: https://issues.jboss.org/browse/JBTIS-633 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Dominik Jelinek > Fix For: 4.3.0.Final > > Original Estimate: 2 days > Time Spent: 5 hours > Remaining Estimate: 1 day, 3 hours > > Tab _Configurations_ in the Camel Editor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-754) Fuse: Adapt tests for 'New Fuse Integration Project' wizard

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-754?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-754. ----------------------------------- pushed to master > Fuse: Adapt tests for 'New Fuse Integration Project' wizard > ----------------------------------------------------------- > > Key: JBTIS-754 > URL: https://issues.jboss.org/browse/JBTIS-754 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Blocker > Fix For: 4.3.1.Final > > > SSIA -- 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