karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-1572) Add SQL Server Support for JDBC Lock
Date Thu, 28 Jun 2012 17:46:57 GMT

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

Christian Schneider commented on KARAF-1572:

While this might work it sounds a lot more complicated than what we have now. I also do not
understand it well enough to be sure it really works reliably. In any case it is really important
that when an instance that is active dies another instance will take over. The current implementation
makes sure this happens. So I am not sure if it would be a good idea to change the locking
like this.

Still it makes sense that you send the patch. I hope we have some others to join in and discuss
your solution.

> Add SQL Server Support for JDBC Lock 
> -------------------------------------
>                 Key: KARAF-1572
>                 URL: https://issues.apache.org/jira/browse/KARAF-1572
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-instance
>    Affects Versions: 2.2.7
>            Reporter: Claudio Corsi
>             Fix For: 2.2.9, 2.3.0, 3.1.0
> The current JDBCLock implementations do not work when using Microsoft SQL Server since
this requires that you use a CURSOR with the SELECT statement.

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