March 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7675) Kerberos tests fail on IBM JDK

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7675?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7675: ---------------------------------- Component/s: Test Suite - Server > Kerberos tests fail on IBM JDK > ------------------------------ > > Key: ISPN-7675 > URL: https://issues.jboss.org/browse/ISPN-7675 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.0.0.CR4 > Environment: IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled) > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final > > > The Kerberos tests refer to com.sun.security.auth.module.Krb5LoginModule. > On IBM JDK this should be com.ibm.security.auth.module.Krb5LoginModule -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7675) Kerberos tests fail on IBM JDK

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-7675: ------------------------------------- Summary: Kerberos tests fail on IBM JDK Key: ISPN-7675 URL: https://issues.jboss.org/browse/ISPN-7675 Project: Infinispan Issue Type: Bug Affects Versions: 9.0.0.CR4 Environment: IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled) Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.0.0.Final The Kerberos tests refer to com.sun.security.auth.module.Krb5LoginModule. On IBM JDK this should be com.ibm.security.auth.module.Krb5LoginModule -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 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 Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1822?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-1822. --------------------------------- Resolution: Out of Date > 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 > > 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 was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3856) Test ConcurrentLoadAndEvictTxTest.testEvictAndTx fails on IBM jDK6

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3856?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-3856. --------------------------------- Resolution: Out of Date > Test ConcurrentLoadAndEvictTxTest.testEvictAndTx fails on IBM jDK6 > ------------------------------------------------------------------ > > Key: ISPN-3856 > URL: https://issues.jboss.org/browse/ISPN-3856 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.1.Final > Environment: {RHELx86,RHELx64}xIBM6 > Reporter: Vitalii Chepeliuk > Labels: testsuite_stability > > NPE is thrown > Look at following jenkins runs > 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... > 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... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2623) SimpleEvictionMaxEntries fails consistently on IBM JDK with "cache size too big: 182"

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2623?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-2623. --------------------------------- Resolution: Out of Date > SimpleEvictionMaxEntries fails consistently on IBM JDK with "cache size too big: 182" > ------------------------------------------------------------------------------------- > > Key: ISPN-2623 > URL: https://issues.jboss.org/browse/ISPN-2623 > Project: Infinispan > Issue Type: Bug > Components: Eviction, Test Suite - Core > Affects Versions: 5.1.8.Final > Environment: IBM JDK6, IBM JDK7, any platfrom > Reporter: Jitka Kozana > Labels: testsuite_stability > > Test SimpleEvictionMaxEntries fails consistently across platforms with the following (output from RHEL6_x86_64): > {code} > 2012-12-05 10:53:13,616 ERROR [UnitTestTestNGListener] (testng-LRUEvictionFunctionalTest) Method testSimpleEvictionMaxEntries(org.infinispan.eviction.LRUEvictionFunctionalTest) threw an exception > java.lang.AssertionError: cache size too big: 182 > at org.infinispan.eviction.BaseEvictionFunctionalTest.testSimpleEvictionMaxEntries(BaseEvictionFunctionalTest.java:67) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:613) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:673) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1170) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1147) > at org.testng.TestRunner.privateRun(TestRunner.java:749) > at org.testng.TestRunner.run(TestRunner.java:600) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:317) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:34) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:351) > at org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:147) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614) > at java.lang.Thread.run(Thread.java:780) > [testng-LRUEvictionFunctionalTest] Test testSimpleEvictionMaxEntries(org.infinispan.eviction.LRUEvictionFunctionalTest) failed. > {code} > Seen during TS runs for test cycle EAP 6.0.1.ER4.2. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7674) BackupFailureException doesn't have a detail message

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7674?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7674: ------------------------------- Status: Open (was: New) > BackupFailureException doesn't have a detail message > ---------------------------------------------------- > > Key: ISPN-7674 > URL: https://issues.jboss.org/browse/ISPN-7674 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.0.0.Final > > > {{BackupFailureException}} overrides {{toString()}} to include a list of failures. However, log4j2 logs the result of {{getMessage()}} instead of {{toString()}}, so the list of failures is not included in the log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7674) BackupFailureException doesn't have a detail message

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7674?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7674: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5024 > BackupFailureException doesn't have a detail message > ---------------------------------------------------- > > Key: ISPN-7674 > URL: https://issues.jboss.org/browse/ISPN-7674 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.CR3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.0.0.Final > > > {{BackupFailureException}} overrides {{toString()}} to include a list of failures. However, log4j2 logs the result of {{getMessage()}} instead of {{toString()}}, so the list of failures is not included in the log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7586) Rolling Upgrade: use of Remote Store in mode read-only causes data inconsistencies

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-7586?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-7586: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1435620 Bugzilla Update: Perform > Rolling Upgrade: use of Remote Store in mode read-only causes data inconsistencies > ---------------------------------------------------------------------------------- > > Key: ISPN-7586 > URL: https://issues.jboss.org/browse/ISPN-7586 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.0.0.CR4 > > > We recommend to do rolling upgrades with the target cluster with a remote-store pointing to the source cluster, in mode ready-only. Clients are switched to point to the target cluster. > This cause situations like this in the client: > {code:java} > client.put("K","value") > // will get "V" back > client.get("K") > // Deletes will not propagate to the source cluster, > // the RemoteStore is in 'read-only' mode. > client.remove("K") > // Returns "V". Although deleted, value will be retrieved > // from the remote store > cache.get("K") > > {code} > This can break existing applications that expect a consistent access to data during a Rolling Upgrade process. Clearly the remote store should not be in read only mode, but at the same time, as the Rolling Upgrade does a put in the target cache reading data from the source cache, it should not trigger a write back to the source cluster. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7674) BackupFailureException doesn't have a detail message

by Dan Berindei (JIRA)

Dan Berindei created ISPN-7674: ---------------------------------- Summary: BackupFailureException doesn't have a detail message Key: ISPN-7674 URL: https://issues.jboss.org/browse/ISPN-7674 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.0.0.CR3 Reporter: Dan Berindei Assignee: Dan Berindei Priority: Minor Fix For: 9.0.0.Final {{BackupFailureException}} overrides {{toString()}} to include a list of failures. However, log4j2 logs the result of {{getMessage()}} instead of {{toString()}}, so the list of failures is not included in the log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7667) Use ArrayDeque for transaction context iterator

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7667?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7667. -------------------------------- Resolution: Done > Use ArrayDeque for transaction context iterator > ----------------------------------------------- > > Key: ISPN-7667 > URL: https://issues.jboss.org/browse/ISPN-7667 > Project: Infinispan > Issue Type: Bug > Reporter: William Burns > Assignee: William Burns > Fix For: 9.0.0.Final > > > Transaction iterator stores entries from the context into a List. It then removes the first element from that as it processes those entries. This should use an ArrayDeque to have constant time removals (where as ArrayList needs to move entries to compensate removing from the front). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2017