[jboss-jira] [JBoss JIRA] (WFLY-8705) Watermark policy does not distribute work (distributed workmanager)

[Stefano Maestri (JIRA)]

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

Stefano Maestri moved JBEAP-10745 to WFLY-8705:
-----------------------------------------------

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


> Watermark policy does not distribute work (distributed workmanager)
> -------------------------------------------------------------------
>
>                 Key: WFLY-8705
>                 URL: https://issues.jboss.org/browse/WFLY-8705
>             Project: WildFly
>          Issue Type: Bug
>          Components: JCA
>            Reporter: Stefano Maestri
>            Assignee: Stefano Maestri
>            Priority: Blocker
>              Labels: KK-DR18
>
> Reproducing test in https://github.com/LittleJohnII/wildfly/tree/eap7-495
> {noformat}
> # build WFLY first
> cd testsuite/integration/basic
> mvn clean test -Dtest='Dwm*TestCase' -Djboss.server.config.file.name=standalone-ha.xml -DtrimStackTrace=false -Darquillian.launch=distributed-group
> {noformat}
> The watermark test will fail and logs will show that work wasn't distributed to the second node when the amount of threads available got down to 1 (and watermark = 1). Even with the default watermark setting, the work is never distributed - if thread pool size = 2 and 3 instances of work are executed, the third always waits for the previous two to finish on the first node.
> [~maeste] is already aware of the issue - it was discussed on HipChat prior to the Jira creation, so this is mainly a tracker.
> I'm setting blocker priority since I'd like to have watermark working before EAP7-495 is resolved (I think this is the most important policy setting, and the default too). If this is a problem, we can discuss lowering the priority and pushing EAP7-495 out anyway, since this isn't a thing that breaks the whole DWM.



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