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

Singleton deployment functionality completely broken

    XMLWordPrintable

Details

    • Regression, Blocks Testing
    • Hide

      Deploy any singleton deployment to a cluster. For example, follow ha-singleton-deployment quickstarts: https://github.com/jbossas/eap-quickstarts/blob/7.x/ha-singleton-deployment/README.md
      Or you can use the attached singleton deployment application (taken from the QS).

      Show
      Deploy any singleton deployment to a cluster. For example, follow ha-singleton-deployment quickstarts: https://github.com/jbossas/eap-quickstarts/blob/7.x/ha-singleton-deployment/README.md Or you can use the attached singleton deployment application (taken from the QS).

    Description

      Since EAP 7.1.0.DR17, singleton deployment functionality is completely broken - i.e. the singleton deployment starts on all nodes of the cluster.

      It doesn't matter if a deployment identifies itself as singleton deployment via a /META-INF/singleton-deployment.xml deployment descriptor or jboss-all.xml.

      I am using vanilla EAP 7.1.0.DR17, standalone-ha.xml configuration.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10111 Former singleton provider node leaving cluster after re-election causes another re-election

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-7542 Application deployed as "singleton-deployment" in a cluster is not always reachable for EJB calls

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBEAP-7969 Create HA Singleton Deployments quickstart

          • 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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: