#11 Stack overflow FunctionCallException

closed
nobody
None
5
2004-09-15
2003-02-03
Anonymous
No

Hello,

we get a stack over flow in FunctionCallException.printStackTrace( PrintStream s )

at java.lang.Throwable.printStackTrace(Throwable.java:451)
at org.jaxen.FunctionCallException.printStackTrace(FunctionCallException.java:96)
at java.lang.Throwable.printStackTrace(Throwable.java:451)
at org.jaxen.FunctionCallException.printStackTrace(FunctionCallException.java:96)
at java.lang.Throwable.printStackTrace(Throwable.java:451)

Ok, our function shouldn't throw an exception. But to fix our bug, it would be nice to see the original
exception. Since Tomcat calls up printStackTrace with an PrintStream there is no easy workaround.

By the Way, thank you for the great jasper package!

Discussion

  • Nobody/Anonymous

    Logged In: NO

    I've seen this one too - the cause is an error in FunctionCallException.

    printStackTrace(PrintStream s) calls super.printStream()
    printStackTrace(PrintWriter w) calls super.printStream()

    ... when both should call their overriden method:
    printStackTrace(PrintStream s) should call super.printStream(s)
    printStackTrace(PrintWriter w) should call super.printStream(w)

    you can reproduce this fault by using the jdom or dom4j navigators to
    call getDocument(uri) for some unreachable uri. (eg go offline!)

     
  • Bazza

    Bazza - 2004-09-15
    • status: open --> closed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks