https://issues.apache.org/bugzilla/show_bug.cgi?id=50660
Summary: Improve validationQuery error handling
Product: Tomcat Modules
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P2
Component: jdbc-pool
AssignedTo: dev@tomcat.apache.org
ReportedBy: dmik...@vmware.com
If an invalid validationQuery is specified, the SQL Exception is logged at the
DEBUG log level.
Example:
2011-01-25 18:32:56,139 DEBUG [org.apache.tomcat.jdbc.pool.PooledConnection]
Unable to validate object:
com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -104, SQLSTATE: 42601,
SQLERRMC: END-OF-STATEMENT;SELECT 1;<table_expr>
Since an invalid validationQuery can cause problems with the data source, it
would be nice to see this message logged at a different log level, such as WARN
or ERROR.
If that would create too much noise then I would suggest instead to add a check
during the initialization of the data source that would test the validation
query. Then this single check could log at WARN or ERROR.
Thanks
Dan
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
