You can force it by: set JAVA_OPTS=%JAVA_OPTS% -*XX:+HeapDumpOnCtrlBreak*-XX:+HeapDumpOnOutOfMemoryError
--- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring & Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://www.baselogic.com Blog: http://www.baselogic.com/blog/ Linked IN: http://linkedin.com/in/mickknutson Twitter: http://twitter.com/mickknutson Vacation Rental: http://tahoe.baselogic.com --- On Fri, Jun 25, 2010 at 10:56 AM, Caldarale, Charles R < chuck.caldar...@unisys.com> wrote: > > From: Ozgur Ozdemircili [mailto:ozgur.ozdemirc...@gmail.com] > > Subject: Re: Tomcat current thread count > > > > What would be the possible ways of finding where the problem lies ? > > As previously stated, take a thread dump *before* the JVM crashes and find > out what your threads are stuck on. Your monitoring tool probably may have > that capability built-in; if it doesn't, look here: > > > http://wiki.apache.org/tomcat/HowTo#How_do_I_obtain_a_thread_dump_of_my_running_webapp_.3F > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you received > this in error, please contact the sender and delete the e-mail and its > attachments from all computers. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
