Anonymous | Login | Signup for a new account | 12-17-2024 10:47 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0002428 | [Resin] | minor | always | 02-12-08 05:33 | 03-26-08 16:51 | ||||
Reporter | sam | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 3.1.6 | Product Version | 3.1.4 | ||||
Product Build | |||||||||
Summary | 0002428: Generate thread dump when CPU usage is high. | ||||||||
Description |
Resin could output a thread dump automatically when the CPU usage of a server exceeds a threshold for a certain period of time. Additional cleverness would be to check the garbage collector. For example, If CPU usage is high, sample 30 times over a period of 30 seconds, and record CPU usage for each sample and whether or not the garbage collector is active. If the CPU usage is high for all samples, output a message if the garbage collector is the suspected problem, and in any case produce a thread dump. Resin should probably not automatically exit based on CPU information only, the <ping> facility covers that case. |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
There are no notes attached to this issue. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
27 total queries executed. 25 unique queries executed. |