You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Jamie goodyear (JIRA)" <ji...@apache.org> on 2009/10/13 20:26:31 UTC

[jira] Created: (FELIX-1752) [Karaf] Extend DefaultJDBCLock to support MySQL out of the box.

[Karaf] Extend DefaultJDBCLock to support MySQL out of the box.
---------------------------------------------------------------

                 Key: FELIX-1752
                 URL: https://issues.apache.org/jira/browse/FELIX-1752
             Project: Felix
          Issue Type: Improvement
          Components: Karaf
            Reporter: Jamie goodyear
             Fix For: karaf-1.0.2


This is to ensure that the DefaultJDBCLock implementation works with MySQL.

The MySQL 'lock table' mechanism may be used to allow a master process to hold a locking table from slave instances. When the master instance losses connection with the DB the lock is broken allowing a slave instance to take over processing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (FELIX-1752) [Karaf] Extend DefaultJDBCLock to support MySQL out of the box.

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet resolved FELIX-1752.
------------------------------------

    Resolution: Fixed
      Assignee: Guillaume Nodet

Committing to https://svn.apache.org/repos/asf/felix/trunk ...
	A	karaf/main/src/main/java/org/apache/felix/karaf/main/MySQLJDBCLock.java
	M	karaf/main/src/main/java/org/apache/felix/karaf/main/Statements.java
Committed r825040


> [Karaf] Extend DefaultJDBCLock to support MySQL out of the box.
> ---------------------------------------------------------------
>
>                 Key: FELIX-1752
>                 URL: https://issues.apache.org/jira/browse/FELIX-1752
>             Project: Felix
>          Issue Type: Improvement
>          Components: Karaf
>            Reporter: Jamie goodyear
>            Assignee: Guillaume Nodet
>             Fix For: karaf-1.0.2
>
>         Attachments: FELIX-1752.patch
>
>
> This is to ensure that the DefaultJDBCLock implementation works with MySQL.
> The MySQL 'lock table' mechanism may be used to allow a master process to hold a locking table from slave instances. When the master instance losses connection with the DB the lock is broken allowing a slave instance to take over processing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (FELIX-1752) [Karaf] Extend DefaultJDBCLock to support MySQL out of the box.

Posted by "Jamie goodyear (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jamie goodyear updated FELIX-1752:
----------------------------------

    Attachment: FELIX-1752.patch

File: FELIX-1752.patch

This patch introduces support for a MySQL database backend to Karaf locking table.

Users of the MySQLJDBCLock would specify the following in their system.properties file:

karaf.lock.class=org.apache.felix.karaf.main.MySQLJDBCLock
karaf.lock.jdbc.url=jdbc:mysql://address:port/dbname
karaf.lock.jdbc.driver=com.mysql.jdbc.Driver

Note:
A cleaner model for JDBC Lock  support may be in order as additional database support is added (similar to Apache ActiveMQ core JDBC Adaptors).

> [Karaf] Extend DefaultJDBCLock to support MySQL out of the box.
> ---------------------------------------------------------------
>
>                 Key: FELIX-1752
>                 URL: https://issues.apache.org/jira/browse/FELIX-1752
>             Project: Felix
>          Issue Type: Improvement
>          Components: Karaf
>            Reporter: Jamie goodyear
>             Fix For: karaf-1.0.2
>
>         Attachments: FELIX-1752.patch
>
>
> This is to ensure that the DefaultJDBCLock implementation works with MySQL.
> The MySQL 'lock table' mechanism may be used to allow a master process to hold a locking table from slave instances. When the master instance losses connection with the DB the lock is broken allowing a slave instance to take over processing.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.