September 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2229) Fix spelling in error message in InfinispanDirectory.java

by Scott Carlson (JIRA)

Scott Carlson created ISPN-2229: ----------------------------------- Summary: Fix spelling in error message in InfinispanDirectory.java Key: ISPN-2229 URL: https://issues.jboss.org/browse/ISPN-2229 Project: Infinispan Issue Type: Bug Affects Versions: 5.2.0.ALPHA2 Reporter: Scott Carlson Assignee: Manik Surtani Priority: Trivial metadata is spelled incorrectly in InfinispanDirectory.java --- a/lucene-directory/src/main/java/org/infinispan/lucene/InfinispanDirectory.java +++ b/lucene-directory/src/main/java/org/infinispan/lucene/InfinispanDirectory.java @@ -283,7 +283,7 @@ public IndexInput openInput(String name) throws IOException { final FileCacheKey fileKey = new FileCacheKey(indexName, name); FileMetadata fileMetadata = (FileMetadata) metadataCache.get(fileKey); if (fileMetadata == null) { - throw new FileNotFoundException("Error loading medatada for index file: " + fileKey); + throw new FileNotFoundException("Error loading metadata for index file: " + fileKey); } else if (fileMetadata.getSize() <= fileMetadata.getBufferSize()) { //files smaller than chunkSize don't need a readLock @@ -293,7 +293,7 @@ else if (fileMetadata.getSize() <= fileMetadata.getBufferSize()) { boolean locked = readLocks.acquireReadLock(name); if (!locked) { // safest reaction is to tell this file doesn't exist anymore. - throw new FileNotFoundException("Error loading medatada for index file: " + fileKey); + throw new FileNotFoundException("Error loading metadata for index file: " + fileKey); } return new InfinispanIndexInput(chunksCache, fileKey, fileMetadata, readLocks); } -- 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

11 years, 7 months

3
7
0 / 0

[JBoss JIRA] (ISPN-2276) NamedCache problem with xml config

by Ron Albury (JIRA)

Ron Albury created ISPN-2276: -------------------------------- Summary: NamedCache problem with xml config Key: ISPN-2276 URL: https://issues.jboss.org/browse/ISPN-2276 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.1.6.FINAL Environment: XUbuntu 12 Reporter: Ron Albury Assignee: Mircea Markus I am using the Tree API for Infinispan. I want to persist the cache. I started with the following configuration xml for my loader: <infinispan> <default> <loaders passivation="false" shared="false" preload="true"> <loader class="org.infinispan.loaders.file.FileCacheStore" fetchPersistentState="true" purgerThreads="1" purgeSynchronously="true" ignoreModifications="false" purgeOnStartup="false"> <properties> <property name="location" value="/home/eialbur/infiniCache" /> </properties> </loader> </loaders> <invocationBatching enabled="true"/> </default> </infinispan> This worked great, but I wanted it to be a named cache. I modified the xml changing <default> to <namedCache name="foo">. This now produces the runtime error: Cannot enable Invocation Batching when the Transaction Mode is NON_TRANSACTIONAL, set the transaction mode to TRANSACTIONAL So then I modified the xml as follows: <infinispan> <namedCache name="foo" > <loaders passivation="false" shared="false" preload="true"> <loader class="org.infinispan.loaders.file.FileCacheStore" fetchPersistentState="true" purgerThreads="1" purgeSynchronously="true" ignoreModifications="false" purgeOnStartup="false"> <properties> <property name="location" value="/home/eialbur/infiniCache" /> </properties> </loader> </loaders> <transaction transactionMode="TRANSACTIONAL" /> <invocationBatching enabled="true"/> </namedCache> </infinispan> This now produces the following runtime error: invocationBatching is not enabled. Make sure this is enabled by calling configurationBuilder.invocationBatching().enable() I assume this is some sort of problem with Infinispan. It appears that namedCache is having troubles with configuring from xml. -- 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, 7 months

4
6
0 / 0

[JBoss JIRA] (ISPN-2274) Configuration builders for DummyInMemoryCacheStore

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2274: ------------------------------------- Summary: Configuration builders for DummyInMemoryCacheStore Key: ISPN-2274 URL: https://issues.jboss.org/browse/ISPN-2274 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores, Test Suite Affects Versions: 5.2.0.Alpha3 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Minor Fix For: 5.2.0.Alpha4 -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] (ISPN-2197) Cache view instalation takes too long

by Ondrej Nevelik (JIRA)

Ondrej Nevelik created ISPN-2197: ------------------------------------ Summary: Cache view instalation takes too long Key: ISPN-2197 URL: https://issues.jboss.org/browse/ISPN-2197 Project: Infinispan Issue Type: Bug Components: State transfer Reporter: Ondrej Nevelik Assignee: Manik Surtani ISPN000172: Failed to prepare view CacheView{viewId=14, members=[edg-perf05-63964]} for cache t, rolling back to view CacheView{viewId=11, members=[edg-perf05-63964]} java.util.concurrent.ExecutionException: java.lang.IllegalStateException: t: Received cache view prepare request after the local node has already shut down. When testing configuration [1] with lots of caches, it takes too long for the caches to shut down - ~20minutes! See the log [2] for more details.. More specifically we are calling cacheManager.stop() method and then waiting for the cacheManager.getMembers() to be <= 0. The Infinispan used is the one in JDG 6.0.1.ER2. [1] https://svn.devel.redhat.com/repos/jboss-qa/load-testing/etc/jdg-60/radar... [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/JDG-RADAR... -- 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

11 years, 7 months

4
7
0 / 0

[JBoss JIRA] (ISPN-2252) mvn deploy -Pdistribution doesn't uploads the sources

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2252: ----------------------------------- Summary: mvn deploy -Pdistribution doesn't uploads the sources Key: ISPN-2252 URL: https://issues.jboss.org/browse/ISPN-2252 Project: Infinispan Issue Type: Bug Affects Versions: 5.2.0.Alpha3 Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.2.0.Alpha4 Here's why: - the "distribution" which we use for releasing which was initially present in root's pom.xml was also added in "parent/pom.xml" (ISPN-1959). - the sources to be uploaded were generated by an "activeByDefault" profile located in "parent/pom.xml", named "extras" - the "activeByDefault" configuration has a rather error prone semantic, that is it only activates a profile if there's no other profile in the same file explicitly or implicitly active[1] [1] {quote} ... This profile will automatically be active for all builds unless another profile in the same POM is activated using one of the previously described methods. All profiles that are active by default are automatically deactivated when a profile in the POM is activated on the command line or through its activation config. ... {quote} -- 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, 7 months

3
21
0 / 0

[JBoss JIRA] (ISPN-2267) Migrate deprecated configuratuion API in hotrod-client

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2267: ---------------------------------- Summary: Migrate deprecated configuratuion API in hotrod-client Key: ISPN-2267 URL: https://issues.jboss.org/browse/ISPN-2267 Project: Infinispan Issue Type: Sub-task Components: Test Suite Affects Versions: 5.2.0.Alpha3 Reporter: Thomas Fromm Assignee: Mircea Markus -- 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, 7 months

2
5
0 / 0

[JBoss JIRA] (ISPN-2272) Migrate deprecated configuration API in tests spring

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2272: ---------------------------------- Summary: Migrate deprecated configuration API in tests spring Key: ISPN-2272 URL: https://issues.jboss.org/browse/ISPN-2272 Project: Infinispan Issue Type: Sub-task Components: Test Suite Affects Versions: 5.2.0.Alpha3 Reporter: Thomas Fromm Assignee: Thomas Fromm -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] (ISPN-2275) Migrate Cassandra Cache Store to CQL3

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2275: ------------------------------------- Summary: Migrate Cassandra Cache Store to CQL3 Key: ISPN-2275 URL: https://issues.jboss.org/browse/ISPN-2275 Project: Infinispan Issue Type: Task Components: Loaders and Stores Affects Versions: 5.2.0.Alpha3 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Minor Fix For: 6.0.0.Final -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2185) AtomicHashMapProxy calls Cache.getCacheConfiguration() triggering legacy config adaptation.

by Paul Ferraro (JIRA)

Paul Ferraro created ISPN-2185: ---------------------------------- Summary: AtomicHashMapProxy calls Cache.getCacheConfiguration() triggering legacy config adaptation. Key: ISPN-2185 URL: https://issues.jboss.org/browse/ISPN-2185 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.1.5.FINAL Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Critical Fix For: 5.1.6.FINAL (JDG) The following commit: https://github.com/infinispan/infinispan/commit/672e91fab76c882498c24f5bf... adds a call to Cache.getCacheConfiguration(). In 5.1.x, this triggers a call to LegacyConfigurationAdaptor.adapt(...). In AS7, this has a consequence of: * a performance penalty per new cache entry (we use an atomic map per session) * an INFO log message containing a warning about the eviction configuration -- 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

11 years, 7 months

3
9
0 / 0

[JBoss JIRA] (ISPN-2263) ConcurrentModificationException during cancellation of outbound state transfer

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-2263: ----------------------------------- Summary: ConcurrentModificationException during cancellation of outbound state transfer Key: ISPN-2263 URL: https://issues.jboss.org/browse/ISPN-2263 Project: Infinispan Issue Type: Feature Request Components: State transfer Affects Versions: 5.2.0.Alpha3 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 5.2.0.Alpha4 The following exception is thrown on the sender node when a receiving node leaves the cache during state transfer. The leave should result in cancellation of outbound state transfers but this fails with the exception seen below: Caused by: java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) [classes.jar:1.6.0_33] at java.util.AbstractList$Itr.next(AbstractList.java:343) [classes.jar:1.6.0_33] at org.infinispan.statetransfer.StateProviderImpl.cancelOutboundTransfer(StateProviderImpl.java:285) [infinispan-core-5.2.0.Alpha3.jar:5.2.0.Alpha3] at org.infinispan.statetransfer.StateRequestCommand.perform(StateRequestCommand.java:96) [infinispan-core-5.2.0.Alpha3.jar:5.2.0.Alpha3] at org.infinispan.remoting.InboundInvocationHandlerImpl.handleInternal(InboundInvocationHandlerImpl.java:95) [infinispan-core-5.2.0.Alpha3.jar:5.2.0.Alpha3] at org.infinispan.remoting.InboundInvocationHandlerImpl.handleWithWaitForBlocks(InboundInvocationHandlerImpl.java:110) [infinispan-core-5.2.0.Alpha3.jar:5.2.0.Alpha3] at org.infinispan.remoting.InboundInvocationHandlerImpl.handle(InboundInvocationHandlerImpl.java:82) [infinispan-core-5.2.0.Alpha3.jar:5.2.0.Alpha3] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.executeCommand(CommandAwareRpcDispatcher.java:228) [infinispan-core-5.2.0.Alpha3.jar:5.2.0.Alpha3] at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle(CommandAwareRpcDispatcher.java:208) [infinispan-core-5.2.0.Alpha3.jar:5.2.0.Alpha3] at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:465) at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:372) at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:247) at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:601) at org.jgroups.blocks.mux.MuxUpHandler.up(MuxUpHandler.java:130) at org.jgroups.JChannel.up(JChannel.java:715) at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1020) at org.jgroups.protocols.RSVP.up(RSVP.java:192) at org.jgroups.protocols.FRAG2.up(FRAG2.java:181) at org.jgroups.protocols.FlowControl.up(FlowControl.java:418) at org.jgroups.protocols.FlowControl.up(FlowControl.java:400) at org.jgroups.protocols.pbcast.GMS.up(GMS.java:899) at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:244) at org.jgroups.protocols.UNICAST2.handleDataReceived(UNICAST2.java:744) at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:414) at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:608) at org.jgroups.protocols.BARRIER.up(BARRIER.java:102) at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:143) at org.jgroups.protocols.FD.up(FD.java:273) at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:288) at org.jgroups.protocols.MERGE2.up(MERGE2.java:205) at org.jgroups.protocols.Discovery.up(Discovery.java:359) at org.jgroups.protocols.TP$ProtocolAdapter.up(TP.java:2568) at org.jgroups.protocols.TP.passMessageUp(TP.java:1211) at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1775) at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1748) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_33] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_33] -- 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, 7 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2012