In a Symantec Endpoint Protection Manager (SEPM) replication setup, after a Replication Partner is added, the error "Unable to connect to the server specified" occurs.
More errors may also appear.
The following errors occur:
NFO: Initializing Coyote HTTP/1.1 on http-9090 May 12, 2009 12:19:58 PM org.apache.coyote.http11.Http11BaseProtocol init SEVERE: Error initializing endpoint java.io.IOException: Keystore was tampered with, or password was incorrect at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:768) at java.security.KeyStore.load(KeyStore.java:1150) at org.apache.tomcat.util.net.jsse.JSSESocketFactory.getStore(JSSESocketFactory.java:287)
The SEPM is a Java-based application, much of its performance is related to the size of the "Java Heap".
Modifying the settings that control the size of the Java Heap will improve the performance of a wide variety of the functions performed by the Symantec Endpoint Protection Manager.
To adjust the SEPM heap size:
Reference : Performance tuning for the manager
The Heap Size for SEPM is specified with two values, stored in the registry.
The default value for JVM Option 1 is 256 MB, while the default value for JVM Option 0 was reduced from 256 MB to 64 MB in SEP 11 MR2 to reduce the memory footprint of the application in smaller environments - the application will automatically increase the size of the Java Heap as required until it encounters the configured maximum size.
These values can be increased to better suit the available resources on the computer; performance can be optimized by following the guidelines below:
Note: Always allow for at least 256 MB to be allocated to the Operating System.
For Example: On a computer with 1 GB of RAM, the maximum value for the Java Heap should not exceed 768 MB.