activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] [Commented] (AMQ-5709) Logging of "Database ... is locked" should be done on level DEBUG
Date Tue, 07 Apr 2015 11:55:12 GMT


Gary Tully commented on AMQ-5709:

maybe we reduce the frequency - there was a fix a few years back for producers blocked on
flow control to log a warn or info level message every 30 seconds[1].
Or log once at INFO and subsequent (the lock retry period) at debug level. That may be simpler.


> Logging of "Database ... is locked" should be done on level DEBUG
> -----------------------------------------------------------------
>                 Key: AMQ-5709
>                 URL:
>             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: File '.../activemq/data/lock'
could not be locked. | | main

This message was sent by Atlassian JIRA

View raw message