10 Dec
2007
10 Dec
'07
8:28 a.m.
On Dec 10, 2007 at 07:20, Greger V. Teigre <greger(a)teigre.com> wrote:
[removed sems and semsdev from cc]
SIP wrote:
MySQL 5.0.X automatically times out its sockets after a hardcoded period
of time. Unless you have configured the socket to auto reconnect (see
http://www.ideasip.com/support/utils/my_con.c.SER2 ), after a little
while, the socket will just time out and you will have to restart SER in
order to connect to the database (it will throw errors).
I thought that issue was resolved. Can you check the tracker ticket and
verify that it is scheduled for ser 2.0 release?
It is fixed in a different way in 2.1, but it was not backported to 2.0
(see http://lists.iptel.org/pipermail/serdev/2007-June/010460.html).
Jan, have you forgotten to backport it or is there some other reason?
(patch for 2.0 attached)
Andrei
Secondary
(but no less important) items that are a must-have:
-MySQL (I'm voting for 5 series here, but that will require my patch for
the mysql code in SER 2.0)
why the patch?