[JBoss JIRA] (JBIDE-16133) No indication that management authentication fails
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16133?page=com.atlassian.jira.plugi... ]
Paul Richardson commented on JBIDE-16133:
-----------------------------------------
Trying to connect to a remote server with an incorrect password, I get the following in the console:
{code}
Nov 29, 2013 10:48:16 AM org.jboss.remoting3.remote.RemoteConnection handleException
ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
!ENTRY org.teiid.designer.dqp 2 0 2013-11-29 10:48:16.602
!MESSAGE Failed to connect to the jboss server at org.jboss.ide.eclipse.as.core.server.internal.v7.JBoss7Server@1fb4112
Nov 29, 2013 10:48:28 AM org.jboss.remoting3.remote.RemoteConnection handleException
ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
!ENTRY org.teiid.designer.dqp 2 0 2013-11-29 10:48:28.933
!MESSAGE Failed to connect to the jboss server at org.jboss.ide.eclipse.as.core.server.internal.v7.JBoss7Server@1fb4112
Nov 29, 2013 10:48:29 AM org.jboss.remoting3.remote.RemoteConnection handleException
ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
!ENTRY org.teiid.designer.dqp 2 0 2013-11-29 10:48:29.018
!MESSAGE Failed to connect to the jboss server at org.jboss.ide.eclipse.as.core.server.internal.v7.JBoss7Server@1fb4112
Nov 29, 2013 10:48:29 AM org.jboss.remoting3.remote.RemoteConnection handleException
ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
!ENTRY org.teiid.designer.dqp 2 0 2013-11-29 10:48:29.083
!MESSAGE Failed to connect to the jboss server at org.jboss.ide.eclipse.as.core.server.internal.v7.JBoss7Server@1fb4112
Nov 29, 2013 10:49:31 AM org.jboss.remoting3.remote.RemoteConnection handleException
ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
Nov 29, 2013 10:49:31 AM org.teiid.adminapi.AdminFactory createAdmin
INFO: TEIID70051 The controller is not available at KESTREL:9,999
java.lang.IllegalArgumentException: admin
at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:303)
at org.teiid84.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:131)
at org.teiid84.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:32)
at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102)
at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:181)
at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:216)
at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:146)
at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742)
at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:210)
at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:100)
at org.jboss.ide.eclipse.as.rse.core.RSEJBossStartLaunchDelegate.preLaunchCheck(RSEJBossStartLaunchDelegate.java:44)
at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.preLaunchCheck(DelegatingStartLaunchConfiguration.java:67)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:813)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:700)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3537)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3473)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
!ENTRY org.teiid.designer.dqp 4 0 2013-11-29 10:50:20.836
!MESSAGE admin
!STACK 0
java.lang.IllegalArgumentException: admin
at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:303)
at org.teiid84.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:131)
at org.teiid84.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:32)
at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102)
at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:181)
at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:216)
at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:146)
at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742)
at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:210)
at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:100)
at org.jboss.ide.eclipse.as.rse.core.RSEJBossStartLaunchDelegate.preLaunchCheck(RSEJBossStartLaunchDelegate.java:44)
at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.preLaunchCheck(DelegatingStartLaunchConfiguration.java:67)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:813)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:700)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3537)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3473)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
java.lang.IllegalArgumentException: admin
at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:303)
at org.teiid84.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:131)
at org.teiid84.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:32)
at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102)
at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:181)
at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:216)
at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:146)
at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742)
at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:210)
at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:100)
at org.jboss.ide.eclipse.as.rse.core.RSEJBossStartLaunchDelegate.preLaunchCheck(RSEJBossStartLaunchDelegate.java:44)
at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.preLaunchCheck(DelegatingStartLaunchConfiguration.java:67)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:813)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:700)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3537)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3473)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
java.lang.IllegalArgumentException: admin
at org.teiid.core.util.ArgCheck.isNotNull(ArgCheck.java:303)
at org.teiid84.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:131)
at org.teiid84.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:32)
at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102)
at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:181)
at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:216)
at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:146)
at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742)
at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:210)
at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:100)
at org.jboss.ide.eclipse.as.rse.core.RSEJBossStartLaunchDelegate.preLaunchCheck(RSEJBossStartLaunchDelegate.java:44)
at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.preLaunchCheck(DelegatingStartLaunchConfiguration.java:67)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:813)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:700)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3537)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3473)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Nov 29, 2013 10:50:40 AM org.jboss.remoting3.remote.RemoteConnection handleException
ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
Nov 29, 2013 10:50:41 AM org.jboss.as.controller.client.impl.RemotingModelControllerClient finalize
WARN: JBAS010600: Closing leaked controller client
JBAS010649: Allocation stack trace:
at java.lang.Thread.getStackTrace(Thread.java:1568)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient.<init>(RemotingModelControllerClient.java:74)
at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:225)
at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:173)
at org.teiid.adminapi.AdminFactory.createAdmin(AdminFactory.java:116)
at org.teiid84.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:127)
at org.teiid84.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:32)
at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102)
at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:181)
at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:216)
at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:146)
at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742)
at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:210)
at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:100)
at org.jboss.ide.eclipse.as.rse.core.RSEJBossStartLaunchDelegate.preLaunchCheck(RSEJBossStartLaunchDelegate.java:44)
at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.preLaunchCheck(DelegatingStartLaunchConfiguration.java:67)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:813)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:700)
at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3537)
at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3473)
at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Nov 29, 2013 10:50:45 AM org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.7.GA-redhat-1
Nov 29, 2013 10:50:45 AM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.7.GA-redhat-1
Nov 29, 2013 10:50:45 AM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.16.GA-redhat-1
Nov 29, 2013 10:50:46 AM org.jboss.remoting3.remote.RemoteConnection handleException
ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
!ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2013-11-29 10:50:46.258
!MESSAGE Error connecting to jmx for server kestrel
!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:87)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:143)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:127)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:116)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:239)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:231)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:344)
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:227)
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:180)
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:187)
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:208)
at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:143)
at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:268)
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:77)
... 6 more
!SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2013-11-29 10:50:46.259
!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: all available authentication mechanisms failed
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:344)
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:227)
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:180)
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:187)
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:208)
at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:143)
at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:268)
at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:77)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:143)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:127)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:116)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:239)
at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:231)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Nov 29, 2013 10:51:05 AM org.jboss.remoting3.remote.RemoteConnection handleException
ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
!ENTRY org.teiid.designer.dqp 2 0 2013-11-29 10:51:05.369
!MESSAGE Failed to connect to the jboss server at org.jboss.ide.eclipse.as.core.server.internal.v7.JBoss7Server@1fb4112
{code}
... which is fairly comprehensive but not necessarily visible to the user since it will be buried in their jbds .metdata/.log file. Can people verify that they see similar in their jbds logs?
In my case since the server is brand new, a Teiid Configuration node is not even created beneath the jboss server's tree in the Server View hence the user has no clue that it failed so some kind of dialog warning is definitely required.
> No indication that management authentication fails
> --------------------------------------------------
>
> Key: JBIDE-16133
> URL: https://issues.jboss.org/browse/JBIDE-16133
> Project: Tools (JBoss Tools)
> Issue Type: Quality Risk
> Components: server
> Reporter: Steven Hawkins
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.1.1.CR1
>
>
> Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server and using an incorrect management password results in a console log entry:
> 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
> On server startup without any indication of what it means.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (JBIDE-16032) java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16032?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-16032:
------------------------------------
[~koen.aers], there is no plan to do 4.1.1.CR1 respin-b. Will it be picked up in Final respin? If so, can you please change the fix version respectively?
> java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences
> ---------------------------------------------------------------------
>
> Key: JBIDE-16032
> URL: https://issues.jboss.org/browse/JBIDE-16032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Environment: Linux
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Labels: respin-a, respin-b
> Fix For: 4.1.1.CR1
>
> Attachments: forge-preferences.png
>
>
> Stacktrace:
> {code}
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage$6.run(ForgeInstallationsPreferencePage.java:293)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage.performOk(ForgeInstallationsPreferencePage.java:290)
> at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:965)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:945)
> at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:448)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:171)
> at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215)
> at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months
[JBoss JIRA] (JBDS-2801) Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2801?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-2801:
--------------------------------
Attachment: install-new-gpe-1.png
install-new-gpe-2.png
install-new-gpe-3.png
install-new-gpe-4.png
OK, so I verified the update process and here's what the users will see:
As I pointed out in my previous comments, 3rd party plugins installed via central will not be updated automatically using Help -> Check for updates.
When JBDS 7.1.0 goes live, central will point to the new content, but unfortunately the only indication of a newer version of a feature will be that the feature will be shown in the list even if it has already be installed. Here on the picture I have already the older version of the google plugins installed:
!install-new-gpe-1.png!
When I chose to install the new GPE and JBoss Maven GWT Configurator, I saw this:
!install-new-gpe-2.png!
I then needed to click the second option - Update my installation to be compatible with the items being installed:
!install-new-gpe-3.png!
Note that this remediation is only needed here because of the GPE plugin name change from com.google.gdt.eclipse.suite.e42.feature to com.google.gdt.eclipse.suite.e43.feature. With other features it should just be a smooth update.
After finishing the install and restarting JBDS and selecting Help -> Install new software -> already installed I saw this:
!install-new-gpe-4.png!
The only blank I need to fill is whether the new central content will be visible once 7.1 goes GA or after the user updates to the 7.1 product (using Help -> Check for updates). I assume the former is true. The latter would only be true if we used a new discovery url for central and the update to 7.1 would update that. [~nickboldt] can you confirm?
All in all, the conclusion is that unfortunately at present we don't have a smooth way for users to update their features installed via JBoss Central (no Help -> Check for update).
> Investigate use of GWT/GPE 3.4 in JBT/JBDS Central
> --------------------------------------------------
>
> Key: JBDS-2801
> URL: https://issues.jboss.org/browse/JBDS-2801
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: new_and_noteworthy
> Fix For: 7.1.0.CR1
>
> Attachments: install-new-gpe-1.png, install-new-gpe-2.png, install-new-gpe-3.png, install-new-gpe-4.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_manual_install_of_GPEe43_throws_remediation.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBDS_CR1_check_for_updates_no_GPE_installed_view.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_1.png, JBDS2801_install_GWT32e42_from_Central_Beta1_site_JBT_CR1_remdiation_option_2.png, JBDS2801_install_JBDS_Beta1_b441_installed.png, JBDS2801_install_JBT_CR1.png, JBDS2801_install_JBT_CR1_installed.png
>
>
> New 3.4.2 mirrors:
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> http://download.jboss.org/jbosstools/updates/requirements/gwt/3.4.2.v2013...
> Note that at least one IU had been renamed:
> OLD:
> * com.google.gdt.eclipse.suite.e42.feature_3.4.2.v201310081840-rel-r42.jar
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081840-rel-r42.jar
> NEW:
> * com.google.gdt.eclipse.suite.e43.feature_3.4.2.v201310081834-rel-r43.jar (now e43)
> * com.google.gdt.eclipse.platform.e42_3.4.2.v201310081834-rel-r43.jar (still e42)
> If we decide to move to e43, we will have to rebuild jbosstools-central due to this requirement:
> {code:title=https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.1.x/maven/features/org.jboss.tools.maven.gwt.feature/feature.xml#L24}
> <import feature="com.google.gdt.eclipse.suite.e42.feature" version="3.0.1" match="greaterOrEqual"/>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 6 months