IV35528: IMMUTABLE FIELDS APPEAR TO BE UNINITIALIZED

APAR status

• Closed as program error.

Error description

• Error Message: Typically a NullPointerException
  .
  Stack Trace: Various stack traces are possible.  Here's a
  sample:
  java.lang.NullPointerException
   at
  com.ibm.rmi.iiop.IIOPOutputStream.<init>(IIOPOutputStream.java:1
  16)
   at
  com.ibm.rmi.iiop.ClientRequestImpl.<init>(ClientRequestImpl.java
  :135)
   at com.ibm.rmi.iiop.GIOPImpl.createRequest(GIOPImpl.java:183)
   at
  com.ibm.rmi.corba.ClientDelegate._createRequest(ClientDelegate.j
  ava:2016)
   at
  com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.ja
  va:1186)
   at
  com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.ja
  va:1278)
  .
  A field appears to be null or zero immediately after its
  constructor has finished, even though that constructor set the
  field to some non-null / non-zero value.  This can occur with
  final fields, and with private fields that are only modified in
  a constructor.
  

Local fix

• -Xjit:disableEscapeAnalysis
  

Problem summary

• The JIT compiler incorrectly concludes that an object's
  constructor won't modify one of its fields, and continues to use
  a stale value of that field after the constructor call has
  returned.
  

Problem conclusion

• This defect will be fixed in:
  7.0.0 SR4
  6.0.1 SR5
  .
  The JIT compiler was modified to avoid this problem.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  IV35548

Fix information

• Fixed component name

  JIT

• Fixed component ID

  620700124

Applicable component levels

• R260 PSY

     UP

• R600 PSY

     UP