check if ajp port is already in use or not.
If hte port is already in use tomcat internally increments the port by one
and starts listening to that port for requests.
In this scenario apache won't be able to forward your requests to respective
node.
kashif_tomcat wrote:
Hi All,
i am doing
Hi All,
i am doing clustering with load balance environment and got stuck with an
issue. can anyone please help me ... below is scenario.
i have two servers running tomcat 1 and 2 (running in cluster)and apache is
on server with tomcat 1.
here is load balancing entries.
Proxy
I want to use Apache to load balance client request to 2 JBoss Tomcat instance
(I use mod_jk to connect Apache and JBoss Tomcat).
I setup Apache server on one machine with IP 192.168.62.1, the 1st JBoss server
is on 192.168.62.2 and the 2nd JBoss is on 192.168.62.3.
Apache load balances very
Something isn't clear here. If you use mod_jk that means that you use
AJP connector on Tomcat side. That's not HTTP neither HTTPS.
https://192.168.62.2:8443/login.do probably works because you
configured HTTPS connectors along with AJP but did you configure
Apache to connect to those connectors?
OK. Thanks for the tip.
Kenneth Svee wrote:
[ "[EMAIL PROTECTED]" [EMAIL PROTECTED] ]
Dear all,
In our environment, we are using 1 apache server and load balanced
to 2 resin servers (all in different machines).
A snippet of our apache httpd.conf:
VirtualHost external_ip:80
[ [EMAIL PROTECTED] [EMAIL PROTECTED] ]
Dear all,
In our environment, we are using 1 apache server and load balanced
to 2 resin servers (all in different machines).
A snippet of our apache httpd.conf:
VirtualHost external_ip:80
RewriteEngine on
RewriteCond %{SERVER_PORT} ^80$
Dear all,
In our environment, we are using 1 apache server and load balanced to 2
resin servers (all in different machines).
A snippet of our apache httpd.conf:
VirtualHost external_ip:80
RewriteEngine on
RewriteCond %{SERVER_PORT} ^80$
RewriteCond %{HTTP_HOST} ^some\.domainname\.com$
