[jboss-jira] [JBoss JIRA] Commented: (JBAS-5506) Deployment state is not set correctly deployments that have previously failed.

[Jay Howell (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-5506?page=comments#action_12411940 ] 
            
Jay Howell commented on JBAS-5506:
----------------------------------

In order to correctly deploy, you must reboot the server after the failure.

> Deployment state is not set correctly deployments that have previously failed.
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-5506
>                 URL: http://jira.jboss.com/jira/browse/JBAS-5506
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Deployment services
>    Affects Versions: JBossAS-4.2.2.GA
>            Reporter: Jay Howell
>         Assigned To: Scott M Stark
>
> Once the deployment of a ear on JBOSS AS 4.2.2.AG has failed, the JMX method MainDeployer.listDeployed() keeps indicating that the deployment of the ear has failed, even when a later deployment of the fixed component succeeds.
> Steps to reproduce
> 1.  Start 4.2.2 
> 2.  Take EJB3Trail.ear and take out the application.xml file.
> 3.  Deploy the ear.  You get an exception and a failure.
> Exception:  
> org.jboss.deployment.DeploymentException: No META-INF/application.xml found
> Inside the MailDeployer.listDeployed() you see:
> org.jboss.deployment.DeploymentInfo at 6b37e2c9 { url=file:/root/jboss/4.2.2/build/output/jboss-4.2.2.GA/server/default/deploy/EJB3Trail.ear/ }
>   deployer: org.jboss.deployment.EARDeployer at e7d53
>   status: null
>   state: FAILED
>   watch: file:/root/jboss/4.2.2/build/output/jboss-4.2.2.GA/server/default/deploy/EJB3Trail.ear/
>   altDD: null
>   lastDeployed: 1210100865412
>   lastModified: 1210099024000
>   mbeans:
> 4.  delete the ear in the deploy directory(complete undeploy)
> 5.  Fix the ear by putting the application.xml back into the ear
> 6.  Copy the ear back into the deploy directory
> 7.  Look in the JMX console under MainDeployer.listDeployed
> you will see that the state has not been updated...
> org.jboss.deployment.DeploymentInfo at 6b37e2c9 { url=file:/root/jboss/4.2.2/build/output/jboss-4.2.2.GA/server/default/deploy/EJB3Trail.ear/ }
>   deployer: org.jboss.deployment.EARDeployer at e7d53
>   status: null
>   state: FAILED
>   watch: file:/root/jboss/4.2.2/build/output/jboss-4.2.2.GA/server/default/deploy/EJB3Trail.ear/
>   altDD: null
>   lastDeployed: 1210100865412
>   lastModified: 1210099024000
>   mbeans:
> But now all the other sub deployments in the ear appear.
> This also seems to happen for war files and other deployments.

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