1 Reply Latest reply on Jan 5, 2008 10:10 AM by Ronald van Kuijk

    2nd level cache management

    Nicolas LE BAS Newbie

      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 ?