March 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8930) RestOperationsTest#shouldPutImmortalEntryWithZeroTtlAndIdleTime random failure

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8930?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8930: -------------------------------- Status: Open (was: New) > RestOperationsTest#shouldPutImmortalEntryWithZeroTtlAndIdleTime random failure > ------------------------------------------------------------------------------ > > Key: ISPN-8930 > URL: https://issues.jboss.org/browse/ISPN-8930 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 9.2.0.Final > Reporter: William Burns > > This test can fail randomly with a NPE > {code} > java.lang.NullPointerException > at org.infinispan.rest.BaseRestOperationsTest.shouldPutImmortalEntryWithZeroTtlAndIdleTime(BaseRestOperationsTest.java:853) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > ... Removed 16 stack frames > {code} > This is caused by the thread being stalled for > 100 ms after the put but before reading. Thus the expiration is not being overridden properly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8930) RestOperationsTest#shouldPutImmortalEntryWithZeroTtlAndIdleTime random failure

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8930?page=com.atlassian.jira.plugin.... ] Work on ISPN-8930 started by William Burns. ------------------------------------------- > RestOperationsTest#shouldPutImmortalEntryWithZeroTtlAndIdleTime random failure > ------------------------------------------------------------------------------ > > Key: ISPN-8930 > URL: https://issues.jboss.org/browse/ISPN-8930 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 9.2.0.Final > Reporter: William Burns > Assignee: William Burns > > This test can fail randomly with a NPE > {code} > java.lang.NullPointerException > at org.infinispan.rest.BaseRestOperationsTest.shouldPutImmortalEntryWithZeroTtlAndIdleTime(BaseRestOperationsTest.java:853) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > ... Removed 16 stack frames > {code} > This is caused by the thread being stalled for > 100 ms after the put but before reading. Thus the expiration is not being overridden properly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8757) Cancel Scheduled TryLock requests if they are already done

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-8757?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-8757: ------------------------------- Status: Open (was: New) > Cancel Scheduled TryLock requests if they are already done > ---------------------------------------------------------- > > Key: ISPN-8757 > URL: https://issues.jboss.org/browse/ISPN-8757 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > > If the users put a vert high timeout, we will have a potential memory issue on the scheduler. > When a tryLock request is done, it scheduler task should be cleaned up -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8757) Cancel Scheduled TryLock requests if they are already done

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-8757?page=com.atlassian.jira.plugin.... ] Work on ISPN-8757 started by Katia Aresti. ------------------------------------------ > Cancel Scheduled TryLock requests if they are already done > ---------------------------------------------------------- > > Key: ISPN-8757 > URL: https://issues.jboss.org/browse/ISPN-8757 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > > If the users put a vert high timeout, we will have a potential memory issue on the scheduler. > When a tryLock request is done, it scheduler task should be cleaned up -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8706) HotRodMergeTest Timed out waiting for rebalancing to complete

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8706?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8706: ------------------------------- Fix Version/s: 9.2.1.Final > HotRodMergeTest Timed out waiting for rebalancing to complete > ------------------------------------------------------------- > > Key: ISPN-8706 > URL: https://issues.jboss.org/browse/ISPN-8706 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.2.0.Alpha2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.1.Final > > Attachments: HotRodMergeTest_20180129.log.gz > > > The HotRodMergeTest is now consistently failing with the following error: > {code} > [OK: 321, KO: 1, SKIP: 0] Test failed: org.infinispan.server.hotrod.HotRodMergeTest.testNewTopologySentAfterCleanMerge[DIST_SYNC] > java.lang.RuntimeException: Timed out waiting for rebalancing to complete on node HotRodMergeTest[DIST_SYNC]-NodeA-31095, expected member list is [HotRodMergeTest[DIST_SYNC]-NodeA-31095, HotRodMergeTest[DIST_SYNC]-NodeB-33866], current member list is [HotRodMergeTest[DIST_SYNC]-NodeA-31095]! > at org.infinispan.test.TestingUtil.waitForNoRebalance(TestingUtil.java:388) > at org.infinispan.test.TestingUtil.waitForNoRebalance(TestingUtil.java:424) > at org.infinispan.partitionhandling.BasePartitionHandlingTest$Partition.waitForPartitionToForm(BasePartitionHandlingTest.java:282) > at org.infinispan.partitionhandling.BasePartitionHandlingTest$Partition.merge(BasePartitionHandlingTest.java:258) > at org.infinispan.partitionhandling.BasePartitionHandlingTest$Partition.merge(BasePartitionHandlingTest.java:246) > at org.infinispan.server.hotrod.HotRodMergeTest.testNewTopologySentAfterCleanMerge(HotRodMergeTest.java:87) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > 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:348) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:38) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:382) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8899) Extend the existing tests for conflict manager to work on replicated caches

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8899?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8899: ------------------------------- Security: (was: Red Hat Internal) > Extend the existing tests for conflict manager to work on replicated caches > --------------------------------------------------------------------------- > > Key: ISPN-8899 > URL: https://issues.jboss.org/browse/ISPN-8899 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite - Core > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.1.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8885) Multiple primary owners during conflict resolution

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8885?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8885: ------------------------------- Fix Version/s: 9.2.1.Final (was: 9.3.0.Final) > Multiple primary owners during conflict resolution > -------------------------------------------------- > > Key: ISPN-8885 > URL: https://issues.jboss.org/browse/ISPN-8885 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.0.CR3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.2.1.Final > > > During the CONFLICT_RESOLUTION topology phase the pending CH is incorrectly set which results in the TriangleDistributionInterceptor (and other distributor interceptors) on multiple nodes thinking they are the primary owner of a key. Consequently, cache write commands during the CONFLICT_RESOLUTION phase are committed multiple times. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8930) RestOperationsTest#shouldPutImmortalEntryWithZeroTtlAndIdleTime random failure

by William Burns (JIRA)

William Burns created ISPN-8930: ----------------------------------- Summary: RestOperationsTest#shouldPutImmortalEntryWithZeroTtlAndIdleTime random failure Key: ISPN-8930 URL: https://issues.jboss.org/browse/ISPN-8930 Project: Infinispan Issue Type: Bug Components: REST Affects Versions: 9.2.0.Final Reporter: William Burns This test can fail randomly with a NPE {code} java.lang.NullPointerException at org.infinispan.rest.BaseRestOperationsTest.shouldPutImmortalEntryWithZeroTtlAndIdleTime(BaseRestOperationsTest.java:853) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) ... Removed 16 stack frames {code} This is caused by the thread being stalled for > 100 ms after the put but before reading. Thus the expiration is not being overridden properly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8769) Improve log messages on trace

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-8769?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-8769: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5827 > Improve log messages on trace > ----------------------------- > > Key: ISPN-8769 > URL: https://issues.jboss.org/browse/ISPN-8769 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > > trace logs do not include lock name > check if tracing is enabled with trace method -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8929) $local management user cannot manage protobuf schemas

by Alex Furmanski (JIRA)

Alex Furmanski created ISPN-8929: ------------------------------------ Summary: $local management user cannot manage protobuf schemas Key: ISPN-8929 URL: https://issues.jboss.org/browse/ISPN-8929 Project: Infinispan Issue Type: Bug Components: CLI, Security, Server Reporter: Alex Furmanski The $local management user cannot manipulate protostream caches because it lacks the ___schema_manager role. For example: {noformat} [user@myhost jboss-datagrid]$ bin/cli.sh You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. [disconnected /] connect 192.168.50.11 [standalone@192.168.50.11:9990 /] container mycontainer [standalone@192.168.50.11:9990 cache-container=mycontainer] :get-proto-schema-names { "outcome" => "failed", "failure-description" => "DGISPN0118: Failed to invoke operation: ISPN000287: Unauthorized access: subject 'Subject with principal(s): [$local@ManagementRealm, org.jboss.remoting3.security.UserPrincipal@439455c7, InetAddressPrincipal <192.168.50.11/192.168.50.11>, InetAddressPrincipal <192.168.50.11/192.168.50.11>]' lacks 'BULK_READ' permission", "rolled-back" => true } {noformat} This was tested with RH Data Grid 7.1.2. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2018