February 2014 - infinispan-issues

[JBoss JIRA] (ISPN-3969) Can't retrieve values from FineGrainedAtomicMap with "storeAsBinary" option enabled

by Gunnar Morling (JIRA)

[ https://issues.jboss.org/browse/ISPN-3969?page=com.atlassian.jira.plugin.... ] Gunnar Morling updated ISPN-3969: --------------------------------- Attachment: MarshallingTest.java Attaching complete test case > Can't retrieve values from FineGrainedAtomicMap with "storeAsBinary" option enabled > ----------------------------------------------------------------------------------- > > Key: ISPN-3969 > URL: https://issues.jboss.org/browse/ISPN-3969 > Project: Infinispan > Issue Type: Bug > Reporter: Gunnar Morling > Assignee: Mircea Markus > Attachments: MarshallingTest.java > > > When using the "storeAsBinary" option to enforce eager serialization, a value added to a {{FineGrainedAtomicMap}} via {{put()}} can't be read back via {{get()}}: > {code} > EmbeddedCacheManager manager = ...; > manager.getCache( "testCache", true ); > > CacheKey cacheKey = new CacheKey( "Some Key" ); > Object key = "the key"; > Object value = "the value"; > FineGrainedAtomicMap<Object, Object> map = AtomicMapLookup.getFineGrainedAtomicMap( cache, cacheKey, true ); > map.put( key, value ); > //fails > assertNotNull( map.get( key ) ); > {code} -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3969) Can't retrieve values from FineGrainedAtomicMap with "storeAsBinary" option enabled

by Gunnar Morling (JIRA)

[ https://issues.jboss.org/browse/ISPN-3969?page=com.atlassian.jira.plugin.... ] Gunnar Morling updated ISPN-3969: --------------------------------- Comment: was deleted (was: Attaching complete test case) > Can't retrieve values from FineGrainedAtomicMap with "storeAsBinary" option enabled > ----------------------------------------------------------------------------------- > > Key: ISPN-3969 > URL: https://issues.jboss.org/browse/ISPN-3969 > Project: Infinispan > Issue Type: Bug > Reporter: Gunnar Morling > Assignee: Mircea Markus > Attachments: MarshallingTest.java > > > When using the "storeAsBinary" option to enforce eager serialization, a value added to a {{FineGrainedAtomicMap}} via {{put()}} can't be read back via {{get()}}: > {code} > EmbeddedCacheManager manager = ...; > manager.getCache( "testCache", true ); > > CacheKey cacheKey = new CacheKey( "Some Key" ); > Object key = "the key"; > Object value = "the value"; > FineGrainedAtomicMap<Object, Object> map = AtomicMapLookup.getFineGrainedAtomicMap( cache, cacheKey, true ); > map.put( key, value ); > //fails > assertNotNull( map.get( key ) ); > {code} -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3969) Can't retrieve values from FineGrainedAtomicMap with "storeAsBinary" option enabled

by Gunnar Morling (JIRA)

[ https://issues.jboss.org/browse/ISPN-3969?page=com.atlassian.jira.plugin.... ] Gunnar Morling updated ISPN-3969: --------------------------------- Description: When using the "storeAsBinary" option to enforce eager serialization, a value added to a {{FineGrainedAtomicMap}} via {{put()}} can't be read back via {{get()}}: {code} EmbeddedCacheManager manager = ...; manager.getCache( "testCache", true ); CacheKey cacheKey = new CacheKey( "Some Key" ); Object key = "the key"; Object value = "the value"; FineGrainedAtomicMap<Object, Object> map = AtomicMapLookup.getFineGrainedAtomicMap( cache, cacheKey, true ); map.put( key, value ); //fails assertNotNull( map.get( key ) ); {code} See the attached file for a complete test case. was: When using the "storeAsBinary" option to enforce eager serialization, a value added to a {{FineGrainedAtomicMap}} via {{put()}} can't be read back via {{get()}}: {code} EmbeddedCacheManager manager = ...; manager.getCache( "testCache", true ); CacheKey cacheKey = new CacheKey( "Some Key" ); Object key = "the key"; Object value = "the value"; FineGrainedAtomicMap<Object, Object> map = AtomicMapLookup.getFineGrainedAtomicMap( cache, cacheKey, true ); map.put( key, value ); //fails assertNotNull( map.get( key ) ); {code} > Can't retrieve values from FineGrainedAtomicMap with "storeAsBinary" option enabled > ----------------------------------------------------------------------------------- > > Key: ISPN-3969 > URL: https://issues.jboss.org/browse/ISPN-3969 > Project: Infinispan > Issue Type: Bug > Reporter: Gunnar Morling > Assignee: Mircea Markus > Attachments: MarshallingTest.java > > > When using the "storeAsBinary" option to enforce eager serialization, a value added to a {{FineGrainedAtomicMap}} via {{put()}} can't be read back via {{get()}}: > {code} > EmbeddedCacheManager manager = ...; > manager.getCache( "testCache", true ); > > CacheKey cacheKey = new CacheKey( "Some Key" ); > Object key = "the key"; > Object value = "the value"; > FineGrainedAtomicMap<Object, Object> map = AtomicMapLookup.getFineGrainedAtomicMap( cache, cacheKey, true ); > map.put( key, value ); > //fails > assertNotNull( map.get( key ) ); > {code} > See the attached file for a complete test case. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3969) Can't retrieve values from FineGrainedAtomicMap with "storeAsBinary" option enabled

by Gunnar Morling (JIRA)

Gunnar Morling created ISPN-3969: ------------------------------------ Summary: Can't retrieve values from FineGrainedAtomicMap with "storeAsBinary" option enabled Key: ISPN-3969 URL: https://issues.jboss.org/browse/ISPN-3969 Project: Infinispan Issue Type: Bug Reporter: Gunnar Morling Assignee: Mircea Markus When using the "storeAsBinary" option to enforce eager serialization, a value added to a {{FineGrainedAtomicMap}} via {{put()}} can't be read back via {{get()}}: {code} EmbeddedCacheManager manager = ...; manager.getCache( "testCache", true ); CacheKey cacheKey = new CacheKey( "Some Key" ); Object key = "the key"; Object value = "the value"; FineGrainedAtomicMap<Object, Object> map = AtomicMapLookup.getFineGrainedAtomicMap( cache, cacheKey, true ); map.put( key, value ); //fails assertNotNull( map.get( key ) ); {code} -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3367) ClusterTopologyManagerTest.testClusterRecoveryWithRebalance fails randomly

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-3367?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-3367: --------------------------------------- Remember to re-enable the test when this is merged. > ClusterTopologyManagerTest.testClusterRecoveryWithRebalance fails randomly > -------------------------------------------------------------------------- > > Key: ISPN-3367 > URL: https://issues.jboss.org/browse/ISPN-3367 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Alpha1 > Environment: {w2k8r2 OracleJDK1.7}, { RHEL6_x86_64, OracleJDK1.7 and OpenJDK1.7}, {solaris10_x86_64 and solaris10-sparc_x86_64, OracleJDK1.7} > Reporter: Vitalii Chepeliuk > Assignee: Dan Berindei > Labels: testsuite_stability > Attachments: ClusterTopologyManagerTest.log.zip > > > Error Message > Thread already timed out waiting for event merge > Stacktrace > java.lang.IllegalStateException: Thread already timed out waiting for event merge > at org.infinispan.test.fwk.CheckPoint.trigger(CheckPoint.java:131) > at org.infinispan.test.fwk.CheckPoint.triggerForever(CheckPoint.java:120) > at org.infinispan.statetransfer.ClusterTopologyManagerTest.testClusterRecoveryWithRebalance(ClusterTopologyManagerTest.java:280) > 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:606) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > 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:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > Add links to jenkins jobs > windows, OracleJDK1.7>>> > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > Linux, OracleJDK1.7>>> > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > Linux, OpenJDK1.7>>> > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3968) Intermittent test failure: CacheLoaderFunctionalTest.testPurgeOnStartup

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-3968: ------------------------------------- Summary: Intermittent test failure: CacheLoaderFunctionalTest.testPurgeOnStartup Key: ISPN-3968 URL: https://issues.jboss.org/browse/ISPN-3968 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Reporter: Sanne Grinovero Assignee: Dan Berindei -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3684) Improve L1 consitency with backup owners

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3684?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-3684: -------------------------------- Description: ISPN-3648 fixed an issue that can occur when a backup owner replies with an outdated value. More details on the original issue can be found at ISPN-3426. This JIRA is to improve this fix to be something more desirable. There are a few ways that this could be done. # Change it so that remote gets only go to the primary owner, which guarantees consistency with that owner (this still has issues with fail over when that primary owner goes down). Also may have performance issues since we don't have backup owners to respond faster. # Change it so that values are only added to L1 if the value was retrieved from the primary owner. (note there is still some stuff to think about for fail over here) # Multicast the invalidation message from the primary owner after updating the value. This is the simplest approach (no requestors map required), but may also have some performance concerns. was: ISPN-3648 fixed an issue that can occur when a backup owner replies with an outdated value. More details on the original issue can be found at ISPN-3426. This JIRA is to improve this fix to be something more desirable. There are a few ways that this could be done. # Change it so that remote gets only go to the primary owner, which guarantees consistency with that owner (this still has issues with fail over when that primary owner goes down) # Change it so that values are only added to L1 if the value was retrieved from the primary owner. (note there is still some stuff to think about for fail over here) # Multicast the invalidation message from the primary owner after updating the value. This is the simplest approach (no requestors map required), but may also have some performance concerns. > Improve L1 consitency with backup owners > ---------------------------------------- > > Key: ISPN-3684 > URL: https://issues.jboss.org/browse/ISPN-3684 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 6.0.0.CR1 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Final > > > ISPN-3648 fixed an issue that can occur when a backup owner replies with an outdated value. > More details on the original issue can be found at ISPN-3426. > This JIRA is to improve this fix to be something more desirable. > There are a few ways that this could be done. > # Change it so that remote gets only go to the primary owner, which guarantees consistency with that owner (this still has issues with fail over when that primary owner goes down). Also may have performance issues since we don't have backup owners to respond faster. > # Change it so that values are only added to L1 if the value was retrieved from the primary owner. (note there is still some stuff to think about for fail over here) > # Multicast the invalidation message from the primary owner after updating the value. This is the simplest approach (no requestors map required), but may also have some performance concerns. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3948) Missing logic to add the store to the configuration for custom stores

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3948?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-3948: ---------------------------------------- For master, I'm adding this as part of the new parser work: ISPN-3514 > Missing logic to add the store to the configuration for custom stores > --------------------------------------------------------------------- > > Key: ISPN-3948 > URL: https://issues.jboss.org/browse/ISPN-3948 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Loaders and Stores > Affects Versions: 6.0.0.Final > Reporter: Kurt Lehrke > Assignee: Dan Berindei > Priority: Critical > > Looking at the Parser60 class, if you specify a custom store that isn't a singleFileStore or a clusterLoader, the store doesn't get added to the configuration. I found this when I specified my own CacheLoader and it wasn't instantiated like expected. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3964) Move unstable tests to different group

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3964?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3964: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2373 > Move unstable tests to different group > -------------------------------------- > > Key: ISPN-3964 > URL: https://issues.jboss.org/browse/ISPN-3964 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite - Core, Test Suite - Query, Test Suite - Server > Affects Versions: 6.0.1.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Labels: testsuite_stability > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > The idea is to move the unstable test to a different test group. This new group will be disabled by default and it would run once a day by CI. -- 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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3967) Create a feature file for HotRod client for easy installation in Karaf

by Martin Gencur (JIRA)

Martin Gencur created ISPN-3967: ----------------------------------- Summary: Create a feature file for HotRod client for easy installation in Karaf Key: ISPN-3967 URL: https://issues.jboss.org/browse/ISPN-3967 Project: Infinispan Issue Type: Feature Request Reporter: Martin Gencur Assignee: Martin Gencur A "feature" file is a descriptor of bundles required by a feature. (More info at http://icodebythesea.blogspot.cz/2012/03/making-osgi-deployments-easier-w...) We should provide such a file for easy deployment on Karaf. Otherwise users will have to install all artifacts one by one (jboss-loggin, jgroups, infinispan-commons, infinispan-core, commons-pool, jboss-marshalling-osgi, ...) -- 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

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2014