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 application doesn't it?
but is there a possibility for us to use mod_jk instead
of mod_proxy for load balancing? I read mod_proxy was quite new when 2.2.3
was released and is this issue related to mod_proxy rather than Apache
Server as a whole? I definitely can think of upgrading Tomcat.
If you want to use mod_proxy, you definitely need to upgrade HTTPD.
If you can't upgrade HTTPD, how are you going to compile mod_jk?
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?
If that's your requirement then your should think long and hard about
how to tell the people setting the requirement that you need to upgrade
your software.
Tying one hand behind your back isn't a good way to start.
1x HTTPD and 5x Tomcat might be enough, but it's not going to depend on
the server software, it's going to depend on your application and the
hardware you're running on.
Your config suggests that you're running this on one server, how much
memory is available and how many processors does it have?
p
Regards
Pid Ster wrote:
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 was released on 14 May 2007, you should definitely upgrade
to the latest version.
Please let us know if the upgraded applications still display the same
problem.
p
Apache is configured to serve the certificates and the request is
actually
being processed
by 3 tomcat instances (TomcatA, TomcatB, TomcatB)running behind. We are
getting a strange log in apache
[error] ajp_read_header: ajp_ilink_receive failed
[error] (120006)APR does not understand this error code: proxy: read
response failed from (null) (localhost)
I have another question like, when Apache forwards a http/https request
to
tomcat and suppose that tomcat takes too long to respond! will the same
request be routed to a different tomcat??
As we have not configured sticky sessions in Apache, We are having many
instances where in the java application in TomcatA takes too long (throws
exception because it waits to connect to another host which takes too
long)
in responding back to Apache and I can see logs in other tomcats, say
TomcatB and TomcatC with a session Id xxxxxxxxxxxxxxxxxxxxx.NodeA, with
empty body which throws exceptions in my application level, why does this
occur and can this be eliminated?? I am not sure that this occurs only
for
https request where we get empty body.
Apache configurations are as follows
<Proxy balancer://tomcatcluster>
Order deny,allow
Allow from all
BalancerMember ajp://localhost:8109/test route=NodeA
BalancerMember ajp://localhost:8209/test route=NodeB
BalancerMember ajp://localhost:8309/test route=NodeC
</Proxy>
ProxyPass /test balancer://tomcatcluster lbmethod=byrequests
nofailover=On
ProxyPassReverse /test ajp://localhost:8109/test
ProxyPassReverse /test ajp://localhost:8209/test
ProxyPassReverse /test ajp://localhost:8309/test
Thanks in advance.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
