Re: ConfigurationBuilder stack traces and exception swallowing

2020-01-06 Thread Bobby Bissett
Hi, Thanks for the quick response on this; sorry for my delay. In short, I get that people don't want logging frameworks to fail, but in this case it is failing (due to bad inputs) but not telling our application. Here's a description of what our app does. When starting it, a "launcher" program i

Re: ConfigurationBuilder stack traces and exception swallowing

2019-11-13 Thread Ralph Goers
In general, our suggestion is to use the configuration file as a template and use dynamic components such as Lookups or Selectors. Choosing the log file directory could easily be handled by a Lookup, depending on what criteria you are using to determine it. In general, Logging Frameworks need

ConfigurationBuilder stack traces and exception swallowing

2019-11-13 Thread Bobby Bissett
Hi all, We use log4j2, version 2.11.1, and have programmatic configuration because we don't know until runtime what the logging settings are. For instance, log directory for file logging, or syslog settings if that's used instead. I can provide the code we use to set things up if it helps, but do