October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3383) Ensure all Elytron subsystem resources that depend on the core services also record a capability dependency.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3383?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-8250 to WFCORE-3383: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-3383 (was: WFLY-8250) Component/s: Security (was: Security) Fix Version/s: (was: 12.0.0.Alpha1) > Ensure all Elytron subsystem resources that depend on the core services also record a capability dependency. > ------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-3383 > URL: https://issues.jboss.org/browse/WFCORE-3383 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > > This builds on https://issues.jboss.org/browse/WFCORE-1106 so we can skip runtime steps when the dependent services are not available. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3382) Further Enhance Elytron Permission Configuration

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3382: ---------------------------------------- Summary: Further Enhance Elytron Permission Configuration Key: WFCORE-3382 URL: https://issues.jboss.org/browse/WFCORE-3382 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Darran Lofthouse Fix For: 4.0.0.Alpha1 This has currently been simplified to a single resource for the out of the box configuration, however this brings issues as now permissions are duplicated so modifications need to be replicated instead of to a single location. Finding a way for the default required permissions to be defined in one location could help eliminate the duplication. We could also consider going one step further and subsystems register the default permissions that should be granted. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9484) Upgrade netty-xnio-transport to 0.1.3.Final

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-9484: --------------------------------- Summary: Upgrade netty-xnio-transport to 0.1.3.Final Key: WFLY-9484 URL: https://issues.jboss.org/browse/WFLY-9484 Project: WildFly Issue Type: Component Upgrade Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 12.0.0.Alpha1 netty-xnio-transport must be updated to the version of XNIO and netty used in WildFly with Artemis 2.x releases -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9483) Upgrade Netty to 4.1.16.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9483?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-9483: ------------------------------ Summary: Upgrade Netty to 4.1.16.Final (was: Upgrade Netty from 4.1.9.Final to 4.1.16.Final) > Upgrade Netty to 4.1.16.Final > ----------------------------- > > Key: WFLY-9483 > URL: https://issues.jboss.org/browse/WFLY-9483 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 12.0.0.Alpha1 > > > https://github.com/netty/netty/compare/netty-4.1.9.Final...netty-4.1.16.F... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9483) Upgrade Netty from 4.1.9.Final to 4.1.16.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9483?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-9483: ------------------------------ Fix Version/s: 12.0.0.Alpha1 > Upgrade Netty from 4.1.9.Final to 4.1.16.Final > ---------------------------------------------- > > Key: WFLY-9483 > URL: https://issues.jboss.org/browse/WFLY-9483 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 12.0.0.Alpha1 > > > https://github.com/netty/netty/compare/netty-4.1.9.Final...netty-4.1.16.F... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9483) Upgrade Netty from 4.1.9.Final to 4.1.16.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9483?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-13616 to WFLY-9483: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9483 (was: JBEAP-13616) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: A-MQ7) > Upgrade Netty from 4.1.9.Final to 4.1.16.Final > ---------------------------------------------- > > Key: WFLY-9483 > URL: https://issues.jboss.org/browse/WFLY-9483 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 12.0.0.Alpha1 > > > https://github.com/netty/netty/compare/netty-4.1.9.Final...netty-4.1.16.F... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9483) Upgrade Netty from 4.1.9.Final to 4.1.16.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9483?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-9483: ------------------------------ Priority: Major (was: Blocker) > Upgrade Netty from 4.1.9.Final to 4.1.16.Final > ---------------------------------------------- > > Key: WFLY-9483 > URL: https://issues.jboss.org/browse/WFLY-9483 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 12.0.0.Alpha1 > > > https://github.com/netty/netty/compare/netty-4.1.9.Final...netty-4.1.16.F... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9482) ejb remote client hangs on undertow default worker pool exhaustion

by Igor Vagulin (JIRA)

[ https://issues.jboss.org/browse/WFLY-9482?page=com.atlassian.jira.plugin.... ] Igor Vagulin commented on WFLY-9482: ------------------------------------ I am using default configuration bundled with wildfly. I believe it should not just lock up on load increase > the number of task threads must exceed the maximum number of allowed concurrent inbound requests I thought task-max-threads of io worker is only option to control maximum concurrent inbound requests > ejb remote client hangs on undertow default worker pool exhaustion > ------------------------------------------------------------------ > > Key: WFLY-9482 > URL: https://issues.jboss.org/browse/WFLY-9482 > Project: WildFly > Issue Type: Bug > Components: Remoting > Affects Versions: 10.1.0.Final > Reporter: Igor Vagulin > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9482) ejb remote client hangs on undertow default worker pool exhaustion

by Igor Vagulin (JIRA)

[ https://issues.jboss.org/browse/WFLY-9482?page=com.atlassian.jira.plugin.... ] Igor Vagulin edited comment on WFLY-9482 at 10/25/17 12:14 PM: --------------------------------------------------------------- I am using default configuration bundled with wildfly. I believe it should not just lock up on load increase > the number of task threads must exceed the maximum number of allowed concurrent inbound requests I thought task-max-threads of io worker is only option to control maximum concurrent inbound requests I am curently workaroun it on my installation creating separate io worker for remoting. but I am unable to use http upgrade with such configuration was (Author: ivagulin): I am using default configuration bundled with wildfly. I believe it should not just lock up on load increase > the number of task threads must exceed the maximum number of allowed concurrent inbound requests I thought task-max-threads of io worker is only option to control maximum concurrent inbound requests > ejb remote client hangs on undertow default worker pool exhaustion > ------------------------------------------------------------------ > > Key: WFLY-9482 > URL: https://issues.jboss.org/browse/WFLY-9482 > Project: WildFly > Issue Type: Bug > Components: Remoting > Affects Versions: 10.1.0.Final > Reporter: Igor Vagulin > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9482) ejb remote client hangs on undertow default worker pool exhaustion

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-9482?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-9482: ----------------------------------- This seems like an unavoidable consequence of having the client and server use the same task pool. In such a configuration, the number of task threads must _exceed_ the maximum number of allowed concurrent inbound requests (which in turn should be governed by configuration). The excess should be at least several threads. > ejb remote client hangs on undertow default worker pool exhaustion > ------------------------------------------------------------------ > > Key: WFLY-9482 > URL: https://issues.jboss.org/browse/WFLY-9482 > Project: WildFly > Issue Type: Bug > Components: Remoting > Affects Versions: 10.1.0.Final > Reporter: Igor Vagulin > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 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 October 2017