Summary:	ASTERISK-24426: CDR Batch mode: size used as time value after first expire
Reporter:	Shane Blaser (shaneblaser)	Labels:	Asterisk12
Date Opened:	2014-10-16 12:05:01	Date Closed:	2014-10-16 16:15:25
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	CDR/General
Versions:	12.5.0	Frequency of Occurrence	Constant
Related Issues:
Environment:	CENTOS 6.5 2.6.32-431.29.2.el6.x86_64 #1 SMP Tue Sep 9 21:36:05 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux	Attachments:	( 0) ASTERISK-24426.diff
Description:	{noformat} batch=yes size=200 time=15 {noformat} (this issue happens with all values I try) after first time expire the time value is set to the record value Below is a sample after a restart: {noformat} Connected to Asterisk 12.5.0 currently running on resale01 (pid = 12363) resale01*CLI> cdr show status Call Detail Record (CDR) settings ----------------------------------  Logging:                    Enabled  Mode:                       Batch  Log unanswered calls:       No  Log congestion:             No * Batch Mode Settings  -------------------  Safe shutdown:              Enabled  Threading model:            Scheduler plus separate threads  Current batch size:         0 records  Maximum batch size:         200 records  Maximum batch time:         15 seconds  Next batch processing time: 11 seconds * Registered Backends  -------------------    csv    cdr_manager (suspended)    cdr-custom    Adaptive ODBC resale01*CLI> cdr show status Call Detail Record (CDR) settings ----------------------------------  Logging:                    Enabled  Mode:                       Batch  Log unanswered calls:       No  Log congestion:             No * Batch Mode Settings  -------------------  Safe shutdown:              Enabled  Threading model:            Scheduler plus separate threads  Current batch size:         0 records  Maximum batch size:         200 records  Maximum batch time:         15 seconds  Next batch processing time: 2 seconds * Registered Backends  -------------------    csv    cdr_manager (suspended)    cdr-custom    Adaptive ODBC resale01*CLI> cdr show status Call Detail Record (CDR) settings ----------------------------------  Logging:                    Enabled  Mode:                       Batch  Log unanswered calls:       No  Log congestion:             No * Batch Mode Settings  -------------------  Safe shutdown:              Enabled  Threading model:            Scheduler plus separate threads  Current batch size:         0 records  Maximum batch size:         200 records  Maximum batch time:         15 seconds  Next batch processing time: 0 seconds * Registered Backends  -------------------    csv    cdr_manager (suspended)    cdr-custom    Adaptive ODBC resale01*CLI> cdr show status Call Detail Record (CDR) settings ----------------------------------  Logging:                    Enabled  Mode:                       Batch  Log unanswered calls:       No  Log congestion:             No * Batch Mode Settings  -------------------  Safe shutdown:              Enabled  Threading model:            Scheduler plus separate threads  Current batch size:         0 records  Maximum batch size:         200 records  Maximum batch time:         15 seconds  Next batch processing time: 199 seconds * Registered Backends  -------------------    csv    cdr_manager (suspended)    cdr-custom    Adaptive ODBC resale01*CLI> {noformat}
Comments:	By: Shane Blaser (shaneblaser) 2014-10-16 12:06:20.287-0500 this issue also happen in 12.6 ... By: Matt Jordan (mjordan) 2014-10-16 16:10:08.066-0500 Whoops. The attached patch (ASTERISK-24426.diff) should fix the issue.