Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java System Application Server 8.1 Enterprise Edition 2005Q1 Troubleshooting Guide 

Chapter 3
HADB Problems

This section covers problems you may encounter when using the Application Server 8.1 EE product with the High Availability Database (HADB) module, HADB Management Client, or the load balancer plugin. These components can be installed separately or with the rest of the Application Server.

Topics in this chapter include:

HADB Database Creation Fails

The database creation may fail due to the following reasons::

failed to start database : HADB Database creation failed

To determine the cause of the problem, use the Log Viewer and/or inspect the install_dir/hadb/4/log directory. Some possible errors are:

Problems Related to Shared Memory


This problem may occur due to any of the following reasons:

Cause 1

Shared memory is not configured or the configuration is not working.

Solution 1

Follow the instructions described in the Sun Java™ System Application Server 8.1 Installation Guide. Remember to reboot the system after configuring shared memory settings.

Cause 2

The physical memory is not enough to satisfy the node requirements. You may see the following error message:

HADB-S-05512: Attaching shared memory segment with key <xx> failed, OS status=12 OS message: Not enough space.

Solution 2

Verify that shared memory is configured and the configuration is working, as mentioned above.

For production systems, reduce the number of nodes on the host or increase the physical memory on the host.

For test/development systems, reduce the shared memory usage by setting the LogBufferSize and DataBufferPoolSize to a value lower than the default values of 48 and 200MB, respectively. The allowed minimum for these variables are 32 and 64MB, respectively.

Cause 3

The size of a shared memory segment has exceeded the allowed maximum size.

HADB-S-05510: Getting shared memory segment with key <xx> failed, OS status=22. OS message: Invalid argument.

Solution 3

Verify that shared memory is configured and the configuration is working, as mentioned above.

If shared memory is configured correctly, check whether you have specified any shared memory segment size (LogBufferSize or DataBufferPoolSize) larger than the system-configured maximum value set in the operating system configuration files (shmsys:shminfo_shmmax in /etc/system on Solaris).

Cause 4

There is already a shared memory segment created with the specified identifier:

HADB-S-05515: Shared memory segment with key <segment_key> exists already.

Solution 4

List the shared memory segments and check. The ipcs can be used to list the segments in Unix. Windows uses memory mapped files for shared memory. HADB uses the getTempPath system call to get the system-defined temporary directory where these files, named as f_segmentid, are stored.

Check whether there is already another running database or any other program using the shared memory segment with this identifier. If so, create a database with another port base. If there are no running databases or other programs using this segment, free the segment with hadbm delete unused_database.

Check whether the segments are freed. If they are still there, remove them (use ipcrm in Unix and delete $TMP/f_* in Windows). The file name consists of the f_ prefix followed by the segment_key translated into hexadecimal. For example, if the error message indicates that segment key 15201 still exists, the temp file would be named f_3B61.

Too Few Semaphores


HADB-E-05521: Operation on semaphore with key "46025" failed, OS status=28 : No space left on device

This can be caused when the number of semaphores is too low. Since the semaphores are provided as a global resource by the operating system, the configuration depends on all processes running on the host, not only the HADB. This can occur either while starting the HADB, or during runtime.


Configure the semaphore settings by editing the /etc/system file. Instructions and guidelines are contained in the Configuring Shared Memory and Semaphores section of the Preparing for HADB Setup chapter of the Sun Java™ System Application Server Installation Guide.

Database Nodes Cannot Be Reached and the Database Does Not Function


The IP addresses of the involved hosts should be fixed. HADB uses the fixed IP addresses present at database creation, so you cannot use dynamic IP addresses (DHCP) for production systems.

The Management Agents Could Not Establish a Domain


The HADB management system is dependent on UDP Multicast messages on multicast address If these messages cannot get through, the createdomain command fails with the following message:

The management agents could not establish a domain, please check that the hosts can communicate with UDP multicast.

Possible causes include:

Solution 1

If the hosts have several network interfaces on different subnets, the management agent must be configured to use one of the subnets. Set the ma.server.mainternal.interfaces attribute.

Solution 2

Configure the needed network infrastructure to support multicast messages.

hadbm create or hadbm addnodes Command Hangs


Some hosts in the host list given to hadbm create or addnodes have multiple network interfaces, while others have only one, and the hadbm create/addnodes command hangs.


For the hosts having multiple network interfaces, specify the dotted IP address of the network interface (for example., to be used by hadb when issuing hadbm create/addnodes. If the host name is used instead of IP address, the first interface registered on the host will be used, and there is no guarantee that the nodes will be able to communicate.

ma (Management Agent Process) Crashes


The ma (Management Agent process) crashes for various reasons.


Display diagnostic information by using hadbm listdomain.Typically, the remedy is to restart the failed agent. If that does not help, restart all agents in turn.

Server Responds Slowly After Idle Period


The server takes a long time to service a request after a long period of idleness, and the sever log shows “lost connection” messages of the form: Store: Lost connection to the server.

In such cases, the server needs to recreate the JDBC pool for HADB.


Change the timeout value. The default HADB connection timeout value is 1800 seconds. If the application server does not send any request over a JDBC connection during this period, HADB closes the connection, and the application server needs to re-establish it. To change the timeout value, use the hadbm set SessionTimeout= command.


Make sure the HADB connection timeout is greater than the JDBC connection pool timeout. If the JDBC connection timeout is more than the HADB connection time out, the connection will be closed from the HADB side, but will remain in the appserver connection pool. When the application then tries to use the connection, the application server will have to recreate the connection, which incurs significant overhead.

Requests Are Not Succeeding

The following problems are addressed in this section:

Is the Load Balancer Timeout Correct?


When configuring the response-timeout-in-seconds property in the loadbalancer.xml file, you must take into account the maximum timeouts for all the applications that are running. If the response timeout it is set to a very low value, numerous in-flight requests will fail because the load balancer will not wait long enough for the Application Server to respond to the request.

Conversely, setting the response timeout to an inordinately large value will result in requests being queued to an instance that has stopped responding, resulting in numerous failed requests.


Set the response-timeout-in-seconds value to the maximum response time of all the applications.

Are the System Clocks Synchronized?


When a session is stored in HADB, it includes some time information, including the last time the session was accessed and the last time it was modified. If the clocks are not synchronized, then when an instance fails and another instance takes over (on another machine), that instance may think the session was expired when it was not, or worse yet, that the session was last accessed in the future!


In a non-colocated configuration, it is important to synchronize the clocks on that machines that are hosting HADB nodes. For more information, see the Installation Guide chapter, “Preparing for HADB Setup.”


Verify that clocks are synchronized for all systems in the cluster.

Is the Application Server Communicating With HADB?


HADB may be created and running, but if the persistence store has not yet been created, the Application Server will not be able to communicate with the HADB. This situation is accompanied by the following message:

WARNING (7715): ConnectionUtilgetConnectionsFromPool failed using connection URL: connection URL


Create the session store in the HADB with a command like the following:

asadmin create-session-store --storeurl connection URL --storeuser haadmin --storepassword hapasswd --dbsystempassword super123

Session Persistence Problems

The following problems are addressed in this section:

The create-session-store Command Failed


The asadmin create-session-store command cannot run across firewalls. Therefore, for the create-session-store command to work, the application server instance and the HADB must be on the same side of a firewall.

The create-session-store command communicates with the HADB and not with the application server instance.


Locate the HADB and the application server instance on the same side of a firewall.

Configuring Instance-Level Session Persistence Did Not Work

The application-level session persistence configuration always takes precedence over instance-level session persistence configuration. Even if you change the instance-level session persistence configuration after an application has been deployed, the settings for the application still override the settings for the application server instance.

Session Data Seems To Be Corrupted


Session data may be corrupted if the system log reports errors under the following circumstances:

If the data has been corrupted, there are three possible solutions for bringing the session store back to a consistent state, as described below.

Solution 1

Use the asadmin clear-session-store command to clear the session store.

Solution 2

If clearing the session store does not work, reinitialize the data space on all the nodes and clear the data in the HADB using the hadbm clear command.

Solution 3

If clearing the HADB does not work, delete and then recreate the database.

For solutions 2 and 3, above, after clearing the HADB, recreate the session store to restablish the database schema.

HADB Performance Problems

Performance is affected when the transactions to HADB get delayed or aborted. This situation is generally caused by a shortage of system resources. Any wait beyond five seconds causes the transactions to abort. Any node failures also cause the active transaction on that node at crash time to abort. Any double failures (failure of both mirrors) will make the HADB unavailable. The causes of the failures can generally be found in the HADB history files.

To isolate the problem, consider the following:

Is There a Shortage of CPU or Memory Resources, or Too Much Swapping?


Node restarts or double failures due to “Process blocked for x sec, max block time is 2.500000 sec.” In this case, x is the length of time the process was blocked, and it was greater than 2.5 seconds.

The HADB Node Supervisor Process (NSUP/clu_nsup_srv) tracks the time elapsed since the last time it did some monitoring work. If that time duration exceeds a specified maximum (2500ms by default), NSUP concludes that it was blocked too long and restarts the node.

NSUP being blocked for more than 2.5 seconds cause the node to restart. If mirror nodes are placed on the same host, the likelihood of double failure is high. Simultaneous occurrence of the blocking on the mirror hosts may also lead to double failures.

The situation is especially likely to arise when there are other processes—for example, in a colocated configuration— in the system that compete for CPU, or memory which produces extensive swapping and multiple page faults as processes are rescheduled.

NSUP being blocked can also be caused by negative system clock adjustments.


Ensure that HADB nodes get enough system resources. Ensure also that the time synchronization daemon does not make large (not higher than 2 seconds) jumps.

Is There Disk Contention?


A disk contention can have a negative impact on user data read/writes to the disk devices, as well as on HADB writing to history files. Severe disk contention may delay or abort user transactions. Delay in history file writing may cause node restarts and, in the worst case, lead to double failures.

The disk contention can be identified by monitoring the disk I/O from the OS, for the disks used for data, log devices and history files. History file write delays are written to the HADB history files. This can be identified by “NSUP BEWARE timestamp Last flush took too long (x msecs).”

This warning shows that disk I/O took too long. If the delay exceeds ten seconds, the node supervisor restarts the trans process with the error message:

Child process trans0 10938 does not respond.
Child died - restarting nsup.
Psup::stop: stopping all processes.

This message indicates that a trans (clu_trans_srv) process has been too busy doing other things (for example, waiting to write to the history file) to reply to the node supervisor’s request checking the heartbeat of the trans process. This causes the nsup to believe that the trans has died and then restarts it.

When the operating system is overloaded with too many processes (many HADB nodes co-located with other processes), the scheduling of I/O operations may be delayed. When the HADB related I/O work is delayed, HADB nodes write the following in the history files, “HADB warning: Schedule of async <read,write> operation took ...

This problem is observed especially in RH AS 2.1 when multiple HADB nodes are placed on the same host and all the nodes use the same disk to place their devices.


Use one disk per node to place the devices used by that node. If the node has more than one data devices and the disk contention is observed, move one data device to another disk. The same applies to the history file as well.

Make sure that all data and log devices and all history files reside on local disks (not NFS-mounted or other remotely mounted disks).

If the monitoring tools still show contention on the HADB disks, the data buffer pool size can be increased.

Is There a Shortage of HADB Data Device Space?


One possible reason for transaction failure is running out of data device space. If this situation occurs, HADB will write warnings to the history file, and abort the transaction which tried to insert and/or update data.

Typical messages are:

HIGH LOAD: about to run out of device space, ...
HIGH LOAD: about to run out of device space on mirror node, ...

The general rule of thumb is that the data devices must have room for at least four times the volume of the user data. Please refer to the Tuning Guide for additional explanation.

Solution 1

Increase the size of the data devices using the following command:

hadbm set DeviceSize=size

This solution requires that there is space available on the physical disks which are used for the HADB data devices on all nodes.

HADBM automatically restarts each node of the database.

Solution 2

Stop and delete the HADB, and create a new instance with more nodes and/or larger data devices and/or several data devices per node. Unfortunately, using this solution will erase all persistent data and the schemas created by the Application Server. See the Administrator's Guide for more information about this procedure.

Is There a Shortage of Other HADB Resources?

When an HADB node is started, it will allocate:

If an HADB node runs out of resources it will delay and/or abort transactions. Resource usage information is shipped between mirror nodes, so that a node can delay or abort an operation which is likely to fail on its mirror node.

Transactions that are delayed repeatedly may time out and return an error message to the client. If they do not time out, the situation will be visible to the client only as decreased performance during the periods in which the system is short on resources.

These problems frequently occur in “High Load” situations. For details, see High Load Problems.

High Load Problems

High load scenarios are recognizable by the following symptoms:

If a high load problem is suspected, consider the following:

Is the Tuple Log Out Of Space?

All user operations (delete, insert, update) are logged in the tuple log and executed. There tuple log may fill up because:

If the tuple log is out of space, the history files contain messages showing HIGH LOAD on the tuple log.

Solution 1

Check CPU usage, as described in Improving CPU Utilization.

Solution 2

If CPU utilization is not a problem, check the disk I/O. If the disk shows contention, avoid page faults when log records are being processed by increasing the data buffer size with hadbm set DataBufferPoolSize=... If there is disk contention, follow the solutions suggested in Is There Disk Contention?

Solution 3

Look for evidence of network contention, and resolve bottlenecks.

Solution 4

Increase the tuple log buffer using hadbm set LogBufferSize=...

Is the node-internal Log Full?

Too many node-internal operations are scheduled but not processed due to CPU or disk I/O problems.

If the node-internal log is out of space, the history files contain messages showing HIGH LOAD on the node internal log.

Solution 1

Check CPU usage, as described in Improving CPU Utilization.

Solution 2

If CPU utilization is not a problem, check the disk I/O. If the disk shows contention, avoid page faults when log records are being processed by increasing the data buffer size with hadbm set DataBufferPoolSize=... If there is disk contention, follow the solutions suggested in Is There Disk Contention?

Are There Enough Locks?

Some extra symptoms that identify this condition are:

Solution 1: Split Long Transactions

A transaction running on a node is not allowed to use more than 25% of the number of locks allocated on that node. Read transactions running at the “repeatable read” isolation level and the update/insert/delete transactions hold the locks until the transaction terminates. Therefore, it is recommended to split long transactions into small batch of separate transactions.

Solution 2: Increase the number of locks

Use hadbm set NumberOfLocks= to increase the number of locks.

Can You Fix the Problem by Doing Some Performance Tuning?

In most situations, reducing load or increasing the availability of resources will improve host performance. Some of the more common steps to take are:

In addition, the following resources can be adjusted to improve “HIGH LOAD” problems, as described in the Performance and Tuning Guide:

Table 3-1  HADB Performance Tuning Properties



Size of Database Buffer

hadbm attribute DataBufferPoolSize

Size of Tuple Log Buffer

hadbm attribute LogBufferSize

Size of Node Internal Log Buffer

hadbm attribute InternalLogBufferSize

Number of Database Locks

hadbm attribute NumberOfLocks

Connection Problem Caused by Lack of Semaphore Resources


This problem is accompanied by a message in the history file:

HADB-E-05521: Operation on semaphore with key "46025" failed, OS status=28 : No space left on devicewhere:

You must configure more semaphore unso structures on the host computer. See the “Preparing for HADB Setup” chapter in the Sun Java™ System Application Server 8.1 Installation Guide for information on how to configure semmnu on your operating system.


Stop the affected HADB node, reconfigure and reboot the affected host, restart the HADB node. HADB will be available during the process.

Improving CPU Utilization


Available CPU cycles and I/O capacity can impose severe restrictions on performance. Resolving and preventing such issues is necessary to optimize system performance (in addition to configuring the HADB optimally.)


If there are additional CPUs on the host that are not exploited, add new nodes to the same host. Otherwise add new machines and add new nodes on them.

If the machine has enough memory, increase the DataBufferPoolSize, and increase other internal buffers that may be putting warnings into the log files. Otherwise, add new machines and add new nodes on them.

For more information on this subject, consult the Performance and Tuning Guide.

HADB Administration Problems

The hadbm command and its many subcommands and options are provided for administering the high-availability database (HADB). The hadbm command is located in the install_dir/SUNWhadb/4/bin directory.

Refer to the chapter on Configuring the High Availability Database in the Sun Java™ System Application Server Administrator’s Guide for a full explanation of this command. Specifics on the various hadbm subcommands are explained in the hadbm man pages.

The following problems are addressed in this section:

hadbm Command Fails: The agents could not be reached


The command fails with the error:

The agents <url> could not be reached.

The hosts in the URL could be unreachable either because the hosts are down, because the communication pathway has not been established, because the port number in the URL is wrong, or because the management agents are down.


Verify that the URL is correct. If the URL is correct, verify that the hosts are up and running and are ready to accept communications; for example:

ping hostname1
ping hostname2

hadbm Command Fails: command not found


The hadbm command can be run from the current directory, or you can set the search PATH to access the hadb commands from anywhere, which is much more convenient. The error, “hadbm: Command not found,” indicates that neither of these conditions has been met.

Solution 1

cd to the directory that contains the hadbm command and run it from there:

cd install_dir/SUNWhadb/4/bin/

Solution 2

Use the full path to invoke the hadbm command:


Solution 3

You can use the hadbm command from anywhere by setting the PATH variable. Instructions for setting the PATH variable are contained in the “Preparing for HADB Setup” chapter of the Sun Java™ System Application Server 8.1 Installation Guide.

To verify that the PATH settings are correct, run the following commands:

which asadmin
which hadbm

These commands should echo the paths to the utilities.

hadbm Command Fails: JAVA_HOME not defined


The message “hadbm: <path>: Invalid Java home location” indicates that the JAVA_HOME environment variable has not been set properly.


If multiple Java versions are installed on the system, ensure that the JAVA_HOME environment variable points to the correct Java version (1.4.1_03 or above for Enterprise Edition).

Instructions for setting the PATH variable are contained in the “Preparing for HADB Setup” chapter of the Sun Java™ System Application Server 8.1 Installation Guide.

hadbm createdomain fails, but two split domains are created


If running the HADB management agent on a host with multiple network interfaces, the createdomain command may fail if not all network interfaces are on the same subnet:

hadbm:Error 22020: The management agents could not establish a domain, please check that the hosts can communicate with UDP multicast.

By default, the management agents use the “first” interface for UDP multicasts (“first” as returned by


The best solution is to tell the management agent which subnet to use by setting ma.server.mainternal.interfaces in the configuration file; for example:


Alternatively, one may configure the router between the subnets to route multicast packets. By default, the management agent uses multicast address

create Fails: “path does not exist on a host”


After issuing the hadbm create command, an error similar to the following appears on the console:

./hadbm create ...
hadbm: Error 22022: Path path does not exist on host host

This error message can also appear when new nodes are added without the specified paths do not exist on the machines.


Log in to the host and create paths for the HADB devices and HADB history files. Run hadbm create and specify the --devicepath and --historypath options to the paths created. Also make sure that the user running the management agent on the host has read and write access to these directories.


HADB executables cannot be installed on different paths on different hosts.

Database Does Not Start

The create or start command fails with the console error message:

hadbm: Error 22095: Database could not be started...

Consider the following possibilities:

Was there a shared memory get segment failure?


Start may fail if the resources (shared memory, disk space) allocated for that node are taken by some other processes, after the node is stopped.


Refer to Problems Related to Shared Memory for suggestions on resolving this issue.

Do the History Files Contain Errors?


If the problem still persists, inspect the HADB history files. Some of the more likely error messages to look for are:


After verifying that none of the above errors have occurred, try the following remedies, in order:

For more information, refer to the Error Message Reference.

clear Command Failed

The clear command reinitializes the database device files residing on disks. This may fail due to problems with disk or disk access. Check whether any error message from hadbm indicates this. If not, look into the ma.log files and check whether devinit has generated any error messages.

create-session-store Failed

The asadmin create-session-store command could fail for one of these reasons:

Invalid user name or password

This error occurs when the --dbsystempassword supplied to the create-session-store command is not the same password as the one given at the time of database creation.

Solution 1

Try the command again with the correct password.

Solution 2

If you cannot remember the dbsystem password, you need to clear the database using hadbm clear and provide a new dbsystem system password.

SQLException: No suitable driver

The create-session-store produces the error: SessionStoreException: java.sql.SQLException: No suitable driver.

Solution 1

This error can occur when asadmin is not able to find hadbjdbc4.jar from the AS_HADB path defined in asenv.conf in the Application Server config directory.

The solution is to change AS_HADB to point to the location of the HADB installation.

Here is a sample AS_HADB entry from an asenv.conf file:


Solution 2

This error can also occur if you provide the incorrect value for --storeUrl. To solve this problem, obtain the correct URL using hadbm get jdbcURL.

hadbm Command Hangs

If the management agent with which the hadbm communicates dies before the operation finishes, then the hadbm process may hang. Check whether the all the agents are running.

Cannot Restart the HADB


HADB restart does not work after a double node failure. Additional recovery actions are needed before HADB can be restarted.

Symptoms of a double node failure include:

This problem occurs when mirror HADB host machines have failed or been rebooted, typically after a power outage, or when a machine is rebooted without first stopping the HADB (in a single-machine installation), or when a pair of mirror machines from both Data Redundancy Units (DRUs) are rebooted.

HADB cannot heal itself automatically in such “double failure” situations because the part of the data that resided on the pair nodes is lost. In such cases, the hadbm start command does not succeed, and the hadbm status command shows that HADB is in a non-operational state.

For more information on the DRUs and HADB confutation, see “Administering the High Availability Database” in the Administration Guide, and the Deployment Guide.


If the HADB exhibits strange behavior (for example consistent timeout problems), and you want to check whether a restart cures the problem, use the hadbm restart command.

When the HADB is restarted in this manner, HADB services remain available. Conversely, if HADB is started and stopped in separate operations using hadbm stop and hadbm start, HADB services are unavailable while HADB is stopped.


Verify that the node states show Starting/Recovering, then reset the database. Follow the instructions under “Recovering from Session Data Corruption” in the “Administering the High Availability Database” chapter of the Administration Guide.

Shared Memory Segment Key Already Exists (Windows only)


The hadbm process returns the following error:

HADB-S-05515: Shared memory segment with key "NNNNN" exists already

This can happen during HADB instance creation following a controlled stop without deleting a previously created instance that is using the same portbase. The problem may also be the result of a failed HADB instance deletion for any reason.


Delete all stopped hadb instances to make sure all HADB resources are free before attempting to reuse them.

If the problem persists, manually remove the HADB Shared Memory segments by deleting the HADB files in $TMP/f_*.

Failure in configure-ha-cluster


Creation of an HADB domain comprising some host names appears to succeed, and the listdomain command confirms it:

$hadbm listdomain -w admin
Hostname Enabled? Running? Release Interfaces
host1 Yes Yes V4-4-1-3
host2 Yes Yes V4-4-1-3

The database is then created with the hadbm create command, and the appropriate host names including the full domain names are used as parameters for the --hosts option:

$ hadbm create,

The following error is then returned:

hadbm:Error 22176: The host is not registered in the HADB management domain. Use hadbm createdomain to set up the management domain or hadbm extenddomain to include new hosts in an existing domain.

Solution 1

Use the names that listdomain displays; for example:

hadbm create --hosts=host1,host2...

Solution 2

Use decimal IP addresses (DDN); for example:

hadbm create --hosts=,

Unable to Run configure-ha-cluster


Two different installations of HADB are configured: one on server hosts, and another on the hadbm client host(s), each running different versions of HADB. The management agents are started with one HADB versions, and then hadbm create is run with the other version. The following error is returned:

HADBMGMT007:hadbm create command failed. Return value: 1 STDOUT:
STDERR: hadbm:Error 22170: The software package V4.4.x could not be
found at path <pacakgepath>/4.4-x on host <hostname>.
CLI137 Command configure-ha-cluster failed.


Use the same HADB version for the management agents and all hadbm clients.

hadbm set Command Fails


hadbm set brings the database instance to a state that is hard to recover from.

Changing a database configuration variable with the hadbm set command fails. For example, setting DataBufferPoolSize to a larger size fails due to lack of shared memory on node-0. The hadbm set command leaves the database with node-0 in a stopped state and node-1 in a running state. Resetting the pool size back to the original value with the help of hadbm set fails with the message:

22073: The operation requires restart of node 1. Its mirror node is currently not available. Use hadbm status --nodes to see the status of the nodes.

The hadbm startnode 0 command is also of no use in this situation.


Stop the database, then restore the old values using hadbm set, then restart the database.

Failure in configure-ha-cluster: Creating an HADB Instance Fails


Creation of an HADB cluster fails with the message:

cresqldict: HADB-E-00208: The transaction was aborted.

This indicates that the booting transaction populating the SQL dictionary tables was aborted.


Run the configure-ha-cluster again. If the hadbm create command fails with the above message, rerun the command.

Previous      Contents      Index      Next     

Part No: 819-0086.   Copyright 2004-2005 Sun Microsystems, Inc. All rights reserved.