This content has been marked as final.
Show 8 replies
-
1. Re: Possible performance problem caused by autoSaveProcessInstances
kukeltje Mar 10, 2010 1:47 PM (in response to richard.qin)Personally I would look first in how it is possible you page adds thousands of the same process instances to the list. We've never heard anyone else having a problem with this.1 of 1 people found this helpful -
2. Re: Possible performance problem caused by autoSaveProcessInstances
richard.qin Mar 10, 2010 10:06 PM (in response to kukeltje)The same processInstance is not added explicitly by the pages of web app, it's added implicitly by the initialization of the seam components. when jbpm is enabled in seam, the initialization of the component will invoke the ProcessInstance.getProcessInstance, it invoke the JbpmContext.getProcessInstanceForUpdate to add the processInstance to the autoSaveProcessInstances. the following picture shows the full call stack:
thanks
-
3. Re: Possible performance problem caused by autoSaveProcessInstances
rpie Mar 11, 2010 8:58 PM (in response to kukeltje)My company is having the exact same issue. This is resulting in disastrous performance and is a major issue for us right now. -
4. Re: Possible performance problem caused by autoSaveProcessInstances
kukeltje Mar 11, 2010 9:48 PM (in response to rpie)The seam/jbpm integration layer is part of seam, so I'd ask there... -
5. Re: Possible performance problem caused by autoSaveProcessInstances
richard.qin Mar 14, 2010 1:54 AM (in response to kukeltje)Thank you, Ronald. Please let me know if you need further information. -
6. Re: Possible performance problem caused by autoSaveProcessInstances
kukeltje Mar 14, 2010 9:58 AM (in response to richard.qin)Sorry, slight misunderstanding... With my previous post I meant that *you*'d better ask there... -
7. Re: Possible performance problem caused by autoSaveProcessInstances
mputz Jul 8, 2010 4:02 AM (in response to richard.qin)This has been fixed in Seam 2.2.1.RC2, see JBSEAM-4629.
-
8. Re: Possible performance problem caused by autoSaveProcessInstances
aguizar Jul 8, 2010 8:32 AM (in response to mputz)Despite the workaround employed in JBSEAM-4629, I have created a Jira issue to assess the original proposal: JBPM-2911. I will check whether it is possible to turn the autoSaveProcessInstances list into a set without compromising backwards compatibililty.