you can configure maxActiveSession,
http://tomcat.apache.org/tomcat-5.0-doc/config/manager.html
Vikram Godse wrote:
Hi,
My CATALINA_OPTS parameter has the following values i have 4gb ram on my server
CATALINA_OPTS="-server -XX:MaxPermSize=512m -Xms1024m -Xmx1024m"
This is what i see in the tomcat manager server info.
Max threads: 200 Min spare threads: 4 Max spare threads: 50 Current
thread count: 20 >Current thread busy: 17
Max processing time: 560464 ms Processing time: 2668.859 s Request
count: 2800 Error >count: 46 Bytes received: 0.00 MB Bytes sent: 27.28
MB
My Max threads are 200 of which current thread count is 20 and current
busy are 17 with
128 active sessions.
and my JVM shows the following
Free memory: 976.13 MB Total memory: 1003.93 MB Max memory: 1003.93 MB
What i am worried about is the number of sessions keep on increasing
my session timeout value is 30minutes.If i keep it less then the user
session times out and the user is logged out of the system.If i run it
in a test environment with about 5-10 people connecting then the
number of sessions never go beyond 10.
Is it so that tomcat is getting less resources due to which it is
crashing or is it a configuration problem?
Thanks & Regards,
VIkram
On 3/7/06, Sheets, Jerald <[EMAIL PROTECTED]> wrote:
I would look at a few things.
First, you should read about and implement the JMX instrumentation
(jconsle) to get a clear idea of your garbage collection profile.
Second, your JVM server options (Xmx, Xms, etc.) need to be set high
enough to handle that number of connections.
Make sure you have enough PermGen size (-XX:PermSize=128m, for instance)
A lot of times people will throw so much ram at -Xms and -Xmx that they
have depleted their PermGen space, and will get odd, nondescript errors
that surround the all important "native memory" errors.
Make sure you aren't garbage collecting to the tenured space quickly and
efficiently, but keeping objeects there forever like luggage. In my
experience (top 10 website with millions of views daily), we see that
pushing the objects into tenured as quickly as possible is the best
scenario, YMMV.
Make sure you're garbage collecting effectively. -XX:+UseparNewGC, or
maybe even an aggressive setting for GC. This will depend entirely on
your own metrics you obtain through the jconsole. Each site is
different, and just randomly throwing in numbers that some guy on the
internet tells you is not the best idea, REGARDLESS of where he works,
what his profile is, or how he does it. You have to tailor the
container, you have to tailor the VM, and you have to start looking at
the code once those are tuned properly.
Jerald Sheets
Systems Administrator
The Weather Channel Interactive
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vikram
Godse
Sent: Tuesday, March 07, 2006 8:22 AM
To: Tomcat Users List
Subject: Tomcat Crashes after 1000 sessions.
Hi,
I am running Apache Tomcat/5.5.12 with JVM 1.5.0-b64.My O/S is RHEL4.0
ES.My hardware configuration is as follows Intel Xeon 3.0Ghz Dual CPU
RAM 4gb I am running an JSP and Servlets based application with
connectivity to MySQL 5 for database access.
I am facing a problem, when my user sessions(in tomcat) go beyond 1000
the tomcat server stop serving requests and just displays a blank
page.What i have observed that, though there are only 150 users actually
accessing the website the number of sessions are atleast 800-900.
Can anybody tell me where the problem lies? i have been trying a lot but
no solution yet.
Thanks & Regards,
VIkram
--
Try not do or do not, there is no try !
---------------------------------------------------------------------
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]
--
Try not do or do not, there is no try !
---------------------------------------------------------------------
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]
