Hi,
We have a new instance of CQ5 (version 5.4) running on a Windows 2003 SP2 Server. For some reason, which we can't determine, after a period of time a Java process on the system begins to consume 100% of the CPU and the system becomes totally unresponsive. Has anyone seen this before? Is there a fix for this?
RK
Does the it eventually recover on it's own? It's possible that the JVM is doing full garbage collection. How big is your max heap size? I suggest to add some garbage collection debugging in the JVM_OPTS to see if it is Java's garbage collection or not. Might as well check the heap too, to see if it's running our of memory.
Example;
-verbose:gc -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:+PrintTenuringDistribution -Xloggc:/tmp/gc.log -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp
Ron
Hi Ron,
We've never seen it recover, but the longest we've ever left it running without killing it is about 12+ hours. I'll add the garbage collection debugging and I'm wondering if you can tell me where I find the max heap size setting? I assume that's in a config file somewhere? Not sure with windows if there's a control panel for the JVM or not... Will check.
Thanks!
Pat
Hi Pat,
For Windows, it should be in crx-quickstart/server/server.bat. Look for the Memory settings:
set JVM_MINHEAP=-Xms64m
set JVM_MAXHEAP=-Xmx256m
set JVM_PERMGEN=-XX:MaxPermSize=128M
Also, you can add the garbage collection debugging parameters in this file:
set JVM_OPTS
Hope this helps.
Ron
Hello,
Did you got chance to create day care ticket about this ? Thread dump with logs will help. Also see http://dev.day.com/content/kb/home/Crx/Troubleshooting/AnalyzeSlowAndB lockedProcesses.html to figure out what is blocking.
Yogesh
Hey Guys,
FYI that we've been able to narrow down the issue to the VM Manager we're using. Running the VM using Microsoft Hyper-V server seems to have some sort of impact on the instance and java process handling. We've run the exact same machine setup (O/S, software versions etc...) on a VMWare based VM and it works perfectly. We're not sure why, but thought I'd provide an update.
FYI...Pat
North America
Europe, Middle East and Africa
Asia Pacific