- logback-user - mailman3.qos.ch

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

How to ensure initialization (StaticLoggerBinder.init())?
by Daniel Guggi 03 Oct '11

03 Oct '11

hi guys, I try to configure logback for our application in glassfish (3.1) as follows: [*] I start gf with -Dlogback.configurationFile=/path/to/file [*] logback.xml is: *<configuration>  <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <file>../logs/r6.log</file> <encoder> <pattern>%date %-5p [%thread] [%contextName] [%logger{20}] %msg%n</pattern> </encoder> </appender> <root level="debug"> <appender-ref ref="FILE" /> </root> </configuration> * So far everything works fine. However I encountered a problem in the following situation. [*] A simple message driven bean, which is invoked if there are new messages in a given "jms-queue" like this:* @MessageDriven( mappedName="myQueue", activationConfig = { @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"), @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") }) public class MyMdb implements MessageListener { private static Logger logger = LoggerFactory.getLogger(MyMdb.class); @Override public void onMessage(Message msg) { logger.info("got message..."); } }* [*] Glassfish is not running, AND there ARE messages in the queue [*] Now when I start glassfish the application (MyMdb) start receiving the messages from the queue [*] At this point logback is not yet initialized, as I see the following messages in my logfile: *The following loggers will not work becasue they were created during the default configuration phase of the underlying logging system. See also http://www.slf4j.org/codes.html#substituteLogger* Any ideas how to solve this? tia, daniel

1 0

Can logback roll catalina.out?
by Paul Gifford 01 Oct '11

01 Oct '11

Hi, I'm surprised I haven't been able to find the answer to this. Can logback control and roll catalina out? Thanks, Paul

2 2

NOP logger issue/workaround
by Rutger Saalmink 29 Sep '11

29 Sep '11

Hi all, Currently I am developing a logging class for weblogic, which functions as a tool for writing to a set of logfiles. Several types of external parties access this class (e.g. other classes, jars, services, etc), potentially concurrent calls. Conceptually it looks like this: public class myClass{ private static Logger loggerLog = LoggerFactory.getLogger(myClass.class); private static Logger logA = LoggerFactory.getLogger("my.logA"); private static Logger logB = LoggerFactory.getLogger("my.logB"); public static boolean logStringToA(final String strValue){ loggerLog.info("Write String to log A."); logA.info(strValue); } public static boolean logNodeToB(final Node nodeValue){ loggerLog.info("Write Node to log B."); // do some stuff with the Node logB.info(nodeToStringFunction(nodeValue)); } } The problem is that SLF4j gets instantiated with NOP loggers on the first calls to the public methods, possibly due to: http://bugzilla.slf4j.org/show_bug.cgi?id=106 http://bugzilla.slf4j.org/show_bug.cgi?id=176 To fix this problem I try to reload the logback configuration at run-time, explained in http://logback.qos.ch/manual/configuration.html#joranDirectly . However, this means that I will have to reinitialize the loggers in myClass (another call to LoggerFactory.getLogger()) before logging starts. But that would imply using some kind of reloading thread which checks for NOP loggers, which isn't that pretty. Also I would lose any logging calls going on in the meanwhile. Anyone has a good idea on how to prevent SLF4j creating these NOP loggers, or a solution for the workaround? Best regards, Roger

2 2

Logback error
by Mark Woon 29 Sep '11

29 Sep '11

I'm getting the following error whenever I start up Logback: LOGBACK: No context given for ch.qos.logback.core.pattern.parser.Compiler@dc67248 Any idea how I can track down what's causing this? -Mark

1 0

about logback configuration file
by Berker Batur 28 Sep '11

28 Sep '11

Hi, I want to save the current configuration of loggers in my application to the configuration file. Is there anyway or any command to do that ? What I want to do is that: - start the logback with a user defined configuration file - change level of some loggers, from the code, with setLevel method - maybe append a socket appender, again in the code - then, before exiting from the application tell logback to dump all configuration changes to the configuration file. If logback could immediately reflect the changes to the configuration file when a change occurs also works for me. Thanks, Best Regards, Berker Batur

2 2