February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23503) Target platform PR check fails to use p2diff correctly, so build fails

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23503?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23503: ------------------------------- Fix Version/s: 4.4.4.AM1 (was: 4.4.3.AM2) > Target platform PR check fails to use p2diff correctly, so build fails > ---------------------------------------------------------------------- > > Key: JBIDE-23503 > URL: https://issues.jboss.org/browse/JBIDE-23503 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.4.AM1 > > Attachments: dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com.log.txt > > > Recently, it was noticed that the TP PR checks are failing. And have been for a long time. > So, I'm opening this to track the work needed to make them work again. > There are two different TP PR jobs: > * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... (which seems to have never worked) > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... (which has been blue in the past) > Recent failure: > {code} > [INFO] Command line: > [/qa/tools/opt/x86_64/jdk1.8.0_101/jre/bin/java, -jar, /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/.repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.100.v20150511-1540/org.eclipse.equinox.launcher-1.3.100.v20150511-1540.jar, -install, /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/eclipserun-work, -configuration, /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/eclipserun-work/configuration, -application, org.eclipse.equinox.p2.example.p2diff.application, -outputFile=/mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/jbosstools-multiple-ignoreVersions.p2diff, -mode=ignoreVersions, file:/mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/jbosstools-multiple.target.repo, http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...] > An error has occurred. See the log file > /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/eclipserun-work/configuration/1479683354475.log.{code} > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20108) Cannot connect to remote server in JMX Navigator - Authentication fails

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20108?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20108: ------------------------------- Fix Version/s: 4.4.4.AM1 (was: 4.4.3.AM2) > Cannot connect to remote server in JMX Navigator - Authentication fails > ----------------------------------------------------------------------- > > Key: JBIDE-20108 > URL: https://issues.jboss.org/browse/JBIDE-20108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, server > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.4.AM1 > > > When I try to connect to a remote server via JMX Navigator, it fails on authentication: > {code} > !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2015-06-17 18:07:30.854 > !MESSAGE Error connecting to jmx for server JBoss EAP 6.4 marvin > !STACK 1 > org.jboss.tools.jmx.core.JMXException: Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor. > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:94) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.nio.NioHandle.run(NioHandle.java:90) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:198) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333) > at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230) > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84) > ... 7 more > !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2015-06-17 18:07:30.854 > !MESSAGE Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor. > !STACK 0 > javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) > at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183) > at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) > at org.xnio.nio.NioHandle.run(NioHandle.java:90) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:198) > at ...asynchronous invocation...(Unknown Source) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270) > at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349) > at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333) > at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230) > at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151) > at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102) > at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270) > at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332) > at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > This is different than JBIDE-19463 where the main problem was the missing runtime and we assumed that otherwise it would work. > Note: I tried WildFly 8.2, WildFly 9.0.0.CR2, EAP 6.4 and all failed the same way. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20063) locked up machine with "Loading descriptor" ...

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20063?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20063: ------------------------------- Fix Version/s: 4.4.4.AM1 (was: 4.4.3.AM2) > locked up machine with "Loading descriptor" ... > ----------------------------------------------- > > Key: JBIDE-20063 > URL: https://issues.jboss.org/browse/JBIDE-20063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.4.4.AM1 > > > when loaded javaee7-samples I ended up with frozen eclipse showing this: > https://www.dropbox.com/s/ttx9ppieads5m7n/Screenshot%202015-06-13%2001.31... > its so frozen I cannot even get a stacktrace from jps. > I tried looking for "Loading descriptor" in common and batch but no luck so maybe it is not in batch this is happening but something is definitely locking up ;/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4016) Add Readme.txt(.md) in the root of devsuite installation with references to all included projects

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4016?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4016: ----------------------------- Fix Version/s: 10.3.0.GA (was: 10.3.0.AM2) > Add Readme.txt(.md) in the root of devsuite installation with references to all included projects > ------------------------------------------------------------------------------------------------- > > Key: JBDS-4016 > URL: https://issues.jboss.org/browse/JBDS-4016 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.3.0.GA > > > This file should be generated during build based on info in platform specific requirements*.json -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22075: ------------------------------- Fix Version/s: 4.4.4.AM1 (was: 4.4.3.AM2) > Confusing error message when trying to attach remote debugger to OS app run in debug mode > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22075 > URL: https://issues.jboss.org/browse/JBIDE-22075 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: debugging, openshift_v3 > Fix For: 4.4.4.AM1 > > Attachments: error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, launch-debug-no-error.mov, remote-debugger-already-launched.png > > > If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically. > If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message > When I am trying to run remote debugging of an application on OpenShift I get following error > !!error-in-launching-remote-debugger.png! ! > {code} > Failed to connect to remote VM > com.sun.jdi.connect.spi.ClosedConnectionException > at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222) > at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214) > at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185) > at java.lang.Thread.run(Thread.java:745) > {code} > *Steps to reproduce:* > ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace. > EXEC: Select "Restart in Debug" in context menu of server adapter. > ASSERT: Server adapter is in state debugging ("[Debugging, Started]"). > EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging. > RESULT: Error is shown. > EXPECTED RESULT: The error message should tell you that there already is an instance running. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21065: ------------------------------- Fix Version/s: 4.4.4.AM1 (was: 4.4.3.AM2) > Server host name address should not be defaulted during server adapter creation > ------------------------------------------------------------------------------- > > Key: JBIDE-21065 > URL: https://issues.jboss.org/browse/JBIDE-21065 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.4.4.AM1 > > > I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}. > This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address. > Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4208) Detection for installed components always counts cygwin as detected on macOS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4208?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4208: ----------------------------- Fix Version/s: 10.3.0.GA (was: 10.3.0.AM2) > Detection for installed components always counts cygwin as detected on macOS > ---------------------------------------------------------------------------- > > Key: JBDS-4208 > URL: https://issues.jboss.org/browse/JBDS-4208 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.GA > Environment: macOS > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.3.0.GA > > > It means confirmation page message about detected components always increase number of detected components by one. If only Java is detected it would say "We found 2 installed components" one is Java and another one is Cygwin which is not visible under macOS. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4232) Implement CDK 3 installation in DevSuite Installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4232?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4232: ----------------------------- Fix Version/s: 10.3.0.GA (was: 10.3.0.AM2) > Implement CDK 3 installation in DevSuite Installer > -------------------------------------------------- > > Key: JBDS-4232 > URL: https://issues.jboss.org/browse/JBDS-4232 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.3.0.GA > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4067) Review labels shown for software components on confirmation page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4067?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4067: ----------------------------- Fix Version/s: 10.3.0.GA (was: 10.3.0.AM2) > Review labels shown for software components on confirmation page > ---------------------------------------------------------------- > > Key: JBDS-4067 > URL: https://issues.jboss.org/browse/JBDS-4067 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: ui > Fix For: 10.3.0.GA > > > On confirmation page installer shows list of components from software stack. For most components there is detection algorithm that can find already installed components, so installer can skip install. There should be term selected for set of version for the required components: > * required; > * recommended; > * tested; > * ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3951: ----------------------------- Fix Version/s: 10.3.0.GA (was: 10.3.0.AM2) > Installer needs to add the VirtualBox install directory to the PATH > ------------------------------------------------------------------- > > Key: JBDS-3951 > URL: https://issues.jboss.org/browse/JBDS-3951 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.3.0.GA > > > The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found. > As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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