You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2016/07/11 07:27:11 UTC
[jira] [Updated] (LOG4J2-1199) Document that JVM Input Arguments
Lookup (JMX) is not available on Google App Engine. (was:
"log4j2.disable.jmx" property is not aware of class
JmxRuntimeInputArgumentsLookup)
[ https://issues.apache.org/jira/browse/LOG4J2-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Remko Popma updated LOG4J2-1199:
--------------------------------
Fix Version/s: 2.7
Component/s: Documentation
Issue Type: Documentation (was: Bug)
Summary: Document that JVM Input Arguments Lookup (JMX) is not available on Google App Engine. (was: "log4j2.disable.jmx" property is not aware of class JmxRuntimeInputArgumentsLookup) (was: "log4j2.disable.jmx" property is not aware of class JmxRuntimeInputArgumentsLookup)
Currently the docs for this lookup (https://logging.apache.org/log4j/2.x/manual/lookups.html#JmxRuntimeInputArgumentsLookup) only mention that
{quote}
Java's JMX module is not available on Android.
{quote}
Perhaps the best way to address this issue is to add a similar note for Google App Engine.
> Document that JVM Input Arguments Lookup (JMX) is not available on Google App Engine. (was: "log4j2.disable.jmx" property is not aware of class JmxRuntimeInputArgumentsLookup)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-1199
> URL: https://issues.apache.org/jira/browse/LOG4J2-1199
> Project: Log4j 2
> Issue Type: Documentation
> Components: Documentation, JMX
> Affects Versions: 2.4.1
> Environment: Google App Engine
> Reporter: Paul Korepanov
> Priority: Minor
> Fix For: 2.7
>
>
> This affects platforms where JMX is not available, such as Google App Engine
> A JMX-related exception is logged at initialization:
> 2015-11-17 08:29:04,292 pool-2-thread-1 ERROR Unable to create Lookup for jvmrunargs java.lang.IllegalArgumentException: java.lang.NoClassDefFoundError: Could not initialize class org.apache.logging.log4j.core.lookup.JmxRuntimeInputArgumentsLookup
> at org.apache.logging.log4j.core.util.ReflectionUtil.instantiate(ReflectionUtil.java:192)
> at org.apache.logging.log4j.core.lookup.Interpolator.<init>(Interpolator.java:65)
> at org.apache.logging.log4j.core.config.AbstractConfiguration.doConfigure(AbstractConfiguration.java:377)
> at org.apache.logging.log4j.core.config.AbstractConfiguration.initialize(AbstractConfiguration.java:169)
> at org.apache.logging.log4j.core.config.builder.impl.DefaultConfigurationBuilder.build(DefaultConfigurationBuilder.java:158)
> at org.apache.logging.log4j.core.config.builder.impl.DefaultConfigurationBuilder.build(DefaultConfigurationBuilder.java:43)
> ...
> ...
> See bug LOG4J2-1051, in which an app crash issue was addressed by not letting the NoClassDefFoundError propagate, but instead it's wrapped in an IllegalArgumentException and logged to the status logger.
> As already mentioned in the ticket above, configuration property "log4j2.disable.jmx" is not aware of class JmxRuntimeInputArgumentsLookup, so setting "-Dlog4j2.disable.jmx=true" has no effect in preventing the exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org