activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-1476) DefaultDatabaseLocker flooding the logs while the database is brought down
Date Sat, 09 Jul 2011 20:55:59 GMT

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

Timothy Bish closed AMQ-1476.
-----------------------------

    Resolution: Not A Problem

Configuration issue, log4j settings can deal with this issue.

> DefaultDatabaseLocker flooding the logs while the database is brought down
> --------------------------------------------------------------------------
>
>                 Key: AMQ-1476
>                 URL: https://issues.apache.org/jira/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
>             Fix For: AGING_TO_DIE
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message