July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3086) Infinite loop when creating more than two Distributed Cache nodes

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3086?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3086: -------------------------------- Priority: Critical (was: Major) > Infinite loop when creating more than two Distributed Cache nodes > ----------------------------------------------------------------- > > Key: ISPN-3086 > URL: https://issues.jboss.org/browse/ISPN-3086 > Project: Infinispan > Issue Type: Bug > Components: JCache > Affects Versions: 5.3.0.Beta1 > Reporter: Balazs Zsoldos > Assignee: Galder Zamarreño > Priority: Critical > Labels: cache, distribution > Fix For: 6.0.0.Final > > > I created a very simple application based on https://docs.jboss.org/author/display/ISPN/Using+Infinispan+as+a+JCache+p... > I changed the code to created distributed caches instead of replicated ones. It works until two nodes but if there are three nodes it starts an infinite loop. > *The modified XML contains:* > <namedCache name="namedCache"> > <clustering mode="dist" /> > </namedCache> > *The modified java code contains:* > CacheManager cacheManager1 = Caching.getCacheManager(new TestClassLoader(tccl), "infinispan-jcache-cluster.xml"); > CacheManager cacheManager2 = Caching.getCacheManager(new TestClassLoader(tccl), "infinispan-jcache-cluster.xml"); > CacheManager cacheManager3 = Caching.getCacheManager(new TestClassLoader(tccl), "infinispan-jcache-cluster.xml"); > *Symptom:* > The code waits on the third command while there is an infinite loop on a background thread. I guess the benefit of distribution would come with more than two nodes but I cannot test it due to the problem above. > Although I used infinispan via JCache I think this issue is not related to the JCache API but it comes from the infinispan core. > *BTW:* Distributed caches seem to me about 30% slower than replicated caches concerning to put and delete functions with two nodes. I guess the benefit would come out between the two topologies with more nodes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3160) RemoteCacheManager javadocs list wrong default pool size

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3160?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3160: -------------------------------- Fix Version/s: 6.0.0.Final > RemoteCacheManager javadocs list wrong default pool size > -------------------------------------------------------- > > Key: ISPN-3160 > URL: https://issues.jboss.org/browse/ISPN-3160 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.1.8.Final > Reporter: Dennis Reed > Assignee: Galder Zamarreño > Priority: Minor > Fix For: 6.0.0.Final > > > RemoteCacheManager javadocs list the default pool size as 10: > "infinispan.client.hotrod.default_executor_factory.pool_size, default = 10." > However, the default is actually 99: > org/infinispan/client/hotrodimpl/ConfigurationProperties.java: return props.getIntProperty(DEFAULT_EXECUTOR_FACTORY_POOL_SIZE, 99); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3160) RemoteCacheManager javadocs list wrong default pool size

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3160?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3160: -------------------------------- Priority: Minor (was: Major) > RemoteCacheManager javadocs list wrong default pool size > -------------------------------------------------------- > > Key: ISPN-3160 > URL: https://issues.jboss.org/browse/ISPN-3160 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.1.8.Final > Reporter: Dennis Reed > Assignee: Galder Zamarreño > Priority: Minor > > RemoteCacheManager javadocs list the default pool size as 10: > "infinispan.client.hotrod.default_executor_factory.pool_size, default = 10." > However, the default is actually 99: > org/infinispan/client/hotrodimpl/ConfigurationProperties.java: return props.getIntProperty(DEFAULT_EXECUTOR_FACTORY_POOL_SIZE, 99); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3223) HotRod Clinet recieves stale toplogy view on instance leave

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3223?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3223: -------------------------------- Fix Version/s: 6.0.0.Final > HotRod Clinet recieves stale toplogy view on instance leave > ----------------------------------------------------------- > > Key: ISPN-3223 > URL: https://issues.jboss.org/browse/ISPN-3223 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.4.Final, 5.3.0.CR1 > Reporter: Takayoshi Kimura > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > When killed a HotRod server node, HotRod Clinet sometimes recieves a stale toplogy view which includes the dead node and uses it as a latest view. In this case the client keeps trying to connect that node and keeps failing. > Looks like the AbstractEncoder1x.generateTopologyResponse() takes care of node join but doesn't handle node leave: > {noformat} > if (!serverEndpointsMap.keySet.containsAll(cacheMembers)) { > {noformat} > For example, serverEndpointsMap.keySet is [A, B, C] and the actual cacheMembers is [A, B]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3270) Hotrod clients removeWithVersion doesn't work with replicated cache

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3270?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3270: -------------------------------- Priority: Critical (was: Major) > Hotrod clients removeWithVersion doesn't work with replicated cache > ------------------------------------------------------------------- > > Key: ISPN-3270 > URL: https://issues.jboss.org/browse/ISPN-3270 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Reporter: Jakub Markos > Assignee: Galder Zamarreño > Priority: Critical > > I have a cluster of 2 latest infinispan servers (6.0.0-SNAPSHOT) with the following container configuration: > {code:xml}<cache-container name="default" default-cache="default" listener-executor="infinispan-listener"> > <transport stack="udp" executor="infinispan-transport" lock-timeout="240000"/> > <replicated-cache name="default" start="EAGER" mode="SYNC" batching="false" remote-timeout="60000"> > <transaction mode="NONE"/> > <state-transfer enabled="true" timeout="60000"/> > </replicated-cache> > </cache-container> > {code} > Running this code: > {code} remoteCache = remoteCacheManager.getCache(); > remoteCache.clear(); > assertFalse(remoteCache.removeWithVersion("aKey", 12321212l)); > remoteCache.put("aKey", "aValue"); > VersionedValue valueBinary = remoteCache.getVersioned("aKey"); > System.out.println("value = " + valueBinary.getValue()); > System.out.println("version = " + valueBinary.getVersion()); > System.out.println(remoteCache.removeWithVersion("aKey",valueBinary.getVersion())); > valueBinary = remoteCache.getVersioned("aKey"); > System.out.println("value = " + valueBinary.getValue()); > System.out.println("version = " + valueBinary.getVersion()); > {code} > results most of the time in (and the other times the removeWithVersion returns false) > {quote} > value = aValue > version = 281483566645249 > true > value = aValue > version = 281483566645249 > {quote} > The command works with distributed/local cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3270) Hotrod clients removeWithVersion doesn't work with replicated cache

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3270?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3270: -------------------------------- Priority: Major (was: Critical) > Hotrod clients removeWithVersion doesn't work with replicated cache > ------------------------------------------------------------------- > > Key: ISPN-3270 > URL: https://issues.jboss.org/browse/ISPN-3270 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Reporter: Jakub Markos > Assignee: Galder Zamarreño > > I have a cluster of 2 latest infinispan servers (6.0.0-SNAPSHOT) with the following container configuration: > {code:xml}<cache-container name="default" default-cache="default" listener-executor="infinispan-listener"> > <transport stack="udp" executor="infinispan-transport" lock-timeout="240000"/> > <replicated-cache name="default" start="EAGER" mode="SYNC" batching="false" remote-timeout="60000"> > <transaction mode="NONE"/> > <state-transfer enabled="true" timeout="60000"/> > </replicated-cache> > </cache-container> > {code} > Running this code: > {code} remoteCache = remoteCacheManager.getCache(); > remoteCache.clear(); > assertFalse(remoteCache.removeWithVersion("aKey", 12321212l)); > remoteCache.put("aKey", "aValue"); > VersionedValue valueBinary = remoteCache.getVersioned("aKey"); > System.out.println("value = " + valueBinary.getValue()); > System.out.println("version = " + valueBinary.getVersion()); > System.out.println(remoteCache.removeWithVersion("aKey",valueBinary.getVersion())); > valueBinary = remoteCache.getVersioned("aKey"); > System.out.println("value = " + valueBinary.getValue()); > System.out.println("version = " + valueBinary.getVersion()); > {code} > results most of the time in (and the other times the removeWithVersion returns false) > {quote} > value = aValue > version = 281483566645249 > true > value = aValue > version = 281483566645249 > {quote} > The command works with distributed/local cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3285) Remove dependency to Lucene Analyzers

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3285?page=com.atlassian.jira.plugin.... ] Sanne Grinovero reassigned ISPN-3285: ------------------------------------- Assignee: Sanne Grinovero (was: Mircea Markus) > Remove dependency to Lucene Analyzers > ------------------------------------- > > Key: ISPN-3285 > URL: https://issues.jboss.org/browse/ISPN-3285 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 6.0.0.Alpha1 > > > Or at least make it optional/test -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3270) Hotrod clients removeWithVersion doesn't work with replicated cache

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3270?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3270: -------------------------------- Fix Version/s: 6.0.0.Final > Hotrod clients removeWithVersion doesn't work with replicated cache > ------------------------------------------------------------------- > > Key: ISPN-3270 > URL: https://issues.jboss.org/browse/ISPN-3270 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Reporter: Jakub Markos > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > I have a cluster of 2 latest infinispan servers (6.0.0-SNAPSHOT) with the following container configuration: > {code:xml}<cache-container name="default" default-cache="default" listener-executor="infinispan-listener"> > <transport stack="udp" executor="infinispan-transport" lock-timeout="240000"/> > <replicated-cache name="default" start="EAGER" mode="SYNC" batching="false" remote-timeout="60000"> > <transaction mode="NONE"/> > <state-transfer enabled="true" timeout="60000"/> > </replicated-cache> > </cache-container> > {code} > Running this code: > {code} remoteCache = remoteCacheManager.getCache(); > remoteCache.clear(); > assertFalse(remoteCache.removeWithVersion("aKey", 12321212l)); > remoteCache.put("aKey", "aValue"); > VersionedValue valueBinary = remoteCache.getVersioned("aKey"); > System.out.println("value = " + valueBinary.getValue()); > System.out.println("version = " + valueBinary.getVersion()); > System.out.println(remoteCache.removeWithVersion("aKey",valueBinary.getVersion())); > valueBinary = remoteCache.getVersioned("aKey"); > System.out.println("value = " + valueBinary.getValue()); > System.out.println("version = " + valueBinary.getVersion()); > {code} > results most of the time in (and the other times the removeWithVersion returns false) > {quote} > value = aValue > version = 281483566645249 > true > value = aValue > version = 281483566645249 > {quote} > The command works with distributed/local cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3284) Remove dependency to Hibernate ORM

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3284: ------------------------------------- Summary: Remove dependency to Hibernate ORM Key: ISPN-3284 URL: https://issues.jboss.org/browse/ISPN-3284 Project: Infinispan Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Mircea Markus Fix For: 6.0.0.Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3285) Remove dependency to Lucene Analyzers

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3285: ------------------------------------- Summary: Remove dependency to Lucene Analyzers Key: ISPN-3285 URL: https://issues.jboss.org/browse/ISPN-3285 Project: Infinispan Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Mircea Markus Fix For: 6.0.0.Alpha1 Or at least make it optional/test -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2013