18.2.13 EADsStoreException class

Organization of this subsection

(1) Description
(2) Inheritance relationship
(3) Format
(4) List of methods
(5) getErrorCode()

(1) Description

This exception class is returned when processing related to a data operation fails.

Use getErrorCode() to obtain an error code to determine the nature of the error.

(2) Inheritance relationship

java.lang.Object
java.lang.Throwable
  java.lang.Exception
    com.hitachi.software.xeads.func.store.EADsStoreException

To Page Top

(3) Format

public class EADsStoreException
extends Exception

To Page Top

(4) List of methods

The following table lists and describes the methods provided by the EADsStoreException class:

Method name	Description
`getErrorCode()`	Acquires an error code for an exception that has occurred.

To Page Top

(5) getErrorCode()

(a) Description

This method acquires an error code for an exception that has occurred.

(b) Format

public int getErrorCode()

(c) Return value

This method returns an error code as a return value. The following table lists the error codes and describes the nature and cause of the errors:

Error code	Error code literal	Exception class	Nature of error	Cause of error	Processing status of data updating API method^#
`1000`	`EAD_ERROR_UNEXPECTED`	`EADsStoreException`	An unexpected error occurred.	An unexpected error occurred within the program.	U
`1010`	`EAD_ERROR_INVALID_PARAMETER`	`UserOperationException`	A specified parameter is invalid.	An invalid parameter was specified in the API method argument.	N
`1050`	`EAD_ERROR_NOT_SERIALIZABLE`	`UserOperationException`	The serialization processing failed.	An object that cannot be serialized is specified in the API method argument.	N
`1060`	`EAD_ERROR_NOT_DESERIALIZABLE`	`UserOperationException`	The deserialization processing failed.	The object acquired from the EADS server could not be deserialized. Possible causes are as follows: The `Class-Path` attribute of the `jar` file manifest does not contain the path of the `jar` file containing the object needed for deserialization. The `jar` file containing the object needed for deserialization is not located under the `management-directory/app/lib` directory.	--
`1130`	`EAD_ERROR_CACHE_NOT_CREATED`	`UserOperationException`	No cache with the specified cache name has been created.	No cache with the specified cache name has been created.	--
`1140`	`EAD_ERROR_CACHE_SETTING`	`UserOperationException`	An API method that is not supported with the current cache settings was executed.	The executed API method attempted to acquire unavailable information from the cache.	--
`4000`	`EAD_ERROR_SERVER`	`InternalServerException`	An internal error that cannot be classified by the EADS server occurred.	An internal error occurred on the EADS server. Normally, this error code is not returned. It is returned when the details about the cause of the error cannot be obtained for one of the following reasons: A deprecated earlier version of the API method was used. The EADS server's internal error could not be classified due to an unexpected problem.	U
`4060`	`EAD_ERROR_SERVER_REPLACE_METHOD_NOT_MATCHED`	`InternalServerException`	The value could not be stored because the value stored during execution of `replace()`did not match `comparativeValue`.	The value specified in the condition in `replace()` did not match a value in the cache.	N
`4070`	`EAD_ERROR_SERVER_REPLACE_METHOD_KEY_NOT_EXIST`	`InternalServerException`	`replace()` was executed, but the value could not be stored because the specified key did not exist (the value associated with the key did not exist).	Values could not be compared because the value associated with the key specified in `replace()` did not exist.	N
`4080`	`EAD_ERROR_SERVER_CREATE_METHOD_KEY_EXIST`	`InternalServerException`	`create()` was executed, but the value could not be stored because the key had already been stored.	The value associated with the key specified in `create()` has already been stored.	N
`4090`	`EAD_ERROR_SERVER_UPDATE_METHOD_KEY_NOT_EXIST`	`InternalServerException`	`update()` was executed, but the value could not be stored because the stored key did not exist.	The value associated with the key specified in `update()` has not been stored.	N
`4200`	`EAD_ERROR_SERVER_CACHE`	`InternalServerException`	A cache operation failed.	A cache operation was disabled because a problem occurred on the EADS server that is executing the user function. Stop the operation and check the EADS server's status.	N
`4220`	`EAD_ERROR_SERVER_CACHE_CLUSTER_NOT_AVAILABLE`	`InternalServerException`	A cache operation failed because the cluster is not available.	A cache operation was disabled because the cluster was not available due to a problem on another EADS server or a network failure. Stop the operation and check the status of all EADS servers that make up the cluster.	N
`4300`	`EAD_ERROR_SERVER_CACHE_BEFORE_REPLICATION`	`InternalServerException`	An internal error occurred during a cache operation, but redundant copies of data had not been created.	During a cache operation, an internal error occurred on the EADS server that was executing the user function. No other normal EADS servers are affected because redundant copies of data had not been created. After the EADS server is isolated, you can restart the same operation on a normal EADS server.	N
`4310`	`EAD_ERROR_SERVER_CACHE_AFTER_REPLICATION`	`InternalServerException`	An internal error occurred on the EADS server during a cache operation and the data update operation failed.	During a cache operation, an internal error occurred on the EADS server that was executing the user function. Because redundant copies of data have already been created, after the erroneous EADS server is isolated, you can resume the operation on a normal server from the status in which data had been updated.	U
`4800`	`EAD_ERROR_SERVER_LIMIT_EXTERNAL_MEMORY`	`InternalServerException`	There is a shortage of memory for storing data.	The processing could not be performed because the memory for storing data (explicit heap) was insufficient.	N
`4810`	`EAD_ERROR_SERVER_LIMIT_CACHE_FILE`	`InternalServerException`	There is a shortage of capacity in the cache files for storing data.	The request could not be processed because the capacity of cache files for storing data was insufficient.	N
`4820`	`EAD_ERROR_SERVER_LIMIT_KV_COUNT`	`InternalServerException`	The number of keys that can be stored has reached the upper limit.	The processing could not be performed because the number of keys that can be stored had reached the upper limit.	N
`4830`	`EAD_ERROR_SERVER_LIMIT_KEY_VALUE_LENGTH`	`InternalServerException`	The size of the specified key, group name, or value is greater than the maximum size permitted in the cluster.	The processing could not be performed because the size of the specified key, group name, or value was greater than the maximum size permitted in the cluster.	N

#

Indicates whether data updating had occurred when an error code was issued during execution of an API method for updating data, such as put() or remove().

The meanings of the letters in this column are as follows:

U: Whether the data was updated is unknown. Check whether the processing was completed.

N: The data has not been updated.

--: This error code is not issued when an API method for updating data, such as put() or remove(), is executed.

(d) Notes

If a deprecated API method is used, the error code might not be classified in detail.

To Page Top