7.4 Messages from KDJE50000 to KDJE54099
This section explains the messages from KDJE50000 to KDJE54099.
-
KDJE50000-E
An internal error occurred.aa....aa
aa....aa: Details
- Description
-
An internal error occurred.
- Action
-
Check the detailed message, and then contact maintenance personnel.
-
KDJE50001-E
Caught an exception.
- Description
-
An exception was caught.
- Action
-
Check the exception.
-
KDJE50002-E
Throw an exception.
- Description
-
An exception was thrown.
- Action
-
Check the exception.
-
KDJE50003-I
A connection was returned to the user.
- Description
-
The DataSource.getConnection method returned a connection to the user.
- Action
-
No action required.
-
KDJE50004-I
A connection was closed.
- Description
-
A connection was closed. A connection closes in the following two cases; when the user issues the Connection.close method and when a J2EE server automatically closes the connection due to a transaction timeout.
- Action
-
No action required.
-
KDJE50005-I
A local transaction was begun.
- Description
-
The J2EE server started a local transaction.
- Action
-
No action required.
-
KDJE50006-I
A local transaction was committed.
- Description
-
The J2EE server committed a local transaction.
- Action
-
No action required.
-
KDJE50007-I
A local transaction was rolled back.
- Description
-
The J2EE server rolled back a local transaction.
- Action
-
No action required.
-
KDJE50008-I
A managed connection was created.
- Description
-
The J2EE server created a managed connection.
- Action
-
No action required.
-
KDJE50009-I
A managed connection was cleaned up.
- Description
-
The J2EE server cleaned up a managed connection.
Cleanup will close a connection generated from a managed connection.
- Action
-
No action required.
-
KDJE50010-I
A managed connection was destroyed.
- Description
-
The J2EE server destroyed a managed connection.
The cleanup of a managed connection is accompanied with the destruction of a managed connection. The physical connection to the relational database system will be disconnected.
- Action
-
No action required.
-
KDJE50011-E
This user handle has been already closed.
- Description
-
The user handle (connection) is already closed.
When a method of an already closed connection is invoked, this message is displayed.
- Action
-
Confirm the following details:
-
A method of an already closed connection is called.
-
A transaction timeout occurred.
-
The automatic close functionality of a J2EE server closed the connection.
-
-
KDJE50012-E
The transaction status of this managed connection is invalid.
- Description
-
The transaction status of the managed connection is invalid.
- Action
-
Confirm the following details:
-
When the JTA transaction is started with the UserTransaction.begin method or when the transaction is started with the transaction attribute of an EJB, the setAutoCommit method, commit method, or rollback method of the Connection class is invoked.
-
When the setAutoCommit (false) method of the Connection class is called and Auto Commit is disabled, an attempt is made to start the transaction with the UserTransaction.begin method or with the EJB transaction attributes.
-
-
KDJE50013-E
Re-authentication is not supported.
- Description
-
Re-authentication is not supported.
- Action
-
Make sure that true is not specified in the <reauthentication-support> tag of the Connector property file.
-
KDJE50014-E
Cannot get an XAResource from a non XA connection.
- Description
-
A XAResource cannot be acquired from a connection that does not support XA.
- Action
-
Make sure that XATransaction is not specified in the <transaction-support> tag of the Connector property file.
-
KDJE50015-E
Failed to get an XAResource from the XAConnection.
- Description
-
The XAConnection.getXAResource method of the JDBC driver caught an SQLException.
- Action
-
Check the JDBC driver log.
-
KDJE50016-E
Failed to close the connection handle.
- Description
-
The Connection.close method of the JDBC driver caught an SQLException.
- Action
-
Check the JDBC driver log.
-
KDJE50017-E
Failed to close the physical connection.
- Description
-
An attempt to close the physical connection has failed.
- Action
-
Check the JDBC driver log.
-
KDJE50018-E
Failed to get a connection.
- Description
-
The PooledConnection.getConnection method of the JDBC driver caught an SQLException.
- Action
-
Check the JDBC driver log.
-
KDJE50019-E
The user name and the password wasn't specified.
- Description
-
The user name and the password are not specified.
This message is displayed if the DataSource.getConnection method is invoked without any arguments when Application is specified for the <res-auth> tag in the resource reference definition of an EJB or ServletDD.
- Action
-
Specify 'Container' for the <res-auth> tag or specify the user name and the password in the arguments of the DataSource.getConnection method.
-
KDJE50020-E
Failed to get a physical connection.
- Description
-
A physical connection cannot be acquired from the JDBC driver.
- Action
-
Check the JDBC driver log.
-
KDJE50021-E
Cannot find the driver class.
- Description
-
The JDBC driver class in not found.
- Action
-
Confirm that the JDBC driver class is included in the class path.
-
KDJE50022-E
Failed to set a property to the driver. driverObject=aa....aa, setterMethodName=bb....bb, propertyValue=cc....cc, cause=dd....dd
aa....aa: Object of the JDBC driver
bb....bb: set method of the property
cc....cc: Value to be set
dd....dd: Exception occurred
- Description
-
A property cannot be set to the JDBC driver.
- Action
-
Check whether:
-
A valid type is set up for each property value.
-
An exception occurred in the JDBC driver from the JDBC driver log.
-
-
KDJE50023-E
Failed to begin a local transaction.
- Description
-
An attempt to start a local transaction has failed because the Connection.setAutoCommit(false) method of the JDBC driver caught an SQLException.
- Action
-
Check the JDBC driver log.
-
KDJE50024-E
Failed to commit a local transaction.
- Description
-
An attempt to commit a local transaction has failed because the Connection.commit method or Connection.setAutoCommit(true) method of the JDBC driver caught an SQLException.
- Action
-
Check the JDBC driver log.
-
KDJE50025-E
Failed to rollback a local transaction.
- Description
-
An attempt to rollback a local transaction has failed because the Connection.rollback method or Connection.setAutoCommit(true) method of the JDBC driver caught an SQLException.
- Action
-
Check the JDBC driver log.
-
KDJE50026-E
Failed to get the EIS product name.
- Description
-
The DatabaseMetaData.getDatabaseProductName method of the JDBC driver caught an SQLException.
- Action
-
Check the JDBC driver log.
-
KDJE50027-E
Failed to get the EIS product version.
- Description
-
The DatabaseMetaData.getDatabaseProductVersion method of the JDBC driver caught an SQLException.
- Action
-
Check the JDBC driver log.
-
KDJE50028-E
Failed to get the maximum number of connections.
- Description
-
The DatabaseMetaData.getMaxConnections method of the JDBC driver caught an SQLException.
- Action
-
Check the JDBC driver log.
-
KDJE50029-E
Failed to get the user name.
- Description
-
The DatabaseMetaData.getUserName method of the JDBC driver caught an SQLException.
- Action
-
Check the JDBC driver log.
-
KDJE50030-E
Failed to get a DatabaseMetaData from the connection handle.
- Description
-
The Connection.getMetaData method of the JDBC driver caught an SQLException.
- Action
-
Check the JDBC driver log.
-
KDJE50031-E
Failed to get the connection handle.
- Description
-
The connection cannot be acquired from the managed connection.
- Action
-
Check the exception of the cause.
-
KDJE50032-E
This Statement has been already closed.
- Description
-
This Statement is already closed.
- Action
-
Check whether an already closed Statement method is being invoked.
-
KDJE50033-E
This PreparedStatement has been already closed.
- Description
-
This PreparedStatement is already closed.
- Action
-
Check whether an already closed PreparedStatement method is being invoked.
-
KDJE50034-E
This CallableStatement has been already closed.
- Description
-
This CallableStatement is already closed.
- Action
-
Check whether an already closed CallableStatement method is being invoked.
-
KDJE50035-E
This ResultSet has been already closed.
- Description
-
This ResultSet is already closed.
- Action
-
Check whether an already closed ResultSet method is being invoked.
-
KDJE50036-E
Physical connection-related error occurred.
- Description
-
An error related to the physical connection (such as disconnection of a physical connection) occurred from the JDBC driver.
- Action
-
Check the JDBC driver log and relational database system log, identify the factor that caused the physical connection-related error, and then take action accordingly.
-
KDJE50037-E
This managed connection has been already destroyed.
- Description
-
The managed connection (physical connection) is already destroyed.
- Action
-
Check whether a physical connection-related error occurred. If an error related to the physical connection occurred, take the necessary action.
-
KDJE50038-E
Failed to change the auto commit mode.
- Description
-
An attempt to change the auto commit mode has failed because the Connection.setAutoCommit method of the JDBC driver caught an exception.
- Action
-
Check the JDBC driver log.
-
KDJE50039-E
Specified log level is invalid.
- Description
-
An invalid log level was specified.
- Action
-
Specify a valid log level.
-
KDJE50040-W
A Statement which is not closed is automatically closed when the Connection that generated it is closed.
- Description
-
When the Connection is closed, a Statement object that is not closed will be closed.
- Action
-
Revise the process so that the Statement object is closed explicitly.
-
KDJE50041-E
Invalid PreparedStatementPoolSize is specified. Specify the value in the range of 0 - aa....aa. Default value is used:bb....bb.
aa....aa: Maximum value of the PreparedStatement pool size
bb....bb: Default value of the PreparedStatement pool size
- Description
-
An invalid PreparedStatement pool size was specified.
The default value (bb....bb) will be used.
- Action
-
Specify a valid PreparedStatement pool size. You can specify the value in the range of 0 to aa....aa.
-
KDJE50042-E
Invalid CallableStatementPoolSize is specified. Specify the value in the range of 0 - aa....aa. Default value is used : bb....bb.
aa....aa: Maximum value of the CallableStatement pool size
bb....bb: Default value of the CallableStatement pool size
- Description
-
An invalid CallableStatement pool size was specified.
The default value (bb....bb) will be used.
- Action
-
Specify a valid CallableStatement pool size. You can specify the value in the range of 0 to aa....aa.
-
KDJE50043-E
The sum of PreparedStatementPoolSize and CallableStatementPoolSize should be aa....aa or less. Default value is used: PreparedStatementPoolSize=bb....bb, CallableStatementPoolSize=cc....cc.
aa....aa: Maximum value of the sum of PreparedStatement pool size and CallableStatement pool size
bb....bb: Default value of the PreparedStatement pool size
cc....cc: Default value of the CallableStatement pool size
- Description
-
Change so that the sum of PreparedStatement pool size and CallableStatement pool size is less than or equal to aa....aa.
The default value bb....bb will be used for the pool size of PreparedStatement. The default value cc....cc will be used for the pool size of CallableStatement.
- Action
-
Specify the settings so that the sum of PreparedStatementPoolSize and CallableStatementPoolSize is less than or equal to the maximum value.
-
KDJE50044-I
A statement was added to the statement pool.
- Description
-
A statement was added to the statement pool.
- Action
-
No action required.
-
KDJE50045-I
A statement was removed from the statement pool.
- Description
-
A statement was destroyed from the statement pool.
- Action
-
No action required.
-
KDJE50046-I
A statement was returned from the statement pool.
- Description
-
A statement was acquired from the statement pool.
- Action
-
No action required.
-
KDJE50047-I
A statement was returned to the statement pool.
- Description
-
A statement was returned to the statement pool.
- Action
-
No action required.
-
KDJE50048-I
A work on behalf of the transaction branch was started.
- Description
-
A process of transaction branch was started.
- Action
-
No action required.
-
KDJE50049-I
A work on behalf of the transaction branch was ended.
- Description
-
A process of transaction branch was ended.
- Action
-
No action required.
-
KDJE50050-I
A work on behalf of the transaction branch was prepared to commit.
- Description
-
A process of transaction branch was prepared to commit.
- Action
-
No action required.
-
KDJE50051-I
A work on behalf of the transaction branch was committed.
- Description
-
A process of transaction branch was committed.
- Action
-
No action required.
-
KDJE50052-I
A work on behalf of the transaction branch was rolled back.
- Description
-
A process of transaction branch was rolled back.
- Action
-
No action required.
-
KDJE50053-I
A list of prepared transaction branch was obtained.
- Description
-
A list of transaction branch that was prepared to commit was acquired.
- Action
-
No action required.
-
KDJE50054-I
A heuristically completed transaction branch was forgotten.
- Description
-
A system reported that the heuristically concluded transaction branch is to be ignored.
- Action
-
No action required.
-
KDJE50055-E
Failed to validate a physical connection.
- Description
-
An attempt to validate a physical connection has failed.
A failure is occurring while connecting to the database.
- Action
-
Check the message of the exception log KDJE50001-E output in the identical threads before this message is displayed, and then remove the cause of the connection failure.
-
KDJE50056-E
Failed to clear warnings reported for the connection handle.
- Description
-
The Connection.clearWarnings method of the JDBC driver caught an SQLException.
- Action
-
Check the JDBC driver log.
-
KDJE50057-E
Failed to destroy the statement pool.
- Description
-
An exception was caught while destroying the statement pool.
- Action
-
Check the JDBC driver log.
-
KDJE50058-E
Failed to validate a physical connection because an invalid transaction support level is specified.
- Description
-
An attempt to validate the connection has failed because an invalid transaction support level was specified.
- Action
-
Specify a transaction support level that you can use in the imported RARs.
-
KDJE50059-W
Cannot find a setter method on the driver.driverObject=aa....aa, propertyKey=bb....bb, propertyValue=cc....cc
aa....aa: Object of the JDBC driver
bb....bb: Property name
cc....cc: Value to be set
- Description
-
A setter method was not found on the JDBC driver.
- Action
-
Check the JDBC driver version.
-
KDJE50060-W
The statement pooling is not supported in this database.
- Description
-
The statement pooling functionality of the specified transaction support level was not supported in this database version.
PreparedStatementPoolSize and CallableStatementPoolSize will operate assuming that 0 is specified.
- Action
-
Confirm that the version of the relational database system to be connected supports the open statements between the transactions of the specified transaction support level. If the statement pooling functionality is not used, specify 0 in PreparedStatementPoolSize and CallableStatementPoolSize.
-
KDJE50061-W
An user name and a password specified on the getConnection() method is ignored.
- Description
-
The user name and the password specified in the getConnection() method are ignored and container management sign-on is performed. When Container is specified for the <res-auth> tag in the resource reference definition of EJB or ServletDD, if the DataSource.getConnection(String user, String password) is invoked, this message will be displayed.
- Action
-
To perform component management sign-on, specify Application for the <res-auth> tag in the resource reference definition of an EJB or ServletDD. To perform container management sign-on, use DataSource.getConnection() without arguments.
-
KDJE50063-I
A JDBC transaction was automatically committed.
- Description
-
The J2EE server committed a JDBC transaction.
- Action
-
Check whether the connection is closed without concluding the JDBC transaction.
When the user program manages the JDBC transaction with the auto commit mode set to disabled, close the connection after the transaction is concluded.
-
KDJE50064-I
The statement will now be canceled. (statement = aa....aa)
aa....aa: Statement to be cancelled
- Description
-
The statement will be canceled.
- Action
-
If the cancellation does not end even after waiting for some time, check the JDBC driver log and the relational database system log.
-
KDJE50065-I
The statement was canceled. (statement = aa....aa)
aa....aa: Statement to be cancelled
- Description
-
The statement was canceled.
-
KDJE50066-I
A JDBC transaction was automatically rolled back.
- Description
-
The J2EE server rolled back a JDBC transaction.
- Action
-
Confirm that the user program has concluded all the JDBC transactions. When the user program manages the JDBC transaction with the auto commit mode set to disabled, the transaction needs to be concluded on the responsibility of the user program.
-
KDJE50067-E
An attempt to cancel the statement has failed. (statement = aa....aa)
aa....aa: Statement to be cancelled
- Description
-
An attempt to cancel the statement has failed.
- Action
-
Check whether the statement is already closed.
-
KDJE50068-E
Processing cannot continue because an application is being forced to stop.
- Description
-
The processing cannot be continued because an application is being forced to stop.
- Action
-
Check whether the application is being forcibly stopped.
-
KDJE50069-E
Cannot find the constant field on JDBC driver class.
- Description
-
The constant field on the JDBC driver was not found.
- Action
-
Confirm whether the JDBC driver of a valid version was added to the class path.
-
KDJE50070-I
Connection ID was renewed. (old Connection ID = aa....aa, new Connection ID = bb....bb)
aa....aa: Connection ID before update
bb....bb: Connection ID after update
- Description
-
A connection ID was updated.
-
KDJE50071-W
Failed to create ConnectionID.
- Description
-
An attempt to create a connection ID has failed.
- Action
-
Confirm whether the permission to reference the dynamic performance view was assigned to the connection user. Note that if you are using Cosminexus DABroker Library, the KDJE50001-E message is displayed before this message.
-
KDJE50072-E
The linked resource adapter has not started. (linked resource adapter = aa....aa, cause = bb....bb)
aa....aa: Linked resource adapter name
bb....bb: Cause
- Description
-
The linked resource adapter has not started.
- Action
-
Start the linked resource adapter. If it does not start, check the cause (bb....bb).
-
KDJE50073-E
The linked resource adapter is not Cosminexus Reliable Messaging. (linked resource adapter = aa....aa)
aa....aa: Linked resource adapter name
- Description
-
The linked resource adapter is not Cosminexus Reliable Messaging.
- Action
-
Specify Cosminexus Reliable Messaging in the linked resource adapter of DB Connector for Cosminexus Reliable Messaging.
-
KDJE50074-E
A connection could not be obtained. (cause = aa....aa)
aa....aa: Cause
- Description
-
A connection cannot be acquired.
- Action
-
Check the cause (aa....aa).
-
KDJE50075-E
This method of the connection interface is not supported. (method name = aa....aa)
aa....aa: Method name
- Description
-
This method of the connection interface is not supported.
- Action
-
If you use the DB Connector for Cosminexus Reliable Messaging, do not use the method to operate the transaction directly in JDBC. Use the DB Connector to operate the transaction directly in JDBC.
-
KDJE50076-E
An attempt to close the connection has failed. (cause = aa....aa)
aa....aa: Cause
- Description
-
An attempt to close the connection has failed.
- Action
-
Check the cause (aa....aa).
-
KDJE50077-E
Disabling the auto-commit mode is not supported.
- Description
-
The process of disabling the Auto Commit Mode is not supported.
- Action
-
If you use the DB Connector for Cosminexus Reliable Messaging, do not use the method to operate the transaction directly in JDBC. Use the DB Connector to operate the transaction directly in JDBC.
-
KDJE50078-W
You can connect to HiRDB only. Set the property databaseName to HIRDB.
- Description
-
You can connect to HiRDB only. Set the property databaseName to HIRDB.
- Action
-
Check the settings of the database type to be connected. Use the DB Connector for Cosminexus Reliable Messaging for the Oracle Thin driver to connect to Oracle.
-
KDJE50079-W
The default value will be used for the loginTimeout property. (default value for loginTimeout = aa....aa)
aa....aa: Default loginTimeout property value
- Description
-
The default value will be used because a value of 0 or less is specified in the loginTimeout property.
- Action
-
Specify a value of 1 or more in the loginTimeout property to use the Oracle JDBC Thin Driver in the member resource adapter.
-
KDJE50080-W
A transaction timeout, a forced termination of an application, or a method cancellation occurred. The last executed SQL will be displayed. (RootAP = aa....aa, connection ID = bb....bb, method name = cc....cc, now executing = dd....dd, SQL = ee....ee)
aa....aa: IP address, process ID, or root application information
bb....bb: Connection ID of the connection in which the SQL is executed
cc....cc: Method name in which the SQL is executed
dd....dd: Method in which the SQL is executed is running (true or false)
ee....ee: SQL executed at the end
- Description
-
A transaction timeout, forced termination of the application, or method cancellation has occurred. The SQL executed at the end will be displayed.
- Action
-
Resolve the problem by referencing the information of the output SQL and application information.
For details about the application information, reference the messages of transaction timeout (KDJE31002-Wand KDJE31016-W), and the messages of method cancellation (KDJE52703-W, KDJE52704-I, and KDJE52705-W) containing the same information as the root application information of this message.
-
KDJE50083-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 aa....aa property from the default value, change the value of the aa....aa property, and then stop and restart the J2EE server.
-
KDJE50084-W
Acquisition of statement information failed. When a statement is stored in a pool, it can no longer be initialized. (statement = aa....aa, info = bb....bb, cause = cc....cc)
aa....aa: Statement
bb....bb: Information that cannot be initialized
cc....cc: Reason for failure in acquiring the value for initialization
- Description
-
The default value of the information about the statement cannot be referenced. The information about the statement cannot be returned to the default value when the statement object is saved in the statement pool.
Note that when the statement object is acquired from the statement pool, the information about the changed statement remains.
- Action
-
Resolve the cause due to which the value for initialization could not be acquired. Stop and restart the J2EE server. If the inability to initialize the information about the statement does not pose any problem, no action is required.
-
KDJE50085-I
A Statement object error occurred with the JDBC driver.
- Description
-
An error related to Statement occurred in the JDBC driver. Close the statement being used and remove from the pool.
-
KDJE50500-E
An error occurred in the web container connection pool function. (error details = aa....aa:bb....bb)
aa....aa: Exception class
bb....bb: Exception message
- Description
-
An error occurred in the connection pool functionality.
This message is displayed if a certain exception occurs.
- Action
-
Take action according to the error details.
-
KDJE50501-E
The number of users connected to a database exceeded the specified limit. The set number of users is aa....aa.
aa....aa: Set the number of maximum users
- Description
-
The number of users who can be connected to the database is exceeded.
- Action
-
Increase the number of users who can be connected to the database.
-
KDJE50502-E
An attempt to establish a connection has failed. (RetryInterval = aa....aa, RetryCount = bb....bb)
aa....aa: Retry waiting time
bb....bb: Retry count
- Description
-
A connection cannot be established.
- Action
-
Change the waiting time and retry count, and then re-execute the process.
-
KDJE50505-E
No database ID is specified in the pool management information.
- Description
-
The database ID was not specified in the pool management information.
- Action
-
Specify a database ID in the pool management information.
-
KDJE50506-E
The old database ID is not specified.
- Description
-
The old database ID is not specified.
- Action
-
Specify the old database ID.
-
KDJE50507-E
The new database ID is not specified.
- Description
-
The new database ID is not specified.
- Action
-
Specify the new database ID.
-
KDJE50508-E
You cannot specify the old database ID as the new database ID.
- Description
-
You cannot specify the same name in the old database ID and the new database ID.
- Action
-
Change either the old database ID or the new database ID.
-
KDJE50509-E
An attempt to get the pool management information corresponding to the database ID has failed. (database ID = aa....aa)
aa....aa: Database ID
- Description
-
The pool management information corresponding to the database ID (aa....aa) cannot be acquired.
- Action
-
Change the database ID, and then re-execute the process.
-
KDJE50510-E
No pool management information is registered.
- Description
-
The pool management information is not registered.
- Action
-
Register the pool management information.
-
KDJE50511-E
The same database ID already exists in the pool management information. (database ID = aa....aa)
aa....aa: Database ID
- Description
-
The specified database ID (aa....aa) already exists.
- Action
-
Change the database ID.
-
KDJE50512-E
The database ID contains invalid characters.
- Description
-
The characters used in the database ID are invalid.
- Action
-
Change the characters used in the database ID.
-
KDJE50513-E
No database ID is specified.
- Description
-
The database ID is not specified.
- Action
-
Specify the database ID.
-
KDJE50514-E
No class name is specified. Specify the class name and URL as a pair.
- Description
-
The class name is not specified. Always specify the class name when specifying the URL.
- Action
-
Specify the class name.
-
KDJE50515-E
No URL is specified. Specify the URL and class name as a pair.
- Description
-
The URL is not specified.
Always specify the URL when specifying the class name.
- Action
-
Specify the URL.
-
KDJE50516-E
An invalid number is specified as the number of users in the pool management information. The value should be more than zero integers.
- Description
-
An invalid number is specified as the number of users.
- Action
-
Set the number of users to 0 or more.
-
KDJE50517-E
An invalid number is specified as the minimum connections value in the pool management information. The value should be more than zero integers.
- Description
-
An invalid number is specified as the minimum connections value.
- Action
-
Set the minimum connections value to 0 or more.
-
KDJE50518-E
An invalid number is specified as the maximum connections value in the pool management information. The value should be more than zero integers.
- Description
-
An invalid number is specified as the maximum connections value.
- Action
-
Set the maximum connections value to 0 or more.
-
KDJE50519-E
An invalid number is specified as the waiting time in the pool management information. The value should be more than zero integers.
- Description
-
An invalid number is specified as the retry waiting time.
- Action
-
Set the retry waiting time to 0 or more.
-
KDJE50520-E
An invalid number is specified as the number of retry times in the pool management information. The value should be more than zero integers.
- Description
-
An invalid number is specified as the retry count.
- Action
-
Set the retry count to 0 or more.
-
KDJE50521-E
The maximum connections value should be more than the minimum connections value.
- Description
-
The relationship between the maximum connections value and minimum connections value is invalid.
- Action
-
If the maximum connections value is 1 or more, make the maximum connections value greater than the minimum connections value.
-
KDJE50522-E
No class name or URL is specified.
- Description
-
A class name or URL is not specified.
- Action
-
Always specify the URL when specifying the class name.
-
KDJE50523-E
An attempt to register pool management information has failed.
- Description
-
An attempt to register the pool management information has failed.
- Action
-
Revise the pool management information, and then re-execute the process.
-
KDJE50524-E
The connection is closed.
- Description
-
The connection is closed.
- Action
-
Acquire the connection again.
-
KDJE51001-W
The directory name specified for the ejbserver.client.log.directory exceeds 200 bytes. The default value aa....aa will be used.
aa....aa: Default directory name
- Description
-
The length of the directory name specified for the ejbserver.client.log.directory key exceeds 200 bytes.
The default value (aa....aa) will be used.
- Action
-
Revise the value of the ejbserver.client.log.directory key.
-
KDJE51002-W
The specified value is invalid. The default value aa....aa will be used. property name = bb....bb
aa....aa: Default value
bb....bb: Property name
- Description
-
An invalid value was specified in the property.
The default value (aa....aa) will be used.
- Action
-
Revise the specified value of the property (bb....bb).
-
KDJE51003-E
The directory aa....aa cannot be accessed. Processing will now stop.
aa....aa: Directory name
- Description
-
The directory (aa....aa) cannot be accessed.
The processing will now stop.
Take action based on the following causes:
-
Permission is not available to access the directory.
-
The file name is specified in the ejbserver.client.log.directory key.
-
An attempt to generate the log directory has failed because more than one Java applications are started simultaneously during the initial startup.
-
- Action
-
-
Check the directory access permission.
-
Check whether the file name is specified in the ejbserver.client.log.directory key.
-
Either specify the settings to avoid starting more than one Java applications simultaneously during the initial startup or create the log output destination directory beforehand.
-
-
KDJE51004-W
The default directory was not found. The EJB client application execution directory aa....aa will be used.
aa....aa: Directory name
- Description
-
An attempt was made to use the default directory in the ejbserver.client.log.directory, but the default directory was not found.
The EJB client application execution directory (aa....aa) will be used.
- Action
-
Confirm that Cosminexus Developer's Kit for Java is being used.
-
KDJE51005-W
An attempt to delete the directory aa....aa has failed.
aa....aa: Directory name
- Description
-
An attempt to delete the directory (aa....aa) has failed. The processing continues.
- Action
-
Check whether the directory and the file to be deleted are being accessed.
When the EJB client applications are started concurrently, this message is displayed. A problem does not exist in the operations of the EJB client application, but the number of subdirectories might exceed the value specified in the ejbserver.client.log.directorynum key. If this message is displayed frequently, change the value of the ejbserver.client.log.directorynum key to '0' and manage the sub directory using the cjcldellog command.
-
KDJE51006-I
Usage: cjcldellog -t <time>h | <days>d [-f] directoryname
- Description
-
This message describes the usage method of the cjcldellog command.
-
KDJE51007-E
The specified directory is incorrect.
- Description
-
The specified directory is incorrect.
- Action
-
Revise the specified directory.
-
KDJE51008-W
The performance trace is unavailable due to failure of initialization. (reason = aa....aa)
aa....aa: Reason
- Description
-
An attempt to initialize the PRF has failed. The PRF trace cannot be used.
- Action
-
Take action according to the reason described in aa....aa. The following table lists the reasons described in aa....aa and the corresponding actions:
Table 7‒6: List of reasons described in KDJE51008-W Reason
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 or the directory exists.
-2
An error occurred while starting the PRF daemon service in the process.
The PRF demon might not be invoked.
Confirm that the PRF daemon is running. Also, check the specification of PRFID of the definition file.
-3
An error occurred while starting the PRF daemon service in the process (error such as system call error).
See the file under environment-variable-PRFSPOOL-setting-directory\log\PRF-identifier (In Windows) or $PRFSPOOL/log/PRF-identifier (In UNIX), check the message of Cosminexus Performance Tracer, check the cause of the error, and take action accordingly.
-4
An attempt to load the library required in the PRF daemon service 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.
Remove the cause of the error, and then re-execute the process.
-
-
KDJE51009-E
The specified value for the aa....aa option is invalid.
aa....aa: Option name
- Description
-
The specified value for the option is invalid.
- Action
-
See the uCosminexus Application Server Command Reference Guide.
-
KDJE51010-E
Failed to initialize ORB. Check the ORB version and setting.
- Description
-
An attempt to initialize ORB has failed. ORB version or setting is invalid.
- Action
-
Confirm the ORB version and the properties specified when starting the program.
-
KDJE51011-E
Failed to initialize client during aa....aa. Detail = bb....bb
aa....aa: Running process
bb....bb: Detailed message
- Description
-
An attempt to initialize the client functionality has failed.
- Action
-
See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact maintenance personnel.
-
KDJE51012-I
Usage: cjclstartap EJBClientMainClassName [[EJBClientArgs] ...]
- Description
-
This message describes the usage method of the cjclstartap command.
-
KDJE51013-E
The common definition file was not found.
- Description
-
The common definition file was not found.
- Action
-
Confirm whether the system is set up correctly.
In UNIX, confirm that the Component container installation directory is correct.
-
KDJE51014-E
The user definition file was not found.
- Description
-
The user definition file (usrconf.cfg, usrconf.properties) was not found.
- Action
-
Confirm that the environment variable CJCLUSRCONFDIR of the user definition file storage directory is specified.
If the above environment variable is specified, confirm that the setting path includes the user option definition file (usrconf.cfg) and the user property file (usrconf.properties).
-
KDJE51015-E
The main method was not found.
- Description
-
An error occurred when executing the EJB client.
- Action
-
Implement the main method in the specified main class.
-
KDJE51016-E
An exception occurred in the main method. (exception message = aa....aa)
aa....aa: Exception type
- Description
-
An exception (aa....aa) occurred in the main method.
- Action
-
See the exception message (aa....aa), and then remove the exception in the main method.
-
KDJE51017-E
The command was not found. Command name = aa....aa
aa....aa: Command name that was not found
- Description
-
The command was not found.
- Action
-
If the java command is not found, confirm that the Cosminexus Developer's Kit for Java is installed.
-
KDJE51018-I
The cjclstartap command will now start. (directory for the user definition file = aa....aa, cjclstartap PID = bb....bb, EJB client PID = cc....cc)
aa....aa: Environment variable settings for storing the user definition file
bb....bb: cjclstartap process ID
cc....cc: EJB client process ID
- Description
-
The cjclstartap command will now start using the user definition of aa....aa directory.
-
KDJE51019-I
The cjclstartap command was stopped. (cjclstartap PID = aa....aa, EJB client PID = bb....bb)
aa....aa: cjclstartap process ID
bb....bb: EJB client process ID
- Description
-
The cjclstartap command was stopped.
-
KDJE51500-E
The SMTP connection test failure to aa....aa in bb....bb.
aa....aa: SMTP server address
bb....bb: Mail display name
- Description
-
An attempt to test the connection to the SMTP server bb....bb set in aa....aa has failed.
There might be a problem in the mail settings.
- Action
-
Check and, if necessary, revise the mail settings. If a problem does not exist in the mail settings, revise the network environment settings.
-
KDJE51600-W
An Invalid property value is specified. aa....aa=bb....bb Default value cc....cc is used.
aa....aa: Property name
bb....bb: Specified value
cc....cc: Default value
- Description
-
The property value (bb....bb) is invalid. The default value (cc....cc) will be used.
- Action
-
Specify a valid property value.
-
KDJE51700-W
A property value is invalid. The default value will be used. (key = aa....aa, value = bb....bb, default value = cc....cc)
aa....aa: Property key
bb....bb: Set value
cc....cc: Default value
- Description
-
The default value will be used because an invalid value was acquired from the property file.
Take action based on the following causes:
-
An invalid value is specified in the property
-
A value outside the valid range is specified
-
- Action
-
Check the contents of the usrconf.properties file, and then modify the property value where the error occurred.
-
KDJE51701-W
An attempt to set the timeout value has failed. (timeout = aa....aa)
aa....aa: Specified timeout value
- Description
-
An attempt to set the timeout value has failed.
The timeout value (aa....aa) outputs "-" when the specified value cannot be acquired.
The processing continues.
- Action
-
Acquire the maintenance information, and then contact maintenance personnel.
-
KDJE51702-E
An attempt to create the RMI server socket has failed. The specified port number might already be in use. (port = aa....aa, details = bb....bb)
aa....aa: Port number
bb....bb: Detailed message
- Description
-
An attempt to create the RMI server socket has failed. The specified port number might already be in use.
- Action
-
Revise the value specified in the property ejbserver.rmi.remote.listener.port.
-
KDJE51703-E
An attempt to create the RMI client socket has failed. An incorrect host name or incorrect port number might be specified. (host = aa....aa, port = bb....bb, details = cc....cc)
aa....aa: Host name
bb....bb: Port number
cc....cc: Details
- Description
-
An attempt to create the RMI client socket has failed. An incorrect host name or incorrect port number was specified.
- Action
-
Revise the value specified in the property ejbserver.rmi.naming.host or property ejbserver.rmi.remote.listener.port.
-
KDJE52100-E
Unexpected error occurred during deploying web application. Detail = aa....aa.
aa....aa: Details
- Description
-
An unexpected error occurred during Web application deployment.
- Action
-
Take action based on the details, if possible.
If you do not understand the cause, acquire the maintenance information, and then contact maintenance personnel.
-
KDJE52101-E
Unexpected error occurred during starting web application. Detail = aa....aa.
aa....aa: Details
- Description
-
An unexpected error occurred during Web application startup.
- Action
-
Take action based on the details, if possible.
If you do not understand the cause, acquire the maintenance information, and then contact maintenance personnel.
-
KDJE52102-E
Cannot find working file necessary to start web application.
- Description
-
The working file necessary to start the Web application was not found.
The file necessary to start the Web application might be deleted.
- Action
-
Restart the J2EE application.
-
KDJE52103-I
Created Context:aa....aa
aa....aa: Created context name
- Description
-
The context aa....aa was created.
-
KDJE52104-E
An attempt to blockade the Web application has failed.
- Description
-
An attempt to lock the Web application has failed.
- Action
-
Restart the J2EE server, and then restart the J2EE application.
-
KDJE52700-W
Necessary user program monitoring information does not exist.
- Description
-
A necessary user program monitoring information does not exist.
The monitoring ends API might be invoked without invoking the monitoring start API.
- Action
-
Check whether the monitoring end API is invoked without invoking the monitoring start API.
-
KDJE52701-W
Unnecessary user program monitoring information exists.
- Description
-
Unnecessary user program monitoring information exists.
The monitoring start API was invoked, but the monitoring end API might not be invoked.
- Action
-
Check whether the monitoring end API is invoked.
-
KDJE52702-W
The thread state is invalid. Recover manually.(threadID = aa....aa, state = bb....bb)
aa....aa: Thread ID
bb....bb: Thread state
- Description
-
The thread state is invalid.
- Action
-
- When the thread state is 'failed'
-
Execute any one of the following actions as required:
-
Method cancellation by a command
-
Forced termination of the application
-
Forced termination of the server
The most reliable action is the forced termination of the server. If you execute method cancellation by a command and forced termination of the application, the thread state might fail once again.
-
- When the thread state is 'stopped'
-
Terminate the server forcibly.
-
KDJE52703-W
A timeout occurred while the user program was executing. (threadID = aa....aa, rootAPInfo = bb....bb, application = cc....cc, dd....dd, ee....ee)
aa....aa: Thread ID
bb....bb: Root AP information
cc....cc: Application name
dd....dd: (contextRoot = context-root-name, uri = URI-name) or (bean = bean-name, method = method-name)
ee....ee: optMsg = Additional information
- Description
-
A method timeout occurred.
- Action
-
Execute any one of the following actions as required:
-
Method cancellation by a command
-
Forced termination of the application
-
Forced termination of the server
The most reliable action is the forced termination of the server. If you execute method cancellation by a command and forced termination of the application, the thread state might fail once again.
-
-
KDJE52704-I
The current processing has been successfully canceled. (threadID = aa....aa, rootAPInfo = bb....bb, application = cc....cc, dd....dd, ee....ee)
aa....aa: Thread ID
bb....bb: Root AP information
cc....cc: Application name or class name of the batch application
dd....dd: (contextRoot = context-root-name, uri = URI-name), (bean = bean-name, method = method-name), or (arguments = argument-of-a-batch-application)
Note that argument-of-the-batch-application is enclosed within parentheses ("") and displayed. When displaying more than one arguments, a single-byte space is provided in between.
ee....ee: optMsg = Additional information
- Description
-
The method is successfully canceled.
-
KDJE52705-W
An attempt to cancel the current execution failed because a critical section is being executed. (threadID = aa....aa, rootAPInfo = bb....bb, application = cc....cc, dd....dd, ee....ee)
aa....aa: Thread ID
bb....bb: Root AP information
cc....cc: Application name or class name of the batch application
dd....dd: (contextRoot = context-root-name, uri = URI-name), (bean = bean-name, method = method-name), or (arguments = argument-of-a-batch-application)
Note that argument-of-the-batch-application is enclosed within parentheses ("") and displayed. When displaying more than one arguments, a single-byte space is provided in between.
ee....ee: optMsg = Additional information
- Description
-
An attempt to cancel the method has failed because a protected area is being executed.
- Action
-
Execute any one of the following actions as required:
-
Method cancellation by a command
-
Forced termination of the application
-
Forced termination of the server
The most reliable action is the forced termination of the server. If you execute method cancellation by a command and forced termination of the application, the thread state might fail once again.
For a batch server, no actions are required because forced termination of the server is performed automatically.
-
-
KDJE52706-E
The critical section list file is invalid. (aa....aa)
aa....aa: Invalid list
- Description
-
The contents of the protected area list file are invalid.
The contents of the list described in aa....aa are incorrect.
- Action
-
Revise the contents of the list, and then restart the J2EE server.
-
KDJE52707-I
The timer for monitoring user program execution times will now start. (interval = aa....aa)
aa....aa: Monitoring interval
- Description
-
The timer for monitoring user program execution time will now start.
-
KDJE52708-E
An attempt to read the critical section list file has failed. (aa....aa)
aa....aa: Reason
- Description
-
The protected area list file cannot be read.
Take action based on the following causes:
-
The file does not exist.
-
The user does not have the permission to read the file.
-
- Action
-
Take action depending on the cause.
-
KDJE52709-W
The timer for monitoring user program execution times has not started.
- Description
-
The timer for monitoring the user program execution time has not started.
- Action
-
If you use API, specify a valid value in the monitoring interval, and then restart the timer.
-
KDJE52710-W
The current thread is not a target of the function for monitoring user program execution times.
- Description
-
The current thread is not a target of the function for monitoring the user program execution time.
Only the thread that executes the J2EE application is to be monitored.
- Action
-
Invoke an API only for the threads executing the J2EE application.
-
KDJE52711-I
Execution of a user program cannot be forcibly stopped in a Java(TM) VM. (vendor = aa....aa, version = bb....bb)
aa....aa: Vendor of the used Java VM
bb....bb: Version of the used Java VM
- Description
-
An execution of a user program cannot be forcibly stopped in a Java VM (vendor = aa....aa, version = bb....bb).
-
KDJE52712-W
An invalid property value was specified (aa....aa = bb....bb). The default value (cc....cc) will be used.
aa....aa: Property name
bb....bb: Property value
cc....cc: Default value
- Description
-
An invalid property value was specified. The default value (cc....cc) will be used.
- Action
-
Specify a correct value.
-
KDJE52713-E
An attempt to cancel execution has failed. (threadIDs = aa....aa)
aa....aa: Thread ID (multiple thread IDs are delimited with comma (,))
- Description
-
An execution cannot be canceled.
- Action
-
To cancel the re-execution, execute one of the following actions:
-
Method cancellation by a command
-
Forced termination of the application
-
Forced termination of the server
The most reliable action is the forced termination of the server. If you execute method cancellation by a command and forced termination of the application, the thread state might fail once again.
-
-
KDJE52714-W
The specified value is invalid. (value = aa....aa)
aa....aa: Specification value
- Description
-
An invalid value was specified.
-
KDJE52715-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. (current number of files = aa....aa, maximum number of files = bb....bb)
aa....aa: Current number of thread dump files
bb....bb: Maximum number (specification value) of thread dump files
- Description
-
The number of thread dump files has reached the maximum value.
New thread dump files cannot be created until the existing thread dump files are moved to another directory.
- Action
-
Move the thread dump files to another directory immediately.
-
KDJE52716-I
The timed-out execution has finished. (thread ID = aa....aa)
aa....aa: Thread ID
- Description
-
The timed-out execution has finished.
-
KDJE52717-I
The forced termination of application aa....aa will now finish. (detail = bb....bb, thread IDs = cc....cc)
aa....aa: Application name
bb....bb: Detailed message
cc....cc: Thread ID (multiple thread IDs are delimited with comma (,))
- Description
-
The forced termination of application aa....aa will now finish.
The contents displayed in the details (bb....bb) and its meaning are as follows:
- In the case of "1"
-
The forced termination of the application ended due to the timeout (lapse of 3 seconds).
- In the case of "2"
-
An attempt to perform the forced termination of the application has failed.
When the forced termination of an application timed out, ""(blank character) might be output to the thread ID (cc....cc). This is because the request processing in the thread has ended during the time period between the time out of the forced termination of the application and until this message is output. This does not cause any problem.
-
KDJE52718-W
It was judged that a critical section was being executed. (threadID = aa....aa, rootAPInfo = bb....bb, application = cc....cc, dd....dd, ee....ee, class = ff....ff)
aa....aa: Thread ID
bb....bb: Root AP information
cc....cc: Application name or class name of the batch application
dd....dd: Any one of the following is displayed:
(contextRoot = context-root-name, uri = URI-name)
(bean = Bean-name, method = method-name)
(arguments = argument-of-the-batch-application#)
#
The argument-of-the-batch-application is enclosed within parentheses ("") and displayed (when displaying more than one arguments, a single-byte space is used as a delimiter).
ee....ee: optMsg = Additional information
ff....ff: Class judged as protected area
- Description
-
It is determined that a protected area is being executed. The protected area judgment processing will be retried.
- Action
-
Execute method cancellation during the execution of the non-protected area.
-
KDJE52900-I
Usage: cjtracesync [-h] | [-thr | -comm] [serverName ]
- Description
-
This message describes the usage method of the cjtracesync command.
-
KDJE52901-E
The spool directory corresponding to the server name "aa....aa" does not exist.
aa....aa: Server name
- Description
-
The spool directory corresponding to the server name specified by the cjtracesync command does not exist.
- Action
-
Confirm that the server name is entered correctly.
-
KDJE52902-E
The trace management file does not exist. (file name = aa....aa)
aa....aa: Absolute path name of the trace management file
- Description
-
The trace management file (aa....aa) does not exist.
- Action
-
Confirm that the specified server is running.
-
KDJE52903-E
The trace management file "aa....aa" cannot be opened. (file name = aa....aa)
aa....aa: Absolute path name of the trace management file
- Description
-
The trace management file (aa....aa) cannot be opened.
- Action
-
Confirm that permission is available to access the trace management file.
-
KDJE52904-E
The trace management file "aa....aa" information is incorrect. (file name = aa....aa)
aa....aa: Absolute path name of the trace management file
- Description
-
The trace management file (aa....aa) information is incorrect.
- Action
-
Confirm that the server acquires the specified trace.
-
KDJE52905-E
The trace file does not exist.
- Description
-
The trace file does not exist.
- Action
-
Confirm that the specified server is running.
-
KDJE52906-E
The trace file cannot be opened. (file name = aa....aa)
aa....aa: Absolute path name of the trace file
- Description
-
The trace file cannot be opened.
- Action
-
Confirm that permission is available to access the trace file.
-
KDJE52907-I
The data in memory was written to the trace file "aa....aa".
aa....aa: Absolute path name of the trace file
- Description
-
The data in memory was written to the trace file aa....aa.
-
KDJE52909-W
An invalid property has been 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 of property
- Description
-
An invalid property value was specified. The default value will be used.
- Action
-
Revise the specified value of the property aa....aa.
-
KDJE52911-W
The format name is invalid. The default format name 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 name is invalid. The default format name will be used.
- Action
-
An invalid format name might be used. Revise the format name.
-
KDJE52912-W
The string specified in the property exceeded "dd....dd" 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
dd....dd: Specified number of characters
- Description
-
The character string specified in the property has exceeded dd....dd characters. The default value will be used (aa....aa = bb....bb, default value = cc....cc).
- Action
-
The character string specified in the property value has exceeded the maximum number of characters that can be specified in the property value.
Reduce the number of characters to be specified.
-
KDJE52913-W
The same format name is already specified in the property. 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 same format name is specified in the property. The default value will be used.
- Action
-
A duplicate format name might be used in the format list. Specify a format name that does not duplicate with another format name.
-
KDJE52914-W
One of the reserved words "common" or "combined" has been 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 of property
- Description
-
The reserved words "common" and "combined" are specified. The default value will be used.
- Action
-
You cannot change the format because "common" and "combined" are the reserved formats.
-
KDJE52915-W
An invalid format name has been 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 of property
- Description
-
An invalid format name is specified. The default value will be used.
- Action
-
Specify the characters that can be specified as the format name.
-
KDJE52916-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 exceeded 1,024 characters. The default value will be used.
- Action
-
Reduce the number of characters to be specified in the property value.
-
KDJE52917-W
An undefined format name has been 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 of property
- Description
-
An undefined format name is specified. The default value will be used.
- Action
-
Confirm that bb....bb is specified in the format list.
-
KDJE52918-W
The undefined format argument "aa....aa" has been specified. The default value will be used.
aa....aa: Undefined format
- Description
-
The undefined format argument (aa....aa) is specified. The default value will be used.
- Action
-
Specify the defined format argument.
-
KDJE52920-E
An error occurred while writing the message aa....aa to the file bb....bb.
aa....aa: Contents of the message to be output
bb....bb: Path name
- Description
-
An error occurred while writing the message (aa....aa) to the file bb....bb.
Take action based on the following causes:
-
Insufficient free disk space
-
Failure in the disk device
-
- Action
-
Take action depending on the cause.
- Insufficient free disk space
-
Delete the unnecessary files to increase the available space at the output destination or change to an output destination with available space.
- Failure in the disk device
-
Contact System Administrator and replace the device.
If the above-mentioned factors are not applicable, contact maintenance personnel.
-
KDJE52921-E
The output stream for file "aa....aa" could not be opened.
aa....aa: path name
- Description
-
The writing stream for file aa....aa cannot be opened.
- Action
-
Confirm that write permission is available to the file aa....aa. If write permission is not available, assign the write permission.
-
KDJE52922-E
The trace management file cannot be created.
- Description
-
The trace management file cannot be created.
- Action
-
Take action based on the following causes:
-
Insufficient free disk space
Delete the unnecessary files to increase the available space at the output destination or change to an output destination with available space.
-
Failure in the disk device
If the disk device is broken, contact the system administrator and replace the device. If this cause is not applicable, contact maintenance personnel.
-
No access permission
Check the access permission to the Cosminexus-installation-directory\CC\spool\server-name directory.
-
-
KDJE52923-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.
-
KDJE52924-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.
-
KDJE53400-I
A JSP file was successfully translated. (date = aa....aa, JSP file = bb....bb, java file = cc....cc)
aa....aa: java file generation date
(If the java file is not generated by the -d:non option, the translation completion time of the jsp file)
bb....bb: Absolute path of the specified JSP file
cc....cc: Absolute path of the generated java file
(If the java file is not generated by the -d:non option, "" (null character))
- Description
-
An attempt to translate the JSP file was successful.
-
KDJE53401-E
Usage: aa....aa
aa....aa: the cjjsp2java command format
- Description
-
The argument of the cjjsp2java command is incorrect. The usage will be output.
- Action
-
Specify the argument of the cjjsp2java command correctly, and then re-execute the cjjsp2java command.
-
KDJE53402-W
A taglib uri has been specified more than once. (taglib uri = aa....aa, taglib location = bb....bb)
aa....aa: uri specified in the -taglib option
bb....bb: location specified in the -taglib option
- Description
-
The uri is specified more than once in the -taglib option.
- Action
-
Specify a value that is not repeated in the uri of the -taglib option.
-
KDJE53403-E
The specified directory could not be accessed. (directory = aa....aa)
aa....aa: Directory that cannot be accessed
- Description
-
The directory specified in -d option and -root option or their sub directories cannot be accessed.
- Action
-
Specify the settings such that the specified directory can be accessed, and then re-execute the cjjsp2java command.
-
KDJE53404-E
The specified JSP file name is incorrect. (JSP file = aa....aa)
aa....aa: Specified JSP file name
- Description
-
The JSP file name is invalid.
Take action based on the following causes:
-
The JSP file does not exist.
-
Permission is not available to access the JSP file.
-
The extension is not lower case ".jsp".
-
- Action
-
Specify a JSP file with extension ".jsp" that can be accessed, and then re-execute the cjjsp2java command.
-
KDJE53405-E
A JAR file could not be accessed. (JAR file = aa....aa)
aa....aa: JAR file under WEB-INF/lib folder
- Description
-
A JAR file cannot be accessed.
- Action
-
Specify the setting such that the JAR file can be accessed, and then re-execute the cjjsp2java command.
-
KDJE53406-E
The specified classpath is incorrect. (directory = aa....aa)
aa....aa: Specified class path
- Description
-
The specified classpath is incorrect.
- Action
-
Specify an appropriate class path, and then re-execute the cjjsp2java command.
-
KDJE53407-E
An unexpected error occurred during an attempt to translate a JSP file. (JSP file = aa....aa, message = bb....bb)
aa....aa: JSP file name
bb....bb: Error message of exception
- Description
-
An unexpected exception occurred during an attempt to translate a JSP file.
- Action
-
See the error message of the exception and check whether any problem exists.
If no problem exists, contact maintenance personnel.
-
KDJE53408-W
The specified JSP file path is invalid. (JSP file = aa....aa)
aa....aa: JSP file name
- Description
-
The specified JSP file path is invalid.
The specified JSP file does not exist under the directory specified in the -root option, hence, JSP translation will be ignored.
- Action
-
Specify a JSP file that exists under the directory specified in the -root option.
-
KDJE53409-E
An attempt to create a java file has failed. (java file = aa....aa)
aa....aa: Name of the java file that you tried to create
- Description
-
A Java file cannot be created.
- Action
-
Specify the settings such that the Java file can be created, and then re-execute the cjjsp2java command.
-
KDJE53410-E
The output directory could not be accessed. (directory = aa....aa)
aa....aa: Output destination directory of java file
- Description
-
The Java file output destination directory cannot be accessed.
- Action
-
Specify the settings such that the Java file output destination directory can be accessed, and then re-execute the cjjsp2java command.
-
KDJE53411-E
The output directory could not be created. (directory = aa....aa)
aa....aa: Output destination directory of java file
- Description
-
The Java file output destination directory cannot be created.
- Action
-
Remove the causes due to which the Java file output destination directory cannot be created, and then re-execute the cjjsp2java command.
The causes due to which the output destination directory cannot be created are as follows:
-
Insufficient disk space.
-
Permission is not available to create the output destination directory.
-
The path length of the output destination directory exceeds the maximum value of the system.
-
A failure occurred in the file system.
-
-
KDJE53412-E
An attempt to delete a java file generated from the JSP file has failed. (java file = aa....aa)
aa....aa: Name of the java file that could not be deleted
- Description
-
An attempt to delete a Java file, whose generation process was interrupted due to an error during JSP translation, has failed.
- Action
-
Remove the causes of the error occurring during file deletion.
Take action based on the following causes:
-
File deletion permission is not available.
-
The file is open.
-
-
KDJE53413-E
The web application directory specified in the -root option was not found. (directory = aa....aa)
aa....aa: Absolute path of the specified directory
- Description
-
The Web application root directory specified in the -root option does not exist or permission is not available to access the root directory.
- Action
-
Remove the problem due to which the specified directory cannot be accessed, and then re-execute the cjjspc command. Take action based on the following causes:
-
A non-existing directory is specified.
-
Permission is not available to read the directory.
-
A file is specified.
-
The file system has failed.
-
-
KDJE53414-E
An attempt to read the excluded files from compilation listed file has failed. (file = aa....aa)
aa....aa: Absolute path of the specified compilation exclusion list file
- Description
-
An attempt to read the compilation exclusion list file has failed.
- Action
-
Remove the problem due to which the compilation exclusion list file cannot be accessed, and then re-execute the cjjspc command. Take action based on the following causes:
-
A non-existing file is specified.
-
Permission is not available to read the file.
-
The file system has failed.
-
-
KDJE53417-E
The specified JSP file was not found. (file = aa....aa)
aa....aa: Path within the Web application of the JSP file
- Description
-
The specified JSP file was not found.
- Action
-
Remove the problem due to which the specified JSP file cannot be accessed, and then re-execute the cjjspc command. Take action based on the following causes:
-
A non-existing file is specified.
-
Permission is not available to read the file.
-
A directory is specified.
-
The file system has failed.
-
-
KDJE53418-E
A value specified in a command option is invalid. (option = aa....aa, value = bb....bb)
aa....aa: Option name
bb....bb: Specified value
- Description
-
A value specified in a command option is invalid.
- Action
-
Specify a valid value in the option, and then re-execute the cjjspc command.
-
KDJE53419-E
The file path specified in -excludefile is invalid. (file = aa....aa)
aa....aa: Specified file path
- Description
-
The specified compilation exclusion JSP file path is invalid.
- Action
-
In the compilation exclusion JSP file path, specify the relative path from the root directory of the Web application beginning with a forward slash (/).
-
KDJE53420-E
An attempt to create a execution results listed file has failed. (file = aa....aa)
aa....aa: Absolute path of the execution result list file
- Description
-
An attempt to create the execution result list file has failed.
- Action
-
Remove the problem due to which the execution result list file cannot be created, and then re-execute the cjjspc command. Take action based on the following causes:
-
A non-existing directory is specified.
-
Permission is not available to access the file.
-
A directory is specified.
-
The available disk space is insufficient.
-
The file system has failed.
-
-
KDJE53421-E
An error occurred while writing to the execution results listed file. (path of execution results listed file = aa....aa)
aa....aa: Absolute path of the execution result list file
- Description
-
An error occurred while writing to the execution result list file.
- Action
-
Remove the problem due to which there was a failure in writing to the execution result list file, and then re-execute the cjjspc command. Take action based on the following causes:
-
The available disk space is insufficient.
-
The file system has failed.
-
-
KDJE53422-E
A reserved word cannot be specified for the JSP work directory. (specified string = aa....aa)
aa....aa: Specified string
- Description
-
The specified string is specified in the reserved word. A reserved word cannot be specified for the JSP work directory name.
- Action
-
You cannot use "lib", "tags", "classes" (not case sensitive) in the -jspworkdir option. Revise the specified directory name, and then re-execute the cjjspc command.
-
KDJE53423-E
The specified excluded files from compilation listed file was not found. (file = aa....aa)
aa....aa: Absolute path of the compilation exclusion list file
- Description
-
The specified compilation exclusion list file was not found.
- Action
-
Remove the problem due to which the compilation exclusion list file cannot be accessed, and then re-execute the cjjspc command. Take action based on the following causes:
-
A non-existing file is specified.
-
Permission is not available to read the file.
-
A directory is specified.
-
The file system has failed.
-
-
KDJE53424-E
The line aa....aa of the excluded files from compilation listed file is invalid. (file = bb....bb)
aa....aa: Line number
bb....bb: Absolute path of the compilation exclusion list file
- Description
-
The file format of the specified compilation exclusion list file is invalid.
- Action
-
From the compilation exclusion list file contents, confirm that the compilation exclusion JSP file path is the relative path from the root directory of the Web application beginning with a forward slash (/).
-
KDJE53427-E
An option has been specified more than once. (option = aa....aa)
aa....aa: Specified option name
- Description
-
The same option is specified more than once.
- Action
-
Specify a valid option, and then re-execute the cjjspc command.
-
KDJE53429-E
Usage: cjjspc [-jspworkdir JSP-work-dir] [-classpath path] [-excludefile JSP-file-path | -excludelist path] [-keepgenerated] [-source {1.3 | 1.4 | 1.5 | 5 | 1.6 | 6 | 1.7 | 7 | 1.8 | 8}] [-pageencoding encoding] [-resultlist path] [-customactiondeclarevariable] [-usebeannocheckclass] [-tagnocheckrtexprvalue] [-tagrtexprvalueterminate] [-taglibnocheckprefix] [-debugging] [-customactionignorecaseattributename] [-usebeannocheckduplicateid] [-jsppagedisablebom] [-nojavaeetaglib] [-lowerversion {2.4 | 2.5}] [-addimport class-name] -root Web- application-root-dir [ JSP-file-path...]
- Description
-
The argument of the cjjspc command is incorrect. The usage will be output.
- Action
-
Specify the argument of the cjjspc command correctly, and then re-execute the cjjspc command. For details on the command arguments, see cjjspc (pre-compile JSP) in the uCosminexus Application Server Command Reference Guide.
-
KDJE53430-E
The -excludelist and -excludefile options can not be specified together.
- Description
-
The -excludelist and -excludefile options cannot be specified together.
- Action
-
Specify only one option out of the -excludefile or -excludelist, and then re-execute the cjjspc command.
-
KDJE53431-E
The -root option is not specified.
- Description
-
The -root option is not specified.
- Action
-
Specify the -root option, and then re-execute the cjjspc command.
-
KDJE53434-E
The invalid option is specified. (option = aa....aa)
aa....aa: Specified option name
- Description
-
An invalid option was specified.
- Action
-
Specify a valid option, and then re-execute the cjjspc command.
-
KDJE53438-E
The invalid classpath is specified. (classpath = aa....aa)
aa....aa: Specified class path
- Description
-
An invalid classpath is specified in the -classpath option.
- Action
-
Remove the problem due to which the class path cannot be accessed, and then re-execute the cjjspc command. Take action based on the following causes:
-
A non-existing file or directory is specified.
-
Permission is not available to read the file or directory.
-
The file system has failed.
-
-
KDJE53439-E
The invalid JSP file path is specified. (file = aa....aa)
aa....aa: Specified file path
- Description
-
An invalid JSP file path was specified.
- Action
-
In the JSP file path, specify the relative path from the root directory of the Web application beginning with a forward slash (/).
-
KDJE53440-E
The specified file is not JSP file. (file = aa....aa)
aa....aa: Path of the specified file in the Web application
- Description
-
The specified file is not a JSP file.
- Action
-
Specify the JSP file.
The values of the following tags specified in web.xml might also be incorrect:
-
<servlet><jsp-file> value
-
<jsp-config><jsp-property-group><url-pattern> value (in the case of JSP2.0 or later)
Check these contents, and then re-execute the cjjspc command.
-
-
KDJE53441-E
The specified default encoding of the JSP file is not supported. (encoding = aa....aa)
aa....aa: Specified character encoding
- Description
-
The specified character encoding cannot be used as the character encoding for JSP.
The processing of the command terminates.
- Action
-
The specified character encoding cannot be used as character encoding for a 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 coded include "Formal name for java.nio API" and "Formal name for java.io and java.lang API" and their optional names in the Supported encoding section.
-
KDJE53442-W
The JSP debugging function is enabled.
- Description
-
The JSP debug functionality is enabled.
- Action
-
We recommend not using the JSP debug functionality in the execution environment because of its effect on the following performances:
-
Increase in the usage of Metaspace area
-
Increase in parsing during class loading
-
-
KDJE53603-Earea
The JavaBeans resource cannot be stopped while it is being used. (resource name = aa....aa)
aa....aa: JavaBeans resource name
- Description
-
An attempt to stop the JavaBeans resource that is being used has failed.
- Action
-
Stop the J2EE application that is using the JavaBeans resource, and then re-execute the operation.
-
KDJE53604-E
An attempt to start the JavaBeans resource aa....aa has failed. (detail = bb....bb)
aa....aa: JavaBeans resource name
bb....bb: Detailed message
- Description
-
An attempt to start the JavaBeans resource has failed.
- Action
-
See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action.
-
KDJE53605-E
An attempt to stop the JavaBeans resource aa....aa has failed. (detail = bb....bb)
aa....aa: JavaBeans resource name
bb....bb: Detailed message
- Description
-
An attempt to stop the JavaBeans resource has failed.
- Action
-
See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action.
-
KDJE53606-E
An unexpected exception occurred. (detail = aa....aa)
aa....aa: Details
- Description
-
An unexpected exception occurred.
- Action
-
See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact maintenance personnel.
-
KDJE53607-E
The JavaBeans resource class was not found. (class name = aa....aa)
aa....aa: JavaBeans class name
- Description
-
The JavaBeans resource class was not found.
- Action
-
Confirm that the JavaBeans resource class is specified correctly.
-
KDJE53608-E
There is a mismatch on the method name or the argument type of the JavaBeans method. (method name = aa....aa, type = bb....bb, value = cc....cc)
aa....aa: Method name
bb....bb: Argument type
cc....cc: Argument value
- Description
-
The method name or the argument type of the JavaBeans method does not match.
- Action
-
Confirm that the method name or the argument type of the JavaBeans method match.
-
KDJE53609-E
The value of the JavaBeans method argument is invalid. (method name = aa....aa, type = bb....bb, value = cc....cc)
aa....aa: Method name
bb....bb: Argument type
cc....cc: Argument value
- Description
-
The value of the JavaBeans method argument is invalid.
- Action
-
Confirm that the value of the JavaBeans method argument matches with the type.
-
KDJE53610-E
An error occurred during invocation of a JavaBeans method. (method name = aa....aa, type = bb....bb, value = cc....cc, error details = dd....dd)
aa....aa: Method name
bb....bb: Argument type
cc....cc: Argument value
dd....dd: Details
- Description
-
An error occurred during the invocation of JavaBeans method.
- Action
-
See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact maintenance personnel.
-
KDJE53800-W
The usrconf.properties property specification is invalid. The default value will be used. (property = aa....aa, default = bb....bb)
aa....aa: Property key
bb....bb: Default value
- Description
-
The invalid characters are specified in the property key. The default value will be used.
- Action
-
Check the specified value of aa....aa set in usrconf.properties.
-
KDJE53810-E
The directory for statistics files could not be created. (directory = aa....aa, details = bb....bb)
aa....aa: Statistics files output destination directory
bb....bb: Detailed message
- Description
-
The output destination directory for statistics files cannot be created.
- Action
-
Check the details, and then restart the J2EE server.
-
KDJE53811-W
A statistics file could not be updated. (file = aa....aa, details = bb....bb)
aa....aa: Statistics file
bb....bb: Details
- Description
-
A statistics file cannot be updated.
- Action
-
Take action based on the following causes:
-
Permission is not available to write to the statistics file output destination directory.
-
A directory with same name exists in the statistics file output destination directory.
-
The statistics file is opened by another process.
-
The header file is opened by another process.
-
The disk space is depleting.
Check the details, and then remove the causes of the error.
-
-
KDJE53812-E
An unexpected exception occurred. (details = aa....aa)
aa....aa: Details
- Description
-
An unexpected error occurred.
- Action
-
Check the details, and then take action. If the cause is unknown, acquire the maintenance information, and then contact maintenance personnel.
-
KDJE53850-W
The full garbage collection count became equal to or higher than the threshold. (threshold = aa....aa, count = bb....bb, sequence number = cc....cc, monitoring interval = dd....dd)
aa....aa: Threshold value
bb....bb: Occurrence frequency of the Full GC
cc....cc: Occurrence frequency of the threshold value event
dd....dd: Threshold value monitoring interval
- Description
-
The Full GC count became equal to or higher than the threshold value.
- Action
-
Check whether the setting of heap memory size is proper because Full GC occurs frequently. Make sure that there is no memory leakage in the application.
-
KDJE53860-W
The % of requests of the URL group waiting for execution reached the warning range. (J2EE application = aa....aa, Web application = bb....bb, context root = cc....cc, URL group thread control name = dd....dd, rate = ee....ee, current value = ff....ff, max = gg....gg, upper threshold = hh....hh, lower threshold = ii....ii)
aa....aa: J2EE application name
bb....bb: Web application name
cc....cc: Context root name
dd....dd: Control definition name of the number of concurrently executing threads of a URL group
ee....ee: Ratio (%) of current value to maximum number of pending requests of each URL group
ff....ff: Current value of the number of pending requests of each URL group
gg....gg: Maximum number [set value] of pending requests of each URL group
hh....hh: Upper threshold value (%)[set value] for monitoring the number of pending requests of each URL group
ii....ii: Lower threshold value (%)[set value] for monitoring the number of pending requests of each URL group
- Description
-
The percentage of the pending requests of each URL group reached the warning range.
- Action
-
Take action based on the following causes:
-
Inappropriate settings for the number of threads executed concurrently for the URL groups.
-
Inappropriate settings for the warning range.
-
There are requests exceeding the processing performance of the J2EE server.
-
There is a request with an unduly long processing time.
-
The processing performance of the J2EE server is declining because of frequent occurrence of the Full GC.
-
-
KDJE53861-I
The % of requests of the URL group waiting for execution returned to the normal range. (J2EE application = aa....aa, Web application = bb....bb, context root = cc....cc, URL group thread control name = dd....dd, rate = ee....ee, current value = ff....ff, max = gg....gg, upper threshold = hh....hh, lower threshold = ii....ii)
aa....aa: J2EE application name
bb....bb: Web application name
cc....cc: Context root name
dd....dd: Control definition name of the number of concurrently executing threads of a URL group
ee....ee: Ratio (%) of current value to maximum number of pending requests of each URL group
ff....ff: Current value of the number of pending requests of each URL group
gg....gg: Maximum number [set value] of pending requests of each URL group
hh....hh: Upper threshold value (%)[set value] for monitoring the number of pending requests of each URL group
ii....ii: Lower threshold value (%)[set value] for monitoring the number of pending requests of each URL group
- Description
-
The percentage of the pending requests of each URL group returned to the normal range.
-
KDJE53862-W
The percentage of all Web container requests awaiting execution exceeded the warning threshold. (J2EE server name = aa....aa, percentage = bb....bb, current value = cc....cc, maximum value = dd....dd, upper limit = ee....ee, lower limit = ff....ff)
aa....aa: J2EE server name
bb....bb: Ratio (%) of current value to the maximum number of total pending requests
cc....cc: Current value of the total number of pending requests
dd....dd: Maximum number of total pending requests [set value]
ee....ee: Upper threshold value (%) for monitoring the total number of pending requests [set value]
ff....ff: Lower threshold value (%) for monitoring the total number of pending requests [set value]
- Description
-
The percentage of total number of pending requests for all Web containers has reached the warning level.
- Action
-
The possible causes are as follows:
Take action based on the applicable causes.
-
Inappropriate settings for the number of concurrently executed threads.
-
Inappropriate settings for the warning range.
-
There are requests exceeding the processing performance of the J2EE server.
-
There are requests with an unduly long processing time.
-
The processing performance of the J2EE server is declining because of frequent occurrence of the Full GC.
-
-
KDJE53863-I
The percentage of all Web container requests awaiting execution returned to a normal level. (J2EE server name = aa....aa, percentage = bb....bb, current value = cc....cc, maximum value = dd....dd, upper limit = ee....ee, lower limit = ff....ff)
aa....aa: J2EE server name
bb....bb: Ratio (%) of current value to the maximum number of total pending requests
cc....cc: Current value of the total number of pending requests
dd....dd: Maximum number of total pending requests [set value]
ee....ee: Upper threshold value (%) for monitoring the total number of pending requests [set value]
ff....ff: Lower threshold value (%) for monitoring the total number of pending requests [set value]
- Description
-
The percentage of the total number of pending requests for all Web containers has returned to a normal level.
-
KDJE53864-W
The percentage of Web container requests awaiting execution exceeded the warning threshold. (J2EE server name = aa....aa, percentage = bb....bb, current value = cc....cc, maximum value = dd....dd, upper limit = ee....ee, lower limit = ff....ff)
aa....aa: J2EE server name
bb....bb: Ratio (%) of current value to maximum number of pending requests
cc....cc: Current value of the number of pending requests
dd....dd: Maximum number of pending requests [set value]
ee....ee: Upper threshold value (%) for monitoring the number of pending requests [set value]
ff....ff: Lower threshold value (%) for monitoring the number of pending requests [set value]
- Description
-
The percentage of the pending requests for all Web containers has reached the warning level.
- Action
-
The possible causes are as follows:
Take action based on the applicable causes.
-
Inappropriate settings for the number of concurrently executed threads.
-
Inappropriate settings for the warning range.
-
There are requests exceeding the processing performance of the J2EE server.
-
There are requests with an unduly long processing time.
-
The processing performance of the J2EE server is declining because of frequent occurrence of the Full GC.
-
-
KDJE53865-I
The percentage of all Web container requests awaiting execution returned to a normal level. (J2EE server name = aa....aa, percentage = bb....bb, current value = cc....cc, maximum value = dd....dd, upper limit = ee....ee, lower limit = ff....ff)
aa....aa: J2EE server name
bb....bb: Ratio (%) of current value to maximum number of pending requests
cc....cc: Current value of the number of pending requests
dd....dd: Maximum number of pending requests [set value]
ee....ee: Upper threshold value (%) for monitoring the number of pending requests [set value]
ff....ff: Lower threshold value (%) for monitoring the number of pending requests [set value]
- Description
-
The percentage of the pending requests for all Web containers has returned to a normal level.
-
KDJE53866-W
The percentage of all Web application requests awaiting execution exceeded the warning threshold. (J2EE application name = aa....aa, Web application name = bb....bb, context root = cc....cc, percentage = dd....dd, current value = ee....ee, maximum value = ff....ff, upper limit = gg....gg, lower limit = hh....hh)
aa....aa: J2EE application name
bb....bb: Web application name
cc....cc: Context root
dd....dd: Ratio (%) of current value to the maximum number of total pending requests
ee....ee: Current value of the total number of pending requests
ff....ff: Maximum number of total pending requests [set value]
gg....gg: Upper threshold value (%) for monitoring the total number of pending requests [set value]
hh....hh: Lower threshold value (%) for monitoring the total number of pending requests [set value]
- Description
-
The percentage of the pending requests for the Web application has reached the warning level.
- Action
-
The possible causes are as follows:
Take action based on the applicable causes.
-
Inappropriate settings for the number of concurrently executed threads.
-
Inappropriate settings for the warning range.
-
There are requests exceeding the processing performance of the J2EE server.
-
There are requests with an unduly long processing time.
-
The processing performance of the J2EE server is declining because of frequent occurrence of the Full GC.
-
-
KDJE53867-I
The percentage of all Web application requests awaiting execution returned to a normal level. (J2EE application name = aa....aa, Web application name = bb....bb, context root = cc....cc, percentage = dd....dd, current value = ee....ee, maximum value = ff....ff, upper limit = gg....gg, lower limit = hh....hh)
aa....aa: J2EE application name
bb....bb: Web application name
cc....cc: Context root
dd....dd: Ratio (%) of current value to the maximum number of total pending requests
ee....ee: Current value of the total number of pending requests
ff....ff: Maximum number of total pending requests [set value]
gg....gg: Upper threshold value (%) for monitoring the total number of pending requests [set value]
hh....hh: Lower threshold value (%) for monitoring the total number of pending requests [set value]
- Description
-
The percentage of the pending requests for the Web application has returned to a normal level.
-
KDJE53868-W
The percentage of Web application requests awaiting execution exceeded the warning threshold. (J2EE application name = aa....aa, Web application name = bb....bb, context root = cc....cc, percentage = dd....dd, current value = ee....ee, maximum value = ff....ff, upper limit = gg....gg, lower limit = hh....hh)
aa....aa: J2EE application name
bb....bb: Web application name
cc....cc: Context root
dd....dd: Ratio (%) of current value to maximum number of pending requests
ee....ee: Current value of the number of pending requests
ff....ff: Maximum number of pending requests [set value]
gg....gg: Upper threshold value (%) for monitoring the number of pending requests [set value]
hh....hh: Lower threshold value (%) for monitoring the number of pending requests [set value]
- Description
-
The percentage of the pending requests for the Web application has reached the warning level.
- Action
-
The possible causes are as follows:
Take action based on the applicable causes.
-
Inappropriate settings for the number of concurrently executed threads.
-
Inappropriate settings for the warning range.
-
There are requests exceeding the processing performance of the J2EE server.
-
There are requests with an unduly long processing time.
-
The processing performance of the J2EE server is declining because of frequent occurrence of the Full GC.
-
-
KDJE53869-I
The percentage of Web application requests awaiting execution returned to a normal level. (J2EE application name = aa....aa, Web application name = bb....bb, context root = cc....cc, percentage = dd....dd, current value = ee....ee, maximum value = ff....ff, upper limit = gg....gg, lower limit = hh....hh)
aa....aa: J2EE application name
bb....bb: Web application name
cc....cc: Context root
dd....dd: Ratio (%) of current value to maximum number of pending requests
ee....ee: Current value of the number of pending requests
ff....ff: Maximum number of pending requests [set value]
gg....gg: Upper threshold value (%) for monitoring the number of pending requests [set value]
hh....hh: Lower threshold value (%) for monitoring the number of pending requests [set value]
- Description
-
The percentage of the pending requests for the Web application has returned to a normal level.
-
KDJE53900-E
An exception occurred during Dependency Injection. (target class = aa....aa, target name = bb....bb, detail = cc....cc)
aa....aa: DI target class name
bb....bb: DI target name
cc....cc: Details
- Description
-
An error occurred during the Dependency Injection.
- Action
-
When the applications starts, check if the message KDJE53905-W is output and if output, follow the action described in the message KDJE53905-W.
See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact maintenance personnel.
-
KDJE53901-E
An exception occurred during creation of information required for Dependency Injection. (detail = aa....aa)
aa....aa: Details
- Description
-
An exception occurred during creation of information required for Dependency Injection.
- Action
-
See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact maintenance personnel.
-
KDJE53902-E
In the target class, there is no target field or method that corresponds to the reference type and the target name of Dependency Injection. (reference type = aa....aa, target class = bb....bb, target name = cc....cc)
aa....aa: Reference type
bb....bb: DI target class name
cc....cc: DI target name
- Description
-
The target class does not contain a field or method that corresponds to the reference type and the target name of the defined Dependency Injection.
- Action
-
Check whether DI enabled field or setter method exists in the corresponding class for the corresponding target name and the reference type. If the target field or method does not exist, add it.
-
KDJE53903-E
The definition of Dependency Injection is invalid. (reference type = aa....aa, target class = bb....bb, detail = cc....cc)
aa....aa: Reference type
bb....bb: DI target class name
cc....cc: Details
- Description
-
The definition of Dependency Injection is invalid.
- Action
-
See the details, and then take action.
-
KDJE53904-W
During reloading, information required for Dependency Injection could not be created. (target class = aa....aa, target name = bb....bb, detail = cc....cc)
aa....aa: DI target class name
bb....bb: DI target name
cc....cc: Details
- Description
-
During reloading, information required for Dependency Injection cannot be created.
- Action
-
See the details, modify the application, and execute reloading again. If the process is continued, the Dependency Injection performed during the generation of the DI target class instances will fail.
-
KDJE53905-W
The specified value for the tag in the deployment descriptor is invalid. If you continue, dependency injection will fail. (reference type = aa....aa, target class = bb....bb, target name = cc....cc)
aa....aa: Reference type
bb....bb: DI target class name
cc....cc: DI target name
- Description
-
The value specified in the tag of the Deployment Descriptor is invalid. If you continue, Dependency Injection will fail.
Take action based on the following causes:
-
The class specified in the <injection-target-class> tag does not exist.
-
The set method corresponding to the value specified in the <injection-target-name> tag does not exist. Alternatively, the set method exists, but the type of the arguments is not an appropriate type as the target.
-
A field with the same name as the value specified in the <injection-target-name> tag does not exist. Alternatively, the field exists, but the type of the field is not an appropriate type as the target.
-
- Action
-
Revise the definition of the Deployment Descriptor or the application.
-
KDJE53906-E
An exception occurred during execution of a method annotated with PostConstruct. (J2EE application = aa....aa, context root = bb....bb, class = cc....cc, detail = dd....dd)
aa....aa: J2EE application name
bb....bb: Context root name
cc....cc: Class name
dd....dd: Detailed information of the occurred exception
- Description
-
An exception occurred during the execution of a method annotated with PostConstruct.
- Action
-
See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact maintenance personnel.
-
KDJE53907-W
An exception occurred during execution of a method annotated with PreDestroy. (J2EE application = aa....aa, context root = bb....bb, class = cc....cc, detail = dd....dd)
aa....aa: J2EE application name
bb....bb: Context root name
cc....cc: Class name
dd....dd: Detailed information of the occurred exception
- Description
-
An exception occurred during the execution of a method annotated with PreDestroy.
- Action
-
See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact maintenance personnel.
-
KDJE54000-I
The database audit trail linkage functionality has been enabled. (linkable database = aa....aa)
aa....aa: Database name that can be linked
- Description
-
The database audit trail linkage functionality has been enabled.
-
KDJE54001-W
The environment does not support the database audit trail linkage functionality.
- Description
-
The environment for using the database audit trail linkage functionality has not been arranged. You must check if the database audit trail linkage functionality can be used in the environment.
- Action
-
Check if the database audit trail linkage functionality can be used in the environment.
A JAR file of the JDBC driver that fulfills the following two conditions must be specified in usrconf.cfg:
-
JAR file of the JDBC driver provided in a database in which the database audit trail linkage functionality can be used.
-
JAR file of the JDBC driver that is of a version in which the database audit trail linkage functionality can be used.
-
-
KDJE54002-W
An invalid property value was specified. The default value (cc....cc) will be used. (aa....aa = bb....bb)
aa....aa: Property name
bb....bb: Property value
cc....cc: Default value
- Description
-
An invalid property value was specified. The default value (cc....cc) will be used.
- Action
-
Specify a correct value.
-
KDJE54003-E
An unexpected error occurred during initialization of the database audit trail linkage functionality. (details = aa....aa)
aa....aa: Error details
- Description
-
An unexpected exception occurred during the initialization of the database audit trail linkage functionality.
The J2EE server startup will be cancelled.
- Action
-
Acquire the maintenance information, and then contact maintenance personnel.
-
KDJE54051-E
An unexpected error occurred during setting of audit trail information for the database. (rootAP = aa....aa, details = bb....bb)
aa....aa: Root application information
bb....bb: Error details
- Description
-
An unexpected exception occurred when setting up the audit trail information in the database. The root application information will not be output in the audit trail information of the database.
- Action
-
Acquire the maintenance information, and then contact maintenance personnel.
Furthermore, collect the database maintenance information.