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)
Brad Maxwell <bmaxwell> updated the status of jira WFLY-2198 to Coding In Progress
Setting to ON_QA since fixed by upgrade
Verified with EAP 6.3.0.ER1 / jboss-remote-naming 1.0.8.Final-redhat-1
Included release note from bug 1053426 (duplicate) that was written for EAP 6.2.2 Release Notes. Marking for inclusion in the documentation.
*** Bug 1014413 has been marked as a duplicate of this bug. ***