Introducing BrainLeg,
the Structural Java Exception Search Engine
and Private Project Exception Repository.

  1.        Find/Solve

  2. Share With Team

  3.       Happy Team

A search engine that actually understands differences in packages and source lines, nesting of exceptions, and more. Privately share solutions to app/project exceptions with your team and build private project support knowledge base.

Need More Info?

Searching by Exception error message is *so* 1999

How do you troubleshoot your java exceptions? Searching in mainstream search engine by exception error message like 'java.util.zip.ZipException: error in opening zip file' most of the time is extremely inefficient because it yields too many irrelevant matches.

BrainLeg was created to make troubleshooting of java exceptions as efficient as possible - you search by your entire exception stacktrace, like this: 

java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.6.0_25]
at java.util.zip.ZipFile.(ZipFile.java:127) [rt.jar:1.6.0_25]
at java.util.jar.JarFile.(JarFile.java:135) [rt.jar:1.6.0_25]
at java.util.jar.JarFile.(JarFile.java:99) [rt.jar:1.6.0_25]
at org.jboss.vfs.spi.JavaZipFileSystem.(JavaZipFileSystem.java:97)
at org.jboss.vfs.spi.JavaZipFileSystem.(JavaZipFileSystem.java:83)
at org.jboss.vfs.VFS.mountZip(VFS.java:408)

Since BrainLeg searches for exceptions structurally you spend less time looking at irrelevant exceptions and focus on the ones similar to yours!

It's free. Give it a spin, see how easy it is to