Started

FusionReactor goes beyond "just monitoring", to actively minimize server downtime and accelerate time to resolution like no other monitoring tool on the market.

Cut to the chase and get to the root of your Java production application problems in no time


Quickstart

Step 1 - Register for your free trial

Register for your free 14 day trial of FusionReactor Cloud here

Step 2 - Download and install FusionReactor

Once registered and logged into your new FusionReactor Cloud account - you can download the latest version of FusionReactor straight from your account settings > license page.

Installing FusionReactor for the first time:

  1. Download the latest FusionReactor JAR.

  2. Place the jar inside a unique directory called:

Windows

    "C:\FusionReactor\instance\INSTANCE_NAME"

Linux

    "/opt/fusionreactor/instance/INSTANCE_NAME"

  1. Edit the JVM settings of the application server that you want to monitor and add the following options:

Windows

    -javaagent:C:/FusionReactor/instance/INSTANCE_NAME/fusionreactor.jar=address=8088

Linux

    -javaagent:/opt/fusionreactor/instance/INSTANCE_NAME/fusionreactor.jar=address=8088

Note

Note: The address port (8088) must be different for each instance that you have on the same host.

Note: You always use / (forward slash) in the -javaagent paths on both Windows and Linux environments.

  1. Restart your application server.

  2. Log into FusionReactor locally.

  3. Enter your CLOUD account license key into the About page and activate the instance.

Updating an existing FusionReactor instance.

  1. Download the latest FusionReactor JAR.

  2. Stop your application server.

  3. Replace the fusionreactor.jar file of the instance with the new one.

  4. Start your application server.

  5. Log into FusionReactor locally.

  6. Enter your CLOUD account license key into the About page and activate the instance.

Step 3 (optional) - Installing the Debugger

Users with an FusionReactor Ultimate license (or trial users) can optionally install the native library required to enable the debugger functionality in FusionReactor.

Note

Debug does not support 32-bit operating systems or 32-bit versions of java running on 64-bit operating systems.

Simply copy the correct library for your operating system, as found in the following table:

Library Operating system
libfrjvmti_x64.so Linux 64-bit
libfrjvmti_x64.dylib MacOS 64-bit
frjvmti_x64.dll Windows 64-bit

and place this file into the instance directory for your configuration, e.g.

    /opt/fusionreactor/instance/<instancename>/

Configuration

Windows example

  1. Inside your ** \bin ** directory
  2. Run the ** TomcatXw.exe ** program. (Where X is the version number of your tomcat)
  3. Within the program, on the 'Java' tab, add the native library for your server to the bottom of the list in the 'Java options:' field.

Windows Java options

-Dcatalina.home=...
-Dcatalina.base=...
-Djava.endorsed.dirs=...
-Djava.io.tmpdir=...
-Djava.util.logging.manager=...
-Djava.util.logging.config.file=...

<Native Library>
1. Hit the apply button and then the OK button. 1. An example model for what the Java options field should look like:

Windows Java options

-Dcatalina.home=...
-Dcatalina.base=...
-Djava.endorsed.dirs=...
-Djava.io.tmpdir=...
-Djava.util.logging.manager=...
-Djava.util.logging.config.file=...

-agentpath:C:\FusionReactor\instance\Tomcat8\frjvmti_x64.dll

Linux example

  1. Inside your /bin/ directory
  2. Edit the setenv.sh, or if the file does not exist then you can go ahead and create the file.
  3. Add the native library value in the setenv.sh file.
Linux setenv.sh
... 
# FusionReactor JVM start options. Please do not edit these options.
FR_OPTS="<Native Library>"
export JAVA_OPTS="$JAVA_OPTS $FR_OPTS"
# End of FusionReactor opts
  1. An example model setenv.sh file:
Linux setenv.sh
... 
# FusionReactor JVM start options. Please do not edit these options.
FR_OPTS="-agentpath:/opt/fusionreactor/instance/tomcat8/libfrjvmti_x64.so"
export JAVA_OPTS="$JAVA_OPTS $FR_OPTS"
# End of FusionReactor opts

Important note

You need to add the native library into your java arguments the same way that the FusionReactor Java agent is configured. You must add the -agentpath argument which points to the correct library for your operating system. e.g. You must have both the agentpath and javaagent configured for Debug to work.

Compatibility

Java only allows one debugger at a time to be used. If you use JDWP (Java Debug Wire Protocol) you need to disable it to use FusionReactor Production Debugger. Having 2 configured will result in a warning from FusionReactor Production Debugger saying it cannot acquire the capabilities to debug the java server. Please remove lines like this from the java arguments:

-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000
OR
-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=12345

Note

JDWP may be written to the config by the server if you are running ColdFusion and have the Line Debugger enabled. This can be disabled at Debugging & logging > Debugger settings > Allow Line Debugging in the ColdFusion admin panel.

Start monitoring

Within a few minutes your server should appear online and start to push data to FusionReactor Cloud. Be sure to check out the Guides section above to make the most of FusionReactor Cloud.

Further installation guidance:

FusionReactor Java agent, Manual installation, Installing the Debugger