[jboss-remoting-issues] [JBoss JIRA] Updated: (JBREM-973) CLONE [JBREM-970] - Enhance client-side error reporting so a misspelled truststore file name required by SSL can be easily spotted

[Ron Sigal (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBREM-973?page=all ]

Ron Sigal updated JBREM-973:
----------------------------

        Fix Version/s: 2.2.2.SP8
                           (was: 2.4.0.GA)
    Affects Version/s: 2.2.2.SP7
                           (was: 2.4.0.CR2)

> CLONE [JBREM-970] - Enhance client-side error reporting so a misspelled truststore file name required by SSL can be easily spotted
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBREM-973
>                 URL: http://jira.jboss.com/jira/browse/JBREM-973
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.2.SP7
>            Reporter: Ovidiu Feodorov
>         Assigned To: Ovidiu Feodorov
>            Priority: Minor
>             Fix For: 2.2.2.SP8
>
>
> A misspelled client-side truststore file name causes a remoting connection to fail with a misleading error message:
> Exception in thread "main" org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [sslsocket://192.168.67.164:3874/]
>         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:530)
>         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>         [...]
> Caused by: java.net.SocketException: Socket Closed
>         at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:201)
>         at java.net.Socket.setSoTimeout(Socket.java:997)
>         at com.sun.net.ssl.internal.ssl.SSLSocketImpl.setSoTimeout(SSLSocketImpl.java:2047)
>         [...]
> There's nothing in the stacktrace hinting towards the root cause of the problem, and this could make the debugging quite laborious and time consuming.
> A welcome improvement would be to identify and loudly advertise the root cause of the problem (or at least problems related to the fact that the SSL handshake did not succeed)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira