APAR status
Closed as program error.
Error description
When using the FileOutput node, a Java deadlock can occur between the message flow thread, as it closes a file, and a worker thread that closes any leftover files. This causes the message flow to hang. If a javacore is generated during the hang, a deadlock similar to the following is reported: 1LKDEADLOCK Deadlock detected !!! NULL --------------------- NULL 2LKDEADLOCKTHR Thread "Thread-19" (0x000000005056B400) 3LKDEADLOCKWTR is waiting for: 4LKDEADLOCKMON sys_mon_t:0x00000001176C15A8 infl_mon_t: 0x00000001176C15F0: 4LKDEADLOCKOBJ com/ibm/broker/flowgroupfiles/FlowGroupFilePool@0x000000004036BB 28 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "FlowGroupFilePool file close daemon" (0x0000000050501E00) 3LKDEADLOCKWTR which is waiting for: 4LKDEADLOCKMON sys_mon_t:0x00000001176C1D88 infl_mon_t: 0x00000001176C1DD0: 4LKDEADLOCKOBJ com/ibm/broker/flowgroupfiles/FlowGroupFile@0x000000004F8DD3F0 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "Thread-19" (0x000000005056B400) This deadlock is more likely to occur when running with additional instances, or if closure of the files by the flow thread is delayed - for example, if there is a large number of files being transferred to a remote system over FTP.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus v9.0.0.3 and above, or IBM Integration Bus v10. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When using the FileOutput node, a Java deadlock can occur between the message flow thread, as it closes a file, and a worker thread that closes any leftover files. This causes the message flow to hang. If a javacore is generated during the hang, a deadlock similar to the following is reported: 1LKDEADLOCK Deadlock detected !!! NULL --------------------- NULL 2LKDEADLOCKTHR Thread "Thread-19" (0x000000005056B400) 3LKDEADLOCKWTR is waiting for: 4LKDEADLOCKMON sys_mon_t:0x00000001176C15A8 infl_mon_t: 0x00000001176C15F0: 4LKDEADLOCKOBJ com/ibm/broker/flowgroupfiles/FlowGroupFilePool@0x000000004036BB 28 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "FlowGroupFilePool file close daemon" (0x0000000050501E00) 3LKDEADLOCKWTR which is waiting for: 4LKDEADLOCKMON sys_mon_t:0x00000001176C1D88 infl_mon_t: 0x00000001176C1DD0: 4LKDEADLOCKOBJ com/ibm/broker/flowgroupfiles/FlowGroupFile@0x000000004F8DD3F0 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "Thread-19" (0x000000005056B400) This deadlock is more likely to occur when running with additional instances, or if closure of the files by the flow thread is delayed - for example, if there's a large number of files being transferred to a remote system over FTP. 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 product now ensures that Java locks are obtained in a different sequence, such that the deadlock described in this APAR cannot occur. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.0 9.0.0.5 v10.0 10.0.0.2 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
IT10092
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
2015-07-17
Closed date
2015-09-13
Last modified date
2015-09-13
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
R900 PSY
UP
[{"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:
23 March 2020