June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4180) ClassNotFoundException thrown on devstudio start up

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4180?page=com.atlassian.jira.plugin.... ] Rob Stryker resolved JBDS-4180. ------------------------------- Resolution: Out of Date All indications point to a broken openjdk build or similar. > ClassNotFoundException thrown on devstudio start up > --------------------------------------------------- > > Key: JBDS-4180 > URL: https://issues.jboss.org/browse/JBDS-4180 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: foundation, upstream > Affects Versions: 10.2.0.GA > Environment: Fedora 24, > openjdk version "1.8.0_102" > OpenJDK Runtime Environment (build 1.8.0_102-b14) > Reporter: Marián Labuda > Assignee: Rob Stryker > Fix For: 11.0.0.AM1 > > > When starting latest DevStudio 10.2.0.GA (build ID GA-v20161116-0039-B6472) I get following error in console output > {code} > SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder] > Noop constructor > java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.validateClassPathAndLibraryPath(Tools.java:365) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:115) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeActiveVms(Tools.java:525) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > {code} > problem is with openjdk version. With the lates 1.8.0_111 it works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4180) ClassNotFoundException thrown on devstudio start up

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4180?page=com.atlassian.jira.plugin.... ] Rob Stryker updated JBDS-4180: ------------------------------ Fix Version/s: 11.0.0.AM1 (was: 10.x) > ClassNotFoundException thrown on devstudio start up > --------------------------------------------------- > > Key: JBDS-4180 > URL: https://issues.jboss.org/browse/JBDS-4180 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: foundation, upstream > Affects Versions: 10.2.0.GA > Environment: Fedora 24, > openjdk version "1.8.0_102" > OpenJDK Runtime Environment (build 1.8.0_102-b14) > Reporter: Marián Labuda > Assignee: Rob Stryker > Fix For: 11.0.0.AM1 > > > When starting latest DevStudio 10.2.0.GA (build ID GA-v20161116-0039-B6472) I get following error in console output > {code} > SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder] > Noop constructor > java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.validateClassPathAndLibraryPath(Tools.java:365) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:115) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513) > at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeActiveVms(Tools.java:525) > at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100) > at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > {code} > problem is with openjdk version. With the lates 1.8.0_111 it works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4179) DevStudio installer uses console installation instead of wizard

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ] Rob Stryker resolved JBDS-4179. ------------------------------- Resolution: Unresolved I'm closing this to help clean up jira. It seems it was either a specific build that was broken, or that users were using a headless jdk. QE: please test with a newer version to verify. > DevStudio installer uses console installation instead of wizard > --------------------------------------------------------------- > > Key: JBDS-4179 > URL: https://issues.jboss.org/browse/JBDS-4179 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: documentation, installer, upstream > Affects Versions: 10.2.0.GA > Environment: openjdk version "1.8.0_102" > OpenJDK Runtime Environment (build 1.8.0_102-b14) > Reporter: Marián Labuda > Assignee: Denis Golovin > Fix For: 11.0.0.AM1 > > > I tried to install latest DevStudio (devstudio-10.2.0.GA-v20161116-0039-B6472-installer-standalone.jar) but when I run installation as usual, I get console installation - at first whole license text and prompt to 1) Accept, 2) Reject, 3) Redisplay. After that installation unpack files to home and I am not able to select destination. > This happens with older version of openjdk8. With latest available openjdk for fedora (1.8.0_111) it works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4179) DevStudio installer uses console installation instead of wizard

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ] Rob Stryker updated JBDS-4179: ------------------------------ Fix Version/s: 11.0.0.AM1 (was: 10.x) > DevStudio installer uses console installation instead of wizard > --------------------------------------------------------------- > > Key: JBDS-4179 > URL: https://issues.jboss.org/browse/JBDS-4179 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: documentation, installer, upstream > Affects Versions: 10.2.0.GA > Environment: openjdk version "1.8.0_102" > OpenJDK Runtime Environment (build 1.8.0_102-b14) > Reporter: Marián Labuda > Assignee: Denis Golovin > Fix For: 11.0.0.AM1 > > > I tried to install latest DevStudio (devstudio-10.2.0.GA-v20161116-0039-B6472-installer-standalone.jar) but when I run installation as usual, I get console installation - at first whole license text and prompt to 1) Accept, 2) Reject, 3) Redisplay. After that installation unpack files to home and I am not able to select destination. > This happens with older version of openjdk8. With latest available openjdk for fedora (1.8.0_111) it works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23045) xml validator can't find xsd even though it's specified in xml file

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23045?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23045: -------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.4.x) > xml validator can't find xsd even though it's specified in xml file > ------------------------------------------------------------------- > > Key: JBIDE-23045 > URL: https://issues.jboss.org/browse/JBIDE-23045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.4.0.Final > Reporter: Josef Ludvicek > Assignee: Lars Heinemann > Fix For: 4.5.0.AM2 > > Attachments: examle-blueprint.xml > > > RHDS xml validator can't find xsd schema in following xml file => validation doesn't work > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> >  > <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" > xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0" > xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0" xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0"> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23045) xml validator can't find xsd even though it's specified in xml file

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23045?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23045: ------------------------------------- Assigning to Lars: You guys should add this to your xml catalog if possible > xml validator can't find xsd even though it's specified in xml file > ------------------------------------------------------------------- > > Key: JBIDE-23045 > URL: https://issues.jboss.org/browse/JBIDE-23045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.4.0.Final > Reporter: Josef Ludvicek > Assignee: Lars Heinemann > Fix For: 4.5.0.AM2 > > Attachments: examle-blueprint.xml > > > RHDS xml validator can't find xsd schema in following xml file => validation doesn't work > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> >  > <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" > xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0" > xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0" xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0"> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23045) xml validator can't find xsd even though it's specified in xml file

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23045?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-23045: ----------------------------------- Assignee: Lars Heinemann (was: Rob Stryker) > xml validator can't find xsd even though it's specified in xml file > ------------------------------------------------------------------- > > Key: JBIDE-23045 > URL: https://issues.jboss.org/browse/JBIDE-23045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.4.0.Final > Reporter: Josef Ludvicek > Assignee: Lars Heinemann > Fix For: 4.4.x > > Attachments: examle-blueprint.xml > > > RHDS xml validator can't find xsd schema in following xml file => validation doesn't work > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> >  > <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" > xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0" > xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0" xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0"> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22725) Provided wrong credentials, CDK adapter creates openshift connection with a strange IP

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22725?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-22725: ----------------------------------- Assignee: Rob Stryker > Provided wrong credentials, CDK adapter creates openshift connection with a strange IP > -------------------------------------------------------------------------------------- > > Key: JBIDE-22725 > URL: https://issues.jboss.org/browse/JBIDE-22725 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.1.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > > When you start CDK with wrong credentials, service manager will return this strange IP: > {code} > # docker env: > # Copying TLS certificates to /Users/rasp/jbossqa/cdk2.1/cdk2.1.rc5/components/rhel/misc/shared_folder/rhel-ose/.vagrant/machines/default/virtualbox/docker > # Set the following environment variables to enable access to the docker daemon running inside of the vagrant virtual machine: > export DOCKER_HOST=tcp://10.0.2.15:2376 > export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk2.1/cdk2.1.rc5/components/rhel/misc/shared_folder/rhel-ose/.vagrant/machines/default/virtualbox/docker > export DOCKER_TLS_VERIFY=1 > export DOCKER_API_VERSION=1.21 > # run following command to configure your shell: > # eval "$(vagrant service-manager env)" > {code} > This has been reported upstream here: > https://github.com/projectatomic/vagrant-service-manager/issues/299 > Let's use this JIRA to track the upstream issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22725) Provided wrong credentials, CDK adapter creates openshift connection with a strange IP

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22725?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22725: -------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Provided wrong credentials, CDK adapter creates openshift connection with a strange IP > -------------------------------------------------------------------------------------- > > Key: JBIDE-22725 > URL: https://issues.jboss.org/browse/JBIDE-22725 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.1.AM1 > Reporter: Martin Malina > Fix For: 4.5.x > > > When you start CDK with wrong credentials, service manager will return this strange IP: > {code} > # docker env: > # Copying TLS certificates to /Users/rasp/jbossqa/cdk2.1/cdk2.1.rc5/components/rhel/misc/shared_folder/rhel-ose/.vagrant/machines/default/virtualbox/docker > # Set the following environment variables to enable access to the docker daemon running inside of the vagrant virtual machine: > export DOCKER_HOST=tcp://10.0.2.15:2376 > export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk2.1/cdk2.1.rc5/components/rhel/misc/shared_folder/rhel-ose/.vagrant/machines/default/virtualbox/docker > export DOCKER_TLS_VERIFY=1 > export DOCKER_API_VERSION=1.21 > # run following command to configure your shell: > # eval "$(vagrant service-manager env)" > {code} > This has been reported upstream here: > https://github.com/projectatomic/vagrant-service-manager/issues/299 > Let's use this JIRA to track the upstream issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20753) Text flickering when selecting server types in New Server wizard

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20753?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-20753. --------------------------------- Resolution: Done fixed upstream > Text flickering when selecting server types in New Server wizard > ---------------------------------------------------------------- > > Key: JBIDE-20753 > URL: https://issues.jboss.org/browse/JBIDE-20753 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Priority: Minor > Labels: regression > Fix For: 4.5.0.AM1 > > > When you open the New Server wizard and select a server type, There will be some elements rendered for a fraction of a second. It's Server Runtime Environment and a dropdown menu - it will disappear again, but it's not nice to see something quickly appear and disappear again. You can keep selecting server types and it will keep happening. All of this is on the first page of the dialog. > I checked and this did not happen in Beta2. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017