-
Bug
-
Resolution: Fixed
-
P2
-
1.0, unknown
-
None
-
ventura
-
generic
-
generic
SSLSocketImpl has a bunch of half done synchronization efforts that
should be better handled. For example, getConnectionState()
and setConnectionState() are defined, but only used in one place.
In all but one, the private field is accessed directly.
Don't have the exact fixes, it was just something I noticed as I
tracked down the causes of 4361124.
bradford.wetmore@eng 2000-08-10
Copied from bug report 4311311 (closing as a duplicate of this one):
In the class SSLSocketImpl, the setting of the flag inHandshake and its checking are not synchronized which may cause race conditions between threads that can mess up the state machine of the SSLSocket.
Also, currently setUseClientMode is the only method that checks the value of this flag. It might also be necessary to check this flag (in a synchronized fashion) in other methods such as setEnableSessionCreation, setNeedClientAuth, and setEnabledCipherSuites.
-mdu
- duplicates
-
JDK-4311311 Improper use of inHandshake flag
- Closed