November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10937) CleanupAfterMethod tests take a very long time

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10937?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10937: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > CleanupAfterMethod tests take a very long time > ---------------------------------------------- > > Key: ISPN-10937 > URL: https://issues.jboss.org/browse/ISPN-10937 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 10.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.0.Beta1 > > > Because of JGRP-2398, every time the cluster is stopped and re-created the new coordinator first tries to connect to the old coordinator: > {noformat} > 13:53:39,024 DEBUG (testng-Test:[]) [GMS] address=Test-NodeA-57106, cluster=org.infinispan.partitionhandling.Test, physical address=127.0.0.1:55320 > 13:53:39,026 TRACE (testng-Test:[]) [GMS] Test-NodeA-57106: discovery took 0 ms, members: 17 rsps (4 coords) [done] > 13:53:39,026 DEBUG (testng-Test:[]) [GMS] Test-NodeA-57106: found multiple coords: [054b27e3-9308-65bf-de26-d6cdd4f6bdd3, 6d7f9fb2-f56b-1b88-7f9d-cdee430ac8ca, Test-NodeA-37104, Test-NodeA-8303] > 13:53:39,026 DEBUG (testng-Test:[]) [GMS] Test-NodeA-57106: sending JOIN(Test-NodeA-57106) to 6d7f9fb2-f56b-1b88-7f9d-cdee430ac8ca > 13:53:41,026 WARN (testng-Test:[]) [GMS] Test-NodeA-57106: JOIN(Test-NodeA-57106) sent to 6d7f9fb2-f56b-1b88-7f9d-cdee430ac8ca timed out (after 2000 ms), on try 0 > ... > 13:53:45,027 DEBUG (testng-Test:[]) [GMS] Test-NodeA-57106: sending JOIN(Test-NodeA-57106) to Test-NodeA-8303 > 13:53:47,027 WARN (testng-Test:[]) [GMS] Test-NodeA-57106: JOIN(Test-NodeA-57106) sent to Test-NodeA-8303 timed out (after 2000 ms), on try 0 > ... > 13:54:51,036 DEBUG (testng-Test:[]) [GMS] Test-NodeA-57106: found multiple coords: [054b27e3-9308-65bf-de26-d6cdd4f6bdd3, 6d7f9fb2-f56b-1b88-7f9d-cdee430ac8ca, 0eb381de-3e9a-0320-b2d9-5db3cb39bb34, Test-NodeA-8303] > 13:54:51,036 DEBUG (testng-Test:[]) [GMS] Test-NodeA-57106: sending JOIN(Test-NodeA-57106) to 054b27e3-9308-65bf-de26-d6cdd4f6bdd3 > 13:54:53,036 WARN (testng-Test:[]) [GMS] Test-NodeA-57106: JOIN(Test-NodeA-57106) sent to 054b27e3-9308-65bf-de26-d6cdd4f6bdd3 timed out (after 2000 ms), on try 9 > ... > 13:54:57,037 DEBUG (testng-Test:[]) [GMS] Test-NodeA-57106: sending JOIN(Test-NodeA-57106) to Test-NodeA-8303 > 13:54:59,037 WARN (testng-Test:[]) [GMS] Test-NodeA-57106: JOIN(Test-NodeA-57106) sent to Test-NodeA-8303 timed out (after 2000 ms), on try 9 > 13:54:59,037 WARN (testng-Test:[]) [GMS] Test-NodeA-57106: too many JOIN attempts (10): becoming singleton > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10912) HotRod server retries CheckAddressTask indefinitely during shutdown

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10912?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10912: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > HotRod server retries CheckAddressTask indefinitely during shutdown > ------------------------------------------------------------------- > > Key: ISPN-10912 > URL: https://issues.jboss.org/browse/ISPN-10912 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.0.Beta1 > > > Normally retrying to add the local address to the topology cache is a good idea, but {{IllegalLifecycleStateException}} should be handled differently. > {noformat} > 09:09:03,471 DEBUG (remote-thread--p11-t2:[]) [HotRodServer] Error re-adding address to topology cache, retrying > org.infinispan.commons.CacheException: org.infinispan.IllegalLifecycleStateException: Cache container has been stopped and cannot be reused. Recreate the cache container. > at org.infinispan.server.hotrod.HotRodServer$ReAddMyAddressListener.lambda$recursionTopologyChanged$0(HotRodServer.java:678) ~[infinispan-server-hotrod-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.impl.LocalClusterExecutor.lambda$submitConsumer$3(LocalClusterExecutor.java:78) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859) ~[?:?] > at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837) ~[?:?] > at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506) ~[?:?] > at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2088) ~[?:?] > at org.infinispan.manager.impl.LocalClusterExecutor.lambda$localInvocation$6(LocalClusterExecutor.java:97) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.util.concurrent.BlockingTaskAwareExecutorServiceImpl$RunnableWrapper.run(BlockingTaskAwareExecutorServiceImpl.java:215) [infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?] > at java.lang.Thread.run(Thread.java:834) [?:?] > Caused by: org.infinispan.IllegalLifecycleStateException: Cache container has been stopped and cannot be reused. Recreate the cache container. > at org.infinispan.manager.DefaultCacheManager.assertIsNotTerminated(DefaultCacheManager.java:1070) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:502) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:498) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:491) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.impl.AbstractDelegatingEmbeddedCacheManager.getCache(AbstractDelegatingEmbeddedCacheManager.java:196) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.impl.UnwrappingEmbeddedCacheManager.getCache(UnwrappingEmbeddedCacheManager.java:25) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.server.hotrod.CheckAddressTask.apply(HotRodServer.java:725) ~[infinispan-server-hotrod-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.server.hotrod.CheckAddressTask.apply(HotRodServer.java:712) ~[infinispan-server-hotrod-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > at org.infinispan.manager.impl.LocalClusterExecutor.lambda$localInvocation$6(LocalClusterExecutor.java:94) ~[infinispan-core-10.1.0-SNAPSHOT.jar:10.1.0-SNAPSHOT] > ... 4 more > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10940) JPA deleteBatch should not pass empty collection to CriteriaDelete

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10940?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10940: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.1.0.Beta1 10.0.2.Final Resolution: Done > JPA deleteBatch should not pass empty collection to CriteriaDelete > ------------------------------------------------------------------ > > Key: ISPN-10940 > URL: https://issues.jboss.org/browse/ISPN-10940 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.4.16.Final, 10.0.1.Final, 10.1.0.Beta1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.0.Beta1, 10.0.2.Final > > > Passing an empty collection to CriteriaDelete is only supported by some DB implementations, therefore {{JpaStore::deleteBatch}} should return before a {{CriteriaDelete}} instance is created when an empty iterable has been supplied. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10928) Counter SecurityException: ISPN000287: Unauthorized access: subject 'null' lacks 'ADMIN'

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10928?page=com.atlassian.jira.plugin... ] Will Burns commented on ISPN-10928: ----------------------------------- 9.4.x still needs to be integrated, but we can't push just yet. > Counter SecurityException: ISPN000287: Unauthorized access: subject 'null' lacks 'ADMIN' > ----------------------------------------------------------------------------------------- > > Key: ISPN-10928 > URL: https://issues.jboss.org/browse/ISPN-10928 > Project: Infinispan > Issue Type: Bug > Components: Clustered Counter, Security, WildFly Server > Affects Versions: 10.0.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.0.Beta1, 10.0.2.Final > > > {code:java} > 12:26:41,192 ERROR [stderr] (async-thread--p6-t1) Exception in thread "async-thread--p6-t1" java.lang.SecurityException: ISPN000287: Unauthorized access: subject 'null' lacks 'ADMIN' permission > 12:26:41,193 ERROR [stderr] (async-thread--p6-t1) at org.infinispan.core:jdg-7.3@9.4.16.CD20191104-redhat-00001//org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:87) > 12:26:41,193 ERROR [stderr] (async-thread--p6-t1) at org.infinispan.core:jdg-7.3@9.4.16.CD20191104-redhat-00001//org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:57) > 12:26:41,193 ERROR [stderr] (async-thread--p6-t1) at org.infinispan.core:jdg-7.3@9.4.16.CD20191104-redhat-00001//org.infinispan.manager.DefaultCacheManager.getCacheManagerConfiguration(DefaultCacheManager.java:841) > 12:26:41,193 ERROR [stderr] (async-thread--p6-t1) at org.infinispan.counter:jdg-7.3@9.4.16.CD20191104-redhat-00001//org.infinispan.counter.impl.manager.CounterConfigurationManager.threadName(CounterConfigurationManager.java:239) > 12:26:41,194 ERROR [stderr] (async-thread--p6-t1) at org.infinispan.counter:jdg-7.3@9.4.16.CD20191104-redhat-00001//org.infinispan.counter.impl.manager.CounterConfigurationManager.lambda$startCounterCache$5(CounterConfigurationManager.java:229) > 12:26:41,194 ERROR [stderr] (async-thread--p6-t1) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > 12:26:41,194 ERROR [stderr] (async-thread--p6-t1) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > 12:26:41,194 ERROR [stderr] (async-thread--p6-t1) at java.base/java.lang.Thread.run(Thread.java:834) > {code} > Also thrown when accessing event log. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10928) Counter SecurityException: ISPN000287: Unauthorized access: subject 'null' lacks 'ADMIN'

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10928?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10928: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.1.0.Beta1 10.0.2.Final Resolution: Done > Counter SecurityException: ISPN000287: Unauthorized access: subject 'null' lacks 'ADMIN' > ----------------------------------------------------------------------------------------- > > Key: ISPN-10928 > URL: https://issues.jboss.org/browse/ISPN-10928 > Project: Infinispan > Issue Type: Bug > Components: Clustered Counter, Security, WildFly Server > Affects Versions: 10.0.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.0.Beta1, 10.0.2.Final > > > {code:java} > 12:26:41,192 ERROR [stderr] (async-thread--p6-t1) Exception in thread "async-thread--p6-t1" java.lang.SecurityException: ISPN000287: Unauthorized access: subject 'null' lacks 'ADMIN' permission > 12:26:41,193 ERROR [stderr] (async-thread--p6-t1) at org.infinispan.core:jdg-7.3@9.4.16.CD20191104-redhat-00001//org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:87) > 12:26:41,193 ERROR [stderr] (async-thread--p6-t1) at org.infinispan.core:jdg-7.3@9.4.16.CD20191104-redhat-00001//org.infinispan.security.impl.AuthorizationHelper.checkPermission(AuthorizationHelper.java:57) > 12:26:41,193 ERROR [stderr] (async-thread--p6-t1) at org.infinispan.core:jdg-7.3@9.4.16.CD20191104-redhat-00001//org.infinispan.manager.DefaultCacheManager.getCacheManagerConfiguration(DefaultCacheManager.java:841) > 12:26:41,193 ERROR [stderr] (async-thread--p6-t1) at org.infinispan.counter:jdg-7.3@9.4.16.CD20191104-redhat-00001//org.infinispan.counter.impl.manager.CounterConfigurationManager.threadName(CounterConfigurationManager.java:239) > 12:26:41,194 ERROR [stderr] (async-thread--p6-t1) at org.infinispan.counter:jdg-7.3@9.4.16.CD20191104-redhat-00001//org.infinispan.counter.impl.manager.CounterConfigurationManager.lambda$startCounterCache$5(CounterConfigurationManager.java:229) > 12:26:41,194 ERROR [stderr] (async-thread--p6-t1) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > 12:26:41,194 ERROR [stderr] (async-thread--p6-t1) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > 12:26:41,194 ERROR [stderr] (async-thread--p6-t1) at java.base/java.lang.Thread.run(Thread.java:834) > {code} > Also thrown when accessing event log. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10943) Handle thread pool queue rejection when invoking rxjava code

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10943?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10943: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7583 > Handle thread pool queue rejection when invoking rxjava code > ------------------------------------------------------------ > > Key: ISPN-10943 > URL: https://issues.jboss.org/browse/ISPN-10943 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.1.0.Beta1 > > > Currently the BlockingRejectedExecutionHandler throws a Rejected exception at https://github.com/infinispan/infinispan/blob/master/commons/src/main/jav... when a non blocking thread can't pass a task to the blocking queue. > Unfortunately in rxjava 2 they catch the exception and log it and do nothing else at https://github.com/ReactiveX/RxJava/blob/2.x/src/main/java/io/reactivex/i.... This leads to having a publisher that never completes. > We should be able to throw a different exception, not RejectedExecutionException, and rxjava2 should catch and properly set it in the publisher to prevent this from happening. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10943) Handle thread pool queue rejection when invoking rxjava code

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10943?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10943: ------------------------------ Status: Open (was: New) > Handle thread pool queue rejection when invoking rxjava code > ------------------------------------------------------------ > > Key: ISPN-10943 > URL: https://issues.jboss.org/browse/ISPN-10943 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.1.0.Beta1 > > > Currently the BlockingRejectedExecutionHandler throws a Rejected exception at https://github.com/infinispan/infinispan/blob/master/commons/src/main/jav... when a non blocking thread can't pass a task to the blocking queue. > Unfortunately in rxjava 2 they catch the exception and log it and do nothing else at https://github.com/ReactiveX/RxJava/blob/2.x/src/main/java/io/reactivex/i.... This leads to having a publisher that never completes. > We should be able to throw a different exception, not RejectedExecutionException, and rxjava2 should catch and properly set it in the publisher to prevent this from happening. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10943) Handle thread pool queue rejection when invoking rxjava code

by Will Burns (Jira)

Will Burns created ISPN-10943: --------------------------------- Summary: Handle thread pool queue rejection when invoking rxjava code Key: ISPN-10943 URL: https://issues.jboss.org/browse/ISPN-10943 Project: Infinispan Issue Type: Bug Components: Core Reporter: Will Burns Assignee: Will Burns Fix For: 10.1.0.Beta1 Currently the BlockingRejectedExecutionHandler throws a Rejected exception at https://github.com/infinispan/infinispan/blob/master/commons/src/main/jav... when a non blocking thread can't pass a task to the blocking queue. Unfortunately in rxjava 2 they catch the exception and log it and do nothing else at https://github.com/ReactiveX/RxJava/blob/2.x/src/main/java/io/reactivex/i.... This leads to having a publisher that never completes. We should be able to throw a different exception, not RejectedExecutionException, and rxjava2 should catch and properly set it in the publisher to prevent this from happening. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10936) StaticFileResource does not detect correct media types for files

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10936?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10936: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7582 > StaticFileResource does not detect correct media types for files > ---------------------------------------------------------------- > > Key: ISPN-10936 > URL: https://issues.jboss.org/browse/ISPN-10936 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.1.0.Beta1 > > > Currently it uses {{java.nio.Files.probeContentType}} which is broken, as it is environment dependent -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10843) CLI Docs: User Guide, Round 2

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10843?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10843: ------------------------------- Description: Update asciidoc man pages for commands as reference content. Add examples for CLI usage: counters -xsite commands TLS support- will create separate jiras for xsite procedures and adding tls. was: Update asciidoc man pages for commands as reference content. Add examples for CLI usage: counters xsite commands TLS support > CLI Docs: User Guide, Round 2 > ----------------------------- > > Key: ISPN-10843 > URL: https://issues.jboss.org/browse/ISPN-10843 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Update asciidoc man pages for commands as reference content. > Add examples for CLI usage: > counters > -xsite commands > TLS support- > will create separate jiras for xsite procedures and adding tls. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2019