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
