Bug #2200
Updated by Henning Blohm 5 days ago
Currently the built-in thread pool does not reset the context class loader of a thread that performs work so that a unit of work may have an arbitrary context class loader set while performing its work, given that some other piece of work set a context class loader and omitted to unset it again. h2. Acceptance Criteria * Before and after performing any application work, the context class loader of the executing pool thread is set to the caller's context class loader * In the case of getAs/runAs, the context class loader is simply not altered null