[jboss-jira] [JBoss JIRA] Closed: (JBAS-6439) Non-DeploymentManager-based HASingletonDeploymentScanner impl results in deploy-hasingleton content removal

[Brian Stansberry (JIRA)]

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

Brian Stansberry closed JBAS-6439.
----------------------------------

    Resolution: Done


> Non-DeploymentManager-based HASingletonDeploymentScanner impl results in deploy-hasingleton content removal
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-6439
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6439
>             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
>             Fix For: JBossAS-5.1.0.Beta1
>
>
> HASingletonDeploymentScanner has two sets of logic for how it interacts with the ProfileService -- one that uses the DeploymentManager when it is available and one that directly interacts with the Profile and the MainDeployer if no DeploymentManager is available.
> The code that doesn't use the DeploymentManager is broken. It results in the deploy-hasingleton/ content being removed when a node stops being the master (including at shutdown). See forum thread.
> I don't see a good fix for this, and the "basic" ProfileService impl that doesn't use a DeploymentManager is not actually used anymore anyway, and will be dropped from future releases. So, my intent in resolving this JIRA is to remove the relevant code from HASingletonDeploymentScanner impl, and require that a DeploymentManager be available.
> There is a separate issue whereby the DeploymentManager isn't being made available to HASingletonDeploymentScanner, causing this to-be-removed logic to execute. I'll file a JIRA for fixing that and link it to this one.

-- 
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