Solaris: Page 5

[frs-27] I switched to Java 5 and now my ColdFusion MX application no longer works!


The FusionReactor 1.0 Setup initially included an option to switch the Java Runtime of the target ColdFusion server to Java 5.

However, Java 5 is not yet certified by Macromedia for use with ColdFusion MX 6 or 7 and there are several ColdFusion MX features which do not work correctly under Java 5 (Such as query of queries with a datestamp in the where clause.) . For this reason this feature is not longer supported.

Issue Details

Type: Technote
Issue Number: FRS-27
Components:
Environment:
Resolution: Fixed
Last Updated: 18/Jun/07 6:00 PM
Affects Version: 1.0
Fixed Version:
Server: ColdFusion 6, ColdFusion 7, JRun 4
Platform: Windows XP, Windows 2000, Windows 2003, Linux, Solaris
Related Issues:

FRS-100: I want to run ColdFusion MX 6 resp. ColdFusion MX 7 on a recent Java VM. Adobe doesn’t support this yet. Some forums that I’ve visited, state that if I have FusionReactor, it will be possible to run coldfusion on Java 5. Is this true?

[frs-151] Does fusion reactor support CFMX7 enterprise war deployment on tomcat 5.5?


FusionReactor 1.0 does support Tomcat 5.


Note: We recommend using FusionReactor 2.0 which fully supports Tomcat and JBoss servers.

Please use one of the following packages for installation:

https://www.fusion-reactor.com/builds/FusionReactor-windows-1.0.7.zip
https://www.fusion-reactor.com/builds/FusionReactor-linux-1.0.7.tgz
https://www.fusion-reactor.com/builds/FusionReactor-generic-1.0.7.zip
https://www.fusion-reactor.com/builds/FusionReactor-generic-1.0.7.tgz

The following documents detail the procedure of installing and configuring FusionReactor on a Tomcat 5 server under Windows and Linux:

https://www.fusion-reactor.com/pdf/FR11-Tomcat5-Windows.pdf
https://www.fusion-reactor.com/pdf/FR12-Tomcat5-Linux.pdf

If you don't want to install FusionReactor global to all web applications you can alternatively copy the fusionreactor.jar file to the WEB-INF/lib folder of the ColdFusion deployment directory and configure the filter in the web descriptor WEB-INF/web.xml of the ColdFusion web application.

Issue Details

Type: Technote
Issue Number: FRS-151
Components: Installer
Environment:
Resolution: Fixed
Last Updated: 18/Jun/07 5:58 PM
Affects Version: 1.0
Fixed Version: 1.0
Server: ColdFusion 6, ColdFusion 7, JRun 4, Tomcat
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris
Related Issues:

[frs-146] As CFMX6 already have FR running with it, in order to upgrade I uninstalled FR, rebooted, updated CF and then reinstalled FR against CFMX7, would that be the recommended approach for CFMX6->7 upgrades?


The way that the update from ColdFusion MX 6 to ColdFusion MX 7 and uninstalled/reinstalled FusionReactor 1.0 is (at this time) the most recommended way to accomplish this process.

The reboot is only necessary if you use the Java 5 VM coming with FusionReactor 1.0 to run the ColdFusion MX server on. So, yes it is possible to uninstall FR without a reboot.

FusionReactor 2.0 introduced a complete new installer which supports multiple instances on JRun and other servers (FLEX, Tomcat, JBoss,…).

Issue Details

Type: Technote
Issue Number: FRS-146
Components: Installer
Environment:
Resolution: Fixed
Last Updated: 14/Jun/07 5:21 PM
Affects Version: 1.0
Fixed Version: 1.0
Server: ColdFusion 6, ColdFusion 7
Platform: Windows XP, Windows 2000, Windows 2003, Linux, Solaris
Related Issues:

[frs-91] I have enabled Timeout Protection to abort and notify after a period of time. However it does not seem to be killing requests that run for longer than the defined time. Am I missing something?


The problem that you are seeing is most likely that the requests don't complete because they are waiting to send data to the browser. This is done via a socket which is a piece of native code that the server uses to return the CF page contents. It can happen however that the browser that is receiving the content keeps the connection open but doesn't consume any of the content sent by the server. This causes the situation that you see. FusionReactor unfortunately cannot kill these requests because of a limitation in Java itself that native code cannot be stopped. This is a known limitation of Java and there is no way around this in any of the current versions of Java.

Internet Explorer can create this problem due to a bug that it has of keeping the connection open when the window has been closed.

Issue Details

Type: Technote
Issue Number: FRS-91
Components: Crash Protection
Environment:
Resolution: Fixed
Last Updated: 14/Jun/07 4:03 PM
Affects Version: 1.0, 2.0
Fixed Version: 1.0, 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-131] I have installed FusionReactor 2 on a system that had FusionReactor 1 installed before and now it does not start again


This issue is caused by an obsolete entry of fusionreactor.jar (belonging to FusionReactor 1.0.x) in the server classpath. In the server log file you see messages like the following:

Jun 28, 2006 9:27:26 AM com.intergral.fusionreactor.D.H A
INFO: ** Initializing Logs & Configuration (Wed Jun 28 09:27:26 PDT 2006)
Jun 28, 2006 9:27:26 AM com.intergral.fusionreactor.D.H A
INFO: Loading configuration from D:FusionReactorinstance81c_cfmx1.jrun4.xd0481cconfreactor.conf...
Jun 28, 2006 9:27:26 AM com.intergral.fusionreactor.D.H A
INFO: Configuration: no settings.fri available.
Jun 28, 2006 9:27:26 AM com.intergral.fusionreactor.D.H A
INFO: Initialization failed: Key jdbc.logfile.dumpsize is unknown to this configuration.
ConfigurationInvalidException [reason, key, value, specials, message]EXCEPTION_TYPE_KEY_UNKNOWN, jdbc.logfile.dumpsize, null, null, Key jdbc.logfile.dumpsize

If you have manually installed FusionReactor 2.0.x check that any old versions of fusionreactor.jar have been removed from the server classpath. FusionReactor 1.0.x typically has been added to the server classpath by a modification to the jvm.config file of the server.

Issue Details

Type: Technote
Issue Number: FRS-131
Components: Installer
Environment:
Resolution: Fixed
Last Updated: 14/Jun/07 3:03 PM
Affects Version: 1.0, 2.0
Fixed Version: 1.0, 2.0
Server: ColdFusion 6, ColdFusion 7, JRun 4
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris
Related Issues:

[frs-77] I have Installed ColdFusion on WebSphere. Is there a way to install FusionReactor, to monitor ColdFusion on this environment?


Issue Details

Type: Technote
Issue Number: FRS-77
Components: Installer
Environment:
Resolution: Fixed
Last Updated: 14/Jun/07 2:50 PM
Affects Version: 2.0
Fixed Version: 2.0
Server: ColdFusion 6, ColdFusion 7, ColdFusion 8, WebSphere
Platform: Windows XP, Windows 2000, Windows 2003, Linux, Solaris
Related Issues:

FRS-89: Can FusionReactor workwith ColdFusion MX J2EE when installed on websphere 5.1.1, if so are there any deployment instructions?

[frs-127] The trial period of FR2.0 is over and I want to return to FR1.0. The uninstaller for FR2.0 appears to be GUI only but the development server is headless. What is the best manual process for uninstalling FR2.0 and restoring FR1.0?


To manually remove FusionReactor 2.0.x and switch back to a previously installed FusionReactor 1.0.x do the following (assuming you use JRun4 installed in directory /opt/jrun4):

  1. Stop the server
  2. Edit /opt/jrun4/servers/coldfusion/SERVER-INF/default-web.xml and change the servlet filter definition for FusionReactor 2.0.x so that it points to the reactor.conf file of FusionReactor 1.0.x (typically in /usr/local/fusionreactor/conf).
  3. Delete the FusionReactor 2.0.x library fusionreactor.jar from the /opt/jrun4/servers/coldfusion/SERVER-INF/lib directory
  4. Make sure the classpath of your server knows how to find the FusionReactor 1.0.x jar file. Either add it to jvm.config (which is what the FusionReactor 1.0.x installer does) or copy it into the /opt/jrun4/servers/coldfusion/SERVER-INF/lib directory.
  5. To make the FusionReactor native library work correctly make sure that the directory containing the file libFusionReactor.so of FusionReactor 1.0.x is included in the LD_LIBRARY_PATH variable or add it to the java.library.path property in jvm.config.
  6. Restart the server.

Issue Details

Type: Technote
Issue Number: FRS-127
Components: Installer
Environment:
Resolution: Fixed
Last Updated: 14/Jun/07 2:49 PM
Affects Version: 1.0, 2.0
Fixed Version: 1.0, 2.0
Server: ColdFusion 6, ColdFusion 7, JRun 4
Platform: Linux, Solaris
Related Issues:

[frs-153] If I purchase your product, are you able to install it for me?


We offer automated installation packages as well as manual installation packages of our software that can be used on Windows, Linux, MacOS and Solaris platforms.
We will of course provide you with installation support for the product if you require. We are unable to install the software directly for you as we do not have access to your computer systems from within our company. The installation process is quite simple and as we mentioned we would be glad to provide you with support during the installation process.

Issue Details

Type: Technote
Issue Number: FRS-153
Components: Installer
Environment:
Resolution: Fixed
Last Updated: 14/Jun/07 12:20 PM
Affects Version: 1.0, 2.0
Fixed Version: 1.0, 2.0
Server:
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris
Related Issues:

[frs-98] I did a manual Install of FusionReactor and cannot see the current instance in the Enterprise Dashboard afterwards


If you do a manual installation it is normal that the current instance is not listed in the Enterprise Dashboard.

To add any FusionReactor instance (remote or local) you can use the Manage Servers page in the Enterprise menu:

1) Give the instance that you want to add a name
2) Enter the URL to the instance, e.g. http://<your hostname>:8088/fusionreactor
3) Enter the password
4) Check the status is set to 'Online'
5) Click 'Add Server' to add the new FusionReactor instance to the Enterprise Dashboard.

To install a new local FusionReactor instance from the Administrator you can use the Instance Manager. On manual installations of FusionReactor you have to scan for any appropriate target servers first (this is done by the automated setup for you). Either manually add the server by choosing the type and the directory in which the server is installed (e.g. /C:/ColdFusionMX7, /opt/jrun4) and click on the 'Add Server ' button afterwards or let FusionReactor scan you system for you. Therefore you have to specify the directory from which the search should start and the number of sub directories the search should follow.

Once you see a list of target servers you can click on the green button to install a new instance of FusionReactor on the server. Give the new instance a name, a port for the internal web server and a password, then click 'Install Instance' to install it.
Note: if you use the same name and port as you have used in the manual installation (typically default and 8088) you can update your current instance. You can then click on the blue button to add the instance to the Enterprise Dashboard. Afterwards all buttons of this instance will be disabled (because it is the instance you are running on and you should not be able to delete it). Open the Enterprise Dashboard and you should see your instance.

Issue Details

Type: Technote
Issue Number: FRS-98
Components: Installer
Environment:
Resolution: Fixed
Last Updated: 14/Jun/07 11:54 AM
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: