"JobSession.getFirstDueJobExcludingMonitoredJobs" query on JBPM_JOB table returns more than one record in jBPM 3.2.9 and "JobSession.getFirstUnownedDueJob" query on jBPM 3.2.11 needs tuning

Solution Unverified - Updated -

Issue

  • "JobSession.getFirstDueJobExcludingMonitoredJobs" query on JBPM_JOB table returns more than one record in jBPM 3.2.9 where as in jBPM 3.2.2 similar query used to return 1 row. This causes high CPU utilisation on the database server whenever jBPM timers expire.
  • "JobSession.getFirstUnownedDueJob" query in jBPM 3.2.11 that is used to calculate nextDueDate in DispatcherThread, returns the bigger part of the JBPM_JOB table.

Environment

  • JBoss Enterprise SOA Platform (SOA-P)
    • 5.1.0
    • 5.2.0
  • JBoss jBPM
    • 3.2.9
    • 3.2.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In