RME4.1.1 - Syslog Analyzer SQLException?

jdwattsdk · ‎04-15-2008

Hi

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?

Thanks

J

Joe Clarke · ‎04-15-2008

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

jdwattsdk · ‎04-15-2008

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.

Thanks

Joe Clarke · ‎04-16-2008

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 · ‎04-19-2008

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.

jdwattsdk · ‎04-20-2008

Thanks, will do. Will post back after I receive it.