OK, so, it's probably due to the workaround I did for log:display and log:tail commands.
Let me take a look. Thanks for the report ! Regards JB On 03/01/2018 07:06 PM, afbagwe wrote: > > Whenever I perform the client log commands. There's no indication of a > problem immediately after startup if I examine the log outside of Karaf. > > -A > > > > jbonofre wrote >> Hi >> >> We didn't change the Pax Logging (Log4j2) version between 4.1.4 and 4.1.5. >> >> Maybe we introduced a regression due to KARAF-5528 even if it looks >> unrelated. >> >> However, the issue seems to come from karaf log, not pax logging directly. >> The >> change can cause the issue is KARAF-5559. >> In order to avoid infinite loop, log:display & log:tail commands now tries >> to >> change the log level of sshd to error (when it's debug). >> >> When do you have this exception ? At startup or when you perform >> log:tail/log:display ? >> >> Regards >> JB >> >> -- >> Jean-Baptiste Onofré > >> jbonofre@ > >> http://blog.nanthrax.net >> Talend - http://www.talend.com > > > > > > -- > Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
