[jboss-remoting-issues] [JBoss JIRA] Updated: (JBREM-976) CLONE [JBREM-912] - Remove stacktrace when SSLSocketBuilder.createSSLSocketFactory() fails

Ron Sigal (JIRA) jira-events at lists.jboss.org
Sat May 3 02:26:20 EDT 2008


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

Ron Sigal updated JBREM-976:
----------------------------

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

> CLONE [JBREM-912] - Remove stacktrace when SSLSocketBuilder.createSSLSocketFactory() fails
> ------------------------------------------------------------------------------------------
>
>                 Key: JBREM-976
>                 URL: http://jira.jboss.com/jira/browse/JBREM-976
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.CR2
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>            Priority: Minor
>             Fix For: 2.4.0.GA
>
>
> 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

        



More information about the jboss-remoting-issues mailing list