Release Notes for Sun^TM ONE Application Server, Enterprise Edition

Uninstallation Instructions

1. Ensure that all webserver and application server processes have been shutdown.
2. Ensure that the directory server is running.
3. Become the user who had installed the application server installation for which you want to backout the patch.
4. Change working directory to the directory where the backup data is saved. The backup data is saved in a directory named backup_patch number in your Sun ONE Application Server installation directory:

Example: cd /opt/appserver/ias/backup_6

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.

5. If you want all the files in the backup directory to be removed after uninstalling Maintenance Update 6, set the REMOVE_BACKUPFILES environment variable to 1.

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.


6. Uninstall the Update by typing:

./unpatch

Special Uninstallation Instructions

• If the installation process quits after patching some of the files, then follow these steps to restore the older files:
  1. Change the working directory to the backup_patch number directory present in your Sun ONE Application Server installation.
  2. Give execute permission to the file, unpatch
  3. Run the following command:

  ./unpatch

  This command will restore the files that were patched.

• To remove the fix for Bug Id: 4819229 replace the line, $JAVA_HOME/bin/java ${JAVA_ARGS} com.kivasoft.engine.Engine $opts in kjs script, located in install_dir/ias/bin directory, over the following lines:

  ## Start fix for bug 4819229
  d_opts=""
  mod_opts=""

  for optvar in $opts
  do
  

  echo $optvar |grep "^-D" >/dev/null
  if [ $? -eq 0 ]
  then
  d_opts="$d_opts $optvar"
  else
  mod_opts="$mod_opts $optvar"
  fi
  

  done

  if [ ! -z "$d_opts" ]
  then
  

  JAVA_ARGS=${JAVA_ARGS}${SPACE}$d_opts

  fi

  $JAVA_HOME/bin/java ${JAVA_ARGS} com.kivasoft.engine.Engine $mod_opts
  ## End fix for bug 4819229

• If you are running Rich clients, after uninstalling the patch, make sure to copy the older install_dir/ias/classes/java/iasacc.jar file to the directory where the Rich client is installed.

Special Instructions

---

• Workaround for bug fix 4990938

  As a result of the fix for bug ID 4990938, a manual workaround is necessary while upgrading from Application Server 6.5SP1 MU5 to MU6. This workaround necessiates the use of the web connector plu-in from MU5.

  Therefore, after upgrading to Application Server MU6, you must replace the MU6 web connector plug-in with the plug-in from MU5.The procedures given here use the Sun ONE Web Server as an example. Use the same procedures for the web server you are using. Follow these instructions to install the MU5 plug-in on Sun ONE Web Server:

  For co-located Web Server and Application Server:

  1. Before applying the 6.5SP1 MU6 patch, rename the 6.5SP1 MU5 web connector plug-in library, libgxnsapi6.so, to libgxnsapi6.so.mu5.
     If you have already applied the MU6 patch, the MU5 files would have been backed up. The backup data is saved in a directory named backup_patch number in your Sun ONE Application Server installation directory. For details see, "Uninstallation Instructions."
  2. Apply MU6 patch as described in Installation Instructions.
  3. After installing MU6, rename the new 6.5SP1MU6 web connector plug-in, libgxnsapi6.so, to libgxnsapi6.so.mu6_not_using.
  4. Rename libgxnsapi6.so.mu5 to libgxnsapi6.so.
  5. Restart the Web Server.

  For non co-located Web Server and Application Server:

  1. Do not upgrade the web connector plug-in from MU5. Apply the MU6 patch only on the machine running Application Server.
     If you have already upgraded the web connector plug-in to MU6, use the MU5 plug-in from the backed up directory. The backup data is saved in a directory named backup_patch number in the web server's installation directory.
  2. Restart the Web Server.

  Impact of the workaround for bug fix 4990938
  • Fix for Bug ID 4990938 will not be available in Application Server 6.5SP1 MU6.
  • Customers who apply this workaround will have to rollback this change from 6.5SP1 MU7 onwards.
  • This workaround is applicable only for 6.5SP1 MU6 release.
  • Fix for bug ID 4990938 will be provided in 6.5SP1 MU7.

• Enabling fix for 5048819.

  To enable this bugfix (KJS hangs waiting for reply from primary KXS (but there is no replyfrom KXS)) you need to manually set the following environmental variable, in System Properties:

  ENABLE_DSYNC_REMOVETOKEN_HANGPREVENTION=YES
  

  To disable the fix, perform the following changes:

  ENABLE_DSYNC_REMOVETOKEN_HANGPREVENTION=NO
  

• Enabling Log Rotation (Fix for 5057165)

  Use the following procedure to enable log rotation on Application Server 6.5 SP1.
  1. Start the Application Server's registry editor by running the command, kregedit.
  2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\iPlanet\Application Server\6.5\CCS0\LOGGING
  3. Uncheck Log to Console.
  4. Check Log to File.
  5. Set log rotation to Every Hour.
  6. Select All Messages.
  7. Select the number of entries that will be logged. The maximum is 100.
  8. Set the time interval (in minutes) for logging operation.
  9. Restart the Application Server.

  After restarting the Application Server, the System.out.println() and printStackTrace() messages go to KJS_1_CCS0 file, while the log messages go to ias.pid.timestamp file.

  After the first log rotation, the System.out.println, printStackTrace() and log messages all go to ias.pid.timestamp file.

• New EJBC option

  This Maintenance Update 5 release includes the -newjavac option, released in Maintenance Update 3. The -newjavac option will invoke a new ejbc shipped with JDK 1.3.1. ejbc command will use the old Java compiler by default to provide backward compatibility.

  The two Java compilers shipped with JDK 1.3.1 are:

  • The old Java compiler available in sun.tools.javac package.
  • The new Java compiler available in com.sun.tools.javac package.

  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.

• The following information is only applicable to customers who have reported bug #4877248. If you have reported this bug, you need to perform the following step to fix the bug:

  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
  

• Stubs and skeletons of EJB used in previous versions of Sun ONE Application Server, needs to be regenerated before deploying them on Sun ONE Application Server 6.5 or later.

  Use the Sun ONE Application Server 6.5 Deploy Tool to regenerate stubs and skeletons. Code changes are not required.

• Firewall Time-outs

  Problem:If the inactivity period of the application server exceeds the TCP/IP timeout interval of the firewall, then you need to restart the application server and web server.

  Workaround:

  1. Open the registry editor by running the command, kregedit
  2. Go to Application Server\6.5\CCSO\HTTPAPI.
  3. Enter the value for the key, KeepAliveTimeOut (in seconds), which could be equal to the default TCP/IP timeout value of the firewall, or equal to the number of seconds for the firewall to timeout.

  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.

  Customizing Local Transaction Timer Thread

  A new registry key, SOFTWARE\iPlanet\Application Server\6.5\CCSO\TXNMGR\TimerMarksLTxnForRollback, has been added in Maintenance Update 4 to customize the Local Transaction Timer thread in Sun ONE Application Server. The value can either be True or Fasle (case insensitive).

  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.

  IBM DB2 JDBC Driver Support

  The third party JDBC database driver support now includes IBM DB2 8.1.4 Type 2 Universal JDBC Driver. The IBM DB2 7.1 JDBC Client driver also continues to be supported.