activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (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 12:00:14 GMT

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

Christian Schneider commented on AMQ-5709:
------------------------------------------

+1 to log the first try at higher level. I think the log message could also state that the
instance is going into slave mode.


> 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
>             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