Issue Details (XML | Word | Printable)

Key: RIO-275
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dennis Reedy
Reporter: Dennis Reedy
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Rio

Provide better management of PermGen

Created: 08/Jul/10 10:35 PM   Updated: 20/Dec/10 10:03 PM
Component/s: Core
Affects Version/s: 4.0
Fix Version/s: 4.1

Time Tracking:
Not Specified

Issue Links:
Dependency
 


 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Dennis Reedy added a comment - 08/Jul/10 10:49 PM
First off, the rio script will have the following GC options added to it:

-XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=256m


Dennis Reedy added a comment - 08/Jul/10 10:51 PM
When services get created that do not extend ServiceBeanAdapter, a dynamic proxy is created to handle the delegation between the bean and the service bean. An approach for caching these proxies should be done, so dynamic proxies can be re-used across service instantiations.

Dennis Reedy added a comment - 08/Jul/10 11:09 PM
A MeasurableCapability will be created to monitor the perm gen. If the perm gen exceeds a threshold (90%?) of total perm gen, the cybernode will cease to be a resource that can be used to instantiate services. If the perm gen gets freed, the cybernode will once again register for the instantiation of services.

We may also want to relocate services, and/or possibly restart the cybernode automatically.

This may also be something that a gnostic can take into account, relocating services to other available cybernodes.