March 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11345) Introduce integration tests for serverNG

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11345?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11345: ------------------------------------------ Sprint: DataGrid Sprint #41 > Introduce integration tests for serverNG > ---------------------------------------- > > Key: ISPN-11345 > URL: https://issues.redhat.com/browse/ISPN-11345 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 11.0.0.Alpha1 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Critical > > Introduce integration tests for serverNG > -Support Arquillian > -Arquillian is now optional > -Support multiple Infinispan Servers > *Support Arquillian* > Allow the current Infinispan source code to be deployed in the target container > *Arquillian is now optional* > As a developer, I would like to run the code without worrying about containers > *Support multiple Infinispan Servers* > As a QE, I would like to create a test scenario using multiple Infinispan Servers -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11367) getCache(name) should never use the default cache's configuration

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11367?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11367: ------------------------------------------ Sprint: DataGrid Sprint #40, DataGrid Sprint #41 (was: DataGrid Sprint #40) > getCache(name) should never use the default cache's configuration > ----------------------------------------------------------------- > > Key: ISPN-11367 > URL: https://issues.redhat.com/browse/ISPN-11367 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core > Affects Versions: 10.1.2.Final, 11.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Dev03 > > > {{DefaultCacheManager.getCache(name)}} will try to create the cache if it doesn't exist, and if a matching configuration doesn't exist either it uses the default cache's configuration. > Since 9.0 named cache configurations no longer inherit from the default cache configuration, so using the default cache's configuration as a default configuration is surprising. > {{DefaultCacheManager.getCache(name)}} should only create the cache if a matching configuration exists, otherwise it should throw an exception. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11425) Missing metada for persistent counter upon server restart

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11425?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11425: ------------------------------------------ Sprint: DataGrid Sprint #40, DataGrid Sprint #41 (was: DataGrid Sprint #40) > Missing metada for persistent counter upon server restart > --------------------------------------------------------- > > Key: ISPN-11425 > URL: https://issues.redhat.com/browse/ISPN-11425 > Project: Infinispan > Issue Type: Bug > Components: Clustered Counter > Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > If you create a counter with a persistent storage, shutdown and spin up the server again then it's no longer possible to add a value to that counter. Instead following error appear in the CLI log: > {code} > Error: java.lang.IllegalStateException: ISPN029518: Metadata not found but counter exists. Counter=cnt1 > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11408) Spring Session simple example in Infinispan Spring Boot Starter

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11408?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11408: ------------------------------------------ Sprint: DataGrid Sprint #41 > Spring Session simple example in Infinispan Spring Boot Starter > --------------------------------------------------------------- > > Key: ISPN-11408 > URL: https://issues.redhat.com/browse/ISPN-11408 > Project: Infinispan > Issue Type: Enhancement > Components: Spring Integration > Affects Versions: 10.1.3.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: spring, springboot > > Actually there is no example for Spring-Boot Session integration with Infinispan. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11388) Refactor CacheIgnoreManager - AbstractProtocolServer collaboration

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11388?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11388: ------------------------------------------ Sprint: DataGrid Sprint #40, DataGrid Sprint #41 (was: DataGrid Sprint #40) > Refactor CacheIgnoreManager - AbstractProtocolServer collaboration > ------------------------------------------------------------------ > > Key: ISPN-11388 > URL: https://issues.redhat.com/browse/ISPN-11388 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 10.1.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > Given the interactions between CacheIgnoreManager and AbstractProtocolServer it seems that CacheIgnoreManager should be a global component in the registry of the EmbeddedCacheManager sitting behind the AbstractProtocolServer. It should be looked up from there, or better injected, rather than being received in ProtocolServer.start method. The start method also has an overloaded version that does not take a CacheIgnoreManager to support tests the do not need it. This lack of orthogonality is annoyoing. > Another aspect to refactor: the startInternal method receives parametters that it assigns to fields. It seems that this should have been done already in the start method. That would get rid of some clunky hacks and some comments/excuses for the said hacks. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11389) Deprecate EmbeddedCacheManager.getStats() method because CacheContainerStats is already deprecated

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11389?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11389: ------------------------------------------ Sprint: DataGrid Sprint #40, DataGrid Sprint #41 (was: DataGrid Sprint #40) > Deprecate EmbeddedCacheManager.getStats() method because CacheContainerStats is already deprecated > -------------------------------------------------------------------------------------------------- > > Key: ISPN-11389 > URL: https://issues.redhat.com/browse/ISPN-11389 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 10.1.3.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11397) Align common dependencies with EAP

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11397?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11397: ------------------------------------------ Sprint: DataGrid Sprint #41 > Align common dependencies with EAP > ---------------------------------- > > Key: ISPN-11397 > URL: https://issues.redhat.com/browse/ISPN-11397 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 11.0.0.Alpha1, 10.1.3.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > > Align dependencies with the lastest EAP release: > {noformat} > =============================== > ** Needs Update: > com.sun.istack:istack-commons-runtime 3.0.5 -> 3.0.7 > commons-beanutils:commons-beanutils 1.9.3 -> 1.9.4 > commons-codec:commons-codec 1.10 -> 1.11 > org.apache.commons:commons-lang3 3.6 -> 3.9 > org.apache.httpcomponents:httpclient 4.5.2 -> 4.5.4 > org.apache.httpcomponents:httpcore 4.4.4 -> 4.4.5 > org.apache.httpcomponents:httpcore-nio 4.4.4 -> 4.4.5 > org.fusesource.jansi:jansi 1.16 -> 1.18 > org.glassfish.jaxb:jaxb-core 2.3.0 -> 2.3.1 > org.glassfish.jaxb:jaxb-runtime 2.3.0 -> 2.3.1 > org.glassfish.jaxb:txw2 2.3.0 -> 2.3.1 > org.hibernate.common:hibernate-commons-annotations 5.0.4.Final -> 5.0.5.Final > org.hibernate:hibernate-osgi 5.3.12.Final -> 5.3.14.Final > org.hibernate:hibernate-validator 5.3.12.Final -> 5.3.14.Final > org.jboss.classfilewriter:jboss-classfilewriter 1.2.2.Final -> 1.2.4.Final > org.jboss.invocation:jboss-invocation 1.5.1.Final -> 1.5.2.Final > org.jboss.modules:jboss-modules 1.8.7.Final -> 1.9.1.Final > org.jboss.msc:jboss-msc 1.4.2.Final -> 1.4.11.Final > org.jboss.openjdk-orb:openjdk-orb 8.1.1.Final -> 8.1.4.Final > org.jboss.remoting:jboss-remoting 5.0.7.Final -> 5.0.16.Final > org.jboss.remotingjmx:remoting-jmx 3.0.0.Final -> 3.0.3.Final > org.jboss.spec.javax.annotation:jboss-annotations-api_1.3_spec 1.0.1.Final -> 2.0.1.Final > org.jboss.spec.javax.batch:jboss-batch-api_1.0_spec 1.0.0.Final -> 2.0.0.Final > org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec 1.0.1.Final -> 2.0.0.Final > org.jboss.spec.javax.el:jboss-el-api_3.0_spec 1.0.11.Final -> 2.0.0.Final > org.jboss.spec.javax.enterprise.concurrent:jboss-concurrency-api_1.0_spec 1.0.2.Final -> 2.0.0.Final > org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.2_spec 1.0.1.Final -> 2.0.0.Final > org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec 1.0.2.Final -> 2.0.0.Final > org.jboss.spec.javax.management.j2ee:jboss-j2eemgmt-api_1.1_spec 1.0.1.Final -> 2.0.0.Final > org.jboss.spec.javax.resource:jboss-connector-api_1.7_spec 1.0.1.Final -> 2.0.0.Final > org.jboss.spec.javax.security.auth.message:jboss-jaspi-api_1.1_spec 1.0.0.Final -> 2.0.1.Final > org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec 1.0.2.Final -> 2.0.0.Final > org.jboss.spec.javax.servlet.jsp:jboss-jsp-api_2.3_spec 1.0.1.Final -> 2.0.0.Final > org.jboss.spec.javax.websocket:jboss-websocket-api_1.1_spec 1.1.0.Final -> 2.0.0.Final > org.jboss.spec.javax.xml.soap:jboss-saaj-api_1.3_spec 1.0.3.Final -> 1.0.6.Final > org.jboss.stdio:jboss-stdio 1.0.2.GA -> 1.1.0.Final > org.jboss.threads:jboss-threads 2.3.2.Final -> 2.3.3.Final > org.jboss.weld:weld-api 2.3.SP2 -> 3.1.SP1 > org.jboss.weld:weld-spi 2.3.SP2 -> 3.1.SP1 > org.jboss.xnio:xnio-api 3.7.3.Final -> 3.7.7.Final > org.jboss.xnio:xnio-nio 3.7.3.Final -> 3.7.7.Final > org.jboss:jboss-vfs 3.2.12.Final -> 3.2.14.Final > org.jgroups.azure:jgroups-azure 1.2.0.Final -> 1.2.1.Final > org.jgroups.kubernetes:jgroups-kubernetes 1.0.6.Final -> 1.0.13.Final > org.jsoup:jsoup 1.7.2 -> 1.8.3 > org.ow2.asm:asm 6.1.1 -> 7.1 > org.wildfly.client:wildfly-client-config 1.0.0.Final -> 1.0.1.Final > org.wildfly.security.elytron-web:undertow-server 1.1.0.Final -> 1.6.0.Final > org.wildfly.security:wildfly-elytron 1.10.3.Final -> 1.10.4.Final > org.wildfly.security:wildfly-elytron-sasl-digest 1.10.3.Final -> 1.10.4.Final > org.wildfly.security:wildfly-elytron-sasl-external 1.10.3.Final -> 1.10.4.Final > org.wildfly.security:wildfly-elytron-sasl-oauth2 1.10.3.Final -> 1.10.4.Final > org.wildfly.security:wildfly-elytron-sasl-plain 1.10.3.Final -> 1.10.4.Final > org.wildfly.security:wildfly-elytron-sasl-scram 1.10.3.Final -> 1.10.4.Final > org.wildfly.transaction:wildfly-transaction-client 1.1.2.Final -> 1.1.8.Final > org.wildfly.wildfly-http-client:wildfly-http-client-common 1.0.12.Final -> 1.0.18.Final > org.wildfly.wildfly-http-client:wildfly-http-naming-client 1.0.12.Final -> 1.0.18.Final > org.wildfly.wildfly-http-client:wildfly-http-transaction-client 1.0.12.Final -> 1.0.18.Final > org.wildfly:wildfly-naming-client 1.0.9.Final -> 1.0.11.Final > org.yaml:snakeyaml 1.17 -> 1.18 > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11390) Non-components cannot export metrics

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11390?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11390: ------------------------------------------ Sprint: DataGrid Sprint #40, DataGrid Sprint #41 (was: DataGrid Sprint #40) > Non-components cannot export metrics > ------------------------------------ > > Key: ISPN-11390 > URL: https://issues.redhat.com/browse/ISPN-11390 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management, Server > Affects Versions: 10.1.3.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > AbstractProtocolServer's worker thread pool and the protocol are such examples. They expose managed attributes but those cannot be currently exported as microprofile metrics due to fact these are not registered in the component registry. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11403) RestMetricsResource fails due to NettyTransportConnectionStats.getNumberOfGlobalConnections metrics not working with jmx disabled

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11403?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11403: ------------------------------------------ Sprint: DataGrid Sprint #40, DataGrid Sprint #41 (was: DataGrid Sprint #40) > RestMetricsResource fails due to NettyTransportConnectionStats.getNumberOfGlobalConnections metrics not working with jmx disabled > --------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-11403 > URL: https://issues.redhat.com/browse/ISPN-11403 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 11.0.0.Alpha1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > NettyTransportConnectionStats depending on jmx being enabled is very very very very wrong. > Today's fix will just allow mp metrics export to work, and these stats be 0 if jmx is not enabled. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11430) Align microprofile metrics and config artifact versions with latest Wildfly

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11430?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11430: ------------------------------------------ Sprint: DataGrid Sprint #40, DataGrid Sprint #41 (was: DataGrid Sprint #40) > Align microprofile metrics and config artifact versions with latest Wildfly > --------------------------------------------------------------------------- > > Key: ISPN-11430 > URL: https://issues.redhat.com/browse/ISPN-11430 > Project: Infinispan > Issue Type: Task > Components: JMX, reporting and management > Affects Versions: 11.0.0.Alpha2 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Dev03 > > > Need to use the same versions used by Wildlfy latest for smooth integration: > microprofile-config-api: 1.4 > microprofile-metrics-api: 2.3 > smallrye-config: 1.6.2 > smallrye-metrics: 2.4.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2020