[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)
5 years, 7 months
[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)
5 years, 7 months
[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:
------------------------------
Description:
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.
was:We need to allow the Infinispan Server to run on Quarkus. See nested issues for more specifics.
> 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)
5 years, 7 months