In case there is an intializing exception in logback.groovy, the logback module will become dysfunctional. ---------------------------------------------------------------------------------------------------------- Key: LBGENERAL-46 URL: http://jira.qos.ch/browse/LBGENERAL-46 Project: logback-general Issue Type: Bug Affects Versions: unspecified Environment: All Reporter: Rathnadhar.K.V Assignee: Logback dev list Priority: Critical When there is an exception while parsing logback.grooy (like the one that is logged in LBGENERAL-45), then no further logging actions takes place. In the program RUN mode (as against the DEBUG mode), the program continues to execute but without any logging messages. There is no way to tell what state the main program is. Now its correct that the main program should run in case of failure of logger. But it is also critical to log the issues at least on the console. So there in case of exception in parsing the logback.groovy, the logger should fall back on default logging mechanism and should not become dysfunctional. Regards Rathnadhar.K.V -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira