IC99865: WSPOLICY DOCUMENTS REFERENCED BY WSP:POLICYREFERENCE DURING WSDL COMPILATION MIGHT NOT BE RELEASED AND CAUSE MEMORY GROWTH
Fixes are available
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
Closed as program error.
Using the WSDL-cache-policy to compile locally stored WSDL files, the resulting QRef entries might not be returned which results in memory growth. This behavior happens in firmware versions 184.108.40.206 and later.
Scenario for cause of growing QRef entries: 1) The WSDLs have WSPolicy embedded inside the WSDL. 2) The WSDLs are all local. 3) The WS Proxy has wsdl-cache-policy & matching is set to "*" Number 3 is where the problem happens. Every 30 seconds, the WS Proxy is recompiling the locally stored WSDLs and recreating all those WSPolicy objects. To work around this issue, make one of the following suggested changes: 1) Either turn off the unnecessary WSDL cache, or change the match expression to something more meaningful, such as "http://*" and increase the TTL. 2) Use the WSDL Status->refresh action to recompile the WSDLs which are stored locally. (Usage: wsdl-refresh <WSGateway> <WSDL>)
Affected is the use of WSDLs (in WSP or elsewhere). WSPolicy documents referenced by <wsp:PolicyReference> are not released during WSDL compilation causing memory growth. This causes trouble especially in case of aggressive wsdl-cache-policy settings leading to frequent WSDL recompilations.
Fix is available in 220.127.116.11, 18.104.22.168 and 22.214.171.124. For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels