IBM Support

JR62521: RUNNING THE UNNAMED SNAPSHOT CLEANUP SERVICE FAILS BECAUSE OF A TRANSACTION TIMEOUT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Running the unnamed snapshot cleanup service on IBM Workflow
    Center might fail because of a transaction timeout. The
    following exception is logged in the SystemOut.log file:
    
    [7/3/20 1:16:16:691 EDT] 000179b5 EmbeddableTra I   WTRN0041I:
    Transaction
    000001731314D96D000000010E43DA0CEC54E8C8026E20973C48AC44DE8D58F1
    DBC9A84C000001731314D96D000000010E43DA0CEC54E8C8026E20973C48AC44
    DE8D58F1DBC9A84C00000001 has been rolled back.
    [7/3/20 1:16:16:785 EDT] 000179b5 WSRdbXaResour E   DSRA0302E:
    XAException occurred.  Error code is: XA_RBROLLBACK (100).
    Exception is: [jcc][t4][10401][12066][4.24.92] XA exception:
    XA_RBROLLBACK ERRORCODE=-4228, SQLSTATE=null
    [7/3/20 1:16:16:884 EDT] 000179b5 RemoteExcepti E   CNTR0019E:
    EJB threw an unexpected (non-declared) exception during
    invocation of method "getEJBMetaData". Exception data:
    com.ibm.websphere.csi.CSITransactionRolledbackException:
    Transaction rolled back; nested exception is:
        javax.transaction.TransactionRolledbackException:
    Transaction is ended due to timeout
        at
    com.ibm.ejs.csi.TransactionControlImpl.completeTxTimeout(Transac
    tionControlImpl.java:1318)
    ...
        at com.ibm.db2.jcc.am.k4.executeQuery(k4.java:750)
        at
    com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteQuer
    y(WSJdbcPreparedStatement.java:1220)
        at
    com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeQuery(W
    SJdbcPreparedStatement.java:738)
        at
    org.springframework.jdbc.core.JdbcTemplate$1.doInPreparedStateme
    nt(JdbcTemplate.java:703)
        at
    org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.
    java:644)
        at
    org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.ja
    va:695)
        at
    org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.ja
    va:727)
        at
    com.lombardisoftware.utility.db.spring.BPMJdbcTemplate.query(BPM
    JdbcTemplate.java:241)
        at
    org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.ja
    va:737)
        at
    com.lombardisoftware.utility.db.spring.BPMJdbcTemplate.query(BPM
    JdbcTemplate.java:184)
        at
    org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.ja
    va:787)
        at
    com.lombardisoftware.utility.db.spring.BPMJdbcTemplate.query(BPM
    JdbcTemplate.java:222)
        at
    org.springframework.jdbc.core.simple.SimpleJdbcTemplate.query(Si
    mpleJdbcTemplate.java:227)
        at
    com.lombardisoftware.utility.db.spring.BPMSimpleJdbcTemplate.que
    ry(BPMSimpleJdbcTemplate.java:684)
        at
    org.springframework.jdbc.core.simple.SimpleJdbcTemplate.query(Si
    mpleJdbcTemplate.java:233)
        at
    com.lombardisoftware.utility.db.spring.BPMSimpleJdbcTemplate.que
    ry(BPMSimpleJdbcTemplate.java:226)
    ...
        at
    com.lombardisoftware.client.persistence.SnapshotFactory.findName
    dSnapshots(SnapshotFactory.java:354)
        at
    com.lombardisoftware.server.core.cache.NamedSnapshotCache.loadCa
    cheData(NamedSnapshotCache.java:50)
        at
    com.lombardisoftware.server.core.cache.NamedSnapshotCache.loadCa
    cheData(NamedSnapshotCache.java:22)
        at
    com.lombardisoftware.core.cache.GenericCache.getCacheData(Generi
    cCache.java:197)
        at
    com.lombardisoftware.server.ejb.repositoryservices.SnapshotSuppo
    rt.cleanSomeUnnammedSnapshots(SnapshotSupport.java:917)
        at
    com.lombardisoftware.server.ejb.repositoryservices.RepositorySer
    vicesCore.cleanSomeUnnammedSnapshots(RepositoryServicesCore.java
    :672)
        ...
    Caused by: javax.transaction.TransactionRolledbackException:
    Transaction is ended due to timeout
        at
    com.ibm.tx.jta.embeddable.impl.EmbeddableTranManagerImpl.complet
    eTxTimeout(EmbeddableTranManagerImpl.java:98)
        at
    com.ibm.tx.jta.embeddable.impl.EmbeddableTranManagerSet.complete
    TxTimeout(EmbeddableTranManagerSet.java:92)
        at
    com.ibm.ejs.csi.TransactionControlImpl.completeTxTimeout(Transac
    tionControlImpl.java:1310)
    

Local fix

Problem summary

  • The default 120s value for the transaction timeout might not be
    enough to perform an unnamed snapshot cleanup.
    
    PRODUCT AFFECTED
    IBM Business Automation Workflow
    

Problem conclusion

  • A fix is available or will be available that uses a longer
    transaction timeout value (14400s) for an unnamed snapshot
    cleanup.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR62521

  • Reported component name

    BPM

  • Reported component ID

    5737A5700

  • Reported release

    K00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-08

  • Closed date

    2020-09-30

  • Last modified date

    2020-09-30

  • 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

    BUS AUTO WORKFL

  • Fixed component ID

    5737H4100

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"20.0.0.1"}]

Document Information

Modified date:
14 December 2020