May 2012 - logback-user - mailman3.qos.ch

SyslogAppender stacktrace logging prefix
by Jiri Sitina 30 May '12

30 May '12

Hi, we have recently switched from Log4J to Logback. Logging seems to work well except stack traces in SyslogAppender. They are prefixed just like remaining log messages. Is there any way how to disable this prefix and ensure they will be printed in the same manner like with Log4J SyslogAppender? Current behavior: Apr 02 12:31:08 host.name 2012-04-02T12:31:08.418+0200 ajp-bio-8009-exec-7 com.gooddata.exception.servlet.HttpExceptionTranslator ERROR: Processing client_request=/gdcwebapp/gdc/projects/FoodMartDemo/groups/everyone status=FAILED errorCode=gdc.usergroups.default_group_modification errorDescription="Attempt to modify default group (everyone)" exceptionId=abc37cf0-9c56-4e68-a4a7-2111ca823fd4 component=webapp request_id=cAWvICOaKVFF1VvI userId=1 projectId=FoodMartDemo nodeId=nodeOne nodeId=nodeOne, requestId=cAWvICOaKVFF1VvI, userId=1, projectId=FoodMartDemo Apr 02 12:31:08 host.name #011at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Apr 02 12:31:08 host.name #011at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) Apr 02 12:31:08 host.name #011at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) Apr 02 12:31:08 host.name #011at java.lang.reflect.Method.invoke(Method.java:601) Apr 02 12:31:08 host.name #011at org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:212) Apr 02 12:31:08 host.name #011at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:126) Apr 02 12:31:08 host.name #011at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:96) Apr 02 12:31:08 host.name #011at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:617) Apr 02 12:31:08 host.name #011at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:578) Apr 02 12:31:08 host.name #011at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:80) Apr 02 12:31:08 host.name #011at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:900) Desired behavior: Apr 02 12:31:08 host.name 2012-04-02T12:31:08.418+0200 ajp-bio-8009-exec-7 com.gooddata.exception.servlet.HttpExceptionTranslator ERROR: Processing client_request=/gdcwebapp/gdc/projects/FoodMartDemo/groups/everyone status=FAILED errorCode=gdc.usergroups.default_group_modification errorDescription="Attempt to modify default group (everyone)" exceptionId=abc37cf0-9c56-4e68-a4a7-2111ca823fd4 component=webapp request_id=cAWvICOaKVFF1VvI userId=1 projectId=FoodMartDemo nodeId=nodeOne nodeId=nodeOne, requestId=cAWvICOaKVFF1VvI, userId=1, projectId=FoodMartDemo at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:212) at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:126) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:96) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:617) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:578) at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:80) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:900) Current logback.xml for SyslogAppender: <appender name="SYSLOG" class="ch.qos.logback.classic.net.SyslogAppender"> <facility>local2</facility> <syslogHost>localhost</syslogHost> <suffixPattern>%d{yyyy-MM-dd'T'HH:mm:ss.SSSZ} %t %c %p: %m component=webapp request_id=%X{requestId} userId=%X{userId} projectId=%X{projectId} nodeId=%X{nodeId} %X%n</suffixPattern> </appender> Thanks in advance for any advice. Best regards Jiri Sitina -- View this message in context: http://old.nabble.com/SyslogAppender-stacktrace-logging-prefix-tp33555063p3… Sent from the Logback User mailing list archive at Nabble.com.

2 4

Re: [logback-user] RCP
by Tony Trinh 28 May '12

28 May '12

On Thu, May 24, 2012 at 9:01 AM, David Virdefors < david.virdefors(a)purplescout.se> wrote: > Hi,**** > > ** ** > > I had a look at it. However it seemed to be outdated, and I really want to > use the the existing ”Error Log” view. **** > > > I took a dive and figured it out. The first step is to add the external JARs to your project. I created a "libs" directory under my Eclipse plugin project, and symlinked the JARs there. Then I specified these project JARs with the "Bundle-ClassPath" property in the plugin's manifest. You can edit this classpath a couple ways: OPTION 1: Manually add "Bundle-ClassPath" property to META-INF/Manifest.MF like so: Bundle-ClassPath: ., libs/slf4j-api-1.6.4.jar, libs/logback-classic-1.0.3.jar, libs/logback-core-1.0.3.jar Add any other external JARs to this list if necessary. Note the first path is "." to tell the plugin to include its root directory in its classpath (it's not smart enough to assume that). OPTION 2: Use the Eclipse GUI to edit MANIFEST.MF. 1. Double-click META-INF/MANIFEST.MF, which automatically opens a GUI presenter for the file's contents. 2. Click the "Runtime" tab in the presenter. 3. In the "Classpath" section, click "New". In the prompt that opens, enter the relative path to the external JAR (e.g., libs/logback-core-1.0.3.jar). 4. Repeat step 3 for each external JAR. 5. Add the plugin's root directory to the classpath (click "New", and enter "."). 6. Sanity check: Click the "MANIFEST.MF" tab. Verify that the "Bundle-ClassPath" property contains the paths you just entered. See the attached sample project with this all working. I created the EclipseLogAppender class, which writes to Eclipse's Error Log. (It would be nice to add this class to logback's source, but it's dependent on Eclipse packages...not sure how to handle that.) To run the example: 1. From Eclipse, import the attached sample project (choose menu "File > Import... > Existing Projects into Workspace"). 2. Download logback-core-1.0.3.jar, logback-classic-1.0.3.jar, and slf4j-api-1.6.4.jar into the project's "libs" directory. 3. Rebuild and run the project (which opens a new instance of Eclipse). 4. From the new instance of Eclipse, open the Error Log (menu "Window > Show Views > Error Log"), and choose menu "Sample Menu > Sample Command". This causes a "Hello World" message box, followed by a log entry in the Error Log.

3 8

Re: [logback-user] RCP
by ceki 24 May '12

24 May '12

On 24.05.2012 14:59, David Virdefors wrote: What's with the "at at" ? Anyway, I cleaned up and copied the stack trace to github:gist. The cleaned up stack trace is available at https://gist.github.com/2781498 Looking at line 47 of that gist, you can see that org.eclipse.osgi.internal.loader.BundleLoader is being used to load foo.RCPAppender which fails. Can you make foo.RCPAppender available to BundleLoader? > Hi, here is the rest of the stack trace: > 14:14:04,991 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - > About to instantiate appender of type [foo.RCPAppender] > 14:14:04,992 |-ERROR in ch.qos.logback.core.joran.action.AppenderAction - > Could not create an Appender of type [foo.RCPAppender]. > ch.qos.logback.core.util.DynamicClassLoadingException: Failed to > instantiate type foo.RCPAppender > at ch.qos.logback.core.util.DynamicClassLoadingException: Failed > to instantiate type foo.RCPAppender > at at > ch.qos.logback.core.util.OptionHelper.instantiateByClassName(OptionHelper. > java:54) > at at > ch.qos.logback.core.util.OptionHelper.instantiateByClassName(OptionHelper. > java:32) > at at > ch.qos.logback.core.joran.action.AppenderAction.begin(AppenderAction.java: > 54) > at at > ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java > :276) > at at [snip] -- Ceki http://twitter.com/#!/ceki

1 0

Multiple layouts for a single appender
by Y M 24 May '12

24 May '12

Hello, My situation is this: on certain specific and frequent log statements, I need the stacktrace to identify the method that needs to be investigated. However, the whole stacktrace is too long and unnecessary in this case (it is generating too much logging and garbage), but in every other, it is useful. I'd like to change the layout for this situation, and use %throwable{5}, for example. So, I found nothing on the manual similar to this, and nothing searching around, maybe I'll need a custom class. If so, how could I do it? Multiple filtered appenders writing to the same file seems too much overhead and troublesome; I think the best approach would be a custom encoder, and do the selection inside 'doEncode', based on some event parameter, probably a specific marker. I'm just analyzing the possibilities, no coding yet, so I'm not aware of any shortcomings or limitations. Given the case, is there any API class I'm missing to do this? Should I take the custom code path? Thanks!

2 4

Re: [logback-user] RCP
by Tony Trinh 24 May '12

24 May '12

On Thu, May 24, 2012 at 5:40 AM, David Virdefors < david.virdefors(a)purplescout.se> wrote: > Hi,**** > > ** ** > > I’m developing Eclipse RCP plug-ins. Is it possible to make logback log to > the existnig workspace log, so that the logs show up in the ”Error Log” > view in the GUI? > You might be interested in the Logback Eclipse Console plugin [1]. However, I've never used it, so I don't know whether it's functional today. It might at least give you a starting point to work from. [1]: http://logback.qos.ch/consolePlugin.html

2 1

Re: [logback-user] RCP
by ceki 24 May '12

24 May '12

Anyway, even without the stack trace, we can assume that your custom appender will be instantiated by calling the instantiateByClassName(String, Class, Context) method in OptionHelper (line 36). This method assumes that you want to use the class loader which loaded the current logback context to be used. (This is usually the same class loader that loaded all other logback classes as well.) Thus, you have to make sure that the said class loader can load foo.RCPAppender. Can you do that? -- Ceki http://twitter.com/#!/ceki On 24.05.2012 14:20, David Virdefors wrote: > Hi, > > It seems like there is no built in support for logging from within an > Eclipse RCP plug-in. So I wrote my own appender and pointed to it from > my logback.xml > > 14:14:04,992 |-ERROR in ch.qos.logback.core.joran.action.AppenderAction > - Could not create an Appender of type [foo.RCPAppender]. > ch.qos.logback.core.util.DynamicClassLoadingException: Failed to > instantiate type se.ericsson.baseband.logging.RCPAppender > > at ch.qos.logback.core.util.DynamicClassLoadingException: Failed to > instantiate type foo.RCPAppender > > I’ve seen other people who have trouble with this when using ecilpse > plug-ins and bundles due to different class loaders. I have however not > found any proper solution to this. > > How would I make logback find my appender? > > BR David > > *From:*logback-user-bounces@qos.ch [mailto:logback-user-bounces@qos.ch] > *On Behalf Of *David Virdefors > *Sent:* den 24 maj 2012 11:41 > *To:* logback-user(a)qos.ch > *Subject:* [logback-user] RCP > > Hi, > > I’m developing Eclipse RCP plug-ins. Is it possible to make logback log > to the existnig workspace log, so that the logs show up in the ”Error > Log” view in the GUI? > > BR David >

2 1

Re: [logback-user] RCP
by ceki 24 May '12

24 May '12

Hi David, Do you have more lines of the stack trace? -- Ceki http://twitter.com/#!/ceki On 24.05.2012 14:20, David Virdefors wrote: > Hi, > > It seems like there is no built in support for logging from within an > Eclipse RCP plug-in. So I wrote my own appender and pointed to it from > my logback.xml > > 14:14:04,992 |-ERROR in ch.qos.logback.core.joran.action.AppenderAction > - Could not create an Appender of type [foo.RCPAppender]. > ch.qos.logback.core.util.DynamicClassLoadingException: Failed to > instantiate type se.ericsson.baseband.logging.RCPAppender > > at ch.qos.logback.core.util.DynamicClassLoadingException: Failed to > instantiate type foo.RCPAppender > > I’ve seen other people who have trouble with this when using ecilpse > plug-ins and bundles due to different class loaders. I have however not > found any proper solution to this. > > How would I make logback find my appender? > > BR David > > *From:*logback-user-bounces@qos.ch [mailto:logback-user-bounces@qos.ch] > *On Behalf Of *David Virdefors > *Sent:* den 24 maj 2012 11:41 > *To:* logback-user(a)qos.ch > *Subject:* [logback-user] RCP > > Hi, > > I’m developing Eclipse RCP plug-ins. Is it possible to make logback log > to the existnig workspace log, so that the logs show up in the ”Error > Log” view in the GUI? > > BR David

1 0

Re: [logback-user] RCP
by David Virdefors 24 May '12

24 May '12

Hi, It seems like there is no built in support for logging from within an Eclipse RCP plug-in. So I wrote my own appender and pointed to it from my logback.xml 14:14:04,992 |-ERROR in ch.qos.logback.core.joran.action.AppenderAction - Could not create an Appender of type [foo.RCPAppender]. ch.qos.logback.core.util.DynamicClassLoadingException: Failed to instantiate type se.ericsson.baseband.logging.RCPAppender at ch.qos.logback.core.util.DynamicClassLoadingException: Failed to instantiate type foo.RCPAppender I've seen other people who have trouble with this when using ecilpse plug-ins and bundles due to different class loaders. I have however not found any proper solution to this. How would I make logback find my appender? BR David From: logback-user-bounces(a)qos.ch [mailto:logback-user-bounces@qos.ch] On Behalf Of David Virdefors Sent: den 24 maj 2012 11:41 To: logback-user(a)qos.ch Subject: [logback-user] RCP Hi, I'm developing Eclipse RCP plug-ins. Is it possible to make logback log to the existnig workspace log, so that the logs show up in the "Error Log" view in the GUI? BR David

1 0

Conditional Processing using MDC key/value pairs
by Shane Kelly 24 May '12

24 May '12

Folks, Just wondering if it is possible to perform conditional processing in Logback by inspecting the MDC for the presence of and/or value of certain keys. The documentation states "The condition is a Java expression in which only context properties or system properties are accessible" Which "context" is it referring to here? Is the MDC map visible to the conditional expression? Why do I want to do this? Well, in this instance I have a small web-app consisting of a number of servlets. The servlets are stateless/sessionless - they service individual requests from clients, but no session is maintained. In the absence of a unique session ID (I could force a session to be created using getSession() - but that would be wasteful of resources for servlets which don't really need one) I would like to insert another UUID into the log files generated by the server so that its easy to zone in on all the log messages generated as the result of a single incoming client request. The approach I've taken here is to create a Servlet Filter which intercepts all URL request patterns (/*), generates a new UUID and inserts it into the MDC with a specific key (e.g. MyApp-UUID) and removes the key again after control is passed back from the servlet to the filter. I then updated the encoder pattern configuration for the appropriate appenders to insert %X{MyApp-UUID} - and this works as expected - I get a unique UUID value for all messages associated with the same servlet request. However, to take this one step further I would like to use different encoder patterns dependent on whether or not a specific MDC key is present. The following is some pseudo-config which hopefully illustrates the concept: --------------------------- <configuration> <appender name="MyAppender" class="..."> <encoder> <if condition='isDefined("MyApp-UUID")'> <then><pattern>... [%X{AssetTracker-UUID}] ...</pattern></then> <else><pattern>... some other pattern ...</pattern></else> </if> </encoder> </appender> </configuration> --------------------------- So, to recap: (a) can conditional processing expressions access key/value pairs in the MDC map? From my basic experimentation, I'm guessing the answer is no - but then I could just be referencing it incorrectly (b) if the answer to (a) is no, then is there a more suitable approach I should be using instead. Note: Since conditional processing can be used anywhere within the logback configuration I may want to use a similar technique for completely different purposes in future, the example I've given just happens to focus on encoder patterns for illustrative purposes. So I'm after a generic solution that allows conditional processing based on MDC key/value pairs. Regards, Shane

2 3

RCP
by David Virdefors 24 May '12

24 May '12

Hi, I'm developing Eclipse RCP plug-ins. Is it possible to make logback log to the existnig workspace log, so that the logs show up in the "Error Log" view in the GUI? BR David

1 0