IBM Support

IT10944: WEBSPHERE MQ FTE FTECLEANAGENT ABENDS AFTER UPGRADE OF FTE MAINTENANCE LEVEL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After installing a fixpack for MQ FTE, fteCleanAgent ABENDed
    with
    
    Class:      com.ibm.wmqfte.agent.AgentRuntime
    Method:     getInstance
    Probe:      ABEND_001
    Cause:      null
    
    java.lang.Exception: Call stack
     at
    com.ibm.wmqfte.ras.impl.IncidentStream.<init>(IncidentStream.jav
    a:210)
     at
    com.ibm.wmqfte.ras.impl.ABENDImpl.internalTerminateJvm(ABENDImpl
    .java:142)
     at com.ibm.wmqfte.ras.ABEND.terminateJvm(ABEND.java:123)
     at
    com.ibm.wmqfte.agent.AgentRuntime.getInstance(AgentRuntime.java:
    196)
     at
    com.ibm.wmqfte.cmdhandler.impl.FTECommandHandlerSAXParser$FTETra
    nsferSetHandler.validateCDBridge(FTECommandHandlerSAXParser.java
    :623)
     at
    com.ibm.wmqfte.cmdhandler.impl.FTECommandHandlerSAXParser$FTETra
    nsferSetHandler.startElement(FTECommandHandlerSAXParser.java:592
    )
     at
    com.ibm.wmqfte.cmdhandler.impl.FTECommandHandlerSAXParser$FTESAX
    Handler.startElement(FTECommandHandlerSAXParser.java:396)
     at
    org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
    Source)
     at
    org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknow
    n Source)
     ..
     at
    com.ibm.wmqfte.api.CleanAgent.cleanAgentQueues(CleanAgent.java:2
    18)
     at com.ibm.wmqfte.api.CleanAgent.main(CleanAgent.java:603)
    
    Note:  After running fteCleanAgent messages messages may be
    left on the command queue.
    

Local fix

  • The workaround to this issue is to clear the messages on the
    agent's  SYSTEM.FTE.COMMAND. queue manually, for
    example via runmqsc or the WebSphere MQ Explorer, and then
    rerun the fteCleanAgent command to perform the remainder of the
    clean operations requested.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of WebSphere MQ File Transfer Edition
    v7.0.4 who try to perform an fteCleanAgent command for an agent
    which has a transfer request pending on the agent's command
    queue and the transfer has programs specified to run before or
    after the transfer has completed.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    During the clean agent process, the agent's command queue was
    scanned and any message present was read.
    If a transfer request was present, it was loaded and read. In
    the process of parsing the message, if the parser discovered a
     call-out option then it would check the agent type to see if
    program invocation was supported. To get the agent type required
    the parser to access the Agent runtime instance.  This was not
    available when performing a clean agent, causing the error.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT10944

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-08-27

  • Closed date

    2016-01-04

  • Last modified date

    2016-05-04

  • 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":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2016