Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10593

Singleton deployment not started if a node is re-elected

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.1.0.DR19
    • 7.1.0.DR17
    • Clustering
    • None
    • Workaround Exists
    • Hide

      Annotate deployment using singleton-deployment.xml instead of jboss-all.xml.

      Show
      Annotate deployment using singleton-deployment.xml instead of jboss-all.xml.

    Description

      Seen in our clustering tests for singleton deployments.

      Timeline:
      Node1 elected as the singleton provider
      Some other node gets elected after topology change
      Node1 gets elected after another topology change and logs:

      13:08:42,248 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0003: node1 elected as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service
13:08:42,474 INFO  [org.wildfly.clustering.server] (DistributedSingletonService - 1) WFLYCLSV0001: This node will now operate as the singleton provider of the jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".installer service
13:08:42,476 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."clusterbench-ee7-singleton-jbossall.ear".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment "clusterbench-ee7-singleton-jbossall.ear"
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: Root element supplier for {http://www.jboss.com/xml/ns/javaee}jboss-app already registered
        at org.jboss.staxmapper.XMLMapperImpl.registerRootElement(XMLMapperImpl.java:51)
        at org.jboss.staxmapper.XMLMapperImpl.registerRootElement(XMLMapperImpl.java:46)
        at org.jboss.as.server.deployment.jbossallxml.JBossAllXMLParsingProcessor.deploy(JBossAllXMLParsingProcessor.java:90)
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
        ... 5 more

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10787 Address DeploymentUnitProcessor leaks in the codebase

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2738 SubDeploymentProcessor leaks Attachments.SUB_DEPLOYMENTS on undeploy()

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2750 ModuleSpecProcessor does not recreate module spec after undeploy()

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2733 JBossAllXmlParserRegisteringProcessor leaks deployment unit attachments on undeploy

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2791 Auto-remove lingering deployment unit attachments following singleton deployment primary->backup transition

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFLY-8695 WeldPortableExtensionProcessor does not clear registered Extensions on undeploy()

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-8697 Address DeploymentUnitProcessor leaks in the codebase

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              mvinkler1@redhat.com Michal Vinkler
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: