You should be aware that AsyncAppender is backed by a bounded fifo. When
this fifo gets full, all requests to that instance of the async appender
will block, until such time that fifo is no longer full. A 'background'
thread is used to consume the entries in the fifo.
So, if the subordinate append
On Feb 10, 2006, at 6:38 AM, Bitzer Stefan wrote:
hello,
on the site http://logging.apache.org/log4j/docs/download.html the
link
to log4jME is down. How can I get the log4jME ?
tanks for help.
kind regards
Stefan Bitzer
The link for Log4jME was stale in a lot of ways, I'll update the
When the buffer in AsyncAppender fills up, it will cause the current
thread to hand until it can remove something from the buffer. If that
is what is happening and that isn't acceptable then AsyncAppender
isn't going to work for your product.
Besides that I have seen emails on this list related t
Log4j experts,
We're using Log4j (version 1.2.9) extensibly in a high-performancy telephony
server, and in our latest release we have seen quite a few "frozen server"
incidents, i.e. extensive deadlocks significantly deteriorating service.
I've now managed to isolate the deadlocks (using Jconsole)
hello,
on the site http://logging.apache.org/log4j/docs/download.html the link
to log4jME is down. How can I get the log4jME ?
tanks for help.
kind regards
Stefan Bitzer
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additiona
