Java in Notes/Domino Explained: Stacktraces

Not much information on Java in Notes/Domino per say in this post but simply a pointer to a nice article on reading stack and tread dumps which is a must for all programming in Java.

Remember that as of Java 1.4 (Notes/Domino 7.x) you can use Java classes access the elements of a stacktrace. You can use this to further diagnose the trace and make a more intelligent decision on how to handle it. Look for the StackTraceElement class in the javadocs.

Link to article: Of Thread dumps and stack traces ….

One thought on “Java in Notes/Domino Explained: Stacktraces”

  1. As someone who has garnered a fair share of Domino Java crash files, I’d have to say that programming directly using Notes.JAR from a standalone application is fraught with peril.  Domino Java has lots of undocumented race conditions when opening databases that make writing multithreaded Java servers quite thrilling.

    I have way more than 100 stack traces, all named hs_err*.log. Each is a nice mini-dump file from the JVM when it completely gives up and crashes.

    There are lots of stack traces here for the young at heart.  The funniest ones are the ones involving Sametime.  Extra points of creativity for the genius who named their threads "Aunt Zelma’s VP Listener", "Uncle Egad’s VP Sender", "Chuck the Postman’s Dispatching Thread".

    Now, whoever said that stacktraces aren’t fun?  If you cannot write solid library code, the next best thing is to give your poor clients a few chuckles while debugging your mistakes.  Tee hee.

    Ken Gartner



Comments are closed.