Hi I'm experiencing odd failures when a servlets init procedure is called for a second time. What I *think* is happening is that Tomcat is deactivating the servlet (as it is allowed to do) but some of the singleton objects created by the servlet initialisation routine are not being culled at the same time. As a result, when Tomcat receives a request for this servlet and starts to re-load it, my servlet is falling over when it tries to create objects that already exist. Obviously this is a logic problem with my servlet rather than with Tomcat but so that I can test my theory (and soloution), how can I "force" tomcat to drop my servlet and reload it under controlled conditions without re-loading the entire web-app? Reloading the entire application through the manager doesn't appear to exhibit the problem.
Regards Roger __________________________________________________________________________ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. __________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
