Java Solaris Communities Sun Store Join SDN My Profile Why Join?
 
Bug Database
Bug Detail
Quick Lists
Top 25 Bugs
Top 25 RFE's
Recently Closed Bugs
Printable Page Printable Page


Bug Database
Bug ID: 6541037
Votes 0
Synopsis Ability to unload classes upon an explicit concurrent gc request
Category hotspot:garbage_collector
Reported Against
Release Fixed hs10(b13), 6u4(b03) (Bug ID:2171952) , 7(b13) (Bug ID:2176918)
State 10-Fix Delivered, request for enhancement
Priority: 4-Low
Related Bugs 6329603 , 6543076 , 5025281
Submit Date 30-MAR-2007
Description
As in synopsis; see comments section for discussion.
Posted Date : 2007-04-05 18:02:51.0
Work Around
N/A
Evaluation
A new experimental JVM has been implemented for testing by customer;
once we are satisfied that there are no hidden land-mines
(based both on customer input and experience, as well as internal
review and analysis by team members) this RFE will be brought
before the CCC for fast-track approval.
Posted Date : 2007-03-30 17:46:28.0

A new JVM-specific flag:
-XX:+ExplicitGCInvokesConcurrentAndUnloadsClasses.
When enabled with the concurrent collector, this flag directs the JVM
to not only execute a concurrent colection cycle (as does the flag
-XX:+ExplicitGCInvokesConcurrent), but in addition
also unload classes in that collection cycle. This would allow the
application to recycle space in the perm gen on an as-required,
schedulable, basis.


===============
-XX:+ExplicitGCInvokesConcurrentAndUnloadsClasses:
 
  If this flag is set then, in response to an explicit GC request,
e.g. System.gc(), the JVM will run a concurrent collection cycle in which
classes eligible for collection are unloaded. This flag implies
-XX:+ExplicitGCInvokesConcurrent and, like that flag, is effective only
when a concurrent collector is in use.
===============
Posted Date : 2007-10-08 17:01:21.0
Comments
  
  Include a link with my name & email   


PLEASE NOTE: JDK6 is formerly known as Project Mustang