On Saturday 28 April 2001 02:13, you wrote:
> > Yes, edit the code and insert a delay. I would suggest instead that you
> > build the jat file somewhere else and copy (or better yet, move) it into
> > place when it is done.
>
> I would suggest the latter... adding a delay would be the wrong thing
> to do IMHO.
I have experienced similar problems. I use 'scp' to copy the jar's over the
network. Every once in a while, the AutoDeployer starts reading the archive
before everything is in place.
I understand the AutoDeployer uses modified date (from the file system) to
determine whether a file has changed. If this date is set when the copy
procedure starts to write to disk, as it appears to do (I'm running Linux,
kernel 2.4.0/ReiserFS), there is a discomforting possibility for a race
condition.
In my humble opinion, either the AutoDeployer, or ReiserFS is broken.
If this is something that the AutoDeployer should fix, a simple delay
wouldn't guarantee anything, the network could be slow, just to mention one
possible situation.
One simple solution comes to mind: If ZipException causes deployment to
fail; wait; retry. Repeat until OK, or a number of retries.
I have never done any patches to the source-code before, so unless someone
asks me, I won't give it a try....
Åsmund Hjulstad
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
