Hi Iñaki, sorry for losing the contact with this thread....
The idea is to identify what was the last mysql query before the query generating the error - this is why I suggested using the pids to be able to correlate all the queries coming from the *same* process (so on the same connection). Once we identify the prev query, we have a starting point in investigating why it didn't release the result. Please let me know if still not clear on what I'm talking about :). Thanks and regards, Bogdan Iñaki Baz Castillo wrote: > El Miércoles, 26 de Noviembre de 2008, Bogdan-Andrei Iancu escribió: > >> What you can do is to log the mysql traffic and which opensips process >> generates it, and when the error pops out, to see what was the last >> mysql query performed by the guilty process. >> > > Hi, I want to invest some time on this issue since it occurs more than very > often (and it's just a testing server with 2 users). > > Do you mean that I should enabled the mysql query log? I've already enabled > it > and will check it. But I don't understant when you suggest "which opensips > process generates it", why is important which process does it? > > Thanks. > > _______________________________________________ Devel mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
