~vinchen13/mysql-proxy/fix_some

~vinchen13/mysql-proxy/fix_some_bugs » Changes from revision 5

From Revision 5

Rev	Summary	Authors	Date
5	fix the stuck problem when the clients' concurrency too much fix the stuck problem when the clients' concurrency too much While doing stress testing, 5000 connections execute a short query through proxy constantly，the proxy would have no response after a while. If strace the proxy process, and all the event threads are always logged like this : sendto(4, ".", 1, 0, NULL, 0 <unfinished ...> The problem come from the function chassis_event_add, and there are too much event when the clients' concurrency too much. Now I modified the implement of chassis_event_add by using random num to determin the handle thread's event_base. Moreover, the event base of libevent must be thread-safe. So the proxy should depend on libevent which version no less than 2.0(event base is thread safe https://raw.github.com/libevent/libevent/patches-2.0/whatsnew-2.0.txt). The problem is critical, and see also in http://bugs.mysql.com/bug.php?id=63908&error=no http://forums.mysql.com/read.php?146,433299,433299#msg-433299	vin	12 years ago
4	fix the potential concurrent problems in chassis_private->co... fix the potential concurrent problems in chassis_private->cons chassis_private->cons is a GPtrArray, and it's not thread-safe. But all the event thread can add or remove connections at one time. So it should have some concurrent protection while adding or removing connections. So, add one mutex to protect chassis_private->cons. By the way, maybe add a connection would not have the concurrent problems, because only the main thread can do it. For security, all the global variable shoule be protected when visiting.	vin	12 years ago
3	fixed up the bug of decoding the string of Protocol 4.0 fixed up the bug of decoding the string of Protocol 4.0 In protocol 4.0, a string at the end of the packet is not null terminated. But proxy use interface "network_mysqld_proto_get_gstring" to decode all null-terminated string. In fact, some tail string in packet may considered to be error(e.g. "network_mysqld_proto_get_auth_response"), leading to wrong error message. For example, 4.0 client connect the proxy, can not get the error message "4.0 protocol is not supported"	vin	12 years ago
2	fix bug for NULL pointer exeception fix bug for NULL pointer exeception	vin	12 years ago
1	origin source code from mysql-proxy-0.8.2 origin source code from mysql-proxy-0.8.2	vin	12 years ago