United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-7091388 Regular unexplained npe's from corba libs after system has been running for days
JDK-7091388 : Regular unexplained npe's from corba libs after system has been running for days

Details
Type:
Bug
Submit Date:
2011-09-16
Status:
Closed
Updated Date:
2013-04-21
Project Name:
JDK
Resolved Date:
2011-11-15
Component:
other-libs
OS:
solaris_9,generic
Sub-Component:
corba
CPU:
sparc,generic
Priority:
P2
Resolution:
Fixed
Affected Versions:
6,6u16
Fixed Versions:
6u29-rev (b22)

Related Reports
Backport:
Backport:
Backport:
Backport:
Backport:
Duplicate:
Relates:

Sub Tasks

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



Hardware and Software, Engineered to Work Together