November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10651) jars added to the server/lib folder are not adding classes to classpath

by Alan Field (Jira)

[ https://issues.jboss.org/browse/ISPN-10651?page=com.atlassian.jira.plugin... ] Alan Field updated ISPN-10651: ------------------------------ Priority: Critical (was: Major) > jars added to the server/lib folder are not adding classes to classpath > ----------------------------------------------------------------------- > > Key: ISPN-10651 > URL: https://issues.jboss.org/browse/ISPN-10651 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.0.0.CR2 > Reporter: Gustavo Lira e Silva > Assignee: Tristan Tarrant > Priority: Critical > Attachments: h2-1.4.199.jar, ispn10651.zip > > > {code:java} > GlobalConfigurationBuilder globalConfigurationBuilder = new GlobalConfigurationBuilder().defaultCacheName("default"); > ConfigurationBuilder builder = new ConfigurationBuilder(); > Configuration build = builder.persistence().addStore(JdbcStringBasedStoreConfigurationBuilder.class) > .table() > .dropOnExit(true) > .createOnStart(true) > .tableNamePrefix("ISPN_STRING_TABLE") > .idColumnName("ID_COLUMN").idColumnType("VARCHAR(255)") > .dataColumnName("DATA_COLUMN").dataColumnType("VARBINARY(1000)") > .timestampColumnName("TIMESTAMP_COLUMN").timestampColumnType("BIGINT") > .connectionPool() > .connectionUrl("jdbc:h2:mem:test;DB_CLOSE_DELAY=-1") > .username("sa") > .password("sa") > .driverClass("org.h2.Driver") > .build(); > RemoteCache<String, String> cache = new RemoteCacheManager().administration().getOrCreateCache("test", builder.build()); > cache.put("k1", "v1"); > System.out.println(cache.get("k1")); > {code} > If you place H2 driver inside ISPN_HOME/server/lib start the server and run the code above, you will receive ClassNotFoundException: org.h2.Driver -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10915) CompletionStages.continueOnExecutor() does not complete the future on rejection

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10915?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10915: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > CompletionStages.continueOnExecutor() does not complete the future on rejection > ------------------------------------------------------------------------------- > > Key: ISPN-10915 > URL: https://issues.jboss.org/browse/ISPN-10915 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.16.Final, 10.0.1.Final > Reporter: Dan Berindei > Assignee: Will Burns > Priority: Major > Fix For: 10.1.0.Beta1 > > > {{CompletionStages.continueOnExecutor()}} returns a {{CompletableFuture}} that is supposed to complete after the supplied action has run on the supplied executor. If the executor rejects the action, e.g. because it was stopped, the {{CompletableFuture}} never completes. > E.g. {{JGroupsTransport.receiveClusterView()}} indirectly uses {{CompletionStages.continueOnExecutor()}}, and it blocks view handling forever if a view is received after the async operations executor has been shut down. In turn this blocks all further view processing and the cache manager shutdown. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10903) Handle thread pool queue rejection better

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10903?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10903: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Handle thread pool queue rejection better > ----------------------------------------- > > Key: ISPN-10903 > URL: https://issues.jboss.org/browse/ISPN-10903 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.1.0.Beta1 > > > A few set of tests fail due to not having a queue large enough for the cpu thread pool, which in turn runs the command on the persistence thread pool. We don't want this to happen as this can cause a deadlock. > https://ci.infinispan.org/job/Infinispan/job/master/1567/testReport/junit... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10855) MultipleCacheManagersTest factory issues are ignored

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10855?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10855. --------------------------------- Resolution: Done > MultipleCacheManagersTest factory issues are ignored > ---------------------------------------------------- > > Key: ISPN-10855 > URL: https://issues.jboss.org/browse/ISPN-10855 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.4.16.Final, 10.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.0.Beta1 > > > TestNG doesn't like exceptions being thrown from {{@Factory}} methods, so when {{MultipleCacheManager.defaultFactory()}} finds a problem with the concrete {{factory()}} implementation or with the annotations it replaces the test instance with a {{TestFrameworkFailure}}. > Turns out that doesn't actually work: TestNG ignores the {{TestFrameworkFailure}} instance and runs the tests on a "default instance" of the test class. This is ok when the problem is the concrete class didn't override {{factory()}} and very likely the test author wanted a single test instance, but it's not ok for other errors like {{factory()}} being copy-pasted from super with the wrong class name. > We can make TestNG report our factory failures if we implement {{IInstanceInfo}} and mock all the test/configuration methods to throw our exception. We just need to make all configuration methods non-final so we can mock them. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10822) java.lang.Error: Maximum permit count exceeded

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10822?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10822. --------------------------------- Fix Version/s: 10.1.0.Beta1 Resolution: Done > java.lang.Error: Maximum permit count exceeded > ---------------------------------------------- > > Key: ISPN-10822 > URL: https://issues.jboss.org/browse/ISPN-10822 > Project: Infinispan > Issue Type: Bug > Components: Clustered Executor > Affects Versions: 9.4.4.Final > Reporter: AshokKumar NV > Assignee: Will Burns > Priority: Major > Fix For: 10.1.0.Beta1 > > > We use an MS-SQL database when we are try to retrieve the data concurrently we are facing this issue. > Please find the stack trace. > {noformat} > java.lang.Error: Maximum permit count exceeded > at java.base/java.util.concurrent.Semaphore$Sync.tryReleaseShared(Semaphore.java:198) > at java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.releaseShared(AbstractQueuedSynchronizer.java:1382) > at java.base/java.util.concurrent.Semaphore.release(Semaphore.java:432) > at io.reactivex.internal.operators.flowable.FlowableUsing$UsingSubscriber.onComplete(FlowableUsing.java:139) > at io.reactivex.internal.operators.flowable.FlowableUsing$UsingSubscriber.onComplete(FlowableUsing.java:148) > at io.reactivex.internal.subscriptions.EmptySubscription.complete(EmptySubscription.java:68) > at io.reactivex.internal.operators.flowable.FlowableFromIterable.subscribe(FlowableFromIterable.java:61) > at io.reactivex.internal.operators.flowable.FlowableFromIterable.subscribeActual(FlowableFromIterable.java:47) > at io.reactivex.Flowable.subscribe(Flowable.java:14409) > at io.reactivex.Flowable.subscribe(Flowable.java:14356) > at io.reactivex.internal.operators.flowable.FlowableUsing.subscribeActual(FlowableUsing.java:74) > at io.reactivex.Flowable.subscribe(Flowable.java:14409) > at io.reactivex.Flowable.subscribe(Flowable.java:14356) > at io.reactivex.internal.operators.flowable.FlowableUsing.subscribeActual(FlowableUsing.java:74) > at io.reactivex.Flowable.subscribe(Flowable.java:14409) > at io.reactivex.internal.operators.flowable.FlowableMap.subscribeActual(FlowableMap.java:38) > at io.reactivex.Flowable.subscribe(Flowable.java:14409) > at io.reactivex.internal.operators.flowable.BlockingFlowableIterable.iterator(BlockingFlowableIterable.java:42) > at org.infinispan.util.Closeables.iterator(Closeables.java:30) > at org.infinispan.stream.impl.local.PersistenceEntryStreamSupplier.lambda$null$5(PersistenceEntryStreamSupplier.java:104) > at org.infinispan.util.LazyConcatIterator.hasNext(LazyConcatIterator.java:43) > at java.base/java.util.Spliterators$IteratorSpliterator.tryAdvance(Spliterators.java:1811) > at java.base/java.util.stream.StreamSpliterators$WrappingSpliterator.lambda$initPartialTraversalState$0(StreamSpliterators.java:294) > at java.base/java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.fillBuffer(StreamSpliterators.java:206) > at java.base/java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.doAdvance(StreamSpliterators.java:169) > at java.base/java.util.stream.StreamSpliterators$WrappingSpliterator.tryAdvance(StreamSpliterators.java:300) > at java.base/java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10749) Invalidation mode needs a proper key partitioner

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10749?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10749. --------------------------------- Resolution: Done > Invalidation mode needs a proper key partitioner > ------------------------------------------------ > > Key: ISPN-10749 > URL: https://issues.jboss.org/browse/ISPN-10749 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.0.Final > > > Caches in invalidation mode used to do everything on the local node and only broadcast an invalidation command to all the members. ISPN-10029 changed this, and now transactional invalidation caches acquire locks for affected keys on the primary owners. > Unfortunately {{KeyPartitionerFactory}} constructs a {{SingleSegmentKeyPartitioner}} in invalidation mode, so there is only one primary owner for all the keys. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10880) JCacheConfigurationTest leaks cache manager

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10880?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10880. --------------------------------- Resolution: Done > JCacheConfigurationTest leaks cache manager > ------------------------------------------- > > Key: ISPN-10880 > URL: https://issues.jboss.org/browse/ISPN-10880 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 10.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.1.0.Beta1 > > > {noformat} > ThreadLeakCheckerorg.infinispan.commons.test.ThreadLeakChecker$LeakException: Leaked thread: expiration-thread--p446-t1 << testng-JCacheConfigurationTest << org.infinispan.jcache.JCacheConfigurationTest > ... > Caused by: org.infinispan.commons.test.ThreadLeakChecker$LeakException: testng-JCacheConfigurationTest << org.infinispan.jcache.JCacheConfigurationTest > at org.infinispan.commons.test.ThreadLeakChecker$ThreadInfoLocal.childValue(ThreadLeakChecker.java:107) > ... > at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:713) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:391) > at org.infinispan.jcache.embedded.JCacheManager.<init>(JCacheManager.java:75) > at org.infinispan.jcache.JCacheConfigurationTest.lambda$testJCacheManagerWithRealJarFileSchema$1(JCacheConfigurationTest.java:107) > at org.infinispan.jcache.util.JCacheTestingUtil.withCachingProvider(JCacheTestingUtil.java:36) > at org.infinispan.jcache.JCacheConfigurationTest.testJCacheManagerWithRealJarFileSchema(JCacheConfigurationTest.java:104) > {noformat} > The leak is only reported some of the time because {{AbstractJCacheManager}} has a {{finalize()}} method and stops the underlying cache manager. > The threads created by {{DefaultCacheManager}} ensure it's still referenced during finalization, allowing it to stop cleanly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10824) Hanged tests are ignored by Jenkins

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10824?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10824. --------------------------------- Resolution: Done > Hanged tests are ignored by Jenkins > ----------------------------------- > > Key: ISPN-10824 > URL: https://issues.jboss.org/browse/ISPN-10824 > Project: Infinispan > Issue Type: Bug > Components: Build, Test Suite - Core > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final > > > ISPN-10161 was supposed to add a custom JUnit report in {{RunningTestsRegistry}} just before killing the JVM. Unfortunately it only calls {{TestSuiteProgress.fakeTestFailure()}}, which sounds like it should do it, but actually only writes a {{Test failed:}} messsage to the console, which Jenkins ignores. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10920) [9.4.x] SB Starter Versions

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10920?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10920: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/oraNod/infinispan/pull/new/ISPN-10920 > [9.4.x] SB Starter Versions > --------------------------- > > Key: ISPN-10920 > URL: https://issues.jboss.org/browse/ISPN-10920 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Need to document SB starter dependencies, relates to JDG-3308 > http://download.eng.bos.redhat.com/brewroot/packages/org.infinispan-infin... > 1.0.7.Final-redhat-00011 is for SB 1.5.x > http://download.eng.bos.redhat.com/brewroot/packages/org.infinispan-infin... > 2.1.8.redhat-00001 is for SB 2.x > https://github.com/infinispan/infinispan/blob/792fdc4d7b98bd009eea8632b28... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10920) [9.4.x] SB Starter Versions

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10920?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10920: ------------------------------- Status: Open (was: New) > [9.4.x] SB Starter Versions > --------------------------- > > Key: ISPN-10920 > URL: https://issues.jboss.org/browse/ISPN-10920 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Need to document SB starter dependencies, relates to JDG-3308 > http://download.eng.bos.redhat.com/brewroot/packages/org.infinispan-infin... > 1.0.7.Final-redhat-00011 is for SB 1.5.x > http://download.eng.bos.redhat.com/brewroot/packages/org.infinispan-infin... > 2.1.8.redhat-00001 is for SB 2.x > https://github.com/infinispan/infinispan/blob/792fdc4d7b98bd009eea8632b28... -- 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