[
https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507491#comment-14507491
]
Arthur Naseef commented on AMQ-5709:
------------------------------------
If I'm reading the commits correctly, the fix was to limit the log message to
only ever be written one time. Reading the comments in the jira ticket here,
though, it seems like the plan was to limit the frequency, allowing more than
one, but just at a limited rate.
Any thoughts?
> 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.12.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)
