At times, WorldServer might become slow for no apparent reasons. Segmentation might take a long time and then fail with unspecific errors. The reasons for this behavior might be multiple. When we receive support cases reporting these symptoms, we (SDL Support) look at the environment, the Workflow Engine Queue, The Filter Engine Queue etc and we analyse the relevant logs to determine what the issue might be. 

Sometimes we find entries like: 'java.lang.OutOfMemory' in the ws.log or ws-legacy.log. When that is the case, the quick fix is to restart WorldServer, but this is usually just a temporary solotion. An analysis of the WorldServer server specifications and requirements often leads to finding that the allocated Java Heap memory can be increased. Keep in mind: changing the Java Memory settings is typically considered a tuning exercise. Depending on environment, different values may work for different setups. This article explains how to change the Java Heap memory settings (click on the Preview and you will be re-directed):