IZ92148: A MEMORY LEAK RESULTS WHEN A SAXSOURCE OBJECT IS SUPPLIED ON INP UT TO A JAXP IDENTITY TRANSFORMER

APAR status

• Closed as program error.

Error description

• Error Message: OutOfMemoryError
  .
  Stack Trace: Not applicable
  .
  Not applicable
  

Local fix

• The problem can be worked around by using a StreamSource instead
  of a SAXSource to supply the input or by setting an XMLReader on
  the SAXSource object.
  

Problem summary

• As a performance optimization, if the input to JAXP identity
  Transformer comes from a StreamSource object or a SAXSource
  object that does not supply its own XMLReader, the XSLT
  processor will cache an instance of org.xml.sax.XMLReader to
  parse the input to the Transformer.  The processor will reuse
  that instance of XMLReader on the same thread, and keeps track
  of whether it is in use, and marks the XMLReader as no longer in
  use when the input has been parsed.  However, code that should
  have marked the XMLReader as no longer in use was missing when
  the input came from a SAXSource.
  As new threads were created and old threads ended, the
  XMLReaders associated with those threads were never released and
  memory usage increased until eventually an OutOfMemoryError
  would occur.
  

Problem conclusion

• This defect will be fixed in:
  6.0.0 SR9 FP2
  .
  The problem was resolved by ensuring XMLReader instances would
  always be eventually released if garbage collection needed the
  memory associated with those XMLReader instances, even if the
  code did not explicit marked the XMLReader as no longer in use.
  .
  To obtain the fix:
  Install build 20110216 or later
  

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:

Fix information

• Fixed component name

  XML/XSL

• Fixed component ID

  620700126

Applicable component levels

• R600 PSN

     UP