[jboss-jira] [JBoss JIRA] (WFLY-8852) Clean up managed domain handling of the transaction subsystem's 'probe' operation

[Kabir Khan (JIRA)]

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

Kabir Khan updated WFLY-8852:
-----------------------------
    Fix Version/s: 11.0.0.Beta1


> Clean up managed domain handling of the transaction subsystem's 'probe' operation
> ---------------------------------------------------------------------------------
>
>                 Key: WFLY-8852
>                 URL: https://issues.jboss.org/browse/WFLY-8852
>             Project: WildFly
>          Issue Type: Sub-task
>          Components: Transactions
>            Reporter: Brian Stansberry
>            Assignee: Michael Musgrove
>             Fix For: 11.0.0.Beta1
>
>
> Subtask for this item from the parent issue:
> {quote}
> The transaction subsystem's "probe" operation. A read-only, runtime-only op registered on the profile resource but which is functionally a no-op if invoked on the profile resource. But WFCORE-2858 would mean this now gets rolled out to all servers in the domain that use the profile, triggering an actual probe on all. So, if we do WFCORE-2858 we could:
> a) Accept this, and let the op roll out. That should be an RFE though, with analysis that rolling it out would be harmless.
> b) Remove the op from the profile. It never did anything useful (just a no-op that isn't rolled out) so removing it is only
> a semi-breaking change.
> c) Add OperationEntry.Flag.HOST_CONTROLLER_ONLY to the operation definition to prevent that rollout.
> Choice c) would let WFCORE-2858 go forward and preserve the status quo for this op, with a) and b) still options for the future, so that's what will be done as part of this work.
> {quote}
> The parent issue will do choice c); this issue is to decide the final status.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)