June 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10346) InitialClusterSizeTest thread leak

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10346?page=com.atlassian.jira.plugin... ] Dan Berindei commented on ISPN-10346: ------------------------------------- The same {{NamedExecutorsFactory}} stop problem happened in {{JBossMarshallerTest.testForeignExternalizerIdNegative}}, leaking a thread {{expiration-thread-JBossMarshallerTest-NodeC-...}}. > InitialClusterSizeTest thread leak > ---------------------------------- > > Key: ISPN-10346 > URL: https://issues.jboss.org/browse/ISPN-10346 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 10.0.0.Beta3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4 > > > I got a thread leak when running the test suite with trace logging enabled and {{taskset -c 1-2}}: > {noformat} > 17:06:05,307 DEBUG (testng-Test:[]) [TestSuiteProgress] Test configuration finished: org.infinispan.remoting.transport.InitialClusterSizeTest.testClassFinished > 17:15:17,284 ERROR [TestSuiteProgress] Test failed: InitialClusterSizeTest.ThreadLeakChecker > java.lang.RuntimeException: Leaked thread Controller-remote-thread-InitialClusterSizeTest-NodeB > at jdk.internal.misc.Unsafe.park(Native Method) ~[?:?] > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:194) ~[?:?] > at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:885) ~[?:?] > at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1039) ~[?:?] > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1345) ~[?:?] > at java.util.concurrent.Semaphore.acquire(Semaphore.java:318) ~[?:?] > at org.infinispan.util.concurrent.BlockingTaskAwareExecutorServiceImpl$ControllerThread.run(BlockingTaskAwareExecutorServiceImpl.java:159) ~[classes/:?] > {noformat} > I believe it may be caused by {{doExecute()}} adding a task to the blocked tasks queue without calling {{checkForReadyTasks()}} (after the executor rejected the task). {{ControllerThread.run()}} needs a semaphore permit to start polling for tasks, so it needs a {{semaphore.release()}} after each {{blockedTasks.add(). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10346) InitialClusterSizeTest thread leak

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10346?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10346: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > InitialClusterSizeTest thread leak > ---------------------------------- > > Key: ISPN-10346 > URL: https://issues.jboss.org/browse/ISPN-10346 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 10.0.0.Beta3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4 > > > I got a thread leak when running the test suite with trace logging enabled and {{taskset -c 1-2}}: > {noformat} > 17:06:05,307 DEBUG (testng-Test:[]) [TestSuiteProgress] Test configuration finished: org.infinispan.remoting.transport.InitialClusterSizeTest.testClassFinished > 17:15:17,284 ERROR [TestSuiteProgress] Test failed: InitialClusterSizeTest.ThreadLeakChecker > java.lang.RuntimeException: Leaked thread Controller-remote-thread-InitialClusterSizeTest-NodeB > at jdk.internal.misc.Unsafe.park(Native Method) ~[?:?] > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:194) ~[?:?] > at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:885) ~[?:?] > at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1039) ~[?:?] > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1345) ~[?:?] > at java.util.concurrent.Semaphore.acquire(Semaphore.java:318) ~[?:?] > at org.infinispan.util.concurrent.BlockingTaskAwareExecutorServiceImpl$ControllerThread.run(BlockingTaskAwareExecutorServiceImpl.java:159) ~[classes/:?] > {noformat} > I believe it may be caused by {{doExecute()}} adding a task to the blocked tasks queue without calling {{checkForReadyTasks()}} (after the executor rejected the task). {{ControllerThread.run()}} needs a semaphore permit to start polling for tasks, so it needs a {{semaphore.release()}} after each {{blockedTasks.add(). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10349) PersistenceManager.addSegments may never complete

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10349?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10349: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7092 > PersistenceManager.addSegments may never complete > ------------------------------------------------- > > Key: ISPN-10349 > URL: https://issues.jboss.org/browse/ISPN-10349 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Beta3 > Reporter: Dan Berindei > Assignee: Will Burns > Priority: Major > Labels: testsuite_stability > Fix For: 10.0.0.Beta4 > > > {{PersistenceManager.addSegments}} returns a {{CompletionStage}} which should be completed on a persistence executor thread. If the persistence executor was already stopped at the time {{addSegments()}} was called, however, the {{CompletionStage}} is never completed. > This doesn't prevent the cache manager from stopping, but it causes a thread leak because a transport thread waits forever on the {{CompletionStage}}. E.g. > {noformat} > 16:57:06,128 TRACE (testng-Test:[]) [BasicComponentRegistryImpl] Changed status of org.infinispan.executors.persistence to STOPPED > 16:57:06,150 TRACE (transport-thread-Test-NodeB-p2059-t4:[Topology-testCache]) [PersistenceManagerImpl] Adding segments for id 584 > # no other mention of id 584 > 17:15:17,300 ERROR [TestSuiteProgress] Test failed: SharedStoreInvalidationDuringRehashTest.ThreadLeakChecker > java.lang.RuntimeException: Leaked thread transport-thread-SharedStoreInvalidationDuringRehashTest-NodeB-p2059-t4 > at jdk.internal.misc.Unsafe.park(Native Method) ~[?:?] > at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234) ~[?:?] > at java.util.concurrent.CompletableFuture$Signaller.block(CompletableFuture.java:1798) ~[?:?] > at java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3128) ~[?:?] > at java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1868) ~[?:?] > at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2021) ~[?:?] > at org.infinispan.util.concurrent.CompletableFutures.await(CompletableFutures.java:110) ~[classes/:?] > at org.infinispan.util.concurrent.CompletionStages.join(CompletionStages.java:73) ~[classes/:?] > at org.infinispan.statetransfer.StateConsumerImpl.onTopologyUpdate(StateConsumerImpl.java:306) ~[classes/:?] > at org.infinispan.scattered.impl.ScatteredStateConsumerImpl.onTopologyUpdate(ScatteredStateConsumerImpl.java:102) ~[classes/:?] > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9893) New Reactive API

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9893?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9893: ------------------------------- Sprint: DataGrid Sprint #29, DataGrid Sprint #30 (was: DataGrid Sprint #29) > New Reactive API > ---------------- > > Key: ISPN-9893 > URL: https://issues.jboss.org/browse/ISPN-9893 > Project: Infinispan > Issue Type: Enhancement > Components: API > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > See sub-talks. This is an umbrella issue -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10355) Run Infinispan Server on Quarkus

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10355?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10355: ------------------------------ Sprint: DataGrid Sprint #30 > Run Infinispan Server on Quarkus > -------------------------------- > > Key: ISPN-10355 > URL: https://issues.jboss.org/browse/ISPN-10355 > Project: Infinispan > Issue Type: Feature Request > Reporter: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > We need to allow the Infinispan Server to run on Quarkus. See nested issues for more specifics. > It may be required to have this run outside of Quarkus as it doesn't yet support a Command Mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10356) Create Quarkus extension that can run LOCAL cache in Quarkus

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10356?page=com.atlassian.jira.plugin... ] Will Burns reassigned ISPN-10356: --------------------------------- Assignee: Will Burns > Create Quarkus extension that can run LOCAL cache in Quarkus > ------------------------------------------------------------ > > Key: ISPN-10356 > URL: https://issues.jboss.org/browse/ISPN-10356 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > The first step should be just to get a LOCAL cache working as a Quarkus extension. This should allow us to get quite a bit of work done without leaving the Quarkus ecosystem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10356) Create Quarkus extension that can run LOCAL cache in Quarkus

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10356?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10356: ------------------------------ Status: Open (was: New) > Create Quarkus extension that can run LOCAL cache in Quarkus > ------------------------------------------------------------ > > Key: ISPN-10356 > URL: https://issues.jboss.org/browse/ISPN-10356 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > The first step should be just to get a LOCAL cache working as a Quarkus extension. This should allow us to get quite a bit of work done without leaving the Quarkus ecosystem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10358) Run Server mode natively

by Will Burns (Jira)

Will Burns created ISPN-10358: --------------------------------- Summary: Run Server mode natively Key: ISPN-10358 URL: https://issues.jboss.org/browse/ISPN-10358 Project: Infinispan Issue Type: Sub-task Reporter: Will Burns After we have embedded clustering and Infinispan Server NG working we should be able to attempt to run the server in a natively compiled SubstrateVM environment. This may or may not live inside of Quarkus depending on its support when working on this issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10356) Create Quarkus extension that can run LOCAL cache in Quarkus

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10356?page=com.atlassian.jira.plugin... ] Will Burns commented on ISPN-10356: ----------------------------------- This is currently blocked until ISPN-10354 can be completed > Create Quarkus extension that can run LOCAL cache in Quarkus > ------------------------------------------------------------ > > Key: ISPN-10356 > URL: https://issues.jboss.org/browse/ISPN-10356 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > The first step should be just to get a LOCAL cache working as a Quarkus extension. This should allow us to get quite a bit of work done without leaving the Quarkus ecosystem. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10357) Add support for clustered embedded mode to Quarkus

by Will Burns (Jira)

Will Burns created ISPN-10357: --------------------------------- Summary: Add support for clustered embedded mode to Quarkus Key: ISPN-10357 URL: https://issues.jboss.org/browse/ISPN-10357 Project: Infinispan Issue Type: Sub-task Reporter: Will Burns After a local cache is working we need to work on getting JGroups and clustering working as a next step in an embedded mode. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 June 2019