Comment 5 for bug 430637

This bug will be fixed in 1.1.

Currently the only solution is to set the variable pbxt_max_threads high enough that the internal thread requirement is not exceeded. pbxt_max_threads cannot be updated dynamically so the server must be restarted to change the value. Setting pbxt_max_threads to zero cause PBXT to estimate the thread requirement based on the max_connections setting. So depending on the number of background tasks run by MySQL, it is always possible to run into the error described here.

In 1.1 we plan to change the semantics of pbxt_max_threads. pbxt_max_threads will then be an upper limit to the number of threads that may be created. Set to zero will mean unlimited.

In order to do this, the thread array inside PBXT must be dynamically reallocated, or we must remove the dependency on this array. This is seen as a significant change which could affect stability and is therefore not desirable in the current RC series.