[
https://issues.apache.org/jira/browse/THRIFT-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805133#action_12805133
]
David Reiss commented on THRIFT-692:
------------------------------------
>From
><http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/ThreadPoolExecutor.html>,
> "If a request cannot be queued, a new thread is created unless this would
>exceed maximumPoolSize, in which case, the task will be rejected." We use a
>SynchronousQueue, so requests can never be queued. This is the expected
>result when you exceed the maximum threadpool size. Please close this bug as
>invalid if this answers your question.
> 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.
