PM39161: SCA CLASSLOADERS RETAINED IN MEMORY AFTER BLA STOP WHEN USING BINDING.WS

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

• Product Release and Version Information: WebSphere Application
  Server Base Version 7.0 with Feature Pack for Service Component
  Architecture (SCA) V1.0.1.
  
  Problem Desciption:
  
  SCA Classloaders retained in memory after business-level
  application (BLA) stop when using binding.ws
  

Local fix

• Local Fix/Work Around: None
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All IBM WebSphere Application Server v7     *
  *                  Feature Pack for Service Component          *
  *                  Architecture (SCA) users.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: SCAClassLoaders are retained in         *
  *                      memory after SCA Applications (BLA)     *
  *                      using binding.ws are stopped.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  After BLA stop the following issues cause the SCA class loaders
  to be retained in memory:
  
  1) References to SCAClassLoaders are not removed from
  org.eclipse.emf.ecore.impl.EPackageRegistryImpl during stop.
  
  2) com.ibm.ws.runtime.metadata.MetaData for SCA dynamically
  generated EARs is not removed when the application stops.
  
  3) org.apache.tuscany.sca.core.invocation.MessageImpl remains
  set on ThreadContext after stop.
  
  4) JAXBContexts no longer referenced by the application remain
  in the JAXBContextCache pool after stop.
  
  5) org.apache.tuscany.sca.interfacedef.java.
  jaxwsGeneratedClassLoader retained in JAXBContextCache.
  

Problem conclusion

• The Feature Pack for SCA code improved memory clean up so SCA
  ClassLoaders are not retained after applications (BLA) are
  stopped.
  
  The fix for APAR PM36358 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

Comments

APAR Information

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

  PM36358

• 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