Hi, We are using the DB as a poor man's queue and we have two instances from our application running. This means we have competing consumers. By default the jpa consumer uses LockType.WRITE. Is it possible to configure this to PESSIMISTIC locking? We call a legacy service which is not IDEM POTENT causing some bugs in a backend system. Using pessimistic locking solves this but it looks like we can not configure the jpa component to use another LockType.
Kind regards, Bart -- View this message in context: http://camel.465427.n5.nabble.com/Configurable-LockType-for-JpaConsumer-tp5738192.html Sent from the Camel - Users mailing list archive at Nabble.com.
