ColdFusion 8: Page 3

[frs-168] FusionReactor trial expires immediately on a Java6 VM running on Linux or Solaris


Overview

Due to Sun Microsystems bug 6519088 in the Linux and Solaris versions of Sun Java 6 prior to version 1.6.0_10-rc2, the FusionReactor license cannot be installed nor activated. The error message reported by the target server looks like the following:

13.08.2007 14:32:03 java.util.prefs.FileSystemPreferences syncWorld
WARNING: Couldn't flush system prefs: java.util.prefs.BackingStoreException: java.lang.IllegalArgumentException: Not supported: indent-number

As a result the trial period for FusionReactor expires immediately after the server is restarted.

Since Sun seems not to be interested in fixing this issue in Java 6, we have created our own fix for it. So, if you are interested in a permanent (unofficial) fix for this issue you can download fix6519088-1.0.0.jar.

This JAR simply implements the fix suggested in http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6519088

To apply the fix you have to prepend the JAR file to the boot classpath of your Java VM. This procedure differs depending on the server you use and is described in the following section.

Applying the fix

Copy the JAR file to the etc/lib directory of your FusionReactor installation (e.g. /opt/fusionreactor/etc/lib). In the following we assume that FusionReactor has been installed to /opt/fusionreactor.

Adobe Servers

JRun and ColdFusion servers require a change in the jvm.config file as shown below:

...
# Arguments to VM
java.args=-Xbootclasspath/p:/opt/fusionreactor/etc/lib/fix6519088-1.0.0.jar -server ...
...

Stop the server, locate the java.args variable and insert the text shown in blue color as the first argument and restart the server again.

Resin Server

Caucho Resin (the application server coming with Railo Server) requires a change in the $RAILO_HOME/conf/resin.conf XML configuration file as shown below:

...
<jvm-arg>-Xbootclasspath/p:/opt/fusionreactor/etc/lib/fix6519088-1.0.0.jar</jvm-arg>
<jvm-arg>-Xmx256m</jvm-arg>
<jvm-arg>-Xss1m</jvm-arg>
<jvm-arg>-Xdebug</jvm-arg>
<jvm-arg>-Dcom.sun.management.jmxremote</jvm-arg>
...

Stop the server, find the first <jvm.arg> element and insert the blue <jvm-arg> shown above before it then restart the server again.

Other Servers

Other servers like Apache Tomcat, JBoss or Jetty require a change of the belonging start or configuration script (e.g. catalina.sh for Tomcat or run.sh for JBoss) or simply passing the -Xbootclasspath/p argument as an additional argument when the server is started directly with the java command.

Tomcat

To apply the fix for a Tomcat server running with a Java 6 VM add the following line at the top of the catalina.sh file but after the #!/bin/sh line:

JAVA_OPTS="-Xbootclasspath/p:/opt/fusionreactor/etc/lib/fix6519088-1.0.0.jar -Djava.library.path=."

JBoss

To apply the fix for a Tomcat server running with a Java 6 VM add the following line at the top of the run.sh file but after the #!/bin/sh line:

JAVA_OPTS="-Xbootclasspath/p:/opt/fusionreactor/etc/lib/fix6519088-1.0.0.jar -Djava.library.path=."

Jetty

Start Jetty with the following command:
java -Xbootclasspath/p:/opt/fusionreactor/etc/lib/fix6519088-1.0.0.jar -jar start.jar

If you change the JVM of your server back to version 5 there will be no such problem. This problem only exists in version 6 of the JVM and unfortunately still has not been fixed by SUN in the latest update (1.6.0_07).

SUN finally fixed this bug in 1.6.0_10-rc2 (search for 6396599 in bugs fixed in JDK6 U10. Hopefully this will be still the case after it has been released.

Issue Details

Type: Technote
Issue Number: FRS-168
Components: Installer
Environment:
Resolution: Fixed
Last Updated: 16/Apr/09 7:54 AM
Affects Version: 2.0.4, 3.0, 3.0.1
Fixed Version: 1.0, 2.0, 2.0.3, 2.0.4, 3.0, 3.0.1
Server: ColdFusion 6, ColdFusion 7, ColdFusion 8, Flex Data Services, JBoss, Jetty, JRun 4, LiveCycle Data Services, Railo, ServletExec, Tomcat, WebSphere, WebLogic
Platform: Linux, Solaris
Related Issues:

FRS-170: Couldn’t flush system prefs: java.util.prefs.BackingStoreException: java.lang.IllegalArgumentException: Not supported: indent-number

FRS-198: Problems with installing or activating a license

[frs-205] FusionReactor Enterprise Dashboard 1.0.1 Release Notes and Resolved Issues



FusionReactor Enterprise Dashboard Rev. 1.0.1


RELEASE NOTES

Status: 01-Sep-2008

Welcome to the FusionReactor Enterprise Dashboard!

We appreciate your feedback. Please use the web form or send mail to:

support@fusion-reactor.com

These Release Notes describe what is contained in this release, provide
late-breaking news, and list additional documentation for the software.

For additional information on FusionReactor, please visit our website at:

https://www.fusion-reactor.com

For known issues and further support, please see the following web pages:

https://www.fusion-reactor.com/fr/faq.cfm
https://www.fusion-reactor.com/fr/support.cfm

To Check for FusionReactor AIR Enterprise Dashboard updates, open the application and select the "Updates" tab from the login dialogue and click the "Check for updates" button. The status text will be updated showing the applications current update status: "Up to date" or "Update Available".
If an update is available, the "Update" button will be enabled. Clicking the update button will download and install the latest update, restarting the application with the new and installed update.

RESOLVED ISSUES

Key Issue Type Summary
FE16 Bug A Status Change dialog is opened for each time a server status changes. Only one dialog should be opened

Issue Details

Type: Technote
Issue Number: FRS-205
Components: FR Enterprise Dashboard Desktop Application
Environment:
Resolution: Fixed
Last Updated: 17/Nov/08 4:40 PM
Affects Version:
Fixed Version: 3.0
Server: ColdFusion 6, ColdFusion 7, ColdFusion 8, Flex Data Services, JBoss, Jetty, JRun 4, LiveCycle Data Services, Railo, ServletExec, Tomcat, WebSphere, WebLogic
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Windows Vista
Related Issues:

FRS-203: FusionReactor Enterprise Dashboard 1.0.0 Release Notes and Resolved Issues

FRS-215: FusionReactor Enterprise Dashboard 1.1 Release Notes and Resolved Issues

[frs-203] FusionReactor Enterprise Dashboard 1.0.0 Release Notes and Resolved Issues



FusionReactor Enterprise Dashboard Rev. 1.0.0


RELEASE NOTES

Status: 22-Jul-2008

Welcome to the FusionReactor Enterprise Dashboard!

We appreciate your feedback. Please use the web form or send mail to:

support@fusion-reactor.com

These Release Notes describe what is contained in this release, provide
late-breaking news, and list additional documentation for the software.

For additional information on FusionReactor, please visit our website at:

https://www.fusion-reactor.com

For known issues and further support, please see the following web pages:

https://www.fusion-reactor.com/fr/faq.cfm
https://www.fusion-reactor.com/fr/support.cfm

To Check for FusionReactor AIR Enterprise Dashboard updates, open the application and select the "Updates" tab from the login dialogue and click the "Check for updates" button. The status text will be updated showing the applications current update status: "Up to date" or "Update Available".
If an update is available, the "Update" button will be enabled. Clicking the update button will download and install the latest update, restarting the application with the new and installed update.

RESOLVED ISSUES

Key Issue Type Summary
FE4 New Feature Create an Update Mechanism that allow updates to the AIR dashboard to be done online

Issue Details

Type: Technote
Issue Number: FRS-203
Components: FR Enterprise Dashboard Desktop Application
Environment:
Resolution: Fixed
Last Updated: 17/Nov/08 4:18 PM
Affects Version:
Fixed Version: 3.0
Server: ColdFusion 6, ColdFusion 7, ColdFusion 8, Flex Data Services, JBoss, Jetty, JRun 4, LiveCycle Data Services, Railo, ServletExec, Tomcat, WebSphere, WebLogic
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Windows Vista
Related Issues:

FRS-205: FusionReactor Enterprise Dashboard 1.0.1 Release Notes and Resolved Issues

[frs-84] How can I best monitor a set of (distributed) servers with FusionReactor?


There are several ways you can use FusionReactor to monitor a set of servers, even if they are installed on different physical machines. Note that FusionReactor is licensed per machine and not per instance so this will not cost you anything.

Some users install a Tomcat server and install FusionReactor into that as the monitoring server. This has the advantage that no ColdFusion server is being used as the monitor and Tomcat won't have to be brought down for any reason typically.

Other users configure a cross-over monitor, which simply means that they monitor all of the boxes from one monitoring server (e.g. Tomcat), and then they have one of the servers monitor Tomcat. This way if any server goes away you will receive a "Server Down" notification.

The FusionReactor Enterprise Dashboard remotely connects to a server using a configurable port number, typically 8088 or you can use port 80 if you configure FusionReactor to be available via your normal web server.

Issue Details

Type: Technote
Issue Number: FRS-84
Components: Enterprise Dashboard, FusionReactor Settings, Installer
Environment:
Resolution: Fixed
Last Updated: 14/Nov/08 6:00 PM
Affects Version: 2.0
Fixed Version: 2.0
Server: ColdFusion 6, ColdFusion 7, ColdFusion 8, Flex Data Services, JBoss, JRun 4, LiveCycle Data Services, Tomcat, WebSphere, WebLogic
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris
Related Issues:

[frs-199] 64bit FusionReactor Support (including ColdFusion 8 on 64 bit platforms)


Problem

When FusionReactor is installed onto a 64bit version of Java (used for example on ColdFusion 8 servers on 64bit machines) the native library will not load as the shipped version is 32bit and therefore incompatible.

The error on a Windows 64 bit server may be for example:

user FusionReactor Exception: C:JRun4binFusionReactor.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
java.lang.UnsatisfiedLinkError: C:JRun4binFusionReactor.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
 at java.lang.ClassLoader$NativeLibrary.load(Native Method) 

Resolution.

You can replace the 32bit version of the native library with the 64bit version by simply copying the new library over the original.

Operating System Download
Windows FusionReactor.dll
Linux libFusionReactor.so
Solaris libFusionReactor.sparc.so
OS X libFusionReactor.jnilib

How do I apply the hotfix?

  • Locate the original native library. Seach for the native library (eg. FusionReactor.dll) under the monitored server's installation folder (e.g. on a ColdFusion 8 server the CF installation folder may be C:ColdFusion8). Here are the locations of where the DLL is typically installed on some sample servers:
Installation Type Location
Standalone ColdFusion 6.1 <CFMX>runtimebin or <CFMX>lib (make sure that you only have the FusionReactor.dll in one of these locations)
Standalone ColdFusion 7 <CFMX>runtimebin or <CFMX>lib (make sure that you only have the FusionReactor.dll in one of these locations)
Standalone ColdFusion 8 <CFMX>runtimebin or <CFMX>lib (make sure that you only have the FusionReactor.dll in one of these locations)
Multi Server ColdFusion <JRUN>bin
JRun4 <JRUN4>bin
Tomcat 4,5,6 <TOMCAT>bin
JBoss 3,4,4.2,5 <JBOSS>bin
Jetty <JETTY>
Servlet Exec AS5,6 <SERVLETEXEC>bin
Railo Railix, Express <RAILO>
Railo Resin <RAILO>win32>
  • Stop the monitored server (e.g. ColdFusion, Tomcat, JBoss etc)
  • Backup the current native library file from it's current location (see above) to the desktop (in case of problems, this file can be restored).
  • Replace the current native library file with the hotfix native library file, overwriting the original.
  • Copy the hotfix native library file into the folder <FUSIONREACTOR>/etc/lib (e.g. C:FusionReactoretclib), overwriting the copy that is already there. (This file is used for new instances installed via the instance manager.)
  • Restart the monitored server (e.g. ColdFusion, Tomcat, JBoss etc)

Please note that the new library is for 64bit Java VM versions and NOT for 32bit Java VMs running on 64bit hardware/operating systems.

Issue Details

Type: Technote
Issue Number: FRS-199
Components: CPU + Memory
Environment:
Resolution: Fixed
Last Updated: 21/Jul/08 6:13 PM
Affects Version: 3.0
Fixed Version: 3.0
Server: ColdFusion 8
Platform:
Related Issues:

[frs-197] Stack Trace (stack dump) sometimes stops working although they did work when FusionReactor was started. (Only affects Windows servers).


NOTE: This Technote relates to FusionReactor version 3.0.0 only. Please see the linked technote FRS 196 for the FusionReactor version 2.0.x hotfix

Problem

On Windows platforms, the stack trace feature may stop working sometimes especially when the monitored server is under heavy load.

The problem is caused by an issue in the native library being unable to gain access to the output of the stack trace data sometimes.

Resolution

We have prepared a hotfix native library (FusionReactor.dll) that resolves this issue. You must replace the FusionReactor.dll running in each instance of FusionReactor and in the FusionReactor/etc/lib folder (so that new instances will use the hotfix library).

Who should use this hotfix?

This hotfix applies only to Windows installations of FusionReactor 3.0.0 versions (this hotfix will be integrated into future FR 3.x updates). Please see the linked tickets for the hotfix for Windows installations of FR 2.0.x.

How do I apply the hotfix?

  • Locate the original FusionReactor.dll. Seach for FusionReactor.dll under the monitored server's installation folder (e.g. on a ColdFusion MX7 server the CF installation folder may be C:CFusionMX7). Here are the locations of where the DLL is typically installed on some sample servers:
    Installation Type Location
    Standalone ColdFusion 6.1 <CFMX>runtimebin or <CFMX>lib (make sure that you only have the FusionReactor.dll in one of these locations)
    Standalone ColdFusion 7 <CFMX>runtimebin or <CFMX>lib (make sure that you only have the FusionReactor.dll in one of these locations)
    Standalone ColdFusion 8 <CFMX>runtimebin or <CFMX>lib (make sure that you only have the FusionReactor.dll in one of these locations)
    Multi Server ColdFusion <JRUN>bin
    JRun4 <JRUN4>bin
    Tomcat 4,5,6 <TOMCAT>bin
    JBoss 3,4,4.2,5 <JBOSS>bin
    Jetty <JETTY>
    Servlet Exec AS5,6 <SERVLETEXEC>bin
    Railo Railix, Express <RAILO>
    Railo Resin <RAILO>win32>
  • Stop the monitored server (e.g. ColdFusion, Tomcat, JBoss etc)
  • Backup the current FusionReactor.dll file from it's current location (see above) to the desktop (in case of problems, this file can be restored).
  • Replace the current FusionReactor.dll file with hotfix FusionReactor.dll file, overwriting the original. Note the new native library is smaller than the existing library.
  • Copy the hotfix FusionReactor.dll file into the folder <FUSIONREACTOR>/etc/lib (e.g. C:FusionReactoretclib), overwriting the copy that is already there. (This file is used for new instances installed via the instance manager.)
  • Restart the monitored server (e.g. ColdFusion, Tomcat, JBoss etc)

In case of problems, stop the monitored server, copy the backup (original) FusionReactor.dll file back to the original location and <FUSIONREACTOR>/etc/lib folder and restart the monitored server.

You must repeat this procedure for every monitored server that contains a FusionReactor instance on the computer, e.g. If you have 2 ColdFusion server instances and 2 Tomcat servers on a computer, all of which have FusionReactor installed in them, you must follow the procedure for all 4 servers.

Hotfix FusionReactor.dll (for FR 3.0.0 only):

(FusionReactor.dll)

Issue Details

Type: Technote
Issue Number: FRS-197
Components:
Environment:
Resolution: Fixed
Last Updated: 09/Apr/08 3:07 PM
Affects Version: 3.0
Fixed Version: 3.0
Server: ColdFusion 6, ColdFusion 7, ColdFusion 8, Flex Data Services, JBoss, Jetty, JRun 4, LiveCycle Data Services, Railo, ServletExec, Tomcat, WebSphere, WebLogic
Platform: Windows XP, Windows 2000, Windows 2003
Related Issues:

FRS-196: Stack Trace (stack dump) sometimes stops working although they did work when FusionReactor was started. (Only affects Windows servers).

[frs-200] Solaris CPU Monitoring does not work: Loading native library failed: libFusionReactor.sparc.so Cause: /opt/coldfusionmx7/lib/libFusionReactor.sparc.so: ld.so.1: cfmx7: fatal: libstdc++.so.6: open failed: No such file or directory


*NOTE: This Technote relates to FusionReactor version 3.0.0 only on Solaris (Sparc).

Problem

On Solaris 8/9 and some Solaris 10 Sparc installations the FusionReactor Native Library does not load and no CPU information is available. An error like the following may be generated in the J2EE log files:

FusionReactor Exception: /opt/coldfusionmx7/runtime/jre/lib/sparc/libFusionReactor.sparc.so: ld.so.1: cfmx7: fatal: libstdc++.so.6: open failed: No such file or directory 

java.lang.UnsatisfiedLinkError: /opt/coldfusionmx7/runtime/bin/libFusionReactor.sparc.so: ld.so.1: cfmx7: fatal: libstdc++. 

The problem is caused by the fact that the libstdc ++.so.6 ( C ++ lib ) is not available but is required by FusionReactor native library to load.

Resolution

We have prepared a hotfix native library (libFusionReactor.sparc.so) that resolves this issue. You must replace the libFusionReactor.sparc.so running in each instance of FusionReactor and in the FusionReactor/etc/lib folder (so that new instances will use the hotfix library).

NOTE: Only Instance CPU monitoring works on Solaris. FusionReactor on Solaris currently does not support System CPU monitoring.

Who should use this hotfix?

This hotfix applies only to Solaris installations of FusionReactor 3.0.0 versions that fail to load the FusionReactor native library due to the error above (this hotfix will be integrated into future FR 3.x updates).

How do I apply the hotfix?

  • Locate the original libFusionReactor.sparc.so. Seach for libFusionReactor.sparc.so under the monitored server's installation folder. Here are the locations of where the SO is typically installed on some sample servers:
    Installation Type Location
    Standalone ColdFusion 6.1 <CFMX>/runtime/bin or <CFMX>/lib (make sure that you only have the libFusionReactor.sparc.so in one of these locations)
    Standalone ColdFusion 7 <CFMX>/runtime/bin or <CFMX>/lib (make sure that you only have the libFusionReactor.sparc.so in one of these locations)
    Standalone ColdFusion 8 <CFMX>/runtime/bin or <CFMX>/lib (make sure that you only have the libFusionReactor.sparc.so in one of these locations)
    Multi Server ColdFusion <JRUN>/bin
    JRun4 <JRUN4>/bin
    Tomcat 4,5,6 <TOMCAT>/bin
    JBoss 3,4,4.2,5 <JBOSS>/bin
    Jetty <JETTY>
  • Stop the monitored server (e.g. ColdFusion, Tomcat, JBoss etc)
  • Backup the current libFusionReactor.sparc.so file from it's current location (see above) to the desktop (in case of problems, this file can be restored).
  • Replace the current libFusionReactor.sparc.so file with hotfix libFusionReactor.sparc.so file, overwriting the original. Note the new native library is smaller than the existing library.
  • Copy the hotfix libFusionReactor.sparc.so file into the folder <FUSIONREACTOR>/etc/lib overwriting the copy that is already there. (This file is used for new instances installed via the instance manager.)
  • Restart the monitored server (e.g. ColdFusion, Tomcat, JBoss etc)

In case of problems, stop the monitored server, copy the backup (original) libFusionReactor.sparc.so file back to the original location and <FUSIONREACTOR>/etc/lib folder and restart the monitored server.

You must repeat this procedure for every monitored server that contains a FusionReactor instance on the computer, e.g. If you have 2 ColdFusion server instances and 2 Tomcat servers on a computer, all of which have FusionReactor installed in them, you must follow the procedure for all 4 servers.

Hotfix libFusionReactor.sparc.so (for FR 3.0.0 only):

(libFusionReactor.sparc.so)

Issue Details

Type: Technote
Issue Number: FRS-200
Components:
Environment:
Resolution: Fixed
Last Updated: 07/Apr/08 10:48 PM
Affects Version: 3.0
Fixed Version: 3.0
Server: ColdFusion 6, ColdFusion 7, ColdFusion 8, JBoss, Jetty, JRun 4, Tomcat, WebSphere, WebLogic
Platform: Solaris
Related Issues:

[frs-196] Stack Trace (stack dump) sometimes stops working although they did work when FusionReactor was started. (Only affects Windows servers).


NOTE: This Technote relates to FusionReactor version 2.0.x only. Please see the linked technote FRS 197 for the FusionReactor version 3.0.0 hotfix

Problem

On Windows platforms, the stack trace feature may stop working sometimes especially when the monitored server is under heavy load.

The problem is caused by an issue in the native library being unable to gain access to the output of the stack trace data sometimes.

Resolution

We have prepared a hotfix native library (FusionReactor.dll) that resolves this issue. You must replace the FusionReactor.dll running in each instance of FusionReactor and in the FusionReactor/etc/lib folder (so that new instances will use the hotfix library).

Who should use this hotfix?

This hotfix applies only to Windows installations of FusionReactor 2.0.0, 2.0.1, 2.0.2, 2.0.3 and 2.0.4 versions. Please see the linked tickets for the hotfix for Windows installations of FR 3.0.0.

How do I apply the hotfix?

  • Locate the original FusionReactor.dll. Seach for FusionReactor.dll under the monitored server's installation folder (e.g. on a ColdFusion MX7 server the CF installation folder may be C:CFusionMX7). Here are the locations of where the DLL is typically installed on some sample servers:
    Installation Type Location
    Standalone ColdFusion 6.1 <CFMX>runtimebin or <CFMX>lib (make sure that you only have the FusionReactor.dll in one of these locations)
    Standalone ColdFusion 7 <CFMX>runtimebin or <CFMX>lib (make sure that you only have the FusionReactor.dll in one of these locations)
    Standalone ColdFusion 8 <CFMX>runtimebin or <CFMX>lib (make sure that you only have the FusionReactor.dll in one of these locations)
    Multi Server ColdFusion <JRUN>bin
    JRun4 <JRUN4>bin
    Tomcat 4,5,6 <TOMCAT>bin
    JBoss 3,4,4.2,5 <JBOSS>bin
    Jetty <JETTY>
    Servlet Exec AS5,6 <SERVLETEXEC>bin
    Railo Railix, Express <RAILO>
    Railo Resin <RAILO>win32>
  • Stop the monitored server (e.g. ColdFusion, Tomcat, JBoss etc)
  • Backup the current FusionReactor.dll file from it's current location (see above) to the desktop (in case of problems, this file can be restored).
  • Replace the current FusionReactor.dll file with hotfix FusionReactor.dll file, overwriting the original. Note the new native library is smaller than the existing library.
  • Copy the hotfix FusionReactor.dll file into the folder <FUSIONREACTOR>/etc/lib (e.g. C:FusionReactoretclib), overwriting the copy that is already there. (This file is used for new instances installed via the instance manager.)
  • Restart the monitored server (e.g. ColdFusion, Tomcat, JBoss etc)

In case of problems, stop the monitored server, copy the backup (original) FusionReactor.dll file back to the original location and <FUSIONREACTOR>/etc/lib folder and restart the monitored server.

You must repeat this procedure for every monitored server that contains a FusionReactor instance on the computer, e.g. If you have 2 ColdFusion server instances and 2 Tomcat servers on a computer, all of which have FusionReactor installed in them, you must follow the procedure for all 4 servers.

Hotfix FusionReactor.dll (for FR 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4 only):

(FusionReactor.dll)

Issue Details

Type: Technote
Issue Number: FRS-196
Components:
Environment:
Resolution: Fixed
Last Updated: 03/Mar/08 5:31 PM
Affects Version: 2.0, 2.0.3, 2.0.4
Fixed Version: 2.0, 2.0.3, 2.0.4
Server: ColdFusion 6, ColdFusion 7, ColdFusion 8, Flex Data Services, JBoss, Jetty, JRun 4, LiveCycle Data Services, Railo, ServletExec, Tomcat, WebSphere, WebLogic
Platform: Windows XP, Windows 2000, Windows 2003
Related Issues:

FRS-197: Stack Trace (stack dump) sometimes stops working although they did work when FusionReactor was started. (Only affects Windows servers).

[frs-193] How can I go back to FusionReactor 2.0.4 after having updated to version 3.0 without losing my configuration?


Before you update…
If you are in doubt whether you want to stay on version 3.0 of FusionReactor make a backup of your FusionReactor instance directory before you run the FusionReactor 3.0 Setup and store it in a safe directory. When uninstalling FusionReactor the complete FusionReactor directory will be removed.

But I have already updated …
If you have already updated your FusionReactor 2.0.x version to 3.0 the configuration of all local FusionReactor instances found in the FusionReactor/instance directory has been upgraded to the current version. This upgrade has not changed your previous configuration but you have to apply some minor modifcations to it to be able to use it with FusionReactor 2.0.x again.

Downgrading from 3.0 to 2.0 without losing the configuration and log files
The following procedure describes the steps you have to do to switch back to FusionReactor 2.0 without losing your configuration and log files.

  1. Make a backup of the Fusionreactor/instance directory and place it in a different directory (outside the FusionReactor install directory!)
  2. Uninstall FusionReactor 3.0
  3. Install FusionReactor 2.0 to the server you had installed it before and add a FusionReactor instance with the same name you used before
  4. Stop the server
  5. Copy the backup of your Fusionreactor/instance directory (you made in step 1) to the current Fusionreactor/instance directory, overriding all files.
  6. Open the reactor.conf files of your FusionReactor instance (Fusionreactor/instance/<your instance>/conf/reactor.conf) and perform the following changes:
    • add the line password=D41D8CD98F00B204E9800998ECF8427E
    • find the line containing version=3 and change it to version=2
  7. Repeat the previous step for any other FusionReactor instances you have configured
  8. Restart the server and login with the empty password.
  9. Set a new password to secure your FusionReactor installation
  10. In the Enterprise Dashboard you will see all instances you have configured previously. In the Instance Manager only the current instance is already configured.
    • Add any other local instances again using the same name as shown in the Enterprise Dashboard to have them under control of the Instance Manager again.

Issue Details

Type: Technote
Issue Number: FRS-193
Components: Installer
Environment:
Resolution: Fixed
Last Updated: 23/Jan/08 4:50 PM
Affects Version: 3.0
Fixed Version:
Server: ColdFusion 6, ColdFusion 7, ColdFusion 8, Flex Data Services, JBoss, Jetty, JRun 4, LiveCycle Data Services, Railo, ServletExec, Tomcat, WebSphere, WebLogic
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris, Windows Vista
Related Issues:

FRS-194: After upgrading a FusionReactor 2.0.4 to FusionReactor 3.0.x, I can no longer log in

[frs-160] default-err.log contains com.intergral.fusionreactor.I.J: Unauthorized – bad password for http://…..:8088/fusionreactor/fService.cfm


The following exception is recorded in the default-err.log file.

com.intergral.fusionreactor.I.J: Unauthorized - bad password for http://.....:8088/fusionreactor/fService.cfm?command=remoting&subcommand=transfer&data=metrics
 at com.intergral.fusionreactor.I.K.B(Unknown Source)
 at com.intergral.fusionreactor.I.K.A(Unknown Source)
 at com.intergral.fusionreactor.G.A.run(Unknown Source)
Caused by: com.intergral.fusionreactor.I.K$_C

This exception indicates that a monitored server has been incorrectly added to the Enterprise Dashboard. Check the password entered in the Manage Machines (Manager Servers) page for the server mentioned in the error message.

Issue Details

Type: Technote
Issue Number: FRS-160
Components: Enterprise Dashboard
Environment:
Resolution: Fixed
Last Updated: 22/Jan/08 12:11 PM
Affects Version: 1.0, 2.0, 2.0.3, 2.0.4, 3.0
Fixed Version:
Server: ColdFusion 6, ColdFusion 7, ColdFusion 8, Flex Data Services, JBoss, JRun 4, LiveCycle Data Services, Tomcat, WebSphere, WebLogic
Platform:
Related Issues: