One workaround would be to not use Windows ;-)
I don't know if there are others, most of it should be solved by deploying a copy from the tmp directory.
Are you telling me that this is windows only issue?
And what do you mean by "deploying a copy from tmp directory"?
What does tmp directory has to do with anything here?
I am seeing that the jars are getting locked in the appName.ear directory not in the tmp directory where I would expect the jars to be locked...
Can you please provide an example of "deploying a copy from tmp"?
I mean, JBoss is already making copies of the packages to tmp to avoid file locking problems in Windows.
Yes it is generally windows only feature.
I just tried 3.2.3 on W2K and I can redeploy normally by touching the deployment descriptor file in an exploded SAR package, can also delete the directory normally.
The current JDK I'm using is 1.4.2_03-b02.
I've seen some locking problems on W2K before but haven't been able to reproduce them, also these occured on an older JDK version, I've yet to see any on this one (in case it's an issue with java.io implementation). But I haven't been using this version for long so that might explain it too.