| Bug #35705 | State of ER_CON_COUNT_ERROR is different on linux as on windows | ||
|---|---|---|---|
| Submitted: | 31 Mar 2008 12:09 | Modified: | 2 Apr 2008 12:43 |
| Reporter: | Salman Rawala | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Errors | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | ER_CON_COUNT_ERROR | ||
[31 Mar 2008 12:34]
Sveta Smirnova
Thank you for the report. I can not repeat described behavior with current development sources, although bug (on Linux) is repeatable with versions 5.1.22 and 5.1.23. Please wait next release.
[2 Apr 2008 12:43]
Alexander Nozdrin
It's a duplicate of Bug#35289: Too many connections -- wrong SQL state in some case.

Description: State of ER_CON_COUNT_ERROR is ! ERROR 00000: Too many connections whereas on Windows it is: ! ERROR HY000: Too many connections How to repeat: --echo ## Setting value of max_connection to 2 ## SET @@global.max_connections = 2; --echo ## Creating new connection ## connect (test_con1,localhost,root,,); connection test_con1; --echo ## Inserting and fetching data of length greater than 1024 ## INSERT into t1(name) values("Record_1"); --echo ## Creating and connecting to new connection test_con2 ## connect (test_con2,localhost,root,,); connection test_con2; INSERT into t1(name) values("Record_2"); SELECT * from t1; --echo ## Creating new connection## --disable_query_log --Error ER_CON_COUNT_ERROR connect (test_con3,localhost,root,,); --enable_query_log