APAR status
Closed as program error.
Error description
Managed File Transfer agent abend when starting up a Resource Monitor during agent shutdown. The abend occurs due to a java.lang.NullPointerException and an abend FDC is generated: Class: com.ibm.wmqfte.thread.FTEThread Instance: d34c8909 Method: uncaughtException Probe: ABEND_001 Cause: java.lang.NullPointerException java.lang.NullPointerException at com.ibm.wmqfte.monitor.management.MonitorPublication.getPublicat ionXML(MonitorPublication.java:94) at com.ibm.wmqfte.monitor.management.MonitorManager.startMonitor(Mo nitorManager.java:652) at com.ibm.wmqfte.monitor.management.MonitorManager.registerMonitor (MonitorManager.java:940) at com.ibm.wmqfte.monitor.management.MonitorManager.recoveryMonitor (MonitorManager.java:781) at com.ibm.wmqfte.agent.AgentRecoveryRunnable.recoverResourceMonito r(AgentRecoveryRunnable.java:851) at com.ibm.wmqfte.agent.AgentRecoveryRunnable.run(AgentRecoveryRunn able.java:225) at java.lang.Thread.run(Thread.java:785) at com.ibm.wmqfte.thread.FTEThread.run(FTEThread.java:70)
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of IBM MQ Managed File Transfer who use resource monitors. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: This problem occurred due to a timing window when an MFT agent was shutting down, and starting up a MFT resource monitor (RM) at the same time. These two operations were executed under separate threads within the agent. The shutdown thread removed the object that represented an instance of the RM, while the recovery thread tried to start the RM using the removed object. This resulted in a java.lang.NullPointerException, which caused the agent to abend.
Problem conclusion
IBM MQ Managed File Transfer has been updated so that if an MFT agent is shutting down, it will not attempt to start a Resource Monitor. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.0 LTS 9.0.0.6 v9.1 CD 9.1.1 v9.1 LTS 9.1.0.1 The latest available MQ maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT25113
Reported component name
IBM MQ BASE M/P
Reported component ID
5724H7261
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-05-21
Closed date
2018-07-18
Last modified date
2018-08-29
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
IBM MQ MFT V9.0
Fixed component ID
5724H7262
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 August 2018