JR42697: Caching of WSDL Objects Consumes Large Amount of Memory

7.5.1.0-WS-BPM-IFJR42697
Version 8.0 Refresh Pack 1 for the IBM Business Process Manager products
Version 7.5.1 Fix Pack 1 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• At runtime on the first invocation of a
  particular version of a Web Service, the WSDL model was cached
  on the versioned object.  If there were many versioned web
  service objects and the WSDL data model had been cached on
  each, this led to large amounts of memory being consumed until
  the version cache was cleared.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  7.5.0.1, 7.5.1 and 8.0 Users of BPM         *
  *                  Express, Standard and Advanced.             *
  ****************************************************************
  * PROBLEM DESCRIPTION: At runtime on the first invocation of   *
  *                      a particular version of a Web Service,  *
  *                      the WSDL model was cached on the        *
  *                      versioned object.  If there were many   *
  *                      versioned web service objects and the   *
  *                      WSDL data model had been cached on      *
  *                      each, this led to large amounts of      *
  *                      memory being consumed until the         *
  *                      version cache was cleared.              *
  ****************************************************************
  * RECOMMENDATION:  Recommended fix.                            *
  ****************************************************************
  At runtime on the first invocation of
  a particular version of a Web Service,
  the WSDL model was cached on the
  versioned object.  If there were many
  versioned web service objects and the
  WSDL data model had been cached on
  each, this led to large amounts of
  memory being consumed until the
  version cache was cleared.
  

Problem conclusion

• JR42697 was primarily for fixing a memory consumption issue,
  but it also fixed an issue relating to qualified versus
  qualified elements.
  When the XML schema used in the WSDL specifies that
  the elements should be unqualified, in some instances the
  resulting elements in the request SOAP body did not honor this
  setting.  This fix corrects situations in which the elements
  should be unqualified instead of qualified.
  
  This fix introduces a new cache for the WSDL objects that can
  be adjusted by adding a
  <wsdl-cache-size>[Integer]</wsdl-cache-size> element as a child
  of element of the <common> element.
  The cache property caches unique IDs of PO Versioned objects
  related to WSDLs.
  When a WSDL is invoked for the first time, it will generate a
  new PO and associate a unique ID. This will get cached and
  subsequent invocations of that WSDL will not generate a new PO
  Object.
  The higher the number, more the POs that will get cached so
  depending on the customer environment The wsdl-cache-size is
  denoted in numbers and represents a two to three digit value
  in normal cases. e.g. 50.
  If no value is used then it assumes a value of 25.
  
  The interim fix is available in fix central for the following
  versions:
  7.5.0.1
  7.5.1
  8.0
  It is also fixed in future fix packs and releases.
  
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  
  Install/Dependency information on 7.5.0.1:
  
  Is available in the readme.txt on FixCentral.
  When the user goes to the download files page in FixCentral the
  readme will be available with the fix package as a seperate
  download.
  
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  Install/Dependency information on 7.5.1:
  
  Is available in the readme.txt on FixCentral.
  When the user goes to the download files page in FixCentral the
  readme will be available with the fix package as a seperate
  download.
  
  
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  Install/Dependency information on 8.0:
  
  Is available in the readme.txt on FixCentral.
  When the user goes to the download files page in FixCentral the
  readme will be available with the fix package as a seperate
  download.
  

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

  BPM STANDARD

• Fixed component ID

  5725C9500

Applicable component levels