816-6373-11
These release notes contain the following sections:
With the KJS hang detection enabled, KXS detects and kills the hung KJS and routes the requests to other available KJS'. KXS detects the hung KJS based on the IAS_KJS_HANG_INTERVAL environment variable value specified in iasenv.ksh. If you do not set a value for this environment variable, the default value of 5 (50 seconds) is used.
The default value of 50 seconds is arrived at by multiplying the IAS_KJS_HANG_INTERVAL value with the SOFTWARE/iplanet/Application Server/6.5/CCS0/conn/RecvTimeOut registry value.
Therefore, if KXS does not receive any reply within the specified time interval, it kills that particular KJS.
NOTE: If an application takes more than 50 seconds, you will have to configure the IAS_KJS_HANG_INTERVAL accordingly, otherwise KXS will assume that KJS is hanging and kill that KJS. Consequently, any requests running on that KJS at that time will be lost.
KXS uses the install_dir/bin/StopHungKjs.sh script to kill the hung KJS. You can insert useful commands in this script, such as taking the stack trace or sending a mail to admin, before terminating the KJS.
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.
NOTE: If the network is taking more than 60 seconds to deliver the request to KJS, then this value should be suitably changed.
The following sample has been added in Sun ONE Application Server, Enterprise Edition 6.5 SP1 release:
The following Message driven samples are bundled with Sun ONE Application Server, Enterprise Edition 6.5 SP1:
- Simple Point-to-Point Queue using an MDB listening on a queue, and a standalone client sending messages to that queue.
- Simple Publisher Subscriber Topic using an MDB listening on a topic, and a standalone client publishing messages on that topic.
- Consumer Stock Management using Queues using a simple servlet as a client, a message listener as sales unit, and an MDB as the production unit.
- Consumer Stock Management using Topics using a simple servlet as a client, a message listener as sales unit, and an MDB as the production unit.
| Note |
|
The following patches for JDK 1.3.1_04 must be applied on Solaris 8. These patches can be downloaded from the http://sunsolve.sun.com/ or http://java.sun.com/j2se/1.3/download-solaris.html .
Table 2 Required patches for Solaris 8
Patch
Patch Description 108652-37 X11 6.4.1 patch 108921-13 CDE 1.4 patch 108940-32 Motif patch Other required patches:
Table 3 Required patches for Solaris 8
Patch
Patch Description 108528-17 kernel update patch 108434-04(32-bit) / 108435-04 (64-bit) libC patch 108827-12 SunOS 5.8: /usr/lib/libthread.so.1 patch
In cases where a patch is listed as missing and you have a later version installed, you can ignore the warning message and continue with installation. That is, the list of missing patches contains a patch whose higher version is already installed.
For example, you have 108435-05 on your system and the list of missing patches shows 108435-04.
No additional patches are required on Solaris 9. The install script will check for missing patches and report that a number of them are not found on your system. Disregard this message and continue with the installation.
| Note | On a FAT file system, the installer may not calculate the required space correctly and may run out of disk space without warning. |
| Note | If you are performing a `Webless' installation, the web server and browser need not be present on the same machine on which you are installing the application server. For more information on Webless installation, see iPlanet Application Server Installation Guide . |
The following directory servers are certified to work with Sun ONE Application Server 6.5 SP1.
|
|
|
|
|---|---|---|
| Windows 2000 | Professional, Server, Advanced Server | JDK 1.3.1_06 |
| Windows NT | 4.0 SP6a | JDK 1.3.1_06 |
| Solaris | 2.6, 8 , 9 | JDK 1.3.1_06 |
|
|
|
The product key is in the welcome letter you received with the product
CD.
The product key is in the welcome letter you received with the product
CD.
This section describes known problems and associated workarounds with Sun ONE Application Server, Enterprise Edition 6.5 SP1.This information is organized into the following sections:
|
|
Problem iPlanet Application Server fails to respond while running UIF + SAP + Process Manager Integration Tests. Workaround Rename libclntsh.so.9.0 under, $ORACLE_HOME/lib to libclntsh.so.8.0 |
|
4719690 |
Problem Session is not retained in a distributed application. Workaround Ensure that all servers participating in a cluster have the same system time and date. |
| 4626356; | Problem Administration Tool fails to connect to application server after the primary fails. This would happen if you have a cluster set-up configured with Maxbackups=0.
If
Maxbackups is specified as 0 (none), then there is no backup
application server and the alternates change to the standalone state.
However, when the primary comes up again, it cannot connect to the alternate
as it's in standalone mode.
Workaround |
| 4753639 |
Problem Issues with shared directory server. In a non-clustered environment, where two application servers are sharing the same directory server, and each running a different instance of the same application, if an application is undeployed from one of the application servers, then requests to the other application server also fails. This problem occurs because when application is undeployed from one of the application servers, that application's "Classdef" information is removed from the directory server. Since this directory server is shared, no other application server would be able to get the GUID of this application.
Workaround |
| 4719687 |
Problem Cluster entries in LDAP are not deleted after uninstalling servers.
These entries, under SOFTWARE\iPlanet\Application
Server\NASCluster\SyncServers, do not cause any problems and, if
required, can be manually deleted. |
| 4639210 | Problem Transaction propagation does not work consistently. If two KJS' are participating in a transaction and only one of them is made recoverable, then this configuration cannot lead to proper recovery.
Workaround |
| 4633284 | Problem When using DB2 as the database, transactions are not rolled back even though one of the application servers fails to recover from a crash. This problem occurs due to limitations in DB2.
Workaround |
| 4633274 | Problem KJS crashes during transaction recovery, if DB2 is in an inconsistent sate. If recovery is done when DB2 is in an inconsistent state, the recovery call to DB2 dumps core and crashes KJS.
Workaround |
| 542273 | Problem The CORBA Executive Server crashes when exceptions are thrown. |
| 536256 | Problem A JSP of size larger than 185 KB cannot be executed on Sun ONE Application Server. |
| 560053 | Problem Struts applications fail when the Versioning key is enabled.
Workaround To disable dynamic reloading:
|
| 557991 | Problem On Windows, the security principal class is not invoked automatically when security is enabled for RMI/IIOP based applications.
Workaround For example, org.omg.CORBA.ORBClass=com.netscape.ejb.client.ClientORB. |
| - | Problem For distributed sessions, a negative value for setMaxInactiveInterval() will make the session timeout immediately.
Workaround |
| 4539468 | Problem In certain cases, IMQ as the JMS will not work on Solaris.
Workaround |
| ID | Summary |
|---|---|
| 537872 | Problem Libthread panic error while opening large application files on Solaris.
Workaround
For example, if a war file contains 970 files, set the File Descriptor
limit to 1000: |
| 548426 | Problem Redeployment of an updated version of an application does not remove the contents of the previous deployment from the file system area of the application area. The default location of deployed files is install_dir/ias/APPS/modules/module_name/ or APPS/ear_name/module_name/ . 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 |
| 537084 |
Problem If Sun ONE Application Server is installed as root on a machine using the custom installation, the deploytool (DT) is not accessible by other uses to create applications on Solaris platforms.
Workaround
|
| ID | Summary |
|---|---|
| 4639241 | Problem Vendor specific parameters, such as global connection, servername, databasename, ifxinformixhost, etc., are not saved when datasource is registered using XML file.
Workaround |
| PointBase Database Installation (Solaris Platforms) | Problem The PointBase database installation requires access to the X Windowing System environment. If you are installing the pointbase database with the application server, the installation should have access to an X Windowing System. If there is no access to the X Windows environment, the PointBase database server will fail to start-up on that machine.
Workaround If the DISPLAY variable is set incorrectly, Sun ONE Application Server post installation commands fail. |
| 4625632 | Problem Unable to use Oracle 9i client libraries through iPlanet Type 2 Native Driver. Workaround Rename libclntsh.so.9.0 under, $ORACLE_HOME/lib to libclntsh.so.8.0 . |
| 4643903 | Problem On Solaris platforms, you will be unable to use the Oracle OCI driver if it has been registered under External JDBC Driver , through the Administration Tool. Workaround Ensure that $ORACLE_HOME is set in the iasenv.ksh script, under iASInstallDir /ias/env directory. |
| ID | Summary |
|---|---|
| 4640249 | Problem Session distribution of soap web application does not work as per sample application documentation.
Workaround |
| 549549 | Problem Samples fail after recreating tables in PointBase. Several of the J2EE Developer's Guide samples require that you to recreate the database tables before executing the samples a second time. If you use the SQL files provided to recreate the tables without restarting the application server, several of the J2EE Developer's Guide samples will fail.
Workaround |
| 548418 | Problem "Inserted value too large for column" errors when using Bank application.
Workaround |
| 558611 | Problem Cannot create new customer in Bank Application with the same SSN of a deleted customer. The Bank Application does not correctly update tables in the database, and therefore you cannot create a new customer with same SSN. |
| 548861 | Problem iPlanet Type 2 Native Drivers for Sybase gives errors with JPS 1.1.2.
Workaround |
| 549374 | Problem The setup_syb.bat and setup_syb.sh scripts for the Transactions sample will not execute.
Workaround |
| 550427 | Problem Documentation error in the J2EEGuide sample. In the chapter "Currency Converter EJB", the third point under "Assemble EAR File", the value of the context root of the web application, is incorrectly mentioned as j2eeguide-confirmer .
Workaround |
| - | Problem Documentation error in the Bank sample. Under the "Create bank.war Module" > "Modify Web Application Descriptor" topic, the login information in the "Security Tab" point is incorrect.
Workaround |
| 545753 | Problem Search functionality does not work when using JPS 1.1.2 with PointBase. Search functions do not work in JPS 1.1.2 when using the bundled PointBase database engine as the current version of PointBase bundled with Sun ONE Application Server 6.0 SP4 does not support subqueries. |
| 560667 | Problem Exception while running l10n application An exception is thrown when the user logs in as restaurant owner. |
| 562432 | Problem Hot deployment of Petstore Application throws exception.
Workaround |
| - | Problem When Sun ONE Application Server is installed with Microsoft IIS Webserver running on port number other than 80, the shortcut link for Sample Application will not work.
Workaround |
| ID | Summary |
|---|
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 January 15, 2004