True, I did ask for a reference, for the specific issue of http requests out of a webapp to another webapp in the same container "during initialization," causing a halt condition.
So either I am just not able to adequately describe what I am seeing, nobody has dealt with this issue, or I am completely missing the forest through the trees via the information you are providing. -Scot -----Original Message----- From: Pid [mailto:p...@pidster.com] Sent: Thursday, December 10, 2009 11:26 AM To: Tomcat Users List Subject: Re: Context Chicken & Egg Problem On 10/12/2009 16:14, Scot Hatt wrote: > So you are saying that a normally available Servlet interface that is > implemented correctly and functions properly in production mode has > something to do with Tomcat contexts being available during a peer context's > deployment? That's a heck of an extrapolation. You asked about a reference, the Servlet Spec is the best one. I've found it helpful when I couldn't get Tomcat to behave how I wanted it to. p > -Scot > > -----Original Message----- > From: Pid [mailto:p...@pidster.com] > Sent: Thursday, December 10, 2009 10:52 AM > To: Scot Hatt > Subject: Re: Context Chicken& Egg Problem > > On 10/12/2009 15:32, Scot Hatt wrote: >> Thank you for the response. >> >> I understand the limitation I am up against and it is not a production > level >> issue that I have to get around. I have a local VM, as I stated, that > solves >> the issue and as far as production, everything is separate. >> >> I was curious if there is a specific reference on this problem that I can >> point to for my fellow devs that try to run everything on a single Tomcat >> instance. > > The Servlet Spec? The popular refrain here is that "it's surprisingly > readable". > > > p > > >> -Scot >> >> -----Original Message----- >> From: Pid [mailto:p...@pidster.com] >> Sent: Thursday, December 10, 2009 10:22 AM >> To: users@tomcat.apache.org >> Subject: Re: Context Chicken& Egg Problem >> >> On 10/12/2009 15:15, Scot Hatt wrote: >>> Hello, >>> >>> I have spent a great deal of time scouring the bug list and trying to put >>> together the right set of terms to find resolution for this but have been >>> unsuccessful. >>> >>> I am dealing with a situation where webapp A is calling a servlet in >> webapp >>> B during A's startup. I think I am dealing with a chicken and egg >> situation >>> where Tomcat knows it has a B context but it can't provide access yet >>> because it is still deploying A. The symptom is a complete halt of A and >>> Tomcat just sits there not responding to any requests. >>> >>> The reason for this configuration is the typical developer workstation >>> situation where I need to run everything locally. It is not a show > stopper >>> and I have gotten around it by running a VM but that is a memory hog. Is >>> there a reference to this scenario that explains why it is not possible > or >>> am I dealing with a known bug? >>> >>> -Scot in VA >> >> Web apps are intended to be independent. The startup sequence for >> contexts is sequential AFAIK, but the order isn't specific or specifiable. >> >> You have have to consider an alternative method of achieving what you > want. >> >> >> p >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
