felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie goodyear (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FELIX-2130) [Karaf] Failover Clustering Mechanism - Database shutdown / loss results in all Karaf instances becoming Active on restart of that DB
Date Wed, 24 Feb 2010 18:23:27 GMT

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

Jamie goodyear updated FELIX-2130:
----------------------------------

    Attachment: felix2130.txt

File: felix2130.txt

Contains fixes for the two issues outlined in this Jira entry.

> [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
>         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.


Mime
View raw message