You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/07/11 11:02:01 UTC
[jira] [Updated] (KARAF-447) Add JDBC lock implementation for
PostgreSQL
[ https://issues.apache.org/jira/browse/KARAF-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-447:
---------------------------------------
Fix Version/s: (was: 2.2.3)
(was: 3.0.0)
3.1.0
> 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: 3.1.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