The issue is I don't provide the thread. JBossWeb or the EJB3 runtime provide the thread, and it periodically invokes my integration code telling it to "backgroundProcess". JBC eviction is then part of that background process work. Perhaps a clearer way to conceptualize the problem is to think of cache eviction as one step in an overall larger task. Say, for example, step 2 of 3. I want to control the order of execution of the whole task. JBC passing one step to an executor on its own schedule doesn't let me do that. If allowing configuration for this is too ugly, I could just drop in a custom executor that just drops tasks on the floor. The main thing for me is to make sure the API still exists for an external thread to run eviction (get region, get the eviction policy, trigger the policy to run.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164585#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...