[
https://issues.apache.org/jira/browse/AMQ-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757214#comment-16757214
]
Megaraj Mahadikar edited comment on AMQ-7144 at 1/31/19 1:10 PM:
-----------------------------------------------------------------
There was a exhaustion of the thread pools in the executor service -
ASYNC_TASKS due to which there was a RejectionExecutionException. Ideally any
application code must be resilient to the thread pool exhaustion and must not
cause the broker to end up in an inconsistent state.
was (Author: megarajtm):
There was a exhaustion of the thread pools in the executor service -
ASYNC_TASKS due to which there was a RejectionExecutionException. Ideally any
application code must be resilient to the thread pool exhaustion and must not
cause the broker to end up in a inconsistent state.
> Issue with Timer in AbstactInactivityMonitor
> --------------------------------------------
>
> Key: AMQ-7144
> URL: https://issues.apache.org/jira/browse/AMQ-7144
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.x
> Reporter: Megaraj Mahadikar
> Priority: Critical
>
> Hi,
> If there is an exception in the Timers that schedules the write checker or
> read check, then this timer is cancelled (refer the java docs of
> java.util.Timer). As a result of this any new connection to the broker will
> never go through since the same Timer is used again to schedule the write or
> read checker. This issue affects the complete broker and the broker needs to
> be restarted to recover from this issue.
> Ideally any such exceptions within the Timer must be never thrown back which
> causes the Timer to be cancelled.
> Regards,
> Megaraj
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
