Back to bug 1030104
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Brad Maxwell | 2013-11-13 22:53:36 UTC | Blocks | 1030102 | |
| Brad Maxwell | 2013-11-13 22:55:18 UTC | Blocks | 1030102 | |
| Brad Maxwell | 2013-11-21 23:04:03 UTC | Status | NEW | MODIFIED |
| Brad Maxwell | 2013-11-21 23:04:08 UTC | Blocks | 1030102 | |
| Carlo de Wolf | 2013-12-12 09:22:20 UTC | Blocks | 1040879 | |
| Brad Maxwell | 2014-01-13 14:25:16 UTC | Target Release | --- | EAP 6.2.1 |
| Blocks | 1027004 | |||
| Summary | segfault and other xnio issues running on IBM JDK on IBM-I | [GSS] (6.2.x) segfault and other xnio issues running on IBM JDK on IBM-I | ||
| Brad Maxwell | 2014-01-13 14:28:25 UTC | Depends On | 1052258 | |
| Brad Maxwell | 2014-01-13 14:31:48 UTC | Blocks | 1030102 | |
| mark yarborough | 2014-01-13 16:41:12 UTC | CC | myarboro | |
| Carlo de Wolf | 2014-01-16 15:13:39 UTC | Target Milestone | --- | CR1 |
| Scott Mumford | 2014-01-20 05:50:18 UTC | CC | smumford | |
| Vaclav Tunka | 2014-01-20 22:17:45 UTC | Status | MODIFIED | ON_QA |
| Scott Mumford | 2014-01-23 02:21:25 UTC | CC | david.lloyd | |
| Flags | needinfo?(david.lloyd) | |||
| David M. Lloyd | 2014-01-23 13:32:56 UTC | Doc Text | Cause: IBM JDKs contain NIO implementations which are optimized for usage on IBM operating systems. Our I/O layer attempts to detect and utilize these implementations. However on some operating systems (like IBM-I) these implementations actually cause a segfault. Consequence: Applications running on some IBM operating systems will segfault immediately. Fix: We detect these operating systems and fall back to a safe alternative. Result: The application server will start as expected without crashing. | |
| Flags | needinfo?(david.lloyd) | |||
| Scott Mumford | 2014-01-24 00:21:11 UTC | Doc Text | Cause: IBM JDKs contain NIO implementations which are optimized for usage on IBM operating systems. Our I/O layer attempts to detect and utilize these implementations. However on some operating systems (like IBM-I) these implementations actually cause a segfault. Consequence: Applications running on some IBM operating systems will segfault immediately. Fix: We detect these operating systems and fall back to a safe alternative. Result: The application server will start as expected without crashing. | An issue with applications running on IBM systems failing with a segmentation fault has been corrected in this release of JBoss EAP 6. The crashes were caused by NIO implementations in IBM JDKs that are optimized for usage on IBM operating systems. The I/O layer in JBoss EAP attempts to detect and utilize these implementations. However on some operating systems (like IBM-I) these implementations cause a segfault. In this release of the product, these operating systems are detected and safe fall-backs are utilized. This resolves the segmentation fault issue and the application server no longer crashes unexpectedly. |
| Jitka Kozana | 2014-01-27 11:30:50 UTC | Status | ON_QA | VERIFIED |
| CC | jkudrnac | |||
| mark yarborough | 2014-02-24 20:14:23 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-02-24 15:14:23 UTC |
Back to bug 1030104