[ https://issues.apache.org/jira/browse/FELIX-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843766#action_12843766 ]
javier commented on FELIX-2130: ------------------------------- hi, remove the break statement is ok, but the log will grow a lot with a DB error in the loop of the Main#lock(). it would be great a sleep or incremental sleep javier > [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.