You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Megaraj Mahadikar (JIRA)" <ji...@apache.org> on 2019/01/30 17:05:00 UTC

[jira] [Created] (AMQ-7144) Issue with Timer in AbstactInactivityMonitor

Megaraj Mahadikar created AMQ-7144:
--------------------------------------

             Summary: 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


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)