IT15521: Memory leak in managed .NET application as a result of MQRC_CONNECTION_BROKEN (2009) situation

WebSphere MQ File Transfer Edition V7.0 Fix Pack 7.0.4.6

APAR status

• Closed as program error.

Error description

• When the logTransferRecovery agent property is set to true
  (which is the default value) diagnostic messages are reported in
  the agent's event log when a transfer enters recovery
  processing.  These log messages have the identifiers:
  
    - BFGTR0062I
    - BFGTR0063I
    - BFGTR0067I
    - BFGTR0068I
  
  For example:
  
  BFGTR0068I: Transfer ID:
  414d51204d465438305f514d4752202082e6355720004f03 entering
  recovery, immediately, due to recoverable error: BFGTR0064I: The
  transfer sender timed out waiting for a response from the
  transfer receiver.
  
  These diagnostic log messages contain the transfer identifier
  for transfer that has entered recovery and the reason why.
  However it does not contain the name of the partner agent for
  this transfer.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of:
  
    - WebSphere MQ File Transfer Edition
    - WebSphere MQ Managed File Transfer
    - IBM MQ Managed File Transfer
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When a transfer entered recovery on an agent and a diagnostic
  message was written to the agent's event log file, it was not
  possible to tell from the log message written what the name of
  the partner agent was for the transfer.
  

Problem conclusion

• This APAR updates the agent event log diagnostic messages with
  identifiers:
  
    - BFGTR0062I
    - BFGTR0063I
    - BFGTR0067I
    - BFGTR0068I
  
  to include the partner agent name.  For example:
  
  BFGTR0068I: Transfer ID:
  414d51204d465438305f514d4752202082e6355720004f03 with partner
  agent AGENT2 is entering recovery, immediately, due to
  recoverable error: BFGTR0064I: The transfer sender timed out
  waiting for a response from the transfer receiver.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.0       7.0.4.6
  v7.5       7.5.0.8
  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 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