A fix is available
APAR status
Closed as program error.
Error description
A WebSphere MQ File Transfer Edition (FTE) agent uses the Java MQI component to handle all communication with a queue manager. Certain aspects of the Java MQI can be tuned or configured through the use of Java System Properties. One such example is the: com.ibm.mq.jmqi.threadWaitTimeout property, as described in the following Technote: http://www-01.ibm.com/support/docview.wss?uid=swg21640627 For BINDINGS transport mode connections to a z/OS queue manager. Despite configuring this Java System Property with a non-default value (such as 0) on an agent's JVM, the default value of 20000 milliseconds was always used. The expectation was, when configuring this Java System Property with the value 0 (for an unlimited wait time), an exception with the WebSphere MQ reason code 2102 (MQRC_RESOURCE_PROBLEM) would not be thrown from the com.ibm.mq.jmqi.JmqiWorkerThread.syncExec(...) method. However, on busy systems, a worker thread would not become available within the default 20 second timeout period and an exception would be thrown to the agent code. This would cause the FTE agent to write an FFDC file to its logging directory and to end. The FFDC file contain contents similar to the following: Filename: /var/mqfte/fte_config/MyConfig/agents/AGENT1/logs/ffdc/FFDC.FTE. 20160204043103540.7386880136930724972.log Level: f704-7045-ZOS-FP20150728-2059 Time: 04/02/2016 04:31:03:540 GMT Thread: 20 (Timer-0) Class: com.ibm.wmqfte.monitor.management.MonitorImpl Instance: a38337e6 Method: run Probe: FFDC_002 Cause: com.ibm.wmqfte.wmqiface.WMQApiFailureException: cc=2 rc=2102 op=connect - jmqiConnect (WMQConnectionData [Queue Manager=QM01, Host=null, Port=0, Channel=null, sslConnectionData=null, standby=null, ccsid=-1, ccsidName=null, hdrCompList=null, msgCompList=null, useJavaUserName=false]) 	at com.ibm.wmqfte.wmqiface.WMQApiImpl.connect(WMQApiImpl.java:350) 	at com.ibm.wmqfte.wmqiface.WMQApiImpl.connect(WMQApiImpl.java:162) 	at com.ibm.wmqfte.monitor.management.MonitorWork.execute(MonitorWor k.java:260) 	at com.ibm.wmqfte.monitor.management.MonitorImpl.run(MonitorImpl.ja va:112) 	at com.ibm.wmqfte.monitor.management.MonitorTimerTask.run(MonitorTi merTask.java:78) 	at java.util.TimerThread.mainLoop(Timer.java:567) 	at java.util.TimerThread.run(Timer.java:517) Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2102 	at com.ibm.mq.jmqi.JmqiWorkerThread.syncExec(JmqiWorkerThread.java: 158) 	at com.ibm.mq.jmqi.local.LocalHconn.syncExec(LocalHconn.java:478) 	at com.ibm.mq.jmqi.local.LocalMQ.jmqiConnect(LocalMQ.java:8440) 	at com.ibm.wmqfte.wmqiface.WMQApiImpl.connect(WMQApiImpl.java:345)
Local fix
No Local Fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects all users of WebSphere MQ File Transfer Edition and Managed File Transfer v7.5 who set Java System Properties to tune behaviour of the Java MQI component. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The Java Message Queueing Interface (JMQI) component used by the WebSphere MQ File Transfer Edition (FTE) and Managed File Transfer (MFT) v7.5 products does not, by default, lookup tuning or configuration properties defined via Java System Properties. Therefore, when tuning properties known to the JMQI were queried, the default values would always be returned and used.
Problem conclusion
The JMQI component permits additional "property handlers" to be registered that property lookups can be delegated to. This APAR adds a property handler for the WebSphere MQ File Transfer Edition (FTE) and Managed File Transfer (MFT) v7.5 code that is registered with the JMQI. When this property handler is invoked, the product code attempts to lookup a Java System Property with the given configuration name and, if it exists, returns the corresponding value to the JMQI. For example, if the Java System Property: com.ibm.mq.jmqi.threadWaitTimeout is set, then the property will now be looked up correctly - the user configured value for the property will be used within the JMQI. This issue does not affect IBM MQ Managed File Transfer v8. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.4.6 v7.5 7.5.0.7 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
IT13140
Reported component name
WMQ FILE TRANSF
Reported component ID
5724R1000
Reported release
704
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-01-12
Closed date
2016-02-23
Last modified date
2016-02-23
APAR is sysrouted FROM one or more of the following:
PI55122
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WMQ FILE TRANSF
Fixed component ID
5724R1000
Applicable component levels
R704 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 February 2016