PROTECTED]]
Sent: Thu 12/26/2002 9:42 AM
To: Tomcat Users List
Cc:
Subject:RE: Urgent - Issue with Tomcat/mod_jk?
I beleive we are dealing with a different problem. My app has been
running on Tomcat 4.0.6 for weeks until I had the problem recently.
There was no crash.
What
,
giving kernel out of memory error in syslog messages
Did you get any workaround for this
Thks,
--Venkat
-Original Message-
From: Ben Ricker [mailto:[EMAIL PROTECTED]]
Sent: Mon 12/23/2002 5:49 PM
To: Tomcat Users List
Cc:
Subject: Re: Urgent - Issue
in syslog messages
Did you get any workaround for this
Thks,
--Venkat
-Original Message-
From: Ben Ricker [mailto:[EMAIL PROTECTED]]
Sent: Mon 12/23/2002 5:49 PM
To: Tomcat Users List
Cc:
Subject:Re: Urgent - Issue with Tomcat/mod_jk?
I had suspected
I posted a message earlier which has not received any replies so I will
try another tact. The earlier mail is posted below this one.
I have a production issue that has arisen in a setup of two Apache
1.3.27/Redhat 7.3 servers load-balanced across 4 Tomcat 4.0.6/Sun
Solaris servers. Tomcat is
Ben,
Disclaimer:
I'm not a Tomcat developer, but I do use it to develop
software and integrate applications.
In $CATALINA_HOME/conf/server.xml you should see an
entry similar to the following:
!-- Define an AJP 1.3 Connector on port 8009 --
Connector
I had suspected that in the problem earlier in the day (the part of the
email I posted at the end if the last email you replied to). However,
what did not make sense was the connection pool woth the database also
going up.
If I understand the stuff below, after 85 concurrent connections (max
