It's interesting that you've tried Tomcat 4.1.24, I was going to try that
this week.  I've tried Sun's JDK 1.4.1_01 and 1.4.1_02, and it made no
difference.

Where do we go from here?

-----Original Message-----
From: Ivan F. Martinez [mailto:[EMAIL PROTECTED]
Sent: 22 March 2003 03:03
To: Tomcat Users List
Subject: Re: tomcat 4.1.18, apache 2.0.43, mod_jk 2.0.43



On Fri, 21 Mar 2003 13:50:41 -0000
"Marion McKelvie" <[EMAIL PROTECTED]> wrote:

MM> Ivan,
MM>
MM> Thanks for your reply.  When you restart Apache, do the threads just
build
MM> up again?

Yes, tomcat gives a lot of messages like this :
512488 [Thread-73] INFO common.ChannelSocket  - server has been restarted or
reset this connection

And it returns to work for some time again.
Apparently tomcat or mod_jk does not close the connection after serving the
request.

MM> If you can't see any difference between the two configurations, do you
think
MM> there may be a difference between the libraries being used?

I'm checked better, and the difference is :

Case when works (USING 2 MACHINES):
   RedHat 8, Apache 2.0.40
   RedHat 7.3 Tomcat 4.1.18

Case when I have problems
   RedHat 8, Apache 2.0.40 Tomcat 4.1.18 (SAME MACHINE)

The 2 use the same SUN SDK 1.4.1-01


But I have tried  today many combinations in the single machine :
SUNSDK 1.4.1, IBM SDK 1.3, 1.3.1, 1.4.
Apache 2.0.40 and 2.0.43
Tomcat 4.1.18 and 4.1.24

All configurations have the same problem.

All machines have up to date , kernels from redhat. And all other updates.

Last week I have made some tests with mod_jk2 with same problem.





MM> Marion
MM>
MM> -----Original Message-----
MM> From: Ivan F. Martinez [mailto:[EMAIL PROTECTED]
MM> Sent: 21 March 2003 12:59
MM> To: Tomcat Users List
MM> Subject: Re: tomcat 4.1.18, apache 2.0.43, mod_jk 2.0.43
MM>
MM>
MM>
MM> On Thu, 20 Mar 2003 09:40:14 -0000
MM> "Marion McKelvie" <[EMAIL PROTECTED]> wrote:
MM>
MM> MM> Hello again,
MM> MM>
MM> MM> Is anyone running with the combination of Tomcat 4.1.18, Apache
2.0.43
MM> and
MM> MM> mod_jk 2.0.43 on Redhat 8?
MM> MM>
MM>
MM> I have one machine that works fine, and other with same problem as you.
MM> When you restart apache everything works again.
MM>
MM> I have tested with mod_jk and mod_jk2.
MM>
MM> I didn't find the difference between the two machines.
MM>
MM> MM> Marion
MM> MM>
MM> MM> -----Original Message-----
MM> MM> From: Marion McKelvie [mailto:[EMAIL PROTECTED]
MM> MM> Sent: 19 March 2003 10:38
MM> MM> To: [EMAIL PROTECTED]
MM> MM> Subject: tomcat 4.1.18, apache 2.0.43, mod_jk 2.0.43
MM> MM>
MM> MM>
MM> MM> Hi,
MM> MM>
MM> MM> I have an installation using Tomcat 4.1.18, Apache 2.0.43 and mod_jk
MM> 2.0.43
MM> MM> running on Redhat 8, all installed from rpms as executables (no
building
MM> MM> from source).
MM> MM>
MM> MM> Everything works fine for a while until I get the following error in
MM> MM> catalina.out
MM> MM>
MM> MM> 19-Mar-2003 10:00:20 org.apache.tomcat.util.log.CommonLogHandler log
MM> MM> INFO: All threads are busy, waiting. Please increase maxThreads or
check
MM> the
MM> MM> servlet sttus75 75
MM> MM>
MM> MM> I can get this error just by playing with the Tomcat examples for
long
MM> MM> enough (presumably after 75 activities).  It's a bit like each
thread is
MM> not
MM> MM> being released after it's used.  I have a comparable installation
which
MM> runs
MM> MM> without problems but it's using Tomcat 4.1.12 with Apache 1.3.22.
MM> MM>
MM> MM> Server.xml is pretty much as installed by default (I've commented
out
MM> the
MM> MM> 8080 connector) so it's using the Coyote connector:
MM> MM>
MM> MM>     <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
MM> MM>                port="8009" minProcessors="5" maxProcessors="75"
MM> MM>                enableLookups="true" redirectPort="8443"
MM> MM>                acceptCount="10" debug="0" connectionTimeout="0"
MM> MM>                useURIValidationHack="false"
MM> MM>
MM> MM> protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"/>
MM> MM>
MM> MM> If I change the timeout to 20000, catalina.out reports that the
timeout
MM> has
MM> MM> been reached.
MM> MM>
MM> MM> workers.properties is as installed by default except that I've
corrected
MM> the
MM> MM> java_home path.
MM> MM>
MM> MM> mod_jk.conf is as follows
MM> MM>
MM> MM> JkWorkersFile /etc/httpd/conf/workers.properties
MM> MM> JkLogFile     /var/log/httpd/mod_jk.log
MM> MM> JkLogLevel error
MM> MM>
MM> MM>
MM> MM> #
MM> MM> # Root context mounts for Tomcat
MM> MM> #
MM> MM> JkMount /*.jsp ajp13
MM> MM> JkMount /servlet/* ajp13
MM> MM>
MM> MM> #########################################################
MM> MM> # Auto configuration for the /examples context starts.
MM> MM> #########################################################
MM> MM>
MM> MM> #
MM> MM> # The following line makes apache aware of the location of the
/examples
MM> MM> context
MM> MM> #
MM> MM> Alias /examples "/var/tomcat4/webapps/examples"
MM> MM> <Directory "/var/tomcat4/webapps/examples">
MM> MM>     Options Indexes FollowSymLinks
MM> MM> </Directory>
MM> MM>
MM> MM> #
MM> MM> # The following line mounts all JSP files and the /servlet/ uri to
MM> tomcat
MM> MM> #
MM> MM> JkMount /examples/servlet/* ajp13
MM> MM> JkMount /examples/*.jsp ajp13
MM> MM>
MM> MM> #
MM> MM> # The following line prohibits users from directly access WEB-INF
MM> MM> #
MM> MM> <Location "/examples/WEB-INF/">
MM> MM>     AllowOverride None
MM> MM>     deny from all
MM> MM> </Location>
MM> MM>
MM> MM> #######################################################
MM> MM> # Auto configuration for the /examples context ends.
MM> MM> #######################################################
MM> MM>
MM> MM>
MM> MM>
MM> MM> Any help much appreciated - I'm sure I've probably missed something
MM> obvious
MM> MM> but all the restarts are getting very annoying!
MM> MM>
MM> MM> Marion
MM> MM>
MM> MM>
MM>
MM> ---------------------------------------------------------------------
MM> MM> To unsubscribe, e-mail: [EMAIL PROTECTED]
MM> MM> For additional commands, e-mail: [EMAIL PROTECTED]
MM> MM>
MM> MM>
MM>
MM> ---------------------------------------------------------------------
MM> MM> To unsubscribe, e-mail: [EMAIL PROTECTED]
MM> MM> For additional commands, e-mail: [EMAIL PROTECTED]
MM> MM>
MM>
MM>
MM> --
MM>
MM>
MM> Ivan F. Martinez
MM>
MM> ---------------------------------------------------------------------
MM> To unsubscribe, e-mail: [EMAIL PROTECTED]
MM> For additional commands, e-mail: [EMAIL PROTECTED]
MM>
MM>
MM> ---------------------------------------------------------------------
MM> To unsubscribe, e-mail: [EMAIL PROTECTED]
MM> For additional commands, e-mail: [EMAIL PROTECTED]
MM>


--


Ivan F. Martinez

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


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

Reply via email to