January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11141) Spring Boot 2.2.2

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11141: -------------------------------------- Summary: Spring Boot 2.2.2 Key: ISPN-11141 URL: https://issues.redhat.com/browse/ISPN-11141 Project: Infinispan Issue Type: Component Upgrade Components: Spring Integration Affects Versions: 9.4.17.Final Reporter: Tristan Tarrant Assignee: Tristan Tarrant -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11140) RemoteCache w/near cache throws InstanceAlreadyExistsException following restart

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/ISPN-11140?page=com.atlassian.jira.plugi... ] Paul Ferraro reassigned ISPN-11140: ----------------------------------- Assignee: Paul Ferraro > RemoteCache w/near cache throws InstanceAlreadyExistsException following restart > -------------------------------------------------------------------------------- > > Key: ISPN-11140 > URL: https://issues.redhat.com/browse/ISPN-11140 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > > A RemoteCache using a near cache throws javax.management.InstanceAlreadyExistsException on restart. RemoteCache w/out a near cache restarts without issue. > This is because InvalidatedNearRemoteCache.stop() does not call the super implementation, which unregisters its mbeans. > This issue technically affects older versions, but the allowDuplicateDomains logic circumvents the InstanceAlreadyExistsException problem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11140) RemoteCache w/near cache throws InstanceAlreadyExistsException following restart

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/ISPN-11140?page=com.atlassian.jira.plugi... ] Paul Ferraro updated ISPN-11140: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7727 > RemoteCache w/near cache throws InstanceAlreadyExistsException following restart > -------------------------------------------------------------------------------- > > Key: ISPN-11140 > URL: https://issues.redhat.com/browse/ISPN-11140 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Priority: Critical > > A RemoteCache using a near cache throws javax.management.InstanceAlreadyExistsException on restart. RemoteCache w/out a near cache restarts without issue. > This is because InvalidatedNearRemoteCache.stop() does not call the super implementation, which unregisters its mbeans. > This issue technically affects older versions, but the allowDuplicateDomains logic circumvents the InstanceAlreadyExistsException problem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11140) RemoteCache w/near cache throws InstanceAlreadyExistsException following restart

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/ISPN-11140?page=com.atlassian.jira.plugi... ] Paul Ferraro updated ISPN-11140: -------------------------------- Status: Open (was: New) > RemoteCache w/near cache throws InstanceAlreadyExistsException following restart > -------------------------------------------------------------------------------- > > Key: ISPN-11140 > URL: https://issues.redhat.com/browse/ISPN-11140 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Priority: Critical > > A RemoteCache using a near cache throws javax.management.InstanceAlreadyExistsException on restart. RemoteCache w/out a near cache restarts without issue. > This is because InvalidatedNearRemoteCache.stop() does not call the super implementation, which unregisters its mbeans. > This issue technically affects older versions, but the allowDuplicateDomains logic circumvents the InstanceAlreadyExistsException problem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11140) RemoteCache w/near cache throws InstanceAlreadyExistsException following restart

by Paul Ferraro (Jira)

Paul Ferraro created ISPN-11140: ----------------------------------- Summary: RemoteCache w/near cache throws InstanceAlreadyExistsException following restart Key: ISPN-11140 URL: https://issues.redhat.com/browse/ISPN-11140 Project: Infinispan Issue Type: Bug Components: Hot Rod Affects Versions: 10.1.0.Final Reporter: Paul Ferraro A RemoteCache using a near cache throws javax.management.InstanceAlreadyExistsException on restart. RemoteCache w/out a near cache restarts without issue. This is because InvalidatedNearRemoteCache.stop() does not call the super implementation, which unregisters its mbeans. This issue technically affects older versions, but the allowDuplicateDomains logic circumvents the InstanceAlreadyExistsException problem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11139) Create separate modules for embedded and remote JCache TCK

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11139?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11139: -------------------------------- Status: Open (was: New) > Create separate modules for embedded and remote JCache TCK > ---------------------------------------------------------- > > Key: ISPN-11139 > URL: https://issues.redhat.com/browse/ISPN-11139 > Project: Infinispan > Issue Type: Task > Components: JCache, Test Suite > Affects Versions: 10.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.1.Final > > > The {{jcache-tck-runner}} POM is very complex, because it needs both the embedded and the remote dependencies, and then needs two {{maven-failsafe-plugin}} executions that filter out unneeded dependencies. > Having two separate modules will simplify the POMs and will also allow running the embedded TCK without starting (and building!) the server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11139) Create separate modules for embedded and remote JCache TCK

by Dan Berindei (Jira)

Dan Berindei created ISPN-11139: ----------------------------------- Summary: Create separate modules for embedded and remote JCache TCK Key: ISPN-11139 URL: https://issues.redhat.com/browse/ISPN-11139 Project: Infinispan Issue Type: Task Components: JCache, Test Suite Affects Versions: 10.1.0.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 10.1.1.Final The {{jcache-tck-runner}} POM is very complex, because it needs both the embedded and the remote dependencies, and then needs two {{maven-failsafe-plugin}} executions that filter out unneeded dependencies. Having two separate modules will simplify the POMs and will also allow running the embedded TCK without starting (and building!) the server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11138) Configuration WARN messages did not include the cache name

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-11138: --------------------------------------- Summary: Configuration WARN messages did not include the cache name Key: ISPN-11138 URL: https://issues.redhat.com/browse/ISPN-11138 Project: Infinispan Issue Type: Enhancement Components: Core Affects Versions: 10.0.0.Final Reporter: Wolf-Dieter Fink If a cache is configured in a way that trigger a WARN message the log message will not contain the cache name. In case a template is used and/or multiple caches are configured that way the WARN message seems to be a duplicate and it is hard to track that down and fix (all) the problems - consider 10 messages like this and you might fix one but did not see a result as you don't count the messages. Examples are WARN [org.infinispan.CONFIG] (main) ISPN000564: Configured store 'SingleFileStore' is segmented and may use a large number of file descriptors WARN [org.infinispan.CONFIG] (main) ISPN000403: No indexable classes were defined for this indexed cache; switching to autodetection (support for autodetection will be removed in Infinispan 11). So it would be good to know which cache configuration is the cause of this -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11137) Remove AdvancedCache.removeLifespanExpired and removeMaxIdleExpired

by Dan Berindei (Jira)

Dan Berindei created ISPN-11137: ----------------------------------- Summary: Remove AdvancedCache.removeLifespanExpired and removeMaxIdleExpired Key: ISPN-11137 URL: https://issues.redhat.com/browse/ISPN-11137 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 10.1.0.Final Reporter: Dan Berindei Assignee: Will Burns Fix For: 11.0.0.Final {{removeLifespanExpired}} and {{removeMaxIdleExpired}} are in the {{AdvancedCache}} interface, but they are only for internal use, not public API. We should remove them, and {{ClusterExpirationManager.removeMaxIdle()}} should create a {{RemoveExpiredCommand}} and execute it with the invocation chain just like {{org.infinispan.cache.impl.CacheImpl.performRemoveExpiredCommand()}} does. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11123) Integrate Mutiny in the new api

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11123?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11123: -------------------------------- Description: Mutiny API has been released in the first version. Upgrade the new reactive api to use it was: Mutinity API has been released in the first version. Upgrade the new reactive api to use it > Integrate Mutiny in the new api > ------------------------------- > > Key: ISPN-11123 > URL: https://issues.redhat.com/browse/ISPN-11123 > Project: Infinispan > Issue Type: Feature Request > Components: API > Affects Versions: 10.1.0.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: api > > Mutiny API has been released in the first version. > Upgrade the new reactive api to use it -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2020