Ah, now that Jira is up I can see that an issue had already been created.

http://jira.qos.ch/browse/LOGBACK-1194


Von: logback-user [mailto:logback-user-boun...@qos.ch] Im Auftrag von ceki
Gesendet: Freitag, 16. September 2016 20:44
An: logback users list <logback-user@qos.ch>
Betreff: Re: [logback-user] jira down; ReconfigureOnChangeTask bug

Jira should be up now. Please create a jira issue for the scanPeriod bug. I'll 
look into it on Tuesday as I am currently traveling.


--
Ceki


-------- Original message --------
From: stefan.brozin...@materna.de<mailto:stefan.brozin...@materna.de>
Date: 2016/09/16 18:41 (GMT+01:00)
To: logback-user@qos.ch<mailto:logback-user@qos.ch>
Subject: [logback-user] jira down; ReconfigureOnChangeTask bug
Dear all,

just in case you haven’t noticed: jira.qos.ch is currently down (http 503).

I would also like to point out that the git commit 1518573 introduced a bug.
Having only the „scan“ attribute in the logback configuration without an 
additional „scanPeriod“ attribute does NOT activate the ReconfigureOnChangeTask.

So currently you need to have something like scanPeriod=“60 seconds“ in your 
logback.xml if you want to have your configuration changes being picked up 
without having to restart your process.

This might also be the reason for the problems that were recently observed by 
Gaël Marziou.
Gaël, does it help to add a scanPeriod to your configuration?

Best regards
Stefan

_______________________________________________
logback-user mailing list
logback-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-user

Reply via email to