All,
I'm not sure exactly when this started happening, but now reloads cause
all my load-on-startup servlets classes to cause the following errors:
2003-10-25 11:57:14 StandardContext[/diagnosis]: Servlet /diagnosis
threw load() exception
javax.servlet.ServletException: Wrapper cannot find
Hi:
Just a blind shot (I've not used Struts yet).
Do these load-on-startup servlets require anything to be initialized in struts
?
Does Struts require initialization by the web app developer ? If so, perhaps
you need to somehow ensure that such initialization takes place before you load
your
Christopher Schultz wrote:
I'm not sure exactly when this started happening, but now reloads cause
all my load-on-startup servlets classes to cause the following errors:
Let me guess: You're running 4.1.27, right? Make sure you've applied
the hotfix.
-Dave
Your load on startup is in your applications web.xml file?
Are you saying it works fine the first time you start Tomcat? If so,
then maybe it doesn't get shutdown propertly, when you restart. Or do you
mean just reloading the application?
There's supposed to be a patch to Tomcat for fixing
Oscar,
Your load on startup is in your applications web.xml file?
Yes.
Are you saying it works fine the first time you start Tomcat? If so,
then maybe it doesn't get shutdown propertly, when you restart. Or do you
mean just reloading the application?
No, everything works okay when I start
Sriram,
Does Struts require initialization by the web app developer ? If so, perhaps
you need to somehow ensure that such initialization takes place before you load
your servlets ?
The first tim I load the web app (i.e. on Tomcat startup) everything
works fine. It's only after a webapp re-load
David,
Let me guess: You're running 4.1.27, right?
Yep, that would be the version (apologies for not giving that in the
first place).
Make sure you've applied the hotfix.
Stupid question: where can I download this fix? The tomcat download page
doesn't give any indication that there's a fix.
All,
Let me guess: You're running 4.1.27, right? Make sure you've applied
the hotfix.
Got the hotfix, installed it, all better now.
Thanks everyone for your patience and help. I'm sure a lot of people do
what I just did and ask for help without doing enough research. :(
-chris
Christopher Schultz wrote:
Let me guess: You're running 4.1.27, right?
Yep, that would be the version (apologies for not giving that in the
first place).
Make sure you've applied the hotfix.
Stupid question: where can I download this fix? The tomcat download page
doesn't give any indication
David Rees wrote:
Something needs to be done about making it known that the hotfix is
available!
Opened a bug: http://issues.apache.org/bugzilla/show_bug.cgi?id=24121
-Dave
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Christopher Schultz wrote:
Got the hotfix, installed it, all better now.
Thanks everyone for your patience and help. I'm sure a lot of people do
what I just did and ask for help without doing enough research. :(
Well, the hotfix should be easier to find, so you can't entirely blame
yourself.
Agreed. If you only look in the directory that apache.org links to, you'll
see the main download but you won't see the hotfix. Only if you click on
the binaries folder will you see it.
I now mention it on my HOWTO page:
http://daydream.stanford.edu/tomcat/install_web_services.html
Maybe others
12 matches
Mail list logo
