[
https://issues.jboss.org/browse/AS7-1473?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse commented on AS7-1473:
---------------------------------------
The unexpected redeploy instead of undeploy actually occurs because the cached timestamp
for the deployment is 0L - i.e. whatever file the timestamp was read from it did not exist
at the time of the reading.
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
Attachments:
org.jboss.as.test.surefire.servermodule.ServerInModuleDeploymentTestCase-output.txt
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