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, 02 Aug 2012 10:18:03 GMT

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

Jamie goodyear commented on KARAF-447:

Thanks for the updates to the unit tests Heath :)

$ svn ci 
Sending        main/src/test/java/org/apache/karaf/main/lock/PostgreSQLJDBCLockIntegrationTest.java
Sending        main/src/test/java/org/apache/karaf/main/lock/PostgreSQLJDBCLockTest.java
Transmitting file data ..
Committed revision 1368406.
> 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: 2.2.9, 2.3.0, 3.0.0
>         Attachments: karaf_447.diff, updated-karaf-3.0_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


View raw message