4:23 p.m.
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: Manik Surtani
Fix For: 4.0.0.BETA1
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
4:33 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-149) Infinispan transaction commit with many modifications
[
https://jira.jboss.org/jira/browse/ISPN-149?page=com.atlassian.jira.plugi...
]
Mircea Markus commented on ISPN-149:
------------------------------------
Test added: LargeTransactionTest
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: Manik Surtani
Fix For: 4.0.0.BETA1
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
4:33 p.m.
New subject: [JBoss JIRA] Assigned: (ISPN-149) Infinispan transaction commit with many modifications
[
https://jira.jboss.org/jira/browse/ISPN-149?page=com.atlassian.jira.plugi...
]
Mircea Markus reassigned ISPN-149:
----------------------------------
Assignee: Mircea Markus (was: Manik Surtani)
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: Mircea Markus
Fix For: 4.0.0.BETA1
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
10:26 a.m.
New subject: [JBoss JIRA] Resolved: (ISPN-149) Infinispan transaction commit with many modifications
[
https://jira.jboss.org/jira/browse/ISPN-149?page=com.atlassian.jira.plugi...
]
Mircea Markus resolved ISPN-149.
--------------------------------
Resolution: Done
Issue was caused by an downcast in ReplicableCommandExternalizer.
byte numArgs = (byte) (args == null ? 0 : args.length);
When we downcast args.length to a byte, if length > 127 then it overflows and args
array (in our case an array of Coomands within a tx) does not get serialized.
The solution was to serialize the entire integer (args.length).
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: Mircea Markus
Fix For: 4.0.0.BETA1
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
11:54 a.m.
New subject: [JBoss JIRA] Reopened: (ISPN-149) Infinispan transaction commit with many modifications
[
https://jira.jboss.org/jira/browse/ISPN-149?page=com.atlassian.jira.plugi...
]
Galder Zamarreno reopened ISPN-149:
-----------------------------------
Assignee: Galder Zamarreno (was: Mircea Markus)
Reopening to implement suggested changes on IRC:
Aug 11 15:46:37 <galderz> hi manik
Aug 11 15:47:05 <manik> galderz hi
Aug 11 15:47:12 <galderz> if we need to write a positive number bigger than a byte,
what would you suggest? writing it as a short, assuming short is good enough, or use a
unsigned int which has variable length?
Aug 11 15:48:58 <galderz> dmlloyd too, thoughts on the above? mmarkus_, u might be
interested in hearing other people's opinion
Aug 11 15:49:06 <galderz> personally, i think i'd stick to a short
Aug 11 15:50:03 <manik> galderz what is this for?
Aug 11 15:50:48 <galderz> ReplicableCommandExternalizer, send the number of
arguments
Aug 11 15:51:02 <galderz> we're previously using a byte but that was not good
enough, since max was 127 params
Aug 11 15:51:11 <galderz> and in long transactions, this was been exceeded
Aug 11 15:51:31 <galderz> https://jira.jboss.org/jira/browse/ISPN-149
Aug 11 15:58:04 <dmlloyd> use both
Aug 11 15:58:17 <dmlloyd> use a different ID byte if it's going to be > 255
Aug 11 15:58:23 <dmlloyd> (also, use an unsigned byte or unsigned short)
Aug 11 15:58:43 <dmlloyd> then it can be 1 byte in the majority of cases, or 2 if
you need the extra range
Aug 11 16:08:19 <manik> galderz yeah, otherwise a variable length int
Aug 11 16:09:05 <galderz> dmlloyd, manik, ok
Aug 11 16:09:19 <galderz> mmarkus_, do u want me to fix this accordingly?
Assigning it to myself.
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.BETA1
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
4:22 p.m.
New subject: [JBoss JIRA] Updated: (ISPN-149) Infinispan transaction commit with many modifications
[
https://jira.jboss.org/jira/browse/ISPN-149?page=com.atlassian.jira.plugi...
]
Manik Surtani updated ISPN-149:
-------------------------------
Fix Version/s: 4.0.0.CR1
(was: 4.0.0.BETA1)
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.CR1
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
12:47 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-149) Infinispan transaction commit with many modifications
[
https://jira.jboss.org/jira/browse/ISPN-149?page=com.atlassian.jira.plugi...
]
Mircea Markus commented on ISPN-149:
------------------------------------
After the disscution I modified the code to use
UnsignedNumeric.writeUnsignedInt(output,numArgs); Guess this is the good approach, right?
I missed it on the #infinispan, sorry.
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.CR1
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
4:47 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-149) Infinispan transaction commit with many modifications
[
https://jira.jboss.org/jira/browse/ISPN-149?page=com.atlassian.jira.plugi...
]
Galder Zamarreno commented on ISPN-149:
---------------------------------------
No, David's point is: if bigger than 255, use an unsigned short, otherwise, use an
unsigned byte.
That way, for most cases, u still send 1 byte and you only send 2 or more when more
parameters are needed.
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.CR1
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
5:51 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-149) Infinispan transaction commit with many modifications
[
https://jira.jboss.org/jira/browse/ISPN-149?page=com.atlassian.jira.plugi...
]
Galder Zamarreno commented on ISPN-149:
---------------------------------------
Actually, just made some comparisons and to cope with different lengths, you end up having
to add an extra byte to differentiate, whereas writeUnsignedInt() can already handle
variable length. This means that currently (needs some debate on the 127 or 255) for bytes
below 127, writeUnsignedInt would write 1 byte whereas David's suggested solution
writes 2 bytes. So, I think Mircea's solution is better.
However, I don't think writeUnsignedInt is as efficient as it could. I'm sending
an email to the dev list wrt to this.
So, for the time being, I'm closing this JIRA again and doing nothing about it.
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.CR1
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
8:02 a.m.
New subject: [JBoss JIRA] Closed: (ISPN-149) Infinispan transaction commit with many modifications
[
https://jira.jboss.org/jira/browse/ISPN-149?page=com.atlassian.jira.plugi...
]
Galder Zamarreno closed ISPN-149.
---------------------------------
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.CR1
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
7:36 p.m.
New subject: [JBoss JIRA] Resolved: (ISPN-149) Infinispan transaction commit with many modifications
[
https://jira.jboss.org/jira/browse/ISPN-149?page=com.atlassian.jira.plugi...
]
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
7:36 p.m.
New subject: [JBoss JIRA] Reopened: (ISPN-149) Infinispan transaction commit with many modifications
[
https://jira.jboss.org/jira/browse/ISPN-149?page=com.atlassian.jira.plugi...
]
Manik Surtani reopened ISPN-149:
--------------------------------
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
5315
days inactive
5375
days old
infinispan-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
Galder Zamarreno (JIRA) -
Manik Surtani (JIRA)
-
Mircea Markus (JIRA)