IBM Support

IC91965: WMQFTE 7.0.4: USER DEFINED AGENT XML SCRIPT TERMINATES WITH BFGUT0003E AND FFDC PROBE IDENTIFIER ABEND_001

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A WebSphere MQ File Transfer Edition agent will terminate
    when a user defined XML command message is placed on
    the agent's SYSTEM.FTE.COMMAND queue that uses an unexpected
    prefix to reference a namespace URI.
    
    For example, consider the following XML message to ping an
    agent.
    The XML message uses the namespace prefix "fteNamespace" to
    reference
    the namespace URI
    "http://www.ibm.com/xmlns/wmqfte/7.0.1/PingAgent":
    
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <fteNamespace:pingAgent version="4.00"
    xmlns:fteNamespace="http://www.ibm.com/xmlns/wmqfte/7.0.1/PingAg
    ent">
    <originator>
    <hostName>127.0.0.1</hostName>
    <userID>user1</userID>
    </originator>
    <agent agent="AGENT1" QMgr="QM1"/>
    <reply QMGR="QM1">myReplyQ</reply>
    </fteNamespace:pingAgent>
    
    When used, the agent will terminate with message such as the
    following
    logged to the agent's output0.log file:
    
    BFGUT0003E: An internal error has occurred.
    An unexpected condition has occurred that has resulted in the
    abnormal end of this process.
    Failure data was captured in file
    "ABEND.FTE.20130419085416298.8998755445709015973.log".
    
    The accompanying ABEND file generated includes the following
    information:
    
    Thread: 16 (CommandHandler)
    Class: com.ibm.wmqfte.thread.FTEThread
    Instance: 1c0d1c0d
    Method: uncaughtException
    Probe: ABEND_001
    Cause: java.lang.NullPointerException
    java.lang.NullPointerException
    at
    com.ibm.wmqfte.cmdhandler.impl.FTECommandIntepreterFactory.newFT
    ECommandIntepreter(FTECommandIntepreterFactory.java:95)
    at
    com.ibm.wmqfte.cmdhandler.impl.MessageHandlerImpl.externalMessag
    eHandler(MessageHandlerImpl.java:199)
    at
    com.ibm.wmqfte.cmdhandler.impl.MessageHandlerImpl.processCommand
    (MessageHandlerImpl.java:145)
    at
    com.ibm.wmqfte.cmdhandler.impl.MessageHandlerImpl.processCommand
    (MessageHandlerImpl.java:134)
    at
    com.ibm.wmqfte.cmdhandler.impl.FTECommandThread.run(FTECommandTh
    read.java:259)
    

Local fix

  • Use the expected namespace prefixes to reference the namespace
    URIs for WebSphere MQ File Transfer Edition agent command
    messages:- "ping" for a command message that pings the
    agent- "monitor" to create / delete a resource monitor
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects all users of WebSphere MQ File Transfer
    Edition that create their own XML command messages which are
    then put to an agent's SYSTEM.FTE.COMMAND queue.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    When a WebSphere MQ File Transfer Edition agent receives a
    message on its SYSTEM.FTE.COMMAND queue, the XML of the
    message is parsed and validated against the schema specified
    in the XML. The WebSphere MQ File Transfer Edition XML
    validation routine incorrectly assumed that the namespace prefix
    used in the XML message to reference a particular namespace
    URI would be a certain, fixed value.
    
    If the expected namespace prefix was not used in a command
    message, so long as the prefix is valid in XML terms, then the
    XML message would pass the schema validation. This would then
    result in a NullPointerException as the expected namespace
    prefix could not be found in the parsed output.
    

Problem conclusion

  • The WebSphere MQ File Transfer Edition agent code has been
    changed to allow any namespace prefix to be used for command
    messages that utilise XML elements and attributes with namespace
    prefixes.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following:
    
    Version            v7.0
    --------           --------------------
    Fix available in:  7.0.4.4
    
    Version            v7.5
    --------           --------------------
    Fix available in:  7.5.0.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 number

    IC91965

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-29

  • Closed date

    2013-06-18

  • Last modified date

    2013-06-18

  • 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

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

Document Information

Modified date:
18 June 2013