APAR status
Closed as program error.
Error description
After upgrading to MQ 8.0.0.5, an Managed File Transfer agent that is configured to run as a Windows service is is unable to start and reports errors similar to the ones below: BFGUE0030E: The agent cannot continue because the user exit class 'myExit' referenced by property 'destinationTransferEndExitClasses' does not implement the required interface type of 'com.ibm.wmqfte.exitroutine.api.DestinationTransferEndExit'. BFGUE0002E: Internal error: Attempt to use User exit before initialized. BFGUT0002E: An internal error has occurred. Product failure data was captured in file "FFDC.FTE.20160811180351568.2052973116764472230.log". BFGPR0067E: An error occurred when processing the contents of a credentials file. File path C:\Users\TEST\MQMFTCredentials.xml. Reported error: BFGPR0094E: Internal error: Attempted to invoke method com.ibm.wmqfte.io.FTELocalFileFactory.getInstance() with C:\Users\TEST\MQMFTCredentials.xml in the IO component has failed with BFGUE0002E: Internal error: Attempt to use User exit before initialised. The agent also generates an FDC containing information similar to the information show below: Class: com.ibm.wmqfte.utils.CredentialsFileHelper Method: <init> Probe: FFDC_001 Cause: java.lang.Exception: BFGPR0094E: Internal error: Attempted to invoke method com.ibm.wmqfte.io.FTELocalFileFactory.getInstance() with C:\Users\TEST\MQMFTCredentials.xml in the IO component has failed with BFGUE0002E: Internal error: Attempt to use User exit before initialised.
Local fix
To work around this issue, run the fteModifyAgent command for the affected agent.
Problem summary
**************************************************************** USERS AFFECTED: This issue affects two categories of user: Category 1: --------------- Users of: - The MQ V8.0.0.5 Managed File Transfer component who have created agents using the MQ V8.0.0.4 Managed File Transfer component (or earlier), where the agents are configured to: - Run as a Windows service. - And use one or more user exits. Category 1: --------------- Users of: - The MQ V8 Managed File Transfer component - The MQ V9 Long Term Support Release (LTSR) Managed File Transfer component who have agents that have been configured to use one or more user exits. Platforms affected: Windows **************************************************************** PROBLEM DESCRIPTION: When using the MQ V8.0.0.4 (or earlier) Managed File Transfer component, agents that are configured to run as a Windows service have a CLASSPATH which includes the JAR file com.ibm.wmqfte.exitroutines.api.jar. In this version of the MQ Managed File Transfer component, this JAR file contains all of the interfaces and classes required to use user exits. As a result of the changes for APAR IT08210, this JAR file was changed to be empty and the interfaces and classes that it contained were moved to a new JAR file, called com.ibm.wmqfte.exitroutines.api.base.jar. The APAR ensured that any new agents that were configured to run as a Windows service, or any existing agents running as a Windows service who had their configuration changed by running the fteMigrateAgent command, would have the new JAR file added to their CLASSPATH. However, it did not take into account any existing agents that were running as a Windows service who had not had their configuration changed by running fteMigrateAgent. This meant that, when an MQ Managed File Transfer installation was upgraded to the V8.0.0.5 level (which included the fix for IT08210), these agents would load the empty JAR file com.ibm.wmqfte.exitroutines.api.jar. Because the JAR file was empty, the agent was unable to find the interfaces required to load the user exits, which caused it to report the following error when it started up: BFGUE0030E: The agent cannot continue because the user exit class <class name>' referenced by property '<agent property name>' does not implement the required interface type of '<exit interface name>'. After failing to load the user exits, the agent would carry on and try to initialise any MQ credentials that it might have been configured to use. In order to access the credential information from the MQMFTCredentials.xml file, the agent attempted to use an internal exit. However, because the user exits had failed to be loaded slightly earlier during the agent's initialization, the credentials file could not be loaded. This caused the agent to generate an FDC and report the error: BFGPR0067E: An error occurred when processing the contents of a credentials file. File path <Path to MQMFTCredentials.xml>. Reported error: BFGPR0094E: Internal error: Attempted to invoke method com.ibm.wmqfte.io.FTELocalFileFactory.getInstance() with <Path to MQMFTCredentials.xml> in the IO component has failed with BFGUE0002E: Internal error: Attempt to use User exit before initialised.
Problem conclusion
There are two parts to the fix for this APAR: Part 1: -------- Firstly, the MANIFEST.MF for the empty JAR file com.ibm.wmqfte.exitroutines.api.jar has been updated to include the following entry: Class-Path: com.ibm.wmqfte.exitroutines.api.base.jar This will ensure that the empty JAR file will implicitly load the JAR file com.ibm.wmqfte.exitroutines.api.base.jar which contains the interfaces and classes required to use user exits. Note that this part of the APAR is only applicable to MQ V8.0.0.4 Managed File Transfer agents. Part 2: -------- The second part of this change is to ensure that the agent does not attempt to load the MQMFTCredentials.xml file if the user exits could not be initialized. This prevents the agent from generating the FDC. This part of the APAR is applicable to both MQ V8 and V9 Long Term Support Release Managed File Transfer agents. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.6 v9.0 CD 9.0.1 v9.0 LTS 9.0.0.1 The latest available FTE maintenance can be obtained from 'Fix List for WebSphere MQ File Transfer Edition 7.0' http://www-01.ibm.com/support/docview.wss?uid=swg27015313 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
IT16734
Reported component name
WMQ MFT V8.0
Reported component ID
5724H7252
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-08-24
Closed date
2016-09-30
Last modified date
2017-06-01
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
WMQ MFT V8.0
Fixed component ID
5724H7252
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 June 2017