-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: 5.0, 5.0u4, 5.0u5, 5.0u6
-
Component/s: core-libs
-
b73
-
generic, x86, sparc
-
linux, linux_2.6, linux_redhat_3.0, solaris_10
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2134804 | 5.0u8 | Dmitriy Samersoff | P4 | Resolved | Fixed | b01 |
The customer is getting following 3 errors at SocketChannel.close processing.
Case1: SIGSEGV occurs and VM crashes.
(See hs_err_pid14024.log, but core was not generated.)
Case2: "IOException: No such file or directory" occurs.
Case3: "IOException: Thread signal failed" occurs
Case1: SIGSEGV occurs and VM crashes.
(See hs_err_pid14024.log, but core was not generated.)
Case2: "IOException: No such file or directory" occurs.
Case3: "IOException: Thread signal failed" occurs
- backported by
-
JDK-2134804 IOException/SIGSEGV occurs during SocketChannel.close processing.
-
- Resolved
-
- duplicates
-
JDK-6445262 Need analysis on nio error
-
- Closed
-
-
JDK-6691969 Workaround Bugzilla Bug 169995 - Crash running pthread_kill on dead thread
-
- Closed
-
- relates to
-
JDK-6419424 (ch) test/java/nio/channels/AsyncCloseAndInterrupt.java fails in 5.0u8 and mustang (linux only)
-
- Resolved
-
-
JDK-2137628 (ch) test/java/nio/channels/AsyncCloseAndInterrupt.java fails in 5.0u8 and mustang (linux only)
-
- Resolved
-