March 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-1016) Hash-aware view update causing lock ups in Hot Rod

by Galder Zamarreño (JIRA)

Hash-aware view update causing lock ups in Hot Rod -------------------------------------------------- Key: ISPN-1016 URL: https://issues.jboss.org/browse/ISPN-1016 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.2.1.FINAL Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.2.BETA1, 5.0.0.BETA1 When encoding a Hot Rod response, if the encoder discovers that the client has an old view, it decides that a new topology needs to be sent to the client. Now, when building this view in distributed caches, the encoder checks whether in the new view, any of the nodes hash ids has changed, and if so, it sends a cluster wide replace with the view containing the new hash ids. This seems to cause some deadlocks as shown in JBPAPP-6113 where one node is timing to send the replace to other node, and another node is timing out doing the same. This needs further thinking but have some ideas in mind... On top of that, it appears that a failure here is causing problems the requests after that, so some thinking needs to be done to see if that replace() call can be moved out of there... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (ISPN-1013) Message ids should be logged as decimal

by Galder Zamarreño (JIRA)

Message ids should be logged as decimal --------------------------------------- Key: ISPN-1013 URL: https://issues.jboss.org/browse/ISPN-1013 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.2.1.FINAL Reporter: Galder Zamarreño Assignee: Galder Zamarreño Priority: Minor Fix For: 4.2.2.BETA1, 5.0.0.BETA1 This is confusing: {code}org.infinispan.client.hotrod.exceptions.InvalidResponseException:: Invalid message id. Expected cfec and received 84b6{code} Message Ids are more readable as numbers rather than hex. The protocol uses hex numbers for things like error codes and those make sense being shown as hex so that they can be easily mapped to the protocol documentation. But for msg ids it should be left as is. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (ISPN-1010) ClusteredCacheLoader not detecting multiple responses are equal

by Galder Zamarreño (JIRA)

ClusteredCacheLoader not detecting multiple responses are equal --------------------------------------------------------------- Key: ISPN-1010 URL: https://issues.jboss.org/browse/ISPN-1010 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.2.1.FINAL Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.2.BETA1, 5.0.0.BETA1 Infinispan's clustered cache loader does not seem to be capable of dealing with two or more identical responses: {code}[JBoss] org.infinispan.loaders.CacheLoaderException: Response length is always 0 or 1, received: [SuccessfulResponse{responseValue=ImmortalCacheValue{value=TopologyView(2,List(TopologyAddress(172.17.65.254,11222,Map(),perf02-7642), TopologyAddress(172.17.67.254,11222,Map(),perf04-36806)))}} , SuccessfulResponse{responseValue=ImmortalCacheValue{value=TopologyView(2,List(TopologyAddress(172.17.65.254,11222,Map(),perf02-7642), TopologyAddress(172.17.67.254,11222,Map(),perf04-36806)))}} ] [JBoss] at org.infinispan.loaders.cluster.ClusterCacheLoader.load(ClusterCacheLoader.java:57){code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (ISPN-1017) Livelock creating lots of cache managers in parallel

by Dan Berindei (JIRA)

Livelock creating lots of cache managers in parallel ---------------------------------------------------- Key: ISPN-1017 URL: https://issues.jboss.org/browse/ISPN-1017 Project: Infinispan Issue Type: Bug Components: Locking and Concurrency Reporter: Dan Berindei Assignee: Dan Berindei While running the HotRod client test suite I sometimes get a livelock and the thread dump shows a lot of stack traces like this: "pool-2-thread-20" prio=10 tid=0x6a63ec00 nid=0x2d71 runnable [0x6943e000] java.lang.Thread.State: RUNNABLE at java.util.HashMap.get(HashMap.java:320) at org.infinispan.factories.ComponentRegistry.isGlobal(ComponentRegistry.java:138) at org.infinispan.factories.ComponentRegistry.registerComponent(ComponentRegistry.java:130) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:185) at org.infinispan.factories.AbstractComponentRegistry.getOrCreateComponent(AbstractComponentRegistry.java:326) at org.infinispan.factories.AbstractComponentRegistry.invokeInjectionMethod(AbstractComponentRegistry.java:254) at org.infinispan.factories.AbstractComponentRegistry$Component.injectDependencies(AbstractComponentRegistry.java:843) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:228) at org.infinispan.factories.ComponentRegistry.registerComponent(ComponentRegistry.java:133) at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:185) at org.infinispan.factories.InternalCacheFactory.bootstrap(InternalCacheFactory.java:102) at org.infinispan.factories.InternalCacheFactory.createAndWire(InternalCacheFactory.java:77) at org.infinispan.factories.InternalCacheFactory.createCache(InternalCacheFactory.java:61) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:538) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:443) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:412) at org.infinispan.server.core.AbstractProtocolServer.startDefaultCache(AbstractProtocolServer.scala:108) at org.infinispan.server.core.AbstractProtocolServer.start(AbstractProtocolServer.scala:69) at org.infinispan.server.hotrod.HotRodServer.start(HotRodServer.scala:48) at org.infinispan.server.hotrod.test.HotRodTestingUtil$.startHotRodServer(HotRodTestingUtil.scala:77) at org.infinispan.server.hotrod.test.HotRodTestingUtil$.startHotRodServer(HotRodTestingUtil.scala:57) at org.infinispan.server.hotrod.test.HotRodTestingUtil$.startHotRodServer(HotRodTestingUtil.scala:46) at org.infinispan.server.hotrod.test.HotRodTestingUtil$.startHotRodServer(HotRodTestingUtil.scala:43) at org.infinispan.server.hotrod.test.HotRodTestingUtil$.startHotRodServer(HotRodTestingUtil.scala:37) at org.infinispan.server.hotrod.test.HotRodTestingUtil.startHotRodServer(HotRodTestingUtil.scala) at org.infinispan.client.hotrod.TestHelper.startHotRodServer(TestHelper.java:34) at org.infinispan.client.hotrod.CacheManagerStoppedTest.createCacheManager(CacheManagerStoppedTest.java:31) This seems to be caused by the fact that the componentScopesLookup map is not synchronized and multiple threads write to it at the same time, leaving it in an invalid state. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

5
9
0 / 0

[JBoss JIRA] Created: (ISPN-850) RemoteCache.replaceWithVersion javadoc is incorrect

by Galder Zamarreño (JIRA)

RemoteCache.replaceWithVersion javadoc is incorrect --------------------------------------------------- Key: ISPN-850 URL: https://issues.jboss.org/browse/ISPN-850 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 5.0.0.ALPHA1, 4.2.0.Final Reporter: Galder Zamarreño Assignee: Mircea Markus Priority: Minor Fix For: 5.0.0.BETA1, 5.0.0.Final replaceWithVersion javadoc is incorrect: /** * Removes the given value only if its version matches the supplied version. See {@link #removeWithVersion(Object, * long)} for a sample usage. * * @return true if the method has been replaced * @see #getVersioned(Object) * @see VersionedValue */ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-970) Consider disabling lock striping by default

by Galder Zamarreño (JIRA)

Consider disabling lock striping by default ------------------------------------------- Key: ISPN-970 URL: https://issues.jboss.org/browse/ISPN-970 Project: Infinispan Issue Type: Task Components: Locking and Concurrency Reporter: Galder Zamarreño Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.Final http://community.jboss.org/message/585513#585513 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-1002) Update to JBoss TS 4.14.0.Final

by Manik Surtani (JIRA)

Update to JBoss TS 4.14.0.Final ------------------------------- Key: ISPN-1002 URL: https://issues.jboss.org/browse/ISPN-1002 Project: Infinispan Issue Type: Task Components: Transactions Affects Versions: 4.2.1.FINAL Reporter: Manik Surtani Assignee: Mircea Markus Fix For: 5.0.0.BETA1, 5.0.0.FINAL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (ISPN-957) Make local suite to run with JBossTM

by Mircea Markus (JIRA)

Make local suite to run with JBossTM ------------------------------------ Key: ISPN-957 URL: https://issues.jboss.org/browse/ISPN-957 Project: Infinispan Issue Type: Feature Request Components: Test Suite, Transactions Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.0.0.Final Suite runs faster with JBossTM (vs DummyTM). A explanation for JBossTM over performing DummyTM in spite keeping a tx log on the disk (which dummyTm doesn't) is the fact that it has 2PC optimisations for situations where only one resource is registered. In other words if there is only one cache participating in the transaction (most of our tests are like that) there won't be 2RPC but only one. It would be good to run the local test suite with JBossTM and CoordinatorEnvironmentBean.commitOnePhase=true and CoordinatorEnvironmentBean.commitOnePhase=false on the hudson environment. This would be good for performance. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (ISPN-792) Migrate to David's JBoss Logging

by Galder Zamarreño (JIRA)

Migrate to David's JBoss Logging -------------------------------- Key: ISPN-792 URL: https://jira.jboss.org/browse/ISPN-792 Project: Infinispan Issue Type: Feature Request Reporter: Galder Zamarreño Assignee: Manik Surtani Based on what David Lloyd said in the AS7 podcast, it performs much better than log4j and in particular, when it comes to log level checks (it apparently uses volatile int checks). This could have a direct impact on the Infinispan performance since we do a fair few level checks. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (ISPN-559) refactor transaction class hierarchy

by Mircea Markus (JIRA)

refactor transaction class hierarchy ------------------------------------ Key: ISPN-559 URL: https://jira.jboss.org/browse/ISPN-559 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.0.0.Final Actual transactional logic should be implemented in InitiatorTransaction (vs RemoteTransaction) Rename TxXaAdapter should be renamed to TxCoordinator -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2011