October 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-1427) Redesign HotRod client retry tests

by Galder Zamarreño (JIRA)

Redesign HotRod client retry tests ---------------------------------- Key: ISPN-1427 URL: https://issues.jboss.org/browse/ISPN-1427 Project: Infinispan Issue Type: Task Components: Cache Server Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.BETA2 Redesign ReplicationRetryTest, ServerFailureRetryTest and DistributionRetryTest. Basically, each test is creating brand new Hot Rod servers but not all are being closed. This is leading to binding issues in tests after that in CI (i.e. https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/org.in...) At the same time, try to make the tests a bit more readable. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

4
7
0 / 0

[JBoss JIRA] (ISPN-1452) Separate FluentTypes into a different file and make it public

by Galder Zamarreño (Created) (JIRA)

Separate FluentTypes into a different file and make it public ------------------------------------------------------------- Key: ISPN-1452 URL: https://issues.jboss.org/browse/ISPN-1452 Project: Infinispan Issue Type: Enhancement Components: Cache Server, Configuration Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.CR1 Move FluentTypes into a separate Java file and make it public. This is to make it easier for Scala classes to build fluent configurations. Scala seems to have stricter access rules and as a result it has issues finding the methods in that interface. Separating it into a public interface in a separate file should solve the issue. It should not cause compatibility issues. Once this is in, convert Hot Rod topology cache configuration definition to fluent. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
2
0 / 0

[JBoss JIRA] (ISPN-1496) FineGrainedAtomicMap not working with REPEATABLE_READ isolation

by Sanne Grinovero (Created) (JIRA)

FineGrainedAtomicMap not working with REPEATABLE_READ isolation --------------------------------------------------------------- Key: ISPN-1496 URL: https://issues.jboss.org/browse/ISPN-1496 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.1.0.BETA3 Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.1.0.BETA4 When using REPEATABLE_READ as isolation level, after the commit all data I stored during the transaction are gone. We'll need enough test coverage for REPEATABLE_READ too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

4
3
0 / 0

[JBoss JIRA] Created: (ISPN-1369) Make c3p0 an optional dependency of cachstore-jdbc

by Paul Ferraro (JIRA)

Make c3p0 an optional dependency of cachstore-jdbc -------------------------------------------------- Key: ISPN-1369 URL: https://issues.jboss.org/browse/ISPN-1369 Project: Infinispan Issue Type: Task Components: Loaders and Stores Affects Versions: 5.0.0.FINAL Reporter: Paul Ferraro Assignee: Manik Surtani Since c3p0 is only used for pooled connection factories, it should not be a required runtime dependency. Specifically, AS7 would rather not pull in c3p0 since AS7 will always use this cache store in conjunction with a managed connection factory. To make c3p0 optional, c3p0 classes should only be imported by the PooledConnectionFactory itself. Currently, there are c3p0 import statements within org.infinispan.loaders.jdbc.logging.Log which prevent c3p0 from being "optional". N.B. To indicate a optional dependency in maven: <dependency> <groupId>c3p0</groupId> <artifactId>c3p0</artifactId> <version>...</version> <optional>true</optional> </dependency> This will prevent c3p0 from being treated as a transient dependency of org.infinispan:infinispan-cachestore-jdbc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

4
5
0 / 0

[JBoss JIRA] (ISPN-1470) Using cache loader preload with DIST triggers NPE

by Paul Ferraro (Created) (JIRA)

Using cache loader preload with DIST triggers NPE ------------------------------------------------- Key: ISPN-1470 URL: https://issues.jboss.org/browse/ISPN-1470 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 5.1.0.BETA2 Reporter: Paul Ferraro Assignee: Manik Surtani Priority: Critical As illustrated by the stacktrace below, the DistributionManagerImpl's ConsistentHash hasn't been set yet, causing an NPE. Oct 19, 2011 3:08:16 PM org.infinispan.interceptors.InvocationContextInterceptor handleAll ERROR: ISPN000136: Execution error java.lang.NullPointerException at org.infinispan.distribution.DistributionManagerImpl.getLocality(DistributionManagerImpl.java:120) at org.infinispan.interceptors.locking.ClusteringDependentLogic$DistributionLogic.localNodeIsOwner(ClusteringDependentLogic.java:85) at org.infinispan.interceptors.locking.ClusteringDependentLogic$DistributionLogic.commitEntry(ClusteringDependentLogic.java:92) at org.infinispan.interceptors.EntryWrappingInterceptor.commitContextEntries(EntryWrappingInterceptor.java:172) at org.infinispan.interceptors.EntryWrappingInterceptor.visitCommitCommand(EntryWrappingInterceptor.java:94) at org.infinispan.commands.tx.CommitCommand.acceptVisitor(CommitCommand.java:66) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:119) at org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.visitCommitCommand(AbstractTxLockingInterceptor.java:47) at org.infinispan.commands.tx.CommitCommand.acceptVisitor(CommitCommand.java:66) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:119) at org.infinispan.interceptors.NotificationInterceptor.visitCommitCommand(NotificationInterceptor.java:56) at org.infinispan.commands.tx.CommitCommand.acceptVisitor(CommitCommand.java:66) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:119) at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:133) at org.infinispan.commands.AbstractVisitor.visitCommitCommand(AbstractVisitor.java:116) at org.infinispan.commands.tx.CommitCommand.acceptVisitor(CommitCommand.java:66) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:119) at org.infinispan.interceptors.TxInterceptor.visitCommitCommand(TxInterceptor.java:121) at org.infinispan.interceptors.DistTxInterceptor.visitCommitCommand(DistTxInterceptor.java:77) at org.infinispan.commands.tx.CommitCommand.acceptVisitor(CommitCommand.java:66) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:119) at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:133) at org.infinispan.commands.AbstractVisitor.visitCommitCommand(AbstractVisitor.java:116) at org.infinispan.interceptors.StateTransferLockInterceptor.visitCommitCommand(StateTransferLockInterceptor.java:86) at org.infinispan.commands.tx.CommitCommand.acceptVisitor(CommitCommand.java:66) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:119) at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:104) at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:64) at org.infinispan.commands.AbstractVisitor.visitCommitCommand(AbstractVisitor.java:116) at org.infinispan.commands.tx.CommitCommand.acceptVisitor(CommitCommand.java:66) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:119) at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:133) at org.infinispan.commands.AbstractVisitor.visitCommitCommand(AbstractVisitor.java:116) at org.infinispan.commands.tx.CommitCommand.acceptVisitor(CommitCommand.java:66) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:119) at org.infinispan.interceptors.BatchingInterceptor.handleDefault(BatchingInterceptor.java:77) at org.infinispan.commands.AbstractVisitor.visitCommitCommand(AbstractVisitor.java:116) at org.infinispan.commands.tx.CommitCommand.acceptVisitor(CommitCommand.java:66) at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:318) at org.infinispan.transaction.TransactionCoordinator.commit(TransactionCoordinator.java:134) at org.infinispan.transaction.xa.TransactionXaAdapter.commit(TransactionXaAdapter.java:127) at org.infinispan.transaction.tm.DummyTransaction.runCommitTx(DummyTransaction.java:312) at org.infinispan.transaction.tm.DummyTransaction.commit(DummyTransaction.java:99) at org.infinispan.transaction.tm.DummyBaseTransactionManager.commit(DummyBaseTransactionManager.java:97) at org.infinispan.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:913) at org.infinispan.CacheImpl.put(CacheImpl.java:620) at org.infinispan.DecoratedCache.put(DecoratedCache.java:147) at org.infinispan.loaders.CacheLoaderManagerImpl.preload(CacheLoaderManagerImpl.java:162) at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:203) at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:825) at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:624) at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:527) at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:177) at org.infinispan.CacheImpl.start(CacheImpl.java:462) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:572) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:451) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:424) at org.jboss.as.web.session.SessionTestUtil$3.getCache(SessionTestUtil.java:214) at org.jboss.as.web.session.SessionTestUtil$1.getCache(SessionTestUtil.java:116) at org.jboss.as.clustering.web.infinispan.DistributedCacheManagerFactory.getDistributedCacheManager(DistributedCacheManagerFactory.java:83) at org.jboss.as.web.session.DistributableSessionManager.<init>(DistributableSessionManager.java:176) at org.jboss.as.web.session.SessionTestUtil.createManager(SessionTestUtil.java:130) at org.jboss.as.web.session.SessionCountUnitTestCase.replicatedWarRedeployTest(SessionCountUnitTestCase.java:645) at org.jboss.as.web.session.SessionCountUnitTestCase.testReplicatedRestart(SessionCountUnitTestCase.java:556) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

7
7
0 / 0

[JBoss JIRA] (ISPN-1442) Document that startBatch and endBatch operations on RemoteCache are not supported

by Martin Gencur (Created) (JIRA)

Document that startBatch and endBatch operations on RemoteCache are not supported --------------------------------------------------------------------------------- Key: ISPN-1442 URL: https://issues.jboss.org/browse/ISPN-1442 Project: Infinispan Issue Type: Task Reporter: Martin Gencur Assignee: Pete Muir Looking at http://docs.jboss.org/infinispan/5.1/apidocs/org/infinispan/client/hotrod... , it seems that these operations are supported even though they're not. Please add some note to their description. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

4
4
0 / 0

[JBoss JIRA] (ISPN-1494) 5.1 config documentation not complete

by Galder Zamarreño (Created) (JIRA)

5.1 config documentation not complete ------------------------------------- Key: ISPN-1494 URL: https://issues.jboss.org/browse/ISPN-1494 Project: Infinispan Issue Type: Bug Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.BETA4 Seems like the 5.1.0.BETA3 release did not generate the config.html file correctly: http://docs.jboss.org/infinispan/5.1/apidocs/config.html It seems to stop after hash seed. Fix and upload a new version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

4
3
0 / 0

[JBoss JIRA] (ISPN-1490) Separate API and common classes from core

by Tristan Tarrant (Created) (JIRA)

Separate API and common classes from core ----------------------------------------- Key: ISPN-1490 URL: https://issues.jboss.org/browse/ISPN-1490 Project: Infinispan Issue Type: Task Affects Versions: 5.1.0.BETA2 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 5.1.0.CR1 API and Common classes should be extracted from core so that they can be used from other modules without too much depdency baggage. The main use case for this is to reduce the dependencies required by the Hot Rod client. This would mean creating two new modules: infinispan-api and infinispan-commons. Infinispan-api would contain the interfaces of the relevant APIs Infinispan-commons would contain utility classes and common API implementations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
2
0 / 0

[JBoss JIRA] (ISPN-1499) Fix failing test in Query: KeyTransformationUsingClassloadersTest

by Sanne Grinovero (Created) (JIRA)

Fix failing test in Query: KeyTransformationUsingClassloadersTest ----------------------------------------------------------------- Key: ISPN-1499 URL: https://issues.jboss.org/browse/ISPN-1499 Project: Infinispan Issue Type: Task Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
3
0 / 0

[JBoss JIRA] (ISPN-1500) SerializationType doesn't visit AdvancedExternalizersType

by William Burns (Created) (JIRA)

SerializationType doesn't visit AdvancedExternalizersType --------------------------------------------------------- Key: ISPN-1500 URL: https://issues.jboss.org/browse/ISPN-1500 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.0.1.FINAL Reporter: William Burns Assignee: Manik Surtani Using infinispan, we have multiple infinispan.xml files that are used to configure our caches. The overrides used on default and cache configurations work great for this. I noticed there is no override global configuration support. So I was trying to make my own for the stuff we needed. One of the items we need to "override" is the serialization configs (it is more additive than override). When doing this I found that the SerializationType doesn't properly pass off the vistor to the AdvancedExternalizersType and thus I can't visit the Type or Configs, which would make doing this much easier. I was hoping I could keep a List of AdvancedSerializationConfigs that it visits and then in my override method just add these Configs 1 by 1 to the SerializationType since it has the public methods to add AdvancedSerializers. It seems to be just an oversight but I would expect the accept method of SerializationType to be the following instead (just added the accept to AdvancedExternalizersType). {code} public void accept(ConfigurationBeanVisitor v) { this.externalizerTypes.accept(v); v.visitSerializationType(this); } {code} Side note I noticed the AdvancedExternalizersType has addExternalizer as package level. It would be easier to just call that method instead of having to detect the id myself and whether an object or class is configured in the AdvancedSerializerConfig to decide what add to call, since I could just do a straight add of the Config. Also there is no way to remove or detect what AdvancedSerializers are present on the SerializationType, which would be very helpful when trying to replace a given AdvancedSerializers. Or are the AdvancedSerializerConfigs used started at the end of the list? This would be preferable, because then I wouldn't care if another existed since the one I just added would take priority. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

9
16
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2011