activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2404) Frequent kahadb messages: "KahaDB long enqueue time: Journal Add Took: 0 ms, Index Update took 125 ms"
Date Wed, 23 Sep 2009 19:43:52 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54470#action_54470
] 

Hiram Chirino commented on AMQ-2404:
------------------------------------

You will now be able to use a system property to set what is considered a slow access time.
 For example you could pass this JVM option to the broker:
{code}
-Dorg.apache.activemq.store.kahadb.LOG_SLOW_ACCESS_TIME=300
{code}

Then if a kahadb operation is takes longer than 300 ms to complete, a log message will be
produced.
Default is set to 500 now.  If you set it to 0, then no log messages are ever produced.


> Frequent kahadb messages: "KahaDB long enqueue time: Journal Add Took: 0 ms, Index Update
took  125 ms"
> -------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2404
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2404
>             Project: ActiveMQ
>          Issue Type: Bug
>         Environment: Windows (at least)
>            Reporter: Colin MacNaughton
>            Priority: Minor
>             Fix For: 5.3.0
>
>
> Perhaps the log level of these should be changed to warn?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message