20.2 Error codes in the client library (C)

The error codes described below are returned by the functions in the C client library, in the location specified in the argument error_code.

The following table lists each error code along with its meaning and cause.

Table 20‒2: Error codes returned by functions in the C client library
Error code	Symbolic constant	Nature of error	Cause	Processing status of data updating API function^#	Value of error_code when 0300 is specified in the eads.client.compat parameter in the client properties
`0`	`EAD_OK`	Processing terminated normally.	Not applicable.	Y	`0`
`1000`	`EAD_ERROR_UNEXPECTED`	An unexpected error occurred.	An unexpected error occurred in the program.	U	`1000`
`1010`	`EAD_ERROR_ILLEGAL_ARGUMENT`	The specified parameter is invalid.	An invalid parameter was specified in an API function argument.	N	`1010`
`1040`	`EAD_ERROR_CACHE_NOT_STARTED`	The operation could not be executed because the cache has not been started.	An attempt was made to manipulate data after the cache had stopped (after execution of `ead_stop_cache()`).	N	`1040`
`1100`	`EAD_ERROR_CACHE_NOT_NEED_STOP`	An attempt was made to stop a cache that has already stopped.	Because the cache has already stopped, there is no need to execute `ead_stop_cache()`.	--	`1100`
`1110`	`EAD_ERROR_INVALID_NODE_ADDRESS`	The specified EADS server's address information does not match any EADS server address information managed by the EADS client.	The address information (IP address and port number) of the EADS server specified in the argument of the API function does not match any EADS server address information maintained by the EADS client.	--	`1110`
`1120`	`EAD_ERROR_EXCEED_MAX_CONNECTION_POOL_SIZE`	The number of connections to be pooled for the same connection target has already reached the maximum value and all of them are in use.	The number of concurrent threads issuing requests to the same EADS server has exceeded the maximum number of connections.	N	`1120`
`2000`	`EAD_ERROR_INIT`	An error occurred during initialization of the EADS client.	An unexpected error occurred while executing `ead_init_client()` or `ead_init_client_n()`.	--	`2000`
`2010`	`EAD_ERROR_INIT_PROPERTIES`	The client property file could not be read.	The following are possible causes of the error: The client property file does not exist. The client property file does not have read permissions. The specified storage destination path name is a directory, not a file.	--	`2010`
`2020`	`EAD_ERROR_INIT_INVALID_PROPERTY`	There is an invalid property in the client property file.	A property in the client property file is invalid.	--	`2020`
`2030`	`EAD_ERROR_INIT_LOGGER`	An attempt to initialize the logger failed.	The following are possible causes of the error: The specified directory or log file at the output destination does not have write permissions. A file with the same name already exists in the specified directory. The specified path name or file name is invalid. There is a directory that has the same name as the log file. There is not enough memory to start log output.	--	`2030`
`2040`	`EAD_ERROR_INIT_CLUSTERINFO`	An attempt to connect to the EADS server specified in the client property file failed.	The following are possible causes of the error: There is an error in the client property specification of the connection-target EADS server. Communication could not be established with the connection-target EADS server. Or, a failure occurred on the connection-target EADS server. The maximum number of simultaneous connections to the EADS server has been exceeded. The connection-target EADS server is not ready to accept requests.	--	`2040`
`3000`	`EAD_ERROR_NET`	A communication error has occurred with the EADS server.	The following are possible causes of the error: A network failure occurred during communication. A problem occurred on the EADS server with which the client was communicating. A problem occurred on the host with which the client was communicating.	U	`3000`
`3001`	`EAD_ERROR_NET_SEND_REQUEST`	A communication error occurred while a request was being sent to an EADS server.	The following are possible causes of the error: A network failure occurred during communication. A problem occurred on the EADS server with which the client was communicating. A problem occurred on the host with which the client was communicating.	U	`3000`
`3002`	`EAD_ERROR_NET_RECEIVE_RESPONSE`	A communication error occurred while a response was being received from an EADS server.	The following are possible causes of the error: A network failure occurred during communication. A problem occurred on the EADS server with which the client was communicating. A problem occurred on the host with which the client was communicating.	U	`3000`
`3010`	`EAD_ERROR_NET_TIMEOUT`	A timeout occurred during communication with the EADS server.	The following are possible causes of the error: A problem occurred on the connection-target EADS server. A problem occurred on the connection-target host. A network problem occurred. The timeout interval setting is incorrect.	U	`3010`
`3011`	`EAD_ERROR_NET_SEND_TIMEOUT`	A timeout occurred while a request was being sent to an EADS server.	The following are possible causes of the error: A problem occurred on the connection-target EADS server. A problem occurred on the connection-target host. A network problem occurred. The timeout interval setting is incorrect.	U	`3010`
`3012`	`EAD_ERROR_NET_RECEIVE_TIMEOUT`	A timeout occurred while a response was being received from an EADS server.	The following are possible causes of the error: A problem occurred on the connection-target EADS server. A problem occurred on the connection-target host. A network problem occurred. The timeout interval setting is incorrect.	U	`3010`
`3020`	`EAD_ERROR_NET_CONNECTION`	The connection to the EADS server failed.	The following are possible causes of the error: A problem occurred on the connection-target EADS server. The settings for the connection-target EADS server are incorrect. A network problem occurred. The timeout interval setting is incorrect.	N	`3020`
`3030`	`EAD_ERROR_NET_PROTOCOL`	A protocol failure occurred during communication with the EADS server.	The following are possible causes of the error: There might be a problem with the connection-target EADS server. The executed user function returned a value that is neither a byte array nor `NULL`. The cache for the connected cluster is in use by Java client libraries.	U	`3030`
`3040`	`EAD_ERROR_NET_CLUSTERINFO`	It was not possible to connect to all of the available EADS servers.	The following are possible causes of the error: Problems occurred on the connection-target EADS servers. The settings for the connection-target EADS servers are incorrect. A network problem occurred. The specified cache does not exist on the connection-target EADS server. The connection-target EADS server has been closed. The cluster information maintained by the EADS client does not match the cluster information maintained by the restarted connection-target EADS server. The maximum number of simultaneous connections to the EADS server has been exceeded.	--	`3040`
`4000`	`EAD_ERROR_SERVER`	An unexpected internal error occurred on the EADS server.	An unexpected internal error occurred on the connection-target EADS server.	U	`4000`
`4010`	`EAD_ERROR_SERVER_UNSUPPORTED_REQUEST`	The request sent by the EADS client could not be processed by the connection-target EADS server.	Possible causes are as follows: The connection-target EADS server cannot process the request for a reason such as corrupted data. The API function used is not supported by the connection-target EADS server.	N	`4010`
`4030`	`EAD_ERROR_SERVER_UNAVAILABLE`	The connection-target EADS server process is temporarily unavailable.	The maximum number of simultaneous connections to the EADS server has been exceeded.	N	`4030`
`4040`	`EAD_ERROR_SERVER_INCOMPATIBLE_CLUSTERINFO`	The cluster information maintained by the connection-target EADS server is not compatible with the cluster information maintained by the EADS client.	The cluster information maintained by the restarted connection-target EADS server does not match the cluster information maintained by the EADS client.	N	`4040`
`4060`	`EAD_ERROR_SERVER_REPLACE_METHOD_NOT_MATCHED`	The value could not be stored because the value existing during execution of `ead_replace()` did not match the value specified in the condition.	The value specified in the condition in `ead_replace()` did not match the value in the cache.	N	`4060`
`4070`	`EAD_ERROR_SERVER_REPLACE_METHOD_KEY_NOT_EXIST`	During execution of `ead_replace()`, processing could not continue because the specified key could not be found (no value for the key could be found).	The values could not be compared because no value could be found for the key specified in `ead_replace()`.	N	`4070`
`4080`	`EAD_ERROR_SERVER_CREATE_METHOD_KEY_EXIST`	During execution of `ead_create()`, the value could not be stored because the specified key already exists.	A value was already stored for the key specified in `ead_create()`.	N	`4080`
`4090`	`EAD_ERROR_SERVER_UPDATE_METHOD_KEY_NOT_EXIST`	During execution of `ead_update()`, the value could not be stored because the specified key was not found.	No value was stored for the key specified in `ead_update()`.	N	`4090`
`4100`	`EAD_ERROR_SERVER_NOT_RUNNING`	No EADS server is available for processing requests.	Possible causes are as follows: The EADS server that processes requests from the EADS client and the EADS servers to which data is to be copied are all isolated or stopped. The cluster is not available.	N	`4100`
`4110`	`EAD_ERROR_SERVER_STATUS`	The EADS server is in a status in which requests cannot be processed.	The request could not be processed due to the status of the connection-target EADS server.	N	`4000`
`4200`	`EAD_ERROR_SERVER_CACHE`	A cache operation failed.	An operation could not be performed on a cache because a problem occurred on the connection-target EADS server. Stop the operation and check the EADS server's status.	N	`4000`
`4210`	`EAD_ERROR_SERVER_CACHE_NOT_FOUND`	A cache operation failed because the specified cache did not exist.	An operation could not be performed on a cache because the specified cache did not exist. Stop operation on the specified cache and check the EADS server's status.	N	`4000`
`4230`	`EAD_ERROR_SERVER_CACHE_CLUSTER_UPDATE`	A cache operation failed because the cluster configuration was changed during request processing.	An operation could not be performed on a cache because the cluster configuration was changed during request processing. Perform the cache operation again after the cluster configuration change processing has been completed.	N	`4000`
`4300`	`EAD_ERROR_SERVER_CACHE_BEFORE_REPLICATION`	An internal error occurred during a cache operation, but redundant copies of data had not been created.	An internal error occurred during a cache operation on the connection-target EADS server. No other normal EADS servers are affected because redundant copies of data had not been created. You can restart the same operation after the EADS server is isolated and then the connection target is changed to a normal EADS server.	N	`4000`
`4310`	`EAD_ERROR_SERVER_CACHE_AFTER_REPLICATION`	An internal error occurred on the EADS server during cache operation and the data update operation failed.	An internal error occurred on the connection-target EADS server during cache operation. Because redundant copies of data had already been created, once the erroneous connection-target EADS server is isolated and the connection target is changed to a normal server, you can restart the operation from the status in which data had been updated.	U	`4000`
`4700`	`EAD_ERROR_SERVER_FUNCTION_EXECUTE`	An error occurred in the user function on the EADS server.	An error occurred in the user function on the connection-target EADS server. Check the user function's processing.	--	`4000`
`4710`	`EAD_ERROR_SERVER_FUNCTION_RETURN_SERIALIZE`	Serialization processing on the return value of the user function failed on the EADS server.	An object that is not serializable is specified for the return value of the user function executed on the connection-target EADS server.	--	`4000`
`4730`	`EAD_ERROR_SERVER_FUNCTION_NOT_FOUND`	No user function with the specified user function name exists on the EADS server.	No user function with the specified user function name exists on the connection-target EADS server.	--	`4000`
`4800`	`EAD_ERROR_SERVER_LIMIT_EXTERNAL_MEMORY`	There is a shortage of memory for storing data.	The request could not be processed because the memory for storing data (explicit heap) was insufficient on the connection-target EADS server.	N	`4000`
`4810`	`EAD_ERROR_SERVER_LIMIT_CACHE_FILE`	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 on the connection-target EADS server.	N	`4000`
`4820`	`EAD_ERROR_SERVER_LIMIT_KV_COUNT`	The number of keys that can be stored on the EADS server has reached the upper limit.	The request could not be processed because the number of keys that can be specified on the connection-target EADS server had reached the upper limit.	N	`4000`
`4830`	`EAD_ERROR_SERVER_LIMIT_KEY_VALUE_LENGTH`	The size of the specified key, group name, or value is greater than the maximum size permitted in the cluster.	The request could not be processed because the size of the specified key, group name, or value was greater than the maximum size permitted in the cluster.	N	`4000`
`4999`	`EAD_ERROR_SERVER_UNKNOWN`	A nonanalyzable internal error occurred on the EADS server.	An internal error occurred on the connection-target EADS server, but the error could not be analyzed because the version of the connection-target EADS server was later than the version of the EADS client libraries.	U	`4000`
`5000`	`EAD_ERROR_CLIENT`	An internal error occurred on an EADS client.	An unexpected error occurred in client libraries.	U	`5000`
`5010`	`EAD_ERROR_CLIENT_OUT_OF_MEMORY`	Memory allocation in the EADS client failed.	Memory allocation failed in client libraries.	U	`5010`
`5020`	`EAD_ERROR_CLIENT_BATCH_CANCEL`	Batch operation was cancelled.	Unperformed operations were cancelled because batch operation could not be continued.	N	`5020`
`6000`	`EAD_ERROR_BATCH_FAILED_ALL`	All of the batch operations failed.	An attempt was made to perform a batch operation on data by using an API function, but all operations failed.	--	`6000`
`6010`	`EAD_ERROR_BATCH_FAILED_PART`	Part of the batch operations failed.	An attempt was made to perform a batch operation on data by using an API function, but some of the operations failed.	--	`6010`

#

Indicates whether data updating had occurred when the error code was issued during execution of an API function for updating data, such as ead_put() or ead_remove().

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

Y: The data had been updated.

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

N: The data had not been updated.

--: This error code is not issued when an API function for updating data, such as ead_put() or ead_remove(), is executed.

To Page Top