The issue occurs when JRun4 re-introduces a Java servlet request into itself, to satisfy one of the following conditions:
After experiencing this error, the thread in which the error occurs becomes invalid, and subsequent requests may receive a correct response, a blank web page, or one containing an error.
This issue has been shown to occur on FusionReactor installations located on JRun4 platforms on Windows XP Pro 32-bit, but may not be limited to this platform.
This issue occurs when the servlet platform attempts to re-run filters on requests which are being reprocessed during forward or include operations. A small change in the way FusionReactor 3.0.1 handles streams may expose this issue.
After the exception occurs, the JRun thread in which it occurred becomes stale. If it is reused for a subsequent request, further exceptions are logged.
Customers experiencing this issue with FusionReactor 3.0.1 only should apply the attached Hotfix 1623, which resolves the issue.
Instructions for applying the hotfix are supplied in instructions.txt within the hotfix zip file.
Hotfixes are cumulative: any future hotfixes on the FusionReactor 3.0.1 stream, up to but not including the next point release, will contain this hotfix (and all earlier hotfixes since the last point release).
After installation, FusionReactor's "About" page should identify itself as Revision: 3.0.1, Build: FR-FR301.1.12052.
Hotfix FR 1623 – obf. (Stream: branch FR301, build 1, SVN 12052)
|Last Updated:||12/Dec/08 4:43 PM|
Comments are closed.