Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-6440

HASingletonDeploymentScanner starts before DeploymentManager

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • JBossAS-5.0.1.GA
    • JBossAS-5.0.0.GA
    • Clustering
    • None
    • Release Notes
    • Workaround Exists
    • Hide

      Edit the server/all/deploy/profileservice-jboss-beans.xml file's "DeploymentManager" bean to add the following element:

      <supply>DeploymentManager</supply>

      Edit the server/all/deploy/cluster/deploy-hasingleton-jboss-beans.xml file's "HASingletonDeploymentScanner" bean to add the following element:

      <demand state="Instantiated">DeploymentManager</demand>

      NOTE: This workaround should not be applied if the deploy-hasingleton/ directory does not contain any content. See JBAS-6441.

      Show
      Edit the server/all/deploy/profileservice-jboss-beans.xml file's "DeploymentManager" bean to add the following element: <supply>DeploymentManager</supply> Edit the server/all/deploy/cluster/deploy-hasingleton-jboss-beans.xml file's "HASingletonDeploymentScanner" bean to add the following element: <demand state="Instantiated">DeploymentManager</demand> NOTE: This workaround should not be applied if the deploy-hasingleton/ directory does not contain any content. See JBAS-6441 .

    Description

      AS 5.0.0.GA ships with a DeploymentManager configured. When a DeploymentManager is available, HASingletonDeploymentScanner is meant to use it. However, the proper dependencies are not in place, which results in HASingletonDeploymentScanner falling back on some buggy logic (see JBAS-6439).

      We need to ensure HASingletonDeploymentScanner depends on DeploymentManager. To ensure that I'll directly dependency inject the DeploymentManager rather than obtaining it from the injected ProfileService.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBAS-6439 Non-DeploymentManager-based HASingletonDeploymentScanner impl results in deploy-hasingleton content removal

          • 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

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: