DO NOT REPLY [Bug 13063] New: - I cant control the Additivity of logger from Properites file.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13063] - I cant control the Additivity of logger from Properites file.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13063] - I cant control the Additivity of logger from Properites file.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

BufferAppender and CyclicBuffer

Hi, I have downloaded Log4J 1.2.6 yesterday and have made a simple BufferAppender. This is storing log events in a cyclic buffer and overwrites the oldest log event when a new one is appended. The whole buffer and the new message are forwarded to a subappender if the new log event has got a prior

DO NOT REPLY [Bug 13063] - I cant control the Additivity of logger from Properites file.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13063] - I cant control the Additivity of logger from Properites file.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

DO NOT REPLY [Bug 13063] - I cant control the Additivity of logger from Properites file.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b

RE: Daemon Thread for AsyncAppender

Ceki, Sorry, I should have looked at #9750 closer and realized that it was marked as fixed. We can review Nick's submission for inclusion anyways. One is not required to call close() to allow the jvm to exit, as the last comment in the bug suggests? Since the thread is daemon, it should just e

RE: log4j with xerces 2.1.0

I did not get a chance to work on this as planned, but I did review the change and download the versions of Xerces to work with. Tomrrow I will work to reproduce it, test the change, and pending the result, merge it. thanks, -Mark > -Original Message- > From: Mark Womack [mailto:[EMAIL

RE: BufferAppender and CyclicBuffer

Ole, I did a quick search, and the only class in the log4j library that appears to be using CyclicBuffer is o.a.l.net.SMTPAppender. Just so we understand what you are proposing: 1) A patch to CyclicBuffer that when resized to a smaller buffer size, keeps the newest messages instead of the old

JMS Appender

Would it be possible with the JMS Appender to provide a non JNDI way of obtaining JMSConnections? I'm using File JNDI at present for JMSAppender (and IPlanet LDAP eventually). The original custom logger that I am currently replacing with Log4J uses parameters - Broker, Host and Topic to point t

AW: BufferAppender and CyclicBuffer

Hi Mark, > Just so we understand what you are proposing: > > 1) A patch to CyclicBuffer that when resized to a smaller > buffer size, keeps the newest messages instead of the oldest. > 2) A new BufferAppender. > > Have I got that right? Yep. > So, please post your code. Here it is. I wasn't

RE: Daemon Thread for AsyncAppender

Bug #9750 is fixed only if you consider the behavior of having an dying app reap the AsynchAppender's Dispacher thread before all events are logged. I think it would be good to make this behavior instrumented instead of "always use daemon threads" approach. There is a 3rd party commercial produc

RE:log4j.ignoreTCL

I am using IntelliJ as my IDE and I run my junit tests from it. It automatically invoke the junit runner to run my tests. I assume the tool reference the junit.jar I set in the classpath and it is version 3.8.1. The unit test I had problem contained just one line to test the initialization of

RE: Daemon Thread for AsyncAppender

Hi Nick, Thanks for the code. I understand your point. One would prefer to ensure that all reported log messages actually get reported. Your change is compatible with the current behavior, it just allows more options. I wonder if another way to do this would be to register a shutdown callbac

DO NOT REPLY [Bug 13099] New: - DOMConfigurator ignores category factory setting

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_b