Hi,
We are seeing this issue intermittently in BPS 3.5.0, even with
DB_CLOSE_DELAY=1000. Hence I have re-opened jira [1].
IMO correct fix would be to keep open database as long as the JVM is
alive. We can configure it by setting DB_CLOSE_DELAY=-1 [2].
[1] https://wso2.org/jira/browse/BPS-529
Hi ,
I had same issue on activity explorer. There is no activiti.cfg.xml in
Activity explorer configurations.
thanks,
Waruna
On Sat, Mar 1, 2014 at 10:19 PM, Amal Gunatilake am...@wso2.com wrote:
Hi Chathura,
Thank you for the info. Until we have a separate xml file for BPMN I'll
configure
Hi Waruna,
In-order to make the data persistence across server restarts in
Activiti-Explorer, once you deploy the war archive in Tomcat server. Go to
webapps/activiti-explorer/WEB-INF/classes/db.properties file and change the
jdbc url from *jdbc:h2:mem:* to *jdbc:h2:file*: as follows.
Hi All,
When running some test on Activiti explorer itself, I observed that the
instances we create will get lost after doing a server restart, no matter
which state the instances are. Is it a normal behaviour ? I think those has
to be permanent data. So we might have to have a contingency plan
Hi Amal,
The default configuration in Activiti uses an in-memory H2 database. Data
can be made persistent (across server restarts) by changing this to a
disk-based DB. Change the database config in activiti.cfg.xml file to do
this. Currently BPS also uses the same XML (until we change it to use
