I continually receive a deadlock error during insertion into the JBPM_LOG
table...since there is no user control over the auditiing process, this would
seem to be a jbpm application error. Any help on resolving this issue would be
appreciated. This is on Postgresql 7.3.x, Tomcat 5.5.x, Java
I'm sorry, I posted too hastily...here is the flow of calls to jbpm:
1) Load processinstance from newly opened JbpmSession
2) Get ContextInstance and delete a variable
3) Get TaskInstances from ProcessInstance's TaskManagementInstance
4) Loop through the TaskInstances and if the task has not
I have the same problem in a production system where one group could have
hundreds of tasks. I am looking into how one can achieve SQL pagination, as
doing this in the application server may be too much overhead. The problem is
compounded by the use of a Comparator b/c the jBPM task lists are
adding optional pagination parameters to the task list is a good idea, i think.
i'll create a jira issue to try it out.
regards, tom.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3916184#3916184
Reply to the post :
we think about writing a book, but the plans are not yet very concrete.
regards, tom.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3916187#3916187
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3916187
Tom,
This is off topic. But is there a book in the works? I think there is a
demand to see the value of jbpm and how to get started with it.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3915900#3915900
Reply to the post :
