start tomcat with -Xrunprof and look at the profile to figureout if there are any objects consuming more memory(leaks). Thread.activeCount() gives you total number of active threads in the current JVM. Refer to javax.management to know more about the Mbeans to monitor the tomcat.

You need to write the proxy valve by implementing the org.apache.catalina.Valve, interface. This proxy will gets the request and invokes the actual servlet. You can track the time taken to process each request here.

Bhaskar



Peddireddy Srikanth wrote:

Hi,
Its giving out of memory over a period of time (i.e after test ran for
some time ) not immediately after starting the test
Follwing settings are given in my server.xml
For HTTP
<Connector port="80"
              maxThreads="500" minSpareThreads="25" maxSpareThreads="75"
              enableLookups="false" redirectPort="8443" acceptCount="150"
              connectionTimeout="20000" disableUploadTimeout="true" />

For HTTPS

<Connector port="443" maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
              enableLookups="false" disableUploadTimeout="true"
              acceptCount="100" scheme="https" secure="true"
              clientAuth="false" sslProtocol="TLS" />


By  active threads do u mean the thread count shown in windows task
manager or is there any way to find out active threads in Tomcat? what
is this Performance-Valve? can u give some more details on it ?

Thank you

regards
Srikanth.P


On 7/14/05, Bhaskar <[EMAIL PROTECTED]> wrote:
You need to check on whether it is giving Outofmemory error is
immediately after starting loadtesting with 1500 users or over period of
time. If it is over period of time then you need to check whether there
are any memory leaks. Or your design for ex., it might happen if you
query db and that ends up resulting in huge number of rows.
BTW., what is the max number of threads you have configured?
and what is the active number of threads? Pbly u can use
Performance-Valve to get such details.

Bhaskar


srikanth peddireddy wrote:

Hi All,

Recently we started load testing our application using Jmeter.
Following error is coming in tomcat while test is run at higher loads like 1500 
virtual users etc

      ======================================

SEVERE: Caught exception (java.lang.OutOfMemoryError) executing org.apache.tomca
[EMAIL PROTECTED], terminating thread
Jun 30, 2005 3:13:53 PM 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run

        ======================================

I already configured the Tomcat using -Xmx option to use upto 2GB of RAM 
(Tomcat is running on a 3GB RAM machine)

Any inputs or pointers to the related resources on this problem??

regards
Srikanth


Disclaimer
------------------------------------------------------------------------------------
This e-mail message may contain confidential, proprietary
or legally privileged information. It should not be used by
anyone who is not the original intended recipient. If you
have erroneously received this message, please delete it
immediately and notify the sender.

The views, opinions, conclusions and other information
expressed in this electronic mail are those of the
individual sender and not endorsed by SDG Software
Technologies Pvt. Ltd. unless otherwise indicated by an
authorised representative independent of this message.

Before opening any attachment please check them for viruses
and defects. SDG Software Technologies Pvt. Ltd. shall not
accept responsibility for any loss or damage arising from
the use of this email or attachment(s).
-------------------------------------------------------------------------------------

---------------------------------
Free antispam, antivirus and 1GB to save all your messages
Only in Yahoo! Mail: http://in.mail.yahoo.com


---------------------------------------------------------------------
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