November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-9771) Support for configuration in JSON format

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-9771?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-9771: --------------------------------------- Assignee: Gustavo Fernandes > Support for configuration in JSON format > ---------------------------------------- > > Key: ISPN-9771 > URL: https://issues.jboss.org/browse/ISPN-9771 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 10.0.0.Alpha1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > To support the cache resource in the v2 endpoint -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9773) Disabling a store puts persistence manager in invalid state if there is another store

by William Burns (Jira)

William Burns created ISPN-9773: ----------------------------------- Summary: Disabling a store puts persistence manager in invalid state if there is another store Key: ISPN-9773 URL: https://issues.jboss.org/browse/ISPN-9773 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Reporter: William Burns Assignee: William Burns Fix For: 9.3.6.Final, 10.0.0.Alpha2, 9.4.3.Final When we disable a store, we accidentally remove all of the storeStatuses. This can cause an issue if there is another store configured besides the one that was just disabled. The problem is that this line is always invoked https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... We need to optionally invoke it if the store matches the type. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9463) Provide API to enlist the resource with TransactionManager

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-9463?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-9463: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6470 > Provide API to enlist the resource with TransactionManager > ---------------------------------------------------------- > > Key: ISPN-9463 > URL: https://issues.jboss.org/browse/ISPN-9463 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod, Remote Protocols, Transactions > Reporter: Ramesh Reddy > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Alpha2 > > > Currently, Infinispan will automatically enlist the transaction when a transaction is bound to the executing thread. However, in cases like Teiid where remote access to Infinispan access is wrapped with a resource-adapter (RAR) the resource adapter does the explicit enlisting or delisting. For this there needs to be API provided by Infinispan Cache like > {code} > RemoteCacheManager.getXaResource() > {code} > where it can access the XA resource. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9463) Provide API to enlist the resource with TransactionManager

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-9463?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-9463: ------------------------------ Fix Version/s: 10.0.0.Alpha2 > Provide API to enlist the resource with TransactionManager > ---------------------------------------------------------- > > Key: ISPN-9463 > URL: https://issues.jboss.org/browse/ISPN-9463 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod, Remote Protocols, Transactions > Reporter: Ramesh Reddy > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Alpha2 > > > Currently, Infinispan will automatically enlist the transaction when a transaction is bound to the executing thread. However, in cases like Teiid where remote access to Infinispan access is wrapped with a resource-adapter (RAR) the resource adapter does the explicit enlisting or delisting. For this there needs to be API provided by Infinispan Cache like > {code} > RemoteCacheManager.getXaResource() > {code} > where it can access the XA resource. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9463) Provide API to enlist the resource with TransactionManager

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-9463?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-9463: ------------------------------ Status: Open (was: New) > Provide API to enlist the resource with TransactionManager > ---------------------------------------------------------- > > Key: ISPN-9463 > URL: https://issues.jboss.org/browse/ISPN-9463 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod, Remote Protocols, Transactions > Reporter: Ramesh Reddy > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Alpha2 > > > Currently, Infinispan will automatically enlist the transaction when a transaction is bound to the executing thread. However, in cases like Teiid where remote access to Infinispan access is wrapped with a resource-adapter (RAR) the resource adapter does the explicit enlisting or delisting. For this there needs to be API provided by Infinispan Cache like > {code} > RemoteCacheManager.getXaResource() > {code} > where it can access the XA resource. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8844) [JDK9+] org.infinispan.util package is exported by multiple jars

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-8844?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-8844: ----------------------------------------- Looks for the class AbstractDelegatingSet for example, it was being included both in commons and in core before the fix > [JDK9+] org.infinispan.util package is exported by multiple jars > ---------------------------------------------------------------- > > Key: ISPN-8844 > URL: https://issues.jboss.org/browse/ISPN-8844 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.6.Final > Environment: JDK9, JDK10 > Reporter: Tomaz Cerar > Assignee: Gustavo Fernandes > Priority: Major > Labels: on-hold > Fix For: 9.4.0.Alpha1, 9.4.0.CR3, 9.3.4.Final > > > Currently if you have > {{infinispan-commons-9.1.6.Final.jar}} and {{infinispan-core-9.1.6.Final.jar}} > on your module path, jvm complains as both jars export package {{org.infinispan.util}} > which violates the modules contract where only one module (jar) can provide single package. > example error that jvm prints > {noformat} > Error: Modules infinispan.commons and infinispan.core export package org.infinispan.util to module wildfly.clustering.common > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9415) Client topology is not updated after cache becomes degraded

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-9415?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-9415: -------------------------------- Tester: Diego Lovison > Client topology is not updated after cache becomes degraded > ----------------------------------------------------------- > > Key: ISPN-9415 > URL: https://issues.jboss.org/browse/ISPN-9415 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 9.4.0.Beta1, 9.3.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.0.CR3 > > > When a new server is started, or after a merge, the other servers may see it as a an owner in the consistent hash before the other servers see its server address in the address cache ({{___hotRodTopologyCache}}). When a server needs to send a topology update but some of the servers are missing from the address cache, it can't send the topology update, so it tries to send a "partial update" that excludes the missing servers from the segment owners. In order to send the full topology update when the address cache is populated, the partial topology update has to be sent a smaller topology id, and that means it is only send if {{serverTopologyId >= clientTopologyId + 2}}. > When the cluster splits and the cache becomes degraded, the servers in the other partition are removed from the address cache, but the list of segment owners is not updated, and the topology id is only incremented by 1. The address cache is incomplete, but a partial update cannot be sent, so the client keeps the old topology and keeps trying to connect to the servers in the other partition. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8844) [JDK9+] org.infinispan.util package is exported by multiple jars

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-8844?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-8844: -------------------------------- Labels: on-hold (was: ) > [JDK9+] org.infinispan.util package is exported by multiple jars > ---------------------------------------------------------------- > > Key: ISPN-8844 > URL: https://issues.jboss.org/browse/ISPN-8844 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.6.Final > Environment: JDK9, JDK10 > Reporter: Tomaz Cerar > Assignee: Gustavo Fernandes > Priority: Major > Labels: on-hold > Fix For: 9.4.0.Alpha1, 9.4.0.CR3, 9.3.4.Final > > > Currently if you have > {{infinispan-commons-9.1.6.Final.jar}} and {{infinispan-core-9.1.6.Final.jar}} > on your module path, jvm complains as both jars export package {{org.infinispan.util}} > which violates the modules contract where only one module (jar) can provide single package. > example error that jvm prints > {noformat} > Error: Modules infinispan.commons and infinispan.core export package org.infinispan.util to module wildfly.clustering.common > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8844) [JDK9+] org.infinispan.util package is exported by multiple jars

by Diego Lovison (Jira)

[ https://issues.jboss.org/browse/ISPN-8844?page=com.atlassian.jira.plugin.... ] Diego Lovison updated ISPN-8844: -------------------------------- Tester: Diego Lovison > [JDK9+] org.infinispan.util package is exported by multiple jars > ---------------------------------------------------------------- > > Key: ISPN-8844 > URL: https://issues.jboss.org/browse/ISPN-8844 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.6.Final > Environment: JDK9, JDK10 > Reporter: Tomaz Cerar > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 9.4.0.Alpha1, 9.4.0.CR3, 9.3.4.Final > > > Currently if you have > {{infinispan-commons-9.1.6.Final.jar}} and {{infinispan-core-9.1.6.Final.jar}} > on your module path, jvm complains as both jars export package {{org.infinispan.util}} > which violates the modules contract where only one module (jar) can provide single package. > example error that jvm prints > {noformat} > Error: Modules infinispan.commons and infinispan.core export package org.infinispan.util to module wildfly.clustering.common > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5997) JMX operation ClusterCacheStats.resetStatistics() not working

by Vladimir Blagojevic (Jira)

[ https://issues.jboss.org/browse/ISPN-5997?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-5997: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6469 > JMX operation ClusterCacheStats.resetStatistics() not working > ------------------------------------------------------------- > > Key: ISPN-5997 > URL: https://issues.jboss.org/browse/ISPN-5997 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.1.0.CR1 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Priority: Major > > Environment: 2 servers started in domain mode (ISPN 8.1.0.CR1). > Having some clustered cache, inserted/read some entries (just to create some statistics). > When connected via JMX (e.g. through JConsole, see https://issues.jboss.org/browse/ISPN-5983 ) to one of the servers, I execute resetStatistics() operation on ClusterCacheStats MBean (object name: jboss.datagrid-infinispan:type=Cache,name="<cache-name>",manager="<cache-container-name>",component=ClusterCacheStats) and nothing happens, the cluster statistics are not reset. > To actually reset the statistics, I have to connect to each of the servers in domain individually and call resetStatistics() on Statistics MBean, which deletes "a portion" of statistics of that particular server to the cluster stats. > I would expect ClusterCacheStats.resetStatistics() to do exactly the same: call Statistics.resetStatistics() on each server. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 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 November 2018