IBM Support

IT07999: WEBSPHERE MQ FTE V7.0.4 (MQ FILE TRANSFER EDITION) WHEN RUNNING FTELISTAGENTS COMMAND REPORTS ERROR BFGCL0329E

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The fteListAgents command fails to show the listing of agents
    and their respective status. The command fails with the
    following WMQFTE error:
    
    BFGUT0002E: An internal error has occurred. Product failure data
    was captured in file "FFDC.FTE.log"
    
    The FFDC.FTE.log file generated will contain the following
    stack, note that the 'Unicode: 0x8' part will vary depending on
    the bad character found.
    
    Cause: java.util.InvalidPropertiesFormatException
    java.util.InvalidPropertiesFormatException
    at java.util.Properties.loadFromXML(Properties.java:808)
    at
    com.ibm.wmqfte.utils.AgentStatusDetails.(AgentStatusDetails.java
    :405)
    at
    com.ibm.wmqfte.utils.AgentDetailsFactory.createInstance(AgentDet
    ailsFactory.java:126)
    at
    com.ibm.wmqfte.api.ListAgents.fetchAgentPublications(ListAgents.
    java:128)
    at com.ibm.wmqfte.api.ListAgents.main(ListAgents.java:241)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:60)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at
    com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain.run(BootstrapM
    ain.java:228)
    at
    com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain.main(Bootstrap
    Main.java:109)
    Caused by: org.xml.sax.SAXParseException: An invalid XML
    character (Unicode: 0x8) was found in the element content of the
    document.
    at
    org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseExcepti
    on(Unknown Source)
    at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
    Source)
    at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
    Source)
    at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
    Source)
    at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown
    Source)
    at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentCo
    ntentDispatcher.dispatch(Unknown Source)
    at
    org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocume
    nt(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
    Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
    Source)
    at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
    at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
    at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown
    Source)
    at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
    at java.util.Properties.loadFromXML(Properties.java:787)
    ... 10 more
    

Local fix

  • Please check the problem agent's agent.properties file and
    correct the malformed property. Once you have completed this
    task, restart the agent.
    
    This should cause the agent to republish its status to the
    SYSTEM.FTE/Agents/ topic, which is used by the fteListAgents.cmd
    to produce the listing of agents and their respective status.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of WebSphere MQ File Transfer Edition
    or the Managed File Transfer component of IBM MQ who are
    attempting to configure an agent with an agent description
    (agentDesc) in agent.properties which is not a valid XML
    character.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The agent description is transmitted within the agent status
    details which are published to the SYSTEM.FTE topic on a regular
    basis for the purpose of allowing commands, such as
    fteListAgents, to output meaningful information concerning the
    status of the agents running within the WebSphere MQ File
    Transfer Edition network. This information is encoded into XML
    1.0 for transmission to the topic.
    
    As dictated by the XML 1.0 specification, not all Unicode
    characters can be encoded into XML form. The specification
    states the individual Unicode characters, and Unicode ranges,
    which can be encoded.
    
    If a user inserted a Unicode character into the agent
    description which was not valid for XML encoding, such as the
    backspace control character (0x8), then the agent would encode
    this value to XML when it published its status even though it
    wasn't a valid Unicode character to be encoded in XML.
    
    When the fteListAgents command was later run, it parsed the XML
    found on the SYSTEM.FTE topic and found Unicode characters which
    were not permitted in an XML document. Because of this the
    parsing of the XML document failed and the fteListAgents command
    subsequently failed due to this error.
    

Problem conclusion

  • The code which generates the XML to be published to the
    SYSTEM.FTE topic for agent status, now checks to ensure that all
    characters are valid unicode characters to be inserted into an
    XML document.
    
    If an invalid character is found, it is removed from the field
    and a message is logged to the agent event log. For example:
    
    BFGPR0135W: The value for property 'agentDescription' has been
    altered from 'Agent 1 ' to 'Agent 1' because it contained
    invalid characters for XML conversion.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.5
    v7.5       7.5.0.6
    v8.0       8.0.0.3
    
    The latest available FTE maintenance can be obtained from
    'Fix List for WebSphere MQ File Transfer Edition 7.0'
    http://www-01.ibm.com/support/docview.wss?uid=swg27015313
    
    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

    IT07999

  • 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

    2015-03-27

  • Closed date

    2015-04-27

  • Last modified date

    2015-04-27

  • 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:
27 April 2015