This document contains the following sections:
Relevant Architecture: SPARC
Relevant Operating Systems: Solaris 2.6, Solaris 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/gxlib/libgxconn.so
./ias/gxlib/libgxutil.so
./ias/bin/.kas
./ias/bin/.kjs
./ias/bin/.kjs.memopt
./ias/bin/.kxs
./ias/bin/.kxs.memopt
./ias/bin/patchversion
./ias/bin/iascontrol
./ias/classes/java/kfcjdk11.jar
./ias/classes/java/kfcjdk11_properties.jar
./ias/classes/java/kadmin.jar
./ias/classes/java/buzz.jar
./ias/classes/java/jasper.jar
./ias/classes/java/jts.jar
./ias/usr/java/jre/lib/ext/j2eeorb.jar
./ias/kdb/en_US/gxserver.properties
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_5
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
Use the Sun ONE Application Server 6.5 Deploy Tool to regenerate stubs and skeletons. Code changes are not required.
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.
When TimerMarksLTxnForRollback is set to True, the timer thread only marks the time consuming transactions for rolling back (by calling setRollbackOnly) instead of actually rolling back the transactions. If the value of this key is set to False (the default), the behavior is to call rollback() for time consuming transactions. These are transactions that have exceeded the TxTimeout value.
Use this registry key in situations where rollback might block and eventually cause a deadlock in the system. If this key is not present, a default value (False) is assumed.
| ID | Summary |
|---|---|
| Problem Incorrect information on session failover in Sun ONE Application Server Performance and Tuning Guide. The Performance and Tuning Guide mentions that to enable session failover for all KJS processes in an application server instance, you should set the cluster configuration to Dsync-Local. Setting the cluster configuration to Local will not provide session failover. Workaround To enable session failover for your application, set the cluster configuration to Distributed. |
|
| 4816176 | Problem EJB methods that have container managed transaction attributes do not throw exceptions to caller when the underlying transaction gets rolled back because of transaction timeout. Use the following workaround for this bug. Workaround Set transaction time out to a very high value. The registry key to be modified is CCS0\\TXNMGR\\Timeout. This time out value is measured in seconds and is applicable to both global and local transactions. The maximum allowable value is the result of Java expression, Integer.MAX_VALUE/1000.
|
| 4719687 | Problem Cluster entries in LDAP are not deleted after uninstallation. Workaround Cluster entries are not removed from LDAP, as it might effect other configurations present in the directory server. The presence of these old entries does not cause any issues regarding Application Server versions or the server's functionality.If absolutely required, you can manually remove the old cluster entries.
|
| 4939828 | Problem The registry values of SyncTimerInterval for individual engines is incorrectly mentioned in Sun ONE Application Server 6.5 SP1 Performance and Tuning Guide. The guide refers to the wrong registry path for the individual settings of each engine: SOFTWARE\iPlanet\Application Server\6.0\CCSO\ENG\ Workaround The correct path in the registry is \SOFTWARE\iPlanet\Application Server\6.5\Clusters\The documentation may contain other similar bugs, where the registry path may not have been updated from the iPlanet Application Server 6.0 release. In most cases, replacing 6.0 with 6.5 will give you the correct path.
|
| 4537418 | Problem SFSB failover is not supported over the RMI/IIOP path. The same session is not failed over to another KJS |
| 4801503 | Problem Web server crashes because of missing smartheap library. A web connector plug-in installation adds the path of the application server's libsmartheap_smp.so to the beginning of web server's LD_LIBRARY_PATH. Therefore, web server will always load the smartheap library of the application server, and crashes if this smartheap is not found. Workaround Ensure that the web server's LD_LIBRARY_PATH is pointing to the correct smartheap library, especially of you have uninstalled the web connector plug-in. |
| 4874547 | Problem Version of Oracle 9i database support information is imprecise in documentation. Sun ONE Application Server is certified with to work with Oracle 9i (9.0.1.x) database and clients. Oracle 9.2.0.1 is not supported. |
| 4863850 | Problem Explanation of Connection Pool Sanity checking in Sun ONE Application Server is lacking details. Additional information is provided in the Workaround. Workaround
|
| 4764638 | Problem Sun ONE Application Server 6.5 Release Notes does not specify the compatibility of the bundled Sun ONE Directory Server 5.0 SP1 with the operation system. The bundled Sun ONE Directory Server 5.0 SP1 is not supported on Solaris 9, though Sun ONE Application Server 6.5 is supported on Solaris 9. Workaround Use Sun ONE Directory Server 5.1 SP1, which is supported on Solaris 9. |
| 4786743 | Problem Sun ONE Directory Server 5.0 SP1 patch installation instructions are not clear. The installation procedure is explained in the Workaround. Workaround Follow these instructions to install Sun ONE Directory Server 5.0 SP1 Patch on Solaris. This patch must be copied to the appropriate directory before installing Sun ONE Application Server 6.5, Enterprise Edition.
|
| 4763145 | Problem Sun ONE Application Server Java Programmer's Guide has incorrect DD for the welcome file list. The guide incorrectly shows a leading /, which is contrary to Servlet 2.3 specification. Workaround The welcome file list should be specified according to the Servlet specifications: "The welcome file list is an ordered list of partial URLs with no trailing or leading /." |
| 4928313 | Problem Documentation about IAS_KXS_HANG_INTERVAL in Sun ONE Application Server, Enterprise Edition Version 6.5 Service Pack 1 is incorrect. The document incorrectly states that If the KXS thread is unable to deliver the request in this specified time, then it times-out and assigns the request to the another KJS. The corrected documentation would read: If the KXS thread is unable to deliver the request in the specified time, the request will time-out (it will be lost and will have to be resubmitted by the client). It will not be re-routed to another KJS engine.
|
| 4816588 | Problem Precompiled JSPs requires contentType to indicate non-standard charset. There is a change in behaviour when a JSP is compiled outside the application server runtime environment compared to when a JSP is compiled within the application server runtime on demand. Workaround When JSPs are compiled using command line JSP compiler, unless user uses contentType directive in the JSP to indicate the charset to be used for JSP encoding, the compiler uses the default charset (8859_1) for that JSP. This is not the case when a JSP is compiled within the application server runtime environment because in such a case if there is no contentType directive the charset for application server is used. |
| 4735296 | Problem In a distributed environment setup for load balancing, application components are served even if the application server instance hosting the the component have been disabled. |
| 4804948 | Problem Changing the JAVA_ARGS in iasenv.ksh does not take effect. Procedure for using a custom JVM instead of the default JVM is not documented. Workaround Use the following procedure to configure Sun ONE Application Server to work with JVM Client version instead of the default server version:
|
| 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. |
| 4805318 | Problem StaticServlet does not serve internationalized document correctly. This problem will be seen by machines that does not have LANG set (mostly English countries) and that want to serve non iso-8859-1 characters (non 7-bit characters). Workaround
|
| 4731873 | Problem Struts templates are not handled properly in S1AS 6.5 Maintenance Update 4. Workaround
Change the chapterTemplate.jsp
in the following manner using struts defined
<td><template:get name='sidebar'
flush='true'/></td> |
| 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
|
| 4943890 | Problem Documentation error in Sun ONE Application Server Performance and Tuning Guide. Use the correct description mentioned under Workaround. Workaround In Chapter 9, "Validating Server Performance," of the English version of Performance and Tuning Guide, use SOFTWARE\iPlanet\Application Server\6.5\CCS0\HTTPAPI\NASRespTime=1 instead of SOFTWARE\iPlanet\Application Server\6.0\CCS0\HTTPAPI\NASRespTime=1.
In the Japanese version of the same document, use SOFTWARE\iPlanet\Application Server\6.5\CCS0\HTTPAPI\NASRespTime=1, instead of SOFTWARE\iPlanet\Application Server\6.0\CCS0\HTTPAPI\NASRespTime=1 |
| 4964960 | Problem Incorrect database configuration information for IBM DB/2 in Sun ONE Application Server Administration Guide.
Workaround The path should be DB2DIR/sqlib/java12/db2java.zip and D:\SQLLIB\java12\db2java.zip instead of DB2DIR/java/db2java.zip and D:\SQLLLIB\java\db2java.zip for Solaris and Windows, respectively. In addition, the application server class, com.iplanet.ias.jdbc.IASConnectionPoolDataSource requires the JDBC Driver Class to be specified as COM.ibm.db2.jdbc.app.DB2Driver.
|
Use of Sun ONE Application Server, Enterprise Edition is subject to the terms described in the license agreement accompanying it.
Copyright © 2004 Sun Microsystems, Inc. All rights reserved.
Last Updated March 24, 2004