On Feb 20, 2008, at 10:18 AM, James A. N. Stauffer wrote:
I don't know if the AyscAppender has been fixed in that version. Can you show how you are configuring the AyscAppender and DBAppender?
I think the AsyncAppender fixes came after 1.3-alpha 8. log4j 1.3 development has been abandoned and log4j 1.3 features have been back- ported as companions to log4j. The DBAppender is part of the "receivers" companion which has not yet been released. The migration path for users of the log4j 1.3 alphas is to 1.2.15 + companions.
I don't think that the AsyncAppender issues however would result in a SQLException. However, it may be that the SQL connection is thread specific and the current implementation of DBAppender doesn't account for that. If your calling app is single threaded, direct use of DBAppender would have all your DB calls coming from the same thread. Wrapping the DBAppender in an AsyncAppender would have the call to activateOptions occurring on the main thread while doAppend would occur on a different thread. If you database connections are thread- specific, then that would result in an exception during doAppend. You have not provided the details (message, stack trace, etc) from the SQLException which would greatly help in troubleshooting.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
