Announcement Announcement Module
No announcement yet.
Cannot see entire exception stack on OC4J Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Cannot see entire exception stack on OC4J


    My team is developing a Spring 2.0.4+AOP (not AspectJ) + Hibernate + Facelets application on OC4J 10g with eclipse 3.3, and when an exception is thrown, the root cause is not included in the exception stack in the console and log file (the exception stack contains AOP stuff that has nothing to do with the real exception). Even when we set the OC4J log setting to the highest level (finest) the root exception is not written to the log file. If we remove the AOP usage or use Tomcat 5.5 the root exception is shown properly.
    Can anyone explain this behaviour and offer a solution please?
    As a workaround we wrote an interceptor that catches all the exceptions that occur in our beans and displays them (in development) or writes them to a log file (in production) and so far it seems to work fine. Do you think it is a trustworthy solution?