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