7.6 Messages from KDJE60000 to KDJE69999
This section explains the messages from KDJE60000 to KDJE69999.
-
KDJE60001-I
The J2EE server will start as ''Java EE Container Mode''. (container version = aa....aa)
aa....aa: Value of the container version
- Description
-
This message indicates that this J2EE server will run in Java EE container mode.
-
KDJE60003-E
Unexpected exception occurred during Java EE Container mode initialization. (detail = aa....aa)
aa....aa: Detailed information of the occurred exception
- Description
-
Unexpected exception occurred during Java EE Container mode initialization.
- Action
-
Contact maintenance personnel.
-
KDJE60004-E
Unexpected exception occurred during Java EE Container mode termination. (detail = aa....aa)
aa....aa: Detailed information of the occurred exception
- Description
-
Unexpected exception occurred during Java EE Container mode termination.
- Action
-
Contact maintenance personnel.
-
KDJE60005-E
An illegal configuration file is specified. (container version = aa....aa, configuration file version = bb....bb)
aa....aa: Value of the container version
bb....bb: Value of the definition file version
- Description
-
Startup of the J2EE server is interrupted because the container version of the J2EE server does not match the expected version of the specified definition file.
- Action
-
After the logical J2EE server having the same name created by using the management portal or Smart Composer functionality was deleted, unsetup of the J2EE server might not have been performed.
Delete the logical J2EE server, perform unsetup by using the cjsetup command (server management command), and then re-create and set up the logical J2EE server.
-
KDJE60010-W
Some message IDs for output suppression will be ignored, because the ones specified for the property ejbserver.javaeeLogfilter.msgids are invalid.
- Description
-
The message ID specified for the property ejbserver.javaeeLogfilter.msgids is invalid.
- Action
-
Revise the set value of the property ejbserver.javaeeLogfilter.msgids, set the correct value, and then restart the J2EE server.
-
KDJE60011-I
Message output will be suppressed. (message ID = aa....aa)
aa....aa: List of message IDs (separated by commas)
- Description
-
Output of messages that match the specified message IDs to the public log is suppressed.
-
KDJE60014-W
Unexpected exception occurred during Java EE logger initialization. (detail = aa....aa)
aa....aa: Detailed information of the occurred exception
- Description
-
Unexpected exception occurred during Java EE logger initialization.
- Action
-
Contact maintenance personnel.
-
KDJE60110-W
The character string length of the constraint violation message which is used in the function that is based on the Bean Validation specification is longer than the value of the system property ejbserver.javaee.bv.message-interpolation.alert-threshold. (tid = aa....aa, property value = bb....bb, message length = cc....cc, message = dd....dd)
aa....aa: Thread ID
bb....bb: Value of the system property ejbserver.javaee.bv.message-interpolation.alert-threshold
cc....cc: Character string length of the constraint violation message to be used as the interpolation target of Bean Validation
dd....dd: Constraint violation message to be used as the interpolation target of Bean Validation. This message consists of the first part containing 100 characters, an asterisk (*), and the last part containing 100 characters.
- Description
-
The character string length of the constraint violation message which is used in the function that is based on the Bean Validation specification is longer than the value of the system property ejbserver.javaee.bv.message-interpolation.alert-threshold.
- Action
-
Revise the application configuration to confirm that excessively long constraint messages will not be used. Alternatively, confirm that the value of the system property is appropriate and, if necessary, revise it.
-
KDJE60111-W
An invalid property value is specified. The default value will be used. (property = aa....aa, value = bb....bb, default value = cc....cc)
aa....aa: Property name
bb....bb: User-specified value
cc....cc: Default value
- Description
-
An invalid property value is specified. The default value will be used.
- Action
-
Check the value specified for the relevant property, and then specify a value within the specifiable range.
-
KDJE60130-I
Exporting the list of deleting batch jobs is complete.
- Description
-
The list of batch jobs to be deleted was output successfully.
- Action
-
Check the contents of the list of deleting batch jobs.
-
KDJE60131-W
The list of deleting batch jobs was not exported because no matching batch jobs found.
- Description
-
The list of batch jobs to be deleted was not output because no data matched the deletion condition.
-
KDJE60132-E
The specified path is invalid. (path = aa....aa)
aa....aa: Specified path name
- Description
-
The specified path is invalid.
- Action
-
Specify a nonexistent file path as an absolute path in the deletion-target list file.
-
KDJE60133-E
An exception occurred during obtaining the list of deleting batch jobs from database. (details = aa....aa)
aa....aa: Detailed information of the occurred exception
- Description
-
An exception occurred while the database was being accessed.
- Action
-
Remove the cause of the error by referencing the detailed information.
-
KDJE60134-E
An exception occurred during output the list of deleting batch jobs. (path = aa....aa, details = bb....bb)
aa....aa: Specified path name
bb....bb: Detailed information of the occurred exception
- Description
-
An exception occurred while the file was being accessed.
- Action
-
Remove the cause of the error by referencing the detailed information.
-
KDJE60135-I
Deleting batch jobs is complete.
- Description
-
The batch job was deleted successfully.
-
KDJE60136-E
An exception occurred during reading the list of deleting batch jobs. (path = aa....aa, details = bb....bb)
aa....aa: Specified path name
bb....bb: Detailed information of the occurred exception
- Description
-
An exception occurred while the file was being accessed.
- Action
-
Remove the cause of the error by referencing the detailed information.
-
KDJE60137-E
The list of deleting batch jobs is invalid. (path = aa....aa)
aa....aa: Specified path name
- Description
-
An attempt to analyze the deletion-target list file failed.
- Action
-
Confirm that the file path to the deletion-target list file is correct. If the file path is correct, re-execute the cjdeljbatchjobs command (with -list specified).
-
KDJE60138-E
An exception occurred during deleting batch jobs from database. (details = aa....aa)
aa....aa: Detailed information of the occurred exception
- Description
-
An exception occurred while the database was being accessed.
- Action
-
Remove the cause of the error by referencing the detailed information.
-
KDJE60139-E
The number of records deleted from the database does not match with the specified file.
- Description
-
The number of records to be deleted in the entered deletion-target list file does not match the number of records to be deleted when the cjdeljbatchjobs command (with -delete specified) is executed. One of the following operations might have been performed:
- The cjdeljbatchjobs command (with -delete specified) has already been executed.
- After the cjdeljbatchjobs command (with -list specified) was executed, batch processing is started before the cjdeljbatchjobs command (with -delete specified) is executed.
- Action
-
Re-execute the cjdeljbatchjobs command (with -list specified) to create a deletion-target list file. Then, execute the cjdeljbatchjobs command (with -delete specified) by specifying the deletion-target list file you created.
-
KDJE60140-E
The configured application tag dose not match with the requested application tag.(apptag configured to J2EE server = aa....aa, requested apptag = bb....bb)
aa....aa: Application tag set for the J2EE server
bb....bb: Application tag obtained from the deletion-target list file
- Description
-
The application tag set for the J2EE server (the value of the ejbserver.javaee.batch.J2EE-application-name.appTag system property or the default value) does not match the requested application tag (value of apptag in the deletion-target list file).
The followings might be the causes.
- The value of the system property is changed after the cjdeljbatchjobs command (with -list specified) was executed.
- The command is executed by specifying the J2EE server name that differs from the one used when the cjdeljbatchjobs command (with -list specified) was executed.
- The contents of the deletion-target list file are changed.
- Action
-
Re-execute the cjdeljbatchjobs command (with -list specified) to create a deletion-target list file. Then, execute the cjdeljbatchjobs command (with -delete specified) by specifying the deletion-target list file you created.
-
KDJE60310-W
An invalid property value is specified. The default value will be used. (property = aa....aa, value = bb....bb, default value = cc....cc)
aa....aa: Property name
bb....bb: User-specified value
cc....cc: Default value
- Description
-
An invalid property value is specified. The default value will be used.
- Action
-
Check the value specified for the relevant property, and then specify a value within the specifiable range.
-
KDJE60311-E
A timeout occurred on the request operation of JAX-RS Client API. (reason = aa....aa, connect timeout = bb....bb, read timeout = cc....cc, RootAP = dd....dd, url = ee....ee)
aa....aa: Reason of timeout
bb....bb: Connection timeout set value (milliseconds)
cc....cc: Read timeout set value (milliseconds)
dd....dd: Root application information
ee....ee: Request destination URL
- Description
-
A timeout occurred on the request operation of JAX-RS Client API.
- Action
-
Remove the cause of the timeout.
-
KDJE60312-E
The JAX-RS Client API could not complete the requested operation. (detail = aa....aa, RootAP = bb....bb, url = cc....cc)
aa....aa: Detailed message
bb....bb: Root application information
cc....cc: Request destination URL
- Description
-
The JAX-RS Client API could not complete the requested operation.
- Action
-
Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.
-
KDJE60510-W
An invalid property value is specified. The default value will be used. (property = aa....aa, value = bb....bb, default value = cc....cc)
aa....aa: Property name
bb....bb: User-specified value
cc....cc: Default value
- Description
-
An invalid property value is specified. The default value will be used.
- Action
-
Check the value specified for the relevant property, and then specify a value within the specifiable range.
-
KDJE60511-I
The executor for Java Batch has registered. (jndiName = aa....aa, minThreads = bb....bb, maxThreads = cc....cc, queueSize = dd....dd, keepAliveTime = ee....ee)
aa....aa: JNDI name of the executor
bb....bb: Minimum number of threads in the thread pool
cc....cc: Maximum number of threads in the thread pool
dd....dd: Queue length of the thread pool
ee....ee: Maximum length of time to wait for a used thread to be reused (seconds)
- Description
-
The executor for Java Batch has registered
-
KDJE60512-E
Unexpected exception occurred during registering the executor for Java Batch. (jndiName = aa....aa, minThreads = bb....bb, maxThreads = cc....cc, queueCapacity = dd....dd, keepAliveTime = ee....ee, details = ff....ff)
aa....aa: JNDI name of the executor
bb....bb: Minimum number of threads in the thread pool
cc....cc: Maximum number of threads in the thread pool
dd....dd: Queue length of the thread pool
ee....ee: Maximum length of time to wait for a used thread to be reused (seconds)
ff....ff: Detailed information of the occurred exception
- Description
-
Unexpected exception occurred during registering the executor for Java Batch.
- Action
-
Check the contents of the stack trace and then take action.
-
KDJE60513-E
Cannot find the specified executor for Java Batch. (jndiName = aa....aa, details = bb....bb)
aa....aa: JNDI name of the executor
bb....bb: Detailed information of the occurred exception
- Description
-
Cannot find the specified executor for Java Batch.
- Action
-
Check the KDJE60005-I message to make sure that the executor for Java Batch having the specified JNDI name has been registered correctly.
-
KDJE60514-E
Cannot find the specified data source for Java Batch. (jndiName = aa....aa, details = bb....bb)
aa....aa: JNDI name of the data source
bb....bb: Detailed information of the occurred exception
- Description
-
Cannot find the specified data source for Java Batch.
- Action
-
Make sure that the DB Connector having the specified JNDI name as an alias has started correctly.
-
KDJE60517-E
Can not find aa....aa for Job Repository of Java Batch. (name = bb....bb)
aa....aa: Check target
bb....bb: Name
- Description
-
A job repository used to store information about batch jobs is not found.
- Action
-
Create a job repository used to store information about batch jobs. If there is a remaining table or the like, clear the table, and then create a job repository.
-
KDJE60518-E
Failed to create aa....aa for Job Repository of Java Batch. (name = bb....bb)
aa....aa: Creation target
bb....bb: Name
- Description
-
An attempt to create a job repository used to store information about batch jobs failed because repository generation was performed within the JTA transaction.
- Action
-
Set ejbserver.javaee.batch.jobRepository.autoCreate.enabled as false.
-
KDJE60519-E
The data source used to store information about batch jobs is not HiRDB.
- Description
-
The data source used to store information about batch jobs is not HiRDB.
- Action
-
Make sure that the data source used to store information about batch jobs is HiRDB.
-
KDJE60810-W
An invalid property value is specified. The default value will be used. (property = aa....aa, value = bb....bb, default value = cc....cc)
aa....aa: Property name
bb....bb: User-specified value
cc....cc: Default value
- Description
-
An invalid property value is specified. The default value will be used.
- Action
-
Check the value specified for the relevant property, and then specify a value within the specifiable range.
-
KDJE60811-I
The specified ManagedExecutorService has been registered. (jndiName = aa....aa, hungAfterSeconds = bb....bb, longRunningTasks = cc....cc, corePoolSize = dd....dd, maxPoolSize = ee....ee, keepAliveSeconds = ff....ff, threadLifeTimeSeconds = gg....gg, threadPriority = hh....hh, taskQueueCapacity = ii....ii, awaitTerminationSeconds = jj....jj)
aa....aa: JNDI name
bb....bb: Task execution time after which the task is determined as no response (seconds)
cc....cc: Long-time task
dd....dd: Initial number of threads
ee....ee: Maximum number of threads
ff....ff: Maximum length of time to wait for a used thread to be reused (seconds)
gg....gg: Period of time to continuously reuse threads (seconds)
hh....hh: Priority of the thread
ii....ii: Queue length
jj....jj: Length of time to wait for the tasks to terminate when the server stops (seconds)
- Description
-
The specified ManagedExecutorService has been registered.
-
KDJE60812-E
Unexpected exception occurred during registering the ManagedExecutorService. (jndiName = aa....aa, hungAfterSeconds = bb....bb, longRunningTasks = cc....cc, corePoolSize = dd....dd, maxPoolSize = ee....ee, keepAliveSeconds = ff....ff, threadLifeTimeSeconds = gg....gg, threadPriority = hh....hh, taskQueueCapacity = ii....ii, awaitTerminationSeconds = jj....jj, details = kk....kk)
aa....aa: JNDI name
bb....bb: Task execution time after which the task is determined as no response (seconds)
cc....cc: Long-time task
dd....dd: Initial number of threads
ee....ee: Maximum number of threads
ff....ff: Maximum length of time to wait for a used thread to be reused (seconds)
gg....gg: Period of time to continuously reuse threads (seconds)
hh....hh: Priority of the thread
ii....ii: Queue length
jj....jj: Length of time to wait for the tasks to terminate when the server stops (seconds)
kk....kk: Detailed information of the occurred exception
- Description
-
Unexpected exception occurred during registering the ManagedExecutorService.
- Action
-
Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.
-
KDJE60813-I
The specified ManagedScheduledExecutorService has been registered. (jndiName = aa....aa, hungAfterSeconds = bb....bb, longRunningTasks = cc....cc, corePoolSize = dd....dd, keepAliveSeconds = ee....ee, threadLifeTimeSeconds = ff....ff, threadPriority = gg....gg, awaitTerminationSeconds = hh....hh)
aa....aa: JNDI name
bb....bb: Task execution time after which the task is determined as no response (seconds)
cc....cc: Long-time task
dd....dd: Initial number of threads
ee....ee: Maximum length of time to wait for a used thread to be reused (seconds)
ff....ff: Period of time to continuously reuse threads (seconds)
gg....gg: Priority of the thread
hh....hh: Length of time to wait for the tasks to terminate when the server stops (seconds)
- Description
-
The specified ManagedScheduledExecutorService has been registered.
-
KDJE60814-E
Unexpected exception occurred during registering the ManagedScheduledExecutorService. (jndiName = aa....aa, hungAfterSeconds = bb....bb, longRunningTasks = cc....cc, corePoolSize = dd....dd, keepAliveSeconds = ee....ee, threadLifeTimeSeconds = ff....ff, threadPriority = gg....gg, awaitTerminationSeconds = hh....hh, details = ii....ii)
aa....aa: JNDI name
bb....bb: Task execution time after which the task is determined as no response (seconds)
cc....cc: Long-time task
dd....dd: Initial number of threads
ee....ee: Maximum length of time to wait for a used thread to be reused (seconds)
ff....ff: Period of time to continuously reuse threads (seconds)
gg....gg: Priority of the thread
hh....hh: Length of time to wait for the tasks to terminate when the server stops (seconds)
ii....ii: Detailed information of the occurred exception
- Description
-
Unexpected exception occurred during registering the ManagedScheduledExecutorService.
- Action
-
Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.
-
KDJE60815-I
The specified ManagedThreadFactory has been registered. (jndiName = aa....aa, threadPriority = bb....bb)
aa....aa: JNDI name
bb....bb: Priority of the thread
- Description
-
The specified ManagedThreadFactory has been registered.
-
KDJE60816-E
Unexpected exception occurred during registering the ManagedThreadFactory. (jndiName = aa....aa, threadPriority = bb....bb, details = cc....cc)
aa....aa: JNDI name
bb....bb: Priority of the thread
cc....cc: Detailed information of the occurred exception
- Description
-
Unexpected exception occurred during registering the ManagedThreadFactory.
- Action
-
Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.
-
KDJE60817-I
The long running task checker thread will now start. (hungCheckIntervalSeconds = aa....aa)
aa....aa: Execution time monitoring interval (seconds)
- Description
-
The long running task checker thread will now start.
-
KDJE60818-W
The following task has been running for longer time than the configured hung task threshold setting. (jndiName = aa....aa, hungAfterSeconds = bb....bb, runningTimeSeconds = cc....cc, taskId = dd....dd, RootAP = ee....ee)
aa....aa: JNDI name of ExecutorService
bb....bb: Task execution time after which the task is determined as no response (seconds)
cc....cc: Task running time (seconds)
dd....dd: Task ID
ee....ee: Root application information
- Description
-
The following task has been running for longer time than the configured hung task threshold setting.
- Action
-
Check the log file and performance analysis trace, and then remove the cause due to which the relevant task does not terminate.
If the execution time is appropriate, revise the value specified for hungAfterSeconds of the relevant ExecutorService.
-
KDJE60819-I
The long running task checker thread will now stop.
- Description
-
The long running task checker thread will now stop.
-
KDJE60820-I
Waiting for the remaining tasks in the ManagedExecutorService. (jndiName = aa....aa, awaitTerminationSeconds = bb....bb)
aa....aa: JNDI name
bb....bb: Length of time to wait for the tasks to terminate when the server stops (seconds)
- Description
-
Waiting for the remaining tasks in the ManagedExecutorService.
-
KDJE60821-W
Timeout occurred during waiting for the remaining tasks in the ManagedExecutorService. (jndiName = aa....aa)
aa....aa: JNDI name
- Description
-
Timeout occurred during waiting for the remaining tasks in the ManagedExecutorService.
- Action
-
Some tasks have not terminated within the specified timeout period and other tasks remaining in the queue were not executed. Check the status of tasks by using, for example, the log file.
If the execution time is appropriate, revise the value specified for awaitTerminationSeconds of the relevant ExecutorService.
-
KDJE60822-W
Some tasks in the ManagedExecutorService has remained. (jndiName = aa....aa, numOfRemainedTasks = bb....bb)
aa....aa: JNDI name
bb....bb: Number of remaining tasks in the queue that were not executed
- Description
-
Some tasks in the ManagedExecutorService has remained.
- Action
-
Some tasks were forcibly terminated and other tasks remaining in the queue were not executed. Check the status of tasks by using, for example, the log file.
-
KDJE60823-I
The ManagedExecutorService has been unregistered successfully. (jndiName = aa....aa)
aa....aa: JNDI name
- Description
-
The ManagedExecutorService has been unregistered successfully.
-
KDJE60824-E
Unexpected exception occurred during unregistering the ManagedExecutorService. (jndiName = aa....aa, details = bb....bb)
aa....aa: JNDI name
bb....bb: Detailed information of the occurred exception
- Description
-
Unexpected exception occurred during unregistering the ManagedExecutorService.
- Action
-
Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.
-
KDJE60825-I
Waiting for the remaining tasks in the ManagedScheduledExecutorService. (jndiName = aa....aa, awaitTerminationSeconds = bb....bb)
aa....aa: JNDI name
bb....bb: Length of time to wait for the tasks to terminate when the server stops (seconds)
- Description
-
Waiting for the remaining tasks in the ManagedScheduledExecutorService.
-
KDJE60826-W
Timeout occurred during waiting for the remaining tasks in the ManagedScheduledExecutorService. (jndiName = aa....aa)
aa....aa: JND name
- Description
-
Timeout occurred during waiting for the remaining tasks in the ManagedScheduledExecutorService.
- Action
-
Some tasks have not terminated within the specified timeout period and other tasks remaining in the queue were not executed. Check the status of tasks by using, for example, the log file.
If the execution time is appropriate, revise the value specified for awaitTerminationSeconds of the relevant ExecutorService.
-
KDJE60827-W
Some tasks in the ManagedScheduledExecutorService has remained. (jndiName = aa....aa, numOfRemainedTasks = bb....bb)
aa....aa: JNDI name
bb....bb: Number of remaining tasks in the queue that were not executed
- Description
-
Some tasks in the ManagedScheduledExecutorService has remained.
- Action
-
Some tasks were forcibly terminated and other tasks remaining in the queue were not executed. Check the status of tasks by using, for example, the log file.
-
KDJE60828-I
The ManagedScheduledExecutorService has been unregistered successfully. (jndiName = aa....aa)
aa....aa: JNDI name
- Description
-
The ManagedScheduledExecutorService has been unregistered successfully.
-
KDJE60829-E
Unexpected exception occurred during unregistering the ManagedScheduledExecutorService. (jndiName = aa....aa, details = bb....bb)
aa....aa: JNDI name
bb....bb: Detailed information of the occurred exception
- Description
-
Unexpected exception occurred during unregistering the ManagedScheduledExecutorService.
- Action
-
Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.
-
KDJE60830-I
The ManagedThreadFactory has been unregistered successfully. (jndiName = aa....aa)
aa....aa: JNDI name
- Description
-
The ManagedThreadFactory has been unregistered successfully.
-
KDJE60831-E
Unexpected exception occurred during unregistering the ManagedThreadFactory. (jndiName = aa....aa, details = bb....bb)
aa....aa: JNDI name
bb....bb: Detailed information of the occurred exception
- Description
-
Unexpected exception occurred during unregistering the ManagedThreadFactory.
- Action
-
Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.