DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42151>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42151 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2007-04-18 08:02 ------- >From the stack trace it appears that you are using >com.csfb.fao.carat.util.file.LoggingOutputStream to redirect System.err to log4j. The ArchivedDailyRollingFileAppender has an IOException while trying to write to an file output stream which results in a diagnostic message being written to System.err, which causes another IOException and that repeats until stack space is exhausted. You could likely repeat this on your dev environment if you can manufacture an IOException on your log file (plug the cable on an external drive, disconnect a network drive, etc). Don't know what the triggering IOException is, but you could break the endless recursion by having the LoggingOutputStream check if the message starts with "log4j:" and if it does, then do something else with it other than feed it back to log4j. Marking this as invalid since the problem can be fixed in LoggerOutputStream. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
