-
Bug
-
Resolution: Fixed
-
P2
-
6, 6u16
-
b22
-
generic, sparc
-
generic, solaris_9
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2215675 | 8 | Sean Coffey | P3 | Closed | Fixed | b15 |
JDK-2215674 | 7u4 | Sean Coffey | P3 | Closed | Fixed | b02 |
JDK-2217322 | 6u32 | Sean Coffey | P2 | Closed | Fixed | b01 |
JDK-2218089 | 6u31-rev | Sean Coffey | P2 | Closed | Fixed | b21 |
JDK-2217299 | 6u30-rev | Sean Coffey | P2 | Resolved | Fixed | b21 |
Unexpected null pointers encountered during corba transactions.
INDICATORS:
stack traces as per BUGDB # 12807608
COUNTER INDICATORS:
TRIGGERS:
KNOWN WORKAROUND:
N/A
PRESENT SINCE:
N/A
HOW TO VERIFY:
No internal testcase available.
NOTES FOR SE:
This issue was produced in production site only. Cu has been helpful
in tracing down root cause. The CDROutputObject object is responsible
from the NPE.
CDRInputStream_1_0.close method will close CDROutputStream in error,
if byte buffers for input and output streams fail to be differentiated
by their HashCodes.
Fix has already been introduced to Glassfish corba and the JDK should
also have this fix.
Cu has verified the fix.
REGRESSION:
No.
- backported by
-
JDK-2217299 Regular unexplained npe's from corba libs after system has been running for days
-
- Resolved
-
-
JDK-2217322 Regular unexplained npe's from corba libs after system has been running for days
-
- Closed
-
-
JDK-2218089 Regular unexplained npe's from corba libs after system has been running for days
-
- Closed
-
-
JDK-2215674 Regular unexplained npe's from corba libs after system has been running for days
-
- Closed
-
-
JDK-2215675 Regular unexplained npe's from corba libs after system has been running for days
-
- Closed
-
- duplicates
-
JDK-6610298 NPE from JMX IIOP Connector
-
- Closed
-
- relates to
-
JDK-6384126 NPE from SharedCDRClientRequestDispatcherImpl
-
- Closed
-