You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/11/07 08:49:39 UTC
DO NOT REPLY [Bug 14329] New: -
load-on-startup ignored at StandardHost level
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14329>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14329
load-on-startup ignored at StandardHost level
Summary: load-on-startup ignored at StandardHost level
Product: Tomcat 4
Version: 4.0.4 Final
Platform: PC
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: david.dawkins@brooks-pri.com
OK, well it's not ignored, but *seems* to be applied in the wrong place.
My apologies are offered in advance if I have misunderstood the purpose
of <load-on-startup>N</load-on-startup>.
Please see the attached log file. The two servlets that I am interested
in are "tibgateway" and "configlet". "configlet" has a load-on-startup
value of 1 and tibgateway has a load-on-startup value of 2; yet configlet
gets loaded after tibgateway (sometimes it gets loaded the other way
around).
I added some trace code to core/StandardContext.java and core/StandardHost.java
to produce the log file, and it seems that load-on-startup is taken into
account, but only between internal (?) servlets local to each application
servlet; so, while loading configlet, the servlets ConfigServlet,
DefaultServlet, InvokerServlet and JspServlet are loaded according to
load-on-startup.
It feels as if StandardHost.install() needs to load all its children,
and sort before calling start(), but I'm no expert in this code.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>