Home / Products / ColdFusion / Support / Release Notes
Macromedia ColdFusion Support Center - Known Issues

ColdFusion MX for J2EE Application Servers
Phase 2
Known Problems

Last Updated December 11, 2002

These notes list known issues with the second release of ColdFusion MX for J2EE Application Servers. They contain the information about known issues in the following areas:

Specific J2EE Application Servers
Configuring Data Sources in ColdFusion MX
Web Services
ColdFusion MX Administrator
Graphing in ColdFusion MX
Verity Searches
Other Known Issues

Note: The latest changes to the ColdFusion MX documentation are listed on the Documentation Updates page (TechNote 22811) and the Documentation Additions page (TechNote 22993) on the Macromedia website.


ColdFusion MX for J2EE on Specific J2EE Application Servers

The following table describes known issues that affect only specific application servers with the second release of Macromedia ColdFusion MX for J2EE Application Servers.

Note: Some issues listed in sections that follow this table also apply only to specific application servers.

Application Server Issue ID
IBM WebSphere V5 If you undeploy ColdFusion MX from Websphere 5, a timeout period in the Administrative console can occur before WebSphere completes deleting all files. As a result, you might get the following error message :

    The timeout has been exceeded but the operation may still complete.

The undeployment process does complete, although some files might remain in the cf_root directory. You can normally ignore this error message.
IBM WebSphere V4 If you install and deploy ColdFusion MX for WebSphere 4 (the first J2EE release) on WebSphere 4 Advanced Edition Single Server, you cannot use the IBM administrator web client to stop the ColdFusion MX application. You must stop the J2EE application server. This problem does not occur if you use the Java-based administrative console, and does not apply to WebSphere 4 Advanced Edition. You can prevent this problem by installing the second J2EE release and deploying ColdFusion MX as an EAR file. For information on installing the second J2EE release software on WebSphere 4, see the J2EE server certification and installation page on the Macromedia website. 48314
IBM WebSphere V4 on AIX The cfexecute tag can cause the application server to spawn a zombie process that consumes 100% of the CPU. This problem only occurs with IBM WebSphere 4 versions prior to 4.0.5 running on AIX, and is IBM issue number 84949001866. To resolve this issue, install IBM WebSphere 4 PTF 5. Alternatively, you can obtain from IBM an updated version of the JDK that resolves this issue when used with WebSphere 4.0.4. 48911
Sun ONE AS 7 J2EE native data sources that are defined at the application server level must are accessible to ColdFusion MX only if they are given a JNDI name that begins with jdbc/ or are at the root level of the naming tree. Therefore, names such as jdbc/mydatasource or mydatasource are valid, but names such as datasources/mydatasource, or /mydatasource are not valid. 49083
BEA WebLogic 7

The instructions for installing ColdFusion MX for J2EE on BEA WebLogic 7 contain two errors:

  • To enable access to COM objects, you must move the jintegra.jar file from the cf_root\WEB-INF\cfusion\lib directory to the cf_root\WEB-INF\lib directory.
  • You do not need to add the following line to wldomain_root/startWebLogic.cmd for COM support:
Sun J2EE 1.3.1 reference implementation To run ColdFusion MX for J2EE on the Sun J2EE 1.3.1 reference implementation application server, the server.policy setting must match the coldfusion.policy setting. 49150

Back to Contents



The following table describes the known localization issues in ColdFusion MX.


  • In this section, "double-byte" refers to specific double-byte encodings that are used for Asian languages (for example, shift_jis and euc_kr).
  • In this section, cf_root refers to the directory in which ColdFusion MX is deployed.

Issue ID
On the Tomcat application server, the getlocale function ignores the Accept-Language header and returns "English" by default, even if the Accept-Language header is set to another locale. However, if you use the setlocale function to set the locale, the getlocale function returns the locale value that you set. 49061

ColdFusion MX for J2EE Application Servers uses the application server's default character encoding when it compiles ColdFusion pages into Java.

You can specify the character encoding to use for all pages by specifying the encoding in the JVM options for your application server. For example, the following application server JVM option specifies the Microsoft Windows Japanese character encoding:


However, you must force ColdFusion to recompile all pages before this switch will take effect. To force recompilation, stop ColdFusion, delete the contents of the cf_root\WEB-INF\cfclasses directory, and restart ColdFusion.

Note: You can also use the cfproccessingdirective tag to specify the character encoding for individual pages. This technique automatically causes ColdFusion to recompile the page.

When submitting data through a form using the post method, and when enctype="multipart/form-data", character encoding is not handled correctly. To remedy this, use code like the following example instead of using SetEncoding:

function getMultipartFormParameter(key, encoding)
	param = key.getBytes(encoding);
	value = evaluate(toString(param, "ISO-8859-1"));
	param = value.getBytes("ISO-8859-1");
	return toString(param, encoding);
When using the SUN JRE 1.3.1 on an English (UK) locale, the LSIsDate function returns False for a date that has a one-digit month or day (for example, 1/1/01). To work around this, insert a zero in a one-digit month or day (for example, 01/01/01). 38440
The ParseDateTime function does not handle Japanese formatted dates in ColdFusion MX. You must use the LSParseDateTime function when using Japanese dates. 34000
ColdFusion MX does not support using double-byte characters in hyperlink href attribute text. 36913
You cannot use cfinclude to include a file with a double-byte filename. 36910
If an invalid mask is passed into the LSTimeFormat or LSDateFormat function (for example, "dd-mm-yymm"), the function outputs the invalid characters in both ColdFusion 5 and ColdFusion MX. However, ColdFusion 5 delimits each character of the output with an apostrophe (') character. 36388
The Encrypt and Decrypt functions do not work with double-byte character sets. If you pass a string containing double-byte characters to the Encrypt function, and later pass the encrypted value to the Decrypt function, the string is not properly decrypted. 38614
When reading and writing a binary file, you should specify ReadBinary in the action attribute of the cffile tag and then create the new file, as the following example shows:

<cffile action="ReadBinary" variable="x" file="c:\input-binaryfile">
<cffile action="write" output="#x#" file="c:\output-binaryfile">

On computers that do not use a Cp1252 file encoding by default (like computers that are set to work with Japanese), specifying action="read" in the cffile tag for a binary file corrupts the file.
If you are using the Microsoft Access driver or ODBC Socket driver on a multi-byte Windows operating system, you must do the following to support multi-byte characters:
  1. Start the ColdFusion MX ODBC Server and ColdFusion MX ODBC Agent services, if they are not already running.
  2. In a command prompt, enter the following command:
    cf_root\db\slserver52\admin\setcp.bat OS
  3. Stop the ColdFusion MX ODBC Server and ColdFusion MX ODBC Agent services.
  4. Start the ColdFusion MX ODBC Server and ColdFusion MX ODBC Agent services.

The setcp.bat file sets the service code page for the ODBC server used by the Access and ODBC socket drivers. It takes one parameter. If you specify OS, the ODBC server uses the operating system code page. Specify OS for multi-byte character set operating systems like Japanese. If you specify value other than OS as the parameter, or omit a paramter, the ODBC service code page is set to the default state, no setting. The Default setting supports only 8-bit character sets.

In the Japanese version of ColdFusion MX, using Verity to index and search double-byte characters (for example, Japanese text) is not supported on Solaris or Linux. 37650

For information about localization changes from ColdFusion 5 to ColdFusion MX, see the Locales section of Migrating ColdFusion 5 Applications.

Back to Contents


Configuring Data Sources in ColdFusion MX

The following table lists the known issues for configuring data sources in ColdFusion MX.

Issue ID
(Windows only) You must provide a username for Microsoft Access and ODBC Socket Data Source Names (DSNs), even if the data sources do not require any user authentication. Provide a username as follows:
  • Access DSN –Select the Use Default Username option; OR show the Advanced Settings section and enter a username in the ColdFusion Username field.
  • ODBC Socket DSN –Select the Use Trusted Connection option; OR show the Advanced Settings section and, in the Username field, accept the default username (system) or enter a username.

ColdFusion MX Administrator looks in the following JNDI locations for JDBC data sources configured at the application server level:

1: ""
2: "/"
3: "jdbc"
4: "java:comp/env/jdbc"

The ColdFusion MX Administrator does not list data sources that are configured at the application server level in other locations in the JNDI tree; however, you can use data sources that are listed elsewhere by specifying the data source's fully qualified JNDI name in any ColdFusion tag that takes a data source name, for example, cfquery.

If you do a standard installation of ColdFusion MX for J2EE on Windows, the example applications can access the sample data sources only if you install support for ODBC data sources when you run the startup wizard. 49103
The JDBC driver for Oracle has a 16-character limit for user passwords. 49021
When using Microsoft Access as a client variable data repository, an error is generated if the cumulative size of client variables exceeds 255 characters. 45548
The JDBC Microsoft SQL Server driver in ColdFusion MX does not support SQL Server 6.5. If you run a query using this driver, the following error is thrown:
The SQL statement [ select 1 ] caused an database query exception.

java.sql.SQLException: [Microsoft SQL Server] Login failed.
RAW_TRACE at coldfusion.tagext.lang.IncludeTag.doStartTag(Unknown Source)
PROBLEM java.lang.NumberFormatException: at coldfusion.tagext.lang.IncludeTag.doStartTag(Unknown Source)
You must add the following line to the connect string for a DB2 Data Source Name (DSN) (under Advanced Settings in the ColdFusion MX Administrator):

where pkgname is the name of the package (maximum of 7 characters) that the driver uses to process SQL statements.

If neither a CollectionID or packageName already exists, set CreateDefaultPackage=true for the first connection, and then modify the data source and set CreateDefaultPackage=false.
For the JDBC drivers provided with ColdFusion MX for DB2 and Informix, there is a problem with the SetTransactionIsolation method that prevents ColdFusion MX from dropping dead connections from the database connection pool before the connection timeout expires.

If you get the following error message repeatedly when a ColdFusion page connects to a database, deselect the Maintain Connections option for the data source:
[Macromedia][Oracle JDBC Driver]Connection reset by peer: socket write error
If you do not want to deselect the Maintain Connections option for performance reasons, you can lower the Timeout setting for the data source from the default of 20 minutes to 1 or 2 minutes. This way, if your database connections are dropped by a database server event, your ColdFusion MX server will recover in 1 or 2 minutes instead of 20 minutes.

Note: It is expected that this message appears once for every connection in the pool that has had its communication with the database server interrupted. However, for DB2 and Informix you continue to see the message until all the connections have timed out.
The Sybase JDBC connection requires a stored procedure on the Sybase server that does not get installed by default on Sybase 11.9 or higher. ColdFusion MX ships this stored procedure in the directory <install dir>/db/sybase. If, when creating a data source, you get an error message stating that procedure 'sp_default_charset' is not found, install the stored procedure on Sybase. 32230
Sybase servers that are configured to use the CP437 character set might fail to connect. If you receive the following error message when you try to connect to your Sybase server, you must update your \lib\macromedia_drivers.jar file.
[Macromedia][Sybase JDBC Driver]Character set CP437 not found in
(Windows NT 4.0, Windows 2000) To work with ODBC data sources, run a recent version of Microsoft Data Access Components (MDAC) and Jet. Otherwise, you might receive the following error:
Connection verification failed for data source: exampleapps [MERANT][SequeLink JDBC Driver] [ODBC Socket][Microsoft][ODBC Microsoft Access 97 Driver] Can't open database '(unknown)'. It may not be a database that your application recognizes, or the file may be corrupt. The root cause was that: null
You can download MDAC and Jet from the following locations:

Back to Contents


Web Services

The following table lists the known issues for using web services in ColdFusion MX.

Issue ID
ColdFusion MX does not support the .NET dataset data type. Ensure that you do not have a ColdFusion page consuming a .NET web service that expects a dataset argument. 39621
Consuming a ColdFusion Component (CFC) web service that returns a CFC instance throws a Class Not Found error when the CFC is in the virtual path. To work around this, refer to the CFC with the absolute path, not a relative path. 45505
To consume a web service that is implemented in a technology other than ColdFusion MX, you must set the following web service options:
  • Use rpc as the SOAP binding style and use encoding as the encodingStyle
  • Use document as the SOAP binding style and use literal as the encodingStyle
The following example shows a portion of the WSDL file for the BabelFish web service:

<binding name="BabelFishBinding" type="tns:BabelFishPortType">
  <soap:binding style="rpc" 
  <operation name="BabelFish">
    <soap:operation soapAction="urn:xmethodsBabelFish#BabelFish" />
      <soap:body use="encoded" namespace="urn:xmethodsBabelFish"
      encodingStyle="" />
      <soap:body use="encoded" namespace="urn:xmethodsBabelFish"
      encodingStyle="" />

The WSDL file for the BabelFish web service is compatible with ColdFusion MX because it uses rpc as the binding style and encoding as the encodingStyle.
You cannot use the cfinvoke tag attributes for username and password to invoke a secured web service. 37005
Avoid non-alphanumeric characters, such as the underscore character (_), in ColdFusion Component names, method names, and argument names. 44924
ColdFusion MX does not have access to files under web server virtual directories. For example, if a web server has a virtual mapping /myvirtual that points to c:/myvirtual, ColdFusion MX cannot include c:/myvirtual/index.cfm using the following call:
<cfinclude template="/myvirtual/index.cfm">
Also, if there is a component file c:/myvirtual/bank/account.cfc, you can access the file directly as a web service (http://myserver/myvirtual/bank/account.cfc?wsdl), or by using URL component invocation (http://myserver/myvirtual/bank/account.cfc?method=deposit&amount=300). However, the component file cannot be referred to by another component or cfml page as This is also true if such referring component would be invoked as a web service.

Either avoid web server virtual directories if the resource in these should be accessed internally by other ColdFusion MX resources, or create a ColdFusion mapping with the same name and location as the web server mapping.

Back to Contents


ColdFusion MX Administrator

The following table lists the known issues for the ColdFusion MX Administrator.

In this section, cf_root refers to the directory in which ColdFusion MX is deployed.

Issue ID
In the German version of ColdFusion MX Administrator, the online help for the general setting page is not properly formatted and is missing the << and >> navigation links. 49006
The ColdFusion MX Administrator online help includes several obsolete ColdFusion 5 help pages. These include documentation for a Manage Locking Variables Administrator page and for Advanced Security. ColdFusion MX does not have these features.


The online help for the ColdFusion MX for J2EE Administrator includes documentation on a Java and JVM page. This page does not exist in the ColdFusion MX for J2EE Administrator. 47986
The Administrator online help Register CFX Tags page is missing an Overview hyperlink. 48871
Several pages of the Administrator online help lack full navigation buttons.


The Overview link on the Administrator online help About the System Probes Page links to an obsolete ColdFusion 5 help page. It should link to CFIDE\administrator\help\probe_types.htm. 48869
The Administrator help Documentation page is obsolete for the second ColdFusion MX for J2EE release. Now, if you click Documentation on the top border of the ColdFusion MX Administrator navigation pane, you go to a page with links to download the ColdFusion online documentation. 48861
The Administrator must reside in its default installation path (.../CFIDE/administrator/) in order for it to function properly. N/A
If your default web browser has pop-up windows disabled, the ColdFusion MX Administrator might not run the first time after you install. To remedy this, enable pop-up windows in your browser and run the ColdFusion MX Administrator. After running the Administrator for the first time, you can disable pop-up windows in your browser again. 45481
On the System Probes page, if you change the URL, username, or password for probe.cfm, you must trigger an update for each existing probe by editing the probe and clicking Submit. 39738
You cannot archive or deploy the following: System Probes, CORBA Connectors, Web Services, and the following settings: Server Settings > Settings > Simultaneous Requests; Server Settings > Basic Security > Security Sandbox - Enable ColdFusion Security checkbox; Server Settings > Debugging > Enable Robust Exception Information, Enable Performance Monitoring, and Enable CFSTAT.

You cannot deploy Server Settings > Basic Security > CF Admin Password and RDS Password. This is intended behavior.
You cannot use single quotataion marks (') in named resources (for example, data sources, probes, Verity collections, and so on). Using a single quotation mark — for example, creating a scheduled task with name="Let's Rock" — causes a WDDX parsing error when the server restarts, and the service whose data contains the single quotation mark fails.

To remedy this, back up and edit the XML file for the failing service. For example, if the Cron service is failing after naming a scheduled task "Let's Rock", make a backup copy of cf_root\lib\neo-cron.xml and edit the original version of the file to change every instance of "Let's Rock" to "Lets Rock".
Currently, when you register or edit a CORBA connector, the Classpath field is not used. Instead, use your application server to specify CORBA (and all other) classpaths. 49380
In the Verity Collections page, when you map an unregistered collection, select the same language that was used to create the collection. Currently, if you select a different language to map to a collection, no error appears. However, if you map, or subsequently index, a collection in a language other than the one in which it was created, you might damage the collection's index and your ability to search the collection.

Examples of unregistered collections include:
  • Collections on another server
  • Collections created with mkvdk
In the ColdFusion MX Administrator, on the Debugging & Logging > Logging Settings page, the Use operating system logging facilities option does not work. If you select it, restarting your application server throws the following error:

    log4j:ERROR No syslog host is set for SyslogAppender named "null".
The URL to access the ColdFusion MX Administrator is case-sensitive: You must use http://server:port/context-root/CFIDE/administrator/index.cfm; you cannot use http://server:port/context-root/cfide/administrator/index.cfm. N/A
If you run ColdFusion MX Administrator using Internet Explorer on Apple OS X, the file browser applet does not display properly. 49067

Back to Contents


Graphing in ColdFusion MX

The following table lists the known issues for graphing in ColdFusion MX.

Issue ID
In the cfgraph and cfchart tags, ColdFusion MX only uses the values in the scaleFrom and scaleTo attributes as a starting point; ColdFusion MX considers the actual data values and the number of labels that need to be displayed and then determines the actual scaleFrom and scaleTo values. For example, ColdFusion MX adjusts the user-specified scaleFrom and scaleTo values to avoid cutting off decimal labels and data. 32837
If the legend for a pie chart contains long labels, the pie chart might appear distorted. To resolve this, increase its width by setting or increasing the value of the graphwidth or chartwidth attribute. 32835
The cffile tag has changed to use a different default encoding when writing to a file. Therefore, to write a generated graph to a file using the name attribute of cfchart, you now have to add the following attribute to the cffile tag: charset="ISO-8859-1". 38867

Back to Contents


Verity Searches

The following table lists the known issues for Verity searches in ColdFusion MX.

Issue ID
You may receive a directory checksum error untarring Verity locale packs on Solaris. To resolve this issue, install GNU Tar and use it to untar the archive.
You cannot index documents that contain double-byte characters using Verity when running Sun ONE Application Server 7 on Solaris. This problem is caused by an incompatibility in the versions of the shared library that ships with both Verity and Sun ONE Application Server 7.
In Windows, you cannot index collections when the combined path and collection name for the collection exceeds 91 characters. 45654
Some Verity functionality fails on RedHat Linux 7.3 and later due to the lack of backwards compatibility in the version 2.5+ glibc libraries included with those distributions. Verity is fully supported on Linux with glibc version 2.4.x and earlier. 47358
Verity does not support VSpider on Linux. Also note that Linux does not support PDF files.  
You might receive the following error when attempting to create a Verity collection or to migrate a Verity collection:

    Error: An error occurred while performing an operation in the Search Engine native     library. coldfusion.tagext.lang.CFCollectionTagException: Error # -10.

To work around this issue, locate the file [installdrive]:/winnt/system32/VDK200.DLL, and rename it to VDK200.dll_old. Restart the ColdFusion server. This is a conflicting file from a previous version of ColdFusion.

Back to Contents


Other Known Issues

The following table lists the general known issues in ColdFusion MX for this release:

Product Area Issue ID
Security Users logging in multiple times might end up with incorrect role assignments. 46672
The CF Service Factory class can be instantiated in CFML. 47545
On IBM WebSphere V4 and V5, sandbox security does not protect against unauthorized file and socket IO, including access using the cffile, cfdirectory, cfhttp, cfftp, or cfmail tags. For information on using a security manager to secure File IO, see the IBM Websphere Application Server documentation. 49329
On IBM WebSphere V5, you must enable a Java security manager for sandbox security changes to take effect immediately. Without a security manager enabled, changes to Sandbox security settings take effect when you restart the application server. 49284
On all application servers, sandbox security does not protect file and socket IO from Java access. To fully protect file socket IO, a security manager must be installed and running on the underlying applicaton server. Sandbox security does fully protect file and socket IO from access by CFML tags on application servers that have been tested to date, with the exception of IBM WebSphere. 48936
Macromedia Dreamweaver MX Component Browser The Macromedia Dreamweaver MX ColdFusion Component Browser will not function if you install ColdFusion MX for J2EE on your application server with a context root other than "/". The component browser only works if ColdFusion MX for J2EE is deployed at "/". 47665
Servlet invocation Only ColdFusion MX Server and ColdFusion MX for JRun 4 include support for invoking servlets in the ../WEB-INF/classes folder by their class name. This limitation is required to ensure security on all application servers.

If the application server has its invoker servlet enabled, then you can specify /servlet/classname to invoke the servlet. However, enabling the invoker servlet allows arbitrary code (that implements the Servlet interface) on the application server to execute. Therefore, most application servers don't allow this feature by default for security reasons. In this case, you can explicitly register the servlet in web.xml and map it to a URL, or you can can use the following CFML function invocation to execute a servlet by its name.

getRequest(), getPageContext().getResponse())

For more information on this issue, see TechNote 23468, ColdFusion MX for J2EE: Invoking Servlets by Class Name on IBM WebSphere or Sun ONE.

RDS On some application servers, RDS might work only if you deploy ColdFusion at the "/" context root. 48721

On a system that is running JDK 1.4, you might encounter an exception that looks like the following when you run ColdFusion MX:

    class file has wrong version 48.0, should be 47.0
    Please remove or make sure it appears in the correct subdirectory of the classpath

If you get this message, replace the tools.jar file in cf_root\WEB-INF\cfusion\lib with the tools.jar that ships with JDK1.4.

If you encounter java.lang.OutOfMemoryError errors, increase the JVM maximum heap size. This is a known issue with the Sun Java Virtual Machine and is listed in the Sun Bug Parade as #4697804. 49245
Documentation The installation documentation indicates that you must add the "-D java.awt.graphicsenv" JVM option to enable CFCHART functionality. This option is only needed on UNIX, and can cause problems with JDK 1.4.1. As a result, the cfcode tag might not work with JDK 1.4.1 on UNIX.
The standard ColdFusion documentation, including online help for the Administrator and all books except for the Installing ColdFusion MX, has not been updated for the ColdFusion MX for J2EE releases, and therefore includes information that does not apply to the J2EE releases. N/A
When defining a PointBase database file for the examples in the Getting Started Building ColdFusion MX Applications book, ensure that the Maintain Connections option is not selected. N/A
The search applet in the online version of the documentation does not work with Netscape version 4.75. 47534
If you are using ColdFusion MX for J2EE on a JVM where the default locale is set to Korean, most localizable ColdFusion MX elements are translated into Korean for convenience, but the installer, Administrator, and any documentation items specific to the J2EE Edition appear in English, because Korean is not officially supported in the J2EE Edition. 49277
Error messages The hyperlink "Check the CFML Reference Manual to verify that you are using the correct syntax" in error messages points to Cold Fusion documentation on the local server, which is not installed in the second release of ColdFusion MX for J2EE.

To make this link work, download and install the complete ColdFusion MX documentation set. For more information on downloading ColdFusion MX documentation, see cf_root/cfdocs/dochome.htm.

Memory usage ColdFusion MX requires more memory to run than ColdFusion 5.
For more information, see the system requirements listed in Installing ColdFusion MX.
Large ColdFusion pages ColdFusion pages that are larger than 500 KB can cause the following compilation error:
java.lang.IllegalStateException: unexpected constant at coldfusion.compiler.ClassReader.readCpool(
ColdFusion Components (CFCs) In this release, within a component <cfset x = 1> puts x in the Variables scope local to the component, and <cfset variables.x = 1> puts x in the Variables scope of the calling page.

After this bug is fixed, both <cfset x = 1> and <cfset variables.x = 1> will do exactly the same thing and put x in the Variables scope local to the component.

Until this bug is fixed, avoid using <cfset variables.x = 1>, because this would conflict with <cfset x = n> in the calling page.
When using components, or when interoperating with Java case-sensitive containers (for example, Hashtable), the dot notation fails to resolve the keys. For example, ( might not be found even though it exists, as in the following example:
<cfset newTC = createObject( "component", testComponent ) /> <cfset foo = /> To work around this, use the equivalent bracket notation; for example, (newTC["foo"]["moo"]).
Initializing arrays A heterogeneous array initializer, such as a[1]["moo"][1] (where a has not been defined), throws an exception. To work around this, assign the heterogeneous parts in separate assignment statements, as in the following example:
<cfset a1[1] = structNew()> <cfset a1[1]["moo"][1] = 12>
Server-side validation for post forms When using the ColdFusion server-side validation technique to validate post forms (for example, input type="hidden" name="myInput_require"), ColdFusion MX ignores the custom message that you place in the value field, and instead displays a message indicating that the field is required. 45443
Server-side redirects Using getpageContext().forward('<your page name>.cfm') to do a server-side redirect throws an "" error if there is any data in the Form scope. 45337
File Server Browser Applet The File Server Browser Applet (allaire.cfide.CFNavigationApplet) does not render icons properly in Netscape 4.x. 31958
User Defined Functions (UDFs) An error results if you have a UDF with N defined arguments, you pass N+1, and then call structKeyList with the arguments. The same error results if you have cfdump inside the function with an undeclared argument. 44635
cfhttp The cfhttp tag has some behaviors that are subject to the performance of the underlying Java Runtime Environment (JRE). For example, when using an IBM JRE, cfhttp does not properly connect to "https" URLs, but it does when using a SUN JRE. However, when using a SUN JRE, cfhttp does not always return a 404 status code page when an http request to a URL contains a nonexistent page, but it does when using an IBM JRE.

Finally, the timeout attribute does not work with the SUN JDK versions 1.3 and 1.3.1_03. For the timeout attribute to be functional, you must use JDK 1.4.0.
cfimport When importing custom tags using cfimport, you cannot use the namespace "CF" as this is reserved for ColdFusion custom tags. 45544
cfldap In ColdFusion MX, cfldap does not support SSL v3 client authentication (certificate authentication), as in ColdFusion 5. In ColdFusion MX, cfldap only supports SSL v2 (basic username/password authentication over SSL). 38693
CORBA invocations When using CORBA (VisiBroker 4.5), an "out" call for an array of structs or multi-dimensional array throws a CORBA_UNKNOWN exception. Use "inout" instead. This is a VisiBroker bug.  
When using the CORBA IOR method in CreateObject/cfobject, ensure that you use an IOR that has been obtained in the same environment as your deployment environment. VisiBroker IORs are not interchangeable. If you decide to deploy your CORBA server on a different computer, you must obtain new IORs. VisiBroker IORs contain IP address information. 36866
ColdFusion MX Administrator security settings If you enter a server IP address for sandbox security (under Sever/Ports) and forget the port number, you receive an error when you try to edit this entry. To work around this, delete the server IP address and re-enter it with the port number. 39860
Example applications (UNIX) You must disable security to use the PointBase data sources for the example applications on UNIX. 45527

Back to Contents