IT03931: DATAPOWER MIGHT INTERMITTENTLY FAIL TO PARSE DATA FROM THE DOCUMENT CACHE WHEN CONSTANTLY AT MAXIMUM XML NAME LIMIT

Fix packs for DataPower XML Security Gateway version 6.0
Fix packs for DataPower B2B Appliance version 6.0
Fix packs for DataPower Integration Appliance version 6.0
Fix packs for DataPower Low Latency Appliance version 6.0
Fix packs for DataPower Service Gateway version 6.0
Fix packs for DataPower Service Gateway version 6.0.1
Fix packs for DataPower B2B Appliance version 6.0.1
Fix packs for DataPower Integration Appliance version 6.0.1
Fix packs for DataPower Service Gateway version 7.0
Fix packs for DataPower B2B Appliance version 7.0
Fix packs for DataPower Integration Appliance version 7.0

APAR status

• Closed as program error.

Error description

• There is a hard limit of XML Names usage on DataPower set at
  65535.  Users can set a warning in the throttle settings
  (Administration>Device>Throttle Settings) which will establish
  the threshold of minimal available XML Names (in percent), for
  any of the three types of XML Names. As this threshold is
  approached, the system attempts to free unused XML Name
  resources, so that this threshold is never reached.
  
  DataPower will begin garbage collection early enough
  to attempt to complete garbage collection before the
  specified threshold. If the threshold is continuously being
  met, this will put DataPower in a state of constant garbage
  collection.
  
  
  In this state of constant garbage collection, DataPower might
  intermittently fail to parse documents stored in the document
  cache.
  
  When in this state, users will see error messages in their logs
  such as:
  
  throttle(Throttler): tid(36647565): The XML Name count is high,
  and the system is working on freeing some of them, but has not
  completed yet. (2)
  

Local fix

• The immediate workaround could be to move the XML Names
  threshold lower until constant garbage collection stops.
  
  The next recommendation is to disable any unused domains, save
  config,  shutdown reload to decrease the XML Name footprint by
  the configuration.
  
  The long term solutions is to:
  
    a) Optimize configuration's XML Names footprint by removing
  any  extraneous services, redundant schema/wsdls, etc.
    b) Separate Services across appliances to better utilize XML
  Names capacity under the garbage collection threshold.
  

Problem summary

• Affected is building an XML tree in processing.
  
  If that happens exactly when an XML names freeing cycle starts,
  this can result in loss of that XML tree.
  

Problem conclusion

• Fix is available in 5.0.0.18, 6.0.0.10, 6.0.1.6, 7.0.0.3 and
  7.1.0.0.
  
  For a list of the latest fix packs available, please see:
  http://www-01.ibm.com/support/docview.wss?uid=swg21237631
  

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

  DTPWR INTGRAPL

• Fixed component ID

  DP905XI52

Applicable component levels

• R500 PSY

     UP

• R600 PSY

     UP

• R601 PSY

     UP

• R700 PSY

     UP

• R710 PSY

     UP