I just ran a test on the sample (reference) web application provided by the jbpm-starters-kit-3.1.1. The test was to create an order using 'Cookie monster' login, later I traced the generated SQL statements. What I founds was around 40+ insert statements for the following JBPM tables JBPM_VARIABLEINSTANCE, JBPM_TOKENVARIABLEMAP, JBPM_SWIMLANEINSTANCE, JBPM_TIMER, JBPM_TASKINSTANCE, JBPM_LOG, JBPM_MODULEINSTANCE
I am wondering did I miss something or is this the expected behavior? It is very expensive for my application, which is more complex than the sample application provided JBPM to handle 40+ insert statement + another set of update statements for each of the major transaction of the system. Can you please clarify this? Is there a way I can optimise this? Thanks, Arshad View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949488#3949488 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3949488 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
