Uploaded image for project: 'AMQ Documentation'
  1. AMQ Documentation
  2. AMQDOC-2675

REQ: new options for critical analysis of deadlock detection


    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: 7.0, 7.0.3
    • Fix Version/s: None
    • Component/s: Broker DOC
    • Labels:


      Please see the upstream for info. This is some of what I found quickly browsing the code PR.

      +If the response time goes beyond a configured timeout, the broker is considered unstable and an action will be taken to either shutdown the broker or halt the VM.
      +You can use these following configuration options on broker.xml to configure how the critical analysis is performed.
      +Name | Description
      +:--- | :---
      +analyze-critical | Enable or disable the critical analysis (default true)
      +analyze-critical-timeout | Timeout used to do the critical analysis (default 120000 milliseconds)
      +analyze-critical-check-period | Time used to check the response times (default half of analyze-critical-timeout)
      +analyze-critical-halt | Should the VM be halted upon failures (default false)
      — End diff –

      i would imagine a health monitor/critical analysers threads are independent of core flow, as such it should detect and action if a component isn't responding or non healthy state. As such it should be able to declare that state back.

      e.g. if JVM bad state due to deadlock, that deadlock should only be affecting the threads/flow where the deadlock is , as such this component should still be servicing.

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  dmuntima Divya Muntimadugu
                  sjayatredhat Susan Jay
                • Votes:
                  0 Vote for this issue
                  2 Start watching this issue


                  • Created: