[JIRA] Created: (LBCLASSIC-193) SyslogAppender quits after a while
SyslogAppender quits after a while ---------------------------------- Key: LBCLASSIC-193 URL: http://jira.qos.ch/browse/LBCLASSIC-193 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19 Environment: At least Debian Etch with JDK5 Reporter: Ingo Siebert Assignee: Logback dev list Priority: Critical I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine. But after several days and weeks, more and more servers doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs. I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57. In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies. If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. The SysLog-Appender is useless for me until this bug is fixed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-193?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-193: -------------------------------------- Can you create the problem? What error(s) are you observing?
SyslogAppender quits after a while ----------------------------------
Key: LBCLASSIC-193 URL: http://jira.qos.ch/browse/LBCLASSIC-193 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19 Environment: At least Debian Etch with JDK5 Reporter: Ingo Siebert Assignee: Logback dev list Priority: Critical
I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine. But after several days and weeks, more and more servers doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs. I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57. In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies. If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. The SysLog-Appender is useless for me until this bug is fixed.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-193?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu edited comment on LBCLASSIC-193 at 3/8/10 1:23 PM: -------------------------------------------------------------- Can you reproduce the problem? What error(s) are you observing? was (Author: noreply.ceki@qos.ch): Can you create the problem? What error(s) are you observing?
SyslogAppender quits after a while ----------------------------------
Key: LBCLASSIC-193 URL: http://jira.qos.ch/browse/LBCLASSIC-193 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19 Environment: At least Debian Etch with JDK5 Reporter: Ingo Siebert Assignee: Logback dev list Priority: Critical
I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine. But after several days and weeks, more and more servers doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs. I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57. In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies. If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. The SysLog-Appender is useless for me until this bug is fixed.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-193?page=com.atlassian.jira.plugin.syste... ] Ingo Siebert commented on LBCLASSIC-193: ---------------------------------------- I have very many log messages and I haven't found a special logback exception, that's why I can't say which log message is the problem. But my problem occurs everytime after some days. The result of the error is that nothing is logged anymore. It may be possible that we sometimes log big messages.
SyslogAppender quits after a while ----------------------------------
Key: LBCLASSIC-193 URL: http://jira.qos.ch/browse/LBCLASSIC-193 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19 Environment: At least Debian Etch with JDK5 Reporter: Ingo Siebert Assignee: Logback dev list Priority: Critical
I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine. But after several days and weeks, more and more servers doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs. I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57. In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies. If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. The SysLog-Appender is useless for me until this bug is fixed.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-193?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-193: -------------------------------------- Have you looked at logback status messages *after* configuration, either by registering a status listener or dumping the contents of status messages?
SyslogAppender quits after a while ----------------------------------
Key: LBCLASSIC-193 URL: http://jira.qos.ch/browse/LBCLASSIC-193 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19 Environment: At least Debian Etch with JDK5 Reporter: Ingo Siebert Assignee: Logback dev list Priority: Critical
I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine. But after several days and weeks, more and more servers doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs. I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57. In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies. If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. The SysLog-Appender is useless for me until this bug is fixed.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-193?page=com.atlassian.jira.plugin.syste... ] Ingo Siebert commented on LBCLASSIC-193: ---------------------------------------- I've set <configuration debug="true"> in my configuration files. The logback status messages are written to catalina.log in my case. Does it also write status messages after configuration? It's all looking fine and after a server restart all seems to work well.
SyslogAppender quits after a while ----------------------------------
Key: LBCLASSIC-193 URL: http://jira.qos.ch/browse/LBCLASSIC-193 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19 Environment: At least Debian Etch with JDK5 Reporter: Ingo Siebert Assignee: Logback dev list Priority: Critical
I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine. But after several days and weeks, more and more servers doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs. I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57. In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies. If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. The SysLog-Appender is useless for me until this bug is fixed.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-193?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-193: -------------------------------------- <configuration debug="true"> prints messages during configuration. You should install a status listener with <configuration> <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener" /> ..... the rest of the configuration file </configuration> as explained in http://logback.qos.ch/manual/configuration.html#statusListener
SyslogAppender quits after a while ----------------------------------
Key: LBCLASSIC-193 URL: http://jira.qos.ch/browse/LBCLASSIC-193 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19 Environment: At least Debian Etch with JDK5 Reporter: Ingo Siebert Assignee: Logback dev list Priority: Critical
I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine. But after several days and weeks, more and more servers doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs. I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57. In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies. If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. The SysLog-Appender is useless for me until this bug is fixed.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-193?page=com.atlassian.jira.plugin.syste... ] Ingo Siebert commented on LBCLASSIC-193: ---------------------------------------- If've added the StatusListener to our App-Servers. I'll monitor the log files the next days.
SyslogAppender quits after a while ----------------------------------
Key: LBCLASSIC-193 URL: http://jira.qos.ch/browse/LBCLASSIC-193 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19 Environment: At least Debian Etch with JDK5 Reporter: Ingo Siebert Assignee: Logback dev list Priority: Critical
I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine. But after several days and weeks, more and more servers doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs. I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57. In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies. If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. The SysLog-Appender is useless for me until this bug is fixed.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-193?page=com.atlassian.jira.plugin.syste... ] Ingo Siebert commented on LBCLASSIC-193: ---------------------------------------- Ok, the last message of my app-server 5 is at 9:46 am. In my catalina.log is the following message: 09:47:04,471 |-ERROR in ch.qos.logback.classic.net.SyslogAppender[SysLogAppender] - Failed to send diagram to 192.168.37.30 java.io.IOException: Message too long at java.io.IOException: Message too long at at java.net.PlainDatagramSocketImpl.send(Native Method) at at java.net.DatagramSocket.send(DatagramSocket.java:612) at at ch.qos.logback.core.net.SyslogWriter.flush(SyslogWriter.java:50) at at ch.qos.logback.core.net.SyslogAppenderBase.append(SyslogAppenderBase.java:84) at at ch.qos.logback.core.AppenderBase.doAppend(AppenderBase.java:87) at at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:60) at at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:271) at at ch.qos.logback.classic.Logger.callAppenders(Logger.java:258) at at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:440) at at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:394) at at ch.qos.logback.classic.Logger.error(Logger.java:541) at at de.cas.open.rapclient.base.core.internal.logging.Slf4jLogger.error(Slf4jLogger.java:61) at at de.cas.open.rapclient.base.core.rap.servicehandler.ScriptErrorHandler.handleRequest(ScriptErrorHandler.java:47) at at de.cas.open.rapclient.base.core.rap.servicehandler.AbstractServiceHandler.service(AbstractServiceHandler.java:66) at at org.eclipse.rwt.internal.service.ServiceManager$HandlerDispatcher.service(ServiceManager.java:98) at at org.eclipse.rwt.internal.engine.RWTDelegate.doPost(RWTDelegate.java:64) at at org.eclipse.ui.internal.servlet.RequestHandler.service(RequestHandler.java:51) at at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) at at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) at at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59) at at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:115) at at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:880) at at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:719) at at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2081) at at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at at java.lang.Thread.run(Thread.java:595) 09:48:28,547 |-WARN in ch.qos.logback.classic.net.SyslogAppender[SysLogAppender] - Attempted to append to non started appender [SysLogAppender]. 09:48:28,547 |-WARN in ch.qos.logback.classic.net.SyslogAppender[SysLogAppender] - Attempted to append to non started appender [SysLogAppender]. 09:48:28,547 |-WARN in ch.qos.logback.classic.net.SyslogAppender[SysLogAppender] - Attempted to append to non started appender [SysLogAppender]. 09:48:28,578 |-WARN in ch.qos.logback.classic.net.SyslogAppender[SysLogAppender] - Attempted to append to non started appender [SysLogAppender]. 09:48:28,578 |-WARN in ch.qos.logback.classic.net.SyslogAppender[SysLogAppender] - Attempted to append to non started appender [SysLogAppender].
SyslogAppender quits after a while ----------------------------------
Key: LBCLASSIC-193 URL: http://jira.qos.ch/browse/LBCLASSIC-193 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19 Environment: At least Debian Etch with JDK5 Reporter: Ingo Siebert Assignee: Logback dev list Priority: Critical
I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine. But after several days and weeks, more and more servers doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs. I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57. In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies. If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. The SysLog-Appender is useless for me until this bug is fixed.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-193?page=com.atlassian.jira.plugin.syste... ] Ralph Goers commented on LBCLASSIC-193: --------------------------------------- Google tells me that a system setting is causing the Message too long exception. Unfortunately, when SyslogAppenderBase encounters an IOException it calls stop(), which disables the Appender. Unfortunately, SyslogAppenderBase doesn't provide any way to change this behavior.
SyslogAppender quits after a while ----------------------------------
Key: LBCLASSIC-193 URL: http://jira.qos.ch/browse/LBCLASSIC-193 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19 Environment: At least Debian Etch with JDK5 Reporter: Ingo Siebert Assignee: Logback dev list Priority: Critical
I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine. But after several days and weeks, more and more servers doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs. I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57. In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies. If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. The SysLog-Appender is useless for me until this bug is fixed.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-193?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu resolved LBCLASSIC-193. ---------------------------------- Fix Version/s: 0.9.19 Resolution: Fixed
SyslogAppender quits after a while ----------------------------------
Key: LBCLASSIC-193 URL: http://jira.qos.ch/browse/LBCLASSIC-193 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19 Environment: At least Debian Etch with JDK5 Reporter: Ingo Siebert Assignee: Logback dev list Priority: Critical Fix For: 0.9.19
I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine. But after several days and weeks, more and more servers doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs. I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57. In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies. If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. The SysLog-Appender is useless for me until this bug is fixed.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-193?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-193: -------------------------------------- Ralph, thank you for pointing out the stop() after IOException behavior in SyslogAppenderBase. The exception is thrown by the local TCP/IP stack and is independent of the remote syslog daemon. Recreating the SyslogWriter after an exception is one valid approach. This strategy was implemented and tried in c.q.lb.core.recovery.ResilientSyslogOutputStream but turns out to be a complete overkill. Realizing that the IOException is a local matter, removing the line which stops the SyslogAppender after the occurrence of an exception solves this problem. Here is the relevant commit http://github.com/ceki/logback/commit/36d3641c8af6d017
SyslogAppender quits after a while ----------------------------------
Key: LBCLASSIC-193 URL: http://jira.qos.ch/browse/LBCLASSIC-193 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19 Environment: At least Debian Etch with JDK5 Reporter: Ingo Siebert Assignee: Logback dev list Priority: Critical Fix For: 0.9.19
I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine. But after several days and weeks, more and more servers doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs. I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57. In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies. If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. The SysLog-Appender is useless for me until this bug is fixed.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-193?page=com.atlassian.jira.plugin.syste... ] Ingo Siebert commented on LBCLASSIC-193: ---------------------------------------- Thank you Ralph and Ceki! Is there a realease-date of 0.9.19 or a nightly build?
SyslogAppender quits after a while ----------------------------------
Key: LBCLASSIC-193 URL: http://jira.qos.ch/browse/LBCLASSIC-193 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 0.9.13, 0.9.14, 0.9.15, 0.9.16, 0.917, 0.9.18, 0.9.19 Environment: At least Debian Etch with JDK5 Reporter: Ingo Siebert Assignee: Logback dev list Priority: Critical Fix For: 0.9.19
I have 5 applications servers and each one logs to one separate SysLog-Server. After Server-Restart, all is working fine. But after several days and weeks, more and more servers doesn't log to he SysLog-Server anymore. But I can't see an Syslog-Error in my Logs. I think this bug is related to http://jira.qos.ch/browse/LBCLASSIC-57. In my opinion, the most important fix would be to re-creae the SysLog-Appender if an exception/error occurs or to avaid that the SysLog-Appender dies. If I miss one single entry, than that's not nice. But if I miss all entries it's very serve. The SysLog-Appender is useless for me until this bug is fixed.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
participants (3)
-
Ceki Gulcu (JIRA) -
Ingo Siebert (JIRA)
-
Ralph Goers (JIRA)