JDK-7091388 : Regular unexplained npe's from corba libs after system has been running for days
  • Type: Bug
  • Component: other-libs
  • Sub-Component: corba
  • Affected Version: 6,6u16
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,solaris_9
  • CPU: generic,sparc
  • Submitted: 2011-09-16
  • Updated: 2014-11-19
  • Resolved: 2011-11-15
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 Availabitlity Release.

To download the current JDK release, click here.
JDK 6 JDK 7 JDK 8
6u29-rev b22Fixed 7u4Fixed 8Fixed
Related Reports
Duplicate :  
Relates :  
Description
SHORT SUMMARY:

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.

Comments
EVALUATION Current CDRInputStream_1_0.close() method is buggy and should be modified like the glassfish corba code has been.
2011-09-16