JDK-8043954 : Behavior difference when connect() is interrupted by signal on AIX
- Type: Bug
- Component: core-libs
- Sub-Component: java.net
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: aix
- CPU: ppc
- Submitted: 2014-05-26
- Updated: 2016-05-27
- Resolved: 2014-06-06
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 8 | JDK 9 |
|---|---|
8u20Fixed  |
9 b19Fixed |
Description
See the description of API connect() for AIX platform, http://www-01.ibm.com/support/knowledgecenter/ssw_aix_71/com.ibm.aix.commtrf2/connect.htm?lang=en The behavior is different when connect() operation got interrupted by signal. On AIX, although the connect() call can be interrupted by signal, the underlying connection will be made asynchronously, as it is described from the docs "EINTR The attempt to establish a connection was interrupted by delivery of a signal that was caught; the connection will be established asynchronously."