September 2007 - logback-dev

[Bug 69] New: I18N Patch
by bugzilla-daemon＠pixie.qos.ch 18 Nov '07

18 Nov '07

http://bugzilla.qos.ch/show_bug.cgi?id=69 Summary: I18N Patch Product: Console Plugin Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: interface AssignedTo: logback-dev(a)qos.ch ReportedBy: sdavids(a)gmx.de -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 6

[Bug 103] New: Two appenders to the same file
by bugzilla-daemon＠pixie.qos.ch 10 Oct '07

10 Oct '07

http://bugzilla.qos.ch/show_bug.cgi?id=103 Summary: Two appenders to the same file Product: logback-core Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: major Priority: P1 Component: Rolling AssignedTo: logback-dev(a)qos.ch ReportedBy: Andriy.Petrov(a)gmail.com There are two different loggers writing to the same file with different patterns (so there are two different file appenders). In case rolling is turned on (on both) output gets lost. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 2

Lumberjack infos - was: Re: Logback Chainsaw Bridge
by Maarten Bosteels 04 Oct '07

04 Oct '07

Hello Joern, I agree with Jozsef: a bounded blocking queue could be an interesting option. For me, it would also be acceptable that events are dropped when the queue fills up: we will always have the log-files as a backup. see http://logging.apache.org/log4j/1.2/faq.html#1.2 (I know, it's about log4j not LogBack) What I want can probably be done with the AsyncAppender http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/AsyncAppender.… Ceki, any plans on adding a AsyncAppender to LogBack ? I have also thought about gzipping the events, with MINA this would be very easy http://mina.apache.org/report/1.1/apidocs/org/apache/mina/filter/Compressio… Maarten On 9/28/07, Hontvari Jozsef <hontvari3(a)solware.com> wrote: > > > The problem with asynchronous SocketAppenders is that you have > > essentially three options: > > a) you keep events in an in memory-back-buffer. This will lead to > > out-of-memory situations if more events are produced than transfered. > > At this point your app will either explode or drop events. Both is not > > really an option. > > b) you keep the events in a disk-based buffer.This will lead to > > out-of-disk-space situations if more events are produced than > > transfered. See a) ;) > > > > So event transmission must be synchronous. > > > You can also use a bounded blocking queue. In this way the process is > usually asynchronous but falls back to (nearly) synchronous it there are > too many events and slows down the system. But I think the througput > will be higher even in the latter case. > > _______________________________________________ > logback-dev mailing list > logback-dev(a)qos.ch > http://qos.ch/mailman/listinfo/logback-dev >

3 2

Logback Chainsaw Bridge
by Maarten Bosteels 28 Sep '07

28 Sep '07

Hello, I've written a Logback Chainsaw Bridge: your programs can use logback and you can receive the events in Chainsaw using the SImpleReceiver. The idea is pretty simple: * You specify a "ch.qos.logback.classic.net.SocketAppender" in logback.xml * LogbackChainsawBridge reads incoming logback events from the wire * LogbackChainsawBridge converts the events to Log4j events * LogbackChainsawBridge sends the events to chainsaw using a SocketAppender It's certainly not a perfect solution, I hope there will be a cool LogBackViewer someday that can compete with chainsaw. (maybe when I have lots of time...) Or does it exist already ? In the meantime, some of you might find it interesting. The following attributes are sent to chainsaw: * ThreadName * Logger * Timestamp * Message * Level * MDC * CallerData (LocationInfo) * Throwable Feedback welcome. Maarten package ch.org.logback; import java.net.ServerSocket; import java.net.Socket; import java.io.ObjectInputStream; import java.io.BufferedInputStream; import java.io.IOException; import java.io.EOFException; import java.util.Map; import java.util.Hashtable; /** * This program will listen on the specified port for Logback logging events * and forward them as Log4j events to another port (to be received by Chainsaw) */ public class LogbackChainsawBridge { static int port; static boolean includeCallerData = false; public static void main(String argv[]) throws Exception { if (argv.length == 0) { init("5555", "false"); } if (argv.length == 1) { init(argv[0], "false"); } if (argv.length == 2) { init(argv[0], argv[1]); } if (argv.length > 2) { usage("too many arguments"); } runServer(); } static void runServer() { org.apache.log4j.net.SocketAppender socketAppender = new org.apache.log4j.net.SocketAppender("localhost", 4445); try { info("Listening on port " + port); ServerSocket serverSocket = new ServerSocket(port); //noinspection InfiniteLoopStatement while (true) { info("Waiting to accept a new client."); Socket socket = serverSocket.accept(); info("Connected to client at " + socket.getInetAddress()); info("Starting new socket node."); new Thread(new SocketHandler(socket, socketAppender)).start(); } } catch (Exception e) { e.printStackTrace(); } } static void usage(String msg) { System.err.println(msg); System.err.println("Usage: java " + MySimpleSocketServer.class.getName() + "[port] [includeCallerData]"); System.err.println(" port : on which port the logback events are coming on"); System.err.println(" includeCallerData : true when you want to include caller data"); System.exit(1); } private static void info(String message) { System.out.println(message); } static void init(String portStr, String includeCallerDataStr) { try { port = Integer.parseInt(portStr); } catch (NumberFormatException e) { e.printStackTrace(); usage("Could not interpret port number [" + portStr + "]."); } includeCallerData = Boolean.parseBoolean(includeCallerDataStr); } private static org.apache.log4j.spi.ThrowableInformation convertToLog4jhTrowableInformation ( ch.qos.logback.classic.spi.ThrowableInformation throwableInformation) { if (throwableInformation == null || throwableInformation.getThrowableStrRep() == null || throwableInformation.getThrowableStrRep().length == 0) { return null; } return new org.apache.log4j.spi.ThrowableInformation(throwableInformation.getThrowableStrRep()); } private static org.apache.log4j.spi.LocationInfo convertToLog4jLocationInfo ( ch.qos.logback.classic.spi.CallerData[] callerData) { if (!includeCallerData || callerData == null || callerData.length == 0) { return org.apache.log4j.spi.LocationInfo.NA_LOCATION_INFO; } ch.qos.logback.classic.spi.CallerData data = callerData[0]; return new org.apache.log4j.spi.LocationInfo( data.getFileName(), data.getClassName(), data.getMethodName(), String.valueOf(data.getLineNumber())); } private static org.apache.log4j.spi.LoggingEvent convertToLog4jEvent ( ch.qos.logback.classic.spi.LoggingEvent event) { String fqnOfCategoryClass = "todo: fqn"; long timestamp = event.getTimeStamp(); org.apache.log4j.Level level = org.apache.log4j.Level.toLevel( event.getLevel().toInt() ); String message = event.getFormattedMessage(); String threadName = event.getThreadName(); String loggerName = event.getLoggerRemoteView().getName(); org.apache.log4j.spi.ThrowableInformation throwableInformation = convertToLog4jhTrowableInformation(event.getThrowableInformation()); String ndc = null; // not supported by SLF4J and LogBack ? org.apache.log4j.spi.LocationInfo locationInfo = convertToLog4jLocationInfo(event.getCallerData()); Map<String,String> mdc = event.getMDCPropertyMap(); org.apache.log4j.spi.LoggingEvent log4jEvent = new org.apache.log4j.spi.LoggingEvent(); log4jEvent.setFQNOfLoggerClass(fqnOfCategoryClass); log4jEvent.setLoggerName(loggerName); log4jEvent.setTimeStamp(timestamp); log4jEvent.setLevel(level); log4jEvent.setMessage(message); log4jEvent.setThreadName(threadName); log4jEvent.setThrowableInformation(throwableInformation); if (mdc != null) { //noinspection unchecked log4jEvent.setProperties(new Hashtable(mdc)); } log4jEvent.setLocationInformation(locationInfo); log4jEvent.setNDC(ndc); //log4jEvent.setSequenceNumber(4); log4jEvent.setRenderedMessage(message); return log4jEvent; } private static class SocketHandler implements Runnable { Socket socket; ObjectInputStream ois; org.apache.log4j.net.SocketAppender log4jAppender; public SocketHandler(Socket socket, org.apache.log4j.net.SocketAppender log4jAppender) { this.socket = socket; this.log4jAppender = log4jAppender; try { ois = new ObjectInputStream(new BufferedInputStream(socket .getInputStream())); } catch (Exception e) { System.err.println("Could not open ObjectInputStream to " + socket); e.printStackTrace(); } } public void run() { ch.qos.logback.classic.spi.LoggingEvent event; try { while (true) { // read an event from the wire try { event = (ch.qos.logback.classic.spi.LoggingEvent) ois.readObject(); } catch (EOFException e) { info("client disconnected"); break; } catch (IOException e) { e.printStackTrace(); break; } catch (ClassNotFoundException e) { e.printStackTrace(); break; } if (event == null) { continue; } org.apache.log4j.spi.LoggingEvent log4jEvent = convertToLog4jEvent(event); log4jAppender.append(log4jEvent); } } catch (Exception e) { System.err.println("Unexpected exception. Closing connection."); e.printStackTrace(); } try { ois.close(); } catch (Exception e) { System.err.println("Could not close connection."); e.printStackTrace(); } } } }

4 5

[Bug 102] New: unregistering in the jmx plugin
by bugzilla-daemon＠pixie.qos.ch 27 Sep '07

27 Sep '07

http://bugzilla.qos.ch/show_bug.cgi?id=102 Summary: unregistering in the jmx plugin Product: logback-classic Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Other AssignedTo: logback-dev(a)qos.ch ReportedBy: hontvari3(a)solware.com I started using the JMX plugin of login, and I wondered how should I shut it down when a web application is restarted. I haven't found a function which unregisters the Configurator MBean. This object holds a reference (through ContextAwareBase) to a Context. I am afraid that not unregistering it causes a memory leak when a web application is restarted. There should be a way to shutdown the JMX plugin. Or more generally an API to shut down the Logback system in its entirety: flush buffers, close files etc. It must be decided what to do if a log request arrives when or after logback is shutting down. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 101] New: rolling policy which starts new file on system startup
by bugzilla-daemon＠pixie.qos.ch 27 Sep '07

27 Sep '07

http://bugzilla.qos.ch/show_bug.cgi?id=101 Summary: rolling policy which starts new file on system startup Product: logback-core Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P4 Component: Rolling AssignedTo: logback-dev(a)qos.ch ReportedBy: hontvari3(a)solware.com I would add an option to the rolling appender to start a new file not only when the trigger fires but also when the system is started. According to the email thread on logback-dev this can be for example an option of the current trigger implementations. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

jmx plugin, unregistering
by Hontvari Jozsef 27 Sep '07

27 Sep '07

I started using the JMX plugin of login, and I wondered how should I shut it down when a web application is restarted. I haven't found a function which unregisters the Configurator MBean. This object holds a reference (through ContextAwareBase) to a Context. I am afraid that not unregistering it causes a memory leak when a web application is restarted.

2 1

rolling policy with starting new file on system startup
by Hontvari Jozsef 27 Sep '07

27 Sep '07

I would add an option to the rolling appender to start a new file not only when the trigger fires but also when the system is started. This doesn't seem to be a difficult task but there are several possible solutions: -it can be an option of the current trigger implementations. As I know actually there is only one trigger implementation, the other trigger type is only implicitly used with time based rolling -it can be a standalone trigger, this is also useful if we don't want to limit the size of the log file -there is an existing attribute of the file appender, named "append". This attribute already has a very similar (the same?) meaning. It causes to start a new log file on startup (i.e. delete its previous content). Currently if this "append" attribute is switched on then the rolling appender literally follows the previous definition and it overwrites the previous content of the last file, instead of rolling the last file. It is unlikely that this is what the user wants. For me the last alternative seems to be the best. What do you think?

2 1

[Bug 98] New: logback mail lists cannot be reached
by bugzilla-daemon＠pixie.qos.ch 27 Sep '07

27 Sep '07

http://bugzilla.qos.ch/show_bug.cgi?id=98 Summary: logback mail lists cannot be reached Product: logback-site Version: unspecified Platform: All URL: http://www.dnsstuff.com/tools/dnsreport.ch?domain=qos.ch OS/Version: All Status: NEW Severity: normal Priority: P3 Component: other AssignedTo: logback-dev(a)qos.ch ReportedBy: hontvari3(a)solware.com Hi, my emails to the logback mail lists are consitently bouncing. A quick check on qos.ch DNS configuration shows there are serious problems with it. Likely this is why your mail server appears to never be available. See for example this report: http://www.dnsstuff.com/tools/dnsreport.ch?domain=qos.ch -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 4

Fwd: [logback-dev] Eclipse plugin
by Maarten Bosteels 27 Sep '07

27 Sep '07

Hello, I am using the LogBack Eclipse plugin. Eclipse version: Version: 3.3.0 Build id: I20070621-1340 I folowed the instructions from http://logback.qos.ch/consolePlugin.html and I just tried with the logback.xml configuration file from the instructions, and of course it works as well. What exactly isn't working for you ? Maarten On 9/26/07, Vicente Ferrer <vteferrer(a)gmail.com> wrote: > Thanks for your response, Maarten. > > If you don't put the <consolePlugin /> tag on logback.xml, what do you do to > show the logback log lines on eclipse plugin? Or... aren't you ussing that > plugin? Maybe are you using a log4j eclipse plugin, like Ganymede? > > Thanks again > > 2007/9/25, Maarten Bosteels <maarten(a)apache.org>: > > I forgot to mention that I have not tried the <consolePlugin /> tag. > > > > I used the following logback.xml : > > > > <?xml version="1.0" encoding="UTF-8"?> > > <configuration> > > <appender class=" ch.qos.logback.core.ConsoleAppender" > > name="RootConsoleAppender"> > > <filter > class="ch.qos.logback.classic.filter.ThresholdFilter"> > > <level>debug</level> > > </filter> > > <layout > class="ch.qos.logback.classic.PatternLayout"> > > <pattern>%d{yyyy-MM-dd HH:mm:ss},%p,%c,%t %m%n</pattern> > > </layout> > > </appender> > > <appender class=" > ch.qos.logback.classic.net.SocketAppender" > > name="RootSocketAppender"> > > <filter > class="ch.qos.logback.classic.filter.ThresholdFilter"> > > <level>debug</level> > > </filter> > > <remoteHost>mortimer.example.com</remoteHost> > > <port>4321</port> > > <reconnectionDelay>30000</reconnectionDelay> > > <includeCallerData>true</includeCallerData> > > </appender> > > > > <root> > > <level value="debug"/> > > <appender-ref ref="RootConsoleAppender"/> > > <appender-ref ref="RootSocketAppender"/> > > </root> > > </configuration> > > > > Maarten > > > > On 9/25/07, Maarten Bosteels <maarten(a)apache.org> wrote: > > > I installed it today and it works. > > > Haven't done extensive testing, but everything I tried (MDC and > > > throwables) seems to work. > > > > > > I would have preferred that logging events were shown in a table > > > (column per field) > > > instead of stringified. But I never use eclipse, so I don't really care > :-) > > > > > > Is anyone working on a plugin for Intellij IDEA ? > > > > > > Maarten > > > > > > On 9/25/07, Vicente Ferrer <vteferrer(a)gmail.com> wrote: > > > > Hi to all, > > > > > > > > I'm having some problems with logback eclipse plugin... ¿somebody has > used > > > > the logback eclipse plugin with success? > > > > > > > > Thanks a lot. > > > > > > > > _______________________________________________ > > > > logback-dev mailing list > > > > logback-dev(a)qos.ch > > > > http://qos.ch/mailman/listinfo/logback-dev > > > > > > > > > > > > > > > _______________________________________________ > > logback-dev mailing list > > logback-dev(a)qos.ch > > http://qos.ch/mailman/listinfo/logback-dev > > > > > > > _______________________________________________ > logback-dev mailing list > logback-dev(a)qos.ch > http://qos.ch/mailman/listinfo/logback-dev > >

3 4