RE: Error: OperationsManager.handleOperations

[Graham Honey]

Hi Michel/Serge,   It is running as a windows service.  I have double checked the memory allocation and it was updated to 512m.  I have also checked the cache which seems to be relatively low and the JSP compiler is set to ‘fork’.  The problem has not arisen and I will monitor it over the coming weeks.   Kind Regards   Graham   From: Michel Romy [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 07, 2006 8:12 PM To: dev_list@jahia.org Subject: Re: Error: OperationsManager.handleOperations   Hi Graham, there may be many cause why an outofmemory error occurs, some of them may be templates related. However are you sure you indeed have doubled the maximum memory allocation ? because by default since at least Jahia 4.0.5 we have these default parameters : -Xms64m -Xmx512m  . You may want to check also if the java process is indeed eating up around 500Mb. To give you an idea, a Jahia customer site containning 500 published pages in 3 languages seems to be running fine with an Xmx set to 512m. Are your running Jahia in command line or as a Windows service ? best regards, Michel   We have recently doubled the memory allocation within the Catalina.bat file to resolve a number of Java.Lang.OutofMemory errors (set JAVA_OPTS=-Xmx512m -Xms256m).  This seems to have resolved the issue.  This morning however the site stopped and produced the enclosed log.  I would appreciate any assistance in resolving this issue to ensure that it does not affect future service.   Site details:   Jahia 4.1.0_01 build 6070 Microsoft Windows Server 2003 Intel(R) Xeon CPU 3.00GHz 3.99GHx, 2.00 GB of RAM Running 2 instances of Tomcat, one for Jahia and the other for Jira SharePoint also installed on the same server     Kind Regards   Graham Honey