• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Thread dump - best practices

 
Ranch Hand
Posts: 128
MS IE Eclipse IDE Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi!

Our app. gets spikes in CPU , memory , and servlet. Do you know of any best practices for taking thread dumps. The spike occurs for a few minutes. By the time we get there, the app returns to normal operation.

thanks,
Sylvester
 
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There is no best practice as such for taking threaddumps (atleast i am not aware of).

But you could write a small script which takes the thread whenever the CPU spikes to more than 80%. Not sure if you have the unix or windows system.

In unix, just monitor the pid of the JVM and say "kill -quit pid" whenever the cpu spikes.

~Rajesh.B
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic