Longest StackTrace ever on TSS

It seams like TheServerSide.com had a problem but recovered already. It is the longest stack trace I have ever seen in a webpage. It is far too long and I copied it, so you can see it here:
It tells a lot of interesting things about TSS.com. So they use:
Kodo from solarmetric.com

And you can even see the Table structure they have.
Seams like no good errormessage delivered to customers, or?

Posted by Karsten at 07.12.04 22:24 | TrackBack

Nice trace :-)
And you can even see that they use Sun One Application Server, the only application server that doesn't put the vendor name in the package hierarchy !

Posted by: Damien B at 08.12.04 10:35

Stack trace shows

at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Posted by: Hobbes at 21.12.04 15:46

This is why I hate Sun's implementation of nested exceptions ... each exception prints out its rootCause exception's stack trace. At least JDK 1.4 has a way to extract the stack frames for reporting without parsing the output from printStackTrace().

What you saw is what happens when Tapestry can't even render the Exception page to report some other error. A fix will be going up on TSS fairly soon.

Anyway, TSS is WebLogic + Kodo + Coherence + Tapestry + HiveMind on top of PostgreSQL.

Posted by: Howard M. Lewis Ship at 30.12.04 00:22

Hi Howard,
nice to see Tapestry Guru No1 on my blog.
I guess I saw something rarely on TSS.
And thanx for letting everybody know how TSS is implemented. I really like to know what technology is behind what I see.
See u around,

Posted by: Karsten Voges at 30.12.04 13:16
Post a comment

Remember personal info?