Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AC2D5F9F5 for ; Mon, 2 Sep 2013 08:55:58 +0000 (UTC) Received: (qmail 68349 invoked by uid 500); 2 Sep 2013 08:55:53 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 68222 invoked by uid 500); 2 Sep 2013 08:55:52 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 68198 invoked by uid 99); 2 Sep 2013 08:55:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Sep 2013 08:55:52 +0000 Date: Mon, 2 Sep 2013 08:55:51 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CAMEL-6681) Configurable LockType for JpaConsumer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-6681: ------------------------------- Fix Version/s: (was: 2.12.1) 2.12.0 > Configurable LockType for JpaConsumer > ------------------------------------- > > Key: CAMEL-6681 > URL: https://issues.apache.org/jira/browse/CAMEL-6681 > Project: Camel > Issue Type: New Feature > Components: camel-jpa > Reporter: Bart De Neuter > Assignee: Claus Ibsen > Priority: Minor > Labels: patch > Fix For: 2.11.2, 2.12.0 > > Attachments: 0001-added-setter-getter-of-LockModeType-to-JpaConsumer.patch > > > Allow the user to specify the LockModeType for the JpaConsumer. This is handy when using a DB as a poor man's queue with multiple competing instances. If those instances call a non IDEM POTENT service, the service can be called multiple times. This can be prevented by using pessimistic locking. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira