These release notes contain important information available at the time of release of Sun Java™ System Active Server Pages 4.0.3 (formerly Sun™ ONE Active Server Pages and Sun Chili!Soft ASP). The release notes also contain installation instructions and information that will help you get started. Be sure to read this document before you begin using the product.
These release notes contain the following sections:
Sun Java System ASP 4.0.3 release support the Sun Java System Web Server 7.0 versions.
Sun Java System ASP 4.0.3 release support the Apache 2.2.x versions.
Sun Java System Active Server Pages (also referred to as Sun Java System ASP) is a platform-independent implementation of ASP technology. Sun Java System ASP 4.0.3 includes the following enhancements:
Support for Red Hat Enterprise Linux 3, Solaris™ 9 x86, Solaris™ 10 SPARC and x86, Windows 2003, HP-UX 11i, and AIX 5.1 and 5.2.
Updated DataDirect ODBC drivers . For more information about the updated driver suite, go to:http://www.datadirect.com/products/odbc/odbcrelhighlights/index.ssp
Support for MySQL database versions 4.0 and 4.1.
Streamlined installation. Serial numbers have been removed, and you no longer need to enter a license key during installation.
Support for access logging and the logging of HTTP errors. Enable or disable these from the Server Settings page of the Administration Console. You can also look in the casp.cnfg configuration file for lines that set asplogdir, asplogerrors, and asplogaccess:
asplogdir sets the directory to which ASP should write log files for HTTP errors and/or ASP page accesses.
asplogerrors and asplogacess work as binary flags to turn either or both of the log files on and off. The appropriate values are 0 and 1 and default to 0 at installation.
Support for custom error pages for the 400-range with both Apache and Sun Java™ System Web Server. If a custom error page is defined in the Web server configuration files, ASP redirects to that page for the corresponding errors (most commonly, 404 file not found).
Enhanced HTTP charset functionality. The HTTP charset attribute can now be set on an ASP-wide basis in the casp.cnfg file (or the registry on Windows). Previously, this had to be set on a page-by-page basis. The charset setting is under the [default machine] section in casp.cnfg. Examples of valid values include ISO-8859-1 and UTF-8. By default, ASP does not set charset on "text/html" pages. In that case, the browser picks up the Web server’s value.
Enhanced VBScript functionality. The following VBScript byte-related functions are now supported: LenB, InStrB, LeftB, RightB, MidB, ChrB, AscB. These functions behave largely as expected. However, there is one caveat you should be aware of regarding the byte-order and wide-character size of the operating system under which ASP runs in some situations. Following is an example scenario in which character width discrepancies would be experienced:
inchar = "A"
leftbyte = LeftB(inchar)rightbyte = RightB(inchar)
outchar = leftbyte & rightbyte
On Windows, outchar will contain "A" as expected. However, on Solaris or Linux, the character A in string "A" is represented by four bytes. So the above code would yield only half of a valid character. Namely, the first and last bytes of "A" without the two middle bytes. A browser will display garbage or its unknown character symbol if the broken character is passed to Response.Write.
You can determine the byte-length of a character by calling the VBScript LenB function as follows:
Response.Write LenB("A")
On Windows, two will be returned. On Solaris x86, Solaris SPARC, and Linux, four will be returned.
Please note the following:
The Apache Web Server is no longer bundled with Sun Java System ASP.
Sun Java System ASP 4.0.3 includes JRE 1.4.2_16 on Solaris x86, Solaris SPARC, Linux, Windows, 1.4.2 ca142-20070708 (SR9) on AIX and 1.4.2_18 on HP-UX.
MySQL is not supported on HP-UX and AIX.
The DBMS tool is not supported on HP-UX and AIX.
The Database Publisher tool is not supported when publishing to HP-UX and AIX.
Red Hat Enterprise Linux 2.1 support was deprecated in previous releases. With ASP 4.0.3, support for this platform is removed.
MySQL 5.x and 6.x database is not supported.
Sun Java System Web Server 6.0 is deprecated. Support for this version is removed.
AIX 5.1 and 5.2 is deprecated.
Solaris 9 and 10 x86 is supported. Solaris 9 x86 platform is deprecated. Future Sun Java System ASP releases will support only Solaris 10 x86.
Solaris 8, 9 and 10 SPARC is supported. Solaris 8 and 9 SPARC support is deprecated. Future Sun Java System ASP releases will support only Solaris 10 SPARC.
HP-UX 11iv1 PA-RISC 2.0 version is supported.
This section lists the hardware and software requirements for installing and running Sun Java System ASP 4.0.3. This section contains the following topics:
This section lists the installation requirements for Sun Java System ASP 4.0.3 for UNIX. This section contains the following topics:
Sun Java System ASP 4.0.3 for UNIX can be installed on UNIX and Linux. The following table lists the supported platforms.
Table 1–1 Supported Platforms for Sun Java System ASP 4.0.3 for UNIX
Operating System |
Processor |
Minimum Memory |
Minimum FreeDisk Space |
---|---|---|---|
Solaris 8, 9 |
SPARC |
512 MB RAM |
250 MB |
Solaris 9 |
AMD/Intel x86 |
512 MB RAM |
250 MB |
Solaris 10 |
SPARC |
512 MB RAM |
250 MB |
Solaris 10 |
AMD/Intel x86 |
512 MB RAM |
250 MB |
Red Hat Enterprise Linux 3.0 and 4.0 * See Product Notes |
AMD/Intel x86 |
512 MB RAM |
250 MB |
HP-UX 11i |
PA-RISC 2.0 only |
512 MB RAM |
250 MB |
AIX 5.1, 5.2 and 5.3 * See Product Notes |
PowerPC only |
512 MB RAM |
250 MB |
For optimal performance it is recommended that you update your operating system with the latest applicable patches. For UNIX platforms, the patch level should be the same as that applied for JDK 1.4.2_16 or higher.
Patch information is listed by platform:
For the Solaris platform, the recommended patch list can be found at http://sunsolve.sun.com/show.do?target=patches/JavaSE
For the HP-UX platform, the recommended patch list can be found at http://www.hp.com/products1/unix/java/patches/index.html
For the AIX platform, the following maintenance packages are recommended:
5100-04 (APAR IY44478)
5200-01 (APAR IY44479)
5200-02 (APAR IY44479)
5300-08-01 or higher
The following Web Servers are certified for the ASP 4.0.3 release.
Sun JavaTM System Web Server 6.1 SP 9
Sun Java System Web Server 7.0 Update 2
Apache 1.3.31
Apache 2.0.52
Apache 2.2.8
This section lists the installation requirements for Sun Java System ASP 4.0.3 for Windows. This section contains the following topics:
The following table lists the supported platforms for Sun Java System ASP 4.0.3 for Windows.
Table 1–2 Supported Platforms for Sun Java System ASP 4.0.3 for Windows
Operating System |
Processor |
Minimum Memory |
Minimum FreeDisk Space |
---|---|---|---|
Windows 2000 Professional, Windows 2000 Advanced Server SP4 |
AMD/Intel x86 |
512 MB RAM |
250 MB |
Windows XP SP2 Professional |
AMD/Intel x86 |
512 MB RAM |
250 MB |
Windows Server 2003 Enterprise Edition SP1 or above |
AMD/Intel x86 |
512 MB RAM |
250 MB |
This section describes how to install Sun Java System ASP. This section contains the following topics:
The setup program takes you through the steps required to install Sun Java System ASP. During installation you have many options to accept default configuration settings or to specify your own. The setup program installs the following components on the target Web server:
Sun Java System ASP Server
Sun Java System ASP Administration Console
If you are upgrading an existing installation of Sun Java System ASP, review Upgrading an Existing Installation before beginning your installation.
This section contains the following topics:
Before starting your installation, make sure you meet the following requirements:
You are logged in as root.
You have at least 250 MB of hard disk space available to extract the installation files.
Your hardware and software meet the requirements listed in System Requirements.
You know the language you want Sun Java System ASP to support. You can change the language after installation using the Sun Java System ASP Administration Console, as described in Managing the ASP Server > Configuring International Support in the product documentation.
If you choose to customize settings for the Sun Java System ASP Administration Console, you must specify a user name and password for accessing the console. Be sure to specify a password that you can remember, or else plan to store the password in a secure location. You cannot access the Administration Console without providing this password. If you choose not to customize settings, the user name is set as ’admin’ and the password as ’root.’ To protect the security of your server, you should change these from the defaults as soon as possible, as described in Using the Administration Console > Configuring Usernames and Passwords.
If you are upgrading from a previous version of the product, you must install Sun Java System ASP 4.0.3 in the same directory as your previous installation. Be sure to review Upgrading an Existing Installation for additional upgrade information.
If you are installing Sun Java System ASP from the CD-ROM, go to Step 2. If you are downloading Sun Java System ASP from the Web, download the file for your platform to a temporary directory and then extract the installation files using the following command:
gunzip -c <name.tar.gz> | tar xvf —This step creates a temporary directory, which can be deleted after completing the installation.
Run the install.sh script with the following command:
./install.sh
For downloaded versions, this script is located in the temporary directory you created in the previous step. For CD-ROM versions, this script is located on your installation CD-ROM.
Review the End-User License Agreement (EULA) that displays. Type ’yes’ if you agree with its conditions. You must type the entire word, yes.-or-Type ’no’ if you do not agree. The Sun Java System ASP setup program quits the installation.
Press Enter to accept the default Sun Java System ASP installation directory (/opt/casp). The installation files will then be extracted. - or - Enter the absolute path name of a different installation directory. Make note of this location so you can easily find the Sun Java System ASP files at a later time. To upgrade from a previous version of the product, you must specify the installation directory of your existing installation.
If the setup program detects a previous installation of Sun Java System ASP in the specified directory, you will be prompted to uninstall the previous version. If a previous installation is not detected, you will go to the next step. Make your selection and then follow the prompts.
Press Enter to accept the default language (English - United States). - or - Enter the number of a language shown in the list.
Specify the desired search option for choosing the Web server to configure with Sun Java System ASP, then follow the prompts for your selection.
After selecting and verifying information about the Web server, choose a configuration option for the ASP Server, and then follow the prompts for your selection.
Select a configuration option for the Administration Console, and then follow the prompts for your selection. If you choose the default configuration option (recommended), the user name is specified as ’admin’ and the password as ’root.’ To protect the security of your server, change these from the defaults as soon as possible, as described in Using the Administration Console > Configuring Usernames and Passwords in the product documentation.
Review and make note of the summary information provided for your Sun Java System ASP Administration Console configuration. It is recommended that you print this information for future reference. When finished, press Enter for product verification and to complete the installation. An installation summary file containing important information about your installation is located in:
[INSTALL_DIR]/logs/install_summary
where [INSTALL_DIR] is the directory in which you installed Sun Java System ASP (/opt/casp by default). Print the install_summary file for future reference.
If you are upgrading from a previous version of the product, you will be prompted to import the previous settings into your new installation. Follow the prompts as desired. If you choose to import previous settings, the settings will be imported, the ASP server and Web server will be restarted, and you will be notified whether the import succeeded or failed.
Before running your installation, review the following information:
The Administration Console is used to start and stop the Sun Java System ASP Server, and to change configuration settings. You can access the Administration Console by entering the following URL in your Web browser address bar:
http://[HOSTNAME]:[PORT]
where [HOSTNAME] is the host name of the Web server configured to run with Sun Java System ASP, and [PORT] is the port on which the Administration Console is running (5100 by default). The URL for accessing the Administration Console is provided in the following file:
[INSTALL_DIR]/logs/install_summary
where [INSTALL_DIR] is the installation directory for Sun Java System ASP (/opt/casp by default).
Expert users can also start and stop the ASP Server from the command line, as described in the Command-line Management section in the product documentation.
If you chose not to configure a Web server to run with Sun Java System ASP during installation, you will be prompted to do so the first time you open the Sun Java System ASP Administration Console.
The Sun Java System ASP setup program makes certain changes to the configuration files for the associated Web server. For more information, see Managing the Web Server > Changes to Web Server Configuration Files in the product documentation.
You can change some of the options that were configured during installation, such as the Web server with which Sun Java System ASP is configured to run. For more information, see the Command-line Management section in the product documentation.
Use the diagnostic applications to verify that your installation is working correctly. Diagnostics can be accessed from:
http://[HOSTNAME]/caspsamp/
where [HOSTNAME] is the host name of the Web server configured to run with Sun Java System ASP.
Certain Sun Java System ASP settings have important implications for the security of the Sun Java System ASP Server. See Managing the ASP Server > Securing the Server in the product documentation to ensure that settings are appropriately configured for your specific environment.
The setup program takes you through the steps required to install Sun Java System ASP 4.0.3 for Windows. All configuration is performed during installation. The setup program installs the following components on the target Web server.
Sun Java System ASP Server
JRE 1.4.2_16 for Chili!Beans (the use of Chili!Beans is optional; this install is performed only if an existing JRE 1.4.1 or higher is not installed)
Sun Java System ASP SpicePack components (the Chili.Mail component is installed only if an existing Microsoft CDONTS.Newmail component is not found on the machine)
The Sun Java System ASP Administration Console is NOT available on Windows.
This section contains the following topics:
Before starting your installation, make sure you meet the following requirements:
You are logged in with administrator privileges.
Your hardware and software meet the requirements listed in System Requirements.
You’ve uninstalled any previous installations of Sun Java System ASP
You’ve closed all applications that use ODBC connections
You’ve stopped the Web server. If you are running the Web server as an executable, stop the server by shutting it down or by closing the executable’s window. If you are running the Web server as a service, stop the service via the Windows Control Panel.
To install and use the Sun Java System ASP ADO samples, MDAC 2.5 or higher must be installed on your computer. If you opt to install the samples during the installation of Sun Java System ASP, and MDAC 2.5 is not yet installed, you have the option to install it. If you choose to install MDAC 2.5, the setup program walks you through the MDAC installation. Following installation, restart your computer and rerun the Sun Java System ASP setup program as described in this procedure.
You must uninstall any previous installations of this product before installing Sun Java System ASP 4.0.3.
Launch the setup program:
If you are installing Sun Java System ASP from a CD-ROM, insert the CD-ROM into the CD-ROM drive. If the setup program does not start automatically, double-click the setup file located on the CD-ROM. - or -If you are downloading Sun Java System ASP from the Web, download the installation file for Windows, and then double-click the file.
Perform the step-by-step installation, as prompted by the setup program.
After the installation of Sun Java System ASP is finished and you have restarted your computer, restart the Web server that was configured to run with Sun Java System ASP.
Before running your installation, review the following information:
Sun Java System ASP runs automatically whenever an ASP page is requested by a user (provided the Web server is running). Sun Java System ASP runs until the Web server is stopped. When the Web server is restarted, Sun Java System ASP will not run until an ASP page is requested by a user.
The Sun Java System ASP Administration Console is referenced throughout the product documentation. The Administration Console is available for the UNIX/Linux version of the product only. With Sun Java System ASP for Windows, all configuration is performed during installation. Some of the configuration information is stored in registry settings, however, and EXPERT users may choose to use regedit to edit those settings.
Do not make any changes to the INSTALL, SYSFILES, or REGLIST settings.
With Sun Java System ASP for Windows, ASP applications are defined by adding aliases or virtual directories to the Web server. Sun Java System ASP treats each alias or virtual directory as an ASP application. With Sun Java System Web Server, ASP applications are defined by adding an additional document directory using the server’s Administration tool. With Apache Web Server, ASP applications are defined by adding an alias to the httpd.conf file.
ODBC drivers are not installed with Sun Java System ASP for Windows. Use the Windows ODBC Data Source Administrator (accessed from the Control Panel) to view installed ODBC drivers and to create and manage DSNs. Consult Microsoft documentation for more information.
On UNIX platforms, Sun Java System ASP automatically upgrades many of your settings from an existing 3.6.2 or 4.0.2 installation of the product. To perform an upgrade to Sun Java System ASP 4.0.3, review the information listed below and take any necessary steps. Then follow the instructions in Installing Sun Java System Active Server Pages. During the installation, you will be prompted to import your settings.
This information applies to UNIX platforms only. Migration is not supported on Windows platforms.
The new installation will completely overwrite your existing installation. If your current Sun Java System ASP installation directory contains any items you want to preserve, copy them to another location or they will be lost. Be sure to back up your existing installation before beginning the upgrade.
The Sun Java System ASP setup program preserves many (but not all) settings from your 3.6.2 or 4.0.2 installation, and imports those settings into your new Sun Java System ASP installation. Most settings imported from your existing installation will override the settings that you configure during installation.
SequeLink DSNs are not migrated when upgrading from 3.6.2 or 4.0.2 to Sun Java System ASP 4.0.3. Neither are the administrator name and password used to access the Sun Java System ASP Administration Console (you will specify these again during the installation). Also, DO NOT press CTRL+C during setting migration.
If necessary, upgrade to meet the requirements listed in System Requirements.
Do not upgrade a mission-critical production server. Performing the upgrade and taking the additional configuration steps required might keep your server offline for an unacceptably long period of time. If possible, mirror the production server to a non-production server, perform the upgrade, and then test and debug the upgraded server before deploying it in your production environment.
When the setup program has completed the installation, do the following:
Verify that any system DSNs defined for your previous installation are functioning correctly. For more information, see Configuring a Database > Configuring Data Source Names (DSNs) > Testing a DSN in the product documentation. You can create or edit the system DSNs as needed, as described in Configuring a Database > Configuring Data Source Names (DSNs). Configuration information for the system DSNs that were defined for your previous installation can be found in the following file:
[INSTALL_DIR]/casp/INSTALL/settings.import
where [INSTALL_DIR] is the path name of the Sun Java System ASP installation directory (/opt/casp by default).
You may also wish to verify that the following migrated successfully:
Environment variables
ADO settings
ASP applications
Server settings
Custom components
Users
This section describes how to uninstall Sun Java System ASP on UNIX and Windows platforms:
On UNIX, Sun Java System ASP is uninstalled by running the script named uninstall located in the Sun Java System ASP installation directory (/opt/casp by default). When you run the uninstall program, you can delete all directories and files contained in the installation directory. Before running the uninstall program, make copies of any files contained under this directory that you do not want to lose. To perform this procedure you must be logged in as root on the computer running Sun Java System ASP.
From the Sun Java System ASP installation directory, enter the following at the command prompt:
./uninstall
Choose the number of the desired uninstall method:
Choose ’1. Uninstall the entire product’ to remove all Sun Java System ASP components and all files and directories under the installation directory. If you choose this option, go to Step 5.- or - Choose ’2. Perform a stage-based uninstall’ to select the components to uninstall. If you choose this option, go to Step 3.- or - Choose ’3. Cancel the uninstall’ to stop the uninstall without removing any files.
If you chose option ’2. Perform a stage-based uninstall,’ you are prompted to select the components to uninstall. At the prompts, enter the number of the component(s) you want removed.
After making your specifications in Step 3, you will then be given the option to uninstall the Web server-Sun Java System ASP association. Respond to the prompts as desired, choosing to either proceed with or cancel the uninstall.
Delete the directories and files in the Sun Java System ASP installation directory.
Use the Add/Remove Programs option from the Control Panel, or launch the uninstall program from Start > Programs > Sun Java System ASP.
In addition to these release notes, Sun Java System ASP also includes an Administrator and Developer’s Guide that provides detailed information about configuring, managing, and using Sun Java System ASP. The guide also provides reference information about using scripting languages, connecting to databases, and developing and using components.
The Administrator and Developer’s Guide can be found at:http://docs.sun.com/app/docs/prod/asp#hic
After you’ve accessed the 4.0.2 collection and located the Administrator and Developer’s Guide, do one of the following:
Click the ’Download’ link to access the PDF version of the guide
-or-
Click the link for the Administrator and Developer’s Guide in the collection list, and then click ’Sun ONE Active Server Pages Online Help’ on the page that displays. This launches the complete HTML version of guide. (Note that the Search box is not functional when the document is accessed in this manner. To search Sun Java System ASP 4.0.3 documentation, go to the docs.sun.com URL listed above, select the 4.0.3 collection, and then use the docs.sun.com ’Search for’ box to search the documents.)
You can also access the documentation in other ways:
From the Administration Console following installation by clicking the ’Documentation’ link in the left navigation pane (UNIX and Linux only).
With the following URL if you enabled documentation on your Web server during the installation of Sun Java System ASP:
http://[HOSTNAME]/caspdoc ; where [HOSTNAME] is the host name of your Web server (the Web server must be running).
In the appropriate installation directory (where [INSTALL_DIR] is the Sun Java System ASP installation directory):
On UNIX and Linux: [INSTALL_DIR]/caspdoc. The index.html file launches the HTML version of the documentation. The PDF version can be found in [INSTALL_DIR]/caspdoc/pdf.
On Windows: [INSTALL_DIR]\UserGuide. The index.html file launches the HTML version of the documentation. The PDF version can be found in [INSTALL_DIR]\UserGuide\pdf.
Using the context-sensitive Administration Console Help that’s part of the product (UNIX and Linux):
To access online Help for an entire screen in the Administration Console, click the HELP button in the upper right corner.
To access online Help for a specific field on a screen, mouse over or click the question mark (?) icon next to the field. The specific fields and elements in the user interface are also listed alphabetically in the Administration Console Glossary section at the end of the administrator’s guide for quick reference and lookup.
The following table lists the most important issues resolved in Sun Java System ASP 4.0.3 release:
Table 1–3 Resolved Issues in Sun Java Systems ASP 4.0.3
Problem ID |
Description |
---|---|
6238357 |
ASP 4.0.2 does not support DSN connection with MS SQL Server 7 or 2000. |
6239314 |
Web Server core gets dumped, when accessing the caspsamp/diag/server.asp resource. |
6318716 |
HTTP header containing quotes causes issue, when retrieving other header data through an ASP |
6340680 |
Warning message is displayed when the user tries to attach a file. |
6363037 |
Custom 404 Error Directive does not work with ASP 4.0.2 Windows version. |
6375404 |
CLI scripts displays the unable to find default run level error |
6380949 |
ChiliBean does not wok on ASP 4.0.2 Windows version. |
6380954 |
Binaries missing from Windows installation bundle. |
6392482 |
The log.cnfg file is called many times for each request. |
6402629 |
The dispint.h header file is not found in ASP 4.0.2 |
6442631 |
Unable to install ASP 4.0.2 after uninstalling the earlier version of ASP. |
6463759 |
Multiple vulnerabilities in ASP 4.0.2 administration server that uses Apache. |
6529288 |
Unable to install ASP 4.0.2 on Windows, when system32/Tag/*. files are present in the system. |
6542849 |
HTTPd crashes when the ASP service is enabled for Apache. |
6550891 |
Multiple vulnerabilities in ASP server might lead to execution of arbitrary code. |
6556637 |
Vulnerabilities in ASP Server may lead to escalation of privileges. |
6577838 |
An incorrect response status (200 vs 30x) is returned with Response.Redirect under Apache/2.0.58 (UNIX) DAV/2 Sun ONE ASP 4.0.2, which causes applications to fail. |
6588868 |
Need to provide migration support from ASP 4.0.2 to 4.0.3. |
6589845 |
ASP 4.0.3 need to support Sun Java System 7.0 Web server. |
6590355 |
Remove the incorrect README file from the admin directory. |
6590361 |
Buffer overflow vulnerability in ASP. |
6593033 |
ASP 4.0.3 need to support Apache 2.2 releases. |
6594286 |
ASP 4.0.3 installer should support Web Server 7.0 in Windows. |
6594778 |
Apache 1.3.x and 2.0.x builds crash on Windows. |
6594779 |
ASP installer for Windows need to support Apache 2.2.x. |
6594786 |
ASP 4.0.2 in Japanese locale fails to connect database when updating records, which has more than hundred Japanese characters. |
6595995 |
ASP administration console pages should be secured. |
6596437 |
ASP sample applications need to be updated. |
6606567 |
ASP is unable to process the casp.cnfg file due to stdio limitations. |
6621471 |
Need to bundle JRE 1.4.2 with ASP server. |
6654973 |
Displays an error when accessing the Web Server tab. |
6656681 |
When ASP server is disabled, Netscape plug-in crashes while serving ASP requests. |
6658139 |
SQL Server drivers need to be branded correctly. |
6658718 |
ASP Server is unable to recognize the Apache 2.x installation without the ServerName directive |
6675459 |
ASP admin fails to start on HP-UX. |
6675461 |
Unable to login to the Administration console, as the service.pwd file is empty. |
6675465 |
Unable to detect and configure Web Server 7.0. |
6675478 |
On AIX, ASP instance fails to start during and after install. |
6692211 |
Accessing ASP admin/instance crashes ASP server |
6693561 |
CVS files that are bundled under admin directory should be removed. |
6693874 |
Disable chilibean by default. |
6694339 |
ASP installation program fails on Windows, when pre-configured Web Server is running. |
6621471 |
Upgrade the JRE version from 1.4.2_06 to 1.4.2_16. |
The following table lists the most important issues resolved in Sun Java System ASP 4.0.2 release:
Table 1–4 Resolved Issues in Sun Java System ASP 4.0.2
Problem ID |
Description |
---|---|
4866826 |
VBScript error on self-assignment of variable. The variable assignment foo = foo incorrectly caused foo’s value to be destroyed. |
4872092 |
RecordSet properties conflict with field names. The following two cases were erroneously behaving the same: myRecordSet("State") and myRecordSet.State. |
4872116 |
Virtual host list truncation. When the list of virtual hosts exceeded a certain length, it was truncated at that point. |
4873437 |
Response.Cookies.Expires gives Type Mismatch error when passed a string containing a validly formatted date. |
4879323 |
VBScript Split function did not create trailing empty elements when last character of the input string was a delimiter character. |
4929078 |
A RecordSet object’s default property with NULL value would cause Response.Write to error-out incorrectly. |
4929094 |
Replace function fails when called more than 128 times. |
4967340 |
On Windows, ASP exits when users log off the system. |
4978332 |
Apache 2.0 virtual hosts do not support setting user/group id to something other than the ids under which the main Apache server is running. This is a change from the Apache 1.x series. To work around this problem, Apache 2.x virtual host blocks can now contain ASPUser=<uid> and ASPGroup=<gid> to set the user and group id values under which the virtual host’s requests will execute. |
4978334 |
Interrupted or failed install procedures now give users the option to leave the partial install. This allows users to examine any error messages in the installation logs. |
4997325 |
VBScript for ... step <increment value> worked incorrectly on Solaris (SPARC). Specifically, the loop always exited immediately after the first iteration when step <increment value> was specified, whereas loops without step worked correctly. Both now work as expected. |
5012510 |
Fails to install on Windows Server 2003 Enterprise Edition. |
5012512 |
Admin Web server fails to start on Red Hat Linux Advanced Server 3.0. |
5040097 |
Custom 404 Error Directive not recognized by the ASP engine. |
5040871 |
500 Error when trying to access ASP updates. |
No ID |
Response.charset not correctly appending its values to the content-type line for text/html. |
6402629 |
dispint.h is a header file and it is relevant only in some situations. If you have already installed ASP product successfully then you do not need to refresh the installation. |
The following table lists the most important known issues in the ASP release:
Table 1–5 Known Issues in Sun Java System ASP
Problem ID |
Description |
---|---|
No ID |
Cannot connect to a remote Oracle database when Sun Java System ASP 4.0.2 is installed on AIX 5.2 with the Oracle client. The connectivity test results in the following error: /opt/casp/asp-server-3154/testadocon[16]: 123088 Illegal instruction(coredump) Workaround By default, 64-bit libraries are installed when Oracle is installed on AIX 5.2. Sun Java System ASP 4.0.2 uses a 32-bit driver, so the following changes must be made:
|
6542849 |
Apache HTTPd crashes with SIGSEGV, when ASP 4.0.2 installed on UNIX/Linux platforms and compiled with some non-standard options. Workaround When Apache HTTPd compiled with some non-standard options, (for example, large file support), Sun Java System ASP Server requires that its module for Apache be re-compiled using apxs. For more information on how to compile, see Apache HTTPd documentation: http://httpd.apache.org/docs/2.2/programs/apxs.html (Apache 2.2) http://httpd.apache.org/docs/2.0/programs/apxs.html(Apache 2.0) http://httpd.apache.org/docs/1.3/programs/apxs.html(Apache 1.3) |
If you have problems with Sun Java System ASP, contact Sun customer support using one of the following mechanisms:
Sun Software Support Services online at http://www.sun.com/service/support/software
The telephone dispatch number associated with your maintenance contract
So that we can best assist you in resolving problems, please have the following information available when you contact support:
Description of the problem, including the situation where the problem occurs and its impact on your operation
Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
Detailed steps on the methods you have used to reproduce the problem
Any error logs or core dumps
Sun is interested in improving its documentation and welcomes your comments and suggestions. Send your comments to Sun using the "Send comments" link athttp://docs.sun.com/
Please include identifying information with your comments, such as the book’s part number and title.
Useful information can be found at the following locations:
Sun Java System ASP Documentation http://docs.sun.com/app/docs/prod/asp#hic
Developer Information http://developers.sun.com/prodtech/asp/
Software Products and Service http://www.sun.com/software
Software Support Services http://www.sun.com/service/support/software
Training Services http://www.sun.com/training
Sun Java System Active Server Pages Developer Forumhttp://forum.java.sun.com/forum.jspa?forumID=736