Child pages
  • Manual Uninstallation
Skip to end of metadata
Go to start of metadata

Contents


Introduction


FusionReactor has automatic uninstallers for all application servers listed as supported for version 6.1.0, Including Tomcat, Jetty, Railo, and ColdFusion. FusionReactor can be automatically uninstalled from your application servers using Instance Manager (provided you had used it for the install process), sparing you the trouble of manually uninstalling. More details can be found on the FusionReactor Installer page.

If you would, however, like to continue uninstalling your servers manually, please see the specific server type below for instructions on possible configuration files to search for the installed FusionReactor Java Agent and/or the FusionReactor Production Debugger, so that FusionReactor can be uninstalled.

This document is for you if you have questions such as:

  • 'My application server refuses to start after installing FusionReactor! What do I need to do to get FusionReactor off my server and get it back up and running?' 
  • 'I want to move to a new application server, how do I remove FusionReactor from my current application server?'
  • 'FusionReactor has corrupted my application server, and things aren't working as they should be. How do I remove it?' 

The uninstall process for all application servers we currently support are listed below:

IMPORTANT - Licensing

When manually uninstalling FusionReactor, be sure to deactivate your license for that particular FusionReactor instance beforehand. This can be be done by navigating to the 'About' page of FusionReactor whilst the application server is running, and hitting 'Deactivate License'. This way, if you choose to re-use FusionReactor on another server, you will be able to use the same license key.

 

Servers


Apache Tomcat (7 / 8 / 9)


Windows

  1. Inside your <Apache_Tomcat_Home>/bin/ directory
  2. Run the TomcatXw.exe program. (Where X is the version number of your tomcat installation).
  3. Within the program, on the 'Java' tab, the FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present somewhere in the list in the 'Java Options:' field. To remove FusionReactor, simply delete the -javaagent and -agentpath text, shown in bold from the list below - note that the directory shown may be different for your installation. Hit 'Apply', then 'Ok', and FusionReactor will be uninstalled on the next reboot.

    Windows Java Options

    -Dcatalina.home=...
    -Dcatalina.base=...
    -Djava.endorsed.dirs=...
    -Djava.io.tmpdir=...
    -Djava.util.logging.manager=...
    -Djava.util.logging.config.file=...
    -javaagent:C:\FusionReactor\instance\Tomcat8\fusionreactor.jar=address=8088
    -agentpath:C:\FusionReactor\instance\Tomcat8\frjvmti_x64.dll

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

Linux

  1. Inside your <Apache_Tomcat_Home>/bin/ directory

  2. Edit the file setenv.sh, or if the file does not exist you can go ahead and create the file

  3. You should find the following (or equivalent) inside the setenv.sh file. FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger values are in the setenv.sh file. Simply remove the highlighted lines, save, and then FusionReactor should then be uninstalled on the next reboot.

    Linux setenv.sh

    ...
    # FusionReactor JVM start options. Please do not edit these options.
    FR_OPTS="-javaagent:/opt/fusionreactor/instance/tomcat8/fusionreactor.jar=address=8088 -agentpath:/opt/fusionreactor/instance/tomcat8/libfrjvmti_x64.so"
    export JAVA_OPTS="$JAVA_OPTS $FR_OPTS"
    # End of FusionReactor opts

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

ColdFusion (9 / 10 / 11 / 2016)


ColdFusion (9 / 10 / 11) on the Windows Operating System

If the Java Argument contains backward slashes (\) the server will interpret this as an attempt to escape the character that follows, meaning that the server will refuse to start.
These slashes should be escaped (\\) or reversed (/) in order for the server to work.
  1. Inside the directory:
    1. for ColdFusion 9:
      1. <ColdFusion_Home>/runtime/bin/ 
    2. for ColdFusion 10|11|2016:
      1. <ColdFusion_Home>/cfusion/bin/ 
  2. Edit the file jvm.config
  3. The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present at the end - or among the arguments - on the line after '# Arguments to VMx'. Remove the java agent - and agent path, if applicable - and ensure the rest of the java arguments intact  and all the Java arguments are on the same line, save, and then FusionReactor will then be uninstalled from the server once it has been rebooted.

    Linux jvm.config

    ...

    # Arguments to VMx
    java.args=-server -Xms256m -Xmx512m -XX:MaxPermSize=192m -Xbatch -Dcoldfusion.home={application.home} -Djava.awt.headless=true -Dcoldfusion.rootDir={application.home} -Djava.security.policy={application.home}/lib/coldfusion.policy -Djava.security.auth.policy={application.home}/lib/neo_jaas.policy -Dcoldfusion.classPath={application.home}/lib/updates,{application.home}/lib,{application.home}/lib/axis2,{application.home}/gateway/lib/,{application.home}/wwwroot/WEB-INF/cfform/jars,{application.home}/wwwroot/WEB-INF/flex/jars,{application.home}/lib/oosdk/lib,{application.home}/lib/oosdk/classes -Dcoldfusion.libPath={application.home}/lib -Dorg.apache.coyote.USE_CUSTOM_STATUS_MSG_IN_HEADER=true -javaagent:/opt/fusionreactor/instance/coldfusion9/fusionreactor.jar=address=8088 -agentpath:/opt/fusionreactor/instance/coldfusion9/libfrjvmti_x64.so

    ...

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

ColdFusion 9 Solr


Windows

  1. Inside the <ColdFusion_Home>/solr/ directory
  2. Edit the file solr.lax
  3. The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present at the end (or among the arguments) of the line beginning with 'lax.nl.java.option.additional='. Simply remove them from the Java arguments, whilst ensuring all the other Java arguments remain intact and all the Java arguments remain on the same line. Save the file, and FusionReactor will then be uninstalled from your server once it has been rebooted.

    Windows solr.lax

    ...

    lax.nl.java.option.additional=-server -Xmx256m -XX:+AggressiveOpts -XX:+ScavengeBeforeFullGC -XX:-UseParallelGC -DSTOP.PORT=8079 -DSTOP.KEY=cfstop -Dsolr.solr.home=multicore -javaagent:C:\FusionReactor\instance\cf9-solr\fusionreactor.jar=address=8088 -agentpath:C:\FusionReactor\instance\cf9-solr\frjvmti_x64.dll

    ...

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

Linux

  1. Inside the <ColdFusion_Home>/solr/ directory
  2. Edit the file cfsolr.
  3. The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present at the end - or among the arguments - on the line after '# JVM Args', . Remove them, and ensure all the Java arguments remain intact and are on the same line, save the file, and FusionReactor should then be uninstalled from your server on the next reboot.

    Linux cfsolr

    ...

    # JVM Args
    JVMARGS="-XX:+AggressiveOpts -XX:+ScavengeBeforeFullGC -XX:-UseParallelGC -Xmx256m -Dsolr.solr.home=multicore -DSTOP.PORT=8079 -DSTOP.KEY=cfsolrstop -javaagent:/opt/fusionreactor/instance/cf9-solr/fusionreactor.jar=address=8088 -agentpath:/opt/fusionreactor/instance/cf9-solr/libfrjvmti_x64.so"

    ...

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

ColdFusion (10 / 11) Solr


Windows

  1. Inside the <ColdFusion_Home>/cfusion/jetty/ directory
  2. Edit the file jetty.lax
  3. The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present at the end - or among the other arguments - on the line beginning with 'lax.nl.java.option.additional='. To remove FusionReactor, simply remove that Java agent - and the agent path, if applicable -  from the arguments, whilst ensuring all the other Java arguments remain intact and are all remain are on the same line. Save the file, and FusionReactor will be uninstalled on the next reboot of the server.

    Windows jetty.lax

    ...

    lax.nl.java.option.additional=-server -Xmx256m -XX:+AggressiveOpts -XX:+ScavengeBeforeFullGC -XX:-UseParallelGC -DSTOP.PORT=8079 -DSTOP.KEY=cfstop -Dsolr.solr.home=multicore -javaagent:C:\FusionReactor\instance\cf10-solr\fusionreactor.jar=address=8088 -agentpath:C:\FusionReactor\instance\cf10-solr\frjvmti_x64.dll

    ...

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

Linux

  1. Inside the <ColdFusion_Home>/cfusion/jetty/ directory
  2. Edit the file cfjetty.
  3. The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present at the end - or among the arguments - on the line after '# JVM Args'. To remove FusionReactor, simply remove that Java agent - and the agent path, if applicable - from the arguments, whilst ensuring all the other Java arguments remain intact and are all on the same line. Save the file, and FusionReactor will be uninstalled on the next reboot of the server.

    Linux cfjetty

    ...

    # JVM Args
    JVMARGS="-XX:+AggressiveOpts -XX:+ScavengeBeforeFullGC -XX:-UseParallelGC -Xmx512m -Dsolr.solr.home=multicore -DSTOP.PORT=$STOPPORT -DSTOP.KEY=cfsolrstop -javaagent:/opt/fusionreactor/instance/cf10-solr/fusionreactor.jar=address=8088 -agentpath:/opt/fusionreactor/instance/cf10-solr/libfrjvmti_x64.so"

    ...

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

ColdFusion 9 Multi


ColdFusion 9 Multi on the Windows Operating System

If the Java Argument contains backward slashes (\) the server will interpret this as an attempt to escape the character that follows, meaning that the server will refuse to start.
These slashes should be escaped (\\) or reversed (/) in order for the server to work.

Each instance must have its own jvm.config file, please see here for more information on how to do this.

  1. Inside <ColdFusion_Multi_Home>/bin/ directory
  2. Edit the new jvm.config file you created
  3. The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present at the end - or among the arguments - on the line after "# Arguments to VMx". To remove FusionReactor, simply remove the Java agent - and the agent path, if applicable - from the arguments, whilst ensuring all the Java arguments remain intact and are all on the same line. FusionReactor will then be uninstalled on the next reboot of the server.

    Windows / Linux Jvm.config

     # Arguments to VMx
    java.args=-server -Xms256m -Xmx512m -XX:MaxPermSize=192m -Xbatch -Dcoldfusion.home={application.home} -Djava.awt.headless=true -Dcoldfusion.rootDir={application.home} -Djava.security.policy={application.home}/lib/coldfusion.policy -Djava.security.auth.policy={application.home}/lib/neo_jaas.policy -Dcoldfusion.classPath={application.home}/lib/updates,{application.home}/lib,{application.home}/lib/axis2,{application.home}/gateway/lib/,{application.home}/wwwroot/WEB-INF/cfform/jars,{application.home}/wwwroot/WEB-INF/flex/jars,{application.home}/lib/oosdk/lib,{application.home}/lib/oosdk/classes -Dcoldfusion.libPath={application.home}/lib -Dorg.apache.coyote.USE_CUSTOM_STATUS_MSG_IN_HEADER=true -javaagent:/opt/fusionreactor/instance/coldfusion9-multi/fusionreactor.jar=address=8088 -agentpath:/opt/fusionreactor/instance/coldfusion9-multi/libfrjvmti_x64.so

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

Glassfish 4


  1. Inside the <Glassfish_Home>/glassfish/domains/domain1/config/ directory
  2. Edit the file domain.xml.
  3. The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present inside the <java-config> tag as a <jvm-options> tag. To remove FusionReactor, simply remove the Java agent - and the agent path, if applicable - and FusionReactor will then be uninstalled from your server on the next reboot.

    Linux domain.xml

    ...

    <jvm-options>-javaagent:/opt/fusionreactor/instance/galssfish4/fusionreactor.jar=address=8088<jvm-options>
    <jvm-options>-agentpath:/opt/fusionreactor/instance/glassfish4/libfrjvmti_x64.so</jvm-options>

    ...

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

    With some glassfish servers the default trust store can affect license activation.  See the following link for more information:

Railo 3


Windows

  1. Inside your <Railo_Home>/tomcat/bin/ directory.
  2. Run the Railow.exe program.
  3. Within the program, on the 'Java' tab, The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present somewhere in the list in the 'Java Options:' field. To remove FusionReactor, simply delete the highlighted values from the list. Hit 'Apply', then 'Ok', and FusionReactor will be uninstalled on the next reboot.

    Windows Java Options

    -Dcatalina.home=...
    -Dcatalina.base=...
    -Djava.endorsed.dirs=...
    -Djava.io.tmpdir=...
    -Djava.util.logging.manager=...
    -Djava.util.logging.config.file=...
    -javaagent:C:\FusionReactor\instance\railo3\fusionreactor.jar=address=8088 
    -agentpath:C:\FusionReactor\instance\railo3\frjvmti_x64.dll

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

Linux

  1. Inside your <Railo_Home>/tomcat/bin/ directory.

  2. Edit/Create the file setenv.sh.

  3. The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present inside the setenv.sh file, possibly at the bottom. Remove the entire following block of text from the file and hit save, FusionReactor will then be uninstalled on the next reboot of your server.

    Linux setenv.sh

    ... 

    # FusionReactor JVM start options. Please do not edit these options.
    FR_OPTS="-javaagent:/opt/fusionreactor/instance/railo3/fusionreactor.jar=address=8088 -agentpath:/opt/fusionreactor/instance/railo3/libfrjvmti_x64.so"

    export JAVA_OPTS="$JAVA_OPTS $FR_OPTS"
    # End of FusionReactor opts 

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

Railo 4


Windows

  1. Inside your <Railo_Home>/tomcat/bin/ directory
  2. Run the Railow.exe program.
  3. Within the program, on the 'Java' tab, the FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present within the list in the 'Java Options:' field. To remove FusionReactor from your server, simply remove the highlighted lines from this list. Hit 'Apply', then 'Ok'. FusionReactor will then be uninstalled on the next reboot of your server.

    Windows Java Options

    -Dcatalina.home=...
    -Dcatalina.base=...
    -Djava.endorsed.dirs=...
    -Djava.io.tmpdir=...
    -Djava.util.logging.manager=...
    -Djava.util.logging.config.file=...
    -javaagent:C:\FusionReactor\instance\railo4\fusionreactor.jar=address=8088 
    -agentpath:C:\FusionReactor\instance\railo4\frjvmti_x64.dll

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

Linux

  1. Inside your <Railo_Home>/ directory

  2. Edit the file start

  3. The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present inside the start file, among arguments that look something like what is shown below: Simply remove the highlighted lines from these arguments whilst keeping the other arguments intact. FusionReactor will then be uninstalled on the next reboot of the server.

    Linux start

    ... 

    jre/bin/java -Djetty.port=8888 -DSTOP.PORT=8887 -DSTOP.KEY=railo -Xms256M -Xmx1024M -javaagent:/opt/fusionreactor/instance/railo4/fusionreactor.jar=address=8088 -agentpath:/opt/fusionreactor/instance/railo4/libfrjvmti_x64.so -jar start.jar 

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

JBoss 7 Standalone & WildFly (8 / 9 / 10)


  1. Inside your <JBoss/Wildfly_Home>/bin/ directory
  2. Edit the file standalone.conf
  3. The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present inside the standalone.conf file, it may be at the bottom, but could have been placed anywhere inside. It will be appended to the current JAVA_OPTS variable. Find the java agent - and the agent path, if applicable - and remove it from the JAVA_OPTS variable. FusionReactor will then be uninstalled on the next reboot of your server.

    Windows / Linux standalone.conf

    ... 

    JAVA_OPTS="$JAVA_OPTS -javaagent:/opt/fusionreactor/instance/railo4/fusionreactor.jar=address=8088 -agentpath:/opt/fusionreactor/instance/railo4/libfrjvmti_x64.so"

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

Jetty (7 / 8 / 9)


  1. Inside your <Jetty_Home>/ directory
  2. Edit the file start.ini
  3. The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present inside the start.ini file, at the bottom, below "--exec". Simple delete the highlighted lines and FusionReactor will then be uninstalled from your server on the next reboot.

    Windows / Linux standalone.conf

    ... 

    --exec
    -javaagent:/opt/fusionreactor/instance/jetty7/fusionreactor.jar=address=8088
    -agentpath:/opt/fusionreactor/instance/jetty7/libfrjvmti_x64.so

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

Lucee (4 / 5)


Windows

  1. Inside your <Lucee_Home>/tomcat/bin/ directory
  2. Run the Luceew.exe program.
  3. Within the program, on the 'Java' tab, The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present within the list in the 'Java Options:' field. Delete the Java agent - and the agent path, if applicable - from this list, hit 'Apply,' then 'Ok'. FusionReactor will then be uninstalled from your server on the next reboot.

    Windows Java Options

    -Dcatalina.home=...
    -Dcatalina.base=...
    -Djava.endorsed.dirs=...
    -Djava.io.tmpdir=...
    -Djava.util.logging.manager=...
    -Djava.util.logging.config.file=...
    -javaagent:C:\FusionReactor\instance\Lucee4\fusionreactor.jar=address=8088
    -agentpath:C:\FusionReactor\instance\Lucee4\frjvmti_x64.dll

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

Linux

  1. Inside your <Lucee_Home>/bin/ directory

  2. Edit the file setenv.sh, or if the file does not exist you can go ahead and create the file

  3. The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present inside the setenv.sh file, usually at the bottom. To remove FusionReactor, simply delete following block of text. Save the file, and then FusionReactor will be uninstalled from your server on the next reboot.

    Linux setenv.sh

    ... 

    # FusionReactor JVM start options. Please do not edit these options.
    FR_OPTS="-javaagent:/opt/fusionreactor/instance/lucee4/fusionreactor.jar=address=8088 -agentpath:/opt/fusionreactor/instance/lucee4/libfrjvmti_x64.so"

    export JAVA_OPTS="$JAVA_OPTS $FR_OPTS"
    # End of FusionReactor opts 

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

     

FusionAnalytics


  1. Inside your <FusionAnalytics_Home>/Server/bin/ directory
  2. Edit the file "FusionAnalytics Server.vmoptions"
  3. The FusionReactor Java Agent and (possibly) the FusionReactor Production Debugger should be present at the bottom of the file. To remove FusionReactor, simple delete the highlighted lines from the list. FusionReactor will then be uninstalled once FusionAnalytics has been rebooted.

    Windows / Linux FusionAnalytics Server.vmoptions

    -server
    -Xms128m
    -Xmx768m
    -XX:MaxPermSize=256m
    -Djava.awt.headless=true
    -Dcom.sun.management.jmxremote.port=3333
    -Dcom.sun.management.jmxremote.ssl=false
    -Dcom.sun.management.jmxremote.authenticate=false
    -Dfusionanalytics.datacollector.dirObserver.scanInterval=5000
    -Dfusionanalytics.lm.store=C:/FusionAnalytics/Server/data/falm/falm.store
    -Dgrails.scan.interval=3600000
    -javaagent:/opt/fusionreactor/instance/fusionanalytics/fusionreactor.jar=address=8088
    -agentpath:/opt/fusionreactor/instance/fusionanalytics/libfrjvmti_x64.so

    red: The actual FusionReactor Java program

    green: The production debugger library (add-on for FusionReactor)

 

  • No labels