I believe I have determined the cause of the behavior I was experiencing with the AsyncAppender. It was a combination of things:
1. I was "re-using" an instance-level object I was trying to log. It appears I was overwriting the properties of the object before the AsyncAppender had a chance to pass the log onto the attached appender. This was resolved by making sure I was sending a new local-level object reference in each log method call. 2. My application was stopping before the AsyncAppender had a chance to log the last logs. I now close the AsyncAppender before the application closes, which forces the last logs to complete before the application completely closes. Thanks. -----Original Message----- From: Curt Arnold [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 10, 2007 3:58 PM To: Log4J Users List Subject: Re: AsyncAppender Issue > > Has anyone else experienced this type of behavior with the > AsyncAppender? > > Thanks. > > Nope. You should pack up your test case and file a bug report to see if we can figure out what is going on. If you can identify the problem and propose a patch even better. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
