Completed local merge of trunk into qa-refactor-namespace. Ran qa and regression test suites.
Performed some profiling on outrigger stress tests, found blocking queue in org.apache.river.thread.ThreadPool to be a significant hot spot. Tested all blocking queue implementations, no improvement. Wild idea: don't pool threads, create new, let used threads be gc'd after completion. Test result; hot spot eliminated, less threads required. I didn't expect that result. Hotspot's now serialization. Going to test jeri mux for graceful degredation under load when oome occurs next. Regards, Peter. Sent from my Samsung device.