ASF GitHub Bot commented on ARTEMIS-1324:

Github user clebertsuconic commented on a diff in the pull request:

    --- Diff: docs/user-manual/en/critical-analysis.md ---
    @@ -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-timeout)
    +analyze-critical-halt | Should the VM be halted upon failures (default 
    --- End diff --
    I can use management.  
    I wasn't sure it would be useful. As if the JVM is in bad state would the 
message arrive ?

> Critical Analysis and deadlock detection on broker
> --------------------------------------------------
>                 Key: ARTEMIS-1324
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1324
>             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

Reply via email to