[jboss-jira] [JBoss JIRA] (WFLY-8184) Singleton deployment not stopped on the previous singleton provider after new provider is elected

[Radoslav Husar (JIRA)]

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

Radoslav Husar moved JBEAP-9010 to WFLY-8184:
---------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-8184  (was: JBEAP-9010)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Clustering
                           (was: Clustering)
    Affects Version/s:     (was: 7.1.0.DR8)
                           (was: 7.1.0.DR9)
                           (was: 7.1.0.DR10)
                           (was: 7.1.0.DR11)
      Affects Testing:   (was: Regression)


> Singleton deployment not stopped on the previous singleton provider after new provider is elected
> -------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-8184
>                 URL: https://issues.jboss.org/browse/WFLY-8184
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>            Priority: Critical
>
> Scenario: failover clustering test with singleton deployment.
> {code:xml|title=Singleton subsystem configuration}
> <subsystem xmlns="urn:jboss:domain:singleton:1.0">
>   <singleton-policies default="default">
>     <singleton-policy name="default" cache-container="server">
>       <random-election-policy/>
>     </singleton-policy>
>   </singleton-policies>
> </subsystem>
> {code}
> Nodes startup order: node1, node2, node3, node4.
> During node1 startup, this server is elected as the singleton provider and deploys singleton deployment. During other servers startup, some other node (usually node2) is elected as the singleton provider and deploys singleton deployment. However, node1 has the singleton deployment still deployed, so there are *2 nodes* effectively providing a singleton deployment.
> Deployment used: [clusterbench-ee7-singleton-jbossall.ear|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-clusterbench-singleton/1/artifact/clusterbench-ee7-singleton-jbossall.ear|http://example.com]
> Standard clusterbench application with modified jboss-all.xml:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <jboss xmlns="urn:jboss:1.0">
>     <singleton-deployment xmlns="urn:jboss:singleton-deployment:1.0"/>
> </jboss>
> {code}
> Server log:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/perflab_eap-7x-failover-singleton-deployment-jvmkill-random-election-policy/7/console-perf18/



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