What all things to keep in mind with respect to jBPM3 in SOA-P while removing clustering features ?
Issue
- In the process of removing clustering from the
SOA-P 5.x
nodes , is there any point to following the instruction from this KCS [1] and forcingjBPM 3
to useJBoss Cache
v/s the defaultorg.hibernate.cache.HashtableCacheProvider
as2nd level cache provider for jBPM
when the nodes are not clustered? - If some users did configure
JBoss Cache
instead would they need change thejbpm.esb/hibernate.cfg.xml
file to useMVCC
instead ofOPTIMISTIC node locking
as mentioned in this KCS [2] in such a scenario?
[1] How to configure JBoss Cache as 2nd level cache provider for jBPM in the SOA platform 5?
[2] org.jboss.cache.optimistic.DataVersioningException for jBPM entities in SOA-P 5
Environment
- Red Hat JBoss SOA Platform (SOA-P)
- 5.3.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.