Chapter 2 Release Notes for the Sun Java Enterprise System Application Server Plug-In

This chapter describes late-breaking news and known issues with the Sun Java Enterprise System Application Server Plug-In.

The chapter contains the following information:

• Installation Issues

• Runtime Issues

Installation Issues

The following are known issues when installing the Sun Java Enterprise System Application Server plug-in.

Log Files May Not Be in Specified Location Upon Installation Failure (6256822)

If an installation fails, you will see an error message reading:

Please check the installation log file under /tmp.

The actual location of the log files is determined by the [tempStateFile] variable, which is /tmp by default. If [tempStateFile] has been changed, the log files will be located in the specified directory.

Runtime Issues

The following are known-issues when running the Sun Java Enterprise System Application Server plug-in.

Deleting a Domain Does Not Completely Delete the Managed Servers or Clusters Associated with the Domain (6227939)

The deleteDomain task does not completely delete the domain. When this occurs, the following error message is displayed:

Error: Domain domain_name delete failed.

The following workaround should only be performed if you have one domain. If there are multiple domains, all domains are deleted.

Workaround: To completely delete the domain, you uninstall and reinstall the Install component.

1. To uninstall - see How to Uninstall the Sun Java Enterprise System Application Server Software.

2. To install - see How to Install the Sun Java Enterprise System Application Server Software.

The Load Balancer Configuration File Is Not Updated Correctly When Multiple Clusters are Created in a Domain (6233520)

If you have more than one cluster created in a domain and are using the load balancer, the load balancer configuration file, loadbalancer.xml, is not properly updated. On starting the domain, you will see the following error message:

Error occured while initializing Loadbalancer config Parser. Please check the config file:

The workaround is to either not run multiple clusters on a domain, or write out loadbalancer.xml to a temporary location and copy in the relevant sections to the web server's loadbalancer.xml.

Two Domain Administration Servers Cannot Run on the Same Host (6228738)

You cannot run more than one Domain Administration Servers on a host due to a port conflict.

Load Balancer Configuration Entries Are Not Deleted When a Cluster is Deleted (6233521)

If you are deleting a cluster on a domain that uses the load balancer, the cluster's entries in the load balancer configuration file, loadbalancer.xml, are not deleted.

The load balancer will automatically remove unavailable nodes from the

Listing JDBC or JMS Resources for a Cluster or Server Instance Displays All the Resources in the Domain (6235760)

The output of the listJMSResources or listJDBCResources tasks for a specified target (a cluster or server instance name) displays the resources for the domain on which the cluster or instance is running.