IC85094: WMQFTE 7.0.4: RESOURCE MONITOR ENCOUNTERS AN ERROR AND CAUSES AGENT TO TERMINATE UNEXPECTEDLY.

WebSphere MQ V7.5 Fix Pack 7.5.0.1
WebSphere MQ File Transfer Edition V7.0 Fix Pack 7.0.4.3

APAR status

• Closed as program error.

Error description

• Error Description
  The WebSphere MQ File Transfer Edition agent terminates and does
  not restart successfully when a resource monitor that monitors a
  queue is created and the agent is unable to access that queue
  for some reason. Deleting the monitor is difficult because
  this configuration causes the agent to restart.
  
  For example, if the agent is not authorised to access the queue,
  an FDC generated records:
  
  Level: f704-FP1-20111122-0937
  Time: 02/07/2012 10:46:19:030 EDT
  Thread: 36 (Thread-25)
  Class: com.ibm.wmqfte.monitor.management.MonitorImpl
  Instance: 1f741f74
  Method: run
  Probe: FFDC_002
  Cause: com.ibm.wmqfte.wmqiface.WMQApiFailureException:
  cc=2
  rc=2035 op=openQueue - MQOPEN (Queue Manager: QM, Queue
  Name: Queue, Open Options: 10)
  
  com.ibm.wmqfte.wmqiface.WMQApiFailureException: cc=2 rc=2035
  op=openQueue - MQOPEN (Queue Manager: QM, Queue Name:
  Queue, Open Options: 10)
  

Local fix

• Local Fix <br/>If no other agent configuration exist for the
  affected agent, the <br/>"fteCleanAgent -ms AGENT_NAME"
  command can be used to remove <br/>all defined resource
  monitors.<br/><br/>Alternatively, the cause of the Exception can
  be resolved if possible.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of queue resource monitors in WebSphere MQ File
  Transfer Edition Version 7.0.4 and 7.5.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM SUMMARY:
  WMQ Exceptions generated when accessing the monitored queue were
  being treated as if they were generated when accessing
  internal queues. As a result, recovery processing was
  triggered and the agent entered recovery. Because the agent
  was continuously in recovery, deleting the monitor configuration
  is difficult.
  

Problem conclusion

• This APAR resolves the problem by wrapping WMQ Exceptions
  generated when accessing the monitored queue as
  MonitorUserExceptions. This prevents the agent from entering
  recovery. Instead a message is output to the log with details of
  the problem.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Platform           v7.5
  --------           --------------------
  Multiplatforms     7.5.0.1
  
  Platform           v7.0
  --------           --------------------
  Multiplatforms     7.0.4.3
  
  The latest available 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