-
1. Re: Problem inserting in JBPM_JOB
iecisa Oct 13, 2009 3:28 PM (in response to iecisa)hi again,
we've found that most of the 10 seconds is going in this block:
Action moveAction = new Action();
moveAction.setName(actionName);
moveAction.setActionDelegation(delegation);
executionContext.getProcessDefinition().addAction(moveAction);
we know it has no sense, but is in this point -
2. Re: Problem inserting in JBPM_JOB
kukeltje Oct 13, 2009 5:55 PM (in response to iecisa)Please turn the loglevel up to see what is going on and post that here.
-
3. Re: Problem inserting in JBPM_JOB
iecisa Oct 13, 2009 6:58 PM (in response to iecisa)well, actually, debugging, we found the problem is exactly here:
actions.put(action.getName(), action);
in class ProcessDefinition in the method: addAction(Action action)
at the moment we fix it, replacing the line above by:
if (! actions.containsKey(action.getName()))
actions.put(action.getName(), action);
we don't understand why is necesary to insert each time the action into the Map. -
4. Re: Problem inserting in JBPM_JOB
iecisa Oct 14, 2009 2:54 PM (in response to iecisa)Also we don't understand why doing a put method it takes 10 seconds.
-
5. Re: Problem inserting in JBPM_JOB
kukeltje Oct 15, 2009 2:14 PM (in response to iecisa)we do not get that either.... if you debug further and see what happens we both can learn from it I think.
-
6. Re: Problem inserting in JBPM_JOB
iecisa Oct 15, 2009 4:56 PM (in response to iecisa)Well, first we saw is that actions Map contains the actions that are defined in the workflow, and taking into account that actions are always the same class isn't necessary to put(mapping) the action each time. So we put the code line:
if (! actions.containsKey(action.getName()))
Why put instruction takes 10 second, we still don't undestand, but we think is an Hibernate issue.