June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1187) Workloads list test - Add back labels comparison

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1187?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1187: ---------------------------------- Sprint: Kiali Sprint #41 > Workloads list test - Add back labels comparison > ------------------------------------------------ > > Key: SWSQE-1187 > URL: https://issues.redhat.com/browse/SWSQE-1187 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > > Label comparison between OC and UI. > In Workloads lists test. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1185) OC API - workload_list - apply Job/Pod filters

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1185?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1185. ----------------------------------- Resolution: Done > OC API - workload_list - apply Job/Pod filters > ---------------------------------------------- > > Key: SWSQE-1185 > URL: https://issues.redhat.com/browse/SWSQE-1185 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > openshift_api.workload_list > # TODO apply Job filters > # TODO apply Pod filters > > Activate in workload lists test: > # TODO when workloads are filtered put == here -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5021) Upgrade jboss-logmanager to 2.1.17.Final

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-5021?page=com.atlassian.jira.plug... ] James Perkins updated WFCORE-5021: ---------------------------------- Issue Type: Component Upgrade (was: Bug) > Upgrade jboss-logmanager to 2.1.17.Final > ---------------------------------------- > > Key: WFCORE-5021 > URL: https://issues.redhat.com/browse/WFCORE-5021 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Upgrade the jboss-logmanager from 2.1.16.Final to 2.1.17.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5021) Upgrade jboss-logmanager to 2.1.17.Final

by James Perkins (Jira)

James Perkins created WFCORE-5021: ------------------------------------- Summary: Upgrade jboss-logmanager to 2.1.17.Final Key: WFCORE-5021 URL: https://issues.redhat.com/browse/WFCORE-5021 Project: WildFly Core Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Upgrade the jboss-logmanager from 2.1.16.Final to 2.1.17.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-279) The configuration API removes handler references before the handler is removed from a logger/handler

by James Perkins (Jira)

[ https://issues.redhat.com/browse/LOGMGR-279?page=com.atlassian.jira.plugi... ] James Perkins updated LOGMGR-279: --------------------------------- Fix Version/s: 2.2.0.Final 2.1.17.Final 2.3.0.Beta1 > The configuration API removes handler references before the handler is removed from a logger/handler > ---------------------------------------------------------------------------------------------------- > > Key: LOGMGR-279 > URL: https://issues.redhat.com/browse/LOGMGR-279 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Fix For: 2.2.0.Final, 2.1.17.Final, 2.3.0.Beta1 > > > Using the configuration API to remove a handler from a logger and a handler in the same transaction does not the handler from a logger or a different handler. The handler reference is removed and closed before the attempt to remove the handler from the logger or handler. This ends up leaving the handler on the logger or on the handler so messages are still published to the handler. > Note too that this could also be an issue with the post configuration actions as they require the handler reference as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-279) The configuration API removes handler references before the handler is removed from a logger/handler

by James Perkins (Jira)

James Perkins created LOGMGR-279: ------------------------------------ Summary: The configuration API removes handler references before the handler is removed from a logger/handler Key: LOGMGR-279 URL: https://issues.redhat.com/browse/LOGMGR-279 Project: JBoss Log Manager Issue Type: Bug Reporter: James Perkins Assignee: James Perkins Using the configuration API to remove a handler from a logger and a handler in the same transaction does not the handler from a logger or a different handler. The handler reference is removed and closed before the attempt to remove the handler from the logger or handler. This ends up leaving the handler on the logger or on the handler so messages are still published to the handler. Note too that this could also be an issue with the post configuration actions as they require the handler reference as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13590) JGroups subsystem logs "version is missing in the configuration file" warning on startup

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13590?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13590: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13368, https://github.com/wildfly/wildfly/pull/13384 (was: https://github.com/wildfly/wildfly/pull/13384) > JGroups subsystem logs "version is missing in the configuration file" warning on startup > ---------------------------------------------------------------------------------------- > > Key: WFLY-13590 > URL: https://issues.redhat.com/browse/WFLY-13590 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 21.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13590) JGroups subsystem logs "version is missing in the configuration file" warning on startup

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13590?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13590: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13384 (was: https://github.com/wildfly/wildfly/pull/13368) > JGroups subsystem logs "version is missing in the configuration file" warning on startup > ---------------------------------------------------------------------------------------- > > Key: WFLY-13590 > URL: https://issues.redhat.com/browse/WFLY-13590 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 21.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13616) Distributed session manager should trigger HttpSessionAttributeListener.attributeRemoved events on session destroy

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13616: ----------------------------------- Summary: Distributed session manager should trigger HttpSessionAttributeListener.attributeRemoved events on session destroy Key: WFLY-13616 URL: https://issues.redhat.com/browse/WFLY-13616 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 20.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Justification: * This is the behavior of the non-distributed session manager * This is the behavior of the servlet container reference implementation * JSF relies on these events being triggered on session destroy. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13615) JaccServices need to depend up Elytron JACC Service

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-13615: --------------------------------------- Summary: JaccServices need to depend up Elytron JACC Service Key: WFLY-13615 URL: https://issues.redhat.com/browse/WFLY-13615 Project: WildFly Issue Type: Bug Components: EE, EJB, Web (Undertow) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 21.0.0.Beta1 Three DeploymentUnitProcessors register a JaccService, if Elytron ihas registered a capability to indicate it is handling JACC a dependency should be added on the service installed by the Elytron subsystem. Presently it is a little racey as to if Elytron will have activated the JACC PolicyConfigurationFactory before the deployment makes use of it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

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 June 2020