Summary: | SocketAppender ignores ReconnectionDelay of 0 (with fix) | ||
---|---|---|---|
Product: | Log4j - Now in Jira | Reporter: | Scott Schram <scott> |
Component: | Appender | Assignee: | log4j-dev <log4j-dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 1.2 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Attachments: | Proposed fix. Lemme know if I did this patch right. |
Description
Scott Schram
2002-12-21 22:49:17 UTC
Created attachment 4250 [details]
Proposed fix. Lemme know if I did this patch right.
I see we could move fireConnector(); into the first if(reconnectionDelay > 0) right after LogLog.error(msg, e); and eliminate the second test. I'll take a look at applying this change. Thanks for reporting this bug. I applied your patch, except that the stack trace is still reported. Altough you might not be interesed in the stack trace other users might be. It is hard to tell. I thus prefer to err on the safe side. |