| Author |
why we go from bottom to top while debugging a log file messages
|
Mathew Lee
Ranch Hand
Joined: Jun 08, 2009
Posts: 238
|
|
hi,
I am debugging some erros within in websphere 6.0 server within the error log files.
I came to know for debugging error say following error
l need to go from bottom to top to understand the flow, issue like
class ServicesAuthBean calling ...BaseBean calling....SecureDelegate calling....ServiceImpl
I though it other way like
class ServiceImpl calling ...SecureDelegate calling...BaseBean calling...ServicesAuthBean
Please clarify how to debug and how to understand thousands of lines of log files
I am bit new to debugging world.
Any ideas, suggestions, ideas, links highly appreciated. Thanks in advance.
|
 |
Balu Sadhasivam
Ranch Hand
Joined: Jan 01, 2009
Posts: 874
|
|
Its actually a combination of both. First go to bottom and search updwards for error and the once you found walk downwards to find the application logic flow.
Well what if your log is weeks old , bottom logs shows up the latest log. I usually prefer opening log in a window and mark the cursor , and test the scenario in another window and watch the logs flow. First Grep (find) for "Error" , "Exception" to make sure there is nothing serious to look for.
Then grab a line where you could relate and walk downwards from there.
(but Unix is cool , Shift f and you are there)
|
 |
Campbell Ritchie
Sheriff
Joined: Oct 13, 2005
Posts: 32714
|
|
|
Too difficult for "beginning Java". Moving.
|
 |
 |
|
|
subject: why we go from bottom to top while debugging a log file messages
|
|
|