How to use it:

<><><><><>

Race Catcher™ product:
In order to analyze your Java application for multithreading issues it must be executed in ARM (Application Reliability Management) mode.

ARM mode is achieved by adding the javaagent parameter pointing to the RaceCatcher.jar to the string that invokes your java application.
I.e. instead of starting you application from the console using the command string: java -jar your.jar, you would type: java -javaagent:path-to-race-catcher\RaceCatcher.jar -jar your.jar

Preinstalled script jta expands into java -javaagent:path-to race-catcher-agent/RaceCatcher.jar
Instead of java -jar your.jar you would type jta -jar your.jar

     Example of running preinstalled demo in ARM mode     You will see the following demo application running     The project will appear on the Race Catcher™ user interface.

     When using script, containing number of java -options, i.e. to start an application server,  add these two JVM arguments to the startup script     How To ARM Enable Different Application Servers

      Please note that default installation folder structure differ between Windows, Linux and MAC OS, and is as follows:
            Windows:       C:\Program Files\Thinking Software\RaceCatcher\lib\RaceCatcher.jar
            Linux:             /home/user-name/tsi/RaceCatcher/lib/RaceCatcher.jar
            Mac:               /Users/user-name/ThinkingSoftware/RaceCatcher/lib/RaceCatcher.jar

To use Race Catcher™ with your favorite IDE, like Eclipse or Netbeans, you would add the -javaagent parameter respectively to VM arguments (Eclipse) or VM options (NetBeans)
Additionally, unless the IDE is started for the command line, which would pick up environment variable SUM4JAVA, the IDE would also need set the system property value of SUMDIR (see example on the link below)
      Example of ARM-Enabled NetBeans project

Explaining Race Catcher™ user interface
ARM-mode enabled java projects automatically show up in the Projects panel of the Race Catcher™ user interface
     If the project has a green light - no race condition or deadlock had been experienced
     If the project is marked by a race or a deadlock icons:
           Click on the Contention in the Contention List to see the performed analysis.
           Click on the Animate button to see the animation of the race condition.

Controlling the overhead
The overhead caused by the Race Catcher™ agent is already small. You can further control it here in 2 different ways from Race Catcher™ user interface menu:
            1: Run => Agent Start Options. Choose between the Test and Production
            2. Run => Next Run Filters.   The filters are explained here

<><><><><>

Race Catcher™ service:
Race Catcher service is explained here. Service Components