I am new to Activiti and i have an issue with internet and Ibatis connection. I cannot start Activiti without internet connection, each time i do, i get an error "Error while building ibatis SqlSessionFactory". Why this behavior and how can i run Activiti regardless of the internet status?
How to increase connection timeout? I have created a lot of human tasks (>800) in nested multi instance processes and receive always timeout exception
…Caused by: org.h2.jdbc.JdbcSQLException: Timeout trying to lock table "ACT_RU_EXECUTION"; SQL statement: select JOB.* from ACT_RU_JOB JOB LEFT OUTER JOIN ACT_RU_EXECUTION PI ON PI.ID_ = JOB.PROCESS_INSTANCE_ID_
LEFT OUTER JOIN ACT_RE_PROCDEF PD ON PD.ID_ = PI.PROC_DEF_ID_ where (JOB.RETRIES_ > 0) and (JOB.DUEDATE_ is null or JOB.DUEDATE_ < ?) and (JOB.LOCK_OWNER_ is null or JOB.LOCK_EXP_TIME_ < ?) and ( (JOB.EXECUTION_ID_ is null) or ((PI.SUSPENSION_STATE_ = 1) and (PD.SUSPENSION_STATE_ = 1)) ) LIMIT ? OFFSET ? [50200-168] at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) at org.h2.message.DbException.get(DbException.java:169) at org.h2.message.DbException.get(DbException.java:146) at org.h2.table.RegularTable.doLock(RegularTable.java:500) at org.h2.table.RegularTable.lock(RegularTable.java:434) at org.h2.table.TableFilter.lock(TableFilter.java:143) at org.h2.table.TableFilter.lock(TableFilter.java:145) at org.h2.command.dml.Select.queryWithoutCache(Select.java:604) at org.h2.command.dml.Query.query(Query.java:307) at org.h2.command.dml.Query.query(Query.java:277)
H2 isn't really a production-database and sometimes locks full tables, while it shouldn't. This is something other DB's don't have and it's recommended to use another one.
If you really want to use H2 (maybe for testing?), look in the H2 documentation for this, think it's a parameter in the jdbc-URL.
I ran into the same problem as JTawk and didn't see an easy solution posted on the thread, so I thought I'd post mine in case someone else has the same problem.
Switching the dependency in my Activiti pom.xml file from apache ibatis to mybatis cleared up the problem for me and avoided messing around with ibatis working with my proxy settings.