[ previous ] [ next ] [ threads ]
 To :  yate@v...
 From :  Bill Simon <bill@b...>
 Subject :  mysqldb connection errors
 Date :  Tue, 12 May 2015 09:05:37 -0400
I'm experiencing something that at first I thought was a bug in my SQL script but now believe to be a bug or incorrect handling of errors in Yate code.

The db setup is mysql, with a connection pool size 5. Yate is calling a stored procedure through the register module for routing.

I started to see errors in the Yate log like this:

mysqldb:WARN> Query for 'db.2' failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'NULL' at line 1

At the same time, the error counter was building up when I looked in rmanager at "status mysqldb".

So it seems there is a problem with the procedure. But trying the same call again, it works. Then it does not work. I also ran the procedure manually from the MySQL GUI tools and from the command line. Everything works fine. I reviewed it for errors.

The only consistent thing about the error is the db connection number in the Yate log. It appears that whenever the connection 'db.2' from the pool is used, we get the error. So I killed off the TCP connections between Yate and the database so that each would reconnect and now the error is no longer happening.

Now I believe that there is a connection error and it is not being handled properly, but Yate or the mysql driver within is giving a misleading error that looks like a SQL syntax error.

I do not know how to proceed from here. Can anyone give some advice?