How to inspect the in-memory Activiti H2 database?

[kcassell]

I'm just getting started using Activiti, and I'd like to be able to examine the contents of the in-memory H2 database as I run my workflows. How can I do so? Is it possible using a tool like Squirrel? If so, what do I use as a URL, user, password, etc.? Right now, I am using the default configuration.

[jbarrez]

In a unit test, you can inspect it quite easily:  http://activiti.org/userguide/index.html#apiDebuggingUnitTest

[kcassell]

Thanks.  That provides me a way to inspect the database.  It doesn't seem to work with Squirrel, and I'm not sure I understand why.  But as long as I can get at the info I care about, I guess I don't really care, although I am curious.

[frederikherema1]

What is the issue with squirrl? H2 offers a plain old JDBC-interface, so don't see any obvious reasons why connection doesn't work. Any stack trace in squirrel?

[fatma19]

it works for me but is it normal that every time i restart the process engine i don't get the old processes ? 

[cjose]

yes, if running against in-memory db.

[fatma19]

So what can i do if i want to make db persist the old processengine instance processes? 

[cjose]

It is not about db persisting the data or not. The DB itself is not getting persisted when you use in-memory. So if you want the process data to be available after an engine re-start, use a non-in-mem db in your activiti configuration. If you are using H2, check Tutorial  for more details.

[fatma19]

ok Thank you  i will follow that  

[fatma19]

So i will use mysql database is that a good choice with activiti?