Closed andreiolaru-ro closed 2 years ago
Could be solved after commit 63ffdd4a5e967349ab41e7269a263cccbf209a3a but could also be a race condition somewhere.
Will not trey to avoid the exception (e.g. by checking if messagingShard
is null
in the idea that it may reappear.
Exception appears again when multiple pylons, not all offering messaging, exist.
Solved in 99a606e. See commit message.
-node main -pylon local:mainPylon use-thread