Chainsaw can easily load 20K events. Are you seeing an outofmemoryerror in the WebStart console?
It sounds like the ability to specify the where clause in the query would alleviate much of your concerns - something we should probably support in dbreceiver. Scott -----Original Message----- From: Ricardo Trindade [mailto:[EMAIL PROTECTED] Sent: Mon 9/20/2004 9:40 AM To: Log4J Users List Cc: Subject: RE: configuring DBAppender / JMSAppender Also, in our usage, we remotely consult logs over slow links. If the DBReceiver only gets a few hundred lines (ideally configurable) and then gets more as the user scrolls, there won't be a problem, but if it attempts to get all of them... I don't think it's a good idea to retrieve results a user is not looking at. I did some simple tests with a DB with 20.000 log events, and even on a lan I gave up before chainsaw ended displaying them (several minutes) thanks Ricardo Trindade -----Mensagem original----- De: Scott Deboy [mailto:[EMAIL PROTECTED] Enviada: segunda-feira, 20 de Setembro de 2004 16:46 Para: Log4J Users List Assunto: RE: configuring DBAppender / JMSAppender There is one case where something like this is important: receiving too many events too quickly can cause an out of memory error in Chainsaw. JDBCReceiver had a similar problem (JDBCReceiver is a receiver in the sandbox module that relies on the user to provide sql describing event fields). To address this problem, jdbcreceiver waits 300 ms every 1000 events processed, giving Chainsaw a chance to process events - avoiding the out of memory error. Maybe we need to add a similar mechanism to dbreceiver. -----Original Message----- From: Ricardo Trindade [mailto:[EMAIL PROTECTED] Sent: Mon 9/20/2004 3:53 AM To: Log4J Users List Cc: Subject: RE: configuring DBAppender / JMSAppender Hi, I've got DBAppender logging to mysql and chainsaw displaying events with DBReceiver. I noticed that DBReceiver / chainsaw gets all of the logging events from the DB, when it initializes the receiver. Wouldn't it be preferable to get data in chunks, when needed ? thanks Ricardo -----Mensagem original----- De: Ceki Gülcü [mailto:[EMAIL PROTECTED] Enviada: quinta-feira, 16 de Setembro de 2004 19:50 Para: Log4J Users List Assunto: Re: configuring DBAppender / JMSAppender At 08:37 PM 9/16/2004, you wrote: >Hi, > > I have some questions configuring DBAppender and JMSAppender. > > I read that to configure them, and some of the new appenders, I > either have >to do it programatically or use Joran. I don't want to code it, so Joran it >is. > > My question is what is the status of the Joran configurator, and > where can >I get docs and examples for it. I found some in the wiki, but not quite what >I wanted. JoranConfigurator is fairly mature. It is used nearly in the same way as DOMConfigurator. See examples in tests/src/java/org/apache/log4j/db/ For sample configuration files see tests/input/db/ > Also, is the .properties configuration format deprecated ? Should > I avoid >it ? JoranConfigurator is much more powerful but for the simple cases PropertyConfigurator does just fine. >thanks >Ricardo Trindade -- Ceki Gülcü For log4j documentation consider "The complete log4j manual" ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
