When FusionReactor attempts to obtain a stack trace, it instead displays the following message:
FusionReactor was unable to show you the stack trace but an attempt has been made to send the stack trace to the console or your runtime log file.
Customers deploying FusionReactor on JVM version 1.4 may also see a MethodNotFound exception in the runtime error log.
- The mechanism for obtaining stack traces was updated in FusionReactor 4.0.0 but an issue with where a temporary file is written caused the dump to fail.
- Due to an issue with how FusionReactor is linked to the virtual machine's runtime library, a mismatch in signatures between
FusionReactor and the VM library occurred.
Both issues are resolved with this hotfix for FusionReactor 4.0.3.
Customers with FusionReactor 4.0.3 only should apply the attached Hotfix 2540, which resolves the issue.
Instructions for applying the hotfix are supplied in instructions.txt within the hotfix zip file.
Customers with 4.0.x versions prior to 4.0.3 should use the latest 4.0.x install/updater package from the FusionReactor website to update their FusionReactor Administration Manager instance (and then the individual instances in Instance Manager), then apply this hotfix.
Hotfixes are cumulative: any future hotfixes on the FusionReactor 4.0.x stream, up to but not including the next minor point release (4.1.0), will contain this hotfix (and all earlier hotfixes since the last point release).
The installers/updaters for the next minor point release (4.1.0) and the next micro release (4.0.4) will roll up and install all previously-issued issued hotfixes.
- Hotfix 2539 ("Slow or fragmented networks can cause FusionReactor to under-read HTTP requests") for FR 4.0.3 documented by
After installation, FusionReactor's "About" page should identify itself as Revision: 4.0.3, Build: n/a.n/a.n/a (this is an ad-hoc build with no detailed build taxonomy).
~Hotfix FR2540- obf. (Stream:
|Last Updated:||12/Apr/12 3:33 PM|
|Affects Version:||4.0.0, 4.0.1, 4.0.2, 4.0.3|