mwinkel-dev

@WhoBrokeTheBuild fixed this issue with PR #2747.

Have not yet investigated and identified the root cause of this issue. However, did notice that the behavior changed when pointed the test to a different `mdsip` server. Must compare...

There is already a test case for this bug in the IDL test harness.

Checked the `systemd` config files on the `mdsip` server that fails the 64 concurrent connections test. No obvious limits spotted. Also, PR #2644 made no difference in the limit.

Was able to easily reproduce the problem with Python thin-client `closeAllTrees()` using this configuration: - current MDSplus alpha - Ubuntu 20 - and two different MDSplus archive servers Also confirmed...

We should check the Python regression tests to see if `closeAllTrees()` is tested. And if not, should add that to the tests.

Preliminary investigation points to three problems: - segfault occurs when dispatching at high rates (e.g., 100+ actions per second) and can be mitigated by throttling to 10 actions per second...

The connection id being overwritten might be a threading problem.

The connection id was indeed being clobbered by another thread. However, that is part of issue #2731, so is described there. And there is a fourth problem: - Improper checking...

Turns out that the throttle on the dispatch rate is also part of Issue #2731. So, is described there.