[
https://issues.jboss.org/browse/JBIDE-16133?page=com.atlassian.jira.plugi...
]
Steven Hawkins commented on 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.
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
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