IT04759: WEBSPHERE MQ V8.0 EXPLORER UNABLE TO CONNECT TO MFT/FTE COORDINATION QUEUE MANAGER

Fix Pack 8.0.0.2 for WebSphere MQ V8.0

APAR status

• Closed as program error.

Error description

• When using a local Managed File Transfer (MFT) configuration,
  the WebSphere MQ v8.0 Explorer fails to connect the MFT
  configuration to the defined coordination and command queue
  managers. The WebSphere MQ v8.0 Explorer does not display any
  error or warning messages.
  
  When WebSphere MQ v8.0 Explorer tracing is enabled, an FFDC file
  is generated with the following information when the user
  attempts to connect the MFT configuration:
  
  Level: f800-20140813-1141
  Time: 24/10/2014 10:39:51:159 EDT
  Thread: 1 (main)
  Class: com.ibm.wmqfte.configuration.FTEPropertiesFactory
  Method: getInstance
  Probe: FFDC_002
  Cause: com.ibm.wmqfte.configuration.FTEConfigurationException:
  BFGUB0010E: Internal error: The configuration has not been
  initialized before first use.
  com.ibm.wmqfte.configuration.FTEConfigurationException:
  BFGUB0010E: Internal error: The configuration has not been
  initialized before first use.
  at
  com.ibm.wmqfte.configuration.FTEPropertiesFactory.getInstance(FT
  EPropertiesFactory.java:175)
  at
  com.ibm.wmqfte.userexits.impl.UserExitsFactoryImpl.(UserExitsFac
  toryImpl.java:198)
  at
  com.ibm.wmqfte.userexits.UserExitsFactory.initialise(UserExitsFa
  ctory.java:107)
  at
  com.ibm.wmqfte.explorer.data.Subscription.updateProperties(Subsc
  ription.java:345)
  at
  com.ibm.wmqfte.explorer.treenode.CoordTreeNode.connect(CoordTree
  Node.java:264)
  at
  com.ibm.wmqfte.explorer.treenode.CoordTreeNode.connect(CoordTree
  Node.java:249)
  at
  com.ibm.wmqfte.explorer.treenode.CoordTreeNode$3.run(CoordTreeNo
  de.java:162)
  
  
  In addition, the WebSphere MQ v8.0 Explorer trace file contains
  the entry:
  
  Exception thrown
  com.ibm.wmqfte.configuration.FTEConfigurationException:
  BFGUB0010E: Internal error: The configuration has not been
  initialized before first use.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects all users of the WebSphere MQ Explorer
  version 8 Managed File Transfer (MFT) plug-in who create local
  MFT configurations.
  
  
  Platforms affected:
  Linux on x86, Linux on x86-64, Windows
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Within the WebSphere MQ Explorer Managed File Transfer (MFT)
  plug-in, there are two types of MFT configuration. They are:
  
    - "global" configurations
  
    - "local" configurations.
  
  A global configuration is used when WebSphere MQ MFT has been
  installed alongside the WebSphere MQ Explorer, such that the
  WebSphere MQ Explorer MFT plug-in can access the MFT properties
  files.
  
  Whereas a local configuration is created when a user
  right-clicks on the "Managed File Transfer" folder within the MQ
  Explorer - Navigator pane, selects "New configuration..." and
  uses the resulting wizard to specify details such as the
  coordination and command queue managers to access their
  WebSphere MQ MFT topology.
  
  When a user attempted to "connect" a local WebSphere MQ Managed
  File Transfer (MFT) configuration within the WebSphere MQ
  Explorer, the MFT plug-in attempted to use a data structure, for
  accessing properties, that had not been initialised. This was
  because, with a local configuration, there are no on-disk
  property files to read and parse that would have resulted in
  this data structure being initialised.
  
  This resulted in an internal error being thrown, which in turn
  prevented the MFT plug-in from connecting to the WebSphere MQ
  coordination queue manager for the MFT topology to which the
  local configuration related. The internal error was caught
  within the WebSphere MQ Explorer however and no error message
  was displayed to the user.
  

Problem conclusion

• The WebSphere MQ Explorer Managed File Transfer (MFT) plug-in
  code has been updated such that the data structure for accessing
  properties is initialised with default values before being
  accessed when connecting to the WebSphere MQ coordination queue
  manager for the MFT topology.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.2
  
  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:

  XX00219

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WMQ BASE MULTIP

• Fixed component ID

  5724H7251

Applicable component levels

• R800 PSY

     UP