IT04219: WEBSPHERE MQ MFT 7.5: AGENT TRACE CAN NOT BE TURNED OFF COMPLETELY USING FTESETAGENTTRACELEVEL

APAR status

• Closed as program error.

Error description

• The customer attempted to collect trace using the
  fteSetAgentTraceLevel command, but when they turned the trace
  off, information was still being written to the trace file.
  
  The problem can be recreated by following these steps:
  
  1) Start an MFT Agent
  2) Start trace using the following command:
   fteSetAgentTraceLevel -traceAgent com.ibm.wmqfte=
  3) Stop trace after 10 minutes using the following command:
   fteSetAgentTraceLevel -traceAgent com.ibm.wmqfte=off
  
  Once trace is stopped (Step 3), the trace file continues to
  have information written to it, and this continues until the
  agent is stopped.
  
  Managed File Transfer uses classes from Java MQ Interface which
  are traced along with the classes from Managed File Transfer.
  Once the trace has been stopped using the fteSetAgentTraceLevel
  command, the Managed File Transfer classes do stop being
  traced. However, the Java MQ Interface classes continue to be
  traced. This is the cause of the growing trace file after trace
  has been stopped.
  
  This is unexpected behaviour as the tracing should have been
  stopped.
  

Local fix

• Restart the agent.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  The issue affect users of the WebSphere MQ V7.5 and V8.0 Managed
  File Transfer component.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Trace can be collected for WebSphere MQ Managed File Transfer
  by:
  - Dynamically setting the agent trace level using the
  fteSetAgentTraceLevel command
  - Changing the level of logger trace by using
  fteSetLoggerTraceLevel
  - Tracing any fte commands using the -trace parameter
  - And configuring an agent to start with trace enabled, setting
  trace properties in agent.properties.
  
  When collecting the trace, the trace file is populated as
  expected. However, once the trace is turned off, the lock on the
  trace file is not released and Java MQ Interface(Jmqi) trace
  points continue to be written to the file.
  

Problem conclusion

• The WebSphere MQ Managed File Transfer component has been
  updated so that, if the trace for the agent or command has been
  turned off, the Java MQ Interface(Jmqi) tracing is also turned
  off. This allows the release of the lock on the trace output
  file and no further tracing is added to the output.
  
  The Java MQ Interface tracing can be useful for diagnostics.
  However, the native MQ calls are traced whether the trace level
  for Java MQ Interface(Jmqi) has been specified or not. This has
  been addressed in APAR IT04776.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.5       7.5.0.6
  v8.0       8.0.0.3
  
  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 MFT

• Fixed component ID

  5724H7242

Applicable component levels

• R750 PSY

     UP