[jboss-jira] [JBoss JIRA] Updated: (AS7-1473) Fix errors causing intermittent failures of ServerInModuleDeploymentTestCase
[
https://issues.jboss.org/browse/AS7-1473?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse updated AS7-1473:
----------------------------------
Summary: Fix errors causing intermittent failures of
ServerInModuleDeploymentTestCase (was: Deleting .deployed occasionaly file is deployed
again immediately after undeployment.)
Description:
After some in-depth investigation a number of issues have been identified as causing the
intermittent failures to the ServerInModuleDeploymentTestCase test case.
1 - The in-memory cached modified time for a deployment can be corrupted if the .deployed
marker is deleted after it is written but before the modified time is cached.
2 - Multiple calls after a deployment can cause a .deployed marker to be written, however
external processes waiting for the presence of this file so that it can be deleted can
delete
it after the first of these calls but before the subsequent call. The end result is
that the process thinks it has deleted the file but in some circumstances it is just
written again!
3 - The test was written before zipped archives were automatically deployed but not
updated - the test case should test the correct behaviour for automatic zip
deployment and deployment based on marker files.
In addition to this modifications to the test revealed that once a deployment scanner has
been removed there is an error if there is an attempt to add a new deployment scanner
using a name used previously.
was:
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.
Complexity: High
Fix errors causing intermittent failures of
ServerInModuleDeploymentTestCase
-----------------------------------------------------------------------------
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
After some in-depth investigation a number of issues have been identified as causing the
intermittent failures to the ServerInModuleDeploymentTestCase test case.
1 - The in-memory cached modified time for a deployment can be corrupted if the
.deployed marker is deleted after it is written but before the modified time is cached.
2 - Multiple calls after a deployment can cause a .deployed marker to be written,
however external processes waiting for the presence of this file so that it can be deleted
can delete
it after the first of these calls but before the subsequent call. The end result is
that the process thinks it has deleted the file but in some circumstances it is just
written again!
3 - The test was written before zipped archives were automatically deployed but not
updated - the test case should test the correct behaviour for automatic zip
deployment and deployment based on marker files.
In addition to this modifications to the test revealed that once a deployment scanner has
been removed there is an error if there is an attempt to add a new deployment scanner
using a name used previously.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira