1. Deprecate mordred (Add notes about its deprecation and the use of dbcp)
2. Add better default for dbcp (insert max_idle and max_wait)
3) Add a link to dbcp options documentation
4) Remove autoReconnect from the documented jdbc url for mysql (autoReconnect has been deprecated and has known problems if used in combination with dbcp) http://www.mail-archive.com/ojb-user@db.apache.org/msg15426.html http://lists.mysql.com/java/4928
Description
The summary already describe it all:
1. Deprecate mordred (Add notes about its deprecation and the use of dbcp)
2. Add better default for dbcp (insert max_idle and max_wait)
3) Add a link to dbcp options documentation
4) Remove autoReconnect from the documented jdbc url for mysql (autoReconnect has been deprecated and has known problems if used in combination with dbcp)
http://www.mail-archive.com/ojb-user@db.apache.org/msg15426.htmlhttp://lists.mysql.com/java/4928
1) Deprecate, yes. Remove, no. We'll end up removing it when we require changes for transactions, but in the meantime it provides a backup in case of DBCP problems.
4) Leave for modred, remove for DBCP. Mordred has issues if the driver doesn't do the reconnecting.
Noel J. Bergman added a comment - 04/Sep/06 01:02 AM 1) Deprecate, yes. Remove, no. We'll end up removing it when we require changes for transactions, but in the meantime it provides a backup in case of DBCP problems.
4) Leave for modred, remove for DBCP. Mordred has issues if the driver doesn't do the reconnecting.
Stefano Bagnara added a comment - 12/Sep/06 12:58 PM the autoReconnect change should be investigated much more. I saw some unexpected error since I removed it but I haven't had time to look in deeper.
Task
Open
Major
DB Access tasks: deprecate mordred, add better defaults for dbcp (document them), remove autoReconnect from sample url
4) Leave for modred, remove for DBCP. Mordred has issues if the driver doesn't do the reconnecting.