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

Enhance client-side error reporting so a misspelled truststore file name required by SSL can be easily spotted -------------------------------------------------------------------------------------------------------------- Key: JBREM-970 URL: http://jira.jboss.com/jira/browse/JBREM-970 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public(Everyone can see) Affects Versions: 2.4.0.CR2 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor Fix For: 2.4.0.GA 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)