The JDBCTempalte is logging at a WARN level for DB2 for SQLCode 100 (no rows returned) -- can this be moved to info? [SPR-2316]

[spring-projects-issues]

Tom Greco opened SPR-2316 and commented

The JdbcTemplate is logging warn messages for SQLCode 100 (No rows returned). The logging level for this SQL Code seems to be high at warn since this is may be a desired result. Can this be lowered to info?

2006-07-18 10:24:51,685 [WebSphere t=009bbb00] WARN org.springframework.jdbc.core.JdbcTemplate - SQLWarning ignored: SQL state '02000', error code '100', message [[IBM/DB2][T2zos/1]T2zosPreparedStatement.readExecuteInternal:nativeExecute:4706:DB2 engine SQL warning, SQLCODE = 100, SQLSTATE = 02000, warning tokens = ]
2006-07-18 10:24:51,815 [WebSphere t=009bbb00] WARN org.springframework.jdbc.core.JdbcTemplate - SQLWarning ignored: SQL state '02000', error code '100', message [[IBM/DB2][T2zos/1]T2zosPreparedStatement.readExecuteInternal:nativeExecute:4706:DB2 engine SQL warning, SQLCODE = 100, SQLSTATE = 02000, warning tokens = ]
2006-07-18 10:24:53,162 [WebSphere t=009bbb00] WARN org.springframework.jdbc.core.JdbcTemplate - SQLWarning ignored: SQL state '02000', error code '100', message [[IBM/DB2][T2zos/1]T2zosPreparedStatement.readExecuteInternal:nativeExecute:4706:DB2 engine SQL warning, SQLCODE = 100, SQLSTATE = 02000, warning tokens = ]

---

Affects: 1.2.7, 1.2.8, 2.0 M3, 2.0 M4, 2.0 M5, 2.0 RC1, 2.0 RC2

Backported to: 1.2.9

[spring-projects-issues]

Andrew Swan commented

More generally, I don't think it's appropriate for the log messages about the ignoring of an SQLWarning to be at the WARN level. Given that the user has told the JDBCTemplate to ignore any warnings, it would be more appropriate if these messages were logged at the INFO level.

As background, my boss gets tetchy if he sees any warnings in the application logs. With the current JdbcTemplate code, there's no way to stop that happening. When an SQLWarning occurs, JdbcTemplate either rethrows it as an SQLWarningException or logs it at the WARN level. Turning this log level down to INFO would make the JdbcTemplate less whiny.

[spring-projects-issues]

Juergen Hoeller commented

I would even argue that the log level should be lowered to DEBUG, if DB2 exposes warnings for such perfectly acceptable conditions there. After all, the INFO level log should not get spammed with repeated messages for such acceptable conditions either...

Juergen

[spring-projects-issues]

Oleksandr Alesinskyy commented

Not only DB2,. Oracle as well, moreover, as far as I can remember this "warning" behavior came from SQL standard (anything that returns non-zero SQLCODE is at least SQL Warning). But it does not preclude downgrade of logging level, in my opinion - to DEBUG.

Really, I can not remember any SQL-Warning that indicates non-legitimate conditions.