[jboss-jira] [JBoss JIRA] Updated: (JBAS-4415) ClusterFileTransferTestCase.testFarmDeploy fails to delete and copy

[Brian Stansberry (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4415?page=all ]

Brian Stansberry updated JBAS-4415:
-----------------------------------

    Fix Version/s: JBossAS-4.2.1.CR1

Experimentation has shown that the kind of operations the test case does (copy file to farm, delete file, copy file) fail on Windows when done against deploy/ as well.  This does not appear to be an issue with the FarmService directly, but rather with the underlying deployment code.

It's intermittent -- the deployed jar is not always locked.  When it is locked, the lock is held for an extended period; i.e. not just for a couple loops of the scanner thread or something.

> ClusterFileTransferTestCase.testFarmDeploy fails to delete and copy
> -------------------------------------------------------------------
>
>                 Key: JBAS-4415
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4415
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: JBossAS-4.2.0.CR2
>         Environment: Affects Windows versions (x86_64-BEA, x86-Sun, x86-BEA, x86_64-Sun)
>            Reporter: Richard Achmatowicz
>         Assigned To: Brian Stansberry
>             Fix For: JBossAS-4.2.1.CR1
>
>
> This clustering test orj.jboss.test.ha.farm.test.ClusterFileTransferTestCase:
> (i) creates a test file farmtestfile.jar on node0, waits 15 seconds and checks that the file has been propagated to node1 and that the files have equal contents
> (ii) deletes the test file on node1, waits 15 seconds and checks that the file on node0 has been deleted
> (iii) creates a file on node1, waits 15 seconds and checks that the file has been propagated to node0 and that the files have equal contents
> The test fails in a repeatable manner, although sometimes for different reasons:
> a. in some cases, the file deletion on node1 in step (ii) fails, despite the fact that the file exists
> b. in some cases, the file existence on node0 in step (iii) fails - the file just does not get propagated
> Please see the initial logged issue JBPAPP-171 for more details and logs.

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