[jboss-jira] [JBoss JIRA] (WFCORE-1418) Reloading host-controller via http-api puts the HC into unresponsive state

[Tomaz Cerar (JIRA)]

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

Tomaz Cerar moved JBEAP-3637 to WFCORE-1418:
--------------------------------------------

              Project: WildFly Core  (was: JBoss Enterprise Application Platform)
                  Key: WFCORE-1418  (was: JBEAP-3637)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Domain Management
                           (was: Domain Management)
       Target Release:   (was: 7.0.0.GA)
    Affects Version/s: 2.0.10.Final
                           (was: 7.0.0.ER5)
      Affects Testing:   (was: Regression)


> Reloading host-controller via http-api puts the HC into unresponsive state
> --------------------------------------------------------------------------
>
>                 Key: WFCORE-1418
>                 URL: https://issues.jboss.org/browse/WFCORE-1418
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 2.0.10.Final
>            Reporter: Tomaz Cerar
>            Assignee: Tomaz Cerar
>            Priority: Blocker
>
> Reloading host-controller via http-api puts the HC into unresponsive state.
> *reproduce*
>  \- create an administrative user admin:asdasd at 2
>  \- start a domain
>  \- reload a server via http api
> {noformat}
> curl --digest -L -D - http://localhost:9990/management --header "Content-Type: application/json" -d '{"operation":"reload","name":"", "address":{"host" : "master"},"json.pretty":1}' -u admin:asdasd at 2
> {noformat}
> *actual*
> Default server instances are stopped, HC is left in unresponsive state.
> Keeping the domain alive, following message will appear in 5 minutes, domain will become responsive again after that.
> {noformat}
> [Host  Controller] 04:47:23,966 ERROR  [org.jboss.as.controller.management-operation] (management task-7)  WFLYCTL0349: Timeout after [300] seconds waiting for service container  stability while finalizing an operation. Process must be restarted. Step  that first updated the service container was 'reload' at address  '[("host" => "master")]'
> {noformat}
> *expected*
> Domain is reloaded
> *additional info*
> The issue was introduced by fix for JBEAP-2751 - https://github.com/jbossas/wildfly-core-eap/commit/4986773a51fbf43ad911aecc403f7eb90e72a8c2
> thread dump of unresponsive HC
> http://pastebin.test.redhat.com/348732
> I am unable to reproduce locally, but issue can be easily reproduced on slower servers in MWQE lab. SSLMasterSlave*WayTestCase using reload via http-api cousing failures in domain modules of wf-core testsuite (e.g. [eap-7x-as-testsuite-test-core-rhel|https://url.corp.redhat.com/9f1f544] )
> Regression against 7.0.0.ER4. I was able to reproduce with the latest wildfly-core bits as well (1be598e)



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)