I'm looking for a way to tune the second level cache of jBPM (3.2.2) according to my needs.
jBPM internally configures the cache concurrency strategy for several collections as "nonstrict read-write", while I need them "read-only" (to avoid prohibitive synchronization cost and eventual errors in my highly concurrent clustered environment).
I tried to setup the properties "hibernate.ejb.collectioncache.*" but jBPM's internal configuration actually overrides them.
Why has the cache concurrency policy to be coded inside the product ?
What is the best way to set it read-only ? Should I rewrite jBPM's mapping files ?
The reason is that it just grew like that, but here is a jira issue to make the 2nd-level cache more configurable.
I have no detailed knowledge about this caching so unfortunately I cannot give you an answer on your last 2 questions