[jboss-jira] [JBoss JIRA] Closed: (JBREM-912) Remove stacktrace when SSLSocketBuilder.createSSLSocketFactory() fails

[Ron Sigal (JIRA)]

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

Ron Sigal closed JBREM-912.
---------------------------

    Resolution: Done

In each method,

         log.error("Error creating SSL Socket Factory for client invoker.", e);

has been replaced by

         log.error("Error creating SSL Socket Factory for client invoker: " + e.getMessage());
         log.debug("Error creating SSL Socket Factory for client invoker.", e);

> Remove stacktrace when SSLSocketBuilder.createSSLSocketFactory() fails
> ----------------------------------------------------------------------
>
>                 Key: JBREM-912
>                 URL: http://jira.jboss.com/jira/browse/JBREM-912
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.2.0.SP4
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>            Priority: Minor
>             Fix For: 2.2.2.SP5
>
>
> Remoting is too noisy in places when org.jboss.remoting.security.SSLSocketBuilder.createSSLSocketFactory() fails.  In particular, 
>    org.jboss.remoting.transport.http.ssl.HTTPSClientInvoker.createSocketFactory()
>    org.jboss.remoting.transport.sslbisocket.BisocketClientInvoker.createSocketFactory()
>    org.jboss.remoting.transport.sslbisocket.BisocketServerInvoker.createSocketFactory()
>    org.jboss.remoting.transport.bisocket.SocketClientInvoker.createSocketFactory()
> print stacktraces at ERROR log level.  It would be better if they just printed a message at ERROR level and saved the stacktrace for DEBUG level.

-- 
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