Back to bug 1014414
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Brad Maxwell | 2013-10-01 23:28:01 UTC | Link ID | JBoss Issue Tracker WFLY-2198 | |
| Brad Maxwell | 2013-10-29 02:06:54 UTC | CC | wfink | |
| Status | NEW | POST | ||
| Brad Maxwell | 2013-10-29 02:11:24 UTC | Depends On | 1024153 | |
| Brad Maxwell | 2014-01-15 08:44:14 UTC | Blocks | 1024153 | |
| Depends On | 1024153 | |||
| Brad Maxwell | 2014-01-15 08:48:41 UTC | Target Release | --- | EAP 6.3.0 |
| Brad Maxwell | 2014-01-15 08:49:15 UTC | Summary | Remote Naming throws the same exception for different causes | [GSS] (6.3.0) Remote Naming throws the same exception for different causes |
| Brad Maxwell | 2014-01-15 08:52:36 UTC | Blocks | 1053426 | |
| Jitka Kozana | 2014-01-22 08:59:48 UTC | CC | jkudrnac | |
| Kabir Khan | 2014-04-04 15:16:36 UTC | Status | POST | ON_QA |
| CC | kkhan | |||
| Target Milestone | --- | DR1 | ||
| Jan Martiska | 2014-04-09 12:58:14 UTC | Status | ON_QA | VERIFIED |
| CC | jmartisk | |||
| Scott Mumford | 2014-04-24 03:55:31 UTC | CC | smumford | |
| Doc Text | In previous versions of JBoss EAP 6 the same exception was thrown in response to a number of connection errors that could arise when a Remote Naming client failed to connect to any host. This behavior was sub-optimal as it gave users no indication of the actual error encountered for any given server. The exception thrown in all cases was: ---- javax.naming.NamingException: Failed to connect to any server. Servers tried: [remote://localhost:4447] ---- In this release the exceptions thrown align more closely to the actual cause of the failure. If the host or port details are incorrect, the following +CommunicationException+ will be thrown, indicating the connection timed-out: ---- javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [remote://localhost:4447 (Operation failed with status WAITING after 5000 MILLISECONDS), remote://localhost2:4321 (Operation failed with status WAITING after 5000 MILLISECONDS)] [Root exception is java.net.ConnectException: Operation failed with status WAITING after 5000 MILLISECONDS] ---- If one of the available servers responds, but the subsequent authentication fails, the following +AuthenticationException+ will be thrown: ---- javax.naming.AuthenticationException: Failed to connect to any server. Servers tried: [remote://localhost:4447 (Authentication failed: all available authentication mechanisms failed), remote://localhost2:4321 (Operation failed with status WAITING after 5000 MILLISECONDS)] [Root exception is javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed] ---- An appropriate message will be given for failures connecting to each server in the list. |
|||
| mark yarborough | 2014-06-28 15:37:17 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-06-28 11:37:17 UTC | |||
| Brad Maxwell | 2016-01-25 20:29:19 UTC | Link ID | Red Hat Knowledge Base (Solution) 1353403 |
Back to bug 1014414