[jboss-jira] [JBoss JIRA] (WFLY-8616) Distributed workmanager does not execute work on other nodes than where the work was scheduled

[Stefano Maestri (JIRA)]

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

Stefano Maestri moved JBEAP-10470 to WFLY-8616:
-----------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-8616  (was: JBEAP-10470)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: JCA
                           (was: JCA)
    Affects Version/s:     (was: 7.1.0.DR13)


> Distributed workmanager does not execute work on other nodes than where the work was scheduled
> ----------------------------------------------------------------------------------------------
>
>                 Key: WFLY-8616
>                 URL: https://issues.jboss.org/browse/WFLY-8616
>             Project: WildFly
>          Issue Type: Bug
>          Components: JCA
>            Reporter: Stefano Maestri
>            Assignee: Stefano Maestri
>            Priority: Blocker
>              Labels: KK-DR17, eap7.1-rfe-blocker, eap71_beta
>
> Scenario: we have two EAP servers, both of them have a distributed workmanager set up. We try to schedule some work on one of the servers (via {{scheduleWork()}} and since we have a policy of ALWAYS, the work should be executed on a node different from the one where it was scheduled. However, it is always executed on the same node.
> This might be related to or even caused by JBEAP-9418.
> I think this is severe enough to warrant a beta blocker label - the DWM can be configured and you can pass work instances to it, but they will never be executed on remote nodes. In effect, policy options other than NEVER do not work. I'm raising the priority to blocker accordingly.
> This also blocks EAP7-495.



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