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.xnodes , is there any point to following the instruction from this KCS [1] and forcingjBPM 3to useJBoss Cachev/s the defaultorg.hibernate.cache.HashtableCacheProvideras2nd level cache provider for jBPMwhen the nodes are not clustered? - If some users did configure
JBoss Cacheinstead would they need change thejbpm.esb/hibernate.cfg.xmlfile to useMVCCinstead ofOPTIMISTIC node lockingas 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 of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
