SEPM services take up a lot of CPU and become unresponsive
Last Updated November 03, 2010
SEPM services take up a lot of CPU and become unresponsive unable to access SEPM console, and clients will fall over to secondary priority servers
Symptoms high CPU usage/memory
unable to access SEPM console
org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Network error IOException: No buffer space available (maximum connections reached?): connect) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1225)
EventDesc: Failed to connect to database after tried 20 times, please start the database! MessageId: -1 ErrorCode: -1 com.sygate.scm.server.util.ScmServerError: Failed to connect to database after tried 20 times, please start the database!
Unexpected behavior when closing out connection threads lead to an issue where the SEPM ran out of available threads
This issue is resolved in RU6.
Imported Document ID: TECH123922
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe