Valid on Windows operating systems.
Symptom 1:
The Arcserve UDP Agent Service on Arcserve UDP Agent systems runs slowly. You can detect other symptoms such as:
Solution 1:
In various environmental configurations, you can discover that the Arcserve UDP Agent Service occupies too much CPU time, or the response is slow. By default, Tomcat is configured to allocate a limited amount of memory to the nodes, which may not be suitable for your environment. To verify this problem, review the following log files:
<D2D_home>\TOMCAT\logs\casad2dwebsvc-stdout.*.log <D2D_home>\TOMCAT\logs\casad2dwebsvc-stder.*.log <D2D_home>\TOMCAT\logs\catalina.*.log <D2D_home>\TOMCAT\logs\localhost.*.log
Search for the following message:
java.lang.OutOfMemoryError
To correct this problem, increase the amount of allocated memory.
To increase the memory, do the following:
HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\CASAD2DWebSvc\Parameters\Java
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\CASAD2DWebSvc\Parameters\Java
java.lang.OutOfMemoryError: PermGen space
Append the following to the value of Options.
-XX:PermSize=128M -XX:MaxPermSize=128M
Note: You may need to increase the value of -XX:MaxPermSize to suit your environment.
java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: GC overhead limit exceeded
Increase the value of the following DWORD:
JvmMx
Symptom 2
Scheduled backups are skipped and stop running.
Solution 2
When you configure the MAX value as 20 or less than 20 for concurrent backups, do the following:
JvmMx=256
Note: This DWORD is referenced in Solution 1.
-XX:MaxPermSize=128M
Note: This DWORD is referenced in Solution 1.
When you configure the MAX value as more than 20 but less than 50 for concurrent backups, do the following:
JvmMx=512
Note: This DWORD is referenced in Solution 1.
-XX:MaxPermSize=256M
Note: This DWORD is referenced in Solution 1.
Copyright © 2015 Arcserve.
All rights reserved.
|
|