June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18912) Custom deploy dir with remote server using filesystem operations does not work

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18912?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18912: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) Slip to AM2 > Custom deploy dir with remote server using filesystem operations does not work > ------------------------------------------------------------------------------ > > Key: JBIDE-18912 > URL: https://issues.jboss.org/browse/JBIDE-18912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: help_wanted > Fix For: 4.5.0.AM2 > > > This is a follow up of JBIDE-17180 and JBIDE-13445 which added the option to add a custom deployment directory if your remote server is using filesystem operations (for management api it's not relevant since the deployment happens directly, no directory is used). > Unfortunately it does not work. It seems I haven't really tried it when reviewing those other JIRAs because there were other obstacles. > I tried this several times and still could not get it to work. > Perhaps it might be worth to try and get this in the final 4.2.1.Final build? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20108?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20108: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) Slip to 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.5.0.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 (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23868) Fix jbt-server otherOS test cases: take 2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23868?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23868: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) Slip to AM2 > Fix jbt-server otherOS test cases: take 2 > ----------------------------------------- > > Key: JBIDE-23868 > URL: https://issues.jboss.org/browse/JBIDE-23868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.AM3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM2 > > > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4254) Validate Hyper-V configuration is correct for minishift to work

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4254?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4254: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Validate Hyper-V configuration is correct for minishift to work > --------------------------------------------------------------- > > Key: JBDS-4254 > URL: https://issues.jboss.org/browse/JBDS-4254 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Environment: Windows 10 Pro > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.0.0.AM2 > > > Installer should check if Hyper-V configured correctly to work with minishift and show warnings/errors. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3962) Blog post about DevSuite installer on developers.redhat.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3962?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3962: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Blog post about DevSuite installer on developers.redhat.com > ----------------------------------------------------------- > > Key: JBDS-3962 > URL: https://issues.jboss.org/browse/JBDS-3962 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: marketing > Fix For: 11.0.0.AM2 > > > We should draw more attention to DevSuite Installer and put more content about it on http://developers.redhat.com/blog/. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3837) Installer UI does not communicate errors to the user properly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3837?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3837: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Installer UI does not communicate errors to the user properly > ------------------------------------------------------------- > > Key: JBDS-3837 > URL: https://issues.jboss.org/browse/JBDS-3837 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Denis Golovin > Labels: ui > Fix For: 11.0.0.AM2 > > Attachments: screen-installer2.png > > > The installation has failed with no reason given. Please see screenshot attached. > We need to improve the UI too - If something fails the progress bar should be changed to red color etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4339) DevSuite installer on Windows should ask for hostfolder details

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4339?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4339: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > DevSuite installer on Windows should ask for hostfolder details > --------------------------------------------------------------- > > Key: JBDS-4339 > URL: https://issues.jboss.org/browse/JBDS-4339 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Fix For: 11.0.0.AM2 > > > Minishift/CDK allows to mount a Samba/CIFS share into the VM. This is a replacement for the current approach of using vagrant-sshfs as part of ADB/CDK 2.x. > The vagrant-sshfs approach was password free, but for the CIFS approach we at the very least need the users Windows password. On top of this we can also allow the user to specify any share (opposed to just this home directory) as well as a custom mount point in the VM. > The question is where and how the user specifies this information. In order to have a fully integrated solution where after the install DevStudio can be launched and the CDK adapter starting the CDK, the installer would need to ask the user for the required information and write some additional configuration data. > Without this additional setup, the user would not have any host folders available. They can be added later by running a {code}minishift{code} command, but this would be a manual step and it might not be obvious to the user. > Thoughts? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4369) Provide a .exe for uninstaller on Windows

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4369?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4369: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Provide a .exe for uninstaller on Windows > ----------------------------------------- > > Key: JBDS-4369 > URL: https://issues.jboss.org/browse/JBDS-4369 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.AM2 > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 11.0.0.AM2 > > > currently it is a .ps1 file, this is very uncommon -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3652) Installer - Replace use of JBDS installer with JBDS product archive - to save time

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3652?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3652: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Installer - Replace use of JBDS installer with JBDS product archive - to save time > ---------------------------------------------------------------------------------- > > Key: JBDS-3652 > URL: https://issues.jboss.org/browse/JBDS-3652 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Minor > Labels: havoc, performance > Fix For: 11.0.0.AM2 > > > The current installer runs for several minutes when it invokes the JBDS installer - can we replace this a JBDS product archive and some follow-on tasks (such as setting the JDK location)? Thx! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3779) Consider changing the installation order

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3779?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3779: ----------------------------- Fix Version/s: 11.0.0.AM2 (was: 11.0.0.AM1) Slip to AM2 > Consider changing the installation order > ---------------------------------------- > > Key: JBDS-3779 > URL: https://issues.jboss.org/browse/JBDS-3779 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 11.0.0.AM2 > > > Right now there are the following installation 'streams': > 1. JDK -> JBDS - looks fine to me > 2. Virtualbox -> Cygwin -> Vagrant -> CDK - this is the one I have an issue with. > The second stream starts with Virtualbox which first needs to be downloaded. Maybe some other component could do something productive while Virtualbox is downloading so it might save some time. In other words - could something other than a download start the installation? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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