topic Java Runtime Environment EXCEPTION_ACCESS_VIOLATION in Alfresco Archive

Java Runtime Environment EXCEPTION_ACCESS_VIOLATION

maximus007 — Tue, 02 Feb 2010 12:19:04 GMT

The responses seem to be better when I start a new thread rather than piggybacking off an old one so here goes:I am running Windows Server 2008 R2 with Alfresco Community 3.2r2 installation package. Everything works fine in normal usage, but Tomcat crashes when trying to bulk upload files, whether v

Re: Java Runtime Environment EXCEPTION_ACCESS_VIOLATION

mrogers — Tue, 02 Feb 2010 13:19:26 GMT

Try a more recent version of JVM.

Re: Java Runtime Environment EXCEPTION_ACCESS_VIOLATION

maximus007 — Tue, 02 Feb 2010 20:29:02 GMT

mrogers,

as I mentioned in my post, I have already tried using the latest version of the JVM (6.0_18).

Re: Java Runtime Environment EXCEPTION_ACCESS_VIOLATION

maximus007 — Wed, 03 Feb 2010 21:07:40 GMT

I appear to have solved the problem by iving the JVM more memory by modifying JAVA_OPTS as follows (from the JVM tuning guide):

JAVA_OPTS=-Xms2g -Xmx3g -Xss1m -XX:MaxPermSize=256m -XX:NewSize=1g -server -Dalfresco.home=%ALF_HOME% -Dcom.sun.management.jmxremote -Xcomp -Xbatch‍

One would expect that the default settings would at least be stable, if perhaps not completely optimised, which doesn't appear to be the case. Thankfully Alfresco seems to be running very quickly and stable with the updated settings. The error message doesn't really give any indication of insufficient or incorrect memory allocation.

FWIW, on Windows Server R2 , it was also helpful to:

Install and reference the latest x64 JDK (currently 6u18)

Update MySQL to the latest x64 binaries (currently 5.1.43-community)

Update Tomcat to the latest version (currently 6.0.24)

Install the x64 APR dlls for Tomcat

Updated ImageMagick and OpenOffice binaries (optional - minor fixes)

With the above setup Alfresco seems to be rock solid, fast and error free (so far).

Re: Java Runtime Environment EXCEPTION_ACCESS_VIOLATION

mikeh — Wed, 03 Feb 2010 23:29:10 GMT

Interesting - thanks for posting a follow-up. I'll make sure the issue is raised internally so QA can work out if the default settings are no longer adequate.

Thanks,
Mike