karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Created] (KARAF-2523) Karaf JDBC lock doesn't word with M$ SQLServer
Date Sun, 20 Oct 2013 23:22:41 GMT
Jean-Baptiste Onofré created KARAF-2523:
-------------------------------------------

             Summary: Karaf JDBC lock doesn't word with M$ SQLServer
                 Key: KARAF-2523
                 URL: https://issues.apache.org/jira/browse/KARAF-2523
             Project: Karaf
          Issue Type: Bug
          Components: karaf-core
    Affects Versions: 2.3.0
            Reporter: Jean-Baptiste Onofré
            Assignee: Jean-Baptiste Onofré
             Fix For: 2.4.0, 3.0.0, 2.3.4


Using the M$ SQLServer (with jtds) as lock backend (and the Karaf default JDBC lock implementation)
with this configuration:

#setup in system.properties
 
karaf.lock=true
karaf.lock.class=org.apache.karaf.main.DefaultJDBCLock
karaf.lock.level=50
karaf.lock.delay=10
karaf.lock.jdbc.url=jdbc:jtds:sqlserver://xxx;databaseName=evillarr
karaf.lock.jdbc.driver=net.sourceforge.jtds.jdbc.Driver
karaf.lock.jdbc.user=xxx
karaf.lock.jdbc.password=xxx
karaf.lock.jdbc.table=KARAF_LOCK
karaf.lock.jdbc.clustername=karaf
karaf.lock.jdbc.timeout=30
 
Karaf doesn't start because it can't acquire the lock:
 
2013-10-21 09:47:42 | WARN | Thread-28 | - - | Failed to acquire database lock: java.sql.SQLException:
Line 1: FOR UPDATE clause allowed only for DECLARE CURSOR.

As SQLServer doesn't support the "select ... for update" statement, we have to provide a MSSQLServerLock
implementation using a different SQL query.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message