January 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9720) JDK11: An illegal reflective access operation has occurred

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9720?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9720: -------------------------------- Tester: Diego Lovison > JDK11: An illegal reflective access operation has occurred > ---------------------------------------------------------- > > Key: ISPN-9720 > URL: https://issues.jboss.org/browse/ISPN-9720 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.1.Final > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Critical > Labels: Java11 > Fix For: 10.0.0.Alpha2, 9.3.6.Final, 9.4.4.Final > > > server prints infinispan warnings during deploying the deployment or start server with deployment: > {noformat} > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by org.infinispan.marshall.exts.SecurityActions (jar:file:/home/mkopecky/playground/eap/7.2.0.GA.CR1/jboss-eap-7.2/modules/system/layers/base/org/infinispan/main/infinispan-core-9.3.3.Final-redhat-00001.jar!/) to field java.util.DoubleSummaryStatistics.count > WARNING: Please consider reporting this to the maintainers of org.infinispan.marshall.exts.SecurityActions > WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations > WARNING: All illegal access operations will be denied in a future release > {noformat} > This is follow up for JBEAP-15475, as [~jamezp] mentioned in [his comment|https://issues.jboss.org/browse/JBEAP-15475?focusedCommentId=1364...]. > cc: [~msvehla], [~rsvoboda] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9628) infinispan-commons MANIFEST doesn not include Multi-Release entry

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9628?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9628: -------------------------------- Tester: Diego Lovison > infinispan-commons MANIFEST doesn not include Multi-Release entry > ----------------------------------------------------------------- > > Key: ISPN-9628 > URL: https://issues.jboss.org/browse/ISPN-9628 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 9.3.3.Final, 9.4.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 9.3.4.Final, 9.4.1.Final > > > The Multi-Release:true entry is present in infinispan-commons test-jar but not in the main jar. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9873) Remove listeners when the lock is removed

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9873?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9873: ------------------------------- Description: When the ClusteredLockImpl object is created, two listeners are added to the cache. These listeners have to be removed when the lock object is removed. This causes a memory leak. This issue has been detected by a user who sent a reproducer. https://github.com/kzaida/clusteredLock-test was: When the ClusteredLockImpl object is created, two listeners are added to the cache. These listeners have to be removed when the ClusteredLockImpl object is removed. This causes a memory leak. This issue has been detected by a user who sent a reproducer. https://github.com/kzaida/clusteredLock-test > Remove listeners when the lock is removed > ----------------------------------------- > > Key: ISPN-9873 > URL: https://issues.jboss.org/browse/ISPN-9873 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.5.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 9.4.6.Final > > > When the ClusteredLockImpl object is created, two listeners are added to the cache. These listeners have to be removed when the lock object is removed. This causes a memory leak. > This issue has been detected by a user who sent a reproducer. > https://github.com/kzaida/clusteredLock-test -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9873) Remove listeners when the lock is removed

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9873?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9873: ------------------------------- Priority: Critical (was: Major) > Remove listeners when the lock is removed > ----------------------------------------- > > Key: ISPN-9873 > URL: https://issues.jboss.org/browse/ISPN-9873 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.5.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 9.4.6.Final > > > When the ClusteredLockImpl object is created, two listeners are added to the cache. These listeners have to be removed when the ClusteredLockImpl object is removed. This causes a memory leak. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9873) Remove listeners when the lock is removed

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9873?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9873: ------------------------------- Description: When the ClusteredLockImpl object is created, two listeners are added to the cache. These listeners have to be removed when the ClusteredLockImpl object is removed. This causes a memory leak. This issue has been detected by a user who sent a reproducer. https://github.com/kzaida/clusteredLock-test was:When the ClusteredLockImpl object is created, two listeners are added to the cache. These listeners have to be removed when the ClusteredLockImpl object is removed. This causes a memory leak. > Remove listeners when the lock is removed > ----------------------------------------- > > Key: ISPN-9873 > URL: https://issues.jboss.org/browse/ISPN-9873 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.5.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Fix For: 9.4.6.Final > > > When the ClusteredLockImpl object is created, two listeners are added to the cache. These listeners have to be removed when the ClusteredLockImpl object is removed. This causes a memory leak. > This issue has been detected by a user who sent a reproducer. > https://github.com/kzaida/clusteredLock-test -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9873) Remove listeners when the lock is removed

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9873?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9873: ------------------------------- Status: Open (was: New) > Remove listeners when the lock is removed > ----------------------------------------- > > Key: ISPN-9873 > URL: https://issues.jboss.org/browse/ISPN-9873 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.5.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 9.4.6.Final > > > When the ClusteredLockImpl object is created, two listeners are added to the cache. These listeners have to be removed when the ClusteredLockImpl object is removed. This causes a memory leak. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9873) Remove listeners when the lock is removed

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9873?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9873: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6595 > Remove listeners when the lock is removed > ----------------------------------------- > > Key: ISPN-9873 > URL: https://issues.jboss.org/browse/ISPN-9873 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.5.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 9.4.6.Final > > > When the ClusteredLockImpl object is created, two listeners are added to the cache. These listeners have to be removed when the ClusteredLockImpl object is removed. This causes a memory leak. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9873) Remove listeners when the lock is removed

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9873?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9873: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6595, https://github.com/infinispan/infinispan/pull/6597 (was: https://github.com/infinispan/infinispan/pull/6595) > Remove listeners when the lock is removed > ----------------------------------------- > > Key: ISPN-9873 > URL: https://issues.jboss.org/browse/ISPN-9873 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.5.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 9.4.6.Final > > > When the ClusteredLockImpl object is created, two listeners are added to the cache. These listeners have to be removed when the ClusteredLockImpl object is removed. This causes a memory leak. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9873) Remove listeners when the lock is removed

by Katia Aresti (Jira)

Katia Aresti created ISPN-9873: ---------------------------------- Summary: Remove listeners when the lock is removed Key: ISPN-9873 URL: https://issues.jboss.org/browse/ISPN-9873 Project: Infinispan Issue Type: Bug Affects Versions: 9.4.5.Final Reporter: Katia Aresti Assignee: Katia Aresti Fix For: 9.4.6.Final When the ClusteredLockImpl object is created, two listeners are added to the cache. These listeners have to be removed when the ClusteredLockImpl object is removed. This causes a memory leak. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9762) Cache hangs during rebalancing

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9762?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9762: -------------------------------- Tester: Diego Lovison > Cache hangs during rebalancing > ------------------------------ > > Key: ISPN-9762 > URL: https://issues.jboss.org/browse/ISPN-9762 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.2.Final, 10.0.0.Alpha1 > Reporter: Sergey Chernolyas > Assignee: Ryan Emerson > Priority: Blocker > Fix For: 10.0.0.Alpha2, 9.3.6.Final, 9.4.4.Final > > Attachments: hang_node.txt, normal_node.txt, stat_bad_node.png, stat_good_node.png > > > I have a cluster with two nodes. One node starts without problem. Second node hangs on rebalancing cache DEVICES. > Configuration of the cache: > {code:xml} > <distributed-cache name="DEVICES" owners="2" segments="256" mode="SYNC"> > <state-transfer await-initial-transfer="true" enabled="true" timeout="2400000" chunk-size="2048"/> > <partition-handling when-split="ALLOW_READ_WRITES" merge-policy="PREFERRED_ALWAYS"/> > <memory> > <object size="300000" strategy="REMOVE"/> > </memory> > <rocksdb-store preload="true" path="/data/rocksdb/devices/data"> > <expiration path="/data/rocksdb/devices/expired"/> > </rocksdb-store> > <indexing index="LOCAL"> > <property name="default.indexmanager">org.infinispan.query.indexmanager.InfinispanIndexManager</property> > <property name="default.directory_provider">infinispan</property> > <property name="default.worker.execution">async</property> > <property name="default.index_flush_interval">500</property> > <property name="default.indexwriter.merge_factor">30</property> > <property name="default.indexwriter.merge_max_size">1024</property> > <property name="default.indexwriter.ram_buffer_size">256</property> > <property name="default.locking_cachename">LuceneIndexesLocking_devices</property> > <property name="default.data_cachename">LuceneIndexesData_devices</property> > <property name="default.metadata_cachename">LuceneIndexesMetadata_devices</property> > </indexing> > <expiration max-idle="172800000"/> > </distributed-cache> > {code} > The cache contains 70 000 elements. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2019