On 5/6/06, David Rees [EMAIL PROTECTED] wrote:
On 5/5/06, Leon Rosenberg [EMAIL PROTECTED] wrote:
you could send the user to a waiting page, which should automatically
retry the action (via http redirect or js redirect) after some amount
of time.
On the other hand, if the waiting condition
: Greg Ward [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 04, 2006 4:20 PM
To: Tomcat Users List
Subject: Re: Limiting the number of connection threads per application
On 04 May 2006, Ken Dombeck said:
We have 2 applications installed inside the same Tomcat 5.0 instance
app1 and app2. URL app1
create a filter
Ken Dombeck wrote:
We have 2 applications installed inside the same Tomcat 5.0 instance
app1 and app2. URL app1.url.com is for app1 and app2.url.com is for
app2. Both URLs have the same ip address but still hit port 80. The
maxThreads for the connector is set to 100.
The
On 5/5/06, Leon Rosenberg [EMAIL PROTECTED] wrote:
you could send the user to a waiting page, which should automatically
retry the action (via http redirect or js redirect) after some amount
of time.
On the other hand, if the waiting condition is almost permanent your
should think about other
We have 2 applications installed inside the same Tomcat 5.0 instance
app1 and app2. URL app1.url.com is for app1 and app2.url.com is for
app2. Both URLs have the same ip address but still hit port 80. The
maxThreads for the connector is set to 100.
The problem we are experiencing is that app2
On 04 May 2006, Ken Dombeck said:
We have 2 applications installed inside the same Tomcat 5.0 instance
app1 and app2. URL app1.url.com is for app1 and app2.url.com is for
app2. Both URLs have the same ip address but still hit port 80. The
maxThreads for the connector is set to 100.
The
On 5/4/06, Ken Dombeck [EMAIL PROTECTED] wrote:
Thanks.
The problem with this solution is that the end user will then see the
SC_SERVICE_UNAVAILABLE error. The desired behavior is for the users
request to wait until a thread is freed up to process their request.
Is there way to do that?
Not
