[ 
https://issues.apache.org/jira/browse/ARTEMIS-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14655170#comment-14655170
 ] 

ASF GitHub Bot commented on ARTEMIS-147:
----------------------------------------

GitHub user ryanemerson opened a pull request:

    https://github.com/apache/activemq-artemis/pull/110

    [ARTEMIS-147] Add WARN log when setting connection-ttl OR connection-…

    …ttl-override equal to check-period.
    
    Now works when ARTEMIS is deployed in an application server as well as 
standalone.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ryanemerson/activemq-artemis 
ARTEMIS-147-UPDATED

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/110.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #110
    
----
commit 60485c4bbdc86768bd4d81520e133f2138cb4a01
Author: Ryan Emerson <[email protected]>
Date:   2015-08-04T15:09:08Z

    [ARTEMIS-147] Add WARN log when setting connection-ttl OR 
connection-ttl-override equal to check-period.
    
    Now works when ARTEMIS is deployed in an application server as well as 
standalone.

----


> Add WARN log when setting connection-ttl OR connection-ttl-override equal to 
> check-period
> -----------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-147
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-147
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Ryan Emerson
>
> If connection ttl is equal to the check-period there is only 1 opportunity to 
> validate the live / backup connection, cluster connection or replication 
> connection.  If a system is under high load or there is a minor network delay 
> there is a high probability of a cluster split / failure due to connection 
> timeout. 
> Add WARN log when setting connection-ttl OR connection-ttl-override equal to 
> check-period.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to