In 5.2 we merge the current implementation for Variable Persistence with the core marshaling mechanisms of drools.
You can find a test that show how to configure the new Persisters in the following test inside the jbpm-persistence-jpa project:
I was responsible for that merge and for the unification of these mechanisms, so please feel free to report any problem that you have with it.
I was wondering if there were any changes to the behavior of calling:
I seem to get the following stack trace when using this (it worked in the previous release)
SEVERE: [http-thread-pool-8080(2)] ERROR essionCommandService - Could not commit session
i encounter the same exception, you can try un-register the JPAWorkingMemoryDbLogger but comment the line:
Hmm that error doens't seem related with the variable persistence strategies.. when are you getting that?