- logback-user - mailman3.qos.ch

RollingFileAppender Issues
by Omar Alrubaiyan 23 Jul '10

23 Jul '10

Hello,I’m trying to use logback for a distributed application that I’m working on. I have a custom appender that buffers log messages and then sends them over to a central logger via RMI. The central logger collects the logs and outputs them to a logback logger that uses a RollingFileAppender with a FixedWindowRollingPolicy and a SizeBasedTriggeringPolicy. The problem is when the log file hits the size limit instead of renaming the file and starting a new one it creates 10 (or whatever the max index is for the window) copies of the same file and slows down while failing to properly roll over. This results in (after the first rollover trigger) 1 + max index copies of the same file all of which are over the size limit. This issue does not occur when using the same logback configuration file on a single jvm setup. I’ve tried the following:- Did away with the custom appender on the clients side and just transmitted raw messages over RMI (i.e. only one central Logback logger is used). Did not resolve the issue.- Switched to a TimeBasedRollingPolicy, under this policy the archiving seems to work properly but the rollover never occurs (the original log file keeps growing).- Switched the central logger over to log4j, this fixed the issue, although I would rather use logback instead.Any ideas about what could be causing this?Thanks,Omar _________________________________________________________________ http://clk.atdmt.com/UKM/go/197222280/direct/01/ We want to hear all your funny, exciting and crazy Hotmail stories. Tell us now

2 4

logback and manual rollover (from java)
by lgonggr 23 Jul '10

23 Jul '10

Hi, I used log4j before and I triggered my RollingFileAppender rollover() manually in some places (batches). I need to create seperate logfiles for each batch run. I want it to rollover using the FixedWindowRollingPolicy if the logfile exceeds 10MB and at the start of each batch run. I've migrated to logback now and it works well, but I can't figure out how to rollover my RollingFileAppender manually. What I have now : <appender name="EntityToCSV" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>/home/tomcat/overname_test_logs/EntityToCSV.log</File> <encoder> <pattern>%d{yyyy-MM-dd HH:mm:ss} %-5p [%t] %c{1}: %m%n</pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <maxIndex>9</maxIndex> <FileNamePattern>/home/tomcat/overname_test_logs/EntityToCSV.log.%i</FileNamePattern> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <MaxFileSize>10MB</MaxFileSize> </triggeringPolicy> </appender> <logger name="nl.realworks.apps.overname.EntityToCSV" level="INFO"> <appender-ref ref="EntityToCSV"/> </logger> in EntityToCSV.java : private static final Logger LOGGER = LoggerFactory.getLogger(EntityToCSV.class); public static void main(String[] args) throws Exception { OvernameUtils.manualRollover(LOGGER); // do stuff and log it in OvernameUtils.java : public static void manualRollover(Logger logger) { Utils.assertNotNull("logger is null.", logger); if (logger instanceof RollingFileAppender) { // <--- FAIL ! try { ((RollingFileAppender)logger).rollover(); } catch (Exception e) { logger.error("rollover failed.", e); } return; } String message = logger.getName() + " is not an instance of RollingFileAppender."; logger.error(message, new RuntimeException(message)); } This won't work of course as Logger != Appender. I have no idea how to get from the Logger to its Appender(s). In log4j you could just do getAppender() but this is not possible with org.slf4j.Logger Perhaps this is a totally wrong approach. Any tips would be greatly appreciated. -- View this message in context: http://old.nabble.com/logback-and-manual-rollover-%28from-java%29-tp2923714… Sent from the Logback User mailing list archive at Nabble.com.

3 2

Advice please
by Jesse Long 21 Jul '10

21 Jul '10

Hi All, Please advise me whether the following is possible, and how to go about implementing it in Logback. I have a web app, with servlets for the web pages, as well as soap web services. Additionally, I have some background threads that do all sorts of interesting things. The servlets, web services and background threads all use the same data model classes which are backed by an orm data access layer, which uses JDBC to get data from a DB. I want all logging that happens while handling a servlet request to go to one log file, all logging that happens while handling a soap web service call to go to another log file, and all logging that happens in a background thread to go to another log file. Also, I want to log all the data model, orm and JDBC layer information to separate log files at debug and up level. For example, imaging the following list of log events (in this order): Logger Level Expected log files x.soap info soap.log x.model info soap.log,model.log x.orm debug orm.log x.orm info soap.log,model.log,orm.log x.jdbc debug jdbc.log x.jdbc info soap.log,model.log,orm.log,jdbc.log x.soap calls x.model, which calls x.orm, which calls x.jdbc. Similar traces for x.servlet, x.helperthread etc. I cant use Logger name to decide which appenders log, but what can I use? How can I achieve this? I would appreciate any pointers. Thanks, Jesse

2 1

logback and jetty 7
by Ramon Salla 19 Jul '10

19 Jul '10

Could you please update this http://logback.qos.ch/access.html to jetty 7 thankyou! Ramon Salla

1 0

Re: [logback-user] TurboFilter scope
by Espen Rydningen 13 Jul '10

13 Jul '10

Hi I want to revisit this subject and theme. I saw that this thread ended 20th May 2008, but I did not find any conclusions on your discussion. The reason I find this subject interesting, is that I have use case which I can't seem to solve in any other way then setting a turbofilter on an appender. This is situation: One enterprise web application, which today uses a proprietary, home built, logging framework, logs statement to both file and to a database via an EJB. I have started the work to replace this logging framework with LogBack/SL4J. Our new design would include a jms queue where we post log messages, and we would use the jms appender to get this done, and a <codeSnippet> logger.debug("Bar property was not defined in abc.properties"); FooLog.log(logcontext, 6001, new String[] { "Bar property was not defined in abc.properties" }, null); </codeSnippet> The logger is the file logger and the FooLog is responsible for sending log message to the EJB <codeSnippet> logger.debug("com.a.b.c.configfile was not defined in abc.properties"); </codeSnippet> <codeSnippet> Marker JMS_MARKER = MarkerFactory.getMarker("JMS"); logger.debug("com.a.b.c.configfile was not defined in abc.properties"); </codeSnippet> This is my use case:

3 5

Integrating OSGi (Felix), Logback and SLF4J
by Sander de Groot 13 Jul '10

13 Jul '10

I'm trying to integrate Logback Classic in Apache Felix. My goal is to have a bundle-based context system so each bundle has it's own logging factory. It's important that each bundle is able to supply it's own configuration file. I've tried a few things and even wrote a simple ContextSelector but I don't seem to get it right. Therefore I thought: before going in a time consuming trial and error process let's ask the experts first. So, my question: how can I create new loggercontexts efficiently with each a separate configuration? Regards, Sander

3 6

Custom appender
by Frank Grimm 13 Jul '10

13 Jul '10

Dear mailing list, I'm trying to use logback (via its slf4j API) in an Eclipe/OSGi environment. More specifically I'm trying to write a logback appender that redirects log events to the Eclipse logging mechanism (org.eclipse.core.runtime.ILog). So the first thing I did was to create an Eclipse plugin/PDE project for the custom appender. In the project, the following class was added: package logback.eclipseappender; import ch.qos.logback.core.AppenderBase; public class EclipseAppender extends AppenderBase<Object> { @Override protected void append(Object eventObject) { // TODO } } The a logback configuration that made use of the custom appender was added to the project, too: <configuration> <appender name="eclipse" class="eclipseappender.EclipseAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%d %p %t %c - %m%n</Pattern> </layout> </appender> <root level="debug"> <appender-ref ref="eclipse"/> </root> </configuration> When the custom appender plugin/bundle is started in a new Eclipse runtime environment, the appender's class cannot be found (see stacktrace below). I've read in another post (DynamicClassLoadingException - How does class loading in logback works?) that logback might require the logback jar files and the custom appender jar file to be bundled together. But bundling them does not make sense in OSGi environments since single bundles for each of logback's components (core, classic, slf4j API) and custom appenders should be used. Is there a way to make logback see the appender class event if it's in another jar/bundle? Thanks, Frank 11:00:58,210 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [eclipseappender.EclipseAppender] 11:00:58,211 |-ERROR in ch.qos.logback.core.joran.action.AppenderAction - Could not create an Appender of type [eclipseappender.EclipseAppender]. ch.qos.logback.core.util.DynamicClassLoadingException: Failed to instantiate type eclipseappender.EclipseAppender at ch.qos.logback.core.util.DynamicClassLoadingException: Failed to instantiate type eclipseappender.EclipseAppender at at ch.qos.logback.core.util.OptionHelper.instantiateByClassName(OptionHelper.java:53) [...] Caused by: java.lang.ClassNotFoundException: eclipseappender.EclipseAppender at at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:506) at at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422) at at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410) at at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at at ch.qos.logback.core.util.OptionHelper.instantiateByClassName(OptionHelper.java:45) at ... 52 common frames omitted

3 4

logback
by Kaushal Shriyan 13 Jul '10

13 Jul '10

Hi Is there a howto for setting up logback on tomcat application server 5.5.27 Thanks, Kaushal

1 0

Using logback from tomcat and webapp
by Justin Nixon 12 Jul '10

12 Jul '10

Hi, I'm trying to use logback for both tomcat internal logging and for all logging from my web app. I was able to accomplish routing all logging through logback by placing logback-classic, logback-core and jcl-over-slf4j into my Tomcat 5.5\common\lib directory and the corresponding logback.xml file into the Tomcat 5.5\common\classes. However, I'm unable to use any custom layouts and appenders. Is there a recommended way to include another logback.xml file in my webapp so that I can use custom layouts and appenders? I'm experimenting with JoranConfigurator, but I haven't had any luck yet. Thanks in advance. Regards, Justin

1 0

Help with Tomcat -> GUI Viewer logging setup
by Steve Johnson 09 Jul '10

09 Jul '10

Greetings, I apologize in advance if my question is obviously documented somewhere already. If so, I haven't been able to find those docs and would welcome being simply pointed to them. I'm looking to switch to Logback after years of struggling with log4j and chainsaw within a Tomcat environment. I'm hoping to get some advice up front to save me frustration in getting to what I want with Logback. What I'd like to do is have multiple web applications running in a single Linux hosted Tomcat instance log to the same log stream. I'd like this stream to be viewable on a remote Windows workstation via a GUI app (via Lilith, I guess). Preferably, multiple GUIs on different workstations ought to be able to view the log stream simultaneously. Also, it would be great if something like ZeroConf could be used such that no mucking with config files and IP addresses will be necessary. I've had some luck getting all of this going with log4j and chainsaw, but the system has always been kinda flakey. I had everything set up with ZeroConf, but I had to write my own version of the ZeroConfSocketHubAppender to bump the port number when a socket bind failed to deal with the fact that multiple appenders would be created by my various web applications and would otherwise all contend for the same local port. I want something more reliable and robust. So, can anyone offer suggestions for getting to such a setup with Logback? Which sort of appender should I use? What gotchas should I be aware of? I quickly reviewed the document "Access log with logback, Jetty and Tomcat", but I find that document kinda confusing. Does this module simply offer a web interface to logs, or is it something more? Would it be any help in my situation if I'm not interested in accessing logs via HTTP? TIA for any help you can provide. Steve

3 2