RE: Caching Problem?

Restarting multiserver seems to have fixed the problem. I probably should've
thought of that earlier!

--
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 Charles Rector
> Sent: Thursday, November 14, 2002 3:01 PM
> To: enhydra@xxxxxxxxxxx
> Subject: Enhydra: Caching Problem?
>
>
> Recently I have been unable to access certain pages on my site
> (Enhydra 5.0
> "application"), and after examining classload debugging logs I found the
> following exception when multiserver was trying to pull up the offending
> pages:
>
> 2002.11.14 14:06:08: pcp,DEBUG: RID:12: exception running
> presentation/admin/customer_internet_add.po:
> de/opus5/servlet/MultipartRequest
> 2002.11.14 14:06:08: pcp,DEBUG+ java.lang.NoClassDefFoundError:
> de/opus5/servlet/MultipartRequest
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> pcp.presentation.FormWizard.run(FormWizard.java:126)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> com.lutris.appserver.server.httpPresentation.HttpPresentationManag
> er.runPres
> entationObj(Unknown Source)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> com.lutris.appserver.server.httpPresentation.HttpPresentationManag
> er.Run(Unk
> nown Source)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> com.lutris.appserver.server.httpPresentation.servlet.HttpPresentat
> ionServlet
> .serviceDirect(Unknown Source)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> com.lutris.appserver.server.httpPresentation.servlet.HttpPresentat
> ionServlet
> .service(Unknown Source)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> org.apache.tomcat.core.ServiceInvocationHandler.method(Unknown Source)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> org.apache.tomcat.core.ServletWrapper.handleInvocation(Unknown Source)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> org.apache.tomcat.core.ServletWrapper.handleRequest(Unknown Source)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> org.apache.tomcat.core.Context.handleRequest(Unknown Source)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> org.enhydra.servlet.servletManager.ServletManager.service(Unknown Source)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> org.enhydra.servlet.connectionMethods.http.HttpHandler.doARequest(Unknown
> Source)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> org.enhydra.servlet.connectionMethods.http.HttpHandler.processRequ
> ests(Unkno
> wn Source)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> org.enhydra.servlet.connectionMethods.http.HttpHandler.run(Unknown Source)
> 2002.11.14 14:06:08: pcp,DEBUG+         at
> java.lang.Thread.run(Thread.java:536)
>
> These pages had come up just fine previously, so I made the
> rounds checking
> the conf file to make sure the multipart jar was present, and even checked
> the jar itself to make sure the MultipartRequest.class was present at the
> correct location, which it was. Having no luck on that front, a fellow
> employee suggested I try a different multipart library, of the
> com.oreilly.servlet flavor. I grabbed it, set everything up and
> deployed the
> site again only to find that the same pages were still dying.
> Upon examining
> classload debugging logs again, I found the same exact exception
> as before,
> which refers to the de.opus5.servlet package!
>
> Obviously something stale is still being referenced, but I have
> no idea why.
> Apparently around the same time these pages started dying, my
> tester for the
> site tried bringing the site up one day only to get that
> Internal-Servlet-Error-500-ClassCastException-thing (I've
> mentioned this in
> previous posts). As I was not around at the time, he got another
> employee to
> look at it, who changed the conf file's Server.AutoReload value
> from 'true'
> to 'false', which apparently fixed the problem. But then of
> course, certain
> pages not coming up due to the exception above was halting
> serious testing.
>
> Does this sound familiar to anyone? I've had nowhere near this amount of
> trouble with any other site I've developed with Enhydra, it's really
> frustrating. If it's of any use, I believe the site was originally created
> under JB5, but I am now using JB7. I have been deploying from JB7 for
> several weeks without hitch, though.
>
> --
> 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
>