February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2282) Get rid of the clientRequestExecutor in AbstractModelControllerOperationHandlerFactoryService

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2282?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2282: ------------------------------------- Fix Version/s: 5.0.0.Alpha1 (was: 4.0.0.Beta2) > Get rid of the clientRequestExecutor in AbstractModelControllerOperationHandlerFactoryService > --------------------------------------------------------------------------------------------- > > Key: WFCORE-2282 > URL: https://issues.jboss.org/browse/WFCORE-2282 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 5.0.0.Alpha1 > > > AbstractModelControllerOperationHandlerFactoryService creates a thread pool for handling management requests, with the goal being to limit the number of concurrently executing requests to 4, with tasks for other requests being queued. > There are other ways to do this kind of limitation that do not involve a new thread pool. See Undertow's RequestLimitHandler and related RequestLimit class for the template. > This task is to implement the equivalent in org.jboss.as.controller.remote (not as public API) and then switch the execution to the ServerService Thread Pool (on a server) or the HostControllerService Thread Pool (on an HC). > It is *not* a request to move execution to the XNIO worker task thread. That should not be done without a very clear discussion. > Part of this task is to account for the thinking that went into a fix for WFCORE-1529. IOW moving work to ServerService Thread Pool / HostControllerService Thread Pool will likely affect the optimum core sizes of those pools. This AbstractModelControllerOperationHandlerFactoryService.clientRequestExecutor is what is referred to in the PR for WFCORE-1529 in its discussion of "management-handler-thread". -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3000) Allow turning the security manager on on a per jvm basis

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3000?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3000: ------------------------------------- Fix Version/s: (was: 4.0.0.Beta2) > Allow turning the security manager on on a per jvm basis > -------------------------------------------------------- > > Key: WFCORE-3000 > URL: https://issues.jboss.org/browse/WFCORE-3000 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Labels: domain-mode > > Turning on the security manager in a WildFly process is done by adding the -secmgr arg to org.jboss.modules.Main. But the jvm config settings in domain mode provide no mechanism for configuring args to Main; they only provide options for args to java. So there is no way to turn on the security manager for an individual jvm config (i.e. one or more servers) or if it is on for the HC there is no way to turn it off for a particular jvm config. > The jvm config needs an attribute for this; default is undefined which should be documented as meaning the setting is derived from the HC's settings (i.e. the way it is now.) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2336) Remove ModelController.createClient

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2336?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2336: ------------------------------------- Fix Version/s: 5.0.0.Alpha1 (was: 4.0.0.Beta2) > Remove ModelController.createClient > ----------------------------------- > > Key: WFCORE-2336 > URL: https://issues.jboss.org/browse/WFCORE-2336 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 5.0.0.Alpha1 > > > Follow up on WFCORE-1507 by removing ModelController.createClient and any use of it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2093) A 'start' operation only is available for a domain server resource when it is started

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2093?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2093: ------------------------------------- Fix Version/s: (was: 4.0.0.Beta2) > A 'start' operation only is available for a domain server resource when it is started > ------------------------------------------------------------------------------------- > > Key: WFCORE-2093 > URL: https://issues.jboss.org/browse/WFCORE-2093 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > Labels: domain-mode > > The server lifecycle ops are registered with the domain server resource by a call to ServerConfigResourceDefintion.registerServerLifecycleOperations. DomainModelControllerService registers that when the server registers with the HC. > This is odd in the case of 'start' as it means that op is only registered when the server is started. > Perhaps it should be registered with StoppedServerResource, although I haven't dug into what happens with that resource when the server is registered. If it is simply ignored that would be great. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-8) Openshift Automation With Cucumber - Presentation/Demo

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-8?page=com.atlassian.jira.plugin.sy... ] Matt Mahoney reassigned SWSQE-8: -------------------------------- Assignee: Peter Ruan (was: Michael Foley) > Openshift Automation With Cucumber - Presentation/Demo > ------------------------------------------------------ > > Key: SWSQE-8 > URL: https://issues.jboss.org/browse/SWSQE-8 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Peter Ruan > Priority: Minor > > Peter R: Present/demo Openshift automation testing with Cucuber. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-8) Openshift Automation With Cucumber - Presentation/Demo

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-8?page=com.atlassian.jira.plugin.sy... ] Matt Mahoney updated SWSQE-8: ----------------------------- Sprint: SWS QE Sprint 1 > Openshift Automation With Cucumber - Presentation/Demo > ------------------------------------------------------ > > Key: SWSQE-8 > URL: https://issues.jboss.org/browse/SWSQE-8 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Peter Ruan > Priority: Minor > > Peter R: Present/demo Openshift automation testing with Cucuber. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-8) Openshift Automation With Cucumber - Presentation/Demo

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-8: -------------------------------- Summary: Openshift Automation With Cucumber - Presentation/Demo Key: SWSQE-8 URL: https://issues.jboss.org/browse/SWSQE-8 Project: Swift Sunshine QE Issue Type: Task Reporter: Matt Mahoney Assignee: Michael Foley Priority: Minor Peter R: Present/demo Openshift automation testing with Cucuber. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9789) Upgrade RESTEasy to 3.5.0.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9789?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-9789: -------------------------------- Fix Version/s: 12.0.0.Beta1 (was: 12.0.0.Alpha1) > Upgrade RESTEasy to 3.5.0.Final > ------------------------------- > > Key: WFLY-9789 > URL: https://issues.jboss.org/browse/WFLY-9789 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 12.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9789) Upgrade RESTEasy to 3.5.0.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9789?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-9789: -------------------------------- Priority: Blocker (was: Major) > Upgrade RESTEasy to 3.5.0.Final > ------------------------------- > > Key: WFLY-9789 > URL: https://issues.jboss.org/browse/WFLY-9789 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Blocker > Fix For: 12.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9789) Upgrade RESTEasy to 3.5.0.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9789?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-9789: ------------------------------------- I'm leaving this open and making it a blocker for Beta1 as we will need a final release. > Upgrade RESTEasy to 3.5.0.Final > ------------------------------- > > Key: WFLY-9789 > URL: https://issues.jboss.org/browse/WFLY-9789 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Blocker > Fix For: 12.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 February 2018