[asterisk-bugs] [JIRA] (ASTERISK-24426) CDR Batch mode: size used as time value after first expire

[Shane Blaser (JIRA)]

Shane Blaser created ASTERISK-24426:
---------------------------------------

             Summary: CDR Batch mode: size used as time value after first expire
                 Key: ASTERISK-24426
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24426
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: CDR/General
    Affects Versions: 12.5.0
         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
            Reporter: Shane Blaser


batch=yes
size=200
time=15

(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:

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> 




--
This message was sent by Atlassian JIRA
(v6.2#6252)