Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CF43F17596 for ; Wed, 22 Apr 2015 20:19:07 +0000 (UTC) Received: (qmail 43268 invoked by uid 500); 22 Apr 2015 20:19:01 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 43213 invoked by uid 500); 22 Apr 2015 20:19:01 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 43199 invoked by uid 99); 22 Apr 2015 20:19:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Apr 2015 20:19:01 +0000 Date: Wed, 22 Apr 2015 20:19:01 +0000 (UTC) From: "Gary Tully (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMQ-5709) Logging of "Database ... is locked" should be done on level DEBUG MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14507811#comment-14507811 ] Gary Tully commented on AMQ-5709: --------------------------------- logging once as warn and every time as debug works fine. This won't fill a production log but dev folks can see some action in debug mode. The frequency is managed by the lock acquire interval. > 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)