Michael Erskine schrieb:
The JDBCAppender is shoddy anyhow - write yourself a replacement. It's a
great way to learn about what makes a good Appender.
To follow up: what I tend to do is have a custom JDBC Appender that adds a small custom
log entry object (with all interesting info from
Thorbjørn Ravn Andersen schrieb:
Johannes Hoechstaedter skrev den 15-07-2008 16:20:
Hi everybody,
I am up to build a coocon webapplication, and I am using the
JDBCAppender for logging. It works quite well. My only problem is,
that when I switch on the loggin in debug mode, my application is
Hi everybody,
I am up to build a coocon webapplication, and I am using the
JDBCAppender for logging. It works quite well. My only problem is, that
when I switch on the loggin in debug mode, my application is as fast as
a snail because of the heavy database traffic. How can I solve that? I
Johannes Hoechstaedter [mailto:[EMAIL PROTECTED] wrote
I am up to build a coocon webapplication, and I am using the
JDBCAppender for logging. It works quite well. My only problem is, that
when I switch on the loggin in debug mode, my application is as fast as
a snail because of the heavy
The JDBCAppender is shoddy anyhow - write yourself a replacement. It's a
great way to learn about what makes a good Appender.
To follow up: what I tend to do is have a custom JDBC Appender that adds a
small custom log entry object (with all interesting info from the LoggingEvent)
to a
Johannes Hoechstaedter skrev den 15-07-2008 16:20:
Hi everybody,
I am up to build a coocon webapplication, and I am using the
JDBCAppender for logging. It works quite well. My only problem is,
that when I switch on the loggin in debug mode, my application is as
fast as a snail because of
