4.2.d nightly build - tomcat stops randomly

[cyberjus]

I had 4.2.c was running fine. Clean upgrade on the same server to 4.2.d nightly (parallel directory) runs for about 6 hours and then tomcat stops randomly. I checked the processes and it is not there, running the stop alfresco script confirms that it is not running. No message in the tomcat (catalina.out) or alfresco logs, which seems strange. I am using Mod_JK so the apache logs do say something, but only that it failed to open the socket. Which would make sense considering Tomcat is no longer running.

I tweaked the JAVA_OPTS to -Xss1024K -Xms1G -Xmx2G -XX:MaxPermSize=512M because I thought it might be a memory problem, but it is still stopping after awhile.

Any idea what I could try next or other places to look to figure out what is going on? I am not sure what other logs I could look at. 

[digcat]

Hi Cyberjus

We have seen this problem, but tracked it down to memory, and we were seeing messages in /var/log/messages. showing that the java process had to be terminated because of lack of memory.  This is more a linux 'feature' rather than alfresco specific, in that linux will save itself, at the expense of terminating any processes causing its memory to run out.  We also had some success using the vmswapiness parameter, which helped squeeze a little more from the machine.

[digcat]

Hi Cyberjus

We have seen this problem, but tracked it down to memory, and we were seeing messages in /var/log/messages. showing that the java process had to be terminated because of lack of memory.  This is more a linux 'feature' rather than alfresco specific, in that linux will save itself, at the expense of terminating any processes causing its memory to run out.  We also had some success using the vmswapiness parameter, which helped squeeze a little more from the machine.