May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12146) Update Galleon universe and producers to 1.0.2.Final

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12146: --------------------------------------- Summary: Update Galleon universe and producers to 1.0.2.Final Key: WFLY-12146 URL: https://issues.jboss.org/browse/WFLY-12146 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry https://github.com/jboss/galleon-community-universe/compare/1.0.0.Final..... https://github.com/wildfly/wildfly-producers/compare/1.0.0.Final...1.0.2.... Using 1.0.2 instead of 1.0.1 was a minor screwup on my part. The pom didn't say 1.0.1.Final-SNAPSHOT so I thought 1.0.1 had been released and moved to 1.0.2. No harm. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4499) Update Galleon universe and producers to 1.0.2.Final

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4499?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-12146 to WFCORE-4499: ------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4499 (was: WFLY-12146) Component/s: Build System (was: Build System) > Update Galleon universe and producers to 1.0.2.Final > ---------------------------------------------------- > > Key: WFCORE-4499 > URL: https://issues.jboss.org/browse/WFCORE-4499 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > https://github.com/jboss/galleon-community-universe/compare/1.0.0.Final..... > https://github.com/wildfly/wildfly-producers/compare/1.0.0.Final...1.0.2.... > Using 1.0.2 instead of 1.0.1 was a minor screwup on my part. The pom didn't say 1.0.1.Final-SNAPSHOT so I thought 1.0.1 had been released and moved to 1.0.2. No harm. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12145) Update Galleon universe and producers to 1.0.2.Final

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12145: --------------------------------------- Summary: Update Galleon universe and producers to 1.0.2.Final Key: WFLY-12145 URL: https://issues.jboss.org/browse/WFLY-12145 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry https://github.com/jboss/galleon-community-universe/compare/1.0.0.Final..... https://github.com/wildfly/wildfly-producers/compare/1.0.0.Final...1.0.2.... Using 1.0.2 instead of 1.0.1 was a minor screwup on my part. The pom didn't say 1.0.1.Final-SNAPSHOT so I thought 1.0.1 had been released and moved to 1.0.2. No harm. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12108) Add a better timeout for the ConsoleAccessLogTestCase

by Ingo Weiss (Jira)

[ https://issues.jboss.org/browse/WFLY-12108?page=com.atlassian.jira.plugin... ] Ingo Weiss updated WFLY-12108: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/12309 (was: https://issues.jboss.org/browse/WFLY-12108) > Add a better timeout for the ConsoleAccessLogTestCase > ----------------------------------------------------- > > Key: WFLY-12108 > URL: https://issues.jboss.org/browse/WFLY-12108 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 17.0.0.Beta1 > > > The {{ConsoleAccessLogTestCase}} had a potential for race conditions only waiting 1 second for messages to be logged. The test has now failed twice and CI which indicates that is not a long enough timeout. The test should be updated with a better timeout routine. > Due to this the {{testPredicate()}} should be removed. It always ran the risk of getting a false positive due to the possible race between when the log is written vs when it is read. Since the timeout will be increased I see no reason to leave this test. If there are concerns with the predicate not working a test should be written in Undertow and likely already exists. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4491) Upgrade jboss-remoting to 5.0.11.Final

by Flavia Rainone (Jira)

[ https://issues.jboss.org/browse/WFCORE-4491?page=com.atlassian.jira.plugi... ] Flavia Rainone updated WFCORE-4491: ----------------------------------- Summary: Upgrade jboss-remoting to 5.0.11.Final (was: Upgrade jboss-remoting to 5.0.10.Final) > Upgrade jboss-remoting to 5.0.11.Final > -------------------------------------- > > Key: WFCORE-4491 > URL: https://issues.jboss.org/browse/WFCORE-4491 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Major > Labels: downstream_dependency > > Upgrade jboss-remoting to 5.0.10.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1824) Provide should cache instances of stateless factories it creates

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1824: ------------------------------------- Summary: Provide should cache instances of stateless factories it creates Key: ELY-1824 URL: https://issues.jboss.org/browse/ELY-1824 Project: WildFly Elytron Issue Type: Enhancement Components: API / SPI Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.9.2.CR1 Our security provider(s) return instances of various factories, these are largely stateless so the instances created should be cached so they can be returned again for future calls. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1823) Update SecurityProviderServerMechanismFactory to cache Provider interaction.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1823?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1823: ------------------------------------- Assignee: Darran Lofthouse > Update SecurityProviderServerMechanismFactory to cache Provider interaction. > ---------------------------------------------------------------------------- > > Key: ELY-1823 > URL: https://issues.jboss.org/browse/ELY-1823 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.9.2.CR1 > > > The SecurityProviderServerMechanismFactory regularly interacts with the Provider which can cause contention as calls to getServices() and getService(S,S) are synchronized. > Runtime updates are not actually expected so we should cache the interactions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1823) Update SecurityProviderServerMechanismFactory to cache Provider interaction.

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1823: ------------------------------------- Summary: Update SecurityProviderServerMechanismFactory to cache Provider interaction. Key: ELY-1823 URL: https://issues.jboss.org/browse/ELY-1823 Project: WildFly Elytron Issue Type: Enhancement Components: HTTP Reporter: Darran Lofthouse Fix For: 1.9.2.CR1 The SecurityProviderServerMechanismFactory regularly interacts with the Provider which can cause contention as calls to getServices() and getService(S,S) are synchronized. Runtime updates are not actually expected so we should cache the interactions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12144) Add support for configuring load-balancer with ranked routing

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12144?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12144: ---------------------------------- Description: Support none/single/ranked affinity strategies for both: * mod_cluster * regular proxy > Add support for configuring load-balancer with ranked routing > ------------------------------------------------------------- > > Key: WFLY-12144 > URL: https://issues.jboss.org/browse/WFLY-12144 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Support none/single/ranked affinity strategies for both: > * mod_cluster > * regular proxy -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12144) Add support for configuring load-balancer with ranked routing support

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12144?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12144: ---------------------------------- Summary: Add support for configuring load-balancer with ranked routing support (was: Add support for configuring LB with ranked routing support) > Add support for configuring load-balancer with ranked routing support > --------------------------------------------------------------------- > > Key: WFLY-12144 > URL: https://issues.jboss.org/browse/WFLY-12144 > Project: WildFly > Issue Type: Bug > Components: Clustering, Web (Undertow) > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 2019