OK my knowledge was weak and I am also not an expert on TC internals.
But pipelining makes only sense when the requests could be useful parallel
processed (e.g. CPU intensive and more CPU's available) and do not depend on
each other.
The responses must be delivered anyhow in incoming sequence.
A
AFAIK the "pipeline length" cannot be more than one by design.
No client will send another request before it received the response from the
last.
And so TC will also not accept another request before it processed the last
Karl-Heinz
- Original Message -
From: "Feng Xie (fxie)" <[EMAIL
Have you checked the tomcat/mod_jk logs (catalina,localhost)?
And only to be sure... have you checked the modification dates of your
apache/mod_jk config files?
of course you have tried restarting tomcat and apache?
I have done a quick check and it seems ok. The front page of the site is ju
I think the http protocol does not allow the parallel processing of requests
using a single connection.
At least the response of a following request cannot pass the
predecessor on the same connection.
(How could the responses be matched to the requests?)
So parallel processing is not really usefu
le virtual hosts
That seems to have been the solution! Thanks very much.
Is this documented anywhere in the official Tomcat documentation?
-Original Message-
From: charly [mailto:[EMAIL PROTECTED]
Sent: 11 June 2005 10:08
To: Tomcat Users List
Subject: Re: Managing automatic deployment
Hello,
have you tried naming the war files
"ROOT.war"??
Because I think there is a special naming convention for the root context.
This means if you have different applications you need to deploy them into
different folders.
Karl-Heinz
- Original Message -
From: "Ben Rometsch" <[EMAI
o: "Tomcat Users List"
Sent: Friday, June 03, 2005 6:33 AM
Subject: Re: when web.xml changes webapp does not reload if not in webapps ..
On 6/3/05, charly <[EMAIL PROTECTED]> wrote:
For example if I change web.xml of "manager" the manager webapp will not
automatically
Hello,
Sorry I forgot something.
How should I configure a webapp which is not located in
${catalina.base}/webapps/ that it will reload when I change its web.xml.
For example if I change web.xml of "manager" the manager webapp will not
automatically reload.
Adding "WEB-INF/web.xml" or
re
Hello,
How should I configure a webapp which is not located in
${catalina.base}/webapps/ that it will reload when I change its web.xml.
For example if I change web.xml of "manager" the manager webapp will not
automatically reload.
Adding "WEB-INF/web.xml" to
${catalina.base}/conf/catal
I am currently using TC 5.0.28 & http1.1-connector and JCIFS for authentication
in a webapp. Authentication is done completely within the webapp without using
TC methods and only when necessary.
This is working quite well except for few users, who are accessing over squid
proxy, which suppresses
10 matches
Mail list logo
