Re: ASYNC Appender not printing line or class information
thanks for sharing your solution with us. I noticed that phenomena too, but it was only in the level of curiosity, as I am not really need that info in the log files. Now I know why and how to overcome it. Cheers, Avner - Original Message - From: "Terence Ingram" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 17, 2003 2:59 AM Subject: Re: ASYNC Appender not printing line or class information > Solved my own problem. Helps when you get access to decent document in the > form of Ceci's book :) Would like to make a friendly suggestion for the > basic documentation to be extended. But regardless for those out there who > don't plan to buy the book. > > There are 3 params you can enter for the ASYNC appender: > *BufferSize - which defaults to 128 messages > *LocationInfo - boolean deafults to false > *Threshold - no idea what this does > > So insert the LocatioInfo param tag i.e. > > > > > > > > > I added the BufferSize for fun. Pretty easy when you find the documentation. > Refer to the javadoc on the AsyncAppender which shows the methods for the > setLocationInfo and setBufferSize: > http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/AsyncAppender.html > > Terence > > - Original Message - > From: "Terence Ingram" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, June 17, 2003 10:33 AM > Subject: ASYNC Appender not printing line or class information > > > > I have searched the archives for a resolution to this problem and the only > > reference is: > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg06540.html > > which does not appear to have a resolution. > > > > My problem. I have upgraded to log4j 1.2.8 I am using the Async appender > and > > then sending all messages to STDOUT and a file. Below is an example of my > > log4j.xml file. The interesting point is that the information for switches > > %L, %F, %M all produce the deadly or rather infamous "?"". > > > > I have read the documentation stating that potentially I need to ensure > that > > my compiled code does not use the -O option. Fine. It doesn't. I tried > > another test by not using the ASYNC Appender i.e. just pumping the output > to > > the CONSOLE. The information for the offending switches is then returned. > > > > This has the same behaviour on windows and linux. > > > > My question is: What's the deal the this ASYNC appender. How can this be > > remedied? > > > > Terence > > > > > > http://jakarta.apache.org/log4j/"; > > debug="true"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - > 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]
Re: ASYNC Appender not printing line or class information
Cheers Paul. - Original Message - From: "Paul Smith" <[EMAIL PROTECTED]> To: "'Log4J Users List'" <[EMAIL PROTECTED]> Sent: Tuesday, June 17, 2003 11:11 AM Subject: RE: ASYNC Appender not printing line or class information > > *Threshold - no idea what this does > > Just like you can set the threshold for the hierarchy, and > loggers/categories to restrict events going any further down if it is not > that level or Higher, you can do the same thing for any appender (that > extend from AppenderSkeleton). This is VERY handy for attaching separate > appenders to the same logger. You have INFO level logs for a Logger going > to a file, but ERROR only going via SMTP to someone. > > Ceki's book is excellent, I think everyone should have it in their toolbelt. > > cheers, > > Paul Smith > > - > 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]
RE: ASYNC Appender not printing line or class information
> *Threshold - no idea what this does Just like you can set the threshold for the hierarchy, and loggers/categories to restrict events going any further down if it is not that level or Higher, you can do the same thing for any appender (that extend from AppenderSkeleton). This is VERY handy for attaching separate appenders to the same logger. You have INFO level logs for a Logger going to a file, but ERROR only going via SMTP to someone. Ceki's book is excellent, I think everyone should have it in their toolbelt. cheers, Paul Smith - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ASYNC Appender not printing line or class information
Solved my own problem. Helps when you get access to decent document in the form of Ceci's book :) Would like to make a friendly suggestion for the basic documentation to be extended. But regardless for those out there who don't plan to buy the book. There are 3 params you can enter for the ASYNC appender: *BufferSize - which defaults to 128 messages *LocationInfo - boolean deafults to false *Threshold - no idea what this does So insert the LocatioInfo param tag i.e. I added the BufferSize for fun. Pretty easy when you find the documentation. Refer to the javadoc on the AsyncAppender which shows the methods for the setLocationInfo and setBufferSize: http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/AsyncAppender.html Terence - Original Message - From: "Terence Ingram" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 17, 2003 10:33 AM Subject: ASYNC Appender not printing line or class information > I have searched the archives for a resolution to this problem and the only > reference is: > http://www.mail-archive.com/[EMAIL PROTECTED]/msg06540.html > which does not appear to have a resolution. > > My problem. I have upgraded to log4j 1.2.8 I am using the Async appender and > then sending all messages to STDOUT and a file. Below is an example of my > log4j.xml file. The interesting point is that the information for switches > %L, %F, %M all produce the deadly or rather infamous "?"". > > I have read the documentation stating that potentially I need to ensure that > my compiled code does not use the -O option. Fine. It doesn't. I tried > another test by not using the ASYNC Appender i.e. just pumping the output to > the CONSOLE. The information for the offending switches is then returned. > > This has the same behaviour on windows and linux. > > My question is: What's the deal the this ASYNC appender. How can this be > remedied? > > Terence > > > http://jakarta.apache.org/log4j/"; > debug="true"> > > > > > > > > > > > > > > > > > > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
