[jboss-jira] [JBoss JIRA] Commented: (JBCACHE-1111) PojoCache does not work with BuddyReplication and autoDataGravitation=false

[Brian Stansberry (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBCACHE-1111?page=comments#action_12366233 ] 
            
Brian Stansberry commented on JBCACHE-1111:
-------------------------------------------

I'm adding a org.jboss.cache.pojo.BuddyReplicationTest to show this.  It's really just a copy of o.j.c.p.ReplicatedTest with BR added to the config and method that tries to force data gravitation.  Seems there is no other test of buddy replication in the PojoCache testsuite.

(Note that BuddyReplicationTest has a FIXME in the getReplicatedPerson method.  That's the method that does the data gravitation.  The method is written to illustrate the failure mode I describe above, but once that is fixed it should be changed to just set the Option before the PojoCache.find call.)

> PojoCache does not work with BuddyReplication and autoDataGravitation=false
> ---------------------------------------------------------------------------
>
>                 Key: JBCACHE-1111
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-1111
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: PojoCache
>    Affects Versions: 2.0.0.CR2
>            Reporter: Brian Stansberry
>         Assigned To: Jason T. Greene
>            Priority: Blocker
>
> When buddy replication is enabled and autoDataGravitation=false, PojoCache does not work.  Setting autoDataGravitation=false is the only realistic mode for a BR-enabled app, so this basically means BR doesn't work with PojoCache.  The BR-enabled FIELD granularity session repl tests in AS trunk all fail because of this.
> The problem is basically that when PojoCache traverses a PojoReference to find the actual pojo in _JBossInternal_, it doesn't add a setForceDataGravitation=true Option before making the invocation.  As a result, the node with the actual pojo is not gravitated.
> If you look at o.j.c.p.impl.InternalHelper.get(Fqn fqn, Object key, boolean gravitate), that's where the required Option would be set.  But if you search for calls that pass 'true' as the 'gravitate' param, you find that they all lead to unused methods.  In the 1.4 branch, those methods are used.  Seems this got broken in HEAD.

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