IBM Support

IC87643: WMQFTE V7.0.4: THE JEE DATABASE LOGGER ABENDS WHEN INSERTING INTO TRIGGER_CONDITION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using the WebSphere MQ File Transfer Edition V7.0.4 JEE
    database logger to record details of triggered file transfers to
    a DB2 database, the following exception is thrown:
    
    EJB threw an unexpected (non-declared) exception during
    invocation of method "onMessage" on bean "BeanId(WebSphere MQ
    File Transfer Edition database
    logger#com.ibm.wmqfte.databaselogger.jee.ejb.jar#DatabaseLoggerM
    DB, null)". Exception data: java.lang.IllegalStateException:
    Exception caught during message processing!
    
    ...
    
    Caused by: <openjpa-2.2.1-SNAPSHOT-r422266:1325904 fatal general
    error> org.apache.openjpa.persistence.PersistenceException:
    DB2 SQL Error: SQLCODE=-407, SQLSTATE=23502,
    SQLERRMC=TBSPACEID=4, TABLEID=10, COLNO=5, DRIVER=4.0.100
    {prepstmnt -1582449257 INSERT INTO FTELOG.TRIGGER_CONDITION
    (comparison, CONDITION_TYPE, value, TRANSFER_EVENT_ID) VALUES
    (?, ?, ?, ?)} [code=-407, state=23502]SQLCA
    OUTPUT[Errp=SQLDFMTL, Errd=-2146041828, 28, 0, 0, -1057, 0]
    DB2 SQL Error: SQLCODE=-407, SQLSTATE=23502,
    SQLERRMC=TBSPACEID=4, TABLEID=10, COLNO=5, DRIVER=4.0.100
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the WebSphere MQ File Transfer
    Edition V7.0.4 JEE database logger who use the database logger
    to record information regarding triggered file transfers.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    To record information regarding triggered file transfers to a
    database the WebSphere MQ File Transfer Edition JEE database
    logger can be used. When WebSphere MQ File Transfer Edition
    transfers files, it publishes information about its actions to a
    SYSTEM.FTE/Log topic on the coordination queue manager. The
    database logger is configured to subscribe to the
    SYSTEM.FTE/Log/# topic and then extract the information
    contained within the messages. The JEE database logger then uses
    the Java Persistence API to persist this information to a
    database. However the filename, extracted from meta-data on
    transfer started messages, was handled in a way that prevented
    it from being converted to a datatype the database could
    understand. Therefore the INSERT SQL statement generated did not
    include a suitable value to for the FILENAME attribute which,
    accepts values of type VARCHAR. The INSERT SQL statement
    generated also shows no mention of FILENAME attribute.
    
    This results in an SQL exception being thrown when the INSERT
    SQL statement is expected as the FILENAME attribute on the
    TRIGGER_CONDITION relation cannot accept NULL values.
    

Problem conclusion

  • The database logger has been updated to ensure the filename
    value extracted from the transfer started message is treated
    as a type that can be inserted into the FILENAME attribute of
    the TRIGGER_CONDITION relation.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Platform           v7.0
    --------           --------------------
    Multiplatforms     7.0.4.3
    
    Platform           v7.5
    --------           --------------------
    Multiplatforms     7.5.0.1
    
    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

    IC87643

  • 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

    2012-10-31

  • Closed date

    2012-12-21

  • Last modified date

    2012-12-21

  • 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:
21 December 2012