[JBoss JIRA] (WFLY-7797) Configuratin for ejb strict-max-pool is confusing regarding derive-size and max-size
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-7797?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-7797:
----------------------------------------
One possible thing to do here is to have the handlers for resource add and for write-attribute for max-pool-size and derive-size all add a Stage.MODEL step to check for the resource model having the combo of max-pool-size is defined and derive-size=NONE and if found, just change the derive-size value to undefined.
Just dropping NONE as a legal value and removing it as a default value is a possibility as well, but we'd have to add a ParameterCorrector such that if the user passed NONE it would convert that to undefined before any validation occurred. The corrector is needed to preserve compatibility. The runtime handler logic would need to account for the fact that resolveModelAttribute may now return undefined.
The latter changes the management API but is probably better as it results in a more straightforward behavior. The former is kind of voodoo behavior where a user-provided setting is discarded.
> Configuratin for ejb strict-max-pool is confusing regarding derive-size and max-size
> ------------------------------------------------------------------------------------
>
> Key: WFLY-7797
> URL: https://issues.jboss.org/browse/WFLY-7797
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Reporter: Wolf-Dieter Fink
> Assignee: Brian Stansberry
> Priority: Minor
> Labels: ejb, management
>
> The strict-max pool can be set for automatical configuration with
> derive-size (none|from-worker-pools|from-cpu-count) or set the number of pool-entries by use max-pool-size.
> If derive-size is set the use of max-pool-size will throw an error during start that the use is exclusive.
> But as derive-size="none" mean the same as if the attribute is not set it will be confusing.
> - not clear what the pool size is then (I checked it is the default max-pool size =20)
> - confusing if it is reset by cli, attr derive-size need to be removed to use max-size
> So finally "none" is useless and should be removed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFCORE-2122) [Deployment overlay] Missing possiblity do print overlay mapping
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2122?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise updated WFCORE-2122:
-----------------------------------------
Labels: UserExperience (was: )
> [Deployment overlay] Missing possiblity do print overlay mapping
> ----------------------------------------------------------------
>
> Key: WFCORE-2122
> URL: https://issues.jboss.org/browse/WFCORE-2122
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI
> Reporter: Jean-Francois Denise
> Assignee: Jean-Francois Denise
> Labels: UserExperience
>
> Problem
> I don't see any possibility to print mapping specified by argument --content in existing overlays.
> Proposed solution
> Provide such functionality. I see 2 levels of granularity
> 1. Display mapping in overlay only
> 2. Display real mapping in specific deployment (not all deployment has to have all files defined by overlay)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFCORE-2122) [Deployment overlay] Missing possiblity do print overlay mapping
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-2122:
--------------------------------------------
Summary: [Deployment overlay] Missing possiblity do print overlay mapping
Key: WFCORE-2122
URL: https://issues.jboss.org/browse/WFCORE-2122
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
Problem
I don't see any possibility to print mapping specified by argument --content in existing overlays.
Proposed solution
Provide such functionality. I see 2 levels of granularity
1. Display mapping in overlay only
2. Display real mapping in specific deployment (not all deployment has to have all files defined by overlay)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFLY-7800) Export jackson-jaxrs-json-provider dependency in resteasy-jackson2-provider module
by Katerina Novotna (JIRA)
[ https://issues.jboss.org/browse/WFLY-7800?page=com.atlassian.jira.plugin.... ]
Katerina Novotna moved JBEAP-7886 to WFLY-7800:
-----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7800 (was: JBEAP-7886)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: REST
(was: REST)
Affects Version/s: (was: 7.1.0.DR9)
> Export jackson-jaxrs-json-provider dependency in resteasy-jackson2-provider module
> ----------------------------------------------------------------------------------
>
> Key: WFLY-7800
> URL: https://issues.jboss.org/browse/WFLY-7800
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Reporter: Katerina Novotna
>
> RFE EAP7-608, Introduces Jackson 2 JsonFilter annotation support for Resteasy.
> This cannot be used without explicitly defined dependency for jackson-jaxrs-json-provider in the deployment.
> *Actual behaviour:*
> Currently a deployment with the resource using JsonFilter annotation must have com.fasterxml.jackson.jaxrs.jackson-jaxrs-json-provider dependency specified in the MANIFEST file in order to correctly deploy.
> See example - https://github.com/resteasy/Resteasy/blob/master/testsuite/integration-te...
> *Expected behaviour*:
> There is no need to add explicit dependency into the deployment.
> Dependencies in the modules/system/layers/base/org/jboss/resteasy/resteasy-jackson2-provider/main/module.xml shall be updated to export jackson-jaxrs-json-provider.
> {code:java}
> <dependencies>
> <module name="com.fasterxml.jackson.core.jackson-annotations" export="true"/>
> <module name="com.fasterxml.jackson.core.jackson-core" export="true"/>
> <module name="com.fasterxml.jackson.core.jackson-databind" export="true"/>
> <module name="com.fasterxml.jackson.jaxrs.jackson-jaxrs-json-provider" export="true"/>
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFLY-7686) Inconsistent attribute desription of security domain
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFLY-7686?page=com.atlassian.jira.plugin.... ]
Jean-Francois Denise updated WFLY-7686:
---------------------------------------
Component/s: Domain Management
(was: CLI)
> Inconsistent attribute desription of security domain
> ----------------------------------------------------
>
> Key: WFLY-7686
> URL: https://issues.jboss.org/browse/WFLY-7686
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 10.1.0.Final
> Reporter: Juraj Duráni
> Assignee: Jason Greene
> Priority: Minor
>
> Some attributes have inconsistent description (obtained using 'read-resource-description' operation):
> - Missing module attribute:
> {code:plain|title=Missing module attribute}
> [standalone@localhost:9990 /] /subsystem=security/security-domain=other/mapping=classic:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "Mapping configuration. Configures a list of mapping modules to be used for principal, role, attribute and credential mapping.",
> "deprecated" => {
> "since" => "1.3.0",
> "reason" => "The Security subsystem is deprecated and may be removed, significantly revised, or limited to managed domain legacy server use in future versions."
> },
> "access-constraints" => {
> "sensitive" => {"security-domain" => {"type" => "core"}},
> "application" => {"security-domain" => {"type" => "security"}}
> },
> "attributes" => {"mapping-modules" => {
> "type" => LIST,
> "description" => "List of modules that map principal, role, and credential information",
> "expressions-allowed" => false,
> "nillable" => true,
> "deprecated" => {
> "since" => "1.2.0",
> "reason" => "Use of this attribute is deprecated, use resource"
> },
> "value-type" => {
> "code" => {
> "description" => "Class name of the module to be instantiated.",
> "type" => STRING,
> "nillable" => false,
> "min-length" => 1
> },
> "type" => {
> "description" => "Type of mapping this module performs. Allowed values are principal, role, attribute or credential..",
> "type" => STRING,
> "nillable" => false
> },
> "module-options" => {
> "description" => "List of module options containing a name/value pair.",
> "type" => OBJECT,
> "value-type" => STRING,
> "nillable" => true
> }
> },
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> }},
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {"mapping-module" => {
> "description" => "List of modules that map principal, role, and credential information",
> "model-description" => undefined
> }}
> }
> }
> {code}
> - Module description in policy-module refers to "login module"
> {code:plain|title=Inaccurate description}
> [standalone@localhost:9990 /] /subsystem=security/security-domain=other/authorization=classic/policy-module=a:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "List of authentication modules",
> "access-constraints" => {
> "sensitive" => {"security-domain" => {"type" => "core"}},
> "application" => {"security-domain" => {"type" => "security"}}
> },
> "attributes" => {
> "code" => {
> "type" => STRING,
> "description" => "Class name of the module to be instantiated.",
> "expressions-allowed" => false,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> "flag" => {
> "type" => STRING,
> "description" => "The flag controls how the module participates in the overall procedure. Allowed values are requisite, required, sufficient or optional.",
> "expressions-allowed" => true,
> "nillable" => false,
> "allowed" => [
> "required",
> "requisite",
> "sufficient",
> "optional"
> ],
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> "module" => {
> "type" => STRING,
> "description" => "Name of JBoss Module where the login module is located.",
> "expressions-allowed" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> "module-options" => {
> "type" => OBJECT,
> "description" => "List of module options containing a name/value pair.",
> "expressions-allowed" => true,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> }
> },
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {}
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFLY-7686) Inconsistent attribute desription of security domain
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFLY-7686?page=com.atlassian.jira.plugin.... ]
Jean-Francois Denise reassigned WFLY-7686:
------------------------------------------
Assignee: Brian Stansberry (was: Jason Greene)
> Inconsistent attribute desription of security domain
> ----------------------------------------------------
>
> Key: WFLY-7686
> URL: https://issues.jboss.org/browse/WFLY-7686
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 10.1.0.Final
> Reporter: Juraj Duráni
> Assignee: Brian Stansberry
> Priority: Minor
>
> Some attributes have inconsistent description (obtained using 'read-resource-description' operation):
> - Missing module attribute:
> {code:plain|title=Missing module attribute}
> [standalone@localhost:9990 /] /subsystem=security/security-domain=other/mapping=classic:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "Mapping configuration. Configures a list of mapping modules to be used for principal, role, attribute and credential mapping.",
> "deprecated" => {
> "since" => "1.3.0",
> "reason" => "The Security subsystem is deprecated and may be removed, significantly revised, or limited to managed domain legacy server use in future versions."
> },
> "access-constraints" => {
> "sensitive" => {"security-domain" => {"type" => "core"}},
> "application" => {"security-domain" => {"type" => "security"}}
> },
> "attributes" => {"mapping-modules" => {
> "type" => LIST,
> "description" => "List of modules that map principal, role, and credential information",
> "expressions-allowed" => false,
> "nillable" => true,
> "deprecated" => {
> "since" => "1.2.0",
> "reason" => "Use of this attribute is deprecated, use resource"
> },
> "value-type" => {
> "code" => {
> "description" => "Class name of the module to be instantiated.",
> "type" => STRING,
> "nillable" => false,
> "min-length" => 1
> },
> "type" => {
> "description" => "Type of mapping this module performs. Allowed values are principal, role, attribute or credential..",
> "type" => STRING,
> "nillable" => false
> },
> "module-options" => {
> "description" => "List of module options containing a name/value pair.",
> "type" => OBJECT,
> "value-type" => STRING,
> "nillable" => true
> }
> },
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> }},
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {"mapping-module" => {
> "description" => "List of modules that map principal, role, and credential information",
> "model-description" => undefined
> }}
> }
> }
> {code}
> - Module description in policy-module refers to "login module"
> {code:plain|title=Inaccurate description}
> [standalone@localhost:9990 /] /subsystem=security/security-domain=other/authorization=classic/policy-module=a:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "List of authentication modules",
> "access-constraints" => {
> "sensitive" => {"security-domain" => {"type" => "core"}},
> "application" => {"security-domain" => {"type" => "security"}}
> },
> "attributes" => {
> "code" => {
> "type" => STRING,
> "description" => "Class name of the module to be instantiated.",
> "expressions-allowed" => false,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> "flag" => {
> "type" => STRING,
> "description" => "The flag controls how the module participates in the overall procedure. Allowed values are requisite, required, sufficient or optional.",
> "expressions-allowed" => true,
> "nillable" => false,
> "allowed" => [
> "required",
> "requisite",
> "sufficient",
> "optional"
> ],
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> "module" => {
> "type" => STRING,
> "description" => "Name of JBoss Module where the login module is located.",
> "expressions-allowed" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> "module-options" => {
> "type" => OBJECT,
> "description" => "List of module options containing a name/value pair.",
> "expressions-allowed" => true,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> }
> },
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {}
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFLY-7794) Adding information how to quit batch mode when a batch fails
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFLY-7794?page=com.atlassian.jira.plugin.... ]
Jean-Francois Denise commented on WFLY-7794:
--------------------------------------------
Hi, that is an interesting feedback. We plan to merge all batch commands under a single command named batch.
So, in your case to discover the batch discard or holdback, you would simply do what you did when creating a new batch: batch <TAB>, and it will list all batch related actions:
- discard, holdback, list, ....
Don't you think that it would have helped you?
Thanks.
JF
> Adding information how to quit batch mode when a batch fails
> ------------------------------------------------------------
>
> Key: WFLY-7794
> URL: https://issues.jboss.org/browse/WFLY-7794
> Project: WildFly
> Issue Type: Enhancement
> Components: CLI
> Affects Versions: 10.1.0.Final
> Reporter: Ondra Chaloupka
> Assignee: Jean-Francois Denise
> Priority: Minor
>
> When running an interactive batch in CLI and there is some fail in steps it would be nice to get information how to exit the batch mode. The proper command is {{discard-batch}} (as I understood from documentation at https://developer.jboss.org/wiki/CLIBatchMode) but it's a bit uneasy to find that command.
> Currently when some error occurs I can see message like
> {quote}
> [standalone@localhost:9990 / #] run-batch
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error):
> WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:
> Step: step-2
> Operation: /subsystem=transactions:write-attribute(name=process-id-uuid, value=false)
> Failure: WFLYCTL0105: process-id-uuid is invalid in combination with process-id-socket-binding
> {quote}
> Could there be added a note that for quiting interactive batch mode use {{discard-batch}} command?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFLY-7799) Failover targets should be chosen deterministically
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-7799?page=com.atlassian.jira.plugin.... ]
Radoslav Husar moved JBEAP-7884 to WFLY-7799:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-7799 (was: JBEAP-7884)
Issue Type: Feature Request (was: Bug)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Web (Undertow)
(was: Web (Undertow))
Affects Version/s: (was: 7.1.0.DR8)
Fix Version/s: (was: 7.1.0.GA)
> Failover targets should be chosen deterministically
> ---------------------------------------------------
>
> Key: WFLY-7799
> URL: https://issues.jboss.org/browse/WFLY-7799
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> See UNDERTOW-898.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months