> From: Scott Eade <[EMAIL PROTECTED]>
> 
> The three environments each have their own jvm however they are connected
> via mod_webapp to the same apache instance.
> 
> I am currently of the belief that mod_webapp, or at least the configuration
> of mod_webapp at my host provider, is contributing to the problem as its
> logs show that for each environment it attempts to initialise the servlet
> context for every context defined to it (i.e. For all sites on the same
> host).  While this is mostly harmless (except perhaps from a security point
> of view) it seems fairly disastrous when the same context name is used by
> more than one site as happens to be the case here (for two of my
> environments anyway).  I am in the process of changing the sites so that
> they each have a unique context name in order to test this theory.
> 
> I say that mod_webapp may be _contributing_ to the problem because I am not
> yet convinced that this is the only problem.
> 
> I am still very interested in hearing from anyone that has experienced
> similar behaviour so that I can determine if there are any similarities
> between our environments and whether or not they cam up with a solution.
> 
> Thanks,
> 
> Scott 
> 
To close this thread off, there were two problems that were causing
additional initialisations of the turbine servlet to occur:

1. The configuration of mod_webapp at the host provider was such that
conflicts would arise of two sites used the same context name.  Short term
solution: use different context names.  Long term solution: fix mod_webapp.

2. A typo in server.xml (incorrect hostname specified in the Engine element)
for one of the sites resulted in turbine servlet being loaded twice for that
site.  Solution: fix typo.

The big clues came from looking at the tomcat/work directory which contained
extra directories for the erroneous contexts.  I also implemented an
ApplicationListener which confirmed that multiple contexts were being
loaded.

Thanks Jeff for your reply.

Cheers,

Scott


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to