"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

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.