APAR status
Closed as program error.
Error description
When a message flow is deployed with the Workload Management (WLM) property processingTimeoutSec set to a value greater than zero and additional instances for the flow is also greater than zero, the integration server may abend when the message flow is run under heavy load. The abend stacks may not all be consistent, but some may be similar to the following: malloc_buckets [] prime_pool_mt [] <no name available> (libicuuc.so) <no name available> (libicuuc.so) <no name available> (libicuuc.so) <no name available> (libicuuc.so) __ct__15ImbConverterCPPFUii (libCommonServices.a.so) __ct__10ImbMqCharvFRC10ImbWstringi (libMessageServices.a.so) putToTopic__11ImbMqHelperFRC9ImbBufferbPCciT4 (libMessageServices.a.so) publishMonitoringEventXMLMessage__20ImbWlmEventWriterXMLFP16ImbT hreadContextR9ImbBufferRC10ImbWstringbN24 (libMessageServices.a.so) writeMonitoringEventXML__20ImbWlmEventWriterXMLFRC18ImbMonitorin gEventb10ImbWstring (libMessageServices.a.so) publishNotificationEvent__18ImbWlmActionCurfewFRC10ImbWstringlT2 T1 (libMessageServices.a.so) comingIn__19ImbWlmThreadContextFv (libMessageServices.a.so) comingIn__18ImbWlmActionCurfewFv (libMessageServices.a.so) endGathering__14ImbWlmGathererFRC15ImbDataFlowNode (libMessageServices.a.so) run__18ImbCommonInputNodeFP11ImbOsThread (libMQLibrary.a.so) malloc_buckets [] malloc_common@AF103_86 [] _Fancy_malloc__FUl [/usr/lib/libC.a(ansicore_64.o)] init_pres__FUl [/usr/lib/libC.a(ansicore_64.o)] getSMFTFromPool__19ImbDataFlowSMFTPoolFRC15ImbDataFlowNode (libMessageServices.a.so) getNewSmftFromSet__13ImbWlmSMFTSetFRC15ImbDataFlowNode7ImbDate7I mbTime (libMessageServices.a.so) startInputNodeStats__14ImbWlmGathererFRC15ImbDataFlowNode (libMessageServices.a.so) startGathering__14ImbWlmGathererFRC15ImbDataFlowNodei (libMessageServices.a.so) run__18ImbCommonInputNodeFP11ImbOsThread (libMQLibrary.a.so) free_buckets [ ] free_common [ ] <no name available> (libicuuc.so) <no name available> (libicuuc.so) __dt__15ImbConverterCPPFv (libCommonServices.a.so) publishNotificationEvent__18ImbWlmActionCurfewFRC10ImbWstringlT2 T1 (libMessageServices.a.so) comingIn__19ImbWlmThreadContextFv (libMessageServices.a.so) comingIn__18ImbWlmActionCurfewFv (libMessageServices.a.so) endGathering__14ImbWlmGathererFRC15ImbDataFlowNode (libMessageServices.a.so) run__18ImbCommonInputNodeFP11ImbOsThread (libMQLibrary.a.so) Additional Symptom(s) Search Keyword(s):WLM, TimeoutSec, ADDITIONAL INSTANCES
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus v9 and v10 and IBM App Connect Enterprise v11 who are using Workload Management (WLM). Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When a message flow is deployed with the Workload Management (WLM) property processingTimeoutSec set to a value greater than zero and additional instances for the flow is also greater than zero, the integration server might abend when the message flow is run under heavy load. The abend stacks may not all be consistent, but some may be similar to the following: malloc_buckets [] prime_pool_mt [] <no name available> (libicuuc.so) <no name available> (libicuuc.so) <no name available> (libicuuc.so) <no name available> (libicuuc.so) __ct__15ImbConverterCPPFUii (libCommonServices.a.so) __ct__10ImbMqCharvFRC10ImbWstringi (libMessageServices.a.so) putToTopic__11ImbMqHelperFRC9ImbBufferbPCciT4 (libMessageServices.a.so) publishMonitoringEventXMLMessage__20ImbWlmEventWriterXMLFP16ImbT hreadContextR9ImbBufferRC10ImbWstringbN24 (libMessageServices.a.so) writeMonitoringEventXML__20ImbWlmEventWriterXMLFRC18ImbMonitorin gEventb10ImbWstring (libMessageServices.a.so) publishNotificationEvent__18ImbWlmActionCurfewFRC10ImbWstringlT2 T1 (libMessageServices.a.so) comingIn__19ImbWlmThreadContextFv (libMessageServices.a.so) comingIn__18ImbWlmActionCurfewFv (libMessageServices.a.so) endGathering__14ImbWlmGathererFRC15ImbDataFlowNode (libMessageServices.a.so) run__18ImbCommonInputNodeFP11ImbOsThread (libMQLibrary.a.so) malloc_buckets [] malloc_common@AF103_86 [] _Fancy_malloc__FUl [/usr/lib/libC.a(ansicore_64.o)] init_pres__FUl [/usr/lib/libC.a(ansicore_64.o)] getSMFTFromPool__19ImbDataFlowSMFTPoolFRC15ImbDataFlowNode (libMessageServices.a.so) getNewSmftFromSet__13ImbWlmSMFTSetFRC15ImbDataFlowNode7ImbDate7I mbTime (libMessageServices.a.so) startInputNodeStats__14ImbWlmGathererFRC15ImbDataFlowNode (libMessageServices.a.so) startGathering__14ImbWlmGathererFRC15ImbDataFlowNodei (libMessageServices.a.so) run__18ImbCommonInputNodeFP11ImbOsThread (libMQLibrary.a.so) free_buckets [ ] free_common [ ] <no name available> (libicuuc.so) <no name available> (libicuuc.so) __dt__15ImbConverterCPPFv (libCommonServices.a.so) publishNotificationEvent__18ImbWlmActionCurfewFRC10ImbWstringlT2 T1 (libMessageServices.a.so) comingIn__19ImbWlmThreadContextFv (libMessageServices.a.so) comingIn__18ImbWlmActionCurfewFv (libMessageServices.a.so) endGathering__14ImbWlmGathererFRC15ImbDataFlowNode (libMessageServices.a.so) run__18ImbCommonInputNodeFP11ImbOsThread (libMQLibrary.a.so)
Problem conclusion
The product no longer abends when multiple threads for the same message flow attempt to publish WLM notification events. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.16 v11.0 11.0.0.4 v9.0 9.0.0.11 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
IT24608
Reported component name
INTEGRATION BUS
Reported component ID
5724J0530
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-04-04
Closed date
2019-04-17
Last modified date
2019-04-17
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
INTEGRATION BUS
Fixed component ID
5724J0530
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
17 April 2019