Mi Reflejo wrote:
Umh. It is working identically to bearerbox.
dbpool_conn_consume is moving in connections (max-connections) until
the list is empty. At this point, gwlist_consume waits forever.
Sqlbox is doing the right things. We need to fix dbpool of kannel.
patch for dbpool? ;)
Stipe
I have been looking into the sources a little bit.
But I cannot seem to find the spot where bearerbox reconnects to the MySQL
daemon.
I figure dbpool_check() should be called somewhere.
Of course, I can just put a call to that function somewhere in sqlbox.
But I would like to follow a little bit
Actually dbpool_check is not used :).
Lets asume that we are using mySQL.
Before each query, dbpool_conn_consume is called.
dbpool_conn_consume call the function: p-db_ops-check(pc-conn)
(declaration: p-db_ops = mysql_ops; and .check = mysql_check_conn,)
Check function does a mysql_ping and
@kannel.org
Subject: Re: sqlbox mysql re-connection (question)
Actually dbpool_check is not used :).
Lets asume that we are using mySQL.
Before each query, dbpool_conn_consume is called.
dbpool_conn_consume call the function: p-db_ops-check(pc-conn)
(declaration: p-db_ops = mysql_ops; and .check
@kannel.org
Subject: Re: sqlbox mysql re-connection (question)
Actually dbpool_check is not used :).
Lets asume that we are using mySQL.
Before each query, dbpool_conn_consume is called.
dbpool_conn_consume call the function: p-db_ops-check(pc-conn)
(declaration: p-db_ops = mysql_ops; and .check
