For users who cannot monitor some or all database instances, and who see "out of memory" errors for permgen in the logs, this article explains what the errors mean and what you can do about it.
According to Sun, it appears to be either a memory bloating issue, or a bug in permanent generation garbage collecting, or perhaps both.
Fixes are documented in 184.108.40.206.5 (and up) and 220.127.116.11.6 (and up). The 1.6 fix is in the "for business" release, so it is not clear that it is in the free version, but we are hopeful that they have rolled this fix into the later versions (18.104.22.168 and higher).
Perm Gen space typically defaults to 64m, but it can be increased using -XX:PermSize=128m (or higher).
All versions of DPA
The following steps should resolve this issue:
java_loc.txtwith the full path including the java executable for the newly-installed JDK.
java_loc.txtwill override any system setting to JAVA_HOME for Ignite/DPA only when it is started or shutdown.
shutdown.shand then run
If you cannot immediately upgrade to the new Java version, try increasing the PermSize to 128m as this may allow more time between the fatal errors. Also, consider stopping/starting DPA on a weekly basis so to reduce the chances of getting memory errors. Another way to reset DPA without a regular schedule is to query the heartbeat parameter in conprm periodically. If the heartbeat has not changed in some interval of time, then stop / start DPA again.