PK68602: MEMORY LEAK WHEN THE XMLSTREAMREADER OBJECT IS NOT ALWAYS CLOSED AFTER SERIALIZATION

APAR status

• Closed as program error.

Error description

• Memory leak when the XMLStreamReader object is not
  always closed after serialization.  The heapdump shows the
  following leak suspect:
  
  java/lang/ApplicationShutdownHooks, class0x6a94f330,
  reaches:696MB),
  LEAK_ROOT
  |java/util/IdentityHashMap, object0x480278, reaches:696MB)
  |-java/lang/Object, array0x4802a0, reaches:696MB)
  |--com/ibm/ws/websvcs/transport/http/client/WAShttpAsyncResponse
  Listener
  $ShutdownThread, object0x654f28, reaches:696MB)
  |---java/lang/ThreadGroup, object0x4203b0, reaches:696MB)
  |----java/lang/Thread, array0xc30d70, reaches:696MB)
  |-----java/lang/Thread, object0x420340, reaches:695MB)
  |------java/lang/ThreadLocal$ThreadLocalMap, object0x420ff8,
  reaches:695MB)
  |-------java/lang/ThreadLocal$ThreadLocalMap$Entry,
  array0xb6cc20,
  reaches:695MB)
  |--------java/lang/ThreadLocal$ThreadLocalMap$Entry,
  object0x6ac268,
  reaches:695MB)
  |---------com/ibm/xml/xlxp/api/util/UnsynchronizedBag,
  object0x6ac208,
  reaches:695MB)
  |---------java/lang/ref/SoftReference, array0xd3cf00,
  reaches:695MB),
  

Local fix

• No work around.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V6.1 Feature Pack for Web Services   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Memory leak when the XMLStreamReader    *
  *                      object is not always closed after       *
  *                      serialization                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The memory leak happens on the client as the response is being
  processed.  The inbound response content goes from Axiom to
  SAAJ, and in so doing the code did not close the parser when
  everything was pulled out of Axiom.
  
  The heapdump shows the following leak suspect:
  
  java/lang/ApplicationShutdownHooks, class0x6a94f330,
  reaches:696MB),
  LEAK_ROOT
  |java/util/IdentityHashMap, object0x480278, reaches:696MB)
  |-java/lang/Object, array0x4802a0, reaches:696MB)
  |--com/ibm/ws/websvcs/transport/http/client/WAShttpAsyncResponse
  Listener
  $ShutdownThread, object0x654f28, reaches:696MB)
  |---java/lang/ThreadGroup, object0x4203b0, reaches:696MB)
  |----java/lang/Thread, array0xc30d70, reaches:696MB)
  |-----java/lang/Thread, object0x420340, reaches:695MB)
  |------java/lang/ThreadLocal$ThreadLocalMap, object0x420ff8,
  reaches:695MB)
  |-------java/lang/ThreadLocal$ThreadLocalMap$Entry,
  array0xb6cc20,
  reaches:695MB)
  |--------java/lang/ThreadLocal$ThreadLocalMap$Entry,
  object0x6ac268,
  reaches:695MB)
  |---------com/ibm/xml/xlxp/api/util/UnsynchronizedBag,
  object0x6ac208,
  reaches:695MB)
  |---------java/lang/ref/SoftReference, array0xd3cf00,
  reaches:695MB),
  

Problem conclusion

• The web services code was updated to correctly close all the
  parsers that it opened.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.21.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WEBSERVIC FEATU

• Fixed component ID

  5724J0850

Applicable component levels

• R610 PSY

     UP