I've had experiences where the ClassLoader used in the ServletContextListener 
isn't the same as the ClassLoader the application uses.  If that is the case 
then the behavior you are seeing will occur.  Unfortunately, this seems to vary 
from one container to another.

Ralph

On Aug 19, 2013, at 1:07 PM, David Nault wrote:

> Thanks Ralph. I've filed LOG4J2-364 and attached a draft of the WebLookup 
> plugin for you to evaluate.
> 
> I wonder why BaseConfiguration doesn't use the PluginManager when building 
> its initial set of Lookups?  I was expecting that to work in conjunction with 
> a call to PluginManager.addPackage(String) prior to Log4J initialization.
> 
> Thanks,
> David
> 
> 
> On Aug 16, 2013, at 5:33 PM, Ralph Goers <[email protected]> wrote:
> 
>> The BaseConfiguration has an initial set of Lookups that are hardwired so 
>> that some variable substitution is possible on the attributes on the 
>> Configuration element. Until the packages attribute is handled custom 
>> lookups won't be found. Your custom Lookups should work for other elements 
>> in the configuration.  I'd like to see your Lookup to see if it could be 
>> included as one of the hard-wired plugins.
>> 
>> Ralph
>> 
>> On Aug 16, 2013, at 3:21 PM, David Nault wrote:
>> 
>>> Hi All,
>>> 
>>> We're using Log4j in a webapp and are looking at migrating to Log4j 2.
>>> 
>>> We'd like to continue writing our log files to a location under the 
>>> webapp's context root -- that is, under the directory returned by 
>>> ServletContext.getRealPath("/"). This works very well in our QA environment 
>>> where multiple versions of the webapp are deployed to a single Tomcat 
>>> server.
>>> 
>>> I've written a Lookup plugin that maps "${web:rootDir}" to the desired 
>>> path. The problem is that the plugin is ignored when parsing the config 
>>> file, specifically the "filename" attribute of a "File" appender. The 
>>> BaseConfiguration object seems to be using a StrSubstitutor with a default 
>>> Interpolator that only knows about the "sys" and "env" prefixes.
>>> 
>>> For what it's worth, the custom Lookup plugin works fine when used in a 
>>> pattern layout string.
>>> 
>>> Any thoughts on how to get the BaseConfiguration to use a custom Lookup 
>>> plugin, or alternate ways to get the log files to appear under the webapp 
>>> root? System properties aren't the solution since they are shared between 
>>> webapps and we'd rather not return to the bad old days of using a different 
>>> property for each webapp.
>>> 
>>> Log4j 2 beta 8.
>>> 
>>> Thanks,
>>> David
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to