[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-149) Infinispan transaction commit with many modifications

[Manik Surtani (JIRA)]

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

Manik Surtani resolved ISPN-149.
--------------------------------

    Fix Version/s: 4.0.0.BETA2
                       (was: 4.0.0.CR1)
       Resolution: Done


> Infinispan transaction commit with many modifications
> -----------------------------------------------------
>
>                 Key: ISPN-149
>                 URL: https://jira.jboss.org/jira/browse/ISPN-149
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 4.0.0.ALPHA6
>            Reporter: Mircea Markus
>            Assignee: Galder Zamarreno
>             Fix For: 4.0.0.BETA2
>
>
> Email from Lukasz Moren
> ----------------------------
> Hello,
> During adapting Infinispan into Hibernate Search I found that trying to commit transaction with many modifications (about 200 or more)
> on cache causes an exception - only if there is more than one member in the cluster. 
> This same problem appears when try to call endBatch(). 
> i.e.:
> begin transaction
> for ( int i = 0; i < 200; i++ )
>          cache.put(key, value);
> commit transaction
> I'm not sure if I do something wrong or it is Infinispan problem. Do you have some idea?  
> Below is configuration I use.
> 		
>                 GlobalConfiguration gc = GlobalConfiguration.getClusteredDefault();
> 		Configuration c = new Configuration();
> 		c.setInvocationBatchingEnabled( true );
> 		c.setCacheMode( Configuration.CacheMode.REPL_SYNC );
> 		c.setSyncReplTimeout( 30000 );
> 		c.setLockAcquisitionTimeout( 60000 );
> 		c.setUseLockStriping( false );
> 		CacheManager manager = new DefaultCacheManager( gc, c );
> 		cache = manager.getCache( "TestCache" );
> 		manager = new DefaultCacheManager( gc, c );
> 		cache2 = manager.getCache( "TestCache" );
> ------------------------

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