Bug 1101263

Summary: Deadlock in SSLSocketImpl between between write and close
Product: Red Hat Enterprise Linux 5 Reporter: Jan Kurik <jkurik>
Component: java-1.7.0-openjdkAssignee: jiri vanek <jvanek>
Status: CLOSED ERRATA QA Contact: Lukáš Zachar <lzachar>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.10CC: ahughes, aph, bgollahe, cww, davjohns, dbhole, jherrman, jnevill, omajid, patrickm, pm-eus, sjavurek
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Prior to this update, an error in the SSL socket code caused the write() and close() calls to be invoked simultaneously on the same socket, but in two different threads. As a consequence, the socket entered a deadlock. With this update, a measure has been implemented to ensure that calls to close() and read() do not interfere with each other, and the deadlock no longer occurs.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-29 10:40:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1096410    
Bug Blocks:    

Description Jan Kurik 2014-05-26 13:33:26 UTC
This bug has been copied from bug #1096410 and has been proposed
to be backported to 5.10 z-stream (EUS).

Comment 7 errata-xmlrpc 2014-05-29 10:40:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0571.html