March 2020 - infinispan-issues - Jboss List Archives

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

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11397?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11397: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.1.4.Final 11.0.0.Dev03 Resolution: Done > 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 > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > 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-11444) Server Driver Support for JUnit5

by Katia Aresti (Jira)

Katia Aresti created ISPN-11444: ----------------------------------- Summary: Server Driver Support for JUnit5 Key: ISPN-11444 URL: https://issues.redhat.com/browse/ISPN-11444 Project: Infinispan Issue Type: Task Components: Test Suite Affects Versions: 10.1.3.Final Reporter: Katia Aresti Assignee: Katia Aresti -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11443) PersistenceManagerImpl checks should use NonBlockingThread interface to check

by Will Burns (Jira)

Will Burns created ISPN-11443: --------------------------------- Summary: PersistenceManagerImpl checks should use NonBlockingThread interface to check Key: ISPN-11443 URL: https://issues.redhat.com/browse/ISPN-11443 Project: Infinispan Issue Type: Sub-task Reporter: Will Burns We added a NonBlockingThread interface that a non blocking thread implements in Infinispan. We should use this for PersistenceManagerImpl checks instead of the brittle thread name, which is already broken. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11126) Health check fails when authz is enabled and cache is not yet started

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11126?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11126: ----------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8017, https://github.com/infinispan/infinispan/pull/8019 (was: https://github.com/infinispan/infinispan/pull/8017) > Health check fails when authz is enabled and cache is not yet started > --------------------------------------------------------------------- > > Key: ISPN-11126 > URL: https://issues.redhat.com/browse/ISPN-11126 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management, REST > Affects Versions: 10.1.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > When using predefined caches on a container with authorization, and the caches have not been started, the health handler for the cachemanager resource fails with an authorization error. > The call should be wrapped in a SecurityAction. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11440) Allow use of config sub-elements in XIncluded fragments

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11440?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11440: ----------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8016, https://github.com/infinispan/infinispan/pull/8018 (was: https://github.com/infinispan/infinispan/pull/8016) > Allow use of config sub-elements in XIncluded fragments > ------------------------------------------------------- > > Key: ISPN-11440 > URL: https://issues.redhat.com/browse/ISPN-11440 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 11.0.0.Alpha2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > The infinispan-config XSD only allows the {{infinispan}} element as a top-level element. However, when using XInclude, it would be useful to be able to have other kinds of top-level elements: > jgroups > threads > cache-container > transport > security > *-cache-* -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11440) Allow use of config sub-elements in XIncluded fragments

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11440?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11440: ----------------------------------- Fix Version/s: 10.1.4.Final > Allow use of config sub-elements in XIncluded fragments > ------------------------------------------------------- > > Key: ISPN-11440 > URL: https://issues.redhat.com/browse/ISPN-11440 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 11.0.0.Alpha2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > The infinispan-config XSD only allows the {{infinispan}} element as a top-level element. However, when using XInclude, it would be useful to be able to have other kinds of top-level elements: > jgroups > threads > cache-container > transport > security > *-cache-* -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11442) Set 'hot-rod' migratior as the default in the Rolling Upgrade Manager

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-11442: ---------------------------------------- Summary: Set 'hot-rod' migratior as the default in the Rolling Upgrade Manager Key: ISPN-11442 URL: https://issues.redhat.com/browse/ISPN-11442 Project: Infinispan Issue Type: Enhancement Reporter: Gustavo Fernandes -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11441) Add blockhound support to hotrod server

by Will Burns (Jira)

Will Burns created ISPN-11441: --------------------------------- Summary: Add blockhound support to hotrod server Key: ISPN-11441 URL: https://issues.redhat.com/browse/ISPN-11441 Project: Infinispan Issue Type: Sub-task Components: Server Reporter: Will Burns Fix For: 11.0.0.Dev03 BlockHound is now in core pretty well and all the core thread pools have been merged together into 2 specific ones. We need to now add block hound support for hotrod server, which will allow us to consolidate the hotrod worker thread pools with these thread pools as well. The latter will be done in a separate JIRA. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11385) Convert Remote Command Executor to Non blocking/blocking thread executor

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11385?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11385: ------------------------------ Status: Open (was: New) > Convert Remote Command Executor to Non blocking/blocking thread executor > ------------------------------------------------------------------------ > > Key: ISPN-11385 > URL: https://issues.redhat.com/browse/ISPN-11385 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Dev03 > > > The remote command executor needs to be updated to use non blocking thread pool instead. If a place cannot be converted, the blocking thread pool can be used for now. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11385) Convert Remote Command Executor to Non blocking/blocking thread executor

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11385?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11385: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7997 > Convert Remote Command Executor to Non blocking/blocking thread executor > ------------------------------------------------------------------------ > > Key: ISPN-11385 > URL: https://issues.redhat.com/browse/ISPN-11385 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Dev03 > > > The remote command executor needs to be updated to use non blocking thread pool instead. If a place cannot be converted, the blocking thread pool can be used for now. -- 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