IBM Support

IT21598: IBM MQ-MFT agent fails to start on AIX after migrating an installation to MQ v9.0 from an earlier version

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • An IBM MQ-MFT agent running on AIX at version 7.5.0.4 is
    migrated to version 9.0.0.0 by upgrading the MQ 7.5.0.4
    installed packages to MQ 9.0.0.0.
    
    Then when an attempt is made to start the agent, the following
    error message is seen in the output0.log file:
    
    BFGBS0005E: An internal error has occurred.  The exception
    details follow this message.
    java.lang.reflect.InvocationTargetException
      at sun.reflect.NativeMethodAccessorImpl.invoke0
      at sun.reflect.NativeMethodAccessorImpl.invoke
      at sun.reflect.DelegatingMethodAccessorImpl.invoke
      at java.lang.reflect.Method.invoke
      at com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain.run
      at com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain.main
    
    Caused by: java.lang.NoClassDefFoundError:
    com.ibm.wmqfte.exitroutine.api.SourceTransferStartExit
      at
    com.ibm.wmqfte.userexits.impl.UserExitsFactoryImpl.loadAllExits
      at com.ibm.wmqfte.userexits.impl.UserExitsFactoryImpl.<init>
      at com.ibm.wmqfte.userexits.UserExitsFactory.initialise
      at com.ibm.wmqfte.agent.Agent.intialiseUserExits
      at com.ibm.wmqfte.agent.Agent.doInitialisation
      at com.ibm.wmqfte.agent.AgentRuntime.mainLoop
      at com.ibm.wmqfte.agent.Agent.main
    
    The agent does not start and is subsequently unable to perform
    any file transfer activity.
    

Local fix

  • The primary recommended upgrade mechanism to avoid this issue is
    to completely uninstall all of the filesets of the older version
    of MQ first, prior to installing the newer MQ v9.0.0.0 or later
    filesets on AIX.
    
    Alternatively if you have already migrated to the MQ v9.0.0.0 or
    later filesets, this issue can be resolved by uninstalling and
    reinstalling the MQ Managed File Transfer components when
    migrating the installation.
    
    The uninstall and re-install of the affected components can be
    achieved by running the following commands:
    Note: the install commands should be run from within the
    directory where the install packages are located, or adjust the
    commands accordingly.
    
    
    installp -u mqm.ft.base mqm.ft.agent mqm.ft.logger
    mqm.ft.service mqm.ft.tools
    
    installp -acgXYd . mqm.ft.base mqm.ft.agent mqm.ft.logger
    mqm.ft.service mqm.ft.tools
    
    
    If MQ is installed in non-default location, then use the
    following commands:
    
    
    installp -R <USIL_Directory> -u mqm.ft.base mqm.ft.agent
    mqm.ft.logger mqm.ft.service mqm.ft.tools
    
    installp -R <USIL_Directory> -acgXYd . mqm.ft.base mqm.ft.agent
    mqm.ft.logger mqm.ft.service mqm.ft.tools
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the IBM MQ Managed File Transfer
    components on AIX, who are migrating an installation prior to
    v9.0.0.0, to v9.0.0.0 or later.
    
    
    Platforms affected:
    AIX
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    At versions of IBM MQ Managed File Transfer prior to v9.0.0.0,
    the .jar file:
    
        com.ibm.wmqfte.exitroutine.api.base.jar
    
    was supplied as part of the "mqm.ft.agent" install component on
    AIX.  In order to satisfy a product dependency on an install
    component,  this .jar file was relocated to another install
    component at IBM MQ v9.0.0.0.  On the AIX platform, the IBM MQ
    component where the file was moved to is called: "mqm.ft.base".
    
    The migration installation mechanism offered by AIX may result
    in files being lost when files are moved between filesets,
    depending on the order in which the filesets are upgraded.
    
    If the first component which is upgraded is "mqm.ft.base" which
    contains the new version of the
    "com.ibm.wmqfte.exitroutine.api.base.jar" file, then when  the
    second component is subsequently upgraded (mqm.ft.agent), the
    file is removed as part of the older component's removal
    procedure, prior to the installation of the updated package.
    When this happens, a warning message is output as part of the
    upgrade process, which reads:
    
    installp: APPLYING software for:
            mqm.ft.base (R) 9.0.0.2
    
    
    . . . . . << Copyright notice for mqm.ft >> . . . . . . .
    
      Licensed Materials - Property of IBM
    
     5724H7251
      (C) Copyright International Business Machines Corp. 1994,
    2016.
    
      US Government Users Restricted Rights - Use, duplication or
    disclosure
      restricted by GSA ADP Schedule Contract with IBM Corp.
    
    
    . . . . . << End of copyright notice for mqm.ft >>. . . .
    
    sysck: 3001-036 WARNING:  File
    /usr/mqm/mqft/lib/com.ibm.wmqfte.exitroutines.api.jar
            is also owned by fileset mqm.ft.agent.
    
    
    This warning message was displayed indicating that the
    com.ibm.wmqfte.exitroutine.api.base.jar now belonged to two
    components, mqm.ft.base and mqm.ft.agent components.
    
    After this, as part of upgrading mqm.ft.agent, it uninstalled
    the mqm.ft.agent component, which resulted in its associated jar
    files including "com.ibm.wmqfte.exitroutine.api.base.jar" being
    deleted.  This .jar file was then not reinstalled as part of the
    mqm.ft.agent fileset installation, as this .jar file is no
    longer associated with that fileset.
    

Problem conclusion

  • The install scripts for the filesets have been updated to
    prevent the problem was occurring.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0 CD    9.0.5
    v9.0 LTS   9.0.0.4
    
    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

    IT21598

  • Reported component name

    WMQ MFT V8.0

  • Reported component ID

    5724H7252

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-07-26

  • Closed date

    2018-01-29

  • Last modified date

    2018-01-29

  • 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 V8.0

  • Fixed component ID

    5724H7252

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
29 January 2018