Brad Maxwell <bmaxwell> updated the status of jira WFLY-2198 to Coding In Progress

Verified in 6.2.2.CR2.

Attention: Brad

Please provide draft release notes text in the 'doc_text' field.

Thanks for the draft text, Brad.

Redrafted for clarity. Including the original below for reference.

Original draft:
> When a Remote Naming client tries to connect to a host with a
> username/password and it fails for one of many causes such as the host/port 
> was wrong, user/pass was wrong, etc, it always threw this exception, which 
> does not indicate what the actual cause was: 

> javax.naming.NamingException: Failed to connect to any server. Servers tried: 
> [remote://localhost:4447]

> After this fix:  It will throw a sub class of NamingException, if it failed to 
> connect to all of the possible hosts, it will throw a CommunicationException 
> and it will list the message of each server tried (which is the WAITING below, 
> meaning it waited until the connection timeout and the host didn't respond)

> When host/port is wrong

> 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 servers in the possible servers responds but then authentication 
> fails, it will throw a AuthenticationException which is again a sub class of 
> NamingException and tell you that the user/pass was wrong, again it will 
> include in the message why the other servers in the list failed also.

> When authentication issue occured
> 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]

Marking for inclusion in 6.2.2 Release Notes document.

Not sure why BZ is showing that I edited the Environment field. AFAIK, I didn't touch that field.

Huh, somehow the text from most of this ticket got copied into the Environment field. I've removed it again.