virtualization server fall over frequently in wcm 2.1.1

[sreedharabc]

The virtualization server is falling over frequently in Alfresco 2.1.1 with the following exception:
java.lang.OutOfMemoryError: PermGen space
RMI TCP Connection(6176)-127.0.1.1" java.lang.OutOfMemoryError: PermGen space

we have 8 webforms and each has on average 10 jsp pages.
we have 5 sandboxes in our development environment.

PermGen is maxed at 128MB
I saw a JIRA WCM-795 as closed in  2.2.0E,
could you please mention what the fix is and how to apply it on 2.1.1

[pmonks]

Can you check the logs for the main (authoring) Alfresco server?  It's a bit hard to tell from the exception message, but it looks like the PermGen problem might be occurring in the authoring Alfresco, but being passed through to the virtualisation server via RMI, and then showing up there.  In other words, I'm not totally convinced that it's the virtualisation server that's running out of PermGen space.

Increasing the PermGen for the main (authoring) Alfresco instance (as described in WCM-795) is worth a shot - the JVM will use 64MB more memory, but other than that there's no down side to trying it out.

[tommorris]

I get the same problem as sreedharabc, using 2.1.1e.

We have to restart the virtualisation service once or twice each day.
This seems to happen during days of frequent WCM-form editing.

(occasionally we get the same happening to the alfresco server)

Changing the PermGen memory allocation seems to just delay the crash.

Could it be due to the frequent unloading/loading of class files (that is, compiled JSP classes)? We do have hundreds of JSP pages.

Perhaps it's the link-validation service. If the validation service fails to compile a JSP, does it re-try endlessly (thereby causing continuous re-compilation attempts)?