[jbosstools-issues] [JBoss JIRA] (JBIDE-16133) No indication that management authentication fails

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-16133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927211#comment-12927211 ] 

Steven Hawkins commented on 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.
                
> 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