Hi,
I'm a bit confused about the documentation on the http connector. The tomcat
documentation talks about parameters such as maxProcessors rather than
maxThreads which seems to be the term used everywhere else. Are these the same
or not?
Also; The documentation on the http connector is
We dont have synchronisation issues - I've already profiled extensively with
jprofiler.. Well we did, but after using jprofiler we dont :)
Err, I think our app is the same as yours :) What im saying is that for the
same load the machine uses more cpu with 2 tomcat instances... So i guess
Dan Keeley wrote:
Hi all,
Just a quick one; It's not clear from the docs.
is %t in the accessLogValve the request datetime or the response
datetime?
It makes a difference to us!
thanks,
Dan
End of response (logging time).
Caution: for Apache httpd 2.x it's start of request.
Thats great
Hi all,
Just a quick one; It's not clear from the docs.
is %t in the accessLogValve the request datetime or the response datetime?
It makes a difference to us!
thanks,
Dan
-
To start a new topic, e-mail:
Hi all,
Just a quick one; It's not clear from the docs.
is %t in the accessLogValve the request datetime or the response datetime?
It makes a difference to us!
thanks,
Dan
-
To start a new topic, e-mail:
Filipe David Manana wrote:
1) Is Tomcat reliable for a production environment, where client requests
can be in the order of a few thousands per hour?
Easily.
Is it fair to say that with load balancing through apache or similar, if you
spread out your app servers you can go up virtually any
