concern about Apache + mod_jk + Tomcat cluster

2003-01-15 Thread YOU, JERRY (SBCSI)
Hi,
I installed the Apache1.3.27, mod_jk1.2.1 and Tomcat4.1.18 recently on our
Solaris6 machine. The approach is that let 1 apache as web server dispatches
requestes to the 3 tomcat server instances. There is no error in the
configuration, 
and install. But when I was load-testing the application, I noticed that
there were
lots of error message shown in the mod_jk file, although all the requests
were
dispatched to the tomcat servers and responded with 200.

I then changed the 3 tomcat servers' configure as following:
Connector className=org.apache.ajp.tomcat4.Ajp13Connector
   port=11009 minProcessors=1 maxProcessors=1
   acceptCount=10 debug=1/
So now every Tomcat can only accept 1 request at the same time.
I then sent 3 concurrent requests to the cluster: tomcat21, tomcat22,
tomcat23.
From the debug/log file, I think the mod_jk and tomcats are working like :
1, 3 requests reaches mod_jk, mod_jk sends requests to tomcat21
2, tomcat21 accepts the first one and rejects the other 2,
3, mod_jk logs errors in mod_jk.log, reports the tomcat is down or network
problem.
4, mod_jk then sends the 2 to tomcat22
5, tomcat22 accepts 1 and rejects the other.
6, mod_jk again logs errors.
7. mod_jk sends the alst one to tomcat23,
8, tomcat 23 accepts it.

I think there is nothing wrong with this procedure, but besides the annoying
error messages,
the whole performance is poor due to the time spent in the probes. I also
suspect that
the socket connection in Solaris6 is too slow, for some reason.

I have questions for those who have the tomcat cluster in there production
site:
how about the performance in your site? Is there anything wrong with my
configuration or should
I use JK2 to improve performance?

The configuration files and log files are attached with this email.

OS: Solaris 6
Apache1.3.27, Tomcat 4.1.18, mod_jk1.2.1( I can not find the binary mod_jk
at the apache.org site
under solaris6 directory, so, I download the one in Solaris8 dir).

Thanks,

Jerry You tomcat_23_catalina.log  the_change_to_httpd.conf  
workers.properties  change_to_tomcat21_server.xml  
tomcat_21_catalina.log  tomact_22_catalina.log 



tomcat_23_catalina.log
Description: Binary data


the_change_to_httpd.conf
Description: Binary data


workers.properties
Description: Binary data


change_to_tomcat21_server.xml
Description: Binary data


tomcat_21_catalina.log
Description: Binary data


tomact_22_catalina.log
Description: Binary data
--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]


Re: concern about Apache + mod_jk + Tomcat cluster

2003-01-15 Thread Julian Löffelhardt
Hi,

Make sure you have set the MaxProcessors property of the AJP13 Connector  in
server.xml to an equal or higher value as specified in MaxClients of the
httpd.conf.

llap,
julian
- Original Message -
From: YOU, JERRY (SBCSI) [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, January 15, 2003 6:04 PM
Subject: concern about Apache + mod_jk + Tomcat cluster


 Hi,
 I installed the Apache1.3.27, mod_jk1.2.1 and Tomcat4.1.18 recently on our
 Solaris6 machine. The approach is that let 1 apache as web server
dispatches
 requestes to the 3 tomcat server instances. There is no error in the
 configuration,
 and install. But when I was load-testing the application, I noticed that
 there were
 lots of error message shown in the mod_jk file, although all the requests
 were
 dispatched to the tomcat servers and responded with 200.

 I then changed the 3 tomcat servers' configure as following:
 Connector className=org.apache.ajp.tomcat4.Ajp13Connector
port=11009 minProcessors=1 maxProcessors=1
acceptCount=10 debug=1/
 So now every Tomcat can only accept 1 request at the same time.
 I then sent 3 concurrent requests to the cluster: tomcat21, tomcat22,
 tomcat23.
 From the debug/log file, I think the mod_jk and tomcats are working like :
 1, 3 requests reaches mod_jk, mod_jk sends requests to tomcat21
 2, tomcat21 accepts the first one and rejects the other 2,
 3, mod_jk logs errors in mod_jk.log, reports the tomcat is down or network
 problem.
 4, mod_jk then sends the 2 to tomcat22
 5, tomcat22 accepts 1 and rejects the other.
 6, mod_jk again logs errors.
 7. mod_jk sends the alst one to tomcat23,
 8, tomcat 23 accepts it.

 I think there is nothing wrong with this procedure, but besides the
annoying
 error messages,
 the whole performance is poor due to the time spent in the probes. I also
 suspect that
 the socket connection in Solaris6 is too slow, for some reason.

 I have questions for those who have the tomcat cluster in there production
 site:
 how about the performance in your site? Is there anything wrong with my
 configuration or should
 I use JK2 to improve performance?

 The configuration files and log files are attached with this email.

 OS: Solaris 6
 Apache1.3.27, Tomcat 4.1.18, mod_jk1.2.1( I can not find the binary mod_jk
 at the apache.org site
 under solaris6 directory, so, I download the one in Solaris8 dir).

 Thanks,

 Jerry You tomcat_23_catalina.log  the_change_to_httpd.conf
 workers.properties  change_to_tomcat21_server.xml
 tomcat_21_catalina.log  tomact_22_catalina.log







 --
 To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
 For additional commands, e-mail:
mailto:[EMAIL PROTECTED]


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: concern about Apache + mod_jk + Tomcat cluster

2003-01-15 Thread Ben Ricker
Can you post the workers.properties file? I use equal lblweight (I think
that is the name of the property) set to 100 for the 4 Tomcat instances.

I have a nearly identical setup: twp Apache 1.3.27 server running on
Redhat 7.3 load balancing across 4.0.6 Tomcat instances running on two
Solaris 8 servers. We have no performance issues and I am using the
default Processor settings in server.xml. We go through roughly 1
million hits a month.

HTH,

Ben Ricker

On Wed, 2003-01-15 at 11:04, YOU, JERRY (SBCSI) wrote:
 Hi,
 I installed the Apache1.3.27, mod_jk1.2.1 and Tomcat4.1.18 recently on our
 Solaris6 machine. The approach is that let 1 apache as web server dispatches
 requestes to the 3 tomcat server instances. There is no error in the
 configuration, 
 and install. But when I was load-testing the application, I noticed that
 there were
 lots of error message shown in the mod_jk file, although all the requests
 were
 dispatched to the tomcat servers and responded with 200.
 
 I then changed the 3 tomcat servers' configure as following:
 Connector className=org.apache.ajp.tomcat4.Ajp13Connector
port=11009 minProcessors=1 maxProcessors=1
acceptCount=10 debug=1/
 So now every Tomcat can only accept 1 request at the same time.
 I then sent 3 concurrent requests to the cluster: tomcat21, tomcat22,
 tomcat23.
 From the debug/log file, I think the mod_jk and tomcats are working like :
 1, 3 requests reaches mod_jk, mod_jk sends requests to tomcat21
 2, tomcat21 accepts the first one and rejects the other 2,
 3, mod_jk logs errors in mod_jk.log, reports the tomcat is down or network
 problem.
 4, mod_jk then sends the 2 to tomcat22
 5, tomcat22 accepts 1 and rejects the other.
 6, mod_jk again logs errors.
 7. mod_jk sends the alst one to tomcat23,
 8, tomcat 23 accepts it.
 
 I think there is nothing wrong with this procedure, but besides the annoying
 error messages,
 the whole performance is poor due to the time spent in the probes. I also
 suspect that
 the socket connection in Solaris6 is too slow, for some reason.
 
 I have questions for those who have the tomcat cluster in there production
 site:
 how about the performance in your site? Is there anything wrong with my
 configuration or should
 I use JK2 to improve performance?
 
 The configuration files and log files are attached with this email.
 
 OS: Solaris 6
 Apache1.3.27, Tomcat 4.1.18, mod_jk1.2.1( I can not find the binary mod_jk
 at the apache.org site
 under solaris6 directory, so, I download the one in Solaris8 dir).
 
 Thanks,
 
 Jerry You tomcat_23_catalina.log  the_change_to_httpd.conf  
 workers.properties  change_to_tomcat21_server.xml  
 tomcat_21_catalina.log  tomact_22_catalina.log 
 
 __
 
 --
 To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]
-- 
Ben Ricker [EMAIL PROTECTED]
Wellinx.com


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: concern about Apache + mod_jk + Tomcat cluster

2003-01-15 Thread YOU, JERRY (SBCSI)
Here is the workers.properties.
One thing to note is that I downloaded the mod_jk from
apache.org. I can only find binary mod_jk_1.3_eapi.so 
(and no_eapi.so) from Solaris8 directory. So, I use it
on Solaris6 system.
Also, all the servers including apache, tomcats are
running on the same machine (5G mem).
I use the grinder http://grinder.sourceforge.net/ 
as load testing tool.

Thanks,

Jerry You
-Original Message-
From: Ben Ricker [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 15, 2003 12:54 PM
To: '[EMAIL PROTECTED]'
Subject: Re: concern about Apache + mod_jk + Tomcat cluster


Can you post the workers.properties file? I use equal lblweight (I think
that is the name of the property) set to 100 for the 4 Tomcat instances.

I have a nearly identical setup: twp Apache 1.3.27 server running on
Redhat 7.3 load balancing across 4.0.6 Tomcat instances running on two
Solaris 8 servers. We have no performance issues and I am using the
default Processor settings in server.xml. We go through roughly 1
million hits a month.

HTH,

Ben Ricker

On Wed, 2003-01-15 at 11:04, YOU, JERRY (SBCSI) wrote:
 Hi,
 I installed the Apache1.3.27, mod_jk1.2.1 and Tomcat4.1.18 recently on our
 Solaris6 machine. The approach is that let 1 apache as web server
dispatches
 requestes to the 3 tomcat server instances. There is no error in the
 configuration, 
 and install. But when I was load-testing the application, I noticed that
 there were
 lots of error message shown in the mod_jk file, although all the requests
 were
 dispatched to the tomcat servers and responded with 200.
 
 I then changed the 3 tomcat servers' configure as following:
 Connector className=org.apache.ajp.tomcat4.Ajp13Connector
port=11009 minProcessors=1 maxProcessors=1
acceptCount=10 debug=1/
 So now every Tomcat can only accept 1 request at the same time.
 I then sent 3 concurrent requests to the cluster: tomcat21, tomcat22,
 tomcat23.
 From the debug/log file, I think the mod_jk and tomcats are working like
:
 1, 3 requests reaches mod_jk, mod_jk sends requests to tomcat21
 2, tomcat21 accepts the first one and rejects the other 2,
 3, mod_jk logs errors in mod_jk.log, reports the tomcat is down or network
 problem.
 4, mod_jk then sends the 2 to tomcat22
 5, tomcat22 accepts 1 and rejects the other.
 6, mod_jk again logs errors.
 7. mod_jk sends the alst one to tomcat23,
 8, tomcat 23 accepts it.
 
 I think there is nothing wrong with this procedure, but besides the
annoying
 error messages,
 the whole performance is poor due to the time spent in the probes. I also
 suspect that
 the socket connection in Solaris6 is too slow, for some reason.
 
 I have questions for those who have the tomcat cluster in there production
 site:
 how about the performance in your site? Is there anything wrong with my
 configuration or should
 I use JK2 to improve performance?
 
 The configuration files and log files are attached with this email.
 
 OS: Solaris 6
 Apache1.3.27, Tomcat 4.1.18, mod_jk1.2.1( I can not find the binary mod_jk
 at the apache.org site
 under solaris6 directory, so, I download the one in Solaris8 dir).
 
 Thanks,
 
 Jerry You tomcat_23_catalina.log  the_change_to_httpd.conf  
 workers.properties  change_to_tomcat21_server.xml  
 tomcat_21_catalina.log  tomact_22_catalina.log 
 
 __
 
 --
 To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
 For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
-- 
Ben Ricker [EMAIL PROTECTED]
Wellinx.com


--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]




workers.properties
Description: Binary data
--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]