----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
In a message dated 9/6/00 1:27:26 PM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
<< > I believe adding this to your zone.properties file will answer your
need.
It
> causes the servlet to be started when JServ starts up.
>
> servlets.startup=<servlet name here>
Actually, this does answer the question for such things as servlets which
are connection pool managers. Loading the servlet at startup does not
initialize the connections to the DB and the wait is still there. I
attempted to do this with a connection pool but it made no difference to
have initialized at startup or not. Maybe that has something to do with how
the servlet is written; I have no idea, being the admin and not the
programmer. Erik Kleing may be having the same problem: the initialization
on startup does not really speed up certain functionality which requires an
actual request for the servlet through http?
Ben Ricker
Web Administrator
US-Rx, Inc. >>
Ben is correct (as he tends to be) in that the startup servlet does not
actually process a HTTP request, which may be what is needed, depending upon
the implementation.
I have successfully used this approach for exactly what Ben references ....
as a database connection pool manager (factory) which allocates and
deallocates DB connections to/from servlet threads as requested.
In my experience with this, the JDBC database connections are instantiated
immediately after the JServ engine starts and they are held until HTTP
requests are processed by other servlets which ask the DB factory for a DB
connection. This saves time by not creating the DB connection when the HTTP
request comes in. This is also an appropriate time to do any type of "static
data loading" (which may be time consuming) that could again be shared by
HTTP servlet requests. This was my understanding of the original author's
requirement.
Erik Klein
Versatile Consulting, Inc.
621 Lovett Road
Colts Neck, NJ 07722
732-936-0573
mailto:[EMAIL PROTECTED]
http://members.aol.com/ErikKlein
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search Archives:
<http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]