StackHunter Java Error Tracker v1.2 Released

StackHunter v1.2.3 - Exception DetailsThe latest beta release of our error tracker for Java apps is now available for download.


Log4J and Logback integration

We now track exceptions you log through the Log4J or Logback frameworks.  This lets you see exceptions in StackHunter even if you’re already handling them and even if they’re outside the request (on a worker thread).  We also make sure not to record the same exception twice, even if the code you’re working with does.  This feature requires no additional configuration or code change.  Just drop in the new client jar and you’re set.

Other changes

  • fixed several UI rendering issues in IE 11
  • fixed not serializable issue
  • using tabs for exception details
  • email alerts are now easier to read and are sent in both HTML & plain text
  • removed fractions from exception graphs
  • added feedback menu item and tweet buttons
  • servlet filter code snippet now shows during setup

Happy coding.

About Dele Taylor

Dele Taylor is the founder of -- a tool to track Java exceptions. You can follow him on Twitter, G+, and LinkedIn.

2 Responses to “StackHunter Java Error Tracker v1.2 Released”

  1. Hi Dele, I’m trying to get this working using logback , but when I try and start up the StackHunterServletFilter I get a ClassNotFoundException: org.apache.log4j.Logger , I obviously cant/don’t want log4j and logback in my client app, Is there something I’m missing / doing wrong ?

    • Hi Riaan,

      You’re not doing anything wrong. This is happening because StackHunter uses Log4J for it’s own internal logging.

      You can fix the ClassNotFoundException by adding the Log4J bridge (log4j-over-slf4j-XXX.jar) that came with Logback/SL4J to your client app.

      If you don’t already have it, it’s inside which you can download from I’ll make sure to add it to the build in the next release.

      Thanks for downloading StackHunter and please let me know how things go for you.