logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leon Finker"<leon...@gmail.com>
Subject Re: 2.6.3-SNAPSHOT java.lang.NoSuchMethodError
Date Thu, 08 Sep 2016 17:55:23 GMT
It's this commit facb281ba2f5f83903a7aedf385f83d7f9520561
* Remove internal method that is @deprecated Use {@link
#createLogger(boolean, Level, String, String, AppenderRef[], Property[],
Configuration, Filter)}

But it was public, not internal. In any case I wouldn't care if major 3rd party library didn't
make use of it. And there is no way to change that. If it was under our control, we would
update our source to new api.



On 2016-09-08 13:49 (-0400), Ralph Goers <ralph.goers@dslextreme.com> wrote: 
> Thanks for pointing this out. There is currently a discussion on the dev list about what
we want to remain backward compatible in Log4j core. AppenderRef is certainly one of the things
that should be.
> 
> Ralph
> 
> > On Sep 8, 2016, at 10:40 AM, Leon Finker <leonfin@gmail.com> wrote:
> > 
> > Hi,
> > 
> > We are using 3rd part library that depends on log4j2 2.3 API. While testing latest
log4j2 master, our process fails to start. Unless this API is compatible there is no way to
upgrade to log4j2 2.7. Can this be fixed?
> > 
> > [2016-09-08 17:16:54,153Z][FATAL][main:0xf][...]
> > java.lang.NoSuchMethodError: org.apache.logging.log4j.core.config.LoggerConfig.createLogger(Ljava/lang/String;Lorg/apache/logging/log4j/Level;Ljava/lang/String;Ljava/lang/String;[Lorg/apache/logging/log4j/core/config/AppenderRef;[Lorg/apache/logging/log4j/core/config/Property;Lorg/apache/logging/log4j/core/config/Configuration;Lorg/apache/logging/log4j/core/Filter;)Lorg/apache/logging/log4j/core/config/LoggerConfig;
> > 	at com.gemstone.gemfire.internal.logging.log4j.Configurator.getOrCreateLoggerConfig(Configurator.java:82)
~[gemfire-8.2.0.13.jar:?]
> > 	at com.gemstone.gemfire.internal.logging.LogService.configureLoggers(LogService.java:98)
~[gemfire-8.2.0.13.jar:?]
> > 	at com.gemstone.gemfire.internal.logging.LogService.init(LogService.java:85) ~[gemfire-8.2.0.13.jar:?]
> > 	at com.gemstone.gemfire.internal.logging.LogService.<clinit>(LogService.java:76)
~[gemfire-8.2.0.13.jar:?]
> > 	at com.gemstone.gemfire.distributed.internal.DistributionManager.<clinit>(DistributionManager.java:133)
~[gemfire-8.2.0.13.jar:?]
> > 	at com.gemstone.gemfire.distributed.DistributedSystem.connect(DistributedSystem.java:1610)
~[gemfire-8.2.0.13.jar:?]
> > 
> > Also noticed that you changed XmlConfiguration ctor and require LoggerContext. That's
ok since we can change that part. Looks a bit silly:
> > loggerContext.start(new XmlConfiguration(loggerContext, configSource));
> > unless absolutely required, probably not good idea to change the public XmlConfiguration
ctor.
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> > 
> > 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message