Event SubSystem database connection vs. log4j

I'm setting up the event subsystem to log events. One of the guys here seems to think I'm just making unnecessary work by connecting to a database.
What are the pros and cons of connecting to a SQL200 database versus writing to the log4j file?

Find more posts tagged with

Comments

Slabrador

Search the forums - the main con of using the log4j file is that you will run out of disk space in very short order (there's apparently a bug in openjms).

- Dan Smith
- University of Southampton, UK

Johnny

A bug which IWOV are distancing themselves from.

A rdbms is one more link in the chain.

I personally do not think it's right for IWOV to say they won't fix it because it is not their code.

1. as far as a customer is concerned, all the software is supplied and hence should be supported by IWOV

2. considering the amount of open source software that is in use in IWOV products - it would be a great contribution to make a fix rather than saying it's not their problem.

The event subsystem has been a trying experience for us - we've turned it off.

John Cuiuli

Slabrador

It was a bit hairy for us for a while too, but all seems to be well since we moved to a DB.

I am inclined to agree with you Johnny, IMHO the whole point of OSS is that if you're selling on some OSS as part of your offering (and therefore making a profit from it, you would hope) and you encounter a bug, you fix the bug and give the fix back to the community. Or am I missing something (dollars, maybe?)

- Dan Smith
- University of Southampton, UK

cgoodall

We're still using the default event logging in TS 6.7 on Win2003. I'm in the process of converting to RDBMS logging.

The Admin Manual indicates that I should edit log4j.xml. Is this step necessary when logging to a database?

Thanks,
~Chris