[asterisk-bugs] [Asterisk 0015864]: idle odbc connections are not cleaned up

[Asterisk Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=15864 
====================================================================== 
Reported By:                kobaz
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   15864
Category:                   Resources/res_odbc
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.0.14 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 not fixable
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-09-09 09:49 CDT
Last Modified:              2009-09-10 18:07 CDT
====================================================================== 
Summary:                    idle odbc connections are not cleaned up
Description: 
When using queries defined in func_odbc, asterisk will periodically
'forget' about connections it's already made, and will think it's
disconnected with the database.

The query will fail for some reason, even though a connection is already
present.  A new connection will be made.  The old connection is not cleaned
up.  And after a while the max connection limit on the server is hit and
asterisk can't make any more odbc connections.

I'm not sure if this is a problem with the unixodbc driver, or with
asterisk.  My short term fix is a script that runs around killing old idle
postgres connections from asterisk.
====================================================================== 

---------------------------------------------------------------------- 
 (0110545) tilghman (administrator) - 2009-09-10 18:07
 https://issues.asterisk.org/view.php?id=15864#c110545 
---------------------------------------------------------------------- 
That is very clearly a database driver issue, not something that we can
address in Asterisk. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-10 18:07 tilghman       Note Added: 0110545                          
2009-09-10 18:07 tilghman       Status                   feedback => closed  
2009-09-10 18:07 tilghman       Resolution               open => not fixable 
======================================================================