Bug 48080 - Tomcat documentation and JDBC context
Summary: Tomcat documentation and JDBC context
Status: RESOLVED DUPLICATE of bug 47235
Alias: None
Product: Tomcat 6
Classification: Unclassified
Component: Documentation (show other bugs)
Version: unspecified
Hardware: Other other
: P2 minor (vote)
Target Milestone: default
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-28 14:16 UTC by supareno
Modified: 2009-11-03 16:27 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description supareno 2009-10-28 14:16:09 UTC
In the Tomcat documentation for JDBC [1], you give an example of resource definition with the mysql option "autoReconnect=true". 

Will it be possible to remove or specified in the tomcat documentation that the
autoreconnect option for the jdbc context definition is not recommended by Mysql [2] and that it could be better to use the validationQuery parameter[3] in the
context definition. I saw this exception arrived 2 times (in 2 differents
projects and replacing the option by validationQuery solved the problem).
 
I suppose that the Tomcat documentation is followed by thousand of people
(newcomers and others) so they will use the standard tomcat sample (with the
autoReconnect option) and won't be aware that this option is not recommended.

I set a "minor" severity but it may be "trivial", i don't know.

[1]:http://tomcat.apache.org/tomcat-6.0-doc/jndi-datasource-examples-howto.html#Database%20Connection%20Pool%20(DBCP)%20Configurations 
[2]:http://dev.mysql.com/doc/refman/5.0/en/connector-j-reference-configuration-properties.html
[3]:http://confluence.atlassian.com/display/JIRA/Surviving+Connection+Closures
Comment 1 Mark Thomas 2009-11-03 16:27:46 UTC

*** This bug has been marked as a duplicate of bug 47235 ***