In the past, the cases of "double loading" I've seen have all been
because an auto-loaded context (created by "AutoSetup" from the
webapps directory) was also manually loaded as a second context, i.e.
<Context path="/othercontext"
docBase="webapps/examples" ...
Each context gets its own instance of servlets. As a result,
init() is called twice, once for each context.
There isn't enough information below to tell if this is the
source of the double-loading.
Cheers,
Larry
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 08, 2001 12:32 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Double loading when loading servlet on startup
>
>
> Got the same problem :(((((( (on v3.2.3 - NT)
>
> -----Message d'origine-----
> De : Alexander Cherinko [mailto:[EMAIL PROTECTED]]
> Envoye : mercredi 8 aout 2001 16:38
> A : [EMAIL PROTECTED]
> Objet : Double loading when loading servlet on startup
>
>
> Hi
> problem is that when I mark servlets as load-on-startup they
> are loaded
> twice in jvm.
> I want this servlet to serve as initializer i.e. to
> initialize some other
> classes in its init method.
> The worst is that that classes are double loaded too. I.e. I
> want to init
> class which is Thread subclass to perform periodical custom action. As
> result I have double threads running in jvm and making the
> same things! That
> was obviousely not my real intention.
> From the other hand when I launch that initializer from
> common servlet (not
> loaded on startup) the problem is not present.
> The most strange thing about it is that in both cases all
> classes are loaded
> with the same ClassLoader.
> I cannot understand is it a bug or just I don't understand something.
> Please help.
> --Che
>
