PM41732: A SLOW MEMORY LEAK, WHICH COULD LEAD TO AN OUT OF MEMORY EXCEPTION, WHEN APPLICATIONS ARE REPEATEDLY STOPPED AND STARTED.

8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• The XML code was sometimes holding onto disposed classloaders,
  preventing memory from being reclaimed.  When applications
  were repeatedly stopped and started, this could eventually
  lead to an Out of Memory Exception.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the XML API for IBM WebSphere      *
  *                  Application Server V8.0                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: An Out of Memory Exception might        *
  *                      occur when installing, starting,        *
  *                      stopping and uninstalling applications. *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When running an SCA/OSGi application that is repeatedly
  installed, started, stopped and uninstalled, an
  OutOfMemoryException may occur.
  
  Here is a sample heapdump that was
  collected during a stress test:
  
  503,952 (0%) [56] 23 class
  com/ibm/xml/xci/internal/util/resources/XSDG
  rammarResource 0x333871c0
  502,904 (0%) [24] 1 java/util/Stack
  0x33d08be8
   502,880 (0%) [104] 1 array of
  java/lang/Object 0x33d111d0
    502,776 (0%) [32] 1
  java/lang/ref/SoftReference 0x3f5bdb98
     502,744 (0%) [40] 6
  com/ibm/xml/xml4j/internal/s1/parsers/XMLGra
  mmarPreparser 0x33d1c318
      380,800 (0%) [40] 1
  java/util/Hashtable 0x33d2f3c8
      98,968 (0%) [24] 2
  com/ibm/xml/xci/internal/util/resources/XSDG
  rammarResource$SchemaResourceResolver
  0x3f5b7168
       98,752 (0%) [40] 1 java/util/HashMap
  0x3f5cff10
        98,712 (0%) [152] 4 array of
  java/util/HashMap$Entry 0x3f7686f0
         98,488 (0%) [24] 3
  java/util/HashMap$Entry 0x3f787820
          98,456 (0%) [24] 2
  java/util/HashMap$Entry 0x3f810308
           98,432 (0%) [88] 16
  com/ibm/xml/sdo/helper/HelperContextImpl
  0x3f5cf778
            49,464 (0%) [32] 5
  com/ibm/xml/sdo/helper/XSDHelperImpl
  0x3f648348
            43,944 (0%) [200] 46
  com/ibm/xml/sdo/helper/TypeHelperImpl
  0x3f655748
            3,632 (0%) [64] 9
  com/ibm/xml/xci/SessionContext 0x3f767f18
             12,440 (0%) [152] 12
  com/ibm/ws/classloader/CompoundClassLoader
  0x339e2818
  
  
  
  503,952 (0%) [56] 23 class
  com/ibm/xml/xci/internal/util/resources/XSDG
  rammarResource 0x333871c0
  502,904 (0%) [24] 1 java/util/Stack
  0x33d08be8
   502,880 (0%) [104] 1 array of
  java/lang/Object 0x33d111d0
    502,776 (0%) [32] 1
  java/lang/ref/SoftReference 0x3f5bdb98
     502,744 (0%) [40] 6
  com/ibm/xml/xml4j/internal/s1/parsers/XMLGra
  mmarPreparser 0x33d1c318
      380,800 (0%) [40] 1
  java/util/Hashtable 0x33d2f3c8
      98,968 (0%) [24] 2
  com/ibm/xml/xci/internal/util/resources/XSDG
  rammarResource$SchemaResourceResolver
  0x3f5b7168
       98,752 (0%) [40] 1 java/util/HashMap
  0x3f5cff10
        98,712 (0%) [152] 4 array of
  java/util/HashMap$Entry 0x3f7686f0
         98,488 (0%) [24] 3
  java/util/HashMap$Entry 0x3f787820
          98,456 (0%) [24] 2
  java/util/HashMap$Entry 0x3f810308
           98,432 (0%) [88] 16
  com/ibm/xml/sdo/helper/HelperContextImpl
  0x3f5cf778
            12,440 (0%) [152] 12
  com/ibm/ws/classloader/CompoundClassLoader
  0x339e2818
  

Problem conclusion

• Heap dump analysis showed that disposed classloaders were held
  by classes in the XML code.  The solution was to modify the
  data structures that were holding these classloaders, to
  enable them to be reclaimed.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.1.  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:

  PM36429

• 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

• R800 PSY