0 Replies Latest reply on Jul 31, 2019 11:58 AM by mickymorgan

    REST API Persistence

    mickymorgan

      I have 2 unix hosts each with a Tomcat which is running jbpm/kieserver. They share a DB (Tomcat 8.5, JBPM 7.5.0 and Oracle 11). Identical containers are deployed on both kieservers

      When I submit a REST call to a specific host to start a process on a specific tomcat/kieserver, often I see the process actually start running on the other tomcat/kieserver.

      My question is: does the REST API layer actually persist a process record in the DB which can be actioned by either of my kieserver instances, such that the REST call does not directly start the process, it really just registers it for execution ?

       

      I'm getting Optimistic lock exceptions which seem to be due to kieserver runtimes trying to grab the process for execution.

      What are the recommended ways of dealing with this ? Is it better to use Pessimistic locks or is there some other mechanism ?

       

      Thank You in Advance