• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Devaka Cooray
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
  • Tim Holloway
Bartenders:
  • Martijn Verburg
  • Frits Walraven
  • Himai Minh

why we go from bottom to top while debugging a log file messages

 
Ranch Hand
Posts: 238
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.





 
Ranch Hand
Posts: 874
Android VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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)
 
Marshal
Posts: 76885
366
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Too difficult for "beginning Java". Moving.
 
Every snowflake is perfect and unique. And every snowflake contains a very tiny ad.
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic