April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3818) Installer does not remember my selected folder until 'continue' is pressed

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3818?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3818: -------------------------------- > Installer does not remember my selected folder until 'continue' is pressed > -------------------------------------------------------------------------- > > Key: JBDS-3818 > URL: https://issues.jboss.org/browse/JBDS-3818 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > For some reason installer remembers the selected folder only if it reached the confirmation page. > Log in -> select a target folder -> go back to login -> log in again -> selected folder is back to default > Log in -> select a target folder -> continue -> go back to login -> log in again -> target folder stays the way it was selected -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3818) Installer does not remember my selected folder until 'continue' is pressed

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3818?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3818: -------------------------------- Target Release: 10.0.0.GA > Installer does not remember my selected folder until 'continue' is pressed > -------------------------------------------------------------------------- > > Key: JBDS-3818 > URL: https://issues.jboss.org/browse/JBDS-3818 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > For some reason installer remembers the selected folder only if it reached the confirmation page. > Log in -> select a target folder -> go back to login -> log in again -> selected folder is back to default > Log in -> select a target folder -> continue -> go back to login -> log in again -> target folder stays the way it was selected -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3783) Installer hangs with install directory too long for Windows - no error reported to user

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3783?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3783: ----------------------------- > Installer hangs with install directory too long for Windows - no error reported to user > --------------------------------------------------------------------------------------- > > Key: JBDS-3783 > URL: https://issues.jboss.org/browse/JBDS-3783 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > With build: Version: 0.0.2-20160406-56 > If an install directory with a length > 256 characters is used, the installer hangs after the user completes the second screen (i.e., where the CDK, etc. are specified). > No error is logged or reported to the user. > The install dir used was: > c:\way_to_long_dir_1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3816) Limit the target folder length to avoid path too long for Windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3816?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3816: -------------------------------- Sprint: devex #6 April 2016 > Limit the target folder length to avoid path too long for Windows > ----------------------------------------------------------------- > > Key: JBDS-3816 > URL: https://issues.jboss.org/browse/JBDS-3816 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > Looks like no length limit is set for the target folder, this way one can run into the path too long error when installing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3818) Installer does not remember my selected folder until 'continue' is pressed

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3818?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3818: -------------------------------- Sprint: devex #6 April 2016 > Installer does not remember my selected folder until 'continue' is pressed > -------------------------------------------------------------------------- > > Key: JBDS-3818 > URL: https://issues.jboss.org/browse/JBDS-3818 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > For some reason installer remembers the selected folder only if it reached the confirmation page. > Log in -> select a target folder -> go back to login -> log in again -> selected folder is back to default > Log in -> select a target folder -> continue -> go back to login -> log in again -> target folder stays the way it was selected -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3849) Store downloaded requirements for bundled installer between builds

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3849?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3849: -------------------------------- Fix Version/s: 10.0.0.Alpha1 > Store downloaded requirements for bundled installer between builds > ------------------------------------------------------------------ > > Key: JBDS-3849 > URL: https://issues.jboss.org/browse/JBDS-3849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Nick Boldt > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > Now build downloads all bundled binaries in every build, because the got wiped out by clean task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18525) Investigate how to do module deployment ordering properly with management api

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18525?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18525: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > Investigate how to do module deployment ordering properly with management api > ----------------------------------------------------------------------------- > > Key: JBIDE-18525 > URL: https://issues.jboss.org/browse/JBIDE-18525 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.CR2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.x > > > This is a followup of JBIDE-18373 which was originally about deployment via management api not handling "mark as deployable" files properly. This was fixed, but there's still a problem of ordering. The use case here was a seam project deployed to EAP 6.3. There are three parts: > 1. Seam project war > 2. database driver jar > 3. datasource xml > When you click "Add and Remove..." on the server in server view, it will sometimes be deployed in the wrong order and fail to deploy. > Specifically, when you click "Add All" in the dialog, it will not work, whereas if you click "Add" for each of the three resources, it will deploy alright. > As Rob pointed out, it can get really tricky to guess the right ordering. > See JBIDE-18373 for more details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20426) JBossAS Tools: sometimes, Restarting in Debug results in "Failed to start", even though it started

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20426?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20426: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > JBossAS Tools: sometimes, Restarting in Debug results in "Failed to start", even though it started > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-20426 > URL: https://issues.jboss.org/browse/JBIDE-20426 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: The Alchemist > Assignee: Rob Stryker > Fix For: 4.4.x > > > This usually happens when I have a few big EARs attached, so I think the "checker" doesn't wait long enough to see if WF actually restarted. > The result is this weird situation where the "Servers" view says that it's "Stopped", but the Console view has the red square to terminate the process. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20108?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20108: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > 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.x > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18274) AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18274?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18274: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) > AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname > ------------------------------------------------------------------------------- > > Key: JBIDE-18274 > URL: https://issues.jboss.org/browse/JBIDE-18274 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.x > > Attachments: server-adapter.png, server-editor.png, server-logs.png, server-runtime.png > > > This is a follow up of JBIDE-17935 . > Previously, Rob fixed this: > {quote} > I've surprisingly been able to replicate this and it's a race-condition. I'll need to synchronize some variables in this class here. > {quote} > But in this rare case it still fails for me. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016