mysql> SHOW VARIABLES LIKE "%version%";
+-------------------------+------------------------------+
| Variable_name | Value |
+-------------------------+------------------------------+
| innodb_version | 1.1.8 |
| protocol_version | 10 |
| slave_type_conversions | |
| version | 5.5.25 |
| version_comment | MySQL Community Server (GPL) |
| version_compile_machine | x86 |
| version_compile_os | Win64 |
+-------------------------+------------------------------+
If I run the same script multiple times, a run will eventuallu hang on an execute statement. The sever shows the client process (shw processlist \G) at first, soon the process goes away but the program never moves again until killed. When I enable a trace the internal trace statment is awlays >parse_params statement ... ( followed by the text of the actual SQL ) ... I'd like to note that the program does not do a statment finish and disconnect
when it ends. I do this purposely to recreate the problem which occured in my larger program when it needs to either re-coonect from a timeout or closes down less than elegant. The above is to easily reproducable and make the interaction with the sever to see unreliable and unstable ... Does anyone have a soloution to fix this ?
+-------------------------+------------------------------+
| Variable_name | Value |
+-------------------------+------------------------------+
| innodb_version | 1.1.8 |
| protocol_version | 10 |
| slave_type_conversions | |
| version | 5.5.25 |
| version_comment | MySQL Community Server (GPL) |
| version_compile_machine | x86 |
| version_compile_os | Win64 |
+-------------------------+------------------------------+
If I run the same script multiple times, a run will eventuallu hang on an execute statement. The sever shows the client process (shw processlist \G) at first, soon the process goes away but the program never moves again until killed. When I enable a trace the internal trace statment is awlays >parse_params statement ... ( followed by the text of the actual SQL ) ... I'd like to note that the program does not do a statment finish and disconnect
when it ends. I do this purposely to recreate the problem which occured in my larger program when it needs to either re-coonect from a timeout or closes down less than elegant. The above is to easily reproducable and make the interaction with the sever to see unreliable and unstable ... Does anyone have a soloution to fix this ?