----------------------------------------------------------------
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 11:21:51 AM Eastern Daylight Time, 
[EMAIL PROTECTED] writes:

<< I have a servlet which takes a while the first time it is invoked. It
 then caches a lot of information and all subsequent runs are
 significantly faster.
 
 I am trying to find a way in which I can "Pre Load" the servlet as soon
 as it comes up so that the first user does not have to wait for a long
 time. My initial thought was that as soon as I start Apache I can hit
 the servlet with one of those messages which will then load everything.
 But this will not work in a load balanced setup because I dont know
 which JServ my message goes to. Suppose I have N number of load balanced
 JServ's then how many messages do I have to send to the servlet to
 guarantee that all my JServ's have been properly initialized? Is there
 any way I can control which JServ I am taking to in this scenario?
 
 I would guess that this should be a pretty common problem. Any ideas of
 how people do this kind of a thing? Any help would be greatly
 appreciated and would help me a lot.
 
 Thanks,
 Anupam
  >>

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>


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]

Reply via email to