December 2016 - infinispan-issues

[JBoss JIRA] (ISPN-1947) Automate staging repository step in release script

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-1947?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-1947: ------------------------------------------- Together with [~NadirX] we agreed that closing staging automatically is not the best approach. What we would like to to instead is to release our stuff, run automated tests on staging repository and close it when they are OK. > Automate staging repository step in release script > -------------------------------------------------- > > Key: ISPN-1947 > URL: https://issues.jboss.org/browse/ISPN-1947 > Project: Infinispan > Issue Type: Task > Components: Build process > Reporter: Sanne Grinovero > Assignee: Sebastian Łaskawiec > Priority: Critical > Fix For: 9.0.0.Beta1 > > > The Nexus staging plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file) > https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7160) RemoteSpringSessionTest random failures

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7160?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7160: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > RemoteSpringSessionTest random failures > --------------------------------------- > > Key: ISPN-7160 > URL: https://issues.jboss.org/browse/ISPN-7160 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Reporter: Dan Berindei > Assignee: Sebastian Łaskawiec > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Beta2 > > > {{RemoteSpringSessionTest}} and {{EmbeddedSpringSessionTest}} use the default cache jmx configuration, so they try to register the same JMX object names. If they run in parallel, one of them will fail to start the cache manager: > {noformat} > org.infinispan.jmx.JmxDomainConflictException: ISPN000034: There's already a JMX MBean instance type=CacheManager,name="DefaultCacheManager" already registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element > at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:53) > at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:79) > at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:73) > at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:37) > at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41) > at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:661) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:235) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:147) > at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.beforeclass(RemoteSpringSessionTest.java:29) > {noformat} > If the cache manager was not created, teardown also fails with a NPE: > {noformat} > java.lang.NullPointerException > at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.afterClass(RemoteSpringSessionTest.java:41) > {noformat} > The test should use the {{TestCacheManagerFactory}} methods to create the cache manager, which will set a unique JMX domain name for each instance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7283) Make remote event supporting cluster listener more fine grained

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7283?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7283: ----------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4711, https://github.com/infinispan/infinispan/pull/4721, https://github.com/infinispan/infinispan/pull/4728 (was: https://github.com/infinispan/infinispan/pull/4711, https://github.com/infinispan/infinispan/pull/4721) > Make remote event supporting cluster listener more fine grained > --------------------------------------------------------------- > > Key: ISPN-7283 > URL: https://issues.jboss.org/browse/ISPN-7283 > Project: Infinispan > Issue Type: Bug > Components: Listeners, Remote Protocols > Affects Versions: 9.0.0.Alpha4, 8.2.5.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Beta2, 8.2.6.Final > > > Make server side cluster listener used for supporting remote events more fine grained. Right now if a client registers for created events, server side all nodes push all currently supported events over to the node where the remote listener is located: created, modified, removed and expired. Having all these events being passed around the cluster creates unnecessary load which can create problems in other nodes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7315) Use activations manager for cluster wide activations stats collection

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7315?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7315: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Use activations manager for cluster wide activations stats collection > --------------------------------------------------------------------- > > Key: ISPN-7315 > URL: https://issues.jboss.org/browse/ISPN-7315 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Beta1 > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Beta2 > > > In ClusterCacheStatsImpl.java we erroneously used passivation manager null check while accessing activation manager. This probably worked because these two were used in tandem but we should nonetheless use an appropriate null check. I ran into NPE when testing 9.0.0.Beta1 and testing off-heap memory -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5806) Add transaction support for Functional API

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5806?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5806: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add transaction support for Functional API > ------------------------------------------ > > Key: ISPN-5806 > URL: https://issues.jboss.org/browse/ISPN-5806 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Radim Vansa > Fix For: 9.0.0.Beta2, 9.0.0.Final > > > A local cache with batching enabled produces this: > {code:java} > java.lang.IllegalArgumentException: Cannot create a transactional > context without a valid Transaction instance. > at org.infinispan.context.TransactionalInvocationContextFactory.createInvocationContext(TransactionalInvocationContextFactory.java:69) > at org.infinispan.context.TransactionalInvocationContextFactory.createInvocationContext(TransactionalInvocationContextFactory.java:63) > at org.infinispan.functional.impl.ReadWriteMapImpl.eval(ReadWriteMapImpl.java:56) > at org.infinispan.lucene.impl.FileListOperations.addFileName(FileListOperations.java:60) > (<-- experimental uncommitted code here) > {code} > For single operations that carry no transaction context, don't try to start a transaction and create a transactional context. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5806) Add transaction support for Functional API

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5806?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5806: ----------------------------------- Fix Version/s: 9.0.0.Beta2 9.0.0.Final > Add transaction support for Functional API > ------------------------------------------ > > Key: ISPN-5806 > URL: https://issues.jboss.org/browse/ISPN-5806 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Radim Vansa > Fix For: 9.0.0.Beta2, 9.0.0.Final > > > A local cache with batching enabled produces this: > {code:java} > java.lang.IllegalArgumentException: Cannot create a transactional > context without a valid Transaction instance. > at org.infinispan.context.TransactionalInvocationContextFactory.createInvocationContext(TransactionalInvocationContextFactory.java:69) > at org.infinispan.context.TransactionalInvocationContextFactory.createInvocationContext(TransactionalInvocationContextFactory.java:63) > at org.infinispan.functional.impl.ReadWriteMapImpl.eval(ReadWriteMapImpl.java:56) > at org.infinispan.lucene.impl.FileListOperations.addFileName(FileListOperations.java:60) > (<-- experimental uncommitted code here) > {code} > For single operations that carry no transaction context, don't try to start a transaction and create a transactional context. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7160) RemoteSpringSessionTest random failures

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7160?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7160: -------------------------------------- Status: Pull Request Sent (was: Reopened) > RemoteSpringSessionTest random failures > --------------------------------------- > > Key: ISPN-7160 > URL: https://issues.jboss.org/browse/ISPN-7160 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Reporter: Dan Berindei > Assignee: Sebastian Łaskawiec > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Beta2 > > > {{RemoteSpringSessionTest}} and {{EmbeddedSpringSessionTest}} use the default cache jmx configuration, so they try to register the same JMX object names. If they run in parallel, one of them will fail to start the cache manager: > {noformat} > org.infinispan.jmx.JmxDomainConflictException: ISPN000034: There's already a JMX MBean instance type=CacheManager,name="DefaultCacheManager" already registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element > at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:53) > at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:79) > at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:73) > at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:37) > at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41) > at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:661) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:235) > at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:147) > at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.beforeclass(RemoteSpringSessionTest.java:29) > {noformat} > If the cache manager was not created, teardown also fails with a NPE: > {noformat} > java.lang.NullPointerException > at org.infinispan.integrationtests.spring.boot.session.remote.RemoteSpringSessionTest.afterClass(RemoteSpringSessionTest.java:41) > {noformat} > The test should use the {{TestCacheManagerFactory}} methods to create the cache manager, which will set a unique JMX domain name for each instance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7080) NPE in CacheNotifierImpl by LIRS eviction listener

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-7080?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-7080: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1382273, https://bugzilla.redhat.com/show_bug.cgi?id=1404373 Bugzilla Update: Perform > NPE in CacheNotifierImpl by LIRS eviction listener > --------------------------------------------------- > > Key: ISPN-7080 > URL: https://issues.jboss.org/browse/ISPN-7080 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.0.0.Alpha4 > Environment: * Infinispan branch: Upstream master > Reporter: ted won > Assignee: William Burns > Labels: core, eviction, lirs > Fix For: 9.0.0.Beta1 > > > The LIRSEvictionFunctionalTest.testSimpleEvictionMaxEntries unit test method in core module fails and throws NPE in CacheNotifierImpl.notifyCacheEntriesEvicted method when trying to reinsert the first keys again. > https://github.com/infinispan/infinispan/blob/master/core/src/test/java/o... > It reproduces only with LIRS eviction strategy and eviction listener. > However, LRU and UNORDERED eviction strategies are working properly. > It makes impossible the use of eviction listeners with LIRS eviction strategy. > It's able to reproduce by: > - inserting 20 keys - values in a 10 sized cache ( keys from key-1 to key-20), > - and then reinsert the first 10 keys (key-1 to key-10) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7315) Use activations manager for cluster wide activations stats collection

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7315?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7315: -------------------------------------- Status: Open (was: New) > Use activations manager for cluster wide activations stats collection > --------------------------------------------------------------------- > > Key: ISPN-7315 > URL: https://issues.jboss.org/browse/ISPN-7315 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Beta1 > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Beta2 > > > In ClusterCacheStatsImpl.java we erroneously used passivation manager null check while accessing activation manager. This probably worked because these two were used in tandem but we should nonetheless use an appropriate null check. I ran into NPE when testing 9.0.0.Beta1 and testing off-heap memory -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7315) Use activations manager for cluster wide activations stats collection

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7315?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7315: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4727/ > Use activations manager for cluster wide activations stats collection > --------------------------------------------------------------------- > > Key: ISPN-7315 > URL: https://issues.jboss.org/browse/ISPN-7315 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Beta1 > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Beta2 > > > In ClusterCacheStatsImpl.java we erroneously used passivation manager null check while accessing activation manager. This probably worked because these two were used in tandem but we should nonetheless use an appropriate null check. I ran into NPE when testing 9.0.0.Beta1 and testing off-heap memory -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 December 2016