[jboss-jira] [JBoss JIRA] (WFLY-2198) Remote Naming throws the same exception for different causes

[Brad Maxwell (JIRA)]

Brad Maxwell created WFLY-2198:
----------------------------------

             Summary: Remote Naming throws the same exception for different causes
                 Key: WFLY-2198
                 URL: https://issues.jboss.org/browse/WFLY-2198
             Project: WildFly
          Issue Type: Bug
          Components: Naming
            Reporter: Brad Maxwell
            Assignee: Brad Maxwell


A generic NamingException are thrown if all of the servers specified are unreachable as well as if the user/pass are invalid and a security exception is thrown up, they both are converted into a RuntimeException and a message listing the servers it was unable to call is reported.

We should be throwing a different exception in the cases we know the cause, such as connection timeout or authentication exception. 

If all the the servers specified are not not running:
--------------------------------------------------------------------------------------------
javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://localhost:4447]
  at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213)

If one of the servers is running, but the client's username/password are incorrect
--------------------------------------------------------------------------------------------
javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://localhost:4447]
  at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:213)


--
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