- logback-user - mailman3.qos.ch

JMXConfigurator OName
by Pritchard, Ellis - Ealing 15 Aug '08

15 Aug '08

Hi, I've currently got multiple logback-enabled servlets running under the same JVM, each in separate web contexts, and each with their own logback.xml and slf4j/logback jars in WEB-INF. Whist this works (in terms of logging), the jmxConfigurator MBean seems to only refer to one of the contexts, and has the name 'default'. I can't see the loggers listed for the other contexts. What I'd expected to see is a different MBean listed for each webapp context. Looking at the jmxConfigurator code, it seems to use the name of the logging context for the JMX name; how does this get set? Can it be set in the logback.xml? Ellis. ------------------------------------------------------------------------------------------------------------ This email (and any attachment) is confidential, may be legally privileged and is intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient please do not disclose, copy or take any action in reliance on it. If you have received this message in error please tell us by reply and delete all copies on your system. Although this email has been scanned for viruses you should rely on your own virus check as the sender accepts no liability for any damage arising out of any bug or virus infection. Please note that email traffic data may be monitored and that emails may be viewed for security reasons. John Wiley & Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. ------------------------------------------------------------------------------------------------------------

4 7

Re: [logback-user] How to get log configuration errors logged but not debug?
by Syvalta 13 Aug '08

13 Aug '08

Thanks for your answers Ceki and Anton, and sorry for the delay to answer. I will submit an issue as suggested. And sorry for using confusing terms, by logging errors I meant just the ability to print logback errors to sdterr by configuration. Ceki Gulcu-2 wrote: > > Hello Syvalta, > > Thank you for your message. I'd to point out that logback does not and > cannot > *log* from within itself, To be more precise, logback does not generate > logging > requests without solicitation from client code (code outside logback). > There is > actually code within logback that drops log messages generated by logback > components. > > However, logback components are allowed to generate status messages about > their > internal state and add them to the StatusManager associated with the > logback > context. Note that most logback components have a reference to their > context. > > If you wanted to have only Warn and Error status messages printed, you > could > write your own StatusManager that does just that. Unfortunately, at > present time > you cannot tell LoggerContext to use a StatusManager different than the > default. > > If you kindly enter a Jira issue asking for this feature, I'd be happy to > oblige. > -- View this message in context: http://www.nabble.com/How-to-get-log-configuration-errors-logged-but-not-de… Sent from the Logback User mailing list archive at Nabble.com.

1 1

logback.xml problem
by Chris Cheshire 12 Aug '08

12 Aug '08

I am trying to convert from log4j to logback, and up until now I have just used the default logging configuration logback provides. Now I am trying to get the errors emailing out, and I have created a logback.xml, put it under "resources" and compiled it into my application jar, yet when I run my app it doesn't appear that the config file is even being loaded (I put a debug="true" in the configuration element and nothing appears on the console like in the example 3.4 in the documentation). What am I missing? The documentation says to create a file called logback.xml and place it in a folder on the classpath and the default configurator will find it, yet it is not. Please help! Chris -- View this message in context: http://www.nabble.com/logback.xml-problem-tp18936222p18936222.html Sent from the Logback User mailing list archive at Nabble.com.

2 2

Is HTMLLayoutBase/WriterAppender correct?
by Natan Cox 08 Aug '08

08 Aug '08

Hi, If I look into the code I can see in WriterAppender writeFooter String h = layout.getFileFooter(); if ((h != null) && (this.writer != null)) { try { this.writer.write(h); String pf = layout.getPresentationFooter(); if (pf != null) { this.writer.write(pf); } And if I look into HTMLLayoutBase I see getFileFooter => </body></html> getPresentationFooter => </table> which means we are first closing the HTML and then the TABLE? I think this is a bug. Thanks & regards! Natan Cox

2 1

Christopher White is out of the office.
by Christopher.White＠bbh.com 08 Aug '08

08 Aug '08

I will be out of the office starting 08/08/2008 and will not return until 08/14/2008. I will respond to your message when I return. *************************** IMPORTANT NOTE***************************** The opinions expressed in this message and/or any attachments are those of the author and not necessarily those of Brown Brothers Harriman & Co., its subsidiaries and affiliates ("BBH"). There is no guarantee that this message is either private or confidential, and it may have been altered by unauthorized sources without your or our knowledge. Nothing in the message is capable or intended to create any legally binding obligations on either party and it is not intended to provide legal advice. BBH accepts no responsibility for loss or damage from its use, including damage from virus. ************************************************************************

1 0

Just started playing with logback
by Rob Ross 06 Aug '08

06 Aug '08

Hello. I finally got around to downloading logback and playing with it. So far, it's been very easy to substitute it for log4j. Let me say first that I think log4j is one of the best Java frameworks ever written, up there with JUnit. It does a specific job very well, with a very lightweight API and it is very easy to get started using it. It also has enough depth to be able to customize things when you need to customize them. So let me say you've done a very good job with log4j, and I'm sure logback will be even better. I have a few comments for you. First, the log4j properties translator ( http://logback.qos.ch/translator/Welcome.do ) does not quite work. Maybe it's based on an old version and is now out of date, but you should think about updating it. The file it produced did not translate my properties that I used in log4j.properties to specify the log file path into the equivalent substitutionProperty elements, and it did not translate the Levels I had set on the log4j appenders. It did wrap them in Threshold elements, but the current XML schema wants these specified in a "filter" element on the appender. Also, it did not translate the settings for the rolling file appender into the FileNamePattern element. However, the Joran configurator gave me detailed enough Exception messages that it was easy to determine what the problems were and fix them. Also, on Chapter 3 of the current Logback documentation manual, when it discusses variable substitution it mentions "Recursive Substitution." Well, if you re-read that section carefully I think you'll agree that this example is in fact NOT doing any kind of *recursion*, it is just using multiple variables. They are not even being nested. So I would suggest calling it something other than "recursion." The people that will read this manual are programmers, and we all know (or should know ) what recursion is, and I think this will just confuse people. I also have a question about functionality. The only difference between log4j and logback that I have noticed so far is a different behavior between the way each will create the log file (for a FileAppender) if it does not yet exist. In log4j when I specified a full path, it would also create the directory for the log file if it did not already exist. Logback does not create the directory, it throws an exception. So I will have to add this to my Java code, but it smells a little fishy to have to configure where the logs are created in two different contexts, one in my application (by creating the directory), one in the logback configuration file. Maybe you can give me a good reason for why this new way is better, or maybe it's just an oversight and it has not been implemented yet? I was wondering what your thoughts were about this? Thank you for your great work on creating some great logging frameworks that really provide useful functionality for Java programs! Rob Ross, Lead Software Engineer E! Networks --------------------------------------------------- "Beware of he who would deny you access to information, for in his heart he dreams himself your master." -- Commissioner Pravin Lal

3 3

Logback Console Plugin for Eclipse: ECF seems to be required - to document?
by Olivier Cailloux 06 Aug '08

06 Aug '08

Hi, I installed Logback Console Plugin for Eclipse as suggested in http://logback.qos.ch/consolePlugin.html, and after a long search, I finally made it work by installing (through eclipse "find and install" functionality) Eclipse Communication Framework Application and Eclipse Communication Framework Core API. I don't know if both are required, but with none of these two the new logback view was not available for me (didn't appear in the list of views). Could this please be documented on the website? The best would naturally to provide a feature for the logback plugin and make it available through eclipse "find and install" and "select required dependencies" features, but at least adding a simple sentence in the documentation would help and take few time. Thank you for your attention and for the wonderful logback. Olivier

1 0

FallBack Appender and error handler
by Jonathan Dray 24 Jul '08

24 Jul '08

Hi, I previously used log4j with a JMSAppender sending messages to a specific ActiveMq Queue. I managed to configure a FallBackErrorHandlor with a second JMSAppender in case the first JMSAppender was not able to write to the queue. The ErrorHandler was also configured to send emails when something went wrong. I now want to try logback and wonder if there is a way to get errors returned by loggers at runtime. Plesae consider the following situation : ** * Hello world! * */ public class App { public static void main( String[] args ) { ... ... (some code herer) Logger log = LoggerFactory.getLogger("myLogger"); log.debug("App : main"); System.out.println( "Normal end of my process" ); } } Let's assume the "myLogger" is configured to use a JMSAppender. I want to know if the log.debug call failed and then not to display "Normal end of my process." 1. Is this possible ? 2. How should I handle errors dealing with logback logger ? Thank you Regards, Jonathan Dray

2 2

Manfred Kuhlmann is out of office.
by Manfred.Kuhlmann＠steria-mummert.de 21 Jul '08

21 Jul '08

Ich werde ab dem 21.07.2008 nicht im Büro sein. Ich kehre zurück am 11.08.2008. I will be out of the office starting 21.07.2008. I will be back on 11.08.2008. Ihre Nachricht werde ich nach meiner Rückkehr beantworten. I will answer your message after my return. Mit freundlichen Grüßen Best regards Manfred Kuhlmann

1 0

Re: [logback-user] Configuring jndi db access in tomcat5.5: some thoughts
by Ceki Gulcu 17 Jul '08

17 Jul '08

Diego Louzán wrote: > The last couple of days I've been learning about SLF4J and Logback. IMHO > this is a great piece of software. Thanks. > One of my needs was to configure logging to a JNDI shared database > inside tomcat 5.5. I followed the directions outlined in > http://logback.qos.ch/manual/appenders.html for configuring the > DBAppender with a JNDIConnectionSource. > > The example code in the manual is like this: > > <connectionSource class="ch.qos.logback.core.db.JNDIConnectionSource"> > <param name="jndiLocation" value="jdbc/MySQLDS" /> > <param name="username" value="myUser" /> > <param name="password" value="myPassword" /> > </connectionSource> > > (BTW, the "username" param in the documentation is wrong, it must be > "user"). If it's not too much to ask, could you please enter a bug report regarding this problem? Actually, you might want to reference this whole thread as from what I could understand, there are multiple issues involved. [snip] > As you can see, tomcat references a JCL logger in > "org.apache.catalina.core.ContainerBase.getLogger" just when first > loading the webapp. This triggers logback initialization, and when the > JNDIConnectionSource tries to get a reference to the DataSource, it > finds nothing. Interesting problem. One way to solve it would be to perform logback configuration in two stages. In the first stage, you would configure logback as usual, using logback.xml. In the second, you would use another config file, say logback-db.xml and invoke Joran after tomcat has been initialized. Here is sample code: LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); URL url = Loader.getResource("logback-db.xml", classLoader); JoranConfigurator configurator = new JoranConfigurator(); LoggerContext loggerContext = () configurator.setContext(lc); configurator.doConfigure(url); > I found a reference to a similar problem with JNDI contexts in the old > bugzilla tracker (http://marc.info/?l=logback-dev&m=119005116732589&w=2) > but although I tried locating this bug report in the new JIRA tracker I > could not find it. Maybe it got lost during the migration? It's here: http://jira.qos.ch/browse/LBCLASSIC-30 I found it by going to jira.qos.ch, FIND ISSUES and entering 96 as the bugzilla id to search for (at the bottom of the page). Entering "ContextSelectors" as the query text also yields valid results. So, it looks like the migration was OK. > At the moment I'm still trying to fully understand the codebase. Do you > figure out any solution to the problem? See above. > I'm sorry for such a lengthy message. Hope this info helps the project. > Regards and keep up the good work. Thanks, > Diego. -- Ceki Gülcü QOS.ch is looking to hire talented developers located in Switzerland to work on cutting-edge software projects. If you think you are qualified, then please contact ceki(a)qos.ch.

1 0