Re: Too few fatal log ststements
Dear Team, I have one query. There are different logging levels in tomcat. Does it matters alot to use right log level? I mean as a researcher I am exploring in which scenarios one should be extremely careful to use right log level. Can anyone of please throw more light on this topic. Thank You On Tue, Aug 12, 2014 at 9:04 AM, sangeeta lal sangeeta.6...@gmail.com wrote: Thanks! All of you :) Now I have much more understanding about tomcat logging. Thanks a lot! On Mon, Aug 11, 2014 at 7:26 PM, Christopher Schultz ch...@christopherschultz.net wrote: Sangeeta, On 8/11/14, 5:41 AM, sangeeta lal wrote: Actually I have data for other log levels also. Debug =600 statements, error=400 statements, trace =90 statements etc. I would usually expect in a typical project that there would be more TRACE logging statements than anything else. On the other hand, DEBUG tends to be the default log level used by most developers that I observe. There are likely many DEBUG statements in Tomcat's code that perhaps should be TRACE statements. 400 ERROR versus 600 DEBUG seems like an awfully large number of ERROR statements, but that may simply be evidence that most errors are properly-logged while there is less DEBUG logging than average. I am just curious, what could be the possible reason for having such few fatal statements. Can you give your opinion about this? There aren't too many things that ate truly /fatal/ to Tomcat. If we can read config files, mostly everything is okay. One might consider that failing to bind to a port is a fatal error, but Tomcat can start up successfully even if no connectors can start properly. This is because connectors can be configured on the fly, etc. and, in embedded contexts, the state of the container can change from within and therefore zero live connectors is no cause for alarm. Most errors don't take-down the container/JVM, so they aren't considered fatal. I wouldn't expect to see very many FATAL log messages in any product, really: the truly fatal things happen at the JVM level and would end up emitting a message to stdout and possibly bringing-down the JVM entirely (e.g. segmentation fault). If you have some /suggestions/ for what conditions might be fatal, we might be able to comment on those specifically. But, we aren't going to re-evaluate every component in Tomcat for logging to satisfy your academic curiosity about logging practices in the Tomcat source. -chris -- Regards... Sangeeta Assistant Professor CSE Department @JIIT Noida -- Regards... Sangeeta Assistant Professor CSE Department @JIIT Noida
Too few fatal log ststements
Hello Team, I am sangeeta PhD scholar and Researcher working in the are of mining software repositories. Currently I am working on the *tomcat *platform. I am parsing the code of tomcat (version 8) and I discovered that there are only *10-11 log.fatal statement.* I am just curious, is it normal? and why is it so? Why there so few*log.fatal *statements? Thanks! -- Regards... Sangeeta Assistant Professor CSE Department @JIIT Noida
Re: Too few fatal log ststements
On 11/08/2014 09:14, sangeeta lal wrote: Hello Team, I am sangeeta PhD scholar and Researcher working in the are of mining software repositories. Currently I am working on the *tomcat *platform. I am parsing the code of tomcat (version 8) and I discovered that there are only *10-11 log.fatal statement.* I am just curious, is it normal? That depends on your definition of normal. and why is it so? Because that this how the Tomcat developers wrote the code. Why there so few*log.fatal *statements? That questions assumes that Tomcat has fewer than the normal number of fatal log statements. As per my comment above, that depends on how normal is defined. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Too few fatal log ststements
Hi Mark, Actually I have data for other log levels also. Debug =600 statements, error=400 statements, trace =90 statements etc. I am just curious, what could be the possible reason for having such few fatal statements. Can you give your opinion about this? Thanks! for reply. On Mon, Aug 11, 2014 at 3:06 PM, Mark Thomas ma...@apache.org wrote: On 11/08/2014 09:14, sangeeta lal wrote: Hello Team, I am sangeeta PhD scholar and Researcher working in the are of mining software repositories. Currently I am working on the *tomcat *platform. I am parsing the code of tomcat (version 8) and I discovered that there are only *10-11 log.fatal statement.* I am just curious, is it normal? That depends on your definition of normal. and why is it so? Because that this how the Tomcat developers wrote the code. Why there so few*log.fatal *statements? That questions assumes that Tomcat has fewer than the normal number of fatal log statements. As per my comment above, that depends on how normal is defined. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org -- Regards... Sangeeta Assistant Professor CSE Department @JIIT Noida
Re: Too few fatal log ststements
maybe tomcat is just so robust, that nothing is fatal to it ;-) Leon On Mon, Aug 11, 2014 at 11:41 AM, sangeeta lal sangeeta.6...@gmail.com wrote: Hi Mark, Actually I have data for other log levels also. Debug =600 statements, error=400 statements, trace =90 statements etc. I am just curious, what could be the possible reason for having such few fatal statements. Can you give your opinion about this? Thanks! for reply. On Mon, Aug 11, 2014 at 3:06 PM, Mark Thomas ma...@apache.org wrote: On 11/08/2014 09:14, sangeeta lal wrote: Hello Team, I am sangeeta PhD scholar and Researcher working in the are of mining software repositories. Currently I am working on the *tomcat *platform. I am parsing the code of tomcat (version 8) and I discovered that there are only *10-11 log.fatal statement.* I am just curious, is it normal? That depends on your definition of normal. and why is it so? Because that this how the Tomcat developers wrote the code. Why there so few*log.fatal *statements? That questions assumes that Tomcat has fewer than the normal number of fatal log statements. As per my comment above, that depends on how normal is defined. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org -- Regards... Sangeeta Assistant Professor CSE Department @JIIT Noida
Re: Too few fatal log ststements
Okay! This means its because of requirement specification of Tomcat. On Mon, Aug 11, 2014 at 3:15 PM, Leon Rosenberg rosenberg.l...@gmail.com wrote: maybe tomcat is just so robust, that nothing is fatal to it ;-) Leon On Mon, Aug 11, 2014 at 11:41 AM, sangeeta lal sangeeta.6...@gmail.com wrote: Hi Mark, Actually I have data for other log levels also. Debug =600 statements, error=400 statements, trace =90 statements etc. I am just curious, what could be the possible reason for having such few fatal statements. Can you give your opinion about this? Thanks! for reply. On Mon, Aug 11, 2014 at 3:06 PM, Mark Thomas ma...@apache.org wrote: On 11/08/2014 09:14, sangeeta lal wrote: Hello Team, I am sangeeta PhD scholar and Researcher working in the are of mining software repositories. Currently I am working on the *tomcat *platform. I am parsing the code of tomcat (version 8) and I discovered that there are only *10-11 log.fatal statement.* I am just curious, is it normal? That depends on your definition of normal. and why is it so? Because that this how the Tomcat developers wrote the code. Why there so few*log.fatal *statements? That questions assumes that Tomcat has fewer than the normal number of fatal log statements. As per my comment above, that depends on how normal is defined. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org -- Regards... Sangeeta Assistant Professor CSE Department @JIIT Noida -- Regards... Sangeeta Assistant Professor CSE Department @JIIT Noida
Re: Too few fatal log ststements
Hi, On Mon, Aug 11, 2014 at 11:45 AM, Leon Rosenberg rosenberg.l...@gmail.com wrote: maybe tomcat is just so robust, that nothing is fatal to it ;-) Leon On Mon, Aug 11, 2014 at 11:41 AM, sangeeta lal sangeeta.6...@gmail.com wrote: Hi Mark, Actually I have data for other log levels also. Debug =600 statements, error=400 statements, trace =90 statements etc. I am just curious, what could be the possible reason for having such few fatal statements. Can you give your opinion about this? It seems you don't know what is the purpose of the log messages. Fatal log level is used to indicate that there is a such a problem that Tomcat cannot even start, e.g. some configuration issue. Error level is used to indicate that there is a serious problem but Tomcat can still work, e.g. some request failed somehow and all its resources will be released, but Tomcat will continue serving more requests. Debug and Trace log levels are used for debugging. Usually they are not enabled. Thanks! for reply. On Mon, Aug 11, 2014 at 3:06 PM, Mark Thomas ma...@apache.org wrote: On 11/08/2014 09:14, sangeeta lal wrote: Hello Team, I am sangeeta PhD scholar and Researcher working in the are of mining software repositories. Currently I am working on the *tomcat *platform. I am parsing the code of tomcat (version 8) and I discovered that there are only *10-11 log.fatal statement.* I am just curious, is it normal? That depends on your definition of normal. and why is it so? Because that this how the Tomcat developers wrote the code. Why there so few*log.fatal *statements? That questions assumes that Tomcat has fewer than the normal number of fatal log statements. As per my comment above, that depends on how normal is defined. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org -- Regards... Sangeeta Assistant Professor CSE Department @JIIT Noida
Re: Too few fatal log ststements
On 11/08/2014 10:41, sangeeta lal wrote: Hi Mark, Actually I have data for other log levels also. Debug =600 statements, error=400 statements, trace =90 statements etc. I am just curious, what could be the possible reason for having such few fatal statements. Can you give your opinion about this? You seem to be missing the point. Your claim that there are too few fatal statements is based on an assumption that there is a correct number of fatal statements. You have not provided any basis for your assumption of the correct number of log statements therefore it is impossible for anyone to explain why Tomcat has a different number. Mark Thanks! for reply. On Mon, Aug 11, 2014 at 3:06 PM, Mark Thomas ma...@apache.org wrote: On 11/08/2014 09:14, sangeeta lal wrote: Hello Team, I am sangeeta PhD scholar and Researcher working in the are of mining software repositories. Currently I am working on the *tomcat *platform. I am parsing the code of tomcat (version 8) and I discovered that there are only *10-11 log.fatal statement.* I am just curious, is it normal? That depends on your definition of normal. and why is it so? Because that this how the Tomcat developers wrote the code. Why there so few*log.fatal *statements? That questions assumes that Tomcat has fewer than the normal number of fatal log statements. As per my comment above, that depends on how normal is defined. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Too few fatal log ststements
Sangeeta, On 8/11/14, 5:41 AM, sangeeta lal wrote: Actually I have data for other log levels also. Debug =600 statements, error=400 statements, trace =90 statements etc. I would usually expect in a typical project that there would be more TRACE logging statements than anything else. On the other hand, DEBUG tends to be the default log level used by most developers that I observe. There are likely many DEBUG statements in Tomcat's code that perhaps should be TRACE statements. 400 ERROR versus 600 DEBUG seems like an awfully large number of ERROR statements, but that may simply be evidence that most errors are properly-logged while there is less DEBUG logging than average. I am just curious, what could be the possible reason for having such few fatal statements. Can you give your opinion about this? There aren't too many things that ate truly /fatal/ to Tomcat. If we can read config files, mostly everything is okay. One might consider that failing to bind to a port is a fatal error, but Tomcat can start up successfully even if no connectors can start properly. This is because connectors can be configured on the fly, etc. and, in embedded contexts, the state of the container can change from within and therefore zero live connectors is no cause for alarm. Most errors don't take-down the container/JVM, so they aren't considered fatal. I wouldn't expect to see very many FATAL log messages in any product, really: the truly fatal things happen at the JVM level and would end up emitting a message to stdout and possibly bringing-down the JVM entirely (e.g. segmentation fault). If you have some /suggestions/ for what conditions might be fatal, we might be able to comment on those specifically. But, we aren't going to re-evaluate every component in Tomcat for logging to satisfy your academic curiosity about logging practices in the Tomcat source. -chris signature.asc Description: OpenPGP digital signature
Re: Too few fatal log ststements
Thanks! All of you :) Now I have much more understanding about tomcat logging. Thanks a lot! On Mon, Aug 11, 2014 at 7:26 PM, Christopher Schultz ch...@christopherschultz.net wrote: Sangeeta, On 8/11/14, 5:41 AM, sangeeta lal wrote: Actually I have data for other log levels also. Debug =600 statements, error=400 statements, trace =90 statements etc. I would usually expect in a typical project that there would be more TRACE logging statements than anything else. On the other hand, DEBUG tends to be the default log level used by most developers that I observe. There are likely many DEBUG statements in Tomcat's code that perhaps should be TRACE statements. 400 ERROR versus 600 DEBUG seems like an awfully large number of ERROR statements, but that may simply be evidence that most errors are properly-logged while there is less DEBUG logging than average. I am just curious, what could be the possible reason for having such few fatal statements. Can you give your opinion about this? There aren't too many things that ate truly /fatal/ to Tomcat. If we can read config files, mostly everything is okay. One might consider that failing to bind to a port is a fatal error, but Tomcat can start up successfully even if no connectors can start properly. This is because connectors can be configured on the fly, etc. and, in embedded contexts, the state of the container can change from within and therefore zero live connectors is no cause for alarm. Most errors don't take-down the container/JVM, so they aren't considered fatal. I wouldn't expect to see very many FATAL log messages in any product, really: the truly fatal things happen at the JVM level and would end up emitting a message to stdout and possibly bringing-down the JVM entirely (e.g. segmentation fault). If you have some /suggestions/ for what conditions might be fatal, we might be able to comment on those specifically. But, we aren't going to re-evaluate every component in Tomcat for logging to satisfy your academic curiosity about logging practices in the Tomcat source. -chris -- Regards... Sangeeta Assistant Professor CSE Department @JIIT Noida
