[asterisk-bugs] [JIRA] (ASTERISK-22708) ODBC negative_connection_cache option not respected

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-22708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-22708:
------------------------------------

    Assignee: JoshE
      Status: Waiting for Feedback  (was: Triage)

Can you provide another log, but including the DEBUG message type , with debug turned up to 5 "core set debug 5" or set in asterisk.conf?

Get at least 20 or 30 lines around where the connection attempts are occurring.
                
> ODBC negative_connection_cache option not respected
> ---------------------------------------------------
>
>                 Key: ASTERISK-22708
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22708
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_odbc
>    Affects Versions: 11.5.1
>         Environment: CentOS 6
>            Reporter: JoshE
>            Assignee: JoshE
>         Attachments: odbc_errors.txt
>
>
> The database failover behavior does not work as expected with MySQL / MariaDB on the databases.  Based on a reading of the documentation and source, I would expect this config in res_odbc to behave differently than it does:
> [config]
> enabled => yes
> dsn => MySQL
> username => user
> password => hidden
> pre-connect => yes
> sanitysql => select 1
> idlecheck => 30
> share_connections => yes
> connect_timeout => 2
> negative_connection_cache => 300
> [config_2]
> enabled => yes
> dsn => MySQL-2
> username => user
> password => hidden
> pre-connect => yes
> sanitysql => select 1
> idlecheck => 30
> share_connections => yes
> connect_timeout => 2
> negative_connection_cache => 300
> Based on my reading, a connect timeout getting hit should cause a negative cache where new connections are not attempted for 300 seconds.  That does not occur in practice.  The server continually attempts to reconnect to the server, meanwhile the entire system becomes totally unusable until the database connection is restored.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira