> From: "Brekke, Jeff" <[EMAIL PROTECTED]> > > I've run into a similar situation with testing the turbine servlet. > The servlet is attempting to behave like a singleton. Therefore you cannot > 'unload/destroy' the servlet and re-init. In testing this becomes very > painful. For the integration unit tests in t3 I added the ability to > re-init the turbine servlet but this didn't work with t2 and the way > services are initialized ( > http://cvs.apache.org/viewcvs/jakarta-turbine-3/src/java/org/apache/turbine/ > Turbine.java?rev=1.35&content-type=text/vnd.viewcvs-markup ). > > Maybe something wrt this semi-singleton behavior is related to these issues? > Seems strange, should only matter if the turbine objects are in the same > jvm. Are they?
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 unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
