karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Anstey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-1938) Lock logic should wait for start level change to occur
Date Mon, 22 Oct 2012 13:22:12 GMT

    [ https://issues.apache.org/jira/browse/KARAF-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481352#comment-13481352
] 

Jonathan Anstey commented on KARAF-1938:
----------------------------------------

Thanks Freeman. Yeah, I'll find some time soon to do up trunk & 2.3 patches.

Cheers,
Jon
                
> Lock logic should wait for start level change to occur
> ------------------------------------------------------
>
>                 Key: KARAF-1938
>                 URL: https://issues.apache.org/jira/browse/KARAF-1938
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 2.2.9
>            Reporter: Jonathan Anstey
>            Assignee: Freeman Fang
>         Attachments: KARAF-1938.patch
>
>
> Consider the case where we have a master and slave Karaf instance:
> 1. Master has acquired lock
> ... time passes... 
> 2. Network problem happens
> 3. Master loses lock (due to the network problem) and reduces start level accordingly
> 4. Before start level reduction is complete master manages to grab the lock
> 6. Start level is set back to normal
> Seems that flipping the start level around before the container has time to complete
is not safe. Proposed solution is to just pause the locking loop until the start level is
actually complete before trying to regain the lock. This will prevent flipping of the start
level too quickly. Patch coming soon

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message