[
https://issues.apache.org/jira/browse/AMQ-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757406#comment-16757406
]
Christopher L. Shannon edited comment on AMQ-7144 at 1/31/19 4:02 PM:
----------------------------------------------------------------------
Another reason could be out of file descriptors for the process or something
random like that I suppose...but maybe not. I don't remember if a new thread
creates a new file descriptor (it actually probably doesn't and just shares the
same process the more I think about it so that most likely isn't the reason)
Either way it seems like the error would be because you are out of resources
I'm not sure we should be just catching the exception and continuing on as that
isn't going to help in that case.
was (Author: christopher.l.shannon):
Another reason could be out of file descriptors for the process I suppose...but
if you are out of resources and that is causing the error then I'm not sure we
should be just catching the exception and continuing on as that isn't going to
help.
> 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)
