Well you typically get faster log performance to a file. And there's much more flexibility using regular expressions than select statements. I write all kinds of short Perl scripts to do common log file parsing tasks.
Donnie >>> [EMAIL PROTECTED] 02/08/02 03:48AM >>> There is a benifit, when you need to do a lot log analyzation or have a lot very different logging going on, you want to lok at in a convinient way without looking at 100 log files. You can just put it in a Table and do analyzes and or use a small (web-based) log-viewer program and have all choices that you can think a "select" statment for. Simon > -----Ursprungliche Nachricht----- > Von: Eric L. Ma [mailto:[EMAIL PROTECTED]] > Gesendet: Freitag, 8. Februar 2002 02:39 > An: [EMAIL PROTECTED] > Betreff: Re: Best practice for using Log4j, EJB, Struts, and WebLogic > 6.1 together > > > What is the benefit of using JDBCAppenders over RFAppenders for EJB > related logging? To me log files are so much easier to read, and I > prefer it over any database, unless there is a fundamental reason > against it, such as problems related to multiple threads trying to write > to the same file simultaneously when the app server is under load. > > > > Donnie: can you provide some details how to set up log4j > programmatically so that I can use configAndWatch? I would think a > stateless session bean loaded into the free pool at server startup can > be used. Any other suggestions? > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
