karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie goodyear (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-447) Add JDBC lock implementation for PostgreSQL
Date Thu, 07 Apr 2011 12:54:05 GMT

    [ https://issues.apache.org/jira/browse/KARAF-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016840#comment-13016840
] 

Jamie goodyear commented on KARAF-447:
--------------------------------------

Discussed issue status with reporter. We'll push this one out to at least the next patch roll
up.

> Add JDBC lock implementation for PostgreSQL
> -------------------------------------------
>
>                 Key: KARAF-447
>                 URL: https://issues.apache.org/jira/browse/KARAF-447
>             Project: Karaf
>          Issue Type: Improvement
>          Components: runtime
>    Affects Versions: 2.1.3
>            Reporter: Gert Vanthienen
>             Fix For: 2.2.1, 3.0.0
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message