IC, Thanx for clearing that out :)
FooShyn
David Delbecq wrote:
It tracks performances under workload, not memory leaks. To track and
locate memory leak, you need profiling tools or be able to load/unload
several time all modules separately.
En l'instant précis du 04/06/07 11:49, Foo Shyn s'exprimait en ces termes:
Hmm i'm not sure whether it can track memory leak or not, since i'm
not a frequent user of it, but you can try JMeter from Apache:
http://jakarta.apache.org/jmeter/
Its testing and monitoring module helps me a lot though...
HTH
FooShyn
Jacob Rhoden wrote:
David Delbecq wrote:
Java comes with a profiling tools available that dump information on a
text file upon exist. Look at sun web site for docs about profiling.
You
jun then have to set the appropriate parameters to your CATALINA_OPTS
Hi, Thanks for your reply however I cant find anything useful on the
Sun site. Only a few things that reveal you have to type a kill
-QUITE <tomcat_proc>, however that doesnt seem to do anything (maybe
it is putting a heap file somewhere I dont know about).
Best Regards,
Jacob
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
