July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3327) Server init.d script should be customized for Infinispan

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3327: ------------------------------------- Summary: Server init.d script should be customized for Infinispan Key: ISPN-3327 URL: https://issues.jboss.org/browse/ISPN-3327 Project: Infinispan Issue Type: Bug Reporter: Tristan Tarrant Assignee: Mircea Markus The current init.d script included in Infinispan Server should be appropriately renamed and verified -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3326) LevelDB cachestore should use cachename to construct path

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3326?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3326: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1972 > LevelDB cachestore should use cachename to construct path > --------------------------------------------------------- > > Key: ISPN-3326 > URL: https://issues.jboss.org/browse/ISPN-3326 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.3.0.Final, 6.0.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha2 > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3326) LevelDB cachestore should use cachename to construct path

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-3326: ------------------------------------- Summary: LevelDB cachestore should use cachename to construct path Key: ISPN-3326 URL: https://issues.jboss.org/browse/ISPN-3326 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 6.0.0.Alpha1, 5.3.0.Final Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 6.0.0.Alpha2 -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3325) ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill random failures

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3325?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3325: -------------------------------- Assignee: Dan Berindei (was: Mircea Markus) > ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill random failures > --------------------------------------------------------------------------------------- > > Key: ISPN-3325 > URL: https://issues.jboss.org/browse/ISPN-3325 > Project: Infinispan > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 5.3.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 6.0.0.Final > > > The test adds a 5th server, but {{ConsistentHashV1IntegrationTest.getHitServer()}} assumes that the requests hit one of the original 4 servers. Because the server CH to client CH is imperfect in protocol versions 1.1 and 1.2, some of the requests may instead hit server 5, causing a {{NullPointerException}}: > {noformat} > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.RangeCheck(ArrayList.java:547) > at java.util.ArrayList.get(ArrayList.java:322) > at org.infinispan.client.hotrod.ConsistentHashV1IntegrationTest.getHitServer(ConsistentHashV1IntegrationTest.java:204) > at org.infinispan.client.hotrod.ConsistentHashV1IntegrationTest.runTest(ConsistentHashV1IntegrationTest.java:129) > at org.infinispan.client.hotrod.ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill(ConsistentHashV1IntegrationTest.java:160) > {noformat} -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3325) ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill random failures

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3325?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3325: -------------------------------- Fix Version/s: 6.0.0.Alpha2 > ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill random failures > --------------------------------------------------------------------------------------- > > Key: ISPN-3325 > URL: https://issues.jboss.org/browse/ISPN-3325 > Project: Infinispan > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 5.3.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > The test adds a 5th server, but {{ConsistentHashV1IntegrationTest.getHitServer()}} assumes that the requests hit one of the original 4 servers. Because the server CH to client CH is imperfect in protocol versions 1.1 and 1.2, some of the requests may instead hit server 5, causing a {{NullPointerException}}: > {noformat} > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList.RangeCheck(ArrayList.java:547) > at java.util.ArrayList.get(ArrayList.java:322) > at org.infinispan.client.hotrod.ConsistentHashV1IntegrationTest.getHitServer(ConsistentHashV1IntegrationTest.java:204) > at org.infinispan.client.hotrod.ConsistentHashV1IntegrationTest.runTest(ConsistentHashV1IntegrationTest.java:129) > at org.infinispan.client.hotrod.ConsistentHashV1IntegrationTest.testCorrectBalancingOfKeysAfterNodeKill(ConsistentHashV1IntegrationTest.java:160) > {noformat} -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1741) Remove old and deprecated pre-5.0 Configuration objects

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-1741?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-1741: -------------------------------- Fix Version/s: 6.0.0.Alpha2 (was: 6.0.0.Alpha1) > Remove old and deprecated pre-5.0 Configuration objects > ------------------------------------------------------- > > Key: ISPN-1741 > URL: https://issues.jboss.org/browse/ISPN-1741 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 5.2.0.Final > Reporter: Manik Surtani > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > Remove the deprecated Configuration object altogether from the code base, and update all public APIs and SPIs accordingly. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1822) Cache entry not evicted from memory on IBM JDK when another entry was loaded from a cache loader and maxEntries had been reached

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-1822?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-1822: -------------------------------- Fix Version/s: 6.0.0.Alpha2 (was: 6.0.0.Alpha1) > Cache entry not evicted from memory on IBM JDK when another entry was loaded from a cache loader and maxEntries had been reached > -------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-1822 > URL: https://issues.jboss.org/browse/ISPN-1822 > Project: Infinispan > Issue Type: Bug > Components: Eviction > Affects Versions: 5.1.0.FINAL > Environment: java version "1.6.0" > Java(TM) SE Runtime Environment (build pxi3260sr9fp1-20110208_03(SR9 FP1)) > IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr9-20110203_74623 (JIT enabled, AOT enabled) ; > java version "1.7.0" > Java(TM) SE Runtime Environment (build pxi3270-20110827_01) > IBM J9 VM (build 2.6, JRE 1.7.0 Linux x86-32 20110810_88604 (JIT enabled, AOT enabled) > Reporter: Martin Gencur > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha2 > > > This behavior is specific to IBM JDK (I tried JDK6 and 7), it works fine with Java HotSpot. > Steps to reproduce the problem: > 1) set maxEntries for eviction to 2 and algorithm e.g. to LRU > 2) store 3 entries key1, key2, key3 to the cache (after that you can see that the cache contains only 2 entries - key2 and key3, the first one was evicted from memory) > 3) call cache.get("key1") > 4) PROBLEM - cache contains all key1, key2, key3 even though it should contain only 2 entries - only happens with IBM JDK (6 or 7 ..no matter) > I'll shortly issue a pull request with a test to ispn-core -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2522) The org.infinispan.statetransfer.StateTransferCacheLoaderFunctionalTest (StateTransferFunctionTest) tests fail periodically

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2522?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2522: -------------------------------- Fix Version/s: 6.0.0.Alpha2 (was: 6.0.0.Alpha1) > The org.infinispan.statetransfer.StateTransferCacheLoaderFunctionalTest (StateTransferFunctionTest) tests fail periodically > --------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2522 > URL: https://issues.jboss.org/browse/ISPN-2522 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Anna Manukyan > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 6.0.0.Alpha2 > > > The following tests of org.infinispan.statetransfer.StateTransferCacheLoaderFunctionalTest class are failing periodically during JDG 6.1.0.ER3 build testing: > org.infinispan.statetransfer.StateTransferCacheLoaderFunctionalTest.testSTWithWritingNonTxThread > org.infinispan.statetransfer.StateTransferCacheLoaderFunctionalTest.testSTWithWritingTxThread > You can find the failure logs here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... > The same issue happens to org.infinispan.statetranser.StateTransferFunctionTest tests(the parent test class). > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-ispn-testsuite... -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2475) When L1.onRehash is enabled, L1 invalidations should be sent to the previous owners

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2475?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2475: -------------------------------- Fix Version/s: 6.0.0.Alpha2 (was: 6.0.0.Alpha1) > When L1.onRehash is enabled, L1 invalidations should be sent to the previous owners > ----------------------------------------------------------------------------------- > > Key: ISPN-2475 > URL: https://issues.jboss.org/browse/ISPN-2475 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.1.0.FINAL > Reporter: Dan Berindei > Assignee: William Burns > Fix For: 6.0.0.Alpha2 > > > Copied from the parent: > {quote} > [...] we can keep track of the consistent hashes in the last 10 minutes (or whatever the L1 lifespan is) and the time of the last invalidation sent for each key. When we need to send a new invalidation, we add the owners in all the consistent hashes since the last invalidation to the invalidation command recipients. > {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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2264) DistL1WriteSkewTest.testSharedCounter failing randomly

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2264?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2264: -------------------------------- Fix Version/s: 6.0.0.Alpha2 (was: 6.0.0.Alpha1) > DistL1WriteSkewTest.testSharedCounter failing randomly > ------------------------------------------------------ > > Key: ISPN-2264 > URL: https://issues.jboss.org/browse/ISPN-2264 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Labels: testsuite_stability > Fix For: 6.0.0.Alpha2 > > > {code}Failed tests: > testSharedCounter(org.infinispan.container.versioning.DistL1WriteSkewTest): > Timed out waiting for updater threads{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

12 years, 8 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 July 2013