Windows Vista: Page 2

[frs-298] Instance Manager picks up the Tomcat based version of Railo twice


This technote is about installing an instance of FusionReactor on Railo Server.

Description

Version 4.5.0 of FusionReactor Instance Manager picks up the Tomcat based version of Railo twice. As a result the list of suitable target servers will contain the following target servers

  • Apache Tomcat
  • Railo

which actually represent the same server. This can be seen in the Server Scan dialog shown below

(note the directory paths) which typically is displayed when FusionReactor does its initial scan for target servers and later on the Instance Manager page:

Resolution

An instance of FusionReactor should be installed in only one of the two candidates, preferable the Railo server. Future versions of FusionReactor will only display Railo and omit the Apache Tomcat if it represents a Railo Server.
If you have done so the Instance Manager page will look like the one shown below.

Issue Details

Type: Technote
Issue Number: FRS-298
Components: Instance Manager
Environment:
Resolution: Fixed
Last Updated: 22/May/12 5:28 PM
Affects Version: 4.0.10
Fixed Version: 4.5.1
Server: Railo
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris, Windows Vista, Windows x64, AIX, Windows 7, Windows 2008
Related Issues:

FRS-299: Railo instances are not updated to the correct server type

[frs-299] Railo instances are not updated to the correct server type


This technote is about updating an instance of FusionReactor on Railo Express or Railo Server.

Description

Version 4.5.0 of FusionReactor Instance Manager will prompt you to update any existing instances when you have completed the Setup.

Previous versions of FusionReactor allowed you to add Railo as Jetty (Railo Express) or Tomcat (Railo Server) server. When FusionReactor Instance Manager scans for new target servers it will list these existing servers as Railo server in addition to the already existing Jetty and Tomcat servers.

This does allow the user to accidentally install a new FusionReactor instance to a server that already has FusionReactor installed. As a result the previous server will report itself as not connected. However, the new instance will work as expected.

Resolution

Do not install a new instance on a target server that has FusionReactor already installed (identify the belonging server by the directory listed behind the server).
Alternatively uninstall the FusionReactor instance from the Apache Tomcat resp. Jetty Server and re-install it on the appropriate Railo Server. Afterwards delete the Tomcat resp. Jetty server from the Instance Manager.

Whether your instance is installed on the Tomcat resp. Jetty server or the Railo server has no effect on functionality. Just make sure that you do not install it on the same server twice. Future versions of FusionReactor will display Railo server only and omit the Tomcat and Jetty servers if these represent a Railo server.

Issue Details

Type: Technote
Issue Number: FRS-299
Components: Installer, Instance Manager
Environment:
Resolution: Fixed
Last Updated: 22/May/12 5:27 PM
Affects Version: 4.5.0
Fixed Version: 4.5.1
Server: Railo
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris, Windows Vista, Windows x64, AIX, Windows 7, Windows 2008
Related Issues:

FRS-298: Instance Manager picks up the Tomcat based version of Railo twice

[frs-287] Instance Manager reports “Could not update web descriptor”


Symptoms

Customers attempting to add an instance of FusionReactor using the FusionReactor Administration Manager (FRAM) Instance Manager receive a dialog box with the following text.

Could not update web descriptor /path/to/descriptor/default-web.xml.

Clicking "Skip" or the close icon is the only available action. The instance is not added.

Analysis

We have tracked this issue to a problem when the J2EE server's runtime user is different to that of FusionReactor. This occurs usually when customers have locked down the J2EE server by changing its runtime user in Windows Services (for Windows) or by installing it as a non-root account in Linux or other Unix.

Because the web descriptor is owned by another user, FusionReactor is unable to access it to add a <filter> element. The dialogue box gives the full path to the file whose edit failed.

Resolution

We have developed a procedure to allow FusionReactor to coexist with J2EE servers with differing runtime users. It is part of FusionReactor's online user manual, and can be found at the following URL:

Installing FusionReactor in Locked Down Environments

Issue Details

Type: Technote
Issue Number: FRS-287
Components: Installer
Environment:
Resolution: Fixed
Last Updated: 10/Jan/12 5:12 PM
Affects Version: 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5
Fixed Version: Pending
Server:
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris, Windows Vista, Windows x64, Windows 2008
Related Issues:

[frs-286] Fixing a FR 4.0.4 installation so that it can be updated by later versions


Problem

Users who have installed FusionReactor 4.0.4 may not be able to upgrade their installations to a newer version due to a bug in the FusionReactor 4.0.4 installer. The problem only pertains to users who installed FusionReactor 4.0.4. The following procedure details a workaround for users who wish to avoid a complete uninstall of FusionReactor 4.0.4 and new installation of the later FusionReactor version.

Procedure

Windows

  1. Start the Windows Registry Editor and browse to the HKEY_LOCAL_MACHINE/SOFTWARE/ej-technologies/install4j/installations hive.








  2. Rename the value allinstdirs9866-5861-3195-1737 to allinstdirs7439-1350-6687-7781
  3. Rename the value instdir9866-5861-3195-1737 to instdir7439-1350-6687-7781








  4. Exit the Registry Editor
  5. Open the file i4params.conf located in the .install4j directory









    of your FusionReactor 4.0.4 installation in an editor.
  6. Find the two occurences of the string 9866-5861-3195-1737 and replace them with 7439-1350-6687-7781.
  7. Save the file and exit the editor to complete the procedure. You can now run the latest Setup to update your version 4.0.4 to the most recent version of FusionReactor.






Linux and Solaris

  1. Stop the FusionReactor daemon
  2. Become user root and execute the cd command to change to the home directory.
  3. If the file /etc/.java/.systemPrefs/com/install4j/installations/prefs.xml exists open it in an editor.
  4. If the files does not exist open the fallback file ./java/.userPrefs/com/install4j/installations/prefs.xml instead. It looks similar to the one shown below:
    </xml version="1.0" encoding="UTF-8" standalone=no"?>
    <!DOCTYPE map SYSTEM "http://java.sun.com/dtd/preferences.dtd">
    <map MAP_XML_VERSION="1.0">
      <entry key="allinstdirs9866-5861-3195-1737" value="opt/fusionreactor"/>
      <entry key="instdirs9866-5861-3195-1737" value="opt/fusionreactor"/>
    </map>
    
  5. Find the two occurences of the string 9866-5861-3195-1737 and replace them with 7439-1350-6687-7781:
    </xml version="1.0" encoding="UTF-8" standalone=no"?>
    <!DOCTYPE map SYSTEM "http://java.sun.com/dtd/preferences.dtd">
    <map MAP_XML_VERSION="1.0">
      <entry key="allinstdirs7439-1350-6687-7781" value="opt/fusionreactor"/>
      <entry key="instdirs7439-1350-6687-7781" value="opt/fusionreactor"/>
    </map>
    
  6. Open the file i4params.conf located in the .install4j directory of your FusionReactor 4.0.4 installation (typically /opt/fusionreactory in an editor.
  7. Find the two occurences of the string 9866-5861-3195-1737 and replace them with 7439-1350-6687-7781.
  8. Save the file and exit the editor to complete the procedure. You can now run the latest Setup to update your version 4.0.4 to the most recent version of FusionReactor.

Issue Details

Type: Technote
Issue Number: FRS-286
Components: Installer
Environment:
Resolution: Fixed
Last Updated: 08/Dec/11 6:58 PM
Affects Version: 4.0.4
Fixed Version: 4.0.5
Server:
Platform: Windows XP, Windows 2000, Windows 2003, Linux, Solaris, Windows Vista, Windows x64, Windows 7, Windows 2008
Related Issues:

[frs-278] How to get a thread dump from the JVM


Background

To assist in debugging potential issues it is sometimes necessary to generate a thread dump. This is a list of all threads in the JVM and their current stack of processing code.

Generating a thread dump

Preferred method: If you have access to FusionReactor, you can goto the "Resource->List All Threads" page in the left-hand menu, then click the "Stack Trace ALL" button at the top-right of the page.

Other ways to generate a thread dump differ depending on the platform:

Windows systems

  • Press Ctrl-Break in the command console you used to start your application.
    • If a command console isn't an option (eg when started as a service) you can use a tool like StackTrace to get a stack trace. At the time of writing, the licence allows free use when started with the JNLP Web Start option.
  • If you start your application with the com.sun.management.jmxremote option you should be able to attach jconsole and get a thread dump (JDK 5.0 or higher.)
  • There is a little tool called SendSignal which uses a clever trick to call the ctrl-break signal handler of any process.
  • JDK 5 & 6 offer tools for monitoring, management, and troubleshooting (jconsole, jps, jstat, jstatd, jinfo, jmap, jstack.)

Mac OS X

  • Press *Ctrl-* in the terminal console you used to start your application.
  • You can also generate a thread dump by sending the QUIT signal to the Java VM running your application kill -QUIT process_id where process_id is the process number of the respective java process.
    • Note: This method outputs the stacktrace to the standard output stream which may be redirected to a log file.
  • Thread dump by using gdb.
    • Attach to the target process with gdb and run the following command:
    • (gdb) call (void)pss()
  • The latest Apple 1.5 JVMs offer all the monitoring tools available for Linux and Solaris (jconsole, jps, jstat, jstatd, jinfo, jmap, jstack.)

Unix systems

  • Press Ctrl- in the terminal console you used to start your application.
  • You can also generate a thread dump by sending the QUIT signal to the Java VM running your application kill -QUIT process_id where process_id is the process number of the respective java process.
    • Note: This method outputs the stacktrace to the standard output stream which may be redirected to a log file.
  • JDK 5 & 6 offer tools for monitoring, management, and troubleshooting (jconsole, jps, jstat, jstatd, jinfo, jmap, jstack.)

Issue Details

Type: Technote
Issue Number: FRS-278
Components: Logging
Environment:
Resolution: Fixed
Last Updated: 08/Nov/11 3:01 PM
Affects Version:
Fixed Version: 4.0.0
Server:
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris, Windows Vista, Windows x64, AIX, Windows 7, Windows 2008
Related Issues:

[FRS-265] Windows Firewall blocking connections to FRAM


FusionReactor Setup

If Windows Firewall is enabled when installing FusionReactor 4.x the following warning message (or similar) is sometimes displayed when clicking 'Next' on the "FusionReactor Administration Manager (FRAM)" or "Configure Ports", screens in the Setup.


Windows Firewall Warning message

This is due to the FusionReactor installer testing if the selected ports (8087 and 8004 by default) are already in use, by attempting to bind to them. Windows Firewall will pick this up, and the above poup will be displayed. However, as this is only for the setup (for example FusionReactor_Windows_4_0_0.exe), it will not affect the FusionReactor Administration Manager, but only the Setup. Click 'Unblock' to allow the Setup to continue.

FusionRector Administration Manager (FRAM)

If Windows Firewall is enabled on the machine, this can cause issues for FRAM, when machines other than localhost attempts to access FRAM. Therefore in most cases an exception will need to be added in Windows Firewall, for whatever port FRAM is on (8087 by default).

The following procedure is for opening port 8087 for public access on Windows XP:

  • Open Windows Firewall (Control Panel -> Windows Firewall on Windows XP) and click the tab 'Exceptions'
  • Click the button 'Add Port'
  • Enter "FRAM" in the 'Name' field and the port FRAM is running on (8087 by default) in the 'Port' field.
  • Click the button 'Change scope' and select the appropriate access level.
    • Private – to allow machines only on the same network as FRAM are allowed to connect.
    • Public – to allow any machine to connect.

Windows Firewall: Add Port Exception


By following the guide above, Windows Firewall should now have been correctly configured to allow connections to the FusionReactor Administration Manager.

Issue Details

Type: Technote
Issue Number: FRS-265
Components: Installer
Environment:
Resolution: Fixed
Last Updated: Today 1:16 PM
Affects Version:
Fixed Version: 4.0.0
Server:
Platform: Windows XP, Windows 2000, Windows 2003, Windows Vista, Windows x64, Windows 7, Windows 2008
Related Issues:

FRS-418: FusionReactor Cloud Firewall DNS and Static IP address rules

[frs-256] FusionReactor Enterprise Dashboard 1.5 Release Notes and Resolved Issues



FusionReactor Enterprise Dashboard Rev. 1.5


RELEASE NOTES

Status: 9-Aug-2011

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.

Note: The new AIR Application is built / compiled using a different version of both Flex and AIR. The installer / updater is not compatible between the two, therefore any old version of the AIR client should be manually removed / uninstalled before the new (latest version – 1.5) version is installed.

RESOLVED ISSUES

Key Issue Type Summary
FE33 Improvement Non responsive hyper links
FE30 Bug Install for AIR Dashboard didn't work
FE28 Improvement Bring the styling of FR AIR Dashboard in line with new look & feel of FR 4.0

Issue Details

Type: Technote
Issue Number: FRS-256
Components: FR Enterprise Dashboard Desktop Application
Environment:
Resolution: Fixed
Last Updated: 09/Aug/11 2:07 PM
Affects Version:
Fixed Version: 4.0.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-207: FusionReactor Enterprise Dashboard 1.1.5 Release Notes and Resolved Issues

[frs-230] FusionReactor 3.5.x Release Notes and Resolved Issues



FusionReactor Rev. 3.5.x


RELEASE NOTES

Status: 17-Feburary-2011

Welcome to FusionReactor!

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 updates use the update page

RESOLVED ISSUES 3.5.5

Key Issue Type Summary
FR2001 Bug License/activation data corrupted due to concurrent access of multiple FR processes

RESOLVED ISSUES 3.5.4

Key Issue Type Summary
FR1836 Bug NullPointerException from JDBC on Railo on getMetaData in some cases
FR1958 Bug In some cases small AMF content is not flushed

RESOLVED ISSUES 3.5.3

Key Issue Type Summary
FR1744 Bug XML content in Railo breaks with a SAX Parser error (org.xml.sax.SAXParseException)
FR1747 Bug FusionReactor runs thousands of samples after it dehibernates (use schedule and not scheduleAtFixedRate)

RESOLVED ISSUES 3.5.2

Key Issue Type Summary
FR1724 Improvement AMF processor should handle a Target in the same way as a serviceName and serviceMethodName

RESOLVED ISSUES 3.5.1

Key Issue Type Summary
FR1704 Bug The Request Details button on the Slow Requests page did not work in FusionReactor 3.5.0. Pressing the Request Details button now correctly calls the Request Details page for requests shown on the Slow Requests page.
FR1706 Bug After a FusionReactor trail period had expired, FusionReactor used too many files handles and did not free them. File handles are now freed correctly. This issue did NOT affect FusionReactor installations that had a valid license, only installations where the trial period had expired and no license was uploaded.

RESOLVED ISSUES 3.5.0

Key Issue Type Summary
FR1648 New Feature Support for ColdFusion 9
FR1693 New Feature Support for Railo 3.1
FR1669 New Feature Support for JBoss 5.1
FR1692 New Feature Support for Windows 2008 Server R2
FR1681 New Feature Support for Windows 7
FR1670 New Feature Support for Mac OS X 10.6 "Snow Leopard"
FR1682 Improvement Support for Flash Player 10c and Flash Player 9 update 5
FR1676 Improvement FusionReactor Setup/Installer and Updater Support for 64 bit Windows machines
FR1667 Improvement FusionReactor's Flash content appears always on top when embedded in HTML in AIR. Use WMODE to correct the problem.
FR1666 Improvement Update Installation Guide
FR1664 Improvement Enhance FRAPI Request Surrogates to include more detail (see JavaDoc)
FR1660 Improvement Update FREM Release Candidate to the 3.5 CORE
FR1658 Improvement New AMF Deserializer implementation / Support for AMF handling Externalizable Objects
FR1650 Improvement FusionReactor Licencing support for AIX on JVM 1.5
FR1691 Bug Installer should select the "coldfusion" J2EE webapp by default when installing FusionReactor into ColdFusion 9
FR1687 Bug Crash Protection Alert Emails are not sent from FusionReactor instances installed in ColdFusion 9
FR1684 Bug Sockets used by FusionReactor's web server can enter CLOSE_WAIT indefinitely when invalid HTTP requests are received
FR1680 Bug Requests sometimes show "null" instead of the server name in CF9
FR1665 Bug Enterprise Dashboard should be able to cope with server names longer than 24 characters
FR1659 Bug Uninstall should only remove FusionReactor files
FR1657 Bug HTTP Post without headers causes a Java NullPointerException; FusionReactors web server can stop working
FR1643 Bug FusionReactor JDBC Wrapper as standalone JAR. It should be possible to place the FR JDBC Wrapper JAR in the same folder as the wrapped JDBC driver to avoid having to move JDBC drivers
FR1638 Bug Deadlock (out-of-order lock acquisition) between FusionReactor's JDBC driver and Metric Probe
FR1630 Bug JDBC Metrics are not tracked when no owning request can be found (eg. in CFTHREAD JDBC request)
FR1622 Bug Illegal State Exception / Response Has Been Closed with upstream Java app on Servet Forward/Includes in JRun. FusionReactor must not wrap a forward/include request if the the source request was already wrapped by FusionReactor.
FR1694 Bug A Race condition in stream data metrics could cause a CrashProtection Request Limit Email Notification to fail under extreme load conditions

Issue Details

Type: Technote
Issue Number: FRS-230
Components: Compression, Content Filters, CPU + Memory, Crash Protection, Enterprise Dashboard, FR Enterprise Dashboard Desktop Application, FusionReactor Settings, Installer, JDBC, License + Activation, Logging, Metrics, Request Managment, Thread Management
Environment:
Resolution: Fixed
Last Updated: 08/Aug/11 11:18 AM
Affects Version:
Fixed Version: 3.5
Server: ColdFusion 6, ColdFusion 7, ColdFusion 8, ColdFusion 9, Flex Data Services, JBoss, Jetty, JRun 4, LiveCycle Data Services, Railo, Resin, ServletExec, Tomcat, WebSphere, WebLogic
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris, Windows Vista, Windows x64
Related Issues:

FRS-214: FusionReactor 3.0.1 Release Notes and Resolved Issues

FRS-251: FusionReactor 4.0.x Release Notes

[frs-198] Problems with installing or activating a license


FusionReactor License and Activation Issues

Version Check

We recommend that you first make sure that you have the most current version of FusionReactor installed as recent updates include license and activation fixes. You can download the most current version from the FusionReactor download page.

Problems and how to fix them

Typical problems

In the following section, we list the most often reported problems with the FusionReactor license and activation process as seen from the user's perspective. The typical causes of these problems are discussed subsequently, along with the steps necessary to solve them.

  1. Restarting the server expires a trial license or activation period immediately
  2. Attempting to activate a license with an expired activation period redirects to the login page (but the license was not activated)
  3. Installing a license shows an error page saying Can not upload license: null
  4. Installing a license silently fails (you get redirected to the login page but the license was not installed)
  5. Loss of license activation after reboot on some multi-server installations of FusionReactor 3.5.1

Typical causes

  1. Insufficient privileges of the server account when trying to write to the Java System Preferences Backing Store.
  2. A Java6 VM on Linux or Solaris that has no fix for SUN JVM bug 6519088
  3. Firefox browsers occasionally corrupting the license during the upload
  4. Trying to activate a license without a connection to the Internet (bug FR1409).

How to fix it

Insufficient privileges

The runtime user of the server on which FusionReactor is installed requires read/write access to the Java System Preferences Backing Store. Depending on the operating system, the location of this data store is different. On Windows the data is stored in the registry hive HKEY_LOCAL_MACHINESOFTWAREJavaSoftPrefs, the data belonging to FusionReactor is in HKEY_LOCAL_MACHINESOFTWAREJavaSoftPrefscomintergralfusionreactor.
Page 14 of the FusionReactor Installation Guide provides you with instructions how to adjust the permissions of this store.
On Linux and Solaris the data is typically stored in the directory /etc/.java/.systemPrefs as a hierarchy of directories containing XML files. The data belonging to FusionReactor is in the directory /etc/.java/.systemPrefs/com/intergral/fusionreactor. To set the necessary permissions execute the following command as user root:

chmod -R 777 /etc/.java/.systemPrefs

Alternative locations of the System Preferences Backing Store

Some JVMs try to create the System Preferences Backing Store in the directory $JAVA_HOME/.systemPrefs as a fallback solution if the directory /etc/.java/.systemPrefs cannot be created where $JAVA_HOME denotes the directory where the JVM itself is located (e.g. /opt/coldfusionmx/runtime/jre ).

We strongly recommend you to use /etc/.java/.systemPrefs as the one and only location of the System Preferences Backing Store. In case there is already data from other applications in $JAVA_HOME/.systemPrefs you should move it to /etc/.java/.systemPrefs and delete $JAVA_HOME/.systemPrefs afterwards (after you have adjusted the permissions of /etc/.java/.systemPrefs properly).

Clear the System Preferences Backing Store

If you attempt to install a license and you get the error message mentioned before:

Can not upload license: null

or simply

null

then you should stop the application server, clear the content of the Java System Preferences Backingstore and restart the application server.

On a Windows machine run the registry editor (regedit.exe or regedt32.exe) and then delete the key

HKEY_LOCAL_MACHINESOFTWAREJavaSoftPrefscomintergralfusionreactor

On a UNIX machine as user root delete the directory

/etc/.java/.systemPrefs/com/intergral/fusionreactor

If the permissions are configured correctly uploading a license and activating it will work properly afterwards.

On MacOS the System Preferences are stored as a set of *.plist files under the /Library/Preferences folder. Once the application server has stopped delete the file /Library/Preferences/com.intergral.fusionreactor.plist to clear all Preferences belonging to FusionReactor.

SUN Java 6 VM bug 6519088

This bug has been introduced with version 6 of the Linux and Solaris SUN Java VM and unfortunately has not been fixed even in the recently released version 6.0_05. We have a technote available at https://www.fusion-reactor.com/support/kb/FRS-168.cfm which provides you with detailed instruction how to apply a fix for this bug.

Bypassing problems with Firefox

If you upload a license with Firefox and nothing seems to happen (except that you have to login again) check the reactor-0.log file for the typical error message (see also https://www.fusion-reactor.com/support/kb/FRS-45.cfm) shown below

...
javax.crypto.IllegalBlockSizeException: Input length must be multiple of 8 when
decrypting with padded cipher
at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
at com.sun.crypto.provider.SunJCE_h.b(DashoA12275)
at com.sun.crypto.provider.SunJCE_ae.b(DashoA12275)
at com.sun.crypto.provider.PBEWithMD5AndDESCipher.engineDoFinal(DashoA12275)
at javax.crypto.Cipher.doFinal(DashoA12275)
...

If multiple retries of uploading the license file again do not change this try to upload the license from a different browser and/or computer. If this does not help neither manually copy the license file to FusionReactor/license/license.lic and restart the server.

Making the manual activation process work

As mentioned in the overview of this document there is a hotfix available that fixes the bug FR1409 in the previous FusionReactor version 3.0.0 where a license can only be activated if the computer has a connection to the Internet. Download: fusionreactor-hotfix1409.zip. It comes as a ZIP file containing a new version of the FusionReactor Java library (fusionreactor.jar) together with instructions how to apply the fix. However, we recommend to upgrade to a newer version, which does not require this hotfix.

Issue Details

Type: Technote
Issue Number: FRS-198
Components: License + Activation
Environment:
Resolution: Fixed
Last Updated: 30/Jul/11 12:02 AM
Affects Version: 3.0, 3.0.1
Fixed Version: 3.0, 3.0.1, 3.5
Server: ColdFusion 6, ColdFusion 7, ColdFusion 8, ColdFusion 9, 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-45: Why can’t I upload my license file (using Firefox)?

FRS-168: FusionReactor trial expires immediately on a Java6 VM running on Linux or Solaris

FRS-204: Safari web browser fails to upload license

[frs-207] FusionReactor Enterprise Dashboard 1.1.5 Release Notes and Resolved Issues



FusionReactor Enterprise Dashboard Rev. 1.1.5


RELEASE NOTES

Status: 14-November-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
FE25 Improvement When a connection to the server is lost the system tray icons remain in sync with the dashboard (blue, amber or red)
FE23 Improvement The automatic undock functionality needs improving to notify users when a conncection is lost
FR1524 Improvement When a server has an expired license and the server is selected within the Enterprise Dashboard a runtime error is thrown
FR1542 Improvement Enterprise Dashboard lights up the [MEM] panel light when Crash Protection limits are reached. It should also light up a [CP]
FE24 Bug The FED does not always undock when a connection is re-established
FR1614 Bug The attributes of a server group can become invisible if the size of the avg request time is too large
FR1600 Bug Too many Crash Protection lights on Enterprise Dashboard
FR1567 Bug XML parser failure: element is malformed when watching ED and Installing a new license
FR1560 Bug When a server is shut down and the ED is running, the ED throws an error if you click on the OFFLINE + button
FR1550 Bug Implement new "trying to connect" alerting metric light [CP] panel light
FR1538 Bug The gauges for the groups within the Enterprise Dashboard seem to be showing invalid data
FR1536 Bug When a server is shut down and the Enterprise Dashboard is running, the Enterprise Dashboard throws numerous runtime / stream errors
FR1535 Bug The gauge and Graphs seem to be showing incorrect averages
FR1530 Bug When a server is not polled / connection then if the server is selected the Enterprise Dashboard throws runtime errors
FR1448 Bug The server links in the Enterprise Dashboard within FusionReactor fail: "Fhtml: Mode is invalid".
FR1436 Bug Dashboard displays incorrect uptime
FR1421 Bug Enterprise Dashboard Grouped server information memory graph shows the max memory in bytes but the units are KB. The value should be adjusted to be KB
FR1420 Bug Server uptime Field is blank when displaying long dates
FR1404 Bug Enterprise Dashboard + System Metrics use different names for the amount of Allocated Memory.
FR1401 Bug Enterprise Dashboard reports item currently being monitored has been grouped or removed when clicking on a ungrouped server during a refresh of the XML data
FR1213 Bug Mouse over issue on gauge "arrow" link
FR1170 Bug Sometimes Servers go RED when taking another server offline in the Enterprise Dashboard

Issue Details

Type: Technote
Issue Number: FRS-207
Components: FR Enterprise Dashboard Desktop Application
Environment:
Resolution: Fixed
Last Updated: 28/Jul/11 10:49 AM
Affects Version:
Fixed Version: 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: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Windows Vista
Related Issues:

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

FRS-256: FusionReactor Enterprise Dashboard 1.5 Release Notes and Resolved Issues