Details
-
Bug
-
Resolution: Fixed
-
P4
-
7
-
b38
-
generic
-
generic
-
Not verified
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2222445 | 7-pool | Xuelei Fan | P5 | Closed | Won't Fix | |
JDK-8175444 | openjdk7u | Xuelei Fan | P4 | Resolved | Fixed | master |
Description
Do you really need the double synchronization here (that is, the two
synchronizedMap()s and the synchronized block in the constructor)? The
only place you're using it is exclusively in the constructor or it's
callers, so just the one lock should be sufficient. I think you can
remove the SynchronizedMap. -- Bradford Wetmore
synchronizedMap()s and the synchronized block in the constructor)? The
only place you're using it is exclusively in the constructor or it's
callers, so just the one lock should be sufficient. I think you can
remove the SynchronizedMap. -- Bradford Wetmore
Attachments
Issue Links
- backported by
-
JDK-8175444 synchronizing handshaking hash.
-
- Resolved
-
-
JDK-2222445 synchronizing handshaking hash.
-
- Closed
-