October 2011 - logback-user

unsubscribe
by Leonid Ilyevsky 24 Oct '11

24 Oct '11

Leonid Ilyevsky Moon Capital Management, LP 499 Park Avenue New York, NY 10022 P: (212) 652-4586 F: (212) 652-4501 E: lilyevsky(a)mooncapital.com [cid:image001.png@01CC924C.BDADDE40] ________________________________ 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.

1 0

Invalid URL reference in logback error code
by Stevo Slavić 24 Oct '11

24 Oct '11

Hello logback users, When trying out perf4j's recently added support for logback I followed example from perf4j logback package javadoc which can be found here: http://perf4j.codehaus.org/apidocs/index.html?org/perf4j/logback/package-su… That example at the moment has a bug, perf4jFileAppender is referenced from a logger, but the appender is listed in configuration file after logger. Logback's AppenderRefAction reports this as an error with following code {code} ... Appender appender = (Appender) appenderBag.get(appenderName); if (appender == null) { String msg = "Could not find an appender named [" + appenderName + "]. Did you define it below in the config file?"; inError = true; addError(msg); addError("See " + CoreConstants.CODES_URL + "#appender_order for more details."); return; } ... {code} Url this produces in logback-classic 0.9.30 is http://logback.qos.ch/codes.html#appender_order When accessed, error codes page opens, but on it there is no explanation for this error and in the page source there is no element with appender_order id. Couldn't find in the history of the codes.html page ( https://github.com/ceki/logback/commits/master/logback-site/src/site/pages/… ) one revision that ever had this. Am I missing something or is this a bug in logback site? Regards, Stevo.

6 19

Configuration Failure
by Pete Haidinyak 19 Oct '11

19 Oct '11

Hi, I allow my users to specify an alternate logback configuration file and I was wondering if there was a way to validate that file? Also, I noticed that logback prints out a bunch of failure messages if the file is invalid. Is there a way to disable that? Thanks -Pete

1 0

Cloning LoggingEvent
by Stevo Slavić 18 Oct '11

18 Oct '11

Hello Logback users, Is there a way to clone LoggingEvent? In a custom PatternLayout implementation I'd like just to change the logging event message, so need to create new LoggingEvent with everything same as original LoggingEvent except for the message. Regards, Stevo.

2 2

Turning off sifting appender when MDC not set
by GS 18 Oct '11

18 Oct '11

Hi, I have configured the sifting appender with a default value (unknown) for the discriminator, which generates a file called foo-unknown.log. But I would ideally like the appender to not output to any file when the discriminator via MDC has not yet been set. Any suggestions? Thanks, G

2 1

conversionRule for the File tag and the fileNamePattern
by Marco Sousa 18 Oct '11

18 Oct '11

Hi there. I want to set the filename of the file in the appender dynamic constructed by conversionRule (ClassicConverter). Because the filename is depending the %logger. Converter: if (event.getLoggerName().contains(NEGOCIO)) { StackTraceElement st= event.getCallerData()[0]; filename = st.getClassName(); filename = filename.substring(NEGOCIO.length()); int endIndex = filename.indexOf("."); filename = filename.substring(0, endIndex); } else { filename = event.getLoggerName(); int endIndex = filename.indexOf("."); filename = filename.substring(0, endIndex); } return filename; But the ConversionRule only work for the encoder pattern tag. So how to make it work for file tag and the fileNamePattern tag. I allready try with property but don't work. ------------------------------------- Marco Sousa

2 4

Migrating from log4j: replacing JDBCAppender
by Stevo Slavić 17 Oct '11

17 Oct '11

Hello Logback users, As subject states, I'm trying to migrate a project from log4j to logback, and need to replace log4j JDBCAppender. I've found following related stackoverflow questions: - http://stackoverflow.com/questions/1364322/log-to-a-database-using-log4j/13… - http://stackoverflow.com/questions/7659837/logback-dbappender-custom-sql DBAppender is nice, but it's not 1-to-1 replacement for log4j's JDBCAppender, since it mandates what gets logged, db layout (number of tables and columns) and thus SQL statements number and layout (number of and indexes of parameters). Trying now to implement custom extension of DBAppenderBase to achieve the goal. It would be great if in the logback DB appender hierarchy was additional level, before DBAppenderBase which would abstract away just ConnectionSource related logic, so without subAppend, secondarySubAppend, or selectEventId. Also, to support using to-be-append logging event when generating insert SQL (e.g. using PatternLayout) it would be good if getInsertSQL would receive ILoggingEvent. Now when implementing JDBCAppender which extends DBAppenderBase I have lots of abstract methods "do-nothing" implementations, pattern layout configured with insert statement SQL and following relevant code: protected Layout<ILoggingEvent> layout; protected void setLayout(Layout<ILoggingEvent> layout) { this.layout = layout; } protected String getInsertSQL(ILoggingEvent event) { return layout.doLayout(event); } @Override public void append(ILoggingEvent eventObject) { Connection connection = null; try { connection = connectionSource.getConnection(); connection.setAutoCommit(false); PreparedStatement insertStatement; insertStatement = connection .prepareStatement(getInsertSQL(eventObject)); int updateCount = insertStatement.executeUpdate(); if (updateCount != 1) { addWarn("Failed to insert loggingEvent"); } // we no longer need the insertStatement close(insertStatement); insertStatement = null; connection.commit(); } catch (Throwable sqle) { addError("problem appending event", sqle); } finally { DBHelper.closeConnection(connection); } } What do you think about improvement requests? Should I log them in JIRA? Any thoughts on this JDBCAppender replacement? What will be the penalty for generating insert statement SQL for every logging event using Layout? Regards, Stevo.

2 1

Obtaining logger list
by Stevo Slavić 17 Oct '11

17 Oct '11

Hello Logback users, I'm trying to migrate from log4j, more specifically to find a replacement for org.apache.log4j.LogManager.getCurrentLoggers Is there any other way to obtain Logger list except through JMX and JMXConfigurator? Accessing LoggerContext would be enough too - how does one grab a hold of that one? I see ContextAware interface and Base implementation, maybe if my custom class would implement/extend these I could get LoggerContext, but how do I register my components with Logback to have the LoggerContext injected? Regards, Stevo.

4 4

Specifying the location of the default configuration file via servlet context parameter
by Stevo Slavić 13 Oct '11

13 Oct '11

Hello Logback users, Logback documentation is great, and in it among other things one can find example for specifying the location of the default logback configuration file as a system property (see http://logback.qos.ch/manual/configuration.html#configFileProperty ) This is nice for command line tools, but not as usable for webapps, typically each web application is configured with separate logback configuration file, so if there is more than one application running. I've found logback-classic has ContextDetachingSCL (ServletContextListener) for stopping logging context when servlet context is destroyed. Maybe similar LogbackConfigurationSCL implementation could be added to logback-classic, to support specifying the location of the default configuration file via servlet context parameter (could be named same as system property, logback.configurationFile) which LogbackConfigurationSCL would use when context is initialized to initialize logback configuration. There is issue though, if both system property and servlet context parameter were specified, which one should logback use. Typically in other libraries, tools etc. (like Maven) system property takes precedence, but in this case, I'm not sure, maybe servlet context parameter should be given precedence. What does community think about this feature? Regards, Stevo.

1 0

logback-access and conditional configuration
by Marshall Pierce 09 Oct '11

09 Oct '11

I got the conditional configuration syntax (http://logback.qos.ch/manual/configuration.html#conditional) working fine for logback-classic, but logback-access doesn't seem to honor it. Is it supported (and I'm just not doing it right)? Thanks, Marshall

2 2