You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Manish Bellani (JIRA)" <ji...@apache.org> on 2007/10/24 16:12:24 UTC
[jira] Created: (AMQ-1476) DefaultDatabaseLocker flooding the logs
while the database is brought down
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.
[jira] Issue Comment Edited: (AMQ-1476) DefaultDatabaseLocker
flooding the logs while the database is brought down
Posted by "Manish Bellani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40501 ]
manishbel edited comment on AMQ-1476 at 10/24/07 7:17 AM:
---------------------------------------------------------------
Right now our customer is testing the application and they bring the database down frequently which causes the log files to grow very quickly, is it possible to provide a quick patch for it so that we can apply and deliver it to customer?
Thanks
Manish
was (Author: manishbel):
Right now our customer is testing the application and they are seeing this issue very frequently, is it possible to provide a quick patch for it so that we can apply and deliver it to customer?
Thanks
Manish
> 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.
[jira] Commented: (AMQ-1476) DefaultDatabaseLocker flooding the
logs while the database is brought down
Posted by "Mario Siegenthaler (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (AMQ-1476) DefaultDatabaseLocker flooding the
logs while the database is brought down
Posted by "Manish Bellani (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40501 ]
Manish Bellani commented on AMQ-1476:
-------------------------------------
Right now our customer is testing the application and they are seeing this issue very frequently, is it possible to provide a quick patch for it so that we can apply and deliver it to customer?
Thanks
Manish
> 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.