I attempted to make use of the Asynchronous LogTarget for Cocoon, however
the LogKit implementation could not do it. I kept getting a "could not
write to closed file" message written to the Tomcat log for each log
message.
Obviously that is not acceptable--and asynchronous logging is key to
Cocoon's performance. Those who are familiar with the AsyncLogTarget,
could you please give me some hints as to what may have gone wrong?
The AsyncLogTarget is crucial for server side logging approaches.
Errors should be logged immediately, and therefore should block, but
all other log messages shouldn't block.
That will help speed Cocoon's performance alot--even when logging
at the DEBUG level!
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
