Thank you Chuck. That is exactly what I was looking for.
-------- Original Message -------- Subject: RE: Context Chicken & Egg Problem From: "Caldarale, Charles R" <chuck.caldar...@unisys.com> Date: Thu, December 10, 2009 6:24 pm To: Tomcat Users List <users@tomcat.apache.org> > From: sh...@radiantblue.com [mailto:sh...@radiantblue.com] > Subject: RE: Context Chicken & Egg Problem > > just a curiosity as to what is happening under the Tomcat > covers during this scenario. Tomcat initialization is single-thread, so if webapp A happens to get initialized before B, and the initialization thread running inside A makes an HTTP request that targets a yet-to-be initialized webapp in the same Tomcat instance, you have a deadlock. Someday maybe, we'll see multi-threaded initialization. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
