When it redeployed did it try to use
122.cactus.jar instead of 123.cactus.jar or
whatever the next number was?
If so, it is a bug.
You might want to post web questions in the http
forum in future?
Me too facing the same problem. Can any one suggest the configuration for the same.
Awaiting your reply.
Regarding the first reply, I'm not sure which one it was referencing, as I cleared out the tmp directory before I had a chance to look.
Though, I did upgrade to Java 1.4 (j2se && j2ee) and that solved the problem! Also, I found that for development, deploying all of my apps/jars/etc as flat files and directories solved many of my problems in this regard.