[jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-915) PojoCache will rollback concurrent transaction using optimistic locking

[Ben Wang (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCACHE-915?page=all ]

Ben Wang resolved JBCACHE-915.
------------------------------

    Resolution: Done

Resolved with the new internal mapping scheme. See JBCACHE-981.

> PojoCache will rollback concurrent transaction using optimistic locking
> -----------------------------------------------------------------------
>
>                 Key: JBCACHE-915
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-915
>             Project: JBoss Cache
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: PojoCache
>            Reporter: Ben Wang
>         Assigned To: Ben Wang
>             Fix For: 2.0.0.GA
>
>
> This is reported in the forum. Concurrent tx on any pojocache pojo will cause rollback under ALPHA1 release. This is clearly a drawback in the combination of PojoCache and optimistic locking becuase we create a new node under "_JBOSS_INTERNAL__" each time a pojo is created.
> Partial get around is to use Cache.getRegion() api as in this code snippet:
>       String configFile = "META-INF/local-service.xml";
>       boolean toStart = false;
>       cache_ = PojoCacheFactory.createCache(configFile, toStart);
>       cache_.start();
>       cache_.getCache().getRegion(Fqn.fromString(REGION), true);
> This will trigger a region creation and subsquent pojocache operation under that region will be placed separately.

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