Fwd: Re: Log file named ${sys

On 8/26/2013 7:48 PM, Remko Popma wrote: Looks like a string substitution issue in the FastFile appender (renamed to RandomAccessFile appender in the next release, btw, so you'll need to change your config when you upgrade). Why would that behave differently on one server vs another? > Can

Re: Log file named ${sys

Looks like a string substitution issue in the FastFile appender (renamed to RandomAccessFile appender in the next release, btw, so you'll need to change your config when you upgrade). Can you file a JIRA ticket for this? Thanks, Remko On Tuesday, August 27, 2013, Eric Schwarzenbach wrote: > I'm

Log file named ${sys

I'm using log4j 2.0-beta8 in a webapp, and running it under Tomcat. I'm setting a system property in my apps ServletContextListener, and using that system property in my log4j2.xml file, like so: fileName="${sys:catalina.home}/logs/${sys:application-name}.log"> On my Windows machine, a log f

Re: javadoc

This has been fixed. When the next version of Log4j releases and the site updates, there will be prominent Javadoc/API documentation links directly at the top of the left-hand menu. Nick On Aug 26, 2013, at 4:18 PM, Eric Schwarzenbach wrote: > I find myself unable to find the log4j2 javadoc. I

javadoc

I find myself unable to find the log4j2 javadoc. I'd swear I found it once before... Googling, I find some discussion of this as a desired change to the site, but that thread is a few months old, so I'm not sure if it has been resolved since then. I do find this page: http://logging.apache.or

Re: Log4jContextFactory does not implement LoggerContextFactory

printing the ClassLoaders gives me following output: interface org.apache.logging.log4j.spi.LoggerContextFactory is loaded by sun.misc.Launcher$AppClassLoader@35a16869 org.apache.logging.log4j.spi.LoggerContextFactory loaded by org.apache.logging.log4j-api We have two different ClassLoaders. T

Re: Log4jContextFactory does not implement LoggerContextFactory

After reducing the bundle composite I can say that this issue only affacts the log4j2-api and the log4j2-core, nothing else. I conclude that this could be a ClassLoader-issue. I think that the log4j2-api uses the bundle-classloader whereas the implementation is created by the bootstrap-classloader

Re: Log4jContextFactory does not implement LoggerContextFactory

g! inspect req * 13 org.apache.logging.log4j-1.2-api [13] requires: --- ... osgi.wiring.package; (osgi.wiring.package=org.apache.logging.log4j) resolved by: osgi.wiring.package; org.apache.logging.log4j 2.0.0.beta9-SNAPSHOT from org.apache.logging.log4

Re: Log4jContextFactory does not implement LoggerContextFactory

Roland wrote > ... > The bundle which uses log4j2-API imports a different LoggerContextFactory > than the core(?) does. > > org.apache.logging.log4j-api [14] provides: > ... > osgi.wiring.package; * > org.apache.logging.log4j.core.impl * > 2.0.0.beta9-SNAPSHOT [UNUSED] > ... > org.apache.logging

Log4jContextFactory does not implement LoggerContextFactory

Hi, what does this error msg. mean? ERROR StatusLogger org.apache.logging.log4j.core.impl.Log4jContextFactory does not implement org.apache.logging.log4j.spi.LoggerContextFactory In an OSGi-environment the container decides which package is imported if there is more than one package of the same v

Re: Discussion about correct inicialization of log4j2 in OSGi context.

hi, today I checked my poms. My mistake was that I didn't specified the dependency on the core. However, the core library was in the same folder as the API, according to the manual. So, if log4j2 is used in an OSGi-environment, you have to specify the dependencies on the core and on the api in the