Bug 780760 (SOA-3214) - The calls org.jbpm.job.executor.JobExecutorThread.getWaitPeriod(int) and org.jbpm.job.executor.JobExecutorThread.getNextDueDate() are taking 2.58 seconds to run. It appears that there is an index missing.
Summary: The calls org.jbpm.job.executor.JobExecutorThread.getWaitPeriod(int) and org....
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3214
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBPM - within SOA
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0 GA,5.2.0 ER1
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-26 10:50 UTC by Julian Coleman
Modified: 2011-10-07 08:26 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
JBoss 4.3 running ESB 4.6
Last Closed: 2011-10-07 08:20:32 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779187 0 high ASSIGNED The calls org.jbpm.job.executor.JobExecutorThread.getWaitPeriod(int) and org.jbpm.job.executor.JobExecutorThread.getNext... 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 780989 0 urgent CLOSED Migration scripts are missing 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBPM-3235 0 None None None Never
Red Hat Issue Tracker SOA-3214 0 None None None Never

Internal Links: 779187 780989

Description Julian Coleman 2011-07-26 10:50:31 UTC 
project_key: SOA

While profiling the users system found that the methods org.jbpm.job.executor.JobExecutorThread.getWaitPeriod(int) and org.jbpm.job.executor.JobExecutorThread.getNextDueDate() are taking 2.58 seconds to run. 

This is true even though the client is not using JBPM and has nothing added to the database.  It appears to be do to a lack of an index on the query.

Since they don't use JBPM in this implementation of ESB we are just taking it out.
Comment 1 Julian Coleman 2011-07-26 10:50:32 UTC 
Link: Added: This issue Cloned from SOA-1581
Comment 2 Julian Coleman 2011-07-26 10:50:32 UTC 
Link: Added: This issue relates to JBPM-3235
Comment 3 Julian Coleman 2011-07-26 10:51:34 UTC 
Fixed in jBPM 3.2.11.
Comment 4 Julian Coleman 2011-07-26 10:52:20 UTC 
Link: Added: This issue is related to SOA-1581
Comment 5 Julian Coleman 2011-08-02 10:42:00 UTC 
SOA 5.2.0 now includes jBPM 3.2.11.
Comment 6 David Le Sage 2011-08-26 04:30:45 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: 
https://issues.jboss.org/browse/SOA-3214

While profiling thesystem, users found that the org.jbpm.job.executor.JobExecutorThread.getWaitPeriod(int) and org.jbpm.job.executor.JobExecutorThread.getNextDueDate() methods were taking 2.58 seconds to run. This was due to the lack of an index on the query. This code has been fixed in the latest version of JBPM and, as a result, the methods now run more quickly.
Comment 7 Jiri Pechanec 2011-10-07 08:20:32 UTC 
Verified in ER4
Comment 8 Jiri Pechanec 2011-10-07 08:26:08 UTC 
Link: Added: This issue relates to SOA-3465
Note You need to log in before you can comment on or make changes to this bug.