activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5709) Logging of "Database ... is locked" should be done on level DEBUG
Date Tue, 07 Apr 2015 21:29:13 GMT

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

ASF GitHub Bot commented on AMQ-5709:
-------------------------------------

GitHub user clebertsuconic opened a pull request:

    https://github.com/apache/activemq/pull/82

    AMQ-5709 Reworking Logging on Locker

    https://issues.apache.org/jira/browse/AMQ-5709
    
    This is about changing how the Log is done in case of not being able to lock (log only
once)

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

    $ git pull https://github.com/clebertsuconic/activemq master-log

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

    https://github.com/apache/activemq/pull/82.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 #82
    
----
commit 89c75ca28aae1e6a5b62f159350d29a5f7782e71
Author: Clebert Suconic <clebertsuconic@apache.org>
Date:   2015-04-07T19:48:42Z

    AMQ-5709 Reworking Logging on Locker
    
    https://issues.apache.org/jira/browse/AMQ-5709
    
    This is about changing how the Log is done in case of not being able to lock (log only
once)

----


> Logging of "Database ... is locked" should be done on level DEBUG
> -----------------------------------------------------------------
>
>                 Key: AMQ-5709
>                 URL: https://issues.apache.org/jira/browse/AMQ-5709
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.11.1
>            Reporter: Christian Schneider
>            Assignee: clebert suconic
>             Fix For: 5.x, 6.0.0
>
>
> The SharedFileLocker tries to acquire a lock on the activemq lock file.  Everytime it
can not lock it outputs the logging message below at INFO level.  On the slave it will try
this forever till the master is down.
> So I propose we only log on DEBUG level so the messages do not fill up a log with a global
default info log level.
> 2015-04-07 12:35:36,522 | INFO  | Database .../activemq/data/lock is locked... waiting
10 seconds for the database to be unlocked. Reason: java.io.IOException: File '.../activemq/data/lock'
could not be locked. | org.apache.activemq.store.SharedFileLocker | main



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

Mime
View raw message