Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Wed, 1 Aug 2012 12:30:03 +0000 (UTC)
From: "Jamie goodyear (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <202644205.356.1343824203277.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <170922792.3727.1297082190860.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (KARAF-447) Add JDBC lock implementation for
 PostgreSQL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/KARAF-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jamie goodyear reassigned KARAF-447:
------------------------------------

    Assignee: Jamie goodyear
    
> Add JDBC lock implementation for PostgreSQL
> -------------------------------------------
>
>                 Key: KARAF-447
>                 URL: https://issues.apache.org/jira/browse/KARAF-447
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-core
>    Affects Versions: 2.1.3
>            Reporter: Gert Vanthienen
>            Assignee: Jamie goodyear
>             Fix For: 3.1.0
>
>         Attachments: karaf_447.diff
>
>
> When using the org.apache.karaf.main.DefaultJDBCLock class together with PostgreSQL, you can run into this exception (caused by the setQueryTimeout() method not being implemented yet - http://jdbc.postgresql.org/todo.html):
> {noformat}
> Failed to acquire database lock: org.postgresql.util.PSQLException: Method org.postgresql.jdbc4.Jdbc4PreparedStatement.setQueryTimeout(int) is not yet implemented.
> {noformat}
> We should at the very least document that the timeout should be set to 0 for PostgreSQL, but perhaps we'd better create a new JDBC lock implementation that hides this bit of knowledge from the users and provides them with a nice and easy way to use PostgreSQL for JDBC locking.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira