IBM Support

PI59071: DSRA9350E DURING EXPLICIT DATABASE TRANSACTION COMMIT

 

APAR status

  • Closed as program error.

Error description

  • We are seeing the following errors in the logs:
    
    [3/3/16 14:39:17:708 UTC] 000001f7 WSJdbcConnect <  commit Exit
                                     java.sql.SQLException:
    DSRA9350E:
    Operation Connection.commit is not allowed during a global
    transaction.
        at
    com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.commit(WSJdbcConnecti
    on.java:
    1106)
        at
    com.ibm.ftm.base.util.logging.J2EEPoolHandler.getConnection(J2EE
    PoolHand
    ler.java:81)
        at
    com.ibm.ftm.base.util.logging.JDBCLogHandler.logToDatabase(JDBCL
    ogHandle
    r.java:840)
        at
    com.ibm.ftm.base.util.logging.JDBCLogHandler.logToDatabase(JDBCL
    ogHandle
    r.java:335)
        at
    com.ibm.ftm.base.util.logging.JDBCLogHandler.publish(JDBCLogHand
    ler.java
    :294)
        at java.util.logging.Logger.log(Logger.java:628)
        at
    com.ibm.ws.logging.WsLogger.deliverOrBuffer(WsLogger.java:407)
        at com.ibm.ws.logging.WsLogger.log(WsLogger.java:385)
        at
    com.ibm.izh.core.shared.db.db2.DB2DBExec.execProc(DB2DBExec.java
    :167)
    

Local fix

Problem summary

Problem conclusion

  • Corrected logging behavior in the J2EE components.
    Beginning with 3.0.0.14, Payment Feature Services components
    running under WebSphere use extended Logger names.  Configuring
    log detail levels under WebSphere?s diagnostic trace service
    will require appending a wildcard character (?*?) to the end of
    each fully-qualified class name.  Omitting the wildcard will
    prevent the custom log detail level from being honored by the
    targeted class.
    
    Most Logger names will be of the format
    package.class[component_name:component_type].  So for example,
    if you previously defined a custom log detail for monitoring
    performance characteristics of Distribution?s FileBean class,
    you need to change the specification from
    ?com.ibm.paydir.presentment.ejb.file.FileBean=FINE? to
    ?com.ibm.paydir.presentment.ejb.file.FileBean*=FINE?.  The
    actual logger name registered by the class in WebSphere will be
    ?com.ibm.paydir.presentment.ejb.file.FileBean
    [Distribution:ENGINE]?.
    
    Corrected in fix pack with fix id 3.0.0-FTM-Check-MP-fp0014
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI59071

  • Reported component name

    CORP PAY SVCS F

  • Reported component ID

    5725S7530

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-15

  • Closed date

    2016-06-09

  • Last modified date

    2016-06-09

  • 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

    CORP PAY SVCS F

  • Fixed component ID

    5725S7530

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPKQ5","label":"Financial Transaction Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"300","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
31 August 2023