Home/ Questions/Q 66319
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T19:05:05+00:00

I have been trying to parse Java exceptions that appear in a log for

  • 0

I have been trying to parse Java exceptions that appear in a log for some code I’m working with. My question is, do you parse the exception trace from the top down, or the bottom up? It looks something like this:

ERROR [main]</b> Nov/04 11:03:19,440 [localhost].[/BookmarksPortlet].[] - Exception sending context... org.springframework.beans.factory.BeanCreationException: Error creating bean...: Cannot Resolve reference...: Error creating bean... nested exception... nested exception is org.hibernate.HibernateException: Dialect class not found: org.hibernate.dialect.Oracle10gDialect Caused by: ... [similar exceptions and nested exceptions] ...     at [start of stack trace]

Something like that. Obviously, I’m not looking for the answer to this specific exception, but how do you go about parsing an exception trace like this? Do you start at the top level error, or do you start at the inner most error (under the ’caused by’ clauses)?

The problem is more difficult for me because I’m not working with code I wrote. I’m editing the XML configurations, so I’m not really even looking the Java code. In my own code, I would recognize locations in the trace and would know what sort of things to look for. So how do you approach an exception like this in general?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. In your particular example, there’s a class missing. As soon as you see an error like that, you know what needs fixing (either correcting the class name, or updating the classpath so that the class can be found).

    In general, though, I look from my code toward the generated code until I find the error. If I get a NullPointerException, for example, I check to see if it’s being caused by one of my classes. If it’s a missing class, though, I won’t find anything wrong with my own classes, so I’ll start at the other end of the stack trace and look for a recognizable error.

    • 0