Hi Remko, I've opened a ticket as you requested: https://issues.apache.org/jira/browse/LOG4J2-1199
Thanks, -Paul On Wed, Nov 18, 2015 at 4:21 AM, Remko Popma <[email protected]> wrote: > Paul, > > The status logger is pretty basic and only supports level based filtering. > > Could you raise a Jira ticket for the change to make > JmxRuntimeInputArgumentsLookup aware of the log4j2.disable.jmx property? > > Thanks! > Remko > > Sent from my iPhone > > On 2015/11/18, at 17:49, Paul K <[email protected]> wrote: > > Hello log4j-devs, > > > We use log4j2 in our project, and since updating to the latest release > (2.4.1) we've been seeing a JMX-related exception being logged at > initialization. Our project runs on Google App Engine, where JMX is not > available. > > I've examined the exchange recorded under LOG4J2-1051 > <https://issues.apache.org/jira/browse/LOG4J2-1051>, a bug that was > resolved in June of this year to address this problem. > > From what I understand, the original bug was severe because it would crash > the application. > The fix applied (wrapping NoClassDefFoundError in an Exception) would > prevent the crash but instead write the error to the system log (status > log): > > LOGGER.error("Unable to create Lookup for {}", entry.getKey(), ex); > > > Certainly, this is much better than crashing the system, and now it's > merely reduced to a stack trace in the logs. > > From what I read in the ticket, class JmxRuntimeInputArgumentsLookup is > not labeled as a JMX-dependent by the framework, so setting property > "log4j2.disable.jmx" > doesn't help to get rid of the exception in the status logs. > > Will this be fixed in a future release? > > Another question for the interim (from a user perspective) - > Is it possible to configure a filter on the StatusLogger, to silence that > particular event? > > > Kind Regards, > > - Paul K. > Universe Projects Inc. > >
