deleted file when re-deploying on a cluster node

SourceForge Submitter: jbaesner .
I'm submitting this bug while knowing that a similar
bug has been submitted in the past for other versions
of JBoss. My impression is that this bug is still open
and no fix/workaround has been found by myself.

Operating System:

• Cluster Node1:
  SunOS 5.8 Generic_117350-02 sun4u sparc
  SUNW,Sun-Fire-V240
• Cluster Node2:
  SunOS 5.8 Generic_108528-27 sun4u sparc
  SUNW,Sun-Fire-V440

JDK Version:

• Cluster Node1:
  java version "1.4.2_05"
  Java(TM) 2 Runtime Environment, Standard Edition
  (build 1.4.2_05-b04)
  Java HotSpot(TM) Client VM (build 1.4.2_05-b04,
  mixed mode)

• Cluster Node2:
  java version "1.4.2_05"
  Java(TM) 2 Runtime Environment, Standard Edition
  (build 1.4.2_05-b04)
  Java HotSpot(TM) Client VM (build 1.4.2_05-b04,
  mixed mode)

JBoss Version:
JBoss 3.2.5

Steps to reproduce the bug:

I'm running a cluster with 2 members (as you can see in
the information above).

On Node1 I have a complete deployment with the existing
farm directory and all .sar and .ear files needed for
my application (1 ear & 3 sar files). This node is
started first.

On Node2 I have an "empty member" that get it's deploy
files using the farm service (this works very well!).
This node is started once Node1 has been completly started.

When I now touch one of the .sar or the .ear file in
the farm directory on Node2, it get's redeployed on
Node2 but DELETED on Node1!

A second touch of the same .sar or .ear file on Node2
will again re-deploy on Node2 and magically do a deploy
of the now again existing file on Node1!!!!

All following attemps of the "touch" on Node2 will
result in the expected behaviour: re-deploying the
"changed" file on BOTH nodes!