Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 Update 7 Release Notes

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.
Enabling fix for bug id 6275091: getServerPort() returns port 80 if the Host header does not contain port number.

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:
1. Modify magnus.conf.
  
  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"
2. Enable the change by specifying:
  
  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.
3. Modify obj.conf.
  
  After PathCheck fn="deny-existance" path="*/WEB-INF/*, add
  
  Service fn="change_hostheader" inside <Object name="lbplugin">.
4. Modify server.xml.
  
  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.
High Availability Requirements and Limitations

The following high availability requirements must be met before configuring the Sun Java System Application Server High Availability component:
- HADB requires 512 MB minimum memory and 1GB recommended memory to work properly with the Application Server.
  
  If you install Application Server and HADB on the same machine, the minimum memory required is 1.5GB and the recommended memory is 2GB.
- 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 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.