Vidéos d'aide de Screencast

DataSource Exceptions every 10 minutes in scm-server-0 log

Created: 27 Mars 2013 • Updated: 27 Mars 2013 | 3 comments
Ce problème a été résolu. Voir la solution.
I'm trying to troubleshoot a problem with our manager that is stopping me from logging in unless I've remoted into the server itself first.  I noticed this occuring the in SCM-SERVER-0.log file every 10 minutes.  Is this normal behavior or something I should be concerned about?
 
 
 
2013-03-27 07:18:41.629 THREAD 28 INFO: LicenseManager>>computeDeployedClientCount>>Feature type = SEP specificClients:5292 commonclients:0
2013-03-27 07:18:41.629 THREAD 28 INFO: EELicenseHelper.getOverdeploymentClientCount(). Deployed count for SEP = 5292
2013-03-27 07:18:41.629 THREAD 28 INFO: EELicenseHelper.getOverdeploymentClientCount().Total licenses seats for SEP = 10600
2013-03-27 07:18:41.629 THREAD 28 INFO: EELicenseHelper.getOverdeploymentClientCount(). No overdeployment
2013-03-27 07:18:41.644 THREAD 28 INFO: LicenseManager>>computeDeployedClientCount>>Feature type = SNAC specificClients:0 commonclients:0 mac common clients = 0
2013-03-27 07:18:41.644 THREAD 28 INFO: EELicenseHelper.getOverdeploymentClientCount(). Deployed count for SNAC = 0
2013-03-27 07:18:41.644 THREAD 28 INFO: EELicenseHelper.getOverdeploymentClientCount().Total licenses seats for SNAC = 0
2013-03-27 07:18:41.644 THREAD 28 INFO: EELicenseHelper.getOverdeploymentClientCount(). No overdeployment
2013-03-27 07:18:41.644 THREAD 28 SEVERE: 
java.sql.SQLException: Connection is closed.
at org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.checkOpen(PoolingDataSource.java:185)
at org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.createStatement(PoolingDataSource.java:215)
at com.sygate.scm.server.db.util.SqlDbHelper.setDeadlockPriority(SqlDbHelper.java:988)
at com.sygate.scm.server.db.util.DatabaseUtilities.closeConnection(DatabaseUtilities.java:882)
at com.sygate.scm.server.db.util.DatabaseUtilities.closeConnection(DatabaseUtilities.java:905)
at com.sygate.scm.server.db.util.DbHelper.close(DbHelper.java:176)
at com.sygate.scm.server.task.SecurityAlertNotifyTask.execute(SecurityAlertNotifyTask.java:451)
at com.sygate.scm.server.task.MonitoredTimerTask.run(MonitoredTimerTask.java:22)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Operating Systems:

Commentaires CommentairesAccéder au dernier commentaire

l'image des Rafeeq

you cannot log in to SEPM? whats the error message you get when you log in?

l'image des diabolicus23

I've already found and already explained it with the help of the Symantec Support.

Briefly: it's a "bug" of this version but it has no impact on SEPM.

Take a look at this thread: https://www-secure.symantec.com/connect/forums/error-javasqlsqlexception-connection-closed

SOLUTION
l'image des Rokem

Thank you for the information about the bug.  At least I know that's not my problem.

I was troubleshooting the login issue when I noticed this.

I have opened another thread about the login issue here:

https://www-secure.symantec.com/connect/forums/sep...