[asterisk-bugs] [Asterisk 0014319]: [patch] describe idlecheck in res_odbc.conf.sample more clear

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14319 
====================================================================== 
Reported By:                klaus3000
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   14319
Category:                   Documentation
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-01-23 01:20 CST
Last Modified:              2009-01-26 03:19 CST
====================================================================== 
Summary:                    [patch] describe idlecheck in res_odbc.conf.sample
more clear
Description: 
Hi!

I did not understand correctly what this parameter does unless reading the
code. I think adding this text will make things more clear.
====================================================================== 

---------------------------------------------------------------------- 
 (0098721) klaus3000 (reporter) - 2009-01-26 03:19
 http://bugs.digium.com/view.php?id=14319#c98721 
---------------------------------------------------------------------- 
My setup is: 
Asterisk 1.4.22/23 and unixODBC 2.2.11-16 and libmyodbc 3.51.15r409-4 and
mysql server 5.0.51a-21.

My problems were, that very often a query failed, the connection was
closed, a new connection was established and then the query succeeded. And
the problem was that the reconnecting always took 5 seconds (I guess a
timeout somewhere in libodbc).

So I began tweaking connection settings. The idlecheck solved the 5
seconds timeout issue, but introduced a IMO not nice behavior
(disconnect/connect).

So I tried other things. Now I used a TCP connection to the MySQL server
and updated to Asterisk 1.4.23 (which has some ODBC changes) and until now
the DB connection works fine.

So, my problems are solved now, nevertheless I thought extending the
documentation is a good idea to prevent other users to missnderstand the
meaning of the idlecheck parameter (just as I did).

Thus, back to the topic - I do not understand why you reject this IMO
useful documentation. users which do not have connection problem will not
use the parameter any. Users which run into CD issues will try to find some
parameters for tuning, and these users for sure are interested what the
idlecheck parameter is about in detail. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-26 03:19 klaus3000      Note Added: 0098721                          
======================================================================