[jboss-jira] [JBoss JIRA] Updated: (JBAS-6440) HASingletonDeploymentScanner starts before DeploymentManager

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated JBAS-6440:
-----------------------------------

    Workaround Description: 
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.


                Workaround: [Workaround Exists]


> HASingletonDeploymentScanner starts before DeploymentManager
> ------------------------------------------------------------
>
>                 Key: JBAS-6440
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6440
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-5.0.0.GA
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>            Priority: Critical
>             Fix For: JBossAS-5.0.1.GA
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira