RME4.1.1 - Syslog Analyzer SQLException?

Unanswered Question
Apr 15th, 2008


I have quite a few devices that now have theier syslogs going into the Unexpected Device report, after working fine for a while. Turning on Debugging, it seems to find the device DCR id but then has a SQLException occurredjava.sql.SQLException: JZ0C0: Connection is already closed. error, if I'm reading it right.

Any ideas?



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Joe Clarke Tue, 04/15/2008 - 08:43

The database error does appear to be related. If you restart SyslogAnalyzer, does the problem clear up?

jdwattsdk Tue, 04/15/2008 - 09:23

I've restart CiscoWorks a few times. It also moves around devices that device is now working again, but others are not - same error in the logs. The messages are from a RSAC if that makes a difference. All Solaris.


Joe Clarke Wed, 04/16/2008 - 07:57

I have fixed some other database connection issues in recent releases, and this may be covered by that. However, I will have to investigate this particular code path. In the meantime, restarting SyslogAnalyzer alone should work around the problem.

Joe Clarke Sat, 04/19/2008 - 22:40

While the bug was opened due to a problem in the BugToolkit report in RME, the same patch should fix this problem for you. If you contact TAC, and request the patch for CSCso14160, this problem should be fixed.


This Discussion