[jira] Commented: (FELIX-2130) [Karaf] Failover Clustering Mechanism - Database shutdown / loss results in all Karaf instances becoming Active on restart of that DB

["Jamie goodyear (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862352#action_12862352 ] 

Jamie goodyear commented on FELIX-2130:
---------------------------------------

Hi,

In the event that the DB is lost already exists a "Thread.sleep(lockDelay);" within the Main#lock method -- we can extend this out to be a larger value or as you suggested make this an incremental delay. Will post back an updated patch, thanks for that catch.

Jamie

> [Karaf] Failover Clustering Mechanism - Database shutdown / loss results in all Karaf instances becoming Active on restart of that DB
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-2130
>                 URL: https://issues.apache.org/jira/browse/FELIX-2130
>             Project: Felix
>          Issue Type: Bug
>          Components: Karaf
>         Environment: Oracle XE Database backend for Karaf JDBC Lock.
>            Reporter: Jamie goodyear
>            Assignee: Chris Custine
>         Attachments: felix2130.txt
>
>
> Two part issue.
> 1) Oracle isAlive() method needs to poll its connection to DB to ensure connection alive.
> 2) Main#lock() remove second break statement - in the event of DB service loss this breaks the lock out of normal spin lock routine.
> I'll be supplying a patch for this issue.

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