7.3 Messages from KDJE40000 to KDJE49999 : Messages

KDJE40000-E

An old version's server having the same name has been set up. The migration should be performed using the cjenvupdate command.

Description: An old version's server having the same name is set up. Migrate the environment using the cjenvupdate command.
Action: Use the cjenvupdate command to migrate the environment.

KDJE40001-I

The setup for the J2EE server has finished successfully. Server name = aa....aa

aa....aa: Server name

Description: The setup for the J2EE server (aa....aa) has finished successfully.

KDJE40002-E

The J2EE server has not been set up. Server name = aa....aa

aa....aa: Server name

Description: The J2EE server (aa....aa) is not set up.
Action: Run the cjsetup command to set up the server.

KDJE40003-E

The setup for the J2EE server has failed. Server name = aa....aa, Reason = bb....bb

aa....aa: Server name

bb....bb: Error contents

Description

An attempt to setup the J2EE server (aa....aa) has failed.

Action

Take action based on the error details.

Already been set up: The J2EE server is set up with the specified server name. To set up the J2EE server again, delete the server once using the cjsetup -d server-name command, and then re-execute the set up command.
Invalid server name: Invalid server name is specified. Single-byte alphanumeric characters, underscores (_), and hyphens (-) can be used in the server name within the range estimated by referencing the manual uCosminexus Application Server System Setup and Operation Guide. The first character of the server name must be an alphanumeric character.
Not supported edition: Execute in an edition of Application Server and Developer that supports the batch server.
In the case of *****: Take action based on the message displayed just before the error.

KDJE40004-E

aa....aa is too long: bb....bb

aa....aa: Target type

bb....bb: Target name

Description

When the target type is path name, the path up to the target name or the path specified in the definition of the target name is too long.

Action

When the target type is path name and the target name is ejb.server.log.directory or web.server.log.directory, specify a path of length 200 bytes or less.

When the target type is path name and the target name is a name other than those mentioned above, specify a path of length less than the MAX_PATH length of the OS.

KDJE40005-W

The specified value is invalid. The sleep processing will be performed with the default value (10 seconds).

Description: The specified value is invalid. The sleep processing will be performed with the default value (10 seconds).
Action: If the default value (10 seconds) causes an error, specify the correct value.

KDJE40006-I

Usage: cjsleep sleepTime

Description: This message describes the usage method of the cjsleep command.

KDJE40007-E

The system setting files aa....aa were not found. There is a possibility that the files are not installed properly, were removed or have permission problems. Reason = bb....bb

aa....aa: Path name

bb....bb: Reason

Description: The system setting file was not found or an attempt to read the file has failed.
Action: Re-install the files or revise the permissions.

KDJE40008-E

The file could not be copied from "aa....aa" to "bb....bb" because of the reason cc....cc. Check the file status.

aa....aa: Copy source file name

bb....bb: Copy destination file name

cc....cc: Details

Description: An attempt to copy the file has failed.
Action: Based on the details, remove the cause of the error, and then re-execute the command.

KDJE40010-I

Processing will wait for aa....aa seconds.

aa....aa: Numeric value

Description: This is the sleeping time of the cjsleep command.

KDJE40011-I

Usage: cjstartsv [serverName] [-nosecurity] [-nostartapp]

Description: This message describes the usage method of the cjstartsv command.

KDJE40012-I

Usage: cjstopsv [serverName] [-f | -fd [ThreadDumpInterval ThreadDumpCount]] [-wait [waitTime]]

Description: This message describes the usage method of the cjstopsv command.

KDJE40013-I

Start Time: aa....aa

Server Name: bb....bb

Server Version: cc....cc(dd....dd)

Process ID:ee....ee

aa....aa: Start time

bb....bb: Server name

cc....cc: Version

dd....dd: Build date

ee....ee: Process ID

Description: The start time (aa....aa), server name (bb....bb), version (cc....cc), build date (dd....dd), and process ID (ee....ee) of the server is displayed.

KDJE40014-E

The specified value for the aa....aa option is invalid.

aa....aa: Option name

Description: The specified value for the option is invalid.
Action: See the manual uCosminexus Application Server Command Reference Guide.

KDJE40016-E

An error has occurred in the internal function. (aa....aa)(errno = bb....bb)

aa....aa: Function name

bb....bb: Detailed message

Description: An error occurred in the function (aa....aa).
Action: When a J2EE server is started, if this message outputs and the server stops, write permission might not be there in the log output destination directory. Revise the permissions for the log output destination directory. If the error cannot be resolved even after revising the permissions, contact maintenance personnel.

KDJE40017-E

A memory shortage occurred. (aa....aa)(errno = bb....bb)

aa....aa: Function name

bb....bb: Detailed message

Description: An attempt to secure memory in function (aa....aa) has failed.
Action: Increase the free memory, and then re-execute the command.

KDJE40018-E

aa....aa was not found. (errno = bb....bb)

aa....aa: Shared library name

bb....bb: Detailed message

Description: The shared library (aa....aa) was not found.
Action: Confirm that the shared library is installed.

KDJE40019-E

The library of Java(TM) VM cannot be loaded. (errno = aa....aa)

aa....aa: Details

Description: The library of Java VM cannot be read.
Action: Revise the access permissions of the shared library.

KDJE40020-W

An invalid value was specified for the jvm.type key of the usrconf.cfg. aa....aa will be used.

aa....aa: Java VM(Java HotSpot Server VM or Java HotSpot Client VM) used during server startup.

Description: The user-specified Java VM type was invalid, therefore, the searched and found aa....aa will be used to start the server.
Action: Specify the correct value in jvm.type of usrconf.cfg.

KDJE40021-E

Invalid Java(TM) VM.

Description: The version of Java is not the one presumed by Cosminexus Component Container.
Action: Confirm the Java version.

KDJE40022-E

Initialization error of Java(TM) VM.

Description

An attempt to initialize Java VM has failed.

Action

If Unrecognized VM option option-name message is displayed just before this message, revise the specified value of add.jvm.arg defined in usrconf.cfg of the server.

Note that the Unrecognized VM option message is output only in the standard error output.

If the Unrecognized VM option message is not output immediately before this message, contact maintenance personnel.

KDJE40023-E

An attempt to open aa....aa has failed. (errno = bb....bb)

aa....aa: File name

bb....bb: Detailed message

Description: An attempt to open the file (aa....aa) has failed.
Action: Confirm that the relevant file exists, and then check the access permissions.

KDJE40024-E

The directory cannot be accessed. (aa....aa)

aa....aa: Directory name

Description: The directory (aa....aa) does not exist or the write permission is not available.
Action: Confirm that the directory exists, and then check the access permissions.

KDJE40025-E

The current working directory of the process cannot be changed. (aa....aa)

aa....aa: Directory name

Description: The current working directory cannot be changed to aa....aa.
Action: Confirm that the directory exists, and then check the access permissions.

KDJE40026-I

The deletion of the J2EE server has completed successfully. Server name = aa....aa

aa....aa: Server name

Description: The deletion of the J2EE server (aa....aa) was completed successfully.

KDJE40027-I

Usage: cjsetup [-d serverName | serverName [-compat setupVersionID] | -batch serverName]

Description: This message describes the usage method of the cjsetup command.

KDJE40028-E

The deletion of the J2EE server has failed. Server name = aa....aa, Reason = bb....bb

aa....aa: Server name

bb....bb: Error contents

Description

An attempt to unset up the J2EE server (aa....aa) has failed.

Action

Take action based on the error details.

Server is not found

A non-existing server name is specified.

Deletion of file failed

The file cannot be deleted. Confirm that the file to be deleted is not being accessed or is not a read-only file.

Invalid server name

Invalid server name is specified. Single-byte alphanumeric characters, underscores (_), and hyphens (-) can be used in the server name within the range estimated by referencing the manual uCosminexus Application Server System Setup and Operation Guide. The first character of the server name must be an alphanumeric character.

*****

Take the following actions based on the previously displayed message ID:

In case of KDJE40016-E

Contact the maintenance personnel.
In case of KDJE40035-E

The J2EE server is running.

Stop the J2EE server, and then re-execute the unset up command.

KDJE40029-E

The directory aa....aa was not found.

aa....aa: Directory name

Description: The directory (aa....aa) was not found.
Action: Confirm that the Cosminexus Component Container is installed properly.

KDJE40030-I

Usage: cjdumpsv [serverName]

Description: This message describes the usage method of the cjdumpsv command.

KDJE40031-E

The aa....aa server was not found.

aa....aa: Server type (J2EE: J2EE server or Web container: WEB Container server)

Description: The J2EE server or the Web Container server was not found.
Action: Confirm that the server is running, and then re-execute the command.

KDJE40032-E

The policy file cannot be accessed: aa....aa

aa....aa: Policy file name that cannot be accessed

Description: The policy file (aa....aa) cannot be accessed.
Action: Confirm that the relevant policy file exists, and then check the access permissions.

KDJE40033-E

A timeout has occurred during waiting for the response of the shutdown request from the J2EE server.

Description: There was no response to the shutdown request from the J2EE server.
Action: See the log of the J2EE server, and then resolve the cause of the error.

KDJE40034-E

An error has occurred in the J2EE server.

Description: An error occurred in the J2EE server that had received the shutdown request.
Action: See the log of the J2EE server, and then resolve the cause of the error.

KDJE40035-E

The J2EE server has already been started.

Description

The start request was cancelled because the J2EE server is already running.

Action

Confirm that the J2EE server is running.

When the running J2EE server is started properly, use that server as it is.

When the server is not started properly, restart the server if required.

KDJE40036-E

The J2EE server could not be shutdown. Reason = aa....aa

aa....aa: Details

Description

The J2EE server cannot be shutdown due to the reason described in the details (aa....aa).

Action

Take the following actions based on the details:

The server shutdown is in progress.: The J2EE server shutdown is in progress. Wait until the server shuts down.
Permission denied.: When the J2EE server is started from the Management Server, stop the J2EE server from the Management Server. When the Management Server is not started from the J2EE server, contact the maintenance personnel.
In cases other than above: Contact the maintenance personnel.

KDJE40037-E

The definition file cannot be accessed: aa....aa

aa....aa: The definition file name that cannot be accessed

Description

The definition file (aa....aa) cannot be accessed.

Action

Confirm that the relevant definition file exists, and then check the access permissions.

In the case of the batch execution command and the batch forced termination command, also check the following:

When the environment variable CJBATCHUSRCONFDIR for the directory, that stores the user definition file, is specified, make sure that the total value of the length of the specified path and the length of the user property file name (usrconf.properties) is lesser than the maximum path length stipulated in the operating system.

When the environment variable CJBATCHUSRCONFDIR for the directory, that stores the user definition, file is not specified, make sure that the length of the absolute path of the user option definition file (usrconf.cfg) or the user property file (usrconf.properties) that exists in the current directory is lesser than the maximum path length stipulated in the operating system.

KDJE40038-W

An invalid value was specified for aa....aa. The default value bb....bb will be used. (cc....cc = dd....dd)

aa....aa: Specified item (property or option)

bb....bb: Property or default value of the command option

cc....cc: Specification destination

Property key: Property key name

Option name: Command option name

dd....dd: Property key name or command option name

Description

An invalid value was specified for the property or command option, therefore, the processing continues with the default value.

Action

When the specified item is property, revise the specified value of the property (dd....dd) of the usrconf.cfg file.

When the specified item is option, revise the specified value of the option (dd....dd) of the command.

KDJE40039-I

Usage: cjenvsetup

Description: This message describes the usage method of the cjenvsetup command.

KDJE40040-I

The setup for the Cosminexus Component Container administrator has finished successfully.

Description: The setup for the Cosminexus Component Container administrator has finished successfully.

KDJE40041-E

The setup for the Cosminexus Component Container administrator has failed. Error = aa....aa (detail = bb....bb)

aa....aa: Error contents

bb....bb: Detail (file name or directory name)

Description

An attempt to setup the Cosminexus Component Container administrator has failed.

Action

Take action based on the error details.

Invalid installation directory: The Cosminexus Component Container might not be installed properly. Install the Cosminexus Component Container, and then perform the set up process again.
Renaming or deleting the output files failed: The output file of the cjenvsetup command is being used, and therefore the execution information cannot be saved successfully. Check that the file shown in the detail is not being used.
In cases other than above: Execute the cjenvsetup command after some time. If the error occurs again, contact the maintenance personnel.

KDJE40042-E

Only the Cosminexus Component Container administrator is permitted to execute this command.

Description: Only the Cosminexus Component Container administrator can execute this command.
Action: The Cosminexus Component Container administrator must execute this command. Make sure that the property (owner or group) of the installation directory (the link destination directory when /opt/Cosminexus/CC is linked symbolically) matches the Cosminexus Component Container Administrator and the primary group of the Cosminexus Component Container Administrator. If not, match the property.

KDJE40043-W

The library of HNTRLib2 cannot be loaded. (errno = aa....aa)

aa....aa: Details

Description

The Hitachi Trace Common Library cannot be read.

The command processing continues without acquiring the trace.

Action

Confirm that the Hitachi Trace Common Library is installed.

KDJE40044-E

The value specified for the environment variable is invalid. Environment variable name = aa....aa, Value = bb....bb

aa....aa: Environment variable name

bb....bb: Set value of the environment variable

Description

The value specified for the environment variable is invalid.

Action

When the environment variable name is CSCCFJ_SERVER_HOME, confirm that the installation directory of the Component Container is correct.

When the environment variable name is other than the name mentioned above, contact the maintenance personnel.

KDJE40045-I

Usage: cjgetsysinfo [-f SystemInformationOutputFile]

Description: This message describes the usage method of the cjgetsysinfo.

KDJE40046-E

The specified file aa....aa already exists. Specify another file.

aa....aa: Operation status output file path

Description: The specified file already exists.
Action: Specify another file, and then re-execute the command.

KDJE40047-E

An attempt to aa....aa a core file has failed. Core file name = bb....bb

aa....aa: Process contents

rename: Failed to rename.

delete: Failed to delete.

bb....bb: The name of the core file that cannot be renamed or deleted

Description

An attempt to rename or delete the core file has failed.

Action

Take action based on the process contents (aa....aa).

rename: The core file will be overwritten and deleted during next server shutdown. Save the core file by renaming it.
delete: Delete the core file.

KDJE40048-I

Specified option(s) = aa....aa

aa....aa: Specified option list

Description

The options specified for cjstartsv are displayed in aa....aa.

When the option is not specified, none is output.

KDJE40049-E

A timeout occurred in cjstopsv during normal stop monitor. Server name = aa....aa

aa....aa: The J2EE server name

Description: A timeout occurred during normal termination monitoring.
Action: Specify the forced termination option, and then re-execute the cjstopsv command.

KDJE40050-E

A timeout occurred in cjstopsv during normal stop monitor. The J2EE server will now be forcibly stopped. Server name = aa....aa

aa....aa: The J2EE server name

Description: A timeout occurred while monitoring the normal termination. The J2EE server will be forcibly stopped.
Action: No action is required.

KDJE40051-W

An invalid value was specified for the property. The default value aa....aa will be used. (property name = bb....bb)

aa....aa: Default value

bb....bb: Property name

Description: An invalid value was specified in the property. The default value will be used.
Action: Reset the property value, if necessary.

KDJE40052-E

The directory aa....aa cannot be accessed. Processing will now stop.

aa....aa: Directory name

Description

One of the following problems might have occurred:

The permission is not available to access the directory.
A file name is specified for the directory.
Exclusive processing of the following log files has failed:

- Operation log of the cjclstartap command

- Startup process standard output information

- Startup process standard error information

Action

Check the status of the directory aa....aa.

When concurrently starting multiple cjclstartap commands in subdirectory shared mode, if the KDJE40016-E (errno is 22), KDJE30043-E, or KDJE40052-E message is output to the standard error output, exclusive processing of the preceding log files might have failed during initialization. In this case, use ejb.client.log.lockRetryCount and ejb.client.log.lockInterval to increase the total retry count, retry interval, and timeout period for lock acquisition.

KDJE40053-I

The cjclstartap command will now start. (directory for the user definition file = aa....aa, PID = bb....bb)

aa....aa: Environment variable settings for storing the user definition file

bb....bb: Process ID

Description: The cjclstartap command will now start using the user definition of aa....aa directory.

KDJE40054-I

The cjclstartap command stopped. (PID = aa....aa, exit status = bb....bb)

aa....aa: Process ID

bb....bb: Exit status of the Java application

Description: The cjclstartap command was stopped.

KDJE40055-I

Usage: cjclstartap [Java option ...] class [args ...]

Description: This message describes the usage method of the cjclstartap command.

KDJE40056-E

An invalid value was specified for aa....aa. (bb....bb = cc....cc)

aa....aa: Specified item (either property or option)

bb....bb: Specification destination of the invalid value (either one of the Property keys (property key name) or Option name (command option name)

cc....cc: Property key name or command option name for which an invalid value is specified

Description

This process will be terminated because the values specified in the property or command options are invalid.

Action

When the specified item is property, revise the specified value of the property (cc....cc) of the usrconf.cfg file.

When the specified item is option, revise the specified value of the option (cc....cc) of the command.

KDJE40057-E

The cjclstartap process cannot be found. (PID = aa....aa)

aa....aa: Process ID

Description: The cjclstartap command corresponding to the process ID specified in the argument is not found.
Action: Check the process ID of the cjclstartap command. Use the verified process ID to re-execute the cjcldumpap command.

KDJE40058-I

Usage: cjcldumpap [PID]

Description: This message describes the usage method of the cjcldumpap command.

KDJE40059-W

The length of the directory name specified for the ejb.client.log.directory exceeds 180 bytes. The default value aa....aa will be used.

aa....aa: Default directory name

Description: The length of the directory name specified for ejb.client.log.directory exceeds 180 bytes. The default value (aa....aa) will be used.
Action: Revise the value of ejb.client.log.directory.

KDJE40060-E

Another process is now running in the same current directory. (directory = aa....aa)

aa....aa: Current directory of the cjclstartap command

Description: Cannot start up because another cjclstartap command is running in the same current directory.
Action: After the running cjclstartap command finishes, re-execute the command.

KDJE40061-E

The log directory is being used by another process. (directory = aa....aa)

aa....aa: Log output destination directory

Description: Cannot start up because another cjclstartap command is using the log output destination directory.
Action: Specify a different log output destination directory for each application.

KDJE40062-E

An error has occurred in the system call(name = aa....aa,errno = bb....bb,line = cc....cc,at = dd....dd).

aa....aa: System call name

bb....bb: Error code

cc....cc: Number of lines

dd....dd: Functionality in which an error has occurred

Description: aa....aa detected the error bb....bb in dd....dd.
Action: Contact the maintenance personnel.

KDJE40063-E

The cjclstartap command has not started, or has not been executed in the same current directory.

Description: The execution of the command will be terminated because the cjclstartap command is not executed in the same current directory.
Action: Make sure that the cjclstartap command is running, and then re-execute the command in the same current directory as the cjclstartap command.

KDJE40064-E

The command cannot be executed because you do not have administrator privileges.

Description: The command cannot be executed because you do not have administrator privileges.
Action: Re-execute the command on a command prompt, as an administrator.

KDJE40065-E

An error occurred while the permissions were being checked.

Description: An error occurred while the permissions were being checked.
Action: The memory might be insufficient. Increase the free memory, and then re-execute the command. If the problem is not resolved, contact the maintenance personnel.

KDJE40066-W

An attempt to initialize the audit log has failed. (details = aa....aa)

aa....aa: Details

Description: An attempt to initialize the audit log has failed. The audit log cannot be output, but the processing continues.
Action: See the message log of the audit log to remove the cause of the error.

KDJE40067-W

An attempt to output the audit log has failed. (aa....aa)(details = bb....bb, errno = cc....cc)

aa....aa: Audit log type

bb....bb: Details

cc....cc: Error code

Description: An attempt to output the audit log has failed. The processing continues.
Action: See the message log of the audit log to remove the cause of the error. If the problem is not resolved, contact maintenance personnel.

KDJE40068-W

A memory shortage occurred. (details = aa....aa, errno = bb....bb)

aa....aa: Details

bb....bb: Error code

Description: An attempt to allocate memory has failed. The audit log cannot be output, but the processing continues.
Action: Increase the size of the free memory.

KDJE40069-W

The library cannot be loaded. (path = aa....aa).

aa....aa: Path name (absolute path)

Description: The library could not be read. The processing continues.
Action: Make sure that the library exists in the path.

KDJE40070-W

An error has occurred in the system call. (name = aa....aa, details = bb....bb, errno = cc....cc).

aa....aa: System call name

bb....bb: Detailed message

cc....cc: Error code

Description: aa....aa detected the error cc....cc. The processing continues.
Action: Contact the maintenance personnel.

KDJE40074-I

Setup of the Cosminexus Component Container administrator started. (installation directory = aa....aa, UID = bb....bb, GID = cc....cc)

aa....aa: Installation directory

bb....bb: User ID

cc....cc: Group ID

Description: The setup of the Cosminexus Component Container administrator has started.

KDJE40075-E

The value specified in "-compat" option is invalid. (specifiable value = aa....aa)

aa....aa: Specifiable setup version identifier

Description

A setup version identifier outside the specifiable range is specified for the -compat option.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE40076-E

An error has occurred during exporting the version information file.

Description: An error related to output of the version information file occurred.
Action: Take action according to the message output immediately before this message.

KDJE40077-E

The version information file is invalid.

Description: An attempt to output the version information file failed.
Action: The version information file is invalid. Run the J2EE server deletion command, and then re-construct the J2EE server. If the problem is not resolved, contact maintenance personnel.

KDJE41000-E

An attempt to connect to the web container has failed. (errno = aa....aa, addr = bb....bb, port = cc....cc, fds = dd....dd)

aa....aa: System-specific error number

bb....bb: IP address of the host on which the Web container (used in the communication with the Web server) is running

cc....cc: Port number of the Web container used in the communication with the Web server

dd....dd: File descriptor of the Web container used in the communication with the Web server

Description

An attempt to connect to the web container has failed.

Action

One of the following problems occurred.

Port number of the worker is invalid.
Host name or IP address of the worker is invalid.
The maximum value of the Listen queue of the Web container is exceeded.
Host on which the Web container is running is down.
A failure occurred in the communication route between the redirector and Web container.
The Web server has stopped.

Remove the cause based on the system-specific error number.

If KDJE41033-I message is displayed after this message, retry connecting to the Web container.

KDJE41001-E

Redirection to the worker failed. (worker name = aa....aa)

aa....aa: Worker name

Description: A failure occurred in the communication with the worker (aa....aa).
Action: The Web server might be stopped. Take action based on the message (KDJE41000-E and so on) displayed just before this message.

KDJE41002-E

The request could not be redirected to a worker. Because the redirector could not access the definition file. (definition file = aa....aa)

aa....aa: File name

Description: The request cannot be redirected to a worker because the redirector cannot access the definition file (aa....aa).
Action: Confirm that the relevant file exists, check the access permissions, and then restart the Web server.

KDJE41003-W

An invalid parameter value is specified in aa....aa file. The default parameter value will be used. (bb....bb = cc....cc, default value = dd....dd)

aa....aa: File name

bb....bb: Parameter name

cc....cc: Value

dd....dd: Default value

Description: The value specified in parameter (bb....bb) is invalid. The default value (dd....dd) will be used.
Action: When changing the default value of the parameter bb....bb of the file aa....aa, specify an appropriate value in the parameter bb....bb, and then restart the Web server.

KDJE41004-E

The request could not be redirected to a worker because request header was too long.

Description

The redirector cannot redirect the HTTP request to a worker because the request header was too long.

The reason might be because of the GET method was used instead of the POST method in those places where the POST method of HTTP was required.

Action

Remove the cause due to which the size of the HTTP request header information is too long and access again.

KDJE41005-E

The request could not be redirected to a worker because worker name which is specified in the mapping definition file was not defined to worker.list parameter in the workers definition file. (worker name = aa....aa)

aa....aa: Worker name

Description: The request cannot be redirected to a worker because the worker name, specified in the mapping definition file, was not defined in worker.list parameter of the worker definition file.
Action: Define the worker name (aa....aa) specified in the mapping definition file (default name: uriworkermap.properties) or the Redirector Operation definition file for Cosminexus HTTP Server (default name: mod_jk.conf) in the worker.list parameter of the worker definition file (default name: workers.properties), and then restart the Web server. Note that this message is output even when an invalid value is specified in the worker.list parameter. Check the value specified in the worker.list parameter.

KDJE41006-E

The request could not be redirected to a worker because a required parameter was not specified in the workers definition file. (parameter = worker.aa....aa.bb....bb)

aa....aa: Worker name

bb....bb: Parameter name

Description: The request cannot be redirected to a worker because a mandatory parameter (worker.aa....aa.bb....bb) was not specified in the workers definition file.
Action: Specify the parameter worker.aa....aa.bb....bb in the workers definition file (default name: workers.properties), and then restart the Web server.

KDJE41007-E

The request could not be redirected to a worker because invalid value was specified in the workers definition file. (worker.aa....aa.bb....bb = cc....cc)

aa....aa: Worker name

bb....bb: Parameter name

cc....cc: Value

Description: The redirector cannot redirect the request to a worker because invalid parameter value (worker.aa....aa.bb....bb) was specified in the workers definition file.
Action: Specify an appropriate value in the parameter (worker.aa....aa.bb....bb) of the workers definition file (default name: workers.properties), and then restart the Web server.

KDJE41008-W

An invalid parameter value is specified in the workers definition file. The default parameter value will be used. (worker.aa....aa.bb....bb = cc....cc, default value = dd....dd)

aa....aa: Worker name

bb....bb: Parameter name

cc....cc: Value

dd....dd: Default value

Description: An invalid parameter (worker.aa....aa.bb....bb) value is specified in the workers definition file. The default value (cc....cc) will be used.
Action: When changing the default value of the parameter (worker.aa....aa.bb....bb) of the workers definition file (default name: workers.properties), specify an appropriate value in the worker.aa....aa.bb....bb parameter, and then restart the Web server.

KDJE41009-E

Could not create worker because it is out of memory.

Description

The worker cannot be created because the memory was insufficient.

The cause of the error could be that the value specified in the parameter (worker.worker-name.cachesize) of the workers definition file might be too large.

The value of worker.worker-name.cachesize consumes the memory as per the following formula:

Memory-usage = (value-of-worker.worker-name.cachesize) x 10 kilobytes

Action

Secure the memory available to the system, and then restart the Web server.

KDJE41010-E

An attempt to connect to a web client has failed. (errno = aa....aa)

aa....aa: System-specific error number

Description

An attempt to connect to the client that has made a request has failed.

The request processing might have been interrupted in the browser, or an update might have been requested, or else, the client that made the request might have stopped during the communication. The data might not have been received while receiving requests from the client, and a timeout might have occurred.

Action

Remove the cause based on the system-specific error number (definition value of errno.h in UNIX, return value of the GetLastError method in Windows).

If this message is output as a result of a browser operation (interruption or update), no action is required.

If this message occurred because of a timeout, check the cause of the timeout, and revise the specified value of the time as required.

KDJE41012-E

A URI pattern that does not start with '/' was specified in the aa....aa file. This parameter is ignored. (URI pattern = bb....bb, worker name = cc....cc)

aa....aa: File name

bb....bb: uri pattern

cc....cc: Worker name

Description: An uri pattern specified in the definition file (aa....aa) must start with /. The parameter definition will be ignored.
Action: To enable the specified uri pattern and the worker name, prepend / to the uri pattern (bb....bb) of the worker name (cc....cc) specified in file (aa....aa), and then restart the Web server.

KDJE41015-I

The redirector redirected the request to the worker. (worker name = aa....aa, request URI = bb....bb, addr = cc....cc, port = dd....dd, fds = ee....ee)

aa....aa: Worker name

bb....bb: Request URI

cc....cc: IP address of the host on which the Web container (used in the communication with the Web server) is running

dd....dd: Port number of the Web container used in the communication with the Web server

ee....ee: File descriptor of the Web container used in the communication with the Web server

Description: The redirector redirected the request to the worker (aa....aa).

KDJE41016-E

The request could not be redirected because it is out of memory.

Description: The request cannot be redirected because memory was insufficient.
Action: Secure the memory available to the system, and then restart the Web server.

KDJE41017-E

The accessed request was refused. The request URI which starts with "/hitachi_ccfj/" cannot be used. (request URI = aa....aa)

aa....aa: Request URI

Description

The accessed request was denied. The request URI which starts with /hitachi_ccfj/ cannot be used.

An invalid request URI was received or the redirector was registered in duplicate in the Web server.

Action

When the request URI from the client differs from the request URI indicated in aa....aa, start the Internet Service Manager from the Internet Information Services displayed in the tree, choose * host-name. In the * host-name, right click the Default Web site to choose Properties.

Choose the ISAPI filter tag and confirm that the hitachi_ccfj is not registered.

KDJE41018-E

The request could not be redirected because the web server was not configured correctly.

Description

The redirector cannot redirect the request because the web server was not configured correctly.

The reason might be because of the internal information of the redirector is conflicting with the other registered ISAPI filters.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE41019-E

The response timeout happen to worker aa....aa. (uri = bb....bb, addr =cc....cc, port = dd....dd, fds = ee....ee, RootAp = ff....ff)

aa....aa: Worker name

bb....bb: Request URI

cc....cc: IP address of the host on which the Web container (used in the communication with the Web server) is running

dd....dd: Port number of the Web container used in the communication with the Web server

ee....ee: File descriptor of the Web container used in the communication with the Web server

ff....ff: Root AP information of PRF

Description

A timeout occurred while receiving the response from the worker.

Action

One of the following problems occurred. Take action against the cause of the corresponding problem.

For details on how to take the action, see 6.5.2 Troubleshooting when a response is delayed in the uCosminexus Application Server Maintenance and Migration Guide.

Response is not returned due to the infinite loop in the processing of servlets or JSPs.
Deadlock occurred in the Web application.
The server processing lags behind during the peak access time.
Host on which the Web container is running is down.
A failure occurred in the communication route between the redirector and the Web container.

KDJE41020-E

An error occurred in the aa....aa function. (bb....bb)

aa....aa: Function name

bb....bb: Error information

Cause: An unexpected error occurred.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE41021-I

The creating of error page is delegated to web server. (error status code = aa....aa, uri = bb....bb)

aa....aa: Error status code

bb....bb: Request URI

Description: The creation of the error page is delegated to the Web server.

KDJE41022-W

The performance trace is unavailable due to failure of initialization. (reason = aa....aa)

aa....aa: Reason code

Description

The PRF trace cannot be used due to failure in initialization.

Action

Take action based on the reason described in aa....aa. The following codes are displayed in aa....aa.

Table 7‒5: List of failure reason codes displayed in KDJE41022-W
Reason code	Cause	Action
-1	Either the environment variable `PRFSPOOL` is not set, or the directory set in the environment variable `PRFSPOOL` does not exist.	Confirm that the environment variable `PRFSPOOL` is set.
-2	An error occurred in the service start processing of the PRF demon present in the process.	The PRF demon might not be invoked. Confirm that the PRF demon is invoked. Also, check the PRFID of the definition file.
-3	An error (such as system call error) occurred in the service start processing of the PRF demon present in the process.	See the log file present below `setup-directory-of-environment-variable-PRFSPOOL\log\PRF-identifier` (in Windows) or `$PRFSPOOL/log/PRF-identifier` (in UNIX), check the Cosminexus Performance Tracer message, and then take action based on the cause.
-4	An attempt to load the library required for the service of PRF demon has failed.	Cosminexus Performance Tracer is not installed. Reload the library after installing the Cosminexus Performance Tracer.

KDJE41023-E

The request header is invalid. An attempt to redirect a request has failed. (header name = aa....aa, header value = bb....bb)

aa....aa: Header name

bb....bb: Contents

Description: An HTTP request header is invalid. An attempt to redirect a request has failed.
Action: Remove the cause due to which the HTTP request header information is invalid from the client that has made a request and access again.

KDJE41024-E

The redirector is unavailable because the invalid value is specified in aa....aa file. (parameter = bb....bb, value = cc....cc)

aa....aa: File name

bb....bb: Parameter name

cc....cc: Value

Description: The redirector is unavailable because the invalid value (cc....cc) of the parameter (bb....bb) is specified in the file (aa....aa).
Action: Specify an appropriate value in the parameter of the file, and then restart the Web server.

KDJE41025-E

The redirector is unavailable because the required parameter is not specified in aa....aa file. (parameter = bb....bb)

aa....aa: File name

bb....bb: Parameter name

Description: The redirector is unavailable because the mandatory parameter is not specified in the file (aa....aa).
Action: Specify an appropriate value in the parameter of the file, and then restart the Web server.

KDJE41026-W

The trace log is not outputted because the specified trace log file cannot be accessed. (trace log file = aa....aa, api = bb....bb, reason = cc....cc, code = dd....dd)

aa....aa: Output destination

bb....bb: Maintenance information

cc....cc: Maintenance information

dd....dd: Maintenance information

Description: The maintenance trace log is not output because the output destination (aa....aa) of trace log for maintenance cannot be accessed.
Action: Check the output destination directory, access permissions of the file, and free disk space. Remove the cause due to which the log cannot be output, and then restart the Web server.

KDJE41027-E

The redirector is unavailable because the specified trace log file is being used as a message log file. (trace log file = aa....aa)

aa....aa: Output destination

Description: The redirector is unavailable because the output destination (aa....aa) of the maintenance trace log is already used as the output destination of the message log.
Action: Change the contents of the output destination, and then restart the Web server.

KDJE41028-W

The specified parameter is invalid. Delete the entry or make it comment. (parameter = aa....aa)

aa....aa: Parameter name

Description: The description contents are ignored since the specified parameter is invalid.
Action: Delete the description of the parameter or comment it, and then restart the Web server.

KDJE41029-I

The initialization of the trace log will now start. (trace log file = aa....aa)

aa....aa: Output destination of maintenance trace log

Description: The initialization of the maintenance trace log will start.

KDJE41030-I

The initialization of the trace log has finished.

Description: The initialization of the maintenance trace log has finished.

KDJE41031-W

The timeout occurred in connecting to the worker. (worker name = aa....aa, URI = bb....bb, addr = cc....cc, port = dd....dd, fds = ee....ee, RootAP = ff....ff)

aa....aa: Worker name

bb....bb: Request URI

cc....cc: IP address of the host on which the Web container (used in the communication with the Web server) is running

dd....dd: Port number of the Web container used in the communication with the Web server

ee....ee: File descriptor of the Web container used in the communication with the Web server

ff....ff: Root AP information of PRF

Description

A timeout occurred while establishing the connection with the worker.

Action

One of the following problems occurred.

Host on which the Web container is running is down.
A failure occurred in the communication route between the redirector and Web container.

If KDJE41033-I message is displayed after this message, retry connecting to the Web container.

KDJE41032-W

The timeout occurred in sending the request data to the worker. (worker name = aa....aa, URI = bb....bb, addr = cc....cc, port = dd....dd, fds = ee....ee, RootAP = ff....ff)

aa....aa: Worker name

bb....bb: Request URI

cc....cc: IP address of the host on which the Web container (used in the communication with the Web server) is running

dd....dd: Port number of the Web container used in the communication with the Web server

ee....ee: File descriptor of the Web container used in the communication with the Web server

ff....ff: Root AP information of PRF

Description

A timeout occurred in sending the request data to the worker.

Action

One of the following problems occurred.

Host on which the Web container is running is down.
A failure occurred in the communication route between the redirector and Web container.

If KDJE41033-I message is displayed after this message, retry connecting to the Web container.

KDJE41033-I

The request sending will retry.

Description: Retry will be performed because an attempt to send a request to the worker, based on the cause described in the message output before this message, has failed.

KDJE41034-I

An attempt to send the request was successful while retrying. (retry count = aa....aa, maximum retry count = bb....bb)

aa....aa: Count of retry count when the requests were successfully sent

bb....bb: Maximum retry count

Description: An attempt to send the request was successful while retrying.

KDJE41035-E

Retry could not continue because an error occurred. (retry count = aa....aa, maximum retry count = bb....bb)

aa....aa: Count of retry when retry cannot be continued due to an error

bb....bb: Maximum retry count

Description: Retry cannot continue when retrying to send a request to the Web container because an error occurred.
Action: Take action based on the message that describes the cause of the failure to send the requests, output before this message.

KDJE41036-E

It did retry for the maximum retry count, but the request could not be sent. (maximum retry count = aa....aa)

aa....aa: Maximum retry count

Description: An attempt was made to retry sending the requests for the maximum retry count but the requests cannot be sent.
Action: Take action based on the message that describes the cause of the failure to send the requests, output before this message.

KDJE41037-I

The redirector will redirect the POST requests that have the Content-Length header, to the worker defined in the worker.<post_size_lb worker name>.post_size_workers parameter in the worker definition file. (post_size_lb worker name = aa....aa, destination worker name = bb....bb, length = cc....cc-dd....dd)

aa....aa: Worker name of the POST request distribution worker

bb....bb: Worker name of the POST request transfer destination worker

cc....cc: Minimum value of the Content-Length header

dd....dd: Maximum value of the Content-Length header

Description: Using the distribution functionality based on the POST data size, transfer the POST requests with the Content-Length header value more than cc....cc and lesser than dd....dd to the worker bb....bb specified in the parameter worker.worker-name-of-the-POST-request-distribution-worker.post_size_workers of the worker definition file.

KDJE41038-I

The redirector will redirect, to the default worker, the requests that do not satisfy the conditions for redirecting to the worker defined in the worker.<post_size_lb worker name>.post_size_workers parameter in the worker definition file. (post_size_lb worker name = aa....aa, default worker name = bb....bb)

aa....aa: Worker name of the POST request distribution worker

bb....bb: Worker name of the default worker

Description: Using the distribution functionality based on the POST data size, transfer the requests that do not satisfy the conditions for distribution to the worker specified in the parameter worker.worker-name-of-the-POST-request-distribution-worker.post_size_workers of the worker definition file to the default worker bb....bb.

KDJE41039-E

The redirector cannot be used because an invalid worker type is specified in the worker definition file. (worker.aa....aa.type = bb....bb)

aa....aa: Worker name

bb....bb: Value

Description: The redirector cannot be used because the type of the worker specified in the worker definition file is invalid. The type of the worker specified as the request transfer destination in the POST request distribution worker is either ajp13 or ajp12.
Action: Specify an appropriate value in the parameter (worker.worker-name.type) of the workers definition file (default name: workers.properties), and then restart the Web server.

KDJE41040-E

The redirector cannot be used because the value specified for the worker.<worker-name>.post_data parameter in the worker definition file has already been defined for another worker. (worker.aa....aa.post_data = bb....bb, other worker = cc....cc)

aa....aa: Worker name of the worker, the value of which is duplicated

bb....bb: Value

cc....cc: Worker name

Description: The redirector cannot be used because the value obtained by adding 1 to the upper-limit value of the Content-Length header of the worker aa....aa specified in the worker definition file is same as the value specified in another worker cc....cc.
Action: Specify the appropriate value in the parameter worker.worker-name.post_data (the worker name is aa....aa) of the worker definition file, and then restart the Web server.

KDJE41041-W

The specified parameter is invalid. (parameter name = aa....aa, value = bb....bb)

aa....aa: Parameter name

bb....bb: Value

Description

The value of the specified parameter is invalid.

If the URL pattern setup during sorting of requests by URL pattern is invalid, urlpattern will be output in aa....aa, and the specified URL pattern will be output in bb....bb.

Action

Specify the appropriate value in the parameter, and then restart the Web server.

KDJE41800-I

The setup for the Web container server has finished successfully. Server name = aa....aa

aa....aa: Server name

Description: The setup for the Web container server (aa....aa) has finished successfully.

KDJE41801-E

The Web container directory aa....aa corresponding to the server name does not exist.

aa....aa: Server name

Description: The directory corresponding to the server name specified by the cjstartweb command and the cjstopweb command does not exist.
Action: Confirm that the server name is entered correctly by the cjstartweb command and the cjstopweb command. When the cjwebsetup command is not executed by the specified server name, set up the server using the cjwebsetup command.

KDJE41802-E

The setup for the Web container server has failed. Server name = aa....aa, Reason = bb....bb

aa....aa: Server name

bb....bb: Error contents

Description

An attempt to setup the Web container server (aa....aa) has failed.

Action

Take action based on the error details.

Already been set up: The Web container server has been set up with the specified server name. To set up the Web container server again, use the cjwebsetup -d server-name command to delete the server once, and then re-execute the set up command.
Invalid server name: Invalid server name is specified. Single-byte alphanumeric characters, underscores (_), and hyphens (-) can be used in the server name within the range estimated by referencing the manual uCosminexus Application Server System Setup and Operation Guide. The first character of the server name must be an alphanumeric character.
In the case of *****: Take action based on the message displayed just before the error.

KDJE41803-E

The definition file aa....aa cannot be accessed.

aa....aa: File name

Description: The definition file (aa....aa) cannot be accessed.
Action: Confirm that the relevant file exists, check the access permissions, and then re-execute the cjstartweb command or the cjstopweb command.

KDJE41804-E

The specified aa....aa is too long: bb....bb

aa....aa: Items with error (path name or server name)

bb....bb: Definition file key name or command name

Description

The specified path name or server name (aa....aa) is too long.

The path name is specified within 256 bytes.

The server name is specified within the range of the maximum length of the host name in the operating OS. Single byte alphanumeric characters, underscores (_), or hyphens (-) can be used. Note that the first character must be an alphanumeric character.

Action

Specify according to the restrictions.

KDJE41805-I

Usage: cjstartweb [serverName] [-security]

Description: This message describes the usage method of the cjstartweb command.

KDJE41806-I

Usage: cjstopweb [serverName] [-f | -fd [ThreadDumpInterval ThreadDumpCount]]

Description: This message describes the usage method of the cjstopweb command.

KDJE41807-I

The deletion of the Web container server has completed successfully. Server name = aa....aa

aa....aa: Server name

Description: The deletion of Web container server (aa....aa) has finished successfully.

KDJE41808-I

Usage: cjwebsetup [-d serverName | serverName]

Description: This message describes the usage method of the cjwebsetup command.

KDJE41809-E

The deletion of the Web container server has failed. Server name = aa....aa, Reason = bb....bb

aa....aa: Server name

bb....bb: Error contents

Description

An attempt to unset up the Web container server (aa....aa) has failed.

Action

Take action based on the error details.

Server is not found

A non-existing server name is specified.

Deletion of file failed

The file cannot be deleted. Confirm that the file to be deleted is not being accessed or is not a read-only file.

Invalid server name

Invalid server name is specified. Single-byte alphanumeric characters, underscores (_), and hyphens (-) can be used in the server name within the range estimated by referencing the manual uCosminexus Application Server System Setup and Operation Guide. The first character of the server name must be an alphanumeric character.

*****

Take the following actions based on the previously displayed message ID:

In case of KDJE40016-E

Contact the maintenance personnel.
In case of KDJE41813-E

The Web container server is running.

Stop the Web container server, and then re-execute the deletion command.

KDJE41810-E

The directory aa....aa was not found.

aa....aa: Directory name

Description: The directory (aa....aa) was not found.
Action: Confirm that the Cosminexus Component Container is installed properly.

KDJE41811-I

Usage: cjdumpweb [serverName]

Description: This message describes the usage method of the cjdumpweb command.

KDJE41813-E

The Web container server has already been started.

Description

The start request is cancelled because the Web container server is already running.

Action

Confirm that the Web container server is running.

If the Web container server is started properly, use that server as it is.

When the server is not started properly, restart the server if required.

KDJE41814-E

The Web container server is not found.

Description: The Web container server is not found.
Action: Confirm that the Web container server is running, and then re-execute the command.

KDJE42000-E

Deployment has abended. An invalid environment entry was found. Values could not converted to the specified types (aa....aa).

aa....aa: Target

Description

The deployment process has abended.

An invalid environment entry (aa....aa) was found. Values cannot be converted to the specified types.

Action

Revise the <env-entry> tag, and then set the appropriate contents.

KDJE42001-E

Deployment has abended. Resources (aa....aa) are unresolved.

aa....aa: Target

Description

The deployment process has abended.

The deployment process failed because the link for resource reference (aa....aa) cannot be resolved.

Action

Use the server management commands to resolve the links for the relevant application resources.

KDJE42002-E

Deployment has abended. EJBs (aa....aa) are unresolved.

aa....aa: Target

Description

The deployment process has abended.

The deployment process failed because the link for the EJB (aa....aa) reference cannot be resolved.

Action

Resolve the links of the EJBs of corresponding application.

When the settings of the property file are invalid: Set up appropriate contents in the <ejb-ref> tag or the <ejb-local-ref> tag of the property file.
When the settings of the Deployment Descriptor are invalid: Revise the <ejb-ref> tag or the <ejb-local-ref> tag of Deployment Descriptor, and set up the appropriate contents.

KDJE42004-E

Deployment has abended. Roles in the security constraint (aa....aa) are unresolved.

aa....aa: Target

Description

The deployment process has abended.

The reference definition of roles is unresolved.

Action

Use the server management commands to resolve the link for the relevant application roles.

KDJE42005-E

This EAR has an invalid context root (aa....aa). It may contain an invalid character such as "*".

aa....aa: Context root name

Description

This EAR has an invalid context root (aa....aa).

This might contain an invalid character such as "*".

Characters that can be specified in the Context Root

Alphanumeric characters and the symbols shown below

/ @ & + $ , - _ . ! ' ( ) % ~

However, the characters must be specified based on the following rules:

/ is valid only as the delimiter of the path and character such as // cannot be specified.
cannot be used to express relative path (such as ./).
% can only be used as escape (such as %20).

Action

Revise with appropriate characters.

KDJE42006-E

Exception while generating remote interface implementation for bean aa....aa. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description: An exception occurred while generating the remote interface implementation class for Bean (aa....aa).
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42007-E

Exception while generating home interface implementation for bean aa....aa. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description: An exception occurred while generating the home interface implementation class for Bean (aa....aa).
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42008-E

Error generating aa....aa stubs for bean interface bb....bb. Reason=cc....cc

aa....aa: Stub type

bb....bb: J2EE application name

cc....cc: Cause of the error

Description: An error occurred while generating aa....aa stubs for Bean interface (bb....bb).
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42009-E

Error compiling container generated java source files Detail=aa....aa

aa....aa: Details

Description

An error occurred while compiling the generated java source files.

Action

Reference the details, and then take action.

Take action based on the following cases:

If another error message is output: Reference the output message, and then take action.
If Generics is used in definitions of the Home/ Component interface: Do not use Generics in the definitions of the Home Component interface.
If Generics is used in definitions of the business interface: Set up the type variable as a parameter of the business interface.
If the method of the parameter in the business interface is redefined: Delete the redefined method.

If the cause is not known, collect the maintenance information, and then contact maintenance personnel.

KDJE42010-E

The native library file (aa....aa) and a native library file with the same name as the resource adapter "bb....bb" are already deployed, so importing or adding is not possible.

aa....aa: Native library file name

bb....bb: Resource adapter display name

Description: The native library file with the same name as the native library file (aa....aa) of resource adapter (bb....bb) is already deployed, therefore, importing or adding is not possible.
Action: Delete the resource adapter that is using the already existing native library file, and then import or add again.

KDJE42011-E

This file (aa....aa) and a file with the same name exist in the J2EE application, so importing is not possible.

aa....aa: File name

Description: This file (aa....aa) and a file with the same name exist in the J2EE application, so importing is not possible.
Action: Change the name of the library JAR file to be imported or delete the already existing file with the same name, and then re-import.

KDJE42012-E

Deployment has abended. An attempt to read the runtime deployment descriptor in the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description: The deployment process has abended. An attempt to read the runtime deployment descriptor in the J2EE application (aa....aa) has failed.
Action: For the messages in which the exception information starts with nnnn (n is a number), see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42014-E

Deployment has abended. An attempt to create the configuration for the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description: The deployment process has abended. An attempt to create the configuration information for the J2EE application (aa....aa) has failed.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42018-E

Deployment has abended. An attempt to check unresolved security roles in the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description: The deployment process has abended. An attempt to check the role with unresolved link settings in the J2EE application (aa....aa) has failed.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42019-E

Deployment has abended. An attempt to check unresolved resource references in the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description: The deployment process has abended. An attempt to check the resource reference information with unresolved link settings in the J2EE application (aa....aa) has failed.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42020-E

Deployment has abended. An attempt to check unresolved EJB references in the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description: The deployment process has abended. An attempt to check the EJB references information with unresolved link setting in the J2EE application (aa....aa) has failed.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42021-E

Deployment has abended. An attempt to check invalid environment entries in the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description: The deployment process has abended. An attempt to check invalid environment entries in the J2EE application (aa....aa) has failed.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42022-E

Deployment has abended. An attempt to deploy WARs in the J2EE application "aa....aa" has failed.

aa....aa: J2EE application name

Description: The deployment process has abended. An attempt to deploy WARs in the J2EE application (aa....aa) has failed.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42023-E

Deployment has abended. An attempt to deploy application clients in the J2EE application "aa....aa" has failed.

aa....aa: J2EE application name

Description: The deployment process has abended. An attempt to deploy application clients in the J2EE application (aa....aa) has failed.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42024-E

Deployment has abended. An attempt to generate IIOP stub/classes for the J2EE application "aa....aa" has failed.

aa....aa: J2EE application name

Description: The deployment process has abended. An attempt to generate IIOP stub and classes for the J2EE application (aa....aa) has failed.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42025-E

Deployment has abended. An attempt to deploy EJBs in the J2EE application "aa....aa" has failed.

aa....aa: J2EE application name

Description: The deployment process has abended. An attempt to deploy the EJBs in the J2EE application (aa....aa) has failed.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42026-E

Deployment has abended. The deploy component in the J2EE application "aa....aa" could not be found.

aa....aa: J2EE application name

Description: The deployment process has abended. The deploy component in the J2EE application (aa....aa) cannot be found.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42028-E

Deployment has abended. An attempt to clean up the J2EE application "aa....aa" has failed.

aa....aa: J2EE application name

Description: The deployment process has abended. An attempt to clean up the J2EE application (aa....aa) has failed.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42031-E

Deployment has abended. An invalid EJB exists.

Description: The deployment process has abended. An invalid EJB exists.
Action: Confirm that an invalid EJB does not exist. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42034-E

Deployment has abended. An attempt to copy the interface for the EJB "aa....aa" has failed.

aa....aa: EJB name

Description

The deployment process has abended.

An attempt to copy the interface for the EJB (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42035-E

Deployment has abended. An attempt to deploy the EJB "aa....aa" has failed.

aa....aa: EJB name

Description

The deployment process has abended.

An attempt to deploy the EJB (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42039-E

EJB error: aa....aa

aa....aa: Details of the error contents

Description

The error details of EJB are displayed.

Action

Reference the details, and then take action. For details, see 7.9 List of details for KDJE42039-E and KDJE42270-W.

Take action based on the following cases:

If another error message is output: Reference the output message, and then take action.
If Generics is used in definitions of the Home/Component interface: Do not use Generics in the definitions of the Home Component interface.

If the cause is not known, collect the maintenance information, and then contact maintenance personnel.

KDJE42040-I

The deploying environment setup has finished.

Description: The deploying environment setup has finished.

KDJE42041-I

Creation of the configuration for the J2EE application "aa....aa" is in progress.

aa....aa: J2EE application name

Description: The creation of the configuration information for the J2EE application (aa....aa) is in progress.

KDJE42042-I

Loading of the EJB-JAR deployment descriptors in the J2EE application "aa....aa" is in progress.

aa....aa: J2EE application name

Description: Loading of the EJB-JAR deployment descriptors in the J2EE application (aa....aa) is in progress.

KDJE42043-I

Deployment of all the application clients for the J2EE application "aa....aa" is in progress.

aa....aa: J2EE application name

Description: The deployment process of all the application clients for the J2EE application (aa....aa) is in progress.

KDJE42044-I

Generation of the IIOP stubs/classes for the J2EE application "aa....aa" is in progress.

aa....aa: J2EE application name

Description: The generation of the IIOP stubs and classes for the J2EE application (aa....aa) is in progress.

KDJE42046-I

Verification of the EJBs is in progress.

Description: Verification of the EJB contents is in progress.

KDJE42047-I

Verification of the EJB "aa....aa" is in progress.

aa....aa: EJB name

Description: Verification of the EJB (aa....aa) contents is in progress.

KDJE42048-I

The deployment environment will now be set.

Description: The deployment environment will now be set.

KDJE42050-I

Deployment of the EJB "aa....aa" is in progress.

aa....aa: EJB name

Description: The deployment process of the EJB (aa....aa) is in progress.

KDJE42051-I

Exporting of the client files is in progress.

Description: Exporting of the client files is in progress.

KDJE42052-I

Deployment of all the web components for the J2EE Application "aa....aa" is in progress.

aa....aa: J2EE application name

Description: The deployment process of all the web components for the J2EE Application (aa....aa) is in progress.

KDJE42053-I

Redeployment of the J2EE application "aa....aa" is in progress.

aa....aa: J2EE application name

Description: The J2EE application (aa....aa) to be redeployed is displayed.

KDJE42055-E

The native library file (aa....aa) that the resource adapter "bb....bb" has cannot be deleted. Reboot the J2EE server, and then redelete.

aa....aa: Native library file name

bb....bb: Resource adapter display name

Description: The native library file (aa....aa) included in the resource adapter (bb....bb), cannot be deleted.
Action: Reboot the J2EE server, and then re-delete.

KDJE42056-E

The file (hitachi-runtime.jar) with the reserved name cannot be imported.

Description: The file (hitachi-runtime.jar) with the reserved name cannot be imported.
Action: Change the file name, and then re-import.

KDJE42057-E

The connection factory class could not be found from the resource adapter "aa....aa", so importing or adding is not possible.

aa....aa: Resource adapter display name

Description: The connection factory class cannot be found from the resource adapter (aa....aa), therefore, you cannot import or add.
Action: Confirm that the contents of the DD for resource adapter are correct or the connection factory class of the resource adapter exists. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42058-E

Exception while generating local component interface implementation for bean aa....aa. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description: An exception occurred while generating a local interface implementation class for Bean (aa....aa).
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42059-E

Exception while generating local home interface implementation for bean aa....aa. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description: An exception occurred while generating local home interface implementation class for Bean (aa....aa).
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42060-E

Exception while generating cmp entity bean:aa....aa implementation. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description: An exception occurred while generating the CMP Entity Bean implementation class.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42061-E

Exception while generating cmp state object implementation for bean aa....aa. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description: An exception occurred while generating the CMP state object class for Bean (aa....aa).
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42062-E

Exception while generating cmp join object:aa....aa implementation. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description: An exception occurred while generating aa....aa.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42063-E

The JAR file (aa....aa) which the resource adapter "bb....bb" has cannot be deleted. Reboot the J2EE server, and then redelete.

aa....aa: JAR file name

bb....bb: Resource adapter display name

Description: The JAR file (aa....aa) included in the resource adapter (bb....bb), cannot be deleted.
Action: Reboot the J2EE server, and then re-delete.

KDJE42064-E

The WAR DD (aa....aa) has more than one filter with the same name "bb....bb".

aa....aa: WAR DD name

bb....bb: Filter name

Description

The WAR DD (aa....aa) has more than one filter with the same name (bb....bb).

The process of importing will be interrupted.

Action

Investigate the WAR file and change the contents of <filter-name> tag.

KDJE42065-E

The WAR file (aa....aa) has more than one filter with the same name "bb....bb".

aa....aa: WAR file name

bb....bb: Filter name

Description

The WAR file (aa....aa) has more than one filter with the same name (bb....bb).

The process of importing will be interrupted.

Action

Investigate the WAR file and change the contents of <filter-name> tag.

When the cjimportapp command is executed, the WAR file is included in EAR.

KDJE42066-E

The J2EE resource aa....aa could not start in the current J2EE server mode.

aa....aa: J2EE resource name

Description: The J2EE resource (aa....aa) cannot be started in the current J2EE functionality mode.
Action: Confirm that the J2EE functionality mode is correct. If the J2EE functionality mode is correct, delete the J2EE resource, and then re-create it.

KDJE42067-E

The J2EE resource adapter aa....aa could not start in the current J2EE server mode.

aa....aa: J2EE resource adapter name

Description: The J2EE resource adapter (aa....aa) cannot be started in the current J2EE functionality mode.
Action: Confirm that the J2EE functionality mode is correct. When the J2EE functionality mode is to be downgraded and used, reset the environment of the J2EE server.

KDJE42068-E

The extension of the library JAR file (aa....aa) is not ".jar", so importing is not possible.

aa....aa: Library JAR file name

Description: You cannot import because the extension of the library JAR file (aa....aa) is not .jar.
Action: Change the extension to .jar, or add the extension, and then re-import.

KDJE42069-E

Deployment has abended. An attempt to deploy the J2EE application "aa....aa" has failed.

aa....aa: J2EE application name

Description: An attempt to deploy the J2EE application (aa....aa) has failed.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42070-E

The resource adapter "aa....aa" has the native library file, so it cannot be added to the J2EE application.

aa....aa: Resource adapter display name

Description: The resource adapter (aa....aa) cannot be added to the J2EE application because it contains a native library file.
Action: Use the resource adapter that contains a native library file, in a stand-alone deployment.

KDJE42071-E

Deployment has abended. An attempt to check the resource reference in the J2EE application "aa....aa" has failed. Details = bb....bb

aa....aa: J2EE application name

bb....bb: Detailed message

Description

The deployment process has abended.

An attempt to check the resource reference in the J2EE application (aa....aa) has failed.

Action

See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42072-E

The stand-alone resource adapter "aa....aa" has been started once. Reboot the J2EE server, and then redelete.

aa....aa: Resource adapter display name

Description: The stand-alone resource adapter (aa....aa) is started once.
Action: Reboot the J2EE server, and then re-delete.

KDJE42073-E

Deployment has abended. The assembly descriptor (aa....aa) is invalid.

aa....aa: Target

Description: The deployment was abended because the assembly descriptor (aa....aa) is invalid.
Action: Check the values of ejb-name, method-intf, method-name, method-params, trans-attribute of the container-transaction. Also check the values of role-name, ejb-name, method-intf, method-name, method-params of the method-permission.

KDJE42074-E

Deployment has abended. An attempt to check the assembly descriptor in the J2EE Application "aa....aa" has failed. Exception=bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to check the assembly descriptor in the J2EE Application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42075-E

Deployment has abended. An attempt to verify the EJB components in the J2EE Application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to verify the EJB components in the J2EE Application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42076-E

Deployment has abended. A J2EE component unsupported by the current J2EE function mode is included: aa....aa

aa....aa: Details

Description

The deployment process has abended.

A J2EE component that is not supported by the current J2EE functionality mode is included in the J2EE functionality mode.

Action

Confirm that the J2EE functionality mode is correct. When the J2EE functionality mode is to be downgraded and used, reset the environment of the J2EE server.

KDJE42077-E

Deployment has abended. An attempt to verify the J2EE components in the J2EE Application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to verify the J2EE components in the J2EE Application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42078-E

Deployment has abended. The same abstract schema name is specified in Jar (aa....aa).

aa....aa: Target

Description: The deployment was abended because the same abstract-schema-name (aa....aa) is specified in the same JAR.
Action: Make sure that the value of abstract-schema-name is not duplicated in the EJB-JAR file.

KDJE42079-E

Deployment has abended. An attempt to check the abstract schema name in the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to check the abstract-schema-name in the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42080-E

Deployment has abended. The JMS resource used in the application does not support XA (aa....aa).

aa....aa: Target

Description

The deployment process has abended.

The JMS resource (aa....aa) used in the application does not support the XA transactions.

Action

Change the value for the transaction-support of the resource adapter.

KDJE42081-E

Deployment has abended. An attempt to check the transaction type of the JMS resource in the J2EE Application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to check the transaction-support of the JMS resource used in the J2EE Application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42082-E

Deployment has abended. SQL statements have not been generated yet (aa....aa).

aa....aa: Details

Description

The deployment process has abended.

SQL statements for CMP2.x are not generated.

Action

Re-generate the SQL statement for each Entity Bean of the CMP using the server management command (cjgencmpsql).

KDJE42083-E

Deployment has abended. An attempt to check the SQL statements in the J2EE Application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to check the SQL statements used in the Entity Beans of CMP2.x in the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42084-E

Deployment has abended. EJB lookup names are duplicated. Details = aa....aa

aa....aa: Details

Description

The deployment process has abended.

The EJB lookup names are duplicated.

Action

Change the EJB lookup names so that they are not duplicated, and then redeploy.

KDJE42085-E

Deployment has abended. An attempt to check duplicated EJB lookup names in the J2EE Application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to check whether the EJB lookup names in the J2EE Application (aa....aa) are duplicated has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42086-E

Deployment has abended. The CMP EntityBean is not mapped correctly. (aa....aa)

aa....aa: Details

Description

The deployment process has abended.

The CMP Entity Bean is not mapped correctly.

Action

Map the CMP, and then redeploy.

KDJE42087-E

Deployment has abended. An attempt to check the CMP Entity Beans in the J2EE Application "aa....aa" has failed. Details = bb....bb

aa....aa: J2EE application name

bb....bb: Detailed message

Description

The deployment process has abended.

An attempt to check whether the CMP Entity Beans in the J2EE Application (aa....aa) are correctly mapped has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42088-E

Deployment has abended. An attempt to check the connection factory reference in the J2EE Application "aa....aa" has failed. Details = bb....bb

aa....aa: J2EE application name

bb....bb: Detailed message

Description

The deployment process has abended.

An attempt to check the connection factory reference in the J2EE Application (aa....aa) has failed.

Action

See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42089-E

Deployment has abended. An attempt to check the resource environment reference in the J2EE Application "aa....aa" has failed. Details = bb....bb

aa....aa: J2EE application name

bb....bb: Detailed message

Description

The deployment process has abended.

An attempt to check the resource environment reference in the J2EE Application (aa....aa) has failed.

Action

See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42090-E

Deployment has abended. An attempt to check the destination reference in the J2EE application "aa....aa" has failed. Details = bb....bb

aa....aa: J2EE application name

bb....bb: Detailed message

Description

The deployment process has abended.

An attempt to check the destination reference in the J2EE application (aa....aa) has failed.

Action

See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42091-E

An attempt to deploy the J2EE resource adapter aa....aa has failed. (details = bb....bb)

aa....aa: J2EE resource adapter name

bb....bb: Detailed message of the exception

Description: An attempt to deploy the J2EE resource adapter (aa....aa) has failed.
Action: See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42092-E

An attempt to start the J2EE resource adapter aa....aa has failed. (detail=bb....bb)

aa....aa: J2EE resource adapter name

bb....bb: Detailed message of the exception

Description: An attempt to start the J2EE resource adapter (aa....aa) has failed.
Action: See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42093-E

An attempt to stop J2EE resource adapter aa....aa has failed. (detail=bb....bb)

aa....aa: J2EE resource adapter name

bb....bb: Detailed message of the exception

Description: An attempt to stop the J2EE resource adapter (aa....aa) has failed.
Action: See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42094-E

An attempt to un-deploy the J2EE resource adapter aa....aa has failed. (detail=bb....bb)

aa....aa: J2EE resource adapter name

bb....bb: Detailed message of the exception

Description: An attempt to undeploy the J2EE resource adapter (aa....aa) has failed.
Action: See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42095-E

An attempt to deploy the J2EE resource aa....aa has failed. (detail = bb....bb)

aa....aa: J2EE resource name

bb....bb: Detailed message of the exception

Description: An attempt to deploy the J2EE resource (aa....aa) has failed.
Action: See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42096-E

An attempt to start the J2EE resource aa....aa has failed. (detail=bb....bb)

aa....aa: J2EE resource name

bb....bb: Detailed message of the exception

Description: An attempt to start the J2EE resource (aa....aa) has failed.
Action: See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42097-E

An attempt to stop J2EE resource aa....aa has failed. (detail=bb....bb)

aa....aa: J2EE resource name

bb....bb: Detailed message of the exception

Description: An attempt to stop the J2EE resource (aa....aa) has failed.
Action: See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42098-E

An attempt to un-deploy the J2EE resource aa....aa has failed. (detail=bb....bb)

aa....aa: J2EE resource name

bb....bb: Detailed message of the exception

Description: An attempt to undeploy the J2EE resource (aa....aa) has failed.
Action: See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42099-E

An attempt to create the directory (aa....aa) has failed.

aa....aa: Directory name

Description

An attempt to create the directory (aa....aa) has failed.

Action

Confirm that the following conditions are fulfilled. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

If the disk space is insufficient, secure sufficient disk space.
When the path or name of the directory is longer than the length restricted by the OS, specify the following settings so that the length is shortened:

- When the root path of the working directory is long, specify a shallow directory tree by an absolute path in the ejb.public.directory key defined in the user definition file (usrconf.cfg) for the J2EE server.

- When the J2EE server name is long, perform operation in the environment with a short J2EE server name.

- When the name of the J2EE module (for example J2EE application, EJB-JAR, WAR, resource adapter, data source, mail configuration) is long, change it to a short name.

- When the file name to be imported or a value of the <display-name> tag defined by the DD in the file is long, use a shorter name and value.
If access permission is not available, assign the access permission.

KDJE42100-E

An attempt to create the file (aa....aa) has failed.

aa....aa: File name

Description

An attempt to create the file (aa....aa) has failed.

Action

Confirm that the following conditions are fulfilled. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

If the disk space is insufficient, secure sufficient disk space.
When the path or name of the directory is longer than the length restricted by the OS, specify the following settings so that the length is shortened:

- When the root path of the working directory is long, specify a shallow directory tree by an absolute path in the ejb.public.directory key defined in the user definition file (usrconf.cfg) for the J2EE server.

- When the J2EE server name is long, perform operation in the environment with a short J2EE server name.

- When the name of the J2EE module (for example J2EE application, EJB-JAR, WAR, resource adapter, data source, mail configuration) is long, change it to a short name.

- When the file name to be imported or a value of the <display-name> tag defined by the DD in the file is long, use a shorter name and value.
If access permission is not available, assign the access permission.

KDJE42101-I

aa....aa / bb....bb stubs are generated.

aa....aa: Number of generated stubs

bb....bb: Number of stubs to be generated

Description

The stubs of aa....aa interface are generated.

This message is displayed when the stubs are generated in multiple interfaces in case they cannot be generated collectively. The stubs cannot be generated collectively because the arguments in the stub generation command might be too long.

KDJE42102-W

aa....aa command failed. Length of arguments may be too long.(length= bb....bb) The command is executed again with reduced number of interfaces.

aa....aa: Command name

bb....bb: Length of the argument when the command is executed

Description: An attempt to execute the command has failed. Length of the arguments of stub generation command might be too long.
Action: Reduce the number of interfaces to be specified in the arguments, and then re-execute the command.

KDJE42103-E

The specified JDBC driver is not supported by the current J2EE feature. JDBC driver = aa....aa Details = bb....bb

aa....aa: File name[, file name]

bb....bb: Detailed message

Description

The specified JDBC driver is not supported by the operation mode of the current J2EE server mode.

Action

Take the following actions based on the details:

To the basic mode, need to import only JdbcDbpsv.jar.

In the case of basic mode, import only the JdbcDbpsv.jar of the Cosminexus Driver for Java Technology.
To the basic mode, need to import JDBC driver that implements the java.sql.Driver interface.

In the case of basic mode, import the JDBC driver containing the class that implements java.sql.Driver interface.

KDJE42105-E

The runtime deployment descriptor was not found. File path = aa....aa

aa....aa: Absolute path of the file

Description: The runtime deployment descriptor was not found.
Action: Re-create the J2EE application. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42106-E

The directories and files in the allstubs directory could not be deleted. allstubs directory path = aa....aa

aa....aa: Absolute path of allstubs directory

Description

The directories and files in the allstubs directory cannot be deleted.

Action

Confirm the following details, and then take action: If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

When the delete permission is not added in the allstubs directory, add the permission, and restart the J2EE server.
When the allstubs directory is referenced from some other process, restart the J2EE server after that process finishes.

KDJE42107-I

The J2EE application aa....aa will now be deployed and started.

aa....aa: J2EE application name

Description: This message indicates the start process of the J2EE application.

KDJE42108-I

The J2EE application aa....aa started successfully.

aa....aa: J2EE application name

Description: This message indicates that the application has started successfully.

KDJE42109-I

The home interface for aa....aa will now be published.

aa....aa: Home interface name

Description: This message indicates that the home interface will now be published.

KDJE42110-I

The Web component aa....aa will now be started.

aa....aa: WEB component

Description: This message indicates the start of WEB component.

KDJE42111-I

Importing "aa....aa" is in progress.

aa....aa: Target

Description: This message indicates the execution of import processing.

KDJE42112-I

Importing "aa....aa" was successful.

aa....aa: Target

Description: This message indicates that the import processing was successful.

KDJE42113-I

Exporting "aa....aa" is in progress.

aa....aa: Target

Description: This message indicates the execution of export processing.

KDJE42114-I

Sending export information of "aa....aa" was successful.

aa....aa: Target

Description: This message indicates that export processing was successful.

KDJE42115-E

An unexpected exception occurred. Details = aa....aa

aa....aa: Details

Description: An unexpected exception occurred.
Action: See the details, and then take action. For the messages in which the detailed information starts with nnnn (n is a number), see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42116-E

The composition of the file (aa....aa) is invalid. Re-create the J2EE application. If you cannot re-create the J2EE application, contact the system administrator.

aa....aa: File name

Description: The composition of the file (aa....aa) is invalid.
Action: Re-create the J2EE application. If you cannot re-create the J2EE application, contact the maintenance personnel.

KDJE42117-E

The value of the sequential number exceeded the limit. Contact the system administrator.

Description: The value of the sequential number has exceeded the limit.
Action: Contact the maintenance personnel.

KDJE42118-E

An attempt to convert the deployment descriptor file (hitachi-ejb-app.xml) in the file (aa....aa) has failed. Re-create the J2EE application. If you cannot re-create the J2EE application, contact the system administrator. Details = bb....bb

aa....aa: Name of the file with runtime information

bb....bb: Detailed message

Description: An attempt to convert the deployment descriptor in the file (aa....aa) has failed.
Action: Re-create the J2EE application. If you cannot re-create the J2EE application, contact the maintenance personnel.

KDJE42119-E

A J2EE resource adapter with the same name already exists. Display name = aa....aa

aa....aa: Display name

Description: A J2EE resource adapter with the same name already exists.
Action: Change the display name of the J2EE resource adapter, and then re-execute the operation.

KDJE42120-E

The context root "aa....aa" of the WAR file (bb....bb) in the file (cc....cc) is invalid. Re-create the J2EE application. If you cannot re-create the J2EE application, contact the system administrator.

aa....aa: Context root

bb....bb: WAR file name

cc....cc: File name

Description: The context root (aa....aa) of the WAR file (bb....bb) in the file (cc....cc) is invalid.
Action: Re-create the J2EE application. If you cannot re-create the J2EE application, contact the maintenance personnel.

KDJE42121-E

An attempt to import the file (aa....aa) has failed. Take action based on the detail message. If the cause is unknown, contact the system administrator. Details = bb....bb

aa....aa: File name

bb....bb: Detailed message

Description: An attempt to import the file (aa....aa) has failed.
Action: See the details, and then take action. For the messages in which the detailed information starts with nnnn (n is a number), see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory. If you do not understand the cause, contact the maintenance personnel.

KDJE42122-E

The value of the sequential number specified in the lookup name of the EJB exceeded the limit. EJB name = aa....aa, Lookup name = bb....bb

aa....aa: EJB name

bb....bb: Lookup name

Description: The value of the sequential number specified in the lookup name (bb....bb) of the EJB(aa....aa) has exceeded the limit.
Action: Change the lookup name of the existing EJB, and then re-execute the operation.

KDJE42123-E

A resource adapter that has the native library file in the file (aa....aa) exists. Delete the native library file, and then re-import.

aa....aa: File name

Description: A resource adapter that contains the native library file, exists in the file (aa....aa).
Action: Delete the native library file, and then re-import.

KDJE42124-E

The application aa....aa already exists. Check the application name. (Application names are not case-sensitive.)

aa....aa: Lookup name

Description

The J2EE application that contains the lookup name (aa....aa), already exists.

Action

Take action depending on the following status:

When creating a new J2EE application

Change the display-name of the J2EE application, and then re-create.
When importing an EAR file based on the J2EE specifications

Change the display-name of the EAR file to be imported, and then re-import, or delete the application with duplicate name, and then re-import.
When importing the file with runtime information

Delete the application with duplicate lookup name, and then re-import.

KDJE42125-W

The value of the tag in the deployment descriptors in the file is duplicated (aa....aa). Only the value found first or last is used. Details = bb....bb

aa....aa: Name of the file with runtime information

bb....bb: Detailed message

Description: The value of the tag in the deployment descriptors in the file (aa....aa) is duplicated. Only the value found first or last is used.
Action: See the details, and then revise the duplicated value of the tag.

KDJE42126-E

An attempt to execute an external program has failed. Details = aa....aa

aa....aa: Details

Description

An attempt to execute an external program has failed.

The environment settings might be invalid.

Action

See the details. Revise the environment settings. If you do not understand the cause, contact the maintenance personnel.

KDJE42127-E

The file could not be deleted. Path = aa....aa

aa....aa: File path

Description: The file cannot be deleted.
Action: Confirm the file to be deleted, and then take action. If you do not understand the cause, contact the maintenance personnel.

KDJE42128-E

An attempt to parse the XML has failed. Details = aa....aa

aa....aa: Details

Description: An attempt to parse the XML has failed.
Action: See the details, confirm the XML file to be processed, and then take action.

KDJE42129-E

The directory could not be deleted. Path = aa....aa

aa....aa: Directory path

Description: The directory cannot be deleted.
Action: Confirm the directory to be processed, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42130-E

This stand-alone resource adapter "aa....aa" is tested once. Reboot the J2EE server, and then delete.

aa....aa: Resource adapter name

Description: This stand-alone resource adapter (aa....aa) is tested once.
Action: Reboot the J2EE server, and then delete the target resource adapter.

KDJE42131-E

Another server management command is already running. Details = [aa....aa]

aa....aa: Details

Description

Either another operation is already being performed by the server management command or the recovery process of the work directory, that is performed when an error occurs in the server management command, has failed.

Action

Take action using any one of the following methods:

If another server management command is being executed, perform the operation again after the operation, that is in progress, terminates.
If the message KDJE42134-E is output before this message, the recovery process of the work directory has failed. See the action described in the message KDJE42134-E.

KDJE42132-I

The status of the public directory is invalid because a server management command operation was interrupted. Recovery will now start. Details = [aa....aa]

aa....aa: Details

Description

This message indicates that the recovery of the working directory has started.

The status of the working directory is invalid because a server management command operation was interrupted. Recovery of the working directory will now start.

KDJE42133-I

Recovery of the public directory has finished.

Description: This message indicates that the recovery of the working directory has finished.

KDJE42134-E

An attempt to recover the public directory has failed. Details = [aa....aa]

aa....aa: Details

Description: An attempt to recover the working directory has failed.
Action: See the details, and then take action. For the messages in which the detailed information starts with nnnn (n is a number), see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory. Check whether any other error message is displayed and if it is displayed, take action. If the problem is not resolved, restart the J2EE server. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42135-E

The directory cannot be accessed. Path = aa....aa

aa....aa: Directory path

Description: The directory cannot be accessed.
Action: Confirm that the access permissions are set to the directory. If access permissions are not set, set the appropriate permissions, and then re-execute the operation.

KDJE42136-E

The status of the public directory is invalid.

Description: The status of the working directory is invalid.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE42137-E

An internal error occurred. Contact the system administrator.

Description: An internal error occurred.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE42138-E

This application had failed in stopping. Please operate it by rebooting the J2EE server.

Description: This message indicates that the J2EE application cannot be started and deleted because an attempt to stop the J2EE application has failed earlier.
Action: Reboot the J2EE server, and then perform the operation.

KDJE42139-I

The J2EE application (aa....aa) will now be stopped.

aa....aa: J2EE application name

Description: This message indicates that the processing to stop the application (aa....aa), has started.

KDJE42140-I

The J2EE application (aa....aa) stopped.

aa....aa: J2EE application name

Description: This message indicates that the J2EE application (aa....aa) is stopped.

KDJE42141-I

The J2EE application (aa....aa) will now be undeployed.

aa....aa: J2EE application name

Description: This message indicates that the processing to undeploy the J2EE application (aa....aa), has started.

KDJE42142-I

The J2EE application (aa....aa) undeployed.

aa....aa: J2EE application name

Description: This message indicates that the J2EE application (aa....aa) is undeployed.

KDJE42143-I

The ClassLoader for the J2EE application was initialized. (display-name = aa....aa, initialized time = bb....bb)

aa....aa: J2EE application name

bb....bb: Initialized time

Description: This message indicates that the ClassLoader was initialized.

KDJE42144-I

The ClassLoader for the J2EE application was finalized. (display-name = aa....aa, initialized time = bb....bb)

aa....aa: J2EE application name

bb....bb: Initialized time

Description

This message indicates that the application class loader is destroyed.

This message is output when the finalize method process of the application class loader is executed, after the J2EE application stops.

If this message is not displayed even after repeatedly starting or stopping the application, memory leakage might have occurred.

By comparing the J2EE application name and time information output in the KDJE42143-I message, the destroyed application class loader can be identified. For details, see Appendix B Configuration of the Class Loader in the uCosminexus Application Server Common Container Functionality Guide. This message indicates that the ClassLoader was destroyed.

The timing of displaying this message depends on the garbage collector. If this message is not displayed even after repeatedly starting or stopping the application, memory leakage might have occurred.

KDJE42145-E

Usage:

Format 1: cjsweepout [servername] -inspect

Format 2: cjsweepout [servername] -allsweep

Format 3: cjsweepout [servername] -sweep id(key)

Description: This message describes the usage method of the cjsweepout command.
Action: Re-execute the cjsweepout command using the correct usage method.

KDJE42146-E

The configuration file for Cosminexus Component Container was not found. (path = aa....aa)

aa....aa: Path of the configuration file

Description: The configuration file of Cosminexus Component Container was not found.
Action: Confirm that the name of the J2EE server specified when executing the cjsweepout command is correct. If the name of the J2EE server is incorrect, specify the correct name, and then re-execute the cjsweepout command. If the configuration file is deleted, re-install the Cosminexus Component Container or set up the J2EE server again, and re-create the configuration file, and then, re-execute the cjsweepout command.

KDJE42147-E

The configuration file for Cosminexus Component Container could not be accessed. (path = aa....aa, detail = bb....bb)

aa....aa: Path of the configuration file

bb....bb: Detailed message

Description: The configuration file for Cosminexus Component Container cannot be accessed.
Action: When the access permissions are not assigned to the configuration file, assign the permissions, and then re-execute the cjsweepout command. When the access permissions are assigned to the configuration file, take action based on the details, and then re-execute the cjsweepout command.

KDJE42148-E

The value of the ejbserver.http.port property, defined in the J2EE server configuration file, is invalid. (path = aa....aa, value = bb....bb, detail = cc....cc)

aa....aa: Path of the configuration file

bb....bb: Value of ejbserver.http.port property

cc....cc: Details

Description: The value of the ejbserver.http.port property, defined in the J2EE server configuration file, is invalid.
Action: Correct the value of ejbserver.http.port property, and then re-execute the cjsweepout command.

KDJE42149-E

The J2EE server specified when the cjsweepout command was executed is already running. (server name = aa....aa, http server port number = bb....bb)

aa....aa: The J2EE server name

bb....bb: Port number of the HTTP server (simple Web server) in which the J2EE server is running internally

Description

The J2EE server specified when the cjsweepout command was executed is already running.

Do not execute the cjsweepout command for the running J2EE server.

Action

When executing the cjsweepout command, if the specified J2EE server is running, stop the J2EE server, and then re-execute the cjsweepout command. Confirm that the application (another J2EE server) using the same port number is not running when the J2EE server is being stopped. If the application (another J2EE server) is running, stop it, and then re-execute the cjsweepout command.

KDJE42150-E

The cjsweepout command was executed for an unsupported version of Cosminexus Component Container. (version = aa....aa)

aa....aa: Version information of Cosminexus Component Container

Description: The cjsweepout command was executed for an unsupported version of Cosminexus Component Container.
Action: Confirm that the version of Cosminexus Component Container supports the cjsweepout command.

KDJE42151-E

A file exists where the public directory for the J2EE server should be. (path = aa....aa)

aa....aa: File path

Description: A file exists on the location where the working directory for the J2EE server should exist.
Action: Delete the file, create the working directory, and then re-execute the cjsweepout command.

KDJE42152-E

The public directory for the J2EE server was not found. (path = aa....aa)

aa....aa: Path of the working directory

Description: The working directory for the J2EE server was not found.
Action: Create the working directory, and then re-execute the cjsweepout command.

KDJE42153-E

The public directory for the J2EE server could not be accessed. (path = aa....aa)

aa....aa: Path of the working directory

Description: The working directory for the J2EE server cannot be accessed.
Action: Confirm that the permissions to access the working directory are available, if not, assign the access permissions to the working directory, and then re-execute the cjsweepout command.

KDJE42154-I

Inspection result:

aa....aa

aa....aa: Inspection result

Description

This message is the result of inspecting the state of the directory configuration present under the working directory of the J2EE server.

The contents displayed in the inspection result (aa....aa) are as follows:

ID(Key): Directory and the file name under the working directory for the J2EE server. The ID is displayed as the character string that can be identified by the cjsweepout command.
Display name: The display name of the J2EE application or the J2EE resource adapter, and the J2EE resource (EJB-JAR, resource adapter, WAR, data source, mail configuration) is displayed. Hyphen (-) is displayed when the display name cannot be obtained.
Condition: Valid is displayed when the directory and the file (ID(Key)) under the working directory for the J2EE server are in normal state, and invalid is displayed when the directory and the file are in abnormal state.

KDJE42155-I

The ID(Key) will now be deleted. (ID = aa....aa)

aa....aa: ID(Key)

Description: The ID(Key) will be deleted.

KDJE42156-I

The ID(Key) has been deleted. (ID = aa....aa)

aa....aa: ID(Key)

Description: The ID(Key) is deleted.

KDJE42157-W

The internal configuration of the J2EE server is in a normal state. (server name = aa....aa)

aa....aa: The J2EE server name

Description: The internal configuration of the J2EE server is in a normal state.
Action: Confirm that the name of the J2EE server specified when executing the cjsweepout command is correct. If the name of the J2EE server is incorrect, specify the correct name, and then re-execute the cjsweepout command.

KDJE42158-W

The ID(Key) is in a normal state. (ID = aa....aa)

aa....aa: ID(Key)

Description: The ID (Key) is in a normal state.
Action: Confirm that the ID (Key) specified while executing the cjsweepout command is correct. If the ID (Key) is incorrect, specify the correct ID (Key), and then re-execute the cjsweepout command.

KDJE42159-E

The ID(Key) was not found. (ID = aa....aa)

aa....aa: ID(Key)

Description: The ID (Key) was not found.
Action: Confirm that the ID (Key) specified while executing the cjsweepout command is correct. If the ID (Key) is incorrect, specify the correct ID (Key), and then re-execute the cjsweepout command.

KDJE42160-I

The cjsweepout command finished successfully.

Description: The cjsweepout command finished successfully.

KDJE42161-E

The attribute of the J2EE application "aa....aa" could not be set. The specification of a library class path is invalid. (invalid path = bb....bb)

aa....aa: J2EE application name

bb....bb: File or directory path

Description: This message indicates that the attribute of the J2EE application cannot be set since the specification of a class path is invalid.
Action: Confirm that the reference path of the class is correct. If the path is incorrect, specify the correct reference path. If the path is correct, confirm that the file specified in the reference path exists on the same machine as the J2EE server. If the file does not exist, place the file in the specified location.

KDJE42162-E

Deployment processing ended abnormally. The specification of a library class path in the J2EE application "aa....aa" is invalid. (invalid path = bb....bb)

aa....aa: J2EE application name

bb....bb: File or directory path

Description: This message indicates that the deployment processing of the J2EE application ended abnormally because the specification of a class path is invalid.
Action: Confirm that the reference path of the class is correct. If the path is incorrect, specify the correct reference path. If the path is correct, confirm that the file specified in the reference path exists on the same machine as the J2EE server. If the file does not exist, place the file in the specified location.

KDJE42163-E

The J2EE application "aa....aa" will not create an RMI-IIOP stub.

aa....aa: J2EE application name

Description: The specified J2EE application will not create an RMI-IIOP stub.
Action: Modify the configuration of the J2EE application, and then execute the command.

KDJE42164-E

This J2EE application has not once been executed. (display-name = aa....aa)

aa....aa: J2EE application name

Description: This J2EE application is not executed even once.
Action: Execute this application once, and then execute the command.

KDJE42165-E

A J2EE application having the same lookup name already exists. (J2EE application display name = aa....aa, J2EE application lookup name = bb....bb, J2EE application mode = cc....cc)

aa....aa: Display name of the J2EE application

bb....bb: Lookup name of the J2EE application

cc....cc: Mode of the J2EE application

Description

A J2EE application with the same lookup name already exists. The lookup name of the J2EE application must be unique in the mode (normal mode, test mode) of the J2EE application.

The lookup name of the J2EE application is auto generated from the display name of the J2EE application.

Action

Change the display name in such a way that the lookup name is not duplicated, and then re-execute the operation.

KDJE42166-I

The J2EE application will now be created. (display name = aa....aa)

aa....aa: Display name of the J2EE application

Description: This message indicates that the processing of creating the J2EE application has started.

KDJE42167-I

The J2EE application was created successfully. (display name = aa....aa)

aa....aa: Display name of the J2EE application

Description: This message indicates that the J2EE application was created successfully.

KDJE42168-I

The resource will now be added to the J2EE application. (resource = aa....aa, type =bb....bb, J2EE application = cc....cc)

aa....aa: Resource display name (file name when the type is LibJar)

bb....bb: Resource type

cc....cc: Display name of the J2EE application

Description: This message indicates that the processing to add the resource to the J2EE application has started.

KDJE42169-I

The resource was successfully added to the J2EE application. (resource = aa....aa, type =bb....bb, J2EE application = cc....cc)

aa....aa: Resource display name (file name when the type is LibJar)

bb....bb: Resource type

cc....cc: Display name of the J2EE application

Description: This message indicates that the resource was successfully added to the J2EE application.

KDJE42170-I

The resource will now be deleted from the J2EE application. (resource = aa....aa, type =bb....bb, J2EE application = cc....cc)

aa....aa: Resource display name (file name when the type is LibJar)

bb....bb: Resource type

cc....cc: Display name of the J2EE application

Description: This message indicates that the processing to delete the resource from the J2EE application has started.

KDJE42171-I

The resource was successfully deleted from the J2EE application. (resource = aa....aa, type =bb....bb, J2EE application = cc....cc)

aa....aa: Resource display name (file name when the type is LibJar)

bb....bb: Resource type

cc....cc: Display name of the J2EE application

Description: This message indicates that the resource was successfully deleted from the J2EE application.

KDJE42174-I

The resource's properties will now be set. (display name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description: This message indicates that the processing to set properties for resource has started.

KDJE42175-I

The resource's properties were set successfully. (display name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description: This message indicates that the properties for resource were set successfully.

KDJE42176-I

The properties for the internal resource of the J2EE application will now be set. (resource = aa....aa, type = bb....bb, J2EE application = cc....cc)

aa....aa: Resource display name

bb....bb: Resource type

cc....cc: Display name of the J2EE application

Description: This message indicates that the processing to set properties for the internal resource of the J2EE application has started.

KDJE42177-I

The properties for the internal resource of the J2EE application were set successfully. (resource = aa....aa, type = bb....bb, J2EE application = cc....cc)

aa....aa: Resource display name

bb....bb: Resource type

cc....cc: Display name of the J2EE application

Description: This message indicates that the properties for the internal resource of the J2EE application were set successfully.

KDJE42178-I

The resource will now be deleted. (display name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description: This message indicates that the processing to delete the resource has started.

KDJE42179-I

The resource was deleted successfully. (display name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description: This message indicates that the resource was deleted successfully.

KDJE42180-I

The resource will now be copied. (display name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description: This message indicates that the processing to copy the resource has started.

KDJE42181-I

The resource was copied successfully. (display name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description: This message indicates that the resource was copied successfully.

KDJE42182-I

The J2EE resource adapter will now be deployed. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description: This message indicates that the deployment process of the J2EE resource adapter has started.

KDJE42183-I

The J2EE resource adapter was deployed successfully. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description: This message indicates that the J2EE resource adapter was deployed successfully.

KDJE42184-I

The J2EE resource adapter will now be undeployed. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description: This message indicates that the undeployment process of the J2EE resource adapter has started.

KDJE42185-I

The J2EE resource adapter was undeployed successfully. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description: This message indicates that the undeployment process of the J2EE resource adapter has ended.

KDJE42186-I

The J2EE resource adapter will now start. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description: This message indicates that the J2EE resource adapter will now start.

KDJE42187-I

The J2EE resource adapter started successfully. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description: This message indicates that the J2EE resource adapter started successfully.

KDJE42188-I

The J2EE resource adapter will now stop. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description: This message indicates that the processing to stop the J2EE resource adapter has started.

KDJE42189-I

The J2EE resource adapter stopped successfully. (display name =aa....aa)

aa....aa: J2EE resource adapter display name

Description: This message indicates that the J2EE resource adapter stopped successfully.

KDJE42190-I

The mail configuration will now be created. (display name = aa....aa)

aa....aa: Display name of the mail configuration

Description: This message indicates that the processing to create the new mail configuration has started.

KDJE42191-I

The mail configuration was created successfully. (display name = aa....aa)

aa....aa: Display name of the mail configuration

Description: This message indicates that the new mail configuration was created successfully.

KDJE42192-I

The connection test for the J2EE resource adapter will now be performed. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description: This message indicates that the connection test for the J2EE resource adapter will now be performed.

KDJE42193-I

The connection test for the J2EE resource adapter has finished. (display name = aa....aa, test result = bb....bb)

aa....aa: J2EE resource adapter display name

bb....bb: Test result

Description: This message indicates that the connection test for the J2EE resource adapter has finished.

KDJE42194-I

The connection test for the data source will now be performed. (display name = aa....aa)

aa....aa: Data source display name

Description: This message indicates that the connection test for the data source will now be performed.

KDJE42195-I

The connection test for the data source has finished. (display name = aa....aa, test result = bb....bb)

aa....aa: Data source display name

bb....bb: Test result

Description: This message indicates that the connection test for the data source has finished.

KDJE42196-I

The mail configuration will now be tested. (display name = aa....aa)

aa....aa: Display name of the mail configuration

Description: This message indicates that connection test used by mail configuration will now start.

KDJE42197-I

The mail configuration test has finished. (display name = aa....aa, test result = bb....bb)

aa....aa: Display name of the mail configuration

bb....bb: Test result

Description: This message indicates that the connection test used by mail configuration has finished.

KDJE42200-E

An attempt to move the J2EE application that is to be replaced has failed. (directory or file path to be moved = aa....aa)

aa....aa: Directory or file path to be moved

Description

An attempt to move the J2EE application that is to be replaced has failed.

The reason might be because either the file under the directory to be moved or the file to be moved is in use, or the directory or the file cannot be moved because the access permissions is not available.

Action

Remove the cause of the error, and then re-execute the process.

KDJE42201-E

An attempt to import the replacement-source J2EE application has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to import the replacement-source J2EE application has failed. The import processing might have failed because the disk space available was not sufficient.

Action

See the details or the message output before this message and remove the cause due to which the import processing failed, and then re-execute the process.

For the messages in which the detailed information starts with nnnn (n is a number), see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory.

KDJE42202-E

The configurations of the J2EE application before and after the replacement do not match. (details = aa....aa)

aa....aa: Details

Description: The configurations of the J2EE application before and after the replacement do not match.
Action: See the details, modify the J2EE application so that the configurations match, and then re-execute the process. If you cannot modify, import the configuration after deleting the J2EE application to be replaced.

KDJE42203-E

An attempt to start the J2EE application after completion of replacement processing has failed. (details = aa....aa)

aa....aa: Details

Description: An attempt to start the J2EE application after completing the replacement processing has failed.
Action: See the details or the message output before this message to remove the cause due to which the start process failed, and then restart the J2EE application.

KDJE42204-E

The development environment and the J2EE server are not running on the same machine. (IP address of the machine running the development environment = aa....aa, IP address of the machine running the J2EE server = bb....bb)

aa....aa: IP address of the machine on which the development environment is running

bb....bb: IP address of the machine on which the J2EE server is running

Description: The development environment and the J2EE server are not running on the same machine.
Action: Start the development environment and the J2EE server on the same machine, and then re-execute the process.

KDJE42205-E

The update list file does not exist. (update list file path = aa....aa)

aa....aa: Update list file path

Description: The update list file does not exist.
Action: Specify the correct update list file path, and then re-execute the process.

KDJE42206-E

An attempt to analyze the update list file has failed. (details = aa....aa)

aa....aa: Details

Description: An attempt to analyze the update list file has failed.
Action: See the details to remove the cause due to which the analysis processing failed, and then re-execute the analysis processing.

KDJE42207-E

The J2EE application is not in a stopped state. (J2EE application display name = aa....aa, J2EE application mode = bb....bb, J2EE application state = cc....cc)

aa....aa: Display name of the J2EE application

bb....bb: Mode of the J2EE application

cc....cc: State of the J2EE application

Description: The J2EE application is not in a stopped state. You cannot operate only when the J2EE application is not running.
Action: Stop the J2EE application, and then re-execute the operation.

KDJE42208-E

An attempt to update the target archive file has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to update the target archive file has failed.

The update processing might have failed because the available disk space was not sufficient.

Action

See the details or the message output before this message to remove the cause due to which the creation processing failed, and then re-execute the process.

KDJE42209-I

The command lock was released because there was no request from the command for a long period. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time = dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description: This message indicates that the command lock was released because there was no request from the command for a long period.

KDJE42210-I

The command lock was released because the cjresetsv command was executed. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time = dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description: This message indicates that the command lock was released because cjresetsv command was executed.

KDJE42211-I

The command status has changed to awaiting execution. (command name = aa....aa, host name = bb....bb, number of commands awaiting execution = cc....cc)

aa....aa: Command name excluding the directory path and the extension of the command awaiting execution

bb....bb: IP address of the host requesting the command awaiting execution

cc....cc: Number of commands awaiting execution

Description: This message indicates that the command is in pending state.

KDJE42212-E

Execution of a command was refused, either because the user did not have execution permission for the command, or the command was canceled. Re-execute the command. (command name = aa....aa)

aa....aa: Command name excluding the directory path and the extension of the command that failed to execute

Description

The processing cannot be continued because the command execution permission is not available with the user.

Take action based on the following causes:

The command processing cannot be finished within the response awaiting period of the J2EE server because of high load processing
Significant communication delay occurred in the network
The command execution process is remarkably delayed
The exclusive access control of the J2EE server was released by the cjresetsv command during the processing of the command

Action

Re-execute the cancelled command.

Make sure that the exclusion release message (KDJE42209-I or KDJE42210-I) is output in the J2EE server console during the iteration and when the processing is interrupted.

Confirm the following, and then take action when the exclusive release message is displayed:

Check the command execution terminal and the network status. If any problem exists, remove it, and then re-execute the command.
When a problem does not exist in the command execution terminal and the network status, use a larger value for the setting value of the response-awaiting period (ejbserver.deploy.exclusive.lockAliveInterval) from the command defined in the user properties file for the J2EE server. Reboot the server after changing the setting value, and then re-execute the command.

If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42213-E

Execution of a command was refused because the server is awaiting shutdown. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time= dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description: Acceptance of a new command was refused because the shutdown command is pending state.
Action: Reboot the server, and then re-execute the command.

KDJE42214-E

Execution of a command was refused because the server is waiting for a GUI command to end. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time = dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description

Acceptance of a new command was refused because the GUI command is in pending state.

When the GUI command is running or is in pending state, the server stops the acceptance of a new command.

Action

After the GUI command finishes on the server, re-execute the command for which execution was refused.

KDJE42215-I

The J2EE application aa....aa will now be blocked.

aa....aa: J2EE application name

Description: The J2EE application will be blocked.

KDJE42216-I

The J2EE application aa....aa was blocked successfully.

aa....aa: J2EE application name

Description: The J2EE application was blocked successfully. As a result, a new request will not be accepted. The processing of the request being processed will continue.

KDJE42217-I

The Web application will now be blocked.

Description: The Web application will be blocked.

KDJE42218-I

The Web application was blocked successfully.

Description: The Web application was blocked successfully.

KDJE42219-I

The CTM queue will now be blocked.

Description: The CTM queue will be blocked.

KDJE42220-I

The CTM queue was blocked successfully.

Description: The CTM queue was blocked successfully.

KDJE42221-I

The front EJB will now be blocked.

Description: The front EJB will be blocked.

KDJE42222-I

The front EJB was blocked successfully.

Description: The front EJB was blocked successfully.

KDJE42223-I

The J2EE application aa....aa will now be forcibly stopped.

aa....aa: J2EE application name

Description: The J2EE application will be forcibly stopped.

KDJE42224-I

The J2EE application aa....aa was forcibly stopped.

aa....aa: J2EE application name

Description: The J2EE application was forcibly stopped.

KDJE42225-E

An attempt to forcibly stop the J2EE application aa....aa has failed.

aa....aa: J2EE application name

Description

An attempt to forcibly stop the J2EE application has failed.

Action

Use the server management command (cjlistapp) to check the state of the J2EE application.

Take action by the following methods depending on the state:

When the J2EE application is in the stopped state: No problem exists because the termination was normal.
When the J2EE application is in the forceStopFailure state: Restart the J2EE server.
For other states: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE42226-E

The property value of the UAP forcible stop function is invalid.

Description: The set value for the property of the forced termination functionality of the J2EE application is incorrect.
Action: Revise the set value of the property.

KDJE42227-E

The forcible stop cannot be executed because the property ejbserver.deploy.app.stopforcibly.disabled is true.

Description: The forcible stop of the J2EE application cannot be executed because the property ejbserver.deploy.app.stopforcibly.disabled is true.
Action: Set the property value to false, restart the J2EE server, and then execute the forcible stop.

KDJE42228-E

The display name contains invalid characters. (display name = aa....aa)

aa....aa: Display name

Description: The display name contains invalid characters. Only single byte alphanumeric characters (a~z, A~Z, 0~9) and single byte underscores (_) can be specified in the display name.
Action: Change the display name, and then re-execute the operation.

KDJE42229-E

The server refused to execute the command because the command cannot wait for other commands to end. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time = dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description: The executed command cannot wait until the termination of other commands. The reception of the command has been denied by the J2EE server on which other commands are running.
Action: Confirm that other commands are not running on the J2EE server on which the command is to executed, and then re-execute the refused commands.

KDJE42230-E

Execution of a command was refused because an another privilege command is already running. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time= dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description: Execution of a command was refused because another privilege command was already running.
Action: Confirm that another privilege command is not running on the J2EE server on which the command is to be executed, and then re-execute the refused command.

KDJE42231-E

aa....aa processing cannot continue because monitoring of the UAP execution time is disabled.

aa....aa: Process contents

Description

The processing cannot be continued because the monitoring of UAP execution time is disabled.

Action

Enable the monitoring functionality of the UAP execution time using any one of the following methods:

Set false for the property ejbserver.deploy.app.stopforcibly.disabled
Specify a number greater than 0 in the property ejbserver.ext.method_observation.interval

KDJE42232-E

aa....aa processing cannot continue because of a discrepancy between the JDK vendor bb....bb and the version cc....cc.

aa....aa: Process contents

bb....bb: JDK vendor name

cc....cc: JDK version

Description

The processing cannot continue because either the JDK vendor or the version is different.

Action

Part of the operation functionality of the J2EE application cannot be used.

When the functionality for monitoring the J2EE application execution time is in use, disable the functionality.

KDJE42233-E

A valid RAR file was not found.

Description: A valid RAR file that can be used for migrating the resource adapter was not found.
Action: Create a valid RAR file.

KDJE42234-E

The server aa....aa has not been updated.

aa....aa: Server name

Description: The resource adapter cannot be migrated because the migration of the J2EE server has not finished.
Action: After the migration of the J2EE server finishes, again migrate the resource adapter.

KDJE42235-E

Migration of the resource adapters of the old version has finished, but some resource adapters could not be migrated.

Description

An error occurred during the migration of the resource adapters.

Action

Check whether KDJE42271-E is displayed.

If displayed, see the action of KDJE42271-E.

When another error message is displayed, if required, restore from the backup.

KDJE42236-I

Processing to migrate the server will now start. (server name = aa....aa)

aa....aa: Server name

Description: This message indicates that the processing to migrate the server has started.

KDJE42237-I

Processing to migrate the server has finished. (server name = aa....aa)

aa....aa: Server name

Description: This message indicates that the processing to migrate the server has finished.

KDJE42238-I

Processing to migrate the resource adapter will now start. (resource name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description: This message indicates that the processing to migrate the resource adapter has started.

KDJE42239-I

Processing to migrate the resource adapter of the J2EE application will now start. (resource name = aa....aa, J2EE application = bb....bb)

aa....aa: Resource display name

bb....bb: J2EE application name

Description: This message indicates that the processing to migrate the resource adapter of the J2EE application has started.

KDJE42240-E

An attempt to migrate the resource adapter has failed (resource name = aa....aa, type = bb....bb, detail = cc....cc).

aa....aa: Resource display name

bb....bb: Resource type

cc....cc: Details

Description

This message indicates that an attempt to migrate the resource adapter has failed.

Action

Take action using any one of the following methods:

When error level message is displayed just before: See the action of the message displayed just before.
In the other cases: See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42241-E

An attempt to migrate the internal resource adapter of the J2EE application has failed (resource name = aa....aa, J2EE application = bb....bb, detail = cc....cc).

aa....aa: Resource display name

bb....bb: J2EE application name

cc....cc: Details

Description

This message indicates that an attempt to migrate the internal resource adapter of the J2EE application has failed.

Action

Take action using any one of the following methods:

When error level message is displayed just before: See the action of the message displayed just before.
In the other cases: See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42242-I

Migration of the resource adapter has finished. (resource name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description: This message indicates that the migration of the resource adapter has finished.

KDJE42243-I

Migration of the resource adapter of the J2EE application has finished. (resource name = aa....aa, J2EE application = bb....bb)

aa....aa: Resource display name

bb....bb: J2EE application name

Description: This message indicates that the migration of the resource adapter of the J2EE application has finished.

KDJE42244-E

The file format is invalid. (file = aa....aa)

aa....aa: File name

Description: The file format is invalid.
Action: Use a valid file to migrate the resource adapter again.

KDJE42245-E

The file aa....aa was not found.

aa....aa: File name

Description: The file aa....aa was not found.
Action: Confirm that the file exists in the path.

KDJE42246-E

Resource "aa....aa" cannot start because the data source is not supported.

aa....aa: Resource display name

Description: Resource cannot start because the data source is not supported.
Action: Use the resource adapter.

KDJE42247-I

Migrating version (file = aa....aa, old version = bb....bb, new version = cc....cc).

aa....aa: File name

bb....bb: Old version

cc....cc: New version

Description: This message indicates the version of the file before and after migration.

KDJE42248-E

The file version is invalid (file = aa....aa, old version = bb....bb, new version = cc....cc).

aa....aa: File name

bb....bb: Old version

cc....cc: New version

Description: This message indicates the version of the file before and after migration when the migration processing cannot be performed.
Action: Confirm the version of the file.

KDJE42249-W

Migration of the resource adapter will now stop. (resource name = aa....aa, type = bb....bb, detail = cc....cc)

aa....aa: Resource display name

bb....bb: Resource type

cc....cc: Details

Description: This message indicates that the migration of the resource adapter will now stop.
Action: When executing the migration forcibly, specify -force option, and then re-execute the cjrarupdate command.

KDJE42250-W

Migration of the resource adapter of the J2EE application will now stop. (resource name = aa....aa, J2EE application = bb....bb, detail = cc....cc)

aa....aa: Resource display name

bb....bb: J2EE application name

cc....cc: Details

Description: This message indicates that the migration of the resource adapter of the J2EE application will now stop.
Action: When executing the migration forcibly, specify -force option, and then re-execute the cjrarupdate command.

KDJE42251-E

The status of the public directory is invalid. (type = aa....aa)

aa....aa: Resource type

Description: The status of the working directory is invalid.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE42252-I

Processing to migrate the resource adapter will now start.

Description: This message indicates that the processing to migrate the resource adapter has started.

KDJE42253-I

Migration of the resource adapter has finished.

Description: This message indicates that the migration of the resource adapter has finished.

KDJE42254-I

Processing to back up the server will now start. (server name = aa....aa, the number of file = bb....bb)

aa....aa: Server name

bb....bb: Number of files for backup

Description: This message indicates that the processing to back up the server will now start.

KDJE42255-I

Processing to back up the server has finished. (server name = aa....aa)

aa....aa: Server name

Description: This message indicates that the processing to back up the server has finished.

KDJE42257-W

An invalid property value is specified. Default value is used. (key = aa....aa, value = bb....bb, default value = cc....cc)

aa....aa: Property key

bb....bb: Set value

cc....cc: Default value

Description

The default value will be used because an invalid value was acquired from the property file.

Take action based on the following causes:

An invalid value is specified in the properties.
A value outside the valid range has been specified.

Action

Revise the set value of the property (aa....aa) of the user properties file (usrconf.properties) for the J2EE server.

KDJE42258-I

Exporting the RMI-IIOP stub for J2EE application is in progress. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description: This message indicates that the processing to export the RMI-IIOP stub for the J2EE application is in progress.

KDJE42259-I

Sending the export information of the RMI-IIOP stub for the J2EE application was successful. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description: This message indicates that sending of the export information of the RMI-IIOP stub for the J2EE application was successful.

KDJE42260-I

The J2EE application name will now be renamed. (old name = aa....aa, new name = bb....bb)

aa....aa: Old name of the J2EE application

bb....bb: New name of the J2EE application

Description: This message indicates that the J2EE application name will now be renamed.

KDJE42261-I

The J2EE application name was renamed successfully. (old name = aa....aa, new name = bb....bb)

aa....aa: Old name of the J2EE application

bb....bb: New name of the J2EE application

Description: This message indicates that the J2EE application name was renamed successfully.

KDJE42262-I

The J2EE application mode will now be changed. (J2EE application = aa....aa, old mode = bb....bb, new mode = cc....cc)

aa....aa: J2EE application name

bb....bb: Old operating mode of the J2EE application

cc....cc: New operating mode of the J2EE application

Description: This message indicates that the processing for changing the operating mode of the J2EE application has started.

KDJE42263-I

The J2EE application mode was changed successfully. (J2EE application = aa....aa, old mode = bb....bb, new mode = cc....cc)

aa....aa: J2EE application name

bb....bb: Old operating mode of the J2EE application

cc....cc: New operating mode of the J2EE application

Description: This message indicates that the operating mode of the J2EE application was changed successfully.

KDJE42264-I

The command lock will now be released because the cjresetsv command was executed. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time = dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description: This message indicates that the command lock will now be released because the cjresetsv command was executed.

KDJE42268-I

The J2EE application will now be replaced. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description: This message indicates that the redeployment of the J2EE application has started.

KDJE42269-I

The J2EE application was replaced successfully. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description: This message indicates that the redeployment of the J2EE application was successful.

KDJE42270-W

The EJB violates the EJB specification. : aa....aa

aa....aa: Details of the error contents

Description

This message indicates that the EJB violates the EJB specification.

Action

See the details of the error, and then take action. For details, see 7.9 List of details for KDJE42039-E and KDJE42270-W.

If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42271-E

An attempt to create a backup for the server has failed. (server name = aa....aa, detail = bb....bb)

aa....aa: Server name

bb....bb: Detailed message

Description: An attempt to create a backup has failed.
Action: See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42272-E

An attempt to export the J2EE application has failed. (J2EE application = aa....aa, detail = bb....bb)

aa....aa: J2EE application name

bb....bb: Detailed message

Description: An attempt to export the J2EE application has failed.
Action: See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42274-E

The setting of the reload function is invalid.

Description

The property combination for the setting of the reload functionality is invalid.

In the case of ejbserver.deploy.context.reload_scope=app, ejbserver.rmi.localinvocation.scope=all cannot be selected.

Action

Check the property setting for the reload functionality.

KDJE42277-I

The J2EE application reload processing will now start.(J2EE application = aa....aa)

aa....aa: J2EE application name

Description: The J2EE application reload processing will now start.

KDJE42278-I

The J2EE application reload processing has finished.(J2EE application = aa....aa)

aa....aa: J2EE application name

Description: The J2EE application reload processing has finished.

KDJE42280-E

The update check for reloading failed. (J2EE application = aa....aa, detail = bb....bb)

aa....aa: J2EE application name

bb....bb: Exception

Description: An exception occurred in the update check for reloading.
Action: Contact the maintenance personnel.

KDJE42284-E

The reload function cannot be used. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description: The reload command was executed when the reload functionality was disabled.
Action: Check the property (ejbserver.deploy.context.reload_scope) that sets the scope of the reload functionality.

KDJE42285-I

A file subject to reloading was not modified. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description: The reload command was executed when a file subject to reloading was not modified.

KDJE42286-E

The command cannot be executed. (J2EE application = aa....aa, reason=bb....bb)

aa....aa: J2EE application name

bb....bb: Reason

Description

The command cannot be executed because of bb....bb.

Action

Reason: stopped: The command cannot be executed because the application has stopped. Start the application.
Reason: reload failure: The command cannot be executed because an attempt to reload has failed. Perform successful reloading or reboot the J2EE server.

KDJE42288-I

A file subject to reloading was modified. (J2EE application = aa....aa, filename = bb....bb)

aa....aa: J2EE application name

bb....bb: Updated file name

Description: A file subject to reloading was modified.

KDJE42290-E

The J2EE application reload processing failed. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description: An attempt to reload the J2EE application has failed.
Action: Take the action for the error message that was output before this message.

KDJE42291-I

The application directory "aa....aa" will now be imported.

aa....aa: Application directory path

Description: The application directory aa....aa will be imported.

KDJE42292-I

The application directory "aa....aa" was imported successfully.

aa....aa: Application directory path

Description: The application directory aa....aa was imported successfully.

KDJE42293-E

The J2EE application "aa....aa" contains the resource adapter.

aa....aa: Application directory path, Ear file name, or ZIP file name

Description: The J2EE application contains the resource adapter.
Action: Delete the resource adapter from the application, and then re-import.

KDJE42294-E

The J2EE application "aa....aa" contains the application client.

aa....aa: Application directory path, Ear file name, or ZIP file name

Description: The J2EE application contains the application client.
Action: Delete the application client from the application, and then re-import.

KDJE42295-E

The module name of the component "bb....bb" in J2EE application "aa....aa" is incorrect.

aa....aa: Application directory path

bb....bb: Module name of the component

Description: The module name of the component in the J2EE application is incorrect.
Action: Change the module name described in application.xml based on the generation rules of the application directory, and then re-import.

KDJE42296-E

The directory of the module "aa....aa" does not exist. The directory name must be "bb....bb".

aa....aa: Module name

bb....bb: Directory name

Description: The directory of the module aa....aa does not exist. The directory name must be bb....bb.
Action: Create the directory with a correct name based on the generation rules of the application directory, and then re-import.

KDJE42297-E

The WAR module "aa....aa" does not have a deployment descriptor.

aa....aa: Module name

Description: The WAR module does not have a DeploymentDescriptor.
Action: Check the configuration of the application directory. Deploy the WAR directory and the Deployment Descriptor correctly, and then re-import.

KDJE42298-E

The EJB-JAR module "aa....aa" does not have an annotation or a deployment descriptor.

aa....aa: Module name

Description: The EJB-JAR module does not have an Annotation or a Deployment Descriptor.
Action: Check the configuration of the application directory. Deploy the EJB-JAR directory and the Deployment Descriptor correctly, and then re-import.

KDJE42299-I

An update of the configuration file of the J2EE application "aa....aa" was detected. (file name = bb....bb) The definition information is now being reread.

aa....aa: J2EE application name

bb....bb: File name

Description: An update of the configuration file of the J2EE application was detected. The definition information is now being reread.

KDJE42300-I

The definition information of the J2EE application "aa....aa" has been reread successfully.

aa....aa: J2EE application name

Description: The definition information of the J2EE application is reread successfully.

KDJE42301-E

An attempt to reread the definition information of J2EE application "aa....aa" has failed. (detailed message = "bb....bb")

aa....aa: J2EE application name

bb....bb: Details

Description: An error was detected when rereading the definition information of the J2EE application.
Action: Modify the contents under the application directory based on the detailed message, and then re-execute the command.

KDJE42302-I

"aa....aa" will now be imported in an archive format.

aa....aa: EAR file name, ZIP file name, or WAR file name

Description: aa....aa will now be imported in an archive format.

KDJE42303-I

"aa....aa" will now be imported in an deployment directory format.

aa....aa: EAR file name or ZIP file name

Description: aa....aa will now be imported in a deployment directory format.

KDJE42304-I

The application will now be expanded into the directory "aa....aa".

aa....aa: Directory name

Description: The application will now be expanded into the directory aa....aa.

KDJE42305-E

The specified directory "aa....aa" does not exist.

aa....aa: Directory name

Description: The specified directory does not exist.
Action: Create an expanded directory, and then re-import.

KDJE42306-E

The files cannot be written to the specified directory "aa....aa".

aa....aa: Directory name

Description: The files cannot be written to the specified directory.
Action: Assign write permission, and then re-import.

KDJE42307-E

The state of a J2EE resource adapter is invalid. (display name =aa....aa)

aa....aa: Display name of the J2EE resource adapter

Description: The state of a J2EE resource adapter is invalid.
Action: Undeploy the J2EE resource adapter, then deploy it again, and then re-execute the operations. In the case the action cannot be taken, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42308-E

The deployment processing has abended. An element defined by a J2EE resource is invalid. (type = aa....aa, resname = bb....bb, parent element = cc....cc, element = dd....dd, detail = ee....ee)

aa....aa: J2EE resource type

bb....bb: Display name of the J2EE resource

cc....cc: Parent element name of the invalid element

dd....dd: Invalid element name

ee....ee: Details

Description

The deployment process has abended. An element defined by a J2EE resource is invalid.

The message displayed in the details and its cause are as follows:

The element is not supported.

The element is not supported.

Action

Take action based on the details. In the case the action cannot be taken, acquire the maintenance information, and then contact the maintenance personnel.

The element is not supported.

Remove the unsupported element, and then re-execute the operation..

KDJE42309-I

Loading annotation is in progress.

Description: Loading annotation is in progress.

KDJE42310-I

Loading annotation was successful.

Description: Loading annotation was successful.

KDJE42311-E

An unsupported Java type is set. (Java type = aa....aa)

aa....aa: Java Type of @Resource

Description: Java Type set in element type() of @Resource is not supported.
Action: Use a supported Java Type.

KDJE42312-E

The occurrence count from which the declaration of the "aa....aa"annotation is defined in the EJB specification is exceeded.

aa....aa: Annotation name exceeding the occurrence count of the EJB specification

Description: The declaration of the annotation exceeds the occurrence count defined in the Deployment Descriptor.
Action: Modify the setting of annotation and match it with the occurrence count defined in the EJB specification.

KDJE42313-I

The JavaBeans resource will now start. (display name = aa....aa)

aa....aa: JavaBeans resource display name

Description: This message indicates that the JavaBeans resource will now start.

KDJE42314-I

The JavaBeans resource started successfully. (display name = aa....aa)

aa....aa: Annotation name exceeding the occurrence count of the EJB specification

Description: This message indicates that the JavaBeans resource started successfully.

KDJE42315-I

The JavaBeans resource will now stop. (display name = aa....aa)

aa....aa: JavaBeans resource display name

Description: This message indicates that the JavaBeans resource will now stop.

KDJE42316-I

The JavaBeans resource stopped successfully. (display name =aa....aa)

aa....aa: JavaBeans resource display name

Description: This message indicates that the JavaBeans resource stopped successfully.

KDJE42317-E

This JavaBeans resource "aa....aa" has been started once. Restart the J2EE server, and then try to delete the resource again.

aa....aa: JavaBeans resource display name

Description: JavaBeans resource is started once.
Action: Restart the J2EE server and delete the resource again.

KDJE42318-W

Cannot get edition information. aa....aa is used as a protocol.

aa....aa: Protocol

Description: An attempt to acquire edition information has failed. Common library might not be installed. The processing continues.
Action: Confirm that the common library is installed.

KDJE42319-E

The required file or directory does not exists. (Path= aa....aa)

aa....aa: File path

Description: The file aa....aa under the application directory that was existing during import does not exist now.
Action: Restore the file or directory that exists on the path with an error when importing, and then re-execute the command.

KDJE42320-E

Deployment has abended. The JMS resource used in the application does not support transaction. (aa....aa)

aa....aa: Resource information

Description: The deployment process has abended. The JMS resource used in the application does not support transactions.
Action: Check the transaction level of the resource adapter. In this resource adapter, the transaction support levels that can be associated with the Message-driven Bean are the LocalTransaction and XATransaction.

KDJE42321-E

Deployment has abended. The transaction support level of the JMS resource is invalid.

Description: The deployment process has abended. The transaction support level of the JMS resource is invalid.
Action: Check the transaction level of the resource adapter.

KDJE42322-E

The application directory "aa....aa" does not have a deployment descriptor.

aa....aa: Application directory path

Description: The application directory does not have META-INF/application.xml.
Action: Create a META-INF/application.xml, and then re-import.

KDJE42323-E

The specified directory "aa....aa" is not empty.

aa....aa: Application directory path

Description: The directory that you tried to expand by specifying cjimportapp -d is not empty.
Action: Delete the files existing in the directory, and then re-import.

KDJE42324-E

The deployment directory format does not support in basic mode.

Description: An attempt was made to use the expanded archive format deployment functionality in the basic mode.
Action: Import to the J2EE server of 1.4 mode.

KDJE42325-E

The J2EE application having the same application directory "aa....aa" is already exists.

aa....aa: Application directory path or WAR directory path

Description

If a J2EE application having the same directory (as shown below) as an application directory or a WAR directory already exists in the J2EE server, a command execution error occurs:

Directory specified in the -a option or the -d option of the cjimportapp command
Directory specified in the -a option of the cjimportwar command

Action

Specify a different directory.

KDJE42326-E

The J2EE application "aa....aa" using an alt-dd element cannot be imported in a deployment directory format.

aa....aa: Application directory path, EAR file name or ZIP file name

Description: The user tried to import the application directory or EAR file or ZIP file with runtime information where alt-dd element is specified as application.xml.
Action: Edit the application.xml, delete the alt-dd element, and then re-import the application.

KDJE42327-E

The EJB-JAR having same display-name "aa....aa" exists in the J2EE application "bb....bb".

aa....aa: EJB-JAR display name

bb....bb: Application directory path

Description: The EJB-JAR display name contained in the application directory created by the user is duplicated.
Action: Change the EJB-JAR display name, and then re-import.

KDJE42328-E

The WAR having same display-name "aa....aa" exists in the J2EE application "bb....bb".

aa....aa: WAR display name

bb....bb: Application directory path

Description: The WAR display name contained in the application directory created by the user is duplicated.
Action: Change the duplicated WAR display name, and then re-import.

KDJE42329-E

The application directory cannot specified in UNC path. (path = aa....aa)

aa....aa: User-specified path

Description: UNC path was specified in cjimportapp -a/-d option argument.
Action: Do not specify the directory in UNC path.

KDJE42330-I

The JavaBeans resource "aa....aa" will now be imported.

aa....aa: JavaBeans resource display name

Description: The processing to import the JavaBeans resource is in progress.

KDJE42331-I

The JavaBeans resource "aa....aa" was imported successfully.

aa....aa: JavaBeans resource display name

Description: The JavaBeans resource was imported successfully.

KDJE42332-W

The J2EE application contains the application client. The application client is not supported.

Description

The J2EE application contains the application client. The application client is not supported.

Action

Delete the coding of <module><java> of application.xml in the J2EE application, and then re-package and import.

As a result of this action, the JAR file specified in <module><java> will be treated as a library JAR. The library JARs also exist in other JAR files, and if the same classes are included, delete the JAR file specified in <module><java>.

KDJE42333-I

The ignore J2EE annotations is specified.

Description: The functionality, for excluding the annotation references in the target J2EE application, will be enabled.

KDJE42334-W

The specified ignore J2EE annotations value is not supported. (value=aa....aa)

aa....aa: Specified value

Description: The functionality, for excluding the annotation references, will be disabled.
Action: true or false can be specified. Check if the specified value is a specifiable value.

KDJE42335-W

An element defined by a J2EE resource is not supported. (filename = aa....aa, element = bb....bb)

aa....aa: Deployment Descriptor for which an unsupported element is defined

In the case of the archive format: Archive file name or entry name

In the case of the expanded archive format: Relative path from the application directory

bb....bb: Unsupported element name

Description: The element (bb....bb) specified in aa....aa is an unsupported element. The element (bb....bb) will be ignored.
Action: Remove the element (bb....bb) specified in aa....aa.

KDJE42336-E

The file of the module does not exist. (file = aa....aa)

aa....aa: File name

Description: The module file (aa....aa) does not exist.
Action: Arrange the file according to the generation rules of the application directory, and then re-import the file.

KDJE42337-E

The "aa....aa" resource adapter cannot be included in the "bb....bb" J2EE application. (details = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

cc....cc: Details

Description

The resource adapter (aa....aa) cannot be included in the J2EE application.

The message displayed in the details and its cause are as follows:

The native library file.

The resource adapter includes the native library.
Tag name = transaction-support. Tag value = XATransaction.

The transaction-support tag is XATransaction.
The resource adapter is not supported.

The resource adapter is not supported.

Action

Take action based on the details.

The native library file.

Change to a supported resource adapter. Alternatively, deploy and use as a J2EE resource adapter.
Tag name = transaction-support. Tag value = XATransaction.

Change the value to NoTransaction or LocalTransaction. Alternatively, deploy and use as a J2EE resource adapter.
The resource adapter is not supported.

Change to a supported resource adapter. Alternatively, deploy and use as a J2EE resource adapter.

KDJE42338-E

"aa....aa" was not found in the "bb....bb" J2EE application.

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

Description: The resource adapter (aa....aa) is not found in the J2EE application (bb....bb).
Action: Revise the command parameters, and then re-execute the command.

KDJE42339-I

Recovery processing for the resource adapter will now start.

Description: The recovery process of the resource adapter will start.

KDJE42340-I

Recovery processing for the resource adapter has finished.

Description: The recovery process of the resource adapter has ended.

KDJE42341-E

The specified backup RAR directory is invalid. (backup RAR directory = aa....aa)

aa....aa: Backup RAR directory

Description: An invalid backup RAR directory (aa....aa) is specified.
Action: Revise the path specified for the backup RAR directory, and then re-execute the command.

KDJE42342-E

An attempt to copy the file from "aa....aa" to "bb....bb" has failed. (details = cc....cc)

aa....aa: Copy source file name

bb....bb: Copy destination file name

cc....cc: Details

Description: An attempt to copy from file aa....aa to file bb....bb has failed.
Action: Based on the details, remove the cause of the error, and then re-execute the command.

KDJE42343-W

The resource adapter in the J2EE server "aa....aa" is not recovered, because the resource adapter configuration has been changed.

aa....aa: The J2EE server name

Description: The resource adapter in the J2EE server (aa....aa) is not recovered because the resource adapter configuration is changed.

KDJE42344-E

This application could not be imported in test mode.

Description: This application cannot be imported in the test mode.
Action: Import without specifying the test mode.

KDJE42345-E

An invalid value is specified for the tag in the deployment descriptors in the resource adapter. (resource adapter = aa....aa, tag name = bb....bb, tag value = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Tag name

cc....cc: Tag value

Description: An invalid value is specified for a tag in the Deployment Descriptor of the resource adapter (resource adapter = aa....aa, tag name = bb....bb, tag value = cc....cc).
Action: Check the tag value, and then re-execute the command.

KDJE42346-E

The aa....aa with the same display name already exists in the J2EE application. (display name = bb....bb, J2EE application = cc....cc)

aa....aa: Resource type

bb....bb: Resource display name

cc....cc: Path of the J2EE application directory

Description: The aa....aa with the same display name already exists in the J2EE application (display name = bb....bb, J2EE application = cc....cc).
Action: Change the display name of bb....bb, and then re-import.

KDJE42347-I

The resource adapter in the J2EE application will now start. (resource adapter = aa....aa, J2EE application = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

Description: The resource adapter in the J2EE application will start (resource adapter = aa....aa, J2EE application = bb....bb).

KDJE42348-I

The resource adapter in the J2EE application started successfully. (resource adapter = aa....aa, J2EE application = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

Description: The resource adapter in the J2EE application has started successfully (resource adapter = aa....aa, J2EE application = bb....bb).

KDJE42349-I

The resource adapter in the J2EE application will now stop. (resource adapter = aa....aa, J2EE application = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

Description: The resource adapter in the J2EE application will stop (resource adapter = aa....aa, J2EE application = bb....bb).

KDJE42350-I

The resource adapter in the J2EE application stopped successfully. (resource adapter = aa....aa, J2EE application = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

Description: The resource adapter in the J2EE application has stopped successfully (resource adapter = aa....aa, J2EE application = bb....bb).

KDJE42351-E

An attempt to delete the file has failed. (file name = aa....aa)

aa....aa: File name

Description: An attempt to delete the file (aa....aa) has failed.
Action: Re-execute the command.

KDJE42352-E

An attempt to set the execution authority of the file has failed. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Detailed message

Description: An attempt to set up the execution permission for the file has failed (file name = aa....aa, details = bb....bb).
Action: Based on the details, resolve what caused the error in execution permission settings, and then re-execute the command.

KDJE42353-I

The connection test for the resource adapter in the J2EE application will now be performed. (resource adapter = aa....aa, J2EE application = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

Description: A connection test will be performed for the resource adapter of the J2EE application (resource adapter = aa....aa, J2EE application = bb....bb).

KDJE42354-I

The connection test for the resource adapter in the J2EE application has finished. (resource adapter = aa....aa, J2EE application = bb....bb, test result = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

cc....cc: Test result

Description: The connection test for the resource adapter in the J2EE application is complete (resource adapter = aa....aa, J2EE application = bb....bb, test result = cc....cc).

KDJE42355-W

The command lock cannot be released, because the command operation has been executed in J2EE server. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time = dd....dd)

aa....aa: Name of the command that is now running

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description

The command exclusion cannot be released because the command processing is executed in the J2EE server.

Action

Check if the command processing is executed in the J2EE server.

If the command processing is executed in the J2EE server, wait until the processing finishes. If the command exclusion is not released even when the processing finishes, execute the cjresetsv command again.

If the command processing is not executed in the J2EE server or if the command exclusion cannot be released even when the cjresetsv command is executed after sometime, contact maintenance personnel.

KDJE42356-E

The resource adaptor based on the Connector 1.5 specification was specified. (RAR file = aa....aa)

aa....aa: RAR file name

Description: A resource adapter conforming to Connector 1.5 specifications was specified (RAR file = aa....aa).
Action: Specify a resource adapter conforming to the Connector 1.0 specifications. When upgrading the version of a resource adapter conforming to the Connector 1.5 specifications, re-import the resource adapter, and reset the definition.

KDJE42357-W

The value of mappedName is invalid. (EJB-JAR = aa....aa, Enterprise Bean = bb....bb, annotation = cc....cc, value = dd....dd)

aa....aa: EJB-JAR display name

bb....bb: Enterprise Bean display name

cc....cc: Annotation type

dd....dd: Value

Description: The value of mappedName is invalid (EJB-JAR = aa....aa, Enterprise Bean = bb....bb, annotation = cc....cc, value = dd....dd).
Action: Check if the optional name specified in the mappedName attribute of @Stateless or @Stateful is a specifiable character string.

KDJE42358-W

The value of mappedName is invalid. (J2EE application = aa....aa, EJB-JAR = bb....bb, Enterprise Bean = cc....cc, annotation = dd....dd, value = ee....ee)

aa....aa: Display name of the J2EE application

bb....bb: EJB-JAR display name

cc....cc: Enterprise Bean display name

dd....dd: Annotation type

ee....ee: Value

Description: The value of mappedName is invalid (J2EE application = aa....aa, EJB-JAR = bb....bb, Enterprise Bean = cc....cc, annotation = dd....dd, value = ee....ee).
Action: Check if the optional name specified in the mappedName attribute of @Stateless or @Stateful is a specifiable character string. Alternatively, specify the optional name in the <optional-name> tag or the <local-optional-name> tag of the property file.

KDJE42359-E

Deployment has ended. An attempt to check the reference to the resource adapter in the J2EE Application "aa....aa" failed. (details = bb....bb)

aa....aa: J2EE application name

bb....bb: Details

Description

The deployment process has abended. An attempt to check the referencing of the resource adapter in the J2EE Application aa....aa has failed. Details = bb....bb

Action

Take action based on the detailed message. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

Not resolve resource adapter.: The display name of the resource adapter is not specified. Revise the MessageDrivenBean property file.
Not exist resource adapter.: The resource adapter cannot be found. Make sure that the resource adapter coded in the MessageDrivenBean property file is already deployed.
Not start resource adapter.: The resource adapter is not started. Make sure that the resource adapter coded in the MessageDrivenBean property file is already running.

KDJE42360-E

The path specified for the library directory is invalid. (library directory = aa....aa)

aa....aa: Library directory

Description

A file is specified in the path of the library directory.

Action

Specify a directory instead of a file in the library directory.

When the <library-directory> tag of the application.xml file or the application.xml file is omitted, the library directory will become lib.

KDJE42361-E

aa....aa cannot be included in the J2EE application. (J2EE application (name = bb....bb, version = cc....cc), aa....aa (name = dd....dd, version = ee....ee))

aa....aa: Resource type

bb....bb: Display name of the J2EE application

cc....cc: Version of the J2EE application

dd....dd: Resource display name

ee....ee: Resource version

If a Deployment Descriptor does not exist in the resource, a hyphen (-) will be displayed in the resource display name ee....ee.

Description: The resource type aa....aa (name = dd....dd, version = ee....ee) cannot be included in the J2EE application (name = bb....bb, version = cc....cc).
Action: Revise the combination of the J2EE application version and the resource version.

KDJE42362-E

The value of <module> is invalid. (module = aa....aa)

aa....aa: Value specified in the <module> tag

Description: A file that exists below the library directory was specified in the <module> tag.
Action: The JAR file in the library directory cannot be specified in the <module> tag of the file application.xml. Revise the configuration of the J2EE application.

KDJE42363-E

The value of <module> is invalid. (module = aa....aa)

aa....aa: Value specified in the <module> tag

Description: The EJB-JAR directory or WAR directory determined from the <module> tag or the files below these directories configure the library directory.
Action: Revise the configuration of the J2EE application in such a way so that the EJB-JAR directory or the WAR directory, or the files below these directories do not configure the library directory.

KDJE42364-E

The value of the aa....aa tag is invalid. (value = bb....bb)

aa....aa: Tag name

bb....bb: Value specified in the tag

Description: An invalid value is specified in a tag of application.xml when importing in the expanded archive format.
Action: Specify a permitted value in the tags of application.xml.

KDJE42365-E

The existence of the file aa....aa differs before and after the replacement. (archive file = bb....bb)

aa....aa: Deployment Descriptor file name

bb....bb: Archive file name

Description: The existence of aa....aa file is not coincident before and after the replacement do not match.
Action: After comparing the archive files and revising the J2EE application in such a way so that the existence of the Deployment Descriptor is matching, re-execute the command. If you cannot modify, import the configuration after deleting the J2EE application to be replaced.

KDJE42366-E

A resource cannot be added to a J2EE application where the application.xml is not present. (J2EE application = aa....aa, resource = bb....bb, type = cc....cc, resource file = dd....dd)

aa....aa: Display name of the J2EE application

bb....bb: Resource display name

cc....cc: Resource type

dd....dd: Resource file name

Description

A resource cannot be added to a J2EE application in which application.xml does not exist.

Action

Add a file with an extension corresponding to the resource type in a J2EE application in which application.xml does not exist.

In the case of an EJB-JAR file, the extension is .jar
In the case of a WAR file, the extension is .war
In the case of a RAR file, the extension is .rar

KDJE42367-W

The context root determined from the WAR file or directory is duplicated. (path1 = aa....aa, path2 = bb....bb, context root = cc....cc)

aa....aa: Path to the WAR file or WAR directory

bb....bb: Path to the WAR file or WAR directory

cc....cc: Context root

Description: The context root determined from the path to the WAR file or WAR directory is duplicated.
Action: Change the context root. Change the path to the WAR file or WAR directory in such a way so that the context root is not duplicated.

KDJE42368-I

The file cosminexus.xml will now be loaded.

Description: The file cosminexus.xml will be read.

KDJE42369-E

The format of the file cosminexus.xml is invalid. (Detail = aa....aa)

aa....aa: Exception information when reading fails

Description: An attempt to read the file cosminexus.xml has failed because of invalid format.
Action: The format of the file cosminexus.xml is invalid. Check if the tag configuration of the file cosminexus.xml is correct.

KDJE42370-W

An element specified in the file cosminexus.xml was not found. This element has been ignored. (element = aa....aa, value = bb....bb)

aa....aa: Element name

bb....bb: Element value

Description: Information corresponding to the element specified in cosminexus.xml is not found in the application. The set value of this element will be ignored.
Action: An element, that cannot be included in the application, is specified in cosminexus.xml. Check the cosminexus.xml file contents.

KDJE42371-E

The specified value is invalid. (element = aa....aa, value = bb....bb)

aa....aa: Element name

bb....bb: Value of the element (Nothing will be output if the value is a space. Null will be output if the element is omitted).

Description: An error exists in the element specified in cosminexus.xml.
Action: An invalid element is specified in the file cosminexus.xml included in the application. Revise the set value of the element aa....aa of the file cosminexus.xml.

KDJE42372-I

The file cosminexus.xml has been loaded.

Description: The reading of the file cosminexus.xml is complete.

KDJE42373-E

The metadata-complete attribute in the deployment descriptor in the EJB-JAR file cannot be set to "true". (J2EE application = aa....aa, EJB-JAR = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjimportres command)

bb....bb: EJB-JAR display name

Description: True cannot be specified in the attribute metadata-complete of the Deployment Descriptor of EJB-JAR.
Action: Either specify false in the attribute metadata-complete of the Deployment Descriptor of EJB-JAR or delete the attribute metadata-complete.

KDJE42374-W

The specified display name includes non-recommended characters. (display name = aa....aa, resource type = bb....bb)

aa....aa: Display name

bb....bb: Type (J2EE Application, EJB-JAR, WAR, RAR, Enterprise Bean, Servlet or JSP, or Filter)

Description

In a J2EE server, the display name set up in the J2EE application and resource (value of the <display-name> tag of the Deployment Descriptor) is used as an identifier. When importing a WAR file in which <servlet><display-name> does not exist, the display name is set up from the <servlet><servlet-name> value.

However, this message is displayed because you can specify a period in <servlet><display-name>; however the conversion to underscore (_) does not occur.

When this message is displayed, errors might occur in another processing.

Action

Change the display name of the J2EE Application, EJB-JAR, Web application, or resource adapter or change the display name of the Enterprise Bean, Servlet or JSP, or Filter included in to the character strings having only the single-byte alphanumeric characters and underscores (_).

KDJE42375-W

An interceptor-class specified in the file deployment descriptor was not found. This interceptor-class has been ignored. (ejb-jar name = aa....aa, interceptor-class = bb....bb)

aa....aa: EJB-JAR name

bb....bb: Interceptor class name

Description: The interceptor class specified in the Deployment Descriptor was not found.
Action: Specify an existing interceptor class.

KDJE42376-E

The specified interceptor-class was not found. (ejb-jar name = aa....aa, interceptor-class = bb....bb)

aa....aa: EJB-JAR name

bb....bb: Interceptor class name

Description: The specified interceptor class was not found. An interceptor class that actually exists must be specified.
Action: Revise the configuration of the application in such a way so that the interceptor class is included in the EJB-JAR or library JAR.

KDJE42377-W

An element was specified more than once. This element has been ignored. (element = aa....aa, value = bb....bb)

aa....aa: Element name

bb....bb: Element value

Description: More than one instance of the definition information exists for the same element. The first definition of the element found in the Deployment Descriptor is used. The value bb....bb of the element aa....aa is not used.
Action: Delete the unnecessary definition information.

KDJE42378-E

A module was not found in a J2EE application. (J2EE application = aa....aa)

aa....aa: Path to the EAR file or application directory

Description: A module was not found in the J2EE application.
Action: Make sure that the module is included in the J2EE application.

KDJE42379-W

The file cosminexus.xml has not been reloaded (application name = aa....aa).

aa....aa: Application name

Description: The definition information is not reloaded even when the file cosminexus.xml is changed.
Action: When the definition information of the file cosminexus.xml is to be applied in the application, restart the application after stopping it.

KDJE42380-W

There exist one or more classes from which annotation information could not be collected. (name = aa....aa, failure count = bb....bb)

aa....aa: File name or J2EE application display name

bb....bb: Number of times when information could not be collected

Description: The annotation information could not be collected for one or more classes (name = aa....aa, failure count = bb....bb).
Action: If java.lang.NoClassDefFoundError is output in the KDJE90001-E message, and a problem exists in the execution of the J2EE application, either revise the J2EE application or change the settings of the J2EE server in such a way so that the class output in the detailed message of java.lang.NoClassDefFoundError can be referenced from the J2EE application.

KDJE42385-W

The specified method was not found. (ejb name = aa....aa, method name = bb....bb, method parameters = cc....cc)

aa....aa: EJB name

bb....bb: Method name

cc....cc: Parameter format^#

# Output the parameters in the following format:

When <method-param> does not exist

A null character string ("")
When <method-param> exists

A character string in which the value of all the <method-param> tags is connected by commas (,)

Description

The method is not defined.

Action

Revise the definition information of the <method> tag.

KDJE42386-E

A file operation on a resource adapter management file of the J2EE server has failed. (operation = aa....aa, details = bb....bb)

aa....aa: Failed operation (any one of write, read, delete, or rename)

bb....bb: Exception information (none, if no exception information exists)

Description

An attempt to operate the file, that manages the status of the resource adapter below the work directory for the J2EE server, has failed.

Action

The action to be taken will differ depending on the operation performed during the occurrence of the error:

When an error occurred in the database node during the cluster configuration of the connection pool

Remove the cause of failure in the file operation by referencing the details. After removing the cause of the problem, restart the J2EE server.
When a resource adapter is deployed

Remove the cause of failure in the file operation by referencing the details. After removing the cause of the problem, restart the J2EE server. After restarting the J2EE server, check if the resource adapter exists. If the resource adapter does not exist, re-deploy it. If the resource adapter exists, check if the executed operation was successful.
When the migration command (cjenvupdate) of the J2EE server is executed

Remove the cause of failure in the file operation by referencing the details. Remove the cause of the error, and then re-execute the operation.
In cases other than above

Remove the cause of failure in the file operation by referencing the details. After removing the cause of the problem, restart the J2EE server. After restarting the J2EE server, check if the executed operation was successful.

KDJE42387-E

The entry name in the EAR file is invalid. (entry name = aa....aa, EAR file = bb....bb)

aa....aa: Entry name

bb....bb: EAR file name

Description: The entry name in the EAR file is invalid.
Action: The entry name in the EAR file indicates a higher level than the root of the application package. Change to an entry name that indicates a lower level than the root of the application package.

KDJE42388-E

The resource adapter not supported in the edition. (resource adapter = aa....aa, edition = bb....bb)

aa....aa: Display name of resource adapter

bb....bb: Edition

Description: The specified resource adapter cannot be used in this edition.
Action: Check the resource adapter document, and then use the resource adapter with a supported edition.

KDJE42389-E

The entry name in component is invalid. (entry name = aa....aa, file = bb....bb, component type = cc....cc)

aa....aa: Entry name

bb....bb: File name

cc....cc: Component type

Description: The entry name in the component is invalid.
Action: The entry name in the component indicates a higher location than the root directory. Change to an entry name indicating a lower location than the root directory.

KDJE42390-E

The start of the application containing a Web Service EJB failed. Root context-root is already used. (application name = aa....aa)

aa....aa: Display name of the application

Description: The EJB of the Web Service cannot be deployed in the context root of the root. Another J2EE application might be using the context root of the root.
Action: Make sure that the application that is using the context root of the root does not already exist. If such an application exists, change the context root so that it is not duplicated.

KDJE42391-I

Working directory for Web Service EJB is created.

Description: A work directory required for executing the EJB of the Web Service is created successfully.

KDJE42392-E

An attempt to create the directory (aa....aa) has failed.

aa....aa: Directory name

Description

An attempt to create the (aa....aa) directory has failed.

Action

The possible causes of the error are described below. If the cause is not clear, obtain the maintenance information, and then contact Maintenance Service.

Failure of the disk drive: If the disk drive has failed due to breakage of the disk drive, contact the system administrator and replace the drive.
Insufficient disk space: Secure enough disk space.
No access permission: Assign access permission.
Characters that cannot be used are used in the path name: Do not use characters that cannot be used in the path name.
The length of the file path is inappropriate: Make sure that the total number of characters of the absolute path length in which the application in the exploded archive format is deployed, the path delimiter (one character), and the relative path length specified in the webservice.container.jaxws.webservice.wsee.warname key of the user property file (usrconf.properties) is 255 characters or less.

KDJE42393-W

The J2EE application contains a aa....aa. Automatic reloading and partial reloading cannot be performed. (J2EE application name = bb....bb)

aa....aa: Component type

bb....bb: J2EE application name

Description: Automatic reloading and partial reloading cannot be used in this J2EE application.
Action: To use the reload functionality, use the cjreloadapp command.

KDJE42394-E

The J2EE application contains a aa....aa. Partial reloading cannot be performed. (J2EE application name = bb....bb)

aa....aa: Component type

bb....bb: J2EE application name

Description: Partial reloading cannot be used in this J2EE application.
Action: To switch the J2EE application, delete the application once. If you want to use the reload functionality, specify app in the property ejbserver.deploy.context.reload.scope.

KDJE42395-I

The J2EE application contains a aa....aa. All of the application components were reloaded. (J2EE application name = bb....bb)

aa....aa: Component type

bb....bb: J2EE application name

Description: All the components included in the application were reloaded.

KDJE42396-E

Test mode cannot be used in CDI applications. (J2EE application name = aa....aa)

aa....aa: J2EE application name

Description: Test mode cannot be used in CDI applications.
Action: Change the operation mode of the J2EE application to a normal mode.

KDJE42397-W

The WebServlet annotation will be ignored because the value set for the name attribute is already set for another WebServlet annotation. (WAR file = aa....aa, class name = bb....bb)

aa....aa: WAR file name

bb....bb: Class name describing the @WebServlet annotation

Description: The @WebServlet annotation will be ignored because the name attribute value in the @WebServlet annotation is duplicated in another @WebServlet annotation.
Action: Change the value of the name attribute in the @WebServlet annotation so that the value is not duplicated in another @WebServlet annotation.

KDJE42398-W

The WebFilter annotation will be ignored because the value set for the filterName attribute is already set for another WebFilter annotation. (WAR file = aa....aa, class name = bb....bb)

aa....aa: WAR file name

bb....bb: Class name describing the @WebFilter annotation

Description: The @WebFilter annotation will be ignored because the filterName attribute value in the @WebFilter annotation is duplicated in another @WebFilter annotation.
Action: Change the value of the filterName attribute in the @WebFilter annotation so that the value is not duplicated in another @WebFilter annotation.

KDJE42399-W

The class file contains one or more generic methods or generic constructors. (class name = aa....aa)

aa....aa: Class name

Description

One or more generic methods or generic constructors are used in the class file contained in the application.

Action

The use of annotations for the application server is not supported for generic methods or generic constructors.

Do not use generics in the class displayed in the message. Alternatively, delete the annotation. There is no problem if the application server does not use the corresponding annotation in this class.

KDJE42400-E

The WAR application does not support the command. (command name = aa....aa)

aa....aa: Command name

Description: The WAR application does not support this command.
Action: Delete the WAR application, import a J2EE application with EAR format, and then execute the J2EE application.

KDJE42401-E

The WAR application does not support a command option. (command name = aa....aa)

aa....aa: Command name

Description: The WAR application does not support the option of this command.
Action: Delet the WAR application, import a J2EE application, and then execute the J2EE application.

KDJE42402-W

The application name was sanitized. (application name = aa....aa)

aa....aa: Application name

Description: When the cjimportwar command is executed, if the -name option is omitted; the WAR file/WAR directory name becomes the application name. Therefore, for the application name, the characters that cannot be used in the WAR file/WAR directory are replaced with underscores.
Action: When executing the server management commands for imported a WAR application, execute the cjlistapp command, and specify the application name to be output, in the -name option, and then execute the command.

KDJE42403-W

The context root was sanitized. (context root = aa....aa)

aa....aa: Application name

Description: When the cjimportwar command is executed, if the -contextroot option is omitted; the WAR file/WAR directory name becomes the context root. Therefore, for the context root of J2EE server, the characters that cannot be used in the WAR file/WAR directory are replaced with underscores.
Action: When accessing the imported WAR application, execute the cjlistapp command, and confirm the context root to be output.

KDJE42404-I

The war directory aa....aa will now be imported.

aa....aa: WAR directory path

Description: Import the WAR directory aa....aa.

KDJE42405-I

The war directory aa....aa was imported successfully.

aa....aa: WAR directory path

Description: WAR directory aa....aa is successfully imported.

KDJE42406-E

The J2EE application that has the upper directory of the directory aa....aa already exists.

aa....aa: Application directory path or WAR directory path

Description

If the J2EE application that has the upper most directory of the below directory as the application directory or the WAR directory already exists in the J2EE server, an error occurs in the command execution:

Directory specified in the -a option or the -d option of the cjimportapp command
Directory specified in the -a option of the cjimportwar command

Action

Check that the path of the application directory or WAR directory is not included in the directory (application directory or WAR directory) that is included in the J2EE application already existing in the J2EE server, and then specify an appropriate directory.

KDJE42407-E

The war directory cannot specified in UNC path. (path = aa....aa)

aa....aa: User specified path

Description: If the UNC path is specified in the -a option of the cjimportwar command, import fails.
Action: Do not specify the UNC path in the -a option of the cjimportwar command.

KDJE42408-E

The specified directory aa....aa is invalid.

aa....aa: Path of the user specified directory

Description: If the directory immediately below the Windows drive (such as C:\) or the root directory (/) in UNIX is specified in the -a option of the cjimportwar command, the import has fails.
Action: Specify a directory that is not immediately below the Windows drive or the root directory in UNIX.

KDJE42410-E

The J2EE application that has the lower directory of the directory aa....aa already exists.

aa....aa: Application directory path or WAR directory path

Description

If the J2EE application that has the lower most directory of the directory below as the application directory or the WAR directory already exists in the J2EE server, an error occurs in the command execution:

Directory specified in the -a option or the -d option of the cjimportapp command
Directory specified in the -a option of the cjimportwar command

Action

Check that the path of the application directory or WAR directory is not included in the directory (application directory or WAR directory) that is included in the J2EE application already existing in the J2EE server, and then specify an appropriate directory.

KDJE43001-E

Error occurred during generating SQL for aa....aa.

aa....aa: EJB class name

Description: An error occurred during generating SQL for aa....aa. Table mapping is wrong.
Action: Check the access to database and correct the table mapping.

KDJE43002-E

JMS Provider(TP1 Message Queue) notified an error to Message-driven Bean container. bean=aa....aa error message=bb....bb

aa....aa: Bean name

bb....bb: Error information of the JMS provider

Description: The Message-driven Bean container detected an error from the JMS provider.
Action: Reference the error information, and remove the cause of the error in the TP1/Message Queue.

KDJE43003-E

Failed to create CMR DB Table : aa....aa.

aa....aa: Display name of DB

Description: An attempt to create the table (aa....aa) for CMR failed.
Action: See the error information displayed in the database together with this message, and then remove the cause of the failure to create the table. For the details on the error information displayed in the database, see the manual supplied with the database products.

KDJE43004-E

Failed to generate SQL for CMR table creation. CMR table name is already used. : aa....aa

aa....aa: Display name of DB

Description: An attempt to generate SQL for CMR table creation has failed because the database table name is already in use.
Action: Re-execute SQL generation.

KDJE43005-E

Failed to generate SQL for CMR table creation. Two Entity Beans participating in a particular relationship must be on the same DB product.

Description: An attempt to generate SQL for CMR table creation has failed because the Entity Beans participating in a particular relationship with CMR are on the database of different DB products.
Action: Create a table corresponding to the Entity Beans on the database of the same DB products.

KDJE43006-I

CMR DB Table: aa....aa is verified.

aa....aa: Display name of DB

Description: CMR Table aa....aa is verified.

KDJE43007-I

CMR DB Table: aa....aa is created successfully.

aa....aa: Display name of DB

Description: CMR table aa....aa is created successfully.

KDJE43008-E

Failed to verify CMR DB Table: aa....aa.

aa....aa: Display name of DB

Description: An attempt to verify CMR table aa....aa has failed.
Action: Redeploy the table. However, after redeploying, a new table is created but the used CMR information is lost.

KDJE43009-I

CMR DB Table: aa....aa is deleted successfully.

aa....aa: Display name of DB

Description: CMR table aa....aa is deleted successfully.

KDJE43010-W

CMR DB Table: aa....aa is not deleted. Table has already been deleted or format has been changed.

aa....aa: Display name of DB

Description

CMR table aa....aa cannot be deleted.

The table might be already deleted or the table format might be changed.

Action

Confirm that the table is not shared or deleted when the application is running.

KDJE43011-E

Failed to delete CMR DB Table: aa....aa.

aa....aa: Display name of DB

Description: An attempt to delete the CMR Table aa....aa has failed.
Action: When an unnecessary table remains on the database, delete it manually.

KDJE43012-E

An error occurred when creating ORB/POA. (error details = aa....aa)

aa....aa: Exception message (Exception information of Cosminexus TPBroker is mainly output)

Description

An error occurred while creating ORB/POA.

When performing the operation by fixing the communication port and IP address, the environment might not be set properly.

Action

Revise the value of vbroker.se.iiop_tp.host key and vbroker.se.iiop_tp.scm.iiop_tp.listener.port key of user property file according to the message displayed in aa....aa, and then restart the J2EE server.

Revise the values from the following viewpoint:

Does the specified port number overlap with the port number that is being used?
Is the specified port number an invalid numeric value such as a negative value and a value out of range?
Is the specified value of fixed IP address correct in terms of the IP address format?
Is a space entered before and after the specified value?

KDJE43050-E

Unexpected error occurred during deploying Stateful Session Bean.

Description: An error occurred during deploying Stateful Session Bean.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE43051-E

Unexpected error occurred during deploying CMP Entity Bean. Bean = aa....aa, Detail = bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description: An error occurred during deploying CMP Entity Bean.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43052-E

An error occurred during deploying Message Driven Bean. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description: An error occurred during the deployment of the Message Driven Bean.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43053-E

An error occurred during loading home interface or component interface. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description: An error occurred during loading home interface or component interface.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43054-E

Failed to create object which is necessary for EJB. Detail = aa....aa.

aa....aa: Details

Description: An attempt to create an object necessary for the internal processing of EJB, has failed.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43055-E

Failed to instantiate EJBHome object. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description: An attempt to instantiate the EJBHome object has failed.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43056-E

Unexpected error occurred during instantiating EJBObject.

Description: An unexpected error occurred during instantiating the EJBObject.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE43057-E

Failed to create object which is necessary for Stateful Session Bean. Detail = aa....aa.

aa....aa: Details

Description: An attempt to create the object necessary for internal processing of the Stateful Session Bean, has failed.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43058-E

Failed to create EJB-specific namespace. Bean = aa....aa.

aa....aa: Bean name

Description

An attempt to create the EJB-specific namespace has failed.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE43059-E

Failed to register EJB to namespace. Bean = aa....aa, Type = bb....bb.

aa....aa: Bean name

bb....bb: type of namespace

Description

An attempt to register an EJB to namespace has failed.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE43060-E

Failed to instantiate Stateless Session Bean. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description: An attempt to instantiate the Stateless Session Bean has failed.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43061-E

An exception occurred in callback method aa....aa.bb....bb. Detail = cc....cc.

aa....aa: Bean name

bb....bb: Callback method name

cc....cc: Details

Description: An exception occurred in the user code that was called back due to extended instance-generation in Stateless Session Bean or Singleton Session Bean.
Action: See the method information and the details described in the message, and remove the cause of exception.

KDJE43062-E

Failed to instantiate Entity Bean. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description: An attempt to instantiate the Entity Beans has failed.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43063-E

An exception occurred in callback method aa....aa.bb....bb Detail = cc....cc.

aa....aa: Bean name

bb....bb: Callback method name

cc....cc: Details

Description: An exception occurred in the user code called back as an extension of generating instances for Entity Bean.
Action: See the method information and the details described in the message, and remove the cause of exception.

KDJE43064-E

Failed to create MDB container. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description: An attempt to create MDB container has failed.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43065-E

An exception occurred in callback method aa....aa.bb....bb. Detail = cc....cc.

aa....aa: Bean name

bb....bb: Callback method name

cc....cc: Details

Description: An exception occurred in the user code called back as an extension of generating instances for Message Driven Bean.
Action: See the method information and the details described in the message, and remove the cause of exception.

KDJE43066-E

Failed to connect to JMS service. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description

An attempt to connect to JMS service has failed.

The status of the resource adapter might be invalid.

Action

Restart the resource adapter, and then redeploy the J2EE application.

KDJE43067-E

Unexpected error occurred during generating stubs for bean interface. Detail = aa....aa.

aa....aa: Details

Description: An unexpected error occurred during generating the stubs for bean interface.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43068-E

Unexpected error occurred during creating implementation for bean. Detail = aa....aa.

aa....aa: Details

Description: An unexpected error occurred during creating the implementation class for bean.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43069-E

Unexpected error occurred during compiling container generated java source files. Detail = aa....aa.

aa....aa: Details

Description: An unexpected error occurred during compiling the generated Java source files.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43070-E

Unexpected error occurred during deploying EJB. Detail = aa....aa.

aa....aa: Details

Description: An unexpected error occurred during deploying the EJB.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43071-E

Unexpected error occurred during starting EJB. Detail = aa....aa.

aa....aa: Details

Description: An unexpected error occurred during EJB startup.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43072-I

J2EE Server connecting to CTM...

Description

The J2EE Server is connecting to CTM.

When the CTM functionality is installed in Enterprise Edition and ejbserver.ctm.enabled=true, the J2EE Server establishes connection with CTM and initializes during start-up. When the J2EE Server fails to establish connection with CTM and initialize, the J2EE server cannot be started.

Action

When the CTM functionality is not required and if you want to start the J2EE server, start it with ejbserver.ctm.enabled=false.

KDJE43073-I

No CTM mode: CTM initialization skipped. To deploy CTM application, start J2EE Server with CTM mode.

Description

CTM initialization was skipped.

When ejbserver.ctm.enabled=false, the J2EE Server will not connect to CTM and initialize during start-up. The application that uses CTM cannot be deployed in the J2EE Server started in this state.

Action

In order to deploy an application that uses CTM, set ejbserver.ctm.enabled=true (CTM integration is enabled) and start the J2EE Server.

KDJE43074-E

Failed to start CTM mode. If CTM function is not necessary, start J2EE Server with No CTM mode.

Description

An attempt to start in the CTM mode has failed.

If an attempt to connect to CTM and initialize fails, the J2EE Server will fail to start.

Action

If you want to use the CTM functionality, confirm that CTM is running and that the properties required for connecting to CTM are set, and then restart the J2EE Server.

When the CTM functionality is not required and if you want to start the J2EE Server, set ejbserver.ctm.enabled=false and start the J2EE Server.

KDJE43075-E

Failed to create object necessary for finder/select method of Entity Bean. Bean = aa....aa, Method = bb....bb, Detail = cc....cc.

aa....aa: Bean name

bb....bb: Method name

cc....cc: Details

Description: An attempt to create an object necessary for the execution of the finder or select method of Entity Bean has failed.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43076-E

Failed to get object necessary to generate SQLs. Detail = aa....aa.

aa....aa: Details

Description

An attempt to acquire the object of the J2EE server required to generate SQLs has failed.

The J2EE server might not be running properly.

Action

Confirm that the J2EE server is running. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43077-E

Failed to connect to J2EE Server. Detail = aa....aa

aa....aa: Details

Description

An error occurred when communicating with the J2EE Server.

The J2EE server might not be running properly.

Action

Confirm that the J2EE server is running. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43078-E

Failed to parse EJB QL. Detail = aa....aa

aa....aa: Details

Description

An attempt to generate an SQL from EJB QL has failed.

An error exists in the syntax of EJB QL.

Action

See the details, and then modify EJB QL.

KDJE43079-E

Unexpected error occurred during generating SQLs for CMP Entity Bean. Detail = aa....aa

aa....aa: Details

Description: An unexpected error occurred during generating SQLs for CMP Entity Bean.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43080-I

Pass-by-reference is defined. Bean: aa....aa.

aa....aa: Bean name

Description: Pass-by-reference is defined in Bean.

KDJE43081-E

Cannot set Entity Bean as CTM Bean.

Description: The Entity Bean cannot be set as a CTM Bean because the CTM functionality does not support Entity Beans.
Action: Do not use a CTM in the Entity Bean.

KDJE43082-E

Cannot set Message Driven Bean as CTM Bean.

Description: The Message Driven Bean cannot be set as a CTM Bean because the CTM functionality does not support Message Driven Bean.
Action: Do not use a CTM in the Message Driven Bean.

KDJE43083-E

Cannot set Stateful Session Bean as CTM Bean.

Description: The Stateful Session Bean cannot be set as a CTM Bean because the CTM functionality does not support Stateful Session Bean.
Action: Do not use a CTM in the Stateful Session Bean.

KDJE43084-E

aa....aa: Pooled instances max value should be more than Parallel Count.

aa....aa: Bean name

Description: A value greater than the max value of Pooled instance cannot be set in Parallel Count because Bean instances will become insufficient.
Action: Set the max value of Pooled instances to a value greater than the Parallel Count.

KDJE43085-E

Exception occurred in registering aa....aa with queue:bb....bb. cc....cc not found in NameSpace.

aa....aa: Bean name

bb....bb: Queue name

cc....cc: Bean name

Description

An error occurred in registering aa....aa with queue (bb....bb).

cc....cc was not found in Name Space.

Action

Confirm that the local CORBA naming service is running, and then redeploy.

KDJE43086-E

Exception occurred in registering aa....aa with queue:bb....bb. cc....cc HomeObject not found.

aa....aa: Bean name

bb....bb: Queue name

cc....cc: Bean name

Description

An attempt to acquire the EJBHomeObject reference while deploying the Bean with the specified CTM scheduling, failed.

An unusual error occurred.

Action

Contact the maintenance personnel.

KDJE43087-E

J2EE Server: No CTM mode. Restart J2EE Server after starting CTM.

Description

The J2EE Server is running in the No CTM mode.

CTM is not running. CTM must be running to use the scheduling functionality of CTM.

Action

Confirm that CTM is running, and then restart the J2EE Server.

KDJE43088-E

No CTM bean in aa....aa. More than one bean should be scheduling-enabled.

aa....aa: Application name

Description

No CTM Bean exists in the application (aa....aa).

More than one CTM Bean needs to be set.

Action

Set Enable scheduling for more than one Stateless Session Bean.

KDJE43089-E

Exception occurred in creating queue:aa....aa. CTM API MSG=bb....bb

aa....aa: Queue name

bb....bb: Detailed message

Description: An attempt to create queue (aa....aa) has failed.
Action: Take action based on the contents of the details.

KDJE43090-E

Number Format Exception: Parallel Count=aa....aa.

aa....aa: Parallel Count

Description: Number Format Error occurred because the numeric value is not entered for Parallel Count.
Action: Enter a numeric value in the specified range.

KDJE43091-E

Exception occurred in activating queue:aa....aa. CTM API MSG=bb....bb

aa....aa: Queue name

bb....bb: Detailed message

Description: An error occurred in activating the queue (aa....aa).
Action: Take action based on the contents of the details.

KDJE43092-I

CTM mode: CTM connection established.

Description

CTM connection is established and the J2EE Server is started in the CTM mode.

To deploy an application in which CTM usage is specified, the J2EE server must be started in the CTM mode.

KDJE43093-E

Failed to start CTM mode: Internal Error.

Description: An attempt to start the CTM mode has failed.
Action: Contact the maintenance personnel.

KDJE43094-E

Failed to start CTM mode: CTM not installed properly.

Description: The CTM functionality might not be installed or might not be installed properly.
Action: Confirm that CTM is installed properly. If CTM is not installed properly, re-install it.

KDJE43095-I

CTM mode stopped. J2EE Server disconnected CTM.

Description

The CTM mode is stopped.

The J2EE server is disconnected from CTM.

This message is displayed when the J2EE Server started in the CTM mode is stopped normally because the connection to CTM is disconnected.

KDJE43096-E

aa....aa does not have remote interface. Remote interface is required to enable scheduling.

aa....aa: Bean name

Description

aa....aa does not have remote interface.

Bean that does not have remote interface is not subject to scheduling by CTM.

Action

Remote interface is required to enable the CTM scheduling for the Bean.

KDJE43097-E

Unexpected error occurred after starting EJB. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description: An unexpected error occurred in the processing after EJB startup.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43098-I

aa....aa is registered with queue:bb....bb successfully.

aa....aa: Bean name

bb....bb: Queue name

Description

aa....aa was registered with queue (bb....bb).

This message is displayed when the Bean in which enable-scheduling is specified, is deployed successfully.

KDJE43099-I

Queue:aa....aa is activated successfully.

aa....aa: Queue name

Description: This message is output when an application using a CTM is deployed successfully or when a batch server using a CTM is registered successfully.

KDJE43100-I

Queue:aa....aa is deactivated successfully.

aa....aa: Queue name

Description: This message is output when an application using a CTM is undeployed successfully or when a batch server using a CTM is deleted successfully.

KDJE43101-E

Unexpected exception occurred while starting CTM application:aa....aa Detail=bb....bb.

aa....aa: Application name

bb....bb: Detailed message

Description: An unexpected exception occurred during a CTM application (aa....aa) startup.
Action: Contact the maintenance personnel.

KDJE43102-E

An error occurred when accessing a database. (error details = aa....aa)

aa....aa: Exception message (Exception information mainly related to database is output)

Description

An exception occurred when accessing a database.

The state probably does not allow access to the database.

Action

Based on the details, revise the environment settings to access the database, Remove the cause of the error, and then re-execute the process.

KDJE43103-E

An error occurred when getting information for connect database. (error details = aa....aa)

aa....aa: Items considered as cause and exception message

Description

An exception occurred when the user tried to acquire information for connecting to the database.

The Data-source or database connector is not set properly.

Action

Based on the details, revise the settings of the data-source or database connector, Remove the cause of the error, and then re-execute the process.

KDJE43104-E

Unexpected error occurred when getting information for database. (error details = aa....aa)

aa....aa: Exception message

Description

An unexpected error occurred when getting information for database.

The environment for accessing the database might not be set properly or the internal processing might have performed an unexpected operation.

Action

Based on the details, determine the action. If you do not understand the cause, contact the maintenance personnel.

KDJE43105-E

Exception occurred in setting Parallel Count to queue:aa....aa. CTM API MSG=bb....bb

aa....aa: Queue name

bb....bb: Detailed message

Description: An exception occurred when setting the Parallel Count for the queue (aa....aa).
Action: Take action based on the details.

KDJE43106-E

Unexpected exception occurred while stopping CTM application:aa....aa. Detail=bb....bb.

aa....aa: Application name

bb....bb: Details of the exception

Description: An unexpected exception occurred while stopping the CTM application (aa....aa).
Action: Contact the maintenance personnel.

KDJE43107-E

Unexpected exception occurred while finalizing CTM.

Description: An unexpected exception occurred while finalizing the CTM.
Action: Contact the maintenance personnel.

KDJE43108-E

Failed to start CTM Application:aa....aa. CTM not installed properly.

aa....aa: Application name

Description

An attempt to start a CTM Application (aa....aa) has failed.

The CTM functionality might not be installed or might not be installed properly.

Action

Check whether CTM is installed properly and if not, install it properly.

KDJE43109-E

Unexpected error occurred during deploying EJB-JAR. EJB-JAR = aa....aa, Detail = bb....bb.

aa....aa: display-name of EJB-JAR

bb....bb: Detailed message

Description: An unexpected error occurred during deploying the EJB-JAR.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43110-E

Unexpected error occurred during starting EJB-JAR. EJB-JAR = aa....aa, Detail = bb....bb.

aa....aa: display-name of EJB-JAR

bb....bb: Detailed message

Description: An unexpected error occurred during EJB-JAR startup.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43111-E

Exception occurred in registering aa....aa. CTM API MSG=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description: An error occurred while registering aa....aa in CTM.
Action: See the details, and then take action.

KDJE43112-E

An exception occurred during deactivation of the CTM queue: aa....aa.

aa....aa: CTM queue name

Description: An error occurred during deactivation of the CTM queue (aa....aa).
Action: When restarting the J2EE application connected to the CTM queue where an error occurred, restart the J2EE Server, and then restart the application.

KDJE43113-E

Timeout occurred during awaiting the method completion of the bean: aa....aa.

aa....aa: Bean name

Description: A timeout occurred while awaiting the method completion of the Bean (aa....aa).
Action: When restarting the J2EE application, containing the Bean with an error, restart the J2EE server, and then restart the application.

KDJE43114-E

An exception occurred during terminating JMS connection or session of the bean: aa....aa.

aa....aa: Bean name

Description: An exception occurred while terminating JMS connection and JMS session of Message-driven Bean (aa....aa).
Action: When restarting the J2EE application, containing the Bean with an error, restart the J2EE server, and then restart the application.

KDJE43115-W

No CTM mode: CTM not installed properly.

Description: The J2EE server is running in the No CTM mode. When CTM is to be used, confirm that CTM is installed properly.
Action: When CTM is to be used, confirm that CTM is installed properly. if not, install it properly.

KDJE43116-I

The Remove timer of Stateful Session Bean has been started. (application = aa....aa, bean = bb....bb, removal timeout [min] = cc....cc)

aa....aa: J2EE application name

bb....bb: Enterprise Bean name

cc....cc: Timeout attribute value (Value set in Removal timeout (Units: Minutes))

Description: The timeout monitoring of Stateful Session Bean is started with the set timeout value (cc....cc) for the Enterprise Bean (bb....bb) in the J2EE application (aa....aa).

KDJE43117-I

The instance of Stateful Session Bean was removed by the Remove timer. (application = aa....aa, bean = bb....bb, removed instances = cc....cc)

aa....aa: J2EE application name

bb....bb: Enterprise Bean name

cc....cc: Number of removed instances

Description: The instances of (cc....cc) of the Enterprise Beans (bb....bb) in the J2EE application (aa....aa) were deleted by the timeout monitoring of Stateful Session Bean.

KDJE43118-E

The value of aa....aa is invalid. The ejb invoking cannot be performed. (value = bb....bb)

aa....aa: Property name

bb....bb: Specified value

Description

The EJB cannot be invoked because the value specified in the system property aa....aa is invalid.

Action

For J2EE Server: Set a correct value, and then restart the server.
For Web container (servlet engine mode): Stop the server, set a correct value, and then restart the server.
For EJB client application: Stop the process, set a correct value, and then re-execute the process.
For a batch application: After stopping the batch execution command, set up the correct value in the user property file of the batch application, and then re-execute the command.

KDJE43119-I

The thread for Remove timer has been started.(remove scan interval [min] = aa....aa)

aa....aa: Interval for monitoring the timeout

Description: The timeout monitoring thread is started.

KDJE43120-I

The thread for Remove timer has not been started.(remove scan interval [min] = 0)

Description: The timeout monitoring thread is not started.

KDJE43121-W

The specified remove scan interval exceeds upper limit. The maximum value(153722867280912min) of scan interval will be used.

Description

The specified interval for monitoring the timeout has exceeded the upper limit.

The maximum value (153722867280912 minutes) of the interval for monitoring the timeout will be used.

KDJE43122-W

Invalid remove scan interval : aa....aa. The default value(5min) of remove scan interval will be used.

aa....aa: Value specified in property

Description

The interval for monitoring the timeout (aa....aa) is invalid.

The default value (5 minutes) of the interval for monitoring the timeout will be used.

KDJE43123-W

The specified remove scan interval is less than lower limit. The thread for Remove timer has not been started.

Description: The timeout monitoring thread is not started as the specified interval for monitoring the timeout is less than the lower limit.

KDJE43124-I

The Remove timer of Stateful Session Bean has not been started.(application = aa....aa, bean = bb....bb, removed timeout = cc....cc)

aa....aa: J2EE application name

bb....bb: Enterprise Bean name

cc....cc: Timeout attribute value (Value set in Removal timeout. Units: Minutes)

Description: The timeout monitoring of Stateful Session Bean is not started for the Enterprise Bean (bb....bb) in the J2EE application (aa....aa).

KDJE43125-W

The Remove timer of Stateful Session Bean has not been started. Since remove scan interval is zero or less value.(application = aa....aa, bean = bb....bb, removed timeout = cc....cc)

aa....aa: J2EE application name

bb....bb: Enterprise Bean name

cc....cc: Timeout attribute value (Value set in Removal timeout. Units: Minutes)

Description

Zero or a value less than zero is set in the interval for monitoring the timeout.

The timeout monitoring of Stateful Session Bean is not started for the Enterprise Bean (bb....bb) in the J2EE application (aa....aa).

KDJE43126-E

Unexpected error occurred while generating interface implementation for bean aa....aa. Detail=bb....bb

aa....aa: Enterprise Bean name

bb....bb: Details

Description

An unexpected exception occurred while generating interface implementation class for Enterprise Bean (aa....aa).

Action

See the detailed message, and then take action. Check whether any other error message is displayed and if it is displayed, take action.

If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43127-E

Unexpected error occurred during awaiting the method completion of the bean aa....aa. Detail=bb....bb

aa....aa: Enterprise Bean name

bb....bb: Details

Description: A timeout occurred during awaiting the method completion of the Enterprise Bean (aa....aa).
Action: When the J2EE application, containing the Enterprise Bean with an error, is to be restarted, once restart the J2EE Server, and then restart the application.

KDJE43128-I

Maximum instances for bean aa....aa set to bb....bb .

aa....aa: Bean name

bb....bb: Maximum number or "unlimited" of EJB objects that can be generated concurrently

Description: The maximum number of EJB objects that can be generated concurrently was specified. In the case of "unlimited", actually there are 2147483647 objects.

KDJE43129-I

Instantiating home for bean aa....aa.

aa....aa: Bean name

Description: Instantiating home for Bean (aa....aa).

KDJE43130-E

The request has refused because of the bean was blockaded. (application = aa....aa, bean = bb....bb)

aa....aa: Application name

bb....bb: Bean name

Description: The request was refused because the bean was locked.
Action: Start the J2EE application containing the Bean with an error, and then execute the client.

KDJE43131-I

Registering bean aa....aa to namespace.

aa....aa: Bean name

Description: Registering Bean (aa....aa) to namespace.

KDJE43132-I

Deploying bean aa....aa.

aa....aa: Bean name

Description: Deploying bean (aa....aa).

KDJE43133-I

Bean aa....aa deployed.

aa....aa: Bean name

Description: Bean (aa....aa) is deployed.

KDJE43134-I

Starting bean aa....aa.

aa....aa: Bean name

Description: Starting bean (aa....aa).

KDJE43135-I

Bean aa....aa started.

aa....aa: Bean name

Description: Bean (aa....aa) is started.

KDJE43136-I

Bean aa....aa stopped.

aa....aa: Bean name

Description: Bean (aa....aa) is stopped.

KDJE43137-I

Bean aa....aa undeployed.

aa....aa: Bean name

Description: Bean (aa....aa) is undeployed.

KDJE43138-E

Unexpected error occurred during instantiating EJBLocalObject.

Description: An unexpected error occurred during instantiating the EJBLocalObject.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE43139-E

Failed to start CTM Application:aa....aa. CTM definition is not found.

aa....aa: Application name

Description: The CTM integration definition related to the application was not found.
Action: Confirm that the CTM integration is defined for each application, and then restart the application.

KDJE43140-E

Failed to start CTM Application:aa....aa, Bean:bb....bb. CTM definition is not found.

aa....aa: Application name

bb....bb: Bean name

Description: The CTM integration definition related to the bean was not found.
Action: Confirm that the CTM integration is defined for each Bean, and then restart the application.

KDJE43141-E

Exception occurred in getting CTMQueueManager to start CTM Application:aa....aa. CTM API MSG=bb....bb

aa....aa: Application name or batch server name

bb....bb: Details of the exception

Description: An exception occurred in getting the CTMQueueManager to start the CTM application.
Action: Take action based on the contents of the details.

KDJE43142-E

Exception occurred in setting Queue Length to queue:aa....aa. CTM API MSG=bb....bb

aa....aa: Queue name

bb....bb: Details of the exception

Description: An exception occurred in setting schedule queue length.
Action: Take action based on the contents of the details.

KDJE43143-E

An attempt to blockade the CTM queue aa....aa has failed.

aa....aa: Queue name

Description: An attempt to lock the CTM queue has failed.
Action: Restart the J2EE Server, and then restart the J2EE application connected to the CTM queue in which an error occurred.

KDJE43144-E

Failed to get a bean instance. Application: aa....aa, Bean: bb....bb, Instance Timeout: cc....cc

aa....aa: Application name

bb....bb: Bean name

cc....cc: Set value of the timeout for acquiring instances

Description

An attempt to acquire a bean instance for processing a request within the set period has failed.

When this message is displayed frequently, the maximum value of instance pool might not match with multiple requests.

Action

Revise the setting of the upper-limit value of the instance pool, and then reset the property file.

When bb....bb is a Stateless Session Bean, revise the value of the following tag of HITACHI Session Bean Property file:

<stateless>

+ <pooled-instance>

+ <maximum>
When bb....bb is Entity Bean, revise the value of the following tag of HITACHI Entity Bean Property file:

<pooled-instance>

+ <maximum>

KDJE43145-E

Exception occurred in getting queue:aa....aa. CTM API MSG=bb....bb

aa....aa: Queue name

bb....bb: Detailed message

Description: An attempt to acquire the queue (aa....aa) has failed.
Action: Take action based on the contents of the details.

KDJE43146-E

Exception occurred while generating source files. (Bean=aa....aa, Class=bb....bb, Detail=cc....cc)

aa....aa: Bean name

bb....bb: Class name

cc....cc: Detailed message

Description: An exception occurred while generating the source file.
Action: See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43147-E

The AroundInvoke method threw an invalid exception that is not permitted by the business method. (AroundInvoke: class = aa....aa, method = bb....bb. BusinessMethod: bean = cc....cc, method = dd....dd)

aa....aa: AroundInvoke method definition class name

bb....bb: AroundInvoke method name

cc....cc: Bean name

dd....dd: Business method name

Description: The AroundInvoke method threw an invalid exception that is not permitted by the business method
Action: Check whether the AroundInvoke method throws an application exception not permitted by the business method.

KDJE43148-I

The EJB timer was created. (EJB name = aa....aa)

aa....aa: EJB name (Specification value of ejb-name tag)

Description: The EJB timer was created.

KDJE43149-I

The EJB timer was cancelled. (EJB name = aa....aa)

aa....aa: EJB name (Specification value of ejb-name tag)

Description: The EJB timer was cancelled.

KDJE43150-I

The EJB timer was deleted. (EJB name = aa....aa)

aa....aa: EJB name (Specification value of ejb-name tag)

Description: The EJB timer was deleted.

KDJE43151-I

The timeout method was invoked. (EJB name = aa....aa)

aa....aa: EJB name (Specification value of ejb-name tag)

Description: The timeout method was invoked.

KDJE43152-E

A method of the timer service was invoked from an unpermitted EJB method. (EJB name = aa....aa, calling EJB method = bb....bb, called timer service method = cc....cc)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Invoker method

cc....cc: Method of the invoked Timer Service

Description: A method of the Timer Service was invoked from an unpermitted EJB method.
Action: The method of Timer Service is not permitted to be executed from the invocation source. Confirm that the execution of the EJB method invoking the Timer Service method is permitted, and then take action.

KDJE43153-E

The EJB timer does not exist yet. (EJB name = aa....aa, calling EJB method = bb....bb, called timer service method = cc....cc)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Invoker method

cc....cc: Method of the invoked Timer Service

Description: The EJB timer already does not exist because it was cancelled or deleted. The EJB timer that does not exist cannot be operated.
Action: An attempt is made to operate the EJB timer that was already cancelled or deleted. Check the problem, and take action.

KDJE43154-E

There is an invalid value in an argument of the createTimer method of the TimerService class. (EJB name = aa....aa, calling EJB method = bb....bb, invalid argument = cc....cc, invalid argument value = dd....dd)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Invoker method

cc....cc: Invalid argument (initial duration, initial expiration, or interval duration)

dd....dd: Value of the invalid argument

Description

The value of relative time is negative and reference of absolute date is null or the time specified as absolute time in the argument of createTimer method of TimerService class is before January 1, 1970, 0 Hour 0 Minute 0 Second. These values cannot be specified.

Action

Confirm that the arguments passed to the createTimer method of TimerService class satisfy the following values, and then resolve the problem:

Relative time is 0 or a positive value
Reference of absolute time is not null
Date of absolute time is January 1, 1970, 0 Hour 0 Minute 0 Second onwards

KDJE43155-W

Invocation of the timeout method failed and will be retried. (EJB name = aa....aa, retry count = bb....bb)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Count of retry after the timeout method

Description

The timeout method failed due to one of the following reason:

The timeout method has thrown an exception.
Transaction of the container management of the timeout method has rolled back during the timeout method.

After retry interval has elapsed, the timeout method will be re-invoked.

Action

Confirm the following and accordingly take action:

When the timeout method throws an exception, remove the cause of exception.
When the transaction of the container management rolls back during the timeout method, remove the cause of the roll-back.

KDJE43156-E

The retry count for the timeout method reached the limit. Retries have stopped. (EJB name = aa....aa, retried count = bb....bb)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Count of retry of the timeout method

Description

The timeout method failed due to one of the following reason:

The timeout method has thrown an exception.
Transaction of the container management of the timeout method has rolled back during the timeout method.

Retry process is not performed since it has exceeded the upper limit.

Action

Check any one of the followings, and then take action:

When the timeout method throws an exception, remove the cause of exception.
When the transaction of the container management rolls back during the timeout method, remove the cause of the roll-back.

KDJE43157-W

The value of a timer service property is invalid. The default value will be used. (property name = aa....aa, specified value = bb....bb, default value = cc....cc)

aa....aa: Property name

bb....bb: Value set in property

cc....cc: Default value of property

Description: The value of property used by the Timer Service is invalid. The Timer Service uses the default value as the property value.
Action: Check the setting of property, and then set the appropriate value.

KDJE43158-E

An unsupported transaction attribute was specified for the timeout method. (EJB name = aa....aa, transaction attribute = bb....bb)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Transaction attribute

Description: An unsupported transaction attribute was specified for the timeout method.
Action: Specify the transaction attribute of the timeout method properly.

KDJE43159-E

The timer service cannot be used from the unsupported bean type. (EJB name = aa....aa, bean type = bb....bb)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Bean type

Description: The Timer Service cannot be used from the unsupported Bean type.
Action: Use the Timer Service from the Bean type in which its usage is permitted.

KDJE43160-W

The EJB timer was cancelled during execution of the timeout method. (EJB name = aa....aa)

aa....aa: EJB name (Specification value of ejb-name tag)

Description: The timeout method was terminated but the EJB timer was cancelled during execution of the timeout method.

KDJE43161-W

The container-managed transaction was rolled back because the EJB timer was cancelled during execution of the timeout method. (EJB name = aa....aa)

aa....aa: EJB name (Specification value of ejb-name tag)

Description: The timeout method was terminated but the transaction of the timeout method was rolled back because the EJB timer was cancelled during execution of the timeout method.

KDJE43162-E

A method of the timer service cannot be executed because the EJB timer has not been created. (method = aa....aa)

aa....aa: Method name

Description: An attempt was made to execute a method of Timer class for the EJB timer that is not created. When the EJB timer is not created, the method of Timer class cannot be executed for that EJB timer.
Action: Execute the method of EJB timer after concluding the transaction for creating the EJB timer or execute the method of EJB timer under the management of transaction that creates the EJB timer

KDJE43163-E

A method cannot be executed because the transaction is inactive. (method = aa....aa)

aa....aa: Method name

Description: An attempt was made to execute the method when the transaction is inactive. The transaction is inactive because the transaction has timed out.
Action: Revise the settings so that the method is executed before a transaction timeout occurs or set the transaction timeout period longer than the method execution period.

KDJE43164-E

The EJB timer cannot be created because the timeout method for the EJB is not defined. (EJB name = aa....aa, calling EJB method = bb....bb)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Invoker method

Description: You can invoke the createTimer method of the TimerService class only from the Bean in which the timeout method is defined.
Action: When using the Timer Service from EJB, define the timeout method in that EJB.

KDJE43165-W

An invalid property value is specified (aa....aa = bb....bb). The default value (cc....cc) will be used.

aa....aa: Property name

bb....bb: Specified value

cc....cc: Default value

Description: The property value is invalid. The default value will be used.
Action: Specify a valid property value.

KDJE43166-E

An invalid property has been specified. (property name = aa....aa, value = bb....bb)

aa....aa: Property name

bb....bb: Specified value

Description: A mistake exists in the value specified in the property.
Action: Specify the correct value in the property, and then start the J2EE server.

KDJE43167-E

An attempt was made to use an interface that is not provided by the resource adapter using an MDB. (EJB name = aa....aa, resource name = bb....bb, interface name = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Interface name

Description: An attempt is made to use an interface that is not provided by the resource adapter, in the Message-driven Bean.
Action: Make sure that the interface specified in the <message-driven>-<messaging-type> tag of ejb-jar.xml is supported by the resource adapter.

KDJE43168-E

An error occurred during creation of an ActivationSpec instance. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Exception character string

Description: An exception occurred during creation of ActivationSpec instance.
Action: Make sure that the class name specified in the <activationspec-class> tag of ra.xml is correct, by checking the processing of the default constructor of the corresponding class.

KDJE43169-E

An attempt to set a configuration property for ActivationSpec has failed. (EJB name = aa....aa, resource name = bb....bb, property name = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Property name

Description: An attempt to set up a property in ActivationSpec has failed.
Action: Make sure that the setup of properties in the <message-driven>-<activation-config> tag of ejb-jar.xml is correct, by checking the documents of the resource adapter.

KDJE43170-E

An error occurred in the method ActivationSpec#validate. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Exception character string

Description: An exception occurred in the ActivationSpec#validate method.
Action: Make sure that the setup of properties in the <message-driven>-<activation-config> tag of ejb-jar.xml is correct, by checking the documents of the resource adapter.

KDJE43171-E

A required configuration property has not been set for ActivationSpec. (EJB name = aa....aa, resource name = bb....bb, property name = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Property name

Description: A mandatory property is not specified during the setup of properties in ActivationSpec.
Action: Make sure that the setup of properties in the <message-driven>-<activation-config> tag of ejb-jar.xml is correct, by checking the documents of the resource adapter.

KDJE43172-E

An attempt to cast an ActivationSpec class to javax.resource.spi.ActivationSpec has failed. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Exception character string

Description: An attempt to perform casting to javax.resource.spi.ActivationSpec from the class specified as ActivationSpec has failed.
Action: Check the source for providing the resource adapter.

KDJE43173-E

An attempt to associate ActivationSpec and javax.resource.spi.ResourceAdapter has failed. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Exception character string

Description: An attempt to correlate ActivationSpec with javax.resource.spi.ResourceAdapter has failed.
Action: Check the source that provides the resource adapters.

KDJE43174-E

An error occurred in the method ResourceAdapter#endpointActivation. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Details of the exception

Description

An exception occurred during the execution of endpointActivation of the resource adapter.

Action

Make sure that no problem exists in the settings of the Message-driven Bean or the resource adapter.

Revise the settings, and then restart the Message-driven Bean or the resource adapter.

KDJE43175-W

An error occurred in the method ResourceAdapter#endpointDeactivation. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Details of the exception

Description: An exception occurred during the execution of endpointDeactivation of the resource adapter.
Action: Revise the settings of the Message-driven Bean or the resource adapter.

KDJE43176-E

The XAResource object is specified as the argument of the method MessageEndpointFactory#createEndpoint. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Details of the exception

Description

XAResource is specified as an argument of the createEndpoint method of MessageEndpointFactory.

XAResource cannot be specified as an argument of createEndpoint because the XA transaction is not supported.

Action

Change the settings of the resource adapter so as to specify null in the argument of the createEndpoint method of MessageEndpointFactory, and then restart the resource adapter.

KDJE43177-E

The resource adapter used the message endpoint after execution of the method endpointDeactivation. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Details of the exception

Description: The resource adapter used the end point after the execution of the endpointDeactivation method.
Action: Check the source of providing the resource adapter.

KDJE43178-E

An exception occurred during loading interceptor class. aa....aa is not found.

aa....aa: Class name (specified value of the <interceptor-class> tag)

Description: An exception occurred while the interceptor class was being loaded.
Action: Make sure that the class name specified in the <interceptor-class> tag is correct.

KDJE43179-W

A transaction was automatically rolled back. (Transaction=aa....aa)

aa....aa: Transaction information

Description: Transaction rollback occurred automatically.
Action: Make sure that the transaction has concluded in the program.

KDJE43186-W

A null object was specified as the argument of the method MessageEndpointFactory#createEndpoint. (EJB name = aa....aa, method = bb....bb, method_params = cc....cc, resource name = dd....dd)

aa....aa: EJB name

bb....bb: Method name

cc....cc: Method argument

dd....dd: Resource display name

Description

null is specified in an argument of the createEndpoint method of MessageEndpointFactory. A transaction will not start when the EJB container executes a method of the Message-driven Bean.

Action

To start a transaction during the execution of a method of the Message-driven Bean, revise the settings of the resource adapter.

To prevent the output of the message, set the transaction attribute to be specified in the method of the Message-driven Bean to NotSupported.

KDJE43200-I

Cleaning up aa....aa async tasks for EJB bb....bb.

aa....aa: Number of deleted processing results of the asynchronous method

bb....bb: EJB name

Description: aa....aa processing results of the EJB bb....bb asynchronous method will be deleted. This message is output when the processing results of the asynchronous method of the EJB executed by remote invocation are deleted during the cleanup processing executed when the application is stopped.

KDJE43201-W

The value of an asynchronous property is invalid. The default value will be used. (property name = aa....aa, specified value = bb....bb, default value = cc....cc)

aa....aa: Property name

bb....bb: Specified value

cc....cc: Default value

Description

The default value will be used because the following asynchronous invocation properties are incorrectly specified in the cosminexus.xml file:

max-thread-pool-size
min-thread-pool-size
thread-pool-keep-alive
result-timeout-value

Action

Specify the correct asynchronous invocation properties.

KDJE43202-I

EJB asynchronous call result cannot be referenced. Timeout for the result of asynchronous call might be occurred.

Description: The objects in the processing results of the EJB asynchronous method were deleted due to timeout; therefore, the results cannot be referenced.

KDJE43203-I

Cleaning up async task (Task ID: aa....aa).

aa....aa: Object in the processing results of the EJB asynchronous method

Description: The processing results of the asynchronous method executed by remote invocation will be cleaned up.

KDJE43204-E

Cyclical dependency: aa....aa. The cyclical dependency graph is as follows bb....bb

aa....aa: Singleton Session Bean with cyclical dependency

bb....bb: Cyclical dependency

Description

A cyclical dependency exists in the @DependsOn annotation of the Singleton Session Bean.

Action

Remove the cyclical dependency from the @DependsOn annotation.

An example of cyclical dependency is as follows:

Example

@Singleton
@DependsOn("B")
class A {..}
 
@Singleton
@DependsOn("A")
class B{..}

KDJE43205-E

Singleton is unavailable because its original initialization failed. (EJB name = aa....aa)

aa....aa: EJB name

Description

An attempt was made to access a Singleton Session Bean that was not initialized properly.

Action

Remove the cause due to which the initialization of Singleton Session Bean failed.

The possible causes are as follows:

DI failure
Failure in the processing of the lifecycle callback method

KDJE43206-W

The schedule associated with the calendar based timer already expired. (EJB name = aa....aa, calling EJB method = bb....bb, schedule = cc....cc)

aa....aa: EJB name

bb....bb: Calling method name

cc....cc: Expired schedule

Description: The schedule expression specified in the createCalendarTimer method is already expired. Therefore, this timer will not time out.
Action: Specify a schedule expression that has not expired.

KDJE43207-E

There is an invalid value in an argument of the createSingleActionTimer method of the TimerService class. (EJB name = aa....aa, calling EJB method = bb....bb, invalid argument = cc....cc, invalid argument value = dd....dd)

aa....aa: EJB name

bb....bb: Method name

cc....cc: Argument type

dd....dd: Value

Description: The value for an argument of the createSingleActionTimer method is invalid.
Action: Check whether the arguments of the createSingleActionTimer method are appropriate.

KDJE43208-E

There is an invalid value in an argument of the createIntervalTimer method of the TimerService class. (EJB name = aa....aa, calling EJB method = bb....bb, invalid argument = cc....cc, invalid argument value = dd....dd)

aa....aa: EJB name

bb....bb: Calling method name

cc....cc: Argument type

dd....dd: Value

Description: An argument of the createIntervalTimer method is invalid.
Action: Check whether the arguments of the createIntervalTimer method are correct.

KDJE43209-E

The ScheduleExpression used in the createCalendarTimer method of the TimerService class is incorrect. (EJB name = aa....aa, calling EJB method = bb....bb, invalid argument = cc....cc, cause = dd....dd)

aa....aa: EJB name

bb....bb: Calling method name

cc....cc: Argument type

dd....dd: Invalid attribute and its value

Description: The schedule expression specified in the createCalendarTimer method of the TimerService class is incorrect.
Action: Check whether the attributes, such as hours and minutes, specified as the schedule are correct.

KDJE43210-E

Carendar based timers or automatic timers can invoke this method. (EJB name = aa....aa, calling EJB method = bb....bb, called javax.ejb.Timer method = cc....cc)

aa....aa: EJB name

bb....bb: Calling method name

cc....cc: Invoked Timer Service method

Description: A timer that is neither a calendar-based timer nor a timer that is auto-generated in the @Schedule annotation invoked the getSchedule() method.
Action: Check whether the invoked timer is a calendar-based timer or a timer that is auto-generated in the @Schedule annotation.

KDJE43211-W

No more timeout is there for this Timer. (EJB name = aa....aa, timer schedule = bb....bb)

aa....aa: EJB name

bb....bb: Timer schedule

Description

This timer will not time out.

Action

Check whether the timer settings are correct.

For example, if @Schedule(year ="2012", month="1", dayOfMonth="1", hour="17") is operated in 2011, deploy is successful and a timer that will time out in 2012/1/1 17:00:00 is generated. This timer is deleted after the 2012/1/1 17:00:00 timeout, but this message is displayed if you execute the getNextTimeout method just before the timer is deleted.

KDJE43216-E

Illegal Reentrant Access: Attempt to make a loopback call on a Write Lock method while a Read lock is already held. (Write Lock method = aa....aa, EJB name = bb....bb)

aa....aa: Method name for which a WRITE lock is specified

bb....bb: EJB name

Description: An attempt was made to execute a method defining WRITE in the @Lock annotation from a method defining READ in the @Lock annotation.
Action: Check whether the method lock is defined properly.

KDJE43217-E

The Lock is not acquired within the time limit. (Time=aa....aa, TimeUnit=bb....bb, EJB name = cc....cc)

aa....aa: Timeout value

bb....bb: Unit of timeout value

cc....cc: EJB name

Description: The lock could not be acquired within the specified limit.
Action: Check whether the specified timeout value is appropriate. Increase the timeout value as and when required.

KDJE43218-E

Illegal synchronous loopback call during Singleton initialization would have resulted in deadlock. (EJB name = aa....aa)

aa....aa: EJB name

Description

Initialization of the Singleton Session Bean failed because during the initialization, there was an invalid loopback invocation that might cause a deadlock.

During the initialization of a Singleton Session Bean, initialization was re-executed for the same Singleton Session Bean.

Action

Check whether the initialization processing is being executed for the same Singleton Session Bean from the @PostConstruct annotation method.

If a different Singleton Session Bean is being invoked from the @PostConstruct annotation method, the dependency based on the @DependsOn annotation becomes invalid and this message is displayed. The invalid example is as follows:

Example

@DependsOn("SingletonA")
@Singleton
@Startup
public class SingletonB implements BIntf {
}
 
@Singleton
public class SingletonA implements AIntf {
 @EJB
 BIntf b;
 @PostConstruct
 void init() {
  b.doB();
 }
}

KDJE43219-E

Client is not authorized for this invocation. Illegal non-business method access on no-interface view. (class name = aa....aa, method = bb....bb)

aa....aa: EJB name

bb....bb: Method name

Description: A method that is not a business method was invoked from the client.
Action: Do not invoke a method that is not a business method from the client.

KDJE43220-W

The schedule associated with the automatic timer is either already expired or invalid. (EJB name = aa....aa, schedule = bb....bb)

aa....aa: EJB name

bb....bb: Schedule

Description

An already expired schedule or an invalid schedule is specified in the timer that is auto-generated in the @Schedule annotation; therefore, the timer does not time out.

The respective examples are as follows:

Already expired schedule

@Schedule(year="1983")

Invalid schedule

@Schedule(year="2011", month="2", dayOfMonth="31")^#

# Invalid because February does not have 31 days.

Action

Check whether the schedule format is correct.

KDJE43223-I

Cleaning up async task (Task ID: aa....aa), as timeout for Asynchronous call result is occurred.

aa....aa: Task ID

Description: The processing results (task ID: aa....aa) of the asynchronous method will be cleaned up because the asynchronous invocation results timed out.

KDJE43224-W

The values of asynchronous properties are invalid. The property value for max-thread-pool-size should be greater than or equal to the property value for min-thread-pool-size. Default values will be used for both properties. (property name = aa....aa, specified value = bb....bb, default value = cc....cc and property name = dd....dd, specified value = ee....ee, default value = ff....ff)

aa....aa: Property name

bb....bb: Value specified in aa....aa

cc....cc: Default value of aa....aa

dd....dd: Property name

ee....ee: Value specified in dd....dd

ff....ff: Default value of dd....dd

Description

The values specified in the asynchronous invocation properties min-thread-pool-size and max-thread-pool-size have the relationship min-thread-pool-size > max-thread-pool-size. Therefore, the default values will be used for both the properties.

The error also occurs in the following cases:

When the default value is used because one of the properties is omitted, and the property value becomes min-thread-pool-size > max-thread-pool-size due to the specification of the other value

In this case, the default value of the property is displayed as the value specified for the omitted property.
When the default value is used because an invalid value is specified for one of the properties, and the property value becomes min-thread-pool-size > max-thread-pool-size due to the specification of the other value

In this case, the default value of the property is displayed as the value specified for the property with an invalid value.

Action

Specify the correct value so that the specified value has the min-thread-pool-size ≤ max-thread-pool-size relationship.

KDJE45000-E

Unexpected error occurred during updating user or role information.

Description: An unexpected error occurred during updating user or role information.
Action: Contact the maintenance personnel.

KDJE45001-E

Failed to update user information.

Description: An attempt to update user information has failed.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE45002-E

Failed to update role information.

Description: An attempt to update role information has failed.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE47000-I

Specified url schema aa....aa is converted into default url schema bb....bb

aa....aa: URL schema name for compatibility

bb....bb: Default URL schema name

Description: Specified URL schema is converted into default schema.

KDJE47001-E

Could not initialize namespace. Reason = aa....aa

aa....aa: Reason for occurrence

Description

An attempt to initialize namespace has failed.

The messages output as reason for occurrence (aa....aa) and their cause are as follows:

Naming Service is not found. Start Naming Service and J2EE Server again.: The naming service might not be started.
Could not initialize ORB. Check the ORB version and setting.: ORB settings might not be correct or the version of ORB being used might be different.
Unexpected exception occurred. Please contact system administrator.: An unexpected problem such as the naming service stopped during the start of J2EE Server might have occurred.

Action

Take action according to the reason for occurrence.

Naming Service is not found. Start Naming Service and J2EE Server again.

Adjust the value of ejbserver.naming.startupWaitTime and ejbserver.naming.startupRetryCount and restart the naming service and the J2EE Server.

Could not initialize ORB. Check the ORB version and setting.

Confirm that the ORB setting is correct or ORB version being used is correct.

Unexpected exception occurred. Please contact system administrator.

Restart the naming service and the J2EE Server.

If the problem is not resolved, contact the maintenance personnel.

KDJE47100-E

Could not find the naming service list.

Description

The naming service list cannot be found.

The value of ejbserver.jndi.namingservice.group.list is not specified.

Action

Specify the value correctly.

KDJE47101-E

The group name aa....aa has already existed in the naming service group list.

aa....aa: Search group name

Description

Search group name (aa....aa) already exists.

You cannot specify the same group name in the ejbserver.jndi.namingservice.group.list.

Action

Delete the group name with same name from ejbserver.jndi.namingservice.group.list.

When same names are specified, they are treated as one group.

KDJE47102-E

Invalid group name is specified.name=aa....aa.

aa....aa: Search group name

Description

Search group name (aa....aa) is invalid.

Characters other than alphanumeric characters (A-Z, a-z, 0-9) and underscore (_) might be used for the group name.

Action

Specify the correct group name.

KDJE47103-E

Could not find the provider urls in the group name aa....aa.

aa....aa: Search group name

Description

The provider URLs cannot be found in the search group (aa....aa).

Provider url is not specified in ejbserver.jndi.namingservice.group.GROUP_NAME.providerurls.

Action

Specify the provider URL in ejbserver.jndi.namingservice.group.Specify-group-name.providerurls correctly.

KDJE47104-E

Invalid provider url is specified.name=aa....aa.

aa....aa: Provider URL

Description

The specified provider URL (aa....aa) is invalid.

An error exists in the syntax of provider URL.

Action

Specify a correct provider URL.

KDJE47105-E

Could not find the group name aa....aa defined in the naming service list.

aa....aa: Search group name

Description

The search group name (aa....aa) defined in the naming service list cannot be found.

Provider URL is not defined for the search group name defined in ejbserver.jndi.namingservice.group.list.

Action

Define a provider URL for the search group name defined in ejbserver.jndi.namingservice.group.list.

KDJE47106-W

Since the group name is not specified, search all naming services in the naming service list.

Description

The search group name is not specified; therefore, all CORBA naming services in the naming service list will be searched.

Correct value is not specified in ejbserver.jndi.namingservice.groupname.

Action

Specify a correct value in ejbserver.jndi.namingservice.groupname.

KDJE47107-I

Naming cache is off.

Description: Naming cache is OFF.

KDJE47108-W

Invalid property value is specified aa....aa=bb....bb. Default value is used. (default value = cc....cc)

aa....aa: Property name

bb....bb: Specified value

cc....cc: Default value

Description: The specified value of property (aa....aa) is invalid. The default value (cc....cc) will be used.
Action: Specify a correct value.

KDJE47109-I

Naming cache is cleared regularly.

Description: Naming cache is cleared regularly.

KDJE47110-I

Start to use the naming service : providerurl = aa....aa.

aa....aa: Provider URL

Description: Start to use the naming service of provider URL (aa....aa).

KDJE47111-I

Stop to use the naming service : providerurl = aa....aa.

aa....aa: Provider URL

Description: Stop to use the naming service of provider URL (aa....aa).

KDJE47112-E

A fatal error occurred during a JNDI method call. Restart the J2EE server and the naming service.

Description

A fatal error occurred during a JNDI method call.

An unexpected situation such as memory insufficiency might have occurred.

Action

Restart the J2EE server and the CORBA naming service.

KDJE47113-I

The specified properties were loaded. (ejbserver.ext.jndi.providerURL.list = aa....aa, ejbserver.ext.jndi.serverName.list = bb....bb, ejbserver.ext.jndi.list.initializeInterval = cc....cc)

aa....aa: Specified value of ejbserver.ext.jndi.providerURL.list

bb....bb: Specified value of ejbserver.ext.jndi.serverName.list

cc....cc: Specified value of ejbserver.ext.jndi.list.initializeInterval

Description: The specified properties were read (ejbserver.ext.jndi.providerURL.list = aa....aa, ejbserver.ext.jndi.serverName.list = bb....bb, ejbserver.ext.jndi.list.initializeInterval = cc....cc).

KDJE47114-E

The property aa....aa does not exist. The looking up cannot be performed.

aa....aa: Property name

Description: The property aa....aa does not exist. A lookup cannot be performed.
Action: Specify the appropriate value to the property.

KDJE47115-E

The value of aa....aa is empty. The looking up cannot be performed.

aa....aa: Property name

Description: The value of the property aa....aa is blank (""). A lookup cannot be performed.
Action: Specify the appropriate value to the property.

KDJE47116-E

The value of aa....aa is invalid. The looking up cannot be performed. (value = bb....bb)

aa....aa: Property name

bb....bb: Specified value of aa....aa

Description: The value of property aa....aa is invalid. A lookup cannot be performed (value = bb....bb).
Action: Specify the appropriate value to the property.

KDJE47117-E

The number of the specified server names and provider URLs must be equal. The looking up cannot be performed.

Description: The number of the specified server names and provider URLs is different. A lookup cannot be performed.
Action: Specify the appropriate value to the property.

KDJE47118-W

The looking up to aa....aa failed. The next candidate server is bb....bb.

aa....aa: Server name

bb....bb: Server name

Description: An attempt to look up aa....aa has failed. The next search candidate is bb....bb.

KDJE47119-E

The looking up to aa....aa failed.

aa....aa: Server name

Description: An attempt to look up aa....aa has failed.
Action: All servers might have encountered errors. Revise the environment.

KDJE47120-E

The object named aa....aa was not found.

aa....aa: Name

Description: An object named aa....aa was not found.
Action: The server might have encountered an error. Revise the environment.

KDJE47121-E

The specified lookup name is invalid. The looking up cannot be performed. (name = aa....aa)

aa....aa: Name

Description: The specified name is invalid. A lookup cannot be performed (name = aa....aa).
Action: Specify a correct name.

KDJE47500-E

Startup of the J2EE server will be cancelled because the specified naming service aa....aa has already started. Stop the running naming service aa....aa, and then restart the J2EE server.

aa....aa: Provider URL

Description: Startup of the J2EE server will be cancelled because the specified naming service (aa....aa) has already started.
Action: Stop the running naming service, and then restart the J2EE server.

KDJE47501-I

The naming service aa....aa will now start in bb....bb mode.

aa....aa: Provider URL

bb....bb: Naming service startup mode (manual, automatic, or inprocess)

Description: The naming service (aa....aa) will now start in bb....bb mode.

KDJE47502-I

The naming service has started.

Description: The naming service has started.

KDJE47503-E

Startup of the J2EE server will now stop because an error occurred during startup processing of the naming service. Check the J2EE server's running environment, and then restart the J2EE server. (error details = aa....aa)

aa....aa: Error details

Description: Startup of the J2EE server will now stop because an error occurred during startup processing of the naming service.
Action: See the error details, remove the cause of the error, and then restart the J2EE server.

KDJE47504-I

Processing will wait aa....aa seconds for the naming service to bb....bb.

aa....aa: Wait time set in ejbserver.naming.startupWaitTime key

bb....bb: Naming service wait type (search process or startup process)

Description: Processing will wait for aa....aa seconds because the naming service is being searched or started (bb....bb).

KDJE47505-I

Retry count is aa....aa times.

aa....aa: Count of retry to confirm the startup of naming service and is set in ejbserver.naming.startupRetryCount key

Description: The count of retry for confirming the startup status of naming service is aa....aa times.

KDJE47600-E

Could not bind the object with the name aa....aa, because another object with the same name has already existed in the naming service.

aa....aa: User-specified name

Description

The object with user-specified name (aa....aa) cannot be registered because another object with the same name already exists in the naming service.

When a distributed object or a context with a name is registered, the name already registered in the naming service cannot be used.

However, even if the name does not match completely, there are cases when the object can be registered and when the object cannot be registered. Each case is described below:

When the object can be registered: After assigning an optional name "A/B/C" to a certain object and deploying it, and if another object is assigned an optional name "A/B/D" and deployed, this message will not be displayed and the object can be registered without any problem. This is only because the context "A/B" with same name is used therefore another object that was newly registered is not recognized..
When the object cannot be registered: After assigning an optional name "A/B/C" to a certain object and deploying it, if another object is assigned an optional name "A/B/C/D" and deployed, this message will be displayed and the object cannot be registered. This is because an attempt is made to register the context with a name even though the distributed object is already registered in "A/B/C", therefore when another object is newly registered, it is recognized as another object.

Action

Check the erroneous user-specified name (aa....aa), change it to another name, and then re-execute the process.

KDJE47601-E

The mail configuration cannot be changed because a J2EE application status is "running". (resource name = aa....aa)

aa....aa: J2EE resource display name

Description: The mail attribute cannot be changed because a J2EE application status is "running".
Action: Stop all the running J2EE applications, and then set the resource attributes.

KDJE47602-I

The optional name was registered. (resource name = aa....aa, optional name = [bb....bb])

aa....aa: J2EE resource display name

bb....bb: Optional name

Description

The optional name assigned to the J2EE resource was registered in the namespace.

When the optional name is registered multiple times, it is displayed as "optA, optB, optC" in bb....bb.

KDJE47603-I

The optional name was deleted. (resource name = aa....aa, optional name = [bb....bb])

aa....aa: J2EE resource display name

bb....bb: Optional name

Description

The optional name given to the J2EE resource was deleted from the namespace.

When optional name is deleted multiple times, it is displayed as "optA, optB, optC" in bb....bb.

KDJE47604-E

A J2EE resource cannot be stopped or deleted because a J2EE application status is "running". (resource name = aa....aa)

aa....aa: J2EE resource display name

Description: A J2EE resource cannot be stopped or deleted because a J2EE application status is running.
Action: Stop or delete the resource after stopping all the running J2EE applications.

KDJE47605-I

The optional name was registered. (Enterprise Bean display name = aa....aa, type = bb....bb, optional name = cc....cc)

aa....aa: Enterprise Bean display name

bb....bb:

remote: Remotely invoked EJB

local: Locally invoked EJB

cc....cc: Optional name

Description: The optional name given to the Enterprise Bean was registered in the name space.

KDJE47606-I

The optional name was deleted. (Enterprise Bean display name = aa....aa, type = bb....bb, optional name = cc....cc)

aa....aa: Enterprise Bean display name

bb....bb:

remote: Remotely invoked EJB

local: Locally invoked EJB

cc....cc: Optional name

Description: The optional name given to the Enterprise Bean was deleted from the name space.

KDJE47607-W

The element value is invalid. (EJB-JAR = aa....aa, Enterprise Bean = bb....bb, annotation = cc....cc, element = dd....dd, value = ee....ee)

aa....aa: EJB-JAR display name

bb....bb: Enterprise Bean display name

cc....cc: Annotation

dd....dd: Attribute

ee....ee: Value

Description: The attribute value is invalid (EJB-JAR = aa....aa, Enterprise Bean = bb....bb, annotation = cc....cc, attribute = dd....dd, value = ee....ee).
Action: Revise the value of the attribute.

KDJE47608-E

The value of the mapped-name tag is invalid. (J2EE application = aa....aa, EJB-JAR = bb....bb, Enterprise Bean = cc....cc, value = dd....dd)

aa....aa: Display name of the J2EE application

bb....bb: EJB-JAR display name

cc....cc: Enterprise Bean display name

dd....dd: Value

Description: The value of the <mapped-name> tag is invalid (J2EE application = aa....aa, EJB-JAR = bb....bb, Enterprise Bean = cc....cc, value = dd....dd).
Action: Check if the optional name specified in the mappedName attribute of @Stateless or @Stateful is a specifiable character string. Alternatively, specify the optional name in the <optional-name> tag or the <local-optional-name> tag of the property file.

KDJE47701-I

A reference to an EJB object was registered in the Portable Global JNDI namespace. (ejbname = aa....aa, jndi name = [bb....bb])

aa....aa: Bean name (<ejb-name>)

bb....bb: JNDI name

Description: A reference to an EJB object is registered in the namespace with the Portable Global JNDI name. If multiple Portable Global JNDI names are registered, the names are displayed as java:global/xxx, java:global/yyy in bb....bb.

KDJE47709-W

The namespace for the Portable Global JNDI name was re-created because a namespace with the same name remains in the naming service. (name = aa....aa, jndi name = bb....bb)

aa....aa: Application display name

bb....bb: JNDI name

Description

The namespace for the Portable Global JNDI name was re-created because a namespace with the Portable Global JNDI name remains in the CORBA naming service operated by another process.

The possible causes are as follows:

The J2EE server was terminated forcibly.
The communication with the naming service failed when the J2EE application was being stopped.

Action

There is no problem because the namespace is re-created automatically. However, if this phenomenon occurs frequently, contact maintenance personnel.

KDJE47710-W

The specified application name is invalid. All objects in this application will not be bound as Portable Global JNDI names. (name = aa....aa, application name = bb....bb)

aa....aa: Application display name

bb....bb: Standard application name

Description

The standard application name contains characters that cannot be specified.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

However, action is required if one of the following cases is applicable:

If there is a client that looks up the objects in this application using the Portable Global JNDI name.
If a resource reference is defined in this application using a name beginning with java:app or java:module.

Action

If the objects must be registered in the Portable Global JNDI name for this application, take the following action to change the standard application name:

If <application-name> of application.xml is specified: Correct the value specified in <application-name> and then re-import.
If <application-name> of application.xml is not specified (if application.xml is omitted): Correct the EAR file name (application directory name in the exploded archive format) and then re-import.

Note that if the objects need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47711-W

The specified module name is invalid. All objects in this module will not be bound as Portable Global JNDI names. (uri = aa....aa, module name = bb....bb)

aa....aa: Module URI

bb....bb: Standard module name

Description

The module name contains characters that cannot be specified.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

However, action is required if one of the following cases is applicable:

If there is a client that looks up the objects in this module using the Portable Global JNDI name.
If a resource reference is defined in this module using a name beginning with java:module.

Action

If the objects must be registered in the Portable Global JNDI name for this module, take the following action to change the standard module name:

For EJB-JAR modules

If <module-name> of ejb-jar.xml is specified

Correct the value specified in <module-name>, re-import, and then execute the module.
If <module-name> of ejb-jar.xml is not specified (if ejb-jar.xml is omitted)

Correct the EJB-JAR file name (EJB directory name in the exploded archive format) and then re-import.

For Web modules (Web application)

If <module-name> of web.xml is specified

Correct the value specified in <module-name> and then re-import.
If <module-name> of web.xml is not specified (if web.xml is omitted)

Correct the WAR file name (WAR directory name in the exploded archive format) and then re-import.

For resource adapter modules

Correct the RAR file name and then re-import.

Note that if the objects need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47712-W

The specified ejb-name is invalid as a Portable Global JNDI name. (ejbname = aa....aa)

aa....aa: Bean name (<ejb-name>)

Description

The EJB Bean name (<ejb-name>) contains characters that cannot be specified as the Portable Global JNDI name.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

However, action is required if there is a client that looks up this EJB object using the Portable Global JNDI name.

Action

If this EJB object must be registered in the Portable Global JNDI name, take the following action to change the EJB Bean name:

If <ejb-name> of ejb-jar.xml is specified: Review, and if necessary revise, the value specified for <ejb-name>.
If the Bean name is specified in the name attribute of the annotation: Review, and if necessary revise, the value specified for the name attribute.

If you change the Bean name, modify the calling lookup name of that Bean.

Note that if the EJB object need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47713-W

The Portable Global JNDI name of the bean is too long. (ejbname = aa....aa, jndi name = bb....bb)

aa....aa: Bean name (<ejb-name>)

bb....bb: JNDI name

Description

The Bean name or the fully-qualified-interface-name is too long. Therefore, the Portable Global JNDI name cannot be registered in the java:global/<app-name>/<module-name>/<ejb-name>!<fully-qualified-interface-name> format.

The length of <ejb-name>!<fully-qualified-interface-name> must be no more than 255 characters.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

Furthermore, there is no problem even if you use only the Portable Global JNDI name omitting the fully-qualified-interface-name.

However, action is required if there is a client that looks up this EJB object using the Portable Global JNDI name with the fully-qualified class name.

Action

If this EJB object must be registered in the Portable Global JNDI name with the fully-qualified class name, take the following action to change the EJB Bean name or the fully-qualified-interface-name.

If <ejb-name> of ejb-jar.xml is specified: Specify length-of-the-value-specified-for-<ejb-name> + length-of-the-fully-qualified-interface-name + 1 in 255 characters or less.
If the Bean name is specified in the name attribute of the annotation: Specify length-of-the-value-specified-for-name-attribute + length-of-the-fully-qualified-interface-name + 1 in 255 characters or less.

If the interface is omitted, the fully-qualified class name of the Bean class is applied instead of the fully-qualified-interface-name.

If you change the Bean name and the fully-qualified class name of the business interface, modify the calling lookup name of that Bean.

Note that if the EJB object need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47720-W

The objects in the J2EE application could not be bound as Portable Global JNDI names because there is already an application in the naming service with the same application name. (name = aa....aa, application name = bb....bb)

aa....aa: Application display name

bb....bb: Standard application name

Description

An application with the same standard application name already exists in the naming service. Therefore, the objects in the J2EE application could not be registered in the Portable Global JNDI name.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

However, action is required if one of the following cases is applicable:

If there is a client that looks up the objects in this application using the Portable Global JNDI name.
If a resource reference is defined in this application using a name beginning with java:app or java:module.

Action

If the objects must be registered in the Portable Global JNDI name for this application, take the following action to change the standard application name:

If <application-name> of application.xml is specified: Change the value specified in <application-name> to another name and then re-import.
If <application-name> of application.xml is not specified (if application.xml is omitted): Change the EAR file name (application directory name in the exploded archive format) to another name and then re-import.

Note that if the objects need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47721-W

The objects in the EJB module could not be bound as Portable Global JNDI names because there are already modules with the same names under the same application in the naming service. (uri = aa....aa, module name = bb....bb)

aa....aa: Module URI

bb....bb: Standard module name

Description

A module in the same application with the same standard module name already exists in the naming service. Therefore, the objects in the EJB module could not be registered in the Portable Global JNDI name.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

However, action is required if one of the following cases is applicable:

If there is a client that looks up the objects in this EJB-JAR module using the Portable Global JNDI name.
If a resource reference is defined in this EJB-JAR module using a name beginning with java:module.

Action

If the objects must be registered in the Portable Global JNDI name for this EJB-JAR module, take the following action to change the standard module name:

If <module-name> of ejb-jar.xml is specified: Change the value specified in <module-name> to another name and then re-import.
If <module-name> of ejb-jar.xml is not specified (if ejb-jar.xml is omitted): Change the EJB-JAR file name (EJB directory name in the exploded archive format) to another name and then re-import.

Note that if the objects need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47722-W

The objects in the Web module could not be bound as Portable Global JNDI names because there are already modules with the same names under the same application in the naming service. (uri = aa....aa, module name = bb....bb)

aa....aa: Module URI

bb....bb: Standard module name

Description

A module in the same application with the same standard module name already exists in the naming service. Therefore, the objects in the Web module could not be registered in the Portable Global JNDI name.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

However, action is required if one of the following cases is applicable:

If there is a client that looks up the objects in this Web module (Web application) using the Portable Global JNDI name.
If a resource reference is defined in this Web module (Web application) using a name beginning with java:module.

Action

If the objects must be registered in the Portable Global JNDI name for this Web module (Web application), take the following action to change the standard module name:

Change the WAR file name (WAR directory name in the exploded archive format) to another name and then re-import.

If <module-name> of web.xml is specified: Change the value specified in <module-name> to another name and then re-import.
If <module-name> of web.xml is not specified (if web.xml is omitted): Change the WAR file name (WAR directory name in the exploded archive format) to another name and then re-import.

Note that if the objects need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47723-W

The objects in the RAR module could not be bound as Portable Global JNDI names because there are already modules with the same names under the same application in the naming service. (uri = aa....aa, module name = bb....bb)

aa....aa: Module URI

bb....bb: Standard module name

Description

A module in the same application with the same standard module name already exists in the naming service. Therefore, the objects in the resource adapter module could not be registered in the Portable Global JNDI name.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

Action

If the objects must be registered in the Portable Global JNDI name for this resource adapter module, take the following action to change the standard module name:

Change the RAR file name of the resource adapter module to another name and then re-import.

Note that if the objects need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47730-E

The JNDI name specified in aa....aa is invalid. (name = bb....bb, JNDI name = cc....cc)

aa....aa: Tag name

bb....bb: Application display name

cc....cc: JNDI name

Description

The prefix of the JNDI name specified in the resource reference name is incorrect. You can use the following prefixes when you specify the resource reference name in the JNDI fully-qualified name (JNDI name beginning with java:):

java:app
java:comp
java:global
java:module

However, if one of the following conditions is applicable, the corresponding prefix cannot be used:

java:app

The registration of the Portable Global JNDI name is disabled.
The standard application name is invalid (KDJE47710-W is output).
The standard application name is duplicated (KDJE47720-W is output).

java:global

The registration of the Portable Global JNDI name is disabled.

java:module

The registration of the Portable Global JNDI name is disabled.
The standard application name is invalid (KDJE47710-W is output).
The standard application name is duplicated (KDJE47720-W is output).
The standard module name is invalid (KDJE47711-W is output).
The standard module name is duplicated (one of the messages from KDJE47721-W to KDJE47723-W is output).

Action

Identify the resource reference definition with the incorrect prefix based on the displayed tag name and JNDI name, and then revise the prefix of the JNDI name specified in the name.
Review, and if necessary revise, the standard application name and the standard module name.
If the registration of the Portable Global JNDI name is disabled, enable the registration of the name. If the version is upgraded from 08-70 or an earlier version, the registration might be disabled.

KDJE47731-E

There is already an object with the same JNDI name specified in aa....aa. (name = bb....bb, JNDI name = cc....cc)

aa....aa: Tag name

bb....bb: Application display name

cc....cc: JNDI name

Description

The JNDI name specified in the resource reference name is already registered as another object or context.

You cannot specify a JNDI name that is duplicated in other resource references, automatically handled objects, or reserved words determined in the standard specifications.

Action

Identify the resource reference definition with the duplicated name based on the displayed tag name and JNDI name, and then revise the JNDI name specified in the name.

Note that depending on the prefix of the JNDI name, the range of names considered as duplicated differ as follows:

For java:global: The Global JNDI name cannot be duplicated in all the J2EE servers sharing the same naming service.
For java:app: The Global JNDI name cannot be duplicated in the same application.
For java:module: The Global JNDI name cannot be duplicated in the same module.
For java:comp: The Global JNDI name cannot be duplicated in the same component.

KDJE48200-E

A format error occurred in a queue configuration file. (cause = aa....aa, file = bb....bb)

aa....aa: Reason

bb....bb: File name

Description: A format error was detected in a queue configuration file.
Action: Re-check the details of the definition file. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48201-W

No queue is registered in the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description

An exception occurred while registering the specified queue in the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48202-W

No queue has been deleted from the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred while deleting the specified queue from the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48203-W

No queue has been deleted from the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description

An exception occurred while deleting the specified queue from the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48204-W

JMSConnectionFactoryDummy is not registered in the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred while registering an object required for executing MDB in the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48205-W

JMSConnectionFactoryDummy is registered in the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description

An exception occurred while registering an object required for executing MDB in the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48206-W

JMSXAQueueConnectionFactory is not registered in the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred while registering an object required for executing MDB in the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48207-W

JMSXAQueueConnectionFactory is not registered in the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description

An exception occurred while registering an object required for executing MDB in the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48208-W

JMSConnectionFactoryDummy has not been deleted from the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred when deleting an object necessary for executing MDB from the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48209-W

JMSConnectionFactoryDummy has not been deleted from the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description

An exception occurred when deleting an object necessary for executing MDB from the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48210-W

JMSXAQueueConnectionFactory has not been deleted from the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred when deleting an object necessary for executing MDB from the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48211-W

JMSXAQueueConnectionFactory has not been deleted from the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description

An exception occurred when deleting an object necessary for executing MDB from the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48212-W

No queue is registered in the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred while registering the specified queue in the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48213-W

An error was detected in the queue configuration file. (error property = aa....aa)

aa....aa: Property name

Description: An invalid queue definition was detected in the queue configuration file.
Action: Re-check the details of the definition file. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48214-I

The NonQueueConfigFile mode does not require a queue configuration file.

Description: The environment can be set up without using the queue definition file.

KDJE48215-I

The QueueConfigFile mode requires a queue configuration file.

Description: The queue definition information must be described in the queue definition file.

KDJE48216-E

The queue configuration information is not registered. (display name = aa....aa)

aa....aa: Resource adapter display name

Description: The queue information could not be collected because the queue definition information is not registered.
Action: Check again if the queue has been created properly. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48500-W

No resource reference is defined for the display name aa....aa.

aa....aa: Resource adapter display name

Description: The reference for the resource adapter is not set correctly.
Action: Set the reference for the resource adapter correctly.

KDJE48501-W

Logwriter is not set for the ManagedConnectionFactory instance. (display name = aa....aa)

aa....aa: Resource adapter display name

Description: Logwriter is not set for the ManagedConnectionFactory instance.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48502-W

Logwriter is not set for the ManagedConnection instance. (display name = aa....aa)

aa....aa: Resource adapter display name

Description: LogWriter is not set for the ManagedConnection instance.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48503-W

A Logwriter instance has not been created. (display name = aa....aa)

aa....aa: Resource adapter display name

Description: An exception occurred during creation of a LogWriter.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48504-W

An Mbean instance has not been created. (display name = aa....aa)

aa....aa: Resource adapter display name

Description: An exception occurred during creation of MBean.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48505-W

An Mbean instance has not been deleted. (display name = aa....aa)

aa....aa: Resource adapter display name

Description: An exception occurred during deletion of MBean.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48506-W

Recovery information cannot be deleted from the RecoveryManager. (display name = aa....aa)

aa....aa: Resource adapter display name

Description: An exception occurred while deleting recovery information.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48507-W

Connection factory cannot be deleted from the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description: An exception occurred while deleting ConnectionFactory from the JNDI namespace.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48508-W

Connection factory cannot be deleted from the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description: An exception occurred while deleting ConnectionFactory from the JNDI namespace.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48509-W

Configuration property has not been set for the ManagedConnectionFactory instance. (display name = aa....aa, method name = bb....bb, cause = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Method name

cc....cc: Exception name and detailed message of the exception

Description: An exception occurred while invoking the initialization method of the ManagedConnectionFactory.
Action: See the exception name, exception details, and log file of the resource adapter, and then resolve the problem.

KDJE48510-W

The value of aa....aa is outside the valid range. The default value (bb....bb) will be used.

aa....aa: Property name

bb....bb: Default value

Description

The property value is invalid.

The default value will be used.

Action

When you change the property from default value, modify the property value, and then restart the J2EE Server.

KDJE48511-E

Connection factory cannot be loaded. (class name = aa....aa, cause = bb....bb)

aa....aa: Class name

bb....bb: Exception name and detailed message of exception

Description: Connection factory cannot be loaded.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48512-E

An instance of the connection factory class could not be created. (class name = aa....aa, cause = bb....bb)

aa....aa: Class name

bb....bb: Exception name and detailed message of exception

Description: An instance of the connection factory cannot be created.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48513-E

An exception occurred during acquisition of a method. (cause = aa....aa)

aa....aa: Exception name and detailed message of exception

Description: An exception occurred during acquisition of a method.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48514-E

An exception occurred during setting of a property value. (object = aa....aa, setter method name = bb....bb, property value = cc....cc, cause = dd....dd)

aa....aa: Class name

bb....bb: Setter method name

cc....cc: Property value

dd....dd: Exception name and detailed message of exception

Description: An exception occurred while setting a property value.
Action: Confirm that the property is correct.

KDJE48515-E

An unexpected exception occurred during a connection test of a resource adapter. (cause = aa....aa)

aa....aa: Exception name and detailed message of exception

Description: An unexpected exception occurred during a connection test of a resource adapter.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48516-E

An attempt to create ManagedConnection has failed. (cause = aa....aa)

aa....aa: Exception name and detailed message of exception

Description: An attempt to create ManagedConnection has failed.
Action: Investigate based on the message exception name and the detailed message of the exception, and remove the cause.

KDJE48517-E

The transaction support level is invalid. (transaction support = aa....aa)

aa....aa: Transaction support

Description: The transaction support level is invalid.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48518-E

An unexpected exception occurred during invocation of a validate method. (class name = aa....aa, cause = bb....bb)

aa....aa: Class name

bb....bb: Exception name and detailed message of exception

Description: An unexpected exception occurred during invocation of a validate method.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48519-E

A connection test has failed. (cause = aa....aa)

aa....aa: Exception name and detailed message of exception

Description

The connection test has failed.

Action

Check the resource adapter settings and the server to be connected.

When you are using the Oracle JDBC driver, this message might be output if oracle.jdbc.autoCommitSpecCompliant=false is not set in usrconf.properties (user property file for J2EE servers).

For details about the necessity of the oracle.jdbc.autoCommitSpecCompliant=false setting, 3.6.6 Preconditions and notes on connecting to Oracle in the uCosminexus Application Server Common Container Functionality Guide.

KDJE48520-E

A resource adapter cannot be used in basic mode.

Description: A resource adapter cannot be used in basic mode.
Action: Use the 1.4 mode.

KDJE48521-E

An XA transaction cannot be used when light transaction is enabled.

Description: An XA transaction cannot be used when light transaction functionality is enabled.
Action: Set the ejbserver.distributedtx.XATransaction.enabled key of the user property file to true, and then restart the server.

KDJE48522-E

Logwriter creation has failed. (log channel name = aa....aa)

aa....aa: Log channel name

Description: An attempt to create Logwriter has failed.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48523-E

Logwriter creation has failed. (log component name = aa....aa)

aa....aa: Log component name

Description: An attempt to create Logwriter has failed.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48524-E

An attempt to set Logwriter to ManagedConnectionFactory has failed. (class name = aa....aa)

aa....aa: Class name

Description: An attempt to set Logwriter to ManagedConnectionFactory has failed.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48530-E

A data-source connection test cannot be performed except basic mode.

Description: A data-source connection test can be performed only in the basic mode.
Action: Switch the J2EE server mode to basic mode.

KDJE48531-E

An XA data-source connection test cannot be performed in basic mode.

Description: An XA data-source connection test cannot be performed in basic mode
Action: Switch the J2EE server mode to 1.4 mode.

KDJE48532-E

An XA data-source connection test cannot be performed when light transaction is enabled.

Description: An XA data-source connection test cannot be performed in the case of light transaction functionality.
Action: When performing XA data-source connection test, set ejbserver.distributedtx.XATransaction.enabled key of user property file to true.

KDJE48533-E

A resource descriptor is invalid. <java-impl> does not exist. (resource = aa....aa)

aa....aa: Resource name

Description: ResourceDescriptor is invalid. <java-impl>tag does not exist.
Action: Contact the maintenance personnel.

KDJE48534-E

A resource descriptor is invalid. <class-name> does not exist. (resource = aa....aa)

aa....aa: Resource name

Description: ResourceDescriptor is invalid. <class-name> tag does not exist.
Action: Contact the maintenance personnel.

KDJE48535-E

The resource descriptor aa....aa does not have an XA resource.

aa....aa: Display name

Description: The specified ResourceDescriptor does not have an XA resource.
Action: Contact the maintenance personnel.

KDJE48536-E

The mandatory property aa....aa does not exist.

aa....aa: Property name

Description: The mandatory property does not exist in the specified ResourceDescriptor.
Action: Contact the maintenance personnel.

KDJE48537-E

An attempt was make to connect the incorrect driver aa....aa to bb....bb.

aa....aa: JDBC driver name

bb....bb: URL

Description

The specified JDBC driver (aa....aa) cannot be connected to bb....bb URL.

Action

Incorrect URL might be specified.

Check the URL.

KDJE48538-E

A data-source connection test has failed. (cause = aa....aa)

aa....aa: Reason

Description: The data-source connection test has failed.
Action: Check the settings of the database to be connected or the data-source.

KDJE48539-E

An XA data-source connection test has failed. (cause = aa....aa)

aa....aa: Reason

Description: The XA data-source connection test has failed.
Action: Check the settings of the database to be connected or an XA data-source.

KDJE48540-E

An unexpected exception occurred. (cause = aa....aa)

aa....aa: Reason

Description: An unexpected exception occurred.
Action: Contact the maintenance personnel.

KDJE48541-E

ConnectorDescriptor was not found. (module name = aa....aa)

aa....aa: ConnectorDescriptor

Description

ConnectorDescriptor (aa....aa) was not found.

The status of the resource adapter might be invalid.

Action

Restart the resource adapter, and then redeploy the J2EE application.

KDJE48542-E

ResourceDescriptor was not found. Module name =aa....aa

aa....aa: ResourceDescriptor

Description

ResourceDescriptor (aa....aa) was not found.

The status of the resource adapter might be invalid.

Action

Restart the resource adapter, and then redeploy the J2EE application.

KDJE48543-E

The same name connector descriptor already exists. (display name = aa....aa)

aa....aa: Display name

Description: The same name ConnectorDescriptor already exists.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48544-E

A resource name that corresponds to the resource descriptor was not found. (display name = aa....aa)

aa....aa: Display name

Description: ResourceDescriptor corresponding to a resource name was not found.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48545-E

An error occurred during creation of a ManagedConnectionFactory instance.

Description: An error occurred during creation of a ManagedConnectionFactory instance.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48546-E

The display name of connectorDescriptor was not found. (display name=aa....aa)

aa....aa: Resource adapter name

Description

ConnectorDescriptor corresponding to the resource adapter name (aa....aa) was not found.

The status of the resource adapter might be invalid.

Action

Restart the resource adapter, and then redeploy the J2EE application.

KDJE48547-E

A resource adapter cannot be stopped while it is being used. (display name = aa....aa)

aa....aa: Resource adapter name

Description: A resource adapter (aa....aa) cannot be stopped while it is being used.
Action: Stop the J2EE application that is using the resource adapter, and then re-execute the operation.

KDJE48548-E

No queue was registered in the namespace. (display name = aa....aa)

aa....aa: Display name

Description

No queue was registered in the namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48549-E

The QueueConfigFileName property was not found in the ra.xml file.

Description: The queue configuration file name property was not found in the ra.xml.
Action: Revise the queue configuration file. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48550-E

A queue configuration file was not found. (URL of key configuration file = aa....aa)

aa....aa: Queue configuration file URL

Description

A queue configuration file (aa....aa) was not found.

Action

Revise the queue configuration file name specified in the resource adapter property.
Revise the access permissions for the queue configuration file and queue configuration file storage directory.

KDJE48551-E

QueueImplClass was not found because a key configuration file was invalid.

Description: QueueImpl class was not found because a queue configuration file was invalid.
Action: Revise QueueImpl class defined in the queue configuration file.

KDJE48552-E

Format error queue configuration file reason: found no queue information.

Description: Queue information was not found because queue configuration file was invalid.
Action: Revise the queue configuration file.

KDJE48553-E

Queue placement information could not be acquired. (display name = aa....aa, cause = bb....bb)

aa....aa: Display name

bb....bb: Exception name and details of exception

Description: The queue placement information cannot be acquired.
Action: Revise the aa....aa queue configuration file.

KDJE48554-E

An error occurred during creation of an XADataSource instance.

Description: An error occurred during creation of a XADataSource instance.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48555-E

A J2EE resource does not exist. (URI = aa....aa)

aa....aa: URI

Description: A J2EE resource does not exist.
Action: Confirm that the J2EE resource of aa....aa exists.

KDJE48556-E

The service cannot start. (module name = aa....aa)

aa....aa: J2EE Module name

Description: The service cannot start.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48557-E

The service cannot be stopped. (module name = aa....aa)

aa....aa: J2EE Module name

Description: The service cannot be stopped.
Action: Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48558-E

A J2EE connector does not exist. (URI = aa....aa)

aa....aa: URI

Description: A J2EE connector does not exist.
Action: Confirm that the J2EE connector of aa....aa exists.

KDJE48570-E

An exception occurred during setting logger object to Cosminexus Reliable Messaging. (cause = aa....aa, resource adapter name = bb....bb)

aa....aa: Detailed message of exception

bb....bb: Resource adapter name

Description: An attempt to set the logger to Cosminexus Reliable Messaging has failed.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48571-E

An exception occurred during Cosminexus Reliable Messaging starting. (cause = aa....aa, resource adapter name = bb....bb)

aa....aa: Detailed message of exception

bb....bb: Resource adapter name

Description: An attempt to start Cosminexus Reliable Messaging has failed.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48580-E

Starting the J2EE resource adapter "aa....aa" failed. Detail=XA Transaction is not available when light transaction is enabled.

aa....aa: Resource adapter name

Description

An XA transaction cannot be used when light transaction functionality is enabled.

Therefore, resource adapter (aa....aa) cannot be started.

Action

In the case of using a distributed transaction, specify true in ejbserver.distributedtx.XATransaction.enabled key of user-defined file.

In the case of not using a distributed transaction, use the resource adapter that does not use an XA transaction.

KDJE48581-E

Starting the J2EE resource "aa....aa" failed. Detail=DataSource is not available when light transaction is enabled.

aa....aa: Data source name

Description

Data-source cannot be used when light transaction functionality is enabled.

Therefore, resource (aa....aa) cannot be started.

Action

In the case of using a distributed transaction, specify true in ejbserver.distributedtx.XATransaction.enabled key of user-defined file.

In the case of not using a distributed transaction, use a DB Connector that does not use an XA transaction.

KDJE48582-E

The linked resource adapter has not started. (linked resource adapter = aa....aa)

aa....aa: Linked resource adapter name

Description: The linked resource adapter has not started.
Action: Start the linked resource adapter.

KDJE48583-E

The linked resource adapter has not stopped. (linked resource adapter = aa....aa)

aa....aa: Linked resource adapter name

Description: The linked resource adapter has not stopped.
Action: Stop the linked resource adapter.

KDJE48584-E

The linked resource adapter is not Cosminexus Reliable Messaging. (linked resource adapter = aa....aa)

aa....aa: Linked resource adapter name

Description: The linked resource adapter is not Cosminexus Reliable Messaging.
Action: Specify Cosminexus Reliable Messaging for the linked resource adapter of DB Connector for Cosminexus Reliable Messaging.

KDJE48585-E

The linked resource adapter is not DB Connector for Cosminexus Reliable Messaging. (linked resource adapter = aa....aa)

aa....aa: Linked resource adapter name

Description: The linked resource adapter is not DB Connector for Cosminexus Reliable Messaging.
Action: Specify DB Connector of Cosminexus Reliable Messaging for the linked resource adapter of Cosminexus Reliable Messaging.

KDJE48586-E

The property that indicates the linked resource adapter is not defined. (resource adapter = aa....aa)

aa....aa: Resource adapter name

Description: The property that indicates the linked resource adapter is not defined.
Action: A link needs to be set as property in DB Connector for Cosminexus Reliable Messaging or Cosminexus Reliable Messaging. Revise the property settings.

KDJE48587-E

The linked resource adapter has already started. (linked resource adapter = aa....aa)

aa....aa: Linked resource adapter name

Description

The linked resource adapter is already running.

Action

Revise the settings paying attention to the following points:

DB Connector for Cosminexus Reliable Messaging needs to be started before the Cosminexus Reliable Messaging to be linked.
DB Connector for Cosminexus Reliable Messaging and Cosminexus Reliable Messaging can only be linked one-to-one.

KDJE48588-E

This resource adapter is linked to multiple resource adapters. (resource adapter = aa....aa)

aa....aa: Resource adapter name

Description: This resource adapter is linked to multiple resource adapters.
Action: DB Connector for Cosminexus Reliable Messaging and Cosminexus Reliable Messaging can only be linked one-to-one. Set this resource adapter at the destination to be linked so that only one resource adapter exists.

KDJE48589-E

An error occurred during creation of a javax.resource.spi.ResourceAdapter instance.(resname=aa....aa Detail = bb....bb)

aa....aa: Application display name: Resource display name

bb....bb: Exception character strings

Description: An exception occurred during creation of a javax.resource.spi.ResourceAdapter instance.
Action: Make sure that the class name specified in the <resourceadapter-class> tag of ra.xml is correct. Also check the processing of the default constructor of the corresponding class.

KDJE48590-E

An exception occurred in javax.resource.spi.ResourceAdapter.aa....aa(). (resname=bb....bb Detail = cc....cc)

aa....aa: Method name

bb....bb: Application display name: Resource display name

cc....cc: Exception character string

Description: An exception occurred in the javax.resource.spi.ResourceAdapter method.
Action: Check the processing of the method of javax.resource.spi.ResourceAdapter in which the exception has occurred.

KDJE48591-E

Cannot associate javax.resource.spi.ManagedConnectionFactory and javax.resource.spi.ResourceAdapter (resname=aa....aa,Detail=bb....bb).

aa....aa: Application display name: Resource display name

bb....bb: Exception character strings

Description

javax.resource.spi.ManagedConnectionFactory and javax.resource.spi.ResourceAdapter cannot be correlated.

Action

Check if the interface javax.resource.spi.ResourceAdapterAssociation is implemented in the class specified with the <managedconnectionfactory-class> tag of ra.xml.

If implemented, check the processing of the setResourceAdapter method.

KDJE48592-E

An exception occurred in javax.resource.spi.work.Work#run(). (resname=aa....aa Detail = bb....bb)

aa....aa: Application display name: Resource display name

bb....bb: Exception character strings

Description: An exception occurred in the run() method of javax.resource.spi.work.Work.
Action: Check the processing of the method of javax.resource.spi.work.Work in which the exception occurred.

KDJE48593-E

An exception occurred in javax.resource.spi.work.WorkListener#aa....aa(). (resname=bb....bb Detail = cc....cc)

aa....aa: Method name

bb....bb: Application display name: Resource display name

cc....cc: Exception character string

Description: An exception occurred in a method of javax.resource.spi.work.WorkListener.
Action: Check the processing of the method of javax.resource.spi.work.WorkListener in which the exception occurred.

KDJE48594-W

Configuration property has not been set for the javax.resource.spi.ResourceAdapter instance. (display name = aa....aa, method name = bb....bb, cause = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Method name

cc....cc: Exception name and detailed message of the exception

Description: An exception occurred while invoking the initialization method of the ResourceAdapter.
Action: See the exception name, exception details, and log file of the resource adapter, and then resolve the problem.

KDJE48595-E

The connection factory class does not implement the connection factory interface. (resname = aa....aa, connection factory class = bb....bb, connection factory interface = cc....cc).

aa....aa: Application display name: Resource display name

bb....bb: Specified value of the <connectionfactory-impl-class> tag

cc....cc: Specified value of the <connectionfactory-interface> tag

Description: The interface specified with the <connectionfactory-interface> tag is not implemented in the class specified with the <connectionfactory-impl-class> tag of ra.xml.
Action: Check if the specification of the <connectionfactory-impl-class> tag or <connectionfactory-interface> tag is correct.

KDJE48596-E

The connection factory interface could not be found. (resname = aa....aa,connection factory interface = bb....bb)

aa....aa: Application display name: Resource display name

bb....bb: Specified value of the <connectionfactory-interface> tag

Description: The interface specified with the <connectionfactory-interface> tag of ra.xml was not found from the class path.
Action: Check if the specification of the <connectionfactory-interface> tag is correct.

KDJE48597-E

An error occurred during creation of an administered object instance. (resource name = aa....aa, details = bb....bb)

aa....aa: Application display name: Resource display name

bb....bb: Exception character strings

Description: An exception occurred when generating an instance of the object to be managed.
Action: Make sure that the class name specified with the <adminobject-class> tag of ra.xml is correct by checking the processing of the default constructor of the corresponding class.

KDJE48598-W

An attempt to set a configuration property for the administered object failed. (resource name = aa....aa, property name = bb....bb)

aa....aa: Application display name: Resource display name

bb....bb: Property name

Description: An attempt to set up a property in the object to be managed has failed.
Action: For details about setting up the specifiable properties in the object to be managed, see the documents of the resource adapter.

KDJE48600-W

The timeout for connection-error detection is disabled because the connection pool is disabled. (resource name = aa....aa)

aa....aa: Resource name

Description: The timeout for connection-error detection is disabled because the connection pool is disabled.
Action: When using the timeout for connection-error detection, enable the connection pooling functionality.

KDJE48601-W

The timeout for connection-error detection is disabled because the maximum size of the connection pool is unlimited. (resource name = aa....aa)

aa....aa: Resource name

Description: The timeout for connection-error detection is disabled because the maximum size of the connection pool is unlimited.
Action: When using the timeout for connection-error detection, set a limit to the maximum size of the connection pool.

KDJE48602-W

A timeout for connection-error detection occurred.

(resource name = aa....aa, connection ID = bb....bb, thread = cc....cc, rootAP = dd....dd)

aa....aa: Resource name

bb....bb: Connection ID

cc....cc: Execution thread

dd....dd: Root AP information

Description: A timeout for connection error detection occurred because there was no response from the connection in the connection pool.
Action: Check the server to be connected and the connection circuit.

KDJE48603-W

Connection-error detection was not executed. (resource name = aa....aa)

aa....aa: Resource name

Description: The connection-error detection cannot be executed because the connection control threads were depleted.
Action: Check the server to be connected and the connection circuit.

KDJE48604-W

The value of connection-sweeper is under an hour(3600 seconds). (resource name = aa....aa, SweeperInterval = bb....bb, ConnectionTimeout = cc....cc)

aa....aa: Resource name

bb....bb: Connection sweeper operating time interval

cc....cc: Value of timeout until the connection is released

Description: The value of the connection sweeper is under one hour (3600 seconds). We recommend that you set one hour (3600 seconds) or more for both, the connection sweeper operating time interval and the value of the timeout until the connection is released.
Action: Revise the value specified for connection sweeper operating time interval and the value of a timeout until the connection is released. For details, see 3.15.7 Connection sweeper in the uCosminexus Application Server Common Container Functionality Guide.

KDJE48605-E

An error was detected during the processing to start J2EE connectors.

Description

An attempt to start the resource adapter during the startup of the J2EE server has failed.

Forcibly terminate the J2EE server without performing the recovery process for the transaction.

Action

From the message output immediately before this message, determine the resource adapter that could not be started, and then remove the cause of failure in starting the resource adapter.

KDJE48606-E

A resource adapter does not have a required connection definition for outbound communication.

Description

A resource adapter does not have the connection definition used for Outbound communication.

The test will be interrupted because the resource adapter is not a target for the resource connection test.

Action

Either a wrong resource adapter is specified or the definition of the resource adapter is invalid. Revise the settings, and then re-execute the command.

KDJE48901-E

The XA data-source connection test cannot be performed because the data source is not supported.

Description: The XA data-source connection test cannot be performed because the data-source is not supported.
Action: Connect to the database using the DB connector.

KDJE49000-W

No recovery information has been deleted from the RecoveryManager. (resource name = aa....aa)

aa....aa: Resource name

Description: An exception occurred while deleting recovery information.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE49001-W

No data source has been deleted from the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description: An exception occurred while deleting the DataSource from JNDI namespace.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE49002-W

An Mbean instance has not been created. (JNDI name = aa....aa)

aa....aa: JNDI name

Description: An exception occurred during creation of MBean.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE49003-W

An Mbean instance has not been removed. (JNDI name = aa....aa)

aa....aa: JNDI name

Description: An exception occurred during deletion of MBean.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE49510-I

The connection pool warmup was not executed. (resource name = aa....aa, resource type = bb....bb, minimum size = cc....cc, maximum size = dd....dd)

aa....aa: Resource display name

bb....bb: Resource type (jdbc: Datasource, or connector: Resource adapter)

cc....cc: Minimum size of connection pool

dd....dd: Maximum size of connection pool

Description: The connection pool warmup was not executed.

KDJE49511-I

The connection pool warmup started. (resource name = aa....aa, resource type = bb....bb, minimum size = cc....cc, maximum size = dd....dd)

aa....aa: Resource display name

bb....bb: Resource type (jdbc: Datasource, or connector: Resource adapter)

cc....cc: Minimum size of connection pool

dd....dd: Maximum size of connection pool

Description: The connection pool warmup was started.

KDJE49512-I

The connection pool warmup finished normally. (resource name = aa....aa, resource type = bb....bb, minimum size = cc....cc, maximum size = dd....dd, size = ee....ee)

aa....aa: Resource display name

bb....bb: Resource type (jdbc: Datasource, or connector: Resource adapter)

cc....cc: Minimum size of connection pool

dd....dd: Maximum size of connection pool

ee....ee: Connection pool size

Description: The connection pool warmup finished normally.

KDJE49513-W

The connection pool warmup failed. (resource name = aa....aa, resource type = bb....bb, minimum size = cc....cc, maximum size = dd....dd, size = ee....ee, cause = ff....ff)

aa....aa: Resource display name

bb....bb: Resource type (jdbc: Datasource, or connector: Resource adapter)

cc....cc: Minimum size of connection pool

dd....dd: Maximum size of connection pool

ee....ee: Connection pool size

ff....ff: Error information

Description: An attempt to warmup the connection pool has failed.
Action: See the error details, and then take action.

KDJE49514-I

The connection pool will now be cleared. (resource name = aa....aa, resource type = bb....bb, mode = cc....cc)

aa....aa: Resource name

bb....bb: Resource type (jdbc: Datasource or jca: Resource adapter)

cc....cc: Mode name (normal, or plan)

Description: The connection pool will now be cleared.

KDJE49515-I

The connection pool was cleared successfully. (resource name = aa....aa, resource type = bb....bb, mode = cc....cc)

aa....aa: Resource name

bb....bb: Resource type (jdbc: Datasource or jca: Resource adapter)

cc....cc: Mode name (normal, or plan)

Description: The connection pool was cleared successfully.

KDJE49516-E

An attempt to clear the connection pool has failed. (resource name = aa....aa, resource type = bb....bb, mode = cc....cc)

aa....aa: Resource name

bb....bb: Resource type (jdbc: Datasource or jca: Resource adapter)

cc....cc: Mode name (normal, or plan)

Description: An attempt to clear the connection pool has failed.
Action: See the error details of command execution, and then take action.

KDJE49517-I

The connection pool will now be cleared. (resource name = aa....aa, resource type = bb....bb, mode = cc....cc, application name = dd....dd)

aa....aa: Resource name

bb....bb: Resource type (jdbc: Datasource or jca: Resource adapter)

cc....cc: Mode name (normal, or plan)

dd....dd: Application name

Description: The connection pool will now be cleared.

KDJE49518-I

The connection pool was cleared successfully. (resource name = aa....aa, resource type = bb....bb, mode = cc....cc, application name = dd....dd)

aa....aa: Resource name

bb....bb: Resource type (jdbc: Datasource or jca: Resource adapter)

cc....cc: Mode name (normal, or plan)

dd....dd: Application name

Description: The connection pool was cleared successfully.

KDJE49519-E

An attempt to clear the connection pool has failed. (resource name = aa....aa, resource type = bb....bb, mode = cc....cc, application name = dd....dd)

aa....aa: Resource name

bb....bb: Resource type (jdbc: Datasource or jca: Resource adapter)

cc....cc: Mode name (normal, or plan)

dd....dd: Application name

Description: An attempt to clear the connection pool has failed.
Action: See the error details of command execution, and then take action.

KDJE49520-I

All connection pools will now be cleared.

Description: All connection pools will now be cleared.

KDJE49521-I

All connection pools were cleared successfully.

Description: All connection pools were cleared successfully.

KDJE49522-E

Some attempts to clear connection pools have failed.

Description: Few attempts to clear the connection pools have failed.
Action: See the error details of command execution, and then take action.

KDJE49523-I

Connections that exceed the specified time will now be closed. (time = aa....aa seconds, resource name = bb....bb)

aa....aa: Time (Seconds)

bb....bb: Resource name

Description: Connections that exceed the specified time will now be closed.

KDJE49524-I

Connections that exceed the specified time were closed successfully. (time = aa....aa seconds, resource name = bb....bb)

aa....aa: Time (Seconds)

bb....bb: Resource name

Description: Connections that exceed the specified time were closed successfully.

KDJE49525-E

An attempt to close a connection that exceeds the specified time has failed. (time = aa....aa seconds, resource name = bb....bb)

aa....aa: Time (Seconds)

bb....bb: Resource name

Description: An attempt to close a connection that exceeds the specified time has failed.
Action: See the error details of command execution, and then take action.

KDJE49526-I

Connections that exceed the specified time will now be closed. (time = aa....aa seconds)

aa....aa: Time (Seconds)

Description: Connections that exceed the specified time will now be closed.

KDJE49527-I

Connections that exceed the specified time were closed successfully. (time = aa....aa seconds)

aa....aa: Time (Seconds)

Description: Connections that exceed the specified time were closed successfully.

KDJE49528-E

Some attempts to close connections that exceed the specified time have failed. (time = aa....aa seconds)

aa....aa: Time (Seconds)

Description: An attempt to close a connection that exceeds the specified time has failed.
Action: See the error details of command execution, and then take action.

KDJE49529-I

The connection will now be closed. (resource name = aa....aa, connection ID = bb....bb)

aa....aa: Resource name

bb....bb: Connection ID

Description: The connection will now be closed.

KDJE49530-I

The connection was closed successfully. (resource name = aa....aa, connection ID = bb....bb)

aa....aa: Resource name

bb....bb: Connection ID

Description: The connection was closed successfully.

KDJE49531-E

An attempt to close the connection has failed. (resource name = aa....aa, connection ID = bb....bb)

aa....aa: Resource name

bb....bb: Connection ID

Description: An attempt to close the connection has failed.
Action: See the error details of command execution, and then take action.

KDJE49532-I

The number of connections was adjusted. (resource name = aa....aa, before = bb....bb, after = cc....cc)

aa....aa: Resource name

bb....bb: Number of connections before adjustment

cc....cc: Number of connections after adjustment

Description: The number of connections of connection pool was adjusted.

KDJE49533-W

A timeout occurred while deleting a connection. (resource name = aa....aa, connection ID = bb....bb)

aa....aa: Resource name

bb....bb: Connection ID

Description: A timeout occurred while deleting a connection by adjusting the number of connections.
Action: Check the server to be connected and the connection circuit.

KDJE49600-E

The memberResourceAdapterName[n] property is not defined. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description: The memberResourceAdapterName[n] property is not defined.
Action: Define one or more memberResourceAdapterName[n] properties.

KDJE49601-E

The property value is empty. (property name = aa....aa, root resource adapter = bb....bb)

aa....aa: Property name

bb....bb: Root resource adapter name

Description: The memberResourceAdapterName[n] property value is empty.
Action: Set the display name of member resource adapter in memberResourceAdapterName[n] property.

KDJE49602-E

Values of the memberResourceAdapterName[n] property are duplicated. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description: Values of memberResourceAdapterName[n] property are duplicated.
Action: Make the specification so that the value of memberResourceAdapterName[n] property is not duplicated.

KDJE49603-E

The member resource adapter does not exist. (member resource adapter = aa....aa, root resource adapter = bb....bb)

aa....aa: Member resource adapter name specified in memberResourceAdapterName[n] property

bb....bb: Root resource adapter name

Description: The member resource adapter specified in memberResourceAdapterName[n] property does not exist.
Action: Confirm that the member resource adapter specified in the memberResourceAdapterName[n] property exists.

KDJE49604-E

The resource adapter cannot be used as a member resource adapter. (resource adapter = aa....aa, root resource adapter = bb....bb)

aa....aa: Resource adapter name specified in memberResourceAdapterName[n] property

bb....bb: Root resource adapter name

Description: Resource adapter specified in memberResourceAdapterName[n] property cannot be used as a member resource adapter.
Action: Confirm that the resource adapter specified in the memberResourceAdapterName[n] property is the DB Connector for member resource adapter.

KDJE49605-E

The member resource adapter has not started. (member resource adapter = aa....aa, root resource adapter = bb....bb)

aa....aa: Member resource adapter name specified in memberResourceAdapterName[n] property

bb....bb: Root resource adapter name

Description: The member resource adapter specified in memberResourceAdapterName[n] property is not running. To start the root resource adapter, you must start all the member resource adapters.
Action: Confirm that the member resource adapter specified in the memberResourceAdapterName[n] property is running.

KDJE49606-E

The member resource adapter is being used as the member resource adapter of another root resource adapter. (member resource adapter = aa....aa, root resource adapter = bb....bb, duplicated root resource adapter = cc....cc)

aa....aa: Member resource adapter name specified in memberResourceAdapterName[n] property

bb....bb: Root resource adapter name

cc....cc: Duplicated root resource adapter name

Description: The member resource adapter specified in memberResourceAdapterName[n] property is used as the member resource adapter of another root resource adapter. The member resource adapter cannot be a member resource adapter of multiple root resource adapters.
Action: Specify the display name of member resource adapter that is not specified in memberResourceAdapterName[n] property of other root resource adapter in the memberResourceAdapterName[n] property.

KDJE49607-E

Not all member resource adapters have been imported from the same RAR file. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description: The member resource adapter specified in the memberResourceAdapterName[n] property is the resource adapter imported from a different rar file. All the member resource adapters need to be the resource adapters imported from the same rar file.
Action: Specify the display name of all the member resource adapters imported from the same rar file in the memberResourceAdapterName[n] property.

KDJE49608-E

A transaction support level of at least one member resource adapter is not supported by the root resource adapter. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description: A transaction support level of the member resource adapter specified in the memberResourceAdapterName[n] property is not supported by the root resource adapter.
Action: Confirm that the transaction support level of the member resource adapter specified in the memberResourceAdapterName[n] property is supported by the root resource adapter.

KDJE49609-E

Transaction support levels of all member resource adapters are not the same. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description: The transaction support levels of the member resource adapter specified in memberResourceAdapterName[n] property are different. All the transaction support levels of the member resource adapter need to be same.
Action: Confirm that all the transaction support levels of member resource adapter specified in memberResourceAdapterName[n] property are same.

KDJE49610-E

User names of all member resource adapters are not the same. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description: The database user names of member resource adapter specified in memberResourceAdapterName[n] property are different. All the database user names of member resource adapter need to be same.
Action: Confirm that all the database user names of member resource adapter specified in memberResourceAdapterName[n] property are same.

KDJE49611-E

The dbCheckInterval property value is not longer than the loginTimeout property value of a member resource adapter. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description: The dbCheckInterval property value is no longer than the loginTimeout property value of a member resource adapter specified in memberResourceAdapterName[n] property. The dbCheckInterval property value needs to be longer than the loginTimeout property value of all the member resource adapters.
Action: Confirm that the dbCheckInterval property value is longer than the loginTimeout property value of all the member resource adapters specified in the memberResourceAdapterName[n] property.

KDJE49612-W

The algorithm property is not defined. The default value will be used. (root resource adapter = aa....aa, default value = bb....bb)

aa....aa: Root resource adapter

bb....bb: Default algorithm property value

Description: The algorithm property is not defined. The default value will be used.
Action: Define the algorithm property.

KDJE49613-W

An invalid value is set in the algorithm property. The default value will be used. (root resource adapter = aa....aa, default value = bb....bb)

aa....aa: Root resource adapter

bb....bb: Default algorithm property value

Description: An invalid value is set in the algorithm property. The default value will be used.
Action: Set a valid value in the algorithm property.

KDJE49614-W

The enableAutoPoolSuspend property is not defined. The default value will be used. (root resource adapter = aa....aa, default value = bb....bb)

aa....aa: Root resource adapter

bb....bb: Default enableAutoPoolSuspend property value

Description: The enableAutoPoolSuspend property is not defined. The default value will be used.
Action: Define the enableAutoPoolSuspend property.

KDJE49615-W

The enableAutoPoolResume property is not defined. The default value will be used. (root resource adapter = aa....aa, default value = bb....bb)

aa....aa: Root resource adapter

bb....bb: Default enableAutoPoolResume property value

Description: The enableAutoPoolResume property is not defined. The default value will be used.
Action: Define the enableAutoPoolResume property.

KDJE49616-W

The dbCheckInterval property is not defined. The default value will be used. (root resource adapter = aa....aa, default value = bb....bb)

aa....aa: Root resource adapter

bb....bb: Default dbCheckInterval property value

Description: The dbCheckInterval property is not defined. The default value will be used.
Action: Define the dbCheckInterval property.

KDJE49617-W

An invalid value is set in the dbCheckInterval property. The default value will be used. (root resource adapter = aa....aa, default value = bb....bb)

aa....aa: Root resource adapter

bb....bb: Default dbCheckInterval property value

Description: An invalid value is set in the dbCheckInterval property. The default value will be used.
Action: Set a valid value in the dbCheckInterval property.

KDJE49620-E

The algorithm property is not defined. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description: The algorithm property is not defined.
Action: Define the algorithm property.

KDJE49621-E

An invalid value is set in the algorithm property. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description: An invalid value is set in the algorithm property.
Action: Set a valid value in the algorithm property.

KDJE49622-E

The enableAutoPoolSuspend property is not defined. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description: The enableAutoPoolSuspend property is not defined.
Action: Define the enableAutoPoolSuspend property.

KDJE49623-E

The enableAutoPoolResume property is not defined. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description: The enableAutoPoolResume property is not defined.
Action: Define the enableAutoPoolResume property.

KDJE49624-E

The dbCheckInterval property is not defined. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description: The dbCheckInterval property is not defined.
Action: Define the dbCheckInterval property.

KDJE49625-E

An invalid value is set in the dbCheckInterval property. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description: An invalid value is set in the dbCheckInterval property.
Action: Set a valid value in the dbCheckInterval property.

KDJE49630-E

Connection pooling is disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description: Connection pooling functionality is disabled. This functionality is a prerequisite for member resource adapter.
Action: Set the maximum size of the connections in the connection pool to one or more.

KDJE49631-E

The maximum size of the connection pool is set to be unlimited. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description: The maximum size of the connections in the connection pool is set to unlimited. The maximum size of the connections for the member resource adapter cannot be unlimited.
Action: Set the maximum size of the connections in the connection pool to one or more.

KDJE49632-E

The function for detecting errors while getting a connection is disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description: The function for detecting the connection errors while getting a connection is disabled. This functionality is a prerequisite for member resource adapter.
Action: Enable the function for detecting the connection errors while getting a connection.

KDJE49633-E

The timeout function for detecting connection errors is disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description: The timeout function for detecting the connection errors is disabled. This functionality is a prerequisite for member resource adapter.
Action: Enable the timeout function for detecting the connection errors.

KDJE49634-E

The function to queue requests for getting a connection is disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description: The function to queue requests for getting a connection is disabled when the connections are depleted. This functionality is a prerequisite for member resource adapter.
Action: Enable the function to queue requests for getting a connection when the connections are depleted.

KDJE49635-E

The retry function for getting a connection is not disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description: The retry function for getting a connection is not disabled. This function cannot be used in the member resource adapter.
Action: Disable the retry function for getting a connection.

KDJE49636-E

The optional name function for J2EE resources is not disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description: The optional name function for the J2EE resources is not disabled. This function cannot be used in the member resource adapter.
Action: Disable the optional name function for the J2EE resources.

KDJE49637-E

The value of the loginTimeout property is not 1 or more. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description: Specify the value of the loginTimeout property to one or more. This setting is required when using Oracle JDBC Thin Driver in the member resource adapter.
Action: Specify the value of the loginTimeout property of the member resource adapter to one or more.

KDJE49640-W

Connection pooling has been enabled. (member resource adapter = aa....aa, default minimum pool size = bb....bb, default maximum pool size = cc....cc)

aa....aa: Member resource adapter name

bb....bb: Default minimum size of the number of connections of the connection pool

cc....cc: Default maximum size of the number of connections of the connection pool

Description: Connection pooling function is enabled. This functionality is a prerequisite for member resource adapter. The default value will be used for the connection pool size.
Action: Set the maximum size of the connections in the connection pool to one or more.

KDJE49641-W

The default value will be used for the connection pool size. (member resource adapter = aa....aa, default minimum pool size = bb....bb, default maximum pool size = cc....cc)

aa....aa: Member resource adapter name

bb....bb: Default minimum size of the number of connections of the connection pool

cc....cc: Default maximum size of the number of connections of the connection pool

Description: The default value will be used for the connection pool size since the maximum size of the connections in the connection pool is set to unlimited. The maximum size of the connections for the member resource adapter cannot be unlimited.
Action: Set the maximum size of the connections in the connection pool to one or more.

KDJE49642-W

The function for detecting errors while getting a connection has been enabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description: The function for detecting the connection errors while getting a connection is enabled. This functionality is a prerequisite for member resource adapter.
Action: Enable the function for detecting the connection errors while getting a connection.

KDJE49643-W

The timeout function for detecting connection errors has been enabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description: The timeout function for detecting the connection errors is enabled. This functionality is a prerequisite for member resource adapter.
Action: Enable the timeout function for detecting the connection errors.

KDJE49644-W

The function to queue requests for getting a connection has been enabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description: The function to queue requests for getting a connection is enabled when the connections are depleted. This functionality is a prerequisite for member resource adapter.
Action: Enable the function to queue requests for getting a connection when the connections are depleted.

KDJE49645-W

The retry function for getting a connection has been disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description: The retry function for getting a connection is disabled. This function cannot be used in the member resource adapter.
Action: Disable the retry function for getting a connection.

KDJE49646-W

The optional name function for J2EE resources has been disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description: The optional name function for the J2EE resources is disabled. This function cannot be used in the member resource adapter.
Action: Disable the optional name function for the J2EE resources.

KDJE49647-E

The root resource adapter is not stopped. (root resource adapter = aa....aa, member resource adapter = bb....bb)

aa....aa: Root resource adapter

bb....bb: Member resource adapter name

Description: The root resource adapter is running. The root resource adapter must be stopped to stop the member resource adapter.
Action: Confirm that the root resource adapter is not running.

KDJE49650-I

The connection pool status has changed to "running". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The member connection pool status was changed to "running".

KDJE49651-I

The member resource adapter has started, and the connection pool status has changed to "running". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The member resource adapter was running, and the member connection pool status was changed to running.

KDJE49652-I

The connection pool status has changed to "runningReserved". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The member connection pool status was changed to runningReserved.

KDJE49653-I

The connection pool status has changed to "resumingAutomatically". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The connection pool status was changed to resumingAutomatically.

KDJE49654-I

The connection pool status has changed to "resumingManually". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The member connection pool status was changed to resumingManually.

KDJE49655-E

The connection pool status has changed to "blockedAutomatically". (resource name = aa....aa, previous pool status = bb....bb, cause = cc....cc)

aa....aa: Resource display name

bb....bb: Connection pool status before update

cc....cc: Reason for lock

Description: The member connection pool status was changed to blockedAutomatically.
Action: An error occurred in the database server. Restore the database server.

KDJE49656-I

The connection pool status has changed to "blockedManually". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The member connection pool status was changed to blockedManually.

KDJE49657-E

The connection pool status has changed to "suspendedAutomatically". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The member connection pool status was changed to suspendedAutomatically.
Action: Restore the database server and change the status of the connection pool to "running" by automatically resuming or by using the cjresumepool command.

KDJE49658-I

The member resource adapter started, and the connection pool status has changed to "suspendedAutomatically". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The member resource adapter was running, and the member connection pool status was changed to suspendedAutomatically.

KDJE49659-I

The connection pool status has changed to "suspendedAutomaticallyReserved". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The member connection pool status was changed to suspendedAutomaticallyReserved.

KDJE49660-I

The connection pool status has changed to "suspendedManually". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The member connection pool status was changed to suspendedManually.

KDJE49661-I

The member resource adapter started, and the connection pool status has changed to "suspendedManually". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The member resource adapter was running, and the member connection pool status was changed to suspendedManually.

KDJE49662-I

The connection pool status has changed to "suspendedManuallyReserved". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The member connection pool status was changed to suspendedManuallyReserved.

KDJE49663-E

The connection pool status has changed to "suspendedAutomatically" because the member connection pool failed to resume. (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The member connection pool status was changed to suspendedAutomatically.
Action: Restore the database server and change the status of the connection pool to "running" by automatically resuming or by using the cjresumepool command.

KDJE49664-E

The connection pool status has changed to "suspendedManually" because the member connection pool failed to resume. (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: The member connection pool status was changed to suspendedManually.
Action: Use the cjresumepool command to restore the database server and change the status of the connection pool to "running".

KDJE49665-I

The member connection pool will be created now. (resource name = aa....aa, pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status

Description: The member connection pool will be created now because the member resource adapter was running.

KDJE49666-I

The member connection pool was registered in the cluster connection pool. (member resource name = aa....aa, root resource name = bb....bb)

aa....aa: Display name of member resource adapter

bb....bb: Display name of root resource adapter

Description: The member connection pool was registered in the cluster connection pool.

KDJE49667-E

An exception occurred while getting the connection pool status. (resource name = aa....aa)

aa....aa: Member resource adapter name

Description: An attempt to acquire the member connection pool status has failed. The processing will be interrupted.
Action: Undeploy the member resource adapter, and then restart the adapter after it is deployed. If action cannot be taken, acquire the maintenance information, and then contact the maintenance personnel.

KDJE49668-E

The connection pool status is invalid. (resource name = aa....aa)

aa....aa: Member resource adapter name

Description: The member connection pool status is invalid. The processing will be interrupted.
Action: Remove the cause of the invalid status of the member connection pool by referencing the messages output before this message. After removing the cause, restart the J2EE server. After restarting the J2EE server, check if the executed operation was successful.

KDJE49669-E

An exception occurred during updating of the member connection pool status. (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description: An attempt to update the member connection pool status has failed.
Action: Remove the cause of failure in updating the status of the member connection pool by referencing the messages output before this message. After removing the cause, restart the J2EE server. After restarting the J2EE server, check if the executed operation is successful.

KDJE49670-E

The connection pool cannot resume because the number of available connection control threads is fewer than the maximum size of the connection pool. (resource name = aa....aa)

aa....aa: Resource display name

Description: The connection pool cannot resume.
Action: Wait until the connection control threads are released.

KDJE49671-I

The number of available connection control threads has reached the maximum size of the connection pool. (resource name = aa....aa)

aa....aa: Resource display name

Description: The post-processing after the member resource adapters in the cluster connection pool paused automatically is complete, and the auto-resume processing can now be executed.

KDJE49672-E

The cjclearpool command cannot execute because the specified resource name is a root resource adapter name. (resource name = aa....aa)

aa....aa: Resource display name

Description: The display name of root resource adapter cannot be specified for the cjclearpool command.
Action: Specify the display name of the resource adapter other than the root resource adapter, and then re-execute the command.

KDJE49673-E

The cjclearpool command cannot execute because the status of the connection pool of the specified resource is not "running". (resource name = aa....aa, pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status

Description

The resource name whose connection pool status is not running cannot be specified for the cjclearpool command.

Action

Change the status of the connection pool to running, and then re-execute the command.

When the connection pool is blocked automatically or manually:

Wait for a while as the connection pool will be suspended. Execute the cjresumepool command when the status of the connection pool is suspended.
When the status of the connection pool is suspendedAutomatically or suspendedManually:

Execute the cjresumepool command.
When the connection pool is resumingAutomatically or resumingManually:

Wait for a while until the status of connection pool is running.

KDJE49674-E

The cjlistpool command cannot execute because the specified resource name is a root resource adapter name. (resource name = aa....aa)

aa....aa: Resource display name

Description: The display name of the root resource adapter cannot be specified for the cjlistpool command.
Action: Specify the display name of the resource adapter other than the root resource adapter, and then re-execute the command.

KDJE49675-E

The cjsuspendpool command cannot execute because the specified resource name is not a member resource adapter name. (resource name = aa....aa)

aa....aa: Resource display name

Description: Only the display name of the member resource adapter can be specified for the cjsuspendpool command.
Action: Specify the display name of member resource adapter, and then re-execute the command.

KDJE49676-E

The cjsuspendpool command cannot execute because the status of the specified connection pool is illegal. An available status is "running", "runningReserved", "suspendedAutomatically" or "suspendedAutomaticallyReserved". (resource name = aa....aa, pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status

Description

The resource name whose connection pool status is not running, runningReserved, suspendedAutomatically, or suspendedManually cannot be specified for the cjsuspendpool command.

Action

When the connection pool is blocked automatically or manually:

The connection pool is now being suspended. Please wait.
When the connection pool is manually suspended or reserved for manual suspension:

You need not take any action because the connection pool has already been suspended.
When the connection pool is resuming automatically, or is being resumed manually:

Wait until the connection pool is started, and then re-execute the command.

KDJE49677-E

The cjresumepool command cannot execute because the specified resource name is not a member resource adapter name. (resource name = aa....aa)

aa....aa: Resource display name

Description: Only the display name of the member resource adapter can be specified for the cjresumepool command.
Action: Specify the display name of member resource adapter, and then re-execute the command.

KDJE49678-E

The cjresumepool command cannot execute because the specified connection pool is not suspended. (resource name = aa....aa, pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status

Description

The resource name whose connection pool status is not suspendedAutomatically, suspendedManually, suspendedAutomaticallyReserved or suspendedManuallyReserved cannot be specified for the cjresumepool command.

Action

When the connection pool has started or is reserved for starting:

You need not take any action because the connection pool has already started.
When the connection pool is blocked automatically or manually:

Wait until the status of the connection pool is suspendedAutomatically or suspendedManually, and then re-execute the command.
When the connection pool is resuming automatically, or is being resumed manually:

The connection pool is now resuming. Please wait.

KDJE49679-E

The command cannot be used in basic mode. (command name = aa....aa)

aa....aa: Command name

Description: This command cannot be used in the basic mode.
Action: Make sure that the startup mode of the J2EE server is set to 1.4 mode.

KDJE49680-I

The connection pool status has been modified. (resource name = aa....aa, previous status = bb....bb, modified status = cc....cc)

aa....aa: Resource display name

bb....bb: Connection pool status before modification

cc....cc: Connection pool status after modification

Description: The status of the connection pool was modified to suspendedAutomatically or suspendedManually because the J2EE Server was forcibly stopped while the connection pool was being resumed or suspended.

KDJE49681-E

The cjresumepool command failed because the connection pool warm up failed. (resource name = aa....aa)

aa....aa: Resource display name

Description: An attempt to manually resume the connection pool has failed.
Action: Restore the database server, and then execute the cjresumepool command.

KDJE49682-W

The value of aa....aa property is invalid. The default value will be used. (default = bb....bb)

aa....aa: Property key

bb....bb: Default value

Description: The default value bb....bb will be applied because the value of the key (aa....aa) is invalid.
Action: Specify a value within the valid range in the key (aa....aa)