[jboss-jira] [JBoss JIRA] Closed: (JBAS-6441) HASingletonDeploymentScanner fails when deploy-hasingleton is empty

[Brian Stansberry (JIRA)]

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

Brian Stansberry closed JBAS-6441.
----------------------------------

    Resolution: Done


> HASingletonDeploymentScanner fails when deploy-hasingleton is empty
> -------------------------------------------------------------------
>
>                 Key: JBAS-6441
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6441
>             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
>
>
> If the contents of deploy-hasingleton are empty, HASingletonDeploymentScanner will call DeploymentManager.startt(...) 
> 1) possibly before DeploymentManager.loadProfile() has been called
> 2) passing in an empty set of deployment names.
> Either will lead to failure.
> Fix is to not call DeploymentManager.startt(...) if the uploadedNames set is empty.
> JBAS-6440 prevents this problem actually being visible to AS 5.0.0.GA users, but if they implement the workaround described on that JIRA they'll see it. Solution is to not implement the workaround if you don't have any content in deploy-hasingleton. :-)

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