h2. Symptom
----
The CDP operations become unstable and the following error message appears:
{code}
java.lang.OutOfMemoryError: Java heap space
{code}
h2. Cause
----
The error occurs due to an insufficient memory amount caused by an issue in Task History Clean-up. When the clean-up process starts, it consumes all available memory and brings the whole system to a halt.
h2. Resolution
----
In CDP 3.14 this problem will be fixed. But for now go to Configuration !arrow.gif! Server Options and click "Edit Schedule" in the "Task History Clean-up" tab.
!never2.png!
Then set the trigger type to "Never."
!never.png!
This will prevent Task History Clean-up from running and taking up the memory.
{note:title=Notice}This step should only be taken after ensuring that the heap space is properly configured and that it is not a low-memory situation. See [CDP:Configuring Heap Memory].
{note}
{kb-related-articles}
----
The CDP operations become unstable and the following error message appears:
{code}
java.lang.OutOfMemoryError: Java heap space
{code}
h2. Cause
----
The error occurs due to an insufficient memory amount caused by an issue in Task History Clean-up. When the clean-up process starts, it consumes all available memory and brings the whole system to a halt.
h2. Resolution
----
In CDP 3.14 this problem will be fixed. But for now go to Configuration !arrow.gif! Server Options and click "Edit Schedule" in the "Task History Clean-up" tab.
!never2.png!
Then set the trigger type to "Never."
!never.png!
This will prevent Task History Clean-up from running and taking up the memory.
{note:title=Notice}This step should only be taken after ensuring that the heap space is properly configured and that it is not a low-memory situation. See [CDP:Configuring Heap Memory].
{note}
{kb-related-articles}