May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1162) Improve output of IPI and UPI provisioning jobs when waiting for operators

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1162?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1162. ---------------------------------- Resolution: Done > Improve output of IPI and UPI provisioning jobs when waiting for operators > -------------------------------------------------------------------------- > > Key: SWSQE-1162 > URL: https://issues.redhat.com/browse/SWSQE-1162 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > The jobs are sometimes stuck on waiting for operators and the output is not very clear, we need to improve that. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1138) NTP not configured alert in OCP 4.5 cluster

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1138?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1138. ---------------------------------- Resolution: Done > NTP not configured alert in OCP 4.5 cluster > ------------------------------------------- > > Key: SWSQE-1138 > URL: https://issues.redhat.com/browse/SWSQE-1138 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > There is a 'Clock on fbr-45-269d2-worker-6qnc7 is not synchronising. Ensure NTP is configured on this host.' alert on OCP 4.5 cluster. We need to fix it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13521) Upgrade Infinispan to 11.0.x

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13521: ----------------------------------- Summary: Upgrade Infinispan to 11.0.x Key: WFLY-13521 URL: https://issues.redhat.com/browse/WFLY-13521 Project: WildFly Issue Type: Component Upgrade Components: Clustering Affects Versions: 20.0.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro https://issues.redhat.com/projects/ISPN/versions/12342851 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1138) NTP not configured alert in OCP 4.5 cluster

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1138?page=com.atlassian.jira.plugi... ] Filip Brychta updated SWSQE-1138: --------------------------------- Summary: NTP not configured alert in OCP 4.5 cluster (was: NPT not configured alert in OCP 4.5 cluster) > NTP not configured alert in OCP 4.5 cluster > ------------------------------------------- > > Key: SWSQE-1138 > URL: https://issues.redhat.com/browse/SWSQE-1138 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > There is a 'Clock on fbr-45-269d2-worker-6qnc7 is not synchronising. Ensure NTP is configured on this host.' alert on OCP 4.5 cluster. We need to fix it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AG-143) Add s flush mode to forcefully remove leaked connections

by Luis Barreiro (Jira)

Luis Barreiro created AG-143: -------------------------------- Summary: Add s flush mode to forcefully remove leaked connections Key: AG-143 URL: https://issues.redhat.com/browse/AG-143 Project: Agroal Issue Type: Bug Components: api, pool Affects Versions: 1.8 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 1.9 When there is a notification of a leaking connection there is no way to remove that connection from the pool. In the event of uncommon connection leaks, these will accumulate over time, eventually blocking the pool. Using the existing mechanism for flush operations, add a new mode to allow the removal of these connections. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13507) Upgrade generic JMS RA to 2.0.6.Final

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13507?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on WFLY-13507: ------------------------------------------ This brings in : * Generic JMS RA leaks memory when using JMS 2.0 API with TIBCO EMS * Support Apache QPID JNDI paramaters * Setting of client id to before session is created https://github.com/jms-ra/generic-jms-ra/commit/0740417de103055732a640bc6... > Upgrade generic JMS RA to 2.0.6.Final > ------------------------------------- > > Key: WFLY-13507 > URL: https://issues.redhat.com/browse/WFLY-13507 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Affects Versions: 20.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > Upgrade the component -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13519) Infinispan module attribute needs to support multiple values

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13519?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13519: -------------------------------- Description: The cache-container and remote-cache-container resources in the Infinispan subsystem have a module attribute that is used to dynamically load externalizers used to configure marshalling for capabilities associated with these resources. Additionally, this attribute is also used to load Infinispan modules (e.g query, multimap, hibernate, etc.). Several users have had issues with configuring the marshalling of a custom cache because the module to which their cache container is associated does not know about their module. Users wanting to a specific Infinispan module has a similar issue. Currently, the only way to load marshalling configuration from multiple modules is through the use of module dependencies (using services="import"). This causes lots of unnatural service dependencies, which complicates the ability to build fine grained galleon layers. In order to support the use of multiple modules for a given cache-container, and also to support marshalling for multiple modules, we need to allow these resources to be associated with a list of modules, instead of a single module. Thus, the "module" will need to be replaced by "modules", where the former becomes an alias for the latter, with some translation logic to convert multiple values to a single value. was: The channel resource in the JGroups subsystem and cache-container and remote-cache-container resources in the Infinispan subsystem have a module attribute that is used to dynamically load externalizers used to configure marshalling for capabilities associated with these resources. In the case of Infinispan, this attribute is also used to load Infinispan modules (e.g query, multimap, hibernate, etc.). Several users have had issues with configuring the marshalling of a custom cache because the module to which their cache container is associated does not know about their module. Currently, the only way to load marshalling configuration from multiple modules is through the use of module dependencies (using services="import"). This causes lots of unnatural service dependencies, which complicates the ability to build fine grained galleon layers. In order to support the use of multiple modules for a given cache-container, and also to support marshalling for multiple modules, we need to allow these resources to be associated with a list of modules, instead of a single module. Thus, the "module" will need to be replaced by "modules", where the former becomes an alias for the latter, with some translation logic to convert multiple values to a single value. > Infinispan module attribute needs to support multiple values > ------------------------------------------------------------ > > Key: WFLY-13519 > URL: https://issues.redhat.com/browse/WFLY-13519 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > The cache-container and remote-cache-container resources in the Infinispan subsystem have a module attribute that is used to dynamically load externalizers used to configure marshalling for capabilities associated with these resources. > Additionally, this attribute is also used to load Infinispan modules (e.g query, multimap, hibernate, etc.). > Several users have had issues with configuring the marshalling of a custom cache because the module to which their cache container is associated does not know about their module. Users wanting to a specific Infinispan module has a similar issue. > Currently, the only way to load marshalling configuration from multiple modules is through the use of module dependencies (using services="import"). This causes lots of unnatural service dependencies, which complicates the ability to build fine grained galleon layers. > In order to support the use of multiple modules for a given cache-container, and also to support marshalling for multiple modules, we need to allow these resources to be associated with a list of modules, instead of a single module. > Thus, the "module" will need to be replaced by "modules", where the former becomes an alias for the latter, with some translation logic to convert multiple values to a single value. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13519) Infinispan module attribute needs to support multiple values

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13519?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13519: -------------------------------- Summary: Infinispan module attribute needs to support multiple values (was: JGroups/Infinispan module attribute needs to support multiple values) > Infinispan module attribute needs to support multiple values > ------------------------------------------------------------ > > Key: WFLY-13519 > URL: https://issues.redhat.com/browse/WFLY-13519 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > The channel resource in the JGroups subsystem and cache-container and remote-cache-container resources in the Infinispan subsystem have a module attribute that is used to dynamically load externalizers used to configure marshalling for capabilities associated with these resources. > In the case of Infinispan, this attribute is also used to load Infinispan modules (e.g query, multimap, hibernate, etc.). > Several users have had issues with configuring the marshalling of a custom cache because the module to which their cache container is associated does not know about their module. > Currently, the only way to load marshalling configuration from multiple modules is through the use of module dependencies (using services="import"). This causes lots of unnatural service dependencies, which complicates the ability to build fine grained galleon layers. > In order to support the use of multiple modules for a given cache-container, and also to support marshalling for multiple modules, we need to allow these resources to be associated with a list of modules, instead of a single module. > Thus, the "module" will need to be replaced by "modules", where the former becomes an alias for the latter, with some translation logic to convert multiple values to a single value. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (LOGMGR-273) Javadoc error on OpenJDK11

by James Perkins (Jira)

[ https://issues.redhat.com/browse/LOGMGR-273?page=com.atlassian.jira.plugi... ] James Perkins updated LOGMGR-273: --------------------------------- Security: (was: Red Hat Internal) > Javadoc error on OpenJDK11 > -------------------------- > > Key: LOGMGR-273 > URL: https://issues.redhat.com/browse/LOGMGR-273 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: Ettore Tognoli > Assignee: Ettore Tognoli > Priority: Minor > Fix For: 2.1.16.Final, 2.2.0.Final, 2.3.0.Beta1, 3.0.0.Final > > > I'm getting this error when I run mvn javadoc:javadoc on branch master and 2.1.15.Final tag with OpenJDK11 > {noformat} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:javadoc (default-cli) on project jboss-logmanager: An error has occurred in Javadoc report generation: > [ERROR] Exit code: 1 - javadoc: error - The code being documented uses modules but the packages defined in https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module. > [ERROR] /home/development/eap-7.1/repos/jboss-logmanager/src/main/java/org/jboss/logmanager/handlers/DelayedHandler.java:177: warning - invalid usage of tag {@link super#isCallerCalculationRequired() > [ERROR] /home/development/eap-7.1/repos/jboss-logmanager/src/main/java/org/jboss/logmanager/handlers/SyslogHandler.java:1016: warning - invalid usage of tag {@link > [ERROR] #setServerAddress(java.net.InetAddress), > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1440) FlexibleIdentityAssociation should runAs the known SecurityIdentity before associating itself.

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1440?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELY-1440: ---------------------------------- Fix Version/s: 1.12.1.CR1 (was: 1.12.0.CR4) > FlexibleIdentityAssociation should runAs the known SecurityIdentity before associating itself. > ---------------------------------------------------------------------------------------------- > > Key: ELY-1440 > URL: https://issues.redhat.com/browse/ELY-1440 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.12.1.CR1 > > > This API was introduced to cover the case where authentication happens late in a request, generally that is quite a rare event. > Even though the API may be popular it would likely happen once for a session and all future requests for that session the identity would be known in advance. > At the moment by not running as the existing identity we are loosing all automatic identity outflow opportunities as calls pass from the servlet container to the EJB container. -- 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

2008

2007

2006

jboss-jira May 2020