You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/06/20 07:05:00 UTC

[jira] [Commented] (ARTEMIS-1944) Typo mistake in broker.xml at journal-buffer-timeout explanation

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

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

GitHub user vkamble60 opened a pull request:

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

    [ARTEMIS-1944] Typo mistake in broker.xml at journal-buffer-timeout explanation

    jira :- https://issues.apache.org/jira/browse/ARTEMIS-1944

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

    $ git pull https://github.com/vkamble60/activemq-artemis ARTEMIS-1944

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

    https://github.com/apache/activemq-artemis/pull/2150.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 #2150
    
----
commit f4097fb01a489d56dde1678ab59115ce06260c51
Author: vkamble60 <vk...@...>
Date:   2018-06-20T07:02:12Z

    [ARTEMIS-1944] Typo mistake in broker.xml at journal-buffer-timeout explanation

----


> Typo mistake in broker.xml at journal-buffer-timeout explanation
> ----------------------------------------------------------------
>
>                 Key: ARTEMIS-1944
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1944
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.6.2
>            Reporter: Varsha Kamble
>            Priority: Trivial
>
>  J is missing @ journal-datasync in broker.xml
>  
> {code:java}
> <!--
>  This value was determined through a calculation.
>  Your system could perform 125 writes per millisecond
>  on the current journal configuration.
>  That translates as a sync write every 8000 nanoseconds.
> Note: If you specify 0 the system will perform writes directly to the disk.
>  We recommend this to be 0 if you are using journalType=MAPPED and ournal-datasync=false.
>  -->
>  <journal-buffer-timeout>8000</journal-buffer-timeout>
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)