This has been fixed in 4.0.31:
As a temporary work-around, you can remove
expand-preserve-fileset="WEB-INF/work/**" from your resin.xml. But that
will remove all compiled JSP causing them to be recompiled even if they
have not changed in the new war.
On Wed, Sep 12, 2012 at 7:30 AM, Mattias Jiderhamn <
> We're in the process of setting up a new server and have installed Resin
> 4.0.29 from RPM. We have made minimal changes to the config to get up
> and running, and are facing an issue we haven't seen on any other Resin
> installation: When a .war is redeployed it seems the contents of the new
> .war is extracted, although the old content is not removed.
> This means, for example, if a JAR file is updated from foo-1.0.jar to
> foo-1.1.jar, when deployed on the new server we will have both
> foo-1.0.jar and foo-1.1.jar (and thus foo-1.0.jar will be used and this
> causes problems).
> Restarting Resin doesn't help. Once a file ends up in the expanded
> directory, I can only get rid of it by manual delete.
> Resin is currently running as root, so I can't really see how it could
> be an access issue.
> I have increased Resin logging but can't find anything abnormal in there.
> Are there any settings that can affect this?
> Anything I should look for in the log? (Any particular Resin package I
> should limit the logging to?)
> resin-interest mailing list
resin-interest mailing list