[JBoss JIRA] (WFLY-7483) Credential store has configuration in "uri" attribute.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/WFLY-7483?page=com.atlassian.jira.plugin.... ]
Hynek Švábek updated WFLY-7483:
-------------------------------
Description:
Credential store has configuration in "uri" attribute. All parameters are in one string. It can be confusing and there is risk of typo (e.g. delimiter typo)
In my opinion the main intention for it is to have general solution for custom implementation.
*Current state*
{code}
/subsystem=elytron/credential-store=cs001:add(uri="cr-store://test/cs/keystore.jceks?store.password=pass123;create.storage=true")
{code}
*Suggestion for improvement:*
Better solution to achieve this could be use a map.
e.g. some like that:
{code}
/subsystem=elytron/credential-store=credStore:add(cs-map={store.password=pass123, create.storage=true, store.file=path/to/cred/file})
{code}
Now credential store name is in URI too, it can be get from resource name.
was:
Credential store has configuration in "uri" attribute. All parameters are in one string. It can be confusing and there is risk of typo (e.g. delimiter typo)
In my opinion the main intention for it is to have general solution for custom implementation.
*Suggestion for improvement:*
Better solution to achieve this could be use a map.
e.g. some like that:
{code}
/subsystem=elytron/credential-store=credStore:add(cs-map={store.password=pass123, create.storage=true, store.file=path/to/cred/file})
{code}
Now credential store name is in URI too, it can be get from resource name.
> Credential store has configuration in "uri" attribute.
> ------------------------------------------------------
>
> Key: WFLY-7483
> URL: https://issues.jboss.org/browse/WFLY-7483
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Peter Skopek
> Priority: Critical
>
> Credential store has configuration in "uri" attribute. All parameters are in one string. It can be confusing and there is risk of typo (e.g. delimiter typo)
> In my opinion the main intention for it is to have general solution for custom implementation.
> *Current state*
> {code}
> /subsystem=elytron/credential-store=cs001:add(uri="cr-store://test/cs/keystore.jceks?store.password=pass123;create.storage=true")
> {code}
> *Suggestion for improvement:*
> Better solution to achieve this could be use a map.
> e.g. some like that:
> {code}
> /subsystem=elytron/credential-store=credStore:add(cs-map={store.password=pass123, create.storage=true, store.file=path/to/cred/file})
> {code}
> Now credential store name is in URI too, it can be get from resource name.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7483) Credential store has configuration in "uri" attribute.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/WFLY-7483?page=com.atlassian.jira.plugin.... ]
Hynek Švábek reassigned WFLY-7483:
----------------------------------
Assignee: Peter Skopek (was: Darran Lofthouse)
> Credential store has configuration in "uri" attribute.
> ------------------------------------------------------
>
> Key: WFLY-7483
> URL: https://issues.jboss.org/browse/WFLY-7483
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Peter Skopek
> Priority: Critical
>
> Credential store has configuration in "uri" attribute. All parameters are in one string. It can be confusing and there is risk of typo (e.g. delimiter typo)
> In my opinion the main intention for it is to have general solution for custom implementation.
> *Suggestion for improvement:*
> Better solution to achieve this could be use a map.
> e.g. some like that:
> {code}
> /subsystem=elytron/credential-store=credStore:add(cs-map={store.password=pass123, create.storage=true, store.file=path/to/cred/file})
> {code}
> Now credential store name is in URI too, it can be get from resource name.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7483) Credential store has configuration in "uri" attribute.
by Hynek Švábek (JIRA)
Hynek Švábek created WFLY-7483:
----------------------------------
Summary: Credential store has configuration in "uri" attribute.
Key: WFLY-7483
URL: https://issues.jboss.org/browse/WFLY-7483
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
Priority: Critical
Credential store has configuration in "uri" attribute. All parameters are in one string. It can be confusing and there is risk of typo (e.g. delimiter typo)
In my opinion the main intention for it is to have general solution for custom implementation.
*Suggestion for improvement:*
Better solution to achieve this could be use a map.
e.g. some like that:
{code}
/subsystem=elytron/credential-store=credStore:add(cs-map={store.password=pass123, create.storage=true, store.file=path/to/cred/file})
{code}
Now credential store name is in URI too, it can be get from resource name.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (JGRP-2124) ByteArrayDataOutputStream: expand more conservatively
by Bela Ban (JIRA)
Bela Ban created JGRP-2124:
------------------------------
Summary: ByteArrayDataOutputStream: expand more conservatively
Key: JGRP-2124
URL: https://issues.jboss.org/browse/JGRP-2124
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 4.0
Currently, unless exponential growth is enabled, BADOSs expand as follows:
{{new_length = remaining_length + new bytes required + 32}}
If we have a 1024 buffer with pos=4 and want to add 1024 bytes, then we expand the buffer to 1020 + 1024 + 32 = 2076 bytes which is wasted space.
I'm changing this to
{{new_length = pos + new bytes required + 32}}. In the above example, we'd expand the buffer to 1060 bytes.
If we really wanted bigger expansion, exponential growth should be enabled.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7477) Elytron dir-context not updatable
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFLY-7477?page=com.atlassian.jira.plugin.... ]
Ilia Vassilev reassigned WFLY-7477:
-----------------------------------
Assignee: Ilia Vassilev
> Elytron dir-context not updatable
> ---------------------------------
>
> Key: WFLY-7477
> URL: https://issues.jboss.org/browse/WFLY-7477
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Ilia Vassilev
>
> All attributes of {{dir-context}} resource are read-only.
> Attempt to update:
> {code}
> [standalone@localhost:9990 /] /subsystem=elytron/dir-context=dc:write-attribute(name=url, value=ldap://localhost:10389)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0048: Attribute url is not writable",
> "rolled-back" => true
> }
> {code}
> Model description:
> {code}
> "url" => {
> "type" => STRING,
> "description" => "The connection url.",
> "expressions-allowed" => true,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-only",
> "storage" => "configuration"
> }
> {code}
> Make {{dir-context}} updatable.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7480) Description of Elytron final-name-rewriter resource
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFLY-7480?page=com.atlassian.jira.plugin.... ]
Ilia Vassilev reassigned WFLY-7480:
-----------------------------------
Assignee: Ilia Vassilev
> Description of Elytron final-name-rewriter resource
> ---------------------------------------------------
>
> Key: WFLY-7480
> URL: https://issues.jboss.org/browse/WFLY-7480
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Ilia Vassilev
> Labels: user_experience
>
> Describe in model / add operation / XSD purpose of this attribute. It is not obvious from name neither from description "The final name rewriter"
> What does this rewriter rewrites?
> As a reference, it can be configured in conjuction with {{pre-realm-mapper}} and {{post-realm-mapper}}, in those two cases I can understand from name and description what is it for.
> This JIRA applies to all occurences of {{final-name-rewriter}} in model:
> * 2x in {{http-authentication-factory}}
> * 2x in {{sasl-authentication-factory}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7482) Poor description of mechanism-name attribute
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/WFLY-7482?page=com.atlassian.jira.plugin.... ]
Ilia Vassilev reassigned WFLY-7482:
-----------------------------------
Assignee: Ilia Vassilev
> Poor description of mechanism-name attribute
> --------------------------------------------
>
> Key: WFLY-7482
> URL: https://issues.jboss.org/browse/WFLY-7482
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Martin Choma
> Assignee: Ilia Vassilev
> Labels: user_experience
>
> Description in model : "The name of the mechanism the configuration applies to"
> XSD description is better and explains why is mechanism-name optional: "This configuration will only apply where a mechanism with the name specified is used. If this attribute is omited then this will match any mechanism name."
> Synchronize descriptions - use description from XSD. in model
> Issue applies to attribute occurences in
> * http-server-mechanism-factory
> * sasl-authentication-factory
> Also applies to description in operation add description. Not sure if this is automatic, therefore mentioning it explicitly.
> {code}
> /subsystem=elytron/http-authentication-factory=a:read-operation-description(name=add)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-4908) Redeploy dependent ear fails with duplicate resource error for persistence unit
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4908?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-4908:
-----------------------------------------------
Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 1370112|https://bugzilla.redhat.com/show_bug.cgi?id=1370112] from ON_QA to VERIFIED
> Redeploy dependent ear fails with duplicate resource error for persistence unit
> -------------------------------------------------------------------------------
>
> Key: WFLY-4908
> URL: https://issues.jboss.org/browse/WFLY-4908
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 8.2.0.Final, 9.0.0.CR2, 9.0.0.Final, 10.0.0.CR4
> Environment: OS:
> Debian GNU/Linux 8.0 (jessie)
> Linux 3.16.0-4-amd64 x86_64 GNU/Linux
> JVM:
> java version "1.8.0_45"
> Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
> Wildfly:
> 9.0.0.Final
> Reporter: Юрий Витковский
> Assignee: Scott Marlow
> Fix For: 10.1.0.CR1, 10.1.0.Final
>
>
> I have two EARs:
> {code}
> module1.ear
> |
> +--ejb.jar
> |
> +--META-INF
> |
> +--persistence.xml with persistence unit "module1-pu"
> {code}
> and
> {code}
> module2.ear
> |
> +--META-INF
> | |
> | +--jboss-all.xml
> |
> +--ejb.jar
> |
> +--META-INF
> |
> +--persistence.xml with persistence unit "module2-pu"
> {code}
> module2.ear/META-INF/jboss-all.xml contains:
> {code:xml}
> <jboss xmlns="urn:jboss:1.0">
> <jboss-deployment-dependencies xmlns="urn:jboss:deployment-dependencies:1.0">
> <dependency name="module1.ear" />
> </jboss-deployment-dependencies>
> </jboss>
> {code}
> When I redeploy module1.ear, module2.ear not redeployed automatically with error: *java.lang.IllegalStateException: WFLYCTL0075: Duplicate resource module2.ear/ejb.jar#module2-pu* (on wildfly 8.2.0.Final: *java.lang.IllegalStateException: JBAS014666: Duplicate resource module2.ear/ejb.jar#module2-pu*)
> Full redeploy log:
> {code}
> 09:11:31,425 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 63) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'module2.ear/ejb.jar#module2-pu'
> 09:11:31,426 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 63) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'module2.ear/ejb.jar#module2-pu'
> 09:11:31,431 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 63) WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'module1.ear/ejb.jar#module1-pu'
> 09:11:31,434 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 63) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'module1.ear/ejb.jar#module1-pu'
> 09:11:31,437 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: ejb.jar) in 17ms
> 09:11:31,438 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment module1.ear (runtime-name: module1.ear) in 18ms
> 09:11:31,495 INFO [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0009: Undeployed "module1.ear" (runtime-name: "module1.ear")
> 09:11:31,495 INFO [org.jboss.as.controller] (management-handler-thread - 3) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.deployment.unit."module1.ear".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."module2.ear".PARSE, service jboss.deployment.subunit."module2.ear"."ejb.jar".PARSE]
>
>
> 09:11:31,558 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0002: Content removed from location /opt/wildfly/standalone/data/content/69/baf0eeab47c006bc1f3d99b21b4355fac62d13/content
> 09:11:43,170 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /opt/wildfly/standalone/data/content/69/baf0eeab47c006bc1f3d99b21b4355fac62d13/content
> 09:11:43,266 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "module1.ear" (runtime-name: "module1.ear")
> 09:11:43,268 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "ejb.jar")
> 09:11:43,273 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Read persistence.xml for module1-pu
> 09:11:43,289 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 63) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'module1.ear/ejb.jar#module1-pu'
> 09:11:43,289 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 63) HHH000204: Processing PersistenceUnitInfo [
> name: module1-pu
> ...]
> 09:11:43,292 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 63) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'module1.ear/ejb.jar#module1-pu'
> 09:11:43,293 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 63) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
> 09:11:43,293 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 63) HHH000431: Unable to determine H2 database version, certain features may not work
> 09:11:43,294 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 63) HHH000397: Using ASTQueryTranslatorFactory
> 09:11:43,296 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0070: Deployment restart detected for deployment module2.ear, performing full redeploy instead.
> 09:11:43,296 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0070: Deployment restart detected for deployment ejb.jar, performing full redeploy instead.
> 09:11:43,296 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: ejb.jar) in 0ms
> 09:11:43,297 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment module2.ear (runtime-name: module2.ear) in 1ms
> 09:11:43,298 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "module2.ear" (runtime-name: "module2.ear")
> 09:11:43,299 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "ejb.jar")
> 09:11:43,300 INFO [org.jboss.as.jpa] (MSC service thread 1-2) WFLYJPA0002: Read persistence.xml for module2-pu
> 09:11:43,307 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 63) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'module2.ear/ejb.jar#module2-pu'
> 09:11:43,308 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 63) HHH000204: Processing PersistenceUnitInfo [
> name: module2-pu
> ...]
> 09:11:43,312 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.subunit."module2.ear"."ejb.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."module2.ear"."ejb.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "ejb.jar" of deployment "module2.ear"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalStateException: WFLYCTL0075: Duplicate resource module2.ear/ejb.jar#module2-pu
> at org.jboss.as.controller.registry.AbstractModelResource$DefaultResourceProvider.register(AbstractModelResource.java:248)
> at org.jboss.as.controller.registry.AbstractModelResource.registerChild(AbstractModelResource.java:143)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addManagementConsole(PersistenceUnitServiceHandler.java:1128)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnitPhaseTwo(PersistenceUnitServiceHandler.java:704)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:289)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleJarDeployment(PersistenceUnitServiceHandler.java:162)
> at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:133)
> at org.jboss.as.jpa.processor.PersistenceCompleteInstallProcessor.deploy(PersistenceCompleteInstallProcessor.java:55)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> ... 5 more
>
>
> 09:11:43,376 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "module1.ear" (runtime-name : "module1.ear")
> 09:11:43,376 INFO [org.jboss.as.controller] (management-handler-thread - 2) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.deployment.subunit."module2.ear"."ejb.jar" (unavailable) dependents: [service jboss.deployment.unit."module2.ear".PARSE]
> service jboss.deployment.subunit."module2.ear"."ejb.jar".STRUCTURE (unavailable) dependents: [service jboss.deployment.unit."module2.ear".PARSE]
> service jboss.deployment.subunit."module2.ear"."ejb.jar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."module2.ear".deploymentCompleteService]
> WFLYCTL0185: Newly corrected services:
> service jboss.deployment.unit."module1.ear".deploymentCompleteService (new available)
> WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."module2.ear"."ejb.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."module2.ear"."ejb.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "ejb.jar" of deployment "module2.ear"
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1936) Value of parameters "restart-required" for fixed-*port attributes does not match reality for socket-binding and *-destination-outbound-socket-binding in CLI
by Ondrej Kotek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1936?page=com.atlassian.jira.plugi... ]
Ondrej Kotek moved JBEAP-6905 to WFCORE-1936:
---------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1936 (was: JBEAP-6905)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Server
(was: Server)
(was: User Experience)
Affects Version/s: 3.0.0.Alpha11
(was: 7.1.0.DR7)
> Value of parameters "restart-required" for fixed-*port attributes does not match reality for socket-binding and *-destination-outbound-socket-binding in CLI
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1936
> URL: https://issues.jboss.org/browse/WFCORE-1936
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Affects Versions: 3.0.0.Alpha11
> Reporter: Ondrej Kotek
> Assignee: Chao Wang
> Labels: user_experience
>
> {{fixed-port}} attribute of {{socket-binding}} and {{fixed-source-port}} attributes of {{*-destination-outbound-socket-binding}} define in its description that there is not necessary to do {{reload}} or {{restart}} for any of them. But reality is different. If you tries to change such attributes you are informed that {{reload}} is necessary.
> The attributes are defined as {{"restart-required" => "no-services"}}, see {{/socket-binding-group=standard-sockets:read-resource-description(recursive=true)}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1936) Value of parameters "restart-required" for fixed-*port attributes does not match reality for socket-binding and *-destination-outbound-socket-binding in CLI
by Ondrej Kotek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1936?page=com.atlassian.jira.plugi... ]
Ondrej Kotek updated WFCORE-1936:
---------------------------------
Labels: user_experience (was: )
> Value of parameters "restart-required" for fixed-*port attributes does not match reality for socket-binding and *-destination-outbound-socket-binding in CLI
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1936
> URL: https://issues.jboss.org/browse/WFCORE-1936
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Affects Versions: 3.0.0.Alpha11
> Reporter: Ondrej Kotek
> Assignee: Chao Wang
> Labels: user_experience
>
> {{fixed-port}} attribute of {{socket-binding}} and {{fixed-source-port}} attributes of {{*-destination-outbound-socket-binding}} define in its description that there is not necessary to do {{reload}} or {{restart}} for any of them. But reality is different. If you tries to change such attributes you are informed that {{reload}} is necessary.
> The attributes are defined as {{"restart-required" => "no-services"}}, see {{/socket-binding-group=standard-sockets:read-resource-description(recursive=true)}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months