Anonymous | Login | Signup for a new account | 12-17-2024 08:25 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0003694 | [Resin] | major | always | 09-23-09 11:46 | 01-18-11 20:33 | ||||
Reporter | mocospace | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 4.0.1 | ||||||
Summary | 0003694: Major garbage collection (GC) causes thread spike | ||||||||
Description |
Every major/full garbage collection (GC) in Resin 4.0.1 professional causes the number of threads to spike in the JVM. This was not the case in Resin 3.2.x professional and is preventing us from upgrading. Resin 4 also seems to use more threads in general than Resin 3. We are running on CentOS 5, with the following JVM params - <jvm-arg>-server</jvm-arg> <jvm-arg>-Xms2560m</jvm-arg> <jvm-arg>-Xmx4608m</jvm-arg> <jvm-arg>-XX:MaxPermSize=256m</jvm-arg> <jvm-arg>-XX:+UseConcMarkSweepGC</jvm-arg> <jvm-arg>-XX:+CMSClassUnloadingEnabled</jvm-arg> <jvm-arg>-XX:CMSInitiatingOccupancyFraction=60</jvm-arg> <jvm-arg>-XX:+PrintGCTimeStamps</jvm-arg> <jvm-arg>-XX:+DisableExplicitGC</jvm-arg> |
||||||||
Additional Information | |||||||||
Attached Files | threads.JPG [^] (27,446 bytes) 09-23-09 12:29 | ||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
35 total queries executed. 28 unique queries executed. |