Closed MercusChan closed 6 years ago
During development, in some cases, swellrt server is very busy. I need to restart the docker container to solve.
In fact, I don't know how to repeat, but I had collected the thread dump before restart the docker container.
Anyway to avoid not response?
thread_dump_1.txt thread_dump_2.txt
See https://github.com/SwellRT/swellrt/issues/243 Major issues are solved in 2.0.x-beta versions
During development, in some cases, swellrt server is very busy. I need to restart the docker container to solve.
In fact, I don't know how to repeat, but I had collected the thread dump before restart the docker container.
Anyway to avoid not response?
thread_dump_1.txt thread_dump_2.txt