Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <11884203.1193248704620.JavaMail.jira@brutus>
Date: Wed, 24 Oct 2007 10:58:24 -0700 (PDT)
From: "Mario Siegenthaler (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-1476) DefaultDatabaseLocker flooding the
 logs while the database is brought down
In-Reply-To: <26348150.1193235144332.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQ-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40503 ] 

Mario Siegenthaler commented on AMQ-1476:
-----------------------------------------

Why don't you reconfigure the logging, so that only errors from the org.apache.activemq.store.jdbc.DefaultDatabaseLocker category are logged? I think that's the fastest way to get rid of the problem, it doesn't even require a recompilation.

The addition of the line
log4.logger.org.apache.activemq.store.jdbc.DefaultDatabaseLocker=WARN
to the log4j.properties in the conf folder of ActiveMQ  should do the job (I didn't test this).

> DefaultDatabaseLocker flooding the logs while the database is brought down
> --------------------------------------------------------------------------
>
>                 Key: AMQ-1476
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1476
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 4.1.1
>         Environment: Jdbc Master/Slave setup deployed in Weblogic with connectivity to oracle database.
>            Reporter: Manish Bellani
>
> Hello
> We are using Jdbc Master/Slave setup for our application, when the database is brought down when the application is still running the DefaultDatabaseLocker for the slave is flooding the logs complaining about it being unable to acquire the lock as the database is down, i think it would be nice to reduce the number of times it logs it e.g. once every nth (100th or so) time.  this might as well result in running out of disc space very quickly if the database remains down for the long time.
> Thanks
> Manish.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.