I have a suspicion: the ns_set used for the configure variables is implemented mutex-lock-free, developed probably under the assumption that only the main thead reads modifies config data during startup. Since the "connsperthread" is read/written back during the startup there can be a race condition.
This would explain the situation, since it depends on the configuration, speed of the machine, .... i will look into this deeper, probably at the weekend.
