June 2020 - logback-user - mailman3.qos.ch

Shibboleth IDP logs stopped generating after tomcat upgrade to 9.0.31
by Chug, Kshitij (NIH/CIT) [C] 23 Jun '20

23 Jun '20

Hi All, We have been using shibboleth IDP and we noticed that the logs stopped generating after we upgraded tomcat from 9.0.15 to 9.0.31. No changes have been made to logback.xml. I have also checked that logback-core, logback-classic and slf4j-api jar files are present. Can anyone please guide us on how to troubleshoot this issue. Thanks, Regards, Kshitij Chug

1 0

回复： maxIndex issue
by 陌路人 18 Jun '20

18 Jun '20

The max index can not greater than 20, hardcode, in FixedWindowRollingPolicy.java     /**      * It's almost always a bad idea to have a large window size, say over 20.      */     private static int MAX_WINDOW_SIZE = 20; BR, Mike(Yu, Chong-Chao)   ------------------ 原始邮件 ------------------ 发件人: "haobo liu"<lhbazazazv(a)gmail.com>; 发送时间: 2020年6月18日(星期四) 上午9:12 收件人: "logback users list"<logback-user(a)qos.ch>; 主题: Re: [logback-user] maxIndex issue does '200KB' is effective? every file part size is '200KB'? Joud Kassem <joud.kassem79(a)gmail.com> 于2020年6月17日周三下午7:57写道： Hi all, I have my rollingFileAppender configured as follows: appender("myAppender", RollingFileAppender) {         file = "${logDir}/myApp.log"         encoder(PatternLayoutEncoder) {             charset = Charset.forName('UTF-8')             pattern = log_pattern         }         rollingPolicy(FixedWindowRollingPolicy) {             fileNamePattern = "${logDir}/myApp%i.log"             minIndex = 1             maxIndex = 24         }         triggeringPolicy(SizeBasedTriggeringPolicy) {             maxFileSize = FileSize.valueOf("200KB")               }     } I had first the maxIndex = 20, i modified it to 24 and I'm testing. As I see the number of logs are 21 and rotating while it should be 24! I tested it a lot and still the same issue. Anybody has this issue before or knows why this is happening? Thanks in advance, Joud _______________________________________________ logback-user mailing list logback-user(a)qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user

1 0

logback does not print exception's cause
by 陌路人 18 Jun '20

18 Jun '20

Hi, Firstly thank you for your time. Sometimes, logback does not print exception's cause, I can't use the log to fix bug, as followings: 2020-06-09 16:54:32,393 ERROR [task-executor-27] [SimpleDispatcher.java:203] Exception occurred during dispatch web socket frame for uri[/ws/partydungeon/move] by uid[‪6493203‬]. java.lang.reflect.InvocationTargetException: null at sun.reflect.GeneratedMethodAccessor100.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.mitu.game.dispatcher.SimpleDispatcher$EventRunnable.doWebSocketMessage(SimpleDispatcher.java:187) at com.mitu.game.dispatcher.SimpleDispatcher$EventRunnable.run(SimpleDispatcher.java:106) at com.mitu.game.wrapper.ThreadPoolTaskExecutorEx$SafeRunnable.run(ThreadPoolTaskExecutorEx.java:74) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NullPointerException: null 2020-06-09 16:54:32,405 INFO [nioEventLoopGroup-3-4] [SimpleLoggingHandler.java:35] IN {uid=‪5589867‬, forward=183.200.25.192, 183.200.25.192:24172, type=websocket, uri=/ws/user/bind, ts=‪1591692869‬} /10.0.0.70:34948 10 And the code is like:     private void doWebSocketMessage(Event event) {             String uri = "some uri";             String uid = "some id";             try {                 Object ret = action.method.invoke(action.instance, event.getData(), new Object[]{event});             } catch (Exception ex) {                 logger.error(String.format("Exception occurred during dispatch web socket frame for uri[%s] by uid[%s].", uri, uid), ex);             }         } I tried to look for answers by google and bing, but failed, and I tried to reproduce this problem, failed too, the cause can be printed, and it likes: java.lang.reflect.InvocationTargetException: null at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.mitu.game.Application.main(Application.java:54) Caused by: java.lang.NullPointerException: null at com.mitu.game.Application$T.f(Application.java:42) ... 5 common frames omitted  the difference is NativeMethodAccessorImpl vs GeneratedMethodAccessor100, is it matter? I steped into the logback code, maybe the target of the exception is null, but I do not know the reason:( Thank you again, for your patient, and sorry for my poor english:( BR,Mike Yu

2 2

maxIndex issue
by Joud Kassem 18 Jun '20

18 Jun '20

Hi all, I have my rollingFileAppender configured as follows: appender("myAppender", RollingFileAppender) { file = "${logDir}/myApp.log" encoder(PatternLayoutEncoder) { charset = Charset.forName('UTF-8') pattern = log_pattern } rollingPolicy(FixedWindowRollingPolicy) { fileNamePattern = "${logDir}/myApp%i.log" minIndex = 1 maxIndex = 24 } triggeringPolicy(SizeBasedTriggeringPolicy) { maxFileSize = FileSize.valueOf("200KB") } } I had first the maxIndex = 20, i modified it to 24 and I'm testing. As I see the number of logs are 21 and rotating while it should be 24! I tested it a lot and still the same issue. Anybody has this issue before or knows why this is happening? Thanks in advance, Joud

2 1