Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 6 Release Notes |
Sun Java™ System Application Server Standard and Enterprise Edition Release Notes
Version 7 2004Q2 Update 6
Part Number 820-2610
These release notes contain important information available at the time of the release of the Sun Java™ System Application Server Standard and Enterprise Edition 7 2004Q2 Update 6. Enhancements, installation notes, known problems, and other late-breaking issues are addressed here. Read this document and associated documents before you begin using the Sun product.
This document contains the following sections:
Release Notes Revision HistoryThis section lists the changes that have been made in these release notes after the initial release of the Sun Java System Application Server 7 Standard and Enterprise Edition product.
Revision Date
Description of Change
June 2008
Added known issue 6635248.
October 2007
Updated the Known Problems and Limitations section in the Update 6 release of Sun Java System Application Server 7 2004Q2 Standard and Enterprise Edition
June 2007
Update 6 release of Sun Java System Application Server 7 2004Q2 Standard and Enterprise Edition
December 2006
Update 5 release of Sun Java System Application Server 7 2004Q2 Standard and Enterprise Edition
November 2005
Update 4 release of Sun Java System Application Server 7 2004Q2 Standard and Enterprise Edition
April 2005
Update 3 release of Sun Java System Application Server 7 2004Q2 Standard and Enterprise Edition
January 2005
Update 2 release of Sun Java System Application Server 7 2004Q2 Standard and Enterprise Edition
September 2004
Update 1 release of Sun Java System Application Server 7 2004Q2 Standard and Enterprise Edition
May 2004
Initial release of Sun Java System Application Server 7 2004Q2 Standard and Enterprise Edition
What’s NewThe Sun Java System Application Server 7 Standard and Enterprise Edition 2004Q2 Update 6 provides a high-performance J2EE platform suitable for broad deployment of application services and web services. The following changes have been made to the Update 6 release:
Java Web Services Developer Pack v1.5.1 Plug-in is available for Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 6. The plug-in can be downloaded at the following URL: http://www.sun.com/download/products.xml?id=432b5f8e
Platform SummaryThis section provides information on supported platform components for the Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 6.
This section includes:
Operating Systems and Distribution Types
The following table identifies the supported operating systems and distribution types for Sun Java System Application Server 7 2004Q2 Update 6:
1On Solaris 10, both file-based and packaged based installs are supported. Only global zone is supported. Local zones or local sparse root zone is not supported.
2 Superuser privileges are required for installing package-based and RPM-based distributions.
3 On Red Hat Advanced Server 2.1, HADB supports devices on ext2 file systems only.
4 On Windows XP Professional, only Standard Edition is available.System Requirements
The following table summarizes the Sun Java System Application Server 7 Standard and Enterprise Edition 2004Q2 Update 6 requirements.
4 32 and 64 bit here refers to the supported OS. Sun Java System Application Server is a 32 bit application.
- On UNIX, you can check your operating system version using the uname command. Disk space can be checked using the df command.
- On Solaris, ensure that the system-wide instance of perl under /usr/bin/perl is in the path. Application Server installation will fail if the default perl installation is not found.
- HADB is not supported on Microsoft Windows or Red Hat Enterprise Linux operating system versions in 64 bit mode. On Solaris (x86), HADB has been tested only in 32 bit mode of the operating system.
- HADB uses Intimate Shared Memory (SHM_SHARE_MMU flag) when it creates and attaches to its shared memory segments. The use of this flag essentially locks the shared memory segments into physical memory and prevents them from being paged out. Therefore, HADB database’s shared memory is locked into physical memory, which can easily impact installations on low end machines. Ensure you have the recommended amount of memory when co-locating Application Server and HADB.
JDBC Drivers and Databases
The Sun Java System Application Server Standard and Enterprise Edition is designed to support connectivity to any DBMS with a corresponding JDBC driver. For a list of components that Sun has tested and found to be acceptable for constructing J2EE compatible database configurations, refer to the following table:
Additional drivers have been tested to meet the JDBC requirements of the J2EE 1.3 platform with the JDBC Driver Certification Program. These drivers can be used for JDBC connectivity with Sun Java System Application Server. While Sun offers no product support for these drivers, we will support the use of these drivers with the Sun Java System Application Server.
Web Servers
This section lists the web servers that are supported for the Sun Java System Application Server 7 2004Q2 Update 6 Standard and Enterprise Edition.
Software Packages
This section lists the associated software packages that are supported for Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 6.
5 Use the JWSDP 1.4 common components available in the product CD to upgrade your JWSDP installation.
Browsers
This section lists the browsers that are supported with the Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 6.
Table 6 Browsers Supported
Browser
Version
Mozilla
1.4, 1.7
Netscape Navigator
4.79, 6.2
Internet Explorer
5.5 Service Pack 2, 6.0
Solaris Patches RequiredSolaris 8 users must install the Sun recommended patch cluster, available in the Recommended and Security Patches section at:
The required patches for Solaris 8 are 109326-06, 108827-26, and 110934 (any revision, for packaged-based installation only). Without these patches, which the installer checks for, you won’t be able to install or run the Sun Java System Application Server 7 2004Q2 Update 6 software. These patches are already contained in the latest recommended patch cluster.
Upgrade OptionsThis section contains the following topics:
Upgrading Sun Java System Application Server
The Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 6 installer allows you to upgrade from a previous version of the Application Server to the current version. The various Application Server installations on all the supported platforms can be upgraded to their corresponding version on the same platform and installation type. The following table identifies the upgrade options available.
- After an upgrade, you must compare the new configuration files with the original files in the backup directory for any changes. Custom settings made in the original configuration files might not be carried over to the new files after upgrading. You might experience issues during server restart if the new configuration files are not in sync with the older files that contained customized settings. The following files will be effected during an upgrade:
For more details on this and other important prerequisites for upgrading, see Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 2 Installation Guide.
Upgrading the High Availability Database
This section contains the following topics:
Pre-upgrade Tasks/Data Migration
Before you begin the upgrade, keep the HADB history files, management agent configuration files, log files and repository, and all the data devices outside the installation path. Use the following procedure to move the management repository and configuration files:
- Stop all the old management agents and keep the HADB nodes running.
- On each host, move the repository directory to the new location.
- On each host, copy the dbconfig directory to the new location.
- On each host, update the mgt.cfg file, and set the correct path for dbconfig and repository directory.
- Start the management agents using the updated mgt.cfg file.
Upgrade Procedure
To upgrade from HADB version 4.4.x to version 4.4.2-7, use the following procedure:
- Perform the pre-upgrade tasks mentioned under "Pre-upgrade Tasks/Data Migration" .
- Install HADB version 4.4.2-7 on all HADB hosts (on another path than that of version 4.4.x, for instance on /opt/SUNWhadb/4.4.2-7).
- Install the HADB 4.4.2-7 version on the hadbm client hosts, if they are different than that of the HADB hosts.
- Stop all management agents running on all HADB hosts.
- Start the management agent processes using the HADB 4.4.2-7 software, with the old configuration files. In the remaining steps, use the hadbm command found in the HADB 4.4.2-7 /bin directory.
- Register the package in the management domain (default package name becomes V4.4, so another package name may be required to avoid conflicts with existing packages having the same name):
hadbm registerpackage --packagepath=/opt/SUNWhadb/4.4.2-7 V4.4.2-7
- Run the hadbm listpackages command and check that the new package is registered in the domain.
- Restart the database with the new hadbm version 4.4.2-7. If it is necessary to move the devices and history files, run online upgrade combined with setting new paths for devices and history files in one single operation:
hadbm set packagename=V4.4.2-7,devicepath=new_devpath,historypath=new_histpath
If the devices and history files are already outside the installation directory, run the following command, which only does a rolling restart of the nodes:
hadbm set packagename=V4.4.2-7 database name
- Check that the database status is "running" (using the hadbm status command) and that it functions normally, serving the client transactions.
- If everything is working, the old installation can be removed later. Before unregistering the old package, remove all references to the old package from the ma repository. Otherwise, hadbm unregisterpackage will fail with "package in use" error message. A dummy reconfiguration operation, for instance, hadbm set connectiontrace=same as previous value will remove all references to the old package.
- Unregister the old package:
hadbm unregisterpackage [--hosts=host-list] old pacakge name
- Remove the old installation from the file system.
Testing the Upgrade
On Solaris, to test that the upgrade was successful, check that the upgrade was performed properly using the following procedure:
- Ensure that the running processes use the new binaries. Check the following in all HADB nodes:
new path/bin/ma -v
new path/bin/hadbm -v
- Check whether the database is running. The following command should show that all the HADB nodes are in a "running" state.
new path/bin/hadbm status -n
- Ensure that the products using HADB have changed their pointers to point to the new HADB path.
- The products using the HADB can run their upgrade tests to verify the HADB upgrade is also working.
- After an online upgrade, if the new version does not work properly, go back to using the previous HADB version. However, if there has been a change to the management agent repository, the HADB itself can be downgraded, but the new management agent must be kept running.
Using Migration ToolIf you have an existing J2EE application that runs on another vendor’s application server, you can use the Sun Java System Migration Tool to migrate the application and run it on the Sun Java System Application Server 7 2004Q2 Update 6 release. The migrated application will run on the Sun Java System Application Server 7 2004Q2 release without any modifications. However, to use the high availability features, change the DTD version of the sun-ejb-jar.xml deployment descriptors to point to sun-ejb-jar_2_0-1.dtd instead of sun-ejb-jar_2_0-0.dtd.
Sun ONE Studio 5 Standard Edition Update 1The Sun ONE Studio 5, Standard Edition product that you can use with the Sun Java System Application Server has its own documentation that can be found at the following location:
http://docs.sun.com/app/docs/coll/790.4
Other IDEs that you can use include, Sun Java Studio 5 Standard Edition Update 1, Sun Java Studio Enterprise 6 2004Q1 and other 3rd party IDEs, for example, Borland’s JBuilder X.
Other Requirements and Limitations
- ACL applet in Admin GUI is not loaded in browsers that do not have Java and cookies enabled. Check your browser settings to ensure that both Java and cookies are set to enabled before accessing the Application Server Admin GUI.
- Application Server is not supported over NFS.
- Application Server 7.0 or 7.1 does not work with J2SE 5.0.
Although the file-based installation can be performed on NFS, it is not recommended to run the Application Server in this configuration for the following reasons:
- Issues with timestamp locking and file synchronization.
- Stability of the Application Server on NFS depends on the network’s availability and reliability.
- NFS introduces an additional point of failure.
- Hard to troubleshoot when there is an NFS issue. Application Server will report vague error messages.
By default, the fix for this bug is disabled. To enable the fix, modify your web server’s configuration files and Application Server’s server.xml file as described in the following procedure:
For Init fn="load-modules" add init-passthrough and service-passthrough in funcs.
Example: funcs="init-passthrough,service-passthrough,name-trans-passthrough,change_hostheader_init,change_hostheader"
Init fn="change_hostheader_init" enabled ="true" debug="false"
By default, this flag is disabled. Set debug=”true” to enable logging for the fix. By default, it is disabled.
If you set enabled="false" your getServerPort will return the port number as it used to do earlier. If you set enabled="true", getServerPort will return the Application Server port you specify in server.xml.
After PathCheck fn="deny-existance" path="*/WEB-INF/*, add
Service fn="change_hostheader" inside <Object name="lbplugin">.
In server.xml, change the servername format to servername="hostname:port".
The hostname should be the same as before. Change the port number to the Application Server instance’s port number. The port number specified here will be returned by the getServerPort() method.
In some cases, the servername attribute might be specified as server-name.
The following high availability requirements must be met before configuring the Sun Java System Application Server High Availability component:
- HADB supports IPv4 only.
- The network must be configured for UDP multicast.
- Do not use dynamic IP addresses (DHCP) for hosts used in create domain, extend domain, hadbm create, or hadbm addnodes commands.
- If running HADB on Red Hat Linux 3.0, you must install Update 4 to avoid problems with excessive swapping by the operating system. See bug id 6158393.
- HADB does not support any Microsoft Windows or Red Hat Enterprise Linux operating system version in 64 bit mode.
- HADB File System Support: There are several important considerations before you configure HADB to use one of the supported file systems.
- Make sure write caching is disabled for hard drives storing data devices and log files.
- On RedHat Linux, use the /sbin/hdparm utility for IDE disks. The command /sbin/hdparm -W0 /dev/hda disables write caching for disk hda. Use /sbin/hdparm -I device to get detailed status information about the drive. For SCSI disks, the sdparm utility (http://sg.torque.net/sg/sdparm.html) must be downloaded and installed, because it is not part of the default RedHat Linux Advanced Server distribution. Be very careful using these utilities, as they can be harmful to your hard drive if used incorrectly.
- On Solaris (SPARC or x86), the format -e utility should be used. Make sure the -e option is used, otherwise, the ’cache’ entry will not be present in the command menu.
- On Windows, open the Device Manager. Find your hard drive, bring up its properties, and select the Disk Properties tab. A checkbox indicates whether write caching is enabled.
For details on important installation prerequisites and troubleshooting options, see Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 2 Installation Guide.
Accessing the DocumentationThe Sun Java System Application Server documentation is provided in a number of ways:
- Manuals—You can view Sun Java System Application Server manuals and release notes in HTML and in printable PDF downloads at:
http://docs.sun.com/app/docs/prod/sjs.asse
- Online help—Click the Help button in the graphical interface to launch a context-sensitive help window.
- Man pages—To view man pages at the command line, you must first add install_dir/man to your MANPATH environment variable (Solaris unbundled only). After setting the variable, you can access man pages for the Sun Java System Application Server commands by typing man command_name on the command line. For example:
Sun Java System Application Server 7 2004Q2 Update 6 DocumentationThe Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 manuals are available as online files in Portable Document Format (PDF) and Hypertext Markup Language (HTML).
The following table lists tasks and concepts described in the Sun Java System Application Server manuals. The following manuals have been updated for the Sun Java System Application Server 7 2004Q2 Update 6 Standard and Enterprise Edition release. For a full list of all available manuals, see http://docs.sun.com/app/docs/prod/sjs.asse.
Resolved IssuesThe following table lists the critical issues resolved in Sun Java System Application Server Standard and Enterprise Edition 7 2004 Update 1, Update 2, Update 3, Update 4, Update 5, and Update 6 releases.
Known Problems and LimitationsThis section describes known problems and associated workarounds for the Sun Java System Application Server 7 2004Q2 Update 6 Standard and Enterprise Edition.
Note
If a problem statement does not specify a particular platform, the problem applies to all platforms.
This information is organized into the following sections:
Installation and Uninstallation
This section describes the known installation and uninstallation issues and associated solutions.
ID
Summary
6602615
After upgrading from localized version of Application Server 7.1 Update 5 to Application Server 7.1 Update 6, the upgraded instance fails to start on Soalris 10 Update 3 and above.
There is a conflict between the Message Queue (MQ) versions bundled with Solaris and the version bundled with Application Server.
Solution:
1. Remove the following MQ packages using the pkgrm command:
2. Install the corresponding OS-bundled base, ja, and zh packages.
6606419
Upgrade from localized version of Application Server 7.1 Update 5 to Application Server 7.1 Update 6 fails.
The installer fails to delete the directory, SUNWhadb/4.
Solution:
Do one of the following:
6606417
Upgrade from localized version of Application Server Enterprise Edition 7.1 Update 5 to Application Server Enterprise Edition 7.1 Update 6 does not change the SUNWhadb/4 symbolic links.
Solution:
Changed the symbolic link to 4.4.2-30.
6606979
Upgrade to localized version of Application Server Enterprise Edition 7.1 Update 6 displays English index.html
Solution:
Perform the following steps:
3. Change directory to <AppServer_install_dir>/domains/domain1/server1/docroot.
4. Rename index.html to index.html_en.
5. Copy AppServer_install_dir/lib/install/templates/index.html to AppServer_install_dir/domains/domain1/server1/docroot.
6245916
When upgrading from localized Application Server 7.1 Update 2 to Update 3/Update 4/Update 6 in Japanese and Simplified Chinese locales, the localized welcome page and index.html is displayed from Update 2.
The localized version of Application Server 7.1 Update 6 contain localized files from Application Server 7.1 Update 2.
Solution
After upgrading to Update 6, refer to the English welcome page and index page located at:
Appserver_Install_Dir/docs/about.html
Appserver_Install_Dirlib/install/templates/index.html
To register Sun Java System Application Server, use the following URLS:
Japanese: https://www.sun.com/software/product_registration?locale=ja_JP
Simplified Chinese: https://www.sun.com/software/product_registration?locale=zh_CN
To view the latest index.html (in English) for an existing domain, instead of the old localized version, copy the index.html to the docroot folder:
copy Appserver_Install_Dir/lib/install/templates/index.html to
Appserver_domain_root/domains/domain1/admin-server/docroot
Before creating a new domain, replace the localized index.html with the English index.html:
Copy Appserver_Install_Dir/lib/install/templates/index.html to
Appserver_Install_Dir/lib/install/templates/{ja,zh_CN}/index.html
Ensure that you back up your current Japanese or Chinese index.html file.
6222700
When upgrading from localized Application Server 7.1 Update 2 to Update 3/Update 4/Update 6 in Japanese and Simplified Chinese locales, the default page of server1 instance is displayed in English.
6245424
After uninstalling localized versions of Application Server Update 6, the localized packages/RPMs will remain.
Solution
Remove the localized packages/RPMs first and then run the uninstall program. Perform the following procedure on package-based Solaris installations.
6. Remove the following packages:
pkgrm SUNWjaspx SUNWjasdmo SUNWjiquc SUNWjiqu SUNWjaso
pkgrm SUNWjjmail SUNWjjaf SUNWjasaco SUNWjascmo SUNWjaspx
pkgrm SUNWcaspx SUNWcasdmo SUNWciquc SUNWciqu SUNWcaso
pkgrm SUNWcjmail SUNWcjaf SUNWcasaco SUNWcascmo SUNWcaspx
7. Run the Application Server uninstall program.
8. Remove the Application Server installation directory.
rm -rf Appserver_Install_Dir
Perform the following procedure on RPM-based Linux installations.
1. Remove the following RPMs:
rpm -e SUNWjasaco-7.1.0-02.src.rpm
rpm -e SUNWjascmo-7.1.0-02.src.rpm
rpm -e SUNWjasdmo-7.1.0-02.src.rpm
rpm -e SUNWjaso-7.1.0-02.src.rpm
rpm -e SUNWjaspx-7.1.0-02.src.rpm
rpm -e SUNWjjaf-7.1.0-02.src.rpm
rpm -e SUNWjjmail-7.1.0-02.src.rpm
rpm -e SUNWasaco-zh_CN-7.1.0-02.src.rpm
rpm -e SUNWascmo-zh_CN-7.1.0-02.src.rpm
rpm -e SUNWasdmo-zh_CN-7.1.0-02.src.rpm
rpm -e SUNWaso-zh_CN-7.1.0-02.src.rpm
rpm -e SUNWaspx-zh_CN-7.1.0-02.src.rpm
rpm -e SUNWjaf-zh_CN-7.1.0-02.src.rpm
rpm -e SUNWjmail-zh_CN-7.1.0-02.src.rpm
2. Run the Application Server uninstall program.
3. Remove the Application Server installation directory.
rm -rf Appserver_Install_Dir
Perform the following procedure on Windows installations:
1. Run the Application Server uninstall program.
2. Delete Appserver_Install_Dir.
6208875
Upgrade installation Failed:java.io.FileNotFoundException
File-based upgrade of HADB on Solaris SPARC, Solaris x86, and Linux will encounter problems in certain scenarios, as described here:
Installation fails with the following exception:
java.io.FileNotFoundException: /sun/appserver7/./SUNWhadb/4 (Is a directory)
Upgrade scenarios: 7.1RTM/7.1ER1/7.1UR1 file-based upgrade to 7.1UR2.
Solution
Rename the file-based-installing-directory/SUNWhadb/4 softlink to another name, such as, SUNWhadb/3. Restart the upgrade.
6217112
Incremental installation is not working on Windows platforms.
Sample applications can be installed along with Application Server. They cannot be incrementally installed.
Solution
Select to install sample applications at the beginning of installation. During incremental installations, do not select the sample applications option.
5006942
On Windows, the services created have the start type set by default to “Automatic” after an upgrade.
Solution
1. Open the Windows services.
2. Change the start type of the servers to “Manual.”
6217097
File-based upgrade performed as a non-root user seems to fail if the Application Server binaries for the upgrade were not downloaded as non-root user.
Solution
The downloaded binaries need to be owned by the non-root user. The downloaded archive must be unzipped by the user who will do the installation or upgrade. Otherwise this is known to lead to permissions issues while the JDK is being upgraded.
Server Startup and Shutdown
This section describes the known startup and shutdown issues and the associated solutions.
Database Driver
This section describes the known database driver issues and associated solutions.
Logging
Web Container
This section describes the known web container issues and associated solutions.
Message Service and Message-Driven Beans
This section describes the known issues in Java Message Service (JMS), Sun Java System Application Server Standard and Enterprise Edition, and message-driven beans issues and the associated solutions.
Java Transaction Service (JTS)
This section describes the known Java Transaction Service (JTS) issues and the associated solutions.
Recovery
There are some known problems with the recovery implementations of some of the JDBC drivers. For these known problems, Sun Java System Application Server provided some workarounds. By default, these workarounds will not be used unless you explicitly indicate that these workarounds are to be used.
- Issue with the Oracle (R) JDBC driver—Oracle XA Resource implementation's recover method repeatedly returns the same set of in-doubt Xids regardless of the input flag. According to the XA specs, the Transaction Manager should initially call XAResource.recover with TMSTARTSCAN and then call XAResource.recover with TMNOFLAGS repeatedly until no Xids are returned.
Oracle XA Resource's commit method also has some problems, which are addressed in a workaround provided by the Application Server. To enable this workaround, the following property should be added to the transaction-service subelement in the server.xml file: oracle-xa-recovery-workaround
This property value should be set to true.
Transactions
In the server.xml file, res-type is used to demarcate the connection as non-XA or XA. This demarcation is used to identify the configuration of the data source to drive data. For example, in the Datadirect driver, the same data source can be used as either XA or non-XA.
The default behavior of the data source is non-XA. To make the data source behave as XA with the connpool element for transactions, res-type is needed. For the connpool element to work and participate in transactions, add the following for the attributes res-type in the server.xml file:
res-type="javax.sql.XADataSource"
Application Deployment
This section describes the known application deployment issues and associated solutions.
Verifier
This section describes the known verifier issues and associated solutions.
Load Balancer
This section describes the known load balancer issues and associated solutions.
ID
Summary
6422893
The Application Server 7.1 UR5 load balancer plug-in does not recognize the HTTPS listeners even when the https-routing property is set to true in loadbalancer.xml.
Solution
If you are installing Application Server 7.1 afresh:
1. Install Application Server 7.1 UR5 without the load balancer plug-in by deselecting the load balancer during product installation.
2. Install the Java Enterprise System (JES) 3 or JES4 Application Server from http://www.sun.com/software/javaenterprisesystem
3. Download JES component Patch 10 from http://sunsolve.sun.com
- For package-based patches, the patch ids are 119166-16(Solaris Sparc), 119167-16 (Solaris x86), 119168-16 (Linux)
- For file-based patches, the patch ids (Enterprise Edition) are 119169-08 (Solaris Sparc), 119170-08 (Solaris x86), 119171-08(Linux) , 119172-08 (Windows)
- For file-based patches, the patch ids (Platform Editon) are 119173-08 (Solaris Sparc), 119174-08 (Solaris x86), 119175-08 (Linux), 119176-08 (Windows)
4. Begin installation. From the component list, select only the load balancer plug-in and proceed with the installation of the load balancer plug-in in the specified Web Server location.
5. Configure Application Server 7.1 UR5 and Web server to use this plug-in.
If you already have an installation of Application Server 7.1:
1. Rename the libpassthrough.so file and all other related files, such as LBPluginDefault_root.res and LBPlugin_root.res installed as part of the Application Server 7.1 UR5 load balancer plugin.
2. Install the Java Enterprise System (JES) 3 or JES4 Application Server from http://www.sun.com/software/javaenterprisesystem
3. Download JES component Patch 10 from http://sunsolve.sun.com
- For package-based patches, the patch ids are 119166-16(Solaris Sparc), 119167-16 (Solaris x86), 119168-16 (Linux)
- For file-based patches, the patch ids (Enterprise Edition) are 119169-08 (Solaris Sparc), 119170-08 (Solaris x86), 119171-08(Linux) , 119172-08 (Windows)
- For file-based patches, the patch ids (Platform Editon) are 119173-08 (Solaris Sparc), 119174-08 (Solaris x86), 119175-08 (Linux), 119176-08 (Windows)
4. Begin installation. From the component list, select only the load balancer plug-in and proceed with the installation of the load balancer in the specified Web Server location.
5. Configure Application Server 7.1 UR5 and Web server to use this plug-in.
6338687
Load Balancer Plug-in cannot handle URL/URI greater than 8K.
Ensure not to create a URL/URI greater than 8k if it is going to be forwarded by the load balancer plug-in to the Application Server.
6262746
Load balancer plug-in on Apache web server, installed on Solaris 10 (SPARC and x86), is not a supported configuration.
Solution
Or,
6155134
Manual setting of path is required for webservers to start.
After installing load balancer plug-in on Windows for IIS or Apache, append the path of the Application Server to the Path environment variable.
4761151, 4825429, 4981545
Intermediate form and basic authentication failures while sending intermittent SSL and non-SSL requests through load balancer plug-in. Displays a 502 Bad Gateway error message. The persistency of proxy-to-container connections is not maintained with the default settings.
Loadbalancer looses persistent connections to the application server due to deployment/undeployment on the application server and/or due to keep alive timeout or due to stale connections in the load balancer’s connection pool. When this happens, some of load balancer’s requests will fail and the error page is displayed. This typically occurs in a development environment where frequent deployment/undeployment and other configuration changes are tried and tested.
Solution
Set the keep alive timeout on the appserver to 0.
Using web-based Administration interface:
1. Launch the Administration console.
2. Select HTTP Server -> Tuning.
3. In the HTTP Persistent Connection Timeout field, enter 0 (last text box on the page)
4. Apply changes and restart the appserver.
Using the Command-line Interface:
1. Add the line: KeepAliveTimeout 0 in init.conf of appserver
2. Launch the asadmin reconfig command.
3. Restart the appserver.
4962735
On Linux, Apache Web Server 1.3.27 does not start after installing load balancer plug-in and sec_db files.
Solution
Include the following lines in /src/MakeFile after “End of automatically generated section,” and just before “OBJS= \”. Also, make sure the Application Server libraries are already installed in a particular location:
LIBS+= -licuuc -licuil8n -lnspr4 -lpthread -lxerces-c -lsupport -lnsprwrap -lns-httpd40 LDFLAGS+= -L/space/SJSAS/installations/lib.
Where: /space/SJSAS/installations is the location of the application server installation. For more information, see Appendix “Compiling Apache Web Server” in Sun Java System Application Server Administration Guide.
5018537
Identity Server/Application Server Integration Services unavailable error shown during failover.
Loadbalancer.xml has “/” as the context-root for a web-module. After a failover, since there is no context root, a “Default” string is assigned as the path of the update JROUTE cookie. This results in two JROUTE cookies on the browser side.
1. The old JROUTE cookie pointing to the failed instance with “/” aspath.
2. The new JROUTE cookie pointing to the new instance with “/Default” as the path.
The browser would always use the old outdated cookie (1) and consequently it results in redirects and failovers, and sometimes the browser itself fails.
Solution
Have specific context root for all web modules. For example:
<web-module context-root=”appl” enabled=”true” disable-timeout-in-minutes=”60” error-url=”appl-lberror.html” />
<web-module context-root=”app2” enabled=”true” disable-timeout-in-minutes=”60” error-url=”app2-lberror.html” />After the failover, the JROUTE gets the path as “/appl” which is valid and works correctly.
5007720
Log message not proper for invalid value for error-url in web-module.
When the error-url attribute in web-module tag of loadbalancer.xml is set, as follows, to an invalid value, such as:
<web-module context-root="app1" enabled="true" disable-timeout-in-minutes="60" error-url="abc"/>
The log message displayed is as follows:
warning (11113): reports: lb.configurator: XML_VALIDATOR_WARNING: Invalid format for the error-url sun-http-lberror.
However, the log should be:
warning (20015): reports: lb.configurator: XML_VALIDATOR_WARNING: Invalid format for the error-url abc
High Availability
This section describes the known high availability issues and associated solutions.
Server Administration
This section contains the following sections:
Command Line Interface (CLI)
This section describes the known command-line interface issues and associated solutions.
Administration Infrastructure
This section describes the known administration infrastructure issues and associated solutions.
ID
Summary
6635248
*~ wildcard pattern does not work as documented.
http://docs.sun.com/source/817-2176/dnwldcrd.html#24629 shows a list of available wildcard patterns
used by Sun Application Server. However, the wildcard pattern with tilde in the ppath does not work as
documented.
Solution
Add one of the following to the obj.conf file.
• <Object ppath="/test[^h].html"> PathCheck fn="htaccess-find"
filename=".htaccess"</Object>
• <Object ppath="*~*(.testh.html|.testh.html/)">
PathCheck fn="htaccess-find" filename=".htaccess" </Object>
• <Object ppath="*~*.testh.html*"> PathCheck fn="htaccess-find" filename=".htaccess"
</Object>
6245376
Virtual server’s obj.conf is not removed after deleting the virtual server.
By default, the configuration file for a virtual server is not removed from the filesystem after deleting the virtual server.
Solution
Manually remove the virtual_server-obj.conf file of the deleted virtual server.
4686003
HTTP Quality of Service limits are not enforced.
Quality of Service (QOS) includes a means of specifying the maximum number of HTTP connections and the bandwidth limit. When these attributes are exceeded, a 503 error should be returned to the client. However, after enabling QOS through the Administration interface, the server does not enforce the QOS limits.
Solution
To fully enable QOS features, you must manually add an AuthTrans fn=qos-handler line to the top of the default object in the obj.conf file of the virtual server. The qos-handler Server Application Function (SAF) and obj.conf configuration file are described in the Developer's Guide to NSAPI.
4740022
SNMP: END OF MIB is returned when adding and starting a new instance server.
If you add and start a new instance without shutting down the instance server and subagent, an END OF MIB message is returned.
Solution
1. To view a new instance, make sure the subagent and all the instance server processes are shut down. Under each server ->Monitoring -> "Enable SNMP Statistics Collection: on", apply the change, then restart each instance server, and start only one subagent process again.
2. If the subagent is already running, don’t start any extra subagent processes in any instance. There can only be one master agent and one subagent for a Application Server installation (common for all domains/instances).
4865739
Negative test for instance port in server.xml corrupts domains.bin
If the port number and/or IP Address includes a letter character, no new instances can be created and the current instances become unmanageable.
Solution
1. Edit the server.xml file and the backup server.xml and correct the port number and/or IP Address.
2. Execute the asadmin reconfig command using the keepmanualchanges=true option.
3. Using the Administration Interface, stop the instance by selecting the instance name in the Administration tree.
4. Restart the administration server and application server instance.
Administration Interface
When using Administration interface, make sure that the browser is configured to check for newer versions of pages from the server, instead of picking these from cache. Generally, default browser settings would not cause problems.
This section describes the known administration graphical user interface issues, and the associated solutions.
Sample Applications
This section describes known sample application issues and associated solutions.
ORB/IIOP Listener
This section describes known ORB/IIOP-Listener issues and associated solutions.
Documentation
This section describes the known documentation issues and associated solutions.
ID
Summary
6489168
Instructions in the README.txt file in the <addons_install>/se directory need to be revised for clarity.
The README.txt currently reads as follows:
Installing on Solaris as root user
1) Copy SUNWaspx from the RootInstall directory on the CD to directory on your machine.
2) Change the directory to where SUNWaspx was copied.
$ cd <addons_install>/ProxyPlugin
Solution:
The instructions in README.txt must read as follows:
1) Copy SUNWaspx from the RootInstall directory on the CD to a directory on your machine.
$ cp -R <addons_install>/se/WebPlugins/RootInstall/SUNWaspx /var/tmp
2) Change the directory to where SUNWaspx was copied.
$ cd /var/tmp
6511489
Information regarding KeepAliveFlushes in the Sun Java System Application Server Performance Tuning guide is incorrect.
The Performance Tuning guide currently has the following information:
The number of times the server had to close a connection because the KeepAliveCount exceeded the MaxKeepAliveConnections. This setting is not tunable.
Solution
The statement must read as follows:
Application Server does not close existing connections when the KeepAliveCount exceeds the MaxKeepAliveConnections. Instead, new keep-alive connections are refused and the KeepAliveRefusals count is incremented.
6495372
The section on Dynamic Deployment in Chapter 13 - Application Deployment of the Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 3 Administration Guide (English) or the Sun ONE Application Server 7 Administration Guide (Japanese) does not warn users about errors that could occur if they attempt dynamic deployment when a client is accessing the server.
Solution
It is recommended that you execute the online dynamic deployment only when a client is not accessing the server. An error could occur in the data processing for memory and files if a client accesses the server during the application deployment process.
6412668
The following statement in the Configuring the File Cache section of the Application Server 7 Performance Tuning Guide is incorrect:
By default, Transmit File is enabled on NT, and not enabled on Unix. On Unix, enable Transmit File for platforms that have native OS support for PR_TransmitFile, which currently includes HP-UX and AIX. It is not recommended for other Unix/Linux platforms.
Solution
The statement must read as follows:
By default, Transmit File is enabled on NT, and not enabled on Unix. On Unix, Transmit File is enabled for platforms that have native OS support for PR_TransmitFile, which currently includes Solaris, HP-UX and AIX. It is not recommended for other Unix/Linux platforms.
6067211
Change in behavior of sessionFilename for memory persistence in Application Server 7 2004Q2 as compared to Application Server 7.0 series not documented.
The sessionFileName property in the manager-properties table from Developer’s Guide to Web Applications should read:
Specifies the absolute or relative pathname of the file in which the session state is preserved between application restarts, if preserving the state is possible. A relative pathname is relative to the temporary directory for this web module. The actual name of the file gets prepended with the context information. For example, if you specify fileName to be /tmp/Session and the web app context name is MemoryPersistenceApp, the session state is preserved in /tmp/MemoryPersistenceAppSession.
This is applicable only if the persistence-type attribute of the session-manager element is memory.
5060001
Typo in sample config.xml in Developing JAX-RPC Web Services chapter.
In the Developer’s Guide to Web Services chapter, Developing JAX-RPC Web Services, the sample config.xml incorrectly capitalizes the S in targetNamespace and typeNamespace.
Solution
targetNameSpace should be targetNamespace.
typeNameSpace should be typeNamespace.
5050378
Incorrect button label specified in Application Server 7 2004Q2 Getting Started Guide.
In Chapter 1, under Session Persistence Types, the guide incorrectly states to use the Save button to complete the procedure.
There is no Save button. Use the OK button.
6267772
Instructions for configuring Borland OptimizeIt are incorrect.
Sun Java System Application Server Developer’s Guide contains a typo in instructions for configuring Borland OptimizeIt Profiler.
Solution
Use the following parameters for JVM options in the Profiler tab:
-DOPTITHOME=Optimizeit_dir
-Xbootclasspath/p:/Optimizit_dir/lib/oibcp.jar
-Xrunpri:startAudit=t5039674
Error in asadmin create-jdbc-connection-pool man page.
The current description of --restype is incorrect.
The -restype must be specified to disambiguate when a Datasource class implements both interfaces. An error is produced when this option has a legal value and the indicated interface is not implemented by the datasource class. This option has no default value.
Solution
--restype must be specified to disambiguate when a datasource class implements more than one of the JDBC interfaces javax.sql.DataSource, javax.sql.ConnectionPoolDataSource or javax.sql.XADataSource. An error is produced when this option has a legal value and the indicated interface is not implemented by the datasource class.
5010038
Incorrect information in Administration Console online help on security realms.
In Application server Administration console, under Appserver instances>Server1>Security>Realms, the help file lists the different realms as: file, ldap, certificate, solaris.
This is incorrect. The actual realms are: file, ldap, certificate, agentRealm. The Application Server installer sets the security realm to agentRealm by default.
6190702
hadbm help gives outdated information.
Solution
For the latest information, see Chapter, “Administering the High-Availability Database (Enterprise Edition),” in Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 3 Administration Guide http://docs.sun.com/app/docs/doc/819-2783.
4970418
In the create-ssl man page, a space is missing between --certname and cert_name.
Solution
The correct syntax for the --certname option is as follows:
--certname cert_name
4993601
Outdated help files from Sun ONE Application Server 7, Enterprise Edition are displayed.
Solution
If you have previously installed a different version of the Sun Java System Application Server (for example, Sun ONE Application Server 7, Enterprise Edition), make sure that your MANPATH environment variable points to your current installation directory.
5008199
Documentation error in the example section of the delete-jvm-options manpage.
The example should read as follows:
asadmin delete-jvm-options --user admin --password adminadmin
--host localhost --port 4848 --instance server1 -- "-Djava.security.policy=/var/opt/SUNWappserver7/domains/domain1/server1/config/server.policy"None
Installation Guide PDF file in product CD is corrupt.
Solution
Use the HTML version of the Installation Guide.
Redistributable FilesSun Java System Application Server Version 7 2004Q2 Update 6 does not contain any files which you can redistribute.
How to Report Problems and Provide FeedbackIf you have problems with Sun Java System Application Server, contact Sun customer support using one of the following mechanisms:
- Sun Software Support services online at
http://www.sun.com/service/sunone/softwareSo 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
You might also find it useful to subscribe to the following interest group, where Sun Java System Application Server topics are discussed:
Sun Welcomes Your Comments
Sun is interested in improving its documentation and welcomes your comments and suggestions. Use the web-based form to provide feedback to Sun:
Please provide the full document title and part number in the appropriate fields. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document. For example, the part number of this Release Notes document is 820-2610.
Additional Sun ResourcesUseful Sun Java System information can be found at the following Internet locations:
- Sun Java System Documentation
http://docs.sun.com/db/prod/sjs.asse- Sun Java System Professional Services
http://www.sun.com/service/sunjavasystem/sjsservicessuite.html- Sun Java System Software Products and Service
http://www.sun.com/software- Sun Java System Software Support Services
http://www.sun.com/service/sunone/software- Sun Java System Support and Knowledge Base
http://www.sun.com/service/support/software- Sun Support and Training Services
http://training.sun.com- Sun Java System Consulting and Professional Services
http://www.sun.com/service/sunps/sunone- Sun Java System Developer Information
http://developers.sun.com- Sun Developer Support Services
http://www.sun.com/developers/support- Sun Java System Software Training
http://www.sun.com/software/training
Copyright © 2007 Sun Microsystems, Inc. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
SUN PROPRIETARY/CONFIDENTIAL.
U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.
Use is subject to license terms.
This distribution may include materials developed by third parties.
Portions may be derived from Berkeley BSD systems, licensed from U. of CA.
Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.
Copyright © 2075 Sun Microsystems, Inc. Tous droits réservés.
Sun Microsystems, Inc. détient les droits de propriété intellectuels relatifs à la technologie incorporée dans le produit qui est décrit dans ce document. En particulier, et ce sans limitation, ces droits de propriété intellectuelle peuvent inclure un ou plus des brevets américains listés à l'adresse http://www.sun.com/patents et un ou les brevets supplémentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.
Propriété de SUN/CONFIDENTIEL.
L'utilisation est soumise aux termes du contrat de licence.
Cette distribution peut comprendre des composants développés par des tierces parties.
Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l'Université de Californie.
Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC I