Hi All
I have changed the call stack prints I found to TRACE level, on both
Axis2 and Axiom. I also saw the code creating a RuntimeException just to
dump the stack trace, which could be replaced by
http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Thread.html#dumpStack()
I hope in future,
On Friday 14 November 2008, Asankha C. Perera wrote:
Usually logging frameworks support configuring different levels of
logging at different package levels. While I am +1 for having a clear
separation of TRACE level messages vs DEBUG level messages
Sanjaya
Actually this problem is not
Hi Asankha,
I don't think having callstack printed on debug level is a good thing. Of
course you can set your log level to a higher one, but even at debug level,
printing call stacks might be cumbersome.
So +1 for the suggestion.
With Mettha,
Eran Chinthaka
Hi All
I am seeing loads and loads of the following log message, which dumps
the thread stack whenever a Parameter was added.. This severely clutters
the log files, and makes it difficult to troubleshoot any other problems.
Although this level of debug information would be valuable to nail
Usually logging frameworks support configuring different levels of logging at
different package levels. While I am +1 for having a clear separation of
TRACE level messages vs DEBUG level messages, that type of a configuration
could help reduce too many unrelated log messages in the log when
Usually logging frameworks support configuring different levels of logging at
different package levels. While I am +1 for having a clear separation of
TRACE level messages vs DEBUG level messages
Sanjaya
Actually this problem is not local to parameter manipulation... it
exists in Axiom as
