7.2 Messages from KDJE30000 to KDJE39999 : Messages

KDJE30000-E

The context-root (aa....aa) has already been used by other application (bb....bb).

aa....aa: Context root name

bb....bb: Application name

Description

Another application (bb....bb) is already using this context root (aa....aa).

Deployment will be interrupted and RemoteException will be thrown.

Action

Specify another context root, and then redeploy the application.

KDJE30003-W

Could not delete directories(aa....aa), so you must remove it manually before deploying other web-application.

aa....aa: Directory name

Description

The directory cannot be deleted. The directory might either be in use or the permission to delete the directory might not be available.

Furthermore, this message might be output even when all of the following conditions are fulfilled:

When Windows is used as the operating system.
When the openStream method of the java.net.URL class is executed in the servlet of the J2EE application.

Because the openStream method is executed when Struts is used, the message will be output in accordance with the conditions.

Action

When an attempt to delete a file in the directory fails, the file name is output in the message KDJE30070-E output in the J2EE server. Either start the application after restarting the J2EE server or delete the file and directory manually. When deleting manually, perform the action before creating another Web application.

KDJE30004-E

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

aa....aa: WAR file name

bb....bb: Servlet or JSP name

Description

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

The process of importing will be interrupted.

Action

Check the WAR file, and then change the contents of the <servlet-name> tag.

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

KDJE30005-E

The archive files(aa....aa, bb....bb) have more than one display name with the same name "cc....cc".

aa....aa: Archive file name

bb....bb: Archive file name

cc....cc: Display name

Description

The archive files (aa....aa and bb....bb) have the same display name (cc....cc).

The process of importing will be interrupted.

Action

Check the archive file included in the EAR, and then change the contents of the <display-name> tag.

KDJE30006-E

The EJB JAR files (aa....aa) have more than one bean with the same name "bb....bb".

aa....aa: EJB-JAR file name

bb....bb: Enterprise Bean name

Description

The EJB-JAR files (aa....aa) have more than one bean with the same Bean name (bb....bb).

The process of importing will be interrupted.

Action

Check the EJB-JAR file included in the EAR, and then change the contents of the <ejb-name> tag.

KDJE30007-E

An EJB DD (aa....aa) has more than one bean with the same name "bb....bb".

aa....aa: Name of EJB-JAR DD

bb....bb: Enterprise Bean name

Description

An EJB-JAR DD (aa....aa) has more than one bean with the same Bean name (bb....bb).

The process of importing will be interrupted.

Action

Check the EJB-JAR file, and then change the contents of the <ejb-name> tag.

KDJE30008-E

A WAR DD(aa....aa) has more than one servlet/JSP with the same name "bb....bb".

aa....aa: WAR DD name

bb....bb: Servlet or JSP name

Description

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

The process of importing will be interrupted.

Action

Check the WAR file, and then change the contents of the <servlet-name> tag.

KDJE30010-E

An error has occurred while initializing of the extended container. Class name = aa....aa, Detailed message = bb....bb

aa....aa: Class name

bb....bb: Detailed message

Description

An error occurred during the server start hook processing.

The J2EE server or the Web container server will terminate after the execution of the server stop hook processing.

Action

Based on the detailed message, revise the classes of the server start hook processing.

KDJE30011-E

An error has occurred during terminating of the extended container. Class name = aa....aa, Detailed message = bb....bb

aa....aa: Class name

bb....bb: Detailed message

Description

An error occurred during the server stop hook processing.

The J2EE server or the Web container server will terminate.

Action

Based on the detailed message, revise the classes of the server stop hook processing.

KDJE30012-E

The class file specified in the property key ejbserver.application.InitTermProcessClasses was not found. Class name = aa....aa

aa....aa: Class name

Description: The class (aa....aa) specified in the key ejbserver.application.InitTermProcessClasses was not found.
Action: Reset the class name of the key ejbserver.application.InitTermProcessClasses.

KDJE30013-E

The class specified in the property key ejbserver.application.InitTermProcessClasses must not belong to a package starting with com.hitachi.software.ejb. Class name = aa....aa

aa....aa: Class name

Description: The class (aa....aa) specified in the key ejbserver.application.InitTermProcessClasses must not belong to a package starting with com.hitachi.software.ejb.
Action: Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30014-E

The class specified in the property key ejbserver.application.InitTermProcessClasses does not implement com.hitachi.software.ejb.application.InitTermProcess. Class name = aa....aa

aa....aa: Class name

Description: The class (aa....aa) specified in the key ejbserver.application.InitTermProcessClasses does not implement com.hitachi.software.ejb.application.InitTermProcess.
Action: Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30015-E

The interface must not be specified in the property key ejbserver.application.InitTermProcessClasses. Class name = aa....aa

aa....aa: Class name

Description: The interface cannot be specified in the key ejbserver.application.InitTermProcessClasses.
Action: Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30016-E

An abstract class must not be specified in the property key ejbserver.application.InitTermProcessClasses. Class name = aa....aa

aa....aa: Class name

Description: An abstract class cannot be specified in the key ejbserver.application.InitTermProcessClasses.
Action: Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30017-E

The class specified in the property key ejbserver.application.InitTermProcessClasses must be public. Class name = aa....aa

aa....aa: Class name

Description: The class (aa....aa) specified in the key ejbserver.application.InitTermProcessClasses must be public.
Action: Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30018-E

The primitive type must not be specified in the property key ejbserver.application.InitTermProcessClasses. Primitive type name = aa....aa

aa....aa: Primitive type name

Description: The primitive type (aa....aa) cannot be specified in the key ejbserver.application.InitTermProcessClasses.
Action: Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30019-E

The default constructor of the class specified in the property key ejbserver.application.InitTermProcessClasses cannot be accessed. Class name = aa....aa

aa....aa: Class name

Description: The default constructor of the class (aa....aa) specified in the key ejbserver.application.InitTermProcessClasses cannot be accessed.
Action: Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30020-I

The initialization of the extended container finished successfully. Class name = aa....aa

aa....aa: Class name

Description: This message indicates that the server start hook processing was executed successfully.

KDJE30021-I

The termination of the extended container finished successfully. Class name = aa....aa

aa....aa: Class name

Description: This message indicates that the server stop hook processing was executed successfully.

KDJE30022-I

aa....aa

aa....aa: Java VM version

Description

This message indicates the version (aa....aa) of Java VM.

This message is output to cjstdout.log of the J2EE server. If, however, the invocation of the J2EE server fails, the message is not output.

KDJE30024-W

Invalid property value. Property = aa....aa

aa....aa: Property name

Description: The property value is invalid.
Action: Reset the property value.

KDJE30025-W

The specified class does not implement the interface com.cosminexus.mngsvr.hmx.agent.InstrumentationAgent. Class name = aa....aa

aa....aa: Class name

Description: The specified class (aa....aa) does not implement the interface com.cosminexus.mngsvr.hmx.agent.InstrumentationAgent.
Action: Implement InstrumentationAgent in the set Agent class.

KDJE30026-W

The defined Agent class cannot be instantiated. Class name = aa....aa, Reason = bb....bb

aa....aa: Class name

bb....bb: Reason

Description: The defined Agent class (aa....aa) cannot be instantiated.
Action: Make sure that the Cosminexus Component Container is installed properly.

KDJE30027-W

The Agent cannot be started. Class name = aa....aa, Reason = bb....bb

aa....aa: Class name

bb....bb: Reason

Description: The Agent cannot be started.
Action: Check the start method of the defined Agent class.

KDJE30028-I

The J2EE server has started. Server name = aa....aa

aa....aa: Server name

Description: The J2EE server (aa....aa) has started.

KDJE30030-E

The server shutdown is in progress.

Description: The server shutdown is in progress.
Action: The cjstopsv command has already been executed, and shutdown is in progress. Wait until the J2EE server stops.

KDJE30031-I

The J2EE server shutdown is in progress. Server name = aa....aa

aa....aa: Server name

Description: The J2EE server (aa....aa) shutdown is in progress.

KDJE30033-W

Statement closes instead. Info=aa....aa

aa....aa: Statement object

Description

An unclosed Statement object exists while the connection is being closed.

The Statement object (aa....aa) is closed when the connection is closed.

Action

Revise the settings so that the Statement object is explicitly closed.

KDJE30034-I

The J2EE server shut down. Server name = aa....aa

aa....aa: The J2EE server name

Description: The J2EE server (aa....aa) has shut down.

KDJE30040-I

The J2EE server will now start. Server name = aa....aa, Version = bb....bb, J2EE server mode = cc....cc, PID = dd....dd

aa....aa: Server name

bb....bb: Version of Cosminexus Component Container

cc....cc: Value specified in the key ejbserver.server.j2ee.feature of the user property file of the J2EE server (default value is 1.4)

dd....dd: Process ID

Description: The J2EE server (aa....aa) is starting.

KDJE30041-E

The property file aa....aa cannot be accessed.

aa....aa: Name of the property file that cannot be accessed

Description

An attempt to read the property file (aa....aa) failed.

The possible causes might be as follows:

The property file cannot be accessed.
The property file format does not conform to Java specifications.

For example, when the property file contains an invalid Unicode escape sequence (the string after " [Figure] u" is not an appropriate Unicode 16 hexadecimal value).

Action

Check whether the property file exists and check the access permissions.

If the property file can be accessed, make sure that the property file format conforms to the Java specifications.

KDJE30042-E

Invalid property value. Property = aa....aa

aa....aa: Property name

Description: Either an invalid property value is specified or the property is not set. The J2EE server will terminate.
Action: Reset the property.

KDJE30043-E

An unexpected exception has occurred. Detail = aa....aa

aa....aa: Details

Description: An unexpected exception occurred.
Action: Acquire the maintenance information, and then contact maintenance personnel.

KDJE30044-E

Access from aa....aa is not permitted. Server name = bb....bb

aa....aa: IP address

bb....bb: Server name

Description: Access from aa....aa is not permitted.
Action: Revise the IP address or the host name specified in the key webserver.connector.http.permitted.hosts of the user property file (usrconf.properties) of the connected the J2EE server.

KDJE30045-E

The version of the command does not match the version of the J2EE server. Server name = aa....aa, Reason code = (bb....bb, cc....cc)

aa....aa: Server name

bb....bb: Maintenance information 1

cc....cc: Maintenance information 2

Description: The version of the command does not match the version of the J2EE server.
Action: Confirm that the version of the Cosminexus Component Container of the environment in which the command is executed matches with the version of the Cosminexus Component Container of the environment in which the J2EE server is running. If the problem cannot be solved, acquire the maintenance information, and then contact maintenance personnel.

KDJE30046-E

An unexpected exception occurred. Details = aa....aa, Server name = bb....bb

aa....aa: Details

bb....bb: Server name

Description: An unexpected exception occurred.
Action: Acquire the maintenance information, and then contact maintenance personnel.

KDJE30047-E

Startup processing for the J2EE server has not yet completed. Server name = aa....aa

aa....aa: Server name

Description: The startup processing for the J2EE server has not yet completed.
Action: After the startup processing for the J2EE server finishes, re-execute the command.

KDJE30048-E

The J2EE server shutdown is in progress. Server name = aa....aa

aa....aa: Server name

Description: The J2EE server shutdown is in progress.
Action: The J2EE server shutdown is in process. After the J2EE server stops, restart it.

KDJE30050-E

The J2EE server aborted. Server name = aa....aa

aa....aa: Server name

Description

The J2EE server has aborted.

Action

See the J2EE server log, and then take action depending on the contents of the message output immediately before the server aborted.

For details on how to extract materials and investigate the cause, see 6.4.2 Troubleshooting during operations in the uCosminexus Application Server Maintenance and Migration Guide.

KDJE30051-W

The specified value is invalid. The default value aa....aa will be used. Property key = bb....bb

aa....aa: Default value

bb....bb: Property key name

Description: The default value aa....aa will be used, since the specified value is invalid.
Action: Revise the value specified in the property key bb....bb.

KDJE30052-E

The public directory is invalid (version=aa....aa, productId=bb....bb, edition=cc....cc)

aa....aa: Version

bb....bb: Model name

cc....cc: Edition

Description

The work directory is invalid. The specified work directory cannot be used with this version, platform, and edition.
If an attempt to start Java VM fails due to the specification of an invalid option definition file for the J2EE server during initial startup of the J2EE server, attempts to start the J2EE server thereafter will fail.

Action

Delete the J2EE server and then reset the J2EE server. For details on how to delete a J2EE server, see 3.2.9 Deleting unwanted J2EE servers in the uCosminexus Application Server System Setup and Operation Guide.

KDJE30060-I

The RMI registry has started. (host name = aa....aa, port = bb....bb)

aa....aa: Set value of the property ejbserver.rmi.naming.host. Local host name, when the property ejbserver.rmi.naming.host is not specified.

bb....bb: RMI port number

Description: The RMI registry was started with host name (aa....aa) and port number (bb....bb).

KDJE30061-E

An attempt to start the RMI registry has failed. (property name = aa....aa, host name = bb....bb, port = cc....cc, details = dd....dd)

aa....aa: Property name

bb....bb: Host name (local host name, when ejbserver.rmi.naming.host is not specified)

cc....cc: RMI port number

dd....dd: Details

Description

An attempt to generate the RMI registry has failed.

Action

If the details (dd....dd) indicate an invalid host name, revise the set value of the property (aa....aa).

If the details (dd....dd) indicate that the port is in use elsewhere, revise the set value of the property (aa....aa).

In the case of details other than those given above, contact maintenance personnel.

KDJE30065-E

aa....aa failed to be bb....bb. (MBean server name = cc....cc, details = dd....dd)

aa....aa: Target name (MBeanserver or JMXConnector)

bb....bb: Operation name (created, removed, started, or stopped)

cc....cc: MBean server name

dd....dd: Details

Description: aa....aa failed to be bb....bb. (MBean server name = cc....cc, details = dd....dd)
Action: The format of the character string might be incorrect in the host name. In the host name, if the format of the character string is not as per the format ruled in RFC 2609, change the host name. If the host name is correct, contact maintenance personnel.

KDJE30066-E

Information needed for XA transaction recovery cannot be obtained.

Description

The information required for recovering a XA transaction cannot be obtained.

The startup of the J2EE server will be interrupted.

Action

Action for the transaction: Check if any residual transactions are found in resources associated with the system. Check the information of resources associated with the system, and if any residual transactions are found, manually perform commit or rollback to secure consistency between each linked resource and transaction.
Action for the J2EE server: Re-setup the J2EE server.

KDJE30070-E

Could not delete a file(aa....aa).

aa....aa: File name

Description: The file cannot be deleted. The file might either be in use or the permission to delete the file might not be available.
Action: Execute the action described in the message KDJE30003-W that is output immediately after this message.

KDJE30200-I

The server migration is in progress. Server name = aa....aa

aa....aa: Server name

Description: The server (aa....aa) environment migration is in progress.

KDJE30201-I

No server needs to be migrated.

Description: A server that needs to be migrated using the command cjenvupdate does not exist.

KDJE30202-E

The Deployment Descriptor cannot be converted. File = aa....aa, Reason = bb....bb

aa....aa: DD name

bb....bb: Reason for failure

Description

The DD (aa....aa) format is invalid, and the DD of a new environment format cannot be converted.

Action

Take action as per the execution format of the command cjenvupdate.

In the case of normal migration

Modify the DD based on the reason for failure, and then re-execute the command cjenvupdate. For the messages in which the reason for failure starts with nnnn (n is a number), see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory.

If modification cannot be done, contact maintenance personnel.

In the case of forced migration

The application or the resource containing this DD is not migrated to the new environment.

If you want to use such applications or resources in a new environment, you need to re-import the resources, and then re-create the applications.

KDJE30203-I

Usage: cjenvupdate [-f]

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

KDJE30204-I

The server checking is in progress. Server name = aa....aa

aa....aa: Server name

Description: Check is in progress to see if the DD present in the server (aa....aa) can be converted to a format used in the new version.

KDJE30205-E

The server will not be migrated because a problem occurred in the Deployment Descriptor. Server name = aa....aa

aa....aa: Server name

Description: The server (aa....aa) will not be migrated because of the presence of a DD that cannot be converted to the new environment format.
Action: Modify the DD according to the action given in KDJE30202-E, and then re-execute the cjenvupdate command.

KDJE30206-I

No problem exists in the Deployment Descriptors in the server. Server name = aa....aa

aa....aa: Server name

Description: Server migration will continue since all the server (aa....aa) DDs can be converted to the new environment format.

KDJE30207-W

The Resource Descriptor cannot be converted. File = aa....aa, Reason = bb....bb

aa....aa: DD name

bb....bb: Reason for failure

Description

The resource DD (aa....aa) cannot be converted.

Check all DDs of the server, and if the messages KDJE30202-E or KDJE37022-E are not output apart from this message, the server is forced to migrate.

Action

If KDJE30202-E or KDJE37022-E is output while the DDs of the same server are being checked, take action given in each message, and then re-execute the cjenvupdate command. For details on how to take action, follow the description in Action of each message.

KDJE30208-W

The server will be migrated because a problem occurred only in the Resource Descriptor and the reference resolution of the application definition. Server name = aa....aa

aa....aa: Server name

Description

Forced migration of the environment will continue because a problem occurred only in the resource DD and the reference resolution of the application definition.

The resource containing a DD that cannot be converted, is not migrated. The deployment of the application that specifies an erroneous resource in reference resolution will fail. Reset the resource and application when using them after environment migration.

Action

If you want to use a resource that was not migrated, import the resource again after migration. If a problem exists in the reference resolution of an application, the application cannot be deployed. Use an appropriate resource to perform reference resolution.

KDJE30209-E

An unexpected exception has occurred. Server name = aa....aa

aa....aa: Server name

Description

An unexpected exception occurred.

The server (aa....aa) is not migrated.

Action

Contact maintenance personnel.

KDJE30220-I

Migration of the definition files of the old version is in progress.

Description: Migration of the definition files of the old version is in progress.

KDJE30221-I

The definition files of the old version have been migrated successfully.

Description: The definition files of the old version have been migrated successfully.

KDJE30222-W

The definition files of the old version have been migrated with errors. Some definition files could not be migrated.

Description

An attempt to migrate some definition files has failed.

If the definition file that cannot be migrated is usrconf.cfg of the J2EE server, it remains as the definition file of the old version and is not migrated. Other definition files are replaced with the default definition file of this version.

Action

The information of the definition file that cannot be migrated is output in either KDJE30225-W or KDJE30226-W, before this message is output. Take action as per the respective messages.

KDJE30223-E

An unexpected exception has occurred.

Description: An unexpected exception occurred.
Action: Contact maintenance personnel.

KDJE30224-E

The attempt to migrate the definition files of the old version has failed. File = aa....aa, Reason = bb....bb

aa....aa: File that cannot be migrated

bb....bb: Reason for migration failure

Description

An attempt to migrate the definition files of the old version has failed.

The definition migration processing will be interrupted.

Action

Take action on the basis of the reason for migration failure (bb....bb). If the factors cannot be identified from the reason, contact maintenance personnel.

KDJE30225-W

The default definition files will be used because the attempt to migrate the definition files of the old version failed. File = aa....aa, Backup = bb....bb

aa....aa: File that cannot be migrated

bb....bb: Backup file of this file

Description

The definition files of the old version cannot be migrated.

The definition files that cannot be migrated will be replaced with the default definition file of this version.

Action

When using a definition file of the old version, migrate the definitions manually based on the backup of the old definition file, indicated by bb....bb.

KDJE30226-W

A problem occurred during migration of the definition file. The definition file will not be migrated. File = aa....aa

aa....aa: File that cannot be migrated

Description

An attempt to migrate the definition files of the old version has failed.

The definition file that has failed to migrate will not be migrated, and the definition file of the old version will be used as is.

Action

When using the definitions for the new environment, set the definition file manually.

KDJE30230-W

The deletion of the file has failed. File = aa....aa

aa....aa: File that cannot be deleted

Description

The deletion of the file has failed.

Take action based on the following causes:

File deletion permission is not available.
The disk device has failed due to reasons, such as disk not working.

Action

Take action based on the following causes:

When file deletion permission is not available: A user who has the correct permissions must delete the file.
When the disk device is not working: Contact the system administrator, and then replace the device.

If the above-mentioned factors are not applicable, contact maintenance personnel.

KDJE30231-W

The deletion of the directory has failed. Directory = aa....aa

aa....aa: Directory that cannot be deleted

Description

An attempt to delete the directory has failed.

Take action based on the following causes:

Directory deletion permission is not available.
The disk device has failed due to reasons, such as disk not working.

Action

Take action depending on the cause.

When directory deletion permission is not available: A user who has the correct permissions must delete the file.
When the disk device is not working: Contact the system administrator, and then replace the device.

If the above-mentioned factors are not applicable, contact maintenance personnel.

KDJE30232-W

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

aa....aa: Copy source file name

bb....bb: Copy destination file name

cc....cc: Details

Description

An attempt to copy the file has failed.

Take action based on the following causes:

The available disk space is insufficient.
The disk device has failed due to reasons, such as disk not working.

Action

Take action depending on the cause.

When the available disk space is insufficient: Delete the unnecessary files to increase the available space at the output destination or change to an output destination with available space.
When the disk device is not working: Contact the system administrator, and then replace the device.

If the above-mentioned factors are not applicable, contact maintenance personnel.

KDJE30233-E

The creation of the file has failed. File name = aa....aa

aa....aa: File name

Description

An attempt to create a file has failed.

Take action based on the following causes:

The available disk space is insufficient.
The disk device has failed due to reasons, such as disk not working.
A file under CC is being accessed.

Action

Take action depending on the cause.

When the available disk space is insufficient

Delete the unnecessary files to increase the available space at the output destination or change to an output destination with available space.

When the disk device is not working

Contact the system administrator, and then replace the device.

When a file under CC is being accessed

Check the output file name, and then take one of the following actions:

If the file name is cjupdate.properties:

Make sure that cjupdate.properties.tmp is not being accessed. Then rename the cjupdate.properties.tmp file as cjupdate.properties, and then re-execute the cjenvupdate command.
If the file name is cjupdate.migratefiles.properties:

Make sure that cjupdate.migratefiles.properties.tmp is not being accessed. Then rename the cjupdate.migratefiles.properties.tmp file as cjupdate.migratefiles.properties, and then re-execute the cjenvupdate command.
If the file name is usrconf.properties.envupdate_bak:

Make sure that usrconf.properties is not being accessed, and then re-execute the cjenvupdate command.
If the file name is server.policy.envupdate_bak:

Make sure that server.policy is not being accessed, and then re-execute the cjenvupdate command.
If the file name is web.policy.envupdate_bak:

Make sure that web.policy is not being accessed, and then re-execute the cjenvupdate command.
If the file name is usrconf.properties:

Make sure that usrconf.properties.envupdate_bak is not being accessed. Then rename the usrconf.properties.envupdate_bak file as usrconf.properties, and then re-execute the cjenvupdate command.
If the file name is server.policy:

Make sure that server.policy.envupdate_bak is not being accessed. Then rename the server.policy.envupdate_bak file as server.policy, and then re-execute the cjenvupdate command.
If the file name is web.policy:

Make sure that web.policy.envupdate_bak is not being accessed. Then rename the web.policy.envupdate_bak file as web.policy.envupdate, and then re-execute the cjenvupdate command.

If the above-mentioned factors are not applicable, contact maintenance personnel.

KDJE30234-E

The directory was not found. Directory name = aa....aa

aa....aa: Directory name

Description: The directory was not found.
Action: Confirm that the directory required for execution of the application is created.

KDJE30250-I

Usage: cjstartrecover [cjstartsv'sOption] [[-p key=value] ...] [-t watchTime]

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

KDJE30251-E

An invalid option was specified. Option name = aa....aa

aa....aa: Invalid option name

Description: An invalid option is specified.
Action: Check the specified option, and then re-execute the process.

KDJE30252-E

A timeout occurred on the J2EE server in recovery mode. Server name = aa....aa

aa....aa: Server name

Description

A timeout occurred on the J2EE server in recovery mode.

Some unconcluded transactions might exist in the resource.

Action

Restart the J2EE server in the recovery mode, and then recover the transactions.

KDJE30253-E

Only the Cosminexus Component Container administrator can execute this command.

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

KDJE30254-I

Usage:

Format1: cjrarupdate -type { dbconnector | rar } [-force] [-f rarfile ... ] [-backupto directory]

Format2: cjrarupdate -recoverfrom directory

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

KDJE30255-E

An attempt to acquire the location of the public directory of the J2EE server has failed. Reason = aa....aa

aa....aa: Reason

Description: The location of the public directory of the J2EE server cannot be acquired.
Action: Take action depending on the contents of the reason for failure.

KDJE30256-E

An attempt to read the property file has failed. File = aa....aa

aa....aa: File that cannot be read (full path)

Description: The property file cannot be read.
Action: Check if the property file to be read exists, and if the file has read permission.

KDJE30257-E

The installation directory of Cosminexus Component Container could not be acquired.

Description: The installation destination of Cosminexus Component Container is not known.
Action: Make sure that the Cosminexus Component Container is installed properly.

KDJE30258-E

An unexpected exception occurred. Detail = aa....aa

aa....aa: Details

Description: An unexpected exception occurred.
Action: Acquire the maintenance information, and then contact maintenance personnel.

KDJE30259-W

The value aa....aa of the option bb....bb is invalid. The cc....cc value will be used.

aa....aa: Invalid value

bb....bb: Option name

cc....cc: Value used

Description

The value aa....aa of the option bb....bb is invalid.

The value cc....cc will be used.

Action

Revise the specified value of the option.

KDJE30260-I

The environment of the public directory will now be migrated. (Stage aa....aa of bb....bb)

aa....aa: Number of current stages

bb....bb: Total number of stages

Description: The environment of the public directory of the J2EE server will be migrated.

KDJE30261-I

The environment of the public directory has been migrated. (Stage aa....aa of bb....bb)

aa....aa: Number of current stages

bb....bb: Total number of stages

Description: The environment of the working directory of the J2EE server was migrated.

KDJE30262-I

The data source will now be migrated to the J2EE resource adapter. Data source display name = aa....aa

aa....aa: Data source display name

Description: The data source will be migrated to the J2EE resource adapter.

KDJE30263-I

The data source has been migrated to the J2EE resource adapter. J2EE resource adapter display name = aa....aa

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

Description: The data source was migrated to the J2EE resource adapter.

KDJE30264-E

The J2EE server has been started. Server name = aa....aa

aa....aa: The J2EE server name

Description

The command cannot be executed because the J2EE server has already been started.

The command execution will be interrupted.

Action

Stop the already running the J2EE server, and then re-execute the command.

KDJE30265-E

An attempt to create a backup for the public directory has failed. (Directory = aa....aa, Backup directory = bb....bb)

aa....aa: Directory name

bb....bb: Backup directory name

Description

An attempt to back up the work directory failed.

The possible cause is as follows.

A file under the work directory is being accessed.

Action

Make sure that no files under the work directory are being accessed, and then re-execute the cjenvupdate command.

KDJE30300-W

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

aa....aa: Failure reason code

Description

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

Action

Take action based on the contents of the failure reason code (aa....aa).

The following table lists the contents displayed in the failure reason code (aa....aa).

Table 7‒1: List of failure reason codes displayed in KDJE30300-W
Failure reason code	Cause of error	Action
`-1`	Either the environment variable `PRFSPOOL` is not set, or the directory set in the environment variable `PRFSPOOL` does not exist.	Confirm that the environment variable `PRFSPOOL` is set, or the directory exists.
`-2`	An error occurred in the service start processing of the PRF demon present in the process.	The PRF demon might not be invoked. Confirm that the PRF demon is invoked. Also, check the `PRFID` of the definition file.
`-3`	An error (such as system call error) occurred in the service start processing of the PRF demon present in the process.	See the log file present below setup-directory-of-environment-variable-PRFSPOOL`\log\`PRF-identifier (in Windows) or `$PRFSPOOL/log/`PRF-identifier (in UNIX). Consult the PRF messages, check the factors, and then take action.
`-4`	An attempt to load the library required for the service of PRF demon has failed.	Take action based on the following causes: Cosminexus Performance Tracer is not installed. PRF trace output library is not specified in the class path. The environment variable is invalid. Correct the cause of the error, and then re-execute the process.

KDJE30310-W

The J2EE server has stopped monitoring the resources because the number of used aa....aa(s) could not be retrieved.

aa....aa: Monitoring target

file descriptor: File descriptor monitoring

thread: Thread monitoring

Description: Resource monitoring has stopped because the usage value of aa....aa cannot be retrieved in this platform.
Action: Set the property of monitoring the file descriptor (ejbserver.watch.fileDescriptor.enabled) or the threads (ejbserver.watch.thread.enabled) as false.

KDJE30311-W

The threshold set for aa....aa exceeds the system maximum. The system maximum will be used. User-specified value = bb....bb, System value = cc....cc

aa....aa: Monitoring target

file descriptor: File descriptor monitoring

thread: Thread monitoring

bb....bb: User-specified value

cc....cc: System upper-limit value

Description

The threshold value of user-specified aa....aa exceeds the system maximum value.

The threshold value will be set same as the system maximum value and monitoring will be performed.

Action

Revise the user-specified value (file descriptor = ejbserver.watch.fileDescriptor.threshold, thread = ejbserver.watch.thread.threshold) or the system maximum value. Note that even if this message is displayed during startup of Management Server, the operations will execute normally.

KDJE30380-E

An attempt to acquire the Cosminexus configuration information has failed. Reason = aa....aa

aa....aa: Reason for failure

Description

An attempt to acquire the shared information of the Application Server has failed.

Action

Take action based on the contents of the reason for failure (aa....aa).

The following contents are displayed in the reason for failure (aa....aa):

Environment is invalid.

The Application Server might not be installed properly.

Check if the application server is properly installed.

Load library failed.

An attempt to load the library has failed. Revise the specified value of the cpp.library.version property of usrconf.cfg.

If no problem exists in the specified value of cpp.library.version, the Application Server might not be installed properly. Check if the application server is properly installed.

Unexpected error occurred.

Acquire the maintenance information, and then contact maintenance personnel.

KDJE30400-I

The user log environment setup will now start.

Description: The user log environment setup will start based on the values set in the property file.

KDJE30401-I

The user log environment setup has been terminated.

Description: The user log environment setup was terminated.

KDJE30402-I

The creation of the Handler object has been completed with the following attribute. Attribute: ClassName = aa....aa[ ; HandlerName = bb....bb[, path = cc....cc] [, count = dd....dd] [, limit = ee....ee] [, level = ff....ff] [, filter = gg....gg] [, formatter =hh....hh] [, encoding = ii....ii] [, appname = jj....jj] [, msgid = kk....kk] [, separator = ll....ll]]

aa....aa: Class name created by Reflection

The following are displayed when the value is not null:

bb....bb: Specified handler name

cc....cc: Prefix of the log file name

dd....dd: Maximum number of log files

ee....ee: Maximum capacity of log files

ff....ff: Maximum value of log output level

gg....gg: Filter class to be connected

hh....hh: Formatter class to be connected

ii....ii: Output encode

jj....jj: Default value for output in the AppName field, when no specification exists during the log output

kk....kk: Default value for output in the MsgID field, when no specification exists during the log output

ll....ll: Separator string between the information elements used in CJSimpleFormatter

Description

The creation of the Handler object was completed.

The handler is created in a configuration beginning with 'ClassName'.

KDJE30403-I

A Logger object has been created with the following attribute. Attribute: LoggerName = aa....aa[ ; ResourceBundleName = bb....bb] [, useParentHandlers = cc....cc] [, level = dd....dd] [, filter = ee....ee] [, ClassName = ff....ff] [ ; HandlerName = gg....gg]

aa....aa: Logger name

bb....bb: Resource bundle name

cc....cc: Setting for propagation to the parent logger (true: propagate, false: do not propagate)

dd....dd: Message filter level of logger

ee....ee: Filter class in which connection to the logger is specified

ff....ff: Class name of the handler connected to the logger

gg....gg: Identification name of the setting used during the initialization of the handler

Description

The creation of the Logger object was completed.

The logger is created in a configuration beginning with 'LoggerName'.

KDJE30404-I

The log file aa....aa was closed successfully.

aa....aa: File name

Description: The log file (aa....aa) was closed successfully.

KDJE30405-I

All the Logger objects and Handler objects managed by LogManager will be closed and the deletion of Loggers and Handlers from LogManager will now be started.

Description: All the Loggers and Handlers managed by the LogManager will be closed and the deletion of the Loggers and Handlers from the LogManager will start.

KDJE30406-I

The deletion of Logger objects and Handler objects from LogManager has finished.

Description: The deletion of Loggers and Handlers from the LogManager has finished.

KDJE30410-W

The value aa....aa of the property key bb....bb is invalid. The cc....cc value will be used.

aa....aa: Actually set value

bb....bb: Property key

cc....cc: Valid value at that point of time

Description

An invalid value is specified in the property key (bb....bb). Since the value is invalid, the currently valid value (cc....cc) will be used.

cc....cc is normally the default value, or the value of handler-name="default", logger-name="default" of the key ejbserver.application.userlog.CJLogHandler.handler-name.* and the key ejbserver.application.userlog.Logger.logger-name.* of the user property file.

Action

Check the value of the property key, and whether the security permission is correct.

KDJE30411-W

The specified class is invalid. This class was not created. ClassName = aa....aa[, HandlerName = bb....bb]

aa....aa: Class name

The following value is displayed when it exists:

bb....bb: Constructor argument

Description: The specified class (aa....aa) cannot be created either because it is invalid, or security permission to create this class using reflection is not available.
Action: Revise the value of the property key and the security permission.

KDJE30413-W

The specified parameter aa....aa is too long. This value was truncated at the maximum length.

aa....aa: Parameter name

Description

The value of the specified parameter (aa....aa) is too long.

The value of this parameter was set within the maximum length.

Action

Check the maximum length of the value of the parameter (aa....aa), and then specify the correct value.

KDJE30420-E

An attempt to read the property file name aa....aa has failed. Make sure that the property file exists.

aa....aa: File name

Description

An attempt to read the property file name (aa....aa) has failed.

Action

Take action based on the following causes:

The property file does not exist on the disk

If the user property file does not exist, copy the default user property file from the templates folder.
Permission is not available for reading the property file

Grant read permission.
Security permission is not available for reading the property file from the running program

Grant security permission for reading the property.

If the above-mentioned factors are not applicable, contact maintenance personnel.

KDJE30421-E

The setup has failed. If there is not enough space on the disk, then either change the output destination or delete unnecessary files to acquire enough space on the disk. ClassName = aa....aa[ ; HandlerName = bb....bb ], path = cc....cc

aa....aa: Class name

bb....bb: Handler name

cc....cc: File path

Description

An attempt to set up the class (aa....aa) has failed.

Action

If the space available on the disk is insufficient, either change the output destination, or delete the unnecessary files to secure sufficient free space. If permission for writing the files, or permission for security file output is not available, grant these permissions.

Take action based on the following causes responsible for failure in setting up the handler:

The available disk space is insufficient

Delete the unnecessary files to increase the available space at the output destination or change to an output destination with available space.
A read only, a running, or an open file already exists with the same name, or a file with no update permission exists

Specify the settings to output to a file with appropriate permissions.
A directory with the same name as the file name already exists, or the directory does not have write permission

Specify the settings to output to a directory or a file with appropriate permissions.
The disk device fails

Contact the system administrator.

The system administrator must replace the device.

If the above-mentioned factors are not applicable, contact maintenance personnel.

KDJE30423-E

An error has occurred during writing the message aa....aa into the file bb....bb.

aa....aa: Contents of the message to be output

bb....bb: Log file name

Description

A file I/O error occurred during the output of a message (aa....aa) to the file name (bb....bb).

Action

When a file I/O error occurs during data output, take action based on the following causes:

The available disk space is insufficient

Delete the unnecessary files to increase the available space at the output destination or change to an output destination with available space.
The disk device fails

Contact the system administrator.

The system administrator must replace the device.

If the above-mentioned factors are not applicable, contact maintenance personnel.

KDJE30424-E

The full path name of the file aa....aa is too long. The maximum length is bb....bb bytes.

aa....aa: Log file name (Full path name)

bb....bb: Maximum length of the log file name

Description

The full path name (aa....aa) of the file exceeds the limit.

Specify within the maximum length (bb....bb) of the log file name.

Action

Revise the output destination of the log file and the file name.

KDJE30429-E

The FileHandler aa....aa specified with the same path bb....bb exists. The value of the path must be unique between each FileHandler.

aa....aa: Handler name

bb....bb: File name

Description

An attempt was made to initialize the handler in a setup that specifies the same path.

Specify the path value of the handler so that it is unique between the handlers being used. The value of the path is not case-sensitive; therefore, strings with only upper case and lower-case differences cannot be specified.

Action

Revise the property definition so that each handler to be generated can be initialized with a different path value.

KDJE30430-E

The setup for the user log manager's properties performed during initializing the user log manager has failed.

Description

An error occurred while the properties of user log manager were being setup during the startup of the server and the setup of properties has failed.

If the message KDJE30420-E is output concurrently, an attempt to read the property file will fail.

Action

If the message KDJE30420-E is output concurrently, perform the action mentioned in the message KDJE30420-E. In other cases, contact maintenance personnel.

KDJE30431-E

An attempt to setup the handler has failed because an error was detected. ClassName = aa....aa[ ; HandlerName = bb....bb ]

aa....aa: Class name

bb....bb: Handler name

Description: An attempt to set up the handler (bb....bb) has failed because an error was detected.
Action: Check the error contents output before this message, based on the class name and the handler name.

KDJE30432-E

The specified logger is invalid. This logger was not created. LoggerName = aa....aa[ ; ResourceBundleName = bb....bb]

aa....aa: Logger name

bb....bb: Resource bundle name

Description

The specified logger (aa....aa) is invalid.

This logger was not created.

Action

Check the rules for the values that can be specified in the resource bundle name, and then specify the correct value.

KDJE30433-E

An attempt to read the system properties has failed, in the user log function of the EJB client application.

Description

An attempt to read the system properties has failed, in the user log functionality of the EJB client application.

Security permission is not available to read the system properties from the running program.

Action

Grant security permission for reading the system properties.

KDJE31000-I

OTS mode is enabled.

Description

The J2EE server will start in the OTS mode.

Using OTS can conclude XA transaction.

KDJE31001-I

Non-OTS mode is enabled.

Description

The J2EE server will start in the non-OTS mode.

Using OTS cannot conclude XA transaction.

KDJE31002-W

A transaction timeout occurred. (application = aa....aa, component = bb....bb, txid = cc....cc, PRF = dd....dd/ee....ee/ff....ff)

aa....aa: J2EE application name that started the transaction (If the transaction is started on another server, a single-byte hyphen (-) is displayed.)

bb....bb: Class name of the J2EE component (EJB/Servlet/JSP) that started the transaction + '@' + instance hash code (If the transaction is started on another server, a single-byte hyphen (-) is displayed.)

cc....cc: Internal ID of the timed out transaction

dd....dd: IP address of the timed out transaction

ee....ee: Process ID of the timed out transaction

ff....ff: Root application information of the timed out transaction

Description: The transaction will be rolled back due to the occurrence of a transaction timeout.
Action: Make sure that time is not being taken for the processing within the transaction, and if time is being taken, remove the cause. If the time taken for the processing within the transaction is appropriate, consider lengthening the time period until a timeout occurs.

KDJE31004-I

Light transaction is enabled.

Description

The local transaction is optimized.

XA transaction that uses OTS, cannot be concluded.

KDJE31005-E

The value of ejbserver.jta.TransactionManager.defaultTimeOut property is invalid. The default value will be used. (180sec)

Description

The value of the key ejbserver.jta.TransactionManager.defaultTimeOut is invalid. The default value (180 seconds) will be used.

The valid value is an integer in the range from 1 to 2147483647.

Action

Make sure that an invalid value is not specified in the key ejbserver.jta.TransactionManager.defaultTimeOut.

KDJE31006-E

Specified transaction timeout value is invalid.

Description

The specified transaction timeout value is invalid.

The valid value is an integer from 0 to 2147483647.

Action

Make sure that an invalid value (value that is not an integer from 0 to 2147483647) is not specified as the timeout value.

KDJE31007-E

Any non-XA Resource cannot be enlisted to global transactions.

Description

Non-XA resources cannot be enlisted in global transactions.

Only XA resources can be enlisted in global transactions.

Action

Make sure that non-XA resources are not enlisted in global transactions.

KDJE31008-E

The local transaction already has a non-XA Resource and cannot have more than two resources.

Description: The local transaction already has a non-XA resource. As a result, more resources cannot be enlisted.
Action: Make sure that multiple resources are not enlisted in the local transaction. If multiple resources are to be enlisted, use a global transaction for enlisting of XA resources.

KDJE31009-E

No nested transaction is supported.

Description: No nested transaction is supported.
Action: Do not use nested transactions.

KDJE31010-W

Unclosed connection was forced to close. (componentInstance=aa....aa, resourceHandle=bb....bb, resource=cc....cc)

aa....aa: Component information

bb....bb: Resource handle information

cc....cc: Resource information

Description

A J2EE application was terminated without closing the connection.

The unclosed connection was forced to close.

Action

Modify the J2EE application so that connection closure is not omitted.

KDJE31011-E

The transaction has been rolled back, not committed. (cause=aa....aa)

aa....aa: Exception information

Description

The transaction cannot be committed because it has rolled back.

Action

Confirm the following details:

Confirm that the J2EE application is not marked for rollback in the state prior to commit.
Confirm 1, and if not marked, confirm that time is not being taken for the processing within the transaction. If time is being taken, remove the cause.
Confirm 2, and if the time taken for the processing within the transaction is appropriate, consider lengthening the time period until a timeout occurs.

If the responsible factors cannot be eliminated even after confirming the above contents, see the exception information or other messages, and then remove the cause of rollback.

KDJE31012-E

A heuristic exception occurred. (cause=aa....aa)

aa....aa: Exception information

Description

A heuristic exception occurred.

The heuristic exception occurs when some of the resource managers enlisted in the global transactions are unilaterally concluded. The factor responsible for heuristic exceptions might have the inability to carry out normal processing due to reasons, such as network failure.

When some of the resource managers enlisted in the global transactions are unilaterally concluded, the consistency of the transactions might not be maintained between resource managers.

Action

Check the state of transaction in the resource managers. For details, see the manual TPBroker User's Guide.

KDJE31013-E

The transaction having non-XA resource cannot be exported; the 2-phase commit has not done.

Description: The transaction having non-XA resource cannot be exported (2-phase commit cannot be done).
Action: Do not perform remote invocation in a local transaction.

KDJE31014-E

The global transaction could not be started. (cause=aa....aa)

aa....aa: Exception information

Description

The global transaction cannot be started.

Action

Check the settings for the transaction service. When checking, confirm the following details:

Is the Smart Agent running?
Does the system environment variable OSAGENT_PORT match with the key vbroker.agent.port in the specification of the Smart Agent port?
Is TCS running?
Are the number of branches of TPBroker appropriate?

For details on the method of setup, see the manual TPBroker User's Guide.

KDJE31015-I

OTS in-process mode is enabled.

Description: Using OTS can conclude XA transaction.

KDJE31016-W

A transaction has been forced to timeout. (application = aa....aa, component = bb....bb, txid = cc....cc, PRF = dd....dd/ee....ee/ff....ff)

aa....aa: J2EE application name that started the transaction (If the transaction is started on another server, a single-byte hyphen (-) is displayed.)

bb....bb: Class name of the J2EE component (EJB/Servlet/JSP) that started the transaction + '@' + instance hash code (If the transaction is started on another server, a single-byte hyphen (-) is displayed.)

cc....cc: Internal ID of the rolled back transaction

dd....dd: IP address of the rolled back transaction

ee....ee: Process ID of the rolled back transaction

ff....ff: Root application information of the rolled back transaction

Description: The running transaction was forced to time out due to forced termination of the application.
Action: Confirm that the time taken for the processing within the transaction is not more than expected and if more time is being taken, remove the cause.

KDJE31017-I

A client transaction was marked for rollback.

Description

When a system exception occurs during EJB invocation, the client transaction is marked for rollback according to the current usrconf.properties settings.

Action

To avoid the client transaction from being marked for rollback when a system exception occurs during EJB invocation, set the following property in usrconf.properties:

ejbserver.distributedtx.rollbackClientTxOnSystemexception=false

KDJE31018-E

The cjlisttrn command cannot be supported because light transaction is enabled.

Description

The cjlisttrn command supports display of the global transaction information when the in-process transaction service is enabled. As a result, the cjlisttrn command cannot be used when the light transaction is enabled.

Action

Confirm the following points, and then re-execute the command:

The J2EE server startup mode is 1.4 mode.
The light transaction functionality is disabled.
The in-process transaction service is enabled.

KDJE31019-E

The cjlisttrn command cannot be supported because out-process transaction service is enabled.

Description: The cjlisttrn command is supported, when the in-process transaction service is enabled. As a result, the cjlisttrn command cannot be used when the out-process transaction service is enabled.
Action: Use the command for displaying the transaction information for out-process transaction service.

KDJE31020-E

The cjlisttrn command cannot be supported because basic mode is enabled.

Description

The cjlisttrn command supports display of the global transaction information when the in-process transaction service is enabled. As a result, the cjlisttrn command cannot be used in the basic mode.

Action

Confirm the following points, and then re-execute the command:

The J2EE server startup mode is 1.4 mode.
The light transaction functionality is disabled.
The in-process transaction service is enabled.

KDJE31021-W

A transaction timeout occurred. (threadName = aa....aa, threadHashCode=bb....bb)

aa....aa: Thread name that started the transaction

bb....bb: Hash code of the thread that started the transaction

Description: The transaction will be rolled back due to the occurrence of a timeout in the transaction started in the EJB client.
Action: Make sure that time is not being taken for the processing within the transaction, and if time is being taken, remove the cause. If the time taken for the processing within the transaction is appropriate, consider lengthening the time period until a timeout occurs.

KDJE31022-E

Using the UserTransactionFactory is not permitted in the J2EE server side.

Description: UserTransactionFactory cannot be used in the J2EE server. UserTransactionFactory can only be used in the EJB client.
Action: To acquire UserTransaction from the EJB and Servlets running on the J2EE server, use JNDI to perform lookup. In the case of EJB, UserTransaction can be acquired from javax.ejb.EJBContext.

KDJE31023-E

The transaction is disabled in the client side.

Description: The transaction is disabled in the client side.
Action: To use the transaction in the EJB client, specify true in the property ejbserver.client.transaction.enabled.

KDJE31024-E

Failed to create UserTransaction. cause=aa....aa

aa....aa: Cause of failure in creating UserTransaction

Description: An attempt to create UserTransaction has failed.
Action: Check the cause of failure (aa....aa), and then take action.

KDJE31025-E

Failed to initialize transaction manager. cause=aa....aa

aa....aa: Cause of failure in initializing the transaction manager

Description: An attempt to initialize the transaction manager has failed.
Action: Check the cause of failure (aa....aa), and then take action.

KDJE31026-E

Failed to load the ORBInitializer class. cause=aa....aa

aa....aa: Cause of failure in loading the ORBInitializer class

Description: An attempt to load the ORBInitializer class has failed.
Action: Check the cause of failure (aa....aa), and then take action.

KDJE31027-E

The OTS status directory path is not specified.

Description: In the EJB client, the directory in which the status file of the in-process transaction service is saved is not specified.
Action: In the invocation batch file of EJB client, specify the directory in which the status file is saved, in the property ejbserver.distributedtx.ots.status.directory1.

KDJE31028-E

This method is not supported. (class = aa....aa, method = bb....bb)

aa....aa: Class name

bb....bb: Method name

Description: An unsupported method is invoked.
Action: Do not invoke a method that is not supported.

KDJE31030-E

The cjcommittrn, cjrollbacktrn, and cjforgettrn command cannot be supported because the light transaction is enabled.

Description: The cjcommittrn command, cjrollbacktrn command, and cjforgettrn command cannot be used because the light transaction functionality is enabled.
Action: Disable the light transaction functionality.

KDJE31031-E

The cjcommittrn, cjrollbacktrn, and cjforgettrn command cannot be supported because the out-process transaction service is enabled.

Description: The cjcommittrn command, cjrollbacktrn command, and cjforgettrn command cannot be used because the out-process transaction service is enabled.
Action: Enable the in-process transaction service.

KDJE31032-E

The cjcommittrn, cjrollbacktrn, and cjforgettrn command cannot be supported because the basic mode is enabled.

Description: The cjcommittrn command, cjrollbacktrn command, and cjforgettrn command cannot be used in the basic mode.
Action: Set the startup mode of the J2EE server to 1.4 mode.

KDJE31800-E

An attempt to obtain property aa....aa has failed.

aa....aa: Property name

Description

An attempt to acquire the property (aa....aa) has failed.

The processing will be interrupted.

Action

Check if the property is specified in the user property file.

KDJE31801-W

An attempt to obtain property aa....aa has failed. The default value bb....bb will be used.

aa....aa: Property name

bb....bb: Default value

Description

An attempt to acquire the property (aa....aa) has failed. The default value (bb....bb) will be used.

The processing continues.

Action

Check if the property is specified in the user property file.

KDJE31802-E

The property value is invalid.(aa....aa=bb....bb)

aa....aa: Property name

bb....bb: Property value

Description

The property value (bb....bb) is invalid.

The processing will be interrupted.

Action

Check if the property value set in the user property file is correct.

KDJE31803-W

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

aa....aa: Property name

bb....bb: Set property value

cc....cc: Default value

Description

The property value (bb....bb) is invalid. The default value (cc....cc) will be used.

The processing continues.

Action

Check if the property value set in the user property file is correct.

KDJE31804-E

A fatal error occurred.(error information=aa....aa)

aa....aa: Error information

Description

A fatal error occurred.

The processing will be interrupted.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KDJE31805-I

A transaction recovery scan is executed. resource name=aa....aa

aa....aa: Resource name

Description: The resource (aa....aa) will be scanned, and if any unconcluded transaction exists, the transaction recovery will be executed.

KDJE31806-E

An attempt to assign a transaction recovery port has failed.(port number=aa....aa)

aa....aa: Port number that cannot be assigned

Description

An attempt to assign the port number (aa....aa) used for transaction recovery has failed.

The processing will be interrupted.

Action

Confirm that no other process is using the port number specified in the key ejbserver.distributedtx.recovery.port specified in the system property file (sysconf.properties) or the user property file (usrconf.properties).

KDJE31808-W

A resource for which a transaction was running has been deleted.(resource name=aa....aa)

aa....aa: Resource name

Description

A resource (aa....aa) for which a transaction was running was deleted.

Action

Unconcluded transactions might exist in the deleted resource.

Check the state of the transaction.

If any unconcluded transactions exist in the target resource, re-register the resource, restart the J2EE server, and then execute transaction recovery.

KDJE31809-W

The resource cannot be deleted because an incomplete transaction exists.(resource name=aa....aa)

aa....aa: Resource name

Description

The resource (aa....aa) cannot be deleted because an unconcluded transaction exists.

Action

Use an OTS command to check whether unconcluded transactions are remaining in the resource.

If the resource has stopped, invoke it.

If any unconcluded transaction exists, conclude the transaction, and then re-execute the process.

If unconcluded transactions do not exist, confirm that the specification of the Smart Agent port is correct (whether the system environment variable OSAGENT_PORT matches with the key vbroker.agent.port set in the user property file).

KDJE31810-I

The system is waiting for incomplete transactions.

Description

The system waits for conclusion of all transactions of the registered resources during the termination of the J2EE server.

When the J2EE server is forcefully terminated, some unconcluded transactions might exist in the resource.

Action

Use an OTS command to confirm that no unconcluded transactions are remaining in the resource. If unconcluded transactions exist, restart the J2EE server, and then execute transaction recovery.

If the J2EE server does not stop even after the lapse of time set up as the transaction timeout^#, confirm the following details, and then take action:

The resource settings are correct.
If the resource has stopped, invoke the resource.
No errors have occurred in the J2EE server, such as insufficient memory.
The specification of the Smart Agent port is correct (the system environment variable OSAGENT_PORT matches with the key vbroker.agent.port set in the user property file).

#: A transaction timeout refers to the value set in the key ejbserver.jta.TransactionManager.defaultTimeOut of the user property file, and the value set in the method setTransactionTimeout of UserTransaction interface.

KDJE31812-W

An attempt to establish a connection to the recovery resource has failed.(resource type=aa....aa, name=bb....bb, reason=cc....cc)

aa....aa: Resource type

bb....bb: Resource name

cc....cc: Exception information

Description

An attempt to establish a connection to the resource (bb....bb), wherein the transactions are to be recovered, has failed.

The processing continues.

Action

Examine the cause of failure in establishing a connection to the target resource, and then take action.

KDJE31813-I

The transaction recovery processing recovered a connection to the target resource.(resource type=aa....aa, resource name=bb....bb)

aa....aa: Resource type

bb....bb: Resource name

Description: The transaction recovery processing recovered a connection to the target resource (bb....bb).

KDJE31814-W

The XA resource cannot be acquired.(resource type=aa....aa, resource name=bb....bb)

aa....aa: Resource type

bb....bb: Resource name

Description

The XA resource (bb....bb) required for transaction recovery cannot be acquired.

Under these circumstances, if the J2EE server is terminated, or the resource is deleted, unconcluded transactions might remain in the target resource.

Action

Confirm the following details, and then take action:

Settings of the resource
The target resource is invoked
Network failure has not occurred

If unconcluded transactions exist in the target resource, restart the J2EE server, and then execute transaction recovery.

KDJE31815-E

You do not have permission to perform the recovery scan.(resource type=aa....aa, resource name=bb....bb)

aa....aa: Resource type

bb....bb: Resource name

Description

Either an attempt to scan the unconcluded transactions in the target resource (bb....bb) has failed, or appropriate permission is not available.

Transactions cannot be started in this state.

Connection to the target resource has probably not been established.

Action

Confirm the following details, and then take action:

Settings of the resource
The target resource is invoked
Network failure has not occurred

If connection to the target resource is established, set appropriate permission so as to enable scanning of unconcluded transactions. If no problem exists in the settings, acquire the maintenance information, and then contact maintenance personnel.

KDJE31816-I

Transaction completion check ended successfully. (resource type=aa....aa, resource name=bb....bb)

aa....aa: Resource type

bb....bb: Resource name

Description: The transaction conclusion check has ended successfully.

KDJE31817-W

Pending transactions exist or recovery process is now in progress. (resource type=aa....aa, resource name=bb....bb)

aa....aa: Resource type

bb....bb: Resource name

Description: Either unconcluded transactions exist or the recovery process is in progress.
Action: Wait for conclusion of unconcluded transactions, or completion of the recovery process.

KDJE31818-W

Establishing a recovery connection to the resource failed. (resource type=aa....aa, resource name=bb....bb)

aa....aa: Resource type

bb....bb: Resource name

Description

An attempt to establish a recovery connection to the resource has failed.

Take action based on the following causes for failure in connecting to the resource:

The resource has stopped.
A network failure occurred.
The resource settings are invalid.

Action

Make sure that the state enables connection to the resource.

KDJE31819-W

Fetching pending transactions of the resource failed. (resource type=aa....aa, resource name=bb....bb)

aa....aa: Resource type

bb....bb: Resource name

Description

An attempt to acquire unconcluded transactions from the resource has failed.

Take action based on the following causes for failure in acquiring the unconcluded transactions:

The permission for acquiring the unconcluded transactions is not set for the user connected to the resource.
The resource settings are invalid.

Action

Make sure that the state enables acquisition of unconcluded transactions from the resource.

KDJE31820-W

Transaction completion check timed out. To recover pending transactions, restart the system.

Description: The transaction conclusion check was timed out.
Action: To execute recovery of unconcluded transactions, restart the system.

KDJE32000-W

Cannot enlist two or more XAResources. Info=aa....aa

aa....aa: Method name

Description

An attempt was made to enlist two or more different data sources in the JTA transaction.

Only one data source can be enlisted in the JTA transaction.

Action

Revise the settings so that multiple data sources are not enlisted in one transaction. If the connection pooling is disabled, the same data source would be treated as another data source. Enable the connection pooling.

KDJE34000-I

The SFO server application will now start.

Description: The SFO server application will start.

KDJE34001-E

An attempt to start the SFO server application failed because the -nosecurity option was not specified in the cjstartsv command.

Description

An attempt to start the SFO server application has failed.

The -nosecurity option is not specified in the cjstartsv command.

Action

Stop the SFO server, specify the -nosecurity option in the cjstartsv command, and then start the SFO server.

KDJE34002-I

The SFO server application will now stop.

Description: The SFO server application will terminate.

KDJE34003-I

Replication of the global session information will now start. (J2EE application = aa....aa, context root = bb....bb, max sessions = cc....cc, max session info size = dd....dd, max inactive interval = ee....ee, lock timeout = ff....ff, GS control = gg....gg, GID cookie name = hh....hh, GID URL param name = ii....ii, jj....jj, kk....kk, replicatable type = ll....ll)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Maximum number of global sessions

dd....dd: Maximum value (in bytes) of the size of global session information

ee....ee: Validity period (in seconds) of the global session

ff....ff: Timeout value for awaiting global session lock

gg....gg: Control method of the global session

cookie: Control is performed by using an HTTP Cookie.

url-rewriting: Control is performed by using URL rewriting.

both: Control is performed by using both the HTTP Cookie and the URL rewriting.

hh....hh: Name of the HTTP Cookie used to send the global session ID when gg....gg is either cookie or both. Null character string, when gg....gg is url-rewriting

ii....ii: Path parameter name of the URL used to send the global session ID when gg....gg is either url-rewriting or both. Null character string, when gg....gg is cookie

jj....jj: Settings of keys for rewritable global session information

The set information of the keys is output in either of the following formats:

RW key = Settings-of-keys-for-rewritable-global-session-information

The set values of the keys of global session information will be output in a semicolon (;) delimited series.

When the GSInfoKey-RW parameter is omitted, a null character string will be output in the set value of the key.
RW key(*)

When the entire session information registered in the HTTP session, except the information registered in the key specified in the GSInfoKey-R parameter, is set up as the rewritable global session information, "RW key(*)" will be output.

kk....kk: Settings of keys for read-only global session information

The set information of the keys is output in either of the following formats:

R key = Settings-of-keys-for-read-only-global-session-information

The set values of the keys of global session information will be output in a semicolon (;) delimited series.

When the GSInfoKey-R parameter is omitted, a null character string will be output in the set value of the key.
R key(*)

When the entire session information registered in the HTTP session, except the information registered in the key specified in the GSInfoKey-RW parameter, is set up as the rewritable global session information, "R key(*)" will be output.

ll....ll: Type of the inheritable session information

String: Only objects of the java.lang.String class

String or byte[]: Objects or byte arrays of the java.lang.String class

Serializable: Objects of a serializable class

Description: Replication of the global session information will start.

KDJE34004-E

There is not enough memory to start replicating the global session information. (J2EE application = aa....aa, context root = bb....bb, max sessions = cc....cc, max session info size = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Maximum number of global sessions

dd....dd: Maximum value (in bytes) of the size of global session information

Description

Sufficient memory is not available to start replicating the global session information.

Take action based on the following causes:

The estimation of memory usage set in the SFO server is wrong
The maximum size of the global session information set in the Web application present on the J2EE server is large
The maximum value of the number of HttpSession set in the J2EE server is inappropriately large

Action

Take the following actions depending upon the cause:

When the memory usage set in the SFO server is wrong

Revise the estimation of the memory required in the SFO server.

The memory required in the SFO server is proportionate to the maximum number of global sessions, and the maximum size of the global session information.

In the case of a problem in setting the required memory, set the appropriate value in the Java VM definition file (usrconf.cfg), and then restart the SFO server.

When the maximum size of the global session information is large

Revise the maximum size of the global session information set in the Web application.

In the case of a problem in the maximum size of the global session information, set the appropriate value in the Deployment Descriptor (web.xml) of the Web application.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied.

When the maximum value of the number of HttpSession is large

Revise the maximum value of the number of HttpSession set in the Web application.

If the maximum value of the number of HttpSession is more than required, change to an appropriate value, and then restart the J2EE application.

KDJE34005-I

The global sessions in the SFO server will be discarded because the SFO server application will stop. (J2EE application = aa....aa, context root = bb....bb, discarded global sessions = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Discarded global sessions

Description: The global sessions in the SFO server will be discarded because the SFO server application will terminate.

KDJE34006-I

The global sessions in the SFO server will be discarded. (J2EE application = aa....aa, context root = bb....bb, discarded global session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Discarded global session ID

Description

The global session ID of the discarded SFO server will be output because the SFO server application will terminate.

If there are multiple global sessions, they are delimited with comma (,) during the output. If the number of global session IDs exceeds 20, output in multiple rows.

KDJE34007-I

The SFO server will now connect with the J2EE server. (J2EE application = aa....aa, context root = bb....bb, connecting J2EE servers = cc....cc, connection timeout = dd....dd, J2EE server = ee....ee : ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Connected J2EE servers

dd....dd: Time set for the connection timeout with the J2EE server

ee....ee: IP address of the J2EE server in which the connection was started

ff....ff: Server name of the J2EE server in which the connection was started

Description

The SFO server will start a connection with the J2EE server with IP address ee....ee, and server name ff....ff, for the Web application with J2EE application name aa....aa, and context root name bb....bb.

The number of J2EE servers connected to this Web application is cc....cc.

KDJE34008-E

An attempt to negotiate with the J2EE server has failed. (J2EE server= aa....aa : bb....bb, invalid parameter = (cc....cc))

aa....aa: IP address of the J2EE server

bb....bb: Server name of the J2EE server

cc....cc: Information of the Web application that was the cause of the error

Description

An attempt to negotiate with the J2EE server has failed.

The set information of the Web application registered in the SFO server does not match with the set information of the Web application of the J2EE server with which a connection was attempted.

In cc....cc, the parameters responsible for the error, and the set values of the J2EE server with which a connection was attempted, will be output in the following format:

Parameter-name = Setting-value

The contents of the parameter name are as follows:

max sessions: Maximum number of global sessions
max session info size: Maximum value (in bytes) of the size of global session information
max inactive interval: Validity period (in seconds) of the global session
lock timeout: Timeout value for awaiting global session lock
GS control: Control method of the global session
GID cookie name: Name of the HTTP Cookie used to send the global session ID
GID URL param name: Path parameter name of the URL used to send the global session ID
RW key = Settings-of-keys-for-rewritable-global-session-information
R key = Settings-of-keys-for-read-only-global-session-information
byte array enable: Can the session information in the form of byte arrays be inherited
serializable enable: Can the session information in the form of objects of the serializable class be inherited

When the entire session information registered in the HTTP session is set up either as the rewritable global session information or as the read-only global session information, "RW key(*)" or "R key(*)" will be output respectively, instead of the output in the format parameter-name = set-value.

In the case of multiple errors, the parameter names are output with comma (,) as delimiters.

The set values of the keys of global session information will be output in a semicolon (;) delimited series.

Action

Revise the set information of the Web application in which the error has occurred.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied.

For details on the set information about the Web application registered in the SFO server, check the message KDJE34003-I, output in the message log of the SFO server.

KDJE34009-I

The SFO server will now disconnect from the J2EE server. (J2EE application = aa....aa, context root = bb....bb, connected J2EE server = cc....cc, J2EE server = dd....dd : ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Connected J2EE servers

dd....dd: IP address of the J2EE server in which the connection was terminated

ee....ee: Server name of the J2EE server in which the connection was terminated

Description

The connection between the Web application with J2EE application name aa....aa, and context root name bb....bb , and the J2EE server with IP address dd....dd, and server name ee....ee, will terminate.

The number of J2EE servers connected to this Web application is cc....cc.

KDJE34010-E

The connection with the J2EE server will now end because the SFO server did not receive a reply from the J2EE server. (J2EE application = aa....aa, context root = bb....bb, connected J2EE server = cc....cc, J2EE server = dd....dd : ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Connected J2EE servers

dd....dd: IP address of the J2EE server in which the connection was disconnected

ee....ee: Server name of the J2EE server in which the connection was disconnected

Description

There is no response from the J2EE server with IP address ee....ee, and server name ff....ff, for the Web application with J2EE application name aa....aa, and context root name bb....bb. The connection will be disconnected.

The number of J2EE servers connected to this Web application is cc....cc.

Action

Make sure that the J2EE server in which an error occurred is running normally, and no problem exists in the communication path between the SFO server and the J2EE server.

In the case of a problem in the J2EE server process, or the host on which the J2EE server is running, solve the problem, and then restart the J2EE server.

In the case of a problem in the communication path between the SFO server and the J2EE server, solve the problem of the communication path. If the communication path becomes normal, the SFO server and the J2EE server will re-connect automatically.

KDJE34011-I

Expired global sessions in the SFO server have been discarded. (J2EE application = aa....aa, context root = bb....bb, global sessions = cc....cc, discarded global sessions = dd....dd, processing time = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global sessions registered in the SFO server, when the validity period check was started

dd....dd: Discarded global sessions

ee....ee: Processing time (in milliseconds) of the validity period check

Description: The expired global sessions have been discarded in the Web application with J2EE application name aa....aa, and context root name bb....bb.

KDJE34012-I

Expired global sessions in the SFO server have been discarded. (J2EE application = aa....aa, context root = bb....bb, discarded global session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Discarded global session ID

Description

The global session ID discarded due to expiry of validity period is output.

If there are multiple global sessions, they are delimited with comma (,) during the output. If the number of global session IDs exceeds 20, output in multiple rows.

KDJE34013-I

Expired global sessions have been discarded. (J2EE application = aa....aa, context root = bb....bb, global session ID = cc....cc, last accessed time = dd....dd, max inactive interval = ee....ee, J2EE server = ff....ff : gg....gg)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

dd....dd: Last updated time of the global session

ee....ee: Validity period of global session

ff....ff: IP address of the J2EE server updated last in the discarded global session

gg....gg: Server name of the J2EE server updated last in the discarded global session

Description: The global session was discarded due to expiry of the validity period. The information of the discarded global session is output.

KDJE34014-W

An unlocked global session was discarded because it had expired. (J2EE application = aa....aa, context root = bb....bb, global session ID = cc....cc, last accessed time = dd....dd, max inactive interval = ee....ee, lock request count = ff....ff, J2EE server = gg....gg : hh....hh)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

dd....dd: Last updated time of the global session

ee....ee: Validity period of global session

ff....ff: Lock request count for awaiting unlocking

gg....gg: IP address of the J2EE server in which the discarded global session is locked

hh....hh: Server name of the J2EE server in which the discarded global session is locked

Description

A global session, in which the lock is not released, was discarded because of expiry of the validity period. The information of the discarded global session is output.

Take action based on the following causes for expiry of validity period while the lock was still not released:

The set value of the validity period of HTTP session is inappropriately small.
The locked J2EE server has slowed down due to some reason, and the processing has not finished during the validity period.
The locked J2EE server has stopped.

Action

Check the working state of the locked J2EE server. Also, check the validity period of the HTTP session.

To change the validity period of the HTTP session, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34015-W

A new global session cannot be created because the number of global sessions has reached the maximum. (J2EE application = aa....aa, context root = bb....bb, max sessions = cc....cc, J2EE server = dd....dd : ee....ee, request = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Maximum number of global sessions

dd....dd: IP address of the J2EE server that requested the creation of a global session

ee....ee: Server name of the J2EE server that requested the creation of a global session

ff....ff: Contents of the request from the J2EE server

Description

There was a request for creation of a global session from the J2EE server, but, since the number of global sessions has reached the maximum value, a new session cannot be created.

The contents of the request from the J2EE server will be output to ff....ff. The output messages and their meaning is described below:

create from the initial HTTP session: A global session is created from the new HTTP session created on the J2EE server.
create from the existing HTTP session: A global session is created from the HTTP session that already exists on the J2EE server. In such a case, the J2EE server disconnects once from the SFO server, and then re-connects.

Action

If you want to create a global session, revise the maximum value of the number of HttpSession and the validity period of the HTTP sessions.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34016-W

A timeout occurred during a lock request. (J2EE application = aa....aa, context root = bb....bb, global session ID = cc....cc, last accessed time = dd....dd, max inactive interval = ee....ee, session info size = ff....ff, lock timeout J2EE server = gg....gg : hh....hh, locked J2EE server = ii....ii : jj....jj, request = kk....kk)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

dd....dd: Last updated time of the global session

ee....ee: Validity period of global session

ff....ff: Size (in bytes) of the global session information

gg....gg: IP address of the J2EE server in which a timeout occurred during the lock request

hh....hh: Server name of the J2EE server in which a timeout occurred during the lock request

ii....ii: IP address of the locked J2EE server

jj....jj: Server name of the locked J2EE server

kk....kk: Contents of the request from the J2EE server

Description

A timeout occurred during the request for locking the global session.

The locked J2EE server might have either slowed down or stopped.

The contents of the request from the J2EE server will be output in kk....kk. The output messages and their meaning is described below:

get: The global session information is acquired from the SFO server, since the HTTP session does not exist on the J2EE server.
lock: The HTTP session exists on the J2EE server. To process the request, the global session present on the SFO server is locked.

Action

Check the working state of the locked J2EE server.

If no problem exists in the working state of the locked J2EE server, confirm that the set value for lock timeout is appropriate.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34017-W

The requested global session does not exist. (J2EE application = aa....aa, context root = bb....bb, global session ID = cc....cc, J2EE server = dd....dd : ee....ee, request = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

dd....dd: IP address of the J2EE server that has sent a request to the SFO server

ee....ee: Server name of the J2EE server that has sent a request to the SFO server

ff....ff: Contents of the request from the J2EE server

Description

The global session requested from the J2EE server does not exist.

The global session is discarded due to one of the following reasons:

The HTTP session was disabled on the J2EE server
The validity period has expired on the SFO server
The SFO server was restarted

The contents of the request from the J2EE server that will be output in ff....ff, and the meaning is described below:

get: The global session information is acquired from the SFO server, since the HTTP session does not exist on the J2EE server.
lock: The HTTP session exists on the J2EE server. To process the request, the global session present on the SFO server is locked.
unlock: The global session information present on the SFO server is updated and released when the request processing on the J2EE server is finished.
invalidate: The global session information present on the SFO server is discarded because the HTTP session was discarded on the J2EE server.
update the last accessed time: After locking the global session on the J2EE server, only the last accessed time of the global session present on the SFO server is updated since a request with the same session ID was received during the request processing.

Action

If the contents of the request from the J2EE server that are output in ff....ff are either "get" or "lock", the J2EE server has received a request for a global session in which the validity period has been expired.

In the case of "unlock", "invalidate", or "update the last accessed time", the J2EE server might be either slowing down or the valid period might be short.

Check the working state of the J2EE server.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34018-W

The requested global session has been discarded. (J2EE application = aa....aa, context root = bb....bb, global session ID = cc....cc, J2EE server = dd....dd : ee....ee, request = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

dd....dd: IP address of the J2EE server

ee....ee: Server name of the J2EE server

ff....ff: Contents of the request from the J2EE server

Description

The global session requested from the J2EE server is discarded either because the HTTP session was disabled on the J2EE server, or the validity period has expired on the SFO server.

The contents of the request from the J2EE server that will be output in ff....ff, and the meaning is as follows:

get: The global session information is acquired from the SFO server, since the HTTP session does not exist on the J2EE server.
lock: The HTTP session exists on the J2EE server. To process the request, the global session present on the SFO server is locked.
unlock: The global session information present on the SFO server is updated and released when the request processing on the J2EE server is finished.
update the last accessed time: After locking the global session on the J2EE server, only the last accessed time of the global session present on the SFO server is updated since a request with the same session ID was received during the request processing.

Action

If the contents of the request from the J2EE server that are output in ff....ff are either "get" or "lock", the J2EE server has received a request for a global session in which the validity period has been expired.

In the case of "unlock" or "update the last accessed time", the J2EE server might be either shutting down or the valid period might be short.

Check the working state of the J2EE server.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34019-E

An unexpected error occurred in the SFO server. (J2EE application = aa....aa, context root = bb....bb, global session ID = cc....cc, last accessed time = dd....dd, max inactive interval = ee....ee, session info size = ff....ff, requested J2EE server = gg....gg : hh....hh, last updated J2EE server = ii....ii : jj....jj, request = kk....kk, error reason = ll....ll)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

dd....dd: Last accessed time of global session

ee....ee: Validity period of global session

ff....ff: Size (in bytes) of the global session information

gg....gg: IP address of the J2EE server in which the request to the SFO server resulted in an error

hh....hh: Server name of the J2EE server in which the request to the SFO server resulted in an error

ii....ii: IP address of the J2EE server in which the global session was last updated

jj....jj: Server name of the J2EE server in which the global session was last updated

kk....kk: Contents of the request from the J2EE server

ll....ll: Maintenance information

Description

An unexpected error occurred in the SFO server while the request from the J2EE server was being processed.

The contents of the request from the J2EE server will be output to ff....ff. The output messages and their meaning is described below:

create from the initial HTTP session: A global session is created from the new HTTP session that was created on the J2EE server.
create from the existing HTTP session: A global session is created from the HTTP session that already exists on the J2EE server. In such a case, the J2EE server disconnects once from the SFO server, and then re-connects.
get: The global session information is acquired from the SFO server, since the HTTP session does not exist on the J2EE server.
lock: The HTTP session exists on the J2EE server. To process the request, the global session present on the SFO server is locked.
unlock: The global session information present on the SFO server is updated and released when the request processing on the J2EE server is finished.
invalidate: The global session information present on the SFO server is discarded because the HTTP session was discarded on the J2EE server.
update the last accessed time: After locking the global session on the J2EE server, only the last accessed time of the global session present on the SFO server is updated since a request with the same session ID was received during the request processing.

Action

Make sure that other error messages are not output in the log of SFO server. If error messages are output, take action as per the contents of the error message. If no error message is output, the followings might be the causes. Take action based on the following causes:

A problem occurred in the host in which the J2EE server is running.

Remove the cause of the problem occurred in the host.
A problem occurred in the communication path between the J2EE server and the SFO server.

Remove the cause of the problem that occurred in the communication path.
A problem occurred in the host in which the J2EE server is running.

Remove the cause of the problem occurred in the host.

If no problem exists, acquire the maintenance information, and then contact maintenance personnel.

KDJE34020-E

An unexpected error occurred in the SFO server. (aa....aa)

aa....aa: Error message for an unexpected exception

Description

An unexpected exception occurred in the SFO server.

Action

Confirm that other error messages are not output in the log of SFO server, or no problem exists in the host on which the SFO server is running.

If error messages are output, take action as per the contents of the error message. If a problem exists in the host on which the SFO server is running, solve the problem, and then restart the SFO server.

If the above-mentioned problems do not occur, acquire the maintenance information, and then contact maintenance personnel.

KDJE34021-W

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

aa....aa: Property name

bb....bb: Specified value

cc....cc: Default value

Description

The property settings of the SFO server are invalid.

The default value will be used.

Action

Modify the set value of the properties output in the message, and then restart the SFO server.

KDJE34022-I

The number of global sessions is zero. (J2EE application = aa....aa, context root = bb....bb, max sessions = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Maximum number of global sessions

Description: The number of global sessions has become zero.

KDJE34023-I

The number of global sessions is aa....aa% (bb....bb) of the maximum allowable sessions. (J2EE application = cc....cc, context root = dd....dd, max sessions = ee....ee)

aa....aa: Ratio of current number of global sessions with respect to the maximum number of global sessions

bb....bb: Current number of global sessions

cc....cc: J2EE application name

dd....dd: Context root name

ee....ee: Maximum number of global sessions

Description: The number of global sessions has become 20%, 40%, or 60% of the maximum number of sessions.

KDJE34024-W

The number of global sessions is 80% (aa....aa) of the maximum allowable sessions. (J2EE application = bb....bb, context root = cc....cc, max sessions = dd....dd)

aa....aa: Current number of global sessions

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Maximum number of global sessions

Description

The number of global sessions has become 80% of the maximum number of sessions.

If the global sessions are created in a number larger than the estimated number, the validity period of the HTTP session might be long.

Action

To change the validity period of the HTTP session, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34025-W

The number of global sessions has reached the maximum. (J2EE application = aa....aa, context root = bb....bb, max sessions = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Maximum number of global sessions

Description

The number of global sessions has reached the maximum number of sessions.

A new global session cannot be generated until the HTTP session is discarded or until the global session is discarded by the validity period check of the SFO server.

If the global sessions are created in a number larger than the estimated number, the validity period of the HTTP session might be long.

Action

To change the validity period of the HTTP session, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34026-E

An attempt to negotiate with the J2EE server failed because the server ID for the HTTP session is being used on a different J2EE server. (requested J2EE server = aa....aa : bb....bb, connecting J2EE server = cc....cc : dd....dd, server ID = ee....ee)

aa....aa: IP address of the J2EE server with which a connection was requested

bb....bb: Server name of the J2EE server with which a connection was requested

cc....cc: IP address of the J2EE server that uses the server ID of the invalid HTTP session

dd....dd: Server name of the J2EE server that uses the server ID of the invalid HTTP session

ee....ee: Server ID of the invalid HTTP session

Description

An attempt to negotiate with the J2EE server has failed. Another J2EE server is using the server ID of the HTTP session of the J2EE server with which a connection is requested.

You need to set such a value in the server ID of the HTTP session of the J2EE server, which is unique for each J2EE server connected to the SFO server.

Action

Reset the server ID of the HTTP session of the J2EE server, and then restart the J2EE server.

KDJE34027-I

Replication of the global session information will now end. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: Replication of the global session information will be ended.

KDJE34029-W

The server ID for the HTTP session is being used on a different J2EE server. (requested J2EE server = aa....aa : bb....bb, connecting J2EE server = cc....cc : dd....dd, server ID = ee....ee)

aa....aa: IP address of the J2EE server with which a connection was requested

bb....bb: Server name of the J2EE server with which a connection was requested

cc....cc: IP address of the J2EE server that uses the server ID of the identical HTTP sessions

dd....dd: Server name of the J2EE server that uses the server ID of the identical HTTP sessions

ee....ee: Server ID of the identical HTTP sessions

Description

The server ID of the HTTP session of the J2EE server with which a connection is requested is being used in another J2EE server, however, since the property webserver.sfo.negotiation.ignore_serverId is enabled, connection will be established. The connections with already connected J2EE server will also be maintained.

Action

Use the webserver.sfo.negotiation.ignore_serverId property only in a cluster environment. There is no problem if this property is used in a cluster environment.

When used in another environment, the usage of property webserver.sfo.negotiation.ignore_serverId becomes invalid. Change the settings of the SFO server, and then restart the server.

The J2EE server with which a connection is requested is already connected using the server ID being used by another J2EE server. Change the server ID to a value unique to each J2EE server connected to the SFO server, and then restart the server.

KDJE34030-E

The SFO server does not support the functionality requested by the J2EE server. (J2EE server= aa....aa : bb....bb, J2EE application = cc....cc, context root = dd....dd)

aa....aa: IP address of the J2EE server

bb....bb: Server name of the J2EE server

cc....cc: J2EE application name

dd....dd: Context root name

Description: An attempt to negotiate with the J2EE server has failed. The SFO server does not support the functionality requested from the J2EE server.
Action: Upgrade the version of the SFO server to a version that supports the functionality requested by the J2EE server.

KDJE34200-I

The session failover function will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The memory session failover functionality of the Web application with J2EE application name aa....aa, and context root name bb....bb will start.

KDJE34201-E

The web application cannot start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The memory session failover functionality cannot be started. The Web application cannot be started.
Action: Implement the action mentioned in the message output before this message. After taking action, either restart the J2EE server, or restart the J2EE application.

KDJE34202-E

The initialization parameter of the filter used for the session failover function is invalid. (J2EE application = aa....aa, context root = bb....bb, init param = cc....cc, value = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Initialization parameter name

dd....dd: Specified value

Description: The value set in the initialization parameter of the filter for session failover is invalid.
Action: Modify the parameter value cc....cc set in the Deployment Descriptor (web.xml), and then restart.

KDJE34203-E

An invalid property has been specified. (property name = aa....aa, value = bb....bb)

aa....aa: Property name with invalid value

bb....bb: Set value

Description: The property set in the user property file is invalid.
Action: Modify the parameter value aa....aa specified in the user property file (usrconf.properties), and then restart the J2EE server.

KDJE34204-I

The session failover function will now stop. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name used

Description: The memory session failover functionality of the Web application with J2EE application name aa....aa, and context root name bb....bb will terminate.

KDJE34205-I

Connection with the SFO server has finished. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service on the SFO server

Description: The connection with the SFO server has finished.

KDJE34206-W

An attempt to connect with the SFO server has failed. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service on the SFO server

Description

An attempt to connect to the SFO server has failed.

Take action based on the following causes:

The SFO server is not running.
Some error occurred in the communication path with the SFO server.
The IP address or the port number of the CORBA Naming Service invoked in the SFO server specified in the user property file is wrongly specified.
The option -nosecurity is not specified in the cjstartsv command during the startup of the SFO server.
The memory of SFO server is insufficient.
The negotiation cannot be completed within time.

Action

Check the error message output in the J2EE server or the SFO server, and also the working state of the SFO server, and ascertain the cause of failure in connecting.

Take the following actions depending upon the cause:

When the SFO server is not running: Start up the SFO server, and then start the J2EE application.
When a problem exists in the communication path with the SFO server: Remove the problem and then restart the J2EE application.
When the IP address or the port number of the CORBA Naming Service invoked in the SFO server is specified wrongly: Stop the J2EE server once, and then after setting the correct information in the user property file, start the J2EE server.
If an attempt to negotiate with the SFO server has failed:: Specify the correct settings for the J2EE server based on the message KDJE34207-E or KDJE34246-E output in the message log, and for the SFO server based on the message KDJE34008-E, KDJE34026-E, or KDJE34003-I output in the message log. When the settings of the Web application are changed, you must restart the J2EE application, and when the server ID is changed, you must restart the J2EE server.
When the option "-nosecurity" is not specified in the command cjstartsv during the startup of the SFO server: Specify the -nosecurity option, restart the SFO server, and then start the J2EE application.
When the memory required in the SFO server is insufficient: Revise the estimation of memory required in the SFO server.
When the negotiation has timed out: Check the working state of the SFO server and the memory usage of the machine on which the SFO server is running, as well as CPU usage. In the case of the occurrence of a problem, remove the cause, and then restart the J2EE application.

KDJE34207-E

An attempt to negotiate with the SFO server has failed. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, valid parameter = (ee....ee))

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service on the SFO server

ee....ee: Set information of the Web application registered in the SFO server

Description

An attempt to negotiate with the SFO server has failed.

The set information of the Web application registered in the SFO server does not match with the set information of the Web application of the J2EE server with which a connection was attempted.

The parameters responsible for the error, and the set information of the Web application registered in the SFO server will be output in ee....ee, in the following format:

Parameter-name = Setting-value

The contents of the parameter name are as follows:

max sessions: Maximum number of global sessions
max session info size: Maximum value (in bytes) of the size of global session information
max inactive interval: Validity period (in seconds) of the global session
lock timeout: Timeout value for awaiting global session lock
GS control: Control method of the global session
GID cookie name: Name of the HTTP Cookie used to send the global session ID
GID URL param name: Path parameter name of the URL used for sending the global session ID
RW key = Settings-of-keys-for-rewritable-global-session-information
R key = Settings-of-keys-for-read-only-global-session-information
byte array enable: Can the session information in the form of byte arrays be inherited
serializable enable: Can the session information in the form of objects of the serializable class be inherited

When the entire session information registered in the HTTP session is set up either as the rewritable global session information or as the read-only global session information, "RW key(*)" or "R key(*)" will be output respectively, instead of the output in the format parameter-name = set-value.

In the case of multiple errors, the parameter names are output with comma (,) as delimiters.

The set values of the keys of global session information will be output in a semicolon (;) delimited series.

Action

Revise the settings according to the set information of the Web application registered in the SFO server displayed in ee....ee.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34208-I

The connection with the SFO server will now end. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service on the SFO server

Description: The connection with the SFO server was disconnected.

KDJE34209-E

The filter mapping of the filter used for the session failover function is not first in the filter mapping defined for that application. (J2EE application = aa....aa, context root = bb....bb, first mapping filter name = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: First filter class name

Description

The filter mapping of the filter used for session failover is not the first in the filter mapping defined in that application.

Action

The settings of the Deployment Descriptor (web.xml) are invalid.

The mapping definition (<filter-mapping> tag) of the filter used for session failover must be coded first in the filter mapping defined in the application.

Modify the filter mapping definition, and then redeploy.

KDJE34210-E

The URL pattern for the filter mapping of the filter used for the session failover function is invalid. (J2EE application = aa....aa, context root = bb....bb, invalid URL pattern = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Invalid URL pattern

Description

The URL pattern for the filter mapping of the filter used for the session failover is invalid.

Action

The settings of the Deployment Descriptor (web.xml) are invalid.

Specify /* in the URL pattern (<url-pattern> tag) of the filter mapping definition.

Modify the filter mapping definition, and then redeploy.

KDJE34211-E

Mapping of the filter used for the session failover function has been specified more than once. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

Mapping of the filter used for the session failover is specified more than once.

Action

The settings of the Deployment Descriptor (web.xml) are invalid.

Only one filter mapping defined in the application can be defined in the mapping definition (<filter-mapping> tag) of the filter used for session failover.

Modify the filter mapping definition, and then redeploy.

KDJE34212-E

No global session information keys have been set for the initialization parameter of the filter used for the session failover function. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

No global session information keys have been set in the initialization parameter of the filter used for the session failover set in the Deployment Descriptor (web.xml) of the Web application with J2EE application name aa....aa, and context root name bb....bb.

When using the memory session failover function, at least one key must be set in the rewritable global session information, as well as the read-only global session information.

Action

Set the global session information keys in the Deployment Descriptor (web.xml) of the Web application with J2EE application name aa....aa, and context root name bb....bb, and then redeploy.

KDJE34213-E

The global session information from the SFO server is corrupted. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: Global session ID

Description

The global session information acquired from the SFO server cannot be inherited because it is corrupted.

Action

Make sure that the SFO server is running properly, and no problem exists in the communication path between the SFO server and the J2EE server.

If no problem exists, acquire the maintenance information, and then contact maintenance personnel.

KDJE34214-E

The global session information from the SFO server is corrupted. An attempt to transfer the global session has failed. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: Global session ID

Description

The global session information acquired from the SFO server cannot be inherited because it is corrupted.

Take action based on the following causes:

The inherited session information could not be de-serialized.

Action

Based on the action described in the message KDJE34258-E output in the message log from the J2EE server, make sure that no problem exists in the J2EE application, and then take action.

If no problem exists in the J2EE application, take the following actions:

Make sure that the SFO server is running properly, and no problem exists in the communication path between the SFO server and the J2EE server.
If no problem exists in the SFO server, acquire the maintenance information, and then contact maintenance personnel.

KDJE34215-E

A health check of the SFO server has detected that it is down. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

Description

A health check of the SFO server has detected that it is down.

An error occurred in the SFO server.

Action

Check the error on the basis of the log message output by the SFO server, remove the cause of the error, and then restart the SFO server.

KDJE34216-I

A connection with the SFO server is now starting. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

Description: A connection with the SFO server has started.

KDJE34217-I

The SFO server was successfully reconnected. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

Description: An attempt to reconnect to the SFO server was successful.

KDJE34218-W

The global session has already been invalidated. The rewritable global session information was removed from the HTTP session. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, HTTP session ID = ee....ee, global session ID = ff....ff, GS control = gg....gg)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: HTTP session ID

ff....ff: Global session ID

gg....gg: Method of acquiring the global session ID

For cookie, acquire from the HTTP Cookie of the request

For url-rewriting, acquire from the parameters of the request URL

Description

The global session for which a lock request is issued has already been disabled on the SFO server. This global session cannot be used.

The rewritable global session information registered in the HTTP session was deleted.

The factor responsible for this might be a request from the client for using an expired global session.

Action

Confirm that the value of the validity period set in the HTTP session is correct.

To change the validity period of the HTTP session, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34219-W

The global session information in the HTTP session is invalid. The rewritable global session information was removed from the HTTP session. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, HTTP session ID = ee....ee, global session ID = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: HTTP session ID

ff....ff: Global session ID

Description

The global session information created from the HTTP session is invalid. This global session cannot be used.

The rewritable global session information registered in the HTTP session was deleted.

Take action based on the following causes:

The size of the global session information exceeds the maximum size.
An object of a type other than the inheritable session information is registered as the global session information.
An attempt to serialize the object to be inherited has failed.

Action

Take the following actions depending upon the cause:

When the size of the global session information exceeds the maximum size: Among the initialization parameters of the filter used for the memory session failover, confirm that the value set in the parameter GSInfoLengthMax is appropriate, and in the case of a problem, modify to correct settings.
When an object of a type other than the inheritable session information is registered as the global session information: Remove this attribute from the global session information either by changing the application or by changing the settings of the keys of the global session information.
When an attempt to serialize the object to be inherited has failed: Take action based on the information of the message KDJE34256-E output in the message log from the J2EE server.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34220-E

An unexpected error occurred in the initialization processing of the filter used for the session failover function. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

An unexpected error occurred in the initialization of the filter used for the session failover.

Action

Make sure that the SFO server is running properly, and no problem exists in the communication path between the SFO server and the J2EE server.

If no problem exists or if the size estimation functionality of the global session information is used, collect the maintenance information, and then contact maintenance personnel.

KDJE34221-E

An unexpected error occurred in the SFO server. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee, error details = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: Global session ID

ff....ff: Error information

Description

An unexpected error occurred in the SFO server.

Action

The followings might be the causes. Take the required action.

The specified time period until the occurrence of a communication timeout with the SFO server set up in the J2EE server is shorter than required.

Revise the specified timeout period, and change it to the appropriate value.
The SFO server is not running properly.

Check the operating status of the SFO server, and then remove the problem.
A problem occurred in the communication path between the SFO server and the J2EE server.

Remove the cause of the problem occurred in the communication path.

If the problem is still not resolved, acquire the maintenance information, and then contact maintenance personnel.

KDJE34222-E

An error occurred during an attempt to connect with the SFO server. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

Description

An attempt to invoke the SFO server has failed.

Action

Make sure that the SFO server is running properly, and no problem exists in the communication path between the SFO server and the J2EE server.

In the case of a problem in the SFO server, check the error from the log message output by the SFO server, remove the cause of the error, and then restart the SFO server.

In the case of a problem in the communication path between the SFO server and the J2EE server, solve the problem of the communication path. If the communication path becomes normal, the SFO server and the J2EE server will re-connect automatically.

If this message is output when the Web application is started, it might be because of failure in negotiating with the SFO server due to expiry of time. Check the working state of the SFO server, and the state of the machine on which the SFO server is running.

KDJE34223-W

The number of replicable sessions in the SFO server has reached the maximum. The HTTP session will now be invalidated. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description

The HTTP session will be discarded because the number of replicable sessions in the SFO server has reached the maximum value.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (cc....cc).

Action

Revise the maximum number of HTTP sessions or the validity period of the HTTP session.

To change the validity period of the HTTP session, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34224-W

The number of replicable sessions in the SFO server has reached the maximum. The HTTP session will now be invalidated. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description

The HTTP session will be discarded because the number of replicable sessions in the SFO server has reached the maximum value.

When the number of replicable sessions does not reach the maximum, the validity period of the HTTP session might be short.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (cc....cc).

Action

Revise the maximum number of HTTP sessions or the validity period of the HTTP session.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied. Alternatively, change the upper-limit value of the number of HTTP sessions, and then restart.

KDJE34225-E

The size of the global session information exceeds the max size. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, global session ID = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Global session ID

Description

The size of the global session information exceeds the maximum value.

The global session information registered in this HTTP session is not replicated to the SFO server.

Action

Among the initialization parameters of the filter used for the memory session failover, confirm that the value set in the parameter GSInfoLengthMax is appropriate, and in the case of a problem, modify to correct settings.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34226-E

The global session information contains an object that is not permitted. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, global session ID = dd....dd, attribute name = ee....ee, invalid class = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Global session ID

ee....ee: Name of the object registered in the HTTP session that has the type other than the inheritable session information

ff....ff: Class name of the object that has the type other than the inheritable session information

Description

An object of a type other than the inheritable session information is registered in the HTTP session.

The global session information registered in this HTTP session is not replicated to the SFO server.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (cc....cc).

Action

Either change the application or change the key settings of the global session information.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
If a connection is established to the SFO server, restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34228-W

A timeout occurred during a lock request. The rewritable global session information was removed from the HTTP session. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, HTTP session ID = ee....ee, global session ID = ff....ff, locked J2EE server name = gg....gg, locked J2EE server IP = hh....hh)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: HTTP session ID

ff....ff: Global session ID

gg....gg: Server name of the J2EE server in which the global session is locked

hh....hh: IP address of the J2EE server in which the global session is locked

Description

This global session cannot be used because a timeout occurred during a global session lock request to the SFO server.

The rewritable global session information registered in the HTTP session was deleted.

Take action based on the following causes:

Either the J2EE server in which the global session is locked has slowed down, or has stopped.
When a request is sent before the response of the previous request is returned, both the requests will be forwarded to different J2EE servers by the schedule functionality of the load balancer. This occurs when requests using the same session are sent simultaneously while using the frames in a page or when a request is sent twice due to the user operation.

Action

Check the working state of the J2EE server in which the global session is locked. If no problem exists in the working state of the locked J2EE server, confirm that the set value for lock timeout is appropriate.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34229-W

The global session ID was not found in the SFO server. The rewritable global session information was removed from the HTTP session. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, HTTP session ID = ee....ee, global session ID = ff....ff, GS control = gg....gg)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: HTTP session ID

ff....ff: Global session ID

gg....gg: Method of acquiring the global session ID

For cookie, acquire from the HTTP Cookie of the request

For url-rewriting, acquire from the path parameter of the request URL.

Description

This global session cannot be used because it was not found in the SFO server.

The rewritable global session information registered in the HTTP session was deleted.

Take action based on the following causes for not finding the global session:

The validity period has expired.
The processing in the application present on the J2EE server has already deleted the global session.
The global session is lost due to restarting the SFO server.

Action

Confirm that the value of the validity period set in the session is correct.

To change the validity period of the HTTP session, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34230-W

The number of replicable sessions in the SFO server has reached the maximum. The HTTP session will now be invalidated. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The HTTP session will be discarded because the number of replicable sessions in the SFO server has reached the maximum value.

Action

Revise the maximum number of HTTP sessions or the validity period of the HTTP session.

To change the validity period of the HTTP session, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34231-I

The global session information was transferred. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee, HTTP session ID = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: Global session ID

ff....ff: HTTP session ID

Description: Since the global session information present on the J2EE server memory is older than the information present on the SFO server, the session information is inherited.

KDJE34232-W

The rewritable global session information was removed from the HTTP session. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, HTTP session ID =ee....ee, global session ID = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: HTTP session ID

ff....ff: Global session ID

Description

This global session cannot be used because of failure of the SFO server.

The rewritable global session information registered in the HTTP session was deleted.

KDJE34233-W

A timeout occurred during a get request. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee, locked J2EE server name = ff....ff, locked J2EE server IP = gg....gg)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: Global session ID

ff....ff: Server name of the J2EE server in which the global session is locked

gg....gg: IP address of the J2EE server in which the global session is locked

Description

This global session cannot be used because a timeout occurred during a global session lock request to the SFO server. The rewritable global session information registered in the HTTP session was deleted.

Take action based on the following causes:

Either the J2EE server in which the global session is locked has slowed down, or has stopped.
When a request is sent before the response of the previous request is returned, both the requests will be forwarded to different J2EE servers by the schedule functionality of the load balancer. This occurs when requests using the same session are sent simultaneously while using frames in a page or when a request is sent twice due to the user operation.

Action

Check the working state of the J2EE server in which the global session is locked. When no problem exists in the working state of the J2EE server locked, follow the below procedure to change the lock time settings:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34234-W

The global session ID was not found in the SFO server. An attempt to transfer the global session has failed. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee, GS control = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: Global session ID

ff....ff: Method of acquiring the global session ID

For cookie, acquire from the HTTP Cookie of the request

For url-rewriting, acquire from the path parameter of the request URL

Description

The global session cannot be inherited because it was not found in the SFO server.

Take action based on the following causes for not finding the global session:

The validity period has expired.
The processing in the application present on the J2EE server has already deleted the global session.
The global session is lost due to restarting the SFO server.

Action

Confirm that the value of the validity period set in the HTTP session is correct.

To change the validity period of the HTTP session, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34235-E

When the session failover functionality is used, the maximum number of HTTP sessions must be specified. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The upper-limit value for the number of HTTP sessions is not set with the functionality for setting the upper-limit value, and also the default value (infinite) is not being used.

When using the memory session failover function, the upper-limit value for the number of HttpSession needs to be set.

Action

Check the setting of the maximum value for the number of HTTP sessions.

To change the settings, stop the J2EE application running in the J2EE server to validate the set value, and then change the settings. Restart the SFO server, and then start the J2EE application.

KDJE34236-I

The global session information was successfully transferred. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee, new HTTP session ID = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: Global session ID

ff....ff: Newly created HTTP session ID

Description: The global session has been inherited.

KDJE34237-W

An attempt to transfer a global session has failed. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: Global session ID

Description

The global session cannot be inherited because of failure in communication with the SFO server.

Action

Make sure that the SFO server is running properly, and no problem exists in the communication path between the SFO server and the J2EE server.

In the case of a problem in the SFO server, check the error from the log message output by the SFO server, remove the cause of the error, and then restart the SFO server.

In the case of a problem in the communication path between the SFO server and the J2EE server, solve the problem of the communication path. If the communication path becomes normal, the SFO server and the J2EE server will re-connect automatically.

KDJE34238-W

The number of HTTP sessions has reached the maximum for the J2EE server. An attempt to transfer the global session has failed. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: Global session ID

Description

The HttpSession object for inheritance cannot be created because the number of HTTP sessions on the J2EE server has reached maximum value.

The global session cannot be inherited.

Action

Revise the maximum number of HTTP sessions or the validity period of the HTTP session.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Delete the set information of the corresponding Web application registered in the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied. Alternatively, change the upper-limit value of the number of HTTP sessions, and then restart.

To delete the Web application settings on the SFO server, use one of the following methods:

Restart the SFO server.
Stop all the corresponding Web applications, and then wait until all the global sessions created in those applications have been deleted from the SFO server by the functionality for monitoring the validity period of the global session information.

If deletion is performed with this method, the message KDJE34027-I is displayed.

KDJE34239-E

The SFO server was not found. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

Description

An attempt to lookup the SFO server by the Naming Service (dd....dd) has failed.

Take action based on the following causes:

The SFO server is not running properly.
A problem occurred in the communication path between the SFO server and the J2EE server.
The address or the port number of the Naming Service specified in the user property file is invalid.

Action

Make sure that the SFO server is running properly, and no problem exists in the communication path between the SFO server and the J2EE server.

If no problem exists in the SFO server and the communication path, check the setting of the address and the port number of the Naming Service specified in the user property file (usrconf.properties). If the setting is invalid, stop the J2EE server and modify to the correct value, and then restart the J2EE server.

KDJE34240-I

The HTTP cookie of the global session ID was not able to be discarded because the response had already committed. (J2EE application = aa....aa, context root = bb....bb, global session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID whose HTTP Cookie cannot be discarded

Description

The HTTP Cookie of the global session ID shown in cc....cc cannot be discarded because the response to the client had already been committed.

Take action based on the following causes:

The HTTP session is disabled in the Web application
The validity period of the HTTP session has expired

The HTTP Cookie cannot be discarded; therefore, an invalid global session ID might be appended to the requests sent henceforth from the client. If an invalid global session ID is sent to the J2EE server, the following messages are output in the Warning level:

Log output by the J2EE server

KDJE34234-W or KDJE34243-W
Log output by the SFO server when a connection is established to the SFO server

KDJE34017-W

KDJE34241-E

The function that adds the server ID to the HTTP cookie is disabled.

Description

The functionality for adding server ID to the HTTP Cookie is not enabled.

When using the memory session failover function, the functionality for adding server ID to the HTTP Cookie needs to be enabled.

Action

Set true in the parameter webserver.session.server_id.enabled of the user property file (usrconf.properties), and then restart the J2EE server.

KDJE34242-W

The rewritable global session information was deleted from the HTTP session. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, HTTP session ID =ee....ee, global session ID = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: HTTP session ID

ff....ff: Global session ID

Description

This global session cannot be used because of failure in communicating with the SFO server.

The rewritable global session information registered in the HTTP session was deleted.

Action

Make sure that the SFO server is running properly, and no problem exists in the communication path between the SFO server and the J2EE server.

In the case of a problem in the SFO server, check the error from the log message output by the SFO server, remove the cause of the error, and then restart the SFO server.

In the case of a problem in the communication path between the SFO server and the J2EE server, solve the problem of the communication path. If the communication path becomes normal, the SFO server and the J2EE server will re-connect automatically.

KDJE34243-W

The global session has already been invalidated. An attempt to transfer the global session has failed. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee, GS control = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

ee....ee: Global session ID

ff....ff: Method of acquiring the global session ID

For cookie, acquire from the HTTP Cookie of the request

For url-rewriting, acquire from the path parameter of the request URL

Description

The global session for which there is a request to acquire information is already disabled on the SFO server.

The global session cannot be inherited.

The reason might be a request sent from the client for using a global session whose validity period has expired.

Action

Confirm that the value of the validity period set in the HTTP session is correct.

To change the validity period of the HTTP session, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Restart the SFO server.
Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34244-E

The same name exists in the GSInfoKey-RW or GSInfoKey-R parameter. (J2EE application = aa....aa, context root = bb....bb, invalid session info key = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Several existing key names of the global session information

Description

There are several key names for the same global session.

Action

The settings of the Deployment Descriptor (web.xml) are invalid.

The same key cannot be specified in the initialization parameters (<init-param> tag) GSInfoKey-RW and GSInfoKey-R of the filter used for the session failover.

Revise the settings of the key name indicated in cc....cc such that it is unique among all the key names specified in GSInfoKey-RW and GSInfoKey-R, and then restart the J2EE application in the J2EE server.

KDJE34245-E

An unexpected error occurred during connection processing to the SFO server. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

Description

An unexpected error occurred during the connection processing to the SFO server.

Action

Make sure that the SFO server is running properly, and no problem exists in the communication path between the SFO server and the J2EE server.

If no problem exists, acquire the maintenance information, and then contact maintenance personnel.

KDJE34246-E

An attempt to negotiate with the SFO server failed because the server ID for the HTTP session is being used on another server. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, server ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service on the SFO server

ee....ee: Server ID of the invalid HTTP session

Description

An attempt to negotiate with the SFO server has failed.

Another J2EE server is using the server ID appended to the session ID of the HTTP session set in the J2EE server.

Action

In the server ID appended to the session ID of the HTTP session of the J2EE server, set a unique value for each J2EE server connected to the SFO server, and then restart the J2EE server.

KDJE34247-E

The SFO server was not found. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

Description

An attempt to lookup the SFO server by the Naming Service (dd....dd) has failed.

Take action based on the following causes:

The SFO server is not running properly.
A problem occurred in the communication path between the SFO server and the J2EE server.
The address or the port number of the Naming Service specified in the user property file is invalid.

Action

Make sure that the SFO server is running properly, and no problem exists in the communication path between the SFO server and the J2EE server.

If no problem exists in the SFO server and the communication path, check the setting of the address and the port number of the Naming Service specified in the user property file (usrconf.properties). If the setting is invalid, stop the J2EE server and modify to the correct value, and then restart the J2EE server.

KDJE34248-E

An error occurred during an attempt to connect with the SFO server. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

Description

An attempt to invoke the SFO server has failed.

Action

Make sure that the SFO server is running properly, and no problem exists in the communication path between the SFO server and the J2EE server.

In the case of a problem in the SFO server, check the error from the log message output by the SFO server, remove the cause of the error, and then restart the SFO server.

In the case of a problem in the communication path between the SFO server and the J2EE server, solve the problem of the communication path. If the communication path becomes normal, the SFO server and the J2EE server will re-connect automatically.

KDJE34249-E

An unexpected error occurred during the processing to connect to the SFO server. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service

Description

An unexpected error occurred during the connection processing to the SFO server.

Action

Make sure that the SFO server is running properly, and no problem exists in the communication path between the SFO server and the J2EE server.

In the case of a problem in the SFO server, check the error from the log message output by the SFO server, remove the cause of the error, and then restart the SFO server.

In the case of a problem in the communication path between the SFO server and the J2EE server, solve the problem of the communication path. If the communication path becomes normal, the SFO server and the J2EE server will re-connect automatically.

KDJE34250-E

The specified SFO server was not found in the user property file. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name specified in the Deployment Descriptor (web.xml)

Description

The SFO server name set in the initialization parameters of the filter used for the session failover of the Deployment Descriptor (web.xml) was not found in the SFO server names defined in the user property file.

Action

Check the setting of the Deployment Descriptor (web.xml) and the user property file, and then modify to the correct value.

To change the settings of the Deployment Descriptor (web.xml), you must stop and delete the J2EE application running in the J2EE server, and then re-create and restart the J2EE application. To change the settings of the user property, you must restart the J2EE server.

KDJE34251-E

The required property for the session failover function has not been specified. (property name = aa....aa)

aa....aa: Required property name

Description: The property (aa....aa) required for using the memory session failover function is not set.
Action: Add the required settings in user properties, and then restart the J2EE server.

KDJE34252-E

A memory shortage occurred in the SFO server. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service on the SFO server

Description

A memory shortage occurred in the SFO server during the negotiation with the SFO server. Take action based on the following causes:

The memory of SFO server is insufficient.
The maximum size of the global session information set in the Web applications on the J2EE server is large.
The maximum value for the number of HttpSession set in the J2EE server is inappropriately large.

Action

Take the following actions depending upon the cause:

When the memory of the SFO server is insufficient

Revise the estimation of the memory required in the SFO server. The memory required in the SFO server is proportionate to the maximum number of global sessions, and the maximum size of the global session information.

In the case of a problem in setting the required memory, set the appropriate value in the option definition file (usrconf.cfg) for the J2EE server, and then restart the SFO server.

When the maximum size of the global session information is large

Revise the maximum size of the global session information set in the Web application. In the case of a problem in the maximum size of the global session information, set the appropriate value in the Deployment Descriptor (web.xml) of the Web application, and then redeploy the J2EE application.

When the maximum value of the number of HttpSession is large

Revise the maximum value of the number of HttpSession set in the Web application. If the maximum value of the number of HttpSession is more than required, change to an appropriate value, and then restart the J2EE application.

KDJE34253-E

A timeout occurred during communication with the SFO server. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service on the SFO server

Description

A timeout occurred during the negotiation with the SFO server. Take action based on the following causes:

The SFO server has a large load.
The memory of SFO server is insufficient.

Action

Take the following actions depending upon the cause:

When the SFO server has a large load

Check the state of the SFO server and the J2EE server, as well as the contents of the output log, and then remove the cause of the error.

When the memory of the SFO server is insufficient

Revise the estimation of the memory required in the SFO server. The memory required in the SFO server is proportionate to the maximum number of global sessions, and the maximum size of the global session information.

If the physical memory of the host on which the SFO server is running is less, some time might be taken for securing the memory. By specifying the amount of memory to be secured during the initialization in the option definition file (usrconf.cfg) for the J2EE server, the time taken for securing the memory can be shortened.

KDJE34254-E

The SFO server does not support necessary functionality. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

dd....dd: Address and port number of the Naming Service on the SFO server

Description: An attempt to negotiate with the SFO server has failed. The SFO server does not support the necessary functionality.
Action: Upgrade the version of the SFO server to a version that supports the necessary functionality.

KDJE34255-W

The global session information contains an object that is not permitted. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, global session ID = dd....dd, attribute name = ee....ee, invalid class = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Global session ID

ee....ee: Name of the object registered in the HTTP session that has the type other than the inheritable session information

ff....ff: Class name of the object that has the type other than the inheritable session information

Description

An object of a type other than the inheritable session information is registered in the HTTP session. This object is ignored and is not replicated to the SFO server.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (cc....cc).

Action

An object of a type other than the inheritable session information is registered in the HTTP session, and will be inherited.

Check the contents of the application and also the key settings of the global session information.

KDJE34256-E

An attempt to serialize the global session information has failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, global session ID = dd....dd, attribute name = ee....ee, invalid class = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Global session ID

ee....ee: Name of the object registered in the HTTP session that failed to be serialized

ff....ff: Class name of the object that failed to be serialized

Description

An attempt to serialize the global session information has failed. The information of this HTTP session will not be replicated to the SFO server.

Take action based on the following causes of failure in serialization:

The object referenced from the object registered in the HTTP session (object of a serializable class) is not from a serializable class.
The writeObject(java.io.ObjectOutputStream out) method is implemented, and an exception occurred during the serialization.

Action

Determine the cause of the failure in serialization based on the contents of the stack trace output with the message ID KDJE34257-E in the Web servlet log, and then take either of the following actions:

Remove the erroneous object from the target objects to be replicated.
Change the application, and then remove the cause of the error.

KDJE34257-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the serialization of the global session information will be output row-wise.

Take action based on the following causes of failure in the serialization:

The object referenced from the object registered in the HTTP session (object of a serializable class) is not from a serializable class.
The writeObject(java.io.ObjectOutputStream out) method is implemented and an exception occurred during the serialization.

Action

Determine the cause of the failure in serialization based on the contents of the stack trace, and then take either of the following actions:

Remove the object in which the error has occurred from the effect of redundancy.
Change the application, and then remove the cause of the error.

KDJE34258-E

An attempt to deserialize the global session information has failed. (J2EE application = aa....aa, context root = bb....bb, global session ID = cc....cc, attribute name = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

dd....dd: Name of the object registered in the HTTP session that failed to be deserialized

Description

The global session information collected from the SFO server could not be inherited because of an attempt to deserialize the global information has failed.

Take action based on the following causes of failure in the deserialization:

The application is different during the serialization and the deserialization, and the change that causes a failure in the deserialization is added to the application.
The readObject() method is implemented and an error occurred internally.

Action

Determine the cause of the failure in deserialization based on the contents of the stack trace output with the message ID KDJE34259-E in the Web servlet log, and then take action.

KDJE34259-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the de-serialization of the global session information will be output row-wise.

Take action based on the following causes of failure in de-serialization:

The application is different during serialization and de-serialization, and the change that causes failure in de-serialization is added to the application.
The readObject() method is implemented, and an error occurred internally.

Action

Determine the cause of failure in de-serialization based on the contents of the stack trace, and then take action.

KDJE34260-I

The global session information was created. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, size(byte) = dd....dd, HTTP session ID = ee....ee, global session ID = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Size (in bytes) of the global session information

ee....ee: HTTP session ID

ff....ff: Global session ID

Description

The size (in bytes) of the global session information replicated to the SFO server is indicated.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (ee....ee).

KDJE34261-I

The session information was serialized. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, attribute name = dd....dd, class name = ee....ee, size(byte) = ff....ff, HTTP session ID = gg....gg, global session ID = hh....hh)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Name of the object registered in the HTTP session

ee....ee: Class name of the object registered in the HTTP session

ff....ff: Size (in bytes) of the global session information created from the objects registered in the HTTP session

gg....gg: HTTP session ID

hh....hh: Global session ID

Description

The size (in bytes) of the global session information of a single object replicated by the memory session failover functionality is indicated.

The output size includes the size of the key names and the delimiting characters.

KDJE34262-E

The size of global session information exceeded 1,048,576 bytes during its creation. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, attribute name = dd....dd, class name = ee....ee, size(byte) = ff....ff, HTTP session ID = gg....gg, global session ID = hh....hh)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Name of the object registered in the HTTP session that caused an increase in the size

ee....ee: Class name of the object that caused an increase in the size

ff....ff: Size (in bytes) of a single instance of the global session information of the object that caused an increase in the size

gg....gg: HTTP session ID

hh....hh: Global session ID

Description

The size of the global session information that was being created exceeded 1,048,576 bytes. The memory session failover functionality does not support the global session information that exceeds 1,048,576 bytes.

Creation of the global session information will be suspended.

Action

Check the cause for the increase in the size of the global session information, and take either of the following actions:

When unnecessary information is to be inherited: Set up the initialization parameters (<init-param> tag) GSInfoKey-RW or GSInfoKey-R of the filter used for the session failover defined in the Deployment Descriptor (web.xml), and specify only the necessary session information as the target for inheritance.
When the size of the session information to be inherited is large: When the inheritance of the objects of a serializable class is enabled, the objects registered as the session information might include some unnecessary information. In such a case, change the application, and then remove the unnecessary information by changing the objects registered in the HTTP session to reduce the size.

KDJE34263-I

The function for outputting the size of the global session information will now be enabled. The redundant global session information is invalid. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The size output functionality of the global session information will be enabled.

The replication of the global session information will not be performed.

KDJE34264-E

The settings for GSInfoKey-RW or GSInfoKey-R are inconsistent. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The GSInfoKey-RW and GSInfoKey-Re key values specified in the initialization parameters (<init-param> tag) of the filter used for the session failover function conflict.

The settings of both the keys, the key of the rewritable global session and the key of the read-only global session, are specified for the entire session information registered in the HTTP session.

Action

When the entire session information registered in the HTTP session is to be inherited, specify either the rewritable global session information or the read-only global session information.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34265-I

The parameter set to the session failover function is shown as follows. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, max sessions = ee....ee, max session info size = ff....ff, max inactive interval = gg....gg, lock timeout = hh....hh, GS control = ii....ii, GID cookie name = jj....jj, GID URL param name = kk....kk, ll....ll, mm....mm, replicatable type = nn....nn)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name^#

dd....dd: Address and port number of the Naming Service on the SFO server^#

ee....ee: Maximum number of global sessions^#

ff....ff: Maximum value (in bytes) of the size of global session information^#

gg....gg: Validity period (in seconds) of the global session

hh....hh: Timeout value for awaiting global session lock^#

ii....ii: Control method of the global session

cookie: Control is performed by using an HTTP Cookie.

url-rewriting: Control is performed by using URL rewriting.

both: Control is performed by using both the HTTP Cookie and the URL rewriting.

jj....jj: Name of the HTTP Cookie used for sending the global session ID when ii....ii is either cookie or both. Null character string, when ii....ii is url-rewriting

kk....kk: Path parameter name of the URL used for sending the global session ID when ii....ii is either url-rewriting or both. Null character string, when ii....ii is cookie

ll....ll: Settings of keys for rewritable global session information

The set information of the keys is output in either of the following formats:

RW key = Settings-of-keys-for-rewritable-global-session-information

The set values of the keys of global session information will be output in a semicolon (;) delimited series.

When the GSInfoKey-RW parameter is omitted, a null character string will be output in the set value of the key.
RW key(*)

When the entire session information registered in the HTTP session, except the information registered in the key specified in the GSInfoKey-R parameter, is set up as the rewritable global session information, "RW key(*)" will be output.

mm....mm: Settings of keys for read-only global session information

The set information of the key is output in either of the following formats:

R key = Settings-of-keys-for-read-only-global-session-information

The set values of the keys of global session information will be output in a semicolon (;) delimited series.

When the GSInfoKey-R parameter is omitted, a null character string will be output in the set value of the key.
R key(*)

When the entire session information registered in the HTTP session, except the information registered in the key specified in the GSInfoKey-RW parameter, is set up as the rewritable global session information, "R key(*)" will be output.

nn....nn: Type of the inheritable session information

String: Only objects of the java.lang.String class

String or byte[]: Objects or byte arrays of the java.lang.String class

Serializable: Objects of a serializable class

#: When the size estimation functionality of the global session information is enabled, a null character string is output.
Description: The settings of the memory session failover functionality are indicated.

KDJE34266-I

Received global session ID is being used by different HTTP session.(J2EE application = aa....aa, context root = bb....bb, using HTTP session ID = cc....cc, received HTTP session ID = dd....dd, global session ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session that is using the global session ID

dd....dd: Session ID of the HTTP session sent by the request

ee....ee: Global session ID

Description: A request containing a global session ID that is in use by another HTTP session is received. A new global session ID will be issued for this request.

KDJE34300-I

The session fail over (DB) function will now start. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description: The database session failover functionality of the Web application with J2EE application name aa....aa, and context root name bb....bb will start.

KDJE34301-E

The session fail over (DB) function cannot start. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description: The database session failover functionality cannot be started. The Web application cannot be started.
Action: Implement the action mentioned in the message output before this message. After taking the action, either restart the J2EE server or restart the J2EE application.

KDJE34302-I

The default value is applied to the application ID. (default value = aa....aa)

aa....aa: Default value

Description: The default value aa....aa is applied to the application identifier.

KDJE34303-E

When the session fail over (DB) function is used, the maximum number of HTTP sessions must be specified. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description

The upper-limit value for the number of HttpSession objects is not set with the functionality for setting the upper-limit value, and also the default value (infinite) is not being used.

When using the database session failover functionality, a valid value must be set up for the upper-limit value of the number of HttpSession objects.

Starting the Web application will be canceled.

Action

After setting up the upper-limit value for the number of HttpSession objects in the Web application, start the J2EE application.

KDJE34304-E

The resource registered is not the DB Connector. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

Description

The resource registered with the optional name indicated by cc....cc is not a DB Connector.

The startup of the Web application will be interrupted because the database session failover functionality cannot be started.

Action

Check the resource registered with the optional name indicated by cc....cc. If the registered resource is not a DB Connector, release the registered resource, and register a DB Connector.

After the preparations for the DB Connector are complete, start the J2EE application.

KDJE34305-E

The DB Connector is not found. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

Description

The DB Connector used with the database session failover functionality is not registered with the specified name.

The startup of the Web application will be interrupted because the database session failover functionality cannot be started.

Action

Make sure that the DB Connector is registered with the name indicated in cc....cc. If the DB Connector is not registered, register the DB Connector to be used in the J2EE server, and set up an optional name.

If the optional name set up in the DB Connector is wrong, specify the correct optional name.

Remove the problem, and then start the Web application.

KDJE34306-I

An attempt to negotiate has succeeded. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, parameter = (dd....dd))

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Set information of the Web application

Description

The negotiation processing executed during the start of the database session failover functionality has succeeded.

The set information dd....dd of the database session failover functionality that is set up in the Web application is output in the following format:

Parameter-name = Setting-value

The contents of the parameter name are as follows:

max sessions: Maximum number of HttpSession objects

max attribute data size: Maximum size (in bytes) of the attribute information of the HTTP session

max inactive interval: Validity period of the HTTP session defined in web.xml

exclude extensions: Extensions for excluding the database session failover functionality^#

integrity mode: Setup value of the integrity assurance mode

session read only uris: Setup value of the read-only request definition functionality of the HTTP session^#

thread control queue enabled: Setup value for determining whether or not to return error 503 when the free space of the pending queue for controlling concurrently executing thread count of each Web application is insufficient

exception type backcompat: Setup value of the compatibility option of the exception occurred when the HttpServletRequest#getSession method is executed in the error page of the requests for which DBSFO functionality is to be disabled

session persistence version: Version of the DBSFO functionality

#: If multiple setup values exist, output the values in a series with comma (,) as the delimiter.

KDJE34307-E

An attempt to negotiate has failed. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, invalid parameter = (dd....dd), valid parameter = (ee....ee))

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Set information that caused the negotiation to fail

ee....ee: Correct set information

Description

The negotiation processing executed during the start of the database session failover functionality has failed. The set information of the Web application saved in the database does not match the set information of the Web application for which an attempt has made to start.

Starting the Web application will be canceled.

For the erroneous parameters, the currently settings is output in dd....dd, and the information saved in the database is output in ee....ee, in the following format:

Parameter-name = Setting-value

The contents of the parameter name are as follows:

max sessions: Maximum number of HttpSession objects
max attribute data size: Maximum size (in bytes) of the attribute information of the HTTP session
max inactive interval: Validity period of the HTTP session defined in web.xml
exclude extensions: Extensions for excluding the database session failover functionality^#
integrity mode: Setup value of the integrity assurance mode
session read only uris: Setup value of the read-only request definition functionality of the HTTP session^#
thread control queue enabled: Setup value for determining whether or not to return error 503 when the free space of the pending queue for controlling concurrently executing thread count of each Web application is insufficient
exception type backcompat: Setup value of the compatibility option of the exception occurred when the HttpServletRequest#getSession method is executed in the error page of the requests for which DBSFO functionality is to be disabled
session persistence version: Version of the DBSFO functionality

In the case of multiple errors, the multiple parameter names are output with comma (,) as delimiters.

#: If multiple setup values exist, output the values in a series with comma (,) as the delimiter.

Action

Revise the settings in accordance with the settings of the Web application saved in the database, as displayed in ee....ee.

For details, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

KDJE34308-W

The table used by the session fail over (DB) function is not found in the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, table = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Name of the table that could not be found

Description

The table used by the database session failover functionality is not found in the database.

Starting the Web application will be canceled.

Action

Make sure that the table with the name output in dd....dd exists in the database connected to the DB Connector.

If the database connected to the DB Connector is invalid, change the settings of the DB Connector to the correct information.

If the table is not created in the database, create the table to be used in the database session failover functionality. For details, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

KDJE34309-E

The table used by the session fail over (DB) function is illegal. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, table = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Name of the table with invalid contents

Description

The contents of the table used in the database session failover functionality are invalid. The database session failover functionality cannot be started.

Starting the Web application will be canceled.

Action

In the case of existence of replicated Web applications that are in the running state, stop all applications.

If the name of the table, that stores the session information, is output in the name of the table with invalid contents, make sure that the maximum value of the number of HttpSession objects set up in the Web application matches the value specified in the SQL file for creating the table that is used during the creation of the table.

Delete, and re-create all three types of tables for the database session failover functionality used by this Web application. For details, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

Start the Web application after re-creating the table.

KDJE34310-I

The watch of the expiration date of the global session information begins. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The monitoring of the validity period of the global session information in the database will start.

KDJE34311-I

Because the expiration date had been passed, the global session information was deleted. (J2EE application = aa....aa, context root = bb....bb, deleted global session information no = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Number of instances of the deleted global session information

Description: Based on the result of the monitoring of the validity period, the global session information for which the validity period had expired was deleted.

KDJE34312-W

An error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information about the exception that occurred

Description

A failure occurred in the communication with the database.

Action

Make sure that the database is operating properly, no problem has occurred in the communication path between the database and J2EE server, and no mistakes exist in the change contents of the SQL file used for creating the table.

If an error occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, solve the problem of the communication path. If a problem occurs in the communication path, the exclusion in the database might not have been released. Before restarting a business, check the invalid connections, and release the unreleased exclusion.

If the change contents of the SQL file used for creating the table are different from the settings of the application, either re-create the table to match the contents or change the settings of the application. For details on the procedure for changing the settings, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

If no problem exists in the change contents of the database, communication path, and the SQL file used for creating the table, check if the settings of the timeout period of the DB Connector connection are correct.

If a short timeout period is set up for the connection, a timeout might occur before the completion of the recovery process, when an error occurs in the database.

Tune the parameters of the DB Connector after considering the recovery period of the database.

KDJE34314-W

An attempt to connect with the database has failed. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information about the exception that has occurred

Description

An attempt to establish a connection to the database has failed.

Action

Make sure that the database is operating properly, and no problem has occurred in the communication path between the database and J2EE server.

If an error occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, solve the problem of the communication path. If a problem occurs in the communication path, the exclusion in the database might not have been released. Before restarting a business, check the invalid connections, and release the unreleased exclusion.

If no problem exists in the database and communication path, check if the settings of the timeout period of the DB Connector connection are correct.

If a short timeout period is set up for the connection, a timeout might occur before the completion of the recovery process, when an error occurs in the database.

Tune the parameters of the DB Connector after considering the recovery period of the database.

KDJE34315-W

The global session information was not found in the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, HTTP session ID = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: HTTP session ID

Description

The global session information was not found in the database.

The HTTP session corresponding to the received session ID has already been invalidated.

Action

A request for using an HTTP session, in which the validity period has expired, is received from the client. Confirm that the value of the validity period set in the HTTP session is correct.

The procedure for changing the validity period of the HTTP session is as follows:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Re-create the three tables used in the database session failover functionality of the database.
Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the business application.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34316-W

The number of replicable sessions in the database has reached the maximum. The HTTP session will now be invalidated. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description

A new session cannot be created because the maximum number of replicable sessions in the database is reached. The created HTTP session will be invalidated.

Action

Check if the upper-limit value of the number of HttpSession objects set up in the Web application or the validity period of an HTTP session is correct.

For details, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

KDJE34317-W

The attribute that cannot be serialized is contained in the HTTP session. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Name of attribute that cannot be serialized

ee....ee: Class name of the object that cannot be serialized

Description

An attribute, that cannot be serialized, is registered in the HTTP session. This attribute will be ignored and not be replicated in the database.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (cc....cc).

Action

An object that is not from a serializable class is registered in the HTTP session as an attribute. Check the contents of the Web application.

KDJE34318-E

An attempt to serialize the attribute information has failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Name of the attribute that failed to be serialized

ee....ee: Class name of the object that failed to be serialized

Description

An attempt to serialize the attribute information of the HTTP session has failed. The information of this HTTP session will not be replicated in the database.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (cc....cc).

Action

Determine the cause of the failure in serialization based on the contents of the stack trace output with the message ID KDJE34319-E in the Web servlet log, and then take either of the following actions:

Remove the erroneous object from the attributes of the HTTP session.
Change the Web application, and then remove the cause of the error from the object that failed to be serialized.

Take action based on the following causes of the failure in serialization:

The object referenced from the object of the attribute that failed to be serialized was not from a serializable class.
The writeObject(java.io.ObjectOutputStream out) method is implemented, and an exception occurred during serialization.

KDJE34319-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the serialization processing of the attribute information of the HTTP session will be output in each line.

Action

Determine the cause of failure in the serialization based on the contents of the stack trace, and then take either of the following actions:

Remove the erroneous object from the attributes of the HTTP session.
Change the Web application, and then remove the cause of the error from the object that failed to be serialized.

Take action based on the following causes of the failure in serialization:

The object referenced from the object of the attribute that failed to be serialized was not from a serializable class.
The writeObject(java.io.ObjectOutputStream out) method is implemented, and an exception occurred during the serialization.

KDJE34320-E

The size of the attribute information exceeds the max size. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description

The size of the attribute information of the HTTP session exceeds the maximum value. The information of this HTTP session will not be replicated to the database.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (cc....cc).

Action

Check if the value, specified in the maximum size of the attribute information of the HTTP session, is correct, and if a problem exists, change to an appropriate value. For details, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

KDJE34321-I

The global session information was successfully transferred. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description: The global session information was inherited successfully.

KDJE34322-I

The global session information was transferred. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description: Because the information of the HTTP session in the memory of the J2EE server is older than the information in the database, the global session information will be inherited.

KDJE34324-W

An attempt to transfer the global session information has failed, because an error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information about the exception that occurred

Description

The global session information cannot be inherited because of failure in communication with the database.

Action

Make sure that the database is operating properly and no problem has occurred in the communication path between the database and the J2EE server.

If an error occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, solve the problem. When the problem occurs, the mutual exclusion of the database might not be released. Before restarting a business, check the invalid connections, and release the unreleased exclusion.

If no problem exists in the database and communication path, check if the settings of the timeout period of the DB Connector connection are correct.

If a short timeout period is set up for the connection, a timeout might occur before the completion of the recovery process, when an error occurs in the database.

Tune the parameters of the DB Connector after considering the recovery period of the database.

KDJE34325-W

An attempt to transfer the global session information has failed, because the global session information was not found in the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, HTTP session ID = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: HTTP session ID

Description

Either the validity period of the HTTP session corresponding to the HTTP session ID received from the client has expired or the HTTP session has already been invalidated during the processing in the Web application running on the J2EE server. The global session information is not found in the database.

The global session cannot be inherited.

Action

A request for using an HTTP session in which the validity period has expired is received from the client.

Confirm that the value of the validity period set in the HTTP session is correct.

The procedure for changing the validity period of the HTTP session is as follows:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
Re-create the three tables used in the database session failover functionality of the database.
Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the business application.
Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34326-E

An attempt to deserialize the global session information has failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Name of the attribute that failed to be deserialized

Description

The session could not be inherited because an attempt to deserialize the global session information, acquired from the database, has failed.

Action

Determine the cause of the failure in deserialization based on the contents of the stack trace output with the message ID KDJE34327-E in the Web servlet log, and then take action:

Take action based on the following causes of the failure in deserialization:

The Web application is different during the serialization and the deserialization, and the change that causes failure in the deserialization is added to the application.
The readObject() method is implemented, and an error occurred internally.

KDJE34327-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the de-serialization of the global session information will be output row-wise.

Action

Determine the cause of the failure in deserialization based on the contents of the stack trace, and then take action.

Take action based on the following causes of the failure in deserialization:

The application is different during the serialization and the deserialization, and the change that causes the failure in deserialization is added to the application.
The readObject() method is implemented, and an error occurred internally.

KDJE34328-E

The global session information from the database is illegal. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

Description

The contents of the global session information acquired from the database are invalid.

Action

Make sure that the database is running properly, and no problem exists in the communication path between the database and the J2EE server.

Also make sure that no invalid operation is performed in the database from the outside.

If no problem exists, acquire the maintenance information, and then contact maintenance personnel.

KDJE34329-I

The function for outputting the size of the attribute information will now be enabled. The redundant global session information is invalid. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The functionality for estimating the size of the attribute information of the HTTP session will be enabled.

The global session information will not be replicated.

KDJE34330-I

The attribute information was created. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, size(byte) = dd....dd, HTTP session ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Size (in bytes) of the attribute information of the HTTP session

ee....ee: HTTP session ID

Description

The size (in bytes) of the attribute information of the HTTP session that is replicated in the database is indicated.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (ee....ee).

KDJE34331-I

An attribute was serialized. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, attribute name = dd....dd, class name = ee....ee, size(byte) = ff....ff, HTTP session ID = gg....gg)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Name of the attribute registered in the HTTP session

ee....ee: Class name of the attribute registered in the HTTP session

ff....ff: Size (in bytes) of the byte array created by serializing the attributes registered in the HTTP session

gg....gg: HTTP session ID

Description

The size (in bytes) after serialization of one attribute registered in the HTTP session replicated by the database session failover functionality is indicated.

The output size includes the information about the names of the attributes.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (gg....gg).

KDJE34332-E

The size of global session information exceeded 10,485,760 bytes during its creation. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, attribute name = dd....dd, class name = ee....ee, size(byte) = ff....ff, HTTP session ID = gg....gg)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Name of the attribute that caused an increase in the size

ee....ee: Class name of the attribute that caused an increase in the size

ff....ff: Size (in bytes) of one attribute that caused an increase in the size

gg....gg: HTTP session ID

Description

The size of the created attribute information exceeded 10,485,760 bytes. The database session failover functionality does not support the attribute information of an HTTP session that exceeds 10,485,760 bytes.

Creation of the global session information will be suspended.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (gg....gg).

Action

Some unnecessary information might be registered in the HTTP session as attributes. In such cases, change the application, and then remove the unnecessary attributes registered in the HTTP session to reduce the size.

KDJE34335-E

The memory session failover function and the database session failover function cannot be enabled at the same time.

Description

The memory session failover functionality and the database session failover functionality cannot be used simultaneously.

Starting the Web application will be canceled.

Action

Apply either one of the memory session failover functionality or the database session failover functionality in accordance with the system configuration and requirements.

KDJE34336-W

An error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

Description

An error occurred in the database during the monitoring processing of the validity period.

Action

Make sure that the database is operating properly, no problem has occurred in the communication path between the database and J2EE server, and no mistakes exist in the change contents of the SQL file used for creating the table.

If an error occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, solve the problem. When the problem occurs, the mutual exclusion of the database might not be released. Before restarting a business, check the invalid connections, and release the unreleased exclusion.

If a mistake exists in the settings of the SQL file used for creating the table or in the settings of the application, revise the settings. For details on the procedure for changing the settings, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

If no problem exists in the database, communication path, and SQL file used for creating the table, check if the settings of the timeout period of the DB Connector connection are correct. If a short timeout period is set up for the connection, a timeout might occur before the completion of the recovery process, when an error occurs in the database. Tune the parameters of the DB Connector after considering the recovery period of the database.

KDJE34337-W

The attribute that cannot be serialized is contained in the HTTP session. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Name of attribute that cannot be serialized

ee....ee: Class name of the object that cannot be serialized

Description

An attribute, that cannot be serialized, is registered in the HTTP session. This attribute will be ignored, and will not be replicated to the database.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (cc....cc).

Action

An object that is not from a serializable class is registered in the HTTP session as an attribute. Check the contents of the Web application.

KDJE34338-E

An attempt to serialize the global session information has failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Name of the attribute that failed to be serialized

ee....ee: Class name of the object that failed to be serialized

Description

An attempt to serialize the attribute information of the HTTP session has failed. The information of this HTTP session will not be replicated to the database.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (ee....ee).

Action

Determine the cause of the failure in serialization based on the contents of the stack trace output with the message ID KDJE34319-E in the Web servlet log, and then take either of the following actions:

Remove the erroneous object from the attributes of the HTTP session.
Change the Web application, and then remove the cause of the error from the object that has failed to be serialized.

Take action based on the following causes of the failure in serialization:

The object referenced from the object of the attribute that failed to be serialized was not from a serializable class.
The writeObject(java.io.ObjectOutputStream out) method is implemented, and an exception occurred during the serialization.

KDJE34339-E

When the session fail over (DB) function is used, the session cookie delete function must be enabled. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description

The HTTP Cookie deletion functionality of the HTTP session is disabled.

When using the database session failover functionality, the HTTP Cookie deletion functionality of the HTTP session must be enabled.

Starting the Web application will be canceled.

Action

After enabling the HTTP Cookie deletion functionality of the HTTP session, start the J2EE application.

To enable the HTTP Cookie deletion functionality of the HTTP session, set up false in the webserver.session.delete_cookie.backcompat key of the user property file for the J2EE server (usrconf.properties), and then restart the J2EE server.

KDJE34340-E

The specified application ID is already being used by another application. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc, table = dd....dd, J2EE application in table = ee....ee, context root in table = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

dd....dd: Name of the application information table

ee....ee: J2EE application name registered in the application information table

ff....ff: Context root name registered in the application information table

Description

The specified application identifier is already in use by another application.

Action

Take action with any of the following methods:

When you want to start an application same as the existing application

Make sure that the J2EE application name or the context root name are not different from the information of the same application that is already running. If the information is different, revise the settings, and start the application.
When you want to start an application different from the existing application

In the Web application, specify an application identifier that is not in use by another application, re-create the table, and then start the application. For details about how to create the table, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

KDJE34341-W

A property of the session fail over (DB) function controlled by the URI is invalid. The URI will be ignored. (URI = aa....aa)

aa....aa: Invalid URI

Description

An invalid URI is specified in the property for stopping the database session failover functionality by URI. The specified URI will be ignored.

Action

Check whether an invalid URI is specified in the property for stopping the database session failover functionality by URI, and then specify a valid URI. The following URIs are invalid:

Not normalized.
The first character is not a forward slash (/).

KDJE34342-I

The database integrity mode of the session failover (database) functionality has been enabled. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description: The integrity assurance mode of the database session failover functionality is enabled.

KDJE34343-I

The database integrity mode of the session failover (database) functionality has been disabled. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description: The integrity assurance mode of the database session failover functionality is disabled.

KDJE34344-I

Transfer of global sessions at Web application startup will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: Start the process for inheriting the global session information executed during the startup of the Web application.

KDJE34345-W

Transfer of global sessions at Web application startup could not start. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information about the exception that occurred

Description

The process of inheriting the global session information during the startup of the Web application could not be started because a failure occurred during database communication.

Action

Make sure that the database is operating properly and that no problem has occurred in the communication path between the database and J2EE server.

If a failure occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, solve the problem of the communication path. If a problem occurs in the communication path, the exclusion in the database might not be released. Before restarting the business, check the invalid connections, and release the unreleased exclusion.

If no problem exists in the database and the communication path, make sure that the settings of the connection timeout of the DB Connector are correct. If the settings of the connection timeout is short, a timeout might occur before completing the recovery process when a failure occurs in the database. Tune the parameters of the DB Connector in view of the database recovery time.

Note that when this message is output, the global session information continues to remain in the database until the Web application is started again or a request is received and the global session information is inherited. Delete the remaining global session information by the global session information deletion command (cjclearsession).

KDJE34346-W

Transfer of global sessions at Web application startup failed because an error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, DB Connector = dd....dd, exception = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID that could not be inherited

dd....dd: Optional name of the DB Connector

ee....ee: Information about the exception that occurred

Description

The global session information could not be inherited during the startup of the Web application because a failure occurred during database communication.

Action

Make sure that the database is operating properly and that no problem has occurred in the communication path between the database and J2EE server.

If a failure occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, solve the problem of the communication path. If a problem occurs in the communication path, the exclusion in the database might not be released. Before restarting the business, check the invalid connections, and release the unreleased exclusion.

If no problem exists in the database and communication path, make sure that the settings of the connection timeout of the DB Connector are correct.

If the settings of the connection timeout is short, a timeout might occur before completing the recovery process when a failure occurs in the database. Tune the parameters of the DB Connector in view of the database recovery time.

Note that when this message is output, the global session information continues to remain in the database until the Web application is started again or a request is received and the global session information is inherited. Delete the remaining global session information by the global session information deletion command (cjclearsession).

KDJE34347-I

The global session has already been transferred. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description: The global session information that was attempted to be inherited during the startup of the Web application is already inherited in the J2EE server.

KDJE34348-I

The global session has already been transferred to another J2EE server. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description: The global session information that was attempted to be inherited during the startup of the Web application is inherited in another J2EE server.

KDJE34349-I

Transfer of global sessions at Web application startup finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The process of inheriting the global session information during the startup of the Web application has terminated.

KDJE34357-W

A property of the requests that only read HTTP session is invalid. The URI will be ignored. (URI = aa....aa)

aa....aa: Invalid URI

Description

An invalid URI is specified in the definition of the read-only requests of the read-only request definition functionality of HTTP session.

Action

Make sure that an invalid URI is not specified as a read-only request, and specify the correct URI. The following URIs are invalid:

Not normalized.
Not beginning with a forward slash (/).
The length of the URI exceeds 512 characters.

KDJE34358-I

A difference of parameters was detected by negotiation. Processing will continue. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, parameter defined by Web application = (dd....dd), parameter stored in database = (ee....ee))

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information that is currently set in the Web application

ee....ee: Information that is saved in the database

Description

The settings of the Web application saved in the database and the settings of the Web application that was attempted to be started did not match in the negotiation processing executed during the startup of the database session failover functionality; however, the start processing continues.

Regarding the parameter for which the settings did not match, the currently set information is output to dd....dd and the information saved in the database is output to ee....ee in the following format:

Parameter-name = Set-value

The contents of the parameter name are as follows:

max sessions: Maximum value of the number of HttpSession objects
max inactive interval: Valid time period of the HTTP session defined in the web.xml

If multiple setup items do not match, output them by demarcating with a comma (,).

KDJE34359-E

Usage: cjclearsession [-count] [-dbtype {hirdb|oracle}] <URL> <user> <password> <application ID> <server ID>

Description: An argument of the global session information deletion command (cjclearsession) is invalid. Output the usage method.
Action: Specify the correct argument of the global session information deletion command (cjclearsession).

KDJE34360-I

The number of global sessions was successfully acquired. (application ID = aa....aa, server ID = bb....bb, number of global sessions = cc....cc)

aa....aa: Application identifier

bb....bb: Server ID

cc....cc: Global session information count

Description: The global session information count was acquired successfully.

KDJE34361-I

The global sessions has been cleared successfully. (application ID = aa....aa, server ID = bb....bb, count of cleared global sessions = cc....cc)

aa....aa: Application identifier

bb....bb: Server ID

cc....cc: Deleted global session information count

Description: The global session information was deleted successfully.

KDJE34362-E

An attempt to clear the global sessions failed because an error occurred during communication with the database. (application ID = aa....aa, server ID = bb....bb, number of cleared global sessions = cc....cc)

aa....aa: Application identifier

bb....bb: Server ID

cc....cc: Deleted global session information count

Description

An attempt to delete the global session information has failed because an error occurred during database access. The processing will be interrupted.

Action

Make sure that the database is operating properly and that no problem has occurred in the communication path between the database and J2EE server.

If a problem occurs in the communication path, the exclusion in the database might not be released. Check the invalid connections, and release the unreleased exclusion.

After solving the problem, execute the global session information deletion command (cjclearsession).

KDJE34363-E

An attempt to load the JDBC driver class failed. (JDBC driver = aa....aa)

aa....aa: Class name of the JDBC driver

Description: An attempt to load a class of the JDBC driver has failed.
Action: Specify the correct path of the JDBC driver.

KDJE34364-E

An attempt to connect to the database failed. (URL = aa....aa, user = bb....bb)

aa....aa: Connection-destination URL

bb....bb: User connecting to the database

Description

An attempt to connect to the database has failed.

The possible causes of the error are as follows:

The connection-destination URL, connected user, or password is invalid.
The database is not operating normally.
A problem has occurred in the communication path between the database and the J2EE server.

Action

Take action according to the cause of the error.

KDJE34365-E

The table specified by the application ID was not found in the database. (application ID = aa....aa, URL = bb....bb, user = cc....cc)

aa....aa: Application identifier

bb....bb: Connection-destination URL

cc....cc: Users connected to the database

Description

The table corresponding to the specified application identifier did not exist in the database.

The possible causes of the error are as follows:

The application identifier is invalid.
The connection-destination database or user is invalid.

Action

Take action according to the cause of the error.

KDJE34366-E

An error occurred during a database access. (exception = aa....aa)

aa....aa: Information about the exception that occurred

Description

An error occurred during database access.

The possible causes of the error are as follows:

The database is not operating normally.
A problem has occurred in the communication path between the database and the J2EE server.

Action

Take action according to the cause of the error.

KDJE34367-W

An HTTP session was not stored in the database because the number of global sessions has reached the maximum. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

A redundant HTTP session exists because the number of global sessions has reached the maximum count during the creation of the global session information.

Action

Session failover is not performed for a redundant HTTP session.

Note that a redundant HTTP session is updated in the database when some space is made available in the database when operating HTTP sessions thereafter.

KDJE34368-W

An HTTP session was not stored in the database because an error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information about the exception that occurred recently

Description

A redundant HTTP session exists because a database failure occurred when operating the global session information.

Action

Session failover is not performed for a redundant HTTP session.

A redundant HTTP session is updated in the database when the database is accessed successfully during the operation of HTTP sessions thereafter.

KDJE34369-I

HTTP sessions that were not stored in the database were lost. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The redundant HTTP session no longer exists.

KDJE34370-W

An attempt to transfer global sessions at Web application startup failed because the number of HTTP sessions has reached the maximum for the J2EE server. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID that could not be inherited

Description

The global session information could not be inherited when the Web application was started because the number of HTTP sessions on the J2EE server has reached the maximum count.

Action

Check, and if necessary, revise the upper-limit setting of the number of HTTP sessions.

Note that when this message is output, the global session information continues to remain in the database until the Web application is started again or a request is received and the global session information is inherited. Delete the remaining global session information by the global session information deletion command (cjclearsession).

KDJE34371-E

The function that adds the server ID to the HTTP cookie is disabled.

Description

The functionality for adding a server ID to the HTTP Cookie is disabled.

Action

When the integrity assurance mode is disabled, you must enable the functionality for adding the server ID to an HTTP Cookie.

Set true in the webserver.session.server_id.enabled key of the user property file (usrconf.properties), and "different value for each redundant J2EE server" in the webserver.session.server_id.value key.

KDJE34376-W

Error 503 cannot be returned by the queue because thread control by Web application is disabled.

Description: The error 503 cannot be returned by the pending queue because controlling the count of concurrently executing threads of each Web application is disabled.
Action: If true is specified in the webserver.dbsfo.thread_control_queue.enabled key of the user property file (usrconf.properties), specify true in the webserver.container.thread_control.enabled key.

KDJE34377-E

An attempt to clear the global sessions failed because an error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information about the exception that occurred

Description

An attempt to delete the global session information or the global session information whose valid period has expired failed because a failure occurred in the database communication.

Action

Make sure that the database is operating properly and that no problem has occurred in the communication path between the database and J2EE server.

If a failure occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, the exclusion in the database might not be released. Check the invalid connections and release the unreleased exclusion.

If no problem exists in the database and communication path, make sure that the setting of the connection timeout of the DB Connector is correct. If the setting of the connection timeout is short, a timeout might occur before completing the recovery process when a failure occurs in the database. Tune the parameters of the DB Connector in view of the database recovery time.

Note that when this message is output, the global session information continues to remain in the database until the Web application is started again or a request is received and the global session information is inherited. Delete the remaining global session information by the global session information deletion command (cjclearsession).

KDJE34378-E

The output directory could not be created. (directory = aa....aa, cause = bb....bb)

aa....aa: Directory path

bb....bb: Cause message

Description: The output-destination directory for logs cannot be created. The execution of the global session information deletion command (cjclearsession) will be interrupted.
Action: Resolve the problem according to the contents of the cause message, and then re-execute the global session information deletion command (cjclearsession).

KDJE34379-E

An unexpected error occurred. (aa....aa)

aa....aa: Error message for an unexpected exception

Description

An unexpected exception occurred in the global session information deletion command (cjclearsession).

Action

Make sure that another error message is not output in the log.

If no problem exists, obtain the maintenance information and contact maintenance service.

KDJE34380-E

The HttpSession object could not be instantiated because the number of global sessions has reached the maximum. (J2EE application = aa....aa, context root = bb....bb, max global sessions = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Upper-limit value of the global session count

Description: The HttpSession object could not be generated because the global session count has reached the upper-limit value.
Action: The number of global sessions of the database might be too less. Increase the upper-limit value of the global session count of the database as and when required.

KDJE34400-I

The session failover (EADs) functionality will now start. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description: The EADs session failover functionality is started for the Web application with the J2EE application name aa....aa and context root name bb....bb.

KDJE34401-E

The session failover (EADs) functionality could not start. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description: The EADs session failover functionality could not be started. The Web application cannot be started.
Action: Take action for the message that is output before this message. After taking action, restart the J2EE server or J2EE application.

KDJE34402-I

The default value will be applied to the application ID. (default value = aa....aa)

aa....aa: Default value

Description: Apply the default value aa....aa to the application identifier.

KDJE34403-E

The session failover (EADs) functionality cannot be used at the same time as the memory session failover functionality or the database session failover functionality.

Description: The EADs session failover functionality cannot be used concurrently with the memory session failover functionality or the database session failover functionality. The Web application initialization will be stopped.
Action: Apply the EADs session failover functionality, memory session failover functionality, or database session failover functionality in conformity with the system configuration and requirements.

KDJE34404-E

The functionality that adds the server ID to HTTP cookies is disabled.

Description

The functionality that adds the server ID to HTTP Cookie is disabled.

Action

With the EADs session failover functionality, the functionality that adds a server ID to HTTP Cookie must be valid.

Specify true in the webserver.session.server_id.enabled property of the Easy Setup definition file and different values to each redundant J2EE server.

KDJE34405-I

Negotiation was successful. (J2EE application = aa....aa, context root = bb....bb, parameter = (cc....cc))

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Web application setup information

Description

The negotiation process was successful during startup of the EADs session failover functionality.

The setup information of the EADs session failover functionality that is specified in the Web application is output with the following format to cc....cc:

Parameter name = Setup value

The contents of the parameter name are as follows:

max sessions: Maximum value of the HttpSession object count
max inactive interval: Validity period of the HTTP session that is defined in web.xml
exclude url patterns: Settings of the EADs session failover inhibit functionality^#
session read only url patterns^#: Settings for the functionality to define requests to exclusively reference the HTTP session^#
session persistence version: Version of the EADs session failover functionality

#: In the case of multiple setup values, the characters are demarcated with commas (,) and output.

KDJE34406-E

Negotiation failed. (J2EE application = aa....aa, context root = bb....bb, invalid parameter = (cc....cc), valid parameter = (dd....dd))

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Setup information that is the cause of negotiation failure

dd....dd: Correct setup information

Description

The negotiation process has failed when starting the EADs session failover functionality. The setup information of the Web application saved in the EADs server and the setup information of the Web application to be started is not in conformity.

The Web application startup is interrupted.

For the error parameters, information that is currently specified is output to cc....cc and information that is saved in the EADs server is output to dd....dd, in the following format:

Parameter name = Setup value

The contents of the parameter name is as follows:

exclude url patterns: Setting of the EADs session failover inhibition functionality^#
session read only url patterns: Setting of the functionality to define the requests for referencing HTTP sessions^#
session persistence version: Version of the EADs session failover functionality

#: In the case of multiple setup values, the characters are demarcated with commas (,) and output.

Action

Modify the settings in conformity with the setup information of the Web application saved on the EADs server that is displayed in dd....dd.

KDJE34407-E

The cache used by the session failover (EADs) functionality was not found in the EADs server. (J2EE application = aa....aa, context root = bb....bb, cache = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Name of the cache that was not found

Description

The cache used by the EADs session failover functionality was not found on the EADs server.

The startup of the Web application is interrupted.

Action

Confirm that the cache with the name that is output to cc....cc exists on the EADs server.

If the connected EADs server is incorrect, correct the settings of the J2EE server.

KDJE34409-I

A difference in the parameter settings was detected during negotiation. Processing will continue. (J2EE application = aa....aa, context root = bb....bb, parameter defined by Web application = (cc....cc), parameter stored in EADs server = (dd....dd))

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Information currently specified in the Web application

dd....dd: Information saved on the EADs server

Description

With the negotiation process during startup of the EADs session failover functionality, the setting information of the Web application saved on the EADs server and the setting information of the Web application to be started are not in conformity. However, the process will continue.

For a parameter in which setting information is not in conformity, the information that is currently set is output to cc....cc and the information saved on the EADs server is output to dd....dd, in the following format:

Parameter name = Setting value

The parameter contents are as follows:

max sessions: Maximum value of the HttpSession object count
max inactive interval: Validity period of the HTTP session defined with web.xml

If multiple setting information is not in conformity, the information is output with commas (,) as demarcators.

KDJE34410-W

The HTTP session contains an attribute that cannot be serialized. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

dd....dd: Name of the attribute that cannot be serialized

ee....ee: Class name of the object that cannot be serialized

Description: The HTTP session contains an attribute that cannot be serialized. This attribute is ignored and is not duplicated on the EADs server.
Action: The HTTP session contains an object that is not a class that can be serialized as an attribute. Check the contents of the Web application.

KDJE34411-E

An attempt to serialize the attribute information failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

dd....dd: Name of the attribute that failed to be serialized

ee....ee: Class name of the object that failed to be serialized

Description

An attempt to serialize the attribute information of the HTTP session is failed. The information of this HTTP session is not duplicated on the EADs server.

The cause of failure in serialization might be as follows:

The object, referenced from the object of the attribute that failed to be serialized, was not a class that can be serialized
The writeObject(java.io.ObjectOutputStream out) method was implemented, and an exception occurred during serialization.

Action

Identify the cause of the failed attempt to serialized the attribute information based on the contents of the stack trace that is output with the message ID KDJE34412-E to the Web servlet log, and then take any of the following actions:

Exclude the object in which the error occurred from the attribute of the HTTP session.
Change the Web application and remove the cause of the error, from the object that failed to be serialized.

KDJE34412-E

aa....aa

aa....aa: Exceptional stack trace

Description

The stack trace that is thrown with the serialize process of the attribute information of the HTTP session is output for each row.

The following might be the causes for the error in serialization:

The object that was referenced from the object of the attribute that failed to be serialized was not a class that can be serialized.
The writeObject(java.io.ObjectOutputStream out) method was implemented and an exception occurred during the serialization.

Action

Identify the cause of failure in serialization based on the contents of the stack trace and take one of the following actions:

Exclude the object in which the error occurred from the attribute of the HTTP session.
Change the Web application, and remove the cause of the error occurred, from the object that failed to be serialized.

KDJE34413-E

An attempt to deserialize the global session information failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

dd....dd: Name of the attribute that failed in deserialization

Description

An attempt to deserialize the global session information that was acquired from the EADs server failed, so the session cannot be inherited.

The following might be the causes for the error in deserialization:

The Web applications differed during serialization and deserialization, and the change that causes the failure of the attempt to deserialize was added in the Web application.
The readObject() method was implemented and an error occurred internally.

Action

Identify the cause of the deserialization error based on the contents of the stack trace that is output with the KDJE34414-E message ID to the Web servlet log, and take actions.

KDJE34414-E

aa....aa

aa....aa: Stack trace of exception

Description

The stack trace of the exception that is thrown with the deserialization process of the global session information is output to each row.

The following might be the causes for the error in deserialization:

The applications were different during serialization and deserialization and the change that caused the failure of the attempt to deserialize was added to the application.
The readObject() method is implemented and an error occurred independently.

Action

Idenfity the cause of the deserialization error based on the contents of the stack trace, and take actions.

KDJE34415-I

The functionality for outputting the size of the attribute information will now be enabled. The global session information will not be duplicated. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The functionality to output the size of the attribute information of the HTTP session will be enabled.

The global session information will not be duplicated.

KDJE34416-I

HTTP session attribute information was created. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, size (bytes) = dd....dd, HTTP session ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Size of the attribute information of the HTTP session (bytes)

ee....ee: Session ID of the HTTP session

Description: The size (unit: bytes) of the HTTP session attribute information duplicated on the EADs server will be displayed.

KDJE34417-I

An attribute registered in the HTTP session was serialized. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, attribute name = dd....dd, class name = ee....ee, size (bytes) = ff....ff, HTTP session ID = gg....gg)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Name of the attribute registered in the HTTP session

ee....ee: Name of the class of the attribute to be registered in the HTTP session

ff....ff: Size in bytes of the array that is created by serializing the attribute registered in the HTTP session

gg....gg: Session ID of the HTTP session

Description

The size (unit: bytes) after partial serialization of the attribute that is registered in the HTTP session duplicated with the EADs session failover functionality will be displayed.

The information of the attribute name will be included in the output size.

KDJE34418-W

The HTTP session contains an attribute that cannot be serialized. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

dd....dd: Name of the attribute that cannot be serialized

ee....ee: Class name of the object that cannot be serialized

Description: The HTTP session contains an attribute that cannot be serialized. This attribute will be ignored, and cannot be duplicated on the EADs server.
Action: The HTTP session includes an object that cannot be serialized as an attribute. Check the Web application contents.

KDJE34419-E

An attempt to serialize the global session information failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

dd....dd: Name of the attribute that failed to be serialized

ee....ee: Class name of the object that failed to be serialized

Description

An attempt to serialize the attribute information of the HTTP session has failed. The information of this HTTP session cannot be duplicated.

The following might be the causes for the error in serialization:

The object that was referenced from the object of the attribute that failed to be serialized was not a class that can be serialized.
The writeObject(java.io.ObjectOutputStream out) method was implemented and an exception occurred during the serialization.

Action

Identify the cause of the error in serialization based on the contents of the stack trace that is output with the KDJE34412-E message ID to the Web servlet log, and take any of the following actions:

Exclude the object in which the error occurred from the attribute of the HTTP session.
Change the Web application and remove the cause of the error from the object that failed to be serialized.

KDJE34420-W

An HTTP session was not stored in the EADs slave server because an error occurred during communication with that server. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Information of the last occurred exception

Description

During operations of the global session information, an error occurred in the EADs server and an attempt to update the copy destination server of the session information has failed. Therefore, the HTTP session was degenerated.

Action

The HTTP session that was degenerated because of an error while updating the copy destination server of the session information might not be the target for the session failover.

The degenerated HTTP session will be updated on the EADs server, when access to the EADs server is successful with the operations of the HTTP session thereafter.

KDJE34421-E

An attempt to connect with the EADs server has failed. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Information of the occurred exception

Description

An attempt to connect with the EADs server has failed.

Action

If this message is output, check that the EADs server is operating correctly and that there is no error in the communication route of the EADs and J2EE servers.

If an error occurs on the EADs server, take an action according to the restoration procedures for the EADs server.

If an error occurs in the communication route of the EADs and J2EE server, remove the error.

KDJE34422-E

An attempt to clear the global session information failed because an error occurred during communication with the EADs slave server. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc, application ID = dd....dd, HTTP session ID =ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Information of the occurred exception

dd....dd: Application identifier

ee....ee: Session ID of the HTTP session

Descritpion

An attempt to delete the global session information on the copy destination server or delete the invalid global session information has failed, because an error occurred during communication with the copy destination server in the session information.

Action

If this message is output, the global session information of one level above is remained on the copy destination server.

If this message is output, check that the EADs server is operating correctly and that there is no error in the communication route of the EADs and J2EE servers.

If an error occurs on the EADs server, take action according to the restoration procedures for the EADs server.

If an error occurs in the communication route of the EADs and J2EE server, remove the error.

KDJE34423-E

An attempt to clear the global session information failed because an error occurred in the operation of the EADs server. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Information of the occurred exception

Description

An attempt to delete the global session information or delete the invalid global session information has failed, because an error occurred in communication with the EADs server or in the user functionality that is provided by the EADs session failover functionality.

Action

If this message is output, one or more global session information items remain on the EADs server.

The global session information remaining on the EADs server is inherited by the J2EE server as an available session when the Web application is restarted or when a request with the same session ID is received.

To delete the global session information remaining on the EADs server, use the command for deleting global session information (cjezclearsession command).

If this message is displayed, check whether the EADs server is running normally, and whether there is any problem in the communication channel between the EADs server and J2EE server.

If an error occurs on the EADs server, take action based on the EADs server restoration procedures.

If there is a problem in the communication channel between the EADs server and the J2EE server, resolve the problem.

Also, check whether the user application JAR files provided by the EADs session failover functionality are allocated to the EADs server, and whether any invalid operations are being performed for the EADs server from an external source.

KDJE34424-I

The global session information was inherited successfully. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

Description: The global session information was inherited successfully.

KDJE34425-W

An attempt to inherit the global session information failed because an error occurred in the operation of the EADs server. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Exception information

Description

The global session could not be inherited because an error occurred in communication with the EADs server or an error occurred in a user application provided by the EADs session failover functionality.

Action

Check whether the EADs server is running normally and whether there is any problem in the communication channel between the EADs and J2EE servers.

If an error occurs on the EADs server, take an action based on the EADs server restoration procedures.

If there is an error in the communication channel between the EADs and J2EE servers, resolve the error.

Also, check whether the user application JAR files provided by the EADs session failover functionality are allocated to the EADs server, and whether any invalid operations are being performed for the EADs server from an external source.

KDJE34426-W

An attempt to inherit the global session information failed because that information was not found in the EADs server. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

Description

The HTTP session corresponding to the HTTP session ID received from the client has expired or has already been disabled due to the processing of the Web application on the J2EE server.

A global session could not be inherited because the global session information was not found on the EADs server.

Action

A request using an expired HTTP session is received from the client.

Check whether the validity period specified for the HTTP session is appropriate.

KDJE34427-W

An HTTP session was not stored in the EADs server because an error occurred during communication with the EADs server. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Latest exception information

Description

A degenerated HTTP session exists because an EADs server error occurred during the operation of global session information.

Action

A degenerated HTTP session is not subject to session failover.

A degenerated HTTP session is updated on the EADs server when the session can access the EADs server during the subsequent HTTP session operations.

KDJE34428-I

HTTP sessions that were not stored in the EADs server have been deleted. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The degenerated HTTP sessions were deleted.

KDJE34429-I

Processing to inherit global session information at Web application startup will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The processing to inherit global session information used at Web application startup will start.

KDJE34430-I

Processing to inherit global session information at Web application startup finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The processing to inherit the global session information used at Web application startup finished.

KDJE34431-W

Processing to inherit global session information at Web application startup could not start. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Exception information

Description

An error occurred in communication with the EADs server, or the processing to inherit global session information used for starting the Web applications, provided by the EADs session failover functionality, could not start.

Action

If this message is displayed, eliminate the cause of the error based on the following action and then restart the Web application, or global session information will remain on the EADs server until a request is received and information is inherited.

To delete the remaining global session information, use the command for deleting global session information (cjezclearsession command).

If this message is displayed, check whether the EADs server is running normally and whether there is any problem in the communication channel between the EADs and J2EE servers.

If an error occurs on the EADs server, take action based on the EADs server restoration procedures.

If there is an error in the communication channel between the EADs and J2EE servers, eliminate the error.

Also, check whether the user application JAR files provided by the EADs session failover functionality are allocated to the EADs server and whether any invalid operations are being performed for the EADs server from an external source.

KDJE34432-I

The global session information to be inherited has already been inherited. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description: The global session information to be inherited during Web application startup has already been inherited on the J2EE server.

KDJE34434-W

Processing to inherit global session information at Web application startup failed because an error occurred during communication with the EADs server. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID that could not be inherited

dd....dd: Exception information

Description

The global session information could not be inherited during Web application startup because an error occurred during communication with the EADs server.

Action

If this message is displayed, eliminate the cause of the error based on the following action and then restart the Web application, or global session information will remain on the EADs server until a request is received and information is inherited.

To delete the remaining global session information, use the command for deleting global session information (cjezclearsession command).

If this message is displayed, check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

If there is an error in the communication channel between the EADs and J2EE servers, eliminate the error.

KDJE34435-W

Processing to inherit global session information at Web application startup failed because the number of HTTP sessions reached the maximum for the J2EE server. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID that could not be inherited

Description

The global session information could not be inherited at Web application startup because the number of HTTP sessions reached the maximum number for the J2EE server.

Action

If this message is displayed, eliminate the cause of the error based on the following action and then restart the Web application, or global session information will remain on the EADs server until a request is received and information is inherited.

To delete the remaining global session information, use the command for deleting global session information (cjezclearsession command).

When this message is displayed, review that the settings are appropriate for the maximum number of HttpSessions.

KDJE34436-E

The global session information obtained from the EADs server is invalid. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The content of global session information acquired from the EADs server is invalid.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs server and J2EE server.

Also, check whether any invalid operations are being performed for the EADs server from an external source.

KDJE34437-W

A definition of the session failover (EADs) functionality is invalid. The URL pattern will be ignored. (URL pattern = aa....aa)

aa....aa: Invalid URL pattern

Description

An invalid URL pattern has been specified in the definition of the EADs session failover control functionality.

Action

Check whether an invalid URL pattern has been specified in the definition of the EADs session failover control functionality, and specify a valid URL pattern. The following URL patterns are invalid:

A URL pattern that is not normalized.
A URL pattern that does not begin with / (forward slash) and *..

KDJE34438-W

A definition of a request that only reads HTTP sessions is invalid. The URL pattern will be ignored. (URL pattern = aa....aa)

aa....aa: invalid URL pattern

Description

An invalid URL pattern is specified in the definition of a reference request with the reference request definition functionality for an HTTP session.

Action

Check whether an invalid URL pattern is specified as the reference request for an HTTP session, and specify the valid URL pattern. The following URL patterns are invalid:

A URL pattern that is not normalized.
A URL pattern that does not begin with / (forward slash) and *..

KDJE34439-E

Usage: cjezclearsession [-count] <J2EE server name> <application ID> {-all | <server ID>}

Description: An argument of the cjezclearsession command is incorrect. The command usage will be output.
Action: Specify the correct argument for the cjezclearsession command.

KDJE34440-I

The number of items of global session information was acquired successfully. (application ID = aa....aa, server ID = bb....bb, number of items of global session information = cc....cc)

aa....aa: Application identifier

bb....bb: Server ID (empty string if -all is specified for the cjezclearsession command)

cc....cc: Number of items of global session information

Description: The number of items of global session information is acquired.

KDJE34441-I

The global session information was cleared successfully. (application ID = aa....aa, server ID = bb....bb, number of items of cleared global session information = cc....cc)

aa....aa: Application identifier

bb....bb: Server ID (empty string if -all is specified for the cjezclearsession command)

cc....cc: Number of global session information items that are deleted

Description: The deletion of global session information is complete.

KDJE34442-E

An attempt to clear the global session information failed because an error occurred during communication with the EADs server. (application ID = aa....aa, server ID = bb....bb, number of items of cleared global session information = cc....cc)

aa....aa: Application identifier

bb....bb: server ID (empty string if -all is specified for the cjezclearsession command)

cc....cc: Number of global session information items that are deleted

Description

An attempt to delete global session information failed because an error occurred while the EADs server was being accessed or an error occurred in the user application provided by the EADs session failover functionality. The processing will be cancelled.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

Also, check whether any invalid operations are being performed for the EADs server from an external source.

After eliminating the error, re-execute the cjezclearsession command.

KDJE34443-E

Initialization of the EADs client failed. (exception = aa....aa)

aa....aa: Exception and message

Description

An attempt to initialize the EADs client has failed.

Action

Check whether the EADs client is installed, whether the path of the JAR files provided by the EADs client is set in the CLASSPATH environment variable, and whether the J2EE server specified in the argument of the cjezclearsession command exists.

Check whether the EADs server is running normally, whether there is any error in the communication channel between the EADs server and the J2EE server, and whether the EADs client settings specified in the Easy Setup Definition file are correct.

After eliminating the error, re-execute the cjezclearsession command.

KDJE34444-E

An attempt to connect the session information cache in the EADs server failed. (cache name = aa....aa, exception = bb....bb)

aa....aa: Cache name

bb....bb: Exception and message

Description

An attempt to connect to the session information cache on the EADs server has failed.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

Check whether the name of the session information cache is correct.

After resolving the problem, re-execute the cjezclearsession command.

KDJE34445-E

An attempt to acquire the session ID list failed.

Description

An attempt to acquire the session ID list failed.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

Check whether the user application JAR files provided by the EADs session failover functionality are allocated to the EADs server.

After eliminating the error, re-execute the cjezclearsession command.

KDJE34446-E

An error occurred during access to EADs. (exception = aa....aa)

aa....aa: Exception and message

Description: An error occurred during the EADs access.
Action: Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

KDJE34447-E

The output directory could not be created. (directory = aa....aa, cause = bb....bb)

aa....aa: Directory path

bb....bb: Message describing the cause

Description

The log output directory could not be created.

The execution of the cjezclearsession command will be cancelled.

Action

Resolve the error based on the message describing the cause, and then re-execute the cjezclearsession command.

KDJE34448-E

An unexpected error occurred. (aa....aa)

aa....aa: Error message for the unexpected exception

Description: An unexpected exception occurred in the cjezclearsession command.
Action: Check whether any other error message is output to the log.

KDJE34449-E

aa....aa

aa....aa: Stack trace

Description: An exception occurred. The stack trace will be output.
Action: Check the cause of the exception from stack trace information of the exception and the log output elsewhere.

KDJE34450-W

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

aa....aa: Property name

bb....bb: Value

cc....cc: Default value

Description: A property value is invalid. The default value will be used.
Action: To change the property aa....aa from the default value, correct the aa....aa property value, and then re-execute the command.

KDJE34451-W

A property value is not specified. The default value will be used. (property = aa....aa, default value = bb....bb)

aa....aa: Property name

bb....bb: Default value

Description: A property value is not specified. The default value will be used.
Action: To change the property aa....aa from the default value, correct the aa....aa property value, and then re-execute the command.

KDJE34452-E

The application information obtained from the EADs server is invalid. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The application information acquired from the EADs server is invalid.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs server and the J2EE server.

Also, check whether any invalid operations are being performed for the EADs server from an external source. If there is no error, collect the maintenance information, and then contact maintenance personnel.

KDJE34453-E

Another application is already using the specified application ID. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc, J2EE application in cache = dd....dd, context root in cache = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

dd....dd: J2EE application name registered in the application information cache

ee....ee: Context root name registered in the application information cache

Description

The specified application identifier is being used by a different application.

Action

To start the same application as the existing application, check whether the J2EE application name or context root name differs from the information of the same application that is already running. If the information is different, correct the settings and then start the application.

To start an application different from the existing application, specify an application identifier that is not used for other applications in the Web application, and then start the application.

KDJE34454-E

Initialization of the EADs client failed. (exception = aa....aa)

aa....aa: Exception information

Description

An attempt to initialize the EADs client has failed.

Action

Take the following action:

Check whether the EADs client is installed and whether the JAR file provided by the EADs client is specified in the option definition file for J2EE servers as the container extension library.
Check whether the EADs server is running normally, whether there is any error in the communication channel between the EADs and J2EE servers, and whether the EADs client settings specified in the Easy Setup Definition file are correct.

For details on the EADs client settings, see 4.11.2 Parameters used for setting up the user properties for the J2EE server in the uCosminexus Application Server Definition Reference Guide.
If the EADs client is not installed, install the EADs client and then set up the EADs session failover functionality.
If the JAR file provided by the EADs client is not specified in the option definition file for J2EE servers as the container extension library, specify the required settings.
If an error occurs on the EADs server, take actions based on the EADs server restoration procedure.
If there is an error in the communication channel between the EADs and J2EE servers, resolve the error.
If the EADs client settings specified in the Easy Setup Definition file are incorrect, correct the settings.

KDJE34455-E

An error occurred in a user function supplied by the session failover (EADs) functionality. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc, function name = dd....dd, exception = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

dd....dd: Name of the function where the exception occurred

ee....ee: Exception information

Description

An error occurred in the user function provided by the EADs session failover functionality.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

Also, check whether any invalid operations are being performed for the EADs server from an external source.

If there is no error, collect the maintenance information and then contact maintenance personnel.

KDJE34456-E

An error occurred in a user function supplied by the session failover (EADs) functionality. (function name = aa....aa, exception = bb....bb)

aa....aa: Name of the function where the exception occurred

bb....bb: Exception information

Description

An error occurred in the user function provided by the EADs session failover functionality.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

Also, check whether any invalid operations are being performed for the EADs server from an external source.

If there is no error, collect the maintenance information and then contact maintenance personnel.

KDJE34500-W

Occupied memory exceeded the threshold. A Full GC might be executed. (Rate1 = aa....aa , Rate2 = bb....bb , Rate3 = 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 = 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 usage (in %) in the Metaspace area

Ratio of the Metaspace area consumption size with respect to the maximum memory size of the Metaspace area

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 heap and memory usage has exceeded the threshold value.

A Full GC might be performed.

Action

This message is displayed when a constant amount of heap and memory is used. There is no problem even if this message is displayed at regular intervals. However, if a Full GC occurs more often than expected, confirm that the heap and memory size settings are appropriate and, if necessary, revise them. If there is no improvement even after changing to an appropriate heap and memory size, check whether a memory leak is occurring in the application, and if necessary, revise the settings.

KDJE34510-W

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

aa....aa: Property key

bb....bb: Set value

cc....cc: Default value

Description

The default value will be used because an invalid value was acquired from the property file.

Take action based on the following causes:

An invalid value is specified in the properties.
A value outside the valid range has been specified.

Action

Revise the set value of the property key (aa....aa) of the user property file for the J2EE server (usrconf.properties).

KDJE34511-I

Full GC monitoring will now start.

Description: Full GC monitoring will start.

KDJE34512-I

Full GC monitoring will now stop.

Description: Full GC monitoring will stop.

KDJE34513-I

Full GC monitoring is not supported.

Description: The JDK you are using does not support Full GC monitoring.
Action: To monitor Full GC, use the JDK described in the preconditions.

KDJE34520-W

The number of used file descriptors has reached the threshold value. (Current = aa....aa, Max = bb....bb, Threshold = cc....cc)

aa....aa: Number of current file descriptors

bb....bb: Maximum number of usable file descriptors

cc....cc: Threshold value of number of file descriptors

Description

The number of used file descriptors has reached the threshold value.

Action

Revise the set value^# of the property or the system, set the correct value, and then restart the J2EE server.

#: You need not check and change the settings for a platform on which the system settings cannot be changed.

KDJE34521-I

File descriptor monitoring will now start.

Description: File descriptor monitoring will start.

KDJE34522-I

File descriptor monitoring will now stop.

Description: File descriptor monitoring will stop.

KDJE34523-I

The monitoring of a file descriptor is not performed. (reason = aa....aa)

aa....aa: Reason

Not supported: Since monitoring is not supported

Description: File descriptor monitoring is not performed due to reason (aa....aa).

KDJE34524-W

The control method of the HTTP session in the received request does not match the control method of the global session. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, GS control = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Control method of the global session specified in the Web application

cookie will be output in the case of the HTTP Cookie, while url-rewriting will be output in the case of the URL re-writing.

Description

The control method of the HTTP session in the received request is different from the control method of the global session set up in the Web application.

Take action based on the following causes:

The settings of the control method of the global session are invalid.
The settings for load balancing are invalid.
The settings of the HTTP Cookie of the Web client are different from the system request.

For this request, the HTTP session will continue, but the memory session failover functionality will not be enabled.

Note that if the HTTP session is disabled when this message is displayed, null might be output to the HTTP session ID (cc....cc).

Action

Take action as follows:

When the settings of the control method of the global session are erroneous

Confirm that the initialization parameters of the filter used for the session failover function and the value set in the parameter GSessionControl is appropriate, and in the case of a problem, modify to correct settings.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.
If a connection is established to the SFO server, restart the SFO server.
Create and start J2EE applications from the Web application in which the settings have been applied.

When the settings of load balancing are invalid

Check the settings of load balancing, and change the settings for load distribution to the appropriate J2EE server by the control method of the global session.

When the settings of the HTTP Cookie of the Web client are different from the system request

Even when the system configuration and the settings are correct, the Web client might send the HTTP session with a method different from the requested method. In a Web application, create an application by considering the case when the Web client sends an incorrect request.

KDJE34530-W

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

aa....aa: Property key

bb....bb: Set value

cc....cc: Default value

Description

The default value will be used because an invalid value was acquired from the property file.

Take action based on the following causes:

An invalid value is specified in the properties.
A value outside the valid range has been specified.

Action

Revise the set value of the property key (aa....aa) of the user property file for the J2EE server (usrconf.properties).

KDJE34540-W

The number of generated threads has reached the threshold value. (Current = aa....aa, Max = bb....bb, Threshold = cc....cc)

aa....aa: Current number of threads

bb....bb: Maximum number of generated threads

cc....cc: Threshold value of number of threads

Description

The number of generated threads has reached the threshold value.

Action

Revise the set value^# of the property or the system, set the correct value, and then restart the J2EE server.

#: You need not check and change the settings for a platform on which the system settings cannot be changed.

KDJE34541-I

Thread monitoring will now start.

Description: Thread monitoring will start.

KDJE34542-I

Thread monitoring will now stop.

Description: Thread monitoring will stop.

KDJE34543-I

The monitoring of a thread is not performed. (reason = aa....aa)

aa....aa: Reason

Not supported: Since monitoring is not supported

Description: Thread monitoring is not performed due to the reason (aa....aa).

KDJE34550-W

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

aa....aa: Property key

bb....bb: Set value

cc....cc: Default value

Description

The default value will be used because an invalid value was acquired from the property file.

Take action based on the following causes:

An invalid value is specified in the properties.
A value outside the valid range has been specified.

Action

Revise the set value of the property key (aa....aa) of the user property file for the J2EE server (usrconf.properties).

KDJE34580-W

The number of thread dump files has exceeded the threshold. Move the existing thread dump files to another directory. (Rate = aa....aa, Current = bb....bb, Max = cc....cc, Threshold = dd....dd)

aa....aa: Ratio (%) of the current number with respect to the maximum number of thread dump files

bb....bb: Current number of thread dump files

cc....cc: Maximum number (set number) of the thread dump files

dd....dd: Threshold value (%) (set value) of thread dump monitoring

Description: The number of thread dump files has reached the threshold value.
Action: Immediately save the thread dump in another directory.

KDJE34581-E

The number of thread dump files has exceeded the maximum. New thread dump files cannot be created until the existing thread dump files are moved to another directory. (Rate = aa....aa, Current = bb....bb, Max = cc....cc, Threshold = dd....dd)

aa....aa: Ratio (%) of the current number with respect to the maximum number of thread dump files

bb....bb: Current number of thread dump files

cc....cc: Maximum number (set number) of the thread dump files

dd....dd: Threshold value (%) (set value) of thread dump monitoring

Description

The number of thread dump files has reached the maximum value.

New thread dump cannot be output until the existing thread dump is saved in another directory.

Action

Immediately save the thread dump in another directory.

KDJE34582-W

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

aa....aa: Property key

bb....bb: Specified value (invalid value) of property

cc....cc: Default value of property

Description: The property value is invalid. The default value will be used.
Action: Revise the property, set the correct value, and then restart the J2EE server.

KDJE34583-I

Thread dump monitoring will now start.

Description: Thread dump monitoring will start.

KDJE34584-I

Thread dump monitoring will now stop.

Description: Thread dump monitoring will stop.

KDJE34621-W

The number of queued requests awaiting execution has exceeded the threshold. (J2eeApplicationName = aa....aa, ContextRootName = bb....bb, Rate = cc....cc, Current = dd....dd, Max = ee....ee, Threshold = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Ratio (%) of the current value to the maximum value of the requests stored in each Web application or the default pending queue

dd....dd: Current value of the requests stored in each Web application or the default pending queue

ee....ee: Maximum value (set value) of the requests stored in each Web application or the default pending queue

ff....ff: Threshold value (%) (set value) to monitor each Web application or the default HTTP request pending queue

Description

The number of requests stored in each Web application or the default pending queue has reached the threshold value.

In the case of default request pending queue, "-" is output for J2EE application name (aa....aa) and the context root name (bb....bb). When the maximum value of the number of requests stored in each Web application or the default pending queue is not specified, "-" is output for the ratio (cc....cc) of the current value to the maximum value of the requests stored in each Web application or the default pending queue, and for the maximum value of requests stored in each Web application or the default pending queue (ee....ee).

Action

The available resources are becoming lesser, therefore, revise the setting before they are depleted.

KDJE34622-I

HTTP request queue monitoring will now start.

Description: The monitoring of the default HTTP request pending queue will start.

KDJE34623-I

HTTP request queue monitoring will now stop.

Description: The monitoring of the default HTTP request pending queue will stop.

KDJE34624-I

HTTP request queue monitoring will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The monitoring of HTTP request pending queue of each Web application will start.

KDJE34625-I

HTTP request queue monitoring will now stop. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The monitoring of HTTP request pending queue of each Web application will stop.

KDJE34626-W

An invalid application attribute value was specified. The default value will be used. (J2EE application = aa....aa, context root = bb....bb, monitoring target resource = cc....cc, dd....dd = ee....ee, default value = ff....ff).

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Resource (request queue or session) to be monitored

dd....dd: Tag name

ee....ee: Value

ff....ff: Default value

Description: An invalid value was specified in the application attribute. The default value will be used.
Action: To change the application attribute to other than the default value, stop the application, and then change the application attribute. After this, restart the application.

KDJE34627-I

The monitoring of a HTTP request queue is not performed. (J2EE application = aa....aa, context root = bb....bb, reason = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Reason

Description

The monitoring of each Web application and default HTTP request pending queue is not performed.

In the case of default request pending queue, "-" is output for J2EE application name (aa....aa) and the context root name (bb....bb).

The reason for not monitoring each Web application and default HTTP request pending queue is displayed in cc....cc.

The contents displayed in cc....cc, and their meaning is described below:

No target

Since 0 is specified as the maximum value of each Web application and default request pending queue, monitoring target does not exist.

No upper limit

The upper limit for each Web application and default request pending queue is not set up, and therefore, the threshold value for output of alert becomes disabled.

If, however, file output of the monitoring results is enabled even when alert output is disabled, this message will not be output, and each Web application and default HTTP request pending queue will be monitored.

KDJE34630-W

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

aa....aa: Property key

bb....bb: Set value

cc....cc: Default value

Description

The default value will be used because an invalid value was acquired from the property file.

Take action based on the following causes:

An invalid value is specified in the properties.
A value outside the valid range has been specified.

Action

Revise the set value of the property key (aa....aa) of the user property file for the J2EE server (usrconf.properties).

KDJE34640-W

The number of sessions has exceeded the threshold. (J2eeApplicationName = aa....aa, ContextRootName = bb....bb, Rate = cc....cc, Current = dd....dd, Max = ee....ee, Threshold = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Ratio (%) of current number of sessions with respect to the number of sessions that can be created

dd....dd: Current number of sessions that have been created

ee....ee: Number of sessions that can be created (set value)

ff....ff: Threshold value (%) (set value) of session monitoring

Description

The number of sessions has reached the threshold value.

When the maximum value is not set, "-" is output for the percentage and maximum value.

Action

The available resources are becoming lesser, therefore, revise the setting before they are depleted.

KDJE34641-I

Monitoring of the number of sessions will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: Monitoring of the number of sessions will start.

KDJE34642-I

Monitoring of the number of sessions will now stop. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: Monitoring of the number of sessions will stop.

KDJE34643-I

The monitoring of a number of sessions is not performed. (J2EE application = aa....aa, context root = bb....bb, reason = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Reason

Description

Monitoring of a number of sessions is not performed.

The reason for not monitoring a number of sessions is displayed in cc....cc.

The contents displayed in cc....cc, and their meaning is described below:

No target

Since 0 is specified as the upper limit of the number of sessions that can be created, monitoring target does not exist.

No upper limit

The upper limit of the number of sessions that can be created is not set, therefore, the threshold value for output of alert becomes disabled.

If, however, file output of the monitoring results is enabled even when alert output is disabled, this message is not output, and the number of sessions is monitored.

KDJE34660-W

The number of connections in use exceeded the threshold. (ResourceName = aa....aa, Rate = bb....bb, Active = cc....cc, Free = dd....dd, Current = ee....ee, Min = ff....ff, Max = gg....gg, Threshold = hh....hh, All = ii....ii)

aa....aa: Resource adapter name

bb....bb: Connection pool usage

cc....cc: Number of connections in use

dd....dd: Number of unused connections

ee....ee: Current number of connections

ff....ff: Minimum number of connections

gg....gg: Maximum number of connections

hh....hh: Threshold value

ii....ii: Total number of connections

Description: The number of connections in use has exceeded the threshold value.
Action: The number of free connections is becoming lesser, therefore, revise the setting.

KDJE34661-W

The number of connections in use reached the maximum number. (ResourceName = aa....aa, Rate = bb....bb, Active = cc....cc, Free = dd....dd, Current = ee....ee, Min = ff....ff, Max = gg....gg, Threshold = hh....hh, All = ii....ii)

aa....aa: Resource adapter name

bb....bb: Connection pool usage

cc....cc: Number of connections in use

dd....dd: Number of unused connections

ee....ee: Current number of connections

ff....ff: Minimum number of connections

gg....gg: Maximum number of connections

hh....hh: Threshold value

ii....ii: Total number of connections

For details about the information shown in the message, see Table 4-12 Contents output in the monitoring information for connection pool depletion in 4.3.5 (7) in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide.

Description: The number of connections in use has reached the maximum number.
Action: Revise the set values related to the connection pool.

KDJE34662-W

No value was specified for property aa....aa of pool monitoring. The default value will be used. (bb....bb)

aa....aa: Property key

bb....bb: Default value of property

Description: The property value is not specified. The default value will be used.
Action: Revise the property, and then set the correct value.

KDJE34663-W

An invalid value was specified for property aa....aa of pool monitoring. The default value will be used. (bb....bb)

aa....aa: Property key

bb....bb: Default value of property

Description: The specified property value is invalid. The default value will be used.
Action: Revise the property, and then set the correct value.

KDJE34670-I

Pool monitoring will now start. (resource display name = aa....aa)

aa....aa: Resource display name

Description: Pool monitoring will start.

KDJE34671-I

Pool monitoring will now stop. (resource display name = aa....aa)

aa....aa: Resource display name

Description: Pool monitoring will stop.

KDJE34672-I

The pool monitoring was not executed. (resource display name = aa....aa)

aa....aa: Resource display name

Description: Pool monitoring is not executed.

KDJE34990-W

The management event issuing function is unavailable. (reason = aa....aa)

aa....aa: Reason code

Description

The management event issuing functionality is unavailable.

Action

Take action based on the reason code.

Table 7‒2: List of reasons indicated in KDJE34990-W
Reason code	Action
`-1`	Management Server is not installed. When using the management event issuing functionality, install Management Server, specify the required settings in the management event issuing functionality, and then restart the J2EE server.
`-2`	The management event issuing functionality is unavailable. When using the management event issuing functionality, confirm that the necessary settings have been specified, and then restart the J2EE server.

When using the functionality for monitoring resource depletion instead of using the management event issuing functionality, set the following properties as false:

Table 7‒3: Properties for disabling the alert output of monitoring depletion of each resource
Function name	Property name	File
Memory monitoring	`ejbserver.watch.memory.enabled`	`usrconf.properties`
File descriptor monitoring	`ejbserver.watch.fileDescriptor.enabled`
Thread monitoring	`ejbserver.watch.thread.enabled`
Thread dump monitoring	`ejbserver.watch.threaddump.enabled`
HTTP request pending queue monitoring	`ejbserver.watch.defaultRequestQueue.enabled`
HTTP request pending queue monitoring	`<watcher-enabled>` present below `<thread-control>`	HITACHI WAR property file
Session count monitoring	`<watcher-enabled>` present below `<http-session>`	HITACHI WAR property file
Connection pool monitoring	`WatchEnabled`	HITACHI Connector property file

KDJE34991-W

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

aa....aa: Property key

bb....bb: Specified value (invalid value) of property

cc....cc: Default value of property

Description: The property value is invalid. The default value will be used.
Action: Revise the property, set the correct value, and then restart the J2EE server.

KDJE37000-E

Usage:

Format1: cjimportapp [servername] [-nameserver providerURL] [-test] [-nodelete] -f applicationfilename [-f applicationfilename ...]

Format2: cjimportapp [servername] [-nameserver providerURL] [-test] -a applicationdirectorypath

Format3: cjimportapp [servername] [-nameserver providerURL] [-test] [-nodelete] -f applicationfilename -d extractdirectorypath

Description: This message describes the usage method of the cjimportapp command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37001-E

Usage : cjexportapp [servername] [-nameserver providerURL] -f applicationfilename -name applicationname [-raw | -normal]

Description: This message describes the usage method of the cjexportapp command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37004-E

Usage : cjstartapp [servername] [-nameserver providerURL] -name applicationname

Description: This message describes the usage method of the cjstartapp command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37005-E

Usage:

Format1: cjstopapp [servername] [-nameserver providerURL] [-test] -name applicationname

Format2: cjstopapp [servername] [-nameserver providerURL] [-test] -name applicationname -t timeoutseconds

Format3: cjstopapp [servername] [-nameserver providerURL] [-test] -name applicationname -cancel

Format4: cjstopapp [servername] [-nameserver providerURL] [-test] -name applicationname -t timeoutseconds -force

Description: This message describes the usage method of the cjstopapp command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37006-E

Usage:

Format1: cjdeleteapp [servername] [-nameserver providerURL] [-test] -name applicationname [-name applicationname ...]

Format2: cjdeleteapp [servername] [-nameserver providerURL] -type ejb -name applicationname -resname ejb-jardisplayname [-resname ejb-jardisplayname ...]

Format3: cjdeleteapp [servername] [-nameserver providerURL] -type war -name applicationname -resname wardisplayname [-resname wardisplayname ...]

Format4: cjdeleteapp [servername] [-nameserver providerURL] -type filter -name applicationname -resname wardisplayname/filterdisplayname [-resname wardisplayname/filterdisplayname ...]

Format5: cjdeleteapp [servername] [-nameserver providerURL] -type rar -name applicationname -resname rardisplayname [-resname rardisplayname ...]

Description: This message describes the usage method of the cjdeleteapp command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37007-E

The cjimportapp command failed. Contact the system administrator.

Description

The cjimportapp command has failed because an unexpected exception occurred.

If the exception messages starting with nnnn (n is a number) is followed by this message , see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37008-E

The cjexportapp command failed. Contact the system administrator.

Description: The cjexportapp command has failed because an unexpected exception has occurred.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37011-E

The cjstartapp command failed. Contact the system administrator.

Description: The cjstartapp command has failed because an unexpected exception occurred.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37012-E

The cjstopapp command failed. Contact the system administrator.

Description: The cjstopapp command has failed because an unexpected exception occurred.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37013-E

The cjdeleteapp command failed. Contact the system administrator.

Description: The cjdeleteapp command has failed because an unexpected exception has occurred.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37016-E

No option is specified.

Description: An argument other than the J2EE server name is specified, without specifying any option.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37020-E

The same options have been specified repeatedly. (option = [aa....aa] )

aa....aa: Option

Description: The same options have been specified multiple times.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37021-I

The server has been migrated successfully. Server name = aa....aa

aa....aa: Server name

Description: The environment of the server (aa....aa) is migrated successfully.

KDJE37022-E

The server failed to be migrated. Reason = aa....aa

aa....aa: Reason for failure

Description

Server migration will be interrupted because of failure during the migration of server environment.

Action

Take action based on the reason for failure (aa....aa). The following reasons for failure are displayed in aa....aa:

Internal error: contact maintenance personnel.
Messages beginning with nnnn (n is a number): See 25.3 Messages when Errors Occur while Changing and Importing the Working Directory, and then take action.
Reason for failure other than the above: Remove the cause of failure based on the reason, and then re-execute the cjenvupdate command.

KDJE37023-E

Invalid option. Option=[aa....aa]

aa....aa: Option

Description: An undefined option is specified.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37024-E

Different export types have been specified simultaneously.

Description: Different export type options have been specified simultaneously.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37027-E

The server was not found. (name = [aa....aa])

aa....aa: Server name

Description: The J2EE server was not found.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37028-E

Application is running. Name=[aa....aa]

aa....aa: Application name

Description: The J2EE application is running.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37029-E

aa....aa was not found.

aa....aa: Application name or resource name

Description: The J2EE application or resource (aa....aa) was not found.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37033-E

The application is not running. (name = [aa....aa])

aa....aa: Application name

Description: The J2EE application is not running.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37035-E

Deploying failed.

Description: Deploying failed.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37037-E

The file does not exist. (path = [aa....aa])

aa....aa: File path

Description: The file does not exist.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37039-E

The specified file type is a directory. (path = [aa....aa])

aa....aa: File path

Description: The specified file path (aa....aa) is a directory.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37041-I

Application has been imported successfully. Name=[aa....aa]

aa....aa: EAR file name

Description: An attempt to import the EAR file was successful.

KDJE37042-I

Application has been exported successfully. Name=[aa....aa]

aa....aa: Application name

Description: An attempt to export the J2EE application was successful.

KDJE37045-I

Application has been started successfully. Name=[aa....aa]

aa....aa: Application name

Description: An attempt to start the J2EE application was successful.

KDJE37046-I

Application has been stopped successfully. Name=[aa....aa]

aa....aa: Application name

Description: An attempt to stop the J2EE application was successful.

KDJE37047-I

Application has been deleted successfully. Name=[aa....aa]

aa....aa: Application name

Description: An attempt to delete the J2EE option was successful.

KDJE37048-I

Connecting to aa....aa...

aa....aa: Server name

Description: Connecting to the J2EE server.

KDJE37049-I

Searching aa....aa...

aa....aa: Application name

Description: The J2EE application (aa....aa) is being searched.

KDJE37050-I

Importing aa....aa...

aa....aa: Application name

Description: The J2EE application (aa....aa) is being imported.

KDJE37051-I

Exporting aa....aa...

aa....aa: Application name

Description: The J2EE application (aa....aa) is being exported.

KDJE37054-I

Starting aa....aa.

aa....aa: Application name

Description: The J2EE application (aa....aa) is being started.

KDJE37055-I

Stopping aa....aa...

aa....aa: Application name

Description: The application (aa....aa) is being stopped.

KDJE37056-I

Deleting aa....aa...

aa....aa: Application name or resource name

Description: The J2EE application or the resource (aa....aa) is being deleted.

KDJE37057-E

Another command is already running.

Description: Another command is already running.
Action: Terminate the other command, and then re-execute the command this command.

KDJE37058-E

Usage: cjresetsv [servername] [-nameserver providerURL]

Description: This message describes the usage method of the cjresetsv command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37059-E

The Naming Service was not found.

Description: The Naming Service was not found.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37060-W

The server has been migrated with errors. Some applications or resources could not be migrated. Server name = aa....aa

aa....aa: Server name

Description: The applications or resources cannot be migrated because they contain DDs that cannot be converted.
Action: If you want to use the applications or resources that were not migrated, reset the resources and applications.

KDJE37061-W

The application definition cannot be converted because the resource specified for the reference resolution has a problem. display-name = aa....aa, res-name(in resource-ref) = bb....bb

aa....aa: Application display name

bb....bb: Maintenance information

Description

The application definition cannot be converted because the resource specified in the reference resolution has a problem.

An attempt to deploy an application, in which a resource with a problem is specified in the reference resolution, will fail

Action

After migration of the environment finishes, reset this resource.

KDJE37062-W

The application definition cannot be converted because the resource specified for the reference resolution has a problem. display-name = aa....aa, res-name(in cmp-map) = bb....bb

aa....aa: Application display name

bb....bb: Maintenance information

Description

The application definition cannot be converted because the resource specified in the reference resolution has a problem.

An attempt to deploy an application, in which a resource with a problem is specified in the reference resolution, will fail

Action

After migration of the environment finishes, reset this resource.

KDJE37063-W

The resource definition cannot be converted. display-name = aa....aa, Reason = bb....bb

aa....aa: Resource display name

bb....bb: Maintenance information

Description

The resource definition cannot be converted.

The resource containing this DD will not be migrated. The application, in which this resource is specified in the reference resolution, cannot be deployed.

Action

After migration of the environment finishes, reset this resource.

KDJE37064-W

An attempt to output the audit log has failed. (detail = aa....aa)

aa....aa: Detailed information

Description

An attempt to output the audit log failed.

Action

Remove the cause of the failure by referencing the detailed information or messages output before this message.

Alternatively, remove the cause of the failure by referencing the audit log.

KDJE37103-E

Usage:

Format1: cjimportres [servername] [-nameserver providerURL] -type ejb -f ejb-jarfilename [-f ejb-jarfilename ...]

Format2: cjimportres [servername] [-nameserver providerURL] -type war -f warfilename [-f warfilename ...]

Format3: cjimportres [servername] [-nameserver providerURL] -type datasource -resname datasourcedisplayname -c datasourcefilename -f JDBCdriverfilename [-f JDBCdriverfilename ...]

Description: This message describes the usage method of the cjimportres command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37105-E

Usage:

Format1: cjaddapp [servername] [-nameserver providerURL] -type ejb -name applicationname -resname ejb-jardisplayname [-resname ejb-jardisplayname ...]

Format2: cjaddapp [servername] [-nameserver providerURL] -type war -name applicationname -resname wardisplayname [-resname wardisplayname ...]

Format3: cjaddapp [servername] [-nameserver providerURL] -type filter -name applicationname -warname wardisplayname -c filterpropertyfilename [-c filterpropertyfilename ...]

Format4: cjaddapp [servername] [-nameserver providerURL] -type rar -name applicationname -resname rardisplayname [-resname rardisplayname ...]

Description: This message describes the usage method of the cjaddapp command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37107-E

Usage:

Format1: cjdeleteres [servername] [-nameserver providerURL] -type ejb -resname ejb-jardisplayname [-resname ejb-jardisplayname ...]

Format2: cjdeleteres [servername] [-nameserver providerURL] -type war -resname wardisplayname [-resname wardisplayname ...]

Format3: cjdeleteres [servername] [-nameserver providerURL] -type datasource -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format4: cjdeleteres [servername] [-nameserver providerURL] -type mail -resname maildisplayname [-resname maildisplayname ...]

Format5: cjdeleteres [servername] [-nameserver providerURL] -type rar -resname rardisplayname [-resname rardisplayname ...]

Description: This message describes the usage method of the cjdeleteres command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37108-E

Usage:

Format1: cjgetappprop [servername] [-nameserver providerURL] -name applicationname [-encoding encoding-name] -c applicationpropertyfilename

Format2: cjgetappprop [servername] [-nameserver providerURL] -name applicationname -type ejb -resname higherresourcename[/lowerresourcename] [-encoding encoding-name] -c applicationpropertyfilename

Format3: cjgetappprop [servername] [-nameserver providerURL] -name applicationname -type war -resname higherresourcename[/lowerresourcename] [-encoding encoding-name] -c applicationpropertyfilename

Format4: cjgetappprop [servername] [-nameserver providerURL] -name applicationname -type rar -resname rardisplayname [-encoding encoding-name] -c applicationpropertyfilename

Description: This message describes the usage method of the cjgetappprop command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37109-E

Usage:

Format1: cjgetresprop [servername] [-nameserver providerURL] -type ejb -resname higherresourcename[/lowerresourcename] [-encoding encoding-name] -c ejb-jarpropertyfilename

Format2: cjgetresprop [servername] [-nameserver providerURL] -type war -resname higherresourcename[/lowerresourcename] [-encoding encoding-name] -c warpropertyfilename

Format3: cjgetresprop [servername] [-nameserver providerURL] -type datasource -resname datasourcedisplayname [-encoding encoding-name] -c datasourcepropertyfilename

Format4: cjgetresprop [servername] [-nameserver providerURL] -type mail -resname maildisplayname [-encoding encoding-name] -c mailpropertyfilename

Format5: cjgetresprop [servername] [-nameserver providerURL] -type rar -resname rardisplayname [-encoding encoding-name] -c rarpropertyfilename

Description: This message describes the usage method of the cjgetresprop command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37110-E

Usage:

Format1: cjsetappprop [servername] [-nameserver providerURL] -name applicationname -c applicationpropertyfilename

Format2: cjsetappprop [servername] [-nameserver providerURL] -name applicationname -type ejb -resname higherresourcename[/lowerresourcename] -c applicationpropertyfilename

Format3: cjsetappprop [servername] [-nameserver providerURL] -name applicationname -type war -resname higherresourcename[/lowerresourcename] -c applicationpropertyfilename

Format4: cjsetappprop [servername] [-nameserver providerURL] -name applicationname -type rar -resname rardisplayname -c applicationpropertyfilename

Description: This message describes the usage method of the cjsetappprop command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37111-E

Usage:

Format1: cjsetresprop [servername] [-nameserver providerURL] -type ejb -resname higherresourcename[/lowerresourcename] -c ejb-jarpropertyfilename

Format2: cjsetresprop [servername] [-nameserver providerURL] -type war -resname higherresourcename[/lowerresourcename] -c warpropertyfilename

Format3: cjsetresprop [servername] [-nameserver providerURL] -type datasource -resname datasourcedisplayname -c datasourcepropertyfilename

Format4: cjsetresprop [servername] [-nameserver providerURL] -type mail -resname maildisplayname -c mailpropertyfilename

Format5: cjsetresprop [servername] [-nameserver providerURL] -type rar -resname rardisplayname -c rarpropertyfilename

Description: This message describes the usage method of the cjsetresprop command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37112-E

Usage:

Format1: cjcopyres [servername] [-nameserver providerURL] -type ejb -src ejb-jardisplayname -dst ejb-jardisplayname

Format2: cjcopyres [servername] [-nameserver providerURL] -type war -src wardisplayname -dst wardisplayname

Format3: cjcopyres [servername] [-nameserver providerURL] -type datasource -src datasourcedisplayname -dst datasourcedisplayname

Format4: cjcopyres [servername] [-nameserver providerURL] -type mail -src maildisplayname -dst maildisplayname

Format5: cjcopyres [servername] [-nameserver providerURL] -type rar -src rardisplayname -dst rardisplayname

Description: This message describes the usage method of the cjcopyres command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37113-E

Usage:

Format1: cjlistapp [servername] [-nameserver providerURL]

Format2: cjlistapp [servername] [-nameserver providerURL] [-test] -name applicationname -type ejb [-resname higherresourcename]

Format3: cjlistapp [servername] [-nameserver providerURL] [-test] -name applicationname -type war [-resname higherresourcename]

Format4: cjlistapp [servername] [-nameserver providerURL] [-test] -name applicationname -type rar [-spec | -resname rardisplayname -outbound | -resname rardisplayname -inbound | -resname rardisplayname -listenertype messagelistenertypename]

Description: This message describes the usage method of the cjlistapp command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37114-E

Usage:

Format1: cjlistres [servername] [-nameserver providerURL] -type ejb [-resname higherresourcename]

Format2: cjlistres [servername] [-nameserver providerURL] -type war [-resname higherresourcename]

Format3: cjlistres [servername] [-nameserver providerURL] -type datasource

Format4: cjlistres [servername] [-nameserver providerURL] -type mail

Format5: cjlistres [servername] [-nameserver providerURL] -type rar [-spec | -resname rardisplayname -outbound | -resname rardisplayname -inbound | -resname rardisplayname -listenertype messagelistenertypename]

Description: This message describes the usage method of the cjlistres command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37119-E

Usage:

Format1: cjaddsec [servername] [-nameserver providerURL] -type user -name username -password password

Format2: cjaddsec [servername] [-nameserver providerURL] -type role -name rolename

Description: This message describes the usage method of the cjaddsec command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37120-E

Usage:

Format1: cjdeletesec [servername] [-nameserver providerURL] -type user -name username

Format2: cjdeletesec [servername] [-nameserver providerURL] -type role -name rolename

Description: This message describes the usage method of the cjdeletesec command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37121-E

Usage:

Format1: cjlistsec [servername] [-nameserver providerURL] -type user

Format2: cjlistsec [servername] [-nameserver providerURL] -type user -name username

Format3: cjlistsec [servername] [-nameserver providerURL] -type role

Format4: cjlistsec [servername] [-nameserver providerURL] -type role -name rolename

Description: This message describes the usage method of the cjlistsec command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37122-E

Usage: cjmapsec [servername] [-nameserver providerURL] -role rolename -user username [-user username ...]

Description: This message describes the usage method of the cjmapsec command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37123-E

Usage: cjunmapsec [servername] [-nameserver providerURL] -role rolename -user username [-user username ...]

Description: This message describes the usage method of the cjunmapsec command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37125-E

Usage:

Format1: cjclearpool [servername] [-nameserver providerURL] [-type jdbc] [-mode {normal|plan}] -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format2: cjclearpool [servername] [-nameserver providerURL] -type connector [-mode {normal|plan}] -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format3: cjclearpool [servername] [-nameserver providerURL] -type connector [-mode {normal|plan}] [-test] -name applicationdisplayname -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format4: cjclearpool [servername] [-nameserver providerURL] [-mode {normal|plan}] -resall

Description: This message describes the usage method of the cjclearpool command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37126-E

Usage: cjgetrarprop [servername] [-nameserver providerURL] -resname displayname [-encoding encoding-name] -c propertyfilename

Description: This message describes the usage method of the cjgetrarprop command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37127-E

Usage: cjsetrarprop [servername] [-nameserver providerURL] -resname displayname -c propertyfilename

Description: This message describes the usage method of the cjsetrarprop command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37128-E

Usage:

Format1: cjclosecn [servername] [-nameserver providerURL] -l [-verbose] -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format2: cjclosecn [servername] [-nameserver providerURL] -l [-verbose] -resall

Format3: cjclosecn [servername] [-nameserver providerURL] -t seconds -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format4: cjclosecn [servername] [-nameserver providerURL] -t seconds -resall

Format5: cjclosecn [servername] [-nameserver providerURL] -resname datasourcedisplayname -cid connectionID [-cid connectionID ...]

Description: This message describes the usage method of the cjclosecn command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37129-E

Usage: cjdeployrar [servername] [-nameserver providerURL] -resname rardisplayname [-resname rardisplayname ...]

Description: This message describes the usage method of the cjdeployrar command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37130-E

Usage: cjundeployrar [servername] [-nameserver providerURL] -resname rardisplayname [-resname rardisplayname ...]

Description: This message describes the usage method of the cjundeployrar command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37131-E

Usage: cjstartrar [servername] [-nameserver providerURL] -resname rardisplayname

Description: This message describes the usage method of the cjstartrar command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37132-E

Usage: cjstoprar [servername] [-nameserver providerURL] -resname rardisplayname

Description: This message describes the usage method of the cjstoprar command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37133-E

Usage:

Format1: cjlistrar [servername] [-nameserver providerURL] [-clusterpool] [-spec]

Format2: cjlistrar [servername] [-nameserver providerURL] -resname displayname -outbound

Format3: cjlistrar [servername] [-nameserver providerURL] -resname displayname -inbound

Format4: cjlistrar [servername] [-nameserver providerURL] -resname displayname -listenertype messagelistenertypename

Description: This message describes the usage method of the cjlistrar command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37134-E

Usage: cjwebeditpool [-host hostname] [-port portnumber] -c poolsettingfilename

Description: This message describes the usage method of the cjwebeditpool command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37135-E

Usage: cjwebchangedbid [-host hostname] [-port portnumber] -olddbid DatabaseID -newdbid DatabaseID

Description: This message describes the usage method of the cjwebchangedbid command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37136-E

Usage: cjwebdeletepool [-host hostname] [-port portnumber] -dbid DatabaseID

Description: This message describes the usage method of the cjwebdeletepool command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37137-E

Usage:

Format1: cjweblistpool [-host hostname] [-port portnumber] -listtype dblist [-f outputfilename]

Format2: cjweblistpool [-host hostname] [-port portnumber] -dbid DatabaseID -listtype poollist [-f outputfilename]

Format3: cjweblistpool [-host hostname] [-port portnumber] -dbid DatabaseID -userid UserID -listtype connectionlist [-f outputfilename]

Format4: cjweblistpool [-host hostname] [-port portnumber] -listtype all [-f outputfilename]

Description: This message describes the usage method of the cjweblistpool command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37138-E

Usage: cjwebclearpool [-host hostname] [-port portnumber] [-mode {normal |plan}] [-dbid DatabaseID]

Description: This message describes the usage method of the cjwebclearpool command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37139-E

Usage:

Format1: cjwebclosepool [-host hostname] [-port portnumber] -dbid DatabaseID -type connectionid -cid connectionID

Format2: cjwebclosepool [-host hostname] [-port portnumber] -dbid DatabaseID -type timeout -time timeout

Description: This message describes the usage method of the cjwebclosepool command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37140-E

Usage: cjimportlibjar [servername] [-nameserver providerURL] [-test] -name applicationname -f libraryjarfilename [-f libraryjarfilename ...]

Description: This message describes the usage method of the cjimportlibjar command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37141-E

Usage: cjdeletelibjar [servername] [-nameserver providerURL] [-test] -name applicationname -f libraryjarfilename [-f libraryjarfilename ...]

Description: This message describes the usage method of the cjdeletelibjar command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37142-E

Usage: cjlistlibjar [servername] [-nameserver providerURL] [-test] -name applicationname

Description: This message describes the usage method of the cjlistlibjar command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37143-E

Usage: cjreplaceapp [servername] [-nameserver providerURL] [-test] -name applicationname -f {earfilename | warfilename} [-t timeoutseconds] [-replaceDD]

Description: This message describes the usage method of the cjreplaceapp command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37144-E

Usage: cjupdateapp [servername] [-nameserver providerURL] -name applicationname -c updatelistfilename [-t timeoutseconds]

Description: This message describes the usage method of the cjupdateapp command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37145-E

Usage:

Format1: cjchmodapp [servername] [-nameserver providerURL] -test -name applicationname -mode normal

Format2: cjchmodapp [servername] [-nameserver providerURL] -name applicationname -mode test

Description: This message describes the usage method of the cjchmodapp command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37146-E

Usage: cjgetstubsjar [servername] [-nameserver providerURL] [-test] -name applicationname -d stubsjardirectory

Description: This message describes the usage method of the cjgetstubsjar command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37147-E

Usage:

Format1: cjtestres [servername] [-nameserver providerURL] -type datasource -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format2: cjtestres [servername] [-nameserver providerURL] -type mail -resname maildisplayname [-resname maildisplayname ...]

Format3: cjtestres [servername] [-nameserver providerURL] -type rar -resname rardisplayname [-resname rardisplayname ...]

Format4: cjtestres [servername] [-nameserver providerURL] [-test] -name applicationname -type rar -resname rardisplayname [-resname rardisplayname ...]

Description: This message describes the usage method of the cjtestres command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37148-E

Usage:

Format1: cjlistthread [servername] [-nameserver providerURL]

Format2: cjlistthread [servername] [-nameserver providerURL] -detail

Description: This message describes the usage method of the cjlistthread command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37149-E

Usage: Format1: cjstopthread [servername] [-nameserver providerURL] -tid threadID [-tid threadID]

Description: This message describes the usage method of the cjstopthread command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37150-E

Usage: cjrenameapp [servername] [-nameserver providerURL] [-test] -name applicationname -newname newapplicationname

Description: This message describes the usage method of the cjrenameapp command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37151-E

Usage: cjexportrar [servername] [-nameserver providerURL] -f resourcefilename -resname displayname [ -raw | -normal]

Description: This message describes the usage method of the cjexportrar command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37152-E

Usage: cjlisttrn [servername] [-nameserver providerURL] [-gid globalTransactionId] [-pending] [-time elapsedTime] [-bqual] [-tp1]

Description: This message describes the usage method of the cjlisttrn command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37153-E

Usage: cjlisttrnfile [servername] [-gid globalTransactionId] [-bqual]

Description: This message describes the usage method of the cjlisttrnfile command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37154-E

Usage:

Format1: cjlistpool [servername] [-nameserver providerURL] -resname rardisplayname [-resname rardisplayname ...]

Format2: cjlistpool [servername] [-nameserver providerURL] [-test] -name applicationname -resname rardisplayname [-resname rardisplayname ...]

Format3: cjlistpool [servername] [-nameserver providerURL] -resall

Description: This message describes the usage method of the cjlistpool command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37155-E

Usage: cjdeletejb [servername] [-nameserver providerURL] -resname javabeansresourcedisplayname [-resname javabeansresourcedisplayname ...]

Description: This message describes the usage method of the cjdeletejb command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37156-E

Usage:cjgetjbprop [servername] [-nameserver providerURL] -resname javabeansresourcedisplayname [encoding encoding-name] -c javabeansresourcepropertyfilename

Description: This message describes the usage method of the cjgetjbprop command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37157-E

Usage:cjsetjbprop [servername] [-nameserver providerURL] -resname javabeansresourcedisplayname -c javabeansresourcepropertyfilename

Description: This message describes the usage method of the cjsetjbprop command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37158-E

Usage: cjlistjb [servername] [-nameserver providerURL]

Description: This message describes the usage method of the cjlistjb command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37159-E

Usage: cjstartjb [servername] [-nameserver providerURL] -resname javabeansresourcedisplayname

Description: This message describes the usage method of the cjstartjb command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37160-E

Usage: cjstopjb [servername] [-nameserver providerURL] -resname javabeansresourcedisplayname

Description: This message describes the usage method of the cjstopjb command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37161-E

Usage:cjreloadapp [servername] [-nameserver providerURL] [-test] -name applicationname [-t timeoutseconds]

Description: This message describes the usage method of the cjreloadapp command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37162-E

Usage:

Format1: cjimportjb [servername] [-nameserver providerURL] -f javabeansresourcejarfilename -c propertyfilename

Format2: cjimportjb [servername] [-nameserver providerURL] -d javabeansresourcedirectoryname -c propertyfilename

Description: This message describes the usage method of the cjimportjb command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37163-E

Usage: cjsuspendpool [servername] [-nameserver providerURL] -resname rardisplayname [-resname rardisplayname ...]

Description: This message describes the usage method of the cjsuspendpool command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37164-E

Usage: cjresumepool [servername] [-nameserver providerURL] -resname rardisplayname [-resname rardisplayname ...]

Description: This message describes the usage method of the cjresumepool command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37165-E

Usage: cjgencmpsql [servername] [-nameserver providerURL] [-test] -name applicationname [-resname ejbjardisplayname/ejbdisplayname]

Description: This message describes the usage method of the cjgencmpsql command.
Action: Check the arguments and value of the command, and then re-execute the command.

KDJE37166-E

Usage: cjcommittrn [servername] [-nameserver providerURL] -gid globalTransactionId

Description: This message describes how to use the cjcommittrn command.
Action: Check the arguments and values of the command, and then re-execute the command.

KDJE37167-E

Usage: cjrollbacktrn [servername] [-nameserver providerURL] -gid globalTransactionId

Description: This message describes how to use the cjrollbacktrn command.
Action: Check the arguments and values of the command, and then re-execute the command.

KDJE37168-E

Usage: cjforgettrn [servername] [-nameserver providerURL] -gid globalTransactionId

Description: This message describes how to use the cjforgettrn command.
Action: Check the arguments and values of the command, and then re-execute the command.

KDJE37170-E

Usage:

Format1: cjimportwar [servername] [-nameserver providerURL] -f warfilename [-name applicationname] [-contextroot contextroot] [-c cosminexus.xml]

Format2: cjimportwar [servername] [-nameserver providerURL] -a wardirectorypath [-name applicationname] [-contextroot contextroot] [-c cosminexus.xml]

Description: This message describes how to use the cjimportwar command.
Action: Check the arguments and values of the command, and then re-execute the command.

KDJE37171-E

Usage:

Format1: cjdeljbatchjobs [servername] [-nameserver providerURL] -list -name applicationname -day day [-all] -f file_path

Format2: cjdeljbatchjobs [servername] [-nameserver providerURL] -delete -f file_path [-t timeoutseconds]

Description: This message describes how to use the cjdeljbatchjobs command.
Action: Check the arguments and values of the command, and then re-execute the command.

KDJE37200-E

The required option aa....aa has not been specified.

aa....aa: Option name

Description

The required option is not specified.

The command execution will be interrupted.

Action

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

KDJE37201-E

No value is specified. (option = [aa....aa])

aa....aa: Option name

Description

The value corresponding to the option name is not specified.

The command execution will be interrupted.

Action

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

KDJE37202-E

No option is specified.

Description

Other than the server name, no option is specified in the parameters.

The command execution will be interrupted.

Action

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

KDJE37203-E

The same options have been specified repeatedly. (option = [aa....aa])

aa....aa: Option name

Description

The same options have been specified multiple times.

The command execution will be interrupted.

Action

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

KDJE37204-E

The specified option is invalid. (option = [aa....aa])

aa....aa: Option name

Description

An invalid option is specified.

The command execution will be interrupted.

Action

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

KDJE37205-E

Different export types have been specified simultaneously.

Description

Different export type options have been specified simultaneously.

The command execution will be interrupted.

Action

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

KDJE37206-E

The specified value is invalid. (option = [aa....aa], value = [bb....bb])

aa....aa: Option name

bb....bb: Option value

Description

An invalid option value is specified.

The command execution will be interrupted.

Action

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

KDJE37207-E

aa....aa cannot be specified simultaneously with bb....bb.

aa....aa: Option name

bb....bb: Option name

Description

Options that cannot be specified simultaneously have been specified simultaneously.

The command execution will be interrupted.

Action

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

KDJE37208-E

The necessary -type connector for -name has not been specified.

Description

The necessary -type connector for -name is not specified.

The command execution will be interrupted.

Action

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

KDJE37209-E

The specified directory does not exist. [aa....aa]

aa....aa: File path

Description

The specified path does not exist.

The command execution will be interrupted.

Action

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

KDJE37210-E

The specified path is not a directory. [aa....aa]

aa....aa: File path

Description

The specified path is not a directory.

The command execution will be interrupted.

Action

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

KDJE37211-E

Cannot access directory. [aa....aa]

aa....aa: File path

Description

The specified path cannot be accessed.

The command execution will be interrupted.

Action

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

KDJE37212-E

An invalid provider URL is specified. (error details = aa....aa)

aa....aa: Error details

Description

An invalid provider URL is specified.

The command execution will be interrupted.

Action

Revise the value of the provider URL, and then re-execute the command.

KDJE37213-E

The same tag is specified more than once. (name = [aa....aa])

aa....aa: Tag name

Description

The same tag is specified more than once.

The command execution will be interrupted.

Action

Check the tag specification in the property file.

KDJE37300-E

The aa....aa command failed. Contact the system administrator.

aa....aa: Command name

Description

The command has failed because an unexpected exception occurred.

The command execution will be interrupted.

Action

If the exception messages starting with nnnn (n is a number) is followed by this message , see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory. If you do not understand the cause, acquire the maintenance information, and then contact the system administrator.

KDJE37301-E

Another command is already running.

Description

Another command is already running.

The command execution will be interrupted.

Action

Wait for the command to finish, and then re-execute the command.

KDJE37302-E

The server was not found. (name = [aa....aa])

aa....aa: Server name

Description

The server was not found.

The command execution will be interrupted.

Action

Start the J2EE server if it is not already started. Alternatively, revise the command parameters, and then re-execute the command.

KDJE37303-E

The Naming Service was not found.

Description

The Naming Service was not found.

The command execution will be interrupted.

Action

Invoke the Naming Service if it is not already invoked. Alternatively, revise the command parameters, and then re-execute the command.

KDJE37304-E

aa....aa was not found.

aa....aa: Application name, parent resource display name, parent resource display name / subordinate resource display name, Resource adapter name, or JavaBeans resource display name, user name, or role name

Description

aa....aa was not found.

The command execution will be interrupted.

Action

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

KDJE37305-E

aa....aa already exists. (name = [bb....bb])

aa....aa: Type (Application, Lookup name, EJB-JAR, Ejb-name, WAR, Datasource, Mail, User, Role, RAR, Library JAR, Filter, Filter-name, or JavaBeans resource)

bb....bb: Application name, Lookup name, EJB-JAR display name, Ejb-name, WAR display name, Datasource display name, Mail display name, User name, Role name, RAR display name, Library JAR name, Filter display name, Filter-name, or JavaBeans resource display name

Description

bb....bb already exists.

The command execution will be interrupted.

Action

Check the command parameters or check that the cjlist-series command corresponds to aa....aa, and then re-execute the command.

KDJE37307-E

aa....aa is running. (name = [bb....bb])

aa....aa: Type (Application)

bb....bb: Application name

Description

Application (bb....bb) is running.

The command execution will be interrupted.

Action

Terminate the application, and then re-execute the command.

KDJE37309-E

aa....aa is being used in one or more applications. (name = [bb....bb])

aa....aa: Type (Datasource or Mail)

bb....bb: Datasource display name or mail display name

Description

bb....bb is being used in one or more applications.

The command execution will be interrupted.

Action

Delete the applications in which bb....bb is in use, and then re-execute the command.

KDJE37310-E

aa....aa is being used by one or more running applications. (name = [bb....bb])

aa....aa: Type (Datasource or Mail)

bb....bb: Datasource display name or mail display name

Description

One or more running applications are using bb....bb.

The command execution will be interrupted.

Action

Terminate the applications in which bb....bb is in use, and then re-execute the command.

KDJE37311-E

The file type is set to directory. (path = [aa....aa])

aa....aa: File path

Description

The directory was specified.

The command execution will be interrupted.

Action

Specify the correct file path, and then re-execute the command.

KDJE37312-E

The file does not exist. (path = [aa....aa])

aa....aa: File path

Description

The file does not exist.

The command execution will be interrupted.

Action

Specify the correct file path, and then re-execute the command.

KDJE37313-E

aa....aa has already been mapped. (name = [bb....bb])

aa....aa: Type (User)

bb....bb: User name

Description

The user (bb....bb) has already been mapped.

The command execution will be interrupted.

Action

Un-map, and then re-execute the command.

KDJE37314-E

aa....aa has not been mapped yet. (name = [bb....bb])

aa....aa: Type (User)

bb....bb: User name

Description

The user (bb....bb) is not mapped yet.

The command execution will be interrupted.

Action

Map, and then re-execute the command.

KDJE37316-E

Deployment Descriptor was not found. (path = [aa....aa])

aa....aa: File path

Description

The DD was not found.

The command execution will be interrupted.

Action

Revise the file contents, and then re-execute the command.

KDJE37317-E

An attempt to read the aa....aa file has failed. (path = [bb....bb], detail = [cc....cc])

aa....aa: Type (Application All property, Application property, EJB-JAR property, Session Bean property, Entity Bean property, WAR property, Servlet property, Datasource property, Mail property, Datasource configuration, RAR property, Filter property or JavaBeans resource property)

bb....bb: File path

cc....cc: Exception information from the XML user

Description: An attempt to read the file (aa....aa) has failed. The command execution will be interrupted.
Action: Revise the file contents, and then re-execute the command.

KDJE37318-E

No DataSource or Driver interface is specified.

Description

No DataSource or Driver interface is specified.

The command execution will be interrupted.

Action

Revise the contents of the DataSource setup file, and then re-execute the command.

KDJE37319-E

No DataSource or Driver interface was found. (name = [aa....aa])

aa....aa: Interface class name

Description

No DataSource or Driver interface was found.

The command execution will be interrupted.

Action

Specify the correct file path of the JDBC driver, and then re-execute the command.

KDJE37321-E

No property value is specified. (name = [aa....aa])

aa....aa: Tag name

Description

Either aa....aa is not specified or the value of aa....aa is a null character.

The command execution will be interrupted.

Action

Confirm that the mandatory tags have been specified or the specification of aa....aa is correct, and then re-execute the command.

KDJE37322-E

The property value is invalid. (name = [aa....aa], value = [bb....bb])

aa....aa: Tag name

bb....bb: Tag value

Description

The value of aa....aa is invalid.

The command execution will be interrupted.

Action

Check the value of aa....aa, and then re-execute the command.

KDJE37323-E

The resource does not exist.

Description

The resource registered in the pool does not exist.

The command execution will be interrupted.

Action

Check the value of the option -resname, and then re-execute the command.

KDJE37324-E

aa....aa produced an error. The command has failed.

aa....aa: Type (J2EE server, I/O, Naming Service, and OTS)

Description

An error occurred in aa....aa.

The command execution will be interrupted.

Action

See the message displayed before this message, check the operation environment (J2EE server, Naming Service, and OTS) during the execution of the command, and then eliminate the cause of the error. Note that if the exception messages starting with nnnn (n is a number) are followed by this message, see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory.

Example causes and actions are as follows:

If this message is displayed in a node switching system

The IP address or host name specified in the webserver.connector.http.permitted.hosts key of the user property file for the connection destination J2EE server (usrconf.properties) is incorrect. Revise the IP address or host name.
If this error occurs due to the settings for the data source attribute

The settings for the data source attribute are invalid. Check whether the settings are invalid and, if necessary, revise the settings.

KDJE37325-E

No aa....aa tag is specified.

aa....aa: Tag name

Description

No aa....aa tag is specified.

The command execution will be interrupted.

Action

Set the value of the tag shown in the error message.

KDJE37326-E

aa....aa command failed.

bb....bb.

aa....aa: Type (Import, Replace or Reload)

bb....bb: Details

Description: An attempt to import, replace, or reload the application has failed. The command execution will be interrupted.
Action: Take action as per the error message.

KDJE37328-E

File format is invalid.

Description: The command execution will be interrupted because the file format is invalid.
Action: Revise the file format.

KDJE37329-E

aa....aa's connection was not found or is not being used.

aa....aa: Connection ID

Description

The connection (aa....aa) was not found or is not being used.

The command execution will be interrupted.

Action

Make sure that the specified connection ID is correct.

KDJE37330-E

The command could not be started in the current J2EE status. This command runs in basic mode.

Description

The J2EE server is not in the basic mode.

The command execution will be interrupted.

Action

Make sure that the startup mode of the J2EE server is set to Basic.

KDJE37331-E

aa....aa is already deployed. (name = [bb....bb])

aa....aa: Type (RAR)

bb....bb: RAR display name

Description

bb....bb is already deployed.

The command execution will be interrupted.

Action

Un-deploy, and then re-execute the command.

KDJE37332-E

The same display name as for aa....aa exists in the J2EE Application. (name = [bb....bb], J2EE Application name = [cc....cc])

aa....aa: Type (RAR)

bb....bb: RAR display name

cc....cc: J2EE application name

Description

A RAR with the same display name as bb....bb exists in the J2EE application (cc....cc).

The command execution will be interrupted.

Action

Change the display name so that it is not same, and then re-execute the command.

KDJE37334-E

aa....aa cannot be undeployed. Retry after rebooting the J2EE Server. (name = [bb....bb])

aa....aa: Type (RAR)

bb....bb: RAR display name

Description

bb....bb cannot be un-deployed.

The command execution will be interrupted.

Action

Restart the J2EE server, and then re-execute the command.

KDJE37335-E

aa....aa is running. (name=[bb....bb])

aa....aa: Type (RAR or JavaBeans resource)

bb....bb: RAR display name or JavaBeans resource display name

Description

bb....bb is running.

The command execution will be interrupted.

Action

Stop bb....bb, and then re-execute the command.

KDJE37336-E

aa....aa is not running. (name=[bb....bb])

aa....aa: Type (RAR or JavaBeans resource)

bb....bb: RAR display name or JavaBeans resource display name

Description

bb....bb is not running.

The command execution will be interrupted.

Action

Start bb....bb, and then re-execute the command.

KDJE37337-E

Deploying failed. (name = [aa....aa])

aa....aa: RAR display name

Description

Deploying failed.

The command execution will be interrupted.

Action

Contact the system administrator.

KDJE37341-E

DatabaseID = [aa....aa] was not found.

aa....aa: Database ID

Description

The pool management information of the database (aa....aa) does not exist.

The command execution will be interrupted.

Action

Check the pool management information with the cjweblistpool command, and then re-execute the command.

KDJE37342-E

DatabaseID already exists. (DatabaseID = [aa....aa])

aa....aa: Database ID

Description

The pool management information of the database (aa....aa) already exists.

The command execution will be interrupted.

Action

Check the pool management information with the cjweblistpool command, and then re-execute the command.

KDJE37343-E

The list does not exist. (listtype = [aa....aa], DatabaseID = [bb....bb])

aa....aa: List type

bb....bb: Database ID

Description

The database (bb....bb) is not in use.

The command execution will be interrupted.

Action

Display the database list with the -listtype dblist option, check the value of bb....bb, and then re-execute the command.

KDJE37344-E

The list does not exist. (listtype = [aa....aa], DatabaseID = [bb....bb], UserID = [cc....cc])

aa....aa: List type

bb....bb: Database ID

cc....cc: User ID

Description: The database ID (bb....bb) or the user ID (cc....cc) is not being used. The command execution will be interrupted.
Action: Display the database list and the pool list with the -listtype dblist and -listtype poollist options, check the value, and then re-execute the command.

KDJE37345-E

No DatabaseID, ClassName, or URL is specified.

Description

The database ID, class name, or URL is not specified.

The command execution will be interrupted.

Action

Check the contents of the pool management information setup file, and then re-execute the command.

KDJE37346-E

There is no scheduled bean.

Description

The Bean invoked through CTM is not the one specified.

The command execution will be interrupted.

Action

Make sure that the setting of the Bean is correct.

KDJE37347-E

The Parallel count of the Scheduling tag cannot be greater than the pooled instances maximum.

Description

In the Bean invoked through CTM, the value specified in Maximum is lesser than that specified in Parallel count.

The command execution will be interrupted.

Action

Make sure that the values of Maximum and Parallel count are correct.

KDJE37348-E

The aa....aa command failed. (detail = [bb....bb])

aa....aa: Command name (cjwebeditpool, cjwebchangedbid, cjwebdeletepool, cjweblistpool, cjwebclearpool, or cjwebclosepool)

bb....bb: Exception information from the connection pool API

Description

The command (aa....aa) has failed.

The command execution will be interrupted.

Action

Contact the system administrator.

KDJE37349-E

The aa....aa command failed due to a [bb....bb] error.

aa....aa: Command name (cjwebeditpool, cjwebchangedbid, cjwebdeletepool, cjweblistpool, cjwebclearpool, or cjwebclosepool)

bb....bb: Type (Connection, I/O, Permission, or Version)

Description

The command (aa....aa) has failed due to the occurrence of an error (bb....bb).

The command execution will be interrupted.

Action

When bb....bb is either Connection or I/O: Revise the host name and the port number, confirm that the Web container server is running, and then re-execute the command.
When bb....bb is Permission: Check the settings of the connection destination Web container server (webserver.connector.http.permitted.hosts), and then re-execute the command.
When bb....bb is Version: Match the version of the Cosminexus Component Container of the host executing the server and the command.

KDJE37350-E

aa....aa cannot be used with this Edition.

aa....aa: Tag name

Description

The tag (aa....aa) cannot be used with this edition of the Application Server.

The command execution will be interrupted.

Action

Check the edition settings of the Application Server.

KDJE37351-E

The property value is invalid.

Name = [thread-control-max-threads], Value = [aa....aa]

Name = [thread-control-exclusive-threads], Value = [bb....bb]

thread-control-max-threads must specify a value beyond that of thread-control-exclusive-threads.

aa....aa: Maximum number of concurrently executing threads of each Web application

bb....bb: Number of dedicated threads

Description

The value specified in the maximum number of concurrently executing threads (aa....aa) of each Web application is lesser than the number of dedicated threads (bb....bb).

The command execution will be interrupted.

Action

Make sure that the specified maximum number of concurrently executing threads of each Web application, or the number of dedicated threads is correct.

KDJE37352-E

aa....aa cannot be used with this configuration.

webserver.container.thread_control.enabled = false

aa....aa: Tag name

Description

The tag (aa....aa) cannot be used with this setting.

The command execution will be interrupted.

Action

Check the setting of webserver.container.thread_control.enabled.

KDJE37353-E

An access from aa....aa is not permitted. Host name = bb....bb

aa....aa: IP address

bb....bb: Host name

Description: Access from aa....aa is not permitted. Host name = bb....bb
Action: The command execution will be interrupted. Check the settings of the connection destination Web container server (webserver.connector.http.permitted.hosts), and then re-execute the command.

KDJE37354-E

The version of Cosminexus Component Container is incompatible.

Host name = aa....aa, Reason code = (bb....bb, cc....cc).

aa....aa: Host name

bb....bb: Maintenance information 1

cc....cc: Maintenance information 2

Description

The version of Cosminexus Component Container is incompatible. Host name = aa....aa, Maintenance information = (bb....bb, cc....cc)

Action

The command execution will be interrupted. Match the version of the Cosminexus Component Container of the host executing the server and the command.

If the responsible factors cannot be resolved, acquire the maintenance information, and then contact maintenance personnel.

KDJE37356-E

The communication timeout occurred.

Description

A timeout occurred during the execution of the server management command.

The command execution will be interrupted.

Action

Make sure that no problem exists in the network environment. If no problem exists in the network environment, take the following actions:

In the case of a command in which the time for timeout can be specified in the argument, increase the value of the timeout specified in the argument, and then re-execute the command.
In the case of a command in which the time for timeout cannot be specified in the argument, revise the value of the key ejbserver.rmi.request.timeout of the user property file, and then re-execute the command.

KDJE37357-E

The same aa....aa have been specified repeatedly. (name = [bb....bb])

aa....aa: Type (library jar names)

bb....bb: Library JAR file name

Description

The same options have been specified multiple times.

The command execution will be interrupted.

Action

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

KDJE37358-E

The specified aa....aa does not exist. Path=[bb....bb]

aa....aa: Type (directory)

bb....bb: Path

Description

The specified path does not exist.

The command execution will be interrupted.

Action

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

KDJE37359-E

File type is not directory. Path=[aa....aa]

aa....aa: Path

Description

The specified path is not a directory.

The command execution will be interrupted.

Action

Specify the correct directory path, and then re-execute the command.

KDJE37360-E

The connected test of aa....aa failed.

aa....aa: Datasource display name, mail display name, or resource adapter display name

Description

The connection test has failed.

The command execution will be interrupted.

Action

Revise the connection information, and then re-execute the command.

KDJE37361-E

The file including runtime information has been specified. Path=[aa....aa]

aa....aa: Path

Description

The file containing the runtime information is specified.

The command execution will be interrupted.

Action

Specify a file (extension .ear) that does not include the runtime information.

KDJE37362-E

The application name specified to be -name option differs from the value of the display-name tag of the application.xml in an EAR file. Value=[aa....aa]

aa....aa: Application name generated from the specified value of the <display-name> tag or from the EAR file name

Description

The application name specified in -name option is different from the application name specified in the <display-name> tag of application.xml in the EAR file.

In the case of an EAR file that does not include application.xml, the application name specified in the -name option and the application name generated from the EAR file name are different.

Action

The command execution will be interrupted.

Revise the value of the <display-name> tag of application.xml, and then re-execute the command.

In the case of an EAR file that does not include application.xml, because the application name is generated from the EAR file name, revise the EAR file name, and then re-execute the command.

KDJE37363-E

The specified path is invalid. Path=[aa....aa]

aa....aa: Path

Description

An invalid path is specified.

The command execution will be interrupted.

Action

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

KDJE37364-E

A command cannot be executed in the state of this application. (name = [aa....aa], status = [bb....bb])

aa....aa: Application name

bb....bb: Application status

Description

A command cannot be executed in this state of the application.

The command execution will be interrupted.

Action

Revise the state of the application, and then re-execute the command.

KDJE37365-E

The following error occurred, but an application has been imported successfully.

Description: The import was successful, but an error occurred. For details on the error, see the messages output in continuation to this message.
Action: Revise the set information of the application based on the information of the messages output in continuation to this message.

KDJE37366-E

The following error occurred, but a resource adapter has been deployed successfully.

Description: The deployment was successful, but an error occurred. For details on the error, see the messages output in continuation to this message.
Action: Revise the set information of the resource adapter based on the information of the messages output in continuation to this message.

KDJE37367-W

A property value is invalid. ([aa....aa] = [bb....bb]) The default value [cc....cc] will be used.

aa....aa: Property name

bb....bb: Set property value

cc....cc: Default value

Description: The property value (bb....bb) is invalid. The processing continues with the default value (cc....cc).
Action: Check if the property value set in the user property file is correct.

KDJE37368-E

This command cannot execute in the current J2EE server mode.

Description

This command cannot be executed in the current J2EE server mode.

The command execution will be interrupted.

Action

Check the startup mode of the J2EE server.

KDJE37369-E

aa....aa is not a member resource adapter of the cluster connection pool.

aa....aa: Resource adapter display name

Description

aa....aa is not a member resource adapter of the cluster connection pool.

The command execution will be interrupted.

Action

Confirm that aa....aa is a member resource adapter of the cluster connection pool, and then re-execute the command.

KDJE37370-E

The connection pool is not running. (name = [aa....aa], connection pool status = [bb....bb])

aa....aa: Resource adapter display name

bb....bb: Connection pool status

Description

The connection pool of aa....aa is not started or reserved for starting. The connection pool is in bb....bb state.

The command execution will be interrupted.

Action

Restart aa....aa with the cjresumepool command, and then re-execute the command.

KDJE37371-E

The connection pool is not suspended. (name = [aa....aa], connection pool status = [bb....bb])

aa....aa: Resource adapter display name

bb....bb: Connection pool status

Description

aa....aa is not automatically suspended, manually suspended, reserved for automatic suspension, or reserved for manual suspension. The connection pool is in bb....bb state.

The command execution will be interrupted.

Action

When the connection pool has started or is reserved for starting:: You need not take any action because the connection pool has already started.
When the connection pool is blocked automatically or manually:: Wait until the connection pool will be suspended either automatically or manually, and then re-execute the command.
When the connection pool is resuming automatically, or is being resumed manually:: The connection pool is now resuming. Please wait.

KDJE37372-E

The root resource adapter is not supported. (name = [aa....aa])

aa....aa: Resource adapter display name

Description

aa....aa is a root resource adapter. Commands cannot be executed for the root resource adapter.

The command execution will be interrupted.

Action

In -resname, specify a resource adapter display name other than the root resource adapter, and then re-execute the command.

KDJE37373-E

SQL cannot be generated because the CMP2.x entity bean field is not mapped to a table in the database. (name = [aa....aa])

aa....aa: Ejb-name

Description: The SQL cannot be generated because the CMP2.x Entity Bean field is not mapped to a table in the database.
Action: Map the CMP2.x Entity Bean field to a table in the database, and then re-execute the command.

KDJE37375-E

A command cannot be executed in an application with the deployment directory format. (name = [aa....aa])

aa....aa: Application name

Description: Commands cannot be executed in an expanded archive format application.
Action: Specify an archive format application, and then re-execute the command.

KDJE37376-E

A command cannot be executed in an application with the archive format. (name = [aa....aa])

aa....aa: Application name

Description: Commands cannot be executed in an archive format application.
Action: Specify an expanded archive format application, and then re-execute the command.

KDJE37377-E

aa....aa is not a CMP2.X Entity Bean.

aa....aa: Ejb-name

Description: aa....aa is not a CMP2.X Entity Bean.
Action: Specify the name of a CMP2.x Entity Bean in -resname, and then re-execute the command.

KDJE37378-E

The same attribute value tag has been specified more than once. (name = [aa....aa], attribute = [bb....bb], value = [cc....cc])

aa....aa: Tag name

bb....bb: Attribute name

cc....cc: Attribute value

Description: The same attribute value tag is specified more than once.
Action: Check the value of xml:lang attribute, and then re-execute the command.

KDJE37379-E

A tag having "en" as the value of the "xml:lang" attribute is not specified. (name = [aa....aa])

aa....aa: Tag name

Description: A tag having "en" as the value of the xml:lang attribute is not specified.
Action: Specify a tag having "en" as the value of the xml:lang attribute, and then re-execute the command.

KDJE37380-E

A Java Beans resource with the same implementation class name exists. (name = [aa....aa], class name = [bb....bb])

aa....aa: Display name of JavaBeans resource

bb....bb: Implementation class name

Description

A Java Beans resource with the same implementation class name already exists.

The command execution will be interrupted.

Action

Change the implementation class name so that there is no duplication, and then re-execute the command.

KDJE37381-W

The resource adaptor has been deleted or there is a problem with the work directory.

Description: The resource adaptor is deleted or there is a problem with the work directory. Check the message in the J2EE server.
Action: Check the message in the J2EE server.

KDJE37382-E

The tag which cannot be specified to [aa....aa] was specified.(name = [bb....bb])

aa....aa: EJB1.1, EJB2.0, EJB2.1, Servlet2.2, Servlet2.3, Servlet2.4, Connector1.0, Connector1.5

bb....bb: Tag name

Description: A tag that cannot be specified was specified.
Action: Check the specifications of the property file in the manual, and if necessary, revise the specification of the tags in the property file.

KDJE37383-E

Two or more tags were specified to [aa....aa]. (name = [bb....bb])

aa....aa: EJB1.1, EJB2.0, Servlet2.2, Servlet2.3, Servlet2.4, Connector1.0

bb....bb: Tag name

Description: Tags that can only be specified once were specified more than once.
Action: Check the specifications of the property file in the manual, and if necessary, revise the specification of the tags in the property file.

KDJE37384-E

A member resource adapter cannot be set in this tag. (tag = [aa....aa], tag value = [bb....bb])

aa....aa: Tag name

bb....bb: Tag value

Description

The display name of the member resource adapter cannot be specified at the following locations:

Resource reference of the J2EE applications
Mapping definition of the CMP Entity Bean

Action

Specify the display name of the root resource adapter in the invalid tag.

KDJE37385-E

aa....aa cannot be deleted. Reboot the J2EE server, and then retry. (name = [bb....bb])

aa....aa: Type (JavaBeans resource)

bb....bb: Display name of JavaBeans resource

Description

bb....bb cannot be deleted.

The command execution will be interrupted.

Action

Restart the J2EE server, and then re-execute the command.

KDJE37386-E

A command cannot be executed from a remote host in an application with the deployment directory format. (name = [aa....aa]).

aa....aa: Application name

WAR directory name if the -name option is omitted in the cjimportwar command

Description: Commands cannot be executed from a remote host, in the expanded archive format.
Action: Execute the commands from the local host.

KDJE37387-E

An empty directory have been specified. (path = [aa....aa])

aa....aa: Path

Description: An empty directory is specified. The command execution will be interrupted.
Action: Revise the command parameters and the contents of the directory, and then re-execute the command.

KDJE37388-E

The total of the property value is invalid. (name = [aa....aa], total = [bb....bb])

aa....aa: Tag name

bb....bb: Total of the tag values

Description: The total of the tag values is invalid. The command execution will be interrupted.
Action: Check the value of the tag names, and then re-execute the command.

KDJE37389-E

The type of the property file is illegal.

Description

The type of the property file is invalid.

Action

Confirm the following contents, and then re-execute the command:

Type of the executed command
Specification of the -type argument
Specification of the -c argument

KDJE37391-E

The connection pool status is illegal. An available status is "running", "runningReserved", "suspendedAutomatically" or "suspendedAutomaticallyReserved". (name = [aa....aa], connection pool status = [bb....bb])

aa....aa: Resource adapter display name

bb....bb: Connection pool status

Description

The connection pool status of aa....aa is invalid. The enabled states are "running", "reserved for running", "automatically suspended", or "reserved for automatic suspension". The command execution will be interrupted.

Action

Execute the following actions:

When the connection pool is blocked automatically or manually:: The suspension processing of the connection pool is in progress. Wait.
When the connection pool is "manually suspended" or "reserved for manual suspension":: The connection pool is already suspended. No action required.
When the connection pool is resuming automatically, or is being resumed manually:: Wait until the connection pool is started, and then re-execute the command.

KDJE37392-E

The length of display name of aa....aa is too long.

aa....aa: an application, a RAR, a data source, a mail, or JavaBeans resource

Description: The display name of the application or resource displayed in aa....aa is too long.
Action: Check the length of the display name, and then re-execute the command.

KDJE37393-E

The J2EE application "aa....aa" cannot be created.

aa....aa: Application name

Description

The application could not be created (name = aa....aa).

The command execution will be interrupted.

Action

The specified application cannot be used.

Check the application name, and then re-execute the command.

KDJE37394-E

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

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

KDJE37395-E

An error occurred while the permissions were being checked.

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

KDJE37396-E

A command cannot be executed in the resource adapter of Connector1.0

Description: A command cannot be executed in the resource adapter of Connector1.0.
Action: Specify the resource adapter of Connector1.5, and then re-execute the command.

KDJE37397-W

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

aa....aa: Detailed information

Description: An attempt to initialize the audit log failed. The audit log cannot be output, but the processing continues.
Action: Remove the cause of the failure by referencing the message log for the audit log.

KDJE37398-W

An attempt to output the audit log has failed. (details = [aa....aa])

aa....aa: Detailed information

Description: An attempt to output the audit log failed. The processing continues.
Action: Remove the cause of the failure by referencing the message log for the audit log. If the problem is not resolved, contact maintenance personnel.

KDJE37399-E

The tag [aa....aa] and the tag [bb....bb] cannot be specified simultaneously.

aa....aa: Tag name

bb....bb: Tag name

Description

Tags that cannot be specified simultaneously have been specified simultaneously.

The command execution will be interrupted.

Action

Check the specifications of the property file in the manual, and if necessary, revise the specification of the tags in the property file.

KDJE37400-I

Connecting to aa....aa...

aa....aa: Server name

Description: Connecting to the server.

KDJE37401-I

Searching aa....aa...

aa....aa: Application name, EJB-JAR display name, WAR display name, RAR display name, data source display name, mail display name, user name, role name, or JavaBeans resource display name

Description: aa....aa is being searched.

KDJE37402-I

Creating aa....aa...

aa....aa: Application name

Description: aa....aa is being created.

KDJE37404-I

Importing aa....aa...

aa....aa: WAR application name, EJB-JAR display name, WAR display name, RAR display name, data source display name, or JavaBeans resource display name

WAR file name or WAR directory name if the -name option is omitted in the cjimportwar command

Description: aa....aa is being created.

KDJE37405-I

Exporting [aa....aa] ...

aa....aa: Application name

Description: The J2EE application (aa....aa) is being exported.

KDJE37406-I

Adding aa....aa...

aa....aa: EJB-JAR display name, WAR display name, RAR display name, user name, role name, or Filter display name

Description: aa....aa is being added.

KDJE37407-I

Deleting aa....aa...

aa....aa: Application name, EJB-JAR display name, WAR display name, RAR display name, data source display name, mail display name, user name, role name, or JavaBeans resource display name

Description: aa....aa is being deleted.

KDJE37408-I

Acquiring aa....aa...

aa....aa: Application name, EJB-JAR display name, WAR display name, RAR display name, data source display name, mail display name, or JavaBeans resource display name

Description: The properties of aa....aa is being acquired.

KDJE37409-I

Setting aa....aa...

aa....aa: Application name, EJB-JAR display name, WAR display name, RAR display name, data source display name, mail display name, or JavaBeans resource display name

Description: The properties of aa....aa are being set.

KDJE37410-I

Copying aa....aa...

aa....aa: EJB-JAR display name, WAR display name, RAR display name, data source display name, or mail display name

Description: aa....aa is being copied.

KDJE37411-I

Testing aa....aa of bb....bb...

aa....aa: DataSource, Mail, or RAR

bb....bb: Datasource display name, mail display name, or resource adapter display name

Description: aa....aa is being tested.

KDJE37413-I

Starting aa....aa...

aa....aa: Application name

Description: aa....aa is running.

KDJE37414-I

Stopping aa....aa...

aa....aa: Application name

Description: aa....aa is being stopped.

KDJE37415-I

Mapping aa....aa...

aa....aa: User name

Description: aa....aa is being mapped.

KDJE37416-I

Unmapping aa....aa...

aa....aa: User name

Description: aa....aa is being un-mapped.

KDJE37417-I

Resetting exclusive information...

Description: The exclusive information of the command is being reset.

KDJE37418-I

Clearing out aa....aa...

aa....aa: Parent resource display name or all resources

Description: aa....aa or all resources are being deleted.

KDJE37419-I

Closing all aa....aa connections...

aa....aa: Parent resource display name, or resources

Description: All aa....aa connections are being closed.

KDJE37420-I

Closing the aa....aa connection...

aa....aa: Connection ID

Description: The connection (aa....aa) is being closed.

KDJE37421-I

Deploying aa....aa...

aa....aa: RAR display name

Description: aa....aa is being deployed.

KDJE37422-I

Undeploying aa....aa...

aa....aa: RAR display name

Description: aa....aa is being un-deployed.

KDJE37423-I

Starting aa....aa...

aa....aa: RAR display name or JavaBeans resource display name

Description: aa....aa is being started.

KDJE37424-I

Stopping aa....aa...

aa....aa: RAR display name or JavaBeans resource display name

Description: aa....aa is being stopped.

KDJE37425-I

Connecting to aa....aa...

aa....aa: Host name

Description: Connecting to the host (aa....aa) of the servlet to be executed.

KDJE37426-I

Replacing aa....aa...

aa....aa: Application name

Description: aa....aa is being replaced.

KDJE37427-I

Updating aa....aa...

aa....aa: Application name

Description: aa....aa is being updated.

KDJE37428-I

Changing aa....aa...

aa....aa: Application name

Description: aa....aa is being changed.

KDJE37429-I

Suspending aa....aa...

aa....aa: Resource adapter display name

Description: aa....aa is being stopped.

KDJE37430-I

Resuming aa....aa...

aa....aa: Resource adapter display name

Description: aa....aa is being resumed.

KDJE37431-I

Generating SQL of aa....aa...

aa....aa: EJB-JAR display name / EJB display name

Description: An SQL statement of aa....aa.is being generated.

KDJE37501-I

aa....aa has been imported successfully. (name = [bb....bb])

aa....aa: Type (WAR application, EJB-JAR, WAR, Datasource, RAR, or JavaBeans resource)

bb....bb: WAR application name, EJB-JAR display name, WAR display name, Datasource display name, RAR display name, or JavaBeans resource display name

Description: bb....bb is imported successfully.

KDJE37502-I

aa....aa has been exported successfully. Name=[bb....bb]

aa....aa: Type (Application or RAR)

bb....bb: Application display name or RAR display name

Description: bb....bb is exported successfully.

KDJE37503-I

aa....aa has been added successfully. (name = [bb....bb])

aa....aa: Type (Application, EJB-JAR, WAR, User, Role, RAR, Filter, or JavaBeans resource)

bb....bb: Application name, parent resource display name, or JavaBeans resource display name

Description: bb....bb is added successfully.

KDJE37504-I

aa....aa has been deleted successfully. (name = [bb....bb])

aa....aa: Type (Application, EJB-JAR, WAR, Datasource, Mail, User, Role, or RAR)

bb....bb: Application name or parent resource display name

Description: bb....bb is deleted successfully.

KDJE37505-I

aa....aa has been obtained successfully. (name = [bb....bb])

aa....aa: Type (Application, EJB-JAR, WAR, Datasource, Mail, RAR, or JavaBeans resource)

bb....bb: Application name, parent resource display name, parent resource display name / subordinate resource display name, or JavaBeans resource display name

Description: The properties of bb....bb have been acquired successfully.

KDJE37506-I

aa....aa has been set successfully. (name = [bb....bb])

aa....aa: Type (Application, EJB-JAR, WAR, Datasource, Mail, RAR, or JavaBeans resource)

bb....bb: Application name, parent resource display name, parent resource display name / subordinate resource display name, or JavaBeans resource display name

Description: The properties of bb....bb have been set successfully.

KDJE37507-I

aa....aa has been copied successfully. (name = [bb....bb])

aa....aa: Type (EJB-JAR, WAR, Datasource, Mail, or RAR)

bb....bb: Parent resource display name, or parent resource display name / subordinate resource display name

Description: bb....bb is copied successfully.

KDJE37508-I

All aa....aa have been listed successfully. (number = [bb....bb])

aa....aa: Applications, EJB-JARs, WARs, Datasources, Mails, Users, Roles, RARs, ejbs, javabeans resource, library jars, lower resources, or threads

bb....bb: Number

Description: All aa....aa have been listed successfully.

KDJE37509-I

aa....aa has been listed successfully. (name = [bb....bb])

aa....aa: Type (Connection, User, or Role)

bb....bb: Datasource display name, all resources, user name, or role name

Description: bb....bb is listed successfully.

KDJE37510-I

aa....aa of bb....bb has been tested successfully. Name=[bb....bb]

aa....aa: DataSource, Mail, or RAR

bb....bb: Datasource display name, mail display name, or resource adapter display name

Description: aa....aa of bb....bb is tested successfully.

KDJE37512-I

aa....aa has started successfully. (name = [bb....bb])

aa....aa: Type (Application)

bb....bb: Application name

Description: The application (bb....bb) has started successfully.

KDJE37513-I

aa....aa has stopped successfully. (name = [bb....bb])

aa....aa: Type (Application)

bb....bb: Application name

Description: The application (bb....bb) has stopped successfully.

KDJE37514-I

aa....aa has been mapped successfully. (name = [bb....bb])

aa....aa: Type (User)

bb....bb: User name

Description: The user (bb....bb) is mapped successfully.

KDJE37515-I

aa....aa has been unmapped successfully. (name = [bb....bb])

aa....aa: Type (User)

bb....bb: User name

Description: The user (bb....bb) is un-mapped successfully.

KDJE37516-I

The exclusive information for command execution has been reset successfully.

Description: The exclusive information of the command was reset successfully.

KDJE37517-I

aa....aa has been cleared successfully. (name = [bb....bb])

aa....aa: Type (JDBC or JCA)

bb....bb: Data source display name or resource adapter display name

Description: The data source or the resource adapter is deleted successfully.

KDJE37518-I

All resources have been cleared successfully.

Description: All resources have been deleted successfully.

KDJE37519-I

aa....aa

Connections have been closed successfully. (name = [bb....bb])

aa....aa: Detailed information from the server

bb....bb: Data source display name, or all resources

Description: The connections have been closed successfully.

KDJE37520-I

The connection has been closed successfully. (CID = [aa....aa])

aa....aa: Connection ID

Description: The connections have been closed successfully.

KDJE37521-I

aa....aa has been deployed successfully. (name = [bb....bb])

aa....aa: Type (RAR)

bb....bb: RAR display name

Description: bb....bb is deployed successfully.

KDJE37522-I

aa....aa has been undeployed successfully. (name = [bb....bb])

aa....aa: Type (RAR)

bb....bb: RAR display name

Description: bb....bb is un-deployed successfully.

KDJE37523-I

aa....aa has started successfully. (name = [bb....bb])

aa....aa: Type (RAR or JavaBeans resource)

bb....bb: RAR display name or JavaBeans resource display name

Description: bb....bb has started successfully.

KDJE37524-I

aa....aa has stopped successfully. (name = [bb....bb])

aa....aa: Type (RAR or JavaBeans resource)

bb....bb: RAR display name or JavaBeans resource display name

Description: bb....bb has stopped successfully.

KDJE37525-I

Pool management information has been set successfully. (DatabaseID = [aa....aa])

aa....aa: Database ID

Description: The pool management information is registered or changed successfully.

KDJE37526-I

DatabaseID has been changed successfully. (DatabaseID = [aa....aa])

aa....aa: Database ID

Description: The database ID is changed successfully.

KDJE37527-I

Pool management information has been deleted successfully. (DatabaseID = [aa....aa])

aa....aa: Database ID

Description: The database ID is deleted successfully.

KDJE37528-I

Pool information has been listed successfully. (listtype = [aa....aa], number = [bb....bb])

aa....aa: List operation type

bb....bb: Number of database lists, number of pool lists, or number of connection lists

Description: The list information is output successfully.

KDJE37529-I

Connection information has been cleared successfully. (mode = [aa....aa], DatabaseID = [bb....bb])

aa....aa: Clear operation type (normal or plan)

bb....bb: Database ID

Description: The connections related to bb....bb have been deleted successfully.

KDJE37530-I

Connection information has been cleared successfully. (mode = [aa....aa])

aa....aa: Clear operation type (normal or plan)

Description: The connection is deleted successfully.

KDJE37531-I

The connection has been closed successfully. (DatabaseID = [aa....aa], CID = [bb....bb])

aa....aa: Database ID

bb....bb: Connection ID

Description: The connections have been closed successfully.

KDJE37532-I

The connection has been closed successfully. (DatabaseID = [aa....aa], TIME = [bb....bb])

aa....aa: Database ID

bb....bb: Timeout period

Description: The connections have been closed successfully.

KDJE37533-I

If you changed class name or URL, you must restart the web container to finish setting it up.

Description: If you have changed the class name or the URL, restart the Web container.

KDJE37534-I

To finish setting up your changes, you must restart the web container.

Description: To apply the settings, restart the Web container.

KDJE37535-I

aa....aa has been replaced successfully. (name = [ bb....bb])

aa....aa: Type (Application)

bb....bb: Application name

Description: aa....aa is replaced successfully.

KDJE37536-I

aa....aa has been updated successfully. (name = [ bb....bb])

aa....aa: Type (Application)

bb....bb: Application name

Description: aa....aa is updated successfully.

KDJE37537-I

aa....aa has been changed successfully. (name = [ bb....bb])

aa....aa: Type (Application)

bb....bb: Application name

Description: aa....aa is changed successfully.

KDJE37538-I

The thread has been stopped successfully.

Description: The thread is stopped successfully.

KDJE37539-I

All transaction have been listed successfully.

Description: All transactions have been listed successfully.

KDJE37540-I

Connections have been listed successfully. name=[aa....aa]

aa....aa: Resource adapter display name

Description: The resource adapter connections have been listed successfully.

KDJE37541-I

All of connections have been listed successfully.

Description: The list of all connections have been listed successfully.

KDJE37542-I

Reloading aa....aa...

aa....aa: Application name

Description: aa....aa is being replaced.

KDJE37543-I

aa....aa has been reloaded successfully. (name=[aa....aa])

aa....aa: Type (Application)

Description: aa....aa is replaced successfully.

KDJE37544-I

The connection pool status was changed successfully. The connection pool which was blocked will now be suspended. (name = [aa....aa])

aa....aa: Resource adapter display name

Description: The status of aa....aa changed normally. The connection pool that was shut down will now be suspended. Use the cjlistrar command to confirm that the connection pool is suspended.

KDJE37545-I

Connection pool has been resumed successfully. (name = [aa....aa])

aa....aa: Resource adapter display name

Description: The connection pool is resumed successfully.

KDJE37546-I

SQL has been generated successfully. (name = [aa....aa])

aa....aa: Application name

Description: An SQL statement is generated successfully.

KDJE37547-I

Application has not been reloaded because a file has not been modified.

Description: An application is not reloaded because a file is not updated.

KDJE37548-I

The transaction has been committed successfully.

Description: The transaction has been committed successfully.

KDJE37549-I

The transaction has been rolled back successfully.

Description: The transaction has been rolled back successfully.

KDJE37550-I

The transaction has been terminated successfully.

Description: The transaction has been terminated successfully.

KDJE37552-I

The list of deleting batch jobs has been exported successfully.

Description: The list of deleting batch jobs has been exported successfully.

KDJE37553-I

Batch jobs have been deleted successfully.

Description: Batch jobs is deleted successfully.

KDJE37600-W

The parent tag [aa....aa], which contains the tag [bb....bb] with the same set value, has been specified more than once. (name = [bb....bb], value = [cc....cc])

The last specified parent tag will be used.

aa....aa: Parent tag name (<resource-external-property> or <property>)

bb....bb: Tag name

cc....cc: Tag value

Description

The aa....aa tag containing a bb....bb tag with the same set value is specified more than once.

The aa....aa tag specified in the end will be used.

Action

Revise the specification of aa....aa, and make sure that no problem exists.

KDJE37601-W

The parent tag [aa....aa] has been specified more than once as a value for the <method> tag. (value = [bb....bb])

The first specified parent tag will be used.

aa....aa: Parent tag name (<ejb-method-observation-timeout> or <ejb-transaction-timeout>)

bb....bb: Set value of the <method> tag

Description

The same aa....aa tag is specified more than once as the set value for the <method> tag.

The aa....aa tag specified first will be used.

Action

Revise the specification of aa....aa, and make sure that no problem exists.

KDJE37602-W

A specification that places one optional name at a higher or lower level than another optional name is not recommended. (name = [aa....aa,bb....bb])

aa....aa: Optional name

bb....bb: Optional name

Description: A specification for placing an optional name at a higher or lower level than another optional name is not recommended.
Action: If it is possible to indicate a specification other than the one for placing an optional name at a higher or lower level than another optional name, revise the specification of the optional name.

KDJE37603-W

The default interceptors cannot be specified before EJB2.1.

Description: A default interceptor cannot be specified for EJB2.1 or earlier.
Action: Do not specify a default interceptor for EJB2.1 or earlier.

KDJE37604-W

The parent tag [aa....aa], which contains the tag [bb....bb] with the same set value, has been specified more than once. (name = [bb....bb], value = [cc....cc])

The first specified parent tag will be used.

aa....aa: Parent tag name (<interceptor-binding>) or <application-exception>)

bb....bb: Tag name

cc....cc: Value of the duplicate tag

Description

The aa....aa tag containing a bb....bb tag with the same set value is specified more than once.

The aa....aa tag specified first will be used.

Action

Make sure that the value cc....cc specified in the bb....bb tag is not duplicate.

KDJE37605-W

<message-selector>,<acknowledge-mode>,<message-driven-destination> cannot be specified after EJB2.1 Message-driven Bean.

Description: <message-selector>, <acknowledge-mode>, and <message-driven-destination> cannot be specified for a Message-driven Bean of version EJB2.1 or later.
Action: Delete the <message-selector>, <acknowledge-mode>, and <message-driven-destination> tags from the MessageDrivenBean property file of the version EJB2.1 or the later versions, and then re-execute the command.

KDJE37606-E

The Filter property file cannot be added to WAR that does not contain web.xml.

Description: The Filter property file cannot be added to a WAR that does not contain web.xml.
Action: Do not add the Filter property file to a WAR that does not contain web.xml.

KDJE37607-E

A memory shortage has occurred. Check, and if necessary, revise aa....aa. (error details = [bb....bb])

aa....aa: Option definition file name

bb....bb: Error details

Description

The usable memory cannot be secured because a memory shortage has occurred in the server management command. Change the settings of the Java heap size and Metaspace area based on the error details, and then re-execute the command.

Action

When the option definition file name is usrconf.bat or usrconf

When the Java heap is insufficient

Specify the Java VM option -Xmx<size> in the USRCONF_JVM_ARGS key of the option definition file for server management commands, and then extend the maximum size of the Java heap memory allocation pool.
When the Metaspace area is insufficient

Specify the Java VM option -XX:MaxMetaspaceSize=<size> in the USRCONF_JVM_ARGS key of the option definition file for server management commands, and then extend the maximum size of the Metaspace area.
When the C heap is insufficient

Terminate the unnecessary applications running on the operating system on which the server management commands are running.

When the option definition file name is adminagentuser.cfg

When the Java heap is insufficient

Specify the Java VM option -Xmx<size> in the add.jvm.arg key of the option definition file for the Administration Agent, and then extend the maximum size of the Java heap memory allocation pool.
When the Metaspace area is insufficient

Specify the Java VM option -XX:MaxMetaspaceSize=<size> in the add.jvm.arg key of the option definition file for the Administration Agent, and then extend the maximum size of the Metaspace area.
When the C heap is insufficient

Terminate the unnecessary applications running on the operating system on which the APIs of the server management commands are running.

KDJE37608-E

An attempt to get the path has failed.(path name = aa....aa)

aa....aa: Argument

Description: An attempt to acquire the path has failed.
Action: Make sure that the Application Server is installed properly.

KDJE37609-E

The command lock was released on the J2EE server because the request from the command did not come for a long time.

Description: The command exclusion was released in the J2EE server because the request from the command did not come through for a long time.
Action: Re-execute the command.

KDJE37610-E

aa....aa has been deleted, or an error occurred in a work directory.

aa....aa: Application name, EJB-JAR name, WAR name, JavaBeans name, library JAR name, and Resource adapter name

Description

Either aa....aa is deleted, or an error such as the write permissions for the temporary directory for the OS being missing might have occurred in the temporary directory.

Action

Review, and if necessary, revise the temporary directory permissions, and then re-execute the command.

The temporary directories vary depending on the environment; however, the following directories generally serve as the temporary directory:

In Windows

Directories such as the directories specified in the environment variable TMP or the environment variable TEMP
In UNIX

Directories such as /tmp or /var/tmp

KDJE37612-W

The specified property value will be ignored, because it is invalid.(name = [aa....aa], value = [bb....bb])

aa....aa: Tag name

bb....bb: Tag value

Description: The value of the specified property will be ignored because it is invalid.
Action: Make sure that the value bb....bb is not invalid.

KDJE37613-W

The tag which cannot be specified to [aa....aa] was specified.(name = [bb....bb])

aa....aa: EJB1.1, EJB2.0, or EJB2.1

bb....bb: Tag name

Description: A tag that cannot be setup is specified. The settings are ignored and the processing will continue.
Action: Revise the specification of the tag in the property file.

KDJE37614-E

The tag [aa....aa] or the tag [bb....bb] must be specified.

aa....aa: Tag name

bb....bb: Tag name

Description: One of the two tags that must be specified is not specified. The execution of the command will be interrupted.
Action: Check the property file specifications in the manual, and review, and if necessary revise, the tags specified in the property file.

KDJE37615-E

File format is invalid. [aa....aa]

aa....aa: File path

Description: The execution of the command will be interrupted because the file format is invalid.
Action: Revise the file format.

KDJE37616-E

Exporting the list of deleting batch jobs is failed.

Description: An attempt to output the deletion-target list file failed.
Action: Check the error message in the message log of the J2EE server, and then take action according to the error message.

KDJE37617-E

Deleting batch jobs is failed.

Description: An attempt to delete job data failed.
Action: Check the error message in the message log of the J2EE server, and then take action according to the error message.

KDJE37618-W

The list of deleting batch jobs was not exported because no matching batch jobs found.

Description: The list of batch jobs to be deleted was not output because no data matched the deletion condition.
Action: Revise the deletion condition or check whether the job repository contains job data.

KDJE39001-I

The web container is now starting. (server name = aa....aa)

aa....aa: Server name

Description: The Web container will start.

KDJE39002-I

The web container is now stopping. (server name = aa....aa)

aa....aa: Server name

Description: The Web container will stop.

KDJE39003-I

The web container started. (server name = aa....aa)

aa....aa: Server name

Description: The Web container was started.

KDJE39004-I

The web container stopped. (server name = aa....aa)

aa....aa: Server name

Description: The Web container was stopped.

KDJE39005-E

The web container aa....aa cannot be started. bb....bb

aa....aa: Server name

bb....bb: Error contents

Description

The Web container cannot be started.

Action

Implement the action mentioned in the message output before this message.

If a message from which the cause can be identified is not output before this message, contact maintenance personnel.

KDJE39006-E

The web container aa....aa cannot be stopped. bb....bb

aa....aa: Server name

bb....bb: Error contents

Description

The Web container cannot be stopped.

Action

Implement the action mentioned in the message output before this message.

If a message from which the cause can be identified is not output before this message, contact maintenance personnel.

KDJE39007-E

The property file could not be accessed. (property file = aa....aa)

aa....aa: File name

Description: The system property file (sysconf.properties) or the user property file (usrconf.properties) cannot be accessed.
Action: Make sure that the file aa....aa can be accessed, and then re-execute the cjstartweb command or cjstopweb command.

KDJE39008-W

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

aa....aa: Property name

bb....bb: Value

cc....cc: Default value

Description

The property value is invalid.

The default value will be used.

Action

When changing the property aa....aa from the default value, modify the property value of aa....aa, and then either stop or restart the Web container server or the J2EE server.

KDJE39009-W

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

aa....aa: Property name

bb....bb: Default value

Description

The property value is not specified.

The default value will be used.

Action

When changing the property aa....aa from the default value, modify the property value of aa....aa, and then either stop or restart the Web container server or the J2EE server.

KDJE39010-W

Adjusted property aa....aa : bb....bb to cc....cc.

aa....aa: Property name

bb....bb: Value before adjustment

cc....cc: Value after adjustment

Description: The property value will be adjusted.
Action: Adjust the value specified in webserver.connector.inprocess_http.*. If the value after adjustment is not correct, revise the relation between the property values, and then reset the correct value.

KDJE39011-E

An attempt to read aa....aa file has failed. bb....bb

aa....aa: File name

bb....bb: Error contents

Description

An attempt to read web-users.xml or hitachi_web.properties has failed.

Action

When aa....aa is web-users.xml

When the contents of bb....bb are 'Not found'

web-users.xml was not found. Start the server that is set up with the cjwebsetup command. If setup finishes properly, confirm that the corresponding files exist, and then restart the server.
When the contents of bb....bb are 'Invalid file'

Either the file cannot be accessed, or the contents are invalid. Check the file access permissions and the file contents, and then restart the server.

When aa....aa is hitachi_web.properties

When the contents of bb....bb are 'Invalid file'

Either the file cannot be accessed, or the contents are invalid. Check the file access permissions and the file contents. Redeploy in the case of the J2EE server mode. If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup. Restart in the case of the servlet engine mode.

KDJE39012-W

An invalid property is specified. The default value will be used. (J2EE application = aa....aa, context root = bb....bb, cc....cc = dd....dd, default value = ee....ee)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Property name

dd....dd: Value

ee....ee: Default value

Description

The property value specified in hitachi_web.properties is invalid.

The default value will be used. If the property is specified in the user property file, its value will become the default context value.

Action

When the property of bb....bb is changed from the default value, change the property value of bb....bb.

In the case of the J2EE server mode: Modify, and then redeploy. If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.
In the case of the servlet engine mode: Modify, and then restart.

KDJE39013-W

The property value is not specified. The default value will be used. (J2EE application = aa....aa, context root = bb....bb, property = cc....cc, default value = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Property name

dd....dd: Default value

Description

The property value is not specified in hitachi_web.properties.

The default value will be used. If the property is specified in the user property file, its value will become the default context value.

Action

When the property of bb....bb is changed from the default value, change the property value of bb....bb.

In the case of the J2EE server mode: Modify, and then redeploy. If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.
In the case of the servlet engine mode: Modify, and then restart.

KDJE39015-W

Exception occurred in stopping Web container aa....aa : bb....bb.

aa....aa: Server name

bb....bb: Exception information

Description

An exception occurred while the Web container was being stopped.

The stop process will continue.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KDJE39016-E

The WAR file could not be expanded. (WAR file = aa....aa, expanded file = bb....bb)

aa....aa: WAR file name

bb....bb: Expanded file name

Description

An attempt to expand a file (bb....bb) from the WAR file (aa....aa) has failed.

Either there might be no permission to access the file or the contents of the WAR file might be invalid.

Action

Check the file access permissions and the contents of the WAR file, and then redeploy.

KDJE39017-E

The http server on port aa....aa could not be started.

aa....aa: Port number

Description

The simple Web server cannot be started on the specified port number (aa....aa).

Another process might be using the specified port number of the simple Web server.

The port number of the simple Web server can be specified either in the key web.server.connector.http.port or the key ejbserver.http.port of the user property file.

If not specified in the user property file, use the port number 8080 as the default value.

Action

Specify a port number that is not in use by another process, and then restart the server.

KDJE39018-I

The web application reload processing has finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description: The web application reload processing has finished.

KDJE39019-E

An error occurred during a web application reload processing. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

An error occurred during the web application reload processing.

Action

Any of the following problems occurred during the reload processing. The error message indicating the cause of the problem is output just before this message, in the message log. Check, and then take action.

An error occurred during the initialization of the filter
An error occurred during the initialization of the listener
An error occurred during the initialization of the servlet for which 0 or a greater value is specified in the <servlet><load-on-startup> element of web.xml
An error occurred during the compilation or initialization of the JSP for which 0 or a greater value is specified in the <servlet><load-on-startup> element of web.xml
An error occurred during the re-reading of the persistent unit
The HTTP Cookie name indicating the HTTP session ID is duplicated with the Cookie name specified in the functionality for adding the server ID in a Cookie

KDJE39020-E

An error occurred in analyzing web.xml at line aa....aa. Initialization of the web application will be stopped. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Line number

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

Description

An error occurred during the analysis of web.xml.

Initialization of the web application will stop.

Action

Modify the location shown in the line number of web.xml, and then redeploy.

If the format or contents of XML are invalid, the message KDJE39308-Ewill be output in the Web servlet log. When message KDJE39308-E is output, modify web.xml on the basis of the detailed information.

If the specified order of the tag does not match the schema definition of XML, the line number of the end tag that includes this tag will be output. As a result, confirm that the specified order of the tag included in the tag shown in the line number matches the schema definition of XML.

Note that in the J2EE server mode, web.xml is re-written in the J2EE server, when the J2EE server imports and deploys an application. Since the line number becomes the line number after web.xml is re-written, for the error location, check the web.xml of the corresponding Web application present below the application directory when the expanded archive format is used. When deployment is performed in the archive format, check web.xml included in the exported EAR file.

KDJE39021-W

web.xml could not be found. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

web.xml was not found.

A Web application that does not contain WEB-INF/web.xml might be deployed or the corresponding web.xml might not be present in the deploy destination directory of the Web application, or access permissions might not be available.

Action

Enable reading of WEB-INF/web.xml, and then redeploy.

KDJE39022-E

A servlet class aa....aa or a class it depends on could not be found.

aa....aa: Servlet class name

Description

A servlet class or a class it depends on was not found.

Take action based on the following causes:

A WAR file that does not contain the class required for execution of the servlet might be deployed, or the class required for execution of the servlet might be deleted from the deploy destination directory of the WAR file.
Permission is not granted to access the class required for execution of the servlet.

Action

Include the class required for execution of the servlet, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39023-I

The web application resource was modified. (J2EE application = aa....aa, context root = bb....bb, resource = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the updated resource

Description: The resource (aa....aa) of the Web application was updated.

KDJE39024-I

The web application resource was removed. (J2EE application = aa....aa, context root = bb....bb, resource = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the deleted resource

Description: The resource (aa....aa) of the Web application was deleted.

KDJE39025-E

The web container server could not be connected. (server name = aa....aa)

aa....aa: Server name

Description

The Web container server (aa....aa) cannot be connected.

Either the Web container server is not started, or the webserver.shutdown.port value set in the user property file might be changed while starting the Web container server.

Action

Confirm that the Web container server aa....aa is started.

If the Web container server is running, take the following actions depending on the status:

If the webserver.shutdown.port value is changed, return to the settings during the startup of the Web container server, and then re-execute the cjstopweb command.
If the webserver.shutdown.port value is not changed, forcibly end the processes of the Web container server with the help of the task manager (in Windows).

Note that if the webserver.shutdown.port value is not specified, 8005 is set as the default value.

KDJE39027-E

The port aa....aa for the shutdown request could not be opened.

aa....aa: Port number

Description

The port (aa....aa) for receiving request to shut down the Web container server cannot be opened.

Another process might be using the specified port number for receiving the request to shut down the Web container server.

The port number for receiving request to shut down the Web container server can be specified in the key webserver.shutdown.port of the user property file. If it is not specified in the user property file, use the port number 8005 as a default value..

Action

Specify a port number that is not in use by another process, and then restart the server.

KDJE39028-W

Security manager denied the access to the resource. (resource = aa....aa)

aa....aa: Resource name

Description: The security manager has denied access to the resource (aa....aa) because the system resource to which access is not allowed as per the security policy was accessed.
Action: Make sure that access to the requested resource is appropriate.

KDJE39030-W

The web container server aa....aa received the shutdown request to the web container server bb....bb.

aa....aa: Server name

bb....bb: Server name

Description: The Web container server (aa....aa) has received the shutdown request to the Web container server (bb....bb).

KDJE39031-E

The port aa....aa for the communication with the web server could not be opened.

aa....aa: Port number

Description

The port for communication with the Web server (redirector) cannot be invoked with the specified port number (aa....aa).

Another process might be using the port number (aa....aa) for communication with the Web server (redirector) set in the user property file.

The port number for communication with the Web server (redirector) can be specified in the key webserver.connector.ajp13.port of the user property file. If it is not specified in the user property file, use the port number 8007 as a default value..

Action

Specify a port number that is not in use by another process, and then restart the server.

KDJE39032-I

The specified value of aa....aa property was applied to bb....bb property. (value = cc....cc)

aa....aa: Property name of an older version

bb....bb: Property name of the current version

cc....cc: Property value

Description

The property (aa....aa) of an older version is specified.

The value (cc....cc) specified in the property of an older version was applied to the currently supported property (bb....bb).

KDJE39033-E

Cosminexus Component Container is not installed correctly. (cause = aa....aa)

aa....aa: Maintenance information

Description: Cosminexus Component Container is not installed properly.
Action: Properly install the Web container server or the J2EE server.

KDJE39035-E

The user property file is invalid. (property file = aa....aa)

aa....aa: Property file name

Description: The contents of the user property file (aa....aa) are invalid.
Action: Revise the contents of the user property file, and then re-execute the cjstartweb command or cjstopweb command.

KDJE39036-E

The web container server was terminated because it is out of memory. (server name = aa....aa)

aa....aa: Server name

Description: The Web container server (aa....aa) will terminate because of insufficient memory.
Action: Secure the memory that can be used by the system, and then restart the Web container server.

KDJE39037-I

aa....aa

aa....aa: Character string specified in the argument, or stack trace of the exception object specified in the argument

Description: The character string specified in the log method of the javax.servlet.ServletContext class, or the argument of the log method of javax.servlet.GenericServlet class will be output. If an exception object is specified in the second argument, the stack trace of the specified exception object will be output row-wise.

KDJE39038-E

The user property file could not be found. (property file = aa....aa)

aa....aa: Property file name

Description: The user property file (aa....aa) was not found.
Action: Make sure that the property file exists, and then re-execute the cjstartweb command or cjstopweb command.

KDJE39039-E

The request data from the web server is invalid.

Description

The request information forwarded from the Web server (redirector) is invalid.

Either the redirector registered in the Web server has a version that is not supported by this version or the data other than the request sent from the redirector might have been received.

Action

Make sure that the version of the redirector is supported. Also make sure that the invalid data, such as the direct transmission of an HTTP request, is not sent to the port used by the Web container for communicating with the Web server.

KDJE39040-E

The web container server abnormally terminated. (server name = aa....aa)

aa....aa: Server name

Description: The Web container server (aa....aa) terminated abnormally because an unexpected error occurred.
Action: Acquire the maintenance information, and then contact maintenance personnel.

KDJE39041-E

An error occurred in reading web.xml. Initialization of the web application will be stopped. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

An error occurred while web.xml was being read.

Initialization of the web application will stop. Permission to access web.xml might not be available.

Action

Set the appropriate access permissions, and then redeploy.

KDJE39042-W

An invalid property is specified. This property is ignored. (aa....aa = bb....bb)

aa....aa: Property name

bb....bb: Value

Description

The property value (bb....bb) is invalid.

The property (aa....aa) value will be ignored.

Action

When setting the property value of aa....aa, properly code the property value of aa....aa, and then restart.

KDJE39045-E

The temporary directory of the web application could not be created. Initialization of the web application will be stopped. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The temporary directory of the Web application that will be created below the temporary directory for JSP cannot be created.

Initialization of the web application will stop. The temporary directory of the Web application might not be created or the permission might not be available.

Action

Set the appropriate access permissions, and then redeploy.

KDJE39046-W

The temporary files of the web application could not be deleted. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The temporary files of the Web application cannot be deleted.

The permission to access the files of the temporary directory of the Web application might not be available.

Action

Delete the files of the temporary directory, and then set appropriate permissions.

KDJE39047-E

An invalid context root name is specified. Initialization of the web application will be stopped. (context root = aa....aa)

aa....aa: Context root name

Description

The context root name (aa....aa) is invalid.

Initialization of the web application will stop.

The context root name needs to be a string in an appropriate format, in the form of a URL created from the alphanumeric characters or the following symbols:

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

%, however, can only be used as escape (such as %20).

Action

Modify the context root name, and then redeploy the application.

For details on the appropriate string format in the form of a URL, see RFC2396.

KDJE39048-E

The webapps directory could not be accessed.

Description

The webapps directory cannot be accessed.

The webapps directory does not exist or access permissions are not available.

Action

Create the webapps directory or set the appropriate permission, deploy the Web application, and then restart the Web container server.

KDJE39049-E

There is no web application to deploy.

Description: The Web application to be deployed does not exist.
Action: Deploy the Web application in the webapps directory, and then restart the Web container server.

KDJE39050-I

The web application resource was added. (J2EE application = aa....aa, context root = bb....bb, resource = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the added resource

Description: The Web application resource was added.

KDJE39051-E

The JSP file could not be found. (J2EE application = aa....aa, context root = bb....bb, JSP file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Path within the Web application of the JSP file

Description

The JSP file was not found.

Action

Add the JSP file, and then update the Web application.

In the case of the J2EE server mode

When the reload functionality of the J2EE application is being used, either add the JSP file or redeploy.

When the reload functionality of the J2EE application is not being used in an application with expanded directory format, either stop the application, add the JSP file, and then restart the application, or else redeploy.

In the case of an archive format application, redeploy.

In the case of the servlet engine mode

When application update detection and reload functionality are being used, either add the JSP file, or redeploy.

When application update detection and reload functionality are not being used, either stop the Web container server, add the JSP file, and then restart the Web container server, or else redeploy.

KDJE39052-I

The JSP file or the file used by the JSP file was modified. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the file

Description

In the case of the J2EE server mode

The JSP file or the file used by the JSP file (cc....cc) was modified.

The files used by the JSP file indicate the following files:

Tag files (excluding the tag files within the JAR file)
Files included by the include directive
Files included by include-prelude and include-coda of web.xml
Tag library descriptor (TLD) files (excluding the TLD file within the JAR file)

In the case of the servlet engine mode

The JSP file (cc....cc) was updated.

KDJE39053-I

The JSP file or the file used by the JSP file was removed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root

cc....cc: Absolute path of the file

Description

In the case of the J2EE server mode

The JSP file or the file used by the JSP file (cc....cc) was deleted.

The files used by the JSP file indicate the following files:

Tag files (excluding the tag files within the JAR file)
Files included by the include directive
Files included by include-prelude and include-coda of web.xml
Tag library descriptor (TLD) files (excluding the TLD file within the JAR file)

In the case of the servlet engine mode

The JSP file (cc....cc) is deleted.

KDJE39054-I

The JSP reload processing per JSP file has finished. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root

cc....cc: Absolute path of the class file generated from the JSP file, when the JSP pre-compile functionality is being used. Absolute path of the JSP file, when the JSP pre-compile functionality is not being used.

Description

When the JSP pre-compile functionality is being used: The class generated from the JSP file (cc....cc) is reloaded.
When the JSP pre-compile functionality is not being used: The JSP file (cc....cc) is recompiled, and the generated class is reloaded.

KDJE39055-E

An error occurred in analyzing the tag library descriptor file at line aa....aa. (J2EE application = bb....bb, context root = cc....cc, TLD = dd....dd)

aa....aa: Line number

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, the cjjspc command, or cjjsp2java command

cc....cc: The context root name in the case of the J2EE server mode or the servlet engine mode and a blank string in the case of the cjjspc command or cjjsp2java command

dd....dd: Path of the TLD file

Description

An error occurred while the tag library descriptor (TLD) file was being analyzed.

The path dd....dd of the TLD file will be output in the following format:

In the case of a TLD file within the Web application

Path within the Web application
In the case of a TLD file saved in the JAR file of the Web application

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')
In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)
In the case of a TLD file within the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Modify the location shown in the line number of the TLD file. If the format or contents of XML are invalid when the application is started, the message KDJE39308-E will be output in either the Web servlet log or the console. When the message KDJE39308-E is output, modify the TLD file on the basis of the detailed information.

If the specified order of the tag does not match the schema definition of XML, the line number of the end tag that includes this tag will be output. As a result, confirm that the specified order of the tag included in the tag shown in the line number matches the schema definition of XML.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39056-E

An exception was raised in executing the request. (request URL = aa....aa, exception = bb....bb)

aa....aa: Resource name

bb....bb: Exception name

Description

An exception occurred during the execution of the request.

Action

Remove the cause due to which the exception was thrown.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39057-E

The status code aa....aa was returned in executing the request. (request URL = bb....bb)

aa....aa: Status code

bb....bb: Resource name (a blank character string, if URL cannot be normalized using the Web server integrated functionality or a simple Web server)

Description

The execution of the request ended with the status code (aa....aa).

Action

Remove the cause due to which the servlet or JSP returned the status code displayed in the message.

However, if the response was already committed when the error causing the message to display occurred, the status code when the response was committed might be output, rather than an error status code (from 400 to 599).

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

Check the cause if an unintended status code is displayed.

The displayed status codes and example causes are as follows:

Status code: 404

Meaning: The requested URL is not found.

Example cause 1: The specified browser URL is incorrect.

Example cause 2: A request was received when the application was not running.
Status code: 503

Meaning: The processing cannot be executed temporarily.

Example cause: A large number of requests were received temporarily.

KDJE39058-I

Could not output the error page because the response was already committed. (error page = aa....aa)

aa....aa: Resource name of the error page

Description: The error page cannot be displayed because the response was already committed.

KDJE39059-E

An exception was raised in outputting the error page. (error page = aa....aa, exception = bb....bb)

aa....aa: Resource name of the error page

bb....bb: Exception name

Description

An exception occurred while the error page was being displayed.

Action

Remove the cause due to which an exception was thrown from the servlet or JSP of the error page.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39060-E

The status code aa....aa was returned in outputting the error page. (error page = bb....bb)

aa....aa: Status code

bb....bb: Resource name of the error page

Description

The display of the error page ended with the status code (aa....aa).

Action

Remove the cause due to which the servlet or JSP of the error page returned the status code displayed in the message.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39061-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace will be output in each line because an exception was thrown by the servlet or JSP processing.

If the output exception is javax.servlet.ServletException exception, javax.servlet.jsp.JspException exception, or javax.servlet.jsp.el.ELException exception that specify the root cause, the stack trace of the root cause will also be output in each line.

Action

Check the servlet or JSP processing and remove the cause of the exception.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39062-W

An invalid value was specified in the cookie. This cookie was ignored. (aa....aa = bb....bb, request URL = cc....cc)

aa....aa: Name of the Cookie that includes invalid characters

bb....bb: Value of the Cookie that includes invalid characters

cc....cc: Requested URL

Description

A name or value including double-byte characters is being used in the Cookie.

This Cookie will be ignored and is not included in the response.

Action

If you want to include double-byte codes in the Cookie, perform URL encoding beforehand, and then set in the Cookie.

KDJE39096-E

The filter class aa....aa or a class it depends on could not be found. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Filter class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

Description

The filter class (aa....aa) or a class it depends on was not found.

When the Web application starts, the processing will be interrupted.

During reload, this filter will be ignored and the reload processing will continue.

Action

Include the class required for execution of the filter, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39097-E

An invalid filter class aa....aa is specified. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Filter class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

Description

An invalid filter class (aa....aa) was specified.

Initialization of the web application will stop.

The filter class must implement the interface javax.servlet.Filter, and must have a constructor without any arguments.

When the Web application starts, the processing will be interrupted.

During reload, this filter will be ignored and the reload processing will continue.

Action

Include the appropriate filter class in the Web application.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39098-E

An exception aa....aa was raised in initialization of the filter class bb....bb. Initialization of the web application will be stopped. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Filter class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

dd....dd: Context root name

Description

An exception occurred during the initialization of the filter class (bb....bb).

When the Web application starts, the processing will be interrupted.

During reload, this filter will be ignored and the reload processing will continue.

Action

Remove the cause due to which an exception occurred during the initialization of the filter class.

If an error occurs in the processing of the Dependency Injection, an error message is output in the message log just before this message. Check, and then take action.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39099-E

An exception aa....aa was raised in the destroy method of the filter class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Filter class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

dd....dd: Context root name

Description

An exception occurred while the filter class (bb....bb) was being released.

The exception will be ignored, and then the processing continues.

Action

Remove the cause due to which an exception occurred during the release of the filter class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39100-E

The listener class aa....aa or a class it depends on could not be found. Initialization of the web application will be stopped. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Listener class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

Description

The listener class (aa....aa) or a class it depends on was not found.

When the Web application starts, the processing will be interrupted.

During reload, this listener will be ignored, and then the reload processing will continue.

Action

Include the class required for execution of the listener, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39101-E

An invalid listener class aa....aa is specified. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Listener class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

Description

An invalid listener class (aa....aa) is specified. The listener class must implement one or more of the following interfaces, and must have a constructor without any arguments.

If the version of the Web application is Servlet 2.3, the listener must not implement an interface added from Servlet 2.4.

When the Web application starts, the processing will be interrupted.

During reload, this listener will be ignored, and then the reload processing will continue.

When the Web application version is Servlet 2.4 or later

javax.servlet.ServletContextListener

javax.servlet.ServletContextAttributeListener

javax.servlet.http.HttpSessionListener

javax.servlet.http.HttpSessionAttributeListener

javax.servlet.ServletRequestListener

javax.servlet.ServletRequestAttributeListener

When the Web application version is Servlet 2.3

javax.servlet.ServletContextListener

javax.servlet.ServletContextAttributeListener

javax.servlet.http.HttpSessionListener

javax.servlet.http.HttpSessionAttributeListener

Action

Include the appropriate listener classes in the Web application.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39102-E

An exception aa....aa was raised in initialization of the listener class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Listener class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

dd....dd: Context root name

Description

An exception occurred during the initialization of the listener class (bb....bb).

When the Web application starts, the processing will be interrupted.

During reload, this listener will be ignored and the reload processing will continue.

Action

Remove the cause due to which an exception occurred during the initialization of the listener class.

If an error occurs in the processing of the Dependency Injection, an error message is output in the message log just before this message. Check, and then take action.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39103-E

An exception aa....aa was raised in notification of the listener class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Listener class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

dd....dd: Context root name

Description

An exception occurred during the execution of the listener class (bb....bb).

When the Web application starts, the start processing will continue.

When the Web application is reloaded, the reload processing will continue.

Action

Remove the cause due to which an exception occurred during the execution of the listener class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39104-E

The tag library validator class aa....aa or a class it depends on could not be found. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Tag library validator class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or the cjjspc command or cjjsp2java command

cc....cc: The context root name in the case of the J2EE server mode or the servlet engine mode, and a blank string in the case of the cjjspc command or cjjsp2java command

Description

The tag library validator class (aa....aa) or a class it depends on was not found.

Take action based on the following causes:

Either the class required for execution of the tag library validator is not included, or the class required for execution of the tag library validator was deleted from the WAR file deploy destination directory, and then the JSP files using the tag library validator were compiled.
Permission to access the class required for execution of the tag library validator is not available.

Action

Include the class required for execution of the tag library validator, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39105-E

An invalid tag library validator class aa....aa is specified. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Tag library validator class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or the cjjspc command or cjjsp2java command

cc....cc: The context root name in the case of the J2EE server mode or the servlet engine mode, and a blank string in the case of the cjjspc command or cjjsp2java command

Description

An invalid tag library validator class (aa....aa) is specified.

The tag library validator class must inherit the class javax.servlet.jsp.tagext.TagLibraryValidator, and must have a constructor without any arguments.

Action

Include the appropriate tag library validator class in the Web application.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39106-E

An exception aa....aa was raised in initialization of the tag library validator class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Tag library validator class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

dd....dd: The context root name in the case of the J2EE server mode or the servlet engine mode, and a blank string in the case of the cjjspc command or cjjsp2java command

Description

An exception occurred during the initialization of the tag library validator class (bb....bb).

Action

Remove the cause due to which an exception occurred during the initialization of the tag library validator class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39107-E

An exception aa....aa was raised in validation of the JSP file or the tag file by the tag library validator class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Tag library validator class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

dd....dd: The context root name in the case of the J2EE server mode or the servlet engine mode, and a blank string in the case of the cjjspc command or cjjsp2java command

Description

In the case of the J2EE server mode or the cjjspc command: An exception occurred during the validation of the JSP file or the tag file of the tag library validator class (bb....bb).
In the case of the servlet engine mode or the cjjsp2java command: An exception occurred during the validation of the JSP file of the tag library validator class (bb....bb).

Action

Remove the cause due to which an exception occurred during the validation of the JSP file or the tag file by the tag library validator class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39108-E

An exception aa....aa was raised in the release method of the tag library validator class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Tag library validator class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

dd....dd: The context root name in the case of the J2EE server mode or the servlet engine mode, and a blank string in the case of the cjjspc command or cjjsp2java command

Description

An exception occurred during the release of the tag library validator class (bb....bb).

Action

Remove the cause due to which an exception occurred during the release of the tag library validator class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39111-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the initialization of the filter class will be output in each line.

Action

Remove the cause due to which the filter class throws the exception displayed in the message.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39112-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the release of the filter class will be output in each line.

Action

Remove the cause due to which an exception occurred during the release of the filter class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39113-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the initialization of the listener class will be output in each line.

Action

Remove the cause due to which the listener class throws the exception displayed in the message.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39114-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the execution of the listener class will be output row-wise.

Action

Remove the cause due to which an exception occurred during the execution of the listener class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39115-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the initialization of the tag library validator class will be output row-wise.

Action

Remove the cause due to which an exception occurred during the initialization of the tag library validator class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39116-E

aa....aa

aa....aa: Stack trace of the exception

Description

In the case of the J2EE server mode or the cjjspc command: The stack trace of the exception thrown during the validation of the JSP file or the tag file by the tag library validator class will be output row-wise.
In the case of the servlet engine mode or the cjjsp2java command: The stack trace of the exception thrown during the validation of the JSP file by the tag library validator class will be output row-wise.

Action

Remove the cause due to which an exception occurred during the validation of the JSP file or the tag file by the tag library validator class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39117-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the release of the tag library validator class will be output row-wise.

Action

Remove the cause due to which an exception occurred during the release of the tag library validator class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39130-W

An error occurred during the data acquisition. (request URL = aa....aa)

aa....aa: Request URL

Description

An error occurred during the acquisition of the POST data.

Take action based on the following causes:

The client might have terminated the transmission of POST data.
The communication between the client and the Web server might be disconnected.
The packet from the redirector might be corrupt.
A communication failure might have occurred between the Web server and the Web container.

Action

Confirm the following details:

The Web server is running properly
No application is sending invalid data to the Web container
No problem exists in the communication path between the Web server and the Web container.
No problem exists in the communication between the Web server and the external network.

KDJE39131-E

The TagExtraInfo class aa....aa or a class it depends on could not be found. (J2EE application = bb....bb, context root = cc....cc, JSP file = dd....dd, tag library = ee....ee)

aa....aa: TagExtraInfo class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or the cjjspc command or cjjsp2java command

cc....cc: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

dd....dd: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

ee....ee: uri attribute value of the taglib directive of this JSP file or tag file

Description

The TagExtraInfo class or a class it depends on was not found.

Action

Include the class required for execution of the TagExtraInfo class, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39132-E

An invalid TagExtraInfo class aa....aa is specified. (J2EE application = bb....bb, context root = cc....cc, file = dd....dd, tag library = ee....ee)

aa....aa: TagExtraInfo class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or the cjjspc command or cjjsp2java command

cc....cc: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

dd....dd: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

ee....ee: uri attribute value of the taglib directive of this JSP file or tag file

Description

An invalid TagExtraInfo class was specified.

The TagExtraInfo class must fulfill the following conditions:

The class TagExtraInfo must be inherited.
It is not an interface or abstract class.
It must have a public constructor.

Action

Include the appropriate TagExtraInfo class in the Web application.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39133-E

An exception aa....aa was raised in initialization of the TagExtraInfo class bb....bb. (J2EE application = cc....cc, context root = dd....dd, file = ee....ee, tag library = ff....ff)

aa....aa: Exception name

bb....bb: TagExtraInfo class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

dd....dd: The context root name in the case of the J2EE server mode or the servlet engine mode, and a blank string in the case of the cjjspc command or cjjsp2java command

ee....ee: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

ff....ff: uri attribute value of the taglib directive of this JSP file or tag file

Description

An exception occurred during the initialization of the TagExtraInfo class.

Action

Remove the cause due to which an exception occurred during the initialization of the TagExtraInfo class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39134-E

The JSP translation failed because a JSP validation error message was reported from the tag library validator. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, tag library = dd....dd, number of message = ee....ee)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: uri attribute value of the taglib directive of this JSP file or tag file

ee....ee: Number of validation error messages

Description

In the case of the J2EE server mode or the cjjspc command: The tag library validator class has reported an error detected during the validation of the JSP file or the tag file.
In the case of the servlet engine mode or the cjjsp2java command: The tag library validator class has reported an error detected during the validation of the JSP file pages.

The validation error message is output in KDJE39135-E.

Action

See the validation error message, and then confirm the usage method of the tag library. The validation error message is output in the message log or the console with the message KDJE39135-E.

KDJE39135-E

A validation message. (id = aa....aa, message = bb....bb)

aa....aa: Return value of getId method of the ValidationMessage class

bb....bb: Return value of the getMessage method of the ValidationMessage class

Description

The message contents (javax.servlet.jsp.tagext.ValidationMessage class) of the validation error that occurred are described in KDJE39134-E.

If the ValidationMessage is null, aa....aa and bb....bb will also become null.

Action

See the output message, and then confirm the usage method of the tag library.

KDJE39136-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the generation of instances of the TagExtraInfo class, or during the failure in initialization will be output row-wise.

Action

Remove the cause due to which an exception occurred during the initialization of the TagExtraInfo class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39139-E

The host name specified in the property webserver.connector.http.permitted.hosts could not be resolved. (host name = aa....aa)

aa....aa: Host name that cannot be resolved

Description

The host name specified in webserver.connector.http.permitted.hosts cannot be resolved.

Allow access only from the local host, and then start.

Action

Make sure that the specified host name can be resolved, and then restart the server.

KDJE39140-W

Access to the internal http server from a forbidden host was rejected. (IP address = aa....aa)

aa....aa: IP address of the host that was denied access

Description: Access to the simple Web server from a forbidden host was denied.
Action: To allow access from a forbidden host, specify the IP address or the host name of the host that is allowed access in the property webserver.connector.http.permitted.hosts, and then restart the server.

KDJE39141-W

The J2EE server denies access to the URI starting with /ejb/ or /web/ through the web server. (request URI = aa....aa)

aa....aa: Request URI

Description

The accessed request was denied.

In the case of the J2EE server mode, the request beginning with /ejb/ or /web/ cannot be used through the Web server.

KDJE39142-E

An exception aa....aa was raised in the JSP page. The request bb....bb will be forwarded to the errorPage URL cc....cc specified by the JSP page.

aa....aa: Exception name

bb....bb: Request URI

cc....cc: Error page URL

Description

An exception occurred in JSP.

The request will be forwarded to the error page specified in the page directive.

Action

Remove the cause due to which an exception was thrown from JSP.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39143-E

aa....aa

aa....aa: Error message

Description

In the case of the J2EE server mode or the cjjspc command

An error occurred during the compilation of the source code of the servlet generated from the JSP file or the tag file.

The compilation of the error message will be output row-wise.

In the case of the servlet engine mode

An error occurred during the compilation of the source codes of the servlet generated from the JSP file.

The compilation of the error message will be output row-wise.

Action

Remove the cause due to which the compilation error occurred.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command

Re-execute the command.

KDJE39144-E

An exception aa....aa was raised in invocation of the filter class bb....bb. (filter name = cc....cc)

aa....aa: Exception name

bb....bb: Filter class name

cc....cc: Filter name

Description: An exception occurred during the execution of the doFilter method of the filter class (bb....bb).
Action: Remove the cause due which an exception occurred in the doFilter method of the filter class.

KDJE39145-E

The JSP translation failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc) detail = dd....dd

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: Cause of the error occurrence during the analysis of the JSP file or the tag file

Description

In the case of the J2EE server mode or the cjjspc command

An error occurred during the analysis of the JSP file or the tag file.

The error message will be output row-wise.

In the case of the servlet engine mode or the cjjsp2java command

An error occurred during the analysis of the JSP file.

The error message will be output row-wise.

Action

Remove the cause due to which an error occurred during the analysis of the JSP file or the tag file.

If an error occurs during the analysis of the JSP file or tag file of XML format, or an error occurs during the analysis of the tag library descriptor specified in JSP, a message with a message ID beginning with KECX will be output. For details on messages with the message ID beginning with KECX, see 11. KECX (Messages Output by Cosminexus XML Processor).

If you are using JSTL or JSF in a Web application conforming to Servlet 2.5 or later specifications, JSTL or JSF might not have been set up properly. Make sure that a JSTL or a JSF of the correct version is added to the class path.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

If the JSTL or the JSF is not set up properly, restart the J2EE server.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39146-E

An exception aa....aa was raised in invocation of the servlet or JSP. (request URL = bb....bb)

aa....aa: Exception name

bb....bb: request URL

Description

An exception occurred during the execution of the servlet or JSP.

Action

Remove the cause due to which an exception was thrown from the servlet or JSP.

If an error occurs in the processing of the Dependency Injection, an error message is output in the message log just before this message. Check, and then take action.

If JSP throws any of the following exceptions, an error might have occurred during the compilation of the JSP file or the tag file. Make sure that no problem exists in the JSP file or the tag file.

org.apache.jasper.JasperException
org.apache.jasper.compiler.ParseException
org.apache.jasper.compiler.CompileException

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39147-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception that has occurred during the execution of the doFilter method of the filter class will be output row-wise.

If the exception that has occurred is either the ServletException exception or the JspException exception that specifies the root cause, the stack trace of the root cause will be output next, row-wise.

Action

Remove the cause due to which the doFilter method of the filter class throws the exception displayed in the message.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39148-I

aa....aa

aa....aa: Java VM version

Description

This message indicates the Java VM version.

This message is output in cjstdout.log of the Web container server.

KDJE39149-E

The auth-method tag is not specified in web.xml. Initialization of the web application will be stopped. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description: When the <auth-constraint> tag is coded in web.xml, the authentication method needs to be specified in the <auth-method> tag. The initialization of the Web application will terminate because the <auth-method> tag is not specified.
Action: Properly specify the <auth-constraint> tag in web.xml, and then redeploy.

KDJE39150-W

The login-config tag is not specified in web.xml. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description: When the <auth-constraint> tag is coded in web.xml, a specific resource might not be accessible, if the authentication method is not specified in the <auth-method> tag in the <login-config> tag.
Action: Code the <login-config> tag in web.xml, specify the authentication method using the <auth-method> tag, and then redeploy application.

KDJE39151-E

The form-login-config tag is not specified in web.xml. Initialization of the web application will be stopped. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description: When using FORM authentication, you need to specify the <form-login-config> tag in web.xml. The initialization of the Web application will terminate because the <form-login-config> tag is not specified.
Action: Specify the <form-login-config> tag in web.xml, and then redeploy the application.

KDJE39152-E

An exception aa....aa was raised in initialization of the servlet class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

dd....dd: Context root name

Description

An exception occurred during servlet initialization.

The exception might have occurred in the following processes:

Class loading
Instantiation
init processing of the servlet
Dependency Injection processing

Action

Remove the cause due to which an exception occurred during the initialization of the servlet. The stack trace is output in the Web servlet log. For details on the Web servlet logs, see 4.3.1 Acquiring the Cosminexus Component Container Logs in the uCosminexus Application Server Maintenance and Migration Guide.

If an error occurs in the processing of the Dependency Injection, an error message is output just before this message. The output destination is the message log. Check, and then take action.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39153-E

aa....aa

aa....aa: Stack trace

Description

The stack trace of the exception that has occurred during the initialization of the servlet will be output row-wise.

Action

Remove the cause due to which the exception displayed in the message occurred during the initialization of the servlet.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39154-E

An exception aa....aa was raised in initialization of the JSP. (J2EE application = bb....bb, context root = cc....cc, file = dd....dd)

aa....aa: Exception name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

dd....dd: Path of the JSP file or tag file within the Web application

(However, for a tag file saved in the JAR file, the output will be in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

Description

An exception occurred during the initialization of JSP.

The exception might have occurred in the following processes:

Class loading
Instantiation
init processing of JSP

Action

Remove the cause due to which an exception occurred during the initialization of JSP. The stack trace is output in the Web servlet log.

If the exception name is ClassNotFoundException, the loading of the class generated from JSP might have failed due to the following reasons.

File read permission is not available.
The file system has failed.
Memory is insufficient.

Correct the error location depending on the reason, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39155-E

aa....aa

aa....aa: Stack trace

Description

The stack trace of the exception that occurred during the initialization of JSP will be output row-wise.

Action

Remove the cause due to which the exception displayed in the message occurred during the initialization of JSP.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39156-I

A new request is kept waiting until the web application reload processing has finished. The web application reload processing is waiting until all processing requests are finished. (J2EE application = aa....aa, context root = bb....bb, number of processing requests = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of processing requests

Description

A resource update was detected.

The new requests will be kept waiting until the Web application reload processing has finished.

The Web application reload processing will be kept waiting until all processing requests are finished.

KDJE39157-I

The web application reload processing is waiting until all processing requests have finished. (J2EE application = aa....aa, context root = bb....bb, number of processing requests = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of processing requests

Description

A resource update was detected.

The Web application reload processing will be kept waiting until all processing requests are finished.

KDJE39158-I

The web application reload processing is waiting until all processing requests have finished. (J2EE application = aa....aa, context root = bb....bb, number of processing requests = cc....cc, timeout(sec) = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of processing requests

dd....dd: Period until a timeout occurs

Description

A resource update was detected.

The Web application reload processing will be kept waiting until all processing requests are finished. If the new requests after detection of resource update are either being processed or are within the maximum delay period, the processing will start as it is.

KDJE39159-I

A new request is kept waiting until the web application reload processing has finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description: The Web application reload processing is starting. The new requests will be kept waiting until the Web application reload processing has finished.

KDJE39160-I

A timeout occurred. A new request is kept waiting until the web application reload processing has finished. The web application reload processing is waiting until all processing requests have finished. (J2EE application = aa....aa, context root = bb....bb, number of processing requests = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of processing requests

Description

A timeout occurred.

The maximum delay period until the new requests are changed to pending status has elapsed. The new requests will be kept waiting until the Web application reload processing has finished. The Web application reload processing will be kept waiting until all processing requests are finished.

KDJE39161-I

The web application reload processing will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description: The Web application reload processing will start.

KDJE39162-I

The serialization of session objects will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description: The serialization of session objects will start.

KDJE39163-E

The session information file could not be written. All sessions in the web application are lost. (context root = aa....aa, file path = bb....bb)

aa....aa: Context root name

bb....bb: File path

Description

Writing is not possible in the session information file.

All sessions in the Web application will be lost.

Take action based on the following causes:

Write permission is not available for the session information file.
A directory exists with the same name as the session information file.
The directory that was created during the startup of the Web container server and that outputs the session information file is deleted.

Action

Take action depending on the cause.

KDJE39164-W

The session attribute that is not serializable was found. It will be deleted. (context root = aa....aa, attribute name = bb....bb, class = cc....cc)

aa....aa: Context root name

bb....bb: Attribute name

cc....cc: Class name of the object that cannot be serialized

Description

An object (cc....cc) that cannot be serialized was found in the session attribute (bb....bb).

The corresponding attribute will be deleted.

Action

Change the object registered in the session attribute to one that can be serialized. If the session attribute is used persistently even after reload, modify the corresponding object to one that can be serialized.

KDJE39165-E

An attempt to write the session information file has failed. All sessions in the web application are lost. (context root = aa....aa, file path = bb....bb)

aa....aa: Context root name

bb....bb: File path

Description

An attempt to write in the session information file has failed.

All sessions in the Web application will be lost.

Action

Make sure that the disk capacity is sufficient, and that no error exists.

KDJE39166-E

An attempt to serialize a session object has failed. All sessions in the web application are lost. (context root = aa....aa, attribute name = bb....bb)

aa....aa: Context root name

bb....bb: Attribute name

Description

An attempt to serialize the session object has failed.

All sessions in the Web application will be lost.

Action

Check the contents of the stack trace of message KDJE39167-E output in the Web servlet log, and then take action for the class responsible for the occurrence of the exception.

KDJE39167-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception that has occurred during the serialization of the session object will be output row-wise.

Action

Check the message output as the class responsible for the occurrence of the exception, and then take one of the following actions for that class:

Modify the class responsible for the occurrence of the exception, so that it can be serialized.
Modify the class responsible for the occurrence of the exception, so that it is not included in the session object.
Modify the class responsible for the occurrence of the exception, so that it is not included as a serialization target.

KDJE39168-I

The serialization of session objects has finished. (J2EE application = aa....aa, context root = bb....bb, number of sessions = cc....cc, session information file size(byte) = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of serialized sessions

dd....dd: Size of the session information file

Description: The serialization of session objects has finished.

KDJE39169-I

The deserialization of session objects will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description: The deserialization of session objects will start.

KDJE39170-E

The session information file could not be read. All sessions in the web application are lost. (context root = aa....aa, file path = bb....bb)

aa....aa: Context root name

bb....bb: File path

Description

The session information file cannot be read.

All sessions in the Web application will be lost.

Take action based on the following causes:

The session information file does not exist.
Read permission is not available for the session information file.
A directory exists with the same name as the session information file.

Action

Take action depending on the cause.

KDJE39171-E

The session information file is invalid. All sessions in the web application are lost. (context root = aa....aa, file path = bb....bb)

aa....aa: Context root name

bb....bb: File path

Description

The session information file is not updated properly.

All sessions in the Web application will be lost.

Action

Do not access the session information file.

KDJE39172-E

An attempt to read the session information file has failed. All sessions in the web application are lost. (context root = aa....aa, file path = bb....bb)

aa....aa: Context root name

bb....bb: File path

Description

An error occurred while the session information file was being read.

All sessions in the Web application will be lost.

Action

Make sure that no problem exists in the disk.

KDJE39173-E

An attempt to deserialize a session object has failed. All sessions in the web application are lost. (context root = aa....aa, attribute name = bb....bb)

aa....aa: Context root name

bb....bb: Attribute name

Description

An attempt to deserialize a session object has failed.

All sessions in the Web application will be lost.

Action

Check the contents of the stack trace of message KDJE39174-E output in the Web servlet log, and then take action for the class responsible for the occurrence of the exception.

KDJE39174-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception that has occurred during the de-serialization of the session object will be output row-wise.

Action

Check the message output as the class responsible for the occurrence of the exception, and confirm the following details:

Has the class of the session attribute, or the class referenced from there been deleted?
Has the class of the session attribute, or the class referenced from there been changed to a configuration not compatible with the data format during serialization?

KDJE39175-E

An attempt to delete the session information file has failed. (context root = aa....aa, file path = bb....bb)

aa....aa: Context root name

bb....bb: File path

Description

An attempt to delete the session information file has failed.

Permission to delete the session information file is not available.

Action

Specify the settings so that the session information file can be deleted.

KDJE39176-I

The deserialization of session objects has finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description: The deserialization of session objects has finished.

KDJE39177-I

The web application reload processing has finished. The waiting requests are resumed. (J2EE application = aa....aa, context root = bb....bb, number of waiting requests = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of pending requests

Description

The Web application reload processing has finished.

The pending requests will be resumed.

KDJE39178-E

The directory for the session information file could not be created. The session persistence of the web application is invalidated. (context root = aa....aa, directory path = bb....bb)

aa....aa: Context root name

bb....bb: Output destination directory path of the session information file

Description

The directory (bb....bb) for output of the session information file cannot be created.

The session is not persisted.

Take action based on the following causes:

Permission is not available to create the directory for output of the session information file.
Invalid characters have been used to create the directory name.
Files with the same name exist in the same directory.

Action

Take action depending on the cause.

KDJE39179-E

An error occurred in the serialization of session objects. All sessions in the web application are lost. (context root = aa....aa)

aa....aa: Context root name

Description

An error occurred during the serialization of the session object.

All sessions in the Web application will be lost.

Action

Identify the cause from the contents of the stack trace of message KDJE39180-E output in the Web servlet log, and then take action.

KDJE39180-E

aa....aa

aa....aa: Stack trace of the exception that has occurred during the serialization of the session object

Description

The stack trace of the exception that has occurred during the serialization of the session object will be output row-wise.

Action

Check the contents of the stack trace, and then take action.

In the case of java.lang.OutOfMemoryError

The memory is insufficient.

Increase the memory that can be used by the system, and then restart the Web container server.

In cases other than java.lang.OutOfMemoryError

Take action against the cause due to which the session attribute throws the exception displayed in the stack trace.

KDJE39181-E

An error occurred in the deserialization of session objects. All sessions in the web application are lost. (context root = aa....aa)

aa....aa: Context root name

Description

An error occurred during the de-serialization of the session object.

All sessions in the Web application will be lost.

Action

Identify the cause from the contents of the stack trace of message KDJE39182-E output in the Web servlet log, and then take action.

KDJE39182-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception that has occurred during the de-serialization of the session object will be output row-wise.

Action

Check the contents of the stack trace, and then take action.

In the case of java.lang.OutOfMemoryError

The memory is insufficient.

Increase the memory that can be used by the system, and then restart the Web container server.

In cases other than java.lang.OutOfMemoryError

Take action against the cause due to which the session attribute throws the exception displayed in the stack trace.

KDJE39183-I

The update of the file used by the JSP has been detected. The JSP reload processing will start after aa....aa second(s). (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Set value of the interval for updating the JSP file

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

Description

When the JSP pre-compile functionality is being used

An update was detected in the class file generated from the JSP file or the tag file.

The JSP reload processing will start after the time period (aa....aa) (in seconds) specified in the interval for updating the JSP file.

When the JSP pre-compile functionality is not being used

An update was detected in the JSP file or the file being used by the JSP file.

The JSP reload processing will start after the time period (aa....aa) (in seconds) specified in the interval for updating the JSP file.

In the case of the servlet engine mode

An update was detected in the JSP file.

The JSP reload processing will start after the time period (aa....aa) (in seconds) specified in the interval for updating the JSP file.

KDJE39184-E

The temporary files of the web application could not be delete. Initialization of the web application will be stopped. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The temporary files of the Web application for JSP cannot be deleted.

Initialization of the web application will stop.

The permission to access the files for JSP under the temporary directory of the Web application for JSP might not be available.

Action

Delete the files for JSP under the temporary directory for JSP, set the appropriate access permissions, and then redeploy the application.

KDJE39185-E

An error occurred in compiling the source code of the servlet that generate from the JSP file or the tag file. (file = aa....aa)

aa....aa: Path within the Web application of this JSP file or the tag file (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

Description

In the case of the J2EE server mode or the cjjspc command: An error occurred during the compilation of the source code of java generated from the JSP file or the tag file.
In the case of the servlet engine mode: An error occurred during the compilation of the source code of java generated from the JSP file.

Action

Remove the cause due to which the compilation error occurred. The details of the compilation error will be output in the Web servlet log or the console, with the message ID KDJE39143-E.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command

Re-execute the command.

KDJE39186-E

An error occurred in parsing the JSP file or the tag file. (file = aa....aa)

aa....aa: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

Description

In the case of the J2EE server mode or the cjjspc command: An error occurred during the analysis of the JSP file or the tag file.
In the case of the servlet engine mode or the cjjsp2java command: An error occurred during the analysis of the JSP file.

Action

Remove the cause due to which an error occurred during the analysis of the JSP file or the tag file. The details of the error during JSP analysis will be output to the Web servlet log or the console, with the message ID KDJE39145-E.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39187-W

The web container failed to read the request data from the redirector. (redirector = aa....aa:bb....bb, container = cc....cc:dd....dd)

aa....aa: IP address of the connection destination redirector

bb....bb: Port number of the connection destination redirector

cc....cc: IP address of the container

dd....dd: Port number of the container

Description

An error occurred while the request data from the redirector was being read.

The error will occur due to the following causes:

When the communication between the client and the Web server is disconnected (request processing is terminated in the browser and an update is requested)
When the Web server stops
When the data is sent to the Web container from an application other than the redirector

Action

Confirm the following details:

the Web server is running properly.
No application is sending invalid data to the Web container
No problem exists in the communication path between the Web server and the Web container.

KDJE39188-E

The timeout occurred in reading the request data from the redirector. (redirector = aa....aa:bb....bb, container = cc....cc:dd....dd)

aa....aa: IP address of the connection destination redirector

bb....bb: Port number of the connection destination redirector

cc....cc: IP address of the container

dd....dd: Port number of the container

Description

A timeout occurred while reading the data from the redirector.

Action

Confirm the following details:

the Web server is running properly.
No application is sending invalid data to the Web container
no problem exists in the communication path between the Web server and the Web container.

KDJE39189-E

The web application failed to start because the web application has illegal state. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description: An attempt to initialize the Web application has failed because the Web application is in an illegal state.
Action: Acquire the maintenance information, and then contact maintenance personnel.

KDJE39190-E

The web container failed to initialize because the web container is illegal state.

Description: An attempt to initialize the Web container has failed because the Web container is in an illegal state.
Action: Acquire the maintenance information, and then contact maintenance personnel.

KDJE39191-E

A number of requests exceeds the waiting queue limit. The request fails. (request URL = aa....aa)

aa....aa: Requested URL

Description

The number of requests has exceeded the size of the pending queue. As a result, the requests will not be pending in the Web application, and will result in an error.

Action

Check whether the specified value of the following pending queue size is appropriate. If the specified value is not appropriate, adjust the value of the pending queue size:

Default pending queue size
Pending queue size of the Web application unit
Pending queue size of the URL group unit

KDJE39192-W

Parameters of the thread control per web application are ignored because they are disabled. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The setting to control the number of concurrently executing threads for each Web application is ignored because the setting to control the number of concurrently executing threads for each Web application is disabled.
Action: Make sure that the settings to control the number of concurrently executing threads for each Web application can be used, change the key webserver.container.thread_control.enabled of the user property file to true, and then restart the J2EE server.

KDJE39193-E

The tag library descriptor is invalid because the tei-class element cannot be used with the variable element in the tag element. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, taglib directive uri = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: uri attribute value of the taglib directive of this JSP file or tag file

Description

In the case of the J2EE server mode or the cjjspc command: An attempt to analyze the JSP file or the tag file has failed. The tag library descriptor (TLD) file used from this JSP is invalid because both the elements <tei-class> and <variable> have been set in the tag element.
In the case of the servlet engine mode or the cjjsp2java command: An attempt to analyze the JSP file has failed. The TLD file used from this JSP is invalid because both the elements <tei-class> and <variable> have been set in the tag element.

Action

You cannot specify both the elements <tei-class> and <variable> in the same tag element. Modify the TLD file.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39194-I

The max threads limit of the web application is set to aa....aa. (J2EE application = bb....bb, context root = cc....cc, the configuration of max threads = dd....dd, a number of processing requests = ee....ee)

aa....aa: Maximum number of concurrently executing threads of Web application

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Set value of maximum number of concurrently executing threads

ee....ee: Number of currently executing requests

Description

The maximum number of concurrently executing threads of a Web application with context root aa....aa has become (bb....bb).

The maximum number of concurrently executing threads of the Web application might reduce from the upper limit of the set value based on the settings of other Web applications. If the number of requests that are currently being executed exceeds the maximum number of concurrently executing threads, after the processing of running requests finishes, the requests will be controlled to the current upper-limit value.

KDJE39195-I

The max threads limit of the web application is set to aa....aa. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Maximum number of concurrently executing threads of Web application

bb....bb: J2EE application name

cc....cc: Context root name

Description: The maximum number of concurrently executing threads of a Web application of the context root cc....cc is set to aa....aa.

KDJE39196-E

The contexts failed to deploy. (assignable threads = aa....aa)

aa....aa: Number of assignable threads

Description

An attempt to deploy the Web application has failed.

The setting of concurrently executing number of threads for each Web application is invalid.

The number of assignable threads is the number of threads that can be newly assigned as dedicated threads. When only a Web application, in which the number of dedicated threads is not specified, is deployed, it will fail to be deployed because the maximum number of concurrently executing threads for each Web container are all being used as dedicated threads. In such a case, the number of assignable threads needs to be one or more.

Action

Revise the setting of the concurrently executing number of threads in each Web application, and then redeploy the application.

The total number of dedicated threads of the Web application to be deployed needs to be lesser than or equal to the number of assignable threads. If the number of assignable threads is 0, new deployment will not be possible. Revise the value set as the concurrently executing number of threads of an already deployed Web application.

KDJE39197-I

The max threads limit of the web applications for which parameters of the thread control per web application have not been set are set to aa....aa. (a number of processing requests = bb....bb)

aa....aa: Maximum number of concurrently executing threads of Web application

bb....bb: Number of currently executing requests

Description

The maximum number of concurrently executing threads of a Web application, in which the setting to control the number of concurrently executing threads for each Web application is not specified, has become aa....aa.

If the number of currently executing requests exceeds the maximum number of concurrently executing threads, the requests will be controlled at the current upper-limit value, after the processing of running requests finishes.

KDJE39198-I

The max threads limit of the max threads of the web applications for which parameters of the thread control per web application have not been set are set to aa....aa.

aa....aa: Maximum number of concurrently executing threads of Web application

Description: The concurrently executing number of threads of a Web application, in which the setting to control the maximum number of concurrently executing threads for each Web application is not specified, has become aa....aa.

KDJE39199-I

The unexpected information is contained in the HTTP request header. (started with aa....aa)

aa....aa: Value of first byte

Description: The unexpected information is contained in the HTTP request header.
Action: Make sure that the version of the redirector and the container match.

KDJE39200-E

The value specified to jsp_precompile of a query is invalid. (value = aa....aa)

aa....aa: Value specified in jsp_precompile

Description: The value specified in the query string jsp_precompile is invalid.
Action: Specify the correct value in the query string jsp_precompile.

KDJE39201-E

The temporary directory aa....aa could not be accessed.

When the JSP pre-compile functionality is being used

aa....aa: JSP work directory name
When the JSP pre-compile functionality is not being used

aa....aa: Name of the temporary directory for JSP

Description

When the JSP pre-compile functionality is being used: The JSP work directory (aa....aa) of the Web application cannot be accessed.
When the JSP pre-compile functionality is not being used: The temporary directory (aa....aa) for JSP of the Web application cannot be accessed.

Action

When the JSP pre-compile functionality is being used

Permission might not be available to access the sub directories present below the JSP work directory of the Web application.

Set the appropriate access permissions.

When the JSP pre-compile functionality is not being used

Permission might not be available to access the sub directories present below the temporary directory for JSP, in the Web application.

Set the appropriate access permissions.

KDJE39202-E

An error occurred in reading the class file generated from the JSP file or the tag file. (class file = aa....aa)

aa....aa: Class file name generated from the JSP file or the tag file

Description

In the case of the J2EE server mode: An error occurred while the class file, generated during the compilation of the JSP file or the tag file, was being read.
In the case of the servlet engine mode: An error occurred while the class file, generated during the compilation of the JSP file, was being read.

Action

Remove the cause due to which an exception occurred while the class file generated during the JSP compilation was being read.

Take action based on the following causes:

File read permission is not available.
The file system has failed.
Memory is insufficient.

KDJE39203-W

An attempt to delete a java file generated from the JSP file or the tag file has failed. (file = aa....aa)

aa....aa: Absolute path of the Java source file generated from the JSP file or the tag file

Description

In the case of the J2EE server mode or the cjjspc command: An error occurred while the Java source file (aa....aa) generated during the compilation of the JSP file or the tag file was being deleted.
In the case of the servlet engine mode: An error occurred while the Java source file (aa....aa) generated during the compilation of the JSP file was being deleted.

Action

Remove the cause due to which an error occurred while the Java source file generated during the compilation of the JSP file or the tag file was being deleted.

The possible causes of error are as follows:

File deletion permission is not available.
The file is open.

KDJE39204-E

The temporary directory aa....aa could not be created.

aa....aa: Name of the temporary directory for JSP

Description

The temporary directory (aa....aa) for JSP of the Web application cannot be created.

Permission might not be available to create sub directories below the temporary directory for JSP, in the Web application.

Action

Set the appropriate access permissions.

KDJE39205-E

An attempt to read the tag library descriptor has failed. (TLD = aa....aa)

aa....aa: TLD file path

Description

An attempt to read the tag library descriptor (TLD) file has failed.

The path aa....aa of the TLD file will be output in the following format:

In the case of a TLD file within the Web application

Path within the Web application
In the case of a TLD file saved in the JAR file of a Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)
In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)
In the case of a TLD file within the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Remove the cause due to which an attempt to read the TLD file has failed.

The possible causes of error are as follows:

The file does not exist.
File read permission is not available.
Read permission is not available for the JAR file that includes the TLD file.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39206-E

An I/O error occurred in reading the tag library descriptor. (TLD = aa....aa)

aa....aa: TLD file path

Description

An I/O error occurred while the tag library descriptor (TLD) file was being read.

The path aa....aa of the TLD file will be output in the following format:

In the case of a TLD file within the Web application

Path within the Web application
In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)
In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)
In the case of a TLD file within the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Remove the cause due to which an error occurred while the TLD file was being read.

The possible causes of error are as follows:

The memory is insufficient.
File read permission is not available.
A file read error occurred due to disk failure.
When the JAR file containing the TLD file was specified, the JAR file was not in the JAR format.
When the TLD file present in another host was specified and a network error occurred.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39207-E

The tag library descriptor was not found inside the JAR file. (JAR file = aa....aa, TLD file entry = bb....bb)

aa....aa: JAR file path

bb....bb: Entry name of the TLD file

Description

The tag library descriptor (TLD) file was not found in the JAR file.

The path aa....aa of the JAR file will be output in the following format

In the case of a JAR file within the Web application

Path within the Web application
In the case of library JAR

LIB (Path from the root of the J2EE application)
In the case of a JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file)

Action

Use the correct JAR file that contains the TLD file.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39208-E

Unexpected error occurred in reading the tag library descriptor.

Description: An unexpected error occurred while the tag library descriptor (TLD) file was being read.
Action: Acquire the maintenance information, and then contact maintenance personnel.

KDJE39209-W

The host name specified in property webserver.connector.ajp13.bind_host could not be resolved. (host name = aa....aa)

aa....aa: Specified host name

Description

The host (aa....aa) specified in the property webserver.connector.ajp13.bind_host cannot be resolved.

The wild card address will be used.

Action

When using an address other than the wild card address, specify the resolvable local host name or the IP address of the local host, and then restart the server.

KDJE39210-W

The host name specified in property webserver.connector.http.bind_host could not be resolved. (host name = aa....aa)

aa....aa: Specified host name

Description

The host (aa....aa) specified in the property webserver.connector.http.bind_host cannot be resolved.

The wild card address will be used.

Action

When using an address other than the wild card address, specify the resolvable local host name or the IP address of the local host, and then restart the server.

KDJE39211-E

An error occurred in initializing the pageContext object. (J2EE application = aa....aa, context root = bb....bb, JSP file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root

cc....cc: JSP file name

Description

An error occurred during the initialization of the pageContext object.

The stack trace will be output in the Web servlet log.

If the log is not output, the memory might be insufficient. The memory might be insufficient because the value specified in the buffer attribute of the page directive of JSP is too large.

Action

Check the stack trace output to the Web servlet log.

If the memory is insufficient, secure the memory that can be used by the system, and then restart the server.

KDJE39212-W

The host specified in property webserver.connector.ajp13.bind_host could not be bound. (host = aa....aa)

aa....aa: Specified host name

Description

The host (aa....aa) specified in the property webserver.connector.ajp13.bind_host cannot be bound.

A host other than the local host might be specified.

The wild card address will be used.

Action

When using an address other than the wild card address, specify the correct host, and then restart the server.

KDJE39213-W

The host specified in property webserver.connector.http.bind_host could not be bound. (host = aa....aa)

aa....aa: Specified host name

Description

The host (aa....aa) specified in the property webserver.connector.http.bind_host cannot be resolved.

A host other than the local host might be specified.

The wild card address will be used.

Action

When using an address other than the wild card address, specify the correct host, and then restart the server.

KDJE39214-E

An attempt to generate a java file from the JSP file or the tag file has failed. (file = aa....aa, java file = bb....bb)

aa....aa: Path within the Web application of this JSP file or the tag file (in the case of a tag file saved in a JAR file, however, output is in the following format:

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

bb....bb: Java source file name that cannot be generated

Description

In the case of the J2EE server mode or the cjjspc command: A Java source file (bb....bb) cannot be generated from the JSP file or the tag file (aa....aa).
In the case of the servlet engine mode or the cjjsp2java command: A Java source file (bb....bb) cannot be generated from the JSP file (aa....aa).

Action

Take action for the cause due to which the Java source file cannot be generated.

Take action based on the following causes for the error:

The disk space was not enough for generating the Java file.
The file system has failed.

KDJE39215-W

The host name specified in property webserver.connector.http.bind_host was a loopback address. (host name = aa....aa)

aa....aa: Specified host name

Description

A loopback address was specified in the property webserver.connector.http.bind_host.

The wild card address will be used.

Action

When using an address other than the wild card address, specify an appropriate host that is not a loopback address, and then restart the server.

KDJE39216-E

The URI in the taglib directive is invalid because a URI in a taglib directive is mapped absolute and the taglib element is not in web.xml. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, taglib directive uri = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format: 'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: uri attribute value of the taglib directive of this JSP file or tag file

Description

In the case of the J2EE server mode or the cjjspc command

An error occurred during the analysis of the JSP file or the tag file (cc....cc).

The uri attribute value (cc....cc) of the taglib directive of the JSP file or the tag file is invalid.

In the case of the servlet engine mode or the cjjsp2java command

An error occurred during the analysis of the JSP file (cc....cc).

The uri attribute value (cc....cc) of the taglib directive of the JSP file is invalid.

Action

If taglib is not mapped to the <taglib> tag of web.xml, or to the <uri> tag of the tag library descriptor (TLD) file, the absolute URI cannot be specified in the uri attribute of the taglib directive of JSP.

Either map taglib to the <taglib> tag of web.xml or to the <uri> tag of the TLD file, or specify the uri attribute of taglib directive of JSP with a relative path within the Web application.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39217-I

The web application which parameters of the thread control per web application have not been set is deployed. (J2EE application = aa....aa, context root = bb....bb, max threads = cc....cc, default queue size = dd....dd, max threads limit of the web container = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root

cc....cc: Maximum number of concurrently executing threads of a Web application, in which the control of concurrently executing number of threads for each Web application is not specified

dd....dd: Default size of the pending queue

ee....ee: Maximum number of concurrently executing threads for each Web container

Description

A Web application, in which the setting to control the number of concurrently executing threads in each Web application is not specified, is deployed.

No change exists in the maximum number of concurrently executing threads of an already deployed Web application.

KDJE39218-I

The web application which parameters of the thread control per web application have been set is deployed. (J2EE application = aa....aa, context root = bb....bb, max threads = cc....cc, exclusive threads = dd....dd, queue size = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root

cc....cc: Maximum number of concurrently executing threads for each Web application

dd....dd: Number of dedicated threads

ee....ee: Size of the pending queue of each Web application

Description: A Web application, in which the setting to control the number of concurrently executing threads in each Web application is specified, is deployed.

KDJE39219-I

The ClassLoader for the web application was initialized. (context root = aa....aa, initialized time= bb....bb)

aa....aa: Context root

bb....bb: Initialized time

Description: The Class Loader for the Web application is initialized.

KDJE39220-I

The ClassLoader for the web application was finalized. (context root = aa....aa, initialized time = bb....bb)

aa....aa: Context root

bb....bb: Initialized time

Description

This message indicates that a Web application class loader was destroyed.

This message is displayed when the finalize processing (processing of the finalize method) of the Web application class loader is executed after the J2EE application stops.

If this message is not displayed even after starting and stopping the Web applications repeatedly, a memory leak might have occurred.

By comparing the context root and time information output in the KDJE39219-I message, you can identify the Web application class loader that was destroyed. For details, see Appendix B Configuration of the Class Loaders in the uCosminexus Application Server Common Container Functionality Guide.

KDJE39221-W

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

aa....aa: Reason code

Description

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

Action

Take action depending on the contents of the reason code shown in aa....aa.

The following reason codes are displayed in aa....aa:

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

KDJE39222-I

The parameters of the thread control per web application is modified. (J2EE application = aa....aa, context root = bb....bb, max threads = cc....cc, exclusive threads = dd....dd, queue size = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Maximum number of concurrently executing threads after change in settings

dd....dd: Number of dedicated threads after change in settings

ee....ee: Size of the pending queue of each Web application after change in settings

Description: The settings related to the number of concurrently executing threads in each Web application were changed.

KDJE39223-E

The specified number of exclusive threads was not able to be assigned. (assignable threads = aa....aa)

aa....aa: Number of assignable threads

Description

The specified number of dedicated threads cannot be assigned.

The number of dedicated threads of Web application after the change in settings needs to be lesser than or equal to the number of assignable threads. If the number of assignable threads is 0, the number of dedicated threads cannot be increased.

Action

Revise the set number of dedicated threads of the Web application.

KDJE39224-W

The specified property is invalid.(context root=aa....aa, resource=bb....bb, cc....cc=dd....dd)

aa....aa: Context root name

bb....bb: Resource name

cc....cc: Property name

dd....dd: Property value

Description

The specified value of the property is invalid.

The default value will be applied.

Action

If you want to apply a value other than the default value, revise the property value.

KDJE39225-E

The HttpSession object could not be instantiated because the number of HttpSession had reached the maximum. (J2EE application = aa....aa, context root = bb....bb, max sessions = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Maximum number of HttpSession

Description

An HttpSession object cannot be generated because the number of HttpSession has reached the maximum value.

If this message is output frequently, the maximum value of the number of HttpSession might be too small.

Action

If necessary, increase the maximum value of the number of HttpSession.

KDJE39226-I

The maximum number of the HttpSession is not specified. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The maximum value of the of HttpSession is not specified.

The default value will be used.

KDJE39227-I

The maximum number of the HttpSession was applied. (J2EE application = aa....aa, context root = bb....bb, max sessions = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Maximum number of HttpSession

Description: The maximum value of the number of HttpSession was set.

KDJE39228-E

The HTTP request body is too large. The internal http server refuses the request. (request URL = aa....aa, content length = bb....bb)

aa....aa: Request URL

bb....bb: Value specified in the Content-Length header

Description: The simple Web server has denied the accessed request because the body information of the HTTP request is too large.
Action: Remove the cause due to which the size of the body information of HTTP request has become inappropriately large, and then re-access the server.

KDJE39229-E

aa....aa

aa....aa: Stack trace of the exception

Description: An exception occurred during the execution of Servlet API.
Action: Remove the cause of the occurrence of the exception, and then re-execute the command.

KDJE39230-I

aa....aa

aa....aa: Stack trace of the exception

Description: An exception occurred during the execution of Servlet API. The exception output in this message might, however, be ignored.

KDJE39231-W

The number of lines in the generated _jspService method or doTag method has exceeded 1000. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, number of lines = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format: 'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: Number of lines including the blank lines or comment lines of the generated _jspService method or doTag method

Description

In the case of the J2EE server mode or the cjjspc command: The number of lines of the _jspService method or the doTag method generated from the JSP file or the tag file has exceeded 1000, including the comments and blank lines.
In the case of the servlet engine mode or the cjjsp2java command: The number of lines of the _jspService method generated from the JSP file has exceeded 1000, including the comments and blank lines.

Action

From the specifications of the Java virtual machine, the byte code of one method needs to be within 64 kilobytes. If the byte code of a method exceeds 64 kilobytes, it will result in an error during the generation of class file, or the exception java.lang.LinkageError will occur when the class is loaded.

If the size of one method is within 64 kilobytes, but is still extremely large, the following adverse effects might occur:

A lot of time would be taken for GC processing.
A lot of time would be taken for JIT compilation.
A lot of memory would be consumed for JIT compilation.

As a result, the size of one method on the Java source is recommended to be within 500 lines, excluding comments and blank lines.

Change JSP as follows to reduce the number of lines of Java code generated from JSP:

In the case of JSP file: Divide the JSP file through dynamic inclusion (include action).
In the case of tag file: Either divide the tag file used from the JSP file into multiple tag files, or divide the tag file so as to invoke other tag files from it.

KDJE39232-E

An attempt to delete a class file generated from the JSP file or the tag file has failed. (class file = aa....aa)

aa....aa: Absolute path of the class file generated from the JSP file or the tag file

Description

In the case of the J2EE server mode or the cjjspc command: An error occurred while the class file (aa....aa) generated during the compilation of the JSP file or the tag file was being deleted.
In the case of the servlet engine mode: An error occurred while the class file (aa....aa) generated during the compilation of the JSP file was being deleted.

Action

Take action for the cause of the error that occurred while the class file, generated during the JSP compilation, was being deleted.

The possible causes of error are as follows:

File deletion permission is not available.
The file is open.

KDJE39233-I

A cache function will be applied. (J2EE application = aa....aa, context root = bb....bb, cache size = cc....cc, file size threshold = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Value (in bytes) of the memory size that can be cached in each Web application

dd....dd: Maximum value (in bytes) of the file size that can be cached

Description: The cache functionality will be enabled.

KDJE39234-I

The total size and the number of a cache. (J2EE application = aa....aa, context root = bb....bb, total size = cc....cc, number of a cache = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Total size (in bytes) of the cache

dd....dd: Number of cache

Description: The total size and number of cache will be output.

KDJE39235-W

The value of the cache function specified by web.xml is invalid. (J2EE application = aa....aa, context root = bb....bb, tag name = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Invalid tag name

Description: The setting of the cache functionality specified in web.xml is invalid. The setting of web.xml will be ignored and the Web application will start.
Action: Stop the Web application, modify the corresponding tag in web.xml, and then start the Web application.

KDJE39248-W

The redirection definition is ignored because there are invalid settings. (definition name = aa....aa)

aa....aa: Ignored redirect definition name

Description: The redirect definition will be ignored because the setting is invalid.
Action: Correctly specify the properties of the redirect functionality, and then restart the J2EE server.

KDJE39249-W

The required property of the redirection definition is not specified. (property = aa....aa)

aa....aa: Property name

Description

The mandatory properties of the redirect definition have not been specified.

Action

Specify the mandatory properties, and then restart the J2EE server. The mandatory properties are as follows:

webserver.connector.inprocess_http.redirect.redirect-definition-name.request_url
webserver.connector.inprocess_http.redirect.redirect-definition-name.redirect_url

(when other than 200 is specified in webserver.connector.inprocess_http.redirect.redirect-definition-name.status)
webserver.connector.inprocess_http.redirect.redirect-definition-name.file

(when 200 is specified in webserver.connector.inprocess_http.redirect.redirect-definition-name.status)

KDJE39250-W

The forbidden property of the redirection definition is specified. (aa....aa = bb....bb)

aa....aa: Property name

bb....bb: Property value

Description

A forbidden property of the redirect definition is specified.

Action

Delete the forbidden property, and then restart the J2EE server. The following property cannot be specified under specific conditions:

webserver.connector.inprocess_http.redirect.redirect-definition-name.request_url

(when 200 is specified in webserver.connector.inprocess_http.redirect.redirect-definition-name.status)

KDJE39251-W

The response body file for the redirection definition cannot be read. (aa....aa = bb....bb)

aa....aa: Property name that specifies a file

bb....bb: Property value

Description: The file, sent as the response body of the redirect functionality, cannot be read.
Action: Either the file does not exist, or permission is not available for the file. Specify a file that exists, set appropriate permissions, and then restart the J2EE server.

KDJE39252-W

The error contents customization definition is ignored because there are invalid settings. (definition name = aa....aa)

aa....aa: Ignored error contents customization definition name

Description: The error contents customization definition will be ignored because of invalid settings.
Action: Correctly specify the properties of the error contents customization functionality and then restart the J2EE server.

KDJE39253-W

The required property of the error contents customization definition is not specified. (property = aa....aa)

aa....aa: Property name

Description

The mandatory properties of the error contents customization definition have not been specified.

Action

Specify the mandatory properties, and then restart the J2EE server. The following properties are mandatory:

webserver.connector.inprocess_http.error_custom.error-contents-customization-definition-name.status
webserver.connector.inprocess_http.error_custom.error-contents-customization-definition-name.file

(when webserver.connector.inprocess_http.error_custom.error-contents-customization-definition-name.redirect_url is not specified)

KDJE39254-W

The forbidden property of the error contents customization definition is specified. (aa....aa = bb....bb)

aa....aa: Property name

bb....bb: Property value

Description

The forbidden property of the error contents customization definition is specified.

Action

Delete the forbidden property, and then restart the J2EE server. The following property cannot be specified under specific conditions:

webserver.connector.inprocess_http.error_custom.error-contents-customization-definition-name.file

(when webserver.connector.inprocess_http.error_custom.error-contents-customization-definition-name.redirect_url is specified)

KDJE39255-W

The response body file for the error contents customization definition cannot be read. (aa....aa = bb....bb)

aa....aa: Property name that specifies a file

bb....bb: Property value

Description: The file, sent as the response body of the error contents customization functionality, cannot be read.
Action: Either the file does not exist, or permission is not available for the file. Specify a file that exists, set appropriate permissions, and then restart the J2EE server.

KDJE39264-W

An error occurred during the data acquisition. (request URL = aa....aa)

aa....aa: Request URL

Description

An error occurred during the acquisition of the POST data.

The value of the Content-Length header and the actually read parameter size do not match.

Action

Check the value of the Content-Length header and the size of the request body.

KDJE39266-E

The timeout occurred in writing the response data to the client. (client = aa....aa : bb....bb)

aa....aa: IP address of the client to which you will connect

(IP address of the reverse proxy, if reverse proxy is being used

bb....bb: Port number of the client to which you will connect

(Port number of the reverse proxy, if reverse proxy is being used)

Description

A timeout occurred while a response was being written to the client.

Action

Confirm the following details:

When the proxy server is not being used

No invalid connection exists from a Web client to the J2EE server.
No problem exists in the communication path.

When the proxy server is being used

Reverse proxy is running properly.
No problem exists in the communication path between the reverse proxy and the J2EE server.

Take the following action for the confirmed details:

If a Web client has established an invalid connection, restrict the client based on the address and the port number output in the message.
If a problem exists in the communication path, remove it.
If the reverse proxy is not running properly, resolve the problem of the reverse proxy.

KDJE39271-E

The thread ended abnormally.(name=aa....aa,hash=bb....bb,priority=cc....cc)

aa....aa: Thread name

bb....bb: Hash value

cc....cc: Priority

Description

The thread that receives requests from the redirector was terminated abnormally.

Action

The system resources (memory, file descriptor) might be insufficient.

Implement the action of the message KDJE39273-E output just before this message, and then restart the Web container.

KDJE39272-E

The illegal processing in the servlet or JSP was detected during executing the request.

Description

An invalid processing in the servlet or JSP was detected during the execution of a request. The operation for the request or the response might be executed from multiple threads.

Action

From the log, identify the servlet or JSP that was executed just before the output of this message, save the following objects in instance variables, and then confirm that these objects are not being executed from multiple threads.

javax.servlet.ServletOutputStream object
javax.servlet.http.HttpServletResponse object
java.io.PrintWriter object acquired by the getWriter method of the javax.servlet.ServletResponse class

KDJE39273-E

An exception was raised during connecting with the redirector. (exception = aa....aa)

aa....aa: Exception information notified from Java VM in the case of failure in establishing a connection with the redirector

Description

An attempt to establish a communication connection from the redirector has failed. This might be due to the occurrence of a problem that does not allow continuance of an operation, such as lack of resources of the system in which the Web container is running.

If message KDJE39275-W is output after this message, and if the connection from the redirector is successful after the occurrence of the failure notified by this message, the system might be recovered.

Even if the error is not output in the Web server log or the redirector log, the system might not recover from this failure when the message KDJE39275-W is not output.

Action

From the Web server access log and the redirector log, make sure that the request is being executed properly. In the case of the error occurrence during the communication with the Web container, the system resources, such as memory, file descriptor, or the TCP port might be insufficient. Check the usage status of the system resources, and then make sure whether the estimation of the system resources is correct.

If resources are insufficient, change the system settings.

KDJE39275-W

The connecting with the redirector has succeeded.

Description

An attempt to establish a connection with the redirector was successful, although an exception occurred while establishing a connection with the redirector. This message is output after the message KDJE39273-E, when a connection with the redirector is established successfully. Message KDJE39273-E is output when a connection with the redirector cannot be established due to insufficient system resources, such as memory, file descriptor, or the TCP port.

Action

From the Web server log and the Web container log, make sure whether the request is being executed properly.

If the request is not being executed properly, identify the cause of the error on the basis of the action of the message KDJE39273-E, and then counteract.

KDJE39280-E

The request header is invalid. The web container refused the request. (request uri = aa....aa, bb....bb = cc....cc)

aa....aa: Request URI

bb....bb: Name of the invalid request header

cc....cc: Value of the invalid request header

Description: The Web container server has denied the accessed request because an invalid request header was received.
Action: Make sure whether no problem exists in the Web client that has sent the invalid request, and avoid sending invalid request headers.

KDJE39281-E

An exception was raised during handling the exception. (exception = aa....aa, method = bb....bb , exception = cc....cc)

aa....aa: User-created exception whose method is invoked

bb....bb: Invoked method

cc....cc: Exception that has occurred during the method invocation of the user-created exception

Description

An exception occurred during the method invocation of the user-created exception class.

When the KDJE39059-E message ID is output immediately after this message, an exception occurred during the method invocation of the user-created exception class, while the error page was being displayed.

At this point, the error page is not displayed.

Action

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39282-E

The JSP translation failed because a JSP validation error message was reported from the extra Tag info. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, tag library = dd....dd, tag name = ee....ee, number of message = ff....ff)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the cjjspc command

bb....bb: The context root name in the case of the J2EE server mode, and a null character string in the case of the cjjspc command

cc....cc: Path within the Web application of this JSP file or the tag file (in the case of a tag file saved in a JAR file, however, output is in the following format: 'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: uri attribute value of the taglib directive of this JSP file or tag file

ee....ee: Tag name specified in <taglib><tag><name> of the tag library descriptor

ff....ff: Number of validation error messages

Description: The TagExtraInfo class has reported an error detected during the validation of the attributes.
Action: See the validation error message, and then confirm the usage method of the tag library. The validation error message is output in the message log or the console with the message ID KDJE39283-E.

KDJE39283-E

A validation message. (id = aa....aa, message = bb....bb)

aa....aa: Return value of getId method of the ValidationMessage class

bb....bb: Return value of the getMessage method of the ValidationMessage class

Description

The message contents (javax.servlet.jsp.tagext.ValidationMessage class) of the validation error that occurred are described in KDJE39282-E.

If the ValidationMessage is null, aa....aa and bb....bb will also become null.

Action

See the output message, and then confirm the usage method of the tag library.

KDJE39284-W

The unknown element is described. (J2EE application = aa....aa, context root = bb....bb, element = cc....cc, file = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Defined element name

dd....dd: Path of the corresponding file

Description

In the case of the J2EE server mode

An element, not defined in the XML schema, is coded in the corresponding tag library descriptor (TLD) file. The contents of this element will be ignored.

The path dd....dd of the corresponding file will be output in the following format:

In the case of a file within the Web application

Path within the Web application
In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)
In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

In the case of the servlet engine mode

An element, not defined in the XML schema, is coded in the corresponding web.xml or TLD file. The contents of this element will be ignored.

The path dd....dd of the corresponding file will be output in the following format:

In the case of a file within the Web application

Path within the Web application
In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)
In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

In the case of the J2EE server mode: The message KDJE39286-W is output in the message log. Check the contents.
In the case of the servlet engine mode: If the target file is web.xml, the message KDJE39285-W is output in the message log, and if the target file is a TLD file, the message KDJE39286-W is output. Check the contents.

KDJE39285-W

The web.xml contains the unknown element. (context root = aa....aa)

aa....aa: Context root name

Description

An element, not defined in the XML schema, is coded in web.xml.

The invalid element will be ignored, and then the processing continues.

Action

The corresponding invalid element is output in the Web servlet log, with the ID KDJE39284-W. Check the contents of the invalid element.

KDJE39286-W

The tag library descriptor contains the unknown element. (J2EE application = aa....aa, context root = bb....bb, TLD = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Path of the corresponding file

Description

An element, not defined in the XML schema, is coded in the tag library descriptor (TLD) file. The invalid element will be ignored, and then the processing continues.

The path cc....cc of the corresponding file will be output in the following format:

In the case of a file within the Web application

Path within the Web application
In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)
In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

The corresponding invalid element is output in the Web servlet log, with the ID KDJE39284-W. Check the contents of the invalid element.

KDJE39287-W

The specified location of the JAR containing the tag library descriptor file defining the tag-file element is deprecated. (J2EE application = aa....aa, context root = bb....bb, JAR location = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the cjjspc command

bb....bb: The context root name in the case of the J2EE server mode, and a null character string in the case of the cjjspc command

cc....cc: Path within the Web application of the JAR file

Description

Deployment of the JAR file including the TLD file that defines the element <taglib><tag-file> specified in web.xml, JSP file, or the tag file is not recommended.

The Web container reads /META-INF/taglib.tld present in this JAR file, but ignores the <taglib><tag-file> tag.

Action

We recommend that you deploy the JAR file in the directory /WEB-INF/lib/.

When changes are made so as to deploy the JAR file in the directory /WEB-INF/lib, also modify the file that specifies the JAR file.

KDJE39288-I

The webserver.jsp.compile.options property is specified. (value = aa....aa)

aa....aa: Set value of webserver.jsp.compile.options

Description: The webserver.jsp.compile.options property is specified.

KDJE39289-W

The specified location of the tag library descriptor file is deprecated. (J2EE application = aa....aa, context root = bb....bb, TLD location = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of the TLD file

Description

In the case of the J2EE server mode or the cjjspc command: Deployment of the tag library descriptor (TLD) file specified in web.xml, JSP file or the tag file is not recommended.
In the case of the servlet engine mode or the cjjsp2java command: Deployment of the TLD file specified in web.xml, or the JSP file is not recommended.

Action

When the Web application version is Servlet 2.3: Deployment of the file is recommended below the directory /WEB-INF.
When the Web application version is Servlet 2.4 or later: Deployment of the file is recommended below the directory /WEB-INF, excluding the directory /WEB-INF/classes, or the directory /WEB-INF/lib.

KDJE39290-W

The tag library descriptor is invalid. The mustUnderstand attribute is specified in aa....aa element. (J2EE application = bb....bb, context root = cc....cc, file = dd....dd)

aa....aa: Element name in which true is set as the value of mustUnderstand attribute

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or cjjspc command

cc....cc: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of cjjspc command

dd....dd: Path of the corresponding file

Description

True is specified as the value of mustUnderstand attribute of element aa....aa. This tag library descriptor (TLD) file becomes disabled and cannot be used.

The path dd....dd of the corresponding file will be output in the following format:

In the case of a file within the Web application

Path within the Web application
In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)
In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)
In the case of a TLD file within the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Check the contents of the element in which the mustUnderstand attribute of the TLD file are set.

KDJE39291-E

An exception aa....aa was raised in validation of the attribute by the TagExtraInfo class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: TagExtraInfo class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

dd....dd: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

Description

An exception occurred during the validation of the attribute by the TagExtraInfo class (bb....bb).

Action

Remove the cause due to which an exception occurred during the validation of the JSP file or the tag file by the TagExtraInfo class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39292-W

The class file generated from the JSP by the earlier version of the web container exists. (J2EE application = aa....aa, context root = bb....bb, class file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the class file

Description: The class file generated from the JSP by the earlier version of the Web container exists. The Web container will compile JSP.
Action: The class file generated from the JSP with the earlier version of the Web container cannot be used. Delete it from the temporary directory for JSP.

KDJE39293-W

The version of the tag library descriptor is aa....aa although the version of the web application is bb....bb. The tag library descriptor is invalid. (J2EE application = cc....cc, context root = dd....dd, file = ee....ee)

aa....aa: Version of the TLD file

bb....bb: Version of the Web application

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

dd....dd: Context root name

ee....ee: Path of the corresponding file

Description

The version of the tag library descriptor (TLD) file is invalid. The specified TLD file cannot be used in the current version of the Web application.

The path dd....dd of the corresponding file will be output in the following format:

In the case of a file within the Web application

Path within the Web application
In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)
In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Implement one of the following actions in the Web application in which the problem occurred:

Change the TLD file version to a version supported by the Web application version.
Change the Web application version to a version supported by the TLD file version.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

When the reload functionality of the J2EE application is being used and the TLD file is modified, either reload or redeploy.

When the reload functionality of the J2EE application is not being used, or the version of the Web application is changed, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

KDJE39294-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the validation of the attribute by the TagExtraInfo class will be output row-wise.

Action

Remove the cause due to which the TagExtraInfo class throws an exception.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39295-E

An attempt to start a web application has failed because the aa....aa version of the web application is not supported by the servlet engine mode. (context root = bb....bb)

aa....aa: Version of the Web application

bb....bb: Context root name

Description

The Web application version is aa....aa. This version is not supported in the servlet engine mode.

This Web application cannot be started.

Action

To use a Web application of Servlet2.4 or a later version, use the J2EE server mode.

KDJE39296-E

The function class aa....aa specified in the tag library descriptor could not be found. (J2EE application = bb....bb, context root = cc....cc, function name = dd....dd, tag library = ee....ee)

aa....aa: Name of the function class specified by the element <function-class> of the TLD file

bb....bb: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

cc....cc: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

dd....dd: Name of the function specified in the element <function><name> of the TLD file

ee....ee: uri attribute value of the taglib directive of this JSP file or tag file

Description

The function class specified by the element <function-class> of the tag library descriptor (TLD) file was not found.

Action

Include the class required for execution of the class defined in the element <function-class> of the TLD file, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39297-W

The specified listener class implementing the aa....aa interface was not registered because this interface is not supported in this web application version. (J2EE application = bb....bb, context root = cc....cc, listener class = dd....dd)

aa....aa: Implemented listener interface name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

dd....dd: Class name specified in web.xml

Description

The specified class implements the listener interface supported by the Servlet 2.4 specifications.

The Servlet 2.4 specifications support the following listener interfaces:

javax.servlet.ServletRequestListener
javax.servlet.ServletRequestAttributeListener

The specified class is not registered as a listener, and is ignored.

Action

To use the listener supported by the Servlet 2.4 specifications, use the Web application version in the application of Servlet 2.4 or later.

KDJE39298-E

An attempt to initialize the JSP has failed because a class file generated from the JSP file or a class file depended on it is invalid. (J2EE application = aa....aa, context root = bb....bb, JSP file = cc....cc, class file = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Path within the Web application of the JSP file that has failed in initialization

dd....dd: Absolute path of the invalid class file

Description

An attempt to initialize the JSP has failed because a class file generated from the JSP file or a class file dependent on it is invalid.

Action

The class file generated from the JSP file or the tag file is invalid.

When using JSTL or JSF in a Web application conforming to Servlet 2.5 or later specifications

The JSTL or the JSF might not be set up properly. Make sure that a JSTL or a JSF of the correct version is added to the class path, and then restart the J2EE server.

When the JSP pre-compile functionality used during application startup is used

Use the JSP pre-compile functionality used during application startup, and compile all JSPs included in the application.

When the JSP pre-compile functionality used during application startup is not used

Compile all JSPs included in the Web application. Update the Web application so that all the class files generated from the JSP file or the tag file are included.

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

KDJE39299-I

The class file generated from the JSP file or the tag file was modified. (J2EE application = aa....aa, context root = bb....bb, class file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Absolute path of the class file

Description: The class file generated from the JSP file or the tag file was updated.

KDJE39300-I

The class file generated from the JSP file or the tag file was removed. (J2EE application = aa....aa, context root = bb....bb, class file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Absolute path of the class file

Description: The class file generated from the JSP file or the tag file was deleted.

KDJE39301-E

An exception aa....aa was raised in initialization of the function class bb....bb. (J2EE application = cc....cc, context root = dd....dd, function name = ee....ee, tag library = ff....ff)

aa....aa: Occurred exception name

bb....bb: Name of the function class specified by the element <function-class> of the TLD file

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the cjjspc command

dd....dd: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

ee....ee: Name of the function specified in the element <function><name> of the TLD file

ff....ff: uri attribute value of the taglib directive of this JSP file or tag file

Description

An exception occurred while the function class specified by the element <function-class> of the tag library descriptor (TLD) file was being loaded.

Action

Remove the cause due to which an exception occurred while the class defined by the element <function-class> of the TLD file was being loaded.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39302-E

The method parameter class aa....aa specified in the tag library descriptor could not be found. (J2EE application = bb....bb, context root = cc....cc, function name = dd....dd, tag library = ee....ee)

aa....aa: Name of the parameter class specified by the element <function-signature> of the TLD file

bb....bb: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

cc....cc: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

dd....dd: Name of the function specified in the element <function><name> of the TLD file

ee....ee: uri attribute value of the taglib directive of this JSP file or tag file

Description

The parameter class of the function specified by the element <function-signature> of the tag library descriptor (TLD) file was not found.

Action

Include the class required for execution of the parameter class defined in the element <function-signature> of the TLD file, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39303-E

An exception aa....aa was raised in initialization of the function. (J2EE application = bb....bb, context root = cc....cc, function name = dd....dd, tag library = ee....ee)

aa....aa: Occurred exception name

bb....bb: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

cc....cc: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

dd....dd: Name of the function specified in the element <function><name> of the TLD file

ee....ee: uri attribute value of the taglib directive of this JSP file or tag file

Description

An exception occurred either while the parameter class of the function specified by the element <function-signature> of the tag library descriptor (TLD) file was being loaded or while the function class specified by the element <function-class> was being accessed.

Action

Remove the cause due to which an exception occurred while the parameter class of the function specified by the element <function-signature> of the TLD file was being loaded, or while the function class specified by the element <function-class> was being accessed.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39304-W

The url-pattern element in web.xml contains the carriage return or line feed character. (J2EE application = aa....aa, context root = bb....bb, element body = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Contents specified in the element <url-pattern>

Description

The linefeed code (CR(#xD) or LF(#xA)) is included in the contents of the element <url-pattern> defined in web.xml.

You cannot include the linefeed code in the contents specified in the element <url-pattern>.

The definition specified by this element will be disabled.

The contents of cc....cc will be displayed without linefeed code.

Action

Modify the contents of the corresponding element, and then redeploy the application.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

KDJE39305-E

The attribute type aa....aa specified for the attribute bb....bb could not be found. (J2EE application = cc....cc, context root = dd....dd, tag name = ee....ee, tag library = ff....ff)

aa....aa: Type of this attribute

bb....bb: Name of this attribute

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the cjjspc command

dd....dd: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

ee....ee: Name of the custom tag that defines this attribute

ff....ff: uri attribute value or tagdir attribute value of the taglib directive of this JSP file or tag file (in the case of the tagdir attribute, output is in the following format: tag library = urn:jsptagdir:value-of-tagdir-attribute)

Description

The class specified in the type attribute of the attribute directive of the class or tag file specified by the element <tag><attribute><type> of the tag library descriptor (TLD) file was not found.

Action

Include the class required for execution of the class defined in the type attribute of the <type> element or the attribute directive of the TLD file, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39306-E

An exception aa....aa was raised in initialization of the attribute type bb....bb specified for the attribute cc....cc. (J2EE application = dd....dd, context root = ee....ee, tag name = ff....ff, tag library = gg....gg)

aa....aa: Occurred exception name

bb....bb: Type of this attribute

cc....cc: Name of this attribute

dd....dd: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

ee....ee: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

ff....ff: Name of the custom tag that defines this attribute

gg....gg: uri attribute value or tagdir attribute value of the taglib directive of this JSP file or tag file (in the case of the tagdir attribute, output is in the following format: tag library = urn:jsptagdir:value-of-tagdir-attribute)

Description

An exception occurred while the class specified in the type attribute of the attribute directive of the class or tag file specified by the element <tag><attribute><type> of the tag library descriptor (TLD) file was being loaded.

Action

Remove the cause due to which an exception occurred while the class defined in the type attribute of the <type> element or the attribute directive of the TLD file was being loaded.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39307-E

The method aa....aa specified in the tag library descriptor could not be found. (J2EE application = bb....bb, context root = cc....cc, function name = dd....dd, function class = ee....ee, tag library = ff....ff)

aa....aa: Function specified by the element <function-signature> of the TLD file

bb....bb: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

cc....cc: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

dd....dd: Name of the function specified in the element <function><name> of the TLD file

ee....ee: Name of the function class specified by the element <function><function-class> of the TLD file

ff....ff: uri attribute value of the taglib directive of this JSP file or tag file

Description

The method specified by the element <function-signature> of the tag library descriptor (TLD) file was not found.

Action

Include the class required for execution of the class defined in the element <function-signature> of the TLD file, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39308-E

An error occurred in analyzing the xml. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, detail = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or the cjjspc command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command

cc....cc: Path of the corresponding file

dd....dd: Detailed information of the occurred error

Description

An attempt to analyze the corresponding web.xml, or the tag library descriptor (TLD) file has failed.

The path cc....cc of the corresponding file will be output in the following format:

In the case of a file within the Web application

Path within the Web application
In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)
In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)
In the case of a TLD file within the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Remove the cause due to which an error occurred during the analysis of web.xml, or the TLD file.

A message with a message ID beginning with KECX will be output in the details of the occurred error. For details on messages with the message ID beginning with KECX, see 11. KECX (Messages Output by Cosminexus XML Processor).

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

When the reload functionality of the J2EE application is being used and the TLD file is modified, either reload or redeploy.

When the reload functionality of the J2EE application is not being used, or the version of the Web application is changed, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command

Re-execute the command.

KDJE39309-E

The class file generated from the JSP file could not be found. (J2EE application = aa....aa, context root = bb....bb, JSP file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Path within the Web application of the JSP file

Description

The class file generated from the JSP file was not found.

Action

When the JSP pre-compile functionality used during application startup is used

If the JSP file does not exist, add it, and then update the Web application.

If the JSP file exists, an error occurs during the JSP compilation. Remove the cause of the error, and then update the Web application.

When the reload functionality of the J2EE application is being used, either compile the added or modified JSP, or redeploy, and then execute the JSP pre-compile functionality used during application startup.

When the reload functionality of the J2EE application is not being used, redeploy, and then execute the JSP pre-compile functionality used during application startup.

When the JSP pre-compile functionality used during application startup is not used

To the JSP work directory, add the class file generated from the JSP file and from the tag file referenced by the JSP file, and then update the Web application.

When the reload functionality of the J2EE application is being used, either add the class file generated from the JSP file and from the tag file referenced by the JSP file, or redeploy.

When the reload functionality of the J2EE application is not being used in an expanded archive format application, either stop the application, add the class file generated from the JSP file and from the tag file referenced by the JSP file, and then restart the application, or else redeploy the application.

In the case of an archive format application, redeploy.

KDJE39310-I

The JSP reload processing will now start. (J2EE application = aa....aa, context root = bb....bb, number of JSP files = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of JSP files to be reloaded

Description

The JSP reload processing will start.

When multiple JSP files are updated, the updated JSP files will be reloaded sequentially.

KDJE39311-I

The JSP reload processing has finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The JSP reload processing has finished.

When multiple JSP files are updated, reload is executed for multiple JSP files.

KDJE39312-I

The JSP reload processing per JSP file will now start. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the class file generated from the JSP file, when the JSP pre-compile functionality is being used. Absolute path of the JSP file, when the JSP pre-compile functionality is not being used.

Description

When the JSP pre-compile functionality is being used: Reload processing of the class generated from the JSP file will start.
When the JSP pre-compile functionality is not being used: Recompilation of the JSP file will start.

KDJE39313-I

The JSP instance was destroyed because the JSP file or the class file generated from the JSP file was removed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the class file generated from the JSP file, when the JSP pre-compile functionality is being used. Absolute path of the JSP file, when the JSP pre-compile functionality is not being used.

Description

When the JSP pre-compile functionality is being used: The JSP instance was released because the class file generated from the JSP file is deleted.
When the JSP pre-compile functionality is not being used: The JSP instance was released because the JSP file is deleted.

KDJE39314-W

The uri to the tag library descriptor mapping is invalid because an uri element is a duplicate of the other file. (J2EE application = aa....aa, context root = bb....bb, uri = cc....cc, valid TLD = dd....dd, invalid TLD = ee....ee)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Duplicate uri

dd....dd: Path within the Web application of the TLD file in which mapping from the uri is valid (in the case of a TLD file saved in a JAR file, however, output is in the following format: Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

ee....ee: Path within the Web application of the TLD file in which mapping from the uri is invalid (in the case of a TLD file saved in a JAR file, however, output is in the following format: Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

Description

In the case of the J2EE server mode, servlet engine mode, or cjjspc command: The contents of the <uri> element and the mapping of the TLD file will become invalid because the contents of the <uri> element coded in the tag library descriptor (TLD) file are same as either the contents of the <taglib-uri> element of web.xml, or the contents of the <uri> element coded in another TLD file.
In the case of the cjjsp2java command: The contents of the <uri> element and the mapping of the TLD file will become invalid because the contents of the <uri> element coded in the tag library descriptor (TLD) file are same as either the contents of uri specified in the command argument -taglib, or the contents of the <uri> element coded in another TLD file.

Action

In the case of the J2EE server mode, servlet engine mode, or the cjjspc command

Specify a value in the <uri> element of the TLD file so that it is not the same as the contents defined in web.xml, and another TLD file.

In the case of the cjjsp2java command

Specify a value in the <uri> element of the TLD file so that it is not the same as the contents of uri specified in the command argument -taglib, and another TLD file.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39315-W

The uri to the tag library descriptor mapping is invalid because an uri element is a duplicate of the other file. (J2EE application = aa....aa, context root = bb....bb, uri = cc....cc, invalid TLD = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Duplicate uri

dd....dd: Path within the Web application of the TLD file in which mapping from the uri is invalid (in the case of a TLD file saved in a JAR file, however, output is in the following format: Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

Description

The contents of the <uri> element and the mapping of the TLD file will become invalid because the contents of the <uri> element coded in the tag library descriptor (TLD) file are same as the contents of the <uri> element coded in another TLD file.

Action

Specify a value in the <uri> element of the TLD file so that it is not the same as another TLD file.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39316-W

The taglib element in web.xml is invalid because a taglib-uri element is a duplicate of the other taglib element. (J2EE application = aa....aa, context root = bb....bb, taglib-uri element in the invalid taglib element = cc....cc, taglib-location element in the invalid taglib element = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or the cjjspc command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command

cc....cc: Contents of the <taglib-uri> element present in the invalid <taglib> element

dd....dd: Contents of the <taglib-location> element present in the invalid <taglib> element

Description

The contents of the <taglib> element specified in web.xml will become invalid because another <taglib> element with the same <taglib-uri> element is specified.

Action

Specify a value in the <taglib-uri> element defined in web.xml so that it is not the same as the <taglib-uri> element specified in another <taglib> element.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command

Re-execute the command.

KDJE39317-E

The JSP reload processing per JSP file has failed because a class file is invalid. (J2EE application = aa....aa, context root = bb....bb, class file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Absolute path of the class file generated from the JSP file or the tag file

Description

An attempt to reload has failed because the class file generated from the JSP file or the tag file, or the class file on which this class depends is invalid.

Action

The class file generated from the JSP file or the tag file is invalid.

Compile all JSPs included in the Web application. Update the Web application so that all the class files generated from the JSP file or the tag file are included, and then reload or redeploy.

KDJE39318-I

The file used by the JSP file or the tag file was excluded from the update detection list. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Absolute path of the file

Description

The file used by the JSP file or the tag file was excluded from the update detection list due to the following factors:

The JSP file or the tag file using this file is updated, and this file is not in use any longer. No other JSP file or tag file is dependent on the corresponding file.
This file or the JSP file or the tag file, using this file, was updated, but a translation error occurred in the JSP file or the tag file. No other JSP file or tag file is dependent on the corresponding file.

KDJE39319-I

The class file generated from the tag file was excluded from the update detection list. (J2EE application = aa....aa, context root = bb....bb, class file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Absolute path of the class file

Description

The class file generated from the tag file was excluded from the update detection list due to the following factors:

The class file generated from the JSP file or the tag file that use this file is updated, and this file is not in use any longer. Other class files generated from the JSP file or tag files dependent on this file do not exist.
An error occurred while the class generated from the JSP file or the tag file using this file was being loaded. Other class files generated from the JSP file or tag files dependent on this file do not exist.

KDJE39320-I

The default encoding of web application is specified. (J2EE application = aa....aa, context root = bb....bb, request = cc....cc, response = dd....dd, JSP file = ee....ee, extension = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Character encoding used for decoding the request body and query (a null character string if not specified in the user property file, HITACHI Application Integrated Property File, or WAR property file)

dd....dd: Character encoding used for encoding the response body (a null character string if not specified in the user property file, HITACHI Application Integrated Property File, or WAR property file)

ee....ee: Character encoding of JSP (a null character string if not specified in the user property file, HITACHI Application Integrated Property File, or WAR property file)

ff....ff: Extension of the static contents when the default response character encoding is applied (a null character string if the extension of the static contents is not specified or if the default response character encoding is not specified)

Description: The default encoding setup functionality was used.

KDJE39321-W

The specified default encoding to J2EE server is not supported. (type = aa....aa, encoding = bb....bb)

aa....aa: Target for setting up the default character encoding

request: Request body and query

response: Response body

jsp: JSP file

bb....bb: Specified character encoding

Description

The specified character encoding cannot be used for decoding the request body and query, for encoding the response body, and as the character encoding of the JSP file.

Ignore the specified contents, and then start the J2EE server.

Action

The specified character encoding cannot be used for decoding the request body and query, for encoding the response body, and as the character encoding of the JSP file. Revise the character encoding.

The character encoding supported by Java VM can be specified. For details about the character encoding supported by Java VM, follow the Supported encoding section in the JDK document. The character strings that can be specified include "Formal name for java.nio API" and its optional name, and "Formal name for java.io and java.lang API" and its optional name described in the Supported encoding section.

KDJE39322-W

The JSP debugging function is enabled.

Description

The JSP debug functionality is enabled.

Action

We recommend not to use the JSP debug functionality in the execution environment because of its effect on the following performances:

Increase in Metaspace area usage
Increase in parsing during class loading

KDJE39324-E

An attempt to output JSP debugging information has failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Path within the Web application of the JSP file or tag file

Description

An attempt to create the JSP debug information has failed.

Action

Take action based on the following causes:

The disk space for embedding the SMAP information in the class file was not sufficient.
The file system has failed.

Check the cause, and take action.

KDJE39325-W

The uri in tag libraries specified Java EE specification cannot override the taglib element in web.xml or uri in tag library descriptor. (J2EE application = aa....aa, context root = bb....bb, uri = cc....cc, invalid TLD = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

bb....bb: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

cc....cc: URI with duplicate definitions

dd....dd: Path of the TLD file with invalid mapping from the URI

Description

The URI of the tag libraries stipulated in the Java EE specifications cannot be overwritten by the value of the <taglib> tag of web.xml, or the value of the <uri> tag of the tag library descriptor.

URI mapping is performed automatically for the tag libraries (JSTL and JSF) stipulated in the Java EE specifications.

When using JSTL 1.2 or later versions and JSF 1.2 or later versions, a TLD file need not be deployed separately.

The path dd....dd of the TLD file, with invalid mapping from the URI, will be output in the following format:

When an invalid definition exists in web.xml

Value of the <taglib-location> tag included in the disabled <taglib> tag
When an invalid definition exists in the TLD file that is not saved in the JAR file within the Web application

Path from the root of the Web application
When an invalid definition exists in the TLD file saved in the JAR file within the Web application

Path from the root of the Web application (entry = path-within-the-JAR-file)
When an invalid definition exists in the TLD file saved in the library JAR

LIB (Path from the root of the J2EE application) (entry = path-within-the-JAR-file)
When an invalid definition exists in the TLD file saved in the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

When using JSTL 1.2 or later versions and JSF 1.2 or later versions, delete the TLD file deployed in the Web application or in the library JAR.

When using a JSTL and JSF different from the above version, disable the automatic mapping of the tag libraries stipulated in Java EE specifications either by the property settings, or by the options of the cjjspc command.

After changing the settings, update the Web application with the following operation:

For J2EE Server: Restart the J2EE server.
In the case of the cjjspc command: Re-execute the command.

KDJE39326-W

The mapping for the URI that identifies the tag library descriptor in the library JAR file is invalid because the <uri> element is duplicated in other files. (J2EE application = aa....aa, context root = bb....bb, URI = cc....cc, valid TLD = dd....dd, invalid TLD = ee....ee)

aa....aa: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

bb....bb: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

cc....cc: Duplicated URI

dd....dd: Path of the TLD file with valid mapping from the URI

ee....ee: Path of the TLD file with invalid mapping from the URI

Description

The mapping of the contents of the <uri> tag and the TLD file is disabled because the contents of the <uri> tag coded in the TLD file within the library JAR (the JAR file specified in the class path in the case of the cjjspc command) are same as the contents of the <taglib-uri> tag of web.xml or the contents of the <uri> tag coded in another TLD file.

Format of the path dd....dd of the TLD file with valid mapping from the URI

In the case of a TLD file within the Web application

Path within the Web application
In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)
In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)
In the case of a TLD file within the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Format of the path ee....ee of the TLD file with invalid mapping from the URI

For J2EE Server

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)
In the case of the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Specify a value in the <uri> tag of the TLD file so that it is not the same as the contents defined in web.xml, and another TLD file.

Correct the error, and then update the J2EE application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39327-E

A given class must not have more than one method annotated with aa....aa. (J2EE application = bb....bb, context root = cc....cc, class = dd....dd)

aa....aa: "PostConstruct" or "PreDestroy"

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Class name

Description: The provided class cannot have more than one method annotated with PostConstruct or PreDestroy.
Action: Revise the J2EE application according to the Java EE specifications.

KDJE39328-E

A method annotated with aa....aa must not have any parameters. (J2EE application = bb....bb, context root = cc....cc, class = dd....dd, method = ee....ee)

aa....aa: "PostConstruct" or "PreDestroy"

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Class name

ee....ee: Method name

Description: A method annotated with PostConstruct or PreDestroy must not have any arguments.
Action: Revise the J2EE application according to the Java EE specifications.

KDJE39329-W

A method annotated with aa....aa must not throw checked exceptions. (J2EE application = bb....bb, context root = cc....cc, class = dd....dd, method = ee....ee)

aa....aa: "PostConstruct" or "PreDestroy"

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Class name

ee....ee: Method name

Description

A method annotated with PostConstruct or PreDestroy cannot throw inspected exceptions.

The method will operate, but will not conform to the Java EE specifications.

A method for which a warning is reported might be defined in web.xml. In such a case, the method is defined in the <post-construct> tag if aa....aa is PostConstruct, and in the <pre-destroy> tag if aa....aa is PreDestroy.

Action

Revise the J2EE application according to the Java EE specifications.

KDJE39330-W

A method annotated with aa....aa must not be declared as static. (J2EE application = bb....bb, context root = cc....cc, class = dd....dd, method = ee....ee)

aa....aa: "PostConstruct" or "PreDestroy"

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Class name

ee....ee: Method name

Description

A method annotated with PostConstruct or PreDestroy cannot be declared as static.

The method will operate, but will not conform to the Java EE specifications.

A method for which a warning is reported might be defined in web.xml. In such a case, the method is defined in the <post-construct> tag if aa....aa is PostConstruct, and in the <pre-destroy> tag if aa....aa is PreDestroy.

Action

Revise the J2EE application according to the Java EE specifications.

KDJE39331-W

The return type of a method annotated with aa....aa must be void. (J2EE application = bb....bb, context root = cc....cc, class = dd....dd, method = ee....ee)

aa....aa: "PostConstruct" or "PreDestroy"

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Class name

ee....ee: Method name

Description

The return-value type of a method annotated with PostConstruct or PreDestroy must be void.

The method will operate, but will not conform to the Java EE specifications.

A method for which a warning is reported might be defined in web.xml. In such a case, the method is defined in the <post-construct> tag if aa....aa is PostConstruct, and in the <pre-destroy> tag if aa....aa is PreDestroy.

Action

Revise the J2EE application according to the Java EE specifications.

KDJE39332-E

The specified value for the aa....aa tag in the web.xml is invalid. (J2EE application = bb....bb, context root = cc....cc, class = dd....dd, method = ee....ee)

aa....aa: "post-construct" or "pre-destroy"

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Class name specified in web.xml

ee....ee: Method name specified in web.xml

Description

The value specified in the <post-construct> tag, or <pre-destroy> tag of the Deployment Descriptor is invalid.

Take action based on the following causes:

The class specified in the <lifecycle-callback-class> tag does not exist.
The method specified in the <lifecycle-callback-method> tag does not exist. Alternatively, the method exists, but it contains arguments.

Action

Revise the definition of web.xml, or the J2EE application.

KDJE39333-W

The number of lines in the method used to process a custom tag exceeded 1000. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, tag = dd....dd, number of lines = ee....ee)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of the concerned JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format: 'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: Custom tag name

ee....ee: Number of lines including the blank lines and comment lines of the method for processing the generated tag file

Description

In the case of the J2EE server mode or the cjjspc command: The number of lines of the method for processing the custom tag in the JSP file or tag file has exceeded 1000, including the comments and blank lines.
In the case of the servlet engine mode or the cjjsp2java command: The number of lines of the custom tag processing method coded in the JSP file has exceeded 1000, including the comments and blank lines.

Action

From the specifications of the Java virtual machine, the byte code of one method needs to be within 64 kilobytes. If the byte code of a method exceeds 64 kilobytes, it will result in an error during the generation of class file, or the exception java.lang.LinkageError will occur when the class is loaded.

If the size of one method is within 64 kilobytes, but is still extremely large, the following adverse effects might occur:

A lot of time would be taken for GC processing.
A lot of time would be taken for JIT compilation.
A lot of memory would be consumed for JIT compilation.

As a result, the size of one method on the Java source is recommended to be within 500 lines, excluding comments and blank lines.

The number of lines of the Java code generated from the custom tag can be reduced by splitting the custom tag using dynamic include (include action).

KDJE39334-I

The version of the class file that was compiled from a JSP file or a tag file is different from the current version of the web application. As a result, the JSP file or tag file will be recompiled. (J2EE application = aa....aa, context root = bb....bb, web application version = cc....cc, file = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Version of the Web application to be executed

dd....dd: Path of the JSP file or the tag file in the Web application

Description

The version of the class file created by compiling the JSP file or the tag file differs from the current version.

Recompile the JSP file or the tag file.

KDJE39335-I

The web application version was changed. (J2EE application = aa....aa, context root = bb....bb, web.xml version = cc....cc, web application version = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: web.xml version

dd....dd: Version of the Web application to be executed

Description: The version of the Web application is changed.

KDJE39336-E

The POST form data has exceeded the maximum size. (request URI = aa....aa, size of the post form data = bb....bb, max size of the post form data = cc....cc)

aa....aa: Request URI

bb....bb: Size of POST form data

cc....cc: Maximum size of the POST form data

Description

The form data of the POST request sent by the client exceeds the maximum size.

If the value of the Content-Type header is application/x-www-form-urlencoded

If the Content-Length header exists

An error with status code 413 is returned to the client.
If the Content-Length header does not exist and the value of the Transfer-Encoding header is chunked

The java.lang.IllegalStateException exception is thrown because of the extension of the Servlet API invocation. The POST form data size read as the parameter is output to bb....bb.

If the value of the Content-Type header is multipart/form-data

The java.lang.IllegalStateException exception is thrown because of the extension of the Servlet API invocation. The POST form data size read as the parameter is output to bb....bb.

Action

Check whether the form data size of the POST request sent by the client is the assumed size of the Web application. If the form data has the assumed size, change the specified value of the webserver.connector.limit.max_post_form_data key of the user properties file (maximum size of the form data of the POST request) with an appropriate value. If the maximum form data size of the POST request is changed, you must restart the J2EE server or the Web container server.

KDJE39338-E

The name of the HTTP cookie showing the HTTP session ID is invalid. (J2EE application = aa....aa, context root = bb....bb, session tracking cookie name = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP Cookie name indicating the HTTP session ID

Description: The name of the HTTP Cookie indicating the HTTP session ID is invalid. The HTTP Cookie name indicating the HTTP session ID specified in the web.xml file or Servlet API is duplicated with the Cookie name specified in the functionality for adding the server ID in a Cookie.
Action: Change either the HTTP Cookie name indicating the HTTP session ID or the Cookie name specified in the functionality for adding the server ID in a Cookie, so that the names are not duplicated.

KDJE39339-E

No servlet class has been specified. (J2EE application = aa....aa, context root name = bb....bb, servlet name = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Servlet name

Description: The servlet cannot be executed because no servlet class has been specified.
Action: Specify the servlet class in the <servlet-class> element of the web.xml file.

KDJE39340-E

No filter class has been specified. (J2EE application = aa....aa, context root name = bb....bb, filter name = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Filter name

Description: The filter cannot be executed because no filter class has been specified.
Action: Specify the filter class in the <filter-class> element of the web.xml file.

KDJE39341-W

The request parameter count exceeded the maximum number. (J2EE application = aa....aa, context root = bb....bb, request URI = cc....cc, max parameter count = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URI

dd....dd: Maximum request parameter count

Description: The number of request parameters sent by the client exceeded the maximum number.
Action: Check whether the number of request parameters sent by the client exceeds the value (maximum request parameter count) set in the webserver.connector.limit.max_parameter_count key of the user property file. If the number of parameters used exceeds the maximum request parameter count, change the maximum request parameter count to an appropriate value. If you change the maximum request parameter count, you must restart the J2EE server or the Web Container server.

KDJE39342-E

The request parameter count exceeded the maximum number. (J2EE application = aa....aa, context root = bb....bb, request URI = cc....cc, max parameter count = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URI

dd....dd: Maximum request parameter count

Description: The acquisition of the Part objects was interrupted because the number of parameters included in the POST data of the multipart/form-data request sent by the client exceeded the maximum number.
Action: Check whether the number of parameters included in the POST data of the multipart/form-data request sent by the client exceeds the value (maximum request parameter count) set in the webserver.connector.limit.max_parameter_count key of the user property file. If the number of parameters used exceeds the maximum request parameter count, change the maximum request parameter count to an appropriate value. If you change the maximum request parameter count, you must restart the J2EE server or the Web Container server.

KDJE39400-W

The format form exceeded 1024 characters. The default value will be used.(aa....aa = bb....bb , default value = cc....cc)

aa....aa: Property name

bb....bb: Property value

cc....cc: Default value of property

Description

The format form exceeds 1024 characters. The default value will be used.(aa....aa = bb....bb, Default value = cc....cc)

Action

The character string specified for the property value contains more than 1024 characters.

Reduce the number of characters to be specified.

KDJE39401-W

An undefined format argument is specified. The default value will be used. (property = aa....aa, default value = bb....bb)

aa....aa: Property name

bb....bb: Default value of property

Description

An undefined format argument is specified. The default value will be used.

Action

An undefined format argument is specified.

Specify the defined format argument.

KDJE39402-W

AccessLog is unavailable due. (reason = aa....aa)

aa....aa: Detailed exception message

Description

The access log cannot be used.

Action

One of the following problems has occurred in the access log function of HTTP or WebSocket. Take action depending on the problem.

Permission is not available for the file.

Set appropriate access permissions.
Either the system resources are insufficient or the file system has failed.

Specify the usage status of the system resources of the OS, as well as any problems in the file system, and then take action.

KDJE39500-E

An attempt to deploy the web application failed because the number of shared threads set for deployed web applications is less than one.

Description

An attempt to deploy the Web application has failed.

The setting of concurrently executing number of threads for each Web application is invalid.

Deployment has failed because the number of shared threads for each Web application is less than one.

The number of shared threads for each Web application needs to be one or more.

Action

Set the number of shared threads for each Web application as one or more.

To increase the number of shared threads for each Web application, reduce the number of dedicated threads for each deployed Web application.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

KDJE39501-E

An attempt to deploy the web application failed because the number of shared threads set for web applications to be deployed is less than one. (J2EE application = aa....aa, context root list = bb....bb)

aa....aa: J2EE application name

bb....bb: List of context root of the Web application in which the number of shared threads in each Web application is less than one

Description

An attempt to deploy the Web application has failed.

Either the setting of concurrently executing number of threads for each Web application or the setting of concurrently executing number of threads in each URL group is invalid.

Deployment has failed because the number of shared threads for each Web application is less than one.

The number of shared threads for each Web application needs to be one or more.

Action

Set the number of shared threads for each Web application as one or more. If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

To increase the number of shared threads for each Web application, execute one of the following operations:

Increase the number of shared threads for each Web application with a context root name that is not displayed in the message.
Reduce the number of dedicated threads in each URL group for a Web application with a context root name that is displayed in the message.

KDJE39502-E

An attempt to dynamically change the web application failed because the number of shared threads set for deployed web applications is less than one.

Description

An attempt to dynamically change the settings to control the number of concurrently executing threads of Web application has failed.

The setting of concurrently executing number of threads for each Web application is invalid.

Deployment has failed because the number of shared threads for each Web application is less than one.

The number of shared threads for each Web application needs to be one or more.

Action

Revise the specified maximum number of concurrently executing threads and the number of dedicated threads of the Web application.

To increase the number of dedicated threads of the Web application after changing the settings, the number of shared threads for each Web application needs to be one or more.

KDJE39503-W

The max threads limit of the URL group thread control set to the max threads limit of the web application thread control, because the web application was dynamically changed. (J2EE application = aa....aa, context root = bb....bb, URL group thread control name = cc....cc, max threads = dd....dd, exclusive threads = ee....ee, a number of processing requests = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Definition name for each URL group

dd....dd: Maximum number of concurrently executing threads for each URL group

ee....ee: Number of dedicated threads for each URL group

ff....ff: Number of current processing requests for each URL group

Description: The maximum number of concurrently executing threads at the URL group level is set to the maximum number of concurrently executing threads of the Web application level, because the Web application has changed dynamically.
Action: To operate the maximum number of concurrently executing threads at the URL group level with the set value, set the maximum number of concurrently executing threads of the Web application to a value greater than the maximum number of concurrently executing threads at the URL group level by dynamically changing the Web application.

KDJE39504-I

The max threads limit of the URL group thread control set to the set value, because the web application was dynamically changed. (J2EE application = aa....aa, context root = bb....bb, URL group thread control name = cc....cc, max threads = dd....dd, exclusive threads = ee....ee, a number of processing requests = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Definition name for each URL group

dd....dd: Maximum number of concurrently executing threads for each URL group

ee....ee: Number of dedicated threads for each URL group

ff....ff: Number of current processing requests for each URL group

Description: The maximum number of concurrently executing threads at the URL group level will operate at the set value because the Web application has changed dynamically.

KDJE39505-W

The exclusive threads for a URL group set for this web application cannot be used because the Web application was dynamically changed. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The number of dedicated threads at the URL group level specified in this Web application cannot be used because the Web application was changed dynamically.
Action: To use the number of dedicated threads at the URL group level, set the number of dedicated threads of the Web application to a value greater than the total number of dedicated threads at the URL group level by dynamically changing the Web application. When increasing the number of dedicated threads by dynamically changing the Web application, set the number of shared threads at the Web application level as one or more.

KDJE39506-I

The exclusive threads for a URL group set for this web application can be used because the Web application was dynamically changed. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The number of dedicated threads at the URL group level specified in this Web application can be used because the Web application was changed dynamically.

KDJE39507-E

The timeout occurred in sending the response data to the redirector. (redirector = aa....aa : bb....bb, container = cc....cc : dd....dd)

aa....aa: IP address of the connection destination redirector

bb....bb: Port number of the connection destination redirector

cc....cc: IP address of the container

dd....dd: Port number of the container

Description

A timeout occurred while a response was being sent to the redirector.

Action

Confirm the following details:

the Web server is running properly.
no problem exists in the communication path between the Web server and the Web container.

KDJE39508-I

JSP precompilation has finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description: JSP precompilation has finished.

KDJE39510-E

The JSP work directory cannot be accessed. (J2EE application = aa....aa, context root = bb....bb, directory = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the JSP work directory

Description

The JSP work directory cannot be accessed.

Action

One of the following problems occurred. Take action depending on the problem.

Permission is not available to access the directory.
The file system has failed.

KDJE39511-W

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

aa....aa: Property name

bb....bb: Property value

cc....cc: Default value

Description: A reserved property value is specified. The default value will be used.
Action: The value specified in the JSP work directory is not case-sensitive, and lib, tags, or classes cannot be used. Check the set value of the key webserver.jsp.precompile.jsp_work_dir of the user property file, and then restart the J2EE server.

KDJE39512-I

The JSP precompilation function is enabled. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The JSP pre-compile functionality is enabled.

KDJE39513-I

The max threads limit of the URL group thread control is set to aa....aa. (J2EE application = bb....bb, context root = cc....cc, URL group thread control name = dd....dd, the configuration of max threads = ee....ee, a number of processing requests = ff....ff)

aa....aa: Context root name

bb....bb: Maximum number of concurrently executing threads for each URL group

cc....cc: J2EE application name

dd....dd: Context root name

ee....ee: Definition name for each URL group

ff....ff: Set value of the maximum number of concurrently executing threads for each URL group

Description

The maximum number of concurrently executing threads at the URL group level of the context root aa....aa has become (bb....bb).

Depending on the upper limit of the set value, the maximum number of concurrently executing threads at the URL group level might depend on the settings of this Web application or the settings of other Web applications, and therefore, the number might be reduced.

If the number of currently executing requests exceeds the maximum number of concurrently executing threads, the requests will be controlled at the current upper-limit value, after the processing of running requests finishes.

KDJE39515-I

The setting used to URL group thread control will now be applied to the web application to be deployed. (J2EE application = aa....aa, context root = bb....bb, URL group thread control name = cc....cc, max threads = dd....dd, exclusive threads = ee....ee, queue size = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Definition name for each URL group

dd....dd: Maximum number of concurrently executing threads for each URL group

ee....ee: Number of dedicated threads for each URL group

ff....ff: Size of the pending queue for each URL group

Description: The setting for controlling the concurrently executing number of threads at the URL group level will be applied to the Web application to be deployed.

KDJE39516-W

The URL pattern bb....bb does not match the definition name aa....aa of a URL group. (J2EE application = cc....cc, context root = dd....dd, URL group thread control name = ee....ee)

aa....aa: Definition name for each URL group

bb....bb: URL pattern

cc....cc: J2EE application name

dd....dd: Context root name

ee....ee: Definition name for each URL group

Description

The URL pattern bb....bb was not mapped to the definition name aa....aa of the URL group level.

Action

The URL mapping will not be performed for the specified URL pattern.

Revise the setting for control of the concurrently executing number of threads at the URL group level.

KDJE39517-E

An attempt to create the JSP work directory has failed. (J2EE application = aa....aa, context root = bb....bb, directory = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the JSP work directory

Description

An attempt to create the JSP work directory has failed.

Action

One of the following problems occurred. Take action depending on the problem.

Permission is not available to access the directory.
The available disk space is insufficient.
The file system has failed.
A file exists with the same name as the JSP work directory.

KDJE39518-E

The java source file to be compiled was not found. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the Java source file

Description

The Java source file translated from the JSP to be compiled was not found.

Action

Permission might not be available to access the file.

Set the appropriate access permissions.

KDJE39519-E

The web.xml was not be found. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description

The file web.xml was not found.

Action

A Web application that does not contain WEB-INF/web.xml might be deployed, the corresponding web.xml might not exists in the deploy destination directory of the Web application, or access permissions might not be available.

Set WEB-INF/web.xml to a state that it can be read.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-execute the command.

KDJE39520-E

An error occurred in while reading web.xml. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description

An error occurred while web.xml was being read.

Action

One of the following problems occurred. Take action depending on the problem.

File read permission is not available.
The file system has failed.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

If the cjjspc command is executed and this message is output, re-execute the cjjspc command.

KDJE39521-E

An error occurred while analyzing web.xml at line aa....aa. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Line number

bb....bb: J2EE application name (a null character string in the case of the cjjspc command)

cc....cc: Context root name (a null character string in the case of the cjjspc command)

Description

An error occurred while analyzing web.xml.

Action

Modify the location shown in the line number of web.xml.

If the format or contents of XML are invalid, the message KDJE39308-Ewill be output in the Web servlet log. When message KDJE39308-E is output, modify web.xml on the basis of the detailed information.

If the specified order of the tag does not match the schema definition of XML, the line number of the end tag that includes this tag will be output. As a result, make sure that the specified order of the tag shown in the line number matches the schema definition of XML.

web.xml is re-written in the J2EE server, when the J2EE server imports and deploys an application. The line number uses the line number after web.xml is re-written, therefore, for the error location, check the web.xml of this Web application present below the application directory, when the expanded archive format is used. When deployment is performed in the archive format, check web.xml included in the exported EAR file.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

If the cjjspc command is executed, re-execute the command.

KDJE39522-E

The class file generated from the JSP file or the tag file cannot be used because its version is invalid. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description

The class file generated by compiling the JSP file or the tag file cannot be used because its version is invalid.

Action

If using the Web application version change functionality, check that the -lowerversion option of the cjjspc command and the webserver.application.lower_version key of the J2EE server have the same values. If the settings are different, recompile to match the -lowerversion option of the cjjspc command with the J2EE server settings or match the webserver.application.lower_version key of the J2EE server with the settings of the -lowerversion option of the cjjspc command, and then restart the J2EE server. If the Web application version change functionality is not used, all the class files generated from the JSP present in the application need to be re-compiled.

If this message is output when the application is started, execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-compile the entire Web application, without specifying the -excludefile and -excludelist options, and the JSP single file.

KDJE39523-E

JSP precompilation at application startup cannot be executed because the JSP precompilation function is disable. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The JSP pre-compile functionality used during application startup cannot be used because the JSP pre-compile functionality is invalid.
Action: If the J2EE server startup mode is the basic mode, the JSP pre-compile functionality cannot be used. Check the set value of the key ejbserver.server.j2ee.feature of the user property file.

KDJE39524-W

The JSP precompilation function is disable. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: The JSP pre-compile functionality is invalid.
Action: If the J2EE server startup mode is the basic mode, the JSP pre-compile functionality cannot be used. Check the set value of the key ejbserver.server.j2ee.feature of the user property file.

KDJE39525-E

JSP precompilation has failed. Application startup will now stop. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description: JSP pre-compilation has failed. Application invocation will stop.
Action: Check the error message output just before this message, and then take action.

KDJE39526-E

An attempt to read the version information file has failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the version information file

Description

An attempt to read the version information file has failed.

Action

One of the following problems occurred. Take action depending on the problem.

Permission is not available to access the file.
The file system has failed.

If this message is output when the application is started, execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-compile the entire Web application, without specifying the -excludefile and -excludelist options, and the JSP single file.

KDJE39527-E

An attempt to create the version information file has failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the version information file

Description

An attempt to create the version information file has failed.

Action

One of the following problems occurred. Take action depending on the problem.

Permission is not available to access the file.
The available disk space is insufficient.
The file system has failed.

If the JSP pre-compile functionality used during application startup is executed, re-execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-compile the entire Web application, without specifying the -excludefile and -excludelist options, and the JSP single file.

KDJE39528-I

JSP precompilation will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description: JSP pre-compilation is started.

KDJE39529-W

A directory could not be accessed during a search for a JSP file. (J2EE application = aa....aa, context root = bb....bb, directory = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the directory that cannot be accessed

Description

A directory cannot be accessed while searching for a JSP file. The JSP files of this directory will not be compiled, and then the processing continues.

Action

One of the following problems occurred. Confirm if action needs to be taken, and if it is to be taken, it will depend on the occurred problem. If there are some files that need to be compiled, re-execute JSP pre-compile.

Permission is not available to access the file.
The file system has failed.

KDJE39530-E

An unexpected error occurred. (J2EE application = aa....aa, context root = bb....bb, message = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Exception message

Description

An unexpected exception occurred.

Action

From the exception message, check whether any problem exists.

If no problem exists, contact maintenance personnel.

KDJE39531-E

The contents of the version information file are invalid. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the version information file

Description

The contents of the version information file are invalid. Either the version information file is corrupt or contains invalid strings.

Action

If this message is output when the application is started, execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-compile the entire Web application, without specifying the -excludefile and -excludelist options, and the JSP single file.

KDJE39532-W

The url-pattern element in web.xml contains the carriage return or line feed character. (J2EE application = aa....aa, context root = bb....bb, element body = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Contents specified in the element <url-pattern>

Description

The linefeed code (CR(#xD) or LF(#xA)) is included in the contents of the element <url-pattern> defined in web.xml. You cannot include the linefeed code in the contents specified in the element <url-pattern>. The definition specified by this element will be disabled. The contents of cc....cc will be displayed without linefeed code.

Action

Modify the contents of the corresponding element, and then redeploy the application. If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

If the cjjspc command is executed, re-execute the command.

KDJE39533-E

The version information file does not exist. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description

The JSP work directory exists, but the version information file is not present below the JSP work directory.

Action

If this message is output when the application is started, re-execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-compile the entire Web application, without specifying the -excludefile and -excludelist options, and the JSP single file.

Note that in Windows, this message is output even when there are no access permissions.

KDJE39534-E

An error occurred during Dependency Injection. Initialization of the web application will be stopped. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

An error occurred in the processing of the Dependency Injection.

Initialization of the web application will stop.

Action

An error message of the processing of the Dependency Injection is output to the message log just before this message. Check, and then take action.

Correct the error location, and then redeploy.

KDJE39535-E

An attempt to create the lock file has failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the lock file

Description

An error occurred while the lock file was being created.

Action

One of the following problems occurred. Take action depending on the problem.

Permission is not available to access the JSP work directory.
Permission is not available to access the lock file.
The available disk space is insufficient.
The file system has failed.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-compile the entire Web application, without specifying the -excludefile and -excludelist options, and the JSP single file.

KDJE39536-E

JSP precompilation is being executed. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description: The JSP pre-compile functionality used during application startup or the cjjspc command is being executed.
Action: After the JSP pre-compile functionality being executed finishes, re-execute JSP pre-compilation.

KDJE39537-W

An attempt to delete the lock file has failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the lock file

Description

An attempt to delete the lock file has failed.

Action

One of the following problems occurred.

JSP pre-compilation is already being executed in another process.
File deletion permission is not available.
The file is open.
The file system has failed.

There is no problem if JSP pre-compilation is already being executed in another process. If this message is output without any concern as to whether the JSP pre-compilation is being executed elsewhere, take action depending on the problem.

KDJE39538-E

An attempt to delete a java source file generated from the JSP file or the tag file has failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the Java source file generated from the JSP file or the tag file

Description

An error occurred while the Java source file (aa....aa) generated during the compilation of the JSP file or the tag file was being deleted.

Action

Take action for the cause of the error that occurred while the Java source file, generated during the compilation of the JSP file or the tag file was being deleted. Re-execute JSP pre-compilation.

The possible causes of error are as follows:

File deletion permission is not available.
The file is open.
The file system has failed.

KDJE39539-W

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

aa....aa: Property name for which an invalid value is set

bb....bb: Invalid value

cc....cc: Default property name

dd....dd: Set value

Description

The value bb....bb set in the property (aa....aa) is invalid.

The value (dd....dd) set in the default property (cc....cc) will be used. If a value is not specified in the default property, the default value of the default property will be used.

Action

When changing the property aa....aa from the value set in the default property, modify the property value of aa....aa, and then either stop or restart the Web container server or the J2EE server.

KDJE39540-I

aa....aa JSP files will be compiled. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Number of JSP files to be compiled

bb....bb: J2EE application name (a null character string in the case of the cjjspc command)

cc....cc: Context root name (a null character string in the case of the cjjspc command)

Description: The number of JSP files to be compiled will be displayed.

KDJE39541-I

JSP file does not exists. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description: There are no JSP files to be compiled.

KDJE39542-E

An exception was raised in executing the request to the static content. (request URL = aa....aa, exception = bb....bb, detail = cc....cc)

aa....aa: Request URL

bb....bb: Exception name

cc....cc: Detailed exception message

Description

An error occurred in a request to the static contents.

The possible causes of error are as follows:

The static contents have been deleted.
The OS resources have been consumed and the static contents cannot be opened.
The contents cannot be accessed because permission is not available for the file.
The file system has failed.

Action

One of the following problems occurred. Take action depending on the problem.

The static contents have been deleted.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

Permission is not available to access the static contents.

Set appropriate access permissions.
Either the system resources are insufficient or the file system has failed.

Specify the usage status of the system resources of the OS, as well as any problems in the file system, and then take action.

KDJE39543-E

An unexpected exception was raised in the web application reload processing. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc, detail = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Exception name

dd....dd: Detailed exception message

Description

An unexpected exception occurred in the reload processing of the Web application.

Action

If exception java.lang.OutOfMemoryError occurs, the memory is insufficient. Increase the memory that can be used by the system, and then restart the J2EE server or the Web container server.

If other than exception java.lang.OutOfMemoryError occurs, Acquire the maintenance information, and then contact maintenance personnel.

KDJE39544-I

The id attribute of a useBean action has been specified more than once. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc(dd....dd,ee....ee), id = ff....ff)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Path within the Web application of the JSP file

dd....dd: Number of lines of the useBean action in the JSP file

ee....ee: Column of the useBean action in the JSP file

ff....ff: id attribute name of the useBean action

Description: The id attribute of the useBean action is duplicate.

KDJE39546-W

Invalid locale was detected in the Accept-Language header. This locale was ignored. (request uri = aa....aa, locale = bb....bb)

aa....aa: Request URI

bb....bb: Invalid locale

Description: An invalid locale was detected in the Accept-Language header. The invalid locale will be ignored.

KDJE39547-E

There is a problem in the JAX-WS settings. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

A problem exists in the settings of JAX-WS.

Action

Initialization of the web application will stop.

See the JAX-WS document and revise the following settings. Next, execute the deployment process again.

webserver.container.jaxws.webservice.no_webxml.enabled property
webserver.container.jaxws.webservice.wsee.no_webxml.enabled property
Settings of the JAX-WS library of usrconf.cfg

KDJE39548-E

Processing of a JAR file failed during the scanning of a aa....aa. (JAR file = bb....bb, context root = cc....cc, message = dd....dd)

aa....aa: Static Resource or ServletContainerInitializer

bb....bb: JAR file path

cc....cc: Context root name

dd....dd: Exception message

Description: The processing of a JAR file failed while searching the implementation class of a static resource or ServletContainerInitializer.
Action: Check whether the specified JAR file is corrupted and whether the implementation class of the static resource or ServletContainerInitializer can be read.

KDJE39549-W

While searching for a class that extends or implements a class specified in the HandlesTypes annotation, or a class that has the annotation specified in the HandlesTypes annotation, the class or another class failed to load. (class name = aa....aa, message = bb....bb)

aa....aa: Class name

bb....bb: Exception message

Description: While searching for a class that extends or implements the class specified in the HandlesTypes annotation of the ServletContainerInitializer interface, or a class that has the annotation specified in the HandlesTypes annotation, the class failed to load. This class is ignored.
Action: Check whether the applicable class or the class required for loading that class is included in the Web application.

KDJE39550-E

Static content cannot be scanned because the syntax of the specified JAR file is invalid. (JAR file = aa....aa, context root = bb....bb)

aa....aa: JAR file path

bb....bb: Context root name

Description: The static contents cannot be searched because the configuration of the specified JAR file is incorrect.
Action: Check whether the JAR file has been created correctly.

KDJE39551-W

Processing of a JAR file that includes static content failed. (JAR file = aa....aa, message = bb....bb)

aa....aa: JAR file path

bb....bb: Exception message

Description: An attempt to process a JAR file including static content failed.
Action: Check whether the JAR file has been created correctly.

KDJE39552-W

A aa....aa cannot be added because it is already registered. The aa....aa will be ignored. (aa....aa name = bb....bb, context root = cc....cc)

aa....aa: Servlet or filter

bb....bb: Servlet name or filter name

cc....cc: Context root name

Description: The servlet or filter cannot be added because it is already registered. This servlet or filter is ignored.
Action: Check whether the servlet or filter has already been registered with the same name.

KDJE39553-W

The specified JAR file, which contains a ServletContainerInitializer interface class, was not found in the list of include files. (file = aa....aa)

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

Description: The JAR file for ServletContainerInitializer specified in the include file list was not found.
Action: Check whether the JAR file exists in the specified path. If the file does not exist, store the JAR file.

KDJE39554-W

The specified JAR file, which contains a ServletContainerInitializer interface class, was not found at the class path. (file = aa....aa)

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

Description: The JAR file for ServletContainerInitializer specified in the include file list was not found in the class path.
Action: Check whether the JAR file exists in the class path.

KDJE39555-W

The url pattern contains the carriage return or line feed character. (J2EE application = aa....aa, context root = bb....bb, urlPattern = cc....cc)

aa....aa: J2EE application

bb....bb: Context root

cc....cc: Value specified for the URL pattern

Description

The value specified in the URL pattern for the dynamic servlet definition contains a linefeed code (CR(#xD), or LF(#xA)). The contents specified in the URL pattern cannot contain a linefeed code.

This definition is invalid.

The cc....cc contents display the value excluding the linefeed code.

Action

Correct the contents of the applicable URL pattern, and then re-deploy the application.

KDJE39556-W

This application contains a JAR file with static content in the META-INF/resources directory. The static content was not reloaded. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application

bb....bb: Context root

Description: When the application contains a JAR file with static contents (including JSP) in META-INF/resources, even if the JAR file is updated and reloaded, the static contents included in the META-INF/resources of the JAR file can only access the pre-update JAR file.
Action: To update the static contents in the META-INF/resources of the JAR file, first stop and then re-deploy the application.

KDJE39557-W

This application includes a class that implements the ServletContainerInitializer interface. The reload function is not supported for this application. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application

bb....bb: Context root

Description: The reload functionality is not supported for applications containing the implementation class of the ServletContainerInitializer interface. The J2EE server operations might not function normally if the applications are reloaded. Do not reload the applications.
Action: Stop and then restart the J2EE server.
Note: This message is not output with the version 09-00-02 or later.

KDJE39558-W

This application includes servlet, filter, or listener classes added by the program. The reload function is not supported for this application. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application

bb....bb: Context root

Description: The reload functionality is not supported for applications containing the Servlet, Filter, or Listener classes added by the dynamic servlet definition. The J2EE server operations might not function normally if the applications are reloaded. Do not reload the applications.
Action: Stop and then restart the J2EE server.
Note: This message is not output with the version 09-00-02 or later.

KDJE39559-W

An invalid character is used for configuring SessionCookieConfig. This configuration may cause improper behavior for session. (aa....aa = bb....bb)

aa....aa: Set item

bb....bb: Set value

Description: An invalid character is used in the SessionCookieConfig settings. These settings might cause invalid session operations.
Action: Use the correct characters for the applicable items.

KDJE39560-I

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

aa....aa: Property name

bb....bb: Default value

Description: The property is not specified. The default value will be used.
Action: To change the aa....aa property from the default value, add the aa....aa property, specify the property value, and then stop or re-start the Web container server or the J2EE server.

KDJE39562-I

The nio http server started. (port = aa....aa)

aa....aa: Port number

Description: The nio http server will start.

KDJE39563-W

The host name specified in the property webserver.connector.nio_http.permitted.hosts could not be resolved. (host name = aa....aa)

aa....aa: Host name that cannot be resolved

Description

The host name specified in webserver.connector.nio_http.permitted.hosts cannot be resolved.

Allow access only from the local host, and then start.

Action

Make sure that the specified host name can be resolved, and then restart the server.

KDJE39564-W

Access to the nio http server from a forbidden host was rejected. (IP address = aa....aa)

aa....aa: IP address of the host that was denied access

Description: Access to the nio http server from a forbidden host was denied.
Action: To allow access from a forbidden host, specify the IP address or the host name of the host that is allowed access in the property webserver.connector.nio_http.permitted.hosts, and then restart the server.

KDJE39565-W

The host name specified in property webserver.connector.nio_http.bind_host could not be resolved. (host name = aa....aa)

aa....aa: Specified host name

Description

The host (aa....aa) specified in the property webserver.connector.nio_http.bind_host cannot be resolved.

The wild card address will be used.

Action

When using an address other than the wild card address, specify the resolvable local host name or the IP address of the local host, and then restart the server.

KDJE39566-E

The nio http server on port aa....aa could not be started.

aa....aa: Port number

Description

The nio http server cannot be started on the specified port number (aa....aa).

Action

Another process might be using the specified port number of the nio http server. Specify a port number that is not in use by another process, and then restart the server. The port number of the nio http server can be specified in the key webserver.connector.nio_http.port of the user property file.

If not specified in the user property file, use the port number 8008 as the default value.

KDJE39567-W

The host specified in property webserver.connector.nio_http.bind_host could not be bound. (host = aa....aa)

aa....aa: Specified host name

Description

The host (aa....aa) specified in the property webserver.connector.nio_http.bind_host cannot be resolved.

The wild card address will be used.

Action

A host other than the local host might be specified.

When using an address other than the wild card address, specify the correct host, and then restart the server.

KDJE39568-E

The request header is exceeds the max size. (request uri = aa....aa, max size of the request header = bb....bb)

aa....aa: Request URI

bb....bb: Maximum size of the request header

Description: The request header of the sent request has exceeded the maximum size. An error with status 400 will be returned to the client.
Action: Check if the set value of the key webserver.connector.nio_http.limit.max_request_header of the user property file is correct. If the set value is incorrect, change the maximum size of the request header to the correct value. When the maximum size of the request header is changed, you need to restart the J2EE server.

KDJE39569-E

The request body is exceeds the max size. (request uri = aa....aa, max size of the request body = bb....bb)

aa....aa: Request URL

bb....bb: Maximum size of the request body

Description: The request body of the sent request has exceeded the maximum size. If the transfer encoding for the sent request is not chunked, an error with status 413 will be returned to the client.
Action: Check if the set value of the key webserver.connector.nio_http.limit.max_request_body of the user property file is correct. If the set value is incorrect, change the maximum size of the request body to the correct value. When the maximum size of the request body is changed, you need to restart the J2EE server.

KDJE39570-E

The http header is exceeds the max number. (request uri = aa....aa, max number of the http header = bb....bb)

aa....aa: Request URI

bb....bb: Maximum number of HTTP headers

Description: The number of HTTP headers included in the sent request has exceeded the maximum number. An error with status 400 will be returned to the client.
Action: Check if the set value of the key webserver.connector.nio_http.limit.max_headers of the user property file is correct. If the set value is incorrect, change the maximum number of HTTP headers to the correct value. When the maximum number of HTTP headers is changed, you need to restart the J2EE server.

KDJE39571-W

The nio http server denies access to the URI starting with /ejb/ or /web/. (request URI = aa....aa)

aa....aa: Request URI

Description

The accessed request was denied.

A request starting with ""/ejb/"" or ""/web/"" cannot be used on the NIO HTTP server.

KDJE39572-E

An exception was raised during connecting with the client. (exception = aa....aa)

aa....aa: Exception information notified from Java VM in the case of failure in establishing a connection with the client

Description

An exception occurred while establishing a connection with the client. This might be due to the occurrence of a problem that does not allow continuance of an operation, such as lack of resources of the system in which the Web container is running.

If message KDJE39573-W is output after this message, and if the connection from the client is successful after the occurrence of the failure notified by this message, the system might recover.

Even if no other error log is output, the system might not recover from this failure when this message KDJE39573-W is not output.

Action

From the J2EE server log, such as the access log of the nio http server, make sure that the request is being executed properly. In the case when the Web container does not receive the request, or an error occurs during the communication with the Web container, the system resources, such as memory, file descriptor, or the TCP port might be insufficient. Check the usage status of the system resources, and then make sure whether the estimation of the system resources is correct. If resources are insufficient, change the system settings.

KDJE39573-W

The connecting with the client has succeeded.

Description: An attempt to establish a connection with the client was successful, although an exception occurred while establishing connection with the client. This message is output after the message KDJE39572-E, when a connection with the client is established successfully. Message KDJE39572-E is output when a connection with the client cannot be established due to insufficient system resources, such as memory, file descriptor, or the TCP port.
Action: From the J2EE server log, such as the access log of the nio http server, make sure that the request is being executed properly. If the request is not being executed properly, identify the cause of the error and take action on the basis of the action for the message KDJE39572-E.

KDJE39574-E

The request header is invalid. The nio http server refused the request. (request uri = aa....aa, bb....bb = cc....cc, client = dd....dd: ee....ee)

aa....aa: Request URI

bb....bb: Name of the invalid request header

cc....cc: Value of the invalid request header

dd....dd: IP address of the client to which you will connect (IP address of the reverse proxy, if reverse proxy is being used)

ee....ee: Port number of the client to which you will connect (port number of the reverse proxy, if reverse proxy is being used)

Description: The nio http server has denied the accessed request because an invalid request header was received.
Action: Make sure whether no problem exists in the Web client that has sent the invalid request, and avoid sending invalid request headers.

KDJE39575-W

The timeout occurred during terminating the web container. Some processing threads may still be running. (thread pool = aa....aa, time = bb....bb seconds)

aa....aa: Name of the thread pool in which the timeout occurred

bb....bb: Timeout period

Description: A timeout occurred during termination of the Web container. Some processing threads might be still running.

KDJE39576-E

The timeout occurred in reading the request data from the client. (client = aa....aa: bb....bb)

aa....aa: IP address of the client to which you will connect (IP address of the reverse proxy, if reverse proxy is being used)

bb....bb: Port number of the client to which you will connect (port number of the reverse proxy, if reverse proxy is being used)

Description

A timeout occurred during reading of a request from the client. Confirm the following details:

If the proxy server is not being used

Make sure that no Web client has sent invalid data to the J2EE client.

Make sure that no failure has occurred in the communication path.
If the proxy server is being used

Make sure that the reverse proxy is running properly.

Make sure that no failure has occurred in the communication path between the reverse proxy and the J2EE server.

Action

Take the following action for the confirmed details:

If a Web client has sent invalid messages, identify the client based on the address and port number indicated in the message, and then take action.
If there is a problem in the communication path, resolve the problem.
If the reverse proxy is not running properly, resolve the problem of the reverse proxy.

KDJE39900-I

The response compression function will be applied. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

Description: The response compression functionality will be applied.

KDJE39901-I

The response compression rule aa....aa will be applied to the response of a request which matches the URL pattern bb....bb. (J2EE application = cc....cc, context root = dd....dd, compression rule name = ee....ee)

aa....aa: Response compression rule

bb....bb: URL pattern

cc....cc: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

dd....dd: Context root name

ee....ee: Response compression rule name

Description: The response compression rule aa....aa will be applied to the request that matches the URL pattern bb....bb.

KDJE39902-E

The URL pattern of the initialization parameter of the filter used for the response compression function is invalid. (J2EE application = aa....aa, context root = bb....bb, init param = cc....cc, url pattern = dd....dd)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Initialization parameter name

dd....dd: Specified URL pattern

Description: The URL pattern specified in the initialization parameter of the filter used for the response compression functionality is invalid.
Action: Modify the URL pattern specified in the initialization parameter of the filter used for the response compression functionality of the Deployment Descriptor (web.xml), and then redeploy.

KDJE39903-E

The compression rule name of the initialization parameter of the filter used for the response compression function is invalid. (J2EE application = aa....aa, context root = bb....bb, init param = cc....cc, compression rule name = dd....dd)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Initialization parameter name

dd....dd: Specified response compression rule name

Description: The response compression rule name specified in the initialization parameter of the filter used for the response compression functionality is invalid.
Action: Modify the response compression rule name specified in the initialization parameter of the filter used for the response compression functionality of the Deployment Descriptor (web.xml), and then redeploy.

KDJE39904-E

The compression rule name of the initialization parameter of the filter used for the response compression function is not found. (J2EE application = aa....aa, context root = bb....bb, init param = cc....cc, compression rule name = dd....dd)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Initialization parameter name

dd....dd: Specified response compression rule name

Description: The response compression rule name specified in the initialization parameter of the filter used for the response compression functionality is not found.
Action: Set the response compression rule name specified in the initialization parameter of the filter used for the response compression functionality of the Deployment Descriptor (web.xml), and then redeploy.

KDJE39905-E

The compression rule of the initialization parameter of the filter used for the response compression function is invalid. (J2EE application = aa....aa, context root = bb....bb, init param = cc....cc)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Initialization parameter name

Description: The response compression rule specified in the initialization parameter of the filter used for the response compression functionality is invalid.
Action: Modify the response compression rule specified in the initialization parameter of the filter used for the response compression functionality of the Deployment Descriptor (web.xml), and then redeploy.

KDJE39906-E

The compression threshold of the initialization parameter of the filter used for the response compression function is invalid. (J2EE application = aa....aa, context root = bb....bb, init param = cc....cc, compression threshold = dd....dd)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Initialization parameter name

dd....dd: Specified compression threshold value

Description: The response compression threshold value specified in the initialization parameter of the filter used for the response compression functionality is invalid.
Action: Modify the compression threshold value specified in the initialization parameter of the filter used for the response compression functionality of the Deployment Descriptor (web.xml), and then redeploy.

KDJE39907-W

The same media type has been specified more than once in the initialization parameters of the filter used for the response compression function. The compression threshold specified last will be applied. (J2EE application = aa....aa, context root = bb....bb, init param = cc....cc, media type = dd....dd, compression threshold = ee....ee)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Initialization parameter name

dd....dd: Specified media type

ee....ee: Applied compression threshold value

Description: The same media type is specified more than once in the initialization parameters of the filter used for the response compression functionality. The compression threshold value specified last will be applied.

KDJE39908-E

The url-mapping of the initialization parameter of the filter used for the response compression function is invalid. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

Description: The value of the url-mapping parameter specified in the initialization parameter of the filter used for the response compression functionality is invalid.
Action: Modify the value of the url-mapping specified in the initialization parameter of the filter used for the response compression functionality of the Deployment Descriptor (web.xml)and then redeploy.

KDJE39909-E

An error occurred in acquisition of the buffer area for compression. (request URL = aa....aa)

aa....aa: Request URL

Description: An error occurred while buffer area for the response compression functionality was being secured.
Action: The memory might be insufficient. Secure the memory that can be used by the system, and then restart. The insufficient memory might be because of the compression threshold value specified in the initialization parameter of the filter used for the response compression functionality is too large.

KDJE39910-I

The response will be compressed. (request URL = aa....aa)

aa....aa: Request URL

Description: The response will be compressed.

KDJE39911-W

The response will not be compressed. (request URL = aa....aa)

aa....aa: Request URL

Description: The Media-Type specified in the response compression rule was set in the response, when data was being written in the buffer of the HTTP response using either ServletOutputStream acquired with the getOutputStream method, or PrintWriter acquired with the getWriter method of javax.servlet.ServletResponse. The response will not be compressed.
Action: When compressing the response, invoke the setContentType method when data is not being written in the buffer of the HTTP response, and then set the Media-Type specified in the response compression rule for the response.

KDJE39912-I

The default response compression rule aa....aa will be applied to all responses. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Default value

bb....bb: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

cc....cc: Context root name

Description: The default response compression rule aa....aa will be applied to all responses.

KDJE39913-E

The filter name of the filter for the response compression function is invalid. (J2EE application = aa....aa, context root = bb....bb, filter name = cc....cc)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Specified filter name

Description: The filter name of the filter used for the response compression functionality is invalid.
Action: Modify the filter name specified in the filter name of the filter used for the response compression functionality of the Deployment Descriptor (web.xml), and then redeploy.