[asterisk-bugs] [Asterisk 0015059]: If the database loses connection for a few seconds, no cdr gets written ever

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15059 
====================================================================== 
Reported By:                falves11
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   15059
Category:                   CDR/cdr_adaptive_odbc
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2 
SVN Revision (number only!): 192874 
Request Review:              
====================================================================== 
Date Submitted:             2009-05-08 01:19 CDT
Last Modified:              2009-05-15 10:10 CDT
====================================================================== 
Summary:                    If the database loses connection for a few seconds,
no cdr gets written ever
Description: 
This is a major and potentially very costly problem with cdr_adaptive.
Suppose I close the firewall in the database (SQL 2005) for 10 seconds.
Then no CDR gets saved to the database ever. ODBC keeps working, I mean, it
bounces back, because successive calls to func_odbc do work. But
cdr_adapative does not any reseiliance, it just never writes a cdr anymore.
It happpened to me twice alrfeady in production.
====================================================================== 

---------------------------------------------------------------------- 
 (0104830) tilghman (administrator) - 2009-05-15 10:10
 https://issues.asterisk.org/view.php?id=15059#c104830 
---------------------------------------------------------------------- 
Again, there is nothing I can do about this, because I cannot reproduce the
issue.  You'll need to workup a repeatable case for me to be able to track
this down, preferably with a non-MS-SQL-Server connection (mysql or
postgres).  I can leave this open for another 5 days, but if you cannot
create such a case, this bug will again need to be closed. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-15 10:10 tilghman       Note Added: 0104830                          
2009-05-15 10:10 tilghman       Status                   assigned => feedback
======================================================================