[jboss-jira] [JBoss JIRA] (WFLY-5126) Inconsistent settings of process-id-* attribute in cli

[Ondřej Chaloupka (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondřej Chaloupka updated WFLY-5126:
-----------------------------------
    Affects Version/s: 10.0.0.Beta1


> Inconsistent settings of process-id-* attribute in cli
> ------------------------------------------------------
>
>                 Key: WFLY-5126
>                 URL: https://issues.jboss.org/browse/WFLY-5126
>             Project: WildFly
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 10.0.0.Beta1
>            Reporter: Ondřej Chaloupka
>            Assignee: Tom Jenkinson
>            Priority: Minor
>
> There is a non-intuitive behavior of setting the process-id-* attributes via jboss cli.
> When I want to set {{process-id-socket-binding}} I need to use composite batch operation
> {code}
> batch
> /subsystem=transactions:undefine-attribute(name=process-id-uuid)
> /subsystem=transactions:write-attribute(name=process-id-socket-binding, value="txn-status-manager")
> run-batch
> {code}
> If not using batch operation I get errors
> {code}
> /subsystem=transactions:undefine-attribute(name=process-id-uuid)
> {
>     "outcome" => "failed",
>     "failure-description" => "WFLYTX0025: Either process-id-uuid must be 'true' or  process-id-socket-binding must be defined.",
>     "rolled-back" => true
> }
> [standalone at localhost:9990 /] /subsystem=transactions:write-attribute(name=process-id-socket-binding, value="txn-status-manager")
> {
>     "outcome" => "failed",
>     "failure-description" => "WFLYCTL0105: process-id-uuid is invalid in combination with process-id-socket-binding",
>     "rolled-back" => true
> }
> {code}
> First inconsistency is that I can't use {{:write-attribute(name=process-id-uuid, value=false)}} but I have to run {{:undefine-attribute}}.
> Then the other strange thing is setting the attribute {{process-id-uuid}} back to live. I can't use composite operation as it fails.
> {code}
> /subsystem=transactions:write-attribute(name=process-id- 
> process-id-socket-binding  process-id-socket-max-ports  process-id-uuid  
> /subsystem=transactions:write-attribute(name=process-id-uuid, value=true)
> 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:" => {"Operation step-1" => "WFLYCTL0155: process-id-socket-binding may not be null"}}
> {code}
> If I want to set the attribute back I have to use simply
> {code}
> /subsystem=transactions:write-attribute(name=process-id-uuid, value=true)
> {code}
> which undefine the {{process-id-socket-binding}} automatically.
> I think that composite operation could not be demanded and {{/subsystem=transactions:write-attribute(name=process-id-socket-binding, value="txn-status-manager")}} could undefine {{process-id-uuid}} automatically as this behaves from other direction.
> Or description of failures should be changed to inform how to proceed the change (batch is needed etc.)
> On the other hand composite operation of setting {{process-id-uuid}} back should not fail I think.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)