Re: Concurrent, persistent background process for a J2EE container

Mark Space <markspace@xxxxxxxxxxxxx> wrote in
news:g99bm8$ng5$1@xxxxxxxxxxxxxxxxxxxxxxxxx:

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....


We can't use java.util.logging for this. Boss wants "structured" data, not
flat text files.

Actually our logging needs are 3 fold.

We have a web type server managing identities and access, kind of an
Identity and Access management solution. It's requests and actions must be
logged, and plain text web server type log file is not enough.

Then we have and Administration GUI Web Service for it, and every action
there must be logged, identifying actions, entity and it's attributes, when
updates, old and new values logged. Very "structural" data.

Finally we have "normal" debug log, which can be handled with
java.util.logging (currently we use Log4j, but boss wants to get rid of
open source).

Our admin/access audit logs will be written to (implementation may vary) to
a database or disk file in some structured format, and those logs will be
available in the Management Console GUI. Debug logs must not be visible in
the GUI, but they must be turned on and off from said GUI. I'm prepared to
let log4j go and use java.util.logging for that, it works ok.

.

Relevant Pages

  • Re: Dynamic Firewall/IDS System
    ... some thoughts about event handling software. ... > is almost impossible to handle manually just reading logs. ... > This is how we fill our database. ... this is logging, way like acid does with snort logs. ...
    (FreeBSD-Security)
  • Re: Exchange - Huge (x10) mismatch between size of priv1.edb and actual size of mailboxes in mai
    ... about 40 transaction logs. ... I think client actions that read from the database are ... mailboxes and the system is not that old. ...
    (microsoft.public.windows.server.sbs)
  • Re: Error in Exchange
    ... Will you provide me some linkes to get more info about the role these logs ... play in .edb file or with database and how information is saved into .edb ... > backup on Sept 8. ... > transaction logs are saved in that backup. ...
    (microsoft.public.exchange.admin)
  • Re: Exchange - Huge (x10) mismatch between size of priv1.edb and actual size of mailboxes in mai
    ... no new logs for the last 5 hours. ... about 40 transaction logs. ... I think client actions that read from the database ... mailboxes and the system is not that old. ...
    (microsoft.public.windows.server.sbs)
  • Re: Minimizing backup induced downtime
    ... With that magical RMAN thing, how will you be able to recover ... take a backup of an Oracle database without the need for having ... I am running the databases in archive log mode and I know what it is. ... that the logs aren't backed up. ...
    (comp.databases.oracle.server)