IBM Support

JR53730: IF MULTIPLE TIMERS ARE SCHEDULED TO FIRE AT THE SAME TIME, NOT ALL THE TIMERS FIRE AS SCHEDULED DUE TO DB LOCK CONTENTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If there are many Event Manager tasks scheduled for the  same
    second, deadlock exceptions might occur in clustered
    environments. These exceptions could lead to scheduled Event
    Manager tasks not running although their timers are due.
    You might see a stack trace that is similar to the following
    stack trace:
    
    DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=2,
    DRIVER=4.13.80; nested exception is
    com.ibm.db2.jcc.am.SqlTransactionRollbackException: DB2 SQL
    Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=2, DRIVER=4.13.80
     at org.springframework.jdbc.support.
      SQLExceptionSubclassTranslator.translate
      (SQLExceptionSubclassTranslator.java:52)
     at org.springframework.jdbc.support.
      SQLErrorCodeSQLExceptionTranslator.translate
      (SQLErrorCodeSQLExceptionTranslator.java:237)
     at org.springframework.jdbc.core.JdbcTemplate.execute
      (JdbcTemplate.java:607)
     at org.springframework.jdbc.core.JdbcTemplate.query
      (JdbcTemplate.java:641)
     at org.springframework.jdbc.core.JdbcTemplate.query
      (JdbcTemplate.java:670)
     at org.springframework.jdbc.core.JdbcTemplate.query
      (JdbcTemplate.java:678)
     at com.lombardisoftware.server.scheduler.Engine.
      loadTasksIfOwnerInternal(Engine.java:1475)
     at com.lombardisoftware.server.scheduler.Engine.
      access$1700(Engine.java:103)
     at com.lombardisoftware.server.scheduler.Engine$12.
      doInTransaction(Engine.java:1347)
     at com.lombardisoftware.server.scheduler.Engine$12.
      doInTransaction(Engine.java:1344)
     at com.lombardisoftware.server.core.TXCommand$2.call
      (TXCommand.java:85)
     at com.lombardisoftware.utility.spring.
      ProgrammaticTransactionSupport$1.doInTransaction
      (ProgrammaticTransactionSupport.java:451)
     at org.springframework.transaction.jta.
      WebSphereUowTransactionManager$UOWActionAdapter.run
      (WebSphereUowTransactionManager.java:306)
     at com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.
      runUnderNewUOW(EmbeddableUOWManagerImpl.java:791)
     at com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.
      runUnderUOW(EmbeddableUOWManagerImpl.java:370)
     at org.springframework.transaction.jta.
      WebSphereUowTransactionManager.
      execute(WebSphereUowTransactionManager.java:252)
     at com.lombardisoftware.utility.spring.
      ProgrammaticTransactionSupport.executeInNewTransaction
      (ProgrammaticTransactionSupport.java:445)
     at com.lombardisoftware.utility.spring.
      ProgrammaticTransactionSupport.execute
      (ProgrammaticTransactionSupport.java:306)
     at com.lombardisoftware.server.core.TXCommand.
      executeInDeadlockRetryLoop(TXCommand.java:83)
     at com.lombardisoftware.server.scheduler.Engine.
      loadTasksIfOwner(Engine.java:1344)
     at com.lombardisoftware.server.scheduler.Engine.executeTasks
      (Engine.java:529)
    

Local fix

  • Stop and restart the AppTarget cluster.
    

Problem summary

  • This issue occurs wherever a problem with the database occurs
    while the Event Manager acquires and tries to load Event Manager
    tasks.
    

Problem conclusion

  • A fix is/will be available for IBM BPM that prevents the
    deadlock.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR53730:
    
    1. Select IBM Business Process Manager with your edition from
      the product selector, the installed version to the fix pack
      level, and your platform, and then click Continue.
    
    2. Select APAR or SPR, enter JR53730, and click Continue.
    
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    fix.
    

Temporary fix

  • Not applicable
    

Comments

APAR Information

  • APAR number

    JR53730

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-06-30

  • Closed date

    2015-08-28

  • Last modified date

    2015-11-05

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R855 PSY

       UP

  • R856 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
05 November 2015