[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-404) Provide API to allow multiple callers to safely call activateRegion() .

[Manik Surtani (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBCACHE-404?page=comments#action_12357929 ] 
            
Manik Surtani commented on JBCACHE-404:
---------------------------------------

I've implemented an activateIfEmpty() method in Region and RegionManager - for now this just catches the RNEE and logs rather than re-throws.



> Provide API to allow multiple callers to safely call activateRegion() .
> -----------------------------------------------------------------------
>
>                 Key: JBCACHE-404
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-404
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.2.4SP1, 1.2.4
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 2.0.0.CR1
>
>
> If a caller calls activateRegion() and the region is already active, they will get a RegionNotEmptyException.  Need to add an API to make it easy for use cases where multiple callers may want to activate the same region.
> Use case for this is ClusteredSSO.  Multiple ClusteredSSO valves can be running in the same server; all share the /SSO region.  The TreeCache is shared with session replication, so the activateRegion API needs to be used.  Currently it catches the RegionNotEmptyException, but I don't like this in the ClusteredSSO code.
> Possibilities:
> 1) Add an isRegionActive() method, callers can check first.  But this can lead to race conditions.
> 2) Overload the activateRegion method with a version that won't throw the RegionNotEmptyException.
> Don't want to get rid of the RegionNotEmptyException, as in many uses cases (e.g. session repl) the region should not have data; if it does that's an error condition the application should know about.

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