activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1324) Critical Analysis and deadlock detection on broker
Date Sun, 06 Aug 2017 04:46:00 GMT


ASF GitHub Bot commented on ARTEMIS-1324:

Github user michaelandrepearce commented on a diff in the pull request:
    --- Diff: docs/user-manual/en/ ---
    @@ -0,0 +1,32 @@
    +# Critical Analysis of the broker
    +There are a few things that can go wrong on a production environment:
    +- Bugs, for more than we try they still happen! We always try to correct them, but that's
the only constant in software development.
    +- IO Errors, disks and hardware can go bad
    +- Memory issues, the CPU can go crazy by another process
    +For cases like this, we added a protection to the broker to shut itself down when bad
things happen.
    +We measure time response in places like:
    +- Queue delivery (add to the queue)
    +- Journal storage
    +- Paging operations
    +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-halt | Should the VM be halted upon failures (default false)
    --- End diff --
    I was more saying:
    how does an outside observer view the state. Eg many people rely on logs or JMX 

> Critical Analysis and deadlock detection on broker
> --------------------------------------------------
>                 Key: ARTEMIS-1324
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: clebert suconic
>            Assignee: clebert suconic
>            Priority: Critical
>             Fix For: 2.3.0

This message was sent by Atlassian JIRA

View raw message