Windows x64: Page 3

[frs-231] The Hostname in Request URL’s show “null” instead of the server name or IP address in ColdFusion 9


Due to an issue in the JRun version used with ColdFusion 9, the Hostname in Request URL's can sometimes contain the string "null" instead of the actual hostname.

Finished: 18:48:30.774 28-Sep-2009  200  192.168.0.11  11841  web-0  http://null:8500/test/test.cfm  0  Cur:(13%)67,809 Free:437,086

The problem occurs when a request is made against a port that is not the default port (e.g. 80) and the port number is not included in the HTTP Host header sent to the ColdFusion server by the web client. For example:

http://server.yourdomain.com:8500/test/test.cfm

Some web clients incorrectly do not include the port number in the Host: header that is sent for the request. For example:

GET /test/test.jdbcfast.cfm HTTP/1.1
Host: server.yourdomain.com
User-Agent: Mozilla/4.0 (compatible; MSIE 4.01; Windows 98)
Accept: */*
Accept-Encoding: gzip, deflate
Accept-Language: en-us
Connection: Close

This problem has been confirmed for Microsoft Web Application Stress (which does not send the port number in the Host header), but other clients may suffer from the same bug.

Workaround

To work around the issue you should use the default web port (e.g. 80), or use a different client that correctly sends the port number in the Host: header of HTTP requests.

A bug report has been submitted to Adobe for this issue.

Issue Details

Type: Technote
Issue Number: FRS-231
Components: Request Managment
Environment:

Windows XP (Darren’s laptop)
ColdFusion GM2
Via internal webserver.

Resolution: Won’t Fix
Last Updated: 30/Sep/09 1:55 PM
Affects Version: 1.0, 2.0, 2.0.3, 2.0.4, 3.0, 3.0.1, 3.5
Fixed Version: Pending
Server: ColdFusion 9
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris, Windows Vista, Windows x64, Windows 7, Windows 2008
Related Issues:

[frs-222] Log messages are not written to the associated log file


Hotfix 1640 for FusionReactor 3.0.1 – Description

This technote describes a fix for a condition under which FusionReactor log files are written to STDOUT or a Resin log file instead of being written to the associated log file.

Symptoms

When FusionReactor is installed on the Caucho Resin 3.x application server with virtual hosts configured (called 'webs' by Railo) the request, jdbc and crashprotection log messages are processed by Resin only but no written to the associated FusionReactor log file.

Analysis

The issue occurs because of the way the Resin 3.1 application server manages the log handler objects used by FusionReactor. Analysis of this problem showed that these handlers could not be retrieved correctly in an environment using multiple Resin EnvironmentClassloader instances which resulted in log messages being written to the default log configured in Resin only.

Note

If you see FusionReactor messages written to STDOUT (or into a Resin log file) you may need to restrict the log configuration of the Resin server accordingly. The following definition in the resin.conf file

<!--- Logging configuration for the JDK logging API. -->
<log name='' level='all' path='stdout:' timestamp='[%H:%M:%S.%s] {%{thread}} '/>

should be changed to something like

<!--- Logging configuration for the JDK logging API. -->
<log name='com.caucho' level='all' path='stdout:' timestamp='[%H:%M:%S.%s] {%{thread}} '/>

so that the FusionReactor loggers are excluded.

Resolution

Customers with FusionReactor 3.0.1 only should apply the attached Hotfix 1640, which resolves this 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).

Included Hotfixes

  • Hotfix 1623, described by technote FRS-216
  • Hotfix 1630, described by technote FRS-218
  • Hotfix 1635, described by technote FRS-219
  • Hotfix 1638, described by technote FRS-220

Files

hotfix-FR-1640-1638-1635-1630-1623.FR-HEAD-1315.12791.zip

Taxonomy

After installation, FusionReactor's "About" page should identify itself as Revision: 3.0.2, Build: FR-HEAD.1315.12791.

~Hotfix FR 1640 – obf. (Stream: trunk, build 1315, SVN 12791)

Issue Details

Type: Technote
Issue Number: FRS-222
Components: Logging
Environment:
Resolution: Fixed
Last Updated: 19/Aug/09 3:26 PM
Affects Version: 3.0.1
Fixed Version: 3.0.1
Server: Railo, Resin
Platform: Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris, Windows Vista, Windows x64
Related Issues:

[frs-211] FusionReactor Setup shows an error dialog on Windows64


On Windows 64 FusionReactor Setup shows an error dialog saying that it cannot start because MSVCR71.dll was not found (see screen shot 1). Clicking on the OK button brings up another dialog saying the the install4j wizard could not find a Java(TM) Runtime Environment on your system (see screen shot 2).

This is a known issue with install4j 3.2 on Windows 64. To install FusionReactor simply click on the Download button on the second dialog, which will download a suitable Java(TM) Runtime Environment from the FusionReactor web site that allows you to proceed with the installation. Once you have downloaded a suitable Java(TM) Runtime Environment you can use the Locate button on the second dialog and choose the java.exe that has been downloaded before if you run FusionReactor Setup again.

Screenshot 1:

Screenshot 2:

Issue Details

Type: Technote
Issue Number: FRS-211
Components: Installer
Environment:
Resolution: Fixed
Last Updated: 20/May/09 5:14 PM
Affects Version: 3.0, 3.0.1
Fixed Version: Pending
Server: ColdFusion 6, ColdFusion 7, ColdFusion 8, Flex Data Services, JBoss, Jetty, JRun 4, LiveCycle Data Services, Railo, ServletExec, Tomcat, WebSphere, WebLogic
Platform: Windows x64
Related Issues: