Caching and connection pooling are good. But sometimes it is just a question
of looking at your application and using jBPM appropriately.
For example, you must consider paging when huge recordsets are returned. In any
case, you will not be able to display thousands of records to the user. So wh
Sounds like you need a rule engine and not a workflow engine.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912741#3912741
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912741
---
I have 4 Integers associated with a taskInstance that are persisted in jbpm
database.
Strangely, retrieval of only one Integer takes a very long time. All others are
retrieved very quickly.
| Object value =
contextInstance.getVariable(variableAccess.getVariableName(), token);
|
the abov
I have discovered that this particular line
| List formParameters = tInstance.getTaskFormParameters();
|
is particularly time consuming. Almost 200 milliseconds per iteration. Any
ideas why this may be the case?
We have to assign variables (Form parameter) to tasks. After all it is only
Hi,
I did some timing and narrowed down the problem to the worst offender.
| private static Map getMap (TaskInstance tInstance)
| {
| List formParameters = tInstance.getTaskFormParameters();
| Object object = null;
| Map taskMap = new Ha
based on my understanding of the problem, there is a very simple solution to
it. You just want to assign priority to taskinstances for a particular user.
They way to do this would be assign variable called priority for that
taskinstance. This variable will be persisted in the jbpm database and
Place your config.files folder in the runtime classpath of your application
server . Not the compile time classpath. That should get rid of the exception.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911782#3911782
Reply to the post :
http://www.jboss.co
I am having a lot of performance related problems with my jBPM deployment.
Currently, I have not integrated it with any application server. Inserting 500
tasks requires close to 30 seconds even when I am using the PreparedStatement
batch insert via Hibernate. Getting a list of tasks is even wo
