-----Original Message-----
From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 15, 2001 2:10 PM
To: [EMAIL PROTECTED]
Subject: RE: jk_ajp13_worker.c error connecting to the tomcat process
>I am using mod_jk/ajp13 with Tomcat 3.2.1 and Apache 1.3.19
>to access an Oracle database via JSP.
>It all works fine until I use a LoadRunner to run multiple users. The
>application handles between 60-80 concurrent users, but then fails.
What happen when you do the same operation with Tomcat native
http connector ?
I have not tried native Tomcat. Do you suggest that this will make a
difference?
One thing I failed to mention earlier was that when the LoadRunner scenario
fails, Apache will
continue to serve html, but not JSPs. Also, the LoadRunner scenario is a
simulation of a user hitting
nine JSPs and running continuously 100 times. So when I mentioned multiple
users, what that equates to
is 60-80 users hitting nine pages 100 times. The scenario has some think
time (delay) between pages
to allow (I'm guessing here) sockets to become open.
>I implemented mod_jk as per the mod_jk_how_to instructions.
>I have tried tuning the workers.properties cachesize and
>the number of connectors in server.xml.
>I have tried to limit the number of clients in httpd.conf
Did you set Apache to fork more clients to handle the load ?
The more httpd task you have in Apache the more connections
you got to Tomcat and it may help here.
I am guessing that I am overloading tomcat. I left this at default, what do
you suggest?
>Also, I have seen this problem posted on a few sites, but have
>not seen a resolution. Any help would be greatly appreciated.
Could you play your config and tell us how many httpd task you
got and Ajp13 task ? A basic netstat will tell you how many
connections are open between Apache and Tomcat
So I took your idea about limiting the child forks and ran the scenario with
100 users.
A netstat -a |grep 1521 |wc
about 621 for 100 users
netstat -a |grep 8009 |wc
between 490 and 677 for 100 users
