Bug 1101263 - Deadlock in SSLSocketImpl between between write and close
Summary: Deadlock in SSLSocketImpl between between write and close
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: java-1.7.0-openjdk
Version: 5.10
Hardware: Unspecified
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: jiri vanek
QA Contact: Lukáš Zachar
URL:
Whiteboard:
Depends On: 1096410
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-26 13:33 UTC by Jan Kurik
Modified: 2018-12-05 18:41 UTC (History)
12 users (show)

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.
Clone Of:
Environment:
Last Closed: 2014-05-29 10:40:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0571 0 normal SHIPPED_LIVE java-1.7.0-openjdk bug fix update 2014-05-29 14:40:35 UTC

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
Note You need to log in before you can comment on or make changes to this bug.