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

["Guillaume Nodet (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FELIX-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet resolved FELIX-2130.
------------------------------------

    Fix Version/s: karaf 1.6.0
       Resolution: Fixed

I've applied the first patch as I don't think having a growing delay for the keep alive is a good idea.   I would be ok with a different value if there is a need, but using a growing delay would mean that after some time, the delay for the keep alive could be one day, which does not make sense i think.

> [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: Guillaume Nodet
>             Fix For: karaf 1.6.0
>
>         Attachments: felix2130.patch, 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.