October 2016 - jbosstools-issues - Jboss List Archives

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20108?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20108: ----------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > 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 > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.2.AM2 > > > 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 (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4014) Track rh-eclipse46-devstudio-*.rpm version usage

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4014?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4014: ---------------------------------- {quote} (2016-10-19 11:59:46) nboldt: mbooth: to confirm, I should be removing com.jboss.devstudio.core.usage.branding and org.jboss.tools.usage.* from devstudio rpm? 12:00 (2016-10-19 12:00:06) nboldt: or keep the usage.branding one, but just remove the plugins/features from jbt? (2016-10-19 12:02:47) mbooth: nboldt: The rpm will only deliver the "org.jboss.tools.usage.*" plugin and feature, so only need to remove those {quote} PR: https://github.com/jbdevstudio/jbdevstudio-product/pull/416/files > Track rh-eclipse46-devstudio-*.rpm version usage > ------------------------------------------------ > > Key: JBDS-4014 > URL: https://issues.jboss.org/browse/JBDS-4014 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexander Kurtakov > Priority: Critical > Fix For: 10.2.0.AM2 > > > We need to distinguish the following use cases: > 1) Devstudio installed via RPM > 2) Devstudio installed via P2 but on top of the "base" eclipse rpm > 3) Devstudio installed traditionally (jar installer or p2) > As a bonus we could want to track if the DTS + devstudio rpms were both installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3509) Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3509?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-3509: ----------------------------------- A bit more backstory from Alex K: * there was actually a jbosstools rpm for a couple years in Fedora * it was built from sources, including all test dependencies and all the JBossAS/EAP/Wildfly runtimes * maintaining this massive dependency tree was time consuming and problematic * the rpm was only just recently removed from Fedora In future, rather than a built-from-sources RPM, we could instead do: * a copr rpm [not built from sources, but rather repackaged from upstream update sites] However, based on feedback from Alexey, Alex, and Martha there's currently no interest in doing so. Once we get numbers from *devstudio* rpm installs/usage, we could consider creating a copr rpm for jbosstools in a future release, if there's sufficient interest & community demand. > Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss > ----------------------------------------------------------------------------------------- > > Key: JBIDE-3509 > URL: https://issues.jboss.org/browse/JBIDE-3509 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.2.AM2 > > Attachments: eclipse-jbosstools-openshift-in-dropins.png, eclipse-jbosstools-server.png > > > John Ford (John64 on Freenode), a college student from Seneca, has expressed interest in packaging JBT for Fedora. This is a placeholder to track that progress as it relates to the JBT 3.0.0 release, possibly as part of Fedora 11? > Details: http://fedoraproject.org/wiki/JBoss -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23128) Eclipse Neon.1 JSDT Blog

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23128?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-23128. ------------------------------ > Eclipse Neon.1 JSDT Blog > ------------------------- > > Key: JBIDE-23128 > URL: https://issues.jboss.org/browse/JBIDE-23128 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, upstream, website > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.2.AM2 > > > Need to write blog about Neon.1 JSDT improvements. Tentative structure: > - Node.js Debugger improvements > - New JavaScript Debugger > - npm scripts support > - OMPH installer support > - Important bug fixes (provide a query with all Neon.1 bug fixes) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-4920) New Hibernate Console Configuration File (cfg.xml) file doesn't save state for Classpath tab in New Hibernate Console Configuration Step after '<Back' is pressed

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-4920?page=com.atlassian.jira.plugin... ] Denis Golovin reassigned JBIDE-4920: ------------------------------------ Assignee: Koen Aers (was: Denis Golovin) > New Hibernate Console Configuration File (cfg.xml) file doesn't save state for Classpath tab in New Hibernate Console Configuration Step after '<Back' is pressed > ----------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-4920 > URL: https://issues.jboss.org/browse/JBIDE-4920 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 3.1.0.M4 > Reporter: Denis Golovin > Assignee: Koen Aers > Priority: Trivial > Fix For: 4.3.x > > > 1. EXECUTE: Create Java Project > 2. EXECUTE: Select Java Project from step 1 and invoke New Hibernate Configuration file Wizard > 3. EXECUTE: Go through all steps to New Hibernate Console Configuration step > 4. EXECUTE: Select 'Classpath' tab, remove 'default classpath' entry > 5. EXECUTE: Press '<Back' > 6. EXECUTE: Press 'Next>' and select 'Classpath' tab > 7. ASSERT: State is the same as it was after step 4 above executed > Now it restores default values -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4108) Detection doesen't work when running DevSuite.app

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4108?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-4108. ------------------------------- Resolution: Done > Detection doesen't work when running DevSuite.app > ------------------------------------------------- > > Key: JBDS-4108 > URL: https://issues.jboss.org/browse/JBDS-4108 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Environment: Mac OS X > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.2.0.AM2 > > > Detection based on > {code}'which vagrant'{code} > fails to find 'which' util, because of $PATH being different from one set in bash. > https://discuss.atom.io/t/how-to-execute-node-js-child-process-from-packa... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4099) DevStudio does not start from installer on Mac

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4099?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-4099. ------------------------------- Resolution: Done > DevStudio does not start from installer on Mac > ---------------------------------------------- > > Key: JBDS-4099 > URL: https://issues.jboss.org/browse/JBDS-4099 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.2.0.AM2 > > > That happens because we use .vbs script to copy environment variables to current process so running Devstudio would see them. This is windows specific code and fails on Mac. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4092) Mac OS X devstudio.app starts with empty screen

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4092?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-4092. ------------------------------- Resolution: Done > Mac OS X devstudio.app starts with empty screen > ----------------------------------------------- > > Key: JBDS-4092 > URL: https://issues.jboss.org/browse/JBDS-4092 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Environment: Mac OS X > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.2.0.AM2 > > Attachments: Screen Shot 2016-10-05 at 10.21.31 PM.png > > > devtools console has error reported > {code}Uncaught AssertionError: missing path{code} > !Screen Shot 2016-10-05 at 10.21.31 PM.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22225: ------------------------------------- could someone review the change - https://github.com/jbosstools/jbosstools-openshift/pull/1340 ? > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-22225: -------------------------------- Story Points: 5 (was: 20) > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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