Hi Thiharie, thanks for the reply.

> There is no such thing as overkill. It is merely an
> architectural decision.

Good point.


> You need to determine whether the overhead of "writing to
> a log file each time" is within acceptable performance
> parameters defined for the application you are building.

I hadn't thought about that. Luckily messages appear on the order of Hz, about one per second.



> Possible work around
> You can create a Value Object and fill it with 20, 50 or
> 100 timestamps and then write out to persistent storage
> or whatever medium you are logging to.

Thanks for bringing this to my attention.

I created a test program with log4j and was instantly enamored. The learning curve was not steep.

The one thing that I did not want to do was use a sledgehammer when a hammer would do, but I quickly realized that the asynchronous nature of JMS made file writing non-trivial.

log4j was the perfect solution.

MPC

===========================================================================
To unsubscribe: mailto listserv@(protected)".
For digest: mailto listserv@(protected)".

Some relevant archives, FAQs and Forums on JSPs can be found at:

http://java.sun.com/products/jsp
http://archives.java.sun.com/jsp-interest.html
http://forums.java.sun.com
http://www.jspinsider.com