February 2017 - logback-user

Logback => TLS/SSL => Syslog ?
by Otis Gospodnetić 21 Feb '19

21 Feb '19

Hi, Does Logback support sending logs to Syslog servers via TLS/SSL? I have a feeling Logback doesn't have a SyslogAppender that can send data using TLS. I say that because I don't see a mention of "syslog" on http://logback.qos.ch/manual/usingSSL.html and I see http://jira.qos.ch/browse/LOGBACK-890 that mentions TLSSyslogAppender, but it looks like this never ended up in Logback. I've only found it committed here: https://github.com/balabit/logback/commit/e0d89de2536e0925a6c816a50793f6a74… Could anyone please clarify? Thanks, Otis -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr & Elasticsearch Support * http://sematext.com/

2 1

Versioning policy?
by list+ch.qos.logback＠io7m.com 25 Feb '17

25 Feb '17

Hello. I use Logback and SLF4J in a rather large number of projects. I like to keep dependencies up-to-date, and this means that I end up incrementing a large set of version numbers fairly frequently. It would reduce my workload if I could specify a version range in my dependency declarations for both Logback and SLF4J. However, I can only do this safely if I know the versioning policy of both of those projects. It sort of looks like they use something like Semantic Versioning [0], but I don't see an explicit policy written down anywhere. Can I use version ranges such as [1.7.0, 2.0.0) safely? M [0] http://semver.org/

2 2

Logback p2 repository unreachable
by contact＠goko.fr 09 Feb '17

09 Feb '17

Hello, I’ve been using the logback p2 repository for some eclipse build using P2 (https://logback.qos.ch/p2/) For a few weeks ( probably January 2017, but not sure), it’s unreachable with the following error : Internal error: java.lang.RuntimeException: Failed to load p2 repository with ID 'logback' from location http://logback.qos.ch/p2/: Unable to read repository at http://logback.qos.ch/p2/content.xml. sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Failed to load p2 repository with ID 'logback' from location http://logback.qos.ch/p2/ Trying to access it in the browser gives a 403 error. Could you please fix this ? Thanks

2 2

Release of logback version 1.2.0
by Ceki Gülcü 08 Feb '17

08 Feb '17

Hello all, I am happy to announce the release of logback version 1.2.0. It contains bug fixes and significant *performance* improvements. It should hit the Maven central repository by the time you read this message. This release also fixes a rather severe serialization vulnerability in SocketServer and ServerSocketReceiver. Users running these components should upgrade immediately. Please refer to the news page for precise details. http://logback.qos.ch/news.html For review of performance figures, see: http://tinyurl.com/logbackPerf You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki

1 0

Benchmark
by Jiri Pejchal 07 Feb '17

07 Feb '17

Hi, I've tried to run logback-perf, may you'll find the result useful. Jiří Pejchal logback 1.1.10, CPU E3-1240 v5 @ 3.50GHz, Samsung SSD 850 PRO 128GB, JDK 1.8.0_102 "Benchmark","Mode","Threads","Samples","Score","Score Error (99.9%)","Unit" "ch.qos.logback.perf.FileAppenderBenchmark.log4j1File","thrpt",1,10,1577.009429,33.154970,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2File","thrpt",1,10,1997.150618,5.731020,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2RAF","thrpt",1,10,2141.647559,8.157930,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.logbackFile","thrpt",1,10,2480.481451,71.973275,"ops/ms" "Benchmark","Mode","Threads","Samples","Score","Score Error (99.9%)","Unit" "ch.qos.logback.perf.FileAppenderBenchmark.log4j1File","thrpt",2,10,1124.216809,24.067386,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2File","thrpt",2,10,2759.163123,37.934327,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2RAF","thrpt",2,10,2739.519271,39.348186,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.logbackFile","thrpt",2,10,1448.307609,14.708407,"ops/ms" "Benchmark","Mode","Threads","Samples","Score","Score Error (99.9%)","Unit" "ch.qos.logback.perf.FileAppenderBenchmark.log4j1File","thrpt",4,10,778.720898,35.585861,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2File","thrpt",4,10,2410.408163,74.131141,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2RAF","thrpt",4,10,2833.438968,192.704404,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.logbackFile","thrpt",4,10,664.899426,174.136282,"ops/ms" "Benchmark","Mode","Threads","Samples","Score","Score Error (99.9%)","Unit" "ch.qos.logback.perf.FileAppenderBenchmark.log4j1File","thrpt",8,10,444.521720,4.222798,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2File","thrpt",8,10,1877.270743,563.989875,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2RAF","thrpt",8,10,1718.415344,355.749375,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.logbackFile","thrpt",8,10,589.209144,14.991014,"ops/ms" "Benchmark","Mode","Threads","Samples","Score","Score Error (99.9%)","Unit" "ch.qos.logback.perf.FileAppenderBenchmark.log4j1File","thrpt",16,10,1047.869080,31.680525,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2File","thrpt",16,10,958.811252,9.776799,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2RAF","thrpt",16,10,923.054985,12.930723,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.logbackFile","thrpt",16,10,627.107129,26.521755,"ops/ms" "Benchmark","Mode","Threads","Samples","Score","Score Error (99.9%)","Unit" "ch.qos.logback.perf.FileAppenderBenchmark.log4j1File","thrpt",32,10,782.954165,44.671984,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2File","thrpt",32,10,947.090112,14.686491,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2RAF","thrpt",32,10,887.397303,9.720897,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.logbackFile","thrpt",32,10,605.394268,47.669206,"ops/ms" "Benchmark","Mode","Threads","Samples","Score","Score Error (99.9%)","Unit" "ch.qos.logback.perf.FileAppenderBenchmark.log4j1File","thrpt",64,10,1059.913755,35.506168,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2File","thrpt",64,10,972.569039,42.377445,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.log4j2RAF","thrpt",64,10,990.437705,18.712172,"ops/ms" "ch.qos.logback.perf.FileAppenderBenchmark.logbackFile","thrpt",64,10,539.095359,52.330557,"ops/ms"

2 6

Release of logback version 1.1.10
by Ceki Gülcü 05 Feb '17

05 Feb '17

Hello all, I am happy to announce the release of logback version 1.1.10. It contains bug fixes and significant *performance* improvements. It should hit the Maven central repository by the time you read this message. Please refer to the news page for precise details. http://logback.qos.ch/news.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki

1 0

logback-access in an embedded jetty server
by Jan-Olav Eide 01 Feb '17

01 Feb '17

I have small main program that fires up a Jetty 9 server. This server is able to run/deploy any war file supplied to it as a command line argument. I construct a *logback-access* appender programmatically, give that appender to an instance of *ch.qos.logback.access.jetty.RequestLogImpl* and wrap that instance in a *org.eclipse.jetty.server.handler.RequestLogHandler* that is finally supplied to the jetty server: handlers.addHandler(webappHandler(contextPath(), warURL())); handlers.addHandler(requestLogHandler()); server.setHandler(handlers); Now, the web-application also uses logback, and has those artifacts in its *WEB_INF/lib* directory inside the war. It appears that the logback-access configuration in the main program and the logging performed by the webapp somewhat interfere with eachother. The symptom is that I see nothing in the request log, so I guess the logging configuration in the webapp "wins", and overrides the request log configuration in the main program. If I do not deploy a webapp, but instead just serve some static files, the request log works as expected, so I believe that my appender is constructed correctly. Is there any way the logging configuration from the webapp and the request log configuration from the server can co-exist ?

2 9