For a while I've suspected that the request processor threads fill up leaving the application useless. I reduced the number of threads to ease the das2 server with Dan's plots, so now I see the case where slow processes are not cancelled leaving the RequestProcessor facility occupied until the tasks are finally complete. This morning I got into a situation where the Recent History dialog would fail because it would get stuck in the RequestProcessor.
For now I'm going to increase the number of processor threads back to the old level and govern the threads within the das2server plugin. Also, items not associated with data loading, like the Recent History dialog, will be performed outside of the request processor facility.
I have not seen any problems with this. Also I've seen cases where clearly it's running out of threads and handling it nicely.