22.2 KDEA00001 to KDEA01999
This section describes messages KDEA00001 to KDEA01999 and explains the corrective actions to take in response to each message.
-
KDEA00001-I
The server will now start. (server name = aa....aa)
aa....aa: EADS server name (management directory name)
- Description
-
The EADS server is starting.
-
KDEA00002-I
The server will now shut down. (server name = aa....aa)
aa....aa: EADS server name (management directory name)
- Description
-
The EADS server is stopping.
-
KDEA00003-W
The server status was set to "ISOLATED".
- Description
-
The EADS server has become isolated.
- Action
-
The possible causes are as follows:
-
The eztool isolate command was executed.
-
A problem that prevents operation occurred on the EADS server.
See 12.2.1 If one or more EADS servers are isolated, and take action according to the instructions given in this subsection.
-
-
KDEA00004-E
Log initialization failed. (directory path = aa....aa)
aa....aa: Path name of the log output destination
- Description
-
An attempt to initialize the log failed.
- Action
-
The possible causes are as follows:
-
The specified log output directory is invalid.
-
There is a problem in the log output directory or with the log file permissions.
Determine the cause of the error, eliminate it, and then restart the EADS server.
-
-
KDEA00005-E
A property file cannot be read. (file path = aa....aa)
aa....aa: Path name to the property file
- Description
-
The property file cannot be read.
The possible causes are as follows:
-
The property file does not exist.
-
The property file cannot be opened.
-
The path name points to a directory rather than to a file.
-
- Action
-
Determine the cause of the error from the standard output, message logs, or exception logs, eliminate it, and then restart the EADS server.
-
KDEA00006-E
The server failed to start. Startup of the server will now end.
- Description
-
Startup processing failed.
Startup of the EADS server is stopping because a problem occurred during startup processing of the EADS server.
- Action
-
Determine the cause of the error by checking the message that was output immediately before this message, eliminate the cause, and then restart the EADS server.
-
KDEA00016-E
An attempt to open a port failed. (address = aa....aa:bb....bb)
aa....aa: IP address
bb....bb: Port number
- Description
-
The communication port cannot be opened.
The possible causes are as follows:
-
The specified IP address is invalid.
-
The specified port number is already in use.
-
The same port number was specified for different parameters.
-
The specified port number is a well-known port for which the user does not have permissions.
-
- Action
-
Check and, if necessary, revise the values specified in the following server property parameters:
Determine the cause of the error from the exception logs, eliminate it, and then restart the EADS server.
-
KDEA00020-I
Initialization of the server will now start. (version = aa....aa)
aa....aa: EADS server version
- Description
-
Initialization of the EADS server is starting.
-
KDEA00021-I
Initialization of the server was completed.
- Description
-
Initialization of the EADS server has been completed.
-
KDEA00028-E
An exception occurred on the server. (exception = aa....aa)
aa....aa: Exception (or error) that occurred
- Description
-
An exception (or error) occurred on the EADS server.
The EADS server has stopped.
- Action
-
Determine the cause of the error from the exception logs and the message that was output immediately before this message, eliminate the cause, and then restart the EADS server.
-
KDEA00029-E
The specified cache was not found. (cache name = aa....aa)
aa....aa: Cache name
- Description
-
The specified cache was not found. An operation was performed on a nonexistent cache.
- Action
-
Create the cache, or else check the processing and revise it if necessary.
-
KDEA00031-E
The thread stopped. (thread name = aa....aa)
aa....aa: Thread name
- Description
-
A problem occurred on the EADS server, and the thread stopped.
- Action
-
Contact the customer support center.
-
KDEA00032-E
An exception occurred while waiting for a connection request. (local = aa....aa:bb....bb)
aa....aa: IP address of the EADS server (string representation of java.net.InetAddress)
bb....bb: Port number of the EADS server
- Description
-
An exception occurred while waiting for a connection request.
- Action
-
The possible causes are as follows:
-
A problem occurred on the EADS client with which communication was underway.
-
A problem occurred on the EADS server with which communication was underway.
-
A problem occurred on the host with which communication was underway.
-
A network problem occurred.
Determine the cause of the error from the exception logs and then eliminate it.
-
-
KDEA00033-W
The number of received connection requests exceeds the maximum number of simultaneous connections. (local = aa....aa:bb....bb, remote = cc....cc:dd....dd, max connections = ee....ee)
aa....aa: IP address of the EADS server (string representation of java.net.InetAddress)
bb....bb: Port number of the EADS server
cc....cc: IP address of the connection source (string representation of java.net.InetAddress)
dd....dd: Port number of the connection source
ee....ee: Maximum number of simultaneous connections
- Description
-
The server received a connection request that exceeded the maximum number of simultaneous connections.
The EADS server returns an error and cuts off communication for connections exceeding the maximum number of simultaneous connections.
Note that this message might also be output in the following cases:
-
All EADS servers in the cluster are restarted while the EADS client is running.
-
A connection timeout occurs between the EADS client and the EADS server due to a temporary increase in load on the EADS server.
-
- Action
-
Check and, if necessary, revise the maximum number of simultaneous connections (the server property parameter eads.server.maxConnections).
-
KDEA00036-E
An exception occurred during request handling. (local = aa....aa:bb....bb, remote = cc....cc:dd....dd)
aa....aa: IP address of the EADS server (string representation of java.net.InetAddress)
bb....bb: Port number of the EADS server
cc....cc: IP address of the connection source (string representation of java.net.InetAddress)
dd....dd: Port number of the connection source
- Description
-
An exception occurred while the request was being processed.
- Action
-
The possible causes are as follows:
-
A problem occurred on the EADS client with which communication was underway.
-
A problem occurred on the host with which communication was underway.
-
A network problem occurred.
Determine the cause of the problem, and then eliminate it.
-
-
KDEA00039-E
An exception or error occurred on the server. (details = aa....aa)
aa....aa: Details
- Description
-
An exception (or error) occurred on the EADS server while a request was being processed. As a result, communication was cut off.
- Action
-
Determine the cause of the error from the exception logs and then eliminate it.
If it remains unresolved, contact the customer support center.
-
KDEA00041-I
The port will now close. (address = aa....aa:bb....bb)
aa....aa: IP address (string representation of java.net.InetAddress)
bb....bb: Port number
- Description
-
The port is closing.
-
KDEA00042-I
The library was added to the class path. (file path = aa....aa)
aa....aa: Path name of the library file
- Description
-
The library was added to the classpath.
-
KDEA00045-E
A received request is not supported by the server. (local = aa....aa:bb....bb, remote = cc....cc:dd....dd)
aa....aa: IP address of the EADS server
bb....bb: Port number of the EADS server
cc....cc: IP address of the connection source
dd....dd: Port number of the connection source
- Description
-
A received request is not supported by the EADS server.
The request will not be processed.
- Action
-
The possible causes are as follows:
-
An invalid EADS client is connected.
-
A different version of the EADS client is connected.
Make sure that the correct EADS client is being used.
-
-
KDEA00047-E
An error occurred during reception of a request. (local = aa....aa:bb....bb, remote = cc....cc:dd....dd)
aa....aa: IP address of the EADS server (string representation of java.net.InetAddress)
bb....bb: Port number of the EADS server
cc....cc: IP address of the connection source (string representation of java.net.InetAddress)
dd....dd: Port number of the connection source
- Description
-
An error occurred during reception processing of the request.
- Action
-
The possible causes are as follows:
-
A problem occurred on the EADS client with which communication was underway.
-
A problem occurred on the host with which communication was underway.
-
A network problem occurred.
Determine the cause of the error from the exception logs and then eliminate it.
-
-
KDEA00048-E
An error occurred during the sending of a response. (local = aa....aa:bb....bb, remote = cc....cc:dd....dd)
aa....aa: IP address of the EADS server (string representation of java.net.InetAddress)
bb....bb: Port number of the EADS server
cc....cc: IP address of the connection source (string representation of java.net.InetAddress)
dd....dd: Port number of the connection source
- Description
-
An error occurred during send processing of the response.
- Action
-
The possible causes are as follows:
-
A problem occurred on the EADS client with which communication was underway.
-
A problem occurred on the host with which communication was underway.
-
A network problem occurred.
Determine the cause of the error from the exception logs and then eliminate it.
-
-
KDEA00049-I
A redirect notification was sent to the client. (local = aa....aa:bb....bb, remote = cc....cc:dd....dd, redirect = ee....ee:ff....ff)
aa....aa: IP address of the EADS server (string representation of java.net.InetAddress)
bb....bb: Port number of the EADS server
cc....cc: IP address of the connection source (string representation of java.net.InetAddress)
dd....dd: Port number of the connection source
ee....ee: IP address of the redirect destination (string representation of java.net.InetAddress)
ff....ff: Port number of the redirect destination
- Description
-
The EADS client is notified of the redirection.
-
KDEA00050-E
An unexpected initialization error occurred.
- Description
-
An unexpected initialization error occurred.
- Action
-
Contact the customer support center.
-
KDEA00051-E
The content of the request is invalid.
- Description
-
The content of the request is invalid.
- Action
-
The possible causes are as follows:
-
A problem occurred on the EADS client with which communication was underway.
-
A problem occurred on the host with which communication was underway.
-
A network problem occurred.
Determine the cause of the error, and then eliminate it.
-
-
KDEA00052-E
An unexpected exception occurred.
- Description
-
An unexpected exception occurred.
- Action
-
Contact the customer support center.
-
KDEA00053-E
Loading of the library file failed.
- Description
-
An attempt to load the library file failed.
- Action
-
The possible causes are as follows:
-
The library file is invalid.
-
There is a problem in the library file or directory permissions.
Determine the cause of the error, and then eliminate it.
-
-
KDEA00054-I
A server port was opened. (local = aa....aa:bb....bb)
aa....aa: IP address of the EADS server (string representation of java.net.InetAddress)
bb....bb: Port number of the EADS server
- Description
-
A port was opened.
-
KDEA00055-I
The server will now start accepting requests. (local = aa....aa:bb....bb)
aa....aa: IP address of the EADS server (string representation of java.net.InetAddress)
bb....bb: Port number of the EADS server
- Description
-
The server will now start accepting requests.
-
KDEA00056-E
An unexpected exception occurred. (detail = aa....aa)
aa....aa: Maintenance information
- Description
-
An unexpected exception occurred.
- Action
-
Contact the customer support center.
-
KDEA00057-E
An attempt to allocate the data area has failed. (type = aa....aa, data size = bb....bb)
aa....aa: Type
bb....bb: Size of the memory area whose allocation was attempted
- Description
-
An attempt to allocate memory failed because there is not enough available memory area.
The following table provides the cause by type:
Type
Cause
store
There is not enough available memory area for storing values.
- Action
-
Take the following action according to the type:
Type
Action
store
Increase the value of the eads.java.external.heapsize parameter in the shared properties.
-
KDEA00058-E
The input data are too long. (type = aa....aa, request = bb....bb, limit = cc....cc)
aa....aa: Type
bb....bb: Required size
cc....cc: Size limit
- Description
-
The size required for the input data exceeds the size limit.
The following table provides the cause by type:
Type
Cause
store
The value specified in the eads.java.external.heapsize shared property parameter is too small for the size of the value.
Alternatively, the value size exceeds the maximum value that can be specified.
dist
The value of the eads.replication.external.heapsize parameter in the shared properties is too small for the size of the history of update operations.
- Action
-
Make sure that the value size does not exceed the maximum value that can be specified.
If the value size does not exceed the maximum value that can be specified, take the action appropriate for the type as shown in the following table:
Type
Action
store
Increase the value of the eads.java.external.heapsize parameter in the shared properties.
dist
Increase the value of the eads.replication.external.heapsize parameter in the shared properties.
If you increase this parameter value, also increase the value of the eads.java.external.heapsize parameter in the shared properties.
-
KDEA00060-W
The fragmentation of data occurred. (type = aa....aa, count = bb....bb)
aa....aa: Type
bb....bb: Number of times data fragmentation occurred
- Description
-
The data stored in the explicit heap was fragmented.
The following table provides the cause by type:
Type
Cause
store
Values were fragmented.
dist
The history of update operations was fragmented.
The displayed count indicates the number of times fragmentation has occurred since the last time this message was output.
- Action
-
If this message is output frequently, fragmentation might have occurred due to an inadequate explicit heap and as a result performance might have become degraded. Take the following action according to the type:
Type
Action
store
Increase the value of the eads.java.external.heapsize parameter in the shared properties.
dist
Increase the value of the eads.replication.external.heapsize parameter in the shared properties.
If you increase this parameter value, also increase the value of the eads.java.external.heapsize parameter in the shared properties.
-
KDEA00061-E
The size of key exceeds the maximum. (maximum size (bytes) = aa....aa, key size (bytes) = bb....bb)
aa....aa: Maximum size (unit: bytes)
bb....bb: key size (unit: bytes)
- Description
-
The specified key size exceeds the maximum size of a key that can be stored in the cluster.
- Action
-
Check and, if necessary, revise the specified key size.
Check and, if necessary, revise the value of the eads.cache.key.maxsize parameter in the shared properties.
-
KDEA00062-E
The size of group name exceeds the maximum. (maximum size (bytes) = aa....aa, group name size (bytes) = bb....bb)
aa....aa: Maximum size (unit: bytes)
bb....bb: Group name size (unit: bytes)
- Description
-
The specified group name is longer than the maximum size of a group name that can be stored in the cluster (the value of the eads.cache.key.maxsize parameter in the shared properties minus 2).
- Action
-
Check and, if necessary, revise the length of the specified group name.
Check and, if necessary, revise the value of the eads.cache.key.maxsize parameter in the shared properties.
-
KDEA01004-I
Initialization of the user function is complete. (function name = aa....aa)
aa....aa: Name of the user function
- Description
-
Initialization of the user function is complete.
-
KDEA01005-W
An exception or error occurred in the init method of the user function. (function name = aa....aa)
aa....aa: Name of the user function
- Description
-
An exception (or error) occurred in init() in the user function.
- Action
-
Check the user exception logs, eliminate the cause of the error, and then restart the EADS server.
-
KDEA01009-I
Processing to terminate the user function is complete. (function name = aa....aa)
aa....aa: Name of user function
- Description
-
Termination processing of the user function is complete.
-
KDEA01010-W
Processing to terminate the user function failed. (function name = aa....aa)
aa....aa: Name of user function
- Description
-
An attempt to terminate processing of the user function failed (an exception (or error) occurred in destroy() in the user function).
- Action
-
Check the user exception logs and eliminate the cause of the error.
-
KDEA01011-E
An exception or error occurred in the user function. (function name = aa....aa)
aa....aa: Name of user function
- Description
-
An exception (or error) occurred in the user function (an exception (or error) occurred during the execution of execute() in the user function).
- Action
-
Check the user exception logs and eliminate the cause of the error.
-
KDEA01012-W
Generation of a user function instance failed. (function name = aa....aa)
aa....aa: Name of user function
- Description
-
An attempt to generate a user function instance failed.
- Action
-
The possible causes are as follows:
-
An exception (or error) occurred while the user function instance was being generated.
-
You do not have access permissions for the default constructor of the user function.
-
The user function is in a format in which its instance cannot be generated.
Check the user exception logs, eliminate the cause of the error, and then restart the EADS server.
-
-
KDEA01016-E
An exception or error occurred in the user function call processing. (function name = aa....aa, details = bb....bb)
aa....aa: User function name to be called
bb....bb: Details
- Description
-
An exception (or error) occurred in the processing of the user function call.
- Action
-
Determine the cause of the error from the details, and then eliminate the problem.
-
KDEA01017-E
The specified user function was not found. (function name = aa....aa)
aa....aa: Name of the user function
- Description
-
The specified user function was not found.
- Action
-
The possible causes are as follows:
-
No user function with the specified name exists on the EADS server.
-
An attempt was made to execute an invalid user function.
Make sure the user function name is specified correctly.
If the user function name is specified correctly, make sure the specified user function is registered as a valid user function on the EADS server.
-
-
KDEA01018-E
An attempt to serialize the user function execution results failed. (function name = aa....aa, details = bb....bb)
aa....aa: User function name to be called
bb....bb: Details
- Description
-
The object specified in the return value as the user function execution results could not be serialized.
- Action
-
Check whether the specified value is a serializable object.
If it is an object that is not serializable, change it to a serializable object.
-
KDEA01019-E
An attempt to deserialize the argument failed. (function name = aa....aa, details = bb....bb)
aa....aa: Name of user function to be called
bb....bb: Details
- Description
-
An argument sent from the EADS client could not be deserialized.
- Action
-
Check the classes in the user function library, and check whether the argument object specified in the EADS client can be deserialized.
If the class is missing, add the class to the user function library or shared library, and then restart the EADS server.
-
KDEA01021-E
The specified cache was not found. (function name = aa....aa, cache name = bb....bb)
aa....aa: User function name to be called
bb....bb: Cache name
- Description
-
An operation was performed on a nonexistent cache.
- Action
-
Either create a cache or check and, if necessary, revise the specified cache name.
-
KDEA01022-I
Initialization of the user function library will now start. (file path = aa....aa)
aa....aa: File path
- Description
-
Initialization of the user function library is starting.
-
KDEA01023-I
Initialization of the user function library is complete. (file path = aa....aa, success = bb....bb, failure = cc....cc)
aa....aa: File path
bb....bb: Number of user functions that have been initialized successfully
cc....cc: Number of user functions whose initialization failed
- Description
-
Initialization of the user function library has been completed.
-
KDEA01024-I
No user function library was found.
- Description
-
The user functions will not be initialized because there is no user function library.
-
KDEA01025-I
"user_function.jar" will not be initialized because a file called "user-function.jar" also exists.
- Description
-
A user function whose file name is user_function.jar cannot be initialized because the same user function already exists.
-
KDEA01026-I
A user function cannot be loaded because a user function with the same fully-qualified class name already exists. (function name = aa....aa)
aa....aa: Name of the user function
- Description
-
The target user function cannot be imported because a user function with the same fully qualified class name already exists.
-
KDEA01027-E
An exception or error occurred in the initialization processing of the user function. (details = aa....aa)
aa....aa: Details
- Description
-
An exception (or an error) occurred during user function initialization processing.
- Action
-
Identify the cause of the error from the detailed information and exception logs, eliminate the problem, and then re-start the EADS server.
-
KDEA01901-I
WRITING (cache = aa....aa, range = bb....bb, ecf = cc....cc, remain = dd....dd)
aa....aa: Cache name
bb....bb: Range ID
cc....cc: Path of the cache data files
dd....dd: Number of unused cache data files
- Description
-
Import processing has started on the cache data files.
-
KDEA01902-I
COMPACTION (cache = aa....aa, range = bb....bb, ecf = cc....cc, size (total = dd....dd, relocated = ee....ee, valid = ff....ff -> gg....gg), count (total = hh....hh, relocated = ii....ii, valid = kk....kk -> mm....mm), time = nn....nn, remain = pp....pp)
aa....aa: Cache name
bb....bb: Range ID
cc....cc: Path of the cache data files subject to compaction (absolute path)
dd....dd: Size of space already in use in the files (bytes)
ee....ee: Amount of data moved (bytes)
ff....ff: Amount of effective data before compaction (bytes)
gg....gg: Amount of effective data after compaction (bytes)
hh....hh: Total number of data items including invalid data
ii....ii: Number of data items moved
kk....kk: Number of effective data items before compaction
mm....mm: Number of effective data items after compaction
nn....nn: Processing time (milliseconds)
pp....pp: Number of unused cache data files
- Description
-
Compaction processing was performed on cache data files.
-
KDEA01903-I
FILE INFO (cache = aa....aa, range = bb....bb, ecf = cc....cc, size = dd....dd, allocated size = ee....ee)
aa....aa: Cache name
bb....bb: Range ID
cc....cc: Path of the cache data files
dd....dd: File size
ee....ee: Actual size allocated
- Description
-
The actual size of the area allocated to the cache data files differs from the file sizes.
-
KDEA01904-I
CORRECTION (cache = aa....aa, range = bb....bb, ecf = cc....cc)
aa....aa: Cache name
bb....bb: Range ID
cc....cc: Path of the cache files
- Description
-
Cache files were modified.