search

cmoutes / soi-toolkit

Automatically exported from code.google.com/p/soi-toolkit
0 stars 0 forks source link

Add validationQuery to jdbc-connection pool configuration #201

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Consider adding "validationQuery" to let the commons-dbcp pool test connections 
before returning them.
Currently stale connections might be sitting in the pool causing errors when 
used (seems like error is also logged to std-err rather than to the components 
log4j-logfile).

See:
1. soitoolkit-mule-jdbc-datasource.xml
2. http://commons.apache.org/dbcp/configuration.html

Original issue reported on code.google.com by hakan.d...@gmail.com on 24 Nov 2011 at 1:16

GoogleCodeExporter commented 8 years ago 
Also consider adding "queryTimeout" to avoid queries being hanging.
Ref: 
http://www.mulesoft.org/documentation/display/MULE3USER/JDBC+Transport+Configura
tion+Reference

Original comment by hakan.d...@gmail.com on 25 Nov 2011 at 10:00

GoogleCodeExporter commented 8 years ago 
Also add exception-handler to generated JDBC-connectors to catch errors, these 
errors will otherwise be caught by a default exception-handler and logged, but 
not reported via the EventLogger-mekanism.

For example (like in the JMS-connectors):
<custom-exception-strategy 
class="org.soitoolkit.commons.mule.error.ExceptionHandler"/>

Original comment by hakan.d...@gmail.com on 25 Nov 2011 at 11:29

GoogleCodeExporter commented 8 years ago 
Also add destroy-method="close" to spring config:

See: 13.2.1.2 JdbcTemplate best practices
http://static.springsource.org/spring/docs/3.1.0.RC1/spring-framework-reference/
html/jdbc.html#jdbc-core

Original comment by hakan.d...@gmail.com on 29 Nov 2011 at 9:24

GoogleCodeExporter commented 8 years ago

Original comment by hakan.d...@gmail.com on 30 Nov 2011 at 9:05

GoogleCodeExporter commented 8 years ago 
Move to 0.5.2

Original comment by magnus.l...@gmail.com on 6 Apr 2012 at 7:56

GoogleCodeExporter commented 8 years ago 
Move all v0.5.2 issues to v0.6.2

Original comment by magnus.l...@gmail.com on 26 Jul 2012 at 4:17