I've found all JMXEnabledThreadPool and JMXConfigurableThreadPool are
constructed with LinkedBlockingQueue as workQueue, and the LBQs are
constructed by the default constructor. It means the queue has
Integer.MAX_VALUE capacity.
In other words, any tasks won't be rejected (Dropped) before we would
Right. We explicitly manage overload by dropping tasks that won't
complete in time, in OutboundTcpConnection and MessagedDeliveryTask.
On Wed, Feb 29, 2012 at 6:01 AM, Maki Watanabe wrote:
> I've found all JMXEnabledThreadPool and JMXConfigurableThreadPool are
> constructed with LinkedBlockingQu
Thanks. I understood the policy.
2012/3/1 Jonathan Ellis :
> Right. We explicitly manage overload by dropping tasks that won't
> complete in time, in OutboundTcpConnection and MessagedDeliveryTask.
>
> On Wed, Feb 29, 2012 at 6:01 AM, Maki Watanabe
> wrote:
>> I've found all JMXEnabledThreadPoo
