We have confirmed this is not a deadlock – FusionReactor does complete the startup procedure, though this can be radically longer than usual.

Resolution and Instructions For Applying Hotfix

We have confirmed this as a bug, and are supplying a hotfix for customers experiencing this issue.

Instructions.

The hotfix should applied only to FusionReactor 4.5.5. Please update if necessary.

Stop FRAM

On Unix, this is done using /etc/init.d/framd stop

On Windows, this is done using the Services control panel, by stopping the FusionReactor AM Service.

Stop all J2EE containers into which FusionReactor has been installed.

For each instance in the FusionReactorinstance<INSTANCE> folder (including FRAM):

Within the instance folder, locate the osgienvsys folder.

This folder will contain a fr-osgi-frameworkhost-1.0.1.jar file. Delete this file.

Copy the attached fr-osgi-frameworkhost-1.0.2.jar into this folder.

Perform the same procedure for the instance template, which can be found in FusionReactoretcosgi-templateosgienvsys

This folder will contain a fr-osgi-frameworkhost-1.0.1.jar file. Delete this file.

Copy the attached fr-osgi-frameworkhost-1.0.2.jar into this folder.

Restart FRAM. It should be available within a few seconds.

Restart instances.

Cumulative Hotfixes

Hotfixes are cumulative: any future hotfixes on the FusionReactor 4.5.x stream, up to but not including the next minor point release (4.5.6), will contain this hotfix (and all earlier hotfixes since the last point release).

We may decide, at our discretion, to release a full suite of installers on the 4.5.x maintenance stream at some future point. This will also incorporate hotfixes whose version numbers are the same or less than that of the installer. This means that this hotfix will be included in a potential future installer whose version is 4.5.6 or greater.