Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.
#Automation
Hi All,
am using wM8.0 version, today am getting below error in server log
[900]2010-04-19 12:22:15 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [899]2010-04-19 12:22:15 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [898]2010-04-19 12:22:15 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [897]2010-04-19 12:22:15 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [896]2010-04-19 12:22:15 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [895]2010-04-19 12:22:15 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [894]2010-04-19 12:22:13 CEST [WmAuditingSC.queue.2406E] AuditQueueWorker for queue ‘Security Queue’ failed to log event to destination ‘CoreAuditDBDest’; reason ‘[wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.’; stack trace follows [893]2010-04-19 12:22:13 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [892]2010-04-19 12:22:13 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [891]2010-04-19 12:22:12 CEST [WmAuditingSC.queue.2406E] AuditQueueWorker for queue ‘Security Queue’ failed to log event to destination ‘CoreAuditDBDest’; reason ‘[wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.’; stack trace follows [890]2010-04-19 12:22:12 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [889]2010-04-19 12:22:12 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [888]2010-04-19 12:22:11 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [887]2010-04-19 12:22:11 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [886]2010-04-19 12:22:10 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [885]2010-04-19 12:22:10 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [884]2010-04-19 12:22:10 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [883]2010-04-19 12:22:10 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [882]2010-04-19 12:22:10 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [881]2010-04-19 12:22:10 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [880]2010-04-19 12:22:06 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [879]2010-04-19 12:22:06 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [878]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [877]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [876]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [875]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [874]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [873]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [872]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [871]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [870]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [869]2010-04-19 12:22:05 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [868]2010-04-19 12:22:01 CEST [WmAuditingSC.queue.2406E] AuditQueueWorker for queue ‘Security Queue’ failed to log event to destination ‘CoreAuditDBDest’; reason ‘[wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.’; stack trace follows [867]2010-04-19 12:22:01 CEST [WmAuditingSC.destination.1110E] Destination ‘CoreAuditDBDest’ caught unexpected SQLException rolling-back transaction: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed. [866]2010-04-19 12:22:01 CEST [WmAuditingSC.destination.1122E] Destination ‘CoreAuditDBDest’ caught unexpected Throwable logging audit event: [wm-cjdbc40-0034][SQLServer JDBC Driver]Object has been closed.
Regards, Anil Kumar E
Hi Anil,
we have the same problem (with Oracle) after restart of the database (logging) without restarting the integration server
Can you can check whether the DB is having issue with its conenction to the IS? If the DB is up, you can reconnect the IS using JDBC pool in the IS admin page to the oracle DB.
Thanks, William.
HI Anil,
You can refer to the forum thread in wmUsers with the same question.
You can read through the readme file for IS_8.0_SP1_Core_Fix3 (current fix) and apply it on your end in development enviroment whether this would resolve your issue.
Thanks
Best regards, William
There was a problem with the auditing subsystem retaining stale database connections. This has been addressed with a fix which you can download: IS_8.0_SP1_Core_Fix5.
Regards, Michael
sorry for late reply, i have updated my environment with IS_8.0_SP1_Core_Fix5 in wM8SP1, got resolved.