PM80728: OUTOFMEMORYERROR DUE TO CLASSLOADER LEAK IN JAX-WS RUNTIME

7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Starting and stopping an application that uses JAX-WS clients
  from within a WebSphere Application Server over time, may
  experience an OutOfMemory due to an accumulation of objects
  in DescriptionFactoryImpl.
  

Local fix

• Application server restart after new deployments.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server using JAX-WS clients from within     *
  *                  WebSphere Application Server invoking       *
  *                  aixs2 service                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Over time, OutOfMemory happens after    *
  *                      starting and stopping JAX-WS            *
  *                      app which uses a client invoking        *
  *                      axis2                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Over time, environments which use JAX-WS clients from within a
  WebSphere Application Server invoking axis2 service may
  experience an OutOfMemory due to an accumulation of Axis2
  ConfigurationContext objects in DescriptionFactoryImpl after
  starting and stopping client applications for many times. It
  should be 1:1 relation between J2EE modules and axis2
  ConfigurationContexts, but the JAX-WS runtime does not remove
  the entries for the ConfigurationContext when the
  corresponding module is stopped. If the application starts
  again, WebServices Engine would create a new
  ConfigurationContext which means the old one is useless but it
  truly exsits in HashTable cache.
  You may get the exceptions:
  Exception in thread "Thread-10" java.lang.OutOfMemoryError
  at
  com.ibm.ws.management.connector.soap.SOAPConnectorClient.handleA
  dminFaul
  t(SOAPConnectorClient.java:935)
  at
  com.ibm.ws.management.connector.soap.SOAPConnectorClient.invokeT
  emplateO
  nce(SOAPConnectorClient.java:903)
  ......
  

Problem conclusion

• Logic is added when a JAX-WS WebServices client application is
  stopped, WebServices Engine will clear corresponding service
  description cache (Axis2 ConfigurationContext) created by
  DescriptionFactoryImpl.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 7.0.0.29, 8.0.0.7 and the fix pack after 8.5.0.2.
  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R700 PSY

     UP

• R800 PSY

     UP

• R850 PSY

     UP