struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Gainty <mgai...@hotmail.com>
Subject RE: Origin of struts log messages misleading
Date Tue, 21 Jul 2015 12:24:50 GMT
Morning Norbert
ceki gulcu spent years mastering the art of incorporating PatternLayouts and different Appenders
into log4j
Say you have a thread that is spiking CPU or heap when processing a particular algo
algos code is out of reach from IDEs and you want to test it near Prod environment (where
there there are no Ides)
so you want your logging to NOT add more heap requirement and  to NOT add CPU usage
Latest 2.3 log4j release version allows asynchronous logging
imagine having a staggering 2,652,412 log messages processed/sec  (or 1,715,344 log messages
processed/sec windows) within the same thread
why should anyone want to duplicate these features when log4j already fulfills those requirements?

http://logging.apache.org/log4j/2.x/
HTH
Martin

> Subject: Re: Origin of struts log messages misleading
> To: user@struts.apache.org
> From: nharrer@gmx.at
> Date: Tue, 21 Jul 2015 13:00:02 +0200
> 
> Alright. Only need to be patient then :-)
> 
> Thanks.
> 
> On 18.07.2015 19:55, Lukasz Lenart wrote:
> > 2015-07-17 23:57 GMT+02:00 Norbert Harrer <nharrer@gmx.at>:
> >> Hi.
> >>
> >> I noticed, that all log messages from struts look like this:
> >>
> >> Jul 17, 2015 11:31:39 PM com.opensymphony.xwork2.util.logging.jdk.JdkLogger
> >> info
> >> INFO: Parsing configuration file [struts-plugin.xml]
> >> Jul 17, 2015 11:31:39 PM com.opensymphony.xwork2.util.logging.jdk.JdkLogger
> >> info
> >> INFO: Parsing configuration file [struts.xml]
> >> Jul 17, 2015 11:31:39 PM com.opensymphony.xwork2.util.logging.jdk.JdkLogger
> >> info
> >> INFO: Choosing bean (struts) for (com.opensymphony.xwork2.ObjectFactory)
> >>
> >> They are all coming from the logging wrapper
> >> com.opensymphony.xwork2.util.logging.jdk.JdkLogger.
> >>
> >> While this is true, wouldn't it be much more helpful if the log would show
> >> the actual class that made the logger call?
> >> Sometimes it's helpful to examine the source code of struts classes where
> >> log messages come from. But that way it's very hard to find out where the
> >> log message actually originated from.
> > That's why we have deprecated the existing logging layer in XWork and
> > switched to Log4j2 in Struts 2.5
> >
> >
> > Regards
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message