Re: Concurrent, persistent background process for a J2EE container
- From: Mark Space <markspace@xxxxxxxxxxxxx>
- Date: Fri, 29 Aug 2008 10:29:27 -0700
Donkey Hottie wrote:
My boss seem to think that he wants to keep things as simple as possible, and maybe the log manager should so all this in the context and thread of the logging application. That might be well possible, because out app run on intranets, and there will not be much traffic.
I think your boss is correct. The Java LogManager is pretty robust. I'd definitely try that first, and only abandon it when it was proven it couldn't work. The LogManager is pretty sophisticated, it'll even rotate your logs for you.
Writing logs to a database... why? The logs should be simple, so that they are present even when things don't work. How are you going to debug database problems when the logs didn't get written because the database was supposed to be hold the logs in the first place? This seems circular, and unnecessarily complex. Even baroque.
If I got an app that wrote logs to a database, I think I'd curse your name. Just saying....
.
- Follow-Ups:
- Re: Concurrent, persistent background process for a J2EE container
- From: Donkey Hottie
- Re: Concurrent, persistent background process for a J2EE container
- From: Donkey Hottie
- Re: Concurrent, persistent background process for a J2EE container
- From: Donkey Hottie
- Re: Concurrent, persistent background process for a J2EE container
- Prev by Date: Re: regex problem
- Next by Date: Re: Concurrent, persistent background process for a J2EE container
- Previous by thread: Core Java Interview Questions And Real Time Discussions
- Next by thread: Re: Concurrent, persistent background process for a J2EE container
- Index(es):
Relevant Pages
|