Just so everyone knows - by and large, these problems seem to only
occur when you deploy through the filesystem. Try deploying through
the admin console or ant tasks (as is intended) and you shouldn't have
these problems :)
On 11/2/05, Malcolm Edgar <malcolm.edga..mail.com> wrote:
> I dont know. It happens with me on Windows.
>
> regards Malcolm
>
>
> On 11/3/05, Gentry, Michael (Contractor) <michael_gentr..anniemae.com>
> wrote:
> >
> > Is this a locking "feature" of Windows or does it happen on Unix, too?
> Just curious ...
> >
> >
> >
> > -----Original Message-----
> > From: Malcolm Edgar [mailto:malcolm.edga..mail.com]
> > Sent: Tuesday, November 01, 2005 7:17 PM
> > To: cayenne-use..bjectstyle.org
> > Subject: Tomcat Log4J jar locking
> >
> > Hi All,
> >
> > if you have had trouble Tomcat auto deploying WAR files it may be due to
> Log4J jar locking issues.
> >
> > The fix is add a anitJARLocking attribute:
> >
> > <Context
> > path="/click-cayenne"
> > docBase="${catalina.home}/webapps/click-cayenne"
> > reloadable="true"
> > antiJARLocking="true">
> >
> > </Context>
> >
> > For more details see:
> >
> >
> http://blog.exis.com/colin/archives/2005/08/23/i-put-a-spell-on-you-because-youre-mine-aka-why-is-tomcat-holding-onto-jars
> >
> > regards Malcolm Edgar
> > http://click.sourceforge.net
> >
> >
>
>
This archive was generated by hypermail 2.0.0 : Fri Nov 04 2005 - 16:38:17 EST