February 2013 - infinispan-issues

[JBoss JIRA] (ISPN-1697) Empty Infinispan config starting transport

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1697?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1697: -------------------------------- Assignee: Galder Zamarreño (was: Manik Surtani) > Empty Infinispan config starting transport > ------------------------------------------ > > Key: ISPN-1697 > URL: https://issues.jboss.org/browse/ISPN-1697 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 5.3.0.Final > > > Note: I think ISPN-1691 and ISPN-1692 will fix this (This failure happens without them applied). Making a note just in case... > Running the testsuite I see: > {code} <failure message="Unknown warning discovered in file minimal.xml: JOIN(dhcp-144-239-26807) sent to dhcp-144-239-47868 timed out (after 3000 ms), > retrying" type="java.lang.AssertionError">java.lang.AssertionError: Unknown warning discovered in file minimal.xml: JOIN(dhcp-144-239-26807) sent to dhcp-144- > 239-47868 timed out (after 3000 ms), retrying > at org.infinispan.config.SampleConfigFilesCorrectnessTest.testConfigWarnings(SampleConfigFilesCorrectnessTest.java:80) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > {code} > minimal.xml has no global configuration (nor transport) defined, so why on earth does a JOIN happen? -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1345) Dirty reads may occurs on mutable objects

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1345?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1345: -------------------------------- Fix Version/s: 5.3.0.Final (was: 6.0.0.Final) > Dirty reads may occurs on mutable objects > ----------------------------------------- > > Key: ISPN-1345 > URL: https://issues.jboss.org/browse/ISPN-1345 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 5.0.0.FINAL > Environment: Windows Java 1.6.0_26 > Reporter: Christophe Labouisse > Assignee: Manik Surtani > Fix For: 5.3.0.Final > > > In local mode, I create a cache like this: > {code} > cacheManager = new DefaultCacheManager(); > cacheManager.getDefaultConfiguration().fluent().storeAsBinary().transaction().cacheStopTimeout(5000); > final Configuration config = new Configuration().fluent().transactionManagerLookup(this.tmLookup).locking() > .isolationLevel(IsolationLevel.READ_COMMITED).build(); > this.cacheManager.defineConfiguration("Gruik", config); > this.cache = this.cacheManager.getCache("Gruik"); > {code} > When retrieving data using {{cache.get(_key_)}} I find out that Infinispan returns the object instance actually stored in the cache datastore. This is OK when the inserted objects are immutable but fails to achieve isolation when using mutable objects. > For instance on a simple Pojo with a {{get/setValue}}. > ||Step||Reader||Writer|| > |1|Starts transaction| | > |2|{{value = cache.get(KEY);}}| | > |3|{{System.out.println(value.getValue());}} Prints 42| | > |4| |Starts transaction| > |5| |{{value = cache.get(KEY);}} Same instance than step 2| > |6| |{{value.setValue(666); // Prepare update}}| > |7|{{System.out.println(value.getValue());}} Prints 666 !| | > |8|{{value = cache.get(KEY);}} Same instance than step 2| | > |9| |{{cache.put(KEY,value);}}| > |10| |Commits transaction| > |11|{{value = cache.get(KEY);}} Same instance than step 2| | > |12|{{System.out.println(value.getValue());}} Prints 666| | > |13|Commits transaction| | > According to the READ_COMMITTED specification, the value printed on step 7 should be 42 as the change to 666 is not committed yet. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1876) clustered query is not executed on the right cache

by Israel Lacerra (JIRA)

[ https://issues.jboss.org/browse/ISPN-1876?page=com.atlassian.jira.plugin.... ] Israel Lacerra commented on ISPN-1876: -------------------------------------- Hi Mircea! Sorry for the looooong inactivity (too much work). I will solve this until the end of february, ok? > clustered query is not executed on the right cache > -------------------------------------------------- > > Key: ISPN-1876 > URL: https://issues.jboss.org/browse/ISPN-1876 > Project: Infinispan > Issue Type: Bug > Components: Querying, RPC > Affects Versions: 5.1.1.FINAL > Reporter: Mathieu Lachance > Assignee: Israel Lacerra > > when using clustered query, command is not executed on the right cache. > when debuging, in CommandAwareRpcDispatcher::executeCommand() > cmd = ClusteredQuery{cache="the-good-cache-name"} > cmd.cache = "the-bad-cache-name" > cmd.cacheName = "the-good-cache-name" -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1501) DefaultCacheManager should not use net.jcip.annotations.GuardedBy annotation

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1501?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-1501. --------------------------------- Resolution: Rejected > DefaultCacheManager should not use net.jcip.annotations.GuardedBy annotation > ---------------------------------------------------------------------------- > > Key: ISPN-1501 > URL: https://issues.jboss.org/browse/ISPN-1501 > Project: Infinispan > Issue Type: Bug > Components: Core API > Affects Versions: 4.2.1.FINAL > Environment: MacOSx, Java6 > Reporter: Jerome R. > Assignee: Manik Surtani > > In infinispan-core artificat : > I suspect that DefaultCacheManage uses annotation net.jcip.annotations.GuardedBy instead of org.jgroups.annotations.GuardedBy > JCIP is not in the dependency tree of the infinispan-core module. > It causes some problem with some annotation processing (maven plugin), due to the missing dependency. > Best regards -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1697) Empty Infinispan config starting transport

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1697?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1697: -------------------------------- Fix Version/s: 5.3.0.Final > Empty Infinispan config starting transport > ------------------------------------------ > > Key: ISPN-1697 > URL: https://issues.jboss.org/browse/ISPN-1697 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Manik Surtani > Fix For: 5.3.0.Final > > > Note: I think ISPN-1691 and ISPN-1692 will fix this (This failure happens without them applied). Making a note just in case... > Running the testsuite I see: > {code} <failure message="Unknown warning discovered in file minimal.xml: JOIN(dhcp-144-239-26807) sent to dhcp-144-239-47868 timed out (after 3000 ms), > retrying" type="java.lang.AssertionError">java.lang.AssertionError: Unknown warning discovered in file minimal.xml: JOIN(dhcp-144-239-26807) sent to dhcp-144- > 239-47868 timed out (after 3000 ms), retrying > at org.infinispan.config.SampleConfigFilesCorrectnessTest.testConfigWarnings(SampleConfigFilesCorrectnessTest.java:80) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > {code} > minimal.xml has no global configuration (nor transport) defined, so why on earth does a JOIN happen? -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2115) Relative path in rhq ant task cause build to fail

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2115?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2115: -------------------------------- Assignee: Galder Zamarreño (was: Manik Surtani) > Relative path in rhq ant task cause build to fail > ------------------------------------------------- > > Key: ISPN-2115 > URL: https://issues.jboss.org/browse/ISPN-2115 > Project: Infinispan > Issue Type: Bug > Components: Build process > Reporter: Thomas Fromm > Assignee: Galder Zamarreño > > When the directory ../../ above the infinispan source dir is not writable, > than build fails: > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (deploy) on project infinispan-rhq-plugin: An Ant BuildException has occured: Directory /usr/local/inubit/jon/dev-container/jbossas/server/default/deploy/${rhq.earName}/rhq-downloads/rhq-plugins creation was not successful for an unknown reason > [ERROR] around Ant part ...<mkdir dir="../../..//jon/dev-container/jbossas/server/default/deploy/${rhq.earName}/rhq-downloads/rhq-plugins"/>... @ 4:116 in /usr/local/inubit/tf/infinispan/rhq-plugin/target/antrun/build-main.xml > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (deploy) on project infinispan-rhq-plugin: An Ant BuildException has occured: Directory /usr/local/inubit/jon/dev-container/jbossas/server/default/deploy/${rhq.earName}/rhq-downloads/rhq-plugins creation was not successful for an unknown reason > In current case the /usr/local/inubit/ is not writable for the user. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2115) Relative path in rhq ant task cause build to fail

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2115?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2115: -------------------------------- Fix Version/s: 5.3.0.Final > Relative path in rhq ant task cause build to fail > ------------------------------------------------- > > Key: ISPN-2115 > URL: https://issues.jboss.org/browse/ISPN-2115 > Project: Infinispan > Issue Type: Bug > Components: Build process > Reporter: Thomas Fromm > Assignee: Galder Zamarreño > Fix For: 5.3.0.Final > > > When the directory ../../ above the infinispan source dir is not writable, > than build fails: > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (deploy) on project infinispan-rhq-plugin: An Ant BuildException has occured: Directory /usr/local/inubit/jon/dev-container/jbossas/server/default/deploy/${rhq.earName}/rhq-downloads/rhq-plugins creation was not successful for an unknown reason > [ERROR] around Ant part ...<mkdir dir="../../..//jon/dev-container/jbossas/server/default/deploy/${rhq.earName}/rhq-downloads/rhq-plugins"/>... @ 4:116 in /usr/local/inubit/tf/infinispan/rhq-plugin/target/antrun/build-main.xml > [ERROR] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (deploy) on project infinispan-rhq-plugin: An Ant BuildException has occured: Directory /usr/local/inubit/jon/dev-container/jbossas/server/default/deploy/${rhq.earName}/rhq-downloads/rhq-plugins creation was not successful for an unknown reason > In current case the /usr/local/inubit/ is not writable for the user. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2059) Custom CacheLoaders are treated as CacheStores unless annotated with @CacheLoaderMetadata

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2059?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2059: -------------------------------- Assignee: Tristan Tarrant (was: Manik Surtani) > Custom CacheLoaders are treated as CacheStores unless annotated with @CacheLoaderMetadata > ----------------------------------------------------------------------------------------- > > Key: ISPN-2059 > URL: https://issues.jboss.org/browse/ISPN-2059 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.1.6.FINAL > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 6.0.0.Final > > > If the @CacheLoaderMetadata is missing, Infinispan will treat the CacheLoader as a CacheStore: if it's not implementing CacheStore as well the component will fail. > @CacheLoaderMetadata should be optional. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2059) Custom CacheLoaders are treated as CacheStores unless annotated with @CacheLoaderMetadata

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2059?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2059: -------------------------------- Fix Version/s: 5.2.1 5.3.0.Final (was: 6.0.0.Final) > Custom CacheLoaders are treated as CacheStores unless annotated with @CacheLoaderMetadata > ----------------------------------------------------------------------------------------- > > Key: ISPN-2059 > URL: https://issues.jboss.org/browse/ISPN-2059 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.1.6.FINAL > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 5.2.1, 5.3.0.Final > > > If the @CacheLoaderMetadata is missing, Infinispan will treat the CacheLoader as a CacheStore: if it's not implementing CacheStore as well the component will fail. > @CacheLoaderMetadata should be optional. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2789) OutOfMemoryError in case if LuceneCacheLoader.loadAll() is called

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-2789?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-2789: --------------------------------------- [~amanukyan]Fix looks great. Looking forward for the pull request. Only bad news is that this will certainly cause conflicts with pull https://github.com/infinispan/infinispan/pull/1619 > OutOfMemoryError in case if LuceneCacheLoader.loadAll() is called > ----------------------------------------------------------------- > > Key: ISPN-2789 > URL: https://issues.jboss.org/browse/ISPN-2789 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.0.Final > Reporter: Anna Manukyan > Assignee: Anna Manukyan > Fix For: 5.3.0.Alpha1, 5.3.0.Final > > > In case when calling LuceneCacheLoader.loadAll() method, the following exception appears: > {code} > java.lang.OutOfMemoryError: Java heap space > at java.util.HashMap.<init>(HashMap.java:204) > at java.util.HashMap.<init>(HashMap.java:216) > at java.util.HashSet.<init>(HashSet.java:142) > at org.infinispan.lucene.cachestore.DirectoryLoaderAdaptor.loadAllEntries(DirectoryLoaderAdaptor.java:87) > at org.infinispan.lucene.cachestore.LuceneCacheLoader.load(LuceneCacheLoader.java:116) > at org.infinispan.lucene.cachestore.LuceneCacheLoader.loadAll(LuceneCacheLoader.java:105) > at org.infinispan.lucene.cacheloader.LuceneCacheLoaderTest.testLoadEntries(LuceneCacheLoaderTest.java:146) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > {code} > I tried to edit VM options for make it to work, but even in case of high numbers for memory usage, this still happens. -- 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

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2013