-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To whom it may concern,
On 3/4/2010 12:34 AM, jkv wrote:
We have a eye popping requirement to handle 15000 concurrent https users
simultaneously, an I am not sure a single Apache Server and five Tomcat
instances (what we now have) can take this?
Thanks for the reply Ster,
Find someone who does., sorry when I said privilege I actually meant
option, that is I cannot install a new Apache over the older 2.2.3 and we
have to go with the default configuration. Because they have chosen RHEL 5.4
as the platform and it comes with 2.2.3 version,
On 05/03/2010 08:01, jkv wrote:
Thanks for the reply Ster,
Find someone who does., sorry when I said privilege I actually meant
option, that is I cannot install a new Apache over the older 2.2.3 and we
have to go with the default configuration. Because they have chosen RHEL 5.4
as the platform
On 04/03/2010 05:34, jkv wrote:
Thanks for the reply Ster,
But we don't have the privilege to upgrade Apache,
Find someone who does.
because we are using Red
Had Enterprise Linux and we have to go with the default httpd installation
in it, i.e., 2.2.3,
Why? RHEL has a built-in updater
Thanks for the reply Ster,
But we don't have the privilege to upgrade Apache, because we are using Red
Had Enterprise Linux and we have to go with the default httpd installation
in it, i.e., 2.2.3, but is there a possibility for us to use mod_jk instead
of mod_proxy for load balancing? I read
On 26/02/2010 06:36, jkv wrote:
We are using the above setup to load balance http and https request, for
https request
Apache HTTPD 2.2.3 was released on 28 Jul 2006, you should definitely
upgrade to the latest version, there have been *many* important updates
since then.
Tomcat 6.0.13
