Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.6.2
-
None
Description
See http://stackoverflow.com/q/39160265/1446916
no need for the stacktrace:
Exception occuring at beginning of server start: 2016-08-26 02:19:15,172 [ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)' ERROR Could not unregister MBeans for org.apache.logging.log4j2:type=AsyncContext@694ae32f, component=AsyncLoggerRingBuffer javax.management.InstanceNotFoundException: org.apache.logging.log4j2:type=AsyncContext@694ae32f, component=AsyncLoggerRingBuffer at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1095) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:427) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:415) at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:546) at org.apache.logging.log4j.core.jmx.Server.unregisterAllMatching(Server.java:335) at org.apache.logging.log4j.core.jmx.Server.unregisterAsyncLoggerRingBufferAdmins(Server.java:316) at org.apache.logging.log4j.core.jmx.Server.unregisterLoggerContext(Server.java:258) at org.apache.logging.log4j.core.jmx.Server.reregisterMBeansAfterReconfigure(Server.java:162) at org.apache.logging.log4j.core.jmx.Server.reregisterMBeansAfterReconfigure(Server.java:138) at org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:502) at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:561) at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:577) at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:212) at org.apache.logging.log4j.core.async.AsyncLoggerContext.start(AsyncLoggerContext.java:75) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:152) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45) at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194) at org.apache.logging.log4j.LogManager.getLogger(LogManager.java:551) at com.company.tns.netmessage.bean.NetMessageListener.<clinit>(NetMessageListener.java:55) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
This ticket previously also reported another unnecessary stacktrace, but this was resolved in LOG4J2-1582:
See http://stackoverflow.com/questions/39457075/jmx-runtime-input-lookup-class-is-not-available-because-this-jre-does-not-suppor
This warning does not need to print the full stacktrace:
2016-09-12 12:01:26,124 main WARN JMX runtime input lookup class is not available because this JRE does not support JMX. JMX lookups will not be available, continuing configuration. java.lang.ClassCastException: Cannot cast org.apache.logging.log4j.core.lookup.JmxRuntimeInputArgumentsLookup to org.apache.logging.log4j.core.lookup.StrLookup at java.lang.Class.cast(Unknown Source) at org.apache.logging.log4j.util.LoaderUtil.newCheckedInstanceOf(LoaderUtil.java:168) at org.apache.logging.log4j.core.util.Loader.newCheckedInstanceOf(Loader.java:301) at org.apache.logging.log4j.core.lookup.Interpolator.<init>(Interpolator.java:106) at org.apache.logging.log4j.core.config.AbstractConfiguration.<init>(AbstractConfiguration.java:116) at org.apache.logging.log4j.core.config.DefaultConfiguration.<init>(DefaultConfiguration.java:46) at org.apache.logging.log4j.core.layout.PatternLayout$Builder.build(PatternLayout.java:492) at org.apache.logging.log4j.core.layout.PatternLayout.createDefaultLayout(PatternLayout.java:376) ...