7.5 Messages from KDJE55000 to KDJE59999 : Messages

KDJE55000-I

Batch application aa....aa will now start.

aa....aa: Batch application class name

Description: The startup processing of the batch application has started.

KDJE55001-I

The main method will now start.

Description: The execution of the main method of the batch application has started.

KDJE55002-I

Batch application aa....aa will now end. (exit code = bb....bb)

aa....aa: Batch application class name

bb....bb: Exit code

Description: The termination processing of the batch application has started.

KDJE55003-I

Batch application aa....aa ended successfully. (exit code = bb....bb)

aa....aa: Batch application class name

bb....bb: Exit code

Description: The termination processing of the batch application is complete.

KDJE55004-I

Batch application will now be forcibly terminated.

Description: The forced termination processing of the batch application has started.

KDJE55005-I

Batch application aa....aa was forcibly terminated.

aa....aa: Batch application class name

Description: The forced termination processing of the batch application is complete.

KDJE55006-E

The main method was not found.

Description: The public static void main(String[]) method or the public static int main(String[]) method does not exist in the batch application.
Action: Execute a class in which a method containing the signature of public static void main(String[]) or public static int main(String[]) is defined.

KDJE55007-E

The batch application cannot be started. (details = aa....aa)

aa....aa: Details

Description

A problem occurred when starting up the batch application.

Action

See the detailed message, and then take action.

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

KDJE55008-E

An unexpected exception occurred. (details = aa....aa)

aa....aa: Details

Description: An unexpected exception occurred.
Action: See the detailed message, and then take action. If the cause is unknown, acquire the maintenance information, and then contact the maintenance personnel.

KDJE55009-E

An exception occurred in the main method. (exception = aa....aa)

aa....aa: Exception

Description

An exception is thrown from the main method during the execution of the batch application.

Action

Reference the exception, and then take action.

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

KDJE55010-E

Batch server aa....aa was not found.

aa....aa: Batch server name

Description

The batch server was not found.

Action

If the batch server name is incorrect, specify a correct name.

If the batch server is not running, start the batch server.

KDJE55011-I

The batch service will now start.

Description: The batch service starts.

KDJE55012-E

The batch service is not running.

Description: The batch service is not running.
Action: When a command is executed for the batch server, make sure that the batch service is running, and then re-execute the command. Furthermore, even if the cjexecjob command or the cjkilljob command is executed for a J2EE server, the command will be disabled. Execute the cjexecjob command or the cjkilljob command for the batch server.

KDJE55013-I

The batch application ClassLoader was initialized. (class name = aa....aa, time of operation = bb....bb)

aa....aa: Batch application class name

bb....bb: Time

Description: The class loader has been initialized.

KDJE55014-I

The batch application ClassLoader was removed. (class name = aa....aa, time of operation = bb....bb)

aa....aa: Batch application class name

bb....bb: Time

Description: The class loader has been discarded. The timing of displaying this message depends on the garbage collector. If this message is not output even when the batch application is executed repeatedly, a memory leakage might occur.

KDJE55015-E

Another batch application is already running.

Description: The batch application is running.
Action: Re-execute the command after the execution of the batch application is complete.

KDJE55016-W

The batch application is not running.

Description

The batch application is not running.

Action

Check the specified server name and job ID.

The correct server name and job ID indicate that the batch application has been terminated, and therefore, no action is required.

If the server name and job ID are incorrect, specify the correct server name and job ID in the forced termination command.

KDJE55017-E

Forcible termination of the batch application aa....aa has failed.

aa....aa: Batch application class name

Description: An attempt to perform the forced termination of the batch application has failed.
Action: Stop the batch server, and then restart.

KDJE55018-I

The cjexecjob command will now start. (aa....aa = bb....bb, directory string the user-definition file = cc....cc, process ID = dd....dd)

aa....aa: "server name" or "schedule group"

bb....bb: Batch server name or schedule group name

cc....cc: Storage destination directory of the user-defined files

dd....dd: Process ID

Description: The cjexecjob command will now start using the user definition of cc....cc directory.

KDJE55019-I

The cjexecjob command was stopped. (process ID = aa....aa, exit status = bb....bb)

aa....aa: Process ID

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

Description: The cjexecjob command was stopped.

KDJE55020-I

The batch server will now be forcibly stopped. (server name = aa....aa)

aa....aa: Batch server name

Description: The batch server will be terminated forcibly.

KDJE55021-E

The batch server stopped abnormally. (server name = aa....aa)

aa....aa: Batch server name

Description: The batch server is terminated abnormally during the processing of the command.
Action: Check the status of the batch server, and then re-execute the command. If the batch server name is not output, make sure that the batch server of the specified schedule group is not terminated abnormally, and then re-execute the command.

KDJE55024-I

The GC controller is waiting until resource access ends.

Description: The GC control functionality is placed in the GC execution standby status.

KDJE55025-I

The GC controller will now start GC. (rate 1 = aa....aa, rate 2 = bb....bb, rate 3 = cc....cc, free (new) = dd....dd, total (new) = ee....ee, max (new) = ff....ff, free (old) = gg....gg, total (old) = hh....hh, max (old) = ii....ii, free (permanent) = jj....jj, total (permanent) = kk....kk, max (permanent) = ll....ll, threshold value = mm....mm)

aa....aa:

When serial GC is valid:

Memory occupied (in %) by Old area

Ratio of the Old area consumption size and Old area total size

When G1 GC is valid:

Usage (in %) in the Java heap area

Ratio of the consumption size of the Java heap area with respect to the total size of the Java heap area

bb....bb:

When serial GC is valid:

The percentage (%) of total memory occupied by the New area with respect to the maximum free memory of the Old area

Ratio of the New area total size and Old area maximum free size

When G1 GC is valid: -1

cc....cc: Memory occupied (in %) by the Metaspace area

Ratio of the Metaspace area consumption size and Metaspace area total size

dd....dd: Free memory size (in bytes) of New area

ee....ee: Total memory size (in bytes) of New area

ff....ff:

When serial GC is valid:

Maximum memory size (in bytes) of New area

When G1 GC is valid: -1

gg....gg: Free memory size (in bytes) of Old area

hh....hh: Total memory size (in bytes) of Old area

ii....ii:

When serial GC is valid:

Maximum memory size (in bytes) of Old area

When G1 GC is valid:

Maximum memory size (in bytes) of the Java heap area

jj....jj: Free memory size (in bytes) of Metaspace area

kk....kk: Total memory size (in bytes) of Metaspace area

ll....ll: Maximum memory size (in bytes) of Metaspace area

mm....mm: Threshold value

Description: The GC control functionality performs a GC.

KDJE55026-E

The specified command parameter is too long.

Description: The specification of the command argument is too long.
Action: Use the usrconf.cfg or usrconf.properties file of the batch execution command to reduce the length of the argument, and then re-execute the command.

KDJE55027-I

The cjkilljob command will now start. (aa....aa = bb....bb)

aa....aa: "server name" or "schedule group"

bb....bb: Batch server name or schedule group name

Description: The cjkilljob command has started.

KDJE55028-I

The cjkilljob command was stopped. (aa....aa = bb....bb)

aa....aa: "server name" or "schedule group"

bb....bb: Batch server name or schedule group name

Description: The cjkilljob command was stopped.

KDJE55029-I

Usage:

Format1:cjexecjob serverName [Java options ...] class-name [args ...]

Format2:cjexecjob [scheduleGroup] [-jobID job ID] [Java options ...] class-name [args ...]

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

KDJE55030-I

Usage:

Format1:cjkilljob serverName

Format2:cjkilljob [scheduleGroup] -jobID jobID

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

KDJE55031-E

The resource adapter cannot be started or stopped while the batch application is running.

Description: The resource adapter cannot be started or stopped while the batch application is running.
Action: After the execution of the batch application is complete, start or stop the resource adapter again.

KDJE55032-E

The specified command cannot be used with the batch server. (server name = aa....aa, command = bb....bb)

aa....aa: Batch server name

bb....bb: Command name

Description: A command that cannot be used for the batch server is executed.
Action: If the server name is incorrect, specify the correct name.

KDJE55033-I

The batch server will suspend termination processing until the batch application has finished.

Description: The batch application is running. Wait for the batch application to terminate, and then stop the batch server.

KDJE55034-I

The batch service ended.

Description: The batch service ended.

KDJE55035-E

The batch server failed to read the user properties file for batch applications. (file = aa....aa)

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

Description: An attempt to read the user property file for batch applications has failed. Either the file path is invalid or the read permission is not available.
Action: Specify the correct path for the user property file for batch applications.

KDJE55036-E

The communication data is invalid. (name = aa....aa, details = bb....bb, errno = cc....cc)

aa....aa: Name

bb....bb: Detailed message

cc....cc: Error code

Description

The communication data is invalid.

Action

Re-execute the command.

If the error occurs again, collect the maintenance information, and contact maintenance personnel.

KDJE55037-E

A protocol error occurred. (name = aa....aa, details = bb....bb, errno = cc....cc)

aa....aa: Name

bb....bb: Detailed message

cc....cc: Error code

Description

A protocol error occurred.

Action

Re-execute the command.

If the error occurs again, collect the maintenance information, and contact maintenance personnel.

KDJE55038-E

The server name specified for the command parameter is too long. (maximum length = aa....aa)

aa....aa: Maximum length

Description: The server name specified in the command argument is too long.
Action: Specify the server name with number of characters lesser than the displayed maximum length.

KDJE55039-W

The length of the directory name specified for aa....aa exceeds bb....bb bytes. The default value cc....cc will be used.

aa....aa: Option name

bb....bb: Directory length

cc....cc: default directory name

Description: The length of the directory name specified for aa....aa exceeds bb....bb bytes. The default value (cc....cc) will be used.
Action: Revise the value of aa....aa.

KDJE55040-E

An attempt to perform a forced stop of the batch server has failed. (server name = aa....aa)

aa....aa: Batch server name

Description: An attempt to perform the forced termination of the batch server aa....aa has failed.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE55042-E

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

aa....aa: Details

bb....bb: Error code

cc....cc: Path name

Description

An attempt to initialize the log has failed.

Action

Take action based on the following causes:

The log output directory cannot be created

Check the value of the log output directory.

The log is initialized simultaneously by multiple commands

Increase the following defined values, and then re-execute the command:

batch.log.lockRetryCount
batch.log.lockInterval

KDJE55043-E

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

aa....aa: Details

bb....bb: Error code

Description

An attempt to output the log has failed.

Action

Take action based on the following causes:

Insufficient free disk space: Delete the unnecessary files to increase the available space at the output destination or change to an output destination with available space.
Failure in the disk device: If the disk device is broken, contact the system administrator and replace the device.
No access permission: Check the access permission of the output directory.

When these factors are not applicable, collect the maintenance information, and then contact maintenance personnel.

KDJE55044-E

The server cannot be accessed. (server name = aa....aa, reason = bb....bb, details = cc....cc, errno = dd....dd)

aa....aa: Server name

bb....bb: Error contents

cc....cc: Details

dd....dd: Error code

Description

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

Action

Take action based on the error details.

Permission denied

In Windows, enable the administrator permission.

In UNIX, re-execute the command as Cosminexus Component Container administrator.

If the problem is not resolved by the above or for error contents other than the above, collect the maintenance information, and contact maintenance personnel.

KDJE55045-E

The path of the current directory is too long. (maximum length = aa....aa, details = bb....bb, errno = cc....cc)

aa....aa: Maximum length

bb....bb: Detailed message

cc....cc: Error code

Description: The path of the current directory is too long.
Action: Change the length of the absolute path of the current directory in which the command is executed in such a way so that the length is lesser than the maximum path length set by the OS.

KDJE55046-E

The smart agent was not started or the schedule group aa....aa was not found.

aa....aa: Schedule group name

Description

Either the Smart Agent is not running or the schedule group is not found.

Action

Make sure that all of the following processes are running:

Smart Agent
CTM regulator
CTM daemon
Batch server having the specified schedule group name

KDJE55047-E

The schedule group aa....aa was not found.

aa....aa: Schedule group name

Description

The schedule group was not found.

Action

Take action based on the following causes, and then restart the process:

The CTM regulator terminated abnormally.
The CTM daemon has been aborted.
The batch server having the specified schedule group name terminated abnormally.

KDJE55048-W

The job ID aa....aa was not found.

aa....aa: Job ID

Description

The job ID was not found.

Action

Check the specified job ID.

the CORRECT job ID indicates that the batch application has been terminated, and therefore, no action is required.

If the job ID is incorrect, specify the correct job ID in the forced termination command.

KDJE55049-I

The cjlistjob command will now start. (aa....aa = bb....bb)

aa....aa: "server name" or "job ID"

bb....bb: Server name or schedule group name

Description: The cjlistjob command has started.

KDJE55050-I

All batch applications have been listed successfully. (number = aa....aa)

aa....aa: Number of batch applications

Description: The list of all batch applications have been output successfully.

KDJE55051-I

The cjlistjob command was finished. (aa....aa = bb....bb)

aa....aa: "server name" or "schedule group"

bb....bb: Server name, schedule group name, or "-all"

Description: The cjlistjob command has finished.

KDJE55052-I

Usage:

Format1:cjlistjob serverName

Format2:cjlistjob [scheduleGroup[,scheduleGroup...]]|[-all]

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

KDJE55053-E

The job ID value is invalid. (value = aa....aa)

aa....aa: Job ID

Description: The value of the job ID is incorrect.
Action: Revise the value of job ID.

KDJE55054-E

The job ID aa....aa already exists. (job ID = aa....aa)

aa....aa: Job ID

Description: The job ID aa....aa already exists.
Action: Specify another value in the job ID, and then re-execute the command.

KDJE55055-E

The command aa....aa timed out.

aa....aa: Command

Description: A timeout occurred in the command aa....aa.
Action: Make sure that the timeout value is correct, and then re-execute the command.

KDJE55056-I

The cjkilljob command has reserved the batch application for deletion. (job ID = aa....aa)

aa....aa: Job ID

Description: The batch application is reserved for deletion by the cjkilljob command.

KDJE55057-W

The batch application is already reserved for deletion. (job ID = aa....aa)

aa....aa: Job ID

Description

The batch application is already reserved for deletion.

Action

Check the specified job ID.

The correct job ID indicates that the batch application is already reserved for deletion, and therefore, no action is required.

If the job ID is incorrect, specify the correct job ID in the forced termination command.

KDJE55058-E

An exception occurred in the CTM. (CTM API MSG = aa....aa)

aa....aa: Details

Description

An exception occurred in CTM.

Action

When detailed-information is output, reference the list of content codes of CTM, and then take action.

When detailed-information is output, reference the message log of CTM, and then take action.

KDJE55059-I

The batch application aa....aa will now be registered in the schedule queue bb....bb. (job ID = cc....cc)

aa....aa: Batch application name

bb....bb: Schedule queue name

cc....cc: Job ID

Description: The batch application aa....aa will be registered in the schedule queue bb....bb.

KDJE55060-E

This processing exceeded the maximum request registration. (queue = aa....aa)

aa....aa: Queue name

Description: The maximum number of registrations for the queue is exceeded.
Action: Re-execute the command after the queue application has executed.

KDJE55061-E

The CTM timed out.

Description: A timeout occurred in the CTM.
Action: Make sure that the timeout period is correct, and then re-execute the command.

KDJE55062-E

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

aa....aa: "server name" or "job ID"

bb....bb: Server name or schedule group name

Description: The value specified in the command option is invalid.
Action: Check the availability of the scheduling functionality for usage, and then input the command in the correct format.

KDJE55063-E

Exception occurred in getting CTMQueueManager to start batch server:aa....aa. (CTM API MSG = bb....bb)

aa....aa: Batch server name

bb....bb: Exceptional detailed-information

Description: An exception occurred when acquiring CTMQueueManager during the startup of the batch server.
Action: After taking action based on detailed-information, start the batch server.

KDJE55064-E

Unexpected exception occurred while starting batch server:aa....aa. (details = bb....bb)

aa....aa: Batch server name

bb....bb: Exceptional detailed-information

Description: An unexpected exception occurred while starting the batch server aa....aa.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE55065-E

Unexpected exception occurred while stopping batch server:aa....aa. (details = bb....bb)

aa....aa: Batch server name

bb....bb: Exceptional detailed-information

Description: An unexpected exception occurred while stopping the batch server aa....aa.
Action: Acquire the maintenance information, and then contact the maintenance personnel.

KDJE55066-I

The batch application aa....aa will now start. (server name = bb....bb, job ID = cc....cc)

aa....aa: Batch application class name

bb....bb: Batch server name

cc....cc: Job ID

Description: The execution of the batch application aa....aa will start.

KDJE55067-E

The batch application to which the scheduling function is disabled cannot be accepted.

Description

The scheduling functionality is not enabled in the cjexecjob command.

Action

If settings are specified for using the scheduling functionality in the batch server, specify the following settings in the usrconf.cfg file of the cjexecjob command:

batch.ctm.enabled=true

KDJE55068-W

The cjexecjob command was not stopped successfully. (process ID = aa....aa, exit status = bb....bb)

aa....aa: Process ID

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

Description

The cjexecjob command did not terminate normally.

Action

Make sure that no other messages are output in the message log of the batch execution command.

If other messages are output, check the output message and then take action. If no other messages are output, check the error message output in the message log of the batch server, and then take action.

KDJE55069-I

The system sets the ejbserver.batch.application.exit.enabled property to false. The method that terminates this Java VM also stops the batch server. Java VM (vendor = aa....aa, version = bb....bb)

aa....aa: Vendor of used Java VM

bb....bb: Version of used Java VM

Description: Specify false in the ejbserver.batch.application.exit.enabled property. The method that terminates the batch server stops Java VM.

KDJE55500-E

An exception occurred during initialization to output log data. (detail = aa....aa)

aa....aa: Exception information

Description: An exception occurred during the initialization processing of log output.
Action: Check the exception information, and take action. If you cannot resolve the error, contact the maintenance personnel.

KDJE55501-E

An attempt to output a message has failed. (id = aa....aa, detail = bb....bb)

aa....aa: Message ID

bb....bb: Exception information

Description: An attempt to output a message has failed.
Action: Acquire the exception information, and then contact the maintenance personnel.

KDJE55502-E

An exception occurred during entity loading. This class could not be loaded. (class = aa....aa, detail = bb....bb)

aa....aa: Class name that failed to load

bb....bb: Exception information

Description: An exception occurred during the entity is loading. This class could not be loaded.
Action: Acquire the exception information, and then contact the maintenance personnel.

KDJE55503-E

An internal exception occurred during JPQL analysis. (detail = aa....aa)

aa....aa: Exception information

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

KDJE55504-W

A Java field could not be converted to the column type of the database. The java.lang.String type will be applied to this field. (column = aa....aa, java type = bb....bb)

aa....aa: Database column name

bb....bb: Java type that failed to be mapped

Description: An attempt to convert a Java field into a database column type has failed. The java.lang.String type will be applied to this field.
Action: Make sure that the settings of the Java field types and database column types are correct.

KDJE55505-E

An invalid property value is specified. (property = aa....aa, value = bb....bb)

aa....aa: Property name

bb....bb: Value specified in property

Description: The property value is invalid.
Action: Check the property value set up in persistence.xml, and then specify the correct value.

KDJE55506-W

The table was not created because it already exists in the database. (table = aa....aa)

aa....aa: Table name

Description: Table is not created because the table already exists in the database.
Action: Check if a table with the same name exists in the database.

KDJE55507-W

The value specified for jta-data-source will be ignored because the transaction type is RESOURCE_LOCAL. (persistence unit = aa....aa)

aa....aa: Persistence unit name

Description: The transaction type is RESOURCE_LOCAL. The value specified in the <jta-data-source> tag of persistence.xml will be ignored.
Action: Check the transaction attribute of the <persistence-unit> tag of persistence.xml, and the specification contents of the <jta-data-source> tag.

KDJE55508-E

An exception occurred during processing to register a Synchronization object to the JTA. (status = aa....aa, detail = bb....bb)

aa....aa: Transaction status

bb....bb: Exception information

Description: An exception occurred during the processing for registering a Synchronization object in JTA.
Action: Acquire the exception information, and then contact the maintenance personnel.

KDJE55509-W

The hint specified for the query will be ignored because the hint is invalid. (query = aa....aa, hint = bb....bb)

aa....aa: Query name

bb....bb: Query hint name

Description: The hint specified for a query will be ignored because the hint is invalid.
Action: Confirm that the query hint is correctly set up.

KDJE55510-E

An exception occurred during the loading of an O/R mapping file. (file = aa....aa, detail = bb....bb)

aa....aa: File name used for O/R mapping

bb....bb: Exception information

Description

An exception occurred while loading the O/R mapping file.

Action

Check the file specified in the <mapping-file> tag of persistence.xml.

The causes of occurrence of this error might be that the file does not exist or the access permission to the file is not available.

KDJE55511-W

An attempt to load an entity class during persistence unit initialization has failed. (class = aa....aa, detail = bb....bb)

aa....aa: Class name specified in the entity

bb....bb: Exception information

Description

An attempt to load the entity class during the initialization of the persistent unit has failed.

Action

Make sure that the correct class name is specified in the class attribute of the <entity> tag of O/R mapping file.

If you cannot resolve the error acquire the maintenance information, and then contact the maintenance personnel.

KDJE55512-W

An optimistic lock was specified for an entity multiple times. The version specified for an element will be ignored. (entity = aa....aa, element = bb....bb)

aa....aa: Entity class

bb....bb: Field or property for which the version is to be specified

Description: An optimistic lock is specified more than once for an entity. The specification of the <version> tag will be ignored.
Action: Check the settings for the optimistic lock.

KDJE55513-W

The same mapping was specified for an entity element multiple times. This mapping specification will be ignored. (entity = aa....aa, element = bb....bb)

aa....aa: Entity class

bb....bb: Field or property for which the mapping is to be specified

Description: The same mapping is specified more than once for an entity element. The specification of the mapping will be ignored.
Action: Check the settings of the entity fields or properties of the O/R mapping file.

KDJE55514-W

The LAZY fetch element for an entity will be ignored. Basic mappings use EAGER fetching by default. (entity = aa....aa, element = bb....bb)

aa....aa: Entity class

bb....bb: Field or property for which the Lazy fetch type is to be specified

Description

The LAZY fetch element specified for an entity will be ignored. The EAGER fetching is used by default in the Basic mappings.

Action

Check the settings of the Basic fetch attribute.

LazyLoading for @Basic is not supported in the Cosminexus JPA provider. The default value FetchType.EAGER is applied at all times.

KDJE55515-W

The id specified for an element will be ignored because a primary key was specified for an entity multiple times. (entity = aa....aa, element = bb....bb)

aa....aa: Entity class

bb....bb: Field or property for which the <id> tag is to be specified

Description: The specification of the <id> tag will be ignored because the primary key is specified more than once for the entity.
Action: Check the settings of the primary key. If you cannot resolve the error, contact the maintenance personnel.

KDJE55516-W

The specified inheritance will be ignored because inheritance information was specified for an entity multiple times. (entity = aa....aa)

aa....aa: Entity class

Description: The specification of the <inheritance> tag will be ignored because the inheritance strategy is specified more than once for the entity.
Action: Check the settings of the inheritance strategy. If you cannot resolve the error, contact the maintenance personnel.

KDJE55517-W

The specified @SecondaryTable(s) information will be ignored because table information was specified for an entity multiple times. (entity = aa....aa)

aa....aa: Entity class for which @SecondaryTable(s) will be specified

Description: The specification of @SecondaryTable(s) will be ignored because the table information is specified more than once for the entity.
Action: Check the settings of the table information. If you cannot resolve the error, contact the maintenance personnel.

KDJE55518-W

The specified @Table information will be ignored because table information was specified for an entity multiple times. (entity = aa....aa)

aa....aa: Entity class for which @Table is to be specified

Description: The specification of @Table will be ignored because the table information is specified more than once for the entity.
Action: Check the settings of the table information. If you cannot resolve the error, contact the maintenance personnel.

KDJE55519-W

The specified id-class will be ignored because primary key information was specified for an entity multiple times. (entity = aa....aa, id-class = bb....bb)

aa....aa: Entity class

bb....bb: Entity class specified in the <id-class> tag

Description: The specification of the <id-class> tag will be ignored because the primary key information is specified more than once for the entity.
Action: Check the settings of the primary key. If you cannot resolve the error, contact the maintenance personnel.

KDJE55520-W

The specified @IdClass information will be ignored because primary key information was specified for an entity multiple times. (entity = aa....aa, @IdClass = bb....bb)

aa....aa: Entity class

bb....bb: Entity class for which @IdClass is specified

Description: The specification of @IdClass will be ignored because the primary key information is specified more than once for the entity.
Action: Check the settings of the primary key. If you cannot resolve the error, contact the maintenance personnel.

KDJE55521-W

The named-native-query defined in the O/R mapping file will be ignored because a query with that name already exists. (file = aa....aa, query = bb....bb)

aa....aa: File name in which the <named-native-query> tag is defined

bb....bb: Query name specified in the <named-native-query> tag

Description: The specification of the <named-native-query> tag defined in the O/R mapping file will be ignored because the query name is already in use.
Action: Check the specification contents of the <named-native-query> tag of O/R mapping file.

KDJE55522-W

Ignoring the @NamedNativeQuery specified on class since a query with that name already exists. (class = aa....aa, query = bb....bb)

aa....aa: Class name in which @NamedNativeQuery is defined

bb....bb: Query name of @NamedNativeQuery

Description: The specification of @NamedNativeQuery will be ignored because the query name is already in use.
Action: Check the specification contents of the <named-native-query> tag of the O/R mapping file and @NamedNativeQuery.

KDJE55523-W

The specified embedded-id will be ignored because primary key information was specified for an entity multiple times. (entity = aa....aa, element = bb....bb)

aa....aa: Entity class

bb....bb: Field or property in which the <embedded-id> tag is to be specified

Description: The specification of the <embedded-id> tag will be ignored because the primary key information is specified more than once for the entity.
Action: Check the settings of the primary key. If you cannot resolve the error, contact the maintenance personnel.

KDJE55524-W

The specified table will be ignored because table information was specified for an entity multiple times. (entity = aa....aa)

aa....aa: Entity class in which the <table> tag is to be specified

Description: The specification of the <table> tag will be ignored because the table information is specified more than once for the entity.
Action: Check the settings of the table information. If you cannot resolve the error, contact the maintenance personnel.

KDJE55525-W

The specified secondary-table will be ignored because table information was specified for an entity multiple times. (entity = aa....aa)

aa....aa: Entity class for which the <secondary-table> tag is to be specified

Description: The specification of the <secondary-table> tag will be ignored because the table information is specified more than once for the entity.
Action: Check the settings of the table information. If you cannot resolve the error, contact the maintenance personnel.

KDJE55526-W

The platform of the connected database was not able to be specified. There is a possibility that peculiar processing to the database cannot be executed. (platform = aa....aa)

aa....aa: Platform name of the database in use

Description: The platform of the connected database could not be determined. Processing specific to the database might not execute.
Action: Check if the connection-destination database is supported by the Cosminexus JPA provider.

KDJE55527-E

Transformation processing for a class has failed. (class = aa....aa, detail = bb....bb)

aa....aa: Class that failed in the conversion processing (class path)

bb....bb: Exception information

Description: The conversion processing for the class has failed.
Action: Acquire the exception information, and then contact the maintenance personnel.

KDJE55528-E

An attempt to output a message to the operation log file has failed. (detail = aa....aa, internal id = bb....bb, persistence unit = cc....cc)

aa....aa: Exception information

bb....bb: Internal ID of the operation log

cc....cc: Persistent unit name

Description: An attempt to output a message in the operation log has failed.
Action: Acquire the exception information, and then contact the maintenance personnel.

KDJE55529-E

A file system exception occurred during the transformation processing for a class. (class = aa....aa, detail = bb....bb)

aa....aa: Class that failed in the conversion processing (class path)

bb....bb: Exception information

Description: A file system exception occurred during the conversion processing for a class.
Action: Acquire the exception information, and then contact the maintenance personnel.

KDJE55530-E

An internal error occurred during the transformation processing for a class.

Description: An internal error occurred during the conversion processing for a class.
Action: Acquire the exception information, and then contact the maintenance personnel.

KDJE55531-W

Acquisition of entity information about a class to be transformed has failed. (class = aa....aa)

aa....aa: Class name that failed in the conversion processing

Description: An attempt to collect the entity information of a class to be converted has failed.
Action: Acquire the exception information, and then contact the maintenance personnel.

KDJE55532-W

The annotation specified for an element will be ignored because the metadata-complete has been specified for the O/R mapping file. (annotation = aa....aa, element = bb....bb)

aa....aa: Annotation name

bb....bb: Entity class, field, or property in which the annotation is to be specified

Description: The annotation specified in the tag will be ignored because the <metadata-complete> tag is specified in the O/R mapping file.
Action: Check the specification contents of the <metadata-complete> tag of O/R mapping file.

KDJE55533-W

The value specified for non-jta-data-source will be ignored because the transaction type is JTA. (persistence unit = aa....aa)

aa....aa: Persistence unit name

Description: The transaction type is JTA. A value is specified in the <non-jta-data-source> tag, but the value will be ignored.
Action: Check the transaction attribute of the <persistence-unit> tag of persistence.xml, and the specification contents of the <non-jta-data-source> tag.

KDJE55534-W

The named-query defined in the O/R mapping file will be ignored because a query with that name already exists. (file = aa....aa, query = bb....bb)

aa....aa: File name in which the <named-query> tag is defined

bb....bb: Query name of the <named-query> tag

Description: The specification of the <named-query> tag defined in the O/R mapping file will be ignored because the query name is already in use.
Action: Check the specification contents of the <named-query> tag of O/R mapping file.

KDJE55535-W

The specified @NamedQuery information will be ignored because a query with that name already exists. (class = aa....aa, query = bb....bb)

aa....aa: Class name in which @NamedQuery is defined

bb....bb: Query name of @NamedQuery

Description: The specification of @NamedQuery will be ignored because the query name is already in use.
Action: Check the specification contents of the <named-query> tag of the O/R mapping file and @NamedQuery.

KDJE55536-W

An invalid property value is specified. The default value will be used. (property = aa....aa, value = bb....bb, default = cc....cc)

aa....aa: Property name

bb....bb: Value specified in property

cc....cc: Default value

Description: The default value will be used because an invalid value is specified in the property.
Action: Check the property value of the user property file (usrconf.properties), and specify the correct value.

KDJE55537-E

An exception occurred during the construction of the SQL statement. (detail = aa....aa)

aa....aa: Exception information

Description: An exception occurred during the construction of the SQL statement.
Action: Acquire the exception information, and then contact the maintenance personnel.

KDJE55538-E

As a result of executing the SQL statement, an exception was received from the database. (detail = aa....aa)

aa....aa: Exception information

Description: As a result of executing the SQL statement, an exception is received from the database.
Action: Check the problem, and take action. If you cannot resolve the error, contact the maintenance personnel.

KDJE55539-W

An exception occurred during mapping of data acquired from the database. (column = aa....aa, java type = bb....bb, detail = cc....cc)

aa....aa: Database column name

bb....bb: Java type that failed to be mapped

cc....cc: Exception information

Description: An exception occurred during the mapping process of the data collected from the database.
Action: Make sure that the data in the database is appropriate for mapping in the Java type.

KDJE56500-W

Deployment of this persistence unit was skipped because a persistence unit that has same name has already been deployed. (persistence unit root = aa....aa, persistence unit name = bb....bb)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

Description: The deployment of the persistent unit is skipped because a persistent unit with the same name is already deployed.
Action: Make changes in such a way so that more than one persistent unit with the same name is not defined in a single EJB-JAR, and WAR or EAR.

KDJE56501-E

No persistence unit with the specified name has been defined. (persistence unit name = aa....aa)

aa....aa: Persistence unit name

Description: The persistent unit with the specified name is not defined.
Action: In the PersistenceContext, PersistenceUnit annotation, or the <persistence-context-ref> and <persistence-unit-ref> tabs of the Deployment Descriptor, specify the persistent unit name defined in the application.

KDJE56502-E

No persistence unit that has the specified persistence unit root has been defined. (persistence unit name = aa....aa)

aa....aa: Persistence unit name

Description: A persistent unit having the root of the specified persistent unit is not defined.
Action: When using the # syntax in PersistenceContext, PersistenceUnit annotation, or in the <persistence-context-ref> and <persistence-unit-ref> tabs of the Deployment Descriptor, specify the correct root of the persistent unit defined in the application.

KDJE56503-E

Instantiation of a persistence provider class has failed. (persistence provider class = aa....aa)

aa....aa: JPA provider class name

Description: An instance of the JPA provider class could not be created.
Action: Make sure that the JPA provider class name specified in the provider element or <ejbserver.jpa.defaultProviderClassName> tag of persistence.xml is correct and the specified class is included in the class path.

KDJE56504-E

The persistence unit to use cannot be identified because multiple persistence units exist within the scope but no persistence unit name is specified for the reference. Explicitly specify the persistence unit name for the reference.

Description: Irrespective of the fact that two or more persistent units are defined in the reference scope of the persistent unit, the persistent unit name has not been specified in the reference.
Action: Specify the persistent unit name in PersistenceContext, PersistenceUnit annotation, or the <persistence-context-ref> and <persistence-unit-ref> tabs of the Deployment Descriptor.

KDJE56505-E

The name of a persistence unit must not be an empty string. Specify at least one character for the name.

Description: Null characters cannot be specified in the persistent unit name in persistence.xml.
Action: Specify a character string of one or more characters in the persistent unit name of persistence.xml.

KDJE56506-E

The jar file specified for the jar-file element cannot be found. (persistence unit root = aa....aa, persistence unit name = bb....bb, jar file name = cc....cc)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: JAR file name

Description: The JAR file specified in the jar-file element of persistence.xml cannot be found.
Action: Specify a JAR file that can be referenced in the jar-file element of persistence.xml.

KDJE56507-E

An entity manager in the transaction scope could not be acquired because the transaction is not in the active status.

Description: The entity manager of the transaction scope could not be acquired because the transaction is not in an active status.
Action: Make sure that the transaction timeout has not occurred.

KDJE56508-E

This operation cannot be invoked using a container-managed entity manager. (operation = aa....aa)

aa....aa: Operation

Description: This operation cannot be invoked using a container-managed entity manager.
Action: Check the application codes to make sure that a method that cannot be invoked using a container-managed entity manager is not invoked.

KDJE56509-E

This operation must be invoked in a transaction context. (operation = aa....aa)

aa....aa: Operation

Description: An operation that cannot be invoked outside a transaction context is invoked.
Action: Check the application codes to make sure that an operation that cannot be invoked outside a transaction context is not invoked.

KDJE56510-E

This operation is not supported for a query object created when no transactions existed. (operation = aa....aa)

aa....aa: Operation

Description: An operation that is not supported by a query object created when no transactions exist is invoked.
Action: Check the application codes to make sure that an operation that is not supported by a query object created when no transactions exist is not invoked.

KDJE56511-E

An extended persistence context cannot be used except with a stateful session bean. (component = aa....aa)

aa....aa: Component

Description: A persistent context extended in other than a stateful session bean cannot be used.
Action: Check the application codes to make sure that a persistent context extended from other than a stateful session bean is not used.

KDJE56512-E

A stateful session bean that has a reference to an extended persistence context was invoked for a transaction already associated with another persistence context.

Description: A stateful session bean referencing an extended persistent context cannot be invoked in a transaction that is already associated with another persistent context.
Action: Check the application codes to make sure that a stateful session bean referencing an extended persistent context is not invoked in a transaction that is already associated with another persistent context.

KDJE56513-I

A persistence unit will now be deployed. (application name = aa....aa, persistence unit root = bb....bb, persistence unit name = cc....cc)

aa....aa: Application name

bb....bb: Root of the persistent unit

cc....cc: Persistent unit name

Description: The deployment of the persistent unit will start.

KDJE56514-I

A persistence unit was successfully deployed. (application name = aa....aa, persistence unit root = bb....bb, persistence unit name = cc....cc)

aa....aa: Application name

bb....bb: Root of the persistent unit

cc....cc: Persistent unit name

Description: A persistent unit has been deployed.

KDJE56515-E

Deployment of a persistence unit has failed. (application name = aa....aa, persistence unit root = bb....bb, persistence unit name = cc....cc)

aa....aa: Application name

bb....bb: Root of the persistent unit

cc....cc: Persistent unit name

Description: An attempt to deploy a persistent unit has failed.
Action: Follow the action described in the message reporting the cause of failure.

KDJE56516-I

All persistence units within the application will now be undeployed. (application name = aa....aa)

aa....aa: Application name

Description: The undeploy of the persistent units within the application will start.

KDJE56517-I

All persistence units within the application were successfully undeployed. (application name = aa....aa)

aa....aa: Application name

Description: All persistent units within the application have been undeployed.

KDJE56518-I

All persistence units within the WAR file will now be undeployed. (application name = aa....aa, path of the WAR file = bb....bb)

aa....aa: Application name

bb....bb: Path of the WAR file

Description: The undeploy of the persistent units within the WAR file will start.

KDJE56519-I

All persistence units within the WAR file were successfully undeployed. (application name = aa....aa, path of the WAR file = bb....bb)

aa....aa: Application name

bb....bb: Path of the WAR file

Description: The persistent units within the WAR file have been undeployed.

KDJE56520-E

Acquisition of the JTA data source specified for the jta-data-source element in the persistence.xml file has failed. (persistence unit root = aa....aa, persistence unit name = bb....bb, JTA data source = cc....cc)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: JTA data source

Description: An attempt to acquire the JTA data source specified in the jta-data-source element of persistence.xml has failed.
Action: Examine the exception that caused the error occurrence, and then take action.

KDJE56521-E

Acquisition of the non-JTA data source specified for the non-jta-data-source element in the persistence.xml file has failed. (persistence unit root = aa....aa, persistence unit name = bb....bb, non-JTA data source = cc....cc)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: Non-JTA data source

Description: An attempt to acquire the non-JTA data source specified in the non-jta-data-source element of persistence.xml has failed.
Action: Examine the exception that caused the error occurrence, and then take action.

KDJE56524-E

Creation of a URL or URI has failed. (path = aa....aa)

aa....aa: Path

Description: An attempt to create a URL or URI has failed.
Action: Examine the exception that caused the error occurrence, and then take action.

KDJE56525-E

An IOException occurred while deploying persistence units. (persistence unit root = aa....aa)

aa....aa: Persistence unit root

Description: An IOException occurred in the deployment processing of the persistent unit.
Action: Examine the exception that caused the error occurrence, and then take action.

KDJE56526-E

An attempt to parse the persistence.xml file has failed. (persistence unit root = aa....aa, cause = bb....bb)

aa....aa: Persistence unit root

bb....bb: Cause

Description: An attempt to parse persistence.xml has failed.
Action: Examine the cause, and check the contents of persistence.xml.

KDJE56527-E

A JTA data source must be specified when the transaction type of the persistence unit is JTA. (persistence unit root = aa....aa, persistence unit name = bb....bb)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

Description: If the transaction type of the persistent unit is JTA, a JTA data source must be specified.
Action: Correctly define the referencing of the resource adapter deployed and started as a standalone module in the jta-data-source element of persistence.xml, the system property ejbserver.jpa.defaultJtaDsName, or the system property ejbserver.jpa.overrideJtaDsName. When referencing a resource adapter conforming to Connector 1.0 specifications, specify the resource-adapter-display-name or resource-adapter-optional-name. When referencing a resource adapter conforming to Connector 1.5 specifications, specify the resource-adapter-display-name!connection-definition-identifier, or the optional name of the resource adapter.

KDJE56528-E

A non-JTA data source must be specified when the transaction type of the persistence unit is RESOURCE_LOCAL. (persistence unit root = aa....aa, persistence unit name = bb....bb)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

Description: If the transaction type of the persistent unit is RESOURCE_LOCAL, a non-JTA data source must be specified.
Action: Correctly define the referencing of the resource adapter deployed and started as a standalone module in the non-jta-data-source element of persistence.xml, the system property ejbserver.jpa.defaultNonJtaDsName, or the system property ejbserver.jpa.overrideNonJtaDsName. When referencing a resource adapter conforming to Connector 1.0 specifications, specify the resource-adapter-display-name or resource-adapter-optional-name. When referencing a resource adapter conforming to Connector 1.5 specifications, specify the resource-adapter-display-name!connection-definition-identifier, or the optional name of the resource adapter.

KDJE56529-E

The JTA data source specified for the system property ejbserver.jpa.defaultJtaDsName or the system property ejbserver.jpa.overrideJtaDsName or the jta-data-source element in the persistence.xml file cannot be found. (persistence unit root = aa....aa, persistence unit name = bb....bb, JTA data source = cc....cc)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: JTA data source

Description: The JTA data source specified in the jta-data-source element of persistence.xml, the system property ejbserver.jpa.defaultJtaDsName, or the system property ejbserver.jpa.overrideJtaDsName cannot be found.
Action: Correctly define the referencing of the resource adapter deployed and started as a standalone module in the jta-data-source element of persistence.xml, the system property ejbserver.jpa.defaultJtaDsName, or the system property ejbserver.jpa.overrideJtaDsName. When referencing a resource adapter conforming to Connector 1.0 specifications, specify the resource-adapter-display-name or resource-adapter-optional-name. When referencing a resource adapter conforming to Connector 1.5 specifications, specify the resource-adapter-display-name!connection-definition-identifier, or the optional name of the resource adapter.

KDJE56530-E

The non-JTA data source specified for the system property ejbserver.jpa.defaultNonJtaDsName or the system property ejbserver.jpa.overrideNonJtaDsName or the non-jta-data-source element in the persistence.xml file cannot be found. (persistence unit root = aa....aa, persistence unit name = bb....bb, non-JTA data source = cc....cc)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: Non-JTA data source

Description: The non-JTA data source specified in the non-jta-data-source element of persistence.xml, the system property ejbserver.jpa.defaultNonJtaDsName, or the system property ejbserver.jpa.overrideNonJtaDsName cannot be found.
Action: Correctly define the referencing of the resource adapter deployed and started as a standalone module in the non-jta-data-source element of persistence.xml, the system property ejbserver.jpa.defaultNonJtaDsName, or the system property ejbserver.jpa.overrideNonJtaDsName. When referencing a resource adapter conforming to Connector 1.0 specifications, specify the resource-adapter-display-name or resource-adapter-optional-name. When referencing a resource adapter conforming to Connector 1.5 specifications, specify the resource-adapter-display-name!connection-definition-identifier, or the optional name of the resource adapter.

KDJE56531-E

The transaction support level of a resource adapter referenced as a JTA data source must be LocalTransaction or XATransaction. (persistence unit root = aa....aa, persistence unit name = bb....bb, JTA data source = cc....cc, resource adapter name = dd....dd)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: JTA data source

dd....dd: Resource adapter name

Description: The transaction support level of the resource adapter referenced as a JTA data source must be LocalTransaction or XATransaction.
Action: Make sure that the transaction support level of the resource adapter referenced as a JTA data source is LocalTransaction or XATransaction.

KDJE56532-E

The transaction support level of a resource adapter referenced as a non-JTA data source must be NoTransaction. (persistence unit root = aa....aa, persistence unit name = bb....bb, non-JTA data source = cc....cc, resource adapter name = dd....dd)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: Non-JTA data source

dd....dd: Resource adapter name

Description: The transaction support level of the resource adapter referenced as a non-JTA data source must be NoTransaction.
Action: Make sure that the transaction support level of the resource adapter referenced as a non-JTA data source is NoTransaction.

KDJE56533-E

The connection factory interface of a resource adapter referenced by a persistence unit must be javax.sql.DataSource. (persistence unit root = aa....aa, persistence unit name = bb....bb, data source = cc....cc, resource adapter name = dd....dd, connection factory interface = ee....ee)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: Data source

dd....dd: Resource adapter name

ee....ee: Connection factory interface

Description: The connection factory interface of the resource adapter referenced from a persistent unit must be javax.sql.DataSource.
Action: Make sure that the connection factory interface of the resource adapter referenced from a persistent unit is javax.sql.DataSource.

KDJE56534-E

The transaction type of a persistence unit used by a container-managed entity manager must be JTA. (persistence unit root = aa....aa, persistence unit name = bb....bb, path of the WAR file or EJB-JAR file = cc....cc)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: Path of the WAR file or the EJB-JAR file

Description: The transaction type of a persistence unit used by a container-managed entity manager must be JTA.
Action: Make sure that the transaction type of a persistence unit used by a container-managed entity manager is specified as JTA.

KDJE56535-E

A reference to an extended persistence context can only be defined with a stateful session bean. (persistence unit root = aa....aa, persistence unit name = bb....bb, path of the WAR file or EJB-JAR file = cc....cc, EJB name = dd....dd)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: Path of the WAR file or the EJB-JAR file

dd....dd: EJB name (only for an EJB)

Description: A referencing of the extended persistence context cannot be defined in other than a stateful session bean.
Action: Make sure that the referencing of the extended persistence context is not defined in other than a stateful session bean.

KDJE56536-E

Deployment of persistence units included in a Web application has failed. (path of the Web application = aa....aa, cause = bb....bb)

aa....aa: Path of the Web application

bb....bb: Cause

Description: An attempt to deploy the persistence units included in the Web application has failed.
Action: Follow the action described in the message included in the cause of the error.

KDJE56538-E

An entity manager cannot be invoked from this method. (method = aa....aa)

aa....aa: Method

Description: The entity manager cannot be invoked from this method.
Action: Check the user program to make sure that the entity manager is not invoked from a location at which invocation is not allowed.

KDJE56539-E

PersistenceProvider#createContainerEntityManagerFactory method of the JPA provider threw an exception.(persistence unit name = aa....aa, persistence provider class name = bb....bb, exception = cc....cc)

aa....aa: Persistence unit name

bb....bb: JPA provider class name

cc....cc: Exception

Description: An exception occurred in the createContainerEntityManagerFactory method of the JPA provider.
Action: Examine the exception that caused the error occurrence, and then take action.

KDJE58300-E

The specified property value is invalid. (resource adapter = aa....aa, property = bb....bb, value = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Property name

cc....cc: Specified value

Description: An invalid value is specified in the property of the TP1 inbound adapter.
Action: Specify an appropriate value in the property.

KDJE58301-W

The specified property value is invalid. The default value will be used. (resource adapter = aa....aa, property = bb....bb, specified value = cc....cc, default value = dd....dd)

aa....aa: Resource adapter display name

bb....bb: Property name

cc....cc: Specified value

dd....dd: Default value

Description: An invalid value is specified in the property of the TP1 inbound adapter. The default value will be used.
Action: If the problem of the default value occurs in the operation, stop the resource adapter, reset the property value, and then restart the resource adapter.

KDJE58302-E

A required property value is not specified. (resource adapter = aa....aa, property = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Property name

Description: A property that must be set up is not specified.
Action: Specify the property that must be set up.

KDJE58303-E

On the J2EE server, there is already a TP1 Inbound Adapter that has the same service group name.(resource adapter = aa....aa, service group = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Service group name of the resource adapter

Description: The service group name specified in the TP1 inbound adapter is already used by another TP1 inbound adapter.
Action: Check the settings of the service group name specified in the TP1 inbound adapter that has failed to start, correct the property value, and then restart the resource adapter.

KDJE58304-E

On the TP1 Inbound Adapter, there is already a service that has the same service name. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Service group name of the resource adapter

cc....cc: Service name of MDB (service)

Description: The service name specified in ActivationSpec of MDB (service) is already used by another MDB (service) within the same service group.
Action: Check the service name settings of the MDB (service) that has failed to start, correct the property value, and then restart the J2EE application.

KDJE58350-I

The TP1 Inbound Adapter started. (resource adapter = aa....aa, service group = bb....bb, scd_port = cc....cc, rn_port = dd....dd)

aa....aa: Resource adapter display name

bb....bb: Service group name of the resource adapter

cc....cc: Port number of port with pending RPC request

dd....dd: Port number of port with pending synchronous messages

Description: The TP1 inbound integrated functionality has started.

KDJE58351-I

The TP1 Inbound Adapter ended. (resource adapter = aa....aa, service group = bb....bb, scd_port = cc....cc, trn_port = dd....dd)

aa....aa: Resource adapter display name

bb....bb: Service group name of resource adapter

cc....cc: Port number of port with pending RPC request

dd....dd: Port number of port with pending synchronous messages

Description: The TP1 inbound integrated functionality has ended.

KDJE58352-E

The port aa....aa for the TP1 Inbound Adapter could not be opened. (resource adapter = bb....bb, service group = cc....cc)

aa....aa: Port number set up in the scd_port or trn_port property of TP1 inbound adapter

bb....bb: Resource adapter display name

cc....cc: Service group name of resource adapter

Description: While starting the TP1 inbound integrated functionality, the port number with pending communication from OpenTP1 did not open. The port might already be used. Starting of resource adapter will be interrupted.
Action: Check whether the port number set up in the scd_port or trn_port property of the TP1 inbound adapter is already used. If the port number is already used, stop the application using the port number or specify another port number in scd_port or trn_port, and then restart the resource adapter.

KDJE58354-E

An error occurred while the request was being received. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, exception = gg....gg, read count = hh....hh)

aa....aa: Resource adapter display name

bb....bb: Service group name (if the service group name cannot be determined, a single-byte hyphen (-) is displayed)

cc....cc: Service name (if the service name cannot be determined, a single-byte hyphen (-) is displayed)

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1 (if the listen port number cannot be determined, a single-byte hyphen (-) is displayed)

ff....ff: CommNo of root AP information

gg....gg: Information of occurring error

hh....hh: Occurrence count of the read method of each connection

Description

While receiving the RPC request using the TP1 inbound integrated functionality, the RPC request reception is interrupted because of a communication problem, such as a timeout and disconnection.

If a connection is established, the connection will be disconnected.

Action

Check whether the problem exists in the communication lines or OpenTP1, and then remove the problem.

KDJE58355-E

The request data is invalid. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, detail = gg....gg)

aa....aa: Resource adapter display name

bb....bb: Service group name (if the service group name cannot be determined, a single-byte hyphen (-) is displayed)

cc....cc: Service name (if the service name cannot be determined, a single-byte hyphen (-) is displayed)

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1 (if the listen port number cannot be determined, a single-byte hyphen (-) is displayed)

ff....ff: CommNo of root AP information

gg....gg: Details

Description

While receiving the RPC request using the TP1 inbound integrated functionality, an invalid data is received. An error has occurred in the settings of OpenTP1, or a client other than OpenTP1 client is connected.

The received data will be cancelled, and then the connection will be disconnected.

Action

Take the following action based on the details:

header: Received header contents (hexadecimal 12 digits): Check whether an invalid client is connected. If an invalid client is connected, modify the settings in such a way so that the invalid client is disconnected.
Scheduler direct function is not used.: Check that the user service network definition uses the scheduler direct function.
dc_rpc_call function is not used.: Check that the dc_rpc_call function is used, and the service is invoked.
It is not the first request data.: The RPC request message received by the TP1 inbound adapter might not be the first message, and might be a later message. Re-execute the RPC request.
An illegal client is connected. (Maintenance information): Check whether an invalid client is connected. If an invalid client is not connected, collect the maintenance information, and then contact maintenance personnel.

KDJE58356-E

The request data is not supported. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, detail = gg....gg)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

gg....gg: Detail

Description

The TP1 inbound integrated functionality received an unsupported data while receiving the RPC request.

The received data will be cancelled, and then the connection will be disconnected.

Action

Take the following action based on the detail:

The value of the flags argument of the dc_rpc_call function is illegal.: Check that DCNOFLAGS or DCNOFLAGS | DCRPC_TPNOTRAN is specified in the flags argument of the dc_rpc_call functionality.
Version of OpenTP1 is not supported.: Check that OpenTP1 version is a supported version.
User data compression function is not supported.: Check that the user data compression functionality (Y in the rpc_datacomp operand of the common system definitions) is not used.
TP1/ Online Tester is not supported.: Check that OpenTP1 does not use the online tester.

KDJE58357-E

The service group name specified in the request is invalid. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

The TP1 inbound integrated functionality received an invalid service group name of the RPC request.

An error exists in the service group name specified in the service_group property of the TP1 inbound adapter or in the service group name of the RPC request.

The received data will be cancelled, and then the connection will be disconnected.

Action

Check whether the service group name specified in the group argument of the dc_rpc_call functionality and the service group name set up in the service_group property of the TP1 inbound adapter are correct.

If the service group name specified in the group argument of the dc_rpc_call functionality is incorrect, remove the problem, and then resend the message.

If the service group name set up in the resource adapter properties is incorrect, stop the resource adapter, change the value of the property, and then restart the resource adapter.

Note that if the service group name is invalid, OpenTP1 resends the RPC request. For this reason, this message will be output only the number of times the RPC request is resent from OpenTP1.

KDJE58358-E

A timeout occurred while the request was being received. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

A timeout occurred while receiving the RPC request in the TP1 inbound integrated functionality.

The RPC request being received is cancelled, and then the connection is disconnected.

Action

Check whether a problem exists in the communication line and OpenTP1, and then remove the problem.

Also check whether a problem exists in the timeout value of the RPC request reception set up in the rpc_receive_timeout property of the TP1 inbound adapter. If the problem exists, stop the resource adapter, change the value of the property, and then restart the resource adapter.

KDJE58359-E

There is not enough space in the buffer to process the request. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

The temporary buffer area, required for RPC request reception with the TP1 inbound integrated functionality, is insufficient.

The RPC request being received will be cancelled, and then the connection will be disconnected.

Action

The message structure list for processing the RPC request temporarily is insufficient. Resend the RPC request. If this message is output continuously, leave the timeout time from the start of the message reception until the message reception ends (rpc_receive_timeout) for a while, and then resend the RPC request or stop and restart the resource adapter.

KDJE58360-E

The number of received requests exceeds the waiting schedule queue limit. The request failed. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

The number of RPC requests pending processing in the TP1 inbound integrated functionality has reached the full schedule queue size. New received RPC requests will be cancelled.

Action

Check whether the setting of the schedule queue size set up in the queue_max_length property of the TP1 inbound adapter is appropriate.

If the set up value is inappropriate, stop the J2EE application, change the value of the property, and then restart the J2EE application.

KDJE58361-W

The number of queued requests has reached the warning level. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, rate = dd....dd, current value = ee....ee, max = ff....ff, next warn interval = gg....gg)

aa....aa: Resource adapter display name

bb....bb: Service group name of resource adapter

cc....cc: Service name of MDB (service)

dd....dd: Current use rate

ee....ee: Current value

ff....ff: Maximum value

gg....gg: Interval until next warning

Description

The percentage of RPC requests retained in the schedule queue of the TP1 inbound integrated functionality has reached the warning area.

Action

Check whether the schedule queue size specified in the queue_max_length property of the TP1 inbound adapter is appropriate.

If this message is output frequently, check whether stay_watch_queue_rate and stay_watch_check_interval specified in the properties of the TP1 inbound adapter are appropriate.

If the specified values are inappropriate, stop the J2EE application, change the values of the property, and then restart the J2EE application.

KDJE58362-E

The service name specified in the request is invalid. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

The TP1 inbound integrated functionality received an invalid service name. The causes might be as follows:

An error exists in the service name specified in the service property of ActivationSpec of MDB (service) or in the RPC request service name.
J2EE application (MDB) does not exist or is not operating.

The received data will be cancelled, and then the connection will be disconnected.

Action

Check the following contents:

Check that the service name specified in the service argument of the dc_rpc_call functionality is correct. If the service name is incorrect, remove the problem, and then resend the RPC request. If the service name is correct, check whether MDB (service) is operating.
Check that the service name specified in the service property of ActivationSpec of MDB (service) is correct. If the service name is incorrect, stop the J2EE application, correct the service name, and then restart the J2EE application.
If MDB (service) is not operating, start the J2EE application.

KDJE58363-E

Transaction linkage could not be started. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description: Transaction linkage could not be started in OpenTP1.
Action: Specify true in ejbserver.distributedtx.XATransaction.enabled key of usrconf.properties (User property file for J2EE server) for transaction linkage in OpenTP1.

KDJE58400-E

An attempt to connect with OpenTP1 has failed. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, exception = gg....gg)

aa....aa: Resource adapter display name

bb....bb: Service group name (When service group name cannot be determined, a single-byte hyphen (-) is displayed)

cc....cc: Service name (When service name cannot be determined, a single-byte hyphen (-) is displayed)

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

gg....gg: Information of occurring exception

Description

An attempt is made to respond to the RPC request received by the TP1 inbound integrated functionality, but the connection with OpenTP1 has failed.

The response will be cancelled.

Action

Check that OpenTP1 is operating normally and no problem has occurred in the communication lines of OpenTP1 and TP1 inbound adapter.

If problems of temporary communication lines such as depletion of port due to concentration of load occur, connection with OpenTP1 might succeed by retrying while sending a response.

Check whether settings of the retry interval while sending response (send_retry_interval) and the retry count (send_retry_count) are appropriate.

If there is no problem in OpenTP1 and the communication line, check whether the setting of the timeout time (connection_timeout) of the send connection of the TP1 inbound adapter is appropriate.

KDJE58401-E

An error occurred while the RPC response data was being sent to OpenTP1. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, exception = gg....gg)

aa....aa: Resource adapter display name

bb....bb: Service group name (When service group name cannot be determined, a single-byte hyphen (-) is displayed)

cc....cc: Service name (When service name cannot be determined, a single-byte hyphen (-) is displayed)

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

gg....gg: Information of occurring exception

Description

An attempt is made to respond to the RPC request received by the TP1 inbound integrated functionality, but an error occurred while sending the message.

The sending connection will be disconnected, and then the response will be cancelled.

Action

The connection with OpenTP1 might be connected. Check whether a problem exists in the communication line of OpenTP1 and the TP1 inbound adapter. If there is no problem, check whether the send timeout (tcp_send_timeout) setting of the TP1 inbound adapter is appropriate.

KDJE58402-W

An attempt to connect with OpenTP1 has failed. The connecting will retry. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, exception = gg....gg, retry count = hh....hh, retry interval = ii....ii)

aa....aa: Resource adapter display name

bb....bb: Service group name (When service group name cannot be determined, a single-byte hyphen (-) is displayed)

cc....cc: Service name (When service name cannot be determined, a single-byte hyphen (-) is displayed)

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

gg....gg: Information of occurring exception

hh....hh: Retry count

ii....ii: Retry intervals

Description

An attempt is made to respond to the RPC request received by the TP1 inbound integrated functionality, but an attempt to connect OpenTP1 has failed.

Execute retry.

Action

Check that OpenTP1 is operating normally, and no problem has occurred in the communication lines of OpenTP1 and the TP1 inbound adapter.

KDJE58403-W

An error occurred while the RPC response data was being sent to OpenTP1. The sending will retry. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, exception = gg....gg, retry count = hh....hh, retry interval = ii....ii)

aa....aa: Resource adapter display name

bb....bb: Service group name (When service group name cannot be determined, a single-byte hyphen (-) is displayed)

cc....cc: Service name (When service name cannot be determined, a single-byte hyphen (-) is displayed)

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

gg....gg: Information of occurring exception

hh....hh: Retry count

ii....ii: Retry intervals

Description

An attempt is made to respond to the RPC request received by the TP1 inbound integrated functionality, but an error occurred while sending the message.

Execute retry.

Action

The connection with OpenTP1 might be disconnected. Check whether a problem exists in the communication lines of OpenTP1 and the TP1 inbound adapter.

KDJE58450-I

The service started. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Service group name of the resource adapter

cc....cc: Service name of MDB (service)

Description: MDB (service) is started.

KDJE58452-W

The maximum for the message endpoint instance pool exceeds the number of message processing threads that can be executed at the same time. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, poolsize = dd....dd, threads = ee....ee)

aa....aa: Resource adapter display name

bb....bb: Service group name of the resource adapter

cc....cc: Service name of MDB (service)

dd....dd: Maximum number of instance pools of MDB (service)

ee....ee: Maximum number of invoked threads of MDB (service)

Description

The total of the maximum number of instance pools of MDB (service) invocation threads exceeds.

If the operation continues in this state, MDB (service) invocation threads might not be allocated, while executing the RPC request.

Action

Change the settings to "Sum up nodes of the maximum number of MDB (service) invocation threads ≥ the maximum number of instance pools of MDB (service)".

KDJE58453-I

The service ended. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Service group name of the resource adapter

cc....cc: Service name of MDB (service)

Description: MDB (service) is ended.

KDJE58455-E

The service was forcibly stopped. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

An executing MDB (service) is forced to terminate.

The stop process continues.

Action

Action is not required for canceling an executing MDB (service). If ending the execution of MDB (service), start MDB (service) after the forced termination, and then re-invoke the MDB (service).

KDJE58456-E

An error occurred while the service was being called. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description: An ending MDB (service) is invoked.
Action: Action is not required if MDB (service) is not executed. To execute MDB (service) after ending MDB (service), re-start the MDB (service), and then re-invoke the MDB (service).

KDJE58457-E

A timeout occurred during execution of the service. The service will now be forcibly stopped. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description: A timeout occurred while executing MDB (service).
Action: Check whether the timeout setting value is appropriate. If the timeout setting value is appropriate, action is not required.

KDJE58459-E

A system exception occurred during execution of the service. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, exception = gg....gg)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

gg....gg: Information of occurring exception

Description: A system exception occurred in MDB (service).
Action: Remove the cause of the exception, and then make the changes to avoid occurrence of exceptions.

KDJE58501-E

A timeout occurred while waiting for a response to a temporary close request. (resource adapter = aa....aa, listen port = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Listen port number

Description

The temporary close request could not be received though the maximum pending time of the temporary close response has lapsed, from the time the status of the request has changed to response pending status in temporary close processing,

The respective connection is disconnected forcibly.

Action

Determine whether there is a problem in communication channels or OpenTP1 and resolve the problem.

If KDJE58354-E is output for the same connection before and after this message, the timeout can be avoided when receiving messages from OpenTP1. In such cases, confirm that the maximum pending time for the temporary close response is applicable and if the problem still persists, perform the settings again.

KDJE58502-I

A connection to OpenTP1 has been established. (resource adapter = aa....aa, listen port = bb....bb, client = cc....cc:dd....dd)

aa....aa: Resource adapter display name

bb....bb: Listen port number

cc....cc: IP address of OpenTP1

dd....dd: Listen port number of OpenTP1 (When listen port number cannot be determined, a single-byte hyphen (-) is displayed)

Description: A connection to OpenTP1 has been established.

KDJE58503-I

A connection to OpenTP1 has been disconnected. (resource adapter = aa....aa, listen port = bb....bb, client = cc....cc:dd....dd)

aa....aa: Resource adapter display name

bb....bb: Listen port number

cc....cc: IP address of OpenTP1

dd....dd: Listen port number of OpenTP1 (When listen port number cannot be determined, a single-byte hyphen (-) is displayed)

Description: A connection to OpenTP1 has been disconnected.

KDJE58550-E

Transaction linkage could not be started. (resource adapter = aa....aa, client = bb....bb:cc....cc, TRNGID = dd....dd)

aa....aa: Resource adapter display name

bb....bb: IP address of OpenTP1

cc....cc: Listen port number of OpenTP1

dd....dd: Transaction global identifier

Description: Transaction linkage could not be started in OpenTP1.
Action: Specify true in ejbserver.distributedtx.XATransaction.enabled key of usrconf.properties (User property file for J2EE server) for transaction linkage in OpenTP1.

KDJE58551-E

An unexpected exception occurred. (resource adapter = aa....aa, client = bb....bb:cc....cc, global transaction ID = dd....dd, method = ee....ee, detail = ff....ff)

aa....aa: Resource adapter display name

bb....bb: IP address of OpenTP1

cc....cc: Listen port number of OpenTP1

dd....dd: Global transaction ID of OpenTP1

ee....ee: Method name

ff....ff: Details

Description: An unexpected exception occurred.
Action: Obtain the maintenance information and contact Maintenance Service.

KDJE59100-W

An invalid value is specified in the property. (property name = aa....aa, value = bb....bb, default value = cc....cc)

aa....aa: Property name

bb....bb: Specified character string

cc....cc: Default value of property

Description

An invalid value is specified in the property used by JavaMail. Use default value as the property value.

If the property name is mail.smtp.connectiontimeout, mail.smtps.connectiontimeout, mail.pop3.connectiontimeout, mail.smtp.timeout, mail.smtps.timeout, or mail.pop3.timeout, INFINITE is output as the default property value.

Action

Check property settings and specify appropriate values.

KDJE59101-E

An attempt to connect to the SMTP server failed. (host = aa....aa, port = bb....bb, connection timeout = cc....cc, message = dd....dd)

aa....aa: Specified host name

bb....bb: Specified port number

cc....cc: Timeout value until establishing connection

dd....dd: getMessage() result of the occurred exception

Description

JavaMail failed in an attempt to connect to the SMTP server.

If the user has not specified the mail.smtp.connectiontimeout property or the mail.smtps.connectiontimeout property, -1 is output as the timeout value.

Action

Check and, if necessary, revise the values specified in the host name, port number, and the mail.smtp.connectiontimeout property or the mail.smtps.connectiontimeout property. Also, check the environment settings of network if valid values are specified in the host name, port number, and property.

KDJE59102-E

An attempt to disconnect from the SMTP server failed. (host = aa....aa, port = bb....bb, message = cc....cc)

aa....aa: Host name

bb....bb: Port number

cc....cc: getMessage() result of the occurred exception

Description: JavaMail failed in an attempt to disconnect to the SMTP server.
Action: Check and, if necessary, revise the environment settings of network.

KDJE59103-E

An attempt to connect to the POP3 server failed. (host = aa....aa, port = bb....bb, connection timeout = cc....cc, message = dd....dd)

aa....aa: Specified host name

bb....bb: Specified port number

cc....cc: Timeout value until establishing the connection

dd....dd: getMessage() result of the occurred exception

Description

JavaMail failed in an attempt to connect to the POP3 server.

If the user has not specified the mail.pop3.connectiontimeout property, -1 is output as the timeout value.

Action

Check and, if necessary, revise the values specified in the host name, port number, and mail.pop3.connectiontimeout property. Also check the environment settings of network if valid values are specified in the host name, port number, and property.

KDJE59104-E

An attempt to disconnect from the POP3 server failed. (host = aa....aa, port = bb....bb, message = cc....cc)

aa....aa: Host name

bb....bb: Port number

cc....cc: getMessage() result of the occurred exception

Description: JavaMail failed in an attempt to disconnect with POP3 server.
Action: Check and, if necessary, revise the environment settings of network.

KDJE59105-E

An exception occurred during communication with the SMTP server. (communication processing = aa....aa, timeout = bb....bb, message = cc....cc)

aa....aa: Character string indicating communication processing

bb....bb: Communication timeout value

cc....cc: getMessage() result of the occurred exception

Description

An exception occurred in the JavaMail and SMTP server communication.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.1 For the SMTP and SMTPS related messages.

If the user has not specified the mail.smtp.timeout property or the mail.smtps.timeout property, -1 is output as the timeout value.

Action

Check and, if necessary, revise the value specified for the mail.smtp.timeout property or the mail.smtps.timeout property, when a timeout occurs. Alternatively, check the environment settings of network.

KDJE59106-E

An exception occurred during communication with the POP3 server. (communication processing = aa....aa, timeout = bb....bb, message = cc....cc)

aa....aa: Character string indicating communication processing

bb....bb: Communication timeout value

cc....cc: getMessage() result of the occurred exception

Description

An exception occurred in the JavaMail and POP3 server communication.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.2 For the POP3-related messages.

If the user has not specified the mail.pop3.timeout property, -1 is output as the timeout value.

Action

Check and, if necessary, revise the value specified for the mail.pop3.timeout property when timeout occurs. Alternatively, check the environment settings of network.

KDJE59107-E

While trying to connect to the SMTP server, JavaMail received an abnormal response code. (response = aa....aa, response code = bb....bb)

aa....aa: Response from server

bb....bb: Normally terminated response code

Description

When trying to connect to the SMTP server, JavaMail has received an abnormal response code.

Output the response code for the response from server.

Action

Determine the cause by referencing the response and log of the SMTP server and the SMTP server manual.

KDJE59108-E

While trying to communicate with the SMTP server, JavaMail received an abnormal response code. (communication processing = aa....aa, response = bb....bb, response code = cc....cc)

aa....aa: Character string indicating communication processing

bb....bb: Response from server

cc....cc: Normally terminated response code

Description

While trying to communicate with the SMTP server, JavaMail has received an abnormal response code.

Output the response code for the response from server.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.1 For the SMTP and SMTPS related messages.

Action

Determine the cause by referencing the response and log of the SMTP server and the SMTP server manual, and then take action.

KDJE59109-E

While trying to connect with the POP3 server, JavaMail received an abnormal response code. (response = aa....aa)

aa....aa: Response from server

Description

When trying to connect with the POP3 server, JavaMail received an abnormal response code.

Output the response code for the response from server.

Action

Determine the cause by referencing the response and log of POP3 server and the POP3 server manual, and then take action.

KDJE59110-E

While trying to communicate with the POP3 server, JavaMail received an abnormal response code. (communication processing = aa....aa, response = bb....bb)

aa....aa: Character string indicating communication processing

bb....bb: Response from server

Description

When trying to communicate with the POP3 server, JavaMail received an abnormal response code.

Output the response code for the response from server.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.2 For the POP3-related messages.

Action

Determine the cause by referencing the response and log of POP3 server and the POP3 server manual, and then take action.

KDJE59111-E

An invalid response was received from the SMTP server. (communication processing = aa....aa, response = bb....bb)

aa....aa: Character string indicating communication processing

bb....bb: Response from server

Description

An invalid response other than RFC specifications was received from the SMTP server.

Only the first row of response is output for the response received from the server. However, if no response exists, an empty string is displayed.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.1 For the SMTP and SMTPS related messages.

Action

Take actions according to the log and trace information.

KDJE59112-E

An invalid response was received from the POP3 server. (communication processing = aa....aa, response = bb....bb)

aa....aa: Character string indicating communication processing

bb....bb: Response from server

Description

An invalid response other than RFC specifications was received from the POP3 server.

Only the first row of response is output for the response received from the server. However, if no response exists, an empty string is displayed.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.2 For the POP3-related messages.

Action

Take actions according to the log and trace information.

KDJE59113-E

An argument of a response received from the POP3 server has an invalid format. (communication processing = aa....aa, response = bb....bb)

aa....aa: Character string indicating communication processing

bb....bb: Response from server

Description

An argument of a response received from the POP3 server has an invalid format.

Only the first row of response is output for the response received from the server. However, for the response from mail receiving commands (TOP, RETR), only the response code is output.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.2 For the POP3-related messages.

Action

Take actions according to the log and trace information.

KDJE59114-E

An argument of a response received from the SMTP server has an invalid format. (communication processing = aa....aa, response = bb....bb)

aa....aa: String indicating communication processing

bb....bb: Response passed from server

Description

An argument of response received from the SMTP server has an invalid format.

Only the first row of response is output for the response received from the server. However, for the response of completion of sending data (\r\n.) for the mail, only the response code is output.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.1 For the SMTP and SMTPS related messages.

Action

Take actions according to the log and trace information.

KDJE59200-E

An error occurred in the aa....aa phase, during processing of the EL expression bb....bb for the attribute cc....cc. (detail = dd....dd)

aa....aa: Phase ID

bb....bb: EL expression (Expression Langage)

cc....cc: beforePhase or afterPhase

dd....dd: Exception information

Description

An error occurred due to the beforePhase attribute or afterPhase attribute of the <f:view> tag in the JSP file or Facelets file.

Action

Review, and if necessary revise, the EL expression set in the beforePhase attribute or afterPhase attribute of the <f:view> tag in the JSP file or Facelets file. Also, review, and if necessary revise, the implementation of the methods referenced by the EL expression.

See the exception information and then take action.

KDJE59201-E

An error occurred when actionListener aa....aa was invoked for the component bb....bb. (detail = cc....cc)

aa....aa: EL expression (Expression Langage)

bb....bb: Component ID

cc....cc: Exception information

Description

An error occurred due to the actionListener attribute of the <f:commandButton> tag or <f:commandLink> tag in the JSP file or Facelets file.

Action

Review, and if necessary revise, the EL expression set in the actionListener attribute of the <f:commandButton> tag or <f:commandLink> tag in the JSP file or Facelets file. Also, review, and if necessary revise, the implementation of the methods referenced by the EL expression.

See the exception information and then take action.

KDJE59202-E

An error occurred during beforePhase() processing of the aa....aa phase for UIComponent-ClientId=bb....bb. (detail = cc....cc)

aa....aa: Phase ID

bb....bb: Client ID

cc....cc: Exception information

Description

An error occurred during the processing of the beforePhase method of the PhaseListener class specified in the Faces configuration file.

Action

Review, and if necessary revise, the implementation of the beforePhase method of the PhaseListener class specified in the Faces configuration file.

See the exception information and then take action.

KDJE59203-E

An error occurred during afterPhase() processing of the aa....aa phase for UIComponent-ClientId=bb....bb. (detail = cc....cc)

aa....aa: Phase ID

bb....bb: Client ID

cc....cc: Exception information

Description

An error occurred during the processing of the afterPhase method of the user-defined PhaseListener class specified in the Faces configuration file.

Action

Review, and if necessary revise, the implementation of the afterPhase method of the PhaseListener class specified in the Faces configuration file.

See the exception information and then take action.

KDJE59204-E

An error occurred during processing of the aa....aa phase for UIComponent-ClientId=bb....bb. (detail = cc....cc)

aa....aa: Phase ID

bb....bb: Client ID

cc....cc: Exception information

Description

An error occurred due to the following tag attributes in the JSP file or Facelets file:

The actionListener attribute of the <f:commandButton> tag and <f:commandLink> tag
The valueChangeListener attribute of the <h:inputHidden> tag, <inputSecret> tag, <h:inputText> tag, <h:inputTextarea> tag, <h:selectBooleanCheckbox> tag, <h:selectManyCheckbox> tag, <h:selectManyListbox> tag, <h:selectManyMenu> tag, <h:selectOneListbox> tag, <h:selectOneMenu> tag, and <h:selectOneRadio> tag
The type attribute of the <f:actionListener> tag, <f:valueChangeListener> tag, and <f:phaseListener> tag
The value or type attributes of the <f:setPropertyActionListener> tag

Action

Review, and if necessary revise, the settings specified in the JSP file or Facelets file as follows:

Review, and if necessary revise, the EL expression set in the actionListener attribute. Also, review, and if necessary revise, the implementation of the methods referenced by the EL expression.
Review, and if necessary revise, the EL expression set in the valueChangeListener attribute. Also, review, and if necessary revise, the implementation of the methods referenced by the EL expression.
Review, and if necessary revise, the type attribute of the <f:actionListener> tag, <f:valueChangeListener> tag, or <f:phaseListener> tag.
Review, and if necessary revise, the EL expression set in the value or target attributes of the <f:setPropertyActionListener> tag.

See the exception information and then action.

KDJE59205-E

An error occurred when phaseListener was invoked. (detail = aa....aa)

aa....aa: Exception information

Description

An error occurred in a method of the PhaseListener class set in the <f:phaseListener> tag of the JSP file or Facelets file.

Action

Review, and if necessary revise, the implementation of the method of the PhaseListener class set in the <f:phaseListener> tag of the JSP file or Facelets file.

See the exception information and then take action.

KDJE59206-E

An error occurred during processing of the deployment descriptor for the context aa....aa. (detail = bb....bb)

aa....aa: Context root name

bb....bb: Exception information

Description

An error occurred while the web.xml file was being parsed.

Action

Review, and if necessary revise, the web.xml file settings.

See the exception information and then take action.

KDJE59207-E

An error occurred during processing of the action expression aa....aa for the component bb....bb. (detail = cc....cc)

aa....aa: EL expression (Expression Langage)

bb....bb: Client ID

cc....cc: Exception information

Description

An error occurred due to the action attribute of the <h:commandButton> tag or <h:commandLink> tag in the JSP file or Facelets file.

Action

Review, and if necessary revise, the EL expression set in the action attribute of the <h:commandButton> tag and <h:commandLink> tag in the JSP file or Facelets file. Also, review, and if necessary revise, the implementation of the methods referenced by the EL expression.

See the exception information and then take action.

KDJE59208-I

Initialization of the JSF application finished successfully. (context name = aa....aa)

aa....aa: Context root name

Description: The JSF application was initialized successfully.

KDJE59209-E

An error occurred during initialization of the JSF application. (context name = aa....aa, detail = bb....bb)

aa....aa: Context root name

bb....bb: Exception information

Description: An error occurred during the initialization of the JSF application.
Action: See the exception information and then take action.

KDJE59210-E

An error occurred during termination of the JSF application. (context name = aa....aa, detail = bb....bb)

aa....aa: Context root name

bb....bb: Exception information

Description: An error occurred during the termination of the JSF application.
Action: See the exception information and then take action.

KDJE59211-E

An error occurred during decoding of the flash data from an incoming cookie. Processing will continue, but the flash is unavailable for this request. (detail = aa....aa)

aa....aa: Exception information

Description: An error occurred while reading the Cookie for the Flash object data.
Action: See the exception information and then take action.

KDJE59212-E

An error occurred during rendering of the response for the component aa....aa. (detail = bb....bb)

aa....aa: Client ID

bb....bb: Exception information

Description: An error occurred while a response was being written to the client during Ajax communication.
Action: See the exception information and then take action.

KDJE59213-E

An error occurred during updating of the model phase for the component aa....aa. (detail = bb....bb)

aa....aa: Client ID

bb....bb: Exception information

Description: An error occurred when the value input by the user was being set in the ManagedBean.
Action: See the exception information and then take action.

KDJE59214-E

An error occurred during PreDestroy processing for the ManagedBean aa....aa. (detail = bb....bb)

aa....aa: ManagedBean name

bb....bb: Exception information

Description

An error occurred during the processing of the PreDestroy method of the ManagedBean.

Action

Review, and if necessary revise, the signature or implementation of the PreDestroy method of the ManagedBean.

See the exception information and then take action.

KDJE59215-I

Termination of the JSF application finished successfully. Context name = aa....aa

aa....aa: Context root name

Description: The JSF application was terminated successfully.

KDJE59216-W

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

aa....aa: Parameter name

bb....bb: Parameter value

cc....cc: Default value

Description: The value specified in the context parameter is invalid. The default value will be set up.
Action: Specify the correct value in the context parameter.

KDJE59217-W

The specified parameter value is invalid. This parameter setting will be ignored because a default value does not exist. (aa....aa = bb....bb)

aa....aa: Parameter name

bb....bb: Parameter value

Description: The value specified in the context parameter is invalid. The settings for this context parameter will be ignored.
Action: Specify the correct value in the context parameter.

KDJE59218-W

An empty string value is set for the parameter aa....aa. The default value will be used. (default value = bb....bb)

aa....aa: Parameter name

bb....bb: Default value

Description: The value set in the context parameter is a null character. The default value will be set up.
Action: Specify the correct value in the context parameter.

KDJE59219-W

An empty string value is set for the parameter aa....aa. This parameter setting will be ignored because a default value does not exist.

aa....aa: Parameter name

Description: The value specified in the context parameter is invalid. The settings for this context parameter will be ignored.
Action: Specify the correct value in the context parameter.

KDJE59220-W

The specified JNDI parameter value is invalid. The default value will be used. (aa....aa = bb....bb, default value = cc....cc)

aa....aa: Parameter name

bb....bb: Parameter value

cc....cc: Default value

Description: The value specified in the context parameter using JNDI is invalid. The default value will be set up.
Action: Specify the correct value in the context parameter.

KDJE59221-W

An empty string value is set for the JNDI parameter aa....aa. The default value will be used. (default value = bb....bb)

aa....aa: Parameter name

bb....bb: Default value

Description: The value specified in the context parameter using JNDI is a null character.The default value will be set up.
Action: Specify the correct value in the context parameter.

KDJE59222-W

The specified resource was not found. The resource will be ignored. (aa....aa = bb....bb)

aa....aa: Parameter name

bb....bb: Default value

Description: The specified config file name does not exist in javax.faces.CONFIG_FILES or javax.faces.FACELETS_LIBRARIES of the context parameter. The settings for this context parameter will be ignored.
Action: Specify the correct value in the context parameter.

KDJE59223-W

An invalid aa....aa is set for the parameter. (bb....bb = cc....cc)

aa....aa: Set value type

bb....bb: Parameter name

cc....cc: Parameter value

Description: The value specified in the context parameter is invalid.
Action: Specify the correct value in the context parameter.

KDJE59224-W

The specified parameter value is invalid. aa....aa will be used as the value. (bb....bb = cc....cc)

aa....aa: Value set for the parameter

bb....bb: Parameter name

cc....cc: Parameter value

Description: The value specified in the context parameter is invalid. aa....aa will be used as the value.
Action: Specify the correct value in the context parameter.

KDJE59225-W

An empty string value is set for the parameter aa....aa. bb....bb will be used as the value.

aa....aa: Parameter name

bb....bb: Value set for the parameter

Description: The value specified in the context parameter is a null character. aa....aa will be used as the value.
Action: Specify the correct value in the context parameter.

KDJE59226-W

The specified delimiter is invalid. The first character of the specified value aa....aa will be used as the delimiter. (bb....bb = cc....cc)

aa....aa: First character of the parameter value

bb....bb: Parameter name

cc....cc: Parameter value

Description: The value specified in the context parameter is invalid. aa....aa will be used as the value.
Action: Specify the correct value in the context parameter.

KDJE59227-I

A Facelets file was modified. (file name = aa....aa)

aa....aa: Changed Facelets file name

Description: A Facelets file of the JSF application has been modified.

KDJE59300-I

Application verification started. The beans.xml file will now be searched for in the application aa....aa.

aa....aa: Application name

Description: The verification of the application started. The beans.xml file will be searched in the application aa....aa.

KDJE59301-I

Verification completed. The beans.xml file was found in the module aa....aa of the application bb....bb.

aa....aa: Module name

bb....bb: Application name

Description: The verification is complete. The beans.xml file was found in the module aa....aa of the application bb....bb.

KDJE59302-I

Verification completed. The beans.xml file was not found in the application aa....aa.

aa....aa: Application name

Description: The verification is complete. The beans.xml file was not found in the application aa....aa.

KDJE59303-I

Pre-deployment processing started for the module bb....bb in the CDI application aa....aa.

aa....aa: Application name

bb....bb: Module name

Description: The pre-deployment processing started for the module bb....bb in the CDI application aa....aa.

KDJE59304-I

Pre-deployment processing ended for the module bb....bb in the CDI application aa....aa.

aa....aa: Application name

bb....bb: Module name

Description: The pre-deployment processing ended for the module bb....bb in the CDI application aa....aa.

KDJE59305-I

The CDI application is now being deployed. The application name is aa....aa.

aa....aa: Application name

Description: The CDI application is being deployed. The application name is aa....aa.

KDJE59306-I

The CDI application aa....aa was successfully deployed.

aa....aa: Application name

Description: The CDI application aa....aa was successfully deployed.

KDJE59307-I

The CDI application is now starting. The application name is aa....aa.

aa....aa: Application name

Description: The CDI application is starting. The application name is aa....aa.

KDJE59308-I

The CDI application aa....aa was successfully started.

aa....aa: Application name

Description: The CDI application aa....aa was successfully started.

KDJE59309-I

The CDI application is now stopping. The application name is aa....aa.

aa....aa: Application name

Description: The CDI application is stopping. The application name is aa....aa.

KDJE59310-I

The CDI application aa....aa was successfully stopped.

aa....aa: Application name

Description: The CDI application aa....aa was successfully stopped.

KDJE59311-E

An exception occurred while verifying the CDI application. (details = aa....aa).

aa....aa: Exception details

Description

An exception occurred while verifying the CDI application.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59312-E

An exception occurred during pre-deployment processing of the CDI application. (details = aa....aa)

aa....aa: Exception details

Description

An exception occurred during the pre-deployment processing of the CDI application.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59313-E

An exception occurred while deploying the CDI application. (details = aa....aa)

aa....aa: Exception details

Description

An exception occurred while deploying the CDI application.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59314-E

An exception occurred while starting the CDI application. (details = aa....aa)

aa....aa: Exception details

Description

An exception occurred while starting the CDI application.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59315-E

An exception occurred while stopping the CDI application. (details = aa....aa)

aa....aa: Exception details

Description

An exception occurred while stopping the CDI application.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59316-E

Acquisition of an EJB reference failed. (EJB name = aa....aa, JNDI name = bb....bb, details = cc....cc)

aa....aa: Class name

bb....bb: JNDI name

cc....cc: Exception details

Description: An attempt to acquire an EJB reference failed.
Action: An EJB cannot be injected using a CDI annotation. Check the application, and modify the settings so that an EJB is not injected using a CDI annotation.

KDJE59317-E

The JNDI name required to acquire an EJB reference could not be acquired. (EJB name = aa....aa)

aa....aa: Class name

Description: The JNDI name required to acquire an EJB reference could not be acquired.
Action: An EJB cannot be injected using a CDI annotation. Check the application, and modify the settings so that an EJB is not injected using a CDI annotation.

KDJE59319-E

The transaction status cannot be acquired. (details = aa....aa)

aa....aa: Exception details

Description

The transaction status cannot be acquired.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59320-E

An instance of the aa....aa class cannot be instantiated via the no-argument constructor. (details = bb....bb)

aa....aa: Class name

bb....bb: Exception details

Description

The aa....aa class cannot be instantiated using the no-argument constructor.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59321-E

The aa....aa class constructor contains an invalid argument. (details = bb....bb)

aa....aa: Class name

bb....bb: Exception details

Description

The argument of the aa....aa class constructor is invalid.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59322-E

An internal status is invalid.

Description

An internal status is invalid.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59323-E

The BeanManager interface cannot be resolved. (details = aa....aa)

aa....aa: Exception details

Description

The BeanManager interface cannot be resolved.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59325-E

The aa....aa class cannot be loaded. (details = bb....bb)

aa....aa: Class name

bb....bb: Exception details

Description

The aa....aa class cannot be loaded.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59326-E

A class was not found while loading the local business interface aa....aa. (details = bb....bb)

aa....aa: Name

bb....bb: Exception details

Description: A class was not found while loading the local business interface aa....aa.
Action: An EJB cannot be injected using a CDI annotation. Check the application, and modify the settings so that an EJB is not injected using a CDI annotation.

KDJE59328-E

The remove method in the EJB aa....aa class cannot be resolved.

aa....aa: Class name

Description: The remove method in the EJB aa....aa class cannot be resolved.
Action: An EJB cannot be injected using a CDI annotation. Check the application, and modify the settings so that an EJB is not injected using a CDI annotation.

KDJE59329-E

A class was not found while loading the remote business interface aa....aa. (details = bb....bb)

aa....aa: Class name

bb....bb: Exception details

Description: A class was not found while loading the remote business interface aa....aa.
Action: An EJB cannot be injected using a CDI annotation. Check the application, and modify the settings so that an EJB is not injected using a CDI annotation.