This chapter describes late-breaking news and known issues for the Sun Java Enterprise System Application Server Plug-In.
The following are known issues when installing the Sun Java Enterprise System Application Server plug-in.
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.
The following are known-issues when running the Sun Java Enterprise System Application Server plug-in.
The deleteDomain task does not completely delete the managed servers and node agents of the specified domain because the clusters and server instances are still running.
Stop all the clusters, Domain Administration Server, and server instances associated with a domain before deleting the domain.
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.
You cannot run more than one Domain Administration Servers on a host due to a port conflict.
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
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.