YAML is also supported!
On 23 July 2014 09:53, Kevin Hale Boyes wrote:
> On 23 July 2014 08:45, Remko Popma wrote:
>
> > The log4j2 xml format is shorter and easier than the log4j-1.2 xml
> format,
> > though. Give it a try...
> >
>
> I didn't realize that. I'd also forgotten that json format
On 23 July 2014 08:45, Remko Popma wrote:
> The log4j2 xml format is shorter and easier than the log4j-1.2 xml format,
> though. Give it a try...
>
I didn't realize that. I'd also forgotten that json formats were supported.
I'll have a look. Thanks!
Kevin, currently log4j2 does not support configuration from a properties
file. Only xml and json formats are supported. I don't think anybody on the
team is jumping to implement a properties configuration, one of the reasons
being that the hierarchical nature of the configuration does not really
ma
Does log4j2 support configuration through property (.lcf) files? I haven't
checked recently but I thought it only supported XML configuration.
Thanks,
Kevin
On 10 July 2014 21:49, Remko Popma wrote:
> Hi,
>
> Is it possible for you to switch to log4j2? All our effort is currently
> focussed on
Hi Jake,
Thank you for the inputs/ advise.
I will look into fixing it with your suggestions.
Dear all,
also thank you for reading my earlier posts and suggestions.
> On 14 Jul, 2014, at 10:39 pm, "Jacob Kjome" wrote:
>
> No. More likely, there some code in your app performing manual config
No. More likely, there some code in your app performing manual configuration.
Jake
On Sun, 13 Jul 2014 16:31:35 +0800
Gerald wrote:
Hi
so in my case, because log4j.properties was not found in my webapps
WEB-INF/classes, the webapp classloader then went to look for the
log4j.properties in
Hi
so in my case, because log4j.properties was not found in my webapps
WEB-INF/classes, the webapp classloader then went to look for the
log4j.properties in my tomcat. this second reloading causes the rolling to
fail.
I see that subsequently the log4j.properties of my webapp (in
WEB-INF/clas
Because Log4j, by default, looks for config files in the default package.
Furthermore, because of Tomcat's child-first classloading behavior, if you
place log4j.properties in the default package of the webapp (WEB-INF/classes)
it won't bother looking in the parent classloader since it will ha
Hi
Could I trouble you to explain further why putting the application
log4j.properties in WEB-INF/classes, as opposed to WEB-INF/classes/properties,
would prevent the webapp classloader from seeing the tomcat's log4j.properties?
Gerald
> On 11 Jul, 2014, at 11:27 pm, "Jacob Kjome" wrote:
>
Why don't you place your webapp's log4j.properties file in WEB-INF/classes
instead of WEB-INF/classes/properties? That way, the webapp classloader won't
ever see the tomcat log4j.properties, thus no rolling file appender conflicts.
Jake
On Fri, 11 Jul 2014 11:16:41 +0800
guowei wrote:
De
Hi,
Is it possible for you to switch to log4j2? All our effort is currently
focussed on log4j2.
Best regards,
Remko
Sent from my iPhone
> On 2014/07/11, at 12:16, guowei wrote:
>
> Dear all,
>
> I am using log4j for tomcat internal logging and also application logging.
>
> I followed Tomc
Dear all,
I am using log4j for tomcat internal logging and also application logging.
I followed Tomcat's instruction to configure log4j rolling and I also have
configured my application to have its own log4j rolling.
log4j.jar is in both Tomcat's lib and web application's lib, each have their
12 matches
Mail list logo
