Sure, the jbpm team knows everything about the jbpm config file and how the engine that uses it works. We are *not* specialists in configurations of datasources the way the hibernate and even your DB2 driver behave in maintaining connections and 'we' certainly did not provide the configfile you show, which is *not* a jbpm config file but a datasource config.
jBPM uses the functionality of an appserver that it runs on, in the jbpm starter kit that is JBoss AS. You seem to have a problem with the persistency layer under JBossAS (hibernate). It could either be the datasource config, hibernate itself or even the DB2 driver. So my statement that you'd be best served in the JBoss AS was one to get *you* the *best* help, since I doubt if you will get a helpful answer her. So.... please try the JBoss AS forum View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112698#4112698 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112698 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
