[jboss-jira] [JBoss JIRA] Commented: (AS7-1473) Deleting .deployed occasionaly file is deployed again immediately after undeployment.

[Darran Lofthouse (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619089#comment-12619089 ] 

Darran Lofthouse commented on AS7-1473:
---------------------------------------

Additional information captured for the accidental redeploy.

The testFilesystemDeployment test reaches the stage where undeploy is called, a temporary System.out records: -

{noformat}
Fri Aug 05 12:17:08 BST 2011 Deleted .deployed
{noformat}

This message is only logged if the call to delete returns true.

The following lines are then logged: -

{noformat}
12:17:08,102 TRACE [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Scan complete
12:17:09,102 TRACE [org.jboss.as.deployment] (DeploymentScanner-threads - 2) Scanning directory /home/darranl/src/jbossas7/jboss-as/testsuite/smoke/target/deployments for deployment content changes
12:17:09,102 TRACE [org.jboss.as.controller] (DeploymentScanner-threads - 2) Executing "read-children-names" undefined
12:17:09,104 TRACE [org.jboss.as.controller] (DeploymentScanner-threads - 2) Prepared response is {
    "outcome" => undefined,
    "result" => [
        "arquillian-service",
        "please-the-arquillian-gods.jar",
        "test-deployment.sar"
    ]
}
12:17:09,114 DEBUG [org.jboss.as.deployment] (DeploymentScanner-threads - 2) Deployment scan of [/home/darranl/src/jbossas7/jboss-as/testsuite/smoke/target/deployments] found update action [{
    "operation" => "full-replace-deployment",
    "address" => undefined,
    "name" => "test-deployment.sar",
    "content" => [{
        "path" => "/home/darranl/src/jbossas7/jboss-as/testsuite/smoke/target/deployments/test-deployment.sar",
        "archive" => true
    }]
}]
12:17:09,114 TRACE [org.jboss.as.controller] (DeploymentScanner-threads - 1) Executing "composite" undefined
{noformat}

So for some reason it appears that the deletion of the .deployed is mistakenly taken as a redeployment instead of an undeployment.  The testExplodedFilesystemDeployment test is then the test that routinely fails as it's first deploy step triggers an undeployment which it mistakenly takes for the first deployment being complete and then fails as the deployment is not yet ready.

> Deleting .deployed occasionaly file is deployed again immediately after undeployment.
> -------------------------------------------------------------------------------------
>
>                 Key: AS7-1473
>                 URL: https://issues.jboss.org/browse/AS7-1473
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>             Fix For: 7.0.1.Final
>
>
> Currently investigating the ServerInModuleDeploymentTestCase intermittent failures and this seems to be the common cause of the failure.  The testFilesystemDeployment test undeploys the deployment at the end but for some reason it is deployed again, testExplodedFilesystemDeployment then fails as when it attempts to deploy it actually triggers a redeployment but is only expecting a single JMX notification.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira