Max Rydahl Andersen <manderse> made a comment on jira JBIDE-16133 I need some more details - what are the steps you do ? what did expect to see/what did you get in past ? just setting username/password doesn't actually do anything.
Steven Hawkins <shawkins> made a comment on jira JBIDE-16133 > what are the steps you do ? From the servers view create a server or select an existing one. Set the "Management Login Credentials" to an invalid name/password combo. Then perform any operation that uses a management command. The log will accumulate the entry shown above with each operation without any indication to the user that the connection is not authenticating. See the related bz entries as well. > what did expect to see/what did you get in past ? Don't know about the past, but I would expect to see something to the affect that I have a bad management password. If it matters what action/tool (if it's likely something being swallowed/mishandled higher up), then this can be moved. Barry Lafond thought is was applicable at this level.
Max Rydahl Andersen <manderse> made a comment on jira JBIDE-16133 [~shawkins] and when you actually put in correct username/password does the error logging stop on the server side ? Trying to understand if we are dealing with one or two errors: 1) No indication that management authentication fails 2) connection reset by peer logged on server side on every(?) management call
Steven Hawkins <shawkins> made a comment on jira JBIDE-16133 > connection reset by peer logged on server side on every management call That is just a side affect of having an invalid username/password. If you put in the correct management credentials, the console log is clear of those errors.
Max Rydahl Andersen <manderse> made a comment on jira JBIDE-16133 [~shawkins] what are the exact server you are running here and I assume you are running the server remotely because when running locally username/password is not used ?
Steven Hawkins <shawkins> made a comment on jira JBIDE-16133 Yes it's a remote DV 6.0.0 ER4, which would be EAP 6.1
Rob Stryker <rob.stryker> made a comment on jira JBIDE-16133 Hi Steven (and [~blafond]): I think I need more information on your specific usecase. I've just tested with an EAP6.1 with the following usecase, and I'm not really able to replicate your issue of the logs filling up. If I use a clean workspace and start the remote server with an incorrect password, I definitely get a credentials dialog popping up. The only way the dialog doesn't show up is if I accidentally click "Never show this again". Unfortunately there's no UI for the "never show this again" button (oops), but the setting is stored as follows: {code} public static final String NEVER_ASK_AGAIN_KEY = "org.jboss.ide.eclipse.as.ui.launch.credentials.neverAsk"; //$NON-NLS-1$ IEclipsePreferences prefs = InstanceScope.INSTANCE.getNode(JBossServerUIPlugin.PLUGIN_ID); boolean ignore = prefs.getBoolean(NEVER_ASK_AGAIN_KEY, false); {code} So if you can try on a clean workspace, or reset that preference, it might fix your issue (or might not). Another possibility is that your remote server is not actually exposing its management port. You'll have to ensure that the remote server was launched with args -Djboss.bind.address.management={yourHost} For random management requests, a trace through my code indicates that each management request requires a IAS7ManagementDetails, and the default impl of this interface is AS7ManagementDetails. The current implementation only requests credentials if the values stored in the server are empty, for example, an empty username setting or an empty password setting. So long as there are values stored in the server, it will use them and *not* request credentials. A management request will only be asked for credentials *once* by the as7/wildfly framework, so there's really not any elegant way for my code to tell the difference. In general, it is up to the caller of the management request (in this case, Teiid) to catch this exception thrown by the management service and to throw up the credential dialog. I'd be happy to work with you guys if you think there's another way, or if you can outline your usecase more deeply as to what exactly you guys are doing. But the main limitation here is that for any single management request, the IAS7ManagementDetails only gets 1 chance to get the credentials correct. This is a wildfly / as7 limitation, and ASTools does not currently have any api to make this easier, or to make multiple requests or poll if the request is wrong. You guys can implement IAS7ManagementDetails yourself and force it to always poll for credentials, but that will quickly become very annoying to the user as well, so I don't think that's the proper solution. I think the best solution for you guys is to catch the credentialing exception, open the credential dialog, and then re-post your management command. {code} } catch (Exception e) { Throwable root = getRootException(e); // If the exception is one that autnentication failed, re-prompt. if(root != null && root.getMessage() != null && root.getMessage().startsWith("Authentication failed:")) //$NON-NLS-1$ provideCredentials(null); {code} To open the credential dialog, you can use the following api: {code} PollThreadUtils.requestCredentialsSynchronous(serverProvider, requiredProperties); {code} One final option is you can implement IAS7ManagementDetails in such a way that each IAS7ManagementDetails is used only once, but if one is used twice, you open the credential dialog. Then in your code, you would need to catch the credentialing exception, and issue the command again using the same IAS7ManagementDetails instance. Let me know if you guys need any more help.
Steven Hawkins <shawkins> made a comment on jira JBIDE-16133 > So if you can try on a clean workspace, or reset that preference, it might fix your issue (or might not). This is as clean of a workspace as I should have. This was a new workspace off a fresh install and the first server instance I created. > Another possibility is that your remote server is not actually exposing its management port. You'll have to ensure that the remote server was launched with args No the log is clean with the correct credentials. > I think the best solution for you guys is to catch the credentialing exception, open the credential dialog, and then re-post your management command. That is something that may be needed. Barry or someone like Paul Richardson should weigh in here.
Max Rydahl Andersen <manderse> made a comment on jira JBIDE-16133 Okey, had a chat with Rob about the issue here. There are two issues in play here: A) lack of credentials dialog when authentication fails B) mysterious logging of JBREM000200 connection reset by peer. For A Rob found that in the past (JBDS 5) we had a dialog *always* show up, no matter if credentials was good or bad before executing a management operation. This was fixed in https://issues.jboss.org/browse/JBIDE-10298 (2 years ago) so the operation now just executes the operation. If the client api wants to execute this operation again you would need to execute this operation again. This is actually no different from the past - after the forced shown credentials dialog, if you put in wrong credentials and exception would be thrown and you would need to handle that on the calling side anyway. You can use PollThreadUtils.requestCredentialsSynchronous(server, props) to show this dialog and have it stored in the server. In case showing the dialog is not possible I suggest you at least log an warning or error even to the eclipse log stating credentials were not correct for Server X and that it can be fixed in the server editor/settings. Unfortunately this API around authentation is not very clean so you have to do things like checking the content of the exception message as Rob describes further above. I recommend we do not change this in this release stream now, but have that as goal for the update/rewrite of AS tools in next major release (JBDS 8/JBT 4.3). Mind you, this is an issue that as far as we can see have been present for 2+ years. For #A - Teiid designer should always have catched the exception and report accordingly. For B, this is still a mystery. We haven't seen this yet when using base server tools and stock EAP 6 thus we are wondering if there are some differences in the server libaries in DV and EAP that could explain this ? Or that there is some missing cleanup/early disconnect that Teiids usage of the server tools api that causes this error. We would need more details/help to track down #B.
Paul Richardson <p.g.richardson.uk> made a comment on jira 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.
Paul Richardson <p.g.richardson.uk> made a comment on jira JBIDE-16133 Pull request for handling incorrect password, ie. authentication failure, in Teiid Designer: [https://github.com/Teiid-Designer/teiid-designer/pull/267]
Van, this seems to be a duplicate of Bug 1035002. Is that intentional?
*** This bug has been marked as a duplicate of bug 1035002 ***