Release Notes for Sun ONE TM Application Server, Enterprise
Edition
Formerly known as iPlanetTM Application
Server.
Version 6.5 Service Pack 1, Maintenance Update 1 for x86/Windows Platform
Part Number: 817-2359-05
Updated June 26, 2003
These release
notes contain important information available at the time of the Version
6.5 SP1, Maintenance Update 1 release of Sun ONE Application Server, Enterprise
Edition.
These release
notes contain the following sections:
Installation Notes
This section contains
information about installing Sun ONE Application Server, Enterprise Edition,
6.5 SP1 Maintenance Update 1. For detailed information about installation
procedures, see Sun ONE Application Server Installation Guide at Sun documentation web site.
Relevant Architecture:
x86
Relevant Operating
Systems: Windows NT 4.0 SP6a, Windows 2000 Professional SP2, Windows
2000 Server SP2, Windows 2000 Advanced Server
Files included
with this patch:
.\ias\bin\iascontrol.bat
.\ias\bin\gxisapi.dll
.\ias\bin\gxsyb2.dll
.\ias\bin\iASApachePlugin.dll
.\ias\bin\gxdsync.dll
.\ias\bin\gxutil.dll
.\ias\bin\jx2principal2.dll
.\ias\bin\gxagent.dll
.\ias\bin\gxconn.dll
.\ias\bin\gxnsapicli.dll
.\ias\bin\gxsession.dll
.\ias\bin\gxnsapi6.dll
.\ias\classes\java\kfcjdk11.jar
.\ias\classes\java\iasacc.jar
.\ias\classes\java\buzz.jar
.\ias\classes\java\tomcat\jasper.jar
Installation
Instructions
- Install Activestate
Perl (ActivePerl) version 5.6.0 or later. You can download it from http://www.activestate.com.
- Ensure that all application server processes have been shutdown.
- Ensure that the directory server is running.
- If the Web server running on the same machine as Sun ONE Application
Server, then stop the Web server before installing this update.
- Become the user who had installed the Sun ONE Application Server
you want to patch.
- Change the working directory to the directory containing the patch.
- Apply the Update by typing:
perl
.\applypatch
Special Install
Instructions
- If you have not installed
the "Core Server Component", "PointBase Database Server", and the "Web Connector
plug-in Component", then set the environment variable SPECIAL_INSTALL_OPTS
to "-i" before you run applypatch
in Step 7, Installation Instructions.
- If the Webconnector
plugin is running on a separate machine, then the Update must be installed
on that machine as well. Set the environment variable SPECIAL_INSTALL_OPTS
to -i
before performing the steps described in Installation Instructions.
- If you are running
Rich clients, ensure that after installing Maintenance Update 3, copy install_dir\ias\classes\java\iasacc.jar
to the directory where the Rich client is installed.
Uninstallation
Instructions
- Become the user who
had installed the application server installation for which you want to
backout the patch.
- Ensure that all webserver
and application server processes have been shutdown.
- Ensure that the directory
server is running.
- Change working directory
to the directory where the backup data is saved. The backup data is saved
in a directory named backup_patch number in your Sun ONE Application
Server installation directory:
Example: cd c:\iplanet\ias6\ias\backup_1
Note: If the
Webconnector plugin is installed on a different machine, then you must uninstall
the update from the Webconnector directory as well. To restore the old files
from the backup directory, follow the steps given under Uninstallation Instructions.
- You have to manually
remove all files in the backup directory after the Maintenance Update uninstallation
is over.
Note: The
presence of the backup directory does not affect the reinstallation of the
same patch. However you may want to remove the files in the backup directory
to save disk space.
- Ensure that all application
server processes have been shutdown.
- Ensure that the directory
server is running.
- Uninstall the Update
by typing:
perl .\unpatch
Special Uninstallation
Instructions
NOTE: If the
installation process quits after patching some of the files then:
- Change the working
directory to the backup_patch number directory present in your Sun
ONE Application Server installation.
- Copy and rename the file unpatch.bak
to unpatch.bat.
- Run the following command:
.\unpatch.bat
This command will restore the files that were patched.
Special Instructions
Firewall Time-outs
Problem:If
the inactivity period of the application server exceeds the TCP/IP timeout
interval of the firewall, then you need to restart the application server
and web server.
Workaround:
- Open the
registry editor by running the command, kregedit
- Go to Application Server\6.5\CCSO\HTTPAPI.
- Create a
new entry called KeepAliveTimeOut, of type integer.
- Enter the
value for this key in seconds, which could be equal to the default TCP/IP
timeout value of the firewall, or equal to the number of seconds for
the firewall to timeout.
This value
represents the number of seconds the plugin will wait for inactivity
after the first request, and keep sending messages at the KeepAliveTimeOut interval to keep the connection between
the web server plugin and KXS process of the application server alive.
Resolved Issues
The following
table lists the critical issues resolved in Sun ONE Application Server, Enterprise
Edition 6.5 SP1, Maintenance Update 1 release.
Table 1
List of resolved issues
|
Bug ID
|
Description
|
| 4754456 |
HTTP response from JSPs contains offending CRLF right after HTTP
header. |
| 4770671 |
Request parameters are getting lost(except 1) when going to FBA
login page. |
| 4779207 |
Registered JSP pages fail to execute properly on 6.5 MU3. |
| 4689007 |
Webconnector logs "info (5242): gxrequest.cpp:gxrequest()..." |
| 4767997 |
Enbale Dynamic Class Reloading check box gets unselected after
restart. |
| 4750058 |
Dsync Logging causes KXS to crash. |
| 4761598 |
JDBC connection pool not releasing connection when an error occured
in db. |
| 4711735 |
iPlanet Application Server 6.0 sp3 KJS not load sharing
properly. |
| 4754692 |
Request forwarding is not working when there is a space character
in parameter |
| 4735914 |
Struts template application is not formatting page properly. |
| 4768799 |
The info for dynamic reloading of servlets is not shown in a log
form in KJS. |
| 4672041 |
MDB Durable Subscribers always create a new subscription. |
| 4804086 |
Could not configure a durable topic from the deploytool during
deployment. |
| 4761319 |
KXS crashes when customer tries to retrieve any cached information. |
| 4760264 |
Client Certificate Authentication fails with certificates from
iCMS 4.2sp2. |
| 4758869 |
Context is wrong after FBA with GET. |
| 4762957 |
The deploytool oes not handle the editing of the deploy descriptors
corrrectly. |
| 4768669 |
When username is same as group name ias authorises an invalid
user to login (FBA). |
| 4693651 |
Monitoring "Total Threads" does not work. |
| 4794965 |
Urgent need for ias-web.xml server-info tags to work. |
| 4640716 |
Cluster problems in DSYNC. |
| 4783055 |
KXS core dumps in GXBuffer::Alloc(). |
| 4825234 |
KJS Hangs at saveSession. |
| 4871079 |
KeepAliveTimeOut is measured in seconds. |
Known Problems and Limitations
This section describes
known problems and associated workarounds with Sun ONE Application Server,
Enterprise Edition 6.5 SP1, Maintenance Update 1. This information is organized into the following
sections:
| ID |
Summary |
| 4828914 |
Problem
unpatch utility of Sun ONE Application Server 6.5 Maintenance Update 1 inadvertently uninstalls Sun ONE Application Server 6.5 SP1 Maintenance Update 1.
When you upgrade from Sun ONE Application Server 6.5 Maintenance Update 1 to Sun ONE Application Server 6.5 SP1 Maintenance Update 1, a backup directory is created for both 6.5 Maintenance Update 1(backup_1) and 6.5 SP1 Maintenance Update 1(backup_65sp1_1 for 65sp1).
If you run the unpatch utility from the 6.5 Maintenance Update 1(backup_1), Sun ONE Application Server 6.5 SP1 Maintenance Update 1 will get uninstalled.
Workaround
To uninstall Sun ONE Application Server 6.5 Maintenance Update 1, make sure you run the unpatch utility from the backup_1) directory.
|
| 4731873 |
Problem
Struts templates are not handled properly in S1AS 6.5
Maintenance Update 1.
Workaround
Use the following recommended
procedure to perform the flush operation.
Change the chapterTemplate.jsp
in the following manner using struts defined
attribute for template tag.
<td><template:get name='sidebar' flush='true'/></td>
<td><table>
<tr><td><template:get name='header' flush='true'/></td></tr>
<tr><td><template:get name='content' flush='true'/></td></tr>
<tr><td><template:get name='footer' flush='true'/></td></tr>
</table>
</td>
The only addition here is flush='true' in every template:get tag which flushes
the
buffer before every include.
|
| 549549 |
Problem
Description of KXS monitoring parameters, Requests Queued and Requests Ready, is confusing.
The current
description of KXS monitoring parameters, Requests Queued and Requests Ready , in Sun ONE Application
Server Administrator's Guide, Chapter 2 "Monitoring Server Activity"
is inadequate. The current description is leading to confusion among users
regarding the values displayed for these two monitoring parameters.
Use the updated description given under Workaround.
Workaround
Requests
Queued: The total number of requests in an internally maintained queue. An
actual count of pending requests in an engine can be monitored using the
Requests Waiting parameter.
T his
internal queue status is meant for analysis by Sun engineers.
Requests
Ready: The total number of requests which are in ready state to be processed
in the internally maintained queue of engine. An actual count of pending
requests in an engine can be monitored using Requests Waiting parameter.
This internal
queue status is meant for analysis by Sun engineers.
|
Additional Information
Useful Sun ONE information can be found at the following Internet
locations:
Use of Sun ONE
Application Server, Enterprise Edition is subject to the terms described in
the license agreement accompanying it.
Copyright ©
2003 Sun Microsystems, Inc. All rights reserved.
Last Updated
June 26, 2003