[
https://issues.apache.org/jira/browse/THRIFT-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866269#action_12866269
]
Rob Slifka commented on THRIFT-692:
-----------------------------------
Hi Philip,
I tend to think of this as an assert.
In this case, you're controlling both ends of the pipe: the Thrift server pool
and the pool on the client side. Using Commons Pool, it's a configuration
option for the size of the pool, so we never ran into this after setting them
both to be the same.
> RejectedExecutionException under load in Java TThreadPoolServer
> ---------------------------------------------------------------
>
> Key: THRIFT-692
> URL: https://issues.apache.org/jira/browse/THRIFT-692
> Project: Thrift
> Issue Type: Bug
> Components: Library (Java)
> Environment: Linux
> Reporter: Rob Slifka
> Priority: Critical
>
> Under load, we're seeing this unpredictably. We're using a version of HEAD
> from August of 2009 since it's worked so well for us. The code that we're
> running against are essentially stubs for when we hook up to "real" Thrift
> server. I.e. our Thrift calls are answered by a server that returns literals
> without doing any "work" per se.
> {code}
> Starting Thrift server on 9090...
> Exception in thread "main" java.util.concurrent.RejectedExecutionException
> at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1760)
> at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)
> at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658)
> at
> org.apache.thrift.server.TThreadPoolServer.serve(TThreadPoolServer.java:185)
> at com.foo.ipc.server.ThriftServer.main(Unknown Source)
> {code}
> Ring a bell?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
