Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Error "java.sql.SQLException: Connection is closed"

Created: 06 Dec 2012 • Updated: 27 Mar 2013 | 13 comments
diabolicus23's picture
This issue has been solved. See solution.

SEP 12.1 RU2 Manager installed in one server (os 2008 R2) with external DB SQL Server 2008 installed in another one (same os, 2008 R2).
These machines are in the same subnet, no firewall or similar in the middle.

In the scm-server-0.log every 10 minuts (precisely) I read the following error:

 

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)
 
 
In the monitor section of the console, I don't see any event.
No effects, till now.
 
What could be?
 
 
Thanks!

 

Comments 13 CommentsJump to latest comment

diabolicus23's picture

It can only reach symantecliveupdate.com and symantec.com domains (LiveUpdate seems to work) via proxy (not authenticated).

Syed saied's picture

HI,

Can you try to access internet without Proxy.

 

Thanks In Advance...

Syed Saied

If the suggestion has helped to solve your problem, please mark the post as a solution

AravindKM's picture

Whether your SEPM service is getting stopped?

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

diabolicus23's picture

I'm investigating this "issue" with the Symantec support. If I get some infos I'll give them to you.

 

Answering your questions:

  • I can't try access without (or bypassing) proxy (I can reach symantec.com, symantecliveupdate.com and akamai.net domains);
  • the SEPM service does not stop and, apparently, no symptoms at all (only the message in the log file).
Syed saied's picture

Dear,

Your issue is resolve or not...?

 

 

Thanks In Advance...

Syed Saied

If the suggestion has helped to solve your problem, please mark the post as a solution

diabolicus23's picture

As I said in my last post, not yet. Under investigation by support.

Troubleshooting is ongoing smiley

One's picture

Had the same issue. Tried below article and the issue is resolved now.

Home, Monitors and Reports tabs in the SEPM are blank. Able to reach SEPM Reporting through Internet Explorer
https://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TECH156875

Please check if this resolves your issue..

 

DGLMike's picture

Hey Diabolicus,

 

Did you get anywhere on this with Symantec Support?

 

I get this exact error on every SQL based installation of SEP 12.1.2 I've done, in all my labs, on customer sites; everywhere!

Service doesn't stop, some SEPM's have full access to Internet, others just to Symantec, some not at all but update via an internal LiveUpdate Administrator server.

There doesn't appear to be any issue with any of the SEPM's at all, everything appears to be working fine, just this annoying error message (and in the case of the no internet access the usual accompanying erros you'd expect to see).

 

I've been led to believe that the DB connection is being closed twice for some reason so maybe this is a side effect of that?

 

I tried the fix in the post above but the key was already present...also that appears to be fixing something to do with displaying Reporting content in the SEPM console (something that often happens when you remove the sa rights on the SQL service account), not fixing a database connection issue...

 

Please let me know if you managed to resolve this error, it's driving me nuts!

 

diabolicus23's picture

Hi Mike!

Symantec support knows the origin of the problem (that, as you said, does not cause any issue) and they said that they will probably fix it in the RU3.

Just as information: the logs occur because there is a call to close a connection twice, instead of once, so the second attempt to close it produces a log that says the connection has already been closed.

 

Hope you can find these infos helpful

SOLUTION
DGLMike's picture

Superb, thanks for confirming that :)

 

Same old, "fixed in next release"...hmmm...we'll see...

One's picture

Home, Monitors and Reports tabs in the SEPM are blank. Able to reach SEPM Reporting through Internet Explorer
https://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TECH156875

 

Have you tried the above article. Has that not resolved your issue