In previous versions of JBoss EAP, a generic `javax.naming.NamingException` was being thrown when a `java.net.ConnectException` occurred instead of the more specific `javax.naming.CommunicationException`.
This release includes a change that ensures a `javax.naming.CommunicationException` is thrown when a connection exception occurs.
`CommunicationException` is a subclass of `NamingException`, so any code that previously caught a `NamingException` will still work as expected.
Use right exception type for communication problem , javax.naming.CommunicationException should be thrown instead of javax.naming.NamingException
Brad Maxwell <email@example.com> updated the status of jira WFLY-2839 to Resolved
Customers apps (try - catch blocks) won't be affected by throwing CommunicationException instead of NamingException
Yes, originally it was a generic NamingException, this change just uses sub classes of NamingException which are more specific, so any customer who was catching the NamingException will not be affected, they will still be caught, they will just provide information about the real issue.
Verified with EAP 6.3.0.ER1 / jboss-remote-naming 1.0.8.Final-redhat-1