[jboss-jira] [JBoss JIRA] Reopened: (JBREM-574) Write SSL info for virtual sockets and server sockets in toString()
[ http://jira.jboss.com/jira/browse/JBREM-574?page=all ]
Ron Sigal reopened JBREM-574:
-----------------------------
This issue was opened because log statements that used to give the cipher suite of an
underlying sockets are now indicating a default cipher suite instead of the actual cipher
suite. The toString() methods of the virtual socket and virtual server socket methods
were altered, but the problem, it turns out, lies in MultiplexingManager. In an attempt
to speed up log statements, the description of the underlying socket is stored during the
call the setup() and used thereafter in log statements. However, in the case of SSL
sockets, the descriptions isn't fully created until the handshake has completed.
Write SSL info for virtual sockets and server sockets in toString()
-------------------------------------------------------------------
Key: JBREM-574
URL: http://jira.jboss.com/jira/browse/JBREM-574
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.GA (Boon)
Reporter: Ron Sigal
Assigned To: Tom Elrod
Priority: Minor
Fix For: 2.0.0.GA (Boon)
The current toString() methods do not indicate if a virtual socket or server socket is an
SSL entity.
--
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