-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Component/s: JBPM - within SOA
-
Labels:None
-
Environment:
JBoss 4.3 running ESB 4.6
-
Release Notes Text:
-
Release Notes Docs Status:Documented as Resolved Issue
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.
- cloned from
-
SOA-1581 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.
-
- Closed
-
- is related to
-
SOA-1581 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.
-
- Closed
-