APAR status
Closed as program error.
Error description
If a SOAPInput node is configured with identity propagation (for example, by enabling the Default Propagation security profile) and also configured for WS-Security using a Policy Set and Policy Set Bindings, then that SOAPInput node will leak at least one instance of java/lang/String for every SOAP request processed by that SOAPInput node. That java/lang/String object will point to a string with the value "SOAP". The leak will eventually lead to a performance degradation due to garbage collection overhead, and finally an OutOfMemory error occurring that will likely crash the integration server. The leak occurs as a JNI reference from C++ to the java/lang/String is not released after processing each message. Additional Symptom(s) Search Keyword(s): SOAPINTPUT node, WS-Security, Policy Set, Policy Set Bindings , Default Propagation, JNI, C++
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus and WebSphere Message Broker v8 using SOAPInput nodes with identity propagation enabled and WS-Security. Platforms affected: MultiPlatform, z/OS **************************************************************** PROBLEM DESCRIPTION: If a SOAPInput node is configured with identity propagation (for example, by enabling the Default Propagation security profile) and also configured for WS-Security using a Policy Set and Policy Set Bindings, then that SOAPInput node will leak at least one instance of java/lang/String for every SOAP request processed by that SOAPInput node. That java/lang/String object will point to a string with the value "SOAP". The leak will eventually lead to a performance degradation due to garbage collection overhead, and finally an OutOfMemory error occurring that will likely crash the integration server. The leak occurs as a JNI reference from C++ to the java/lang/String is not released after processing each message. There are a number of resource name changes between WebSphere Message Broker and IBM Integration Bus Version 9.0. For details visit http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e tools.mft.doc/bb23814_.htm
Problem conclusion
The SOAPInput node no longer leaks the JNI reference. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.5 v8.0 8.0.0.8 v9.0 9.0.0.7 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT16159
Reported component name
WEB MESSAGE BRO
Reported component ID
5724J0520
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-07-15
Closed date
2016-08-22
Last modified date
2016-08-22
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
WEB MESSAGE BRO
Fixed component ID
5724J0520
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSKM8N","label":"WebSphere Message Broker"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
22 August 2016