Hi Andrew, Thanks for the quick reply.
We use different providers, but often ec2. We use a long playing contexts, ~1 hour (after 1 hour they are closing and removed from the cache), but sometimes we have a bug: java.util.concurrent.RejectedExecutionException: Task [delegate=[method=AWSInstanceAsyncClient.describeInstancesInRegion, request=POST https://ec2.us-west-1.amazonaws.com/ HTTP/1.1], executionList=com.google.common.util.concurrent.ExecutionList@161293c] rejected from java.util.concurrent.ThreadPoolExecutor@1ce813d[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 484] 2013/6/13 Andrew Phillips <andr...@apache.org> > How to check the closed ComputeContext or not? >> > > I don't think there's an "obvious" call you can make, unfortunately. > Which provider are you using and, perhaps more importantly, could you > describe your use case in a bit more detail..? > > Thanks! > > ap > -- Sincerely yours Anton Panasenko Team Lead / Senior Engineer Cometera Inc Skype: anton.panasenko Phone: +380635892683 +79179838291 Email: apanase...@cometera.com
