A fix is available
APAR status
Closed as program error.
Error description
After configuring a WebSphere MQ File Transfer Edition agent with the following property: enableMemoryAllocationChecking=true some managed transfers entered recovery processing. When this occurred, an FFDC file was generated with following details: Class: com.ibm.wmqfte.statestore.impl.FTEStateStoreImpl Method: recoverSenderTransfer Probe: FFDC_025 Cause: null java.lang.Exception: Call stack at com.ibm.wmqfte.ras.impl.IncidentStream.<init> at com.ibm.wmqfte.ras.impl.FFDCImpl.createIncidentStream at com.ibm.wmqfte.ras.impl.FFDCImpl.ffdc at com.ibm.wmqfte.ras.impl.FFDCImpl.internalCapture at com.ibm.wmqfte.ras.FFDC.capture at com.ibm.wmqfte.statestore.impl.FTEStateStoreImpl. recoverSenderTransfer at com.ibm.wmqfte.transfer.impl.TransferSenderRunnable.run at java.lang.Thread.run at com.ibm.wmqfte.thread.FTEThread.run
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of WebSphere MQ File Transfer Edition v7.0.4 and WebSphere MQ Managed File Transfer v7.5 Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When using WebSphere MQ File Transfer Edition (FTE) V7.0.4 or WebSphere MQ Managed File Transfer v7.5, an agent may put a managed transfer into a "ResumingTransfer" state. A managed transfer can enter this state at the source agent when the agent receives a resynchronization request message from the partner, destination agent. The managed transfer is then scheduled for restart. If the managed transfer could not be restarted by the source agent, then the agent attempted to move it to a "Recovering" transfer state. However, the source agent did not contain a valid mapping that would allow the transfer state to be moved from "Resuming" to "Recovering" and, as such, an FFDC was generated.
Problem conclusion
The WebSphere MQ File Transfer Edition product code has been updated such that a source agent has a valid mapping that allows it to move a managed transfer from "Resuming" state to "Recovering" state, preventing an FFDC from being generated. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.4.6 v7.5 7.5.0.2 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
IT11545
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
2015-10-02
Closed date
2016-01-27
Last modified date
2016-01-27
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 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:
27 January 2016