PM39182: SCA MEMORY FOOTPRINT INCREASES AFTER REPEATEDLY REDEPLOYING/RESTARTING APPLICATIONS

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

• Service Component Architecture (SCA) Memory Footprint increases
  after repeatedly redeploying/restarting implementation.osgiapp
  applications using JAXB data types.
  
  
  Details: When an SCA application using implementation.osgiapp
  stops, the JAXB data types associated with that application
  are not removed from the LRUCache in the JAXBContextCache. As
  a result, the memory footprint grows and may result in an
  OutOfMemory Exception.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All IBM WebSphere Application Server Feature*
  *                  Pack for Service Component Architecture     *
  *                  (SCA) users                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: Service Component Architecture (SCA)    *
  *                      memory footprint increases after        *
  *                      repeatedly restarting SCA               *
  *                      applications that include               *
  *                      implementation.osgiapp.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an SCA application containing an implementation
  type of "implementation.osgiapp" is stopped, a cache inside of
  the JAXBContextCache is not reaped. As a result, memory usage
  can grow larger than necessary.
  

Problem conclusion

• The Feature Pack for Service Component Architecture code was
  corrected to reap the cache used by JAXBContextCache when
  the application is stopped.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 1.0.1.13. Please refer to the Recommended Updates page
  for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Restarting the server that the SCA application is deployed to
  will reset the cache used inside JAXBContextCache.
  

Comments

APAR Information

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

  PM37754

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

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R800 PSY

     UP

• R700 PSN

     UP

• R600 PSN

     UP

• R60A PSN

     UP

• R60H PSN

     UP

• R60I PSN

     UP

• R610 PSN

     UP

• R60P PSN

     UP

• R60S PSN

     UP

• R60W PSN

     UP

• R60Z PSN

     UP

• R61A PSN

     UP

• R61H PSN

     UP

• R61I PSN

     UP

• R61P PSN

     UP

• R61S PSN

     UP

• R61W PSN

     UP

• R61Z PSN

     UP