[jboss-jira] [JBoss JIRA] Moved: (JBCLUSTER-268) Distributed locking API should indicate whether taking lock from another node was necessary

[Brian Stansberry (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBCLUSTER-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry moved JBAS-7851 to JBCLUSTER-268:
--------------------------------------------------

          Project: JBoss Clustering  (was: JBoss Application Server)
              Key: JBCLUSTER-268  (was: JBAS-7851)
      Component/s: HA-Server-API
                       (was: Clustering)
    Fix Version/s: HA-Server-API 2.0.0.Beta1
                       (was: JBossAS-6.0.0.M4)


> Distributed locking API should indicate whether taking lock from another node was necessary
> -------------------------------------------------------------------------------------------
>
>                 Key: JBCLUSTER-268
>                 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-268
>             Project: JBoss Clustering
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: HA-Server-API
>            Reporter: Brian Stansberry
>             Fix For: HA-Server-API 2.0.0.Beta1
>
>
> Callers asking for a lock should be able to distinguish these cases:
> 1) Lock can't be obtained
> 2) Lock obtained, and node already held it.
> 3) Lock obtained, but the node had to make a group RPC to get it
> Purpose of this is to use condition 3) as a way to detect failover.
> Related to this, the API should also support creation of a new lock category such that the node immediately owns the lock with no group RPC.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira