What all things to keep in mind with respect to jBPM3 in SOA-P while removing clustering features ?

Solution Unverified - Updated -

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 forcing jBPM 3 to use JBoss Cache v/s the default org.hibernate.cache.HashtableCacheProvider as 2nd level cache provider for jBPM when the nodes are not clustered?
  • If some users did configure JBoss Cache instead would they need change the jbpm.esb/hibernate.cfg.xml file to use MVCC instead of OPTIMISTIC 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.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content