This document contains the following sections:
Relevant Architecture: SPARC
Relevant Operating Systems: Solaris 2.6, 8, and 9
Files included with this patch:
./ias/gxlib/libgxbindu.so
./ias/gxlib/libgxprincipal.so
./ias/gxlib/libgxreposit.so
./ias/gxlib/libjx2thread.so
./ias/gxlib/libjx2ebfp.so
./ias/gxlib/libiASApachePlugin.so
./ias/gxlib/libgxdsync.so
./ias/gxlib/libgxdsync_failover.so
./ias/gxlib/libgxdsync_token.so
./ias/gxlib/libgxdsync_messenger.so
./ias/gxlib/libgxagent.so
./ias/gxlib/libgxnsapi6.so
./ias/gxlib/libgxsecurity.so
./ias/gxlib/libgxorcl.so
./ias/bin/patchversion
./ias/classes/java/kfcjdk11.jar
./ias/classes/java/kadmin.jar
./ias/classes/java/buzz.jar
./ias/classes/java/jasper.jar
./ias/bin/.kas
Example: for Bourne shell
GX_ROOTDIR=/opt/appserver/ias; export GX_ROOTDIR
Example: for Korn shell and BASH
export GX_ROOTDIR=/opt/appserver/ias
Example: for C shell
setenv GX_ROOTDIR /opt/appserver/ias
./applypatch
$JAVA_HOME/bin/java ${JAVA_ARGS} com.kivasoft.engine.Engine $opts
with the following lines
## Start fix for bug 4819229
for optvar in $opts
if [ ! -z "$d_opts" ]
$JAVA_HOME/bin/java ${JAVA_ARGS} com.kivasoft.engine.Engine $mod_opts
d_opts=""
mod_opts=""
do
echo $optvar |grep "^-D" >/dev/null
done
if [ $? -eq 0 ]
then
d_opts="$d_opts $optvar"
else
mod_opts="$mod_opts $optvar"
fi
then
JAVA_ARGS=${JAVA_ARGS}${SPACE}$d_opts
fi
## End fix for bug 4819229
Example: cd /opt/appserver/ias/backup_3
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.
Example: for Bourne shell
REMOVE_BACKUPFILES=1; export REMOVE_BACKUPFILES
Example: for Korn shell and BASH
export REMOVE_BACKUPFILES=1
Example: for C shell
setenv REMOVE_BACKUPFILES 1
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.
./unpatch
./unpatch
This command will restore the files that were patched.
## Start fix for bug 4819229
for optvar in $opts
if [ ! -z "$d_opts" ]
$JAVA_HOME/bin/java ${JAVA_ARGS} com.kivasoft.engine.Engine $mod_opts
d_opts=""
mod_opts=""
do
echo $optvar |grep "^-D" >/dev/null
done
if [ $? -eq 0 ]
then
d_opts="$d_opts $optvar"
else
mod_opts="$mod_opts $optvar"
fi
then
JAVA_ARGS=${JAVA_ARGS}${SPACE}$d_opts
fi
## End fix for bug 4819229
The two Java compilers shipped with JDK 1.3.1 are:
If the -newjavac option is passed to ejbc, then the new Java compiler will be used. Using the new compiler does not affect the code generation path. Except in a few corner cases, the two Java compilers are highly compatible with respect to the class files they generate. If you use the -newjavac option, ensure that you build both the client and server with the new compiler to avoid any incompatibility issues.
Before using the new compiler, you will have to modify the existing build scripts, such as makefiles, Ant and shell scripts.
Set an environment variable IAS_CLONE_ATTR_LIST to yes in KJS engine runtime environment. This can be achieved by setting this variable in ias/bin/kjs script as follows:
IAS_CLONE_ATTR_LIST=yes
export IAS_CLONE_ATTR_LIST
Workaround:
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.
| ID | Summary |
|---|---|
| 4878322 | Problem By default, the application server's IP address and port number will not be displayed if the application server goes down. Workaround To know the IP address and port number of the machine on which the application server went down, set the debug mode of webconnector plug-in to 2 or greater. |
| 4892677, 4858315 | Problem Redeployment of an updated version of an application does not remove the contents of the previous deployment from the file system area. In addition to leftover file system content, some of the application server registry settings are also not overwritten and/or removed as an application is redeployed.� This behavior can lead to older application settings remaining in effect after a redeploy.� Workaround To perform a clean redeployment, first perform a remove (iasdpeloy removeapp, removemodule, etc.) followed by a deploy.�To remove unnecessary entries from the file system in a much faster way, set the registry key, Application Server\6.5\Deployment\cleanup, to true before redeploying applications. |
| 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 3.
If you run the unpatch utility from the 6.5 Maintenance Update 1(backup_1) directory, Sun ONE Application Server 6.5 SP1 Maintenance Update 3 will get uninstalled.
Workaround |
| 4805318 | Problem StaticServlet does not serve internationalized document correctly.
Workaround
Use the format, export LC_ALL=language.charset
|
| 4731873 | Problem Struts templates are not handled properly in S1AS 6.5 Maintenance Update 3. Workaround
Change the chapterTemplate.jsp
in the following manner using struts defined |
| 4858315� | Problem Redeployment of an updated version of an application does not does not delete LDAP entries if the updated application has less registered components than previous deployments. This can leave "orphan" entries that are difficult to remove.� This behavior can lead to older application settings remaining in effect after a redeploy.� Workaround
|
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 September 11, 2003