| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8048416 | 8u25 | Jonathan Lu | P4 | Resolved | Fixed | b05 |
| JDK-8046332 | 8u20 | Jonathan Lu | P4 | Resolved | Fixed | b20 |
| JDK-8053674 | emb-8u26 | Jonathan Lu | P4 | Resolved | Fixed | b17 |
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."
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."
- backported by
-
JDK-8046332 Behavior difference when connect() is interrupted by signal on AIX
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-