- logback-user - mailman3.qos.ch

logback.xml configuration scan (Glassfish 3.1)
by Sven Hafner 06 May '11

06 May '11

Hi ! I use below settings and deploy to Glassfish. Logback.xml is not inside the warfile, but I copy it to the classes folder under /domain/application/... <configuration scan="true" scanPeriod="20 seconds" debug="true"> <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener" /> When deploying or restarting the app the config is read .. 16:02:41,826 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Setting ReconfigureOnChangeFilter scanning period to 20 seconds 16:02:41,826 |-INFO in ch.qos.logback.classic.turbo.ReconfigureOnChangeFilter@12a0ca7 - Will scan for changes in [[/home/sven/glassfish3/glassfish/domains/domain1/applications/HelloLog/WEB-INF/classes/logback.xml]] every 20 seconds. 16:02:41,826 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Adding ReconfigureOnChangeFilter as a turbo filter 16:02:41,828 |-INFO in ch.qos.logback.core.joran.action.StatusListenerAction - Adding status listener of type [ch.qos.logback.core.status.OnConsoleStatusListener] .. but it does not re-read on any change, only restarting the app will read changes like debug-level change. Any ideas ? Thanks ! Sven

2 2

How to use UTF-8?
by moxol 05 May '11

05 May '11

I have tried to put some UTF-8 characters with File appender but I didn't succed. It only gives me question marks ?? instead of characters. How to use UTF-8? -- View this message in context: http://old.nabble.com/How-to-use-UTF-8--tp31551911p31551911.html Sent from the Logback User mailing list archive at Nabble.com.

2 2

Urgent: Help needed
by Yihya Hugirat 04 May '11

04 May '11

Hello, i need to configure Netbeans 6.9.1 to color the levels of logback like it does with levels from JUL. Any Help will be appreciated Yahya

1 0

Lilith 0.9.41 has been released!
by Joern Huxhorn 02 May '11

02 May '11

Lilith 0.9.41 - Release Notes This is an interim release because of a rather critical bug discovered by Andy Goossens. Webapps using a ClassicMultiplexSocketAppender would not undeploy properly because of a dangling classloader. I originally wanted to wait for Logback 0.9.29 due to the issues with 0.9.28 described in "Known Issues" below but I was unable to get any ETA for the next release. Changes: - The NDC behavior has changed a bit since it does not inherit the NDC of the parent threads anymore. This is actually a better behavior. Inheriting does not make much sense for an NDC - in contrast to MDC where it is very helpful - since it resembles a contextual "stacktrace". I never documented the previous behavior, anyway. Problem? ;) - Fixed two classloader-leak-issues that prevented proper unloading of webapps upon undeploy/redeploy. 1.) The threads startet by the Lilith multiplex appenders did stop but I didn't bother to wait until they finished doing so. This has been fixed now. All threads are destroyed before stop() returns. 2.) I had an issue in the NDC implementation that was very comparable to the one that caused LBCLASSIC-183. I was putting an instance of a class loaded by the webapp classloader into a ThreadLocal. I fixed this by using two ThreadLocals, a ThreadLocal<String> and a ThreadLocal<String[]>, instead of my own class. This issue was discovered and reported by Andy Goossens. Thank you very much! (issue #96) - Minimize to system tray. Added support for (optional, default is on) system tray icon. Double-clicking the icon hides/shows all windows. The menu also contains a Quit action. If system tray icon is active (supported and enabled) then closing the main frame does not exit the application. This will now hide all windows, instead. This was requested by Adrien Sales and Joe. (issue #91) - Implemented custom "Copy to clipboard" functionality using Groovy. This was suggested by Joe. - Added support for cat/tail of Lilith AccessEvent files. - Better generation of message tooltip. Content is not tailed anymore. - Colors of logging level and access status type are now configurable. (issue #5) - Importing gzipped java.util.logging or log4j xml is now supported. - Using JComboBox & CardLayout instead of JTabbedPane in Preferences Dialog. - "Go to Source" is now executed asynchronously. (issue #12) - Detached windows were using the popup menu of the main frame. They are now using the popup menu of the detached frame as originally intended. This bug was found by Dimi. (issue #95) - Added messagePattern.contains condition and "Copy message pattern" action. Using message pattern for filtering is faster than using message. - Using Mensch font by @robey (Robey Pointer) as the monospace font of the HTML View. - HTML View is now anti-aliasing the fonts. - Updated dependencies: Logback 0.9.28, AspectJ 1.6.10, Jackson 1.7.1, JCommander 1.17, JGoodies Looks 2.2.2, Groovy 1.8.0, commons-lang 2.6, commons-io 2.0.1, httpclient 4.1, httpcore 4.1 Known Issues: - The Logback error message on startup is caused by LBCLASSIC-246 introduced in 0.9.28 and will be fixed in Logback 0.9.29. - cat and tail are currently still experimental features. - LoggingEvent isn't fully supported, yet. See LBCLASSIC-257. - Flying Saucer related issues: - Selection in the HTML view is currently somewhat buggy, especially in case of scaled view. - The first line of the message in HTML view is not properly indented if it starts with whitespace. You can see this effect by examining the event created by LogPinupLargeRunnable (executed via "Log ASCII"). The HTML created is actually correct. - Jumping to anchors is currently not supported so the navigation in help and details view isn't as good as it could be. - Lilith may hang during startup while creating the preferences dialog. Just restart Lilith in that rare case. This is caused by Java bug #6995182 and I can't do anything about it. Sorry about it. It's a stupid Java-MediaTracker-ColorChooser-Bug with no workaround available. m( Cheers, Joern.

1 0

Tomcat hanging when logging in an app at the "error" level?
by Michael Andrews 01 May '11

01 May '11

I thought I would throw this out to the list before I started deep diving. I'm logging with org.slf4j.Logger and logback classic in an app running in Tomcat. Tomcat is using its regular JULI logging. When I use: logger.error(msg); Everything works great. But when I add a Throwable in there: logger.error(msg, t); The connection thread hangs in tomcat. Just thought I'd see if anyone has run into this before. M

1 0

Why DEBUG by default?
by Leonid Ilyevsky 29 Apr '11

29 Apr '11

When logback cannot find configuration file anywhere, it sets the default to send everything to standard output and the level is set to DEBUG. This creates a big problem in our production environment: super-verbose log that is even difficult to look at. My solution was to create a small wrapper using JoranConfigurator. This works great, and I can do whatever I need. However, here is the downside: my code is no longer ignorant of logback. Previously it was purely slf4j everywhere, but now every class is indirectly dependent on logback stuff (though it is limited to 2 lines in every java file). This defeats the purpose of slf4j as pure facade. Is there any better solution? Our problem is, we need to guarantee that no matter what happens in the logging layer, it should never go wild and produce all that debugging noise. ________________________________ This email, along with any attachments, is confidential and may be legally privileged or otherwise protected from disclosure. Any unauthorized dissemination, copying or use of the contents of this email is strictly prohibited and may be in violation of law. If you are not the intended recipient, any disclosure, copying, forwarding or distribution of this email is strictly prohibited and this email and any attachments should be deleted immediately. This email and any attachments do not constitute an offer to sell or a solicitation of an offer to purchase any interest in any investment vehicle sponsored by Moon Capital Management LP ("Moon Capital"). Moon Capital does not provide legal, accounting or tax advice. Any statement regarding legal, accounting or tax matters was not intended or written to be relied upon by any person as advice. Moon Capital does not waive confidentiality or privilege as a result of this email.

6 7

DBAppender arguments
by Alphy 29 Apr '11

29 Apr '11

I am using DBAppender with Postgre as my DB. I created few fields arg0,arg1,arg2,arg3...arg8 to store my arguments separately in each fields. But I realised only arg0 .. arg3 is filled with argument values. But the arguments are added in formatted_message field. I looked into the code and realised only 4 fields are used for storing arguments and maximum length is 254. Is it possible to add more arguments and increase the max size . -- View this message in context: http://old.nabble.com/DBAppender-arguments-tp31502308p31502308.html Sent from the Logback User mailing list archive at Nabble.com.

1 0

Logback JMX Operations and Attributes
by LogbackUser 28 Apr '11

28 Apr '11

I am using glassfish 3.1 as my application server and I have enabled JMX by adding the <jmxConfigurator/> tag in the logback.xml. I am able to view the logback classic mbeans on jconsole but invoking operations like getLoggerLevel fails with an error - "Problem invoking getLoggerLevel : java.lang.IllegalStateException: WEB9031: WebappClassLoader unable to load resource[java.lang.Object], because it has not been started or was always stop...." Accessing the "LoggerList" attribute also does not give any output. Statuses attributes shows the status messages though. Is there anything I am missing in terms of configuration? -- View this message in context: http://old.nabble.com/Logback-JMX-Operations-and-Attributes-tp31423995p3142… Sent from the Logback User mailing list archive at Nabble.com.

1 2

Logback configuration
by Neha Kothari 25 Apr '11

25 Apr '11

If I have a configuration file like the following: <appender name="file" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>test.log</File> <encoder> <pattern>... </pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>test.%d{yyyy-MM}.%i.log</fileNamePattern> <maxHistory>2</maxHistory> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>10MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> </appender> The max history parameter here , does it mean test.2011-04.0.log test.2011-04.1.log And then renaming test.log.2011-04.1.log to test.2011-04.0.log. The new logs go to the file test.2011-04.1.log Or does it mean test.2011-04.0.log test.2011-04.1.log test.2011-04.2.log test.2011-04.3.log test.2011-04.4.log..... Having as many index as needed. But saving this files for 2 months. So that we have something like the following: test.2011-04.0.log test.2011-04.1.log test.2011-04.2.log test.2011-04.3.log....... test.2011-05.0.log test.2011-05.1.log...... Now when we have logs for 2011-06 delete the logs for 2011-04. Which condition applies when you have maxHistory for a filename pattern like '<fileNamePattern>test.%d{yyyy-MM}.%i.log</fileNamePattern>' Thanks Neha --- 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.

1 0

Missing column names in .sql files?
by Simon Gaeremynck 23 Apr '11

23 Apr '11

Hi, I was playing with the DBAppender in order to get some logging data in an Oracle database. I ran the sql scripts for Oracle [1] and created the necessary tables/triggers. The logging didn't happen and failed silently. When I started debugging I noticed that Appender tried to execute an insert query with columnames 'arg0', 'arg1', 'arg2', arg3'. These don't appear in the sql files [1]. Once I added those 4 (with a type: varchar(254) ) logging went perfectly. I'd be happy to provide a patch/JIRA if this is an unknown bug .. (couldn't find it in JIRA.) Kind regards, Simon Gaeremynck [1] http://svn.qos.ch/viewvc/logback/trunk/logback-classic/src/main/java/ch/qos… -- View this message in context: http://old.nabble.com/Missing-column-names-in-.sql-files--tp31461476p314614… Sent from the Logback User mailing list archive at Nabble.com.

1 0