RE: Possible Caching Problem Solution

Terry,

Yep, they all get deposited in the same location. What I think I'll be doing
now is setting up my ant buildfile to remove any existing jars from the lib
folder and maybe back them up somewhere else prior to uploading the new one.

I would be interested to know why it might be undesirable to have multiple
jars in the lib folder, since it clearly has been a problem for me. If it's
looking at all of the files in the lib folder, I would think that would be
counterintuitive to having to specify which jar to use in the conf file in
the first place. Like I had mentioned, I no longer was referencing the older
jar files anywhere explicitly. Peculiar stuff!

--
Chuck Rector
Internet Exposure, Inc.
http://www.iexposure.com
crector@xxxxxxxxxxxxx

Web Development - Web Marketing - ISP Services
(612) 676-1946

> -----Original Message-----
> From: enhydra-admin@xxxxxxxxxxx [mailto:enhydra-admin@xxxxxxxxxxx]On
> Behalf Of Terry Steichen
> Sent: Monday, November 18, 2002 4:05 PM
> To: enhydra@xxxxxxxxxxx
> Subject: Re: Enhydra: Possible Caching Problem Solution
>
>
> Charles,
>
> Were the old jar files in the lib directory?
>
> Terry
>
> ----- Original Message -----
> From: "Charles Rector" <crector@xxxxxxxxxxxxx>
> To: <enhydra@xxxxxxxxxxx>
> Sent: Monday, November 18, 2002 3:17 PM
> Subject: Enhydra: Possible Caching Problem Solution
>
>
> > Interesting thing. Recently my site started dying all over the place
> again,
> > and setting CLASSLOAD debugging showed me that it was dying because it
> > couldn't find the com.oreilly.servlet.FileRenamePolicy class. Earlier I
> was
> > using de.opus5.servlet and it would die because it couldn't find the
> > de.opus5.servlet.MultipartRequest class.
> >
> > I had written an ErrorHandler page just to be neat and tidy,
> but when the
> > lion's share of my pages stopped coming up I decided to remove the
> > ErrorHandler so I could see any exceptions that were being thrown (this
> was
> > before I tried CLASSLOAD debugging info). So I removed the page, and
> > redeployed. I tried accessing a couple pages again and was surprised to
> find
> > that my ErrorHandler page was still coming up for all of them! I checked
> the
> > jar. Not in there. I resaved and restarted the application in the
> > multiserver admin. Didn't help. I restarted multiserver itself. No go.
> >
> > Then I thought about where it could possibly be getting all
> this old code
> > from. That's when I realized we have several older jars from past
> > deployments lying around (because of classloading problems in
> the past, we
> > don't deploy the same app.jar file each time; we deploy
> app-2002-01-01.jar,
> > app-2002-01-02.jar, etc.). Perhaps some of you also do this? At
> any rate,
> > when I removed all the older jars, and THEN restarted multiserver, the
> site
> > started working again. Really weird! None of the old jars were
> referenced
> > anywhere in the conf files. Perhaps multiserver keeps some internal
> record?
> >
> > --
> > Chuck Rector
> > Internet Exposure, Inc.
> > http://www.iexposure.com
> > crector@xxxxxxxxxxxxx
> >
> > Web Development - Web Marketing - ISP Services
> > (612) 676-1946
> >
> > _______________________________________________
> > Enhydra mailing list
> > Enhydra@xxxxxxxxxxx
> > http://www.enhydra.org/mailman/listinfo.cgi/enhydra
> >
>
> _______________________________________________
> Enhydra mailing list
> Enhydra@xxxxxxxxxxx
> http://www.enhydra.org/mailman/listinfo.cgi/enhydra
>