Just had a talk with . He presented me a problem in reading the data from the CMR leads to some non-responsive service calls after some time..
His setup was to every 5 seconds do the following:
get overview on all agents
get details of each connected agent (in his case only 1)
load invocation sequence overview for last 5 seconds
We go the thread dump during such non-responsive calls and what can be seen is that the "problem" most likely lies in threads with prefix btpool0-. This is the Jetty pool for answering to HTTP requests. Funny thing is that the thread numbers are always rising, so thread dump also shows the thread with number btpool0-117.. Since it might be pool with min-max threads this can be OK, but still..
Also notice the block on the socketRead0() method.. We did another thread dump few minutes later and thread btpool0-117 was still running in this method. This is very strange.
This should be easy to reproduce. Also think we should also be careful that this is happening when CMR is running in Windows.