April 2011 - logback-user - mailman3.qos.ch

Loglevel Question
by Yihya Hugirat 08 Apr '11

08 Apr '11

hi all, is it possible to set the loglevels dynamically, throw the property file, for more than one web app. ??? Best regadrs Yahya -- إِنَّ الَّذِينَ يُحِبُّونَ أَنْ تَشِيعَ الْفَاحِشَةُ فِي الَّذِينَ آمَنُوا لَهُمْ عَذَابٌ أَلِيمٌ فِي الدُّنْيَا وَالآخِرَةِ وَاللَّهُ يَعْلَمُ وَأَنْتُمْ لا تَعْلَمُونَ My public key please use it when you contact me: هذا مفتاحي العام الرجاء أستخدامه عند الإتصال بي: 09BA B710 4B98 ECDA 8C0A 6CB1 2E1E CF88 6A12 F2C3

1 0

Logback viewer
by Gadkari Amit 07 Apr '11

07 Apr '11

We want to analysis files generated by Logback fileappender Which should be best log viewer for this? Do any log viewer provides web interface (servlet) for displaying files generated by logback file appender I understand that lilith is for online viewing of logevents generated by socket appender and for generating log file based on collected log events

2 1

syslogappender
by David Tkaczyk 07 Apr '11

07 Apr '11

I saw this in a post stating that it would be in 0.9.20. I'm currently using 0.9.26. <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d %t [%-5level] - %-40class{40} - %msg%n</pattern> <charset>UTF-8</charset> </encoder> </appender> Is there charset support for the syslogappender as well? If so, how is it configured as I don't see the "encoder" element in the documentation for syslogappender either? Thanks, Dave

1 0

Q: How to capture SocketAppender-format data to a file?
by Richard Wagner 06 Apr '11

06 Apr '11

Hi - Sorry in advance if this is a FAQ: I didn't find an answer after searching for a while, hence this email... On the one hand, I'm using a SocketAppender for sending serialized LoggingEventVO objects from some of my company's software (which I help develop) to a custom consumer of such events. That works just fine. But now I also want to configure a "logback.xml" file so that the same kind of serialized LoggingEventVO objects can alternatively be captured to a file. We need that when either QA engineers or end-users are running the software, but do not have access to the socket server that I use (and hence can't use the SocketAppender). The hope is that then the QA engineer or end-user could get that log file to me, and I could have my serialized event consumer read from the file, instead of getting the data from a socket connection. Then I can diagnose that QA person's problem, or end-user's problem. However, I don't know what particular logback XML to use. I tried a "FileAppender" / "ObjectStreamEncoder" combination, but the file ended up being empty (whereas a simple ConsoleAppender proved there were in fact events to capture). Here's my failed XML: <appender name="SERIALIZED_FILE" class="ch.qos.logback.core.FileAppender"> <file>log_output_serialized.bin</file> <append>false</append> <encoder class="ch.qos.logback.core.encoder.ObjectStreamEncoder" /> </appender> <root level="ALL"> <appender-ref ref="STDOUT" /> <appender-ref ref="SERIALIZED_FILE" /> </root> Do I need to write my own variant of "FileAppender": one which (like SocketAppender) doesn't use an Encoder, but instead bakes in the code to serialize LoggingEventVO objects? Thanks in advance, Rich Wagner Rich Wagner | Senior Software Engineer | StreamBase Systems, Inc., 181 Spring Street, Lexington, MA 02421 rwagner(a)streambase.com<mailto:rwagner@streambase.com> | (p) +1 781-761-0868 | http://www.streambase.com<http://www.streambase.com/> StreamBase - 2010 World Economic Forum Technology Pioneer<http://www.time.com/time/specials/packages/article/0,28804,1948486_1948485_…>

1 0

Logback configuration
by Neha Kothari 06 Apr '11

06 Apr '11

Hi have started to use logback for logging in java. I am using "TimeBasedRollingPolicy" rolling policy as I wanted dated logs. My file pattern looks like c:/spg-live.%d{yyyy-MM-dd}.%i.log Is there a way that I can put a maxIndex (i.e the maximum limit for i) using the same rolling policy? Thanks --- This communication may contain confidential and/or privileged information. If you are not the intended recipient (or have received this communication in error) please notify the sender immediately and destroy this communication. Any unauthorized copying, disclosure or distribution of the material in this communication is strictly forbidden. Deutsche Bank does not render legal or tax advice, and the information contained in this communication should not be regarded as such.

3 4

ClassCastException with ViewStatusMessagesServlet
by Robert Magnus 06 Apr '11

06 Apr '11

Hi I tried to use the HTTP-access logs in JBoss 6.0. Following http://logback.qos.ch/access.html I did: - copy logback-access-0.9.28.jar and logback-core-0.9.28.jar to server/default/lib - edit server/default/deploy/jbossweb.sar/server.xml and add the line <Valve className="ch.qos.logback.access.tomcat.LogbackValve"/> - put a logback-access.xml to server/default/conf/ - edit my web.xml and add the servlet and the servlet-mapping After starting the JBoss I navigate to the lbAccessStatus url an got this exception: java.lang.ClassCastException: ch.qos.logback.core.BasicStatusManager cannot be cast to ch.qos.logback.core.status.StatusManager ch.qos.logback.access.ViewStatusMessagesServlet.getStatusManager(ViewStatusMessagesServlet.java:32) ch.qos.logback.core.status.ViewStatusMessagesServletBase.service(ViewStatusMessagesServletBase.java:51) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) Any ideas? regards, Robert -- Robert Magnus akquinet tech@spree GmbH Bülowstraße 66, D-10783 Berlin Tel. +49 (0)30 235 520 - 44 Fax. +49 (0)30 217 520 - 12 Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth Amtsgericht Berlin-Charlottenburg HRB 86780 B USt.-Id. Nr.: DE 225 964 680

1 0

JoranConfigurator printing status data
by Will Taylor 05 Apr '11

05 Apr '11

Hi, I'm using JoranConfigurator directly to configure my logging context. It is printing out a ton of status information because I have multiple instances of logback.xml on my classpath (this is expected). Is there a way to change this behavior and have JoranConfigurator only print errors? Thanks, --Will Taylor will.taylor(a)dealer.com 802.540.2869

1 0

irc room for logback
by Yihya Hugirat 05 Apr '11

05 Apr '11

hi all, is there any irc room for logback user or developer -- إِنَّ الَّذِينَ يُحِبُّونَ أَنْ تَشِيعَ الْفَاحِشَةُ فِي الَّذِينَ آمَنُوا لَهُمْ عَذَابٌ أَلِيمٌ فِي الدُّنْيَا وَالآخِرَةِ وَاللَّهُ يَعْلَمُ وَأَنْتُمْ لا تَعْلَمُونَ My public key please use it when you contact me: هذا مفتاحي العام الرجاء أستخدامه عند الإتصال بي: 09BA B710 4B98 ECDA 8C0A 6CB1 2E1E CF88 6A12 F2C3

2 1

Retrieving the log filenames
by Clemens Siebler 04 Apr '11

04 Apr '11

Hi all, I'm currently using Logback (SLF4J) with a TimeBasedRollingPolicy defined in logback.xml. Everything works fine, however, I'd like to retrieve the filenames of the current logging session since the application started. The user can obviously change the log filenames and policies in logback.xml, so I don't want them hardcoded in the source. My goal is to retrieve these filenames straight within Java in order to do some more processing with them. Is there any possibility in logback/slf4j to retrieve those names? I currently aquire the logger via: Logger logger = LoggerFactory.getLogger(Test.class); but obviously, this Logger object in particular doesn't provide such functionality. Any ideas? Thanks in advance, Clemens

4 10

java.net.SocketException with logback-access on jetty 6
by Steven Parkes 02 Apr '11

02 Apr '11

Not sure if this is a jetty issue or a logback issue: I'm getting intermittent errors using logback-access to write the jetty access log. Full backtrace below. A race condition? Maybe the socket already closed before the logger gets run? I've seen it on 6.1.24 and 6.1.26 with 0.9.28. java.lang.Error: java.net.SocketException: Socket operation on non-socket at sun.nio.ch.Net.localAddress(Net.java:128) at sun.nio.ch.SocketChannelImpl.localAddress(SocketChannelImpl.java:423) at sun.nio.ch.SocketAdaptor.getLocalAddress(SocketAdaptor.java:147) at java.net.Socket.getLocalSocketAddress(Socket.java:717) at org.mortbay.io.nio.ChannelEndPoint.getLocalPort(ChannelEndPoint.java:341) at org.mortbay.jetty.Request.getLocalPort(Request.java:839) at ch.qos.logback.access.spi.AccessEvent.getLocalPort(AccessEvent.java:445) at ch.qos.logback.access.spi.AccessEvent.prepareForDeferredProcessing(AccessEvent.java:481) at ch.qos.logback.core.OutputStreamAppender.subAppend(OutputStreamAppender.java:211) at ch.qos.logback.core.OutputStreamAppender.append(OutputStreamAppender.java:108) at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:88) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:64) at ch.qos.logback.access.jetty.RequestLogImpl.log(RequestLogImpl.java:133) at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:51) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) Caused by: java.net.SocketException: Socket operation on non-socket at sun.nio.ch.Net.localInetAddress(Native Method) at sun.nio.ch.Net.localAddress(Net.java:125) at sun.nio.ch.SocketChannelImpl.localAddress(SocketChannelImpl.java:423) at sun.nio.ch.SocketAdaptor.getLocalAddress(SocketAdaptor.java:147) at java.net.Socket.getLocalSocketAddress(Socket.java:717) at org.mortbay.io.nio.ChannelEndPoint.getLocalPort(ChannelEndPoint.java:341) at org.mortbay.jetty.Request.getLocalPort(Request.java:839) at ch.qos.logback.access.spi.AccessEvent.getLocalPort(AccessEvent.java:445) at ch.qos.logback.access.spi.AccessEvent.prepareForDeferredProcessing(AccessEvent.java:481) at ch.qos.logback.core.OutputStreamAppender.subAppend(OutputStreamAppender.java:211) at ch.qos.logback.core.OutputStreamAppender.append(OutputStreamAppender.java:108) at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:88) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:64) at ch.qos.logback.access.jetty.RequestLogImpl.log(RequestLogImpl.java:133) at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:51) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

1 0