uCosminexus Application Server Messages

3021-3-J27-10(E)

Notices

Relevant program products

See the Release Notes.

Export restrictions

If you export this product, please check all restrictions (for example, Japan's Foreign Exchange and Foreign Trade Law, and USA export control laws and regulations), and carry out all required procedures.

If you require more information or clarification, please contact your Hitachi sales representative.

Trademarks

HITACHI, Cosminexus, DABroker, HiRDB, JP1, OpenTP1, TPBroker, uCosminexus, XDM are either trademarks or registered trademarks of Hitachi, Ltd. in Japan and other countries.

AIX is a trademark of International Business Machines Corporation, registered in many jurisdictions worldwide.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Microsoft, Windows are trademarks of the Microsoft group of companies.

Microsoft, Windows Server are trademarks of the Microsoft group of companies.

Microsoft is a trademark of the Microsoft group of companies.

Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

SPARC is a registered trademark of SPARC International, Inc. Products bearing SPARC trademarks are based on an architecture developed by Sun Microsystems, Inc

UNIX is a trademark of The Open Group.

Other company and product names mentioned in this document may be the trademarks of their respective owners.

Eclipse is an open development platform for tools integration provided by Eclipse Foundation, Inc., an open source community for development tool providers.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

Issued

Aug. 2022: 3021-3-J27-10(E)

Copyright

All Rights Reserved. Copyright (C) 2022, Hitachi, Ltd.

Preface

For details on the prerequisites before reading this manual, see the Release Notes.

Non-supported functionality

Some functionality described in this manual is not supported. Non-supported functionality includes:

Audit log functionality

Compatibility functionality

Cosminexus Component Transaction Monitor

Cosminexus Reliable Messaging

Cosminexus TPBroker and VisiBroker

Cosminexus Web Service - Security

Cosminexus XML Security - Core functionality

JP1 linkage functionality

Management Server management portal

Remote installation functionality for the UNIX edition

SOAP applications complying with specifications other than JAX-WS 2.1

uCosminexus OpenTP1 linkage functionality

Virtualized system functionality

XML Processor high-speed parse support functionality

Non-supported compatibility functionality

"Compatibility functionality" in the above list refers to the following functionality:

Basic mode

Check of JSP source compliance (cjjsp2java) with JSP1.1 and JSP1.2 specifications

Database connection using Cosminexus DABroker Library

EJB client application log subdirectory exclusive mode

J2EE application test functionality

Memory session failover functionality

Servlet engine mode

Simple Web server functionality

Switching multiple existing execution environments

Using EJB 2.1 and Servlet 2.4 annotation

Part 1: Overview

1 Overview of Messages

This chapter gives an overview of messages output by Application Servers, and describes the location of the descriptions in this manual.

Application Servers output two types of messages; messages that are output during system setup and operations or during application development, and the audit log messages.

1.1 Types of messages

This section describes the types of Application Server messages.

1.1.1 Messages output when building or operating systems or when developing applications

Messages are output when you build and operate the systems on Application Server or develop applications.

The prefixes of messages correspond to the component software or the functions that output the messages. The following table describes the prefixes and classification of messages output by Application Servers, and the corresponding references. Confirm the corresponding reference sections and manuals of the messages according to the prefixes of the output messages. Note that some of the messages output by Cosminexus HTTP Server, the JAXB functionality of Cosminexus XML Processor, and some messages output during the operation of TPBroker do not have prefixes.

Table 1‒1: Reference sections for the messages output by Application Server

Prefixes

Classification of messages

Reference manuals

Reference locations

KDAL

Messages output by the audit log library functionality

This manual

Chapter 3

KDAN

Messages output by Cosminexus JMS Provider

This manual

Chapter 4

KDCC

Messages output by the SOAP application development support function

This manual

Chapter 5

KDCG

Messages output by the Web Service security functionality

This manual

Chapter 6

KDEC

Messages output by the Cosminexus Service Platform infrastructure

uCosminexus Service Platform Messages

--

KDJE

Messages output by Cosminexus Component Container

This manual

Chapter 7

Messages output by OSS

This manual

Chapter 24

KDJJ

Messages output by Cosminexus Component Container

This manual

Chapter 8

KDJR

This manual

Chapter 9

KDJW

This manual

Chapter 10

KECT

Messages output in the Cosminexus Service Platform development environment

uCosminexus Service Platform Messages

--

KECX

Messages output by Cosminexus XML Processor

This manual

Chapter 11

KEDT

Messages output by Developer

This manual

Chapter 12

KEOS02000 to KEOS29999

Messages output during setup, operations, and maintenance executed using Cosminexus Manager

This manual

Chapter 13

KEOS50000 to KEOS59999

Messages output by HCSC-Manager on Cosminexus Service Platform

uCosminexus Service Platform Messages

--

KEQR

Messages output by the virtual server manager setup tool

This manual

Chapter 14

KEUC

Messages output when the execution environment is switched

This manual

Chapter 15

KEXS

Messages output by Cosminexus XML Security - Core

This manual

Chapter 16

KFCB29000 to KFCB59999

Messages output by TPBroker

This manual

Chapter 17

KFCB91000 to KFCB92999

Messages output during TPBroker operations

This manual

Chapter 18

KFCT

Messages output by CTM and PRF

This manual

Chapter 19

KFDB

Messages output by Cosminexus DABroker Library

This manual

Chapter 20

KFDJ

This manual

Chapter 21

KFRM

Messages output by Cosminexus RM

This manual

Chapter 22

AH

Messages output by the Web server (Cosminexus HTTP Server)

This manual

Chapter 23

KH

Without prefix

Messages output by the JAXB functionality of Cosminexus XML Processor

This manual

25.2

Without prefix

Messages output when errors occur while migrating and importing the work directory

This manual

25.3

Legend:

--: Reference the whole manual.

1.1.2 Audit log messages

When executing commands, audit log messages used for system audit are output.

Prefixes of the messages correspond to the component software or the functionality that output the messages. The following table describes the prefixes, classifications, and reference manuals for the audit log messages output by Application Server.

Table 1‒2: Classifications of the messages described in this manual and the corresponding reference sections of messages

Prefixes

Classification of messages

Reference manuals

Reference locations

KAWS10000 to KAWS19999

Audit log messages output by Cosminexus HTTP Server

uCosminexus Application Server Audit Log Messages

Chapter 3

KDJE54100 to KDJE54999

Audit log messages output by Cosminexus Component Container

uCosminexus Application Server Audit Log Messages

Chapter 4

KEOS80000 to KEOS89999

Audit log messages output by Cosminexus Manager

uCosminexus Application Server Audit Log Messages

Chapter 5

KFCT80000 to KFCT99999

Audit log messages output by CTM and PRF

uCosminexus Application Server Audit Log Messages

Chapter 6

Part 2: Messages Output during System Setup, Operations, and Application Development

2 Overview of Messages Output during System Setup, Operations, and Application Development

This chapter describes the message output destinations and formats as an overview of messages output during system setup and operations or during application development.

2.1 Message output destinations and formats

This section describes the message output destinations and formats.

2.1.1 Message output destinations

The following table describes the output destinations of messages output during system setup and operations or during application development in Application Servers.

Table 2‒1: Output destinations of messages output during system setup and operations or during application development in Application Servers

Prefixes

Classification of messages

Output destination

Remarks

KDAL

Messages output by the audit log library functionality

Standard output or standard error output

Log file

For details on the log file output destination, see 4. Output Destinations and Output Methods of Data Required for Troubleshooting in the uCosminexus Application Server Maintenance and Migration Guide.

KDAN

Messages output by Cosminexus JMS Provider

Event log or syslog

Standard output and standard error output

Log file

GUIs provided by the component software (Web browser and dialog box)

KDCC

Messages output by SOAP application development support function

Trace file

Standard output and standard error output

Elements of the exception classes returned to user-created programs (such as detailed messages)

For details on the exception classes and trace files of the SOAP application development support function and SOAP Communication Infrastructure, see the uCosminexus Application Server SOAP Application Development Guide.

KDCG

Messages output by the Web Service security functionality

Trace files of the SOAP Communication Infrastructure

Trace files of the Web Service security functionality

Standard output and standard error output

Elements of the exception classes of the SOAP Communication Infrastructure, returned to user-created programs (such as detailed messages)

Operation log of the JAX-WS engine

Maintenance log of the JAX-WS engine

For details on the exception classes of the SOAP Communication Infrastructure, see 13. APIs Provided in the SOAP Communication Infrastructure in the uCosminexus Application Server SOAP Application Development Guide. For details on the trace files of the SOAP Communication Infrastructure, see 14.4 Trace files in the uCosminexus Application Server SOAP Application Development Guide.

For details on the trace files of the Web Service security functionality, the operation log of the JAX-WS engine, and the maintenance log of the JAX-WS engine, see 6. Troubleshooting in the uCosminexus Application Server Web Service Security Users Guide.

KDJE

Messages output by Cosminexus Component Container

Event log or syslog

Standard output and standard error output

Log file

GUIs provided by the component software (Web browser and dialog box)

For details on the log file output destination, see 4. Output Destinations and Output Methods of Data Required for Troubleshooting in the uCosminexus Application Server Maintenance and Migration Guide.

Messages output by OSS

Log file

KDJJ

Messages output by Cosminexus Component Container

Log file

Standard output and standard error output

Elements of the exception classes returned to user-created programs (such as detailed messages)

For details on the exception classes and log files, see 13. Settings and Operations of the JAX-RS Functionality in the uCosminexus Application Server Web Service Development Guide.

KDJR

Log file

Standard output and standard error output

Elements of the exception classes returned to user-created programs (such as detailed messages)

--

KDJW

Log file

Standard output and standard error output

Elements of the exception classes returned to user-created programs (such as detailed messages)

For details on the exception classes and log files, see 10. Settings and Operations of the JAX-WS Functionality in the uCosminexus Application Server Web Service Development Guide.

KECX

Messages output by Cosminexus XML Processor

The message output destination depends on the upper-level component or user application.

--

KEDT

Messages output by Developer

Console

Log file

For details on the log file output destination, see 4. Output Destinations and Output Methods of Data Required for Troubleshooting in the uCosminexus Application Server Maintenance and Migration Guide.

KEOS02000 to KEOS29999

Messages output during setup, operation, and maintenance executed using Cosminexus Manager

Event log or syslog

Standard output and standard error output

Log file

GUIs provided by the component software (Web browser and dialog box)

KEQR

Messages output by the virtual server manager setup tool

Console

Log file

KEUC

Messages output when the execution environment is switched

Event log or syslog

Standard output and standard error output

Log file

GUIs provided by the component software (Web browser and dialog box)

--

KEXS

Messages output by Cosminexus XML Security - Core

Standard output

Log file

--

KFCB29000 to KFCB59999

Messages output by TPBroker

Event log or syslog

Standard output and standard error output

Log file

For details on the log file output destination, see 4. Output Destinations and Output Methods of Data Required for Troubleshooting in the uCosminexus Application Server Maintenance and Migration Guide.

KFCB91000 to KFCB92999

Messages output during TPBroker operations

Event log or syslog

Standard output and standard error output

Log file

KFCT

Messages output by CTM and PRF

Event log or syslog

Standard output and standard error output

Log file

GUIs provided by the component software (Web browser and dialog box)

KFDB

Messages output by Cosminexus DABroker Library

Event log or syslog

Standard output and standard error output

Log file

GUIs provided by the component software (Web browser and dialog box)

--

KFDJ

Event log or syslog

Standard output and standard error output

Log file

GUIs provided by the component software (Web browser and dialog box)

KFRM

Messages output by Cosminexus RM

Console of Cosminexus Component Container

Standard output and standard error output

Log file

--

--

Messages output by the Web server (Cosminexus HTTP Server)

Standard output

Standard error output

Error log file

--

--

Messages output by the JAXB functionality of Cosminexus XML Processor

The message output destination depends on the upper-level component or user application.

--

--

Messages output when errors occur while migrating and importing the work directory

The location where this message is output depends on the location where the previous message is output.

--

Legend:

--: Not applicable.

2.1.2 Message output formats

For details on the output format and items of the Application Server messages, see 5.2.1 Output Format and Output Items of the Hitachi Trace Common Library Format Log in the uCosminexus Application Server Maintenance and Migration Guide.

3 KDAL (Messages Output by the Audit Log Library Functionality) (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

3.1 (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

4 KDAN (Messages output by Cosminexus JMS Provider)

This chapter describes the messages that are output by Cosminexus JMS Provider.

4.1 Format for describing the messages

The format for describing the messages in this chapter is as follows:

KDALnnnnn-Y

Message text

Description of variable values

Description

Supplementary description of the message text

Action

Action taken by the user

Note that for some messages, Description about the variable value, Description, and Action might not be described.

Each item is described as follows:

KDANnnnnn

This describes the message ID.

The elements configuring a message ID are as follows:

KDAN

This describes prefixes of the messages output by Cosminexus JMS Provider.

nnnnn

This describes message numbers managed by Cosminexus JMS Provider. A five-digit unique number is attached to each message.

Y

This describes the message level. The message level is indicated by one alphabetic character.

The alphabetic characters indicating the message levels and their meanings are as follows:

E (Error)

This message reports the occurrence of an error-level problem.

When this message is displayed the processing is interrupted.

W (Warning)

This message reports the occurrence of a warning-level problem.

The processing continues even after this message is displayed.

I (Information)

This message reports a system operation.

The processing continues even after this message is displayed.

Q (Question)

This message reports responses of a user for the output message.

When this message is displayed the system waits for the user response.

Message text

This describes the message text output by Cosminexus JMS Provider.

Note that the variable value (value that differs depending upon the status in which the message is output) within the message text is output with the format xx....xx (xx are lower-case alphabetical characters).

Description of variable values

The information displayed in the variable value within the message text is output with the format 'xx....xx: displayed-information' (xx are lower-case alphabetical characters). An example of the format for describing variable values is as follows:

Example:

aa....aa: File name

bb....bb: Application name

Description

This is the supplementary description of the message, such as the factors responsible for reporting the message and operation of the component software that output the message.

Action

This is the action to be taken by the user. Note that 'Contact maintenance personnel' in the action indicates that maintenance personnel need to contact our helpdesk based on the purchase agreement.

4.2 Messages beginning with KDAN

This section describes the messages beginning from KDAN00001 to KDAN99999 that are output by Cosminexus JMS Provider.

KDAN00001-I

Connection ID aa....aa closing. Client ID is bb....bb

aa....aa: Connection ID

bb....bb: Client ID

Description

This message is displayed when the connection is closed.

KDAN00002-I

onEvent() connection event for ManagedConnection aa....aa and event ID bb....bb

aa....aa: Managed connection ID

bb....bb: Event ID

Description

This message is displayed when the connection event generated by client runtime is delivered.

KDAN00003-I

onEvent() connection event for ManagedConnection aa....aa:, event ID bb....bb: and New AddressList= cc....cc:

aa....aa: Managed connection ID

bb....bb: Event ID string

cc....cc: addressList string

Description

This message is displayed when addressList is not null and when the connection event generated by client runtime is provided.

KDAN00004-I

connectionClosed event ID aa....aa cleanup&destroy ManagedConnection bb....bb

aa....aa: Event ID

bb....bb: Managed connection

Description

This message is displayed when the physical connection is closed.

KDAN00005-I

Creating managed connection Id aa....aa Using xa connection factory config bb....bb

aa....aa: Managed connection ID

bb....bb: Managed connection factory

Description

This message is displayed when a Managed connection is set up.

KDAN00006-I

In getConnection() managed connection Id aa....aa XA connection Id bb....bb opening ConnectionAdapter, setting ClientId cc....cc

aa....aa: Managed connection ID

bb....bb: Direct connection ID

cc....cc: Client ID

Description

This message is displayed when a new connection is acquired.

KDAN00008-I

EndpointConsumer Activation Spec aa....aa

aa....aa: Activation Spec (start specifications)

Description

This message is displayed when the onException method of the ExceptionListener interface is invoked.

KDAN00009-I

EndpointConsumer reconnect attempt loop# aa....aa Delayed bb....bb milliseconds.

aa....aa: Loop count

bb....bb: Loop delay

Description

This message is displayed when one or more attempts are made to reconnect the endpoint consumer.

KDAN00010-I

EndpointConsumer reconnect success on loop# aa....aa for bb....bb.

aa....aa: Loop count

bb....bb: Activation Spec (start specifications)

Description

This message is displayed when the endpoint consumer is reconnected normally.

KDAN00012-I

ResourceAdapter JMS Resource Adapter starting...

Description

This message is displayed when the resource adapter is starting.

KDAN00013-I

Resource Adapter Configuration aa....aa

aa....aa: Resource adapter configuration

Description

This message is displayed when the resource adapter configuration information is displayed while starting the resource adapter.

KDAN00014-I

ResourceAdapter JMSRA Connection Factory Config = aa....aa.

aa....aa: XAConnection factory configuration

Description

This message is displayed when the information about the resource adapter connection factory configuration is displayed while starting the resource adapter.

KDAN00015-I

ResourceAdapter JMSRA Started Broker Type = aa....aa.

aa....aa: Broker type

Description

This message is displayed when the Broker type is displayed while starting the resource adapter.

KDAN00016-I

ResourceAdapter JMSRA stopping...

Description

This message is displayed when the resource adapter is stopping.

KDAN00017-I

ResourceAdapter Closing Connection. Connection ID = aa....aa.

aa....aa: Connection ID

Description

This message is displayed when the resource adapter is stopping.

KDAN00018-I

ResourceAdapter JMSRA stopped.

Description

This message is displayed when the resource adapter is stopped.

KDAN00020-I

ResourceAdapter endpointActivation : createMessageConsumer Done. Factory ID = aa....aa Consumer ID = bb....bb.

aa....aa: Factory ID

bb....bb: Consumer ID

Description

This message is displayed after creating the message consumer.

KDAN00023-I

ResourceAdapter endpointDeactivation : stopMessageConsumer. Factory ID = aa....aa Consumer ID = bb....bb.

aa....aa: Factory ID

bb....bb: Consumer ID

Description

This message is displayed when the message consumer is stopped.

KDAN00026-I

ResourceAdapter onException Reconnect unsuccessfull on loop # aa....aa.

aa....aa: Loop count

Description

This message is displayed when the resource adapter cannot be reconnected within the reconnection retry count.

KDAN00027-I

ResourceAdapter onEvent : Connection Event : aa....aa.

aa....aa: Event ID

Description

This message is displayed when the onEvent method of the EventListener interface is invoked.

KDAN00028-I

ResourceAdapter getConnectionURL : returning default of ''localhost'' for empty connectionURL.

Description

This message is displayed when the connection url for resource adapters is acquired.

KDAN00029-I

ResourceAdapter getJMXServiceURLList : addressList component = aa....aa.

aa....aa: Connection url

Description

This message is displayed when JMXServiceURLList for resource adapters is acquired.

KDAN00030-I

ResourceAdapter getJMXServiceURLList : Address= aa....aa.

aa....aa: imq address

Description

This message is displayed after imqAddress for resource adapters is set up.

KDAN00031-I

ResourceAdapter getJMXServiceURLList: JMXServiceURL string for addressList component aa....aa = bb....bb.

aa....aa: Connection url

bb....bb: JMXServiceURL

Description

This message is displayed when JMXServiceURLList for resource adapters is acquired.

KDAN00032-I

ResourceAdapter init done. ResourceAdapter UID = aa....aa.

aa....aa: Resource adapter uid

Description

This message is displayed when the resource adapter connection factory is configured.

KDAN00033-I

ResourceAdapter start : Connection ID = aa....aa.

aa....aa: Connection id

Description

This message is displayed if the Broker type is not direct, when a connection is created.

KDAN03001-W

setResourceAdapter Illegal to re-associate ResourceAdapter aa....aa

aa....aa: Exception message

Description

This message is displayed when the resource adapter Javabean is not integrated with ActivationSpec.

Action

Make sure that the resource adapter Javabean that has already been allocated to the ActivationSpec instance is not allocated.

KDAN03002-W

setResourceAdapter Using default addressList due to setAddressList Exception

Description

When the imqAddressList property is set up, take action based on the following causes:

If the property name is invalid

If the property value is invalid

If an attempt is made to change the set value, when the readOnly flag is set up

Action

Specify a valid property name and value.

KDAN03003-W

setResourceAdapter Using default userName due to setUserName Exception

Description

When the imqDefaultUsername property is set up, take action based on the following causes:

If the property name is invalid

If the property value is invalid

If an attempt is made to change the specified value, when the readOnly flag is set up

Action

Specify a valid property name and value.

KDAN03004-W

setResourceAdapter Using default password due to setPassword Exception

Description

When the imqDefaultPassword property is set up, take action based on the following causes:

If the property name is invalid

If the property value is invalid

If an attempt is made to change the specified value, when the readOnly flag is set up

Action

Specify a valid property name and value.

KDAN03005-W

Property aa....aa is defaulted to bb....bb, Since the value = cc....cc is invalid

aa....aa: Property name

bb....bb: Default property value

cc....cc: User-specified property value

Description

Take action based on the following causes:

When the value of the reconnectAttempts property is less than 1 for the connection factory

When the value of the reconnectInterval property is smaller than 0 (zero) for the connection factory

Action

Do not set up the reconnectAttempts and reconnectInterval properties.

KDAN03007-W

connectionErrorOccurred, event ID aa....aa destroy ManagedConnection bb....bb

aa....aa: Event ID

bb....bb: Managed connection information

Description

This message is displayed when a Managed connection is destroyed.

Action

Contact maintenance personnel for internal errors.

KDAN03009-W

Previously destroyed ManagedConnection Id aa....aa

aa....aa: Managed connection ID

Description

This message is displayed for an already terminated Managed connection.

Action

Make sure that a Managed connection that is not terminated, is specified.

KDAN03010-W

TemporaryDestination delete() Can only delete user created TemporaryDestinations.

Description

This message is displayed when an attempt is made to delete a system-created temporary destination.

Action

Make sure that a user-created temporary destination is used.

KDAN03011-W

TemporaryDestination delete() Cannot delete TemporaryDestination with active consumers.

Description

This message is displayed when active consumers exist in the temporary destination that the user wants to delete.

Action

Make sure that the active consumers are terminated before deleting the temporary destination.

KDAN03012-W

ResourceAdapter - Resource Adapter already Started. Ignoring...

Description

This message is displayed when the resource adapter is already running.

Action

Confirm that the resource adapter has not been started.

KDAN03014-W

ResourceAdapter start:Invalid to perform doInitOnlyOnStart if RA has been started previously and stopped:Ignoring and Resetting doInitOnlyOnStart.

Description

This message is displayed when the resource adapter is already running.

Action

Confirm that the resource adapter has not been started.

KDAN03015-W

ResourceAdapter - Resource Adapter already Stopped. Ignoring...

Description

This message is displayed when the resource adapter is not running.

Action

Check whether the resource adapter has been terminated.

KDAN03016-W

ResourceAdapter onException Connection Failed aa....aa

aa....aa: Exception message

Description

Take action based on the following causes:

When CJMSPBroker was terminated during the execution of the resource adapter

When the connection to CJMSPBroker from the resource adapter is disconnected

Action

If CJMSPBroker is terminated, start CJMSPBroker or perform the operations required for restoring the connection between the resource adapter and CJMSPBroker.

KDAN03017-W

ResourceAdapter onException Reconnecting... Loop Attempt # aa....aa. Delayed bb....bb milliseconds.

aa....aa: Loop count

bb....bb: Delay (milliseconds)

Description

The connection between the resource adapter and CJMSPBroker is disconnected and the resource adapter attempts to connect to CJMSPBroker.

Action

Perform the operations required for restoring the connection between the resource adapter and CJMSPBroker.

KDAN03018-W

ResourceAdapter onException Reconnect successfull on loop # aa....aa.

aa....aa: Loop count

Description

The connection between the resource adapter and CJMSPBroker is disconnected and the resource adapter successfully reconnects to CJMSPBroker.

Action

Since the connection is restored, no action is required.

KDAN03019-W

ResourceAdapter getJMXServiceURL : RA not started. Returning null.

Description

This message is displayed when the resource adapter is not running.

Action

Start the resource adapter.

KDAN03022-W

Property MsgLogFileNum is defaulted to : aa....aa. Since the valid file num should be between 1 to bb....bb.

aa....aa: Default value

bb....bb: Maximum number of files

Description

This message is displayed when an invalid value is specified for the MsgLogFileNum property of the resource adapter.

Action

The valid value for the MsgLogFileNum property of the resource adapter is in the range from 1 to 16 (integer).

KDAN03023-W

Property MsgLogFileSize is defaulted to : aa....aa. Since the valid file size should be between bb....bb to cc....cc.

aa....aa: Default value

bb....bb: Minimum log file size

cc....cc: Maximum log file size

Description

This message is displayed when an invalid value is specified for the MsgLogFileSize property of the resource adapter.

Action

The valid value for the MsgLogFileSize property of the resource adapter is in the range from 8192 to 4194304 (integer).

KDAN03024-W

Property ExpLogFileNum is defaulted to : aa....aa. Since the valid file num should be between 1 to bb....bb.

aa....aa: Default value

bb....bb: Maximum number of files

Description

This message is displayed when an invalid value is specified for the ExpLogFileNum property of the resource adapter.

Action

The valid value for the ExpLogFileNum property of the resource adapter is in the range from 1 to 16 (integer).

KDAN03025-W

Property ExpLogFileSize is defaulted to : aa....aa. Since the valid file size should be between bb....bb to cc....cc.

aa....aa: Default value

bb....bb: Minimum log file size

cc....cc: Maximum log file size

Description

This message is displayed when an invalid value is specified for the ExpLogFileSize property of the resource adapter.

Action

The valid value for the ExpLogFileSize property of the resource adapter is in the range from 8192 to 4194304 (integer).

KDAN03026-W

Non-supported feature, Transacted session creation is used.

Description

This warning message is displayed if Session, QueueSession, or TopicSession is created, when Transacted value is TRUE.

Action

When Transacted value is TRUE, avoid creating Session, QueueSession, or TopicSession and use FALSE.

KDAN03027-W

Non-supported feature, JTA transaction(XA) is used.

Description

This warning message is displayed, when XATransaction is used as the transaction support level in the resource adapter.

Action

Avoid using XATransaction as the transaction support level. Instead, use LocalTransaction.

KDAN06001-E

Invalid property value aa....aa = bb....bb

aa....aa: Property name

bb....bb: Invalid value

Description

This error occurs when the client sets up an invalid value for the property name.

Action

Specify an appropriate property name.

KDAN06002-E

setResourceAdapter Incompatible ResourceAdapter class

Description

This error occurs when the client uses an incompatible ResourceAdapter class associated with the ActivationSpec instance.

Action

Specify name of a compatible ResourceApapter class to associate with ActivationSpec.

KDAN06004-E

Associating unknown resource adapter class-

Description

This error occurs when the client uses an incompatible ResourceAdapter class associated with ManagedConnectionFactory instance.

Action

Specify name of a compatible ResourceApapter class to associate with ManagedConnectionFactory.

KDAN06005-E

Illegal to change resource adapter association

Description

This error occurs when the ra object becomes null while the Resource Adapter Javabean that is associated with the ManagedConnectionFactory instance is set up.

Action

The ra object must not be null, when the Resource Adapter Javabean that is associated with the ManagedConnectionFactory instance is set up.

KDAN06006-E

Invalid property value, aa....aa must be greater than or equal to 0 Invalid value bb....bb

aa....aa: Property name

bb....bb: Invalid value

Description

This error occurs when the client specifies an invalid value (<0) for the property name.

Action

Confirm that the property value is valid.

If the value is invalid, set up a valid property value.

KDAN06007-E

Invalid property value, aa....aa must be greater than 0 Invalid value bb....bb

aa....aa: Property name

bb....bb: Invalid value

Description

This error occurs when the client specifies an invalid value (<=0) for the property name.

Action

Confirm that the property value is valid.

If the value is invalid, set up a valid property value.

KDAN06008-E

Invalid property value, subscriptionName and clientId must be non-null. subscriptionName= aa....aa clientId= bb....bb

aa....aa: Subscriber name

bb....bb: Client ID

Description

This error occurs when the subscriber name and client ID property value are null.

Action

Make sure that the subscriber name and client ID are not null.

KDAN06009-E

Invalid property value, endpointPoolSteadySize must be less than or equal to endpointPoolMaxSize endpointPoolSteadySize= aa....aa endpointPoolMaxSize bb....bb

aa....aa: EndpointPoolSteadySize

bb....bb: EndpointPoolMaxSize

Description

This error occurs when the client sets up invalid values for endpointPoolSteadySize and endpointPoolMaxSize. endpointPoolSteadySize must be less than endpointPoolMaxSize.

Action

Confirm that endpointPoolSteadySize is less than endpointPoolMaxSize.

KDAN06010-E

Unsupported- aa....aa

aa....aa: Operation name

Description

This error occurs when an attempt is made to use a functionality that is not supported by the client.

Action

Make sure that an unsupported functionality is not used.

KDAN06011-E

While closing got JMSExcption during _closeForPooling aa....aa

aa....aa: Connection debug information

Description

This error occurs when the Managed connection is inactive and an attempt is made to associate the inactive Managed connection with ra or close the connection.

Action

Confirm that the Managed connection is active during association or during close operations.

KDAN06012-E

aa....aa failed, Only one JMS Session allowed when managed connection is involved in a transaction

aa....aa: Session, queue session, or topic session

Description

This error occurs when multiple sessions are created using a Managed connection. In the case of Managed connections, only one JMS session is allowed.

Action

In the case of a Managed connection, make sure that more than one session is not created.

KDAN06013-E

Illegal operation, Connection is closed

Description

This error occurs when the connection is lost during operations. If the connection is closed, IllegalStateException is thrown.

Action

Make sure that the connection is not lost during operations in ra.

KDAN06014-E

Unable to associate ManagedConnection - Connection is destroyed

Description

This error occurs when an inactive Managed connection is associated with ra.

Action

When associating a Managed connection with ra, confirm that the Managed connection is active.

KDAN06015-E

While Destroy Exception on physical cnxn close-ignoring aa....aa

aa....aa: Exception message

Description

This message is displayed when an exception occurs while destroying a connection.

Action

Contact maintenance personnel for internal errors. Also, check the other logs.

KDAN06016-E

sendEvent:Unknown Event aa....aa

aa....aa: Event type

Description

This error occurs when the event type does not exist in the registered list of listeners.

Action

Contact maintenance personnel for internal errors. Also, check the other logs.

KDAN06017-E

connectionErrorOccurred Exception on cleanup&destroy event ID aa....aa and ManagedConnection bb....bb

aa....aa: Event ID

bb....bb: Managed connection

Description

A connection error occurred during the cleanup and destroy processing, when closing the connection.

Action

Contact maintenance personnel for internal errors. Also, check the other logs.

KDAN06018-E

connectionErrorOccurred Exception on destroy() event ID aa....aa and ManagedConnection bb....bb

aa....aa: Event ID

bb....bb: Managed connection

Description

A connection error occurred during the destroy processing, when closing the connection.

Action

Contact maintenance personnel for internal errors. Also, check the other logs.

KDAN06019-E

While destroyConnections Exception occurred aa....aa

aa....aa: Exception message

Description

A connection error occurred, when destroying a connection.

Action

Contact maintenance personnel for internal errors. Also, check the other logs.

KDAN06020-E

JMSException on createConnection aa....aa

aa....aa: Exception message

Description

This error occurs when the Broker fails.

An error occurred while a connection was being created.

Action

Make sure that the Broker started normally.

See the contents of the exception message and then take action, or contact maintenance personnel.

KDAN06021-E

Exception on setExceptionListener- aa....aa

aa....aa: Exception message

Description

An error occurred, when setting up the exception listener for a Managed connection.

Action

Contact maintenance personnel for internal errors. Also, check the other logs.

KDAN06022-E

Exception on XA Resource creation- aa....aa

aa....aa: Exception message

Description

An error occurred, when creating the xa resource for a Managed connection.

Action

Contact maintenance personnel for internal errors. Also, check the other logs.

KDAN06023-E

In getConnection auth failed for Subject aa....aa

aa....aa: Subject object

Description

An error occurred, when creating a new connection handler using invalid user credentials.

Action

Contact maintenance personnel for internal errors. Also, check the other logs.

KDAN06024-E

InvalidClientIDException in Managed Connection- aa....aa

aa....aa: Exception message

Description

An error occurred, when an attempt was made to create a new connection using an invalid client ID.

Action

Confirm that the client ID is valid.

KDAN06025-E

JMSException in Managed Connection- aa....aa

aa....aa: Exception message

Description

An error occurred in RA, when establishing a Managed connection.

Action

Contact maintenance personnel for internal errors. Also, check the other logs.

KDAN06026-E

associateConnection() invalid connection class name- aa....aa toString()- bb....bb

aa....aa: Connection class

bb....bb: Connection value

Description

An error occurred because the connection object is not of the ConnectionAdapter type.

Action

Contact maintenance personnel for internal errors. Also, check the other logs.

KDAN06027-E

Destroyed-Id in Managed Connection- aa....aa

aa....aa: ManagedConnection ID

Description

An error occurred, when destroying a Managed connection.

Action

Contact maintenance personnel for internal errors. Also, check the other logs.

KDAN06028-E

ConnectionFactoryAdapter getReference() NOT Supported

Description

An error occurred, when the getReference method of the ConnectionFactory interface was called.

Action

Do not call an unsupported method.

KDAN06029-E

ConnectionFactoryAdapter allocation failure for aa....aa

aa....aa: Connection or queue connection or topic connection

Description

This message is displayed when the Broker fails.

An error occurred in ConnectionFactoryAdapter, when connecting to Broker.

Action

Make sure that the Broker started normally.

See the contents of the exception message and then take action, or contact maintenance personnel.

KDAN06030-E

EndpointConsumer Exception setting Connection Factory reconnect params- aa....aa

aa....aa: Exception

Description

An error occurred due to one of the following causes, when setting up the imqReconnectEnabled, imqReconnectAttempts, imqReconnectInterval, or imqAddressListIterations properties:

When name of an invalid property is set up

When an invalid property value is set up

An attempt is made to change the settings although the ReadOnly flag is set up

Action

Specify a valid property name and value.

KDAN06031-E

EndpointConsumer Either ResourceAdapter or EndPointFactory or ActivationSpec value is null.

Description

This error occurs when ResourceAdapter, MessageEndpointFactory, or ActivationSpec is null.

Action

Contact maintenance personnel for internal errors. Also, check the other logs.

KDAN06032-E

EndpointConsumer Unsupported ActivationSpec Class - aa....aa

aa....aa: Class name

Description

This error occurs when an unsupported operation is executed.

Action

Avoid executing unsupported operations.

KDAN06034-E

EndpointConsumer createRemoteMessageConsumer Exception setting XA-ConnectionFactory properties - aa....aa.

aa....aa: Exception message

Description

An error occurred due to one of the following causes, when setting up the imqDefaultUsername, imqDefaultPassword, imqAddressList, or imqReconnectEnabled properties:

When an invalid property name is set up

When an invalid property value is set up

When an attempt is made to change the settings although the ReadOnly flag is set up

Action

Specify a valid property name and value.

KDAN06035-E

EndpointConsumer createConnection failed on addressListIteration # aa....aa of bb....bb Exception = cc....cc.

aa....aa: Current address list iteration

bb....bb: Address list iteration

cc....cc: Exception message

Description

This error occurs when the client ID is set up. Take action based on the following causes:

When the specified client ID is invalid or is repeated

When the client ID is configured from the viewpoint of management

Action

Confirm that the specified client ID is valid and is not repeated.

Confirm that the client ID is not configured from the viewpoint of management.

KDAN06036-E

EndpointConsumer createConnction failed. aborting after aa....aa addressListIterations.

aa....aa: Address list iteration

Description

This error occurs when the specified address list iteration count is exceeded.

Action

Increase the address list iteration count.

KDAN06037-E

EndpointConsumer createDurableConsumer: createConnection failed: aborting due to aa....aa

aa....aa: Exception message

Description

This error occurs when the specified address list iteration count exceeds.

Action

Increase the address list iteration count.

KDAN06039-E

EndpointConsumer Error creating Remote Message Consumer aa....aa

aa....aa: Exception message

Description

An error occurred, when creating the remote message consumer.

Action

Contact maintenance personnel for internal errors.

KDAN06040-E

EndpointConsumer Error on closing MessageConsumer.

Description

An error occurred, when terminating the remote message consumer.

Action

Contact maintenance personnel for internal errors.

KDAN06041-E

EndpointConsumer Error on closing JMS Connection.

Description

An error occurred, when closing JMSConnection.

Action

Contact maintenance personnel for internal errors.

KDAN06042-E

EndpointConsumer Invalid Destination - aa....aa.

aa....aa: Destination name

Description

This error occurs when an invalid destination name is specified.

Action

Specify a valid destination name.

KDAN06043-E

EndpointConsumer Need Valid SubscriptionName - aa....aa.

aa....aa: Subscriber name

Description

This error occurs when an invalid subscriber name is specified.

Action

Specify a valid subscriber name.

KDAN06044-E

EndpointConsumer Need Valid ClientID - aa....aa.

aa....aa: Client ID

Description

This error occurs when an invalid client ID is specified.

Action

Specify a valid client ID.

KDAN06045-E

EndpointConsumer Exception setting ConnectionFactory properties - addressList = aa....aa.

aa....aa: Address list

Description

An error occurred due to one of the following causes, when setting up the imqAddressList or imqReconnectEnabled properties:

When an invalid property name is set up

When an invalid property value is set up

When an attempt is made to change the settings although the ReadOnly flag is set up

Action

Specify a valid property name and value.

KDAN06046-E

EndpointConsumer createConnection failed on addressListIteration # aa....aa of bb....bb. Exception = cc....cc.

aa....aa: Current address list iteration

bb....bb: Address list iteration

cc....cc: Exception message

Description

This error occurs when the client ID is set up. Take action based on the following causes:

When the specified client ID is invalid or repeated

When the client ID is configured from the viewpoint of management

Action

Confirm that the specified client ID is valid and is not repeated.

Confirm that the client ID is not configured from the viewpoint of management.

KDAN06049-E

EndpointConsumer Error creating Durable Message Consumer aa....aa

aa....aa: Exception message

Description

An error occurred, when creating a durable subscriber.

Action

Contact maintenance personnel for internal errors.

KDAN06050-E

EndpointConsumer Clustered Non-Durable Message Consumer requires non-null clientID OR mdbName. clientID = aa....aa, mdbName = bb....bb.

aa....aa: Client ID

bb....bb: MDB name

Description

This error occurs when the MDB name is null or space while creating a non-durable consumer.

Action

Specify a valid MDB name.

KDAN06053-E

EndpointConsumer Error creating Non-Durable Message Consumer aa....aa.

aa....aa: Exception message

Description

An error occurred, when creating a non-durable subscriber.

Action

Contact maintenance personnel for internal errors.

KDAN06054-E

EndpointConsumer Error creating Direct Message Consumer aa....aa.

aa....aa: Exception message

Description

An error occurred, when creating a non-durable subscriber or durable subscriber.

Action

Contact maintenance personnel for internal errors.

KDAN06055-E

EndpointConsumer Error on closing Direct MessageConsumer.

Description

An error occurred, when terminating a non-durable subscriber or durable subscriber.

Action

Contact maintenance personnel for internal errors.

KDAN06056-E

EndpointConsumer Error closing DircetConnection.

Description

An error occurred, when closing a connection.

Action

Contact maintenance personnel for internal errors.

KDAN06057-E

LocalTransaction startTransaction exception - Connection is closed.

Description

This error occurs when a connection is closed.

Action

Confirm that the connection is not closed.

KDAN06058-E

LocalTransaction startTransaction exception - aa....aa.

aa....aa: Exception message

Description

This message is displayed when the Broker fails.

An error occurred while a local transaction was being started.

Action

Make sure that the Broker started normally.

See the contents of the exception message and then take action, or contact maintenance personnel.

KDAN06059-E

LocalTransaction commitTransaction exception - Connection is closed.

Description

This message is displayed if an exception occurs, when a connection is closed.

Action

Confirm that the connection is not closed.

KDAN06060-E

LocalTransaction commit exception aa....aa.

aa....aa: Exception message

Description

This message is displayed when the Broker fails.

An error occurred while a local transaction was being committed.

Action

Make sure that the Broker started normally.

See the contents of the exception message and then take action, or contact maintenance personnel.

KDAN06061-E

LocalTransaction rollbackTransaction exception - Connection is closed.

Description

This message is displayed when a connection is closed.

Action

Confirm that the connection is not closed.

KDAN06062-E

LocalTransaction rollback exception:aa....aa.

aa....aa: Exception message

Description

This message is displayed when the Broker fails.

An error occurred while a local transaction was being rolled back.

Action

Make sure that the Broker started normally.

See the contents of the exception message and then take action, or contact maintenance personnel.

KDAN06063-E

MessageListener onMessage - JMSException on getOnMessageRunner.

Description

An error occurred, when acquiring OnMessageRunner from the pool.

Action

Contact maintenance personnel for internal errors.

KDAN06064-E

MessageListener Endpoint Unavailable - Shutting down delivery for aa....aa

aa....aa: ActivationSpec (start specifications)

Description

This message is displayed when the message endpoint is null during the shut down of the message delivery for this session.

Action

Contact maintenance personnel for internal errors.

KDAN06065-E

MessageListener Exception setting ContextClassLoader aa....aa.

aa....aa: Error message

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN06066-E

MessageListener JMSException on acknowledge.

Description

An error occurred during message acknowledgement from the resource adapter.

Action

Contact maintenance personnel for internal errors.

KDAN06067-E

MessageListener Caught Exception from onMessage() - aa....aa.

aa....aa: Exception message

Description

An error occurred during message acknowledgement from the resource adapter.

Action

Contact maintenance personnel for internal errors.

KDAN06068-E

MessageListener Exhausted redeliveryAttempts - shutting down delivery for aa....aa

aa....aa: Start specifications

Description

This error occurs when the value of the endpointExceptionRedeliveryAttempts property is greater than 0.

Action

Contact maintenance personnel for internal errors.

KDAN06069-E

MessageListener onMessage caught Throwable - Before OR On OR After Delivery - Class = aa....aa Message = bb....bb

aa....aa: Exception class

bb....bb: Exception message

Description

An error occurred, when delivering a JMS message to MessageEndPoint.

Action

Contact maintenance personnel for internal errors.

KDAN06070-E

OnMessageRunner Exception on XAResource creation - aa....aa.

aa....aa: Exception message

Description

An error occurred, when setting up an XA resource for a resource adapter.

Action

Contact maintenance personnel for internal errors.

KDAN06071-E

OnMessageRunner createEndpoint - UnavailableException. Sleeping for aa....aa MilliSeconds.

aa....aa: Milliseconds

Description

An error occurred, when creating an endpoint from MessageEndPointFactory.

Action

Contact maintenance personnel for internal errors.

KDAN06072-E

OnMessageRunner Endpoint Unavailable - Marking OMR as invalid. omrId = aa....aa for bb....bb

aa....aa: omrid

bb....bb: ActivationSpec (start specifications)

Description

This message is displayed when the message endpoint is null during the shut down of message delivery for this session.

Action

Contact maintenance personnel for internal errors.

KDAN06073-E

OnMessageRunner EndPoint invalid-Ack Undeliverable And remove OMR for pool-omrId = aa....aa msg = bb....bb

aa....aa: omrid

bb....bb: Message

Description

This error occurs when the message endpoint is null.

Action

Contact maintenance personnel for internal errors.

KDAN06074-E

OnMessageRunner EndPoint invalid JMSException on Ack Undeliverable - aa....aa.

aa....aa: Exception message

Description

An error occurred during the acknowledgement of undeliverable messages from the resource adapter.

Action

Contact maintenance personnel for internal errors.

KDAN06075-E

OnMessageRunner Exception setting ContextClassLoader - aa....aa

aa....aa: Error message

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN06076-E

OnMessageRunner JMSException on message acknowledgement - Rolling back if in transaction.

Description

An error occurred, when acknowledging the messages from MDB or resource endpoint.

Action

Contact maintenance personnel for internal errors.

KDAN06077-E

OnMessageRunner Caught Exception from onMessage Redelivering - aa....aa

aa....aa: Exception message

Description

An error occurred, when acknowledging the messages from resource endpoint or MDB.

Action

Check the onMessage processing of the MDB application.

Check whether the message is stored in the destination.

KDAN06078-E

OnMessageRunner Exception on setJMSRedelivered() - aa....aa

aa....aa: Exception message

Description

An error occurs, when the redelivery status cannot be set up due to an internal error.

Action

Contact maintenance personnel for internal errors.

KDAN06079-E

OnMessageRunner Exhausted redeliveryAttempts - aa....aa = bb....bb

aa....aa: Activation Spec

bb....bb: Property information of Activation Spec

Description

This error occurs when the value of the endpointExceptionRedeliveryAttempts property is greater than 0.

Action

Check the onMessage processing of the MDB application.

Check whether the message is stored in the destination.

KDAN06080-E

OnMessageRunner Message returned and marked for aa....aa.

aa....aa: Routing to the DMQ or Redelivery by the broker

Description

This error occurs when the undeliverable messages are sent to the dead message queue.

Action

Check the onMessage processing of the MDB application.

Check whether the message is stored in the destination.

KDAN06081-E

OnMessageRunner omrId = aa....aa Acknowledged Undeliverable - Message = bb....bb

aa....aa: omrid

bb....bb: Message

Description

An error occurred during operations in the direct mode.

Action

Contact maintenance personnel.

KDAN06082-E

OnMessageRunner JMSException when Acknowledging Undeliverable Message -aa....aa

aa....aa: Exception message

Description

An error occurred, when acknowledging the undeliverable messages from the resource adapter endpoint or when acknowledging the dead messages for MDB.

Action

Contact maintenance personnel for internal errors.

KDAN06083-E

OnMessageRunner caught Throwable - Before OR On OR After Delivery - Class = aa....aa Message = bb....bb

aa....aa: Exception class name

bb....bb: Exception message

Description

An error occurred when acknowledging the undeliverable messages from the resource adapter endpoint or when acknowledging the dead messages for MDB.

Action

Contact maintenance personnel for internal errors.

KDAN06084-E

OnMessageRunner WorkException - aa....aa on omrId = bb....bb.

aa....aa: Exception message

bb....bb: omrid

Description

An error occurred when using WorkManager for scheduling in order to deliver messages.

Action

Contact maintenance personnel for internal errors.

KDAN06085-E

OnMessageRunnerPool - Unable to get OMR from pool - aa....aa

aa....aa: Exception message

Description

An interrupt exception occurred when acquiring OnMessageRunner from the pool.

Action

Contact maintenance personnel for internal errors.

KDAN06086-E

OnMessageRunnerPool Did not finish waiting for OMRs to return - aa....aa

aa....aa: Exception message

Description

This error occurs when an interrupt exception occurs while all OnMessageRunners are on standby.

Action

Contact maintenance personnel for internal errors.

KDAN06087-E

ManagedConnectionMetaData getEISProductName - Failed aa....aa

aa....aa: Exception message

Description

This error occurs when an attempt to acquire the metadata fails due to an internal error.

Action

Contact maintenance personnel for internal errors.

KDAN06088-E

ManagedConnectionMetaData getEISProductName()

Description

This error occurs when an attempt to acquire the metadata fails due to an internal error.

Action

Contact maintenance personnel for internal errors.

KDAN06089-E

ManagedConnectionMetaData getEISProductVersion - Failed - aa....aa

aa....aa: Exception message

Description

This error occurs when an attempt to acquire the metadata fails due to an internal error.

Action

Contact maintenance personnel for internal errors.

KDAN06090-E

ManagedConnectionMetaData getEISProductVersion()

Description

This error occurs when an attempt to acquire the metadata fails due to an internal error.

Action

Contact maintenance personnel for internal errors.

KDAN06091-E

ManagedConnectionMetaData getUserName - Failed - ManagedConnection is destroyed.

Description

This error occurs when a Managed connection is destroyed.

Action

Confirm that the Managed connection is not closed.

KDAN06092-E

ManagedConnectionMetaData getUserName()

Description

This error occurs when a Managed connection is destroyed.

Action

Contact maintenance personnel for internal errors.

KDAN06093-E

SessionAdapter closeAdapter - Exception - aa....aa

aa....aa: Exception message

Description

An error occurred when closing a connection adapter.

Action

Contact maintenance personnel for internal errors.

KDAN06094-E

SessionAdapter createSender() disallowed on TopicSession.

Description

This error occurs when an attempt is made to call the createSender() method on TopicSession.

Action

The createSender() method can be invoked on QueueSession.

KDAN06095-E

SessionAdapter createBrowser() disallowed on TopicSession.

Description

This error occurs when an attempt is made to call the createBrowser() method on TopicSession.

Action

The createBrowser() method can be invoked on QueueSession.

KDAN06096-E

SessionAdapter createSubscriber Exception. Require non-null, non-empty clientId for clustered non-durable subscription. ClientId = aa....aa.

aa....aa: Client ID

Description

This error occurs when the specified client ID is null or space.

Action

Specify a valid client ID.

KDAN06097-E

SessionAdapter unsubscribe() disallowed on QueueSession.

Description

This error occurs when an attempt is made to invoke the unsubscribe() method on QueueSession.

Action

The unsubscribe() method can be invoked on TopicSession.

KDAN06098-E

SessionAdapter createTemporaryTopic() disallowed on QueueSession.

Description

This error occurs when an attempt is made to invoke the createTemporaryTopic() method on QueueSession.

Action

The createTemporaryTopic() method can be invoked on TopicSession.

KDAN06099-E

SessionAdapter createTemporaryQueue() disallowed on TopicSession.

Description

This error occurs when an attempt is made to invoke the createTemporaryQueue() method on TopicSession.

Action

The createTemporaryQueue() method can be invoked on QueueSession.

KDAN06100-E

SessionAdapter Disallowed - Session.run()

Description

This error occurs when the run() method is invoked.

Action

The run() method must not be invoked.

KDAN06101-E

SessionAdapter IllegalState - Session is closed.

Description

This error occurs when the session is closed.

Action

Confirm that the session is not closed.

KDAN06102-E

ResourceAdapter Property msgLogLevel is defaulted to : ERROR. Since the valid msgLogLevel should be INFO or WARNING or ERROR.

Description

This error occurs when an invalid log level is specified.

Action

Specify DEBUG/ INFO/ WARNING/ ERROR as the log level.

KDAN06103-E

Resource Adapter cannot be started since the property ''raName'' is a reserved device name.

Description

This error occurs when a reserved device name is specified for raName.

Action

Confirm that raName is not a reserved device name.

KDAN06104-E

ResourceAdapter start : Aborting : Exceptionperforming doInitOnlyOnStart on broker = aa....aa

aa....aa: Exception message

Description

An error occurred when starting a resource adapter.

Action

Contact maintenance personnel for internal errors.

KDAN06107-E

ResourceAdapter Aborting : Exceptionstarting LOCAL broker = aa....aa

aa....aa: Exception message

Description

An error occurred when starting a resource adapter.

Action

Contact maintenance personnel for internal errors.

KDAN06108-E

ResourceAdapter Aborting : Exceptionstarting EMBEDDED broker = aa....aa

aa....aa: Exception message

Description

An error occurred when starting a resource adapter.

Action

Contact maintenance personnel for internal errors.

KDAN06110-E

ResourceAdapter start : Aborting JMSException on createConnection = aa....aa

aa....aa: Exception message

Description

An error occurred when initializing the connection or configuring the RA connection factory.

Action

Contact maintenance personnel for internal errors.

KDAN06111-E

ResourceAdapter Exception on Stopping RA. Ignoring...

Description

An error occurred when terminating the resource adapter instances.

Action

Contact maintenance personnel for internal errors.

KDAN06112-E

ResourceAdapter JMSRA - Cannot perform Endpoint Activation. RA not started. Aborting...

Description

This error occurs if the resource adapter is already running.

Action

Stop, and then restart the resource adapter.

KDAN06114-E

ResourceAdapter endpointDeactivation() Exception on stopMessageConsumer. Ignoring.

Description

An error occurred when terminating a consumer or connection associated with EndpointConsumer.

Action

Contact maintenance personnel for internal errors.

KDAN06115-E

ResourceAdapter stopMessageConsumer exception. ignoring...

Description

An error occurred when terminating a consumer or connection associated with EndpointConsumer.

Action

Contact maintenance personnel for internal errors.

KDAN06116-E

ResourceAdapter AdjustInApplicationClientContainer System Property inACC is NOT null.

Description

This error occurs when the system property ResourceAdapter AdjustInApplicationClientContainer (inACC) is not null.

Action

Contact maintenance personnel for internal errors.

KDAN06117-E

ResourceAdapter AdjustInApplicationClientContainer setting inACC to aa....aa.

aa....aa: Positive or negative

Description

This message is displayed for setting up the ResourceAdapter AdjustInApplicationClientContainer (inACC) property to positive or negative.

Action

Contact maintenance personnel for internal errors.

KDAN10001-E

Packet acknowledge failed.

Description

An error occurred when the client read or processed ACK from CJMSP.

A possible cause is the disconnection from CJMSP.

Action

Confirm that the network connection is normal and that the machine on which CJMSP is set up is accessible.

KDAN10002-E

Write packet failed.

Description

An error occurred when sending information from the client to CJMSP.

A possible cause is the disconnection from CJMSP.

Action

Confirm that the network connection is normal and that the machine on which CJMSP is set up is accessible.

KDAN10003-E

Read packet failed.

Description

An error occurred when the client was reading information from CJMSP.

A possible cause is the disconnection from CJMSP.

Action

Confirm that the network connection is normal and that the machine on which CJMSP is set up is accessible.

KDAN10004-E

Error occurred on connection creation aa....aa.

aa....aa: Connection type

Description

An error occurred when connecting the client with CJMSP.

Take action based on the following causes:

CJMSP is not running

The server machine that operates CJMSP is inaccessible

Action

Confirm that CJMSP is running.

Confirm that the network connection is normal and that the machine that operates CJMSP is accessible.

KDAN10005-E

Error occurred on connection close.

Description

An error occurred when an attempt was made to close the connection with CJMSP. Take action based on the following causes:

CJMSP has been shut down

Network failure

Action

Confirm that CJMSP is running.

Confirm that the network connection is normal.

KDAN10006-E

Get properties from packet failed.

Description

An error occurred when the client was reading the property information for packets sent by CJMSP. A possible cause is the disconnection from CJMSP.

Action

Confirm that the network connection is normal and that the machine on which CJMSP is set up is accessible.

KDAN10007-E

Set properties to packet failed.

Description

An internal error occurred when the client was reading the property information for packets received from CJMSP.

Action

An internal error occurred. Contact maintenance personnel.

KDAN10008-E

Durable subscription aa....aa in use.

aa....aa: Durable subscriber name

Description

Take action based on the following causes:

The client attempted to create a durable subscriber using an already existing name.

The client attempted to unsubscribe a durable subscriber being used by another consumer.

Action

When creating a durable subscriber, confirm that another durable subscriber does not exist with the same name.

When unsubscribing a durable subscriber, confirm that consumers subscribing messages from the applicable durable subscriber do not exist.

KDAN10009-E

Message in read-only mode.

Description

This error occurs when the client attempts to change the message body without clearing the body.

Action

Invoke the clearBody() method before changing the message body.

KDAN10010-E

Message in write-only mode.

Description

This error occurs when the client reads the StreamMessage or BytesMessage body and the body is blank.

Action

Before reading the StreamMessage or BytesMessage body, check whether the message body is blank.

KDAN10011-E

Read message failed.

Description

This error occurs when the client reads BytesMessage from byte stream. A possible cause might be that the BytesMessage body is in the write mode.

Action

To change the BytesMessage body into the read mode, invoke the BytesMessage.reset() method.

KDAN10012-E

Write message failed.

Description

An error occurs when the client writes BytesMessage in the byte stream. A possible cause might be that the BytesMessage body is in the read mode.

Action

To change the BytesMessage body into the write mode, invoke the BytesMessage.clearBody() method.

KDAN10013-E

Reset message failed.

Description

This error occurs when an attempt is made to reset a message. A possible cause might be an internal error or invalid message format.

Action

Check whether the message format is correct.

KDAN10014-E

Unexpected end of stream when read message

Description

Take action based on the following causes:

This error occurs when the client reads the blank body of BytesMessage or StreamMessage.

This error occurs when the client attempts to read although the end of the stream has been reached.

Action

Before reading, check whether the end of the stream has been reached.

KDAN10015-E

Cannot serialize the Message body.

Description

This error occurs when the client sets up a Java object as the body in MapMessage or ObjectMessage. A possible cause is that the Java objects are unserializable.

Action

Confirm that the Java object set up in MapMessage or ObjectMessage has implemented the java.io.Serializable interface.

KDAN10016-E

Failed to Deserialize message body.

Description

This error occurs when the client attempts to deserialize an unserializable message body.

Action

Before deserializing, the Java object must implement java.io.Serializable.

KDAN10017-E

Error occurred during message acknowledgement.

Description

This error occurs when the client attempts to notify the receipt of message. A possible cause is the disconnection from CJMSP.

Action

Confirm that the network connection is normal and that the machine on which CJMSP is set up is accessible.

KDAN10018-E

Invalid message format.

Description

An error occurred when the client attempts to transform a property value object into an invalid Java object type.

Action

Confirm that the property value is transformed into one of the following types:

Integer, Short, Float, Double, Long, String, Character, Byte, Byte Array, Boolean

KDAN10019-E

Error occurred on request message redeliver.

Description

A network error occurred when redelivering a packet to CJMSP during the processing of recover() or rollback() in the JMS session.

Action

Confirm that the network is operating normally.

KDAN10020-E

Destination not found: aa....aa.

aa....aa: Destination name

Description

This error occurs when the client attempts to create a message producer or message consumer using a deleted temporary destination.

This error occurs when null is specified as the destination for creating the message producer or message consumer, or for sending a message.

This error occurs when the applicable destination does not exist in CJMSP.

Action

Before creating the message producer or message consumer, confirm that the temporary destination exists.

Specify an existing valid destination in CJMSP.

KDAN10021-E

Temporary destination belongs to a closed connection or another connection - aa....aa.

aa....aa: Temporary destination name

Description

This error occurs when the client attempts to create a temporary destination using a closed connection.

This error occurs when the client attempts to create a message consumer using the temporary destination of another connection.

Action

Before creating a temporary destination, confirm that the connection is not closed.

Check the connection applicable to the temporary destination that is used for creating the message consumer.

KDAN10022-E

Consumer not found.

Description

This error occurs when the application or client closes a consumer before the message is processed.

Action

Make sure that the application or client does not close the consumer.

KDAN10023-E

Invalid Message selector expression: aa....aa.

aa....aa: selector expression

Description

This message is displayed for an invalid message selector expression.

Action

Specify a valid selector expression that conforms to the SQL92 syntax.

KDAN10024-E

Client unacknowledged messages exceeded the system defined limit.

Description

This error occurs when the unacknowledged messages exceed the system-defined limit in the CLIENT_ACKNOWLEDGE mode.

Action

Confirm that the received messages are acknowledged.

KDAN10025-E

The session is not transacted.

Description

This error occurs when the client attempts to commit or rollback a Non Transacted session.

Action

Do not use a transacted session.

KDAN10026-E

Cannot call this method from a transacted session.

Description

This error occurs when the client invokes the recover method for a Transacted session.

Action

Do not use a transacted session.

KDAN10027-E

Client non-committed messages exceeded system defined limit.

Description

This error occurs when the non-committed messages exceed the system-defined limit in a Transacted session.

Action

Do not use a transacted session.

KDAN10033-E

Cannot use receive() when message listener is set.

Description

This error occurs when the client attempts to perform a synchronous reception operation for an asynchronous message consumer.

Action

Make sure that a synchronous reception operation is only performed for a synchronous message consumer.

KDAN10034-E

Authentication type not match: aa....aa and bb....bb.

aa....aa: Authentication type used by the client at runtime

bb....bb: Authentication type requested by CJMSP

Description

This error occurs when the client authentication type differs from the CJMSP authentication type.

Action

Contact maintenance personnel.

KDAN10037-E

A broker error occurred.

Description

This error occurs when the Broker is stopped while a request is being processed.

Action

Make sure that the Broker is not stopped during the processing of a request.

KDAN10038-E

Broker is unavailable or broker timeout.

Description

This error occurs when the Broker is stopped while writing the packet data to CJMSP.

Action

Make sure that the Broker is not stopped during the process of packet writing to CJMSP.

KDAN10039-E

aa....aa is the cause for bb....bb.

aa....aa: Cause

bb....bb: Exception message for the original cause

Description

A network error occurred during message writing or acquiring a property from CJMSP.

This error occurs when an invalid CJMSP address is specified.

Action

Contact the network administrator.

Specify a valid CJMSP address.

KDAN10040-E

Cannot delete destination

Description

This error occurs when the client attempts to delete the temporary destination of another connection object.

This error occurs when the client attempts to delete the temporary destination that contains a consumer.

Action

Make sure that the temporary destination of the applicable connection is deleted.

Before deleting the temporary destination, confirm that the consumer is closed.

KDAN10041-E

Invalid ObjectProperty type

Description

This error occurs when a non-primitive Java object is set up as a JMS message property.

Action

Make sure that one of the following is specified as the property value type:

Boolean, Byte, Short, Integer, Long, Float, Double, String

KDAN10042-E

Reserved word used as property name - aa....aa.

aa....aa: Property name

Description

This error occurs when a JMS reserved word is used as a property name.

Action

Do not use a JMS reserved word in the property name.

KDAN10043-E

Illegal first character of property name - aa....aa.

aa....aa: Property name

Description

This error occurs when an invalid character is entered in the property name.

Action

Make sure that invalid characters are not used as the property name.

KDAN10044-E

Illegal character aa....aa used in property name - bb....bb.

aa....aa: Invalid character

bb....bb: Property name

Description

This error occurs when an invalid character is entered in the property name.

Action

Make sure that invalid characters are not used as the property name.

KDAN10045-E

Browser timeout.

Description

This error occurs when the client attempts to browse a message after the queue browser interval timeout.

Action

Specify an appropriate time interval.

KDAN10046-E

No more elements in the Queue to browse.

Description

This error occurs when the client attempts to browse an empty queue.

Action

Before browsing, confirm that the queue is not empty.

KDAN10047-E

QueueBrowser closed.

Description

This error occurs when the client attempts to browse a closed queue.

Action

Before browsing, confirm that the browser is not closed.

KDAN10050-E

Cannot call Connection.close(), stop(), etc from message listener.

Description

This error occurs when the client attempts to close or terminate the connection while the message listener is receiving a message.

Action

Confirm that the connection is not closed.

KDAN10051-E

Invalid destination name - aa....aa.

aa....aa: Destination name

Description

This error occurs when the specified destination name is null.

This error occurs when the client attempts to create a destination name using special characters.

Action

Confirm that the specified destination name is not null.

Confirm that the destination name does not contain invalid characters.

KDAN10052-E

Invalid message delivery parameter. aa....aa : bb....bb.

aa....aa: Delivery mode

bb....bb: Delivery mode value

Description

This error occurs when an invalid value is specified for the following parameters when the client is sending a message:

Delivery Mode, Priority, and Time to Live

Action

Specify the following values:

Delivery Mode- PERSISTENT or NON_PERSISTENT
Priority- 0 to 9
Time to Live- Zero or more

KDAN10053-E

Client ID is already in use - aa....aa.

aa....aa: Client ID

Description

This error occurs when an attempt is made to set up a client ID that already exists on the system.

Action

Specify a unique client ID.

KDAN10054-E

Invalid client ID - aa....aa.

aa....aa: Client ID

Description

This error occurs when an attempt is made to specify an invalid value for the client ID.

Action

Specify a valid client ID.

KDAN10055-E

Cannot set client ID, invalid state.

Description

This error occurs when the client ID is not set up as the first operation after the connection is established.

Action

Do not set up the client ID.

KDAN10056-E

Session in conflict. Concurrent operations on a session.

Description

This error occurs when multiple threads access the session concurrently.

Action

Avoid multiple concurrent operations on a session.

KDAN10057-E

Received goodbye message from broker.

Description

This error occurs when the connection with the Broker is lost.

Action

Confirm that CJMSP is running.

KDAN10059-E

Cannot acknowledge message for closed consumer.

Description

This error occurs when the consumer is closed while processing a message.

Action

Make sure that the consumer is not closed while processing a message.

KDAN10060-E

Cannot perform operation on a closed session.

Description

This error occurs when the client attempts to perform operations on a closed session.

Action

Do not perform operations for a closed session.

KDAN10062-E

Connection recovery failed, cannot recover connection.

Description

This error occurs when the client attempts to restore a connection that has an associated connection consumer.

Action

Before restoring the connection, make sure that the connection consumer is closed.

KDAN10063-E

Cannot perform operation, connection is closed.

Description

This error occurs when the client attempts to operate a closed connection.

Action

Do not perform operations for a closed connection.

KDAN10064-E

Cannot perform operation, consumer is closed.

Description

This error occurs when the client attempts to perform operations for a closed consumer.

Action

Do not perform operations for a closed consumer.

KDAN10065-E

Cannot perform operation, producer is closed.

Description

This error occurs when the client attempts to perform operations for a closed producer.

Action

Do not perform operations for a closed producer.

KDAN10067-E

Invalid or empty Durable Subscription Name used: aa....aa.

aa....aa: Durable subscriber name

Description

This error occurs when the client sets up a null or an invalid value for a durable subscriber name.

Action

Specify a valid durable subscriber name.

KDAN10068-E

Invalid session acknowledgement mode: aa....aa.

aa....aa: Acknowledgement mode

Description

This error occurs when the client attempts to create a session using an invalid acknowledgement mode.

Action

Make sure that one of the following is specified as the acknowledgement mode:

AUTO_ACKNOWLEDGE, CLIENT_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE

KDAN10069-E

Invalid Destination Classname: aa....aa.

aa....aa: Destination class name

Description

This error occurs when the client attempts to create a destination with an invalid type.

Action

Confirm that the destination type is QUEUE or TOPIC.

KDAN10070-E

Cannot perform commit or rollback on an XASession.

Description

This error occurs when the client attempts to commit or rollback a transaction that is being managed by Transaction Manager.

Action

Do not perform commit or rollback for XASession.

KDAN10072-E

Invalid method in this messaging domain: aa....aa.

aa....aa: Method name

Description

This error occurs when an attempt is made in the Point To Point domain to perform operations unique to the Publish/ Subscribe domain.

This error occurs when an attempt is made in the Publish/ Subscribe domain to perform operations unique to the Point To Point domain.

Action

Make sure that operations dedicated to the appropriate domains are performed.

KDAN10073-E

Illegal property name - "" or null.

Description

This error occurs when the client attempts to set up null or space in the property name.

Action

Specify a valid property name.

KDAN10074-E

A JMS destination limit was reached. Too many Subscribers/Receivers for aa....aa : bb....bb.

aa....aa: Destination type

bb....bb: Destination name

Description

This error occurs when a JMS destination reaches its limit.

Action

Increase the JMS destination limit or delete the unnecessary subscribers or receivers.

KDAN10077-E

Client does not have permission to create producer on destination: aa....aa.

aa....aa: Destination name

Description

This error occurs when the client does not have the permission to create a producer.

Action

Contact maintenance personnel.

KDAN10078-E

Client is not authorized to create destination: aa....aa.

aa....aa: Destination name

Description

This error occurs when the client does not have the permission to create a destination.

Action

Contact maintenance personnel.

KDAN10079-E

Client is unauthorized to send to destination: aa....aa.

aa....aa: Destination name

Description

This error occurs when the client does not have the permission to produce the messages for the destination.

Action

Contact maintenance personnel.

KDAN10080-E

Client does not have permission to register a consumer on the destination: aa....aa.

aa....aa: Destination name

Description

This error occurs when the client does not have the permission to consume the messages from the destination.

Action

Contact maintenance personnel.

KDAN10081-E

Client does not have permission to delete consumer: aa....aa.

aa....aa: Consumer

Description

This error occurs when the client does not have the permission to delete a consumer from the destination.

Action

Contact maintenance personnel.

KDAN10082-E

Client does not have permission to unsubscribe: aa....aa.

aa....aa: Durable subscriber name

Description

This error occurs when the client does not have the permission to unsubscribe the specified durable subscriber.

Action

Contact maintenance personnel.

KDAN10083-E

Client is not authorized to access destination: aa....aa.

aa....aa: Destination name

Description

The application client does not have the permission to access the specified destination.

Action

Contact maintenance personnel.

KDAN10084-E

Client does not have permission to browse destination: aa....aa.

aa....aa: Destination name

Description

The application client does not have the permission to browse the specified destination.

Action

Contact maintenance personnel.

KDAN10086-E

Delete consumer failed. Consumer was not found: aa....aa.

aa....aa: Consumer

Description

This error occurs when the client attempts to delete a non-existent consumer.

Action

Before deleting the consumer, confirm that the consumer exists on CJMSP.

KDAN10087-E

Unsubscribe failed. Subscriber was not found: aa....aa.

aa....aa: Subscriber

Description

This error occurs when the client attempts to unsubscribe a durable subscriber that does not exist on CJMSP.

Action

Confirm that the specified subscriber exists on CJMSP.

KDAN10088-E

Set Client ID operation failed. Invalid Client ID: aa....aa.

aa....aa: Client ID

Description

This error occurs when the client specifies an invalid client ID for the connection.

Action

Specify a valid client ID for the connection.

KDAN10089-E

A JMS destination limit was reached. Too many producers for aa....aa : bb....bb.

aa....aa: Character string to be sent

bb....bb: Destination name

Description

This message is displayed when the number of producers at the destination reaches the upper limit while producers are being created.

Action

Increase the upper limit for the maximum producer count for the destination.

KDAN10090-E

Caught JVM Error: aa....aa.

aa....aa: Exception message for the original cause

Description

This error occurs when JVM crashes.

Action

Contact maintenance personnel.

KDAN10091-E

Invalid port number. Broker is not available or may be paused or quiesced: aa....aa.

aa....aa: Host name, port number

Description

This message is displayed when an exception occurs in JVM.

Action

Broker must specify the port number corresponding to the request.

KDAN10094-E

Received wrong packet type. Expected: aa....aa, but received: bb....bb.

aa....aa: Packet type that must be received

bb....bb: Packet type that was received

Description

This error occurs when an attempt to process a message fails.

Action

Contact maintenance personnel.

KDAN10095-E

The destination this message was sent to could not be found: aa....aa.

aa....aa: Destination name

Description

This error occurs when the client attempts to send a message to a destination that does not exist on CJMSP.

Action

Before the message is sent to a destination, confirm that the applicable destination exists.

KDAN10096-E

Message exceeds the single message size limit for the broker or destination: aa....aa.

aa....aa: Destination name

Description

This error occurs when the client attempts to send a message that has exceeded the maximum size limit.

Action

Increase the upper limit for the maximum message size for the destination.

KDAN10097-E

Destination is full and is rejecting new messages: aa....aa.

aa....aa: Destination name

Description

This error occurs when the client attempts to create more producers or consumers than the maximum limit for the destination.

This error occurs when the JVM memory size for the Broker is exceeded.

Action

Increase the maximum limit for messages at the destination.

Increase the JVM memory size for CJMSP-Broker.

KDAN10099-E

Unknown broker service: aa....aa.

aa....aa: Service name

Description

This error occurs when the client attempts to use an unsupported service.

Action

Check whether the specified service is supported.

KDAN10115-E

Bad imqAddressListBehavior value : aa....aa.

aa....aa: Value of the imqAddressListBehavior property

Description

This error occurs when the specified value of the imqAddressListBehavior property is invalid.

Action

Do not specify the imqAddressListBehavior property.

KDAN10116-E

ConnectionRecover aborted!

Description

This error occurs when an attempt is made to stop the recovery of a disconnected connection.

Action

Contact maintenance personnel.

KDAN10117-E

Timeout on ConnectionRecover object. Broker: aa....aa.

aa....aa: Address of the Broker exchanged last

Description

This error occurs when the maximum waiting time is exceeded.

Action

Contact maintenance personnel.

KDAN10118-E

Exception caught when reading portmapper.

Description

An I/O error occurred when creating a socket.

An unknown host name is specified.

Action

Specify a valid host name address.

KDAN10119-E

Name MUST NOT be null or empty.

Description

This error occurs when the specified Name is a null or empty string.

Action

Specify a valid Name.

KDAN10123-E

JVM Error. Message Queue is null. Create time:aa....aa duration: bb....bb.

aa....aa: Creation time

bb....bb: Difference between the current time and creation time

Description

A JVM error occurs when the specified destination is null.

Action

Make sure that the specified destination name is appropriate.

KDAN10129-E

Exception thrown closing session. Reason : aa....aa

aa....aa: Error reason

Description

An internal error occurred when closing a session.

Action

Reference the reason for the error, and then take the appropriate measures.

KDAN10130-E

Exception thrown when exiting a connection. Reason: aa....aa

aa....aa: Error reason

Description

This exception is thrown when an attempt to close a consumer connection fails.

This exception is thrown when an attempt to close a session fails.

Action

Reference the reason for the error, and then take the appropriate measures.

KDAN10131-E

Connection recover failed. Reason : aa....aa

aa....aa: Error reason

Description

An error occurred in the active temporary destination related to the connection.

An error occurred in the session processing.

An error occurred during the client acknowledgement of unacknowledged messages.

Action

Reference the reason for the error, and then take the appropriate measures.

KDAN10132-E

JMSException thrown when recreate the consumer. Reason : aa....aa

aa....aa: Error reason

Description

The exception is thrown when the sending of messages between sessions cannot be stopped.

The exception is thrown when the consumer queue cannot be cleaned or deleted.

The exception is thrown when the consumer state cannot be registered in Broker.

Action

Reference the reason for the error, and then take the appropriate measures.

KDAN10133-E

Internal error : aa....aa

aa....aa: Error message

Description

An internal error occurred.

Action

Reference the contents of the error message, and then take the appropriate measures.

KDAN10134-E

JMSException thrown while starting direct MessageConsumer.

Description

This error occurs when the connection cannot be established.

Action

Contact maintenance personnel.

KDAN10135-E

JMSException thrown while creating direct MessageConsumer.

Description

This error occurs when the connection cannot be started.

This error occurs when the session cannot be created.

This error occurs when the consumer cannot be created.

This error occurs when directMessageListener cannot be set up in the consumer.

Action

Contact maintenance personnel.

KDAN10136-E

Exception delivering message aa....aa.

aa....aa: Error message

Description

An error occurred when delivering a message from the Session.

Action

Reference the contents of the error message, and then take the appropriate measures.

KDAN10137-E

Exception creating Endpoint:aa....aa

aa....aa: Error message

Description

An error occurred when creating a new instance for directMessageListener.

Action

Reference the contents of the error message, and then take the appropriate measures.

KDAN10138-E

Invalid destination name - "" or null.

Description

This error occurs when the specified destination is invalid or NULL.

Action

Make sure that the specified destination is not an invalid string or NULL.

KDAN10139-E

Throw JMS Exception: aa....aa

aa....aa: Error message

Description

A JMS error occurred.

Action

Reference the contents of the error message, and then take the appropriate measures, or contact maintenance personnel.

KDAN10140-E

EndpointConsumer got Exception aa....aa

aa....aa: Error message

Description

This error occurs when the onException method of the ExceptionListener interface is invoked.

Action

Reference the contents of the error message, and then take the appropriate measures, or contact maintenance personnel.

KDAN10141-E

ResourceAdapter endpointActivation() Failed due to aa....aa

aa....aa: Error message

Description

An error occurred when starting the message consumer.

Action

Reference the contents of the error message, and then take the appropriate measures, or contact maintenance personnel.

KDAN10142-E

ResourceAdapter onException Reconnect unsuccessfull on loop # aa....aa Exception = bb....bb

aa....aa: Loop count

bb....bb: Error message

Description

This error occurs when the RA cannot be reconnected.

Action

Reference the contents of the error message, and then take the appropriate measures, or contact maintenance personnel.

KDAN10143-E

Connection closed due to broker crashed: aa....aa.

aa....aa: Number of seconds

Description

This error occurs when the Broker crashes.

Action

Reference the error log, and then take the appropriate measures, or contact maintenance personnel.

KDAN10144-E

Connection closed. The connection is closed due to the broker is not responsive: aa....aa.

aa....aa: Number of seconds

Description

This error occurs when the Broker is not responsive.

Action

Reference the error log, and then take the appropriate measures, or contact maintenance personnel.

KDAN10145-E

Connection closed. The connection is closed due to a

network problem, broker crashed, or internal error: aa....aa.

aa....aa: Number of seconds

Description

This error occurs when the connection with the Broker is disconnected during client runtime.

This message is displayed when a network problem occurs or when the Broker crashes.

Action

Reference the error log, and then take the appropriate measures, or contact maintenance personnel.

KDAN10146-E

Connection closed due to broker error: aa....aa.

aa....aa: Number of seconds

Description

This message is displayed when the Out Of Memory error occurs.

Action

Reference the error log, and then take the appropriate measures, or contact maintenance personnel.

KDAN10147-E

Connection reconnect to the broker failed: aa....aa.

aa....aa: Number of seconds

Description

This error occurs when an attempt is made to reconnect to the Broker during client runtime.

Action

Reference the error log, and then take the appropriate measures, or contact maintenance personnel.

KDAN10148-E

EndpointConsumer Unable to re-establish connection for aa....aa in bb....bb

aa....aa: Activation Spec name

bb....bb: Resource adapter name

Description

This error occurs when the end point consumer cannot be reconnected.

Action

Reference the error log, and then take the appropriate measures, or contact maintenance personnel.

KDAN10149-E

ResourceAdapter endpointActivation() JMSRA not started : Aborting...

Description

This error occurs when the resource adapter is not running.

Action

Reference the error log, and then take the appropriate measures, or contact maintenance personnel.

KDAN10150-E

ResourceAdapter endpointDeactivation() JMSRA not started. Aborting...

Description

This error occurs when the resource adapter is not running.

Action

Reference the error log, and then take the appropriate measures, or contact maintenance personnel.

KDAN10151-E

ResourceAdapter endpointDeactivation : Ignoring : Not found Activation Spec aa....aa

aa....aa: Activation Spec name

Description

This error occurs when the message consumer is stopped.

Action

Reference the error log, and then take the appropriate measures, or contact maintenance personnel.

KDAN10152-E

Caused by aa....aa

aa....aa: Exception message

Description

This message is displayed when JMSException occurs.

Action

See the contents of the exception message and then take action, or contact maintenance personnel.

KDAN12001-W

Received unknown packet:

Description

This message is displayed when a message packet with an unidentifiable client runtime is received. A possible cause might be the network changes.

Action

Confirm that the network is stable.

KDAN12002-W

packet not processed, no message consumer: aa....aa.

aa....aa: Packet information

Description

This message is displayed when a message packet with an unexpected client runtime is received during the reception of receipt notification. A possible cause might be the network changes.

Action

Confirm that the network is stable.

KDAN12003-W

Failed to close JMSXAConnection.

Description

This message is displayed when the client stops XAConnection. Take action based on the following causes:

CJMSP has been shut down.

Network failure

Action

Confirm that CJMSP is running.

Check whether the network connection is correct.

KDAN12004-W

Broker not responding [aa....aa] for bb....bb seconds. Still trying...cc....cc

aa....aa: Packet type

bb....bb: Elapsed time

cc....cc: Broker address, connection ID , client ID, consumer ID

Description

This message is displayed when there is no response from the Broker even after the lapse of the displayed time. Take action based on the following causes:

CJMSP has been shut down.

Network failure

Action

Confirm that CJMSP is running.

Check whether the network connection is correct.

KDAN12005-W

[Informational]: aa....aa

aa....aa: Packet contents

Description

This message is displayed when a packet is sent to the Broker and the system waits for the response.

Action

Make sure that the network connection is correct.

KDAN12006-W

transaction is not in prepared state: aa....aa

aa....aa: Error message

Description

This message is displayed when the transaction is not in a prepared state.

Action

Confirm that the transaction is in a prepared state.

KDAN12009-W

Caught JVM Exception: aa....aa.

aa....aa: Error information

Description

This message is displayed when an error occurs during client execution.

Action

Check the message, and take action accordingly, or contact maintenance personnel.

KDAN14001-I

Connection closing in aa....aa seconds (bb....bb milliseconds): cc....cc

aa....aa: Remaining time (seconds)

bb....bb: Remaining time (milliseconds)

cc....cc: Broker address

Description

This message is displayed when the connection closes.

KDAN14002-I

Connection closed due to admin requested shutdown: aa....aa

aa....aa: Remaining time (seconds)

Description

This message is displayed when the Broker is shutting down.

KDAN14003-I

Connection closed due to admin requested restart: aa....aa

aa....aa: Remaining time (seconds)

Description

This message is displayed when there is a Broker restart request from admin.

KDAN14005-I

Connection closed due to admin killed the connection: aa....aa

aa....aa: Remaining time (seconds)

Description

This message is displayed when admin Kills the connection.

KDAN14009-I

Connection reconnected to the broker: aa....aa

aa....aa: Remaining time (seconds)

Description

This message is displayed when an attempt is made to reconnect to the Broker at client runtime.

KDAN14011-I

Connection is permanent broken: aa....aa

aa....aa: Remaining time (seconds)

Description

This message is displayed when the connection is terminated.

KDAN14012-I

Broker address list changed: aa....aa

aa....aa: Remaining time (seconds)

Description

This message is displayed when there is one Broker address in the address list.

KDAN14013-I

Connection created: aa....aa

aa....aa: Connection type

Description

This message is displayed when the connection is created.

KDAN14014-I

Connection closed: aa....aa

aa....aa: Connection type

Description

This message is displayed when the application closes the connection.

KDAN14016-I

PAUSED MESSAGE DELIVERY FOR: aa....aa

aa....aa: Flow control entry

Description

This message is displayed when the message delivery is suspended.

KDAN14017-I

RESUME MESSAGE DELIVERY FOR: aa....aa

aa....aa: Flow control entry

Description

This message is displayed when the message delivery resumes.

KDAN14018-I

Inbound Packet: aa....aa;bb....bb

aa....aa: Packet

bb....bb: Connection

Description

This message is displayed when the packet is read.

KDAN14019-I

Outbound Packet:aa....aa;bb....bb

aa....aa: Packet

bb....bb: Connection

Description

This message is displayed when writing to the packet.

KDAN14020-I

Connection recover state: aa....aa, broker: bb....bb

aa....aa: Recover state

bb....bb: Address of the Broker connected last

Description

This message is displayed when the connection is recovered.

KDAN14021-I

Received MOVED_PERMANENTLY status from broker: aa....aa, Redirecting to broker: bb....bb

aa....aa: Address of the Broker connected last

bb....bb: JMQ store owner

Description

This message is displayed when redirecting to another Broker.

KDAN14022-I

Received TIME_OUT status from broker: aa....aa

aa....aa: Address of the Broker connected last

Description

This message is displayed when a timeout status is received from the Broker.

KDAN14026-I

Session created: aa....aa

aa....aa: Session

Description

This message is displayed when a session is created.

KDAN14027-I

Session closed: aa....aa

aa....aa: Session

Description

This message is displayed when a session is closed.

KDAN14028-I

Message consumer created: aa....aa

aa....aa: Message consumer

Description

This message is displayed when a message consumer is created.

KDAN14029-I

Message consumer closed: aa....aa

aa....aa: Message consumer

Description

This message is displayed when a message consumer is closed.

KDAN14030-I

Message delivered to consumer: aa....aa

aa....aa: Message consumer

Description

This message is displayed when a message is delivered to the consumer.

KDAN14031-I

Message producer created: aa....aa

aa....aa: Message producer

Description

This message is displayed when a message producer is created.

KDAN14032-I

Message producer closed: aa....aa

aa....aa: Message producer

Description

This message is displayed when a message producer is closed.

KDAN14033-I

Message producer sending message: aa....aa

aa....aa: Message producer

Description

This message is displayed when a message is sent to the destination.

KDAN14097-I

Re-creating consumers for the session: aa....aa

aa....aa: Session ID

Description

This message is displayed if the remote Broker fails when the specified acknowledgement type is AUTO_ACKNOWLEDGE.

KDAN14098-I

Consumers recreated for the session: aa....aa

aa....aa: Session ID

Description

This message is displayed if the remote Broker fails when the specified acknowledgement type is AUTO_ACKNOWLEDGE.

KDAN14103-I

Re-create message consumer for RA starting ...

Description

This message is displayed before the message consumer is re-created for the resource adapter.

KDAN14104-I

Re-create message consumer for RA finished ...

Description

This message is displayed after the message consumer is re-created for the resource adapter.

KDAN14107-I

Starting to exit connection ...

Description

This message is displayed before the connection is closed.

KDAN14108-I

Message consumer closed: aa....aa.

aa....aa: Consumer ID

Description

This message is displayed after the message consumer is closed.

KDAN14109-I

all sessions closed ...

Description

This message is displayed after closing all the sessions.

KDAN14110-I

closing all sessions ...

Description

This message is displayed before closing all the sessions.

KDAN14111-I

***** set logger aa....aa to level bb....bb

aa....aa: Logger name

bb....bb: Level

Description

This message is displayed when the log level is set up during the setting of the logging configuration.

KDAN14112-I

**** Handler: aa....aa

aa....aa: Handler class name

Description

This message is displayed when the log handler class name is displayed during the setting of the logging configuration.

KDAN14113-I

**** logging pattern: aa....aa

aa....aa: Value of the logging pattern

Description

This message is displayed when the logging pattern is displayed during the setting of the logging configuration.

KDAN14114-I

*** setting formatter to handler: aa....aa

aa....aa: formatter class name

Description

This message is displayed when the formatter class is displayed during the setting of the logging configuration.

KDAN14115-I

***** set handler aa....aa to loggerbb....bb

aa....aa: Handler class name

bb....bb: Logger name

Description

This message is displayed after the handler is set up in the logger.

KDAN14116-I

No consumer for pkt: aa....aa.

aa....aa: Packet

Description

This message is displayed when the message is sent.

KDAN14117-I

No Session for pkt: aa....aa.

aa....aa: Packet

Description

This message is displayed when the message is sent.

KDAN14118-I

##### closing session. consumer table size: aa....aa.

aa....aa: Number of consumers

Description

This message is displayed when the session is closed.

KDAN14119-I

***** consumer table size:aa....aa.

aa....aa: Number of consumers

Description

This message is displayed when the session is closed.

KDAN14120-I

SessionImpl.matchConsumerIDs: Consumer ID matches:aa....aa.

aa....aa: Consumer ID

Description

This message is displayed when the remote Broker fails.

KDAN14121-I

XA verifyPrepare(), jmqXid: aa....aa.

aa....aa: jmqXid

Description

This message is displayed when the preparation status is confirmed.

KDAN14122-I

transaction in prepared state: aa....aa.

aa....aa: Transaction ID

Description

This message is displayed when the preparation status is confirmed.

KDAN14125-I

read packet ... aa....aa

aa....aa: Packet

Description

This message is displayed when the packet is read.

KDAN14126-I

sent packet ... aa....aa

aa....aa: Packet

Description

This message is displayed when writing to the packet.

KDAN14127-I

Cleaning up consumers in session. SessionID: aa....aa

aa....aa: Session ID

Description

This message is displayed when the consumers are cleaned up when closing the session.

KDAN14128-I

RedirectURL= aa....aa:

aa....aa: Connection redirecting URL

Description

This message is displayed when the redirect URL is set up.

KDAN14129-I

transaction is in prepared state,committing the transaction: aa....aa:

aa....aa: Transaction ID

Description

This message is displayed when the transaction is in a prepared state.

KDAN14130-I

prepared transaction committed successfully: aa....aa:

aa....aa: Transaction ID

Description

This message is displayed when a prepared transaction is committed.

KDAN20001-E

Could not open persistent message store.

Description

An error occurred in CJMSP when an attempt was made to access a persistent store. The file used for persistence is corrupt or the configured file does not exist.

Action

Re-execute the operation. If the problem is not resolved, restart the Broker.

KDAN20002-E

Defaulting to use the fallback properties. The Broker will only run in a minimal configuration using these settings. Fallback properties are being used because the defaults.property files could not be loaded. Please check the value of CJMSP_HOME.

Description

This error occurs when CJMSP cannot find the default.properties file.

Action

Contact maintenance personnel.

KDAN20003-E

Unable to load Persistence Store implementation class aa....aa.

Instance properties cannot be loaded or saved.

aa....aa: Name of the class that performs persistence

Description

An error occurred when CJMSP attempted to load the Persistence Store class that performs persistence. A possible cause is that the CJMSP-related JAR file does not exist in the class path.

Action

Confirm that the class path shows the CJMSP-related JAR file.

If the problem is not resolved, contact maintenance personnel since an internal error might have occurred.

KDAN20004-E

Unable to store modified properties in file aa....aa.

aa....aa: Location of the config.properties file

Description

This error occurs when CJMSP attempted to update the configuration file. A possible cause is that the configuration file is read only.

Action

Make sure that the configuration file has the write permission for the applicable user.

KDAN20005-E

No threads are available to process a new connection on service aa....aa. bb....bb threads out of a maximum of cc....cc threads are already in use by other connections. A minimum of 2 threads must be available to process the connection. Please either limit the # of connections or increase the imq.<service>.max_threads property. Closing the new connection.

aa....aa: Service name

bb....bb: Number of executing threads

cc....cc: Maximum number of threads

Description

This error occurs when the number of CJMSP connections for a particular service has exceeded the specified maximum number of connections.

Action

Set up a value greater than the expected number of connections in the imq.<service_name>.max_threads property.

The other connections to CJMSP might have closed; therefore, wait for some time, and then reconnect.

KDAN20007-E

Failed to open persistent store.

Description

An error occurred when CJMSP attempted to load the Persistence Store class that performs persistence. A possible cause is that the CJMSP-related JAR file does not exist in the class path.

Action

Confirm that the class path shows the CJMSP-related JAR file.

If the problem is not resolved, contact maintenance personnel since an internal error might have occurred.

KDAN20008-E

Message aa....aa on destination bb....bb could not be found in the store.

aa....aa: Message id

bb....bb: Destination name

Description

This error occurs when CJMSP attempts to acquire, delete, or update a message using an ID that does not exist in the persistence store.

Action

Make sure that the message exists in the persistence store.

KDAN20009-E

Message aa....aa on destination bb....bb exists in the store already.

aa....aa: System message ID of the JMS message

bb....bb: Destination name

Description

All the error messages have a unique ID that is automatically generated by CJMSP.

This error occurs when the CJMSP message ID generator generates an already existing ID.

Action

An internal error occurred. Contact maintenance personnel.

KDAN20010-E

Unable to start service aa....aa.

aa....aa: Service name

Description

This error occurs when an attempt is made to start the CJMSP Broker. A possible cause is that a required configuration is missing.

Action

See the CJMSP manual and specify the required configuration information in the config.properties file.

If the problem is not resolved, contact maintenance personnel.

KDAN20011-E

Consumer aa....aa on destination bb....bb exists in the store already.

aa....aa: Unique consumer ID

bb....bb: Destination name

Description

All the consumers have a unique ID that is automatically generated by CJMSP.

This error occurs when the CJMSP consumer ID generator generates an already existing ID.

Action

An internal error occurred. Contact maintenance personnel.

KDAN20012-E

Consumer aa....aa on destination bb....bb could not be found in the store.

aa....aa: Unique consumer ID

bb....bb: Destination name

Description

This error occurs when CJMSP attempts to acquire, delete, or update a consumer using an ID that does not exist in the persistence store.

Action

An internal error occurred. Contact maintenance personnel.

KDAN20013-E

Destination aa....aa exists in the store already.

aa....aa: Destination name

Description

This error occurs when the user attempts to create a destination using an existing name.

Action

Make sure that the destination name to be created does not exist in CJMSP. Specify a unique destination name.

KDAN20014-E

Destination aa....aa could not be found in the store.

aa....aa: Destination name

Description

This error occurs when a destination with the specified name does not exist in CJMSP.

Action

Confirm that the destination with the specified name exists in CJMSP.

KDAN20015-E

State of consumer aa....aa for message bb....bb could not be found in the store.

aa....aa: Unique consumer ID

bb....bb: Unique message ID

Description

This error occurs when CJMSP attempts to acquire the status information of a consumer that does not exist in the store.

Action

Make sure that the consumer exists in the persistence store.

KDAN20016-E

Transaction ID aa....aa exists in the store already.

aa....aa: Transaction ID

Description

This error occurs when CJMSP attempts to store the transaction information in the persistence store. A possible cause is that the transaction ID generated by CJMSP already exists in the persistence store.

Action

An internal error occurred. Contact maintenance personnel.

KDAN20017-E

Transaction ID aa....aa could not be found in the store.

aa....aa: Transaction ID

Description

This error occurs when CJMSP attempts to acquire, delete, or update the transaction information. A possible cause is that the relevant transaction ID does not exist in the persistence store.

Action

An internal error occurred. Contact maintenance personnel.

KDAN20018-E

Failed to create the store hierarchy - aa....aa

aa....aa: Directory to be created

Description

This error occurs when CJMSP fails to create the directory while creating a file for the file persistence store. A possible cause is that the user does not have the write permission for the relevant directory.

Action

Confirm that the user has the permission to create the directory.

KDAN20019-E

Unable to run the service aa....aa, the broker will no longer accept connections on this service.

aa....aa: Service name

Description

This error occurs when an attempt is made to start the CJMSP Broker. A possible cause is that a required configuration is missing.

Action

See the CJMSP manual and specify the required configuration information in the config.properties file.

If the problem is not resolved, contact maintenance personnel.

KDAN20023-E

Could not run the service aa....aa on port bb....bb:

aa....aa: Service name

bb....bb: Port number

Description

This error occurs when the specified port is invalid or is in use.

Action

Set up a different port number, and then restart the Broker. Confirm that the specified port number is not in use.

KDAN20025-E

Failed to load JDBC driver: aa....aa

aa....aa: JDBC driver URL

Description

This error occurs when the specified JDBC URL is invalid or the specified class path does not refer the JDBC driver JAR file.

Action

Confirm that the JDBC driver JAR file is specified in the class path.

KDAN20032-E

Bad name value pair specified (aa....aa) for option: bb....bb.Please use the format: name=value

aa....aa: Used invalid name/ value pair

bb....bb: Used option

Description

This error occurs when the name or value specified in the command line option is null.

Action

Specify a valid name/ value pair.

KDAN20035-E

Error detected while validating command line options.

Description

The path file was not found in the specified location.

Action

Contact maintenance personnel for internal errors.

KDAN20042-E

Internal Error

Description

An unexpected error occurred in CJMSP.

Action

An internal error occurred. Contact maintenance personnel.

KDAN20048-E

User aa....aa already exists in the password file.

aa....aa: Existing user name

Description

This message is displayed when an existing user name is specified in the "etc" location of the CJMSP instance while adding the user information (example: cjmsusermgr add -u guest -p guest).

Action

Specify a unique user name.

KDAN20055-E

Invalid option aa....aa

aa....aa: Command line option

Description

This error occurs when an invalid command line argument is passed.

Action

Specify a valid command line option.

KDAN20058-E

Acknowledgement aa....aa for Transaction ID bb....bb already exists in the store.

aa....aa: Acknowledgement

bb....bb: Transaction ID

Description

This error occurs when CJMSP attempts to persist the acknowledgement for transaction in the persistence store. A possible cause is that the acknowledgement for the relevant transaction already exists in the persistence store.

Action

An internal error occurred. Contact maintenance personnel.

KDAN20060-E

Exception when pausing service aa....aa

aa....aa: Service

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN20062-E

Could not start the Broker's portmapper service because hostname/ port is invalid.

Description

This error occurs when the port is being used in another application (another instance of the Broker).

This error occurs when the host name is invalid.

Action

Specify another port number, and then restart the Broker. Confirm that the specified port number is not in use.

Specify a valid host name.

KDAN20063-E

Portmapper got an exception in accept(). Continuing

Description

An I/O error occurred when a client connection was standby.

Action

Make sure that the network connection is correct.

KDAN20064-E

Portmapper could not create ServerSocket. Exiting.

Description

An unexpected error occurred when creating the server socket.

Action

An internal error occurred. Contact maintenance personnel.

KDAN20066-E

Invalid timestamp specified (aa....aa), timestamp should be greater than 0.

aa....aa: Time stamp

Description

This message is displayed when the time stamp specified in the configuration file is invalid.

Action

Make sure that the value of the time stamp specified in the configuration file is 0 or more.

KDAN20075-E

The message aa....aa has an associated acknowledgement list already.

aa....aa: Unique ID for the message

Description

All the messages are associated with a consumer list. This error occurs when CJMSP stores the specified consumer list and the states in the file/JDBC store so that the list and the states correspond to the specified message IDs.

A possible cause is that the generated message IDs already exist.

Action

An internal error occurred. Contact maintenance personnel.

KDAN20076-E

The arrays for consumer ids and states have different size or are empty.

Description

This error occurs when an attempt is made to store the specified consumers and states.

When the consumer does not exist in the store

When the consumer ids and states have different sizes

Action

Confirm that the consumer exists in the store.

KDAN20077-E

The Broker got an exception when trying to acquire the lock file: aa....aa, bb....bb

The lock file may be corrupted, or there may be a permission problem with the lock file or the directory that contains the lock file. If you are certain no other copy of the Broker is running with the instance name "cc....cc" then you may remove the lock file and try starting the Broker again.

aa....aa: Lock file path

bb....bb: Detailed exception message

cc....cc: Instance name

Description

This message is displayed when the lock file is corrupted, or when there is a permission problem with the lock file or the directory that stores the lock file.

Action

If you are certain that no other copy of Broker is running with the applicable instance name, then delete the lock file and restart the Broker.

KDAN20078-E

The broker has detected an active lock file: aa....aa This file indicates that there is another copy of the broker running on bb....bb that is also using the instance name "cc....cc". Please use a different instance name or terminate the broker on bb....bb.

aa....aa: Lock file path

bb....bb: Host:Port

cc....cc: Instance name

Description

This error occurs when a Broker instance is started or deleted. Take action based on the following causes:

When the same Broker instance is already running on another port

When the Broker to be deleted is running

Action

Before starting the Broker instance, make sure that the Broker instance is not running. If the instance is running, stop the instance, and then restart.

Stop, and then delete the Broker instance.

KDAN20079-E

Cannot update port number in lock file

Description

An I/O error occurred when the host name or port was updated in the lock file.

Action

Make sure that the lock file permissions are appropriate.

KDAN20085-E

Unexpected Broker Internal Error : [aa....aa].

aa....aa: Reason for internal error

Description

An internal error occurred.

Action

An internal error occurred. Contact maintenance personnel.

KDAN20086-E

Error retrieving persisted data

Description

This error occurs when CJMSP attempts to load the destination information from the persistence store. Take action based on the following causes:

In the case of file-based persistence, this error occurs when a file is corrupted or is not found.

In the case of database-based persistence, this error occurs when a table is corrupted or has not been created.

Action

An internal error occurred. Contact maintenance personnel.

KDAN20087-E

Store method accessed after the store is closed.

Description

This error occurs when an operation closes a persistence store and another operation attempts to save information in that persistence store.

Action

Make sure that the persistence store is open.

KDAN20091-E

Attempt to free memory failed, taking more drastic measures.

Description

An OutofMemory error occurred in CJMSP during the processing of a packet received by the handler. The possible causes are as follows:

When the memory or disk size assigned to CJMSP is inadequate

When the JVM heap size of the CJMSP Broker is exceeded

Action

Make sure that CJMSP is configured with the appropriate memory and disk size.

For details on the memory and disk size configuration, see the CJMSP manual.

Increase the JVM heap size of the CJMSP Broker.

KDAN20093-E

Cannot update service port number dynamically. The change will take effect after a broker restart.

Description

An internal error occurred during service update.

Action

Contact maintenance personnel.

KDAN20097-E

No such transaction: aa....aa.

aa....aa: Transaction ID

Description

This error occurs when CJMSP attempts to acquire transaction information from the persistence store. A possible cause is that the relevant transaction ID does not exist in the persistence store.

Action

Re-execute the operation. If the problem is not resolved, contact maintenance personnel.

KDAN20098-E

Cannot perform operation. Transaction aa....aa is not in PREPARED state.

aa....aa: Transaction ID

Description

This error occurs when the user attempts to commit a transaction when the transaction is not in PREPARED state.

Action

Before committing a transaction, confirm that the transaction has been started.

KDAN20099-E

File aa....aa contains bad file magic number.

aa....aa: File name

Description

This error occurs when the magic number in the configrecord file does not match the defined magic number. The file might be corrupted.

Action

An internal error occurred. Contact maintenance personnel.

KDAN20100-E

Failed to reset store, cannot remove: aa....aa

aa....aa: File name

Description

The user does not have the permission to delete the file.

Action

Make sure that the file permissions are appropriate.

KDAN20101-E

Failed to encrypt password: aa....aa

aa....aa: Exception string

Description

This error occurs when the password cannot be encrypted when the user information is added or updated.

Action

Use an appropriate encryption method.

KDAN20102-E

The broker instance "aa....aa" does not exist.

aa....aa: Instance name

Description

This error occurs when an invalid Broker instance is specified when the Broker is started.

Action

Confirm that the specified Broker instance name is valid.

KDAN20103-E

Failed to remove file store: aa....aa

aa....aa: File name

Description

The user does not have permission to remove the file.

Action

Make sure that the user has the permission to delete the file or directory.

KDAN20107-E

Old persistent store might be corrupted: found unexpected version aa....aa. Expected bb....bb.

aa....aa: File version

bb....bb: Version

Description

The old file version is corrupted and does not contain a parsable integer.

KDAN20108-E

Old persistent store might be corrupted: no version file aa....aa exists.

aa....aa: Version file name

Description

The old file version does not exist.

Action

Confirm that the old file version exists.

KDAN20109-E

No table schema specified for table aa....aa by imq.persist.jdbc.table.aa....aa

aa....aa: Database table name

Description

This error occurs when a database that is not supported in CJMSP is used for the JDBC store.

Action

Specify or use a database that is supported in CJMSP.

KDAN20110-E

Unknown destination bb....bb of type aa....aa.

aa....aa: Destination type

bb....bb: Destination name

Description

This error occurs when the applicable destination does not exist in CJMSP while acquiring the information or deleting the destination.

Action

Specify a valid destination that exists in CJMSP.

KDAN20111-E

Unsupported persistent store found at aa....aa.

aa....aa: Directory path name

Description

An unsupported store was found in CJMSP instance persistence store (example: a directory named file store "fs370" and "fs360" was created).

Action

Delete the unsupported persistence store (directory) from the CJMSP instance file store location.

KDAN20112-E

No such connection: aa....aa

aa....aa: Connection identifier

Description

This error occurs when the relevant connection is not found in CJMSP while destroying the connection or acquiring the connection information.

Action

Specify an appropriate connection.

KDAN20116-E

Destination is not paused.

Description

This error occurs when the destination to be compressed is not paused.

Action

Before compressing a destination, pause the destination.

KDAN20117-E

Some destinations are not paused.

Description

This error occurs if some destinations are not paused when compressing all the destinations.

Action

Pause all the destinations, and then perform the compress operation.

KDAN20119-E

The broker instance "aa....aa" does not exist. Run the broker to create the instance before using the user manager utility.

aa....aa: Instance name

Description

This error occurs when the Broker instance does not exist during the execution of the user manager (cjmsusermgr) command line utility.

Action

Start CJMSP, and then create the instance.

KDAN20120-E

Unable to parse property aa....aa.

aa....aa: Property name

Description

This error occurs when an incompatible data type value is specified in the property file.

Action

Specify an appropriate data type value in the property file.

KDAN20122-E

Unable to use CJMS_VAR_HOME aa....aa.

aa....aa: Reason for the unavailability of the path

Description

This error occurs when an invalid directory path is specified in CJMSP home.

Action

Make sure that the CJMSP home directory path is correct.

KDAN20125-E

Broker is forcibly closing the connection to aa....aa.

aa....aa: is connection ID

Description

An OutofMemory error occurred in the communication between CJMSP and client.

Action

Create a new connection with CJMSP.

KDAN20126-E

Unable to read message aa....aa.

aa....aa: Message ID

Description

An invalid destination has been specified.

An invalid message ID has been specified.

Action

Make sure that a valid destination is specified.

KDAN20127-E

Unable to remove message aa....aa.

aa....aa: Message ID

Description

An error occurred when removing the message.

The message was not found in the store.

Action

Make sure that the message exists in the persistence store.

KDAN20128-E

Unable to load durable subscriptions

Description

The following errors occurred when loading the destination:

All the consumers could not be acquired.

The destination could not be acquired from CJMSP.

The consumer could not be added to the destination.

Action

Restart CJMSP or contact maintenance personnel.

KDAN20129-E

Unable to store durable subcription aa....aa bb....bb for destination cc....cc.

aa....aa: Durable subscriber name

bb....bb: Client ID

cc....cc: Destination name

Description

The following errors occurred when storing the durable subscriber:

A consumer with the same ID already exists in the store.

An I/O error occurred during consumer persistence.

Action

Make sure that a consumer with the same ID does not exist in the store.

KDAN20130-E

Unable to remove durable subcription aa....aa bb....bb from destination cc....cc.

aa....aa: Durable subscriber name

bb....bb: Client ID

cc....cc: Destination name

Description

The following errors occurred when removing the durable subscriber:

The consumer was not found in the store.

An I/O error occurred when removing the consumer.

Action

Make sure that the specified consumer exists in the store.

KDAN20131-E

Unable to create durable subcription aa....aa bb....bb from destination cc....cc.

aa....aa: Durable subscriber name

bb....bb: Client ID

cc....cc: Destination name

Description

The following errors occurred when storing the durable subscriber:

A consumer with the same ID already exists in the store.

An I/O error occurred when persisting the consumer.

Action

Make sure that a consumer with the same ID does not exist in the store.

KDAN20132-E

Unable to resolve hostname ''aa....aa''

aa....aa: Host name that could not be converted to IP address

Description

An invalid host name has been specified.

Action

Specify a valid host name for the Broker instance.

KDAN20133-E

Unable to resolve hostname ''aa....aa'' specified by property ''bb....bb''

aa....aa: Host name

bb....bb: Property name

Description

This error occurs when an invalid host name is specified as the portmapper host name in config.properties. In this case, CJMSP will terminate.

Action

Specify a valid host name in the portmapper host name.

KDAN20134-E

Unable to resolve local hostname

Description

The IP address was not found on the local machine.

Action

Confirm that the local machine has an IP address.

KDAN20135-E

Invalid Java version: aa....aa. Minimum Java version required: bb....bb.

aa....aa: Message id

bb....bb: Message id

Description

A JRE version older than 1.4 has been installed. In this case, you cannot use CJMSP.

Action

Contact maintenance personnel.

KDAN20138-E

Cannot create address URL for broker. URL string used: aa....aa

aa....aa: String/ url

Description

This error occurs when the host name value specified in the config.properties file is invalid.

Action

Specify a valid host name value.

KDAN20142-E

The portmapper service got an exception processing a request from client aa....aa. The client may need to attempt the connection again

aa....aa: IP address

Description

The following errors occurred when writing the portmapper data:

The socket was closed.

An I/O error occurred when writing the portmapper data into the specified DataOutputStream.

Action

Confirm that the network connection is appropriate.

Confirm that the I/O device or driver is running.

Contact the System Administrator.

KDAN20158-E

Unable to shutdown a broker that is running in process.

Description

This error occurs when CJMSP is shut down during the processing of a message.

Action

Shut down CJMSP after the message processing is finished.

KDAN20159-E

Failed to create transaction log file aa....aa.

aa....aa: File name

Description

An I/O error occurred while the log writer was being created.

Action

Make sure that the root directory permissions are appropriate.

KDAN20160-E

Unable to process transaction log record with sequence aa....aa: bb....bb.

aa....aa: Sequence value

bb....bb: Record type

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN20162-E

Failed to reconstruct persistence store from transaction log files.

Description

An I/O error occurred while restoring the persistence store from the transaction log files.

Action

Check whether the file-based permissions are appropriate.

KDAN20164-E

Failed to purge messages on destination aa....aa.

aa....aa: Destination name

Description

This error occurs when the destination is purged. Take action based on the following causes:

The applicable destination does not exist in the store.

An I/O error occurred when deleting the message.

Action

Make sure that the applicable destination exists in the store.

KDAN20165-E

Unable to open protocol bb....bb for cc....cc service using aa....aa.

aa....aa: Protocol class

bb....bb: Protocol type

cc....cc: Instance name

Description

This error occurs when the specified port is being used in another application.

This error occurs when an invalid host name is specified.

Action

Make sure that the same port number is not used in another application.

Specify a valid host name.

KDAN20166-E

aa....aa protocol unavailable: cannot load protocol class needed for service bb....bb.

aa....aa: Protocol class

bb....bb: Service name

Description

This error occurs when an invalid protocol class name is specified when creating the service.

Action

Contact maintenance personnel.

KDAN20167-E

Unable to start service aa....aa: missing property bb....bb.

aa....aa: Service name

bb....bb: Missing property

Description

This message is displayed when null is specified in the value of the protocol type property.

Action

Check whether a valid value is specified in the protocol type property.

KDAN20168-E

Failed to persist message aa....aa.

aa....aa: Message ID

Description

The user does not have the write permission for the message-related file.

The message-related file is corrupted.

Action

Grant the write permission to the file that stores the message.

Re-execute the Broker. In this case, the old data is lost.

KDAN20169-E

Failed to retrieve message aa....aa for destination bb....bb.

aa....aa: Message ID

bb....bb: Destination name

Description

An I/O error occurred while obtaining a message from the persistence store.

Action

Make sure that the network connection is correct.

KDAN20171-E

Unable to unsubscribe to durable topic aa....aa with [Durable Name, Client ID] = [bb....bb, cc....cc]: consumer is in use.

aa....aa: Destination name

bb....bb: Consumer durable name

cc....cc: Consumer client ID

Description

This error occurs when an attempt is made to unsubscribe the durable subscriber being used in the consumer.

Action

Make sure that the persistence subscriber specifying a consumer is not used.

KDAN20172-E

Failed to persist consumer aa....aa.

aa....aa: Consumer ID

Description

The user does not have the write permission for the message file store.

The message file store is corrupted.

A consumer with the same name already exists in the store.

A runtime exception occurred when saving the consumer identified by the consumer ID.

Action

Grant the write permission to the file store that saves the message.

Restart CJMSP. In this case, the old data is lost.

KDAN20174-E

Failed to persist destination aa....aa.

aa....aa: Destination name

Description

An error occurred while a file was being accessed.

The data is corrupted.

A runtime exception occurred during an attempt to store the destination in the persistence store.

A runtime exception occurred during an attempt to update the destination in the persistence store.

Action

Check whether the file-based permissions are appropriate.

KDAN20175-E

Failed to persist state of consumer aa....aa for message bb....bb.

aa....aa: Consumer id

bb....bb: Message id

Description

The specified message does not exist in the persistence store.

The consumer is not associated with the message.

An error occurred while a file was being accessed.

The data is corrupted.

Action

Restart CJMSP. In this case, the old data is lost.

Check whether the file-based permissions are appropriate.

KDAN20176-E

Could not locate destination aa....aa.

aa....aa: Destination name

Description

This error occurs when the specified destination does not exist in the store.

Action

Confirm that the specified destination exists in the store.

KDAN20177-E

Failed to persist transaction aa....aa.

aa....aa: Transaction id

Description

An error occurred while a file was being accessed.

The data is corrupted.

A runtime exception occurred during an attempt to store the transaction in the persistence store.

A runtime exception occurred during an attempt to update the transaction in the persistence store.

Action

Make sure that the file permissions are appropriate.

KDAN20178-E

while reading from passfile

Description

The user does not have the read permission for the user information-related file.

The file is corrupted.

Action

Grant the read permission to the user information-related file.

Restart CJMSP. In this case, the old data is lost.

KDAN20179-E

The Maximum Number of messages currently in the system [ aa....aa ] has been exceeded, rejecting message bb....bb.

aa....aa: Maximum number of messages

bb....bb: Message id

Description

This message is displayed when the maximum number of messages is exceeded.

Action

Increase the upper limit for the maximum number of messages.

KDAN20180-E

The Maximum Size limit for the messages currently in the system [ aa....aa ] has been exceeded, rejecting message bb....bb.

aa....aa: System id

bb....bb: Message id

Description

This message is displayed when the maximum size for the total number of messages is exceeded.

Action

Increase the maximum size for the total number of messages.

KDAN20181-E

The size [ aa....aa bytes ] of Message bb....bb is larger than the individual message limit (maxBytesPerMsg) of cc....cc bytes, rejecting the message.

aa....aa: Maximum message size

bb....bb: Message ID

cc....cc: Maximum bytes/ message

Description

This error occurs when the message size exceeds the system-defined individual message limit.

Action

Increase the individual message size.

Specify a message size as infinite.

KDAN20182-E

Invalid property value: aa....aa = bb....bb.

aa....aa: Property name

bb....bb: Property value

Description

This error occurs when the property value is not specified.

This error occurs when an invalid property value is specified.

This error occurs when the property value does not have a parsable integer.

Action

Specify a valid property value.

KDAN20183-E

Invalid property: aa....aa.

aa....aa: Property name

Description

This error occurs when an invalid property name is specified.

Action

Specify a valid property name.

KDAN20184-E

Failed to load destinations from store.

Description

An I/O error occurred while obtaining the destination from the persistence store.

Action

Make sure that the network connection is correct.

Check whether the I/O device or driver is running.

Contact the System Administrator.

KDAN20185-E

Failed to load transactions from store.

Description

An I/O error occurred while obtaining the transaction from the persistence store.

Action

Make sure that the network connection is correct.

Check whether the I/O device or driver is running.

Contact the System Administrator.

KDAN20187-E

Failed to remove consumer aa....aa from store.

aa....aa: Consumer id

Description

An error occurred while a file was being accessed.

The data is corrupted.

A runtime error occurred while deleting the consumer from the persistence store.

Action

Make sure that the file permissions are appropriate.

KDAN20188-E

Failed to load consumers from store.

Description

This message is displayed when an invalid varhome location is specified when the Broker is started.

An I/O error occurred while obtaining the consumer from the persistence store.

Action

Make sure that the value specified in the varhome location is appropriate.

KDAN20194-E

Connection not authenticated.

Description

This error occurs when a connection is not authenticated.

Action

Contact maintenance personnel.

KDAN20196-E

Access Control class not defined for type aa....aa.

aa....aa: Access control type

Description

This error occurs when the access control class is not specified.

Action

Contact maintenance personnel.

KDAN20202-E

aa....aa is not an administrator

aa....aa: User name

Description

The specified user does not have administrator privileges.

Action

Make sure that the relevant user has the administrator privileges.

KDAN20203-E

Failed to load transaction acknowledgements from store.

Description

An I/O error occurred while obtaining the transaction acknowledgements from the persistence store.

Action

Make sure that the network connection is correct.

KDAN20204-E

Failed to clear the transaction acknowledgement file: aa....aa.

aa....aa: File name

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN20205-E

Failed to persist acknowledgement aa....aa for transaction bb....bb.

aa....aa: Acknowledgement

bb....bb: Transaction ID

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN20206-E

No such service: aa....aa.

aa....aa: Name of the non-existent service

Description

This message is displayed when an invalid service name is specified.

Action

Make sure that the specified service name is appropriate.

KDAN20207-E

Unable to unsubscribe to consumer with a durable name of aa....aa and a client ID of bb....bb - consumer does not exist.

aa....aa: Durable name

bb....bb: Consumer name

Description

This error occurs when an attempt is made to unsubscribe a consumer that is already deleted.

Action

Unsubscribe only when the consumer is not already unsubscribed.

KDAN20209-E

Failed to remove acknowledgements for transaction aa....aa.

aa....aa: Transaction ID

Description

A runtime exception occurred when removing all the acknowledgements of the specified transaction ID.

Action

Check the log file, and then take appropriate measures.

KDAN20210-E

Cannot use Transaction ID aa....aa : ID is currently in use.

aa....aa: Transaction ID

Description

This error occurs when the specified transaction ID already exists and is in use.

Action

Contact maintenance personnel.

KDAN20211-E

Error storing information associated with Transaction aa....aa: data may be lost if the Broker exits before the transaction completed.

aa....aa: Transaction id

Description

This message is displayed when the user does not have the appropriate file permissions while the transaction-related information is being stored.

Action

Check whether the file-based permissions are appropriate.

KDAN20212-E

Cannot create Destination aa....aa - the destination already exists.

aa....aa: Destination name

Description

This error occurs when an attempt is made to re-create an existing destination.

Action

Specify a unique name for the destination.

KDAN20215-E

Forbidden authenticated name aa....aa from service bb....bb[cc....cc] on administration destination.

aa....aa: Principal name

bb....bb: Service name

cc....cc: Service type

Description

This message is displayed when a non-admin service attempts to access the destination.

This message is displayed when a restricted admin service attempts to access the destination.

Action

Use the ADMIN service to access the destination.

Grant the permission to access the destination to the ADMIN service.

KDAN20221-E

Failed to load configuration change records from store.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20222-E

Failed to persist configuration change record with timestamp aa....aa.

aa....aa: Time stamp

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20223-E

No properties modified for service: aa....aa.

aa....aa: Service name

Description

The specified port number is invalid.

Action

Make sure that the specified number is correct.

KDAN20224-E

Unable to destroy destination: aa....aa, because bb....bb

aa....aa: Destination name

bb....bb: Cause of error

Description

The specified destination is a dead message queue and the dead message queue cannot be destroyed.

The destination does not exist.

An invalid destination ID has been specified.

Action

Make sure that the destination is not a dead message queue.

Specify a valid destination.

KDAN20225-E

The Destination of aa....aa contains invalid characters.

aa....aa: Information about the JMQ destination

Description

The specified sending name contains invalid characters.

Action

Specify a valid destination name.

KDAN20226-E

Could not resume service: aa....aa, because bb....bb

aa....aa: Destination name

bb....bb: Exception message

Description

An invalid service name has been specified.

The service could not be paused/resumed.

Action

Make sure that a valid service name is specified.

KDAN20227-E

Durable subscription aa....aa:bb....bb is already active on destination cc....cc.

aa....aa: Durable name

bb....bb: Client ID

cc....cc: Destination ID

Description

The specified durable subscriber is already active on the destination.

Action

Create a unique durable subscriber.

KDAN20228-E

Failed to clear all records from configuration change record tables.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20232-E

Access non-administration destination aa....aa denied for restricted administration service bb....bb.

aa....aa: Destination name

bb....bb: Service name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20234-E

Failed to persist consumer list for message aa....aa.

aa....aa: Message ID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20235-E

Cannot remove lock file.

Description

An I/O error occurred when creating a socket. The lock file could not be removed.

Action

Make sure that the lock file permissions and network connection are correct.

KDAN20236-E

Failed to load message aa....aa from store.

aa....aa: Message ID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20237-E

Connection logged out.

Description

An invalid authentication type is specified.

The authentication protocol handler is not specified.

Action

Contact maintenance personnel.

KDAN20238-E

Invalid client ID aa....aa.

aa....aa: Client ID sent from the client

Description

The client ID for creating the connection consumer is null.

The client ID is null or space during the set up of the client ID.

Action

Specify a valid client ID value (excluding null and space).

KDAN20239-E

Minimum threads aa....aa greater than maximum threads bb....bb.

aa....aa: Minimum thread value

bb....bb: Maximum thread value

Description

This error occurs when the minimum thread value is greater than the maximum thread value.

Action

Make sure that the minimum thread value is always smaller than the maximum thread value.

KDAN20240-E

Failed to persist property aa....aa.

aa....aa: Property name

Description

An internal error occurred when updating a property.

Action

Contact maintenance personnel.

KDAN20241-E

Failed to load properties from store.

Description

An access error occurred while obtaining the property information from the file.

The data is corrupted.

Action

Make sure that the file permissions are appropriate.

KDAN20242-E

Verification of persistent store version failed with exception.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20243-E

Unable to set thread values to min=aa....aa max=bb....bb.

aa....aa: Minimum value

bb....bb: Maximum value

Description

This error occurs when an attempt is made to set up a minimum thread value that is greater than the maximum thread value.

Action

Make sure that the minimum thread value is smaller than the maximum thread value.

KDAN20244-E

Unexpected Broker Exception: [aa....aa].

aa....aa: Exception message

Description

An exception occurred due to a Broker internal error.

Action

Check the log file, and then take the appropriate measures.

KDAN20245-E

Cannot store message aa....aa on destination bb....bb. The message limit (maxNumMsgs) of cc....cc has been reached.

aa....aa: sysmsgid

bb....bb: Destination name

cc....cc: Limit

Description

This error occurs when the number of messages at the destination exceeds the maximum value.

Action

Increase the maximum number of messages for the destination.

KDAN20246-E

Cannot store message aa....aa on destination bb....bb. The byte limit (maxTotalMsgBytes) of cc....cc bytes has been reached.

aa....aa: sysmsgid

bb....bb: Destination name

cc....cc: Limit

Description

This error occurs when the total message byte size at the destination exceeds the maximum value.

Action

Increase the total message bytes for the destination.

KDAN20247-E

Cannot store message aa....aa on destination bb....bb. The message size of cc....cc bytes is larger than the individual message byte limit (maxBytesPerMsg) of dd....dd bytes.

aa....aa: sysmsgid

bb....bb: Destination name

cc....cc: Limit

dd....dd: Exceeded value

Description

This error occurs when the message size exceeds the maximum size (byte limit) for an individual message.

Action

Increase the individual message size for the destination.

KDAN20254-E

Port number conflict. Please use different port numbers for TCP and HTTP services.

Description

This error occurs when the specified port number is in use.

Action

Specify a unique port number.

KDAN20256-E

Cannot add durable consumer aa....aa. No ClientID was set on connection.

aa....aa: Consumer ID

Description

This error occurs when the client ID is not set up for the connection during the creation of a consumer.

Action

Set up a valid client ID for the connection.

KDAN20257-E

The thread pool maximum for service aa....aa cannot be set to bb....bb.

aa....aa: Service name

bb....bb: Maximum number of threads

Description

This error occurs when the maximum number of threads is set up to 0 (zero).

Action

Set up the maximum number of threads to a value greater than 0 (zero).

KDAN20260-E

Failed to clear transactions that are not in state aa....aa, all transactions will be cleared.

aa....aa: State of the transaction to be excluded

Description

A runtime exception occurred when clearing all the transactions that are not in the specified state.

Action

For details, reference the log file, and then take action.

KDAN20261-E

Broker is shutting down.

Description

This error occurs when an operation is executed for CJMSP when CJMSP is shutting down.

Action

Confirm that CJMSP is running.

KDAN20262-E

Failed to upgrade configuration change record.

Description

An I/O error occurred when upgrading the configuration change record.

Action

Confirm that the file has the appropriate access permission.

KDAN20263-E

Failed to parse message from a VRecord for destination aa....aa.

aa....aa: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20264-E

Failed to remove destination aa....aa.

aa....aa: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20265-E

Failed to load messages for destination aa....aa from store.

aa....aa: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20266-E

Failed to release message directory aa....aa for destination bb....bb.

aa....aa: Directory name

bb....bb: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20267-E

Failed to load message directory aa....aa for destination bb....bb.

aa....aa: Directory name

bb....bb: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20268-E

Got exception while reading packet size from file aa....aa.

aa....aa: File name

Description

An I/O error occurred when reading a record.

Action

Confirm that the file has the property permissions and is not corrupt.

KDAN20269-E

Resetting messages failed; failed to remove all files in aa....aa.

aa....aa: Directory name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20273-E

Failed to upgrade messages.

Description

An I/O error occurred when a message was upgraded from the old store.

Action

Confirm that the message store has appropriate permissions.

KDAN20274-E

Failed to upgrade properties from aa....aa to bb....bb.

aa....aa: Old file

bb....bb: Backing file

Description

An I/O error occurred when a property was upgraded from the old store.

Action

Confirm that the message store has appropriate permissions.

KDAN20275-E

Failed to upgrade durables from aa....aa to bb....bb.

aa....aa: Old file

bb....bb: Backing file

Description

An I/O error occurred when a consumer was upgraded from the old store.

Action

Confirm that the message store has appropriate permissions.

KDAN20276-E

Failed to upgrade transaction acknowledgement from aa....aa to bb....bb.

aa....aa: Old file

bb....bb: Backing file

Description

An I/O error occurred when a transaction acknowledgement was upgraded from the old store.

Action

Confirm that the message store has appropriate permissions.

KDAN20277-E

Failed to upgrade transactions from aa....aa to bb....bb.

aa....aa: Old file

bb....bb: Backing file

Description

An I/O error occurred when a transaction was upgraded from the old store.

Action

Confirm that the message store has appropriate permissions.

KDAN20278-E

Failed to upgrade destinations from aa....aa to bb....bb.

aa....aa: Old file

bb....bb: Backing file

Description

An I/O error occurred when a destination was upgraded from the old store.

Action

Confirm that the message store has appropriate permissions.

KDAN20279-E

Failed to load configuration change records from old store aa....aa.

aa....aa: Old file

Description

An I/O error occurred when a configuration change record was upgraded from the old store.

Action

Check whether the persistence store permissions are appropriate.

KDAN20280-E

Could not compact destinations, because aa....aa

aa....aa: Exception string

Description

The destinations were not paused when the cjmsicmd compact dst command was used to compress the destinations.

Action

Before compressing destinations (before using the cjmsicmd pause dst command), pause all the destinations.

KDAN20281-E

Could not compact destination: aa....aa, because bb....bb

aa....aa: Destination name

bb....bb: Exception string

Description

The destination is not paused when the cjmsicmd compact dst -n destination-name -t destination-type command was used to compress one destination.

Action

Before compressing destinations (before using the cjmsicmd pause dst -n destination-name -t destination-type command), pause the applicable destination.

KDAN20292-E

The following destination cannot be created: aa....aa. Destination names starting with "bb....bb" are reserved for internal Message Queue use. They cannot be created administratively.

aa....aa: Destination name

bb....bb: Prefix of the internal destination name (example: mq)

Description

When creating a destination, if the destination name begins with mq., the destination is not to be created.

Action

Make sure that the destination name does not begin with mq.(dot).

KDAN20293-E

Cannot create property file aa....aa.

aa....aa: Property file

Description

This error occurs when the path specified for creating the properties file is incorrect.

Action

Confirm that the var directory path is valid.

KDAN20294-E

Max Producer Count for aa....aa cannot be set to 0.

aa....aa: Destination name

Description

The maximum number of producers for the queue topic destination is set up to 0 (zero).

Action

Make sure that the maximum number of producers for the destination is set up to a value greater than 0 (zero).

KDAN20295-E

Max Consumer Count for aa....aa cannot be set to 0.

aa....aa: Destination name

Description

The maximum number of consumers for the queue destination is set up to 0 (zero).

Action

Make sure that the maximum number of consumers for the destination is set up to a value greater than 0 (zero).

KDAN20296-E

Support for feature aa....aa is unavailable on destination bb....bb, please upgrade to the Enterprise Edition to enable this feature.

aa....aa: Destination monitoring

bb....bb: Destination name

Description

The watch functionality is not enabled at the destination.

A non-local destination attempts to use the scope of the local destination.

The specified maximum number of active consumers is invalid.

The specified maximum number of active backup consumers is invalid.

Action

Enable the watch functionality at the destination.

Specify a valid destination scope.

Specify a valid maximum number of active consumers.

Specify a valid maximum number of active backup consumers.

KDAN20298-E

Consumer cannot be added to destination aa....aa, limit of bb....bb consumers would be exceeded.

aa....aa: Destination

bb....bb: Maximum number of consumers

Description

This message is displayed when an attempt is made to create consumers exceeding the limit for the destination in CJMSP.

Action

Terminate the consumers for which the processing has ended.

Increase the maximum number of consumers for the destination.

KDAN20299-E

Producer cannot be added to destination aa....aa, limit of bb....bb producers would be exceeded.

aa....aa: Destination

bb....bb: Maximum number of producers

Description

This message is displayed when an attempt is made to create producers exceeding the limit for the destination in CJMSP.

Action

Terminate the producers for which the processing has ended.

Increase the maximum number of producers for the destination.

KDAN20300-E

Producers are not allowed to produce messages to a monitoring destinations aa....aa.

aa....aa: Destination

Description

This error occurs when an attempt is made to create messages for the dead message queue.

Action

A producer cannot be created for a dead message queue. Specify another destination.

KDAN20301-E

Autocreation of bb....bb destinations is not allowed, destination aa....aa must be administratively created before it can be monitored.

aa....aa: Destination name

bb....bb: Destination type

Description

The value specified for the imq.autocreate.queue or imq.autocreate.topic properties is false.

Action

Set up the value for the imq.autocreate.queue or imq.autocreate.topic properties to true.

KDAN20303-E

Failed to move message aa....aa from destination bb....bb to destination cc....cc.

aa....aa: System message ID of the JMS message

bb....bb: Source destination

cc....cc: Target destination

Description

An attempt to move a message from the old destination has failed.

Action

Make sure that the permissions for the old store are appropriate.

KDAN20304-E

The size [ aa....aa bytes ] of packet bb....bb is larger than the individual packet limit of cc....cc bytes, rejecting packet.

aa....aa: Packet size

bb....bb: Packet

cc....cc: Maximum packet size

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20305-E

The useDMQ attribute cannot be changed on the Dead Message Queue.

Description

This error occurs when the Use Dead Message Queue option is selected while changing the dead message queue attributes.

Action

The Use Dead Message Queue attribute cannot be changed on the dead message queue.

KDAN20306-E

Dead Message retains on its original destination.

Description

An error occurred when deploying a message on the dead message queue.

Action

Contact maintenance personnel.

KDAN20307-E

FLOW_CONTROL is not a legal behavior for the Dead Message Queue.

Description

The legal behavior for the dead message queue is set up to FLOW_CONTROL.

Action

The FLOW_CONTROL limit behavior is not applied to the dead message queue. This is a restriction. Specify the following valid limit behaviors:

REMOVE_OLDEST

REJECT_NEWEST

REMOVE_LOW_PRIORITY

KDAN20308-E

Number of Producers cannot be changed on the Dead Message Queue.

Description

This error occurs when the number of producers on the dead message queue is changed from 0 (zero) to another integer value.

Action

The producer for the dead message queue cannot be created. Specify another destination.

KDAN20309-E

The Dead Message Queue cannot be destroyed.

Description

This error occurs when an attempt is made to destroy the dead message queue using the cjmsicmd destroy dst -n destination-name -t destination-type command.

Action

The dead message queue is used for the internal processing of CJMSP; and therefore, cannot be destroyed.

KDAN20310-E

Failed to load a destination.

Description

This error occurs when the file in the file store corresponding to the destination, is corrupted.

Action

Restart CJMSP. A new destination file is created, but the old destination data is lost.

KDAN20311-E

Failed to load a consumer.

Description

This error occurs when the file in the file store corresponding to the consumer, is corrupted.

Action

Restart CJMSP. A new consumer file is created, but the old consumer data is lost.

KDAN20312-E

Failed to load a property.

Description

This error occurs when the file in the file store corresponding to the property, is corrupted.

Action

Restart CJMSP. A new property file is created, but the old property data is lost.

KDAN20313-E

Failed to load a transaction.

Description

This error occurs when the file in the file store corresponding to the transaction, is corrupted.

Action

Restart CJMSP. A new transaction file is created, but the old transaction data is lost.

KDAN20314-E

Failed to load a transaction acknowledgement.

Description

This error occurs when the file in the file store corresponding to the transaction acknowledgement, is corrupted.

Action

Restart CJMSP. A new transaction acknowledgement file is created, but the old transaction acknowledgement data is lost.

KDAN20315-E

Failed to load a destination from the old store.

Description

An error occurred when loading a destination from the old store.

Action

Contact maintenance personnel for internal errors.

KDAN20316-E

Failed to load a consumer from the old store.

Description

An error occurred when loading a consumer from the old store.

Action

Make sure that the permissions for the old store are appropriate.

KDAN20317-E

Failed to load a property from the old store.

Description

An error occurred when loading a property from the old store.

Action

Make sure that the permissions for the old store are appropriate.

KDAN20318-E

Failed to load a transaction from the old store.

Description

An error occurred when loading a transaction from the old store.

Action

Make sure that the permissions for the old store are appropriate.

KDAN20319-E

Failed to load a transaction acknowledgement from the old store.

Description

An error occurred when loading a transaction acknowledgement from the old store.

Action

Make sure that the permissions for the old store are appropriate.

KDAN20320-E

Failed to reestablish database connection to aa....aa.

Description

A database error occurred when an attempt was made to create a connection for an already terminated idle connection in the connection pool.

Action

Make sure that the database connection is normal.

KDAN20321-E

Failed to attach to a consumer to shared consumer bb....bb on

topic aa....aa:number of subscribers dd....dd is at or above the limit

of cc....cc

aa....aa: Destination

bb....bb: Subscriber

cc....cc: Maximum number of active consumers

dd....dd: Number of subscribers created

Description

This error occurs when the number of consumers created is equal to the predefined maximum value.

KDAN20322-E

Unable to unsubscribe to subscription with a durable name of aa....aa and a client ID of bb....bb - Destination cc....cc and its associated consumers have been destroyed.

aa....aa: Durable subscriber name

bb....bb: Client ID

cc....cc: Destination name

Description

This error occurs when the consumer corresponding to the subscriber name is already destroyed.

Action

Confirm that the consumer exists.

KDAN20323-E

JAAS authentication configuration name index not defined.

Description

This error occurs when the JAAS authentication name is not set up.

Action

Specify a valid configuration name for JAAS authentication.

KDAN20324-E

Message aa....aa already exists in destination bb....bb.

aa....aa: Message ID

bb....bb: Destination name

Description

This error occurs when the specified message already exists in the destination.

KDAN20325-E

Unable to get loopback IP address on the system for validation of broker address aa....aa.

Description

An attempt to acquire the IP address of the loopback interface has failed.

Action

Contact maintenance personnel for internal errors.

KDAN20327-E

Failed to load destination aa....aa from store.

aa....aa: Destination

Description

The data in the database table is corrupt.

A database error occurred when acquiring a destination.

Action

Make sure that the database connection is normal.

KDAN20328-E

Failed to remove consumer states for destination aa....aa.

aa....aa: Destination name

Description

The data in the database table is corrupt.

A database error occurred when removing the consumer states for the destination.

Action

Make sure that the database connection is normal.

KDAN20330-E

Failed to load acknowledgements for transaction aa....aa.

aa....aa: Transaction ID

Description

The data in the database table is corrupt.

A database error occurred when acquiring the transaction acknowledgement.

Action

Make sure that the database connection is normal.

KDAN20331-E

Failed to get message counts for broker aa....aa from database.

aa....aa: Broker ID

Description

The data in the database table is corrupt.

A database error occurred when returning the number of CJMSP messages.

Action

Make sure that the database connection is normal.

KDAN20333-E

Failed to remove property aa....aa from store.

aa....aa: Property name

Description

The data in the database table is corrupt.

A database error occurred when removing a property.

Action

Make sure that the database connection is normal.

KDAN20335-E

Failed to load transactions for broker aa....aa from store.

Description

The data in the database table is corrupt.

A database error occurred.

Action

Make sure that the database connection is normal.

KDAN20341-E

Unable to load destination aa....aa.

aa....aa: Destination name

Description

An I/O error occurred when the destination was continuously accessed.

Action

Confirm that the file store is accessible if the appropriate permissions are used.

KDAN20342-E

Cannot stop service which is not running.

Description

This error occurs when an attempt is made to stop a service that is not running.

Action

Before stopping a service, confirm that the service is running.

KDAN20343-E

Cannot start service which is not paused.

Description

This error occurs when an attempt is made to start a service that is not paused.

Action

Before starting a service, confirm that the service is paused.

KDAN20360-E

Acknowledgement aa....aa for bb....bb exists already.

aa....aa: Acknowledgement

bb....bb: Transaction ID

Description

This error occurs when the acknowledgement already exists for the message.

Action

Make sure that the message is acknowledged only once.

KDAN20361-E

Connection aa....aa is closing.

aa....aa: Connection ID

Description

This error occurs when a connection is closed and destroyed while terminating a non-durable consumer or subscriber. The consumer is not terminated.

Action

When terminating a consumer, confirm that the connection is open. In the case of shared connections, make sure that when one thread is operating a connection, another thread does not terminate the connection.

KDAN20362-E

No session found for consumer aa....aa on connection bb....bb.

aa....aa: Consumer uid

bb....bb: Connection uid

Description

When destroying a consumer, the session is terminated and destroyed.

Action

When terminating a consumer, confirm that the session is open.

KDAN20371-E

Auto-creation of destination aa....aa is not allowed on service bb....bb because service restriction cc....cc is in effect.

aa....aa: Destination name

bb....bb: Service name

cc....cc: Service restriction

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20372-E

Creation of producer on topic aa....aa is not allowed on service bb....bb because service restriction cc....cc is in effect.

aa....aa: Destination name

bb....bb: Service name

cc....cc: Service restriction

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20373-E

Creation of consumer on topic aa....aa is not allowed on service bb....bb because service restriction cc....cc is in effect.

aa....aa: Destination name

bb....bb: Service name

cc....cc: Service restriction

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20381-E

Missing operator )

Description

An invalid message selector expression (closing bracket is missing) was specified when creating a message consumer. The consumer is not created.

Action

Specify a valid selector expression based on the SQL92 syntax.

KDAN20382-E

Invalid Character : ','

Description

An invalid message selector expression (BETWEEN is used) was specified when creating a message consumer. The consumer is not created.

Action

Specify a valid selector expression based on the SQL92 syntax.

KDAN20383-E

Temporary destination belongs to a closed connection or another connection - aa....aa.

aa....aa: temporary destination name

Description

This error occurs when an attempt is made to access the temporary destination belonging to a closed connection or another connection.

Action

The temporary destination belonging to a closed connection or another connection cannot be accessed.

KDAN20390-E

Unable to start Broker with an instance name of bb....bb. The instance directory aa....aa does not have the correct permissions. Exiting.

aa....aa: Current name of Broker

bb....bb: Instance directory name

Description

The instance directory does not have the read or write permissions.

Action

Contact maintenance personnel for internal errors.

KDAN20450-E

No Destination Type was set on the command.

Description

The destination type is not specified.

Action

Specify q (queue) or t (topic) as the destination type.

KDAN20451-E

No Destination Name was set on the command.

Description

The destination name is not specified.

Action

Specify a valid destination name.

KDAN20452-E

Unable to create destination: aa....aa, because bb....bb

aa....aa: Destination name

bb....bb: Reason

Description

The Broker was shut down when creating a destination.

The specified destination already exists.

Action

Confirm that the Broker is running.

Confirm that the specified destination does not exist.

KDAN20453-E

Unable to set/ update attributes destination: aa....aa, because bb....bb

aa....aa: Destination name

bb....bb: Exception message

Description

The specified destination does not exist in the store.

Action

Confirm that the specified destination exists in the store.

KDAN20495-E

Broker cannot be started.

Description

This error occurs in the following cases:

When the specified instance name is the reserved device name

When the specified path does not have write permissions

When the specified path is invalid

Action

Change the instance name.

Confirm that the specification of the path is correct.

KDAN20496-E

Broker cannot be started since the default services(jms/ admin) are not started.

Description

The jms and admin services are not executed.

Action

For details, reference the error log file, and then perform the appropriate processing to start the jms and admin services.

KDAN20497-E

Destination logger: Can't log to destination:aa....aa.

aa....aa: Topic destination

Description

This error occurs when the message is output to the log file. A possible cause is as follows:

An I/O error occurred when writing a message into the log file.

Action

Contact maintenance personnel for internal errors.

KDAN20498-E

Could not get or configure logging destination aa....aa. Closing destination logger:bb....bb.

aa....aa: Topic destination

bb....bb: Exception

Description

This error occurs when the message is output to the log file. A possible cause is as follows:

The specified destination does not exist in the store.

Action

Confirm that the specified destination exists in the store.

KDAN20499-E

Uncaught Exception in thread aa....aa.

aa....aa: Thread

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20500-E

error with properties

Description

This error occurs when properties are acquired from packet references.

Action

Contact maintenance personnel for internal errors.

KDAN20501-E

trying to timeout a non-TIMEOUT thread

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20502-E

attempting to destroy unknown thread aa....aa

aa....aa: Handler ID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20503-E

Unexpected Exception or Error

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20504-E

loading memory manager

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20506-E

Error closing portmapper

Description

An I/O error occurred during the termination of a server socket.

Action

Contact maintenance personnel for internal errors.

KDAN20507-E

assigning read for aa....aa to available thread bb....bb.

aa....aa: IMQIPConnection

bb....bb: Operation Runnable

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20508-E

Internal Error, unable to convert old packet.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20509-E

Requested removal of producer aa....aa which is not associated with connection bb....bb.

aa....aa: Producer UID

bb....bb: Connection UID

Description

This error occurs when the requested producer is not associated with the current connection.

Action

Contact maintenance personnel for internal errors.

KDAN20510-E

Requested removal of session aa....aa which is not associated with connection bb....bb.

aa....aa: Session UID

bb....bb: Connection UID

Description

This error occurs when the requested session is not associated with the current connection.

Action

Contact maintenance personnel for internal errors.

KDAN20511-E

starting paused service aa....aa.

aa....aa: IMQ redirect service object

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20513-E

Cannot deliver message to aa....aa.

aa....aa: Consumer object

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20514-E

Cannot determine behavior from imq.packet.read.override = aa....aa not one of the valid setting [heap,direct].

aa....aa: Value of imq.packet.read.override property

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20515-E

Cannot determine behavior from jmq.packet.fill.override = aa....aa not one of the valid setting [heap,direct].

aa....aa: Value of jmq.packet.fill.override property

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20516-E

Received out of memory error trying to shutdown.

Description

This error occurs when the JVM memory size is exceeded.

Action

Increase the JVM memory size.

KDAN20517-E

Internal Error: Received unexpected exception processing connection closing connection

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20519-E

Internal error, got interrupted exception.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20520-E

Unable to allocate connection aa....aa on service bb....bb , closing

aa....aa: IMQIPConnection

bb....bb: Connection name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20521-E

Connection going away

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20522-E

Closing destination logger.

Description

An exception occurred when publishing the message in the log.

Action

Contact maintenance personnel for internal errors.

KDAN20524-E

Address is not an IPv4 or IPv4-mapped IPv6 address.

Description

This error occurs when the specified IP address is not an IPv4 address.

Action

Specify an IPv4 address.

KDAN20526-E

JMSServiceReply has no return property values.

Description

This error occurs when the return value of JMSServiceReply does not contain the property value.

Action

Contact maintenance personnel for internal errors.

KDAN20527-E

JMSServiceReply is missing boolean property - aa....aa.

aa....aa: JMSServiceReply property value

Description

This message is displayed when the Boolean type property is acquired from JMSServiceReply.

Action

Contact maintenance personnel for internal errors.

KDAN20528-E

JMSServiceReply is missing int property - aa....aa.

aa....aa: Property

Description

This message is displayed when the int type property is acquired from JMSServiceReply.

Action

Contact maintenance personnel for internal errors.

KDAN20529-E

JMSServiceReply is missing long property - aa....aa.

aa....aa: Property

Description

This message is displayed when the long type property is acquired from JMSServiceReply.

Action

Contact maintenance personnel for internal errors.

KDAN20530-E

JMSServiceReply is missing string property - aa....aa.

aa....aa: Property

Description

This message is displayed when the string type property is acquired from JMSServiceReply.

Action

Contact maintenance personnel for internal errors.

KDAN20531-E

Cannot make a NumericValue from a aa....aa.

aa....aa: Object class name

Description

This error occurs when an attempt is made to cast an object, not belonging to the Number sub-class, into a numeric value.

Action

If the specified object is not null, make sure that the object belongs to the Number sub-class.

KDAN20532-E

PropertyValueComparator: Invalid types for comparison between aa....aa and bb....bb.

aa....aa: SQL syntax compare object

bb....bb: SQL syntax comparable object

Description

This error occurs when invalid types are compared.

Action

The Compare object and comparable object must be of the same type.

KDAN20533-E

Selector must evaluate to a java.lang.Boolean. Instead evaluated to a aa....aa.

aa....aa: SQL-92 expression

Description

This error occurs when the evaluation result of the selector expression is not a Boolean value.

Action

The evaluation result of the selector expression must be a Boolean value.

KDAN20535-E

Cannot use a static CharStream class with a non-static lexical analyzer.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal exceptions.

KDAN20536-E

Ignoring invalid lexical state : aa....aa. State unchanged.

aa....aa: Lexical state

Description

An internal error occurred.

Action

Contact maintenance personnel for internal exceptions.

KDAN20537-E

The LValue for BETWEEN must be a java.lang.Number. Found aa....aa

aa....aa: SQL statement

Description

This error occurs when the left side value for BETWEEN in the selector expression is not a numeric value.

Action

The left side value must be a numeric value.

KDAN20538-E

The START target for BETWEEN must be a numeric value. Found aa....aa

aa....aa: SQL statement

Description

This error occurs when the lower limit (START target) for BETWEEN in the selector expression is not a numeric value.

Action

The lower limit (START target) for BETWEEN must be a numeric value.

KDAN20539-E

The LIKE target must be a string. Found aa....aa.

aa....aa: SQL pattern

Description

The LIKE target in the selector expression is not a string.

Action

The LIKE target in the selector expression must be a string.

KDAN20540-E

All TARGETS of a IN clause must be a String. Found a aa....aa.

aa....aa: List of SQL values

Description

This message is displayed when all the targets of an IN clause are not string.

Action

All the targets of an IN clause in the selector expression must be String.

KDAN20541-E

Source of IN clause must be a String. Found a aa....aa.

aa....aa: SQL expression

Description

This error occurs when the source of an IN clause is not a string.

Action

The source of an IN clause must be a string.

KDAN20542-E

Bad packet magic number: aa....aa. Expecting: bb....bb.

aa....aa: Invalid packet magic number

bb....bb: Expected packet magic number

Description

This error occurs when the packet magic number is invalid or does not match the expected magic number.

Action

Contact maintenance personnel.

KDAN20543-E

Bad packet version number: aa....aa. Expecting: bb....bb.

aa....aa: Invalid packet version number

bb....bb: Expected packet version number

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20544-E

Can't unmarshall pkt

Description

This error occurs when the unmarshaling of packet properties fails.

Action

Contact maintenance personnel for internal errors.

KDAN20545-E

no data available

Description

This error occurs when one of the InterruptedIOExceptions occurs during the reading of a packet.

Action

Contact maintenance personnel for internal errors.

KDAN20546-E

Trying to read aa....aa bytes. Already read bb....bb bytes.

aa....aa: Length

bb....bb: Number (count)

Description

An EOF exception occurred during reading.

Action

Contact maintenance personnel for internal errors.

KDAN20547-E

Can't marshall pkt

Description

This error occurs when the marshaling of a packet header fails.

Action

Contact maintenance personnel for internal errors.

KDAN20548-E

Illegal address. Hostname missing : aa....aa.

aa....aa: Address

Description

This error occurs when an invalid address or host name is missing.

Action

Specify a valid host name.

KDAN20549-E

Illegal address. Port missing : aa....aa.

aa....aa: Address

Description

This error occurs when an invalid port number of the Broker URL is specified for the schema name of mqtcp or mqssl.

Action

Specify a valid port number.

KDAN20550-E

Illegal address. Unknown address scheme : aa....aa.

aa....aa: Broker URL

Description

This message is displayed when an invalid schema name is specified for the Broker URL.

Action

Specify a valid schema name (name beginning with mq).

KDAN20551-E

Illegal address. Bad query string : aa....aa.

aa....aa: Address

Description

This error occurs when an invalid schema format is specified for the Broker URL.

Action

Specify a valid schema format. The schema is as follows:

mq://localhost:7676/jms

KDAN20552-E

Can't read packet. Write in progress.

Description

This error occurs when an attempt is made to read during the writing of the packet.

Action

Contact maintenance personnel for internal errors.

KDAN20553-E

Packet has been destroyed

Description

This error occurs when an attempt is made to read an already destroyed packet.

Action

Contact maintenance personnel for internal errors.

KDAN20554-E

Packet size (aa....aa) is greater than the maximum allowed packet size (bb....bb). Disgarding packet.

aa....aa: Packet size

bb....bb: Maximum packet size

Description

This error occurs when an attempt is made to read a packet of a size greater than the maximum allowed packet size.

Action

Contact maintenance personnel for internal errors.

KDAN20556-E

Can't write packet. Read in progress.

Description

This error occurs when an attempt is made to write during the reading of the packet.

Action

Contact maintenance personnel for internal errors.

KDAN20557-E

Unsupported version of properties serialization [aa....aa].

aa....aa: Version

Description

The current version does not match the expected version.

Action

Contact maintenance personnel for internal errors.

KDAN20558-E

No buffer to write

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20559-E

Internal Error: Invalid Acknowledge Packet processing cannot notify the client aa....aa

aa....aa: Packet information

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20560-E

Bad Sysmessage ID

Description

This error occurs when the message ID does not begin from ID:prefix.

Action

Make sure that the message ID begins from ID:prefix.

KDAN20561-E

aa....aa: try to write integer at position bb....bb.

aa....aa: VRecordRAF information

bb....bb: Record header size

Description

An I/O error occurred when writing an integer at a specific position.

Action

Contact maintenance personnel for internal errors.

KDAN20562-E

aa....aa: try to read an integer from position bb....bb.

aa....aa: VRecordRAF information

bb....bb: Record header size

Description

An I/O error occurred when reading an integer (int type) from a specific position.

Action

Contact maintenance personnel for internal errors.

KDAN20563-E

aa....aa: try to read a long from position bb....bb.

aa....aa: VRecordRAF information

bb....bb: Record header size

Description

An I/O error occurred when writing a long type value from a specific position.

Action

Contact maintenance personnel for internal errors.

KDAN20564-E

aa....aa: try to write bb....bb bytes at position cc....cc.

aa....aa: VRecordRAF information

bb....bb: Record header size

cc....cc: Index

Description

An I/O error occurred when writing multiple bytes at a specific position.

Action

Contact maintenance personnel for internal errors.

KDAN20565-E

aa....aa: try to read bb....bb bytes from position cc....cc.

aa....aa: VRecordRAF information

bb....bb: Record header size

cc....cc: Index

Description

An I/O error occurred when reading multiple bytes from a specific position.

Action

Contact maintenance personnel for internal errors.

KDAN20566-E

aa....aa: try to position at position bb....bb.

aa....aa: VRecordRAF information

bb....bb: Record header size

Description

An I/O error occurred when searching for an operation position.

Action

Contact maintenance personnel for internal errors.

KDAN20567-E

aa....aa: try to write a long at position bb....bb.

aa....aa: VRecordRAF information

bb....bb: Record header size

Description

An I/O error occurred when writing a long type value at a specific position.

Action

Contact maintenance personnel for internal errors.

KDAN20568-E

aa....aa: try to read bb....bb bytes at position cc....cc.

aa....aa: VRecordRAF information

bb....bb: Record header size

cc....cc: Index

Description

An I/O error occurred when reading multiple bytes from a specific position.

Action

Contact maintenance personnel for internal errors.

KDAN20569-E

aa....aa: try to write a short at position bb....bb.

aa....aa: VRecordRAF information

bb....bb: Record header size

Description

An I/O error occurred when writing a short type value at a specific position.

Action

Contact maintenance personnel for internal errors.

KDAN20570-E

Block size must be positive. Illegal block size: aa....aa.

aa....aa: vrfile block size

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20571-E

Growth factor must be positive. Illegal growth factor: aa....aa.

aa....aa: Growth factor

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20572-E

Failed to free vrecord:aa....aa:bb....bb:cc....cc.

aa....aa: Backing file path

bb....bb: Vrecord (V record)

cc....cc: Exception

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20573-E

aa....aaCannot compact a file of version bb....bb.

aa....aa: Backing file name

bb....bb: Backing file version

Description

This error occurs when the backing file version is not compatible with the current version during the compression of the file.

Action

Contact maintenance personnel for internal errors.

KDAN20574-E

aa....aaCannot write to a file of version bb....bb.

aa....aa: Backing file name

bb....bb: Backing file version

Description

This error occurs when the backing file version is not compatible with the current version when writing to the file.

Action

Contact maintenance personnel for internal errors.

KDAN20586-E

Failed to synchronize file: aa....aa.

aa....aa: Backing file

Description

An I/O error occurred when an attempt was made to forcibly write the data on the disk.

Action

Contact maintenance personnel for internal errors.

KDAN20587-E

Got exception while synchronizing data to disk.

Description

An I/O error occurred during the synchronization of the data with the disk data.

Action

Contact maintenance personnel for internal errors.

KDAN20588-E

Failed to compact file: aa....aa.

aa....aa: Backing file

Description

An I/O error occurred during the compression of vrfile.

Action

Contact maintenance personnel for internal errors.

KDAN20589-E

Failed to free the corrupted vrecord: aa....aa.

aa....aa: Exception

Description

The VRFile is corrupted.

An I/O error occurred when releasing the invalid Vrecord.

Action

Contact maintenance personnel for internal errors.

KDAN20590-E

Failed to synchronize data to disk for file: aa....aa.

aa....aa: vrfile

Description

An I/O error occurred during the synchronization of the data with the disk.

Action

Contact maintenance personnel for internal errors.

KDAN20591-E

Got IOException while closing transaction log file.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20592-E

Failed to synchronize message stores.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20593-E

Failed to synchronize persistence store for transaction log checkpoint.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20597-E

Cannot access more than one stored property location.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20598-E

Cannot load property from null location.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20599-E

setProperty is not implemented, use updateProperty.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20600-E

Illegal Internal Name aa....aa.

aa....aa: Destination name

Description

The prefix of the internal sending name is not mq.

Action

Contact maintenance personnel for internal errors.

KDAN20601-E

Missing type for monitoring aa....aa.

aa....aa: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20602-E

Illegal type aa....aa for monitoring. Only Metrics is valid [bb....bb].

aa....aa: Type

bb....bb: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20603-E

Missing area for monitoring aa....aa.

aa....aa: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20604-E

Bad name for broker monitoring aa....aa should be bb....bb broker.

aa....aa: Destination name

bb....bb: Prefix of the internal destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20605-E

Bad name for broker monitoring aa....aa should be bb....bb jvm.

aa....aa: Destination name

bb....bb: Prefix of the internal destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20606-E

Missing destination type or list for broker destination monitoring aa....aa.

aa....aa: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20607-E

Missing name for broker queue monitoring aa....aa.

aa....aa: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20608-E

Missing name for broker topic monitoring aa....aa.

aa....aa: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20609-E

Illegal area aa....aa for monitoring bb....bb.

aa....aa: Area

bb....bb: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20610-E

Error sending metrics data.

Description

This error occurs when the metrics data cannot be written to the output stream. The possible causes might be that the output stream was not initialized correctly or some IOException (IO exception) occurred during the writing of the metrics data.

Action

Contact maintenance personnel for internal errors.

KDAN20611-E

Internal Error: removing consumer aa....aa from bb....bb.

aa....aa: Consumer UID

bb....bb: Destination

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20612-E

Internal Error: bad stored selector[aa....aa], ignoring

aa....aa: Selector

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20613-E

Internal Exception processing packet

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20614-E

Only Busy State Changed notifications supported on this class

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20615-E

shared clientID's not supported w/ o cluster

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20616-E

Broker Internal Error: unexpected call acknowledgeMessage

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20617-E

Not Supported.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20618-E

Internal error: moving message to null targets not supported.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20619-E

Internal Error: No AckInfo for message aa....aa.

aa....aa: System message ID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20620-E

Unable to replace already delivered message.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20621-E

Unable to replace partially acknowledged message.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20622-E

Internal Error updating properties.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20623-E

Internal Error checking ack on aa....aa for bb....bb.

aa....aa: Message ID

bb....bb: Consumer UID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20624-E

Internal Error: Received Unknown ack aa....aa for message bb....bb.

aa....aa: Consumer UID

bb....bb: Message ID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20626-E

Internal Error: received ack twice on aa....aa for bb....bb state is = cc....cc.

aa....aa: Message ID

bb....bb: Consumer UID

cc....cc: Consumer message pair

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20627-E

Error in processing ack on aa....aa for bb....bb.

aa....aa: Message ID

bb....bb: Consumer UID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20628-E

Internal Error: unknown interest for getConsumed on aa....aabb....bb.

aa....aa: Message ID

bb....bb: Consumer UID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20629-E

reference has been destroyed.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20630-E

Internal Error: unknown interest for consumed on aa....aabb....bb.

aa....aa: Message ID

bb....bb: Consumer UID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20631-E

Internal Error: unknown interest for remove consumed on aa....aabb....bb.

aa....aa: Message ID

bb....bb: Consumer UID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20632-E

Unable to process ack

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20633-E

bad value aa....aa expected integer.

aa....aa: Property value

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20634-E

Max Active Consumer count cannot be 0.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20635-E

Internal Error aa....aa trying to add remote consumer to local dest.

aa....aa: Destination information

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20636-E

Internal Error: Invalid Ack Type :aa....aa.

aa....aa: Acknowledgement type

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20637-E

Unable to process acknowledgement, Ignoring.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20638-E

Message Gone, unable to update state of the message aa....aa.

aa....aa: Packet reference

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20639-E

Detatching consumer aa....aa not currently attached to bb....bb.

aa....aa: Consumer

bb....bb: Session

Description

This error occurs when the specified consumer does not exist when detaching the consumer.

Action

Confirm that the connection is not closed.

KDAN20640-E

Unable to clean up remote message aa....aa .

aa....aa: Message information

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20641-E

Error handling undeliverable

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20642-E

Internal error, unable to deliver aa....aa:bb....bb.

aa....aa: Consumer UID

bb....bb: Packet reference

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20643-E

Only Busy and Not Busy types supported on this class

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20644-E

nolocal must match on all consumers.

Description

An exception occurred when adding a consumer.

Action

Contact maintenance personnel for internal errors.

KDAN20645-E

Error loading consumer exception.

Description

An exception occurred when loading a consumer.

Action

Contact maintenance personnel for internal errors.

KDAN20646-E

Error removing corrupt consumer aa....aa.

aa....aa: Consumer UID

Description

An I/O exception occurred when removing a consumer.

The consumer does not exist in the store.

Action

Contact maintenance personnel for internal errors.

KDAN20647-E

Internal Error: both key and value are corrupted.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20648-E

could not get props.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20649-E

timer canceled.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20650-E

Internal Exception: Only topics are supported for monitoring.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20652-E

Start message index needs to be in between 0 and aa....aa.

aa....aa: Maximum message index

Description

This error occurs when the start message index value is negative.

Action

Contact maintenance personnel for internal errors.

KDAN20653-E

Max number of messages retrieved value needs to be greater than 0.

Description

This error occurs when the maximum acquired messages index value is negative.

Action

Contact maintenance personnel for internal errors.

KDAN20654-E

setting max active consumers not supported on this destination type.

Description

This message is displayed when the maximum active consumers are set up for this destination.

Action

Contact maintenance personnel for internal errors.

KDAN20655-E

setting max failover consumers not supported on this destination type.

Description

This message is displayed when the maximum failover consumers are set up for this destination.

Action

Contact maintenance personnel for internal errors.

KDAN20656-E

Destination aa....aa destroyed.

aa....aa: Destination

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20657-E

Removing message to invalid dst.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20658-E

Internal Error, Unknown destination aa....aa isValid= bb....bb.

aa....aa: Destination

bb....bb: Flag

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20659-E

Processing aa....aa while loading destination bb....bb

aa....aa: Packet reference

bb....bb: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20660-E

Unloading destination aa....aa.

aa....aa: Destination

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20661-E

Destination aa....aa is also being created by another broker.

aa....aa: Destination

Description

This message is displayed when a destination is acquired from the destination list.

Action

Contact maintenance personnel for internal errors.

KDAN20662-E

Unable to remove dest

Description

An I/O exception occurred during the removal of the destination.

The destination does not exist in the store.

Action

Confirm that the specified destination exists in the store.

KDAN20663-E

Destination already destroyed.

Description

This error occurs when the specified destination has already been destroyed.

Action

Confirm that the specified destination exists in the store.

KDAN20664-E

Destination already exists

Description

This error occurs when the specified destination already exists while creating a new destination.

Action

Confirm that the specified destination does not exist in the store.

KDAN20666-E

expired messages

Description

This error occurs when the destination is null during the deletion of expired messages.

Action

Confirm that the specified destination exists in the store.

KDAN20667-E

unable to load destinations

Description

This message is displayed when a destination is loaded.

Action

Contact maintenance personnel for internal errors.

KDAN20668-E

aa....aa : Got exception reading body of administration message:bb....bb cc....cc

aa....aa: Class name

bb....bb: Exception

cc....cc: Packet

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20669-E

aa....aa : Got exception writing Vector to admin reply message:bb....bb, cc....cc

aa....aa: Class name

bb....bb: Exception

cc....cc: Packet

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20670-E

No administration handler found for message type aa....aa. Ignoring.

aa....aa: Message type

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20671-E

Administration message has no ReplyTo destination. Not replying.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20672-E

Could not reply to administrative message.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20673-E

Error aa....aaing bb....bb because cc....cc.

aa....aa: Command

bb....bb: Command argument

cc....cc: Exception message

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20674-E

No consumers on the broker.

Description

This error occurs when consumers are not found during the listing of the connections.

Action

Contact maintenance personnel for internal errors.

KDAN20675-E

Please supply targetType if you are supplying a target

Description

This error occurs when the target type is not specified.

Action

Specify the target type.

KDAN20676-E

Error listing consumers on destination aa....aa unknown destination.

aa....aa: Destination

Description

This error occurs when the consumers are listed on an unknown destination. This error occurs in the cases such as when the specified destination does not exist in the store.

Action

Confirm that the specified destination exists in the store.

KDAN20677-E

No consumers on destination aa....aa.

aa....aa: Destination

Description

This error occurs when the consumers are acquired on an unknown destination. This error might occur if the specified destination does not exist in the store.

Action

Confirm that the specified destination exists in the store.

KDAN20678-E

Error listing consumers on connection aa....aa because bb....bb.

aa....aa: jmq target

bb....bb: Exception message

Description

This error occurs when the consumers are acquired using an unknown connection. This error might occur if the specified destination is already terminated.

Action

Confirm that the application or client does not terminate the destination.

KDAN20679-E

Error listing consumers on session aa....aa unknown sessionUID.

aa....aa: jmq target

Description

This error occurs when the consumers are listed for an unknown session. This error might occur if the specified session is already terminated.

Action

Confirm that an application or client has not terminated the session.

KDAN20680-E

No consumers on session aa....aa.

aa....aa: jmq target

Description

This error occurs when the consumers are acquired using an unknown session. This error might occur if the specified session is already terminated.

Action

Confirm that the application or client does not terminate the session.

KDAN20681-E

Error listing consumers on connection aa....aa unknown connectionUID.

aa....aa: jmq target

Description

This error occurs when the consumers are acquired using an unknown connection ID. This error might occur if the specified connection is already terminated.

Action

Confirm that an application or client has not terminated the connection.

KDAN20682-E

Unknown targetType (-t) aa....aa. Valid formats are of the form: [q|t|ses|cxn]

aa....aa: Invalid target type

Description

This error occurs when the specified target type is invalid.

Action

Specify a specific target type that is not invalid.

KDAN20683-E

Error listing producers on destination aa....aa unknown destination.

aa....aa: Destination

Description

This error occurs when the producers are listed on an unknown destination. This error might occur in the cases such as when the specified destination does not exist in the store.

Action

Confirm that the specified destination exists in the store.

KDAN20684-E

Error listing producers on connection aa....aa because bb....bb.

aa....aa: Destination

bb....bb: Exception message

Description

This error occurs when the producers are listed using an unknown connection. This error might occur if the specified connection is already terminated.

Action

Confirm that an application or client has not terminated the connection.

KDAN20685-E

Error listing producers on connection aa....aa unknown connectionUID.

aa....aa: Destination

Description

This error occurs when the producers are listed using an unknown connection ID. This error might occur if the specified connection is already terminated.

Action

Confirm that an application or client has not terminated the connection.

KDAN20686-E

Unknown targetType (-t) aa....aa. Valid formats are of the form: [t|q|cxn]

aa....aa: Invalid target type

Description

This error occurs when the specified target type is invalid.

Action

Confirm that the specified target type is valid.

KDAN20688-E

Unknown argument aa....aa.

aa....aa: Argument

Description

This error occurs when the specified argument is invalid.

Action

Specify a valid argument.

KDAN20689-E

Bad Selector aa....aa.

aa....aa: Selector

Description

This error occurs when the specified selector is invalid.

Action

Make sure that the specified selector conforms to the SQL92 format.

KDAN20692-E

Error resuming flow from producer aa....aa because bb....bb.

aa....aa: jmq target

bb....bb: Exception message

Description

This error occurs when the producer is restarted. This error might occur if the specified producer does not exist in the Broker.

Action

Confirm that an application or client has not terminated the producer.

KDAN20693-E

Error resuming flow on connection aa....aa because bb....bb.

aa....aa: jmq target

bb....bb: Exception message

Description

This error occurs when the connection is restarted. This error might occur if the specified connection does not exist in the Broker.

Action

Confirm that an application or client has not terminated the connection.

KDAN20694-E

Error resuming flow to consumer aa....aa because bb....bb.

aa....aa: jmq target

bb....bb: Exception message

Description

This error occurs when the consumer is restarted. This error might occur if the specified consumer does not exist in the Broker.

Action

Confirm that an application or client has not terminated the consumer.

KDAN20695-E

Error resuming flow to session aa....aa because bb....bb.

aa....aa: jmq target

bb....bb: Exception message

Description

This error occurs when the session is restarted. This error might occur if the specified session does not exist in the Broker.

Action

Confirm that an application or client has not terminated the session.

KDAN20696-E

Unknown resume argument aa....aa.

aa....aa: Argument

Description

This message is displayed when the specified argument is invalid.

Action

Specify a valid argument.

KDAN20697-E

Missing connectionUID.

Description

This error occurs when the specified target is invalid.

Action

Specify a valid target.

KDAN20698-E

Unknown connectionUID aa....aa.

aa....aa: Connection UID

Description

This message is displayed when the connection does not exist. This error might occur if the connection is terminated.

Action

Confirm that an application or client has not terminated the connection.

KDAN20699-E

Error notifying consumer aa....aa because bb....bb.

aa....aa: Consumer

bb....bb: Exception message

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN20700-E

Unknown service aa....aa.

aa....aa: Service name

Description

This error occurs when the specified service name is null.

Action

Specify a valid service name (such as jms or admin).

KDAN20702-E

Error killing connection aa....aa because bb....bb.

aa....aa: Connection UID

bb....bb: Exception message

Description

This error occurs when an unexpected internal error occurs during the killing of the connection.

Action

Contact maintenance personnel for internal errors.

KDAN20703-E

Unknown kill argument aa....aa .

aa....aa: Argument

Description

This error occurs when invalid arguments are specified.

Action

Specify a valid argument (cxn).

KDAN20704-E

topic or queue not specified with -t [t|q].

Description

This error occurs when the destination type is not specified during the operations for the destination.

Action

Specify an appropriate destination type (q or t).

KDAN20705-E

Unknown -t argument aa....aa expected t or q.

aa....aa: Argument

Description

This error occurs when invalid arguments are specified in the destination type.

Action

Use -t[t or q] and specify a valid destination type.

KDAN20706-E

Unknown destination aa....aa.

aa....aa: Destination UID

Description

This error occurs when an attempt is made to acquire an invalid destination.

Action

Initially confirm that the destination exists.

KDAN20707-E

Unknown consumer aa....aa.

aa....aa: Consumer UID

Description

This error occurs when an attempt is made to acquire a non-existent consumer.

Action

Confirm that the specified consumer exists in the store.

KDAN20708-E

Please specify consumerUID.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20709-E

Please specify connectionUID.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20710-E

Cannot find connection aa....aa.

aa....aa: Connection uid

Description

This error occurs when an attempt is made to acquire a closed connection.

This error occurs when an attempt is made to use an invalid connection.

Action

Confirm that the connection is open. Also, if the connection is shared, make sure that when this thread is using the connection, another thread does not close the connection.

KDAN20711-E

Please specify SessionUID.

Description

This error occurs when ses is not specified as the session uid type when the packet information is acquired.

Action

Specify ses as the session uid type.

KDAN20712-E

Cannot find session aa....aa.

aa....aa: Session uid

Description

This error occurs when an attempt is made to use a closed session.

Action

Confirm that the session is open.

KDAN20713-E

Cannot find uid aa....aa.

aa....aa: Connection uid

Description

This error occurs when an attempt is made to use a closed connection.

Action

Confirm that the connection is open.

KDAN20714-E

Cannot find consumer aa....aa.

aa....aa: Consumer uid

Description

This error occurs when the application or client closes the consumer before a message is processed.

Action

Make sure that an application or client does not close the consumer.

KDAN20715-E

Cannot find producer aa....aa.

aa....aa: Producer uid

Description

This error occurs when the application or client closes the producer before a message is processed.

Action

Make sure that an application or client does not close the producer.

KDAN20716-E

Cannot find Destination aa....aa.

aa....aa: Destination uid

Description

The destination does not exist.

Action

Confirm that the destination exists.

KDAN20717-E

Destination name and type not specified.

Description

This error occurs when the destination name and type are not specified for deleting the messages from a destination.

Action

Specify a valid destination name and type.

KDAN20718-E

Message ID not specified.

Description

The specified message ID is null.

Action

Confirm that the message ID is valid.

KDAN20719-E

Could not locate message aa....aa in destination bb....bb.

aa....aa: Message

bb....bb: Destination

Description

The specified message does not exist in the destination.

Action

Confirm that the specified message exists in the destination.

KDAN20720-E

aa....aa:could not set message body: bb....bb.

aa....aa: Class name

bb....bb: Exception message

Description

An internal error occurred during the set up of the message body.

Action

Contact maintenance personnel for internal errors.

KDAN20721-E

Caught exception while creating text message body.

Description

An internal error occurred during the creation of a text message.

Action

Contact maintenance personnel for internal errors.

KDAN20722-E

Caught exception while creating map message body.

Description

An internal error occurred during the creation of a map message.

Action

Contact maintenance personnel for internal errors.

KDAN20723-E

Caught exception while creating object message body.

Description

An internal error occurred during the creation of an object message.

Action

Contact maintenance personnel for internal errors.

KDAN20724-E

Unsupported message type for GET_MESSAGES handler: aa....aa.

aa....aa: Packet type

Description

This error occurs when an attempt is made to acquire a message of an unsupported type.

Action

Confirm that the specified message is of the TextMessage/ ObjectMessage/ BytesMessage/ StreamMessage/ MapMessage type.

KDAN20725-E

aa....aa:failed to get destination (bb....bb:cc....cc).

aa....aa: Class name

bb....bb: Destination type

cc....cc: Destination

Description

The specified destination does not exist.

An invalid destination type is specified.

Action

Confirm that the specified destination exists.

Specify a valid destination type.

KDAN20726-E

unknown durable subscription aa....aa:bb....bb.

aa....aa: Durable subscriber name

bb....bb: Client ID

Description

This error occurs when an attempt is made to access an invalid durable subscriber.

Action

Confirm that the durable subscriber exists.

KDAN20727-E

REPLACE_MESSAGE: Destination name and type not specified.

Description

This error occurs when the destination name and type are not specified.

Action

Confirm that the destination name and type are specified.

KDAN20728-E

REPLACE_MESSAGE: Message ID not specified.

Description

This error occurs when the message ID is not specified.

Action

Confirm that the message ID is specified.

KDAN20729-E

REPLACE_MESSAGE: New message body specified or is of incorrect type.

Description

This error occurs when the message body is not specified.

Action

Confirm that the message body is specified.

KDAN20730-E

REPLACE_MESSAGE: Existing message and new message types do not match.

Description

This error occurs when the new message type does not match with the old message type.

Action

Contact maintenance personnel for internal errors.

KDAN20731-E

REPLACE_MESSAGE: New message ID not returned as expected.

Description

This error occurs when the message ID is not specified.

Action

Confirm that the message ID is specified.

KDAN20732-E

REPLACE_MESSAGE: Could not locate message aa....aa in destination bb....bb

aa....aa: Message ID

bb....bb: Destination

Description

This error occurs when the message does not exist in the destination.

Action

Confirm that the message exists in the destination.

KDAN20733-E

Unsupported message type for REPLACE_MESSAGE handler: aa....aa

aa....aa: Message type

Description

This error occurs when the specified message type is invalid.

Action

Confirm that the specified message is of the TextMessage/ ObjectMessage/ BytesMessage/ StreamMessage/ MapMessage type.

KDAN20734-E

Internal Error: can updated non-standard Service.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20735-E

Unable to create/ destroy destination - no properties.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20736-E

Cannot handle create/ destroy destination.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20737-E

protocol error, destination is null.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20738-E

protocol error, bad rbuf size.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20739-E

Elements are not in subset

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20740-E

Object added is past end of subset

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20741-E

Event aa....aa not supported.

aa....aa: Event type

Description

This message is displayed when the specified event type does not match the expected event type.

Action

Specify an event type matching with the expected event type.

KDAN20742-E

remove is not supported on this iterator

Description

The Remove method is not supported.

Action

Contact maintenance personnel.

KDAN20744-E

Cannot order unordered items.

Description

This message is displayed when the object is not an Ordered instance.

Action

Make sure that the object is an Ordered instance.

KDAN20745-E

Unable to support null values.

Description

This error occurs when the specified object is null.

Action

Confirm that the object is not null.

KDAN20746-E

Unable to add object not of type Sized when byteCapacity has been set.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20747-E

Unable to add object not of type Sized when maxByteSize has been set.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20748-E

Object added is past end of subset.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20749-E

Object added is past beginning of subset.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20750-E

Implementation not complete.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20751-E

Unable to support null keys or values.

Description

This error occurs when a key and value is null.

Action

Confirm that the keys and values are not null.

KDAN20753-E

Internal Error: timer canceled .

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20754-E

This file mode is not supported: aa....aa.

aa....aa: Mode

Description

This error occurs when the specified file mode is invalid.

Action

Confirm that the user has file read and write permissions or the read, write, and execute permissions as the owner.

KDAN20755-E

File Header size mismatch. Expected: aa....aa, read: bb....bb.

aa....aa: File header size

bb....bb: Size

Description

This error occurs when the file is corrupted.

Action

Contact maintenance personnel.

KDAN20756-E

File Header checksum mismatch. Expected: aa....aa, calculated: bb....bb.

aa....aa: Expected value

bb....bb: Calculated value

Description

This error occurs when the file is corrupted.

Action

Contact maintenance personnel.

KDAN20757-E

File Magic number/ version mismatch: aa....aa : bb....bb.

aa....aa: Magic number

bb....bb: Version number

Description

This error occurs when the file is corrupted.

Action

Contact maintenance personnel.

KDAN20762-E

failed to delete aa....aa.

aa....aa: File

Description

This error occurs when the applicable file does not have the "delete" permission.

Action

Make sure that the file to be deleted has the "delete" permission.

KDAN20764-E

Invalid operator ==, use =

Description

This error occurs when the selector string contains the "==" token.

Action

Use "=" instead of "==".

KDAN20765-E

Invalid character aa....aa

aa....aa: Character

Description

This error occurs when the selector string contains an invalid character.

Action

Make sure that the selector string does not contain invalid characters.

KDAN20766-E

Invalid numeric constant: aa....aa.

aa....aa: Exception message

Description

This error occurs when the selector has an invalid constant.

Action

Make sure that the selector string does not contain an invalid constant.

KDAN20767-E

Unknown token: aa....aa tokenBuf=bb....bb.

aa....aa: Invalid token

bb....bb: Token buffer

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN20768-E

Missing closing quote

Description

This error occurs when the selector string is not closed using a quotation mark.

Action

Confirm that the selector string is closed using a quotation mark.

KDAN20769-E

Invalid Expression

Description

This error occurs when the selector contains an invalid expression.

Action

Confirm that the SQL 92 format syntax is used in the selector string.

KDAN20770-E

Selector tokenizer in bad state:aa....aatokenBuf=bb....bbchar=cc....cc

aa....aa: State

bb....bb: Token buffer

cc....cc: Character

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN20771-E

Missing ( in IN statement

Description

This error occurs when "(" (left parenthesis) is missing in the IN statement of the selector string.

Action

Confirm that "(" is specified in the IN statement of the selector string.

KDAN20772-E

IN requires string literal:aa....aa.

aa....aa: String literal

Description

This error occurs when the IN statement of the selector string does not contain a string literal.

Action

Confirm that the IN statement of the selector string contains a string literal.

KDAN20773-E

LIKE requires string literal:aa....aa.

aa....aa: String literal

Description

This error occurs when the LIKE statement of the selector string does not contain a string literal.

Action

Confirm that the LIKE statement of the selector string contains a string literal.

KDAN20774-E

ESCAPE requires string literal:aa....aa.

aa....aa: String literal

Description

This error occurs when the ESCAPE statement of the selector string does not contain a string literal.

Action

Confirm that the ESCAPE statement of the selector string contains a string literal.

KDAN20775-E

Missing operator

Description

This error occurs when an operator is not specified in the selector string.

Action

Confirm that the selector string contains an operator.

KDAN20776-E

Missing (

Description

This error occurs when the selector string has the right parenthesis, but does not have the left parenthesis.

Action

Confirm that the selector string contains the left and the right parenthesis.

KDAN20777-E

IN requires string operand: aa....aa.

aa....aa: Operand

Description

This error occurs when the IN statement of the selector string does not contain a string operand.

Action

Confirm that the IN statement of the selector string contains the string operand.

KDAN20778-E

LIKE requires string operand: aa....aa.

aa....aa: Operand

Description

This error occurs when the LIKE statement of the selector string does not contain a string operand.

Action

Confirm that the LIKE statement of the selector string contains the string operand.

KDAN20779-E

Unknown operator: aa....aa.

aa....aa: Operand

Description

This error occurs when the selector string contains an invalid operator.

Action

Make sure that the selector string contains a valid operator (such as NOT, AND, OR, LIKE, or IN).

KDAN20780-E

Missing operand

Description

This error occurs when the selector string does not contain an operand.

Action

Confirm that the selector string contains an operand.

KDAN20781-E

Non-boolean expression aa....aa

aa....aa: Selector string

Description

This message is displayed when an invalid Bool value is specified in the selector string.

Action

Make sure that True or False are specified as the Bool value.

KDAN20782-E

Cannot convert string to number 'aa....aa'

aa....aa: First operand of the selector

Description

This error occurs when the selector token is converted from a string to a number.

Action

Confirm that the string does not contain special characters.

KDAN20783-E

Non-numeric argument 'aa....aa'

aa....aa: Argument

Description

This error occurs when the specified argument is not a numeric value.

Action

Specify a numeric value in the relevant argument.

KDAN20784-E

Unknown numeric operation: aa....aa

aa....aa: Selector token

Description

This error occurs when the selector string contains a non-numeric operation.

Action

Confirm that the selector string contains a numeric operation (such as DIVIDE, MULTIPLY, MINUS, PLUS, GT, LT, or EQUALS).

KDAN20785-E

Invalid client data size.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal exceptions.

KDAN20786-E

Client data size has not been initialized.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal exceptions.

KDAN20787-E

Record not found [key=aa....aa , cData=bb....bb].

aa....aa: Key

bb....bb: cData

Description

An internal error occurred.

Action

Contact maintenance personnel for internal exceptions.

KDAN20788-E

Failed to load data in [aa....aa].

aa....aa: VRecordRAF

Description

This message is displayed when VRecordRAF is corrupted.

Action

Check whether the file is corrupted.

KDAN20789-E

Unable to update client data [key= aa....aa, cData= bb....bb].

aa....aa: Key

bb....bb: cData

Description

This message is displayed when VRFile is corrupted.

Action

Check whether the file is corrupted.

KDAN20790-E

Failed to set client data marker.

Description

This message is displayed when VRFile is corrupted.

Action

Check whether the file is corrupted.

KDAN20792-E

Could not decode xid from packet aa....aa : bb....bb.

aa....aa: Packet type

bb....bb: Exception

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20796-E

Unable to verify destination - no properties.

Description

An I/O error occurred while obtaining the message properties and destination.

Action

Make sure that the network connection is correct.

Check whether the I/O device or driver is running.

Contact maintenance personnel.

KDAN20797-E

Unable to verify destination -bad class.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20798-E

Unable to verify destination.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20803-E

Could not write Xid aa....aa to message body: bb....bb.

aa....aa: JMQXid

bb....bb: Exception

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20813-E

Internal Error: unknown destination for reference: aa....aa.

aa....aa: Packet reference

Description

An internal error occurred.

Action

Contact maintenance personnel for internal exceptions.

KDAN20814-E

Internal Error: Unable to re-queue message to queue aa....aa.

aa....aa: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal exceptions.

KDAN20818-E

Internal Error: received bad session ID aa....aa when starting session.

aa....aa: Session uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20819-E

Internal Error: received bad session ID aa....aa when stopping session.

aa....aa: Session uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20820-E

aa....aa:Got exception writing metrics to browse reply message:bb....bb

aa....aa: Class name

bb....bb: Exception message

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20821-E

Internal Error: client sent invalid sessionUID w/ ADD_PRODUCER aa....aa session does not exist.

aa....aa: Session uid

Description

This error occurs when the specified session is closed.

Action

Contact maintenance personnel for internal errors.

KDAN20822-E

error destroying connection aa....aa.

aa....aa: Connection uid

Description

This message is displayed when an exception occurs while closing a connection.

Action

Contact maintenance personnel for internal errors.

KDAN20829-E

Internal error: Bad change record. Upgrade failed.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20831-E

adding packet handlers to admin packet router.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20833-E

Received Out Of Memory Error [ aa....aa ].

aa....aa: Exception reason

Description

This error occurs when the JVM memory size of the CJMSP Broker is insufficient.

Action

Increase the JVM memory size of the CJMSP Broker.

KDAN20835-E

received unexpected exception

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20837-E

Internal Error: Unable to load broker, configuration properties are not available. Exiting.

Description

This error occurs in an invalid environment.

Action

Contact maintenance personnel.

KDAN20838-E

aa....aa :failed to parse message from byte array.

aa....aa: Destination uid

Description

An I/O error occurred when loading a message.

Action

Contact maintenance personnel for internal errors.

KDAN20839-E

aa....aa :failed to parse message from vrecord( bb....bb ).

aa....aa: Destination uid

bb....bb: vrecord

Description

An I/O error occurred when loading the message from the backing buffer.

Action

Contact maintenance personnel for internal errors.

KDAN20840-E

Fault Injection: triggered aa....aa.

aa....aa: Fault

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20841-E

Unable to apply fault.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20848-E

failed to parse interest list(size=aa....aa) for msg(size=bb....bb) from vrecord(cc....cc), dd....dd.

aa....aa: Size

bb....bb: Packet size

cc....cc: VRecordRAF

dd....dd: Exception

Description

An I/O error occurred when loading the list of consumers from the backing buffer.

Action

Contact maintenance personnel for internal errors.

KDAN20849-E

aa....aa:failed to parse message(size=bb....bb) from vrecord(cc....cc), dd....dd.

aa....aa: Destination uid

bb....bb: Packet size

cc....cc: VRecordRAF

dd....dd: Exception

Description

An I/O error occurred when loading the message from the backing buffer.

Action

Contact maintenance personnel for internal errors.

KDAN20850-E

size of interest list is corrupted.

Description

This error occurs when the backing buffer is corrupted.

Action

Contact maintenance personnel for internal errors.

KDAN20862-E

missing Broker instancename

Description

This message is displayed when no argument is specified for -name.

Action

Make sure that an appropriate argument is specified for -name.

KDAN20872-E

missing remove argument

Description

This error occurs when no argument is specified for -remove.

Action

Confirm that an appropriate argument is specified for -remove.

KDAN20873-E

unknown remove argument

Description

This error occurs when invalid arguments are specified for -remove.

Action

Confirm that an appropriate argument is specified for -remove.

KDAN20874-E

missing reset argument

Description

This error occurs when no argument is specified for -reset.

Action

Confirm that an appropriate argument is specified for -reset.

KDAN20875-E

bad reset argument

Description

This message is displayed when an invalid argument is specified for -reset.

Action

Specify a valid argument (store, messages, and durables).

KDAN20880-E

requested invalid packet router aa....aa

aa....aa: Type

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20881-E

Fault Insertion: aa....aa.

aa....aa: Value

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20882-E

Got IOException while resetting transaction log file.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20883-E

Already Quiescing.

Description

This error occurs when the Broker is already quiescing.

Action

Release the quiescing of the Broker.

KDAN20884-E

Null destination type specified.

Description

This error occurs when the specified destination type is null.

Action

When the destination is queue, specify q and when the destination is topic, specify t.

KDAN20888-E

Cannot pause admin service: aa....aa.

aa....aa: Service

Description

This error occurs when an attempt is made to pause the admin service.

Action

The admin service cannot be paused.

KDAN20889-E

Cannot resume admin service: aa....aa.

aa....aa: Service

Description

This error occurs when an attempt is made to resume the admin service.

Action

The admin service cannot be resumed.

KDAN20890-E

Internal Error: can updated non-standard Service.

Description

This error occurs when the specified service is not the IMQService instance.

Action

Contact maintenance personnel for internal errors.

KDAN20891-E

Destination name and type not specified.

Description

This error occurs when the destination name and type are not specified.

Action

When the destination type is queue, specify q and when the destination type is topic, specify t. Also, specify the destination name.

KDAN20892-E

Could not locate message aa....aa in destination bb....bb.

aa....aa: Message ID

bb....bb: Destination name

Description

This error occurs when the relevant message does not exist in the destination during message deletion.

Action

Confirm that the relevant message exists in the destination.

KDAN20893-E

Message ID not specified.

Description

This error occurs when the message ID is null during the deletion of messages.

Action

Confirm that the relevant message exists in the destination.

KDAN20894-E

New message body not specified.

Description

This error occurs when the message body is null during the replacement of messages.

Action

Confirm that the relevant message exists in the destination.

KDAN20895-E

Existing message and new message types do not match.

Description

This error occurs when the new message type does not match the old message type.

Action

Contact maintenance personnel for internal errors.

KDAN20896-E

New message ID not returned as expected.

Description

This error occurs when the new message ID is null during the replacement of messages.

Action

Contact maintenance personnel for internal errors.

KDAN20897-E

Internal Error: transaction broker list size of aa....aa is larger than the reserved client data byte limit of bb....bb for transaction cc....cc.

aa....aa: Number of Brokers

bb....bb: Limit

cc....cc: Transaction uid

Description

This error occurs when the transaction Broker list size exceeds the reserved list size.

Action

Contact maintenance personnel for internal errors.

KDAN20898-E

Internal Error: unknown ackType aa....aa.

aa....aa: Acknowledgement type

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20899-E

Internal Error: Empty Ack Message aa....aa.

aa....aa: System message ID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20900-E

Internal Error: Invalid Ack Message Size aa....aa for message bb....bb.

aa....aa: Message size

bb....bb: System message ID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20901-E

Internal Error: cannot create transactionID for aa....aa.

aa....aa: Message

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20903-E

Internal Error: Unable to complete processing acks: Unknown consumer aa....aa.

aa....aa: Consumer uid

Description

This error occurs when the Broker is shutting down and the acknowledgement processing is not yet complete.

Action

Contact maintenance personnel for internal errors.

KDAN20905-E

Internal Error: Unable to complete processing transaction: Unknown consumer/ session aa....aa.

aa....aa: Consumer uid

Description

This error occurs during Broker shut down and the transaction processing is not yet complete.

Action

Contact maintenance personnel for internal errors.

KDAN20906-E

Internal Error: Unable to complete processing acknowledgements in a tranaction: aa....aa.

aa....aa: Transaction uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20907-E

Internal Error unknown consumer aa....aa.

aa....aa: Consumer uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20909-E

Internal Error: unable to retrieve properties from clientID message aa....aa.

aa....aa: Message ID

Description

An I/O error occurred when acquiring properties from the packet.

Action

Contact maintenance personnel for internal errors.

KDAN20910-E

unexpected error processing clientid.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20911-E

Internal Error: unable to retrieve properties from consumer message aa....aa.

aa....aa: Message ID

Description

An I/O error occurred when acquiring properties from the packet.

Action

Contact maintenance personnel for internal errors.

KDAN20912-E

Internal Error: client set invalid sessionUID aa....aa session does not exist

aa....aa: Session uid

Description

This error occurs when the session has been closed.

Action

Contact maintenance personnel for internal errors.

KDAN20913-E

no properties in addConsumer packet - client does not match protocol.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20914-E

Client is not sending DestType, unable to add interest.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20915-E

NoLocal is not supported on Queue Receivers.

Description

This error occurs when NoLocal is used in the queue receiver.

Action

Do not use NoLocal in the queue receiver.

KDAN20916-E

Unsupported property on queues JMQNoLocal is set to aa....aa.

aa....aa: nolocal

Description

This error occurs when the NoLocal property is used in the queue receiver.

Action

Do not use the NoLocal property in the queue receiver.

KDAN20917-E

JMQReconnect not implemented.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20918-E

client did not send setCLIENTID method before adding/removing a consumer, retrieved clientid aa....aa from packet properties.

aa....aa: Client ID

Description

The client ID is not set up for the consumer.

Action

Set up the client ID before acquiring the consumer.

KDAN20919-E

Unknown Destination: aa....aa.

aa....aa: Destination

Description

This error occurs when the destination is null during message processing.

Action

Make sure that the destination is not null.

KDAN20920-E

Internal Error: unable to retrieve properties from deliver message aa....aa.

aa....aa: Message ID

Description

An I/O error occurred when acquiring the properties from a delivery message.

Action

Contact maintenance personnel for internal errors.

KDAN20921-E

Empty Deliver Message.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20922-E

Reprocessing Indempotent message for aa....aa on destination cc....cc from bb....bb.

aa....aa: Consumer uid

bb....bb: Remote connection uid

cc....cc: Destination uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20923-E

Could not start the Broker''s aa....aa service on port bb....bb. This port is already in use by another application.

aa....aa: Service name

bb....bb: Port number

Description

This error occurs when the specified port is already in use.

Action

Use a different port number.

KDAN20924-E

aa....aa Location:- bb....bb.cc....cc

aa....aa: Error message

bb....bb: File path name

cc....cc: Information about the internal processing that could not be executed

Description

This error occurs in the following cases:

When an attempt is made to generate the Broker using a reserved keyword

When an error occurs while acquiring the HNTR library for recording the messages in the log file

When the disk size of the directory specified in the property value is inadequate

Action

Make sure that you do not start the Broker by using a reserved word in the Broker instance name.

Make sure that the amount of memory on the specified directory is adequate.

KDAN20925-E

Failed to get transaction aa....aa information from store after takeover.

aa....aa: Transaction ID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20929-E

received message with Unknown Transaction ID aa....aa : ignoring message

aa....aa: Transaction uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20930-E

Transaction aa....aa : is has timed out

aa....aa: Transaction uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20931-E

Transaction aa....aa : is not started, ignoring.

aa....aa: Transaction uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20932-E

received acknowledgement with Unknown Transaction ID aa....aa : ignoring message

aa....aa: Transaction uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20935-E

Internal Error:both key and value for a Transaction Ack entry are corrupted.

Description

The data was corrupted when the data was loaded from the persistence store.

Action

Contact maintenance personnel for internal errors.

KDAN20940-E

XXXI18N-Unable to update transaction state for TUID=aa....aa:bb....bb.

aa....aa: Transaction uid

bb....bb: Transaction state

Description

An I/O error occurred when CJMSP attempted to acquire, delete, or update the persistence store transaction information. A possible cause is that the transaction ID generated by CJMSP does not exist in the persistence store or the transaction ID is null.

Action

Contact maintenance personnel for internal errors.

KDAN20946-E

XXXI18N - Consumed message [aa....aa:bb....bb]not found in transaction cc....cc.

aa....aa: System message ID

bb....bb: Consumer uid

cc....cc: Transaction uid

Description

This error occurs when the consumed message is null during the deletion of the consumed message.

Action

Contact maintenance personnel for internal errors.

KDAN20949-E

Failed to cleanup committed transaction aa....aa.

aa....aa: Transaction uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20952-E

received acknowledgement with Unknown Transaction ID aa....aa

aa....aa: Transaction uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20953-E

Internal Error:Error updating transaction aa....aa.

aa....aa: Transaction uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20955-E

Caught exception when reading passwd: aa....aa.

aa....aa: IO exception

Description

An I/O error occurred when reading the password from the command line.

Action

Contact maintenance personnel for internal errors.

KDAN20956-E

Unexpected failure in getIndexForType objClass=aa....aa.

aa....aa: Class name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20957-E

Unable to remove the transaction ID aa....aa.

aa....aa: Transaction uid

Description

An I/O error occurred when removing the transaction ID from the store.

Action

Contact maintenance personnel for internal errors.

KDAN20958-E

Unknown Transaction ID aa....aa for transaction ack [bb....bb:cc....cc]dd....dd

aa....aa: Transaction uid

bb....bb: System message ID

cc....cc: Consumer uid

dd....dd: Broker address

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20959-E

updateState(): Unknown transaction: aa....aa.

aa....aa: Transaction uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20960-E

updateState(): No state for transaction: aa....aa.

aa....aa: Transaction uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20961-E

Internal Error:Error updating transaction acks aa....aa.

aa....aa: Transaction uid

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20970-E

Unable to start transaction reaper thread .

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20971-E

Failed to schedule detached-transaction reaper aa....aa.

aa....aa: Transaction list

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20972-E

set empty

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20973-E

not part of set

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20979-E

flow paused is not supported by the client.

Description

This error occurs when an attempt is made to perform an unsupported operation.

Action

Contact maintenance personnel for internal errors.

KDAN20980-E

Cannot use JMQValidate with an ackType of aa....aa.

aa....aa: Acknowledgement type

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20981-E

Cannot use JMQValidate with no tid.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20982-E

Acknowledgement could not be found.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20985-E

Internal Error: bad protocol

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20986-E

Invalid Deliver Message Size: aa....aa. Not multiple of bb....bb.

aa....aa: Message body size

bb....bb: Message size

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20987-E

Internal Error: setting timeout .

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20988-E

received unexpected error in handler.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20989-E

Invalid Redeliver Message Size: aa....aa. Not multiple of bb....bb.

aa....aa: Message body size

bb....bb: redeliver block size

Description

The size of the Redeliver message is invalid.

Action

Confirm that the size of the Redeliver message is valid.

KDAN20990-E

Unknown XID aa....aa

aa....aa: JMQXid

Description

This error occurs when the transaction UID is null.

Action

Confirm that the transaction UID is not null.

KDAN20991-E

No transaction ID

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN20992-E

Unknown service restriction aa....aa on service bb....bb.

aa....aa: Service restriction

bb....bb: Service

Description

An internal error occurred. The service contains an unknown restriction.

Action

Contact maintenance personnel for internal errors.

KDAN20995-E

Cannot load props

Description

An I/O error occurred when acquiring the properties from the packet.

Action

Contact maintenance personnel for internal errors.

KDAN20996-E

Low memory

Description

This error occurs when the JVM memory size is exceeded.

Action

Increase the JVM memory size.

KDAN20997-E

cannot create destination

Description

This error occurs when the destination is null.

Action

Confirm that an appropriate destination name and type is specified.

KDAN20998-E

no destination passed [dest,type] = [aa....aa,bb....bb].

aa....aa: Destination

bb....bb: Destination type

Description

This error occurs when the destination name or type is null.

Action

Confirm that an appropriate destination name and type is specified.

KDAN20999-E

unknown producer

Description

This error occurs when the producer is null during the deletion of the producer. This error occurs when the producer is already closed.

Action

Confirm that an application or client has not closed the producer.

KDAN21000-E

Trying to add handler which has no corresponding packet type [ aa....aa].

aa....aa: Packet type

Description

An error occurred when registering a new handler for the message ID. The message ID is too long.

Action

Contact maintenance personnel for internal errors.

KDAN21001-E

Unexpected Error processing message

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21011-E

non-XA transactions only supported on non-sessionless connections.

Description

This error occurs when non-XA transactions are used on sessionless connections. This is not supported.

Action

Contact maintenance personnel for internal errors.

KDAN21013-E

Message requeued:aa....aa.

aa....aa: Packet reference

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21014-E

aa....aa is closed.

aa....aa: Session uid

Description

This error occurs when an attempt is made to add a consumer to a closed session.

Action

Confirm that the session is not closed.

KDAN21015-E

Already dead

Description

This error occurs when an attempt is made to delete an already deleted dead message from the dead message queue.

Action

Delete a dead message only when the message exists in the dead message queue.

KDAN21016-E

No Reaper

Description

This error occurs when the message expiration reaper is null.

Action

Contact maintenance personnel for internal errors.

KDAN21017-E

Null destination passed to GetDurablesHandler

Description

This error occurs when a destination is passed as null.

Action

Confirm that the destination is not null.

KDAN21018-E

Admin: GetTransactions: Could not extract properties from pkt

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21019-E

invalid packet type aa....aa

aa....aa: Packet type

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21021-E

Null/ Missing values for aa....aa and/ or bb....bb properties.

aa....aa: Message type

bb....bb: Message type

Description

This error occurs when null is passed for JMQCommand and JMQCommandArg.

Action

Confirm that JMQCommand and JMQCommandArg are not null.

KDAN21023-E

Rollback of non-XA transaction aa....aa in non-PREPARED state is not supported.

aa....aa: Transaction uid

Description

This error occurs when an attempt is made to rollback a non-XA transaction in a non-PREPARED state. This is not supported.

Action

Contact maintenance personnel for internal errors.

KDAN21024-E

Could not locate TransactionHandler

Description

An internal error occurred. The TransactionHandler class was not found during rollback/commit transaction.

Action

Contact maintenance personnel for internal errors.

KDAN21025-E

conflict w/ clientID

Description

This error occurs when an attempt was made to create an existing client ID.

Action

Make sure that the client ID is unique.

KDAN21026-E

transaction failed: aa....aa

aa....aa: Error message

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21027-E

No session for aa....aa

aa....aa: Session uid

Description

This error occurs when an attempt is made to stop or start a session when the session is null.

Action

Confirm that the session is not null.

KDAN21028-E

AckInfo aa....aa

aa....aa: Acknowledgement information

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21029-E

access to destination aa....aa is forbidden.

aa....aa: Destination

Description

This error occurs when an attempt is made to browse a non-browsable destination.

Action

Make sure that the destination is browsable.

KDAN21030-E

double ack

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21031-E

getBrokerInfo:

Description

An internal error occurred when acquiring the Broker information.

Action

Contact maintenance personnel for internal errors.

KDAN21032-E

XXX not implemented

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21033-E

aa....aa : Got exception when reading bb....bb bytes from buffer cc....cc.

aa....aa: Class name

bb....bb: Buffer length

cc....cc: Buffer name

Description

This error occurs when the data is read from this input stream into the byte string.

Action

Contact maintenance personnel for internal errors.

KDAN21034-E

Class MetricCounters could not be cloned.

Description

This error occurs when the log handler class does not exist.

This error occurs when an appropriate package name is not specified for a class.

Action

Confirm that the class exists.

Specify an appropriate Broker package.

KDAN21035-E

Exception when reading packet body: aa....aa.

aa....aa: Exception

Description

An internal error occurred during the reading of the packet body.

Action

Contact maintenance personnel for internal errors.

KDAN21036-E

Unknown authentication type

Description

This error occurs when an invalid authentication type is specified in the default configuration file.

Action

Specify a valid authentication type in the default configuration file.

KDAN21037-E

Exception when deserializing packet body: aa....aa.

aa....aa: Exception

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21038-E

Could not decode XIDs: aa....aa.

aa....aa: Exception

Description

An I/O error occurred when reading Xid from the input stream.

Action

Contact maintenance personnel for internal errors.

KDAN21039-E

Could not decode INFO packet: aa....aa.

aa....aa: Exception

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21040-E

Could not decode XID: aa....aa.

aa....aa: Exception

Description

An I/O error occurred when reading Xid from the input stream.

Action

Contact maintenance personnel for internal errors.

KDAN21041-E

Could not decode verify body: aa....aa.

aa....aa: Exception

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21042-E

Exception when deserializing packet body: aa....aa.

aa....aa: Exception

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21043-E

unable to load fallback properties.

Description

An I/O error occurred when reading the Fallback properties (properties used when the property file cannot be used).

Action

Contact maintenance personnel for internal errors.

KDAN21044-E

no threads available from pool aa....aa.

aa....aa: List

Description

This error occurs when an attempt is made to acquire the thread object from the thread pool when there are no free threads.

Action

Contact maintenance personnel for internal errors.

KDAN21045-E

connection gone

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21046-E

aa....aa has been destroyed.

aa....aa: Thread

Description

An I/O error occurred during the addition of a connection.

Action

Contact maintenance personnel for internal errors.

KDAN21047-E

Could not get charset: aa....aa.

aa....aa: Exception

Description

This error occurs when the specified character set name is invalid.

Action

Contact maintenance personnel for internal errors.

KDAN21048-E

Could not decode string aa....aa.

aa....aa: Exception

Description

This error occurs when the decode operation is already in progress.

Action

Contact maintenance personnel for internal errors.

KDAN21049-E

Exception on pending con aa....aa : cannot process.

aa....aa: IMQIP connection

Description

An I/O error occurred during the processing of the threads.

Action

Contact maintenance personnel for internal errors.

KDAN21050-E

Connection aa....aa no longer has a valid channel.

aa....aa: IMQIP connection

Description

An I/O error occurred during the processing of pending connections.

Action

Contact maintenance personnel for internal errors.

KDAN21052-E

unable to create class for handling READ selectors.

Description

The ReadThread class does not exist.

An appropriate package name is not specified for the class.

Action

Confirm that the ReadThread class exists.

Specify an appropriate package name.

KDAN21053-E

unable to create class for handling WRITE selectors.

Description

The WriteThread class does not exist.

An appropriate package name is not specified for the class.

Action

Confirm that the WriteThread class exists.

Specify an appropriate package name.

KDAN21054-E

service does not have thread pool.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21055-E

Internal Error: TakingoverTracker.setMessageMap() not runner thread.

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21056-E

Internal Error: TakingoverTracker.setMessageMap() unexpected stage aa....aa (bb....bb).

aa....aa: Stage

bb....bb: Expected stage

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21057-E

addShutdownHook: can't find java.lang.Thread: aa....aa.

aa....aa: Exception

Description

The java.lang.Threadclass class does not exist.

An appropriate package name is not specified for the class.

Action

Confirm that the class exists.

Specify an appropriate package name.

KDAN21058-E

addShutdownHook: could not call addShutdownHook: aa....aa.

aa....aa: Exception

Description

An internal error occurred during the addition of the shut down hook.

Action

Contact maintenance personnel for internal errors.

KDAN21059-E

removeShutdownHook: can't find java.lang.Thread: aa....aa.

aa....aa: Exception

Description

The java.lang.Threadclass class does not exist.

An appropriate package name is not specified for the class.

Action

Confirm that the class exists.

Specify an appropriate package name.

KDAN21060-E

removeShutdownHook: could not call removeShutdownHook: aa....aa.

aa....aa: Exception

Description

An internal error occurred during the remove of the shut down hook.

Action

Contact maintenance personnel for internal errors.

KDAN21061-E

Exception running broker.

Description

An internal error occurred when starting the Broker.

Action

Contact maintenance personnel.

KDAN21062-E

aa....aa:allocate()

aa....aa: Exception

Description

An I/O exception occurred.

Action

Make sure that the network connection is correct.

Check whether the I/O device or driver is running.

Contact the System Administrator.

KDAN21063-E

Too many threads aa....aa,bb....bb

aa....aa: Current count

bb....bb: maximum count

Description

This error occurs when an attempt is made to create a thread when the maximum thread count is exceeded.

Action

Contact maintenance personnel for internal errors.

KDAN21064-E

got an unexpected error aa....aa freeing thread bb....bb.

aa....aa: Exception

bb....bb: Thread

Description

An internal error occurred during the processing of the thread.

Action

Contact maintenance personnel for internal errors.

KDAN21066-E

generateUID: quantity is less than 0: aa....aa

aa....aa: Quantity

Description

This error occurs when an attempt is made to generate a unique ID that is smaller than 0.

Action

Contact maintenance personnel for internal errors.

KDAN21067-E

setClientId: set client ID failed. Connection ID: aa....aa , Client ID: bb....bb, Shareable: cc....cc, nameSpace: dd....dd.

aa....aa: Connection uid

bb....bb: Client ID

cc....cc: Shareable

dd....dd: Namespace

Description

An internal error occurred when an attempt was made to set up a client ID for the connection.

Action

Contact maintenance personnel for internal errors.

KDAN21068-E

unsetClientId: unset client ID failed. Connection ID: aa....aa.

aa....aa: Connection uid

Description

An internal error occurred when an attempt was made to set up a null client ID for the connection.

Action

Contact maintenance personnel for internal errors.

KDAN21069-E

createSession: create session failed. Connection ID: aa....aa, acknowledge mode: bb....bb.

aa....aa: Connection uid

bb....bb: Acknowledgement mode

Description

This error occurs when an attempt by the connection object to create a session fails due to an internal error or when the transaction and acknowledgement mode are not supported.

Action

Confirm that the specified transaction and acknowledgement mode are supported.

KDAN21070-E

destroySession: destroy session failed. Connection ID: aa....aa, Session ID: bb....bb.

aa....aa: Connection uid

bb....bb: Session uid

Description

An internal error occurred when closing the session or when an attempt to release the resources or close the socket connection fails.

Action

Contact maintenance personnel for internal errors.

KDAN21071-E

startSession: Start of session failed. Session ID: aa....aa.

aa....aa: Session uid

Description

This error occurs when an attempt is made to restart the session when the session uid is null.

Action

Confirm that the session uid is not null.

KDAN21072-E

stopSession: Stop of session failed. Session ID: aa....aa.

aa....aa: Session uid

Description

This error occurs when an attempt is made to pause the session when the session uid is null.

Action

Confirm that the session uid is not null.

KDAN21073-E

verifyDestination: verify of destination failed. Destination name: aa....aa, type: bb....bb.

aa....aa: Destination name

bb....bb: Destination type

Description

This error occurs when the applicable destination does not exist in the destination list.

Action

Confirm that the specified destination exists in the store.

KDAN21074-E

createDestination: Destination creation failed. Destination name: aa....aa, type:bb....bb, lifespan: cc....cc.

aa....aa: Destination name

bb....bb: Destination type

cc....cc: Lifespan

Description

This error occurs when the user does not have the permission to create a destination.

This error occurs when a Broker error occurs during the creation of a destination.

Action

Confirm that the user has the permission to create a destination.

Contact maintenance personnel.

KDAN21075-E

destroyDestination: Destination destroy failed. Destination name: aa....aa, type: bb....bb, lifespan: cc....cc.

aa....aa: Destination name

bb....bb: Destination type

cc....cc: Lifespan

Description

This error occurs when the destination does not exist in the store.

This message is displayed when an error occurs during the destroy of a destination.

Action

Confirm that the specified destination exists in the store.

Contact maintenance personnel.

KDAN21076-E

addProducer: Add producer failed. Connection ID: aa....aa, session ID: bb....bb.

aa....aa: Connection uid

bb....bb: Session uid

Description

This error occurs when the user does not have the permissions or when an attempt is made to create producers after the maximum producer limit is exceeded.

An internal error occurred during the creation of a producer.

Action

Confirm that the user has the permissions for creating a producer.

Contact maintenance personnel for internal errors.

KDAN21077-E

deleteProducer: Delete producer failed. Connection ID: aa....aa, session ID: bb....bb, producer ID: cc....cc.

aa....aa: Connection uid

bb....bb: Session uid

cc....cc: Producer uid

Description

This error occurs when the specified producer is not created.

Action

Confirm that the specified producer is already created.

KDAN21078-E

addConsumer: Add consumer failed. Connection ID: aa....aa, session ID: bb....bb.

aa....aa: Connection uid

bb....bb: Session uid

Description

An error occurred during the creation of a consumer.

Action

Confirm that the connection and session are not closed.

KDAN21079-E

deleteConsumer: Delete consumer failed. Connection ID: aa....aa, session ID: bb....bb, consumer ID: cc....cc, durable name: dd....dd, client ID: ee....ee.

aa....aa: Connection uid

bb....bb: Session uid

cc....cc: Consumer uid

dd....dd: Durable subscriber name

ee....ee: Client ID

Description

An error occurred during the deletion of a consumer.

This error occurs when an attempt is made to unsubscribe a consumer that has been deleted when the destination was destroyed.

Action

Confirm that the connection and session are not closed.

KDAN21080-E

setConsumerAsync: Set Async consumer failed. Connection ID: aa....aa, session ID: bb....bb, consumer ID: cc....cc.

aa....aa: Connection uid

bb....bb: Session uid

cc....cc: Consumer uid

Description

This error occurs when an asynchronous listener is registered to a consumer.

Action

Confirm that the connection and session are not closed.

KDAN21088-E

sendMessage: Sending message failed. Connection ID: aa....aa.

aa....aa: Connection uid

Description

A problem occurred when sending a message. A possible cause is that the maximum number of messages or maximum total message bytes or maximum bytes/ messages was exceeded.

An internal error occurred.

Action

Increase the maximum limit of the message count/ total message bytes/ bytes/ messages for the relevant destination.

Contact maintenance personnel.

KDAN21089-E

fetchMessage: Fetch Message failed. Connection ID: aa....aa, session ID: bb....bb, consumer ID: cc....cc.

aa....aa: Connection uid

bb....bb: Session uid

cc....cc: Consumer uid

Description

A problem occurred when acquiring the messages from the Broker.

Action

Contact maintenance personnel for internal errors.

KDAN21090-E

acknowledgeMessage: Sending Acknowledgement failed. Connection ID: aa....aa.

aa....aa: Connection uid

Description

A problem occurred during message acknowledgement to the Broker.

Action

Contact maintenance personnel for internal errors.

KDAN21091-E

sendAcknowledgement: Sending Acknowledgement failed. Connection ID: aa....aa.

aa....aa: Connection uid

Description

A problem occurred when sending an acknowledgement to the Broker.

Action

Contact maintenance personnel for internal errors.

KDAN21092-E

addBrowser: Add browser failed. Connection ID: aa....aa, session ID: bb....bb, destination: cc....cc, selector: dd....dd.

aa....aa: Connection uid

bb....bb: Session uid

cc....cc: Destination

dd....dd: Selector

Description

This error occurs when the specified selector string is invalid when the browser is added.

Action

Confirm that the specified selector string is valid.

KDAN21093-E

deleteBrowser: consumer ID not found. Connection ID:aa....aa, Session ID: bb....bb, Consumer ID: cc....cc.

aa....aa: Connection uid

bb....bb: Session uid

cc....cc: Consumer uid

Description

This error occurs when the specified consumer does not exist in the queue browser list when the browser is deleted.

Action

Make sure that the consumer is not closed.

KDAN21094-E

browseMessages: Destination not found. Connection ID:aa....aa, Session ID: bb....bb, Consumer ID: cc....cc destination: dd....dd.

aa....aa: Connection uid

bb....bb: Session uid

cc....cc: Consumer uid

dd....dd: Destination

Description

This error occurs when the destination is not found during the browsing of the messages.

Action

Confirm that the specified destination exists in the store.

KDAN21095-E

browseMessages: Browse queue failed. Connection ID: aa....aa, session ID: bb....bb, consumer ID: cc....cc.

aa....aa: Connection uid

bb....bb: Session uid

cc....cc: Consumer uid

Description

This error occurs when the specified selector string is invalid when the browser is added.

Action

Confirm that the specified selector string is valid.

KDAN21096-E

browseMessages: consumer ID not found. Connection ID:aa....aa, Session ID: bb....bb, Consumer ID: cc....cc.

aa....aa: Connection uid

bb....bb: Session uid

cc....cc: Consumer uid

Description

This error occurs when the destination is not found during the browsing of the messages.

Action

Make sure that the consumer is not closed.

KDAN21097-E

redeliverMessages: Redeliver failed. Connection ID: aa....aa, session ID: bb....bb, transaction ID: cc....cc.

aa....aa: Connection uid

bb....bb: Session uid

cc....cc: Transaction uid

Description

An I/O error occurred during the redelivery of the messages.

Action

Contact maintenance personnel for internal errors.

KDAN21098-E

aa....aa:connection ID not found: bb....bb.

aa....aa: Method name

bb....bb: Connection uid

Description

This error occurs when an attempt is made to perform some operations (such as add/delete browser, consumer, producer, or fetch messages) for a connection when an invalid connection ID has been passed.

Action

Contact maintenance personnel for internal errors.

KDAN21099-E

aa....aa:session ID not found: bb....bb.

aa....aa: Method name

bb....bb: Session uid

Description

This error occurs when an attempt is made to perform some operations (such as add/delete browser, consumer, producer, or fetch messages) for a session when an invalid session ID has been passed.

Action

Contact maintenance personnel for internal errors.

KDAN21100-E

Cannot invoke SessionListener.getNextConsumerPacket() when in asynchronous receiving mode.

Description

This error occurs when messages are fetched from the Broker in the asynchronous reception mode.

Action

Contact maintenance personnel for internal errors.

KDAN21101-E

Connection has been closed aa....aa.

aa....aa: IMQIP connection

Description

This error occurs when the IMQIP connection is closed during the reading of the data from the packet.

Action

Confirm that the connection is open.

KDAN21102-E

Failed to copy old persistent data under aa....aa to bb....bb.

aa....aa: Current directory

bb....bb: Root directory

Description

The file does not have read permission.

The file is corrupted or the configured file does not exist.

An I/O error occurred.

Action

Grant the read permission to the file.

Repeat the operation. If the problem is not resolved, restart the Broker. In this case, the old data is lost.

Contact maintenance personnel.

KDAN21103-E

This should never happen!

Description

This message is displayed when an attempt is made to clone the transaction information object for the specified transaction.

Action

Confirm that the class of the object supports the Cloneable interface.

KDAN21104-E

Could not parse properties aa....aa.

aa....aa: Exception

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21105-E

Could not marshal properties aa....aa.

aa....aa: Exception

Description

An I/O error occurred when acquiring the property bytes.

Action

Confirm that the network connection is appropriate.

KDAN21106-E

Exception getting properties: aa....aa.

aa....aa: Exception message

Description

An I/O error occurred when acquiring the properties.

Action

Confirm that the network connection is appropriate.

KDAN21107-E

Could not get message body: aa....aa.

aa....aa: Exception

Description

An error occurred during the reading of a null message body.

An I/O error occurred when acquiring the message body.

Action

Make sure that the message body is not null.

Contact maintenance personnel.

KDAN21108-E

aa....aa:setCookie()

aa....aa: VRecordRAF information

Description

A runtime exception occurred when writing a message and its consumer state in VRFile.

Action

Contact maintenance personnel for internal errors.

KDAN21109-E

aa....aa:free()

aa....aa: VRecordRAF information

Description

A runtime exception occurred while releasing a record from VRFile.

Action

Contact maintenance personnel for internal errors.

KDAN21110-E

Fault Injection: triggered aa....aa selector [bb....bb]

aa....aa: Fault

bb....bb: Selector

Description

An I/O error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN21111-E

Internal Error: Invalid Acknowledge Packet processing notifying client aa....aa

aa....aa: Packet information

Description

An internal error occurred during the processing of an acknowledgement message.

Action

Contact maintenance personnel for internal errors.

KDAN21115-E

The END target for BETWEEN must be a numeric value. Found aa....aa

aa....aa: Class name

Description

This error occurs when END of the BETWEEN statement is not a numeric value.

Action

Confirm that the END of the BETWEEN statement is a numeric value.

KDAN21116-E

Pass <vmarguments> to the Java VM.

Description

This message is displayed when no command argument is specified in -vmargs.

Action

Specify a valid command argument in -vmargs.

KDAN21118-E

Acknowledgement could not be processed because the broker is shutting down.

Description

This error occurs when the Broker is shut down during the processing of an acknowledgement.

Action

Confirm that the Broker is running.

KDAN21119-E

Transaction acknowledgement could not be added because message aa....aa has already been removed.

aa....aa: Message ID

Description

This error occurs when the message does not exist in the destination.

Action

Confirm that the relevant message exists in the destination.

KDAN21120-E

Transaction acknowledgement could not be added because message aa....aa was locked.

aa....aa: Message ID

Description

An internal error occurred during the addition of an acknowledgement.

Action

Contact maintenance personnel for internal errors.

KDAN21121-E

Specify a valid absolute path for var home to use.

Description

This error occurs when the directory path is not specified in the -varhome option.

Action

Specify the correct directory path in the -varhome option.

KDAN21122-E

Exception caught while login. Reason: aa....aa.

aa....aa: Error reason

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21123-E

Exception caught while updating portmapper property. Reason: aa....aa.

aa....aa: Error reason

Description

An invalid property name was specified in the attribute value to be updated.

An invalid property value was specified in the attribute value to be updated.

Action

Specify the correct property name in the attribute value to be updated.

Specify the correct property value in the attribute value to be updated.

KDAN21124-E

Exception canceling key.

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21125-E

Exception processing aa....aa.

aa....aa: Error information

Description

An error occurred in the connection processing.

Action

Contact maintenance personnel.

KDAN21126-E

Exception while removing persistent store. Reason: aa....aa.

aa....aa: Error reason

Description

An error occurred when an attempt was made to remove the persistence store.

Action

Make sure that the persistence store permissions are appropriate.

KDAN21127-E

Internal Error : aa....aa.

aa....aa: Error reason

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21128-E

Exception occur while upgrading the store. Reason: aa....aa.

aa....aa: Error reason

Description

The old persistence store is invalid.

The old persistence store does not exist.

Action

Re-execute the operation. If the problem persists, restart the Broker.

After the Broker is restarted, the message and destination data is lost.

KDAN21129-E

Unsupported Operation.

Description

An unsupported method was invoked.

Action

Contact maintenance personnel.

KDAN21130-E

Already waiting for aa....aa

aa....aa: Object

Description

This message is displayed when the system is already waiting for the specified object during request notification.

Action

Contact maintenance personnel.

KDAN21131-E

Unknown size aa....aa

aa....aa: Property value or byte value

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21132-E

Unable to paused unknown destination aa....aa.

aa....aa: Destination

Description

This error occurs when the destination is paused and does not exist in the persistence store.

Action

Make sure that the persistence store exists in the destination.

KDAN21133-E

Unable to paused admin or internal destination aa....aa.

aa....aa: Destination

Description

This error occurs when the creation of the destination is paused.

Action

Check whether the destination has been created when the creation of a destination is paused.

KDAN21134-E

Unable to resume unknown destination aa....aa.

aa....aa: Destination

Description

This error occurs when the specified destination does not exist in the persistence store.

Action

Make sure that the destination exists in the persistence store.

KDAN21135-E

Internal error processing delete consumer aa....aa

aa....aa: Consumer

Description

An internal error occurred when deleting the specified consumer.

Action

Contact maintenance personnel.

KDAN21136-E

Failed to delete file: aa....aa.

aa....aa: File name

Description

The file specified in the path does not exist.

The file does not have delete permission.

Action

Confirm that the file exists.

Confirm that the file has delete permission.

KDAN21137-E

Internal Error loading/ routing transacted message, throwing out message aa....aa.

aa....aa: Error message

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21138-E

Internal Exception:

Description

This message is displayed during the display of the internal error.

Action

Contact maintenance personnel.

KDAN21139-E

Exception caught while updating the broker configuration. Reason: aa....aa.

aa....aa: Error reason

Description

The properties cannot be set up due to some reason.

The properties cannot be stored.

Action

Make sure that values can be set up for the properties.

Confirm that the properties can be stored.

KDAN21140-E

Client Failover

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21141-E

Failed to truncate file: aa....aa.

aa....aa: File name

Description

An I/O error occurred during file operations.

Action

Make sure that the network connection is correct.

Check whether the I/O device or driver is running.

Contact the System Administrator.

KDAN21142-E

Bad sysmessageid is specified.

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21143-E

Properties is not specified.

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21144-E

BEFORE SLEEP aa....aa(seconds) BECAUSE OF FAULT bb....bb

aa....aa: Number of seconds

bb....bb: Invalid value

Description

An internal error occurred in the Broker.

Action

Re-execute the operation. If the problem persists, restart the Broker. If the Broker is restarted, the old data is lost.

Contact maintenance personnel.

KDAN21145-E

Internal Error: unable to process consumer request aa....aa.

aa....aa: Packet

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21146-E

Error setting overrides

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21147-E

Shutting down metrics, timer has been canceled.

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21148-E

Sending detach notification for aa....aa from bb....bb.

aa....aa: Consumer ID

bb....bb: Persistence subscriber

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21149-E

XXX - internal error handling delivery policy change

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21150-E

Internal Error Unable to consume aa....aa:bb....bb.

aa....aa: Consumer ID

bb....bb: Packet reference

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21151-E

Internal Exception: unable to load destination aa....aa.

aa....aa: Topic destination

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21152-E

Monitor destination Error aa....aa.

aa....aa: Destination name

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21153-E

Internal Error: unable to retrieve properties from resume message aa....aa.

aa....aa: Packet

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21154-E

Internal Error: unable to retrieve properties from generateUID message aa....aa.

aa....aa: Packet

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21155-E

Internal Error: error retrieving properties from INFO_REQUEST message.

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21156-E

Internal Error: error retrieving properties from hello message.

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21157-E

Internal Error: unable to retrieve properties from goodbye message aa....aa.

aa....aa: Packet

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21158-E

SLEEP aa....aa(seconds) FAULT (bb....bb) interrupted: cc....cc

aa....aa: Number of seconds

bb....bb: Invalid value

cc....cc: Error message

Description

An internal error occurred in the Broker.

Action

Re-execute the operation. If the problem persists, restart the Broker. If the Broker is restarted, the old data is lost.

Contact maintenance personnel.

KDAN21159-E

error connection removing producer it doesn't own PID=aa....aa, connectionUID of request bb....bb, connectionUID of creator cc....cc, checking producer state: dd....dd.

aa....aa: Producer ID

bb....bb: Connection ID

cc....cc: Connection ID

dd....dd: Producer ID

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21160-E

SHUTING DOWN BROKER BECAUSE OF FAULT aa....aa

aa....aa: Invalid value

Description

An internal error occurred in the Broker.

Action

Re-execute the operation. If the problem persists, restart the Broker. If the Broker is restarted, the old data is lost.

Contact maintenance personnel.

KDAN21161-E

HALTING BROKER BECAUSE OF FAULT aa....aa

aa....aa: Invalid value

Description

An internal error occurred in the Broker.

Action

Re-execute the operation. If the problem persists, restart the Broker. If the Broker is restarted, the old data is lost.

Contact maintenance personnel.

KDAN21162-E

Broker down Unable to acknowledge aa....aa:bb....bb

aa....aa: SysMessageID

bb....bb: Consumer ID

Description

An internal error occurred in the Broker.

Action

Re-execute the operation. If the problem persists, restart the Broker.

If the problem persists even after restarting the Broker, delete the Broker instance, and then re-create. In this case, the message and destination data will be lost.

Contact maintenance personnel.

KDAN21163-E

Invalid value for -reset

Description

This error occurs when the arguments for -reset are invalid.

Action

Specify correct arguments for -reset.

KDAN21164-E

Running low on memory while writing a message to a client, the current message may be lost

Description

This error occurs when the specified Java memory is exceeded.

Action

Increase the Java memory size. Contact maintenance personnel.

KDAN21165-E

The broker ran out of memory during startup and was unable to recover, please adjust the amount of memory allocated to the java process in the cjmsbroker script or bat file and restart the broker

Description

This error occurs when the specified Java memory is exceeded.

Action

Increase the Java memory size. Contact maintenance personnel.

KDAN21166-E

Running low on memory while allocating space for a message header, system will attempt to recover

Description

This error occurs when the specified Java memory is exceeded.

Action

Increase the Java memory size. Contact maintenance personnel.

KDAN21167-E

Invalid value for -remove

Description

This error occurs when the arguments for -remove are invalid.

Action

Specify correct arguments for -remove.

KDAN21168-E

Running low on memory while portmapper service listening client connection, system will attempt to recover.

Description

This error occurs when the specified heap memory is exceeded.

Action

Increase the heap size. Contact maintenance personnel.

KDAN21169-E

Running low on memory while portmapper service processing client connection, system will attempt to recover.

Description

This error occurs when the specified heap memory is exceeded.

Action

Increase the heap size. Contact maintenance personnel.

KDAN21170-E

Running low on memory in portmapper service, broker will attempt to restart.

Description

This error occurs when the specified heap memory is exceeded.

Action

Increase the heap size. Contact maintenance personnel.

KDAN21171-E

Unable to process admin request: Broker has not completed startup.

Description

This error occurs when the Broker has not completed startup.

Action

Re-execute the operation. If the problem persists, restart the Broker.

If the problem persists even after restarting the Broker, delete the Broker instance, and then re-create. In this case, the old data will be lost.

KDAN21172-E

Unable to process admin request: Broker is shutting down.

Description

This error occurs when Broker is shutting down.

Action

Re-execute the operation. If the problem persists, restart the Broker.

If the problem persists even after restarting the Broker, delete the Broker instance, and then re-create. In this case, the old data will be lost.

KDAN21173-E

Unable to store message to destination aa....aa: Broker is shutting down or destination is being destroyed.

aa....aa: Destination name

Description

This error occurs when the Broker is being shut down while storing the messages in the destination.

This error occurs when the destination does not exist in the store while storing the messages in the destination.

Action

Re-execute the operation. If the problem persists, restart the Broker. In this case, the old data is lost.

KDAN21174-E

Transaction aa....aa has state bb....bb during connection cc....cc cleanup

aa....aa: Transaction ID

bb....bb: Transaction state

cc....cc: Connection ID

Description

This error occurs if the transaction is not closed when the session is closed.

Action

Confirm that the resource is closed correctly after use.

KDAN21175-E

Internal Error: Messageaa....aa queued on destroyed connection bb....bb.

aa....aa: Packet

bb....bb: IMQIPConnection object

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21176-E

Wait for reference : aa....aa.

aa....aa: Packet reference

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21177-E

Weird reference behavior aa....aa.

aa....aa: Packet reference

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21178-E

loaded durable consumer [cid=aa....aa, dn=bb....bb] already exists cc....cc

aa....aa: Client ID

bb....bb: Persistence subscriber name

cc....cc: Persistence subscriber list

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21179-E

Canceling message expiration on aa....aa

aa....aa: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21180-E

Unknown Monitor destination aa....aa.

aa....aa: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21181-E

Data logged at file aa....aa

aa....aa: File name

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21182-E

Unknown dump arg aa....aa.

aa....aa: Argument

Description

This error occurs when invalid arguments are specified.

Action

Specify the correct argument.

KDAN21183-E

Ignore duplicated redeliver request [aa....aa:bb....bb]

aa....aa: Packet

bb....bb: Error message

Description

An internal error of the Broker occurred when attributes were acquired from a message packet.

Action

Contact maintenance personnel.

KDAN21184-E

Session aa....aa is bad because it is from a different connection [owning,current]=[bb....bb,cc....cc].

aa....aa: Session ID

bb....bb: Connection ID

cc....cc: Connection ID

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21185-E

local consumer does not have associated session aa....aa.

aa....aa: Consumer ID

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21186-E

Bad body in destroy consumer

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21187-E

Bad selector format, cannot match against aa....aa

aa....aa: Selector string

Description

A syntax error occurred in the specification of the selector.

Action

Modify the selector correctly.

KDAN21188-E

Unable to retrieve transaction information aa....aa for bb....bb we may be clearing the transaction

aa....aa: Transaction information

bb....bb: Transaction ID

Description

An error occurred when a transaction was acquired from the transaction list when the transaction does not exist.

Action

Contact maintenance personnel.

KDAN21189-E

Could not get variable headeraa....aa.

aa....aa: Error message

Description

An I/O error occurred during packet processing.

Action

Make sure that the network connection is correct.

Check whether the I/O device or driver is running.

Contact the System Administrator.

KDAN21190-E

Max file descriptors: aa....aa (bb....bb).

aa....aa: Current value

bb....bb: Maximum number

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21191-E

Unable to clean up message aa....aa after ack processing

aa....aa: Packet reference

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21192-E

Received bad address aa....aa ignoring

aa....aa: mqAddress

Description

An internal error occurred in the Broker.

Action

Contact maintenance personnel.

KDAN21193-E

Cannot reschedule task, timer has been canceled, the broker is probably shutting down.

Description

An internal error occurred in the Broker.

Action

Check the error log and take measures, or contact maintenance personnel.

KDAN21701-E

Could not use log file aa....aa.bb....bb

aa....aa: Log file

bb....bb: Reason for the non-availability of the file

Description

The directory could not be created for the log location.

The log file does not have the write permission.

Action

Specify the appropriate permissions for creating the log location.

Either grant write permissions to the log file or remove the read attribute.

KDAN21702-E

Could not open logging device aa....aa.bb....bb

aa....aa: Logging device

bb....bb: Reason why the device was not opened

Description

An I/O error occurred when opening the file logging device.

Action

Confirm that appropriate permissions have been given to the file.

KDAN21703-E

Could not log message to aa....aa.bb....bb

aa....aa: Logging device

bb....bb: Reason why login failed

Description

An I/O error occurred when writing to the log file.

An I/O error occurred when writing to the OUT or ERR stream.

Action

Confirm that appropriate permissions have been granted to the file.

KDAN21704-E

No log handlers specified by aa....aa.

aa....aa: Property name

Description

The log handler is not specified in the property file.

Action

Specify one of the following log handlers:

File, console, destination, jmx

KDAN21705-E

No log handler specified by aa....aa.

aa....aa: Property name

Description

The implementation class is not specified in the log handler.

Action

Confirm that the log handler has an implementation class.

KDAN21706-E

Could not load LogHandler class: aa....aa

aa....aa: LogHandler class name

Description

The log handler class does not exist.

A package name appropriate for the class is not specified.

Action

Confirm that the class exists.

Specify an appropriate package name.

KDAN21707-E

Unable to find version properties for this resource, jar file may be corrupted.

Description

The version.properties file does not exist.

Action

Specify the version.properties file in an appropriate location.

KDAN21708-E

Exception loading version properties for this resource, jar file may be corrupted.

Description

An error occurred when reading from the version properties.

The properties file is corrupted or does not have appropriate permissions.

Action

Specify appropriate permissions for the file.

KDAN21709-E

Error retrieving version information from aa....aa

aa....aa: Class path name

Description

The version property object is null.

Action

Specify the version.properties file in an appropriate location.

KDAN21710-E

Compact cannot be done on opened file.

Description

This error occurs when an attempt is made to compress an opened VRFile (file that stores the file store information).

Action

Before compressing the file, make sure that the file is closed.

KDAN21711-E

File is not yet opened and loaded.

Description

This error occurs when an attempt is made to perform some operations on an unopened VRFile (Variable Record file- saves the file store information).

Action

Before performing some operations for VRFile, call the open method to open the file.

KDAN21712-E

Failed to rename backing file aa....aa to backup file bb....bb

aa....aa: Backing file name

bb....bb: Backup file name

Description

This error occurs when an attempt to rename a file to the backup file failed during the compression of VRFile.

Action

Specify the appropriate permissions for the file store.

KDAN21713-E

Failed to rename temp file aa....aa to backing file bb....bb

aa....aa: Backing file name

bb....bb: Backup file name

Description

This error occurs when an attempt to rename a temporary file to VRFile failed during the compression of VRFile.

Action

Specify the appropriate permissions for the file store.

KDAN21714-E

Failed to delete the backup file aa....aa

aa....aa: Backup file path

Description

The backup file could not be deleted during the compression of VRFile.

Action

Specify the appropriate permissions for the file store.

KDAN21715-E

aa....aa:Bad file magic number: bb....bb; Expecting: cc....cc

aa....aa: Backing file path

bb....bb: Number read from the backing file

cc....cc: Expected magic number

Description

The magic number in VRFile differs from the expected magic number.

Action

Confirm that the file in the file store is not corrupted.

KDAN21716-E

aa....aa:Unsupported VRFile version: bb....bb; Expecting: cc....cc

aa....aa: Backing file path

bb....bb: Found version number

cc....cc: Expected version number

Description

The VRFile version differs from the expected version.

Action

Confirm that the file in the file store is not corrupted.

KDAN21717-E

aa....aa:Unrecognized VRecord specified

aa....aa: Backing file path

Description

The VRFile records are invalid.

Action

Confirm that the file in the file store is not corrupted.

KDAN21718-E

aa....aa:Unrecognized VRFile format, no valid file header

found, can only read bb....bb bytes

aa....aa: Backing file path

bb....bb: Bytes read from the header

Description

The file format of the record base file is invalid.

Action

Confirm that the file in the file store is not corrupted.

KDAN21719-E

Uncaught exception aa....aa occurred in thread bb....bb

aa....aa: Backing file path

bb....bb: Cookie read from the backing file

Description

This error occurs when the thread is terminated by an uncaught exception.

Action

Contact maintenance personnel for internal errors.

KDAN21720-E

Could not create directory aa....aa.

aa....aa: File path/ directory path

Description

The directory for the log location could not be created.

Action

Grant the appropriate permissions to the log location.

KDAN21721-E

Could not write to file aa....aa.

aa....aa: File path/ directory path

Description

Writing to the log file failed.

Action

Grant the write permission to the log file.

KDAN21722-E

Could not write to file aa....aa. It is a directory.

aa....aa: File path/ directory path

Description

A directory, and not a file, has been used for log file rollover.

Action

No action is required.

KDAN21723-E

Could not write creation timestamp to file aa....aa.

aa....aa: File path/ directory path

Description

This message is displayed when an I/O error occurs or the stream is closed while writing the creation date and time information into the rollover file.

Action

Confirm that the log file location has the appropriate permissions.

KDAN21724-E

Could not read creation timestamp from file aa....aa. It may be corrupted.

aa....aa: File path/ directory path

Description

An I/O error occurred during the reading of the creation date and time from the rollover file.

Action

Confirm that the log file location has the appropriate permissions.

KDAN21726-E

Portmapper version mismatch. Version=aa....aa. Expecting bb....bb

aa....aa: Current version

bb....bb: Expected version

Description

The portmapper version does not match the expected version.

Action

Contact maintenance personnel for internal errors.

KDAN21727-E

Could not skip bytes

Description

An I/O error occurred during the reading of the creation date and time information from the file.

Action

Contact maintenance personnel.

KDAN21728-E

Internal Error: timer canceled.

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN21729-E

Could not set handlers: aa....aa.

aa....aa: Exception

Description

The logger was not closed when specifying the log handlers to be used.

Action

Make sure that the logger is not closed before the handlers are set up.

KDAN21730-E

Logger must be closed before setting handlers.

Description

The logger was not closed when specifying the log handlers to be used.

Action

Make sure that the logger is not closed before the handlers are set up.

KDAN22001-W

Authentication of aa....aa for bb....bb service failed.

aa....aa: User name

bb....bb: Service name

Description

This message is displayed when the specified user does not exist in the user repository.

Action

Specify a valid user name and password.

KDAN22002-W

Unable to load aa....aa property file bb....bb.

aa....aa: Type of property file that could not be opened

bb....bb: Property file path

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22003-W

Unable to save properties without a valid configStore class

Description

This message is displayed when the property file of the specified CJMSP instance does not exist.

Action

Make sure that each CJMSP instance has a valid property file.

KDAN22004-W

Creation of destination aa....aa failed.

aa....aa: Destination name

Description

This message is displayed when the connection does not exist or there is no memory for creating a destination.

Action

Make sure that there is sufficient memory for creating the destination.

KDAN22005-W

Destruction of destination aa....aa failed.

aa....aa: Destination name

Description

This message is displayed when the specified destination is null.

This message is displayed when the specified destination is a dead message queue.

This message is displayed when the specified destination does not exist.

Action

Specify a valid destination existing in CJMSP.

The dead message queue cannot be deleted.

KDAN22006-W

Creation of consumer aa....aa from connection bb....bb on destination cc....cc failed.

aa....aa: Consumer ID

bb....bb: Connection name

cc....cc: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN22007-W

Destruction of consumer aa....aa from connection bb....bb on destination cc....cc failed.

aa....aa: Consumer ID

bb....bb: Connection name

cc....cc: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN22008-W

Storing of JMS message from aa....aa failed.

aa....aa: Message ID

Description

This message is displayed when the specified destination does not exist in the destination file that contains the CJMSP destination information.

This message is displayed when the messages in the system exceed the maximum count and the message is rejected.

Action

Specify a valid destination existing in the destination file.

Create a destination with the specified name.

Increase the maximum number of messages for the CJMSP Broker.

KDAN22009-W

Could not control debug setting of a class

Description

This message is displayed when the debug property is not specified in the property file.

Action

Specify the debug property in the property file.

KDAN22010-W

Browsing of Queue aa....aa failed.

aa....aa: Queue name

Description

This message is displayed when the specified destination does not exist in the destination file that contains the CJMSP destination information.

Action

Specify a valid destination existing in the destination file.

Create a destination with the specified name.

KDAN22011-W

Unable to parse selector aa....aa

aa....aa: Selector string

Description

This message is displayed when the specified message selector expression is invalid.

Action

Specify a valid selector expression based on the SQL92 syntax.

KDAN22012-W

Unable to stop service aa....aa.

aa....aa: Service name

Description

This message is displayed when the specified service is already stopped.

Action

Contact maintenance personnel.

KDAN22013-W

Unable to destroy service aa....aa.

aa....aa: Service name

Description

This message is displayed when the specified service does not exist.

Action

Confirm that the service exists and has been stopped.

KDAN22014-W

Deleted file with non-numeric file name: aa....aa.

Description

This message is displayed when the user attempts to delete a non-existent file.

Action

Do not delete a non-existent file.

KDAN22015-W

Unable to read data file: aa....aa.

aa....aa: File name

Description

This message is displayed when the specified file does not exist in the directory.

Action

Contact maintenance personnel.

KDAN22018-W

A client attempted to add an invalid client ID aa....aa on connection bb....bb.

aa....aa: Client ID

bb....bb: Connection

Description

This message is displayed when the specified client ID is as follows:

Either a CJMS reserved name, null, or null string

When the beginning of the client ID is the string ${u:}

When the beginning of the client ID is the string ${%%}

Action

Make sure that the CJMS reserved name, null, null string, and a name beginning with ${u:} or ${%%} characters is not specified for the client ID.

KDAN22019-W

Admin Operation Failed:

Description

This message is displayed when the destination name specified for purging the destination is invalid.

This message is displayed when an error occurs during the purging of the destination.

Action

Specify a valid destination name existing in CJMSP.

KDAN22020-W

Service aa....aa[bb....bb] access denied.

aa....aa: Service name

bb....bb: Service type

Description

This message is displayed when the specified access management information is invalid.

Action

Specify a valid access management information.

KDAN22021-W

aa....aa on bb....bb destination cc....cc denied - dd....dd.

aa....aa: Operation

bb....bb: Destination type (such as queue, topic)

cc....cc: Destination name

dd....dd: Exception message

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN22022-W

aa....aa bb....bb destination cc....cc denied - dd....dd.

aa....aa: Operation

bb....bb: Destination type (such as queue, topic)

cc....cc: Destination name

dd....dd: Exception message

Description

This message is displayed when CJMSP is not running.

Action

Start CJMSP.

KDAN22023-W

Unable to cleanup all data in thread pool aa....aa within the destroy time of bb....bb, data may be corrupted.

aa....aa: Thread instance

bb....bb: Timeout value

Description

This message is displayed when the specified service is running and the data cannot be cleaned up because of an internal error.

Action

Contact maintenance personnel.

KDAN22024-W

Unable to update service aa....aa

aa....aa: Service name

Description

This message is displayed when the specified service does not exist.

Action

Contact maintenance personnel.

KDAN22025-W

Administration service received a forbidden operation on a restricted connection. Operation=aa....aa.

aa....aa: Operation

Description

This message is displayed when the specified user is not an administrator.

Action

Only the administrator can connect to CJMSP.

KDAN22026-W

Removing aa....aa:state[bb....bb]. Timeout in reaching state cc....cc within dd....dd seconds.

aa....aa: Connection

bb....bb: Current state

cc....cc: Requested state

dd....dd: Standby interval (seconds)

Description

This message is displayed when the connection to CJMSP is terminated.

Action

Establish a new connection with CJMSP.

KDAN22027-W

Client protocol level aa....aa was not at the supported level of bb....bb.

Broker is closing the connection to allow the client to reconnect at a supported level.

aa....aa: Incompatible protocol level

bb....bb: Protocol level requested by the Broker

Description

This message is displayed when the requested client protocol is not supported in CJMSP.

This message is displayed when the specified protocol is not running.

Action

Start the specified protocol.

For details, contact maintenance personnel.

KDAN22028-W

Could not configure MetricManager because a property was set to an invalid value

Description

This message is displayed when the metrics interval property of metrics is not set up.

This message is displayed when an invalid value is set up for the metrics interval property of metrics.

Action

Set up a valid value for the metrics interval property.

KDAN22032-W

Data on connection aa....aa is corrupted, closing connection.

aa....aa: Connection

Description

This message is displayed when the data for the specified connection is corrupted. The connection is terminated.

Action

Confirm that the network connection is stable and secure.

KDAN22033-W

Could not register diagnostic class

Description

This message is displayed when an invalid class is specified when acquiring the diagnosis information of the class.

Action

Specify a class containing a complete package name in the config.properties file.

KDAN22034-W

Property [aa....aa] has whitespace at the end of the property [bb....bb], removing extra whitespace and re-storing.

aa....aa: Property name

bb....bb: Property value

Description

Extra whitespace is specified in the properties file. This extra whitespace is removed.

Action

No action is required.

KDAN22035-W

Got exception while loading configuration change records, aa....aa records loaded, file truncated at bb....bb.

aa....aa: Record size

bb....bb: Position

Description

This message is displayed when the config record file is corrupted. The config record file manages all the configuration-related change log.

Action

Restart CJMSP (a new config record file is created). However, the past data is lost.

KDAN22036-W

Found incomplete record at the end of the file [aa....aa], file truncated at bb....bb.

aa....aa: Record size

bb....bb: Position

Description

This message is displayed when the config record file is corrupted. The config record file manages all the configuration-related change log.

Action

Restart CJMSP (a new config record file is created). However, the past data is lost.

KDAN22037-W

Broker ran out of memory before the passed in VM maximum (-Xmx) bb....bb b, lowering max to currently allocated memory (aa....aa b ) and trying to recover

aa....aa: Memory size

bb....bb: Memory size

Description

This message is displayed when the JVM memory is insufficient for starting or executing CJMSP. If an error occurs when starting CJMSP, CJMSP is stopped.

Action

If this warning message appears several times, increase the JVM memory size.

KDAN22038-W

Broker is rejecting new producers, because it is extremely low on memory

Description

This message is displayed if there is a memory shortage when CJMSP creates producers for the general users.

Action

If this warning message appears several times, restart CJMSP or increase the JVM memory size.

KDAN22039-W

Broker is rejecting the creations of destinations, because it is extremely low on memory

Description

This message is displayed if there is a memory shortage when CJMSP creates destinations.

Action

If this warning message appears several times, restart CJMSP or increase the JVM memory size.

KDAN22040-W

Browsing of Queue aa....aa failed, destination unknown

aa....aa: Queue name

Description

This message is displayed when the destination specified for browsing does not exist in CJMSP. (When dynamic destination is used for browsing).

Action

Specify a destination that exists in CJMSP.

KDAN22041-W

Destroying destination aa....aa with bb....bb active producers. Reason: cc....cc.

aa....aa: Destination name

bb....bb: Active producers

cc....cc: String containing detailed information

Description

This message is displayed when the administrator destroys an active destination with producers. The destination is destroyed.

Action

When destroying a destination, confirm that the producer is terminated.

KDAN22042-W

Destroying destination aa....aa with bb....bb active consumers. Consumers will no longer receive messages. Reason: cc....cc.

aa....aa: Destination name

bb....bb: Active consumers

cc....cc: String containing detailed information

Description

This message is displayed when the administrator destroys an active destination with consumers. The destination is destroyed.

Action

When destroying a destination, confirm that the consumer is terminated.

KDAN22043-W

Unable to create destination aa....aa, autocreation is forbidden.

aa....aa: Destination name

Description

This message is displayed when the autocreate functionality is disabled.

Action

Contact maintenance personnel for internal errors.

KDAN22045-W

Loading Destination aa....aa failed. Messages stored on that destination will not be available.

aa....aa: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN22048-W

Unable to load message aa....aa from destination bb....bb because cc....cc

aa....aa: Message ID

bb....bb: Destination UID

cc....cc: Exception information

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN22049-W

Unable to move message aa....aa to the Dead Message Queue.

aa....aa: Message

Description

This message is displayed when the Broker is not executed.

Action

Confirm that the Broker is running.

KDAN22050-W

Attempt to repair corrupted destination for aa....aa failed, throwing out.

aa....aa: Destination name

Description

An internal error occurred.

Action

Contact maintenance personnel for internal errors.

KDAN22051-W

Destination aa....aa cannot be loaded, it has been recreated using default configuration values

aa....aa: Destination name

Description

This message is displayed when the destination-related files are corrupted and cannot be loaded when starting CJMSP.

Action

Confirm that the files in the file store are not corrupted.

KDAN22052-W

Destination aa....aa could not be loaded or regenerated

aa....aa: Destination string value

Description

This message is displayed when the destination-related files are corrupted and the destination cannot be re-created when starting CJMSP.

Action

Confirm that the files in the file store are not corrupted.

KDAN22053-W

Attempt to repair corrupted consumer for aa....aa failed, throwing out.

aa....aa: Consumer UID value

Description

This message is displayed when the consumer-related files are corrupted and cannot be restored by the consumer.

Action

Confirm that the files in the file store are not corrupted.

KDAN22054-W

Consumer aa....aa is corrupted and cannot be repaired, discarding.

aa....aa: Consumer UID string value

Description

This message is displayed when the consumer-related files are corrupted and cannot be restored. The consumer will be excluded.

Action

Confirm that the files in the file store are not corrupted.

KDAN22055-W

Unable to load transaction information.

Description

This message is displayed when the transaction-related files are corrupted and cannot be re-created when starting CJMSP.

Action

Confirm that the files in the file store are not corrupted.

KDAN22056-W

Transaction State Information for aa....aa corrupted, setting to PREPARED.

aa....aa: Transaction ID

Description

This message is displayed when the transaction-related files are corrupted and cannot be re-created when starting CJMSP.

Action

Confirm that the files in the file store are not corrupted.

KDAN22057-W

Transaction ID for Transaction State aa....aa is corrupted, discarding

aa....aa: Transaction ID

Description

This message is displayed when the transaction-related files are corrupted and cannot be re-created when starting CJMSP.

Action

Confirm that the files in the file store are not corrupted.

KDAN22058-W

Transaction Acknowledge Information for aa....aa corrupted, discarding

aa....aa: Transaction ID

Description

This message is displayed when the transaction-related files are corrupted and cannot be re-created when starting CJMSP.

Action

Confirm that the files in the file store are not corrupted.

KDAN22059-W

Warning clock synchronization problem detected, the system time of the client on connection aa....aa is at least bb....bb seconds faster than the system time of the broker. A message may live longer than its ttl.

aa....aa: Connection ID

bb....bb: Value of imq.clock.skew.interval

Description

This message is displayed when there is a synchronization problem between the system time of the client and the system time of CJMSP.

Action

Synchronize the system time of the client and CJMSP.

KDAN22060-W

Warning possible clock synchronization problem detected. The broker received a message more than bb....bb after it was sent from the client on connection aa....aa. Check system clocks on both systems to ensure that a message expires only after its ttl elapses.

aa....aa: Connection ID

bb....bb: Number of messages

Description

This message is displayed when there is a synchronization problem between the system time of the client and the system time of CJMSP.

Action

Synchronize the system time of the client and CJMSP.

KDAN22061-W

Warning possible clock synchronization problem detected. Messages from connection aa....aa are arriving close to their expiration times. Check system clocks on both systems to

ensure that clock skew does not affect message expiration.

aa....aa: Connection ID

Description

This message is displayed when there is a synchronization problem between the system time of the client and the system time of CJMSP.

Action

Synchronize the system time of the client and CJMSP.

KDAN22062-W

Creation of consumer aa....aa from connection bb....bb on the auto-created destination cc....cc failed.

aa....aa: Consumer ID

bb....bb: Connection object

cc....cc: Destination

Description

This message is displayed when an attempt is made to auto-create a destination during the creation of a consumer since the destination does not exist in CJMSP.

Action

No action is required.

KDAN22098-W

Destroying unresponsive connection aa....aa, connection has not responded for bb....bb seconds.

aa....aa: Connection ID

bb....bb: Time interval

Description

This message is displayed when the connection does not respond for more than the ping time interval.

Action

Contact maintenance personnel for internal errors.

KDAN22104-W

Removing aa....aa messages associated with destination bb....bb.

aa....aa: Message size at the destination

bb....bb: Destination name

Description

This message is displayed when an attempt is made to remove a destination containing messages. The messages and destination are destroyed.

Action

Before removing a destination, make sure that the message is received.

KDAN22166-W

HALTING BROKER BECAUSE OF aa....aa

aa....aa: Cause of the termination of the Broker

Description

This message is displayed when the instance does not exist during the deletion of the instance.

Action

Confirm that the instance exists.

KDAN22173-W

Received acknowledgement to a message aa....aa that has been removed.

aa....aa: Session object

Description

This message is displayed when an ACK message is sent to the Broker after the expiry of the message.

Action

Contact maintenance personnel for internal errors.

KDAN22175-W

possible loss of destination data.

Description

This message is displayed when the data is corrupted during the loading of the backing file.

Action

Contact maintenance personnel for internal errors.

KDAN22176-W

possible loss of destination data in old store.

Description

This message is displayed when the data is corrupted during the loading of the backing file.

Action

Contact maintenance personnel for internal errors.

KDAN22177-W

possible data loss for aa....aa.

aa....aa: Destination UID

Description

This message is displayed when the data is corrupted during the loading of the backing file.

Action

Contact maintenance personnel for internal errors.

KDAN22178-W

possible loss of consumer data.

Description

This message is displayed when the data is corrupted during the loading of the backing file.

Action

Contact maintenance personnel for internal errors.

KDAN22179-W

possible loss of consumer data in old store.

Description

This message is displayed when the data is corrupted during the loading of the backing file.

Action

Contact maintenance personnel for internal errors.

KDAN22180-W

Internal Error: Problem cleaning consumer aa....aa.

aa....aa: Consumer object

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22181-W

Internal Error: Problem purging consumer aa....aa.

aa....aa: Consumer object

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22182-W

Update consumer aa....aa state failed for message bb....bb:cc....cc.

aa....aa: Consumer UID

bb....bb: System message ID

cc....cc: Exception message

Description

This message is displayed when the message does not exist in the store.

This message is displayed when the consumer is not linked to the message.

Action

Confirm that the message exists in the store.

KDAN22185-W

Unknown type for verbose aa....aa

aa....aa: Class of the object

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22186-W

Unknown type for preserve undelivered aa....aa.

aa....aa: Class of the object

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22187-W

Unable to update destination aa....aa.

aa....aa: Destination name

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22188-W

Admin: Could not extract properties from pkt.

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22189-W

Message received on administration destination aa....aa has no bb....bb property ignoring it

aa....aa: JMQ message type

bb....bb: JMQ message type

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22190-W

Cannot determine type of ReplyTo destination. There is a topic and queue with the name: aa....aa

aa....aa: Destination name for ReplyTo

Description

This message is displayed when the ReplyTo destination does not exist.

Action

Confirm that the ReplyTo destination exists.

KDAN22191-W

Caught exception while determining ReplyTo destination type.

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22192-W

sending back broker data.

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22194-W

Internal Error: received HELLO on already authenticated connection aa....aa bb....bb.

aa....aa: Remote connection

bb....bb: ConnectionUID

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22195-W

Internal Error: received HELLO on already started connection aa....aa bb....bb.

aa....aa: Remote connection

bb....bb: ConnectionUID

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22196-W

Internal Error: Received session on non-clustered broker.

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22197-W

Internal error: received goodbye on unauthenticated connection aa....aa bb....bb.

aa....aa: Connection UID

bb....bb: Remote connection

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22202-W

possible loss of persisted properties.

Description

VRFile might be corrupted.

Action

Contact maintenance personnel for internal errors.

KDAN22203-W

possible loss of persisted properties in old store.

Description

This message is displayed when the data is corrupted during the loading of the backing file.

Action

Contact maintenance personnel for internal errors.

KDAN22216-W

Timeout in waiting for runnable threads release in aa....aa.

aa....aa: IMQIPConnection

Description

This message is displayed when the value of the specified timeout interval is a negative value.

Action

Make sure that the timeout interval value is a positive value.

KDAN22217-W

Property aa....aa is defaulted to : bb....bb. Since the value ''cc....cc'' is invalid.

aa....aa: Property name

bb....bb: Default value

cc....cc: Specified value

Description

This message is displayed when the default value is used since the specified property value is invalid.

Action

Confirm that the property value is valid.

If an invalid property value is specified, specify a valid property value.

KDAN22219-W

aa....aa: found a corrupted message at vrecord(bb....bb), a message might be lost.

aa....aa: Destination name

bb....bb: VRecordRAF

Description

Vrecord might be corrupted.

Action

Contact maintenance personnel for internal errors.

KDAN22220-W

Could not update buffers: aa....aa.

aa....aa: Exception

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel for internal errors.

KDAN22231-W

Invalid value for property aa....aa: bb....bb.

aa....aa: Count property name

bb....bb: Count string

Description

This message is displayed when the specified property value is invalid.

Action

Confirm that the property value is valid.

If an invalid property value is specified, specify a valid property value.

KDAN22233-W

Unknown properties aa....aa is configured in bb....bb

aa....aa: Property key

bb....bb: Value set by the -D option in config.properties or commomconfig.properties or admin.properties or properties

Description

This message is displayed when a private or invalid property name is described in the property file.

Action

The Broker and command can be executed normally, but when this message is not required, delete the aa....aa property from the bb....bb file.

KDAN23501-W

Invalid number format: Property: aa....aa, Value=bb....bb.

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

bb....bb: Invalid value

Description

This message is displayed when an invalid value is specified instead of an integer in the config.properties file.

Action

Specify a valid integer value in the config.properties file.

KDAN23504-W

An error occurred configuring the logging system: aa....aa.

aa....aa: Detailed information for the errors occurring during the configuration of the logging system

Description

This message is displayed when an invalid logger configuration is included in the properties file. This warning is issued by one of the following warning IDs:

KDAN22056-W, KDAN22057-W, or KDAN22058-W

This message is displayed when an IO error occurs during the configuration of the file log.

This message is displayed when an invalid log level is specified in the properties file.

Action

Specify the appropriate configuration information in the properties file. Check the action related to the following IDs:

KDAN22195-W, KDAN22196-W, and KDAN22197-W

Confirm that the log file has the appropriate access permissions.

Specify a valid log level.

KDAN23505-W

Log output channel aa....aa is disabled: bb....bb.

aa....aa: Log handler configuration

bb....bb: UnsatisfiedLinkError message

Description

This message is displayed when the output channel of the log handler is disabled.

Action

Contact maintenance personnel for internal errors.

KDAN23506-W

Unable to set UncaughtExceptionHandler for aa....aa.

aa....aa: Class name

Description

The thread is suddenly terminated by an uncaught exception and the uncaught exception handler is invoked. However, the current thread cannot make changes for the suddenly terminated thread. This warning is issued when UncaughtExceptionHandler is set up for the object.

Action

Contact maintenance personnel for internal errors.

KDAN23507-W

Unable to schedule UncaughtExceptionHandler TimerTask: aa....aa.

aa....aa: Exception message

Description

When the UncaughtExceptionHandler TimerTask task was scheduled so that the task could be executed at a specific time, this message is displayed in the following cases:

The task has already been scheduled

The task has already been cancelled

The timer was cancelled

The timer thread was terminated

Action

Make sure that the specified task has not been scheduled already.

Make sure that the specified task has not been cancelled.

Make sure that the timer has not been cancelled.

KDAN24001-I

"Usage: cjmsbroker

[-force]

[-h | -help]

[-name <name>]

[-remove instance]

[-reset <data>]

[-vmargs <vmarguments>]

[-varhome <location>]

-force Perform action without user confirmation.

-h displays usage information.

-name Set the instance name of this Broker to <name> and use the

corresponding property configuration.

-remove instance

Cause the broker instance to be removed.

Delete the persistent store and 'etc' directory.

The configuration and log files are not removed.

-reset Reset or clear dynamically created broker data.

Currently the following arguments are supported by the

reset option.

'store' - causes the broker to clear all persistent

data including all messages and related data

as well as durable subscribers and transaction

information.

'messages' - causes the broker to clear all persistent

messages.

'durables' - causes the broker to clear all durable

subscribers.

-vmargs Pass <vmarguments> to the Java VM. If <vmarguments> contains

spaces or more than one argument, it should be enclosed in double quotes.

-varhome Specify an alternate var home to use."

Description

This message shows the usage of cjmsbroker help.

KDAN24009-I

Broker exiting.

Description

This message is displayed when the Broker is shutting down.

KDAN24011-I

unlimited

Description

This message is displayed when an infinite value is set up in the property.

KDAN24024-Q

All data for the broker instance ""aa....aa"" will be removed.

Do you wish to proceed? [y/ n]

aa....aa: Config name

Description

This message is displayed when an attempt is made to remove a Broker instance.

KDAN24044-I

aa....aa [bb....bb]

aa....aa: Destination name

bb....bb: Destination type

Description

This message displays the destination name and type when destroying a destination.

KDAN24051-I

Message Placed on the Dead Message Queue because aa....aa

aa....aa: Reason for entering a message in the dead message queue

Description

This message is displayed when a message has expired.

KDAN24052-I

Message on destination aa....aa Expired: expiration time bb....bb, arrival time cc....cc, JMSTimestamp dd....dd

aa....aa: Destination name

bb....bb: Expiration time

cc....cc: Arrival time

dd....dd: JMSTimestamp

Description

This message is displayed when a message has expired.

KDAN24053-I

Limit exceeded on Destination aa....aa: message limit (maxNumMsgs)=bb....bb; bytes limit (maxTotalMsgBytes)=cc....cc.

aa....aa: Destination name

bb....bb: Maximum number of messages

cc....cc: Maximum number of bytes for total messages

Description

This message is displayed when the specified maximum number of messages is reached.

The message is displayed when the specified maximum number of bytes for total messages is reached.

KDAN24054-I

Message on destination aa....aa was Undeliverable.

aa....aa: Destination name

Description

This message is displayed when a message is entered in the dead message queue.

KDAN24055-I

Error was received processing the message on destination aa....aa.

aa....aa: Destination name

Description

This message is displayed when a message is entered in the dead message queue.

KDAN24058-I

Client closed the connection.

Description

This message is displayed when the client closes the connection.

KDAN24059-I

Service shutting down

Description

This message is displayed when a service terminates.

KDAN24060-I

Client exited without closing connections.

Description

This message is displayed when a client is terminated without closing the connections.

KDAN24061-I

Admin requested close

Description

This message is displayed when the client closes the connection.

KDAN24062-I

Initialization Failure

Description

This message is displayed when the client closes the connection.

KDAN24063-I

Authorization Failure

Description

This message is displayed when the client closes the connection.

KDAN24064-I

Message on destination aa....aa expired before arrival: expiration time bb....bb, arrival time cc....cc, JMSTimestamp dd....dd.

aa....aa: Destination name

bb....bb: Expiration time

cc....cc: Arrival time

dd....dd: JMSTimestamp

Description

This message is displayed when a message has expired.

KDAN24065-I

at Admin Request

Description

This message is displayed when destination is deleted.

KDAN24066-I

at Request of Connection aa....aa

aa....aa: Connection

Description

This message is displayed when destination is deleted.

KDAN24067-I

at Close of Connection aa....aa

aa....aa: Connection

Description

This message is displayed when a temporary destination is cleaned up.

KDAN24068-I

Autocreated destination reaped

Description

This message is displayed when the specified reap time is exceeded.

KDAN24069-I

Reconnect interval expired for destination

Description

This message is displayed when a temporary destination is deleted.

KDAN24070-I

at request of remote administrator

Description

This message is displayed when the destination is deleted by the administrator of the remote Broker.

KDAN24075-I

Admin requested shutdown by aa....aa.

aa....aa: Shutdown requester

Description

This message is displayed when a Broker is shutting down.

KDAN24081-I

Portmapper exiting.

Description

This message is displayed when portmapper is terminating.

KDAN24082-I

Accepted connection from aa....aa. Connection count=bb....bb.

aa....aa: Connection information

bb....bb: Connections

Description

This message is displayed when a new connection is created.

KDAN24083-I

Using aa....aa as the location for CJMSP_HOME.

aa....aa: Connection information

Description

This message is displayed when a Broker is configured at the specified CJMSP_HOME location.

KDAN24086-I

Starting the aa....aa service using bb....bb with min threads cc....cc and max threads of dd....dd.

aa....aa: Service name

bb....bb: Service protocol (example: tcp, http)

cc....cc: Numeric value

dd....dd: Numeric value

Description

This message is displayed when a service is starting.

KDAN24087-I

Pausing Service aa....aa with protocol bb....bb.

aa....aa: Service name

bb....bb: Service protocol (example: tcp, http)

Description

This message is displayed when a service is paused.

KDAN24088-I

Resuming Service aa....aa with protocol bb....bb.

aa....aa: Service name

bb....bb: Service protocol (example: tcp, http)

Description

This message is displayed when a service is restarting.

KDAN24089-I

Stopping Service aa....aa with protocol bb....bb.

aa....aa: Service name

bb....bb: Service protocol (example: tcp, http)

Description

This message is displayed when a service is stopping.

KDAN24090-I

Removing Connection aa....aa, connection count = bb....bb.

aa....aa: Connection ID

bb....bb: Service protocol (example: tcp, http)

Description

This message is displayed when a connection is removed.

KDAN24096-I

Auto Creation of Topics is disabled.

Description

This message is displayed when the auto-creation of topics is disabled.

KDAN24116-I

Destination aa....aa is being purged using a criteria of bb....bb.

aa....aa: Numeric value

bb....bb: Conditions used for purging a message from a destination

Description

This message is displayed when a destination is purged using the specified conditions.

KDAN24117-I

Delete all messages in the destination.

Description

This message is displayed when a destination is purged using the specified conditions.

KDAN24121-I

Broker "aa....aa" ready.

aa....aa: Broker name and host name and port number

Description

This message is displayed when the Broker has started.

KDAN24129-I

Shutting down broker...

Description

This message is displayed when the Broker is shutting down.

KDAN24130-I

Shutdown of broker complete.

Description

This message is displayed when the Broker is shutting down.

KDAN24131-I

Shutdown hook added.

Description

This message is displayed when exiting from a virtual machine.

KDAN24132-I

Shutdown hook NOT added. Running JDK1.2?

Description

This message is displayed when the Broker is executed for JDK1.2.

KDAN24135-I

Shutting down Service aa....aa with protocol bb....bb.

aa....aa: Shut down database url

bb....bb: Protocol

Description

This message is displayed when the Broker is shutting down.

KDAN24141-I

Resetting persistent store...

Description

This message is displayed when a persistence store is reset.

KDAN24142-I

Loading persistent data...

Description

This message is displayed when a persistence store is loaded.

KDAN24147-I

Accepting: aa....aa->bb....bb. Count: service=cc....cc broker=dd....dd.

aa....aa: Connection type and host name

bb....bb: Information about the service to be connected

cc....cc: Services

dd....dd: Connection count of the Broker

Description

This message is displayed when establishing a connection.

KDAN24148-I

Closing: aa....aa->bb....bb because "cc....cc". Count: service=dd....dd broker=ee....ee

aa....aa: Connection information

bb....bb: Information about the service to be connected

cc....cc: Reason

dd....dd: Services

ee....ee: Connection count

Description

This message is displayed when closing a connection.

KDAN24159-I

Broadcast good-bye to all connections ...

Description

This message is displayed when the Broker is shutting down.

KDAN24160-I

Flushing good-bye messages ...

Description

This message is displayed when the Broker is shutting down.

KDAN24161-I

Found aa....aa transactions. bb....bb will be rolled back.

aa....aa: Transactions

bb....bb: Transaction number

Description

This message is displayed when the Broker is starting.

KDAN24162-I

Of aa....aa transactions, bb....bb are in PREPARED state, cc....cc are in COMMITTED state.

aa....aa: Transactions

bb....bb: Transaction number

cc....cc: Transaction in a committed state

Description

This message is displayed when the transaction-related information is written to a file when the Broker starts.

KDAN24165-I

Resetting all messages...

Description

This message is displayed when all the persistence messages are cleared from the Broker.

KDAN24166-I

Resetting all durable subscribers...

Description

This message is displayed when all the persistence subscribers are cleared from the Broker.

KDAN24167-I

Loading other persistent data...

Description

This message is displayed when the Broker loads the persistence data related to the persistence messages, persistence subscribers, and transaction information.

KDAN24171-I

In low memory condition, Broker is attempting to free up resources.

Description

This message is displayed when the persistence messages are cleaned up in low memory conditions.

KDAN24177-I

Removing persistent store...

Description

This message is displayed when the Broker clears all the persistence data related to messages, persistence subscribers, and transaction information.

KDAN24178-I

Removing all instance data...

Description

This message is displayed when the Broker instance is removed.

KDAN24179-I

Instance data not removed.

Description

This message is displayed when the Broker instance is not removed.

KDAN24204-I

Reconnecting client aa....aa.

aa....aa: Connection ID

Description

This message is displayed when reconnecting to an old connection.

KDAN24205-I

Compacting aa....aa

aa....aa: Destination

Description

This message is displayed when the destination is compressed.

KDAN24206-I

Pausing Service aa....aa

aa....aa: Service

Description

This message is displayed when a service is paused.

KDAN24207-I

Pausing Destination aa....aa.

aa....aa: Destination

Description

This message is displayed when a destination is paused.

KDAN24210-I

Resuming Service aa....aa.

aa....aa: Destination

Description

This message is displayed when a service is restarted.

KDAN24211-I

Resuming Destination aa....aa.

aa....aa: Destination

Description

This message is displayed when a destination is restarted.

KDAN24213-I

Removed all Durable Consumers associated with Destination aa....aa. Reason: bb....bb.

aa....aa: Destination

bb....bb: Reason for removing the durable consumers associated with the destination

Description

This message is displayed when an internal error occurs.

KDAN24216-I

In-conflict clientID aa....aa is owned by local connection bb....bb.

aa....aa: Client ID

bb....bb: Connection ID

Description

This message is displayed when a client ID is created and required by a local connection.

KDAN24222-I

Expired aa....aa messages from destination bb....bb

aa....aa: Messages

bb....bb: Destination name

Description

This message is displayed when a message has expired.

KDAN24223-I

Using built-in file-based persistent store: aa....aa

aa....aa: Root directory of the persistence store

Description

This message displays a file-based persistence store when starting the Broker.

KDAN24225-I

No valid license files found. The default license (platform edition) will be used. To use the platform edition in the absence of valid license start the broker with pe option along with the license subcommand while starting the broker.

Description

This message is displayed when the dead message queue is generated while starting the Broker.

KDAN24226-I

Creating Dead Message Queue

Description

This message is displayed when the dead message queue is created.

KDAN24227-I

Message aa....aa has been removed from the Dead Message Queue (original destination was bb....bb).

aa....aa: Message ID

bb....bb: Destination name

Description

This message is displayed when an internal Broker error occurred.

KDAN24228-I

Message aa....aa has been removed from destination bb....bb because cc....cc

aa....aa: Message ID

bb....bb: Destination name

cc....cc: Reason for removing the messages from the destination

Description

This message is displayed when the message has expired.

KDAN24229-I

Message aa....aa from destination bb....bb has been placed on the DMQ because cc....cc

aa....aa: Message ID

bb....bb: Destination name

cc....cc: Reason for inserting the message in the DMQ

Description

This message is displayed when the message has expired.

KDAN24233-I

Loading destination aa....aa with bb....bb messages

aa....aa: Destination name

bb....bb: Message ID

Description

This message is displayed when a destination is loaded.

KDAN24234-I

Loading of destination aa....aa complete.

aa....aa: Destination name

Description

This message is displayed when the loading of the destination is complete.

KDAN24235-I

Loading of destination aa....aa in process, bb....bb of cc....cc messages loaded, dd....dd% complete.

aa....aa: Destination name

bb....bb: Currently loaded messages

cc....cc: Total messages to be loaded

dd....dd: Total messages loaded (%)

Description

This message is displayed when a destination is loaded.

KDAN24240-I

Administrator has created destination aa....aa.

aa....aa: Destination name

Description

This message is displayed when the destination type is Admin.

KDAN24241-I

Destination aa....aa has been destroyed.

aa....aa: Destination name

Description

This message is displayed when the specified destination is destroyed.

KDAN24242-I

Connection aa....aa has created destination bb....bb.

aa....aa: Connection ID

bb....bb: Destination name

Description

This message is displayed when a temporary destination is created.

KDAN24243-I

Initialization of instance has completed, exiting

Description

This message is displayed when the initialization flag is True.

KDAN24277-I

Unable to load monitor for destination aa....aa

aa....aa: Destination name

Description

This message is displayed when the destination watch functionality is not supported.

KDAN24278-I

Processing bb....bb messages on destination aa....aa.

aa....aa: Destination name

bb....bb: Messages

Description

This message is displayed when a takeover message is loaded.

KDAN24281-I

Shutdown Requested by aa....aa

aa....aa: User

Description

This message is displayed when the Broker is shutting down.

KDAN24282-I

Shutting down the broker in aa....aa seconds (bb....bb milliseconds)

aa....aa: Remaining time (seconds)

bb....bb: Remaining time (milliseconds)

Description

This message is displayed when the Broker is shutting down.

KDAN24283-I

Waiting to complete shutdown, broker will shutdown at aa....aa.

aa....aa: Remaining time (seconds)

Description

This message is displayed when the Broker is shutting down.

KDAN24334-I

Pausing all services

Description

This message is displayed when a Broker is paused.

KDAN24335-I

Resuming all services

Description

This message is displayed when a Broker is restarted.

KDAN24342-I

Transaction acknowledgement could not be processed because consumer aa....aa not exist.

aa....aa: Consumer uid

Description

This message is displayed when the consumer does not exist in the store.

KDAN24354-I

Found transaction ID aa....aa [transaction log record type bb....bb].

aa....aa: Transaction ID

bb....bb: Log record type

Description

This message is displayed if the transaction ID exists during the initialization of the transaction class.

KDAN24355-I

Committing transaction ID aa....aa.

aa....aa: Transaction ID

Description

This message is displayed when a transaction needs to be committed.

KDAN24356-I

Load aa....aa records from message transaction log file

aa....aa: Records

Description

This message is displayed when the records from the message transaction log file are loaded.

KDAN24357-I

Load aa....aa records from acknowledgement transaction log file

aa....aa: Records

Description

This message is displayed when the records from the administration transaction log file are loaded.

KDAN24358-I

Replace existing message aa....aa.

aa....aa: Message ID

Description

This message is displayed when the message already exists in the store.

KDAN24359-I

Reconstruct message aa....aa

aa....aa: Message ID

Description

This message is displayed when the message does not exist in the store.

KDAN24360-I

Update state of consumer aa....aa for message bb....bb.

aa....aa: Consumer state

bb....bb: Message ID

Description

This message is displayed when the consumer state is updated for the relevant message.

KDAN24361-I

Disregard state of consumer aa....aa for already purged message bb....bb.

aa....aa: Consumer state

bb....bb: Message ID

Description

This message is displayed when the message does not exist in the store.

KDAN24362-I

Reconstructing persistence store from transaction log files done.

Description

This message is displayed when the transaction log is reset after updating the store.

KDAN24367-I

Committed transaction reaper thread has started (limit aa....aa, interval bb....bbsec).

aa....aa: Transaction reap limit

bb....bb: Repeat interval

Description

This message is displayed when the applications running on the J2EE server use transactions.

KDAN24368-I

Committed transaction reaper thread is exiting.

Description

This message is displayed when the applications running on the J2EE server use transactions.

KDAN24372-I

Transaction acknowledgement could not be processed because message aa....aa reference is gone .

aa....aa: Message ID

Description

This message is displayed when there is no packet reference during transaction acknowledgement.

KDAN24381-I

Embedded Broker

Description

This message is displayed when the inprocess flag is True.

KDAN24384-I

Unable to load destination aa....aa because of not found in store: bb....bb.

aa....aa: Destination name

bb....bb: Store

Description

This message is displayed when the specified destination does not exist during the loading of the destination.

KDAN24385-I

Unable to remove all messages in destination aa....aa because the destination is not found in store: bb....bb.

aa....aa: Destination name

bb....bb: Store

Description

This message is displayed when the specified destination does not exist during the remove of the messages.

KDAN24386-I

Unable to remove destination aa....aa from store because of not found in store: bb....bb.

aa....aa: Destination name

bb....bb: Store

Description

This message is displayed when the specified destination does not exist during the remove of the destination.

KDAN24394-I

PortMapper: accepted client connection ( aa....aa ) that is no longer connected. Ignoring.

aa....aa: Socket

Description

This message is displayed when the connection is closed.

KDAN24396-I

Throwing out packet, could not find old consumer ID for new ID aa....aa.

aa....aa: New consumer ID

Description

This message is displayed when the consumer does not exist in the store.

KDAN24398-I

Sessions (size) : aa....aa

aa....aa: Number

Description

This message displays the session information when dumping the connection information.

KDAN24399-I

Sessions (list) : aa....aa

aa....aa: Session list

Description

This message displays the session information when dumping the connection information.

KDAN24400-I

Busy (size) : aa....aa

aa....aa: Busy session size

Description

This message displays the session information when dumping the connection information.

KDAN24401-I

Busy (list) : aa....aa

aa....aa: Busy session

Description

This message displays the session information when dumping the connection information.

KDAN24402-I

Cleanup connection aa....aa: cleaning up transaction bb....bb cc....cc.

aa....aa: Connection uid

bb....bb: Transaction uid

cc....cc: Transaction state

Description

This message is displayed when the transaction is cleaned up using a connection.

KDAN24403-I

Unable to destroy temp destination aa....aa.

aa....aa: Destination uid

Description

This message is displayed when the temporary destination of a connection is destroyed.

KDAN24404-I

Could not retrieve local address.

Description

This message is displayed when the host IP address is not found.

KDAN24409-I

Waiting for runnable threads release in aa....aa.

aa....aa: IMQIP connection object

Description

This message is displayed when the system is in standby state for releasing connections.

KDAN24411-I

Connection Information [aa....aa]bb....bb.

aa....aa: IMQIP connection object

bb....bb: String

Description

This message is displayed when the connection information is dumped.

KDAN24417-I

Session: Pausing aa....aa[bb....bb]cc....cc.

aa....aa: Session object

bb....bb: Number

cc....cc: String

Description

This message is displayed when the destination corresponding to the session is paused.

KDAN24418-I

Session: Resuming aa....aa[bb....bb]cc....cc

aa....aa: Session object

bb....bb: Number

cc....cc: String

Description

This message is displayed when the destination corresponding to the session is restarted.

KDAN24421-I

Dumping active sessions

Description

This message is displayed when the active sessions are dumped.

KDAN24423-I

Loading stored durable aa....aa:bb....bb.

aa....aa: Client ID

bb....bb: Durable subscriber name

Description

This message is displayed when the durable subscriber from the store is loaded.

KDAN24426-I

Received unknown message for transaction aa....aa on session bb....bb ack info is cc....cc,dd....dd:

aa....aa: Transaction uid

bb....bb: Session uid

cc....cc: Consumer uid

dd....dd: sysMessageID

Description

This message is displayed when acknowledgements that are not pending are received for the delivered messages.

KDAN24427-I

Broker does not know about the message

Description

This message is displayed when the message does not exist in the store.

KDAN24428-I

Broker knows about the message, not associated with the session.

Description

This message is displayed when the message exists in the store and that message corresponds to the current session.

KDAN24432-I

Syncing message store: aa....aa

aa....aa: Boolean value

Description

This message is displayed when the message store is synchronized.

KDAN24433-I

Producer flow control is turned off

Description

This message is displayed when the value of the imq.noProducerFlow property is True.

KDAN24438-I

Ref null for aa....aa

aa....aa: sysMessageID

Description

This message is displayed when the reference packet is null.

KDAN24445-I

Loaded Message aa....aa into destination bb....bb

aa....aa: Packet

bb....bb: Destination object

Description

This message is displayed when the message is loaded into the destination.

KDAN24446-I

Message aa....aa[bb....bb] has been acked, destory..

aa....aa: sysMessageID

bb....bb: Destination object

Description

This message is displayed when the message is acknowledged.

KDAN24447-I

Message aa....aa [TUID=bb....bb, cc....cc] no interest, destroy...

aa....aa: sysMessageID

bb....bb: Transaction uid

cc....cc: Destination object

Description

This message is displayed when the consumer does not exist in the store.

KDAN24448-I

Message aa....aa [TUID=bb....bb, cc....cc] to be rolled back, destroy...

aa....aa: sysMessageID

bb....bb: Transaction uid

cc....cc: Destination object

Description

This message is displayed when a destroyed message is rolled back.

KDAN24449-I

Redeliver message aa....aa [TUID=bb....bb, cc....cc] to consumer dd....dd.

aa....aa: sysMessageID

bb....bb: Transaction uid

cc....cc: Destination object

dd....dd: Consumer uid

Description

This message is displayed when the message is redelivered to the consumer.

KDAN24450-I

Dumping order

Description

This message is displayed when the saved setup information is dumped.

KDAN24454-I

Deleting message ID: aa....aa.

aa....aa: Message ID

Description

This message is displayed when the message is deleted.

KDAN24457-I

Internal Error: unable to retrieve properties from redeliver message aa....aa.

aa....aa: sysMessageID

Description

This message is displayed when an internal Broker error occurred.

KDAN24459-I

Unable to find producer aa....aa checking if producer was removed recently bb....bb.

aa....aa: Producer uid

bb....bb: String

Description

This message is displayed when an internal Broker error occurred.

KDAN24464-I

Unknown consumer aa....aa.

aa....aa: Consumer uid

bb....bb: Packet reference

Description

This message is displayed when the consumer does not exist in the store.

KDAN24470-I

Consumer with ID of aa....aa is unavailable on session bb....bb [conuid,sess conuid] =[cc....cc,dd....dd] consumer session is : ee....ee.

aa....aa: Consumer uid

bb....bb: Session

cc....cc: Connection uid

dd....dd: Connection uid

ee....ee: Session uid

Description

This message is displayed when the consumer does not exist in the store.

KDAN24472-I

Setting Fault aa....aa [ selector= bb....bb ]

aa....aa: Fault information

bb....bb: Selector expression

Description

This message is displayed when the selector format is invalid.

KDAN24473-I

Removing Fault aa....aa

aa....aa: Fault information

Description

This message is displayed when the fault is removed from the fault injection.

KDAN24474-I

Turning on Fault Injection

Description

This message is displayed when the fault injection is turned on.

KDAN24475-I

Turning off Fault Injection

Description

This message is displayed when the fault injection is turned off.

KDAN24480-I

AFTER SLEEP aa....aa(seconds) BECAUSE OF FAULT bb....bb

aa....aa: 60

bb....bb: String

Description

This message is displayed when a fault occurs during the invocation of the sleep method of the thread.

KDAN24491-I

Unknown ProducerUID aa....aa.

aa....aa: Producer uid

Description

This message is displayed when an internal Broker error occurred.

KDAN24492-I

Producer aa....aa not on this connection bb....bb

aa....aa: Producer uid

bb....bb: Connection uid

Description

This message is displayed when an internal Broker error occurred.

KDAN24496-I

Timer shutting down

Description

This message is displayed when the timer is shut down.

KDAN24497-I

calculateState:didnt meet delta requirement

Description

This message is displayed when an internal Broker error occurred.

KDAN24498-I

Connection count aa....aa

aa....aa: Number

Description

This message is displayed when the connection count of the service is output.

KDAN24499-I

Connection aa....aa

aa....aa: Connection ID

Description

This message is displayed when the connection name of the service is output.

KDAN24501-I

Starting...

Description

This message is displayed when the Broker is started.

KDAN24502-I

XXX - target of null not implemented for aa....aa

aa....aa: Argument

Description

This message is displayed when svc is not specified as the argument in the target.

KDAN24506-I

Getting destination metrics on aa....aa

aa....aa: Destination

Description

This message is displayed when the metrics are acquired in the specified destination.

KDAN24508-I

aa....aa Consumer: bb....bb [paused, active,flowPaused, parentBusy, hasMessages, parentSize ] = [cc....cc,dd....dd,ee....ee,ff....ff,gg....gg,hh....hh].

aa....aa: Prefix

bb....bb: Consumer uid

cc....cc: Pause flag

dd....dd: Active flag

ee....ee: Flow pause flag

ff....ff: Parent list

gg....gg: Message

hh....hh: Parent list size

Description

This message displays the consumer information when dumping the session information.

KDAN24509-I

aa....aaBusy state [bb....bb] is cc....cc

aa....aa: Prefix

bb....bb: Consumer uid

cc....cc: Busy state

Description

This message displays the consumer state when dumping the session information.

KDAN24510-I

msgs is null

Description

This message is displayed when the message is null during the dumping of details.

KDAN24511-I

parentList is null

Description

This message is displayed when the consumer does not exist during the dumping of consumer details.

KDAN24512-I

GC'ing the system

Description

This message is displayed when the specified command argument is gc.

KDAN24513-I

Dumping threads: aa....aa

aa....aa: Stack trace

Description

This message is displayed when the specified command argument is threads.

KDAN24514-I

Resuming aa....aa

aa....aa: Producer

Description

This message is displayed when the specified command is resume and the command argument is prd.

KDAN24515-I

Resuming all destinations

Description

This message is displayed when all the destinations are restarted.

KDAN24516-I

Unable to tag some file free

Description

This message is displayed when the user does not have the permissions for the file during the deletion of the data from the vr file.

KDAN24517-I

number of opened files: aa....aa

aa....aa: File count

Description

This message is displayed when the file information is output.

KDAN24518-I

number of available opened files: aa....aa

aa....aa: Free files in the pool

Description

This message is displayed when the file information is output.

KDAN24519-I

number of transaction ids: aa....aa

aa....aa: Transaction ID

Description

This message is displayed when the transaction ID information is output.

KDAN24520-I

Transaction acknowledgements

Description

This message is displayed when the transaction acknowledgement information is output.

KDAN24521-I

Number of transactions containing acknowledgements: aa....aa.

aa....aa: Transaction ID

Description

This message is displayed when the number of transaction acknowledgements is output.

KDAN24523-I

SysMessageID: Could not clone: aa....aa.

aa....aa: Exception

Description

This message is displayed when the SysMessageID object is cloned.

KDAN24524-I

ReadOnlyPacket: Could not clone: aa....aa.

aa....aa: Exception

Description

This message is displayed when the ReadOnlyPacket object is cloned.

KDAN24525-I

Message Body: aa....aa bytes

aa....aa: Body size

Description

This message is displayed when the packet body is dumped.

KDAN24532-I

... ... ... Dumping MapEntry aa....aa

aa....aa: Hash code

Description

This message is displayed when the map memory is dumped.

KDAN24533-I

... ... ... .... thread info aa....aa

aa....aa: Thread

Description

This message is displayed when the thread information is dumped.

KDAN24535-I

Invalid growth_factor value. Using default value of 50%.

Description

This message is displayed when an invalid value is specified in the imq.persist.file.message.vrfile.growth_factor property.

KDAN24536-I

Invalid threshold value. Using default value of 0.

Description

This message is displayed when an invalid value is specified in the imq.persist.file.message.vrfile.threshold property.

KDAN24537-I

Invalid threshold_factor value. Using default value of 0%.

Description

This message is displayed when an invalid value is specified in the imq.persist.file.message.vrfile.threshold_factor property.

KDAN24538-I

bufs[aa....aa]=bb....bb

aa....aa: Prefix

bb....bb: Byte buffer

Description

This message is displayed when the buffer information is dumped.

KDAN24539-I

Dumping state of aa....aa

aa....aa: Thread

Description

This message is displayed when the general connection information and metrics are dumped.

KDAN24540-I

sessions = aa....aa

aa....aa: Sessions

Description

This message is displayed when the general connection information and metrics are dumped.

KDAN24541-I

busySessions = aa....aa

aa....aa: Busy sessions

Description

This message is displayed when the general connection information and metrics are dumped.

KDAN24542-I

runningMsgs = aa....aa

aa....aa: Running messages

Description

This message is displayed when the general connection information and metrics are dumped.

KDAN24543-I

paused = aa....aa

aa....aa: Pause type

Description

This message is displayed when the general connection information and metrics are dumped.

KDAN24544-I

waitingForResumeFlow = aa....aa

aa....aa: wait for resume flow flag

Description

This message is displayed when the general connection information and metrics are dumped.

KDAN24545-I

----------- busy sessions -----------

Description

This message is displayed when the connection information is dumped.

KDAN24546-I

----------- sessions -----------

Description

This message is displayed when the connection information is dumped.

KDAN24547-I

DUMPING CONNECTION aa....aa

aa....aa: imq connection

Description

This message is displayed when the connection information is dumped.

KDAN24548-I

control = aa....aa

aa....aa: NFLPriorityFifoSet size

Description

This message is displayed when the general connection information and metrics are dumped.

KDAN24549-I

read_assigned = aa....aa

aa....aa: runnable operation

Description

This message is displayed when the general connection information and metrics are dumped.

KDAN24550-I

write_assigned = aa....aa

aa....aa: runnable operation

Description

This message is displayed when the general connection information and metrics are dumped.

KDAN24551-I

Finished writing packet [aa....aa]

aa....aa: Packet

Description

This message is displayed when the packet data is written.

KDAN24552-I

Configuration Change Record

Description

This message is displayed when the configuration change record is output.

KDAN24553-I

backing file: aa....aa

aa....aa: Backing file

Description

This message is displayed when the backing file name is output.

KDAN24554-I

number of records: aa....aa

aa....aa: List of time stamps

Description

This message is displayed when the persisted records are output.

KDAN24555-I

number of interests: aa....aa

aa....aa: Consumers

Description

This message is displayed when the persisted consumers are output.

KDAN24556-I

Consumer [aa....aa] get message null reference

aa....aa: Consumer uid

Description

This message is displayed when the packet reference is null while acquiring or embedding the next packet.

KDAN24557-I

Consumer [aa....aa] message requened: bb....bb

aa....aa: Consumer uid

bb....bb: Packet reference

Description

This message is displayed when the packet reference exists while acquiring or embedding the next packet.

KDAN24558-I

Displaying broker metrics : aa....aa

aa....aa: Metrics information

Description

This message displays the Broker metrics.

KDAN24559-I

Exception caught when setting output to file: aa....aa: : bb....bb:

aa....aa: File name

bb....bb: Error message

Description

This message is displayed when the specified file does not exist.

KDAN24560-I

Exception caught when closing print streams to: aa....aa: : bb....bb:

aa....aa: File name

bb....bb: Error message

Description

This message is displayed when an internal Broker error occurred.

KDAN24561-I

Reverting to stdout

Description

This message is displayed when the specified file does not exist.

KDAN30001-E

Error detected while parsing command line options.

Description

This error occurs when the user specifies invalid command line arguments.

Action

Specify valid command line options.

KDAN30002-E

Invalid option: aa....aa.

aa....aa: Subcommand

Description

This error occurs when an invalid subcommand is specified for the command.

Action

Use the -h option to execute the command and check the valid subcommands.

KDAN30003-E

Invalid base property name specified for option: aa....aa

aa....aa: Command line option

Description

This error occurs when the user specifies an invalid property name as the command line option.

Action

Specify a valid property name as the command line option.

KDAN30004-E

Invalid hard coded value specified for option: aa....aa

aa....aa: Command line option

Description

This error occurs when the user directly specifies a numeric value as the command line option.

Action

Specify a valid property name as the command line option.

KDAN30005-E

An argument was expected for option: aa....aa. Please type "bb....bb -h" for help.

aa....aa: Command line option

bb....bb: Command

Description

This error occurs when the argument is not specified.

Action

Make sure that the following arguments are specified for the option. To display help, execute the command using the -h option.

KDAN30006-E

Bad name value pair specified (aa....aa) for option: bb....bb. Please use the format: name=value

aa....aa: Argument

bb....bb: Command line option

Description

This error occurs when an incorrect data format is specified for the name/value pair in the -o option during the execution of cjmsobjmgr.

Action

Specify the argument in the name=value format.

KDAN30008-E

aa....aaError detected while validating command line options.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when an invalid command line option is specified.

Action

Specify a valid command line option.

KDAN30009-E

aa....aaBad command specified: bb....bb

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Command

Description

This error occurs when an invalid subcommand is specified.

Action

Specify a valid subcommand. To display help, enter aa....aa -h.

KDAN30014-E

The destination name must be specified with the aa....aa option.

aa....aa: Command line option

Description

This error occurs when the destination name is specified without the command line option.

Action

Specify the destination name using the -n option.

KDAN30015-E

Invalid read-only value specified: aa....aa.

aa....aa: Read-only value

Description

This error occurs when the user attempts to change the state of a read-only object.

Action

When updating the state, make sure that the state of the object is not read-only.

KDAN30028-E

Invalid property name: aa....aa.

aa....aa: Property name

Description

This error occurs when an invalid property name is specified.

Action

Specify a valid property name.

KDAN30031-E

Caught exception while loading command file.

Description

This error occurs when the property file does not exist.

Action

Confirm that the required property file exists.

KDAN30032-E

Caught exception while getting user input.

Description

This error occurs when there is no input from the user when the command is executed.

Action

Provide the require input data when the command is executed.

KDAN30033-E

aa....aaThe target name must be specified with the bb....bb option.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Command option

Description

This error occurs when the destination name is not specified during the execution of the cjmsicmd command (with -n option).

Action

Specify the destination name using the -n option.

KDAN30034-E

aa....aaBad argument specified for the bb....bb command: cc....cc

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Subcommand

cc....cc: Argument

Description

This error occurs when invalid arguments are specified.

Action

Specify a valid argument.

KDAN30035-E

aa....aaThe valid command arguments for the bb....bb command are:

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Pause

Description

This error occurs when no argument is specified for the PAUSE command.

Action

Make sure that the specified argument is correct.

KDAN30036-E

aa....aaThe destination name needs to be specified with the bb....bb option.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Command line option

Description

This error occurs when the destination name is specified without specifying the command line option.

Action

Specify the destination name using the -n option.

KDAN30037-E

aa....aaThe target attributes need to be specified with the bb....bb option.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Command line option

Description

This error occurs when the command line option is not specified while passing the arguments.

Action

Specify command line options such as -o or -n.

KDAN30038-E

aa....aaThe destination type needs to be specified with the bb....bb option.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Command line option

Description

This error occurs when the destination name is not specified using the -t option during the execution of the cjmsicmd command.

Action

Specify the destination name using the -t option.

KDAN30039-E

aa....aaThe queue delivery policy value ''bb....bb'' is not valid.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Delivery policy value

Description

This error occurs when the user specifies an invalid value.

Action

Contact maintenance personnel.

KDAN30040-E

aa....aaThe value ''bb....bb'' for the attribute ''cc....cc'' is invalid.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Active consumers

cc....cc: Maximum active consumers

Description

This error occurs when the user specifies a non-integer value for maximum active consumers.

Action

Make sure that an integer value is specified.

KDAN30041-E

aa....aaThe destination type ''bb....bb'' is not valid.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Destination type

Description

This error occurs when an invalid destination type is specified.

Action

Specify a valid destination type (q [queue] or t [topic]).

KDAN30042-E

The ''aa....aa'' service cannot be paused.

aa....aa: Service name

Description

This error occurs when an attempt is made to pause the ADMIN service.

Action

The ADMIN service cannot be paused.

KDAN30043-E

The ''aa....aa'' service cannot be resumed.

aa....aa: Service name

Description

This error occurs when an attempt is made to resume the ADMIN service.

Action

The ADMIN service cannot be resumed.

KDAN30044-E

The destination ''aa....aa'' does not exist or its type is not topic.

aa....aa: Destination name

Description

This error occurs when the specified destination does not exist in CJMSP or is not a topic type.

Action

Specify an existing topic destination name or destination type t (topic).

KDAN30045-E

aa....aaThe client ID must be specified with the bb....bb option.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Command line option

Description

This error occurs when the client ID is specified without specifying the -c option.

Action

Specify the client ID with the -c option.

KDAN30047-E

aa....aaThe value ''bb....bb'' for the attribute''cc....cc'' is invalid.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Option value

cc....cc: Broker command option

Description

This error occurs when the user specifies an invalid boolean value.

Action

Specify a valid boolean value of True/ False.

KDAN30048-E

aa....aaThe value ''bb....bb'' for the attribute ''cc....cc'' is invalid.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Log level

cc....cc: imq.log.level

Description

This error occurs when the log level is not specified.

Action

Specify the message log level. The valid values are INFO, ERROR, DEBUG and WARNING.

KDAN30049-E

aa....aa bb....bb seconds has elapsed and the broker failed to restart.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Time interval (seconds)

Description

This error occurs when the Broker is disconnected.

Action

Make sure that the Broker is running.

KDAN30050-E

aa....aaThe byte value ''bb....bb'' for the attribute ''cc....cc'' is invalid.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Byte value

cc....cc: Destination size

Description

This error occurs when the user specifies an invalid value.

Action

Specify a valid byte value. The valid values are

10000= 10000 bytes

2500b= 2500 bytes

4k= 4 Kilo bytes

12m= 12 Mega bytes.

KDAN30051-E

aa....aaThe value ''bb....bb'' specified for the receive timeout is invalid.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: ADMIN receive timeout value (seconds)

Description

This error occurs when a negative value is specified for ADMIN receive timeout (-rtm) during the execution of the cjmsicmd command.

Action

When using the -rtm option, make sure that a positive value is specified.

KDAN30052-E

aa....aaThe value ''bb....bb'' for the pause type is invalid.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Pause type argument

Description

This error occurs when an invalid PAUSE type is specified during the execution of the cjmsicmd command.

Action

Specify a valid PAUSE type (PRODUCERS, CONSUMERS, and ALL).

KDAN30053-E

Error while connecting to the broker on host ''aa....aa'' and port ''bb....bb''.

aa....aa: Host name

bb....bb: Port

Description

This error occurs in the following cases:

When an invalid host name or invalid port number is specified

When an incorrect port number, on which the Broker is not running, is specified in the -b option of cjmsicmd

Action

Specify the correct host name and port number.

Confirm that the Broker is running at the specified port number.

KDAN30054-E

aa....aaError while sending the request to the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is disconnected.

Action

Restart the Broker.

KDAN30055-E

aa....aaError while performing this operation on the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs in the following cases:

When an attempt is made to create an existing destination

When the Broker is disconnected

Action

Make sure that the destination name is unique.

Restart the Broker.

KDAN30056-E

aa....aaError while closing connection to the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is already in a stopped mode.

Action

Make sure that a running Broker is stopped.

KDAN30057-E

aa....aaError when getting type of the admin message.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is disconnected.

Action

Restart the Broker.

KDAN30058-E

aa....aaError when getting the admin reply message status.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Start the Broker.

KDAN30059-E

aa....aaReply to admin message was not received.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Start the Broker.

KDAN30060-E

aa....aaInvalid operation is detected.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the user attempts to perform an invalid operation.

Action

Perform a valid operation.

KDAN30061-E

aa....aaInvalid port number value is specified.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when an invalid port number is set up in the properties file or the port number is not set up at all.

Action

Specify a valid value for imq.portmapper.port in the properties file.

KDAN30062-E

aa....aaInvalid attribute specified: bb....bb

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Attribute

Description

This error occurs when an invalid attribute is specified during the execution of the cjmsicmd list dst command.

Action

Specify a valid attribute.

KDAN30070-E

The value ''aa....aa'' for the metric interval is invalid. Please use an integer value.

aa....aa: Metric (measurement) interval

Description

This error occurs when a non-integer value is specified for the metric (measurement) interval during the execution of the cjmsicmd command.

Action

Specify an integer value for the metric (measurement) interval using the -int option.

KDAN30071-E

The value ''aa....aa'' for the broker/ service metric type is invalid.

The valid values for broker/ service metric type are:

aa....aa: Broker or service metric type

Description

This error occurs when an invalid Broker or service metric type is specified during the execution of the cjmsicmd command.

Action

Specify a valid Broker or service type (cxn, rts, and tt1) using the -m option.

KDAN30072-E

Please verify that there is a Broker running on the specified host and port or use the ''aa....aa'' option to specify the correct broker host and port.

aa....aa: Command line option

Description

This error occurs when CJMSP does not run on the specified port.

Action

Start CJMSP, and then try re-executing the command.

KDAN30075-E

Property file:aa....aa is not readable.

aa....aa: File name

Description

This error occurs when the property file does not exist in the specified location.

Action

Confirm that the property file exists.

KDAN30076-E

Failed to open property file: aa....aa, bb....bb

aa....aa: File name

bb....bb: Exception message

Description

This error occurs when the property file does not exist in the specified location.

Action

Confirm that the property file exists.

KDAN30077-E

Property file: aa....aa is not writeable.

aa....aa: File name

Description

This error occurs when the user attempts to write to a write-inhibit property file.

Action

Check whether the user has the write permission for the property file.

KDAN30078-E

Cannot create property file:aa....aa

aa....aa: File name

Description

This error occurs when the directory is write inhibit.

Action

Confirm that the user has the write permission for the directory.

KDAN30079-E

Failed to write to property file: aa....aa, bb....bb

aa....aa: File name

bb....bb: Exception message

Description

This error occurs when the directory is write inhibit.

Action

Confirm that the user has the write permission for the directory.

KDAN30081-E

aa....aaThe target attribute name needs to be specified with the bb....bb option.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Option

Description

This error occurs when the target name (such as the destination name or destination type) is specified without specifying the option.

Action

Specify the target name after specifying the option.

Example:

Destination name with the -n option

Destination type with the -t option

KDAN30082-E

aa....aaCannot update ''Port Number'' for ''bb....bb'' service.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Service name

Description

This error occurs when the user attempts to change the Broker service port number.

Action

Do not change the port number.

KDAN30087-E

Problem encountered when using SSL/ TLS as the admin transport.

Description

This error occurs when the user attempts to set up an invalid protocol service.

Action

Do not set up the SSL and TLS protocol services.

KDAN30091-E

aa....aaThe value ''bb....bb'' specified for the number of retries is invalid.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Retry count

Description

This error occurs when the retry count is not specified.

Action

Specify a valid value.

KDAN30092-E

aa....aaThe connection identifier specified (bb....bb) is not valid, it is not a long integer.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Connection ID

Description

This error occurs when the specified connection ID is not a long type.

Action

Specify a valid connection ID. Execute the list cxn command to check the valid connection ID.

KDAN30093-E

aa....aaThe value ''bb....bb'' for the attribute ''cc....cc'' is invalid.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Invalid value

cc....cc: Attribute or property name

Description

This error occurs when an invalid value is specified for the attribute or property name.

Action

Specify a valid value for the attribute or property name.

KDAN30095-E

Property aa....aa not found in passfile bb....bb.

aa....aa: Property name

bb....bb: Password file name

Description

This error occurs when the properties do not contain items corresponding to cjmsicmd passwd.

Action

Stop, and then restart the Broker.

KDAN30096-E

Creation of destination bb....bb of type aa....aa failed.

aa....aa: Destination type

bb....bb: Destination name

Description

This error occurs when an attempt to create a destination fails.

Action

Confirm that the Broker contains sufficient memory to create a destination.

KDAN30097-E

The type of the value specified for the attribute aa....aa is incorrect. Please specify the value using a java.lang.String object.

aa....aa: Destination attribute

Description

This error occurs when the user attempts to specify a non-java.lang.String type value for the destination attribute.

Action

Specify the java.lang.String type attributes.

KDAN30098-E

aa....aaThe value ''bb....bb'' specified for the number of seconds is invalid. Please specify an integer value that is larger than zero.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Shutdown interval

Description

This error occurs when a negative value is specified as the shutdown interval.

Action

Make sure that a positive value is specified.

KDAN30100-E

Bad broker address specified: aa....aa.

aa....aa: Broker address

Description

This error occurs when an invalid Broker address is specified.

Action

Specify an address where the Broker is running.

KDAN30101-E

aa....aaAttribute specified is for use at creation time only: bb....bb.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Attribute name

Description

This error occurs when the user attempts to update a read-only attribute.

Action

Do not update a read-only attribute.

KDAN30107-E

Name is already bound.

Description

This error occurs when the user specifies an already bound JNDI.

Action

Specify a unique JNDI lookup name.

KDAN30108-E

Authentication error while accessing the naming or directory service.

Description

This error occurs when the information provided in the user program is invalid or the user authentication fails for the naming or directory service.

Action

Specify a valid user information.

KDAN30111-E

The client is unable to communicate with the directory or naming service.

Description

This error occurs when the client cannot communicate with the directory or naming service due to network partition, hardware or interface problems, or client and server machine failures.

Action

Confirm that the network communication is normal.

KDAN30112-E

No initial context implementation could be created.

Description

This error occurs when the initial context cannot be created.

Action

Make sure that the initial context is created before executing the operation.

KDAN30113-E

The service provider schema was violated in some way.

Description

This error occurs when there are schema violations because the method changes the attributes of the object in some way.

Action

Move the object to a namespace that violates the schema without changing the attributes of the object.

KDAN30114-E

The name does not exist.

Description

The components of the specified name are not resolved because the components are not bound and this warning is issued.

Action

Make sure that the components are bound.

KDAN30115-E

The name of the object already exists in the store.

Description

This error occurs when the client attempts to use a name that is already bound to other objects.

Action

Use a unique binding name.

KDAN30116-E

This context does not take binding attributes.

Description

This error occurs when an attempt is made to add or change an attribute set that is incompletely or incorrectly specified.

Action

Before updating an attribute set, make sure that the attributes are set up.

KDAN30118-E

A general naming exception is caught.

Description

This error occurs when name resolution is not performed for the specified JNDI name.

Action

Specify a valid JNDI name.

KDAN30119-E

Invalid port number is specified in aa....aa

aa....aa: Port number

Description

This error occurs when an invalid port number is specified.

Action

Specify a valid port number.

KDAN30120-E

Neither Queue nor Topic type

Description

This error occurs when the user specifies a ConnectionFactory type other than Queue and Topic.

Action

Specify a valid type (Queue and Topic).

KDAN30121-E

Invalid object type

Description

This error occurs when the user specifies a ConnectionFactory type other than Queue and Topic.

Action

Specify a valid type (QueueConnectionFactory, TopicConnectionFactory, XAQueueConnectionFactory, and XATopicConnectionFactory).

KDAN30122-E

Destination name is not specified.

Description

This error occurs when the destination is not specified in the property file.

Action

Specify a valid destination name.

KDAN30123-E

Deletion of Message Queue broker instance aa....aa failed. The deletion was interrupted prematurely.

aa....aa: Broker instance

Description

This error occurs when the Broker is stopped during the deletion of the message queue.

Action

Confirm that the Broker is running.

KDAN30124-E

Deletion of Message Queue broker instance aa....aa failed. The broker instance does not exist.

aa....aa: Broker instance

Description

This error occurs when the Broker is not running during the deletion of the message queue.

Action

Confirm that the Broker is running.

KDAN30125-E

Deletion of Message Queue broker instance aa....aa failed. A broker with this instance name is still active.

aa....aa: Broker instance

Description

This error occurs when the user attempts to stop the Broker while the Broker is processing a request.

Action

Confirm that the Broker is running.

KDAN30126-E

Deletion of Message Queue broker instance aa....aa failed. The instance directory does not have the correct permissions.

aa....aa: Broker instance

Description

This error occurs when the instance directory of the Broker instance does not have the write permission.

Action

Confirm that the instance directory has the appropriate permissions.

KDAN30127-E

Deletion of Message Queue broker instance aa....aa failed. Problem encountered while removing the persistent store.

aa....aa: Broker instance

Description

This error occurs when the persistence store of the Broker instance is already deleted.

Action

Before removing the Broker instance, confirm that the corresponding persistence store exists.

KDAN30128-E

Deletion of Message Queue broker instance aa....aa failed. Caught an IOException.

aa....aa: Broker instance

Description

This error occurs due to a network problem.

Action

Make sure that the network communication is normal.

KDAN30129-E

Deletion of Message Queue broker instance aa....aa failed: store. Unknown reason.

aa....aa: Broker instance

Description

This error occurs when the Broker instance is already deleted.

Action

Before deleting the Broker instance, make sure that the Broker instance exists.

KDAN30131-E

JMSException caught: aa....aa.

aa....aa: Exception message

Description

This message is displayed when an internal error occurs.

Action

Contact maintenance personnel.

KDAN30132-E

Invalid broker address aa....aa specified.

aa....aa: Broker address

Description

This error occurs when an invalid Broker address is specified.

Action

Specify an accurate Broker address.

KDAN30133-E

Invalid host name aa....aa specified

aa....aa: Host or port value

Description

This error occurs when an invalid Broker host name is specified.

Action

Specify an accurate Broker host name.

KDAN30134-E

Invalid port aa....aa specified

Description

This error occurs when an invalid port number is set up in the properties file or the port number is not set up at all.

Action

Confirm that the correct port number has been set up.

KDAN30135-E

Failed to set system property: aa....aa=bb....bb.

aa....aa: Property name

bb....bb: Property value

Description

This error occurs in the following cases when the system properties are set up:

When the key or value is null

When the key is empty

Action

Confirm that the key and value are not null.

KDAN30136-E

Listing messages failed.

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30137-E

Destroying message failed.

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30138-E

Purging all the destinations failed.

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30139-E

Purging failed for queue aa....aa.

aa....aa: Queue name

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30140-E

Purging failed for topic aa....aa

aa....aa: Topic name

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30141-E

Destroying all the destinations failed.

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30142-E

Destroy failed for queue aa....aa.

aa....aa: Queue name

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30143-E

Destroy failed for topic aa....aa.

aa....aa: Topic name

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30144-E

Querying message failed.

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30145-E

Problems retrieving the destination info.

Description

This error occurs when the specified destination does not exist.

Action

Make sure that the specified destination exists in the Broker.

KDAN30146-E

Problems retrieving the broker info.

Description

An internal error occurred when acquiring the Broker properties from the return message.

Action

Contact maintenance personnel for internal errors.

KDAN30147-E

Problems retrieving the service info.

Description

An internal error occurred when acquiring the service information from the return message.

Action

Contact maintenance personnel for internal errors.

KDAN30148-E

Unknown exception caught: aa....aa.

aa....aa: Exception type

Description

This error occurs when the caught exception is not the expected exception.

Action

Contact maintenance personnel for internal errors.

KDAN30149-E

Error occurred while checking the reply.

Description

This error occurs when the received message type is not the expected message type.

Action

Contact maintenance personnel for internal errors.

KDAN30152-E

Property Name and Value :aa....aa=bb....bb

aa....aa: Property name

bb....bb: Property value

Description

This message is displayed when 0 is specified in the property value.

Action

Set up a valid value, excluding 0, in the property value.

KDAN30153-E

aa....aaListing destinations failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30154-E

aa....aaListing services failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30155-E

aa....aaPausing the broker failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30156-E

aa....aaPausing the service failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30157-E

aa....aaResuming the broker failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30158-E

aa....aaResuming the service failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30159-E

aa....aaShutting down the broker failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30160-E

aa....aaRestarting the broker failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30161-E

aa....aaCreating the destination failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30162-E

aa....aaDestroying the destination failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30163-E

aa....aaPurging the destination failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30164-E

aa....aaQuerying the destination failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30165-E

aa....aaQuerying the service failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30166-E

aa....aaListing transactions failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30167-E

Querying the transaction failed.

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30168-E

Commiting the transaction failed.

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30169-E

Rolling back the transaction failed.

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30170-E

aa....aaPausing the destination failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30171-E

aa....aaResuming the destination failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30172-E

aa....aaDisplaying destination metrics failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30173-E

aa....aaCompacting the destination failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30174-E

aa....aaCompacting the destinations failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30175-E

aa....aaPausing all destinations failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30176-E

aa....aaResuming all destinations failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30177-E

aa....aaListing connections failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30178-E

aa....aaQuerying the connection failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30179-E

aa....aaQuerying the broker failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30180-E

aa....aaUpdating the broker failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30181-E

aa....aaUpdating the service failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30182-E

aa....aaUpdating the destination failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30183-E

aa....aaListing durable subscriptions failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30184-E

aa....aaDestroying the durable subscription failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30185-E

aa....aa Displaying service metrics failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30186-E

aa....aaDisplaying broker metrics failed.

aa....aa: Broker host name and port number (information about this argument is only output to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30187-E

Reloading broker cluster configuration failed.

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30188-E

aa....aaPurging the durable subscription failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30189-E

aa....aaQuiescing the broker failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30190-E

Taking over another broker failed.

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30191-E

aa....aaListing the broker failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30192-E

aa....aaListing JMX Connectors failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30193-E

aa....aaDestroying the connection failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30194-E

aa....aaUnquiescing the broker failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30195-E

aa....aaResetting the broker failed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker is not running.

Action

Confirm that the Broker is running.

KDAN30196-E

Internal Error

Description

An internal error occurred when the sender, receiver, or session was terminated.

Action

Contact maintenance personnel.

KDAN30197-E

aa....aaBrokerException thrown. Reason: bb....bb

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Cause of the error

Description

This message is displayed when the specified destination name is repeated while a new destination is being created with the cjmsicmd command.

An exception occurs while a management command is being processed through the Broker.

Action

Make sure that the specified destination does not exist in the Broker.

KDAN30198-E

Exception caught: aa....aa

aa....aa: Error message

Description

This message is displayed when an invalid host name is specified in the -b option.

An internal error occurred when the input data is read.

Action

Make sure that a valid host name is specified in the -b option.

KDAN30199-E

aa....aaThere are no JMX Connectors on the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs while listing the JMX connectors that are not JMX connectors.

Action

Before executing this operation, confirm that the JMX connector exists on the Broker.

KDAN30200-E

There are no messages.

Description

This error occurs when there are no messages when the messages in the Broker are listed.

Action

Before executing this operation, confirm that the messages exist in the Broker.

KDAN30201-E

aa....aaIncorrect data returned from broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN30202-E

aa....aa is not recognized.

aa....aa: Attribute name

Description

This error occurs when invalid arguments are specified.

Action

Specify a correct argument.

KDAN30203-E

Property Name :aa....aa=-1

aa....aa: Property name

Description

This error occurs during the unlimited -1 check of the property.

Action

Set up the unlimited value -1.

KDAN30204-E

aa....aaUnrecognized response: bb....bb.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: User input [Y/ N]

Description

This error occurs when invalid arguments are specified.

Action

Specify a correct argument.

KDAN30208-E

aa....aaBroker not responding, retrying [bb....bb of cc....cc attempts, timeout=dd....dd seconds]

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Retry count

cc....cc: Maximum retry count

dd....dd: Retry interval

Description

This error occurs when the network connection is invalid.

Action

Make sure that the network connection is correct.

Contact the System Administrator.

KDAN30209-E

aa....aaThe broker was not updated.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when invalid arguments are specified while updating the Broker.

Action

Specify the correct argument when updating the Broker.

KDAN30210-E

aa....aaThe service was not updated.

aa....aa: Broker host name and port number (Information about this argument is output only to the management command log)

Description

This error occurs when invalid arguments are specified while updating the service.

Action

Specify the correct argument when updating the service.

KDAN30211-E

aa....aaThe destination was not updated.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when invalid arguments are specified while updating the destination.

Action

Specify the correct argument when updating the destination.

KDAN30213-E

aa....aaThe broker was not quiesced.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when invalid arguments are specified while the Broker is in a quiescent state.

Action

Specify the correct argument when the Broker is in a quiescent state.

KDAN30214-E

aa....aaThe connection was not destroyed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when the Broker connection, specified when the connections are destroyed, does not exist.

Action

Confirm that the connection with the Broker exists.

KDAN30215-E

aa....aaThe broker was not unquiesced.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when invalid arguments are specified while unquiescing the Broker.

Action

Specify the correct arguments while unquiescing the Broker.

KDAN30216-E

aa....aaThe broker was not reset.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This error occurs when invalid arguments are specified while resetting the Broker.

Action

Specify the correct arguments when resetting the Broker.

KDAN30217-E

The message was not destroyed.

Description

This error occurs when invalid arguments are specified while destroying a message.

Action

Specify the correct arguments while destroying messages.

KDAN30219-E

The destinations were not destroyed.

Description

This error occurs when invalid arguments are specified while destroying multiple destinations.

Action

Specify the correct arguments while destroying multiple destinations.

KDAN30220-E

Ungracefully shutdown the broker.

Description

An internal error occurred.

Action

Contact maintenance personnel.

KDAN30221-E

No destinations purged.

Description

This error occurs when invalid arguments are specified while deleting the messages for a destination.

Action

Specify the correct arguments while deleting the messages for a destination.

KDAN30222-E

No destinations destroyed.

Description

This error occurs when invalid arguments are specified while destroying a destination.

Action

Specify the correct arguments while destroying a destination.

KDAN32012-W

The value aa....aa (unlimited) was specified for the following attributes:

aa....aa: Value

Description

This message is displayed when an invalid value indicating an unlimited value is specified. This message is displayed when the user specifies 0, indicating an unlimited value, in a property.

Action

To specify an unlimited value, specify -1 in the property.

KDAN32013-W

The new value that should be used for specifying ''unlimited'' is: aa....aa

aa....aa: Value

Description

This message is displayed when an invalid value indicating an infinite value is specified. This message is displayed when the user specifies 0, indicating an infinite value, in a property.

Action

To specify an infinite value, specify -1 in the property.

KDAN32014-W

The values for the attributes above have been converted to the following:

Description

This message is displayed when an invalid value indicating an infinite value is specified. This message is displayed when the user specifies 0, indicating an infinite value, in a property.

Action

To specify an infinite value, specify -1 in the property.

KDAN34081-I

Usage: cjmsicmd <subcommand> <argument> [<options>]

Description

This message displays the usage of cjmsicmd help.

KDAN34082-I

Valid cjmsicmd subcommands and arguments:

compact dst : Compact one or all destinations.

create dst : Create a destination.

destroy dst : Destroy a destination.

destroy dur : Destroy a durable subscription.

list bkr : List the broker.

list dst : List destinations on the broker.

list dur : List durable subscriptions on the topic.

list svc : List services on the broker.

pause bkr : Pause jms service on the broker.

pause dst : Pause one or all destinations.

purge dst : Purge all messages on a destination without

destroying the destination.

purge dur : Purge all messages on a durable subscription

without destroying the durable subscription.

query bkr : Query and display information on a broker.

query dst : Query and display information on a destination.

resume bkr : Resume jms service on the broker.

resume dst : Resume one or all destinations.

shutdown bkr : Shutdown broker.

Description

This message displays the usage of cjmsicmd help.

KDAN34083-I

cjmsicmd options:

-b : Specify the broker host and port (host:port).

-c : Specify the client ID.

-d : Specify the topic name.

Used only when listing durable subscriptions.

-f : Perform action without user confirmation.

-h, -help : Display usage help.

-n : Specify the name of the argument (e.g. destination name,

durable subscription name).

-o : Specify argument properties (e.g. destination

properties).

-rtm : Specify the admin receive timeout in seconds. Default is 10.

-t : Specify the type of destination

Valid values = {q, t} where

q = Queue

t = Topic

-time : Specify the number of seconds prior to shutdown.

Used only when shutting down the broker.

-tmp : Also display temporary destinations.

Description

This message displays the usage of cjmsicmd help.

KDAN34084-I

Attributes:

Description

This message displays the usage of cjmsicmd help.

KDAN34085-I

Queue:

Description

This message displays the usage of cjmsicmd help.

KDAN34086-I

Topic:

Description

This message displays the usage of cjmsicmd help.

KDAN34101-I

aa....aaThe valid values for ''bb....bb'' are:

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

bb....bb: Property name

Description

This message displays a valid log level value.

This message displays a valid limit action value.

KDAN34106-I

The value '-1' can be used to specify 'unlimited' for the following Queue/ Topic attributes:

Description

This message displays the queue/ topic attributes for which -1 can be set as an infinite value.

KDAN34107-I

The value '-1' can be used to specify 'unlimited' for the following Broker attributes:

Description

This message displays the Broker attributes for which -1 can be set as an infinite value.

KDAN34108-I

On the broker specified by:

Description

This message displays the Broker information.

KDAN34110-I

aa....aaSuccessfully listed destinations.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the destinations are listed normally.

KDAN34113-I

aa....aaSuccessfully listed services.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the services are listed normally.

KDAN34115-I

Pausing the broker specified by:

Description

This message is displayed when a Broker is paused.

KDAN34116-I

aa....aaSuccessfully paused the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is paused normally.

KDAN34118-I

aa....aaThe broker was not paused.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is not running.

KDAN34120-I

aa....aaSuccessfully paused the service.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a service is paused normally.

KDAN34122-I

aa....aaThe service was not paused.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is not running.

KDAN34123-I

Resuming the broker specified by:

Description

This message is displayed when a Broker is resumed.

KDAN34124-I

aa....aaSuccessfully resumed the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is resumed normally.

KDAN34126-I

aa....aaThe broker was not resumed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is not running.

KDAN34128-I

aa....aaSuccessfully resumed the service.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a service is resumed normally.

KDAN34130-I

aa....aaThe service was not resumed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is not running.

KDAN34131-I

Shutting down the broker specified by:

Description

This message is displayed when a Broker is shut down.

KDAN34132-I

aa....aaSuccessfully shutdown the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is shut down normally.

KDAN34134-I

aa....aaThe broker was not shutdown.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is not running.

KDAN34136-I

aa....aaSuccessfully restarted the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is restarted normally.

KDAN34138-I

aa....aa The broker was not restarted.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is not running.

KDAN34140-I

aa....aaSuccessfully created the destination.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a destination is created normally.

KDAN34143-I

aa....aaSuccessfully destroyed the destination.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a destination is destroyed normally.

KDAN34145-I

aa....aaThe destination was not destroyed.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is not running.

KDAN34147-I

aa....aaSuccessfully purged the destination.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a destination is purged normally.

KDAN34149-I

aa....aaThe destination was not purged.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is not running.

KDAN34151-I

aa....aaSuccessfully queried the destination.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a destination is queried normally.

KDAN34154-I

aa....aa Successfully queried the service.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a service is queried normally.

KDAN34180-I

aa....aaSuccessfully paused the destination.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a destination is paused normally.

KDAN34182-I

aa....aaThe destination was not paused.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is not running.

KDAN34186-I

CREATED

Description

This message is displayed when a transaction attribute is displayed.

KDAN34187-I

STARTED

Description

This message is displayed when a transaction attribute is displayed.

KDAN34188-I

FAILED

Description

This message is displayed when a transaction attribute is displayed.

KDAN34189-I

INCOMPLETE

Description

This message is displayed when a transaction attribute is displayed.

KDAN34190-I

COMPLETE

Description

This message is displayed when a transaction attribute is displayed.

KDAN34191-I

PREPARED

Description

This message is displayed when a transaction attribute is displayed.

KDAN34192-I

COMMITTED

Description

This message is displayed when a transaction attribute is displayed.

KDAN34193-I

ROLLEDBACK

Description

This message is displayed when a transaction attribute is displayed.

KDAN34194-I

UNKNOWN

Description

This message is displayed when a transaction attribute is displayed.

KDAN34198-I

aa....aaSuccessfully resumed the destination.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a destination is resumed normally.

KDAN34203-I

aa....aaSuccessfully displayed service metrics.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is issued when the service metrics are displayed normally.

KDAN34204-I

aa....aaSuccessfully displayed broker metrics.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is issued when the Broker metrics are displayed normally.

KDAN34205-I

aa....aaSuccessfully displayed destination metrics.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is issued when the destination metrics are displayed normally.

KDAN34208-I

aa....aaSuccessfully compacted the destination.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the destination is compressed normally.

KDAN34209-I

aa....aaSuccessfully compacted the destinations.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the destination is compressed normally.

KDAN34215-I

aa....aaSuccessfully paused all destinations.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when all the destinations are paused normally.

KDAN34219-I

aa....aaSuccessfully resumed all destinations.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when all the destinations are resumed normally.

KDAN34222-I

Using the following attribute:

Description

This message is displayed when a paused type is specified while resetting a Broker.

KDAN34225-I

aa....aaSuccessfully listed connections.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the connections are listed normally.

KDAN34227-I

aa....aaThere are no connections to list.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the connections to the Broker do not exist when the connections are listed.

KDAN34238-I

aa....aaSuccessfully queried the connection.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a connection is queried normally.

KDAN34242-I

Destination Name

Description

This message displays the destination information.

KDAN34243-I

Destination Type

Description

This message displays the destination information.

KDAN34246-I

Current Number of Messages

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34247-I

Current Message Bytes

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34248-I

Max Total Message Bytes

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34249-I

Max Number of Messages

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34250-I

Max Bytes per Message

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34252-I

Max Number of Active Consumers

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34254-I

Limit Behavior

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34256-I

Consumer Flow Limit

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34257-I

Max Number of Producers

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34258-I

Current Number of Active Consumers

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34262-I

Service Name

Description

This message is displayed when the destination is queried using the cjmsicmd query svc command.

KDAN34263-I

Port Number

Description

This message is displayed when the destination is queried using the cjmsicmd query svc command.

KDAN34264-I

Service State

Description

This message is displayed when the destination is queried using the cjmsicmd query svc command.

KDAN34265-I

Min Number of Threads

Description

This message is displayed when the destination is queried using the cjmsicmd query svc command.

KDAN34266-I

Max Number of Threads

Description

This message is displayed when the destination is queried using the cjmsicmd query svc command.

KDAN34267-I

Current Number of Allocated Threads

Description

This message is displayed when the destination is queried using the cjmsicmd query svc command.

KDAN34268-I

Current Number of Connections

Description

This message is displayed when the destination is queried using the cjmsicmd query svc command.

KDAN34270-I

Current Number of Producers

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34271-I

Destination State

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34277-I

Primary Port

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34282-I

Use Dead Message Queue

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34295-I

aa....aaSuccessfully queried the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the Broker is queried normally.

KDAN34296-I

Instance Name

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34297-I

Auto Create Topics

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34298-I

Auto Create Queues

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34305-I

Max Number of Messages in System

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34306-I

Max Total Message Bytes in System

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34307-I

Max Message Size

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34312-I

aa....aaSuccessfully updated the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the Broker is updated normally.

KDAN34316-I

aa....aaSuccessfully updated the service.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the service is updated normally.

KDAN34321-I

aa....aaSuccessfully updated the destination.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the destination is updated normally.

KDAN34322-I

Listing all durable subscriptions on the topic ''aa....aa'' on the broker specified by:

aa....aa: topic name

Description

This message is displayed when all the durable subscribers on a specified topic are listed normally.

KDAN34323-I

aa....aaSuccessfully listed durable subscriptions.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the durable subscribers are listed normally.

KDAN34326-I

aa....aaSuccessfully destroyed the durable subscription.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the durable subscribers are destroyed normally.

KDAN34393-I

Current Number of Messages in System

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34394-I

Current Total Message Bytes in System

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34401-I

aa....aaSuccessfully purged the durable subscription.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a durable subscriber is purged normally.

KDAN34402-I

aa....aaThe durable subscription was not purged.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is not running.

KDAN34416-I

Auto Created Queue Max Number of Active Consumers

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34445-I

Log Dead Messages

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34446-I

Current Number of Messages in Dead Message Queue

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34447-I

Current Total Message Bytes in Dead Message Queue

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34448-I

Truncate Message Body in Dead Message Queue

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34454-I

aa....aaSuccessfully quiesced the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a Broker is quiesced normally.

KDAN34466-I

aa....aaSuccessfully listed broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the Brokers are listed normally.

KDAN34476-I

aa....aaSuccessfully listed JMX Connectors.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the JMX connectors are listed normally.

KDAN34483-I

aa....aaSuccessfully destroyed the connection.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when a connection is destroyed normally.

KDAN34485-I

Broker is Embedded

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34486-I

Held in Transaction

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34487-I

Actual

Description

This message is displayed when the destination is queried using the cjmsicmd query dst command.

KDAN34492-I

aa....aaSuccessfully unquiesced the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the Broker is unquiesced normally.

KDAN34494-I

aa....aaSuccessfully sent command to shutdown the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the command to shutdown the Broker is sent normally.

KDAN34495-I

Waiting for broker at aa....aa to shutdown...

aa....aa: Host name: Port value

Description

This message is displayed when waiting for the Broker to shutdown.

KDAN34497-I

Instance Configuration/ Data Root Directory

Description

This message is displayed when the Broker is queried using the cjmsicmd query bkr command.

KDAN34499-I

aa....aaSuccessfully reset the broker.

aa....aa: Broker host name and port number (information about this argument is output only to the management command log)

Description

This message is displayed when the Broker is reset normally.

KDAN34504-I

Setting System Property: aa....aa=bb....bb

aa....aa: Property name

bb....bb: Property value

Description

This message is displayed when a property is specified using the -D option.

KDAN34508-I

Listing messages for the destination

Description

This message is displayed when listing the messages for the destination.

KDAN34509-I

Successfully listed messages.

Description

This message is displayed when the messages are listed normally.

KDAN34511-I

Successfully destroyed message.

Description

This message is displayed when the messages are destroyed normally.

KDAN34513-I

Purging all the destinations

Description

This message is displayed when all the destinations are purged.

KDAN34514-I

Skipping destination:aa....aa.

aa....aa: Destination name

Description

This message is displayed when the destination type is Admin during the destruction or purging of the destinations.

KDAN34515-I

Successfully purged queue aa....aa

aa....aa: Queue name

Description

This message is displayed when a queue is purged normally.

KDAN34516-I

Successfully purged topic aa....aa.

aa....aa: topic name

Description

This message is displayed when a topic is purged normally.

KDAN34518-I

Destroying all the destinations

Description

This message is displayed when all the destinations are destroyed.

KDAN34519-I

Successfully destroyed queue aa....aa

aa....aa: Queue name

Description

This message is displayed when a queue is destroyed normally.

KDAN34520-I

Successfully destroyed topic aa....aa.

aa....aa: Topic name

Description

This message is displayed when a topic is destroyed normally.

KDAN34522-I

Successfully queried message.

Description

This message is displayed when a message is queried normally.

KDAN34523-I

Problems connecting to the broker.

Description

This message is displayed when a Broker has been stopped.

KDAN34526-I

Data received back from broker:

Description

This message is displayed when data is being received from the Broker while using the -debug option.

KDAN34527-I

No additional data received back from broker.

Description

This message is displayed when data is being received from the Broker while using the -debug option.

KDAN34528-I

BrokerAdmin defaultTimeout set to: aa....aa.

aa....aa: Default timeout value

Description

This message is displayed when the Broker Admin default timeout value is set up.

KDAN34529-I

BrokerAdmin defaultNumRetries set to: aa....aa

aa....aa: Default retry count

Description

This message is displayed when the Broker Admin default retry count is set up.

KDAN34530-I

BrokerAdmin num retries set to: aa....aa

aa....aa: Retry count

Description

This message is displayed when Broker Admin retry count is set up.

KDAN34531-I

Destroying message:

Description

This message is displayed when a message is destroyed.

KDAN34532-I

In the destination

Description

This message is issued before displaying the destination information.

KDAN34535-I

Querying message:

Description

This message is displayed when a message is queried.

KDAN34536-I

DEBUG message sent successfully.

Description

This message is displayed when a debug message is sent normally while using the -debug option.

KDAN34537-I

Sending the following DEBUG message:

Description

This message is displayed when a debug message is sent normally while using the -debug option.

KDAN34538-I

Optional properties:

Description

This message displays optional properties.

KDAN34539-I

The values '-1 or 0' can be used to specify 'unlimited' for the following Queue/ Topic attributes:

Description

This message displays the queue/ topic attributes for which -1 or 0 can be set up as the unlimited value.

KDAN34540-I

The values '-1 or 0' can be used to specify 'unlimited' for the following Broker attributes:

Description

This message displays the Broker attributes for which -1 or 0 can be set up as the unlimited value.

KDAN34541-I

cjmsicmd command was executed specified by:aa....aa

aa....aa: User-specified argument

Description

This message is displayed when some argument is specified for the cjmsicmd command.

KDAN34542-I

aa....aa The durable subscription was not destroyed.

aa....aa: Broker host name and port number (information about this argument is only output to the management command log)

Description

This message is displayed when the user ignores the execution of the operation and when an invalid value is specified for the argument, while a persistence subscriber is being deleted.

KDAN34543-I

aa....aa The destination was not compacted.

aa....aa: Broker host name and port number (information about this argument is only output to the management command log)

Description

This message is displayed when an invalid argument is specified while compressing the destination.

The message is also displayed when the user ignores the operation.

KDAN34544-I

aa....aa The destinations were not compacted.

aa....aa: Broker host name and port number (information about this argument is only output to the management command log)

Description

This message is displayed when an invalid argument is specified while compressing multiple destinations.

The message is also displayed when the user ignores the operation.

KDAN34545-I

aa....aa The destinations were not purged.

aa....aa: Broker host name and port number (information about this argument is only output to the management command log)

Description

This message is displayed when an invalid argument is specified while destroying the message.

The message is also displayed when the user ignores the operation.

KDAN34546-I

aa....aa The destination was not resumed.

aa....aa: Broker host name and port number (information about this argument is only output to the management command log)

Description

This message is displayed if the user ignores the operation, or if an invalid argument is specified when the delivery of messages to the destination is resumed.

KDAN34547-I

aa....aa The destinations were not paused.

aa....aa: Broker host name and port number (information about this argument is only output to the management command log)

Description

This message is displayed if the user ignores the operation, or if an invalid argument is specified when the delivery of messages to multiple destinations is paused.

KDAN34548-I

aa....aa The destinations were not resumed.

aa....aa: Broker host name and port number (information about this argument is only output to the management command log)

Description

This message is displayed if the user ignores the operation, or if an invalid argument is specified when the delivery of messages to multiple destinations is resumed.

KDAN38004-Q

Are you sure you want to destroy this destination? (y/ n)[n]

Description

This message is displayed when an attempt is made to destroy a destination.

KDAN38005-Q

Are you sure you want to purge this destination? (y/ n)[n]

Description

This message is displayed when an attempt is made to purge a destination.

KDAN38006-Q

Are you sure you want to pause this broker? (y/ n)[n]

Description

This message is displayed when an attempt is made to pause a destination.

KDAN38007-Q

Are you sure you want to pause this service? (y/ n)[n]

Description

This message is displayed when an attempt is made to pause a service.

KDAN38008-Q

Are you sure you want to resume this broker? (y/ n)[n]

Description

This message is displayed when an attempt is made to resume a Broker.

KDAN38009-Q

Are you sure you want to resume this service? (y/ n)[n]

Description

This message is displayed when an attempt is made to resume a service.

KDAN38010-Q

Are you sure you want to shutdown this broker? (y/ n)[n]

Description

This message is displayed when an attempt is made to shutdown a Broker.

KDAN38011-Q

Are you sure you want to restart this broker? (y/ n)[n]

Description

This message is displayed when an attempt is made to restart a Broker.

KDAN38012-Q

Are you sure you want to update this broker? (y/ n)[n]

Description

This message is displayed when an attempt is made to update a Broker.

KDAN38013-Q

Are you sure you want to update this service? (y/ n)[n]

Description

This message is displayed when an attempt is made to update a service.

KDAN38014-Q

Are you sure you want to update this destination? (y/ n)[n]

Description

This message is displayed when an attempt is made to update a destination.

KDAN38015-Q

Are you sure you want to destroy this durable subscription? (y/ n)[n]

Description

This message is displayed when an attempt is made to destroy a durable subscriber.

KDAN38021-Q

Are you sure you want to purge this durable subscription? (y/ n)[n]

Description

This message is displayed when an attempt is made to purge a durable subscriber.

KDAN38022-Q

Are you sure you want to pause this destination? (y/ n)[n]

Description

This message is displayed when an attempt is made to pause a durable subscriber.

KDAN38023-Q

Are you sure you want to resume this destination? (y/ n)[n]

Description

This message is displayed when an attempt is made to resume a durable subscriber.

KDAN38024-Q

Are you sure you want to compact this destination? (y/ n)[n]

Description

This message is displayed when an attempt is made to compress a destination.

KDAN38025-Q

Are you sure you want to compact all the destinations? (y/ n)

Description

This message is displayed when an attempt is made to compress all the destinations.

KDAN38026-Q

Are you sure you want to pause all the destinations? (y/ n)[n]

Description

This message is displayed when an attempt is made to pause all the destinations.

KDAN38027-Q

Are you sure you want to resume all the destinations? (y/ n)[n]

Description

This message is displayed when an attempt is made to resume all the destinations.

KDAN38028-Q

Are you sure you want to quiesce this broker? (y/ n)[n]

Description

This message is displayed when an attempt is made to quiesce a Broker.

KDAN38029-Q

Are you sure you want to takeover the broker? (y/ n)[n]

Description

This message is displayed when an attempt is made to takeover a Broker.

KDAN38030-Q

Are you sure you want to destroy this connection? (y/ n)[n]

Description

This message is displayed when an attempt is made to destroy a connection.

KDAN38031-Q

Are you sure you want to unquiesce this broker? (y/ n)[n]

Description

This message is displayed when an attempt is made to unquiesce a Broker.

KDAN38032-Q

Are you sure you want to reset this broker? (y/ n)[n]

Description

This message is displayed when an attempt is made to reset a Broker.

KDAN38033-Q

The state of this transaction is aa....aa.

Are you sure you want to rollback this transaction? (y/ n)[n]

aa....aa: Transaction state

Description

This message is displayed when an attempt is made to roll back a transaction.

KDAN38034-Q

Are you sure you want to commit this transaction? (y/ n)[n]

Description

This message is displayed when an attempt is made to commit a transaction.

KDAN38035-Q

Are you sure you want to destroy this message? (y/ n)[n]

Description

This message is displayed when an attempt is made to destroy a message.

KDAN38036-Q

Are you sure you want to purge all the destinations? (y/ n)[n]

Description

This message is displayed when an attempt is made to purge all the destinations.

KDAN38037-Q

Are you sure you want to destroy all the destinations? (y/ n)[n]

Description

This message is displayed when an attempt is made to destroy all the destinations.

5 KDCC (Messages Output by the SOAP Application Development Support Function)

This chapter describes the messages that are output when you use the SOAP application development support function and the SOAP Communication Infrastructure.

5.1 Format for describing the messages

The format for describing the messages in this chapter is as follows:

XXXXXnnnn-Y

Message text

Description

Supplementary explanation for the message text

Action

Action performed by the user

The description of each item is as follows:

XXXXXnnnn

This indicates a message ID.

Y

This indicates the message type.

Message text

This indicates the message contents.

The part enclosed within <> in the message indicates that the output contents might differ depending on the status during the message output or depending on the error target.

Description

This indicates the supplementary explanation such as the factors due to which the message is reported and configuration software operations that output the message.

Action

This indicates the actions performed by the user.

The format of a message ID, message type, and Message text differs depending on the type of the output message. The format for each type of output message is described from the subsection 5.1.1 onwards. Furthermore, the details about each message are described in the order of the message IDs from the section 5.2 onwards.

5.1.1 Format of the messages (KDCCP) output by the C4Fault class

This subsection describes the format of the messages output by the C4Fault class. Of the messages beginning with KDCCP, the messages that begin with KDCCP30 are output when you use DII. For details about the formatting the messages that are output when you use DII, see 5.1.10 Format of the messages (KDCCP30) output when using DII.

FaultCode: Fault code

FaultString: Message text

FaultActor: Fault creator

FaultDetail: Fault details

The description of each item is as follows:

FaultCode: Fault code

The Fault code consists of a prefix and a local part. The Fault code format is as follows:

{Prefix}Local part

Prefix

{http://c4web.cosminexus.com} will be output.

Local part

A string beginning with Server. or Client. will be output.

You can use the getFaultCode method of the C4Fault class to acquire the value of the Fault code.

FaultString: Message text

This indicates the message text. The Message text consists of a message ID, message type, and the message contents.

The message format is as follows:

KDCCPnnnn-Y Message text

The description of each item is as follows:

KDCCPnnnn

This indicates a message ID.

The elements configuring a message ID are as follows:

KDCCP

This indicates the prefix of the messages output by the C4Fault class.

nnnn

This indicates the message number managed in the C4Fault class. A unique four-digit number is assigned to each message.

Y

This indicates the message type. The message type of the C4Fault class is as follows:

E(ERROR): This message reports that a failure has occurred.

Message text

This indicates the message contents.

The value of the Message text can be acquired with the getFaultString method of the C4Fault class.

FaultActor: Fault creator

The Fault creator can be acquired with the getFaultActor method of the C4Fault class.

FaultDetail: Fault details

You can use the getFaultDetails method to acquire the C4Fault class.

5.1.2 Format of the messages (KDCCE05) output by the C4Exception class

The format of the messages output by the C4Exception class is as follows:

Message: Message text

The Message text includes a message ID, message type, and the message contents. The message format is as follows:

KDCCE05nn-Y Message text

The description of each item is as follows:

KDCCE05nn

This indicates a message ID.

The elements configuring a message ID are as follows:

KDCCE

This indicates the prefix of the messages output by the C4Exception class.

05nn

This indicates the message number managed in the C4Exception class. A unique four-digit number with the first two digits as 05 is assigned to each message.

Y

This indicates the message type. The message type of the C4Exception class is as follows:

E(ERROR): This message reports that a failure has occurred.

Message text

This indicates the message contents.

You can use the getMessage method of the C4Exception class to acquire the value of the Message text.

5.1.3 Format of the messages (KDCCE06, KDCCE9, and KDCCS30) output by the SOAP Engine

The format of the messages output by the SOAP Engine is as follows:

XXXXXnnnn-Y Message text

The description of each item is as follows:

XXXXXnnnn

This indicates a message ID.

The elements configuring a message ID are as follows:

XXXXX

This indicates the prefix of the messages output by the SOAP Engine. Prefix is shown with five alphabetic characters.

nnnn

This indicates the message number managed in SOAP engine. A unique four-digit number is assigned to each message.

The messages output by the SOAP Engine are indicated by the following three types of message IDs:

KDCCE06nn

KDCCE9nnn

KDCCS30nn

Y

This indicates the message type. The following types of messages are output by the SOAP Engine:

E (ERROR): This message reports that a failure has occurred.

I (INFORMATION): This message reports information.

W (WARN): This message reports a warning.

Message text

This indicates the message contents.

5.1.4 Format of the messages (KDCCR) output by the UDDI client library

The format of the messages output by the UDDI client library is as follows:

KDCCRnnnn-Y Message text

The description of each item is as follows:

KDCCRnnnn

This indicates a message ID.

The elements configuring a message ID are as follows:

KDCCR

This indicates the prefix of the messages output by the UDDI client library.

nnnn

This indicates the message number managed in UDDI client library. A four-digit number is assigned to each message.

1001 to 1999: Messages related to Connection

2001 to 2999: Messages related to Querymanager or LifeCycleManager

3000 onwards: Other messages

Y

This indicates the message type.

The following types of messages are output by the UDDI client library:

E (ERROR): This message reports that a failure has occurred.

W (WARN): This message reports a warning.

Message text

This indicates the message contents.

5.1.5 Format of the messages (KDCCC) output by development support commands

The format of the messages output by the development support commands is as follows:

KDCCCnnnn-Y Message text

The description of each item is as follows:

KDCCCnnnn

This indicates a message ID.

The elements configuring a message ID are as follows:

KDCCC

This indicates the prefix of the messages output by the development support commands.

nnnn

This indicates the message number managed in the development support command. A unique four-digit number is assigned to each message.

Y

This indicates the message type.

The following types of messages are output by the development support commands:

E (ERROR): This message reports that a failure has occurred.

I (INFORMATION): This message reports information.

W (WARN): This message reports a warning.

Message text

This indicates the message contents.

5.1.6 Format of the messages (KDCCS1151 to KDCCS1199) output during the size check of the transmission data

The format of the messages output during the size check of the transmission data is as follows:

KDCCSnnnn-Y Message text

The description of each item is as follows:

KDCCSnnnn

This indicates a message ID.

The elements configuring a message ID are as follows:

KDCCS

This indicates the prefix of the messages output during the size check of the transmission data.

nnnn

This indicates the message number managed during the size check of the transmission data. A unique four-digit number is assigned to each message.

Y

This indicates the message type. The following types of messages are output during the size check of the transmission data:

E (ERROR): This message reports that a failure has occurred.

Message text

This indicates the message contents.

5.1.7 Format of the messages (KDCCS1001 to KDCCS1150) output by SAAJ

The format of the messages output by SAAJ is as follows:

Message: Message text

The Message text includes a message ID, message type, and the message contents. The message format is as follows:

KDCCSnnnn-Y Message text

The description of each item is as follows:

KDCCSnnnn

This indicates a message ID.

The elements configuring a message ID are as follows:

KDCCS

This indicates the prefix of the messages output by SAAJ.

nnnn

This indicates the message number managed in SAAJ. A unique four-digit number is assigned to each message.

Y

This indicates the message type. The following types of messages are output by SAAJ:

E (ERROR): This message reports that a failure has occurred.

Message text

This indicates the message contents.

5.1.8 Format of the messages (KDCCT0) output during the acquisition of the PRF trace

The format of the messages output during the acquisition of the PRF trace is as follows:

KDCCT0nnn-Y Message text

The description of each item is as follows:

KDCCT0nnn

This indicates a message ID.

The elements configuring a message ID are as follows:

KDCCT

This indicates the prefix of the messages output during the acquisition of the PRF trace.

0nnn

This indicates the message number managed during the acquisition of the PRF trace. A unique four-digit number with the first digit as 0 is assigned to each message.

Y

This indicates the message type. The following types of messages are output during the acquisition of the PRF trace:

E (ERROR): This message reports that a failure has occurred.

W (WARN): This message reports a warning.

Message text

This indicates the message contents.

5.1.9 Format of the messages (KDCCT1) output by the trace functionality

The format of the messages output by the trace functionality is as follows:

KDCCT1nnn-Y Message text

The description of each item is as follows:

KDCCT1nnn

This indicates a message ID.

The elements configuring a message ID are as follows:

KDCCT

This indicates the prefix of the messages output by the trace functionality.

1nnn

This indicates the message number managed in the trace function. A unique four-digit number with the first digit as 1 is assigned to each message.

Y

This indicates the message type. The following types of messages are output by the trace functionality:

I (INFORMATION): This message reports information.

Message text

This indicates the message contents.

5.1.10 Format of the messages (KDCCP30) output when using DII

The format of the messages output when using DII is as follows:

KDCCP30nn-Y Message text

The description of each item is as follows:

KDCCP30nn

This indicates a message ID.

The elements configuring a message ID are as follows:

KDCCP

This indicates the prefix of the messages output when using DII.

30nn

This indicates the message number of the messages that are output when using DII. A unique four-digit number with the first two digits as 30 is assigned to each message.

Y

This indicates the message type.

The following types of messages are output by the trace functionality:

E (ERROR): This message reports that a failure has occurred.

W (WARN): This message reports a warning.

Message text

This indicates the message contents.

5.1.11 Precautions

The precautions for the messages output by the SOAP Engine are as follows:

The messages KDCCE0601-W, KDCCE0602-W, KDCCE0605-W, KDCCE0611-W, KDCCE0614-E, KDCCE0615-E, KDCCE0620-I, KDCCE0621-W, and KDCCE9000-E might be output in the default trace.

The message KDCCE0608-W is displayed on the window when the SOAP application is executed from the command line.

The message KDCCE0610-E is output in the message log of the Application Server, and also on the console window.

5.2 Messages from KDCCC0001 to KDCCC9999

This section describes the messages from KDCCC0001 to KDCCC9999 output by the development support commands.

KDCCC0001-I

The command finished normally.

Description

The command terminated normally.

Action

Not required.

KDCCC0011-E

A library required for command execution was not found. (details = detailed-information)

Description

The library required for command execution is either not found or is incompatible.

Action

See the description about the development support commands in the manual uCosminexus Application Server SOAP Application Development Guide.

KDCCC0012-E

A command could not be executed. (details = detailed-information)

Description

The command could not be executed because of detailed-information.

Action

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

If the WSDL2Java command is executed, specify the -C option, and then re-execute the command.

KDCCC0013-E

An attempt to analyze the WSDL definition has failed. (details = detailed-information)

Description

The WSDL analysis could not be executed because of detailed-information.

Action

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

If the WSDL2Java command is executed, specify the -C option, and then re-execute the command.

KDCCC0014-E

An attempt to copy files failed.

Description

An attempt to copy the file has failed.

Action

Revise the directory permissions, and then re-execute the command.

KDCCC0101-E

The specified class class-name cannot be converted to an xml schema data type. The type anyType will be used. (details = bean)

Description

The class-name class is not a bean class and cannot be converted to an XML schema data type.

Define the class as the anyType type of XML schema based on the WSDL definition.

Action

Either make the changes such that the class-name class is not used as an argument of the target class or do not generate a WSDL for the methods containing the class-name class.

KDCCC0102-E

The specified class class-name cannot be converted to an xml schema data type. The type anyType will be used. (details = package)

Description

The class-name class is defined as the java or javax package, and cannot be converted to an XML schema data type.

Action

Either make the changes such that the class-name class is not used as an argument of the target class or do not generate a WSDL for the methods containing the class-name class.

KDCCC0103-E

The specified class class-name cannot be converted to an xml schema data type. The type anyType will be used. (details = holders)

Description

The class-name class is defined as the org.apache.axis.holders package, and cannot be converted to an XML schema data type.

Action

Either make the changes such that the class-name class is not used as an argument of the target class or do not generate a WSDL for the methods containing the class-name class.

KDCCC0111-E

A WSDL2Java command timed out.

Description

The WSDL generation processing has timed out.

Action

Reset the timeout to a bigger value in the -O option.

KDCCC0121-E

The wsdl file has already been specified as, WSDL-file-name1. It cannot be specified again as WSDL-file-name2.

Description

The WSDL file is specified as WSDL-file-name-1. You cannot specify the WSDL file as WSDL-file-name2.

Action

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

KDCCC0122-E

The wsdl file was not specified.

Description

The WSDL file is not specified.

Action

Specify the WSDL file.

KDCCC0123-E

An option specification is incorrect. (details = detailed-information)

Description

A mistake described in detailed-information exists in the specification method of the option.

Action

Correct the mistake, and then re-execute the command.

KDCCC0131-E

A binding element was not found. (binding = binding-name)

Description

binding (binding-name) does not exist in the WSDL definition. Revise the value specified in port- binding=".." of the WSDL definition.

Action

Revise the WSDL definition, and then re-execute the command after correction.

KDCCC0132-E

A binding element was not found in the WSDL document WSDL-file-name. (binding = binding-name)

Description

binding (binding-name) does not exist in the WSDL definition WSDL-file-name. Revise the value specified in port-binding=".." of the WSDL definition.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0133-E

A portType element was not found. (portType = port-type-name)

Description

portType (portType-name) does not exist in the WSDL definition. Revise the value specified in binding-type=".." of the WSDL definition.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0134-E

A portType element was not found in the WSDL document WSDL-file-name. (portType = portType-name)

Description

portType (portType-name) does not exist in the WSDL definition (WSDL-file-name). Revise the value specified in binding-type=".." of the WSDL definition.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0135-E

The specified XML schema type data-type is not valid in XML schema version schema-version.

Description

The specified XML Schema type data-type is not valid in the Schema version "<Schema version>".

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0136-E

A specified XML schema type is not currently supported. (XML schema type = data-type)

Description

The specified XML Schema type data-type is not currently supported.

Action

Revise the WSDL definition, and then re-execute the command after correction.

KDCCC0137-E

A specified type is referenced but not defined. (type = data-type)

Description

The specified Type data-type is not defined.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0138-E

The specification of a type or ref attribute is incorrect. (element = element-name)

Description

The type attribute or ref attribute of element-name is incorrect.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0139-E

The specification of a parameterOrder attribute is incorrect. (element = element-name)

Description

Not all the part elements for sending are defined in the parameterOrder attribute of element-name.

Action

Define all the part element names for sending when specifying the parameterOrder attribute.

KDCCC0140-E

The specification of the part element used for input or output is incorrect. (element = element-name)

Description

element-name is not defined in the part attribute for sending or receiving.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0141-E

The part element lacks the element attribute or type attribute. (operation or fault element = element-name, part element = part-element-name)

Description

The element or type attribute is not specified in the Message part element part-element-name of the operation or fault element element-name.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0142-E

The binding operation element has no corresponding portType operation element. (binding operation name = element-name, input name = input-element-name, output name = output-element-name)

Description

The binding operation element does not correspond with the portType operation element.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0143-E

The name attribute of the fault element is incorrect. (binding = binding-element-name, operation = operation-element-name)

Description

The name attribute of the Fault element is incorrect.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0144-E

The soap:fault element is incorrect. (binding = binding-element-name, operation = operation-element-name, fault = fault-element-name)

Description

The soap:fault element of binding binding-element-name, operation operation-element-name, and Fault Fault-element-name is incorrect.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0145-E

The binding fault element does not match the portType fault element. (binding = binding-element-name, operation = operation-element-name, fault = fault-element-name)

Description

The description of binding fault fault-element-name and portType fault does not match in binding binding-element-name and operation operation-element-name.

Action

Revise the relationship between binding fault and portType fault, and then re-execute the command after correcting the WSDL definition.

KDCCC0146-E

The operation element requires the use attribute. (binding operation = operation-element-name)

Description

The use attribute is not specified in the binding operation operation-element-name.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0147-E

The specification of the service element's name attribute is incorrect.

Description

The name attribute of the service element is either not specified or is incorrect.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0148-E

The name attribute is not specified in the port element.

Description

The name attribute is not specified in the port element.

Action

Define the name attribute in the port element, and then re-execute the commands.

KDCCC0149-E

The binding attribute is not specified in the port element.

Description

The binding attribute is not specified in the port element.

Action

Define the binding attribute in the port element, and then re-execute the command.

KDCCC0150-E

The message attribute is not specified in a child element of the portType element.

Description

The value of the message attribute is not specified in any one of input, output, or fault of the portType element.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0151-E

The message attribute specified in a child element of the portType element is incorrect. (message = value-specified-for-message-attribute)

Description

The value specified for the message element value-specified-for-message-element in any one of <input>, <output>, or <fault> of the portType element is invalid.

Action

Revise the WSDL definition, and then re-execute the command after corrections.

KDCCC0161-E

The file cannot be opened. (file = file-name)

Description

The mapping file file-name of the name space and package name cannot be opened.

Action

Check whether the file exists.

If the file exists, check the access permission.

KDCCC0171-W

A file already exists. WSDL2Java cannot overwrite it. (file = file-name)

Description

The file-name file already exists. The file-name file is not overwritten.

Action

Revise the output destination, and re-execute the command as and when required.

KDCCC0172-E

A file already exists. (file = file-name)

Description

An error occurred when checking the existence of the file-name file. The file has not been created.

Action

If the file exists, revise the access permission of the file, and then re-execute the command.

KDCCC0181-E

The location attribute is not specified in the address element. (service = service-element-name, port = port-element-name)

Description

The location attribute does not exist in the address element of the service element service-element-name, and the port element port-element-name in the WSDL definition.

Action

Revise the specified value, and then re-execute the command.

KDCCC0182-E

The address element's location attribute is invalid. (service = service-element-name, port = port-element-name, location attribute value = location-attribute-value)

Description

The location attribute value location-attribute-value of the address element in the service element service-element-name, and the port element port-element-name of the WSDL definition are incorrect.

Action

Revise the specified value, and then re-execute the command.

KDCCC0191-E

A file name is duplicated. (file = file-name)

Description

The file-name to be generated is duplicated. There are elements with same package names for namespace.

Action

Revise the WSDL definition, and then re-execute the command.

If you change the package name, make sure to revise the contents also.

KDCCC0201-E

The class has already been specified as class-name1. It cannot be specified again as class-name2.

Description

The class name is specified as class-name1. You cannot specify the class name as class-name2.

Action

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

KDCCC0202-W

An option specification is incorrect. (option = -w, value = option-value)

Description

A value other than All, Interface, or Implementation is specified in the -w option.

All will be assumed.

Action

To specify a value other than All, revise the option value, and then re-execute the command.

KDCCC0203-E

An option specification is incorrect. (option = -T)

Description

A value other than 1.1 or 1.2 is specified in the -T option.

Action

Revise the option value, and then re-execute the command.

KDCCC0204-E

An option specification is incorrect. (option = -A)

Description

A value other than DEFAULT, NONE, or OPERATION is specified in the -A option.

Action

Revise the option value, and then re-execute the command.

KDCCC0205-E

An option specification is incorrect. (option = -u)

Description

A value other than LITERAL or ENCODED is specified in the -u option.

Action

Revise the option value, and then re-execute the command.

KDCCC0206-E

The class name is not specified.

Description

The class name is not specified.

Action

Specify the class name, and then re-execute the command.

KDCCC0207-E

An option is not specified. (option = -l)

Description

If All or Implementation is specified in the -w option, you must specify the -l option.

Action

Specify -l option, and then re-execute the process.

KDCCC0208-E

A specified class was not found. (class = class-name)

Description

The specified class does not exist.

Action

Revise the class name, and then re-execute the command.

KDCCC0211-W

An option specification is incorrect. The specified value will be ignored. (option = -d, value = option-value)

Description

The -d option is specified incorrectly.

Action

Revise the option value, and then re-execute the command.

The source is generated by assuming Request.

KDCCC0221-W

An option specification is incorrect. The system assumes an RPC was specified. (option = -p, value = option-value)

Description

A value other than RPC, EJB, or C4MSG is specified in the -p option.

Action

Revise the option value, and then re-execute the command.

KDCCC0222-I

An option is not specified. The system assumes an RPC was specified. (option = -p)

Description

The -p option is not specified.

RPC will be assumed.

Action

If you want to use a value other than RPC for creation, revise the option value, and then re-execute the command.

KDCCC0223-E

The option option-name1 cannot be specified when the specified value of option-name2 is option-value.

Description

The option-name1 option cannot be specified when the value of option-name2 is option-value.

Action

Revise the option value, and then re-execute the command.

KDCCC0224-E

A required option is not specified. (option = option-name)

Description

The mandatory option-name option is not specified.

Action

Revise the option value, and then re-execute the command.

KDCCC0225-E

The onMessage method is not defined in the specified class.

Description

The onMessage method does not exist in the specified class, and therefore, the -p option cannot be used if the value is C4MSG.

Action

Revise the option value, and then re-execute the command.

KDCCC0226-E

The specified class is not an EJB remote interface or EJB local interface.

Description

If EJB is specified in the -p option, specify the remote or local interface class of the EJB.

Action

Revise the option value, and then re-execute the command.

KDCCC0227-E

The value of the specified option is incorrect. (option = -z)

Description

A value other than RPC or DOCUMENT is specified in the -z option.

Action

Revise the option value, and then re-execute the command.

KDCCC0228-W

method-name method defined in the specified class was assumed to throw java.rmi.RemoteException. An implementation class of java.rmi.Remote including javax.ejb.EJBObject must throw it.

Description

The java.rmi.RemoteException exception does not exist in the throws clause of the method-name method defined in the specified class. An implementation class of java.rmi.Remote (including javax.ejb.EJBObject), or a method of the inherited interface must throw the java.rmi.RemoteException exception.

Action

Add the java.rmi.RemoteException exception to the throws clause of the method-name method.

KDCCC0229-W

exception-class-name exception of method-name method defined in the specified class was ignored.

Description

The exception-class-name exception included in the throws clause of the method-name method defined in the specified class was not processed. If this command terminates normally, the information related to the exception-class-name exception will not be included in the generated WSDL or the service deployment definition.

Action

Delete the exception-class-name exception from the throws clause of the method-name method.

KDCCC0230-W

java.rmi.RemoteException of method-name method defined in the specified class was ignored. An implementation class of javax.ejb.EJBLocalObject must not throw it.

Description

The java.rmi.RemoteException exception exists in the throws clause of the method-name method defined in the specified class. An implementation class of javax.ejb.EJBLocalObject or a method of the inherited interface must not throw the java.rmi.RemoteException exception.

Action

Delete the java.rmi.RemoteException exception from the throws clause of the method-name method.

KDCCC0231-E

Cannot generate exception class from complexType or element tag-name. Name "exception-class-name" is reserved.

Description

An exception class cannot be generated from the complex type or element tag-name. The name exception-class-name is reserved.

Action

Either revise the name space URI of tag-name or change the package name specified in the -N, -f, or -p option, and then re-execute the command.

KDCCC0232-E

The value option-value1 of the option option-name1 and the value option-value2 of the option option-name2 are exclusive.

Description

If option-value1 is specified as the value of option-name1, you cannot specify option-value2 as the value of option-name2.

Action

Revise the option value, and then re-execute the command.

KDCCC0233-I

The validation of the WSDL document was started. (WSDL document = option-value1)

Description

The validation of WSDL is started.

Action

Not required.

KDCCC0234-E

The WSDL document is invalid. The document has unsupported WSDL elements or attributes.

Description

Unsupported WSDL elements or attributes are used in the WSDL definition.

Action

Delete the unsupported WSDL elements or attributes from the WSDL definition.

KDCCC0235-E

The WSDL document is invalid. The document has unsupported MIME binding elements or attributes.

Description

Unsupported MIME binding elements or attributes are used in the WSDL definition.

Action

Delete the unsupported MIME binding elements or attributes from the WSDL definition.

KDCCC0236-E

The WSDL document is invalid. The document has unsupported XML Schema elements or attributes.

Description

Unsupported WSDL elements or attributes are used in the WSDL definition.

Action

Delete the unsupported XML Schema elements or attributes from the WSDL definition.

KDCCC0237-I

The validation of the WSDL document was finished successfully.

Description

The validation processing of the WSDL definition is completed successfully.

Action

Not required.

KDCCC0238-E

The type referenced by part-element-name of message-element-name is simple type or array.

Description

The type referenced by part-element-name of message-element-name is either a simple type or an array.

Action

Make the changes so as to reference a complex type, and then re-execute the command.

KDCCC0239-E

Multiple part elements or no part elements were found in message-element-name.

Description

Either 0, or multiple part elements are specified in message-element-name. Only one part element can be included in message-element-name.

Action

Correct the WSDL, and then re-execute the command.

KDCCC0240-E

The type attribute of the part element is specified when the style is document. (message = message-element-name, part = part-element-name)

Description

The type attribute is specified in the part element of the document or literal WSDL.

Action

Specify the element attribute in the part element of the document or literal WSDL.

KDCCC0245-E

An option specification is incorrect. (option = -C, --check).

Description

An invalid string is passed to the argument of the WSDL validation option of the WSDL2Java command.

Action

Revise the argument of the WSDL validation option, and then re-execute the command.

KDCCC0247-E

Cannot specify multiple "element1" elements in a single "element2" element.

Description

Multiple element1 elements are defined as the child elements of the element2 element. More than one element1 element cannot be specified in the element2 element.

Action

Revise the WSDL definition, and then re-execute the command.

KDCCC0263-E

Multiple part elements are defined in the message element when the style is document. (message = message-element-name)

Description

Multiple part elements are defined for one message element in the document or literal WSDL.

Action

Specify one or lesser part elements for one message element.

KDCCC0265-E

The specified URL is invalid. (option = -l/--location, specified url = specified-URL)

Description

An invalid URL is specified in the -l or --location option.

Action

Revise the URL, and specify a correct URL.

KDCCC0266-E

The style of all the operations in the wsdl:binding element is not the same. (binding = binding-element-name)

Description

Operations with different styles cannot be defined in the binding element.

Action

Specify the same style for all the operations in the binding element.

KDCCC0269-E

The overloaded method is not supported when the document style is specified. (method = method-name)

Description

If DOCUMENT is specified in the -z option, the interface containing the overloaded method cannot be specified.

Action

Change the method name.

KDCCC0271-E

The specified URL contains invalid character(s). (option = -l/--location, specified url = specified-URL)

Description

An invalid URL is specified in -l option.

Action

Unsupported characters have been used in the URL. Revise the URL, and specify a correct URL.

For a URL exceeding 128 bytes, only up to 128 bytes will be displayed in specified-URL. If the characters are not delimited at the 128th byte, the character displayed in the 128th byte will be different from the specified character.

KDCCC0272-E

The specified URL is too long. (option = -l/--location, specified url = specified-URL)

Description

An invalid URL is specified in -l option.

Action

The URL length exceeds 8,190 bytes. Revise the URL, and specify a correct URL.

Up to 128 bytes will be displayed in specified-URL. If the characters are not delimited at the 128th byte, the character displayed in the 128th byte will be different from the specified character.

KDCCC0273-E

The value of the address element's location attribute contains invalid character(s). (service = service-element-name, port = port-element-name, location attribute value = location-attribute-value)

Description

The location attribute value location-attribute-value of the address element in the service element service-element-name, and the port element port-element-name of the WSDL definition are incorrect.

Action

Unsupported characters are used in the value of the location attribute. Revise the value of the location attribute, and then re-execute the command.

If the value of the location attribute exceeds 128 bytes, only up to 128 bytes will be displayed in location-attribute-value. If the characters are not delimited at the 128th byte, the character displayed in the 128th byte will be different from the specified character.

KDCCC0274-E

The value of the address element's location attribute is too long. (service = service-element-name, port = port-element-name, location attribute value = location-attribute-value)

Description

The location attribute value location-attribute-value of the address element in the service element service-element-name, and the port element port-element-name of the WSDL definition are incorrect.

Action

The string length of the location attribute value exceeds 8,190 bytes. Revise the value of the location attribute, and then re-execute the command.

Up to 128 bytes will be displayed in location-attribute-value. If the characters are not delimited at the 128th byte, the character displayed in the 128th byte will be different from the specified character.

KDCCC0275-E

An unsupported XML Schema version is specified. (value = value, file = file-name)

Description

An unsupported version of XML Schema is used. (value = value, file = file-name).

Action

Revise the WSDL definition, and use http://www.w3.org/2001/XMLSchema.

KDCCC0276-W

The filename specified in the attribute-name attribute of element-name element is not a relative URI. The specified file is skipped. (attribute-name = value, file = file-name)

Description

The file specified in the attribute-name attribute of the element-name element is not a relative URI. The specified file is skipped (attribute-name = value, file = file-name).

The specification of a file name using various protocols, such as file, http, and ftp is not supported.

Action

Revise the WSDL definition, and describe the file path with a relative URI.

KDCCC0277-E

The file path specified by attribute-name attribute of element-name element is too long. Please specify it within 256 characters. (attribute-name = value, file = file-name)

Description

The file path specified in the attribute-name attribute of the element-name element is too long. Specify the file path within 256 characters (attribute-name = value, file = file-name).

Action

Revise the WSDL definition and make sure that after converting to absolute path, the number of characters is within 256 characters.

KDCCC0278-E

The XML Schema file specified in the schemaLocation attribute of import element is already imported. (namespace = namespace, schemaLocation= value, file = file-name)

Description

The XML Schema file specified in the schemaLocation attribute of the import element is already imported. (namespace = namespace, schemaLocation = value, file = file-name).

The same XML Schema file cannot be imported twice.

Action

Revise the XML Schema definition.

KDCCC0279-E

The namespace of "target-file-name" file specified in the element-name element does not match to that specified in the attribute-name attribute. (attribute-name = namespace, file = file-name)

Description

The namespace of the target-file-name file specified in the element-name element does not match the namespace specified in the attribute-name attribute (attribute-name = namespace, file = file-name).

Action

Revise the WSDL definition, and specify the same namespace.

KDCCC0280-E

A XML Schema definition has to be imported to refer the element or attribute of other namespaces. (namespace = value, file = file-name)

Description

The XML Schema definition must be imported to reference the elements and attributes of other namespace (namespace = value, file = file-name).

Action

Import the XML Schema definition with the xsd:import element.

KDCCC0281-E

The namespace "http://www.w3.org/2001/XMLSchema" cannot be imported. (file = file-name)

Description

Cannot import the namespace http://www.w3.org/2001/XMLSchema (file = file-name).

Action

Delete the import element in which http://www.w3.org/2001/XMLSchema is described.

KDCCC0282-W

A schemaLocation attribute of import element cannot be specified. (namespace = value, file = file-name)

Description

The schemaLocation attribute of the import element is not required (namespace = value, file = file-name).

Action

Delete the schemaLocation attribute of the import element.

KDCCC0283-E

A types element must be specified before all other elements (except documentation and import element) in a WSDL definition. (file = file-name)

Description

The types element must be defined before all other elements, except the documentation element and import element, in the WSDL definition (file = file-name).

Action

Revise the WSDL definition, and describe at the correct location.

KDCCC0284-E

A WSDL file structure specified in the import element of WSDL definition is invalid or the WSDL definition specified import element is invalid. (location = value, file = file-name, details = detailed-information)

Description

The WSDL file structure specified in the import element of the WSDL definition is invalid, or the WSDL definition describing the import element is incorrect (location = value, file = file-name, details = detailed-information).

Action

Revise the structure of the WSDL file. For details about the combination of each element of the WSDL definition, see the description about the combination of elements when the WSDL is imported in the manual uCosminexus Application Server SOAP Application Development Guide.

KDCCC0285-E

An import element must be specified before all other elements (except documentation element) in a WSDL definition. (file = file-name)

Description

The import element must be defined before all other elements, except the documentation element, in the WSDL definition (file = file-name).

Action

Revise the WSDL definition, and describe at the correct location.

KDCCC0286-E

A namespace attribute of import element does not exist in the XML Schema definition. (file = file-name)

Description

The namespace attribute of the import element does not exist in the XML Schema definition (file = file-name).

Action

Revise the XML Schema definition.

KDCCC0287-E

The XML shema file specified in the schemaLocation attribute of include element is already included. (targetNamespace = namespace, schemaLocation = value, file = file-name)

Description

The XML Schema file specified in the schemaLocation attribute of the include element has been already included (targetNamespace = namespace, schemaLocation = value, file = file-name).

The same XML Schema file cannot be included twice.

Action

Revise the XML Schema definition.

KDCCC0288-E

The WSDL file specified in the location attribute of import element is already imported. (namespace = namespace, location = value, file = file-name)

Description

The WSDL file specified in the location attribute of the import element has been already imported (namespace = namespace, location = value, file = file-name).

The same WSDL file cannot be imported twice.

Action

Revise the WSDL definition.

KDCCC0289-W

The namespace "namespace" has to be imported. (file = file-name)

Description

The namespace namespace must be imported (file = file-name).

Action

Import namespace.

KDCCC0290-E

The target namespace is not specified for targetNamespace attribute. (file = file-name)

Description

The namespace is not specified in the targetNamespace attribute (file = file-name). This message is output in the following cases:

When the value of the import source targetNamespace attribute or the import target targetNamespace attribute is omitted

When the combination of the values of the import source targetNamespace attribute and the import target targetNamespace attribute is a blank character

Action

Specify the target name space.

KDCCC0291-E

The percent-encoded valuefile has to be specified instead of the "value" which used in attribute-name attribute of element-name element. (percent-encoded value = percent-encoded-value, file = file-name)

Description

Specify a percent-encoded value for the value to be specified in the attribute-name attribute of the element-name element (percent-encoded value = percent-encoded-value, file = file-name).

Action

If a character string containing other than the reserved characters and unreserved characters stipulated in RFC3986 is used, the percent encoding must be performed in UTF-8.

Use the percent-encoded file name output in the message.

KDCCC0292-E

The percent-encoded value of the port element's name attribute is not equal the value of the end part of the URL path component. (service = service-element-name, port = port-element-name, name attribute value (percent-encoded) = percent-encoded-name-attribute-value, the end part of the URL path component = end-part-of-URL-path)

Description

After performing percent encoding for the value specified in the name attribute in the port element port-element-name of the service element service-element-name in the WSDL definition, percent-encoded-name-attribute-value and the end part of the URL path component end-part-of-URL-path specified in the location attribute of the address element do not match.

Action

Specify the value displayed in percent-encoded-name-attribute-value in the end part of the location attribute of the URLaddress element. However, if the length of the string exceeds 128 bytes, only the first 128 bytes will be displayed. In such a case, perform percent encoding for the value of the name attribute of port element in the encryption-format UTF-8 encoding, and specify the result in the end part of the location attribute of the address element.

If the length of the strings specified in service-element-name, port-element-name, percent-encoded-name-attribute-value, and end-part-of-URL-path exceeds 128 bytes, the end part will be truncated, and only the first 128 bytes will be displayed. If the characters are not delimited at the 128th byte, the character displayed in the 128th byte will be different from the specified character.

KDCCC0293-E

The value of the port element's name attribute is not equal the value of the end part of the URL path component. (service = service-element-name, port = port-element-name, the end part of the URL path component = end-part-of-URL-path)

Description

The value specified in the name attribute in the port element port-element-name of the service element service-element-name in the WSDL definition does not match the end part of the URL path component end-part-of-URL-path specified in the location attribute of the address element.

Action

Check the value of the name attribute of the port element and the location attribute of the address element, and specify the correct value.

If the length of the strings specified in service-element-name, port-element-name, and end-part-of-URL-path exceeds 128 bytes, the end part will be truncated, and only the first 128 bytes will be displayed. If the characters are not delimited at the 128th byte, the character displayed in the 128th byte will be different from the specified character.

KDCCC0295-I

The validation of the XML Schema document was started. (XML Schema document = file-name)

Description

The processing of the WSDL validation function has started (XML Schema document = file-name).

Action

Not required.

KDCCC0296-I

The validation of the XML Schema document was finished successfully.

Description

The processing of the WSDL validation function is completed successfully.

Action

Not required.

KDCCC0297-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.

KDCCC0298-E

An error occurred while the permissions were being checked.

Description

An error occurred while the permissions were being checked.

Action

The memory may be insufficient. Increase the free memory, and then re-execute the command. If the problem is still not resolved, contact the system administrator.

KDCCC0299-E

The XML Schema document is invalid. The document has unsupported XML Schema elements or attributes.

Description

Unsupported XML Schema elements or attributes are used in the XML Schema definition.

Action

Delete the unsupported XML Schema elements or attributes from the XML Schema definition.

KDCCC0300-E

The targetNamespace attribute of the importing schema must be different from the targetNamespace attribute of the schema which contains import. (targetNamespace = value, file = file-name)

Description

The value of the import target targetNamespace attribute must be different from the value of the import source targetNamespace attribute (targetNamespace = value, file = file-name).

Action

Revise the targetNamespace attribute.

KDCCC0301-W

The definition of the type QName-definition-type is duplicate.

Description

The definition of QName-definition-type is duplicate in the WSDL.

Action

Revise the WSDL, and if necessary, re-execute the command.

KDCCC0302-E

Element element-name is referenced but not defined.

Description

The element-name element is referenced, but is not defined.

Action

Revise the WSDL definition or XML Schema definition.

KDCCC0303-E

There is a wrong description in the WSDL definition. (file = file-name)

Description

The WSDL definition contains a wrong description (file = file-name).

Action

Delete the wrong description from the WSDL definition.

KDCCC0304-E

The file path of specified WSDL is invalid. (file = file-name)

Description

The file path of the specified WSDL is invalid (file = file-name).

Action

Make sure that no invalid characters are included in the file path of the specified WSDL.

KDCCC0305-E

The value of -z/--style option for Java2WSDL or Java2WSDD command is incorrect when using attachments. (-z = specified-value-for-option--z)

Description

The specification of the -z option of the Java2WSDL command or Java2WSDD command is invalid when attached files are used (-z = specified-value-for-option--z).

Action

Revise the options specified during the execution of the Java2WSDL command or the Java2WSDD command.

KDCCC0306-E

Attachments cannot be used when the style is rpc.

Description

If the style attribute of the soap:binding element in the WSDL definition is rpc, the attached file cannot be used.

Action

Revise the WSDL definition that is the input of the WSDL2Java command.

KDCCC0308-E

Attachments cannot be used in the xsd:attribute element in the WSDL definition. (attribute name = specified-attribute-value)

Description

The attached file cannot be used in the xsd:attribute element of the WSDL definition (attribute name = specified-attribute-name).

Action

Revise the WSDL definition that is the input of the WSDL2Java command.

KDCCC0309-E

Attachments cannot be used in the user definition exception.

Description

The attached file cannot be used in a user-defined exception.

Action

Revise the user-defined exception, and the contents of the Java class referenced from the user-defined exception.

KDCCC0310-E

Attachments cannot be specified as the type referenced by wsdl:fault element. (fault name = specified-fault-name)

Description

The attached file cannot be used in the element type referenced from the wsdl:fault element (fault name = specified-fault-name).

Action

Revise the WSDL definition that is the input of the WSDL2Java command.

5.3 Messages from KDCCE0501 to KDCCE0599

This section describes the messages from KDCCE0501 to KDCCE0599 output by the C4Exception class.

KDCCE0501-E

Message: KDCCE0501-E caught unexpected exception.

Description

An unexpected exception is caught during the processing of the SOAP client library.

Action

Contact system administrator.

KDCCE0550-E

Message: KDCCE0550-E Specified argument is invalid. argument = argument-name : value

Description

The argument is incorrect.

Action

Check if the specified argument is correct.

KDCCE0551-E

Message: KDCCE0551-E Specified file does not exist. file = argument, detail = detailed-information

Description

The specified file is incorrect. The invalid contents are described in detailed-information.

Action

Check the following contents depending on detailed-information:

does_not_exist

Make sure that the file specified in the argument exists.

Directory

Make sure that no directory name is specified in the argument.

FileNotFoundException

Make sure that access permission is available for the file specified in the argument.

KDCCE0553-E

Message: KDCCE0553-E java.lang.SecurityException occurred. file = argument, detail = getMessage()-value-for-security-exception

Description

The specified file cannot be read because the security manager is operating.

Action

Check the security settings for the specified file, or for the application.

KDCCE0558-E

Message: KDCCE0558-E The IO error occurred. details = detailed-information

Description

An I/O error occurred during the acquisition of the input stream of the attached file.

Action

Contact the system administrator.

5.4 Messages from KDCCE0601 to KDCCE0699, and the KDCCE9000 message

This section describes the messages from KDCCE0601 to KDCCE0699, and also the KDCCE9000 message output by the SOAP engine.

KDCCE0601-W

A trace-output error occurred. The default value was assumed.

Description

An error occurred during the initialization processing of the trace file output, and therefore, the trace file is output by assuming the default value.

Action

Specify the correct value for the trace output destination.

KDCCE0602-W

The property contains an invalid value. The default value will be used. key = key-name specified value = specified-value value to be used = assumed-value

Description

The property value specified in the operation definition file or in the setProperty method of the C4Property class is invalid, and therefore, the processing continues by assuming the default value.

Action

Specify the correct property value.

KDCCE0603-W

The client ID does not match the current thread client ID. current = current-client-ID specified value = specified-client-ID

Description

The value of the client identifier (client ID) specified in the disconnectClientIDtoCurrentThread method of the Management class is different from the value of the client identifier correlated to the current thread. Release the correlation of the current client identifier, and continue the processing.

Action

Specify the same identifier as the client identifier specified in the connectClientIDtoCurrentThread method of the Management class.

KDCCE0604-W

The local trace file which is not closed exists.

Description

An unclosed local trace file exists. Close the file forcibly.

Action

Confirm if the finalizeClient method of the Management class is invoked as many times as the initializeClient method of the Management class.

KDCCE0605-W

Summons frequency of finalizeClient method is unjust.

Description

The finalizeClient method of the Management class is invoked more than the required number of times. Ignore, and continue the processing.

Action

Confirm if the finalizeClient method of the Management class is invoked as many times as the initializeClient method of the Management class.

KDCCE0606-W

The client ID is not erased. client ID = client-ID

Description

The client ID value is still correlated to the thread. Ignore, and continue the processing.

Action

Confirm that the disconnectClientIDtoCurrentThread method of the Management class is invoked.

KDCCE0607-W

The specified argument is invalid. Class name = class-name Method name = method-name argument = argument-name

Description

A null argument has been specified. Ignore, and continue the processing.

Action

Revise the contents of the argument.

KDCCE0608-W

System property "cosminexus.home" is not specified.

Description

The system property cosminexus.home has not been specified.

Action

Specify the system property cosminexus.home in the command line argument, and then re-execute the command.

KDCCE0610-E

Failed to initialize the log file. File = file-path, Method = method-name, Detail = detailed-information

Description

An attempt to initialize the log file has failed.

Action

Remove the cause of the error based on detailed-information.

KDCCE0611-W

The "c4webcom.cfg" contains an invalid property value. The default value will be used. key = property-name specified value = specified-value value to be used = value-to-be-used

Description

The property value specified in the common definition file is invalid. The processing will continue by assuming the default value.

Action

Specify the correct property value.

KDCCE0612-E

UnsupportedOperationException was occurred. Detail = detailed-information

Description

The java.lang.UnsupportedOperationException exception occurred. The requested operation is not supported.

Action

Make sure that the unsupported operation is not invoked.

KDCCE0613-E

IllegalStateException was occurred. Detail = detailed-information

Description

The java.lang.IllegalStateException exception occurred. An invalid or inappropriate operation is performed. The status of the SOAP Engine does not correspond to the requested operation.

Action

Make sure that no invalid or inappropriate operation is performed.

KDCCE0614-E

Method not found. Method name = method-name, Service name = service-name

Description

The service cannot be invoked because the method-name method of the service-name service does not exist.

Action

Make sure that the method-name method of the service-name service is implemented. Also check that the arguments of the method implemented in the method-name method of the service-name service are correct.

KDCCE0615-E

Exception occurred while invoking a method on a service. Method name = method-name, Service name = service-name, Detail = detailed-information

Description

The exception described in detailed-information is thrown from the method-name method of the service-name service.

Action

Take action according to the contents of the exception.

KDCCE0616-W

The "server-config.xml" contains an invalid value. The default value will be used. tag = tag-name specified value = specified-value value to be used = assumed-value

Description

The value of the elements of the service deployment definition file is invalid. The processing will continue by assuming the default value.

Action

Specify the correct value for the elements.

KDCCE0617-E

The call to the SOAP service has failed. (Target endpoint address = target-URL-for-request-message, Service name = service-name, Operation name = operation-name, Service provider = service-provider, Style = style-attribute, Use = use-attribute)

Description

A failure occurred when invoking the SOAP service from the client.

Action

Confirm that no problem exists in the program by checking the information output in this message and in the message that is output immediately before this message.

KDCCE0618-E

The execution of the SOAP service has failed. (Service implementation class = service-implementation-class, Remote address = remote-IP-address, Protocol = protocol, Reqeust URL = target-URL-for-request-message, Service name = service-name, Operation name = operation-name, Service provider = service-provider, Style = style-attribute, Use = use-attribute)

Description

A failure occurred during the execution of a SOAP service in the server.

Action

Confirm that no problem exists in the program by checking the information output in this message and in the message that is output immediately before this message.

KDCCE0620-I

A session has timed out in service-name service. session ID = session-ID

Description

A session timeout occurred.

Action

Not required.

KDCCE0621-W

An active session exists in service-name service. A session is about to be invalidated. session ID = session-ID

Description

An active session exists. Deactivate the session.

Action

Implement the session termination processing.

KDCCE0622-W

A child node of the detail element is ignored because it is not an element node. (Ignored node name = ignored-node-name, Ignored node value = ignored-node-value)

Description

Nodes other than the Element node are ignored in the child nodes of the detail element.

Action

Not required.

KDCCE0631-I

The connection was closed because of the time out. (id = connection-object-ID, server_name = connected-server-name, server_port = connected-server-port-number, local_port = local-port-number, use_time = length-of-the-time-used-for-connection)

Description

The value obtained by subtracting the connection usage time from the current time exceeds the value specified in c4web.common.connection_pool.timeout, and the timeout occurs. Therefore, the connection is closed.

Action

Not required.

KDCCE0632-I

The connection was closed because it had reached the upper limit value of the number of times of use. (id = connection-object-ID, server_name = connected-server-name, server_port = connected-server-port-number, local_port = local-port-number, number_of_times = number-of-times-used-for-connection)

Description

The number of times the connection can be used reached the value specified in c4web.common.connection_pool.max_use. Therefore, the connection is closed.

Action

Not required.

KDCCE0633-I

The connection in the connection pool had been closed. (id = connection-object-ID, server_name = connected-server-name, server_port = connected-server-port-number, local_port = local-port-number)

Description

The connection in the connection pool has been already disconnected.

Action

Not required.

KDCCE0634-I

The number of connections with the server reached the upper limit value.

Description

The number of connections with the server has reached the value specified in c4web.common.connection_pool.max_connection.

Action

Not required.

KDCCE9000-E

A problem occurred in the SOAP engine. Detail = detailed-information

Description

A problem occurred in the SOAP Engine.

Action

Take action according to the contents of detailed-information. If the action to be taken according to detailed-information is not clear, contact the system administrator.

5.5 Messages from KDCCP0001 to KDCCP2999, and the KDCCP9000 message

This section describes the messages from KDCCP0001 to KDCCP2999, and also the KDCCP9000 message that is output by the C4Fault class.

KDCCP0001-E

FaultCode: {http://c4web.cosminexus.com}Client.ConnectionRefused

FaultString: KDCCP0001-E Connection to SOAP server was refused. details = detailed-information

FaultActor: none

FaultDetail: none

Description

A connection request to the SOAP service is denied. The possible causes are as follows:

The connection destination SOAP service or the J2EE server is not running.

The URL of the connection destination SOAP service is incorrect.

A problem exists in the network environment.

The cause of denial is described in detailed-information.

Action

Make sure that there is no problem in the cause described in detailed-information.

KDCCP0002-E

FaultCode: {http://c4web.cosminexus.com}Server.NoService

FaultString: KDCCP0002-E The SOAP engine could not find a target service to invoke. targetService is service-name

FaultActor: none

FaultDetail: none

Description

The service-name service is not registered.

Action

Make sure that the service-name service is deployed.

Make sure that the URL of the service-name service is correct.

KDCCP0003-E

FaultCode: {http://c4web.cosminexus.com}Server.ClassNotFound

FaultString: KDCCP0003-E Class file not found. Class name = class-name

FaultActor: none

FaultDetail: none

Description

The class file of the SOAP service specified with class-name does not exist.

The possible causes are as follows:

The service is not deployed as a J2EE application.

Action

Deploy the service according to the operation of the Management Server.

KDCCP0004-E

FaultCode: {http://c4web.cosminexus.com}Server.MethodNotFound

FaultString: KDCCP0004-E Method not found. Method name = method-name, Service name = service-name

FaultActor: none

FaultDetail: none

Description

The service cannot be invoked because the method-name method of the service-name service does not exist.

Action

Make sure that the method-name method of the service-name service is implemented. Also check that the arguments of the methods implemented in the method-name method of the service-name service are correct.

KDCCP0005-E

FaultCode: {http://c4web.cosminexus.com}Client.HTTPMessageNotPredicted

FaultString: KDCCP0005-E The HTTP message which is not predicted was received. Status Code = status-code, Reason Phrase = detailed-information, Content-Type = content-type

FaultActor: none

FaultDetail: none

Description

The SOAP client library received an unpredicted HTTP message. status-code describes the HTTP return code. detailed-information describes the HTTP return message. content-type describes the content type of the received HTTP message. If status-code is 0 and detailed-information and content-type are null, either of the following might have occurred:

- The connection pooling functionality is enabled and the HTTP server on which the connection destination SOAP service is running or other devices such as relay network equipment are not set up properly.

- The connection is disconnected in, for example, the network path between the SOAP client and the connection destination SOAP service.

Action

Make sure that the URL of the SOAP service is correct.

Check if the user authentication is required for the SOAP service.

If the user authentication is required for the SOAP service, make sure that there are no mistakes in the user ID and in the password specified in the URL of the SOAP service.

If the connection pooling functionality is enabled, make sure that the HTTP server on which the connection destination SOAP service is running and other devices such as relay network equipment are set up properly.

If there are no problems in the above details, contact the system administrator.

KDCCP0006-E

FaultCode: {http://c4web.cosminexus.com}Client.SOAPMessageNotPredicted, or {http://c4web.cosminexus.com}Server.SOAPMessageNotPredicted

FaultString: KDCCP0006-E The SOAP message which is not predicted was received. Detail = maintenance-information

FaultActor: none

FaultDetail: none

Description

When the local part of FaultCode begins with Client

The SOAP client library received an unpredicted SOAP message.

When the local part of FaultCode begins with Server

The SOAP Engine received an unpredicted SOAP message.

Action

Make sure that the URL of the SOAP service is correct.

Make sure that the characters other than a to z, A to Z, and underscores (_) are not used at the beginning of the names described in the WSDL definition of the service.

If there are no mistakes in the URL of the SOAP service or in the characters being used, contact the system administrator.

KDCCP0007-E

FaultCode: {http://c4web.cosminexus.com}Server.UserServiceException

FaultString: KDCCP0007-E caught the exception that was not predicted from user implementation service. Detail = detailed-information

FaultActor: none

FaultDetail: none

Description

The exception described in detailed-information is thrown from the SOAP service that is implemented by the user.

Action

Revise the implementation of the SOAP service.

KDCCP0009-E

FaultCode: {http://c4web.cosminexus.com}Client.SOAPHeaderNotModifiedNamespace, or {http://c4web.cosminexus.com}Server.SOAPHeaderNotModifiedNamespace

FaultString: KDCCP0009-E SOAP header is not modified namespace.

FaultActor: none

FaultDetail: none

Description

When the local part of FaultCode begins with Client

The names of the child elements of the SOAP header included in the SOAP message sent from the client are not modified. The SOAP message received by the client is also not modified.

When the local part of FaultCode begins with Server

The names of the child elements of the SOAP header that is included in the SOAP messages received by the SOAP Engine or the SOAP messages to be sent by the SOAP Engine are not modified.

Action

Make sure that the names of the child elements of the SOAP header are modified.

KDCCP0012-E

FaultCode: {http://c4web.cosminexus.com}Client.IOError, or {http://c4web.cosminexus.com}Server.IOError

FaultString: KDCCP0012-E The IO error occurred. details = detailed-information

FaultActor: none

FaultDetail: none

Description

An IO error has occurred.

Action

Take the following actions depending on detailed-information. The countermeasures corresponding to the respective detailed-information are as follows:

java.io.IOException: No serializer found for class-name1 in registry class-name2

The serializer corresponding to class-name1 does not exist in class-name2. Make sure that there are no mistakes in the service settings.

java.io.IOException: Cannot serialize a raw object

The java.lang.Object type cannot be used directly in the arguments or as a return value type. Use a type that inherits the java.lang.Object type.

In cases other than above

Make sure that there is no problem in the cause described in detailed-information.

KDCCP0013-E

FaultCode: {http://c4web.cosminexus.com}Server.ServiceException

FaultString: KDCCP0013-E Could not connect the JNDI service. details = detailed-information

FaultActor: none

FaultDetail: none

Description

An attempt to connect to the JNDI service has failed.

Action

Check that there is no mistake in the contents specified in JNDI name space of the EJB interface and in CORBA NamingService URL.

KDCCP0014-E

FaultCode: {http://c4web.cosminexus.com}Client.NoSOAPAction

FaultString: KDCCP0014-E No SOAPAction Header.

FaultActor: none

FaultDetail: none

Description

SOAPAction does not exist in the HTTP headers of the SOAP messages sent from the client.

Action

Either specify SOAPAction in the HTTP headers or set up the value of fault_omit_soapaction in the server definition file to false.

KDCCP0015-E

FaultCode: {http://c4web.cosminexus.com}Server.userException

FaultString: KDCCP0015-E The user definition exception occurred.exceptionName = exception-class-name

FaultActor: none

FaultDetail: exception-class-information

Description

A user-defined exception specified in exception-class-name is thrown from the SOAP service implemented by the user.

Action

Take action according to the contents of the exception.

KDCCP0016-E

FaultCode: {http://c4web.cosminexus.com}Server.ServiceException

FaultString: KDCCP0016-E Could not narrow <beanJNDIName> to <homeInterfaceName>. details = detailed-information

FaultActor: none

FaultDetail: none

Description

An attempt to downcast objects from beanJNDIName to homeInterfaceName has failed. The name specified in the -J option of the Java2WSDD command will be output in beanJNDIName. Also, the name specified in the -H option of the Java2WSDD command will be output in homeInterfaceName.

Action

Make sure that there is no mistake in the contents specified in the -J option and the -H option of the Java2WSDD command. Take action according to the contents of detailed-information. If you cannot take actions according to the contents of detailed-information, contact the system administrator.

KDCCP0020-E

FaultCode: {http://c4web.cosminexus.com}Server.InvalidContentType

FaultString: KDCCP0020-E Invalid content type. ContentType = content-type

FaultActor: none

FaultDetail: none

Description

The SOAP Engine received a request message of an unpredicted content-type.

Action

Make sure that the SOAP client is sending correct messages.

KDCCP0025-E

FaultCode: {http://schemas.xmlsoap.org/soap/envelope/}VersionMismatch

FaultString: KDCCP0025-E Invalid namespace associated with the SOAP envelope. Invalid namespace = namespace

FaultActor: none

FaultDetails: none

Description

The SOAP Engine cannot recognize namespace correlated to the SOAP envelope included in the received SOAP message.

Action

Specify http://schemas.xmlsoap.org/soap/envelope/ in namespace correlated to the SOAP envelope.

KDCCP0053-E

FaultCode: {http://c4web.cosminexus.com}Client.ConnectionNotAvailable

FaultString: KDCCP0053-E There is no connection that can be used. (connections_under_use = connection-under-use, connections_in_connection_pool=connections-in-connection-pool)

FaultActor: none

FaultDetails: none

Description

A usable connection does not exist.

Action

The possible causes are as follows. Take action depending upon the cause.

The value of c4web.common.connection_pool.max_connection is incorrect.

The upper-limit value of the file descriptor that can be used in the OS is less.

Other processes are inappropriately using too many file descriptors.

There are requests exceeding the processing performance of the J2EE server.

There is a request with an unduly long processing time.

KDCCP0054-E

FaultCode: {http://c4web.cosminexus.com}Client.MIMEMessageNotPredicted or {http://c4web.cosminexus.com}Server.MIMEMessageNotPredicted

FaultString: KDCCP0054-E An instance of the javax.activation.DataHandler class is invalid. (detail = detailed-information)

FaultActor: none

FaultDetails: none

Description

An instance of the javax.activation.DataHandler class is invalid.

Action

When generating the instances of the javax.activation.DataHandler class, make sure that the following points hold true in connection with the value specified in the constructor:

When instances are generated with the constructor DataHandler (DataSource)

Does the file that is specified during the generation of the javax.activation.FileDataSource object that is used as an argument exist?

Is the file path correct?

Is the access permission available for the file?

When instances are generated with the constructor DataHandler (Object, String)

Is the correct MIME type specified in the second argument?

Is the object corresponding to the MIME type specified in the first argument?

In other cases, take the action according to detailed-information.

KDCCP1106-E

FaultCode: {http://c4web.cosminexus.com}Server.NoService

FaultString: KDCCP1106-E=The CosminexusSOAP engine could not find a target service to invoke! targetService is service-name.

FaultActor: none

FaultDetails: none

Description

The service-name service is not registered.

Action

Make sure that the service-name service is deployed.

Make sure that the URL of the service-name service is correct.

KDCCP1403-E

FaultCode: {http://c4web.cosminexus.com}Server.IllegalState

FaultString: KDCCP1403-E The SOAP engine is not in an appropriate state for the requested operation. Detail = detailed-information1

FaultActor: none

FaultDetails: none

Description

An invalid or inappropriate operation was performed. The status of the SOAP Engine does not correspond to the requested operation.

Action

Take the following actions depending on the contents of detailed-information1:

An EJB object no longer exists. (detailed-information2)

An EJB object does not exist in the EJB container because of the error described in detailed-information2. Remove the cause described in detailed-information2.

java.rmi.ServerException: java.rmi.RemoteException: javax.ejb.ConcurrentAccessException: Concurrent method call is forbidden.;

The remove method is invoked during the EJB operation. Check the state of the EJB.

An attempt to get a domain name has failed. (detailed-information2)

The domain name cannot be acquired because of the error described in detailed-information2. Remove the cause described in detailed-information2.

KDCCP1404-E

FaultCode: {http://c4web.cosminexus.com}Server. UnsupportedOperation

FaultString: KDCCP1404-E The requested operation is not supported. Detail = detailed-information

FaultActor: none

FaultDetails: none

Description

The requested operation is not supported.

Action

Take the following action according to the contents of detailed-information:

Application scope does not permit a remove() invocation on EJBObject.

In an EJB form of service in which DeployScope is Application, you cannot invoke the remove method. Do not invoke the remove method.

KDCCP1405-E

FaultCode: {http://c4web.cosminexus.com}Server.IllegalState

FaultString: KDCCP1405-E The requested message has an invalid session Id.

FaultActor: none

FaultDetails: none

Description

An invalid session ID is included in the request message received by the server during the invocation of the service method in a SOAP application that uses RPC or EJB.

The possible causes are as follows:

When the scope is Session, the service method is invoked after the session is made invalid by invoking the C4Session.invalidate method in the service side.

When the scope is Session, the service method is invoked after the session is made invalid because of the session timeout.

Action

To inherit a session, make sure that the session is not invalid because of the timeout. Make changes in the processing at the client side in such a way so that the interval of the service method invocation does not exceed the timeout value.

Furthermore, after invoking the C4Session.invalidate method, do not use the same service class to invoke the service method. If a session need not be inherited, create a new service class object at the client side, and then invoke the method of the service class.

KDCCP1406-E

FaultCode: {http://c4web.cosminexus.com}Server.IllegalState

FaultString: KDCCP1406-E Cannot get a HTTP Session in service-name service. Detail = detailed-information

FaultActor: none

FaultDetails: none

Description

The HTTP session cannot be acquired.

Action

Revise the settings of the J2EE server according to the contents of detailed-information.

KDCCP1407-E

FaultCode: {http://c4web.cosminexus.com}Server. IndexOutOfBounds

FaultString: KDCCP1407-E Cannot create a new session as the limit on maximum number of sessions has already been reached available-session-numbers in service-name service.

FaultActor: none

FaultDetails: none

Description

A new session could not be created because the number exceeds the maximum value of the usable sessions.

Action

If necessary, increase the maximum value of the number of the usable sessions.

KDCCP9000-E

FaultString: KDCCP9000-E C4Fault exception occurred. Detail = detailed-information

Description

The C4Fault exception is thrown.

This message is output even when the C4Fault exception is thrown from a user-implemented SOAP application. In such a case, the value specified during the generation of the C4Fault class will be set up in FaultCode, FaultActor, and in FaultDetail.

Action

Take action according to the contents of detailed-information. If the action to be taken according to detailed-information is not clear, contact the system administrator.

5.6 Messages from KDCCP3000 to KDCCP3999

This section describes the messages from KDCCP3000 to KDCCP3999 output when using DII.

KDCCP3000-E

Illegal argument has been set. (Class name = class-name, Method signature = method-signature, argument = argument-name, value = argument-value)

Description

An invalid argument was specified.

Action

Specify a valid argument.

KDCCP3001-E

The class corresponding to the specified parameter name does not exist. (parameter name = parameter-name)

Description

The class corresponding to the specified parameter name does not exist.

Action

Check that the type of the class corresponding to the specified parameter name is supported.

KDCCP3002-E

The URL does not include a local file path. (Class name = class-name, Method signature = method-signature, argument = argument-name, value = argument-value)

Description

The URL is not the local file path.

Action

Specify a URL that includes a local file path beginning with the file scheme.

KDCCP3003-E

The requested operation is not supported. (Class name = class-name, Method signature = method-signature, argument = argument-name, value = argument-value)

Description

An unsupported method is invoked.

Action

Invoke a supported method.

KDCCP3004-E

Unsupported property name is specified. (Class name = class-name, Method signature = method-signature, argument = argument-name, value = argument-value)

Description

An unsupported property is specified.

Action

Specify a supported property.

KDCCP3005-E

The specified property does not exist. (Class name = class-name, Method signature = method-signature, argument = argument-name, value = argument-value)

Description

The specified property does not exist.

Action

Check that the specified property has been set up.

KDCCP3006-E

An attempt to create a Call object has failed. (Detail = detailed-information)

Description

An attempt to create a Call object has failed.

Action

Check that no problem exists in the program, based on the contents of Detail.

KDCCP3007-E

Illegal property value is specified. (Class name = class-name, Method signature = method-signature, property name = property-name, property value = property-value, reason = reason)

Description

An invalid property value was specified.

Action

Based on the reason, check that the specified property is valid.

KDCCP3008-E

An attempt to execute the invoke method has failed.(Class name = class-name, Method signature = method-signature, reason = reason)

Description

An attempt to execute the invoke method has failed.

Action

Based on the reason, check that there is no problem in the program.

KDCCP3010-E

An attempt to create a Service object has failed. (Detail = detailed-information1)

Description

An attempt to create a Service object has failed.

Action

Based on detailed-information1, check that there is no problem in the program.

detailed-information1

Failed to make the output directory. (WSDL file = WSDL-file-name, Detail = detailed-information2)

An attempt to create an output directory has failed. Based on the contents of detailed-information2, check the environment of the output directory.

Error processing WSDL document: detailed-information2.

An error occurred in the WSDL analysis process. Based on the contents of detailed-information2, check that there is no problem in the program.

Failed to compile the Java source file. (WSDL file = WSDL-file-name, Detail = detailed-information2)

An attempt to compile the Java source file has failed. Based on the contents of detailed-information2, check that there is no problem in the program.

Failed to load the Java class file. (WSDL file = WSDL-file-name, Detail = detailed-information2)

An attempt to load the Java class file has failed. Based on the contents of detailed-information2, check that there is no problem in the program.

Failed in the deletion of the Java source file or the Java class file. (WSDL file = WSDL-file-name, Detail = detailed-information)

An attempt to delete the Java class file has failed. Based on the contents of detailed-information, check the environment of the output directory.

Other messages

Based on the contents of the exception, either check that there is no problem in the program or contact the system administrator.

KDCCP3011-E

Output parameters are only available after invoke method has been called. (Class name = class-name, Method signature = method-signature)

Description

The OUTPUT parameters can be used after invoking the invoke method.

Action

Before invoking the invoke method, check that the OUTPUT parameters are acquired.

KDCCP3012-E

The specified value type for argument should be correct-value-type. (Class name = class-name, Method signature = method-signature, specified value type = specified-value-type)

Description

correct-value-type must be specified for the value type specified-value-type that is specified in argument.

Action

Change the value type specified-value-type specified in argument to correct-value-type.

KDCCP3013-W

The length of the specified path is invalid. The default directory is assumed and the processing is continued. specified value = specified-value, length = character-length-of-specified-value, default directory = default-directory

Description

The string length of the specified path is invalid. Continue the processing by assuming the default directory.

Action

Specify a directory with a string length between 1 to 128 characters.

KDCCP3014-W

The specified value is not an absolute path. The default directory is assumed and the processing is continued. specified value = specified-value, default directory = default-directory

Description

The specified value is not an absolute path. The processing is continued assuming the default directory.

Action

Specify the absolute path for the directory.

KDCCP3015-W

The specified path is not a directory. The default directory is assumed and the processing is continued. specified path = specified-value, default directory = default-directory

Description

The specified path is not for the directory. The processing is continued assuming the default directory.

Action

Specify a directory.

KDCCP3016-W

Failed in making the directory. The default directory is assumed and the processing is continued. specified directory = directory-name, default directory = default-directory

Description

An attempt to create the directory has failed. The processing is continued assuming the default directory.

Action

If the space is insufficient, either delete the unnecessary files and create some free space or specify a directory with free space. If the specified directory is invalid, check the following, and then change to a directory path that can be created:

Make sure that unusable characters are not used in the directory name as stipulated in the OS.

Make sure that instead of a directory name, a file name is not included in the path.

Make sure that access permission is available.

KDCCP3017-W

Cannot access the directory. The default directory is assumed and the processing is continued. specified directory = directory-name, default directory = default-directory

Description

The directory cannot be accessed. The processing is continued assuming the default directory.

Action

Check the directory access permission.

5.7 Messages from KDCCR1001 to KDCCR9999

This section describes the messages from KDCCR1001 to KDCCR9999 output by the UDDI client library.

KDCCR1001-E

Connection property "javax.xml.registry.queryManagerURL" is missing.

Description

The queryManagerURL property to be set up in the ConnectionFactory object or in the system property is either not specified or a null character string is specified.

Action

A valid value must be specified in the javax.xml.registry.queryManagerURL property with either of the following methods:

Set up javax.xml.registry.queryManagerURL in the Java system properties.

Set up javax.xml.registry.queryManagerURL in the Properties object, and then invoke ConnectionFactory#setProperties.

KDCCR1003-E

Authentication failed for the given Credentials.

Description

The user name or password specified in the Connection#setCredential method is invalid.

Action

Specify the correct user name and password in the setCredential method.

KDCCR1004-E

Bulk response is not found.Incorrect/Invalid connection mode.Check the connection mode.

Description

An invalid connection mode might have specified. This error occurs in the following cases:

When the getBulkResponse (requestID) method for RegistryService is executed in the synchronous connection mode

When an invalid or not existing requestID is specified in getBulkResponse

When BulkResponse is acquired with an already specified requestID

Action

Specify the correct connection mode (synchronous or asynchronous). The getBulkResponse method can be used in RegistryService that is generated from Connection of the asynchronous connection mode. Also check requestID specified in the getBulkResponse method. The getBulkResponse method cannot be invoked twice with the same requestID.

KDCCR1005-E

An Internal Error occurred while creating the Connection.

Description

This message occurs when the client program corresponds to any one of the following cases:

When the URL for queries or issues is not set up in properties

When the user name or password is not correct

When the authentication information cannot be acquired as and when required

Action

Specify the appropriate connection property.

KDCCR1006-E

JAXRProvider supports UDDI_GET_AUTHTOKEN authentication method only.

Description

In this program, only the get_authToken method of UDDI is supported as the method for accessing the authentication information. All other means of user authentication stipulated in JAXR are not supported.

Action

Specify the appropriate value in the javax.xml.registry.security.authenticationMethod property. Only UDDI_GET_AUTHTOKEN can be specified as a valid value.

KDCCR1007-E

An Internal Error occurred while closing the Connection.

Description

The connection cannot be closed because of the following reasons:

The Connection objects are not created properly.

The connection is already closed.

Action

Invoke the isClosed method to confirm that the connection is already closed. Make sure that the RegistryService instance the value of which is not null is returned by the getRegistryService method.

KDCCR1008-E

Cannot perform this operation, Connection is closed.

Description

The processing cannot be executed hereafter because the connection is already closed.

Action

Check that the Connection#close method for closing the connection is executed.

KDCCR1009-E

Invalid value set for Connection property "javax.xml.registry.queryManagerURL"/"javax.xml.registry.lifeCycleManagerURL".

Description

The format of the URL specifying QueryManager, LifeCycleManager, or both is invalid.

Action

Make sure that the format of the specified queryManagerURL and lifeCycleManagerURL is valid as a URL format.

KDCCR1104-W

Invalid value set for Connection property "javax.xml.registry.uddi.maxRows".

Description

An invalid value is specified in the javax.xml.registry.uddi.maxRows property. The processing will continue without specifying the value.

Action

Set up a specifiable value in the property.

KDCCR2001-E

Unexpected object type found in the Collection.

Description

The object type included in the Collection object specified in the parameter is invalid.

Action

Check the API name, and create the Collection object in such a way so that the Collection object includes valid objects.

For example, the saveService object must include the objects of the Service class.

KDCCR2002-E

IdentificationScheme is expected for ExternalIdentifier.

Description

The objects of the ExternalIdentifier class do not include the mandatory objects of the ClassificationScheme class.

Action

Create the correct ExternalIdentifier object.

KDCCR2003-E

Name is not present in ExternalIdentifier.

Description

The objects of the ExternalIdentifier class do not contain the mandatory Name attribute.

Action

Create the correct ExternalIdentifier object.

KDCCR2004-E

Value is not present in ExternalIdentifier.

Description

The objects of the ExternalIdentifier class do not contain the mandatory Value attribute.

Action

Create the correct ExternalIdentifier object.

KDCCR2005-E

Mutually Exclusive FindQualifiers present in the Collection.

Description

Mutually exclusive search conditions are specified in the collections of FindQualifiers.

Action

Mutually exclusive search conditions cannot be included in the Collection object as the collection of FindQualifiers. For example, SORT_BY_NAME_ASC (ascending order of the names) and SORT_BY_NAME_DESC (descending order of the names) are mutually exclusive search conditions. Delete either of these.

KDCCR2006-E

Invalid/Empty/Null Key found in the Collection.

Description

The value of the Key object included in the Collection object is invalid.

Action

The value of the Key object included in the Collection object cannot be an empty character string, null, or an invalid value. Create the Collection object such that the Collection object includes only the correct Key object.

KDCCR2007-E

Collection is Empty or Null.

Description

The Collection object is either empty or null.

Action

An empty or null Collection object cannot be specified in JAXR API. Create the Collection object in such a way so that the Collection object includes at least one object that is not null.

KDCCR2008-E

Method is not supported by JAXRProvider.

Description

This program does not support the method with Level 1 support level.

Action

Check the support level (Capability level), and do not use the method with Level 1 support level.

KDCCR2009-E

ClassificationScheme is expected for Concept Object.

Description

This error occurs when an attempt is made to create an internal Classification object in the client program having the Concept object specified as the parameter that is not correlated to any ClassificationScheme object.

Action

When issuing the createClassification (concept) method, make sure that the Concept object specified as the parameter contains the parent ClassificationScheme object.

KDCCR2010-E

Concept has a parent Concept or is under a ClassificationScheme.

Description

This error occurs when an attempt is made to create the ClassificationScheme object in the client program having the Concept object specified as the parameter that is correlated to the parent Concept or the ClassificationScheme object.

Action

When issuing the createClassificationScheme (concept) method, make sure that the Concept object specified as the parameter does not contain the parent Concept object or the ClassificationScheme object.

KDCCR2012-E

Objects in the collection should be of type javax.xml.registry.infomodel.SpecificationLink.

Description

When using the addSpecificationLinks method of the ServiceBinding object, the Collection object specified as the parameter must contain the SpecificationLink object.

Action

Create the correct Collection object.

KDCCR2013-E

Error in Setting AccessURI,cannot set both (TargetBinding and AccessURI) for javax.xml.registry.infomodel.ServiceBinding object.

Description

Both the TargetBinding and AccessURI attributes are specified.

Action

When the targetBinding attribute of the ServiceBinding object is null, make sure that the correct value that is not null is specified in the setAccessURI method.

KDCCR2014-E

Error in Setting TargetBinding,cannot set both (TargetBinding and AccessURI) for javax.xml.registry.infomodel.ServiceBinding object.

Description

Both the TargetBinding and AccessURI attributes are specified.

Action

When the accessURI attribute of the ServiceBinding object is null, make sure that the correct value that is not null is specified in the setTargetBinding method.

KDCCR2016-E

NamePattern is not specified in findClassificationSchemeByName.

Description

The string of the passed NamePattern parameter is either null or an empty string.

Action

To pass the NamePattern string as a parameter, specify a partially matching character string or a completely matching character string using wildcard characters.

KDCCR2017-E

Both the Classification value and the Concept value within the Classification are null.

Description

Both the Value attribute and the Concept attribute are not specified in the Classification object.

Action

Either set up a value in the Classification object with the setValue method or use the setConcept method to set up the Concept object, the value of which is not null.

KDCCR2018-E

LocalizedString cannot be null.

Description

An attempt is made to specify null in the Collection object of LocalizedString.

Action

Create the Collection object, the value of which is not null.

KDCCR2019-E

Objects of type javax.xml.registry.infomodel.LocalizedString expected in the Collection.

Description

The Collection object to be set up in InternationalString is not the same as the Collection object of LocalizedString.

Action

Create a proper Collection object.

KDCCR2020-E

Both SourceKeyId and TargetKeyId passed are Null.

Description

Null is passed to SourceKeyId and TargetKeyId.

Action

Specify the appropriate ID string for the relative source and relative target objects in the parameter.

KDCCR2021-E

The name/value of AssociationType is Null.

Description

The Name attribute or the Value attribute of the Concept object is null.

Action

Set up the Name attribute and the Value attribute in the Concept object.

KDCCR2022-E

Value of AssociationType is not valid.

Description

The value of the Concept object specified as the type (AssociationType) of the Association object is not the same value that is specified for the already defined Concept object.

Action

Use the value of the already defined Concept object that can be specified as AssociationType.

KDCCR2023-E

Authentication from Registry is needed.

Description

The authentication information is null.

Action

Provide the correct authentication information.

KDCCR2024-E

Key for Source Organization cannot be Null.

Description

The key of SourceObject is null.

Action

When creating the Association object, provide a key to the Source object.

KDCCR2025-E

KeyId for Source Organization cannot be Null.

Description

The contents of the key of SourceObject are null.

Action

When creating the Association object, provide the contents of key in the Source object.

KDCCR2026-E

Key for Target Organization cannot be Null.

Description

The key of TargetObject is null.

Action

When creating the Association object, provide the key of the Target object.

KDCCR2027-E

KeyId for Target Organization cannot be Null.

Description

The contents of the key of TargetObject are null.

Action

When creating the Association object, provide the contents of the key in the Target object.

KDCCR2028-E

User Name/Password is not set.

Description

The user name and password are not set up in the Connection object.

Action

Provide the authentication information for the user name and the password.

KDCCR2029-E

Requested interface name does not belongs to javax.xml.registry.infomodel package.

Description

The interface name requested as a parameter does not belong to the Infomodel class.

Action

Specify the requested interface name as an integer of the LifeCycleManager class.

Example: LifeCycleManager.SERVICE_BINDING

KDCCR2030-E

SourceObject is not of type javax.xml.registry.infomodel.Organization.

Description

The SourceObject type is different than Organization.

Action

The type of the Source object in the Association object to be created must be Organization.

KDCCR2031-E

TargetObject is not of type javax.xml.registry.infomodel.Organization.

Description

The TargetObject type is different than Organization.

Action

The type of the Target object in the Association object to be created must be Organization.

KDCCR2032-E

Slot cannot be Null.

Description

The slot for specifying parameters is null.

Action

Provide an object that is not null in the slot.

KDCCR2033-E

Collection of LocalizedString objects cannot be Null.

Description

Null is specified in the collection of LocalizedStrings.

Action

Provide a valid collection of LocalizedStrings in the addLocalizedString method.

KDCCR2035-E

URI is invalid or inaccessible.

Description

An invalid URI is specified.

Action

Specify the correct URI.

KDCCR2036-E

Cannot change data that is controlled by another party.

Description

An attempt is made to change the data of the object owned by another person.

Action

Only the owner of the object can modify the object.

KDCCR2037-E

Association object is Null.

Description

The Association object specified in the parameter is either null or invalid.

Action

Specify the correct Association object in the parameter that is not null.

KDCCR2038-E

Objects in the collection should be of type javax.xml.registry.infomodel.ExternalIdentifier.

Description

The objects of the ExternalIdentifier class are not specified in the Collection.

Action

Make sure that the objects specified in the Collection are those of the ExternalIdentifier class.

KDCCR2039-E

Association Key is not formed properly.

Description

The Association key is not created properly.

Action

Set up an appropriate key in the created Association object.

KDCCR2040-E

Association Key passed cannot be Null.

Description

The passed Association key is null.

Action

Pass a valid Association key that is not null.

KDCCR2041-E

Source Organization in Association cannot Null.

Description

Null is specified in the Source Organization of the Association object.

Action

Specify an Organization object other than null in the Source object.

KDCCR2042-E

Target Organization in Association cannot Null.

Description

Null is specified in the Target Organization of the Association object.

Action

Specify an Organization object other than null in the Target object.

KDCCR2043-E

Type of Object requested is empty or Null.

Description

The ObjectType passed as a parameter is either null or blank.

Action

Specify the ObjectType parameter as a valid parameter of the method. The ObjectType parameter is defined as an integer of the LifeCycleManager class.

Example: LifeCycleManager.ORGANIZATION

KDCCR2045-E

Unable to create an instance of ConnectionFactory.

Description

The ConnectionFactory object could not be created. The security settings of Java might not have been specified properly.

Action

Make sure to revise the security settings of Java. Contact the system administrator.

KDCCR2046-E

URL is malformed.

Description

An invalid protocol might be specified for the URL added to the objects saved in the registry server or the format of the URL might be invalid.

Action

Check that the protocol (such as http://) that is added to the URL string is correct. Also check that the format of the URL is valid.

KDCCR2047-E

Association Type is Null.

Description

Null is specified in the Association type of the Association object.

Action

If the Concept object that indicates the Association type is null, this message will be displayed. Check that the Association type (Concept object) is valid.

KDCCR2048-E

Error occurred while performing Input/Output.

Description

The SOAP message cannot be output in the byte row.

Action

Check whether the memory is insufficient. For other causes, contact the system administrator.

KDCCR2049-E

Host cannot be resolved.

Description

The IP address for the host cannot be found.

Action

Make sure that the host name and the IP address can be resolved properly.

KDCCR2050-E

Missing ResourceBundle/Property.

Description

The resource file used internally is invalid.

Action

Contact the system administrator.

KDCCR2051-E

DocumentBuilder instance could not be created as per the configuration requested.

Description

A critical configuration error occurred in the XML parser.

Action

Contact the system administrator.

KDCCR2052-E

I/O Exception occurred in opening connection at the URI.

Description

A connection could not be established to the URI specified in ExternalLink or ServiceBinding.

Action

Check that the specified URI can be connected properly.

If URI verification is not necessary, specify false in the setValidateURI method.

KDCCR2053-E

Classification or Concept name can not be Null.

Description

The name of the Concept or ClasificationScheme object is null.

Action

Specify a name in the Concept object that is specified during the invocation of the saveConcepts method or in the ClassificationScheme object that is specified during the invocation of the saveClassificationSchemes method.

KDCCR2054-E

Neither AccessURI nor TargetBinding is set to javax.xml.registry.infomodel.ServiceBinding object.

Description

Neither AccessURI nor TargetBinding is specified in the ServiceBinding object.

Action

Specify either AccessURI or TargetBinding in the ServiceBinding object.

KDCCR2055-E

BindingKey of TargetBinding cannot be Null/Empty.

Description

The binding key of TargetBinding specified in the ServiceBinding object is either null or blank.

Action

Specify a binding key that is neither null nor blank in TargetBinding.

KDCCR2056-E

ServiceKey cannot be Null.

Description

Null is passed to ServiceKey when searching the ServiceBinding object.

Action

Set up ServiceKey when searching the ServiceBinding object.

KDCCR2057-E

Name of the Organization must be specified.

Description

The name of the Organization object was not specified when saving Organization.

Action

Specify a name for the Organization object to be saved.

KDCCR2059-E

SpecifiedObject or its Key in SpecificationLink is Null/Empty/Invalid.

Description

Either the SpecifiedObject specified in the SpecificationLink object is invalid or the key of the specified SpecifiedObject is null or empty.

Action

Make sure that the SpecifiedObject specified in the SpecificationLink object is not invalid or the key of the SpecifiedObject is neither null nor empty.

KDCCR2060-E

Only one or none usageParameters can be set to the SpecificationLink object.

Description

Two or more usageParameters are specified in the SpecificationLink object.

Action

When specifying usageParameters in the SpecificationLink object, make sure that you specify only a single parameter.

KDCCR2061-E

Specifications Collection is Null or Empty.

Description

The Specifications parameter specified when searching the ServiceBinding object is either null or empty.

Action

When searching the ServiceBinding object, set up a value in the Specifications parameter.

KDCCR2062-E

UserName or Password is not set for Source Organization or Target Organization or Association Object.

Description

No authentication information is set up in the Source object, the Target object, or the Association object.

Action

When creating a new Source object, Target object, or Association object, acquire the LifeCycleManager object from the Connection object in which the authentication information is set up with the setCredentials method, and then use the create method for creating each object.

KDCCR2063-E

Multiple ClassificationSchemes are found.

Description

Multiple ClassificationSchemes are found.

Action

Revise the search conditions for searching ClassificationScheme. When searching multiple ClassificationScheme, use the BusinessQueryManager#findClassificationSchemes method.

KDCCR3005-E

Exception occurred.

Description

An exception is thrown in the internal processing.

Action

When this message is output in the trace file, make sure that the detailed message does not contain another message ID that is the main cause of occurrence of this error.

If this message ID alone is output, contact the system administrator.

KDCCR3009-E

SOAP request is invalid.

Description

An error occurred while processing the SOAP library.

Action

Reference the trace output in the SOAP library, and take actions against the error message. Also check the following:

URL of the UDDI registry server

Settings of the proxy server (when using a proxy)

KDCCR3010-E

SAX Parsing exception has occurred.

Description

An exception occurred in the SAX-related processing during the initialization of the XML parser.

Action

Contact the system administrator.

KDCCR3011-E

Input/Output exception has occurred.

Description

An internal I/O error occurred during initialization of the XML document.

Action

Check whether the memory is insufficient. If the error is caused by other reasons, contact the system administrator.

KDCCR3012-E

Exception occurred while instantiating the class.

Description

The class instances could not be created internally.

Action

Contact the system administrator.

KDCCR3013-E

Specified class is not found.

Description

An internally required class could not be found.

Action

The XML elements sent from the registry server might be invalid. Make sure that the registry server conforms to UDDI Version 2.0, and also that the XML message is correct.

KDCCR3014-E

Specified method/class is not accessible.

Description

An internally required class cannot be accessed.

Action

Contact the system administrator.

KDCCR3015-E

An error occurred during invocation of target method.

Description

An attempt to invoke an internal method that processes the request or response messages has failed.

Action

Contact the system administrator.

KDCCR3017-E

SecurityException has occurred.

Description

A security exception occurred.

Action

If Java security manager is being used, check that the settings of the security policy are correct.

KDCCR3018-E

Argument passed are Invalid/Illegal.

Description

The arguments during the invocation of the internal methods are invalid.

Action

Contact the system administrator.

KDCCR3019-E

An error occurred during DOM operation.

Description

An internal error occurred when creating or parsing DOM from XML.

Action

Contact the system administrator.

KDCCR3020-E

SOAP Fault occurred.

Description

A SOAP-level error (SOAP Fault) occurred in the registry server.

Action

Take action according to the contents of the detailed message output from the registry server.

KDCCR3021-W

File could not be found.

Description

The file required in the taxonomy server functionality does not exist. The processing continues.

Action

Make sure that the JAR file (hitjaxr.jar) of the UDDI client library has not been corrupted. If the error is caused by other reasons, contact the system administrator.

KDCCR3022-W

Unable to load Document Object.

Description

An attempt to perform parsing of an internal XML with the taxonomy server functionality has failed. The processing continues.

Action

Contact the system administrator.

KDCCR3023-W

Trace is initialized with default parameters.

Description

The trace will be initialized with the default parameters because the trace properties are not specified, and the processing will continue.

Action

As and when required, specify the trace properties.

KDCCR3024-W

UDDI disposition report :

Description

A UDDI-level error (dispositionReport) occurred in the registry server.

Action

Take action according to the contents of the detailed message output from the registry server.

KDCCR3028-W

Null is removed from the collection.

Description

The Collection object that is specified as a parameter of the method contains a null object. The processing continues after the removal of the null object.

Action

Check that a null object is included in the Collection object.

5.8 Messages from KDCCS1001 to KDCCS1150

This section describes messages from KDCCS1001 to KDCCS1150 output by SAAJ.

KDCCS1045-E

Message: KDCCS1045-E Header is already present.

Description

The SOAP header already exists. There can be only one SOAP header in a SOAP message.

Action

To add a new SOAP header, delete the old SOAP header beforehand.

KDCCS1051-E

Message: KDCCS1051-E No custom elements allowed at top level until after the body tag.

Description

An attempt is made to add elements other than the SOAP header and SOAP body in the SOAP message. The elements other than the SOAP header and SOAP body cannot be added immediately below the SOAP envelope.

Action

Do not add elements other than the SOAP header and SOAP body in a SOAP message.

KDCCS1056-E

Message: KDCCS1056-E Only one Body element is allowed.

Description

A message containing multiple SOAP body elements is received.

Action

A SOAP message contains only one SOAP body element. Check with the sender and confirm that the correct message is sent.

KDCCS1057-E

Message: KDCCS1057-E Only one Header element is allowed.

Description

A message containing multiple SOAP header elements is received.

Action

A SOAP message contains only one SOAP header element. Check with the sender and confirm that the correct message is sent.

KDCCS1149-E

Message: KDCCS1149-E Invocation of Call failed.

Description

The service could not be called.

Action

Take action according to the message output before this message.

5.9 Messages from KDCCS1151 to KDCCS1199

This section describes messages from KDCCS1151 to KDCCS1199 output during the size check of the transmission data.

KDCCS1151-E

Size of the attachment is exceeding the maximum size (maximum-value-set-up-in-the-operation-definition-file). Process = (send-or-receive#1), Content-ID = (content-ID-value#2), Content-Location = (content-location-value#2)

#1 In the case of an API, class-name::method-name will be displayed.

#2 If the content location does not exist, NONE will be displayed.

Description

The size of the attached data is more than the maximum size.

Action

Reduce the size of the attached data. Alternatively, revise the parameters of the operation definition file.

KDCCS1152-E

Total number of attachments is exceeding the maximum attachment count (maximum-value-set-up-in-the-operation-definition-file). Process = (send-or-receive)

Description

The total number of attachments is more than the maximum attachment count.

Action

Reduce the number of attachments. Alternatively, revise the parameters of the operation definition file.

KDCCS1160-E

Size of the SOAPEnvelope is exceeding the maximum size (maximum-value-set-up-in-the-operation-definition-file). Process = (send-or-receive)

Description

The size of SOAPEnvelope is more than the maximum size.

Action

Reduce the size of SOAPEnvelope. Alternatively, revise the parameters of the operation definition file.

5.10 Messages from KDCCS3000 to KDCCS3999

This section describes messages from KDCCS3000 to KDCCS3999 output by the SOAP Engine.

KDCCS3000-E

An attempt to create a SOAPMessge object has failed. (Class name = class-name, Method signature = method-signature, reason = reason)

Description

An attempt to create a SOAPMessage object has failed.

Action

Check that there is any problem in the program based on the contents of reason. If the action to be taken according to the contents of reason is not clear, contact the system administrator.

KDCCS3001-E

Illegal argument has been set. (Class name = class-name, Method signature = method-signature, argument = argument-name, value = argument-value)

Description

An invalid argument was specified.

Action

Specify a valid argument.

KDCCS3002-E

An attempt to execute the method has failed. (Class name = class-name, Method signature = method-signature, reason = reason)

Description

An attempt to execute the method has failed.

Action

Check if there is any problem in the program based on the contents of reason.

KDCCS3003-E

The detail element of the SOAP Fault does not exist. (Class name = class-name, Method signature = method-signature)

Description

The detail element does not exist in the SOAP Fault element.

Action

Invoke this method only when the detail element exists in the SOAP Fault element.

KDCCS3005-E

The specified element is illegal. (Class name = class-name, Method signature = method-signature, reason = reason)

Description

An invalid element was specified.

Action

Check that there is no problem in the program based on the contents of reason.

KDCCS3006-E

The type of the specified argument argument-name is illegal. (Class name = class-name, Method signature = method-signature, specified type = specified-type, expected type = expected-type)

Description

The type specified-type of the argument-name argument is invalid.

Action

Specify the type expected-type.

KDCCS3007-E

The specified URL is illegal. (Class name = class-name, Method signature = method-signature, reason = reason)

Description

The specified URL is incorrect.

Action

Check that the correct URL is specified based on the contents of reason.

KDCCS3008-E

An attempt to serialize a Document object has failed. (detail = detailed-information)

Description

An attempt to serialize the Document object has failed.

Action

Check that there is no problem in the program based on the contents of reason.

5.11 Messages from KDCCT0001 to KDCCT0999

This section describes messages from KDCCT0001 to KDCCT0999 output during the acquisition of the PRF trace.

KDCCT0001-E

The error occurred while initializing PRF trace. (details= detailed-information)

Description

An error occurred during the process of initializing the PRF trace.

Action

Refer to the detailed information, and remove the cause of the error.

detailed-information

The environment variable PRFSPOOL is not set.

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.

PRF daemon does not start. PRFID = PRF-identifier

The PRF demon may not have been invoked. Check that the PRF daemon is running (is the cprfstart command running?). Alternatively, check the PRF identifier specified in the cprfstart command.

System call error occurred.

In Windows

Reference the log file below the following path: setup-directory-of-environment-variable-PRFSPOOL\log\PRF-identifier Check the cause of the error from the PRF message, and then take the actions.

In UNIX

Reference the log file below the following path:

$PRFSPOOL/log/PRF-identifier

Check the cause of the error from the PRF message, and then take the actions.

Loading JNI library of PRF trace service was failed.

The possible causes are as follows:

- Cosminexus Performance Tracer is not installed.

- PRF trace output library is not specified in the class path.

- The environment variable is invalid.

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

Exception that actually occurred, and the detailed message of the error.

Contact the system administrator.

KDCCT0002-E

The error occurred while terminating PRF trace. (details= detailed-information)

Description

An error occurred during the termination of the PRF trace.

Action

Contact the system administrator.

detailed-information

Exception that actually occurred, and the detailed message of the error.

KDCCT0003-E

The error occurred while outputting PRF trace. (place = location-information, details= detailed-information)

Description

An error occurred while acquiring the PRF trace.

Action

Contact the system administrator.

location-information

ENTER: Method entry

EXIT: Method exit

detailed-information

Exception that actually occurred, and the detailed message of the error.

KDCCT0004-W

The processing of the SOAP client is continued though the error occurred.

Description

An error occurred during the initialization or termination of the PRF trace. The processing of the SOAP client continues.

Action

Reference the error message output immediately before this message, and remove the cause of the error.

5.12 Messages from KDCCT1001 to KDCCT1999

This section describes messages from KDCCT1001 to KDCCT1999 output by the trace functionality.

KDCCT1001-I

invoke User RPC Service. Method = method-name

Description

The RPC service is invoked. The invoked service method is method-name.

Action

Not required.

KDCCT1002-I

return User RPC Service. Method = method-name

Description

The RPC service is executed. The executed service method is method-name.

Action

Not required.

KDCCT1003-I

invoke User Messaging Service.

Description

The messaging service is invoked.

Action

Not required.

KDCCT1004-I

return User Messaging Service.

Description

The messaging service is executed.

Action

Not required.

6 KDCG (Messages Output by the Web Service Security Functionality) (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

6.1 (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

7 KDJE (Messages Output by Cosminexus Component Container)

This chapter describes the messages beginning with KDJE from the messages output by Cosminexus Component Container and Cosminexus TPBroker.

7.1 Format for describing the messages

The format of message descriptions in this chapter is as follows:

XXXXnnnnn-Y

Message text

Explanation of variable values

Description

Supplementary explanation for the message text

Action

Action performed by the user

Note that depending upon the message, Explanation of variable values, Description, and Action might not be described.

The description of each item is as follows:

XXXXnnnnn

This indicates the message ID.

The elements configuring a message ID are as follows:

XXXX

The prefix of a message output by Cosminexus Component Container is indicated by KDJE.

nnnnn

This indicates the message number managed in the Cosminexus Component Container. A unique five-digit number is assigned to each message.

Y

This indicates the message level. The message level is shown with one alphabetic character.

The characters showing message levels and their meaning are mentioned below:

E (Error)

This message reports that an error level problem has occurred.

The process is interrupted when this message is output.

W (Warning)

This message reports that a warning level problem has occurred.

The process continues even after the message is output.

I (Information)

This message reports a system operation.

The process continues even after the message is output.

Message text

This indicates the message text output by Cosminexus Component Container.

Note that the variable value (value that changes according to the message output status) in the message text is shown in the format of xx....xx (xx are lower case alphabetic characters).

Explanation of variable values

The information displayed in the variable value within the message text is shown in the format of xx....xx: displayed information (xx are lower case alphabetic characters). A format example of the explanation of variable values is shown below:

(Example)

aa....aa: File name

bb....bb: Application name

Description

This indicates the supplementary message explanation items such as the factors due to which the message is reported and Cosminexus Component Container operations that output the message.

Action

This indicates the actions performed by the user. Note that 'Contact maintenance personnel' in the action indicates that the system administrator needs to contact our helpdesk based on the purchase agreement.

7.2 Messages from KDJE30000 to KDJE39999

This section describes the messages from KDJE30000 to KDJE39999, and also describes the actions to be taken.

KDJE30000-E

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

aa....aa: Context root name

bb....bb: Application name

Description

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

Deployment will be interrupted and RemoteException will be thrown.

Action

Specify another context root, and then redeploy the application.

KDJE30003-W

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

aa....aa: Directory name

Description

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

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

When Windows is used as the operating system.

When the openStream method of the java.net.URL class is executed in the servlet of the J2EE application.

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

Action

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

KDJE30004-E

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

aa....aa: WAR file name

bb....bb: Servlet or JSP name

Description

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

The process of importing will be interrupted.

Action

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

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

KDJE30005-E

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

aa....aa: Archive file name

bb....bb: Archive file name

cc....cc: Display name

Description

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

The process of importing will be interrupted.

Action

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

KDJE30006-E

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

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

bb....bb: Enterprise Bean name

Description

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

The process of importing will be interrupted.

Action

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

KDJE30007-E

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

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

bb....bb: Enterprise Bean name

Description

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

The process of importing will be interrupted.

Action

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

KDJE30008-E

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

aa....aa: WAR DD name

bb....bb: Servlet or JSP name

Description

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

The process of importing will be interrupted.

Action

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

KDJE30010-E

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

aa....aa: Class name

bb....bb: Detailed message

Description

An error occurred during the server start hook processing.

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

Action

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

KDJE30011-E

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

aa....aa: Class name

bb....bb: Detailed message

Description

An error occurred during the server stop hook processing.

The J2EE server or the Web container server will terminate.

Action

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

KDJE30012-E

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

aa....aa: Class name

Description

The class (aa....aa) specified in the key ejbserver.application.InitTermProcessClasses was not found.

Action

Reset the class name of the key ejbserver.application.InitTermProcessClasses.

KDJE30013-E

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

aa....aa: Class name

Description

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

Action

Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30014-E

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

aa....aa: Class name

Description

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

Action

Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30015-E

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

aa....aa: Class name

Description

The interface cannot be specified in the key ejbserver.application.InitTermProcessClasses.

Action

Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30016-E

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

aa....aa: Class name

Description

An abstract class cannot be specified in the key ejbserver.application.InitTermProcessClasses.

Action

Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30017-E

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

aa....aa: Class name

Description

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

Action

Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30018-E

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

aa....aa: Primitive type name

Description

The primitive type (aa....aa) cannot be specified in the key ejbserver.application.InitTermProcessClasses.

Action

Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30019-E

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

aa....aa: Class name

Description

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

Action

Revise the class specified in the key ejbserver.application.InitTermProcessClasses.

KDJE30020-I

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

aa....aa: Class name

Description

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

KDJE30021-I

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

aa....aa: Class name

Description

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

KDJE30022-I

aa....aa

aa....aa: Java VM version

Description

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

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

KDJE30024-W

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

aa....aa: Property name

Description

The property value is invalid.

Action

Reset the property value.

KDJE30025-W

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

aa....aa: Class name

Description

The specified class (aa....aa) does not implement the interface com.cosminexus.mngsvr.hmx.agent.InstrumentationAgent.

Action

Implement InstrumentationAgent in the set Agent class.

KDJE30026-W

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

aa....aa: Class name

bb....bb: Reason

Description

The defined Agent class (aa....aa) cannot be instantiated.

Action

Make sure that the Cosminexus Component Container is installed properly.

KDJE30027-W

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

aa....aa: Class name

bb....bb: Reason

Description

The Agent cannot be started.

Action

Check the start method of the defined Agent class.

KDJE30028-I

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

aa....aa: Server name

Description

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

KDJE30030-E

The server shutdown is in progress.

Description

The server shutdown is in progress.

Action

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

KDJE30031-I

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

aa....aa: Server name

Description

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

KDJE30033-W

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

aa....aa: Statement object

Description

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

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

Action

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

KDJE30034-I

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

aa....aa: The J2EE server name

Description

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

KDJE30040-I

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

aa....aa: Server name

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

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

dd....dd: Process ID

Description

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

KDJE30041-E

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

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

Description

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

The possible causes might be as follows:

The property file cannot be accessed.

The property file format does not conform to Java specifications.

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

Action

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

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

KDJE30042-E

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

aa....aa: Property name

Description

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

Action

Reset the property.

KDJE30043-E

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

aa....aa: Details

Description

An unexpected exception occurred.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KDJE30044-E

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

aa....aa: IP address

bb....bb: Server name

Description

Access from aa....aa is not permitted.

Action

Revise the IP address or the host name specified in the key webserver.connector.http.permitted.hosts of the user property file (usrconf.properties) of the connected the J2EE server.

KDJE30045-E

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

aa....aa: Server name

bb....bb: Maintenance information 1

cc....cc: Maintenance information 2

Description

The version of the command does not match the version of the J2EE server.

Action

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

KDJE30046-E

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

aa....aa: Details

bb....bb: Server name

Description

An unexpected exception occurred.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KDJE30047-E

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

aa....aa: Server name

Description

The startup processing for the J2EE server has not yet completed.

Action

After the startup processing for the J2EE server finishes, re-execute the command.

KDJE30048-E

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

aa....aa: Server name

Description

The J2EE server shutdown is in progress.

Action

The J2EE server shutdown is in process. After the J2EE server stops, restart it.

KDJE30050-E

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

aa....aa: Server name

Description

The J2EE server has aborted.

Action

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

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

KDJE30051-W

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

aa....aa: Default value

bb....bb: Property key name

Description

The default value aa....aa will be used, since the specified value is invalid.

Action

Revise the value specified in the property key bb....bb.

KDJE30052-E

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

aa....aa: Version

bb....bb: Model name

cc....cc: Edition

Description

The work directory is invalid. The specified work directory cannot be used with this version, platform, and edition.

If an attempt to start Java VM fails due to the specification of an invalid option definition file for the J2EE server during initial startup of the J2EE server, attempts to start the J2EE server thereafter will fail.

Action

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

KDJE30060-I

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

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

bb....bb: RMI port number

Description

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

KDJE30061-E

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

aa....aa: Property name

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

cc....cc: RMI port number

dd....dd: Details

Description

An attempt to generate the RMI registry has failed.

Action

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

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

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

KDJE30065-E

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

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

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

cc....cc: MBean server name

dd....dd: Details

Description

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

Action

The format of the character string might be incorrect in the host name. In the host name, if the format of the character string is not as per the format ruled in RFC 2609, change the host name. If the host name is correct, contact maintenance personnel.

KDJE30066-E

Information needed for XA transaction recovery cannot be obtained.

Description

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

The startup of the J2EE server will be interrupted.

Action

Action for the transaction

Check if any residual transactions are found in resources associated with the system. Check the information of resources associated with the system, and if any residual transactions are found, manually perform commit or rollback to secure consistency between each linked resource and transaction.

Action for the J2EE server

Re-setup the J2EE server.

KDJE30070-E

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

aa....aa: File name

Description

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

Action

Execute the action described in the message KDJE30003-W that is output immediately after this message.

KDJE30200-I

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

aa....aa: Server name

Description

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

KDJE30201-I

No server needs to be migrated.

Description

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

KDJE30202-E

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

aa....aa: DD name

bb....bb: Reason for failure

Description

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

Action

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

In the case of normal migration

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

If modification cannot be done, contact maintenance personnel.

In the case of forced migration

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

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

KDJE30203-I

Usage: cjenvupdate [-f]

Description

This message describes the usage method of the cjenvupdate command.

KDJE30204-I

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

aa....aa: Server name

Description

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

KDJE30205-E

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

aa....aa: Server name

Description

The server (aa....aa) will not be migrated because of the presence of a DD that cannot be converted to the new environment format.

Action

Modify the DD according to the action given in KDJE30202-E, and then re-execute the cjenvupdate command.

KDJE30206-I

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

aa....aa: Server name

Description

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

KDJE30207-W

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

aa....aa: DD name

bb....bb: Reason for failure

Description

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

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

Action

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

KDJE30208-W

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

aa....aa: Server name

Description

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

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

Action

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

KDJE30209-E

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

aa....aa: Server name

Description

An unexpected exception occurred.

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

Action

Contact maintenance personnel.

KDJE30220-I

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

Description

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

KDJE30221-I

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

Description

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

KDJE30222-W

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

Description

An attempt to migrate some definition files has failed.

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

Action

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

KDJE30223-E

An unexpected exception has occurred.

Description

An unexpected exception occurred.

Action

Contact maintenance personnel.

KDJE30224-E

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

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

bb....bb: Reason for migration failure

Description

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

The definition migration processing will be interrupted.

Action

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

KDJE30225-W

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

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

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

Description

The definition files of the old version cannot be migrated.

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

Action

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

KDJE30226-W

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

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

Description

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

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

Action

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

KDJE30230-W

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

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

Description

The deletion of the file has failed.

Take action based on the following causes:

File deletion permission is not available.

The disk device has failed due to reasons, such as disk not working.

Action

Take action based on the following causes:

When file deletion permission is not available

A user who has the correct permissions must delete the file.

When the disk device is not working

Contact the system administrator, and then replace the device.

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

KDJE30231-W

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

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

Description

An attempt to delete the directory has failed.

Take action based on the following causes:

Directory deletion permission is not available.

The disk device has failed due to reasons, such as disk not working.

Action

Take action depending on the cause.

When directory deletion permission is not available

A user who has the correct permissions must delete the file.

When the disk device is not working

Contact the system administrator, and then replace the device.

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

KDJE30232-W

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

aa....aa: Copy source file name

bb....bb: Copy destination file name

cc....cc: Details

Description

An attempt to copy the file has failed.

Take action based on the following causes:

The available disk space is insufficient.

The disk device has failed due to reasons, such as disk not working.

Action

Take action depending on the cause.

When the available disk space is insufficient

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

When the disk device is not working

Contact the system administrator, and then replace the device.

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

KDJE30233-E

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

aa....aa: File name

Description

An attempt to create a file has failed.

Take action based on the following causes:

The available disk space is insufficient.

The disk device has failed due to reasons, such as disk not working.

A file under CC is being accessed.

Action

Take action depending on the cause.

When the available disk space is insufficient

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

When the disk device is not working

Contact the system administrator, and then replace the device.

When a file under CC is being accessed

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

If the file name is cjupdate.properties:

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

If the file name is cjupdate.migratefiles.properties:

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

If the file name is usrconf.properties.envupdate_bak:

Make sure that usrconf.properties is not being accessed, and then re-execute the cjenvupdate command.

If the file name is server.policy.envupdate_bak:

Make sure that server.policy is not being accessed, and then re-execute the cjenvupdate command.

If the file name is web.policy.envupdate_bak:

Make sure that web.policy is not being accessed, and then re-execute the cjenvupdate command.

If the file name is usrconf.properties:

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

If the file name is server.policy:

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

If the file name is web.policy:

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

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

KDJE30234-E

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

aa....aa: Directory name

Description

The directory was not found.

Action

Confirm that the directory required for execution of the application is created.

KDJE30250-I

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

Description

This message describes the usage method of the cjstartrecover command.

KDJE30251-E

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

aa....aa: Invalid option name

Description

An invalid option is specified.

Action

Check the specified option, and then re-execute the process.

KDJE30252-E

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

aa....aa: Server name

Description

A timeout occurred on the J2EE server in recovery mode.

Some unconcluded transactions might exist in the resource.

Action

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

KDJE30253-E

Only the Cosminexus Component Container administrator can execute this command.

Description

Only the Cosminexus Component Container administrator can execute this command.

Action

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

KDJE30254-I

Usage:

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

Format2: cjrarupdate -recoverfrom directory

Description

This message describes the usage method of the cjrarupdate command.

KDJE30255-E

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

aa....aa: Reason

Description

The location of the public directory of the J2EE server cannot be acquired.

Action

Take action depending on the contents of the reason for failure.

KDJE30256-E

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

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

Description

The property file cannot be read.

Action

Check if the property file to be read exists, and if the file has read permission.

KDJE30257-E

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

Description

The installation destination of Cosminexus Component Container is not known.

Action

Make sure that the Cosminexus Component Container is installed properly.

KDJE30258-E

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

aa....aa: Details

Description

An unexpected exception occurred.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KDJE30259-W

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

aa....aa: Invalid value

bb....bb: Option name

cc....cc: Value used

Description

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

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

Action

Revise the specified value of the option.

KDJE30260-I

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

aa....aa: Number of current stages

bb....bb: Total number of stages

Description

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

KDJE30261-I

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

aa....aa: Number of current stages

bb....bb: Total number of stages

Description

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

KDJE30262-I

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

aa....aa: Data source display name

Description

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

KDJE30263-I

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

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

Description

The data source was migrated to the J2EE resource adapter.

KDJE30264-E

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

aa....aa: The J2EE server name

Description

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

The command execution will be interrupted.

Action

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

KDJE30265-E

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

aa....aa: Directory name

bb....bb: Backup directory name

Description

An attempt to back up the work directory failed.

The possible cause is as follows.

A file under the work directory is being accessed.

Action

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

KDJE30300-W

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

aa....aa: Failure reason code

Description

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

Action

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

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

Table 7‒1: List of failure reason codes displayed in KDJE30300-W

Failure reason code

Cause of error

Action

-1

Either the environment variable PRFSPOOL is not set, or the directory set in the environment variable PRFSPOOL does not exist.

Confirm that the environment variable PRFSPOOL is set, or the directory exists.

-2

An error occurred in the service start processing of the PRF demon present in the process.

The PRF demon might not be invoked.

Confirm that the PRF demon is invoked. Also, check the PRFID of the definition file.

-3

An error (such as system call error) occurred in the service start processing of the PRF demon present in the process.

See the log file present below setup-directory-of-environment-variable-PRFSPOOL\log\PRF-identifier (in Windows) or $PRFSPOOL/log/PRF-identifier (in UNIX). Consult the PRF messages, check the factors, and then take action.

-4

An attempt to load the library required for the service of PRF demon has failed.

Take action based on the following causes:

Cosminexus Performance Tracer is not installed.

PRF trace output library is not specified in the class path.

The environment variable is invalid.

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

KDJE30310-W

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

aa....aa: Monitoring target

file descriptor: File descriptor monitoring

thread: Thread monitoring

Description

Resource monitoring has stopped because the usage value of aa....aa cannot be retrieved in this platform.

Action

Set the property of monitoring the file descriptor (ejbserver.watch.fileDescriptor.enabled) or the threads (ejbserver.watch.thread.enabled) as false.

KDJE30311-W

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

aa....aa: Monitoring target

file descriptor: File descriptor monitoring

thread: Thread monitoring

bb....bb: User-specified value

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

Description

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

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

Action

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

KDJE30380-E

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

aa....aa: Reason for failure

Description

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

Action

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

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

Environment is invalid.

The Application Server might not be installed properly.

Check if the application server is properly installed.

Load library failed.

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

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

Unexpected error occurred.

Acquire the maintenance information, and then contact maintenance personnel.

KDJE30400-I

The user log environment setup will now start.

Description

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

KDJE30401-I

The user log environment setup has been terminated.

Description

The user log environment setup was terminated.

KDJE30402-I

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

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

The following are displayed when the value is not null:

bb....bb: Specified handler name

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

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

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

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

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

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

ii....ii: Output encode

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

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

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

Description

The creation of the Handler object was completed.

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

KDJE30403-I

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

aa....aa: Logger name

bb....bb: Resource bundle name

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

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

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

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

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

Description

The creation of the Logger object was completed.

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

KDJE30404-I

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

aa....aa: File name

Description

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

KDJE30405-I

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

Description

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

KDJE30406-I

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

Description

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

KDJE30410-W

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

aa....aa: Actually set value

bb....bb: Property key

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

Description

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

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

Action

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

KDJE30411-W

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

aa....aa: Class name

The following value is displayed when it exists:

bb....bb: Constructor argument

Description

The specified class (aa....aa) cannot be created either because it is invalid, or security permission to create this class using reflection is not available.

Action

Revise the value of the property key and the security permission.

KDJE30413-W

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

aa....aa: Parameter name

Description

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

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

Action

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

KDJE30420-E

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

aa....aa: File name

Description

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

Action

Take action based on the following causes:

The property file does not exist on the disk

If the user property file does not exist, copy the default user property file from the templates folder.

Permission is not available for reading the property file

Grant read permission.

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

Grant security permission for reading the property.

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

KDJE30421-E

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

aa....aa: Class name

bb....bb: Handler name

cc....cc: File path

Description

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

Action

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

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

The available disk space is insufficient

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

A read only, a running, or an open file already exists with the same name, or a file with no update permission exists

Specify the settings to output to a file with appropriate permissions.

A directory with the same name as the file name already exists, or the directory does not have write permission

Specify the settings to output to a directory or a file with appropriate permissions.

The disk device fails

Contact the system administrator.

The system administrator must replace the device.

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

KDJE30423-E

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

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

bb....bb: Log file name

Description

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

Action

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

The available disk space is insufficient

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

The disk device fails

Contact the system administrator.

The system administrator must replace the device.

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

KDJE30424-E

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

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

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

Description

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

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

Action

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

KDJE30429-E

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

aa....aa: Handler name

bb....bb: File name

Description

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

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

Action

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

KDJE30430-E

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

Description

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

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

Action

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

KDJE30431-E

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

aa....aa: Class name

bb....bb: Handler name

Description

An attempt to set up the handler (bb....bb) has failed because an error was detected.

Action

Check the error contents output before this message, based on the class name and the handler name.

KDJE30432-E

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

aa....aa: Logger name

bb....bb: Resource bundle name

Description

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

This logger was not created.

Action

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

KDJE30433-E

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

Description

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

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

Action

Grant security permission for reading the system properties.

KDJE31000-I

OTS mode is enabled.

Description

The J2EE server will start in the OTS mode.

Using OTS can conclude XA transaction.

KDJE31001-I

Non-OTS mode is enabled.

Description

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

Using OTS cannot conclude XA transaction.

KDJE31002-W

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

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

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

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

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

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

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

Description

The transaction will be rolled back due to the occurrence of a transaction timeout.

Action

Make sure that time is not being taken for the processing within the transaction, and if time is being taken, remove the cause. If the time taken for the processing within the transaction is appropriate, consider lengthening the time period until a timeout occurs.

KDJE31004-I

Light transaction is enabled.

Description

The local transaction is optimized.

XA transaction that uses OTS, cannot be concluded.

KDJE31005-E

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

Description

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

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

Action

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

KDJE31006-E

Specified transaction timeout value is invalid.

Description

The specified transaction timeout value is invalid.

The valid value is an integer from 0 to 2147483647.

Action

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

KDJE31007-E

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

Description

Non-XA resources cannot be enlisted in global transactions.

Only XA resources can be enlisted in global transactions.

Action

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

KDJE31008-E

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

Description

The local transaction already has a non-XA resource. As a result, more resources cannot be enlisted.

Action

Make sure that multiple resources are not enlisted in the local transaction. If multiple resources are to be enlisted, use a global transaction for enlisting of XA resources.

KDJE31009-E

No nested transaction is supported.

Description

No nested transaction is supported.

Action

Do not use nested transactions.

KDJE31010-W

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

aa....aa: Component information

bb....bb: Resource handle information

cc....cc: Resource information

Description

A J2EE application was terminated without closing the connection.

The unclosed connection was forced to close.

Action

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

KDJE31011-E

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

aa....aa: Exception information

Description

The transaction cannot be committed because it has rolled back.

Action

Confirm the following details:

Confirm that the J2EE application is not marked for rollback in the state prior to commit.

Confirm 1, and if not marked, confirm that time is not being taken for the processing within the transaction. If time is being taken, remove the cause.

Confirm 2, and if the time taken for the processing within the transaction is appropriate, consider lengthening the time period until a timeout occurs.

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

KDJE31012-E

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

aa....aa: Exception information

Description

A heuristic exception occurred.

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

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

Action

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

KDJE31013-E

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

Description

The transaction having non-XA resource cannot be exported (2-phase commit cannot be done).

Action

Do not perform remote invocation in a local transaction.

KDJE31014-E

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

aa....aa: Exception information

Description

The global transaction cannot be started.

Action

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

Is the Smart Agent running?

Does the system environment variable OSAGENT_PORT match with the key vbroker.agent.port in the specification of the Smart Agent port?

Is TCS running?

Are the number of branches of TPBroker appropriate?

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

KDJE31015-I

OTS in-process mode is enabled.

Description

Using OTS can conclude XA transaction.

KDJE31016-W

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

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

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

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

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

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

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

Description

The running transaction was forced to time out due to forced termination of the application.

Action

Confirm that the time taken for the processing within the transaction is not more than expected and if more time is being taken, remove the cause.

KDJE31017-I

A client transaction was marked for rollback.

Description

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

Action

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

ejbserver.distributedtx.rollbackClientTxOnSystemexception=false

KDJE31018-E

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

Description

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

Action

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

The J2EE server startup mode is 1.4 mode.

The light transaction functionality is disabled.

The in-process transaction service is enabled.

KDJE31019-E

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

Description

The cjlisttrn command is supported, when the in-process transaction service is enabled. As a result, the cjlisttrn command cannot be used when the out-process transaction service is enabled.

Action

Use the command for displaying the transaction information for out-process transaction service.

KDJE31020-E

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

Description

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

Action

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

The J2EE server startup mode is 1.4 mode.

The light transaction functionality is disabled.

The in-process transaction service is enabled.

KDJE31021-W

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

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

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

Description

The transaction will be rolled back due to the occurrence of a timeout in the transaction started in the EJB client.

Action

Make sure that time is not being taken for the processing within the transaction, and if time is being taken, remove the cause. If the time taken for the processing within the transaction is appropriate, consider lengthening the time period until a timeout occurs.

KDJE31022-E

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

Description

UserTransactionFactory cannot be used in the J2EE server. UserTransactionFactory can only be used in the EJB client.

Action

To acquire UserTransaction from the EJB and Servlets running on the J2EE server, use JNDI to perform lookup. In the case of EJB, UserTransaction can be acquired from javax.ejb.EJBContext.

KDJE31023-E

The transaction is disabled in the client side.

Description

The transaction is disabled in the client side.

Action

To use the transaction in the EJB client, specify true in the property ejbserver.client.transaction.enabled.

KDJE31024-E

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

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

Description

An attempt to create UserTransaction has failed.

Action

Check the cause of failure (aa....aa), and then take action.

KDJE31025-E

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

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

Description

An attempt to initialize the transaction manager has failed.

Action

Check the cause of failure (aa....aa), and then take action.

KDJE31026-E

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

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

Description

An attempt to load the ORBInitializer class has failed.

Action

Check the cause of failure (aa....aa), and then take action.

KDJE31027-E

The OTS status directory path is not specified.

Description

In the EJB client, the directory in which the status file of the in-process transaction service is saved is not specified.

Action

In the invocation batch file of EJB client, specify the directory in which the status file is saved, in the property ejbserver.distributedtx.ots.status.directory1.

KDJE31028-E

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

aa....aa: Class name

bb....bb: Method name

Description

An unsupported method is invoked.

Action

Do not invoke a method that is not supported.

KDJE31030-E

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

Description

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

Action

Disable the light transaction functionality.

KDJE31031-E

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

Description

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

Action

Enable the in-process transaction service.

KDJE31032-E

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

Description

The cjcommittrn command, cjrollbacktrn command, and cjforgettrn command cannot be used in the basic mode.

Action

Set the startup mode of the J2EE server to 1.4 mode.

KDJE31800-E

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

aa....aa: Property name

Description

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

The processing will be interrupted.

Action

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

KDJE31801-W

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

aa....aa: Property name

bb....bb: Default value

Description

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

The processing continues.

Action

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

KDJE31802-E

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

aa....aa: Property name

bb....bb: Property value

Description

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

The processing will be interrupted.

Action

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

KDJE31803-W

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

aa....aa: Property name

bb....bb: Set property value

cc....cc: Default value

Description

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

The processing continues.

Action

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

KDJE31804-E

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

aa....aa: Error information

Description

A fatal error occurred.

The processing will be interrupted.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KDJE31805-I

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

aa....aa: Resource name

Description

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

KDJE31806-E

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

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

Description

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

The processing will be interrupted.

Action

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

KDJE31808-W

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

aa....aa: Resource name

Description

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

Action

Unconcluded transactions might exist in the deleted resource.

Check the state of the transaction.

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

KDJE31809-W

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

aa....aa: Resource name

Description

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

Action

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

If the resource has stopped, invoke it.

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

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

KDJE31810-I

The system is waiting for incomplete transactions.

Description

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

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

Action

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

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

The resource settings are correct.

If the resource has stopped, invoke the resource.

No errors have occurred in the J2EE server, such as insufficient memory.

The specification of the Smart Agent port is correct (the system environment variable OSAGENT_PORT matches with the key vbroker.agent.port set in the user property file).

#

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

KDJE31812-W

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

aa....aa: Resource type

bb....bb: Resource name

cc....cc: Exception information

Description

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

The processing continues.

Action

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

KDJE31813-I

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

aa....aa: Resource type

bb....bb: Resource name

Description

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

KDJE31814-W

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

aa....aa: Resource type

bb....bb: Resource name

Description

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

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

Action

Confirm the following details, and then take action:

Settings of the resource

The target resource is invoked

Network failure has not occurred

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

KDJE31815-E

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

aa....aa: Resource type

bb....bb: Resource name

Description

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

Transactions cannot be started in this state.

Connection to the target resource has probably not been established.

Action

Confirm the following details, and then take action:

Settings of the resource

The target resource is invoked

Network failure has not occurred

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

KDJE31816-I

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

aa....aa: Resource type

bb....bb: Resource name

Description

The transaction conclusion check has ended successfully.

KDJE31817-W

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

aa....aa: Resource type

bb....bb: Resource name

Description

Either unconcluded transactions exist or the recovery process is in progress.

Action

Wait for conclusion of unconcluded transactions, or completion of the recovery process.

KDJE31818-W

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

aa....aa: Resource type

bb....bb: Resource name

Description

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

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

The resource has stopped.

A network failure occurred.

The resource settings are invalid.

Action

Make sure that the state enables connection to the resource.

KDJE31819-W

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

aa....aa: Resource type

bb....bb: Resource name

Description

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

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

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

The resource settings are invalid.

Action

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

KDJE31820-W

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

Description

The transaction conclusion check was timed out.

Action

To execute recovery of unconcluded transactions, restart the system.

KDJE32000-W

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

aa....aa: Method name

Description

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

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

Action

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

KDJE34000-I

The SFO server application will now start.

Description

The SFO server application will start.

KDJE34001-E

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

Description

An attempt to start the SFO server application has failed.

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

Action

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

KDJE34002-I

The SFO server application will now stop.

Description

The SFO server application will terminate.

KDJE34003-I

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

aa....aa: J2EE application name

bb....bb: Context root name

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

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

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

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

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

cookie: Control is performed by using an HTTP Cookie.

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

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

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

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

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

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

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

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

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

RW key(*)

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

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

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

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

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

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

R key(*)

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

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

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

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

Serializable: Objects of a serializable class

Description

Replication of the global session information will start.

KDJE34004-E

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

aa....aa: J2EE application name

bb....bb: Context root name

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

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

Description

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

Take action based on the following causes:

The estimation of memory usage set in the SFO server is wrong

The maximum size of the global session information set in the Web application present on the J2EE server is large

The maximum value of the number of HttpSession set in the J2EE server is inappropriately large

Action

Take the following actions depending upon the cause:

When the memory usage set in the SFO server is wrong

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

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

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

When the maximum size of the global session information is large

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

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

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied.

When the maximum value of the number of HttpSession is large

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

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

KDJE34005-I

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Discarded global sessions

Description

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

KDJE34006-I

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Discarded global session ID

Description

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

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

KDJE34007-I

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Connected J2EE servers

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

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

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

Description

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

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

KDJE34008-E

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

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

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

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

Description

An attempt to negotiate with the J2EE server has failed.

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

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

Parameter-name = Setting-value

The contents of the parameter name are as follows:

max sessions: Maximum number of global sessions

max session info size: Maximum value (in bytes) of the size of global session information

max inactive interval: Validity period (in seconds) of the global session

lock timeout: Timeout value for awaiting global session lock

GS control: Control method of the global session

GID cookie name: Name of the HTTP Cookie used to send the global session ID

GID URL param name: Path parameter name of the URL used to send the global session ID

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

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

byte array enable: Can the session information in the form of byte arrays be inherited

serializable enable: Can the session information in the form of objects of the serializable class be inherited

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

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

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

Action

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

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied.

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

KDJE34009-I

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Connected J2EE servers

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

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

Description

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

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

KDJE34010-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Connected J2EE servers

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

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

Description

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

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

Action

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

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

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

KDJE34011-I

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

aa....aa: J2EE application name

bb....bb: Context root name

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

dd....dd: Discarded global sessions

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

Description

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

KDJE34012-I

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Discarded global session ID

Description

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

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

KDJE34013-I

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

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

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

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

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

Description

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

KDJE34014-W

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

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

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

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

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

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

Description

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

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

The set value of the validity period of HTTP session is inappropriately small.

The locked J2EE server has slowed down due to some reason, and the processing has not finished during the validity period.

The locked J2EE server has stopped.

Action

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

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

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34015-W

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

aa....aa: J2EE application name

bb....bb: Context root name

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

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

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

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

Description

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

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

create from the initial HTTP session

A global session is created from the new HTTP session created on the J2EE server.

create from the existing HTTP session

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

Action

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

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34016-W

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

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

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

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

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

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

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

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

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

Description

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

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

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

get

The global session information is acquired from the SFO server, since the HTTP session does not exist on the J2EE server.

lock

The HTTP session exists on the J2EE server. To process the request, the global session present on the SFO server is locked.

Action

Check the working state of the locked J2EE server.

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

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34017-W

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

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

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

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

Description

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

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

The HTTP session was disabled on the J2EE server

The validity period has expired on the SFO server

The SFO server was restarted

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

get

The global session information is acquired from the SFO server, since the HTTP session does not exist on the J2EE server.

lock

The HTTP session exists on the J2EE server. To process the request, the global session present on the SFO server is locked.

unlock

The global session information present on the SFO server is updated and released when the request processing on the J2EE server is finished.

invalidate

The global session information present on the SFO server is discarded because the HTTP session was discarded on the J2EE server.

update the last accessed time

After locking the global session on the J2EE server, only the last accessed time of the global session present on the SFO server is updated since a request with the same session ID was received during the request processing.

Action

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

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

Check the working state of the J2EE server.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34018-W

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

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

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

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

Description

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

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

get

The global session information is acquired from the SFO server, since the HTTP session does not exist on the J2EE server.

lock

The HTTP session exists on the J2EE server. To process the request, the global session present on the SFO server is locked.

unlock

The global session information present on the SFO server is updated and released when the request processing on the J2EE server is finished.

update the last accessed time

After locking the global session on the J2EE server, only the last accessed time of the global session present on the SFO server is updated since a request with the same session ID was received during the request processing.

Action

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

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

Check the working state of the J2EE server.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34019-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

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

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

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

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

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

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

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

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

ll....ll: Maintenance information

Description

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

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

create from the initial HTTP session

A global session is created from the new HTTP session that was created on the J2EE server.

create from the existing HTTP session

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

get

The global session information is acquired from the SFO server, since the HTTP session does not exist on the J2EE server.

lock

The HTTP session exists on the J2EE server. To process the request, the global session present on the SFO server is locked.

unlock

The global session information present on the SFO server is updated and released when the request processing on the J2EE server is finished.

invalidate

The global session information present on the SFO server is discarded because the HTTP session was discarded on the J2EE server.

update the last accessed time

After locking the global session on the J2EE server, only the last accessed time of the global session present on the SFO server is updated since a request with the same session ID was received during the request processing.

Action

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

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

Remove the cause of the problem occurred in the host.

A problem occurred in the communication path between the J2EE server and the SFO server.

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

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

Remove the cause of the problem occurred in the host.

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

KDJE34020-E

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

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

Description

An unexpected exception occurred in the SFO server.

Action

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

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

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

KDJE34021-W

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

aa....aa: Property name

bb....bb: Specified value

cc....cc: Default value

Description

The property settings of the SFO server are invalid.

The default value will be used.

Action

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

KDJE34022-I

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

aa....aa: J2EE application name

bb....bb: Context root name

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

Description

The number of global sessions has become zero.

KDJE34023-I

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

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

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

cc....cc: J2EE application name

dd....dd: Context root name

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

Description

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

KDJE34024-W

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

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

bb....bb: J2EE application name

cc....cc: Context root name

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

Description

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

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

Action

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

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34025-W

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

aa....aa: J2EE application name

bb....bb: Context root name

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

Description

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

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

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

Action

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

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34026-E

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

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

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

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

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

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

Description

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

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

Action

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

KDJE34027-I

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

aa....aa: J2EE application name

bb....bb: Context root name

Description

Replication of the global session information will be ended.

KDJE34029-W

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

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

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

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

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

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

Description

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

Action

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

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

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

KDJE34030-E

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

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

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

cc....cc: J2EE application name

dd....dd: Context root name

Description

An attempt to negotiate with the J2EE server has failed. The SFO server does not support the functionality requested from the J2EE server.

Action

Upgrade the version of the SFO server to a version that supports the functionality requested by the J2EE server.

KDJE34200-I

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

aa....aa: J2EE application name

bb....bb: Context root name

Description

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

KDJE34201-E

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

aa....aa: J2EE application name

bb....bb: Context root name

Description

The memory session failover functionality cannot be started. The Web application cannot be started.

Action

Implement the action mentioned in the message output before this message. After taking action, either restart the J2EE server, or restart the J2EE application.

KDJE34202-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Initialization parameter name

dd....dd: Specified value

Description

The value set in the initialization parameter of the filter for session failover is invalid.

Action

Modify the parameter value cc....cc set in the Deployment Descriptor (web.xml), and then restart.

KDJE34203-E

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

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

bb....bb: Set value

Description

The property set in the user property file is invalid.

Action

Modify the parameter value aa....aa specified in the user property file (usrconf.properties), and then restart the J2EE server.

KDJE34204-I

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name used

Description

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

KDJE34205-I

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

The connection with the SFO server has finished.

KDJE34206-W

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

An attempt to connect to the SFO server has failed.

Take action based on the following causes:

The SFO server is not running.

Some error occurred in the communication path with the SFO server.

The IP address or the port number of the CORBA Naming Service invoked in the SFO server specified in the user property file is wrongly specified.

The option -nosecurity is not specified in the cjstartsv command during the startup of the SFO server.

The memory of SFO server is insufficient.

The negotiation cannot be completed within time.

Action

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

Take the following actions depending upon the cause:

When the SFO server is not running

Start up the SFO server, and then start the J2EE application.

When a problem exists in the communication path with the SFO server

Remove the problem and then restart the J2EE application.

When the IP address or the port number of the CORBA Naming Service invoked in the SFO server is specified wrongly

Stop the J2EE server once, and then after setting the correct information in the user property file, start the J2EE server.

If an attempt to negotiate with the SFO server has failed:

Specify the correct settings for the J2EE server based on the message KDJE34207-E or KDJE34246-E output in the message log, and for the SFO server based on the message KDJE34008-E, KDJE34026-E, or KDJE34003-I output in the message log. When the settings of the Web application are changed, you must restart the J2EE application, and when the server ID is changed, you must restart the J2EE server.

When the option "-nosecurity" is not specified in the command cjstartsv during the startup of the SFO server

Specify the -nosecurity option, restart the SFO server, and then start the J2EE application.

When the memory required in the SFO server is insufficient

Revise the estimation of memory required in the SFO server.

When the negotiation has timed out

Check the working state of the SFO server and the memory usage of the machine on which the SFO server is running, as well as CPU usage. In the case of the occurrence of a problem, remove the cause, and then restart the J2EE application.

KDJE34207-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

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

Description

An attempt to negotiate with the SFO server has failed.

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

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

Parameter-name = Setting-value

The contents of the parameter name are as follows:

max sessions: Maximum number of global sessions

max session info size: Maximum value (in bytes) of the size of global session information

max inactive interval: Validity period (in seconds) of the global session

lock timeout: Timeout value for awaiting global session lock

GS control: Control method of the global session

GID cookie name: Name of the HTTP Cookie used to send the global session ID

GID URL param name: Path parameter name of the URL used for sending the global session ID

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

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

byte array enable: Can the session information in the form of byte arrays be inherited

serializable enable: Can the session information in the form of objects of the serializable class be inherited

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

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

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

Action

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

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34208-I

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

The connection with the SFO server was disconnected.

KDJE34209-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: First filter class name

Description

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

Action

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

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

Modify the filter mapping definition, and then redeploy.

KDJE34210-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Invalid URL pattern

Description

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

Action

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

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

Modify the filter mapping definition, and then redeploy.

KDJE34211-E

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

aa....aa: J2EE application name

bb....bb: Context root name

Description

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

Action

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

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

Modify the filter mapping definition, and then redeploy.

KDJE34212-E

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

aa....aa: J2EE application name

bb....bb: Context root name

Description

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

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

Action

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

KDJE34213-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: Global session ID

Description

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

Action

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

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

KDJE34214-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: Global session ID

Description

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

Take action based on the following causes:

The inherited session information could not be de-serialized.

Action

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

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

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

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

KDJE34215-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

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

An error occurred in the SFO server.

Action

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

KDJE34216-I

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

A connection with the SFO server has started.

KDJE34217-I

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

An attempt to reconnect to the SFO server was successful.

KDJE34218-W

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: HTTP session ID

ff....ff: Global session ID

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

For cookie, acquire from the HTTP Cookie of the request

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

Description

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

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

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

Action

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

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

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34219-W

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: HTTP session ID

ff....ff: Global session ID

Description

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

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

Take action based on the following causes:

The size of the global session information exceeds the maximum size.

An object of a type other than the inheritable session information is registered as the global session information.

An attempt to serialize the object to be inherited has failed.

Action

Take the following actions depending upon the cause:

When the size of the global session information exceeds the maximum size

Among the initialization parameters of the filter used for the memory session failover, confirm that the value set in the parameter GSInfoLengthMax is appropriate, and in the case of a problem, modify to correct settings.

When an object of a type other than the inheritable session information is registered as the global session information

Remove this attribute from the global session information either by changing the application or by changing the settings of the keys of the global session information.

When an attempt to serialize the object to be inherited has failed

Take action based on the information of the message KDJE34256-E output in the message log from the J2EE server.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34220-E

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

aa....aa: J2EE application name

bb....bb: Context root name

Description

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

Action

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

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

KDJE34221-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: Global session ID

ff....ff: Error information

Description

An unexpected error occurred in the SFO server.

Action

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

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

Revise the specified timeout period, and change it to the appropriate value.

The SFO server is not running properly.

Check the operating status of the SFO server, and then remove the problem.

A problem occurred in the communication path between the SFO server and the J2EE server.

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

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

KDJE34222-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

An attempt to invoke the SFO server has failed.

Action

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

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

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

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

KDJE34223-W

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description

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

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

Action

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

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

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34224-W

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description

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

When the number of replicable sessions does not reach the maximum, the validity period of the HTTP session might be short.

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

Action

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

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied. Alternatively, change the upper-limit value of the number of HTTP sessions, and then restart.

KDJE34225-E

The size of the global session information exceeds the max size. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, global session ID = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Global session ID

Description

The size of the global session information exceeds the maximum value.

The global session information registered in this HTTP session is not replicated to the SFO server.

Action

Among the initialization parameters of the filter used for the memory session failover, confirm that the value set in the parameter GSInfoLengthMax is appropriate, and in the case of a problem, modify to correct settings.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34226-E

The global session information contains an object that is not permitted. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, global session ID = dd....dd, attribute name = ee....ee, invalid class = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Global session ID

ee....ee: Name of the object registered in the HTTP session that has the type other than the inheritable session information

ff....ff: Class name of the object that has the type other than the inheritable session information

Description

An object of a type other than the inheritable session information is registered in the HTTP session.

The global session information registered in this HTTP session is not replicated to the SFO server.

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

Action

Either change the application or change the key settings of the global session information.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

If a connection is established to the SFO server, restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34228-W

A timeout occurred during a lock request. The rewritable global session information was removed from the HTTP session. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, HTTP session ID = ee....ee, global session ID = ff....ff, locked J2EE server name = gg....gg, locked J2EE server IP = hh....hh)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: HTTP session ID

ff....ff: Global session ID

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

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

Description

This global session cannot be used because a timeout occurred during a global session lock request to the SFO server.

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

Take action based on the following causes:

Either the J2EE server in which the global session is locked has slowed down, or has stopped.

When a request is sent before the response of the previous request is returned, both the requests will be forwarded to different J2EE servers by the schedule functionality of the load balancer. This occurs when requests using the same session are sent simultaneously while using the frames in a page or when a request is sent twice due to the user operation.

Action

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

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34229-W

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: HTTP session ID

ff....ff: Global session ID

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

For cookie, acquire from the HTTP Cookie of the request

For url-rewriting, acquire from the path parameter of the request URL.

Description

This global session cannot be used because it was not found in the SFO server.

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

Take action based on the following causes for not finding the global session:

The validity period has expired.

The processing in the application present on the J2EE server has already deleted the global session.

The global session is lost due to restarting the SFO server.

Action

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

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

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34230-W

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

aa....aa: J2EE application name

bb....bb: Context root name

Description

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

Action

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

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

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34231-I

The global session information was transferred. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee, HTTP session ID = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: Global session ID

ff....ff: HTTP session ID

Description

Since the global session information present on the J2EE server memory is older than the information present on the SFO server, the session information is inherited.

KDJE34232-W

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: HTTP session ID

ff....ff: Global session ID

Description

This global session cannot be used because of failure of the SFO server.

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

KDJE34233-W

A timeout occurred during a get request. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee, locked J2EE server name = ff....ff, locked J2EE server IP = gg....gg)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: Global session ID

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

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

Description

This global session cannot be used because a timeout occurred during a global session lock request to the SFO server. The rewritable global session information registered in the HTTP session was deleted.

Take action based on the following causes:

Either the J2EE server in which the global session is locked has slowed down, or has stopped.

When a request is sent before the response of the previous request is returned, both the requests will be forwarded to different J2EE servers by the schedule functionality of the load balancer. This occurs when requests using the same session are sent simultaneously while using frames in a page or when a request is sent twice due to the user operation.

Action

Check the working state of the J2EE server in which the global session is locked. When no problem exists in the working state of the J2EE server locked, follow the below procedure to change the lock time settings:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34234-W

The global session ID was not found in the SFO server. An attempt to transfer the global session has failed. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee, GS control = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: Global session ID

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

For cookie, acquire from the HTTP Cookie of the request

For url-rewriting, acquire from the path parameter of the request URL

Description

The global session cannot be inherited because it was not found in the SFO server.

Take action based on the following causes for not finding the global session:

The validity period has expired.

The processing in the application present on the J2EE server has already deleted the global session.

The global session is lost due to restarting the SFO server.

Action

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

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

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34235-E

When the session failover functionality is used, the maximum number of HTTP sessions must be specified. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The upper-limit value for the number of HTTP sessions is not set with the functionality for setting the upper-limit value, and also the default value (infinite) is not being used.

When using the memory session failover function, the upper-limit value for the number of HttpSession needs to be set.

Action

Check the setting of the maximum value for the number of HTTP sessions.

To change the settings, stop the J2EE application running in the J2EE server to validate the set value, and then change the settings. Restart the SFO server, and then start the J2EE application.

KDJE34236-I

The global session information was successfully transferred. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee, new HTTP session ID = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: Global session ID

ff....ff: Newly created HTTP session ID

Description

The global session has been inherited.

KDJE34237-W

An attempt to transfer a global session has failed. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: Global session ID

Description

The global session cannot be inherited because of failure in communication with the SFO server.

Action

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

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

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

KDJE34238-W

The number of HTTP sessions has reached the maximum for the J2EE server. An attempt to transfer the global session has failed. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: Global session ID

Description

The HttpSession object for inheritance cannot be created because the number of HTTP sessions on the J2EE server has reached maximum value.

The global session cannot be inherited.

Action

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

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Delete the set information of the corresponding Web application registered in the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied. Alternatively, change the upper-limit value of the number of HTTP sessions, and then restart.

To delete the Web application settings on the SFO server, use one of the following methods:

Restart the SFO server.

Stop all the corresponding Web applications, and then wait until all the global sessions created in those applications have been deleted from the SFO server by the functionality for monitoring the validity period of the global session information.

If deletion is performed with this method, the message KDJE34027-I is displayed.

KDJE34239-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

An attempt to lookup the SFO server by the Naming Service (dd....dd) has failed.

Take action based on the following causes:

The SFO server is not running properly.

A problem occurred in the communication path between the SFO server and the J2EE server.

The address or the port number of the Naming Service specified in the user property file is invalid.

Action

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

If no problem exists in the SFO server and the communication path, check the setting of the address and the port number of the Naming Service specified in the user property file (usrconf.properties). If the setting is invalid, stop the J2EE server and modify to the correct value, and then restart the J2EE server.

KDJE34240-I

The HTTP cookie of the global session ID was not able to be discarded because the response had already committed. (J2EE application = aa....aa, context root = bb....bb, global session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID whose HTTP Cookie cannot be discarded

Description

The HTTP Cookie of the global session ID shown in cc....cc cannot be discarded because the response to the client had already been committed.

Take action based on the following causes:

The HTTP session is disabled in the Web application

The validity period of the HTTP session has expired

The HTTP Cookie cannot be discarded; therefore, an invalid global session ID might be appended to the requests sent henceforth from the client. If an invalid global session ID is sent to the J2EE server, the following messages are output in the Warning level:

Log output by the J2EE server

KDJE34234-W or KDJE34243-W

Log output by the SFO server when a connection is established to the SFO server

KDJE34017-W

KDJE34241-E

The function that adds the server ID to the HTTP cookie is disabled.

Description

The functionality for adding server ID to the HTTP Cookie is not enabled.

When using the memory session failover function, the functionality for adding server ID to the HTTP Cookie needs to be enabled.

Action

Set true in the parameter webserver.session.server_id.enabled of the user property file (usrconf.properties), and then restart the J2EE server.

KDJE34242-W

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: HTTP session ID

ff....ff: Global session ID

Description

This global session cannot be used because of failure in communicating with the SFO server.

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

Action

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

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

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

KDJE34243-W

The global session has already been invalidated. An attempt to transfer the global session has failed. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, global session ID = ee....ee, GS control = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

ee....ee: Global session ID

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

For cookie, acquire from the HTTP Cookie of the request

For url-rewriting, acquire from the path parameter of the request URL

Description

The global session for which there is a request to acquire information is already disabled on the SFO server.

The global session cannot be inherited.

The reason might be a request sent from the client for using a global session whose validity period has expired.

Action

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

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

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Restart the SFO server.

Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the J2EE application.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34244-E

The same name exists in the GSInfoKey-RW or GSInfoKey-R parameter. (J2EE application = aa....aa, context root = bb....bb, invalid session info key = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Several existing key names of the global session information

Description

There are several key names for the same global session.

Action

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

The same key cannot be specified in the initialization parameters (<init-param> tag) GSInfoKey-RW and GSInfoKey-R of the filter used for the session failover.

Revise the settings of the key name indicated in cc....cc such that it is unique among all the key names specified in GSInfoKey-RW and GSInfoKey-R, and then restart the J2EE application in the J2EE server.

KDJE34245-E

An unexpected error occurred during connection processing to the SFO server. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

An unexpected error occurred during the connection processing to the SFO server.

Action

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

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

KDJE34246-E

An attempt to negotiate with the SFO server failed because the server ID for the HTTP session is being used on another server. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, server ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

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

Description

An attempt to negotiate with the SFO server has failed.

Another J2EE server is using the server ID appended to the session ID of the HTTP session set in the J2EE server.

Action

In the server ID appended to the session ID of the HTTP session of the J2EE server, set a unique value for each J2EE server connected to the SFO server, and then restart the J2EE server.

KDJE34247-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

An attempt to lookup the SFO server by the Naming Service (dd....dd) has failed.

Take action based on the following causes:

The SFO server is not running properly.

A problem occurred in the communication path between the SFO server and the J2EE server.

The address or the port number of the Naming Service specified in the user property file is invalid.

Action

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

If no problem exists in the SFO server and the communication path, check the setting of the address and the port number of the Naming Service specified in the user property file (usrconf.properties). If the setting is invalid, stop the J2EE server and modify to the correct value, and then restart the J2EE server.

KDJE34248-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

An attempt to invoke the SFO server has failed.

Action

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

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

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

KDJE34249-E

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

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

An unexpected error occurred during the connection processing to the SFO server.

Action

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

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

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

KDJE34250-E

The specified SFO server was not found in the user property file. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name specified in the Deployment Descriptor (web.xml)

Description

The SFO server name set in the initialization parameters of the filter used for the session failover of the Deployment Descriptor (web.xml) was not found in the SFO server names defined in the user property file.

Action

Check the setting of the Deployment Descriptor (web.xml) and the user property file, and then modify to the correct value.

To change the settings of the Deployment Descriptor (web.xml), you must stop and delete the J2EE application running in the J2EE server, and then re-create and restart the J2EE application. To change the settings of the user property, you must restart the J2EE server.

KDJE34251-E

The required property for the session failover function has not been specified. (property name = aa....aa)

aa....aa: Required property name

Description

The property (aa....aa) required for using the memory session failover function is not set.

Action

Add the required settings in user properties, and then restart the J2EE server.

KDJE34252-E

A memory shortage occurred in the SFO server. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

A memory shortage occurred in the SFO server during the negotiation with the SFO server. Take action based on the following causes:

The memory of SFO server is insufficient.

The maximum size of the global session information set in the Web applications on the J2EE server is large.

The maximum value for the number of HttpSession set in the J2EE server is inappropriately large.

Action

Take the following actions depending upon the cause:

When the memory of the SFO server is insufficient

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

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

When the maximum size of the global session information is large

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

When the maximum value of the number of HttpSession is large

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

KDJE34253-E

A timeout occurred during communication with the SFO server. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

A timeout occurred during the negotiation with the SFO server. Take action based on the following causes:

The SFO server has a large load.

The memory of SFO server is insufficient.

Action

Take the following actions depending upon the cause:

When the SFO server has a large load

Check the state of the SFO server and the J2EE server, as well as the contents of the output log, and then remove the cause of the error.

When the memory of the SFO server is insufficient

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

If the physical memory of the host on which the SFO server is running is less, some time might be taken for securing the memory. By specifying the amount of memory to be secured during the initialization in the option definition file (usrconf.cfg) for the J2EE server, the time taken for securing the memory can be shortened.

KDJE34254-E

The SFO server does not support necessary functionality. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name

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

Description

An attempt to negotiate with the SFO server has failed. The SFO server does not support the necessary functionality.

Action

Upgrade the version of the SFO server to a version that supports the necessary functionality.

KDJE34255-W

The global session information contains an object that is not permitted. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, global session ID = dd....dd, attribute name = ee....ee, invalid class = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Global session ID

ee....ee: Name of the object registered in the HTTP session that has the type other than the inheritable session information

ff....ff: Class name of the object that has the type other than the inheritable session information

Description

An object of a type other than the inheritable session information is registered in the HTTP session. This object is ignored and is not replicated to the SFO server.

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

Action

An object of a type other than the inheritable session information is registered in the HTTP session, and will be inherited.

Check the contents of the application and also the key settings of the global session information.

KDJE34256-E

An attempt to serialize the global session information has failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, global session ID = dd....dd, attribute name = ee....ee, invalid class = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Global session ID

ee....ee: Name of the object registered in the HTTP session that failed to be serialized

ff....ff: Class name of the object that failed to be serialized

Description

An attempt to serialize the global session information has failed. The information of this HTTP session will not be replicated to the SFO server.

Take action based on the following causes of failure in serialization:

The object referenced from the object registered in the HTTP session (object of a serializable class) is not from a serializable class.

The writeObject(java.io.ObjectOutputStream out) method is implemented, and an exception occurred during the serialization.

Action

Determine the cause of the failure in serialization based on the contents of the stack trace output with the message ID KDJE34257-E in the Web servlet log, and then take either of the following actions:

Remove the erroneous object from the target objects to be replicated.

Change the application, and then remove the cause of the error.

KDJE34257-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the serialization of the global session information will be output row-wise.

Take action based on the following causes of failure in the serialization:

The object referenced from the object registered in the HTTP session (object of a serializable class) is not from a serializable class.

The writeObject(java.io.ObjectOutputStream out) method is implemented and an exception occurred during the serialization.

Action

Determine the cause of the failure in serialization based on the contents of the stack trace, and then take either of the following actions:

Remove the object in which the error has occurred from the effect of redundancy.

Change the application, and then remove the cause of the error.

KDJE34258-E

An attempt to deserialize the global session information has failed. (J2EE application = aa....aa, context root = bb....bb, global session ID = cc....cc, attribute name = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Global session ID

dd....dd: Name of the object registered in the HTTP session that failed to be deserialized

Description

The global session information collected from the SFO server could not be inherited because of an attempt to deserialize the global information has failed.

Take action based on the following causes of failure in the deserialization:

The application is different during the serialization and the deserialization, and the change that causes a failure in the deserialization is added to the application.

The readObject() method is implemented and an error occurred internally.

Action

Determine the cause of the failure in deserialization based on the contents of the stack trace output with the message ID KDJE34259-E in the Web servlet log, and then take action.

KDJE34259-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the de-serialization of the global session information will be output row-wise.

Take action based on the following causes of failure in de-serialization:

The application is different during serialization and de-serialization, and the change that causes failure in de-serialization is added to the application.

The readObject() method is implemented, and an error occurred internally.

Action

Determine the cause of failure in de-serialization based on the contents of the stack trace, and then take action.

KDJE34260-I

The global session information was created. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, size(byte) = dd....dd, HTTP session ID = ee....ee, global session ID = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

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

ee....ee: HTTP session ID

ff....ff: Global session ID

Description

The size (in bytes) of the global session information replicated to the SFO server is indicated.

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

KDJE34261-I

The session information was serialized. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, attribute name = dd....dd, class name = ee....ee, size(byte) = ff....ff, HTTP session ID = gg....gg, global session ID = hh....hh)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Name of the object registered in the HTTP session

ee....ee: Class name of the object registered in the HTTP session

ff....ff: Size (in bytes) of the global session information created from the objects registered in the HTTP session

gg....gg: HTTP session ID

hh....hh: Global session ID

Description

The size (in bytes) of the global session information of a single object replicated by the memory session failover functionality is indicated.

The output size includes the size of the key names and the delimiting characters.

KDJE34262-E

The size of global session information exceeded 1,048,576 bytes during its creation. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, attribute name = dd....dd, class name = ee....ee, size(byte) = ff....ff, HTTP session ID = gg....gg, global session ID = hh....hh)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Name of the object registered in the HTTP session that caused an increase in the size

ee....ee: Class name of the object that caused an increase in the size

ff....ff: Size (in bytes) of a single instance of the global session information of the object that caused an increase in the size

gg....gg: HTTP session ID

hh....hh: Global session ID

Description

The size of the global session information that was being created exceeded 1,048,576 bytes. The memory session failover functionality does not support the global session information that exceeds 1,048,576 bytes.

Creation of the global session information will be suspended.

Action

Check the cause for the increase in the size of the global session information, and take either of the following actions:

When unnecessary information is to be inherited

Set up the initialization parameters (<init-param> tag) GSInfoKey-RW or GSInfoKey-R of the filter used for the session failover defined in the Deployment Descriptor (web.xml), and specify only the necessary session information as the target for inheritance.

When the size of the session information to be inherited is large

When the inheritance of the objects of a serializable class is enabled, the objects registered as the session information might include some unnecessary information. In such a case, change the application, and then remove the unnecessary information by changing the objects registered in the HTTP session to reduce the size.

KDJE34263-I

The function for outputting the size of the global session information will now be enabled. The redundant global session information is invalid. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The size output functionality of the global session information will be enabled.

The replication of the global session information will not be performed.

KDJE34264-E

The settings for GSInfoKey-RW or GSInfoKey-R are inconsistent. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The GSInfoKey-RW and GSInfoKey-Re key values specified in the initialization parameters (<init-param> tag) of the filter used for the session failover function conflict.

The settings of both the keys, the key of the rewritable global session and the key of the read-only global session, are specified for the entire session information registered in the HTTP session.

Action

When the entire session information registered in the HTTP session is to be inherited, specify either the rewritable global session information or the read-only global session information.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34265-I

The parameter set to the session failover function is shown as follows. (J2EE application = aa....aa, context root = bb....bb, SFO server = cc....cc, naming service = dd....dd, max sessions = ee....ee, max session info size = ff....ff, max inactive interval = gg....gg, lock timeout = hh....hh, GS control = ii....ii, GID cookie name = jj....jj, GID URL param name = kk....kk, ll....ll, mm....mm, replicatable type = nn....nn)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: SFO server name#

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

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

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

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

hh....hh: Timeout value for awaiting global session lock#

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

cookie: Control is performed by using an HTTP Cookie.

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

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

jj....jj: Name of the HTTP Cookie used for sending the global session ID when ii....ii is either cookie or both. Null character string, when ii....ii is url-rewriting

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

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

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

RW key = Settings-of-keys-for-rewritable-global-session-information

The set values of the keys of global session information will be output in a semicolon (;) delimited series.

When the GSInfoKey-RW parameter is omitted, a null character string will be output in the set value of the key.

RW key(*)

When the entire session information registered in the HTTP session, except the information registered in the key specified in the GSInfoKey-R parameter, is set up as the rewritable global session information, "RW key(*)" will be output.

mm....mm: Settings of keys for read-only global session information

The set information of the key is output in either of the following formats:

R key = Settings-of-keys-for-read-only-global-session-information

The set values of the keys of global session information will be output in a semicolon (;) delimited series.

When the GSInfoKey-R parameter is omitted, a null character string will be output in the set value of the key.

R key(*)

When the entire session information registered in the HTTP session, except the information registered in the key specified in the GSInfoKey-RW parameter, is set up as the rewritable global session information, "R key(*)" will be output.

nn....nn: Type of the inheritable session information

String: Only objects of the java.lang.String class

String or byte[]: Objects or byte arrays of the java.lang.String class

Serializable: Objects of a serializable class

#

When the size estimation functionality of the global session information is enabled, a null character string is output.

Description

The settings of the memory session failover functionality are indicated.

KDJE34266-I

Received global session ID is being used by different HTTP session.(J2EE application = aa....aa, context root = bb....bb, using HTTP session ID = cc....cc, received HTTP session ID = dd....dd, global session ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session that is using the global session ID

dd....dd: Session ID of the HTTP session sent by the request

ee....ee: Global session ID

Description

A request containing a global session ID that is in use by another HTTP session is received. A new global session ID will be issued for this request.

KDJE34300-I

The session fail over (DB) function will now start. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description

The database session failover functionality of the Web application with J2EE application name aa....aa, and context root name bb....bb will start.

KDJE34301-E

The session fail over (DB) function cannot start. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description

The database session failover functionality cannot be started. The Web application cannot be started.

Action

Implement the action mentioned in the message output before this message. After taking the action, either restart the J2EE server or restart the J2EE application.

KDJE34302-I

The default value is applied to the application ID. (default value = aa....aa)

aa....aa: Default value

Description

The default value aa....aa is applied to the application identifier.

KDJE34303-E

When the session fail over (DB) function is used, the maximum number of HTTP sessions must be specified. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description

The upper-limit value for the number of HttpSession objects is not set with the functionality for setting the upper-limit value, and also the default value (infinite) is not being used.

When using the database session failover functionality, a valid value must be set up for the upper-limit value of the number of HttpSession objects.

Starting the Web application will be canceled.

Action

After setting up the upper-limit value for the number of HttpSession objects in the Web application, start the J2EE application.

KDJE34304-E

The resource registered is not the DB Connector. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

Description

The resource registered with the optional name indicated by cc....cc is not a DB Connector.

The startup of the Web application will be interrupted because the database session failover functionality cannot be started.

Action

Check the resource registered with the optional name indicated by cc....cc. If the registered resource is not a DB Connector, release the registered resource, and register a DB Connector.

After the preparations for the DB Connector are complete, start the J2EE application.

KDJE34305-E

The DB Connector is not found. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

Description

The DB Connector used with the database session failover functionality is not registered with the specified name.

The startup of the Web application will be interrupted because the database session failover functionality cannot be started.

Action

Make sure that the DB Connector is registered with the name indicated in cc....cc. If the DB Connector is not registered, register the DB Connector to be used in the J2EE server, and set up an optional name.

If the optional name set up in the DB Connector is wrong, specify the correct optional name.

Remove the problem, and then start the Web application.

KDJE34306-I

An attempt to negotiate has succeeded. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, parameter = (dd....dd))

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Set information of the Web application

Description

The negotiation processing executed during the start of the database session failover functionality has succeeded.

The set information dd....dd of the database session failover functionality that is set up in the Web application is output in the following format:

Parameter-name = Setting-value

The contents of the parameter name are as follows:

max sessions: Maximum number of HttpSession objects

max attribute data size: Maximum size (in bytes) of the attribute information of the HTTP session

max inactive interval: Validity period of the HTTP session defined in web.xml

exclude extensions: Extensions for excluding the database session failover functionality#

integrity mode: Setup value of the integrity assurance mode

session read only uris: Setup value of the read-only request definition functionality of the HTTP session#

thread control queue enabled: Setup value for determining whether or not to return error 503 when the free space of the pending queue for controlling concurrently executing thread count of each Web application is insufficient

exception type backcompat: Setup value of the compatibility option of the exception occurred when the HttpServletRequest#getSession method is executed in the error page of the requests for which DBSFO functionality is to be disabled

session persistence version: Version of the DBSFO functionality

#

If multiple setup values exist, output the values in a series with comma (,) as the delimiter.

KDJE34307-E

An attempt to negotiate has failed. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, invalid parameter = (dd....dd), valid parameter = (ee....ee))

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Set information that caused the negotiation to fail

ee....ee: Correct set information

Description

The negotiation processing executed during the start of the database session failover functionality has failed. The set information of the Web application saved in the database does not match the set information of the Web application for which an attempt has made to start.

Starting the Web application will be canceled.

For the erroneous parameters, the currently settings is output in dd....dd, and the information saved in the database is output in ee....ee, in the following format:

Parameter-name = Setting-value

The contents of the parameter name are as follows:

max sessions: Maximum number of HttpSession objects

max attribute data size: Maximum size (in bytes) of the attribute information of the HTTP session

max inactive interval: Validity period of the HTTP session defined in web.xml

exclude extensions: Extensions for excluding the database session failover functionality#

integrity mode: Setup value of the integrity assurance mode

session read only uris: Setup value of the read-only request definition functionality of the HTTP session#

thread control queue enabled: Setup value for determining whether or not to return error 503 when the free space of the pending queue for controlling concurrently executing thread count of each Web application is insufficient

exception type backcompat: Setup value of the compatibility option of the exception occurred when the HttpServletRequest#getSession method is executed in the error page of the requests for which DBSFO functionality is to be disabled

session persistence version: Version of the DBSFO functionality

In the case of multiple errors, the multiple parameter names are output with comma (,) as delimiters.

#

If multiple setup values exist, output the values in a series with comma (,) as the delimiter.

Action

Revise the settings in accordance with the settings of the Web application saved in the database, as displayed in ee....ee.

For details, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

KDJE34308-W

The table used by the session fail over (DB) function is not found in the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, table = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Name of the table that could not be found

Description

The table used by the database session failover functionality is not found in the database.

Starting the Web application will be canceled.

Action

Make sure that the table with the name output in dd....dd exists in the database connected to the DB Connector.

If the database connected to the DB Connector is invalid, change the settings of the DB Connector to the correct information.

If the table is not created in the database, create the table to be used in the database session failover functionality. For details, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

KDJE34309-E

The table used by the session fail over (DB) function is illegal. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, table = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Name of the table with invalid contents

Description

The contents of the table used in the database session failover functionality are invalid. The database session failover functionality cannot be started.

Starting the Web application will be canceled.

Action

In the case of existence of replicated Web applications that are in the running state, stop all applications.

If the name of the table, that stores the session information, is output in the name of the table with invalid contents, make sure that the maximum value of the number of HttpSession objects set up in the Web application matches the value specified in the SQL file for creating the table that is used during the creation of the table.

Delete, and re-create all three types of tables for the database session failover functionality used by this Web application. For details, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

Start the Web application after re-creating the table.

KDJE34310-I

The watch of the expiration date of the global session information begins. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The monitoring of the validity period of the global session information in the database will start.

KDJE34311-I

Because the expiration date had been passed, the global session information was deleted. (J2EE application = aa....aa, context root = bb....bb, deleted global session information no = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Number of instances of the deleted global session information

Description

Based on the result of the monitoring of the validity period, the global session information for which the validity period had expired was deleted.

KDJE34312-W

An error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information about the exception that occurred

Description

A failure occurred in the communication with the database.

Action

Make sure that the database is operating properly, no problem has occurred in the communication path between the database and J2EE server, and no mistakes exist in the change contents of the SQL file used for creating the table.

If an error occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, solve the problem of the communication path. If a problem occurs in the communication path, the exclusion in the database might not have been released. Before restarting a business, check the invalid connections, and release the unreleased exclusion.

If the change contents of the SQL file used for creating the table are different from the settings of the application, either re-create the table to match the contents or change the settings of the application. For details on the procedure for changing the settings, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

If no problem exists in the change contents of the database, communication path, and the SQL file used for creating the table, check if the settings of the timeout period of the DB Connector connection are correct.

If a short timeout period is set up for the connection, a timeout might occur before the completion of the recovery process, when an error occurs in the database.

Tune the parameters of the DB Connector after considering the recovery period of the database.

KDJE34314-W

An attempt to connect with the database has failed. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information about the exception that has occurred

Description

An attempt to establish a connection to the database has failed.

Action

Make sure that the database is operating properly, and no problem has occurred in the communication path between the database and J2EE server.

If an error occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, solve the problem of the communication path. If a problem occurs in the communication path, the exclusion in the database might not have been released. Before restarting a business, check the invalid connections, and release the unreleased exclusion.

If no problem exists in the database and communication path, check if the settings of the timeout period of the DB Connector connection are correct.

If a short timeout period is set up for the connection, a timeout might occur before the completion of the recovery process, when an error occurs in the database.

Tune the parameters of the DB Connector after considering the recovery period of the database.

KDJE34315-W

The global session information was not found in the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, HTTP session ID = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: HTTP session ID

Description

The global session information was not found in the database.

The HTTP session corresponding to the received session ID has already been invalidated.

Action

A request for using an HTTP session, in which the validity period has expired, is received from the client. Confirm that the value of the validity period set in the HTTP session is correct.

The procedure for changing the validity period of the HTTP session is as follows:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Re-create the three tables used in the database session failover functionality of the database.

Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the business application.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34316-W

The number of replicable sessions in the database has reached the maximum. The HTTP session will now be invalidated. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description

A new session cannot be created because the maximum number of replicable sessions in the database is reached. The created HTTP session will be invalidated.

Action

Check if the upper-limit value of the number of HttpSession objects set up in the Web application or the validity period of an HTTP session is correct.

For details, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

KDJE34317-W

The attribute that cannot be serialized is contained in the HTTP session. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Name of attribute that cannot be serialized

ee....ee: Class name of the object that cannot be serialized

Description

An attribute, that cannot be serialized, is registered in the HTTP session. This attribute will be ignored and not be replicated in the database.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (cc....cc).

Action

An object that is not from a serializable class is registered in the HTTP session as an attribute. Check the contents of the Web application.

KDJE34318-E

An attempt to serialize the attribute information has failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Name of the attribute that failed to be serialized

ee....ee: Class name of the object that failed to be serialized

Description

An attempt to serialize the attribute information of the HTTP session has failed. The information of this HTTP session will not be replicated in the database.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (cc....cc).

Action

Determine the cause of the failure in serialization based on the contents of the stack trace output with the message ID KDJE34319-E in the Web servlet log, and then take either of the following actions:

Remove the erroneous object from the attributes of the HTTP session.

Change the Web application, and then remove the cause of the error from the object that failed to be serialized.

Take action based on the following causes of the failure in serialization:

The object referenced from the object of the attribute that failed to be serialized was not from a serializable class.

The writeObject(java.io.ObjectOutputStream out) method is implemented, and an exception occurred during serialization.

KDJE34319-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the serialization processing of the attribute information of the HTTP session will be output in each line.

Action

Determine the cause of failure in the serialization based on the contents of the stack trace, and then take either of the following actions:

Remove the erroneous object from the attributes of the HTTP session.

Change the Web application, and then remove the cause of the error from the object that failed to be serialized.

Take action based on the following causes of the failure in serialization:

The object referenced from the object of the attribute that failed to be serialized was not from a serializable class.

The writeObject(java.io.ObjectOutputStream out) method is implemented, and an exception occurred during the serialization.

KDJE34320-E

The size of the attribute information exceeds the max size. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description

The size of the attribute information of the HTTP session exceeds the maximum value. The information of this HTTP session will not be replicated to the database.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (cc....cc).

Action

Check if the value, specified in the maximum size of the attribute information of the HTTP session, is correct, and if a problem exists, change to an appropriate value. For details, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

KDJE34321-I

The global session information was successfully transferred. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description

The global session information was inherited successfully.

KDJE34322-I

The global session information was transferred. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description

Because the information of the HTTP session in the memory of the J2EE server is older than the information in the database, the global session information will be inherited.

KDJE34324-W

An attempt to transfer the global session information has failed, because an error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information about the exception that occurred

Description

The global session information cannot be inherited because of failure in communication with the database.

Action

Make sure that the database is operating properly and no problem has occurred in the communication path between the database and the J2EE server.

If an error occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, solve the problem. When the problem occurs, the mutual exclusion of the database might not be released. Before restarting a business, check the invalid connections, and release the unreleased exclusion.

If no problem exists in the database and communication path, check if the settings of the timeout period of the DB Connector connection are correct.

If a short timeout period is set up for the connection, a timeout might occur before the completion of the recovery process, when an error occurs in the database.

Tune the parameters of the DB Connector after considering the recovery period of the database.

KDJE34325-W

An attempt to transfer the global session information has failed, because the global session information was not found in the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, HTTP session ID = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: HTTP session ID

Description

Either the validity period of the HTTP session corresponding to the HTTP session ID received from the client has expired or the HTTP session has already been invalidated during the processing in the Web application running on the J2EE server. The global session information is not found in the database.

The global session cannot be inherited.

Action

A request for using an HTTP session in which the validity period has expired is received from the client.

Confirm that the value of the validity period set in the HTTP session is correct.

The procedure for changing the validity period of the HTTP session is as follows:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

Re-create the three tables used in the database session failover functionality of the database.

Change the settings of the Deployment Descriptor (web.xml), or the setting of the validity period of the HTTP session of the business application.

Create and start J2EE applications from the Web application in which the settings have been applied.

KDJE34326-E

An attempt to deserialize the global session information has failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Name of the attribute that failed to be deserialized

Description

The session could not be inherited because an attempt to deserialize the global session information, acquired from the database, has failed.

Action

Determine the cause of the failure in deserialization based on the contents of the stack trace output with the message ID KDJE34327-E in the Web servlet log, and then take action:

Take action based on the following causes of the failure in deserialization:

The Web application is different during the serialization and the deserialization, and the change that causes failure in the deserialization is added to the application.

The readObject() method is implemented, and an error occurred internally.

KDJE34327-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the de-serialization of the global session information will be output row-wise.

Action

Determine the cause of the failure in deserialization based on the contents of the stack trace, and then take action.

Take action based on the following causes of the failure in deserialization:

The application is different during the serialization and the deserialization, and the change that causes the failure in deserialization is added to the application.

The readObject() method is implemented, and an error occurred internally.

KDJE34328-E

The global session information from the database is illegal. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

Description

The contents of the global session information acquired from the database are invalid.

Action

Make sure that the database is running properly, and no problem exists in the communication path between the database and the J2EE server.

Also make sure that no invalid operation is performed in the database from the outside.

If no problem exists, acquire the maintenance information, and then contact maintenance personnel.

KDJE34329-I

The function for outputting the size of the attribute information will now be enabled. The redundant global session information is invalid. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The functionality for estimating the size of the attribute information of the HTTP session will be enabled.

The global session information will not be replicated.

KDJE34330-I

The attribute information was created. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, size(byte) = dd....dd, HTTP session ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Size (in bytes) of the attribute information of the HTTP session

ee....ee: HTTP session ID

Description

The size (in bytes) of the attribute information of the HTTP session that is replicated in the database is indicated.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (ee....ee).

KDJE34331-I

An attribute was serialized. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, attribute name = dd....dd, class name = ee....ee, size(byte) = ff....ff, HTTP session ID = gg....gg)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Name of the attribute registered in the HTTP session

ee....ee: Class name of the attribute registered in the HTTP session

ff....ff: Size (in bytes) of the byte array created by serializing the attributes registered in the HTTP session

gg....gg: HTTP session ID

Description

The size (in bytes) after serialization of one attribute registered in the HTTP session replicated by the database session failover functionality is indicated.

The output size includes the information about the names of the attributes.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (gg....gg).

KDJE34332-E

The size of global session information exceeded 10,485,760 bytes during its creation. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, attribute name = dd....dd, class name = ee....ee, size(byte) = ff....ff, HTTP session ID = gg....gg)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Name of the attribute that caused an increase in the size

ee....ee: Class name of the attribute that caused an increase in the size

ff....ff: Size (in bytes) of one attribute that caused an increase in the size

gg....gg: HTTP session ID

Description

The size of the created attribute information exceeded 10,485,760 bytes. The database session failover functionality does not support the attribute information of an HTTP session that exceeds 10,485,760 bytes.

Creation of the global session information will be suspended.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (gg....gg).

Action

Some unnecessary information might be registered in the HTTP session as attributes. In such cases, change the application, and then remove the unnecessary attributes registered in the HTTP session to reduce the size.

KDJE34335-E

The memory session failover function and the database session failover function cannot be enabled at the same time.

Description

The memory session failover functionality and the database session failover functionality cannot be used simultaneously.

Starting the Web application will be canceled.

Action

Apply either one of the memory session failover functionality or the database session failover functionality in accordance with the system configuration and requirements.

KDJE34336-W

An error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

Description

An error occurred in the database during the monitoring processing of the validity period.

Action

Make sure that the database is operating properly, no problem has occurred in the communication path between the database and J2EE server, and no mistakes exist in the change contents of the SQL file used for creating the table.

If an error occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, solve the problem. When the problem occurs, the mutual exclusion of the database might not be released. Before restarting a business, check the invalid connections, and release the unreleased exclusion.

If a mistake exists in the settings of the SQL file used for creating the table or in the settings of the application, revise the settings. For details on the procedure for changing the settings, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

If no problem exists in the database, communication path, and SQL file used for creating the table, check if the settings of the timeout period of the DB Connector connection are correct. If a short timeout period is set up for the connection, a timeout might occur before the completion of the recovery process, when an error occurs in the database. Tune the parameters of the DB Connector after considering the recovery period of the database.

KDJE34337-W

The attribute that cannot be serialized is contained in the HTTP session. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Name of attribute that cannot be serialized

ee....ee: Class name of the object that cannot be serialized

Description

An attribute, that cannot be serialized, is registered in the HTTP session. This attribute will be ignored, and will not be replicated to the database.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (cc....cc).

Action

An object that is not from a serializable class is registered in the HTTP session as an attribute. Check the contents of the Web application.

KDJE34338-E

An attempt to serialize the global session information has failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Name of the attribute that failed to be serialized

ee....ee: Class name of the object that failed to be serialized

Description

An attempt to serialize the attribute information of the HTTP session has failed. The information of this HTTP session will not be replicated to the database.

Note that if the HTTP session is invalid during output of this message, null is output to the HTTP session ID (ee....ee).

Action

Determine the cause of the failure in serialization based on the contents of the stack trace output with the message ID KDJE34319-E in the Web servlet log, and then take either of the following actions:

Remove the erroneous object from the attributes of the HTTP session.

Change the Web application, and then remove the cause of the error from the object that has failed to be serialized.

Take action based on the following causes of the failure in serialization:

The object referenced from the object of the attribute that failed to be serialized was not from a serializable class.

The writeObject(java.io.ObjectOutputStream out) method is implemented, and an exception occurred during the serialization.

KDJE34339-E

When the session fail over (DB) function is used, the session cookie delete function must be enabled. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description

The HTTP Cookie deletion functionality of the HTTP session is disabled.

When using the database session failover functionality, the HTTP Cookie deletion functionality of the HTTP session must be enabled.

Starting the Web application will be canceled.

Action

After enabling the HTTP Cookie deletion functionality of the HTTP session, start the J2EE application.

To enable the HTTP Cookie deletion functionality of the HTTP session, set up false in the webserver.session.delete_cookie.backcompat key of the user property file for the J2EE server (usrconf.properties), and then restart the J2EE server.

KDJE34340-E

The specified application ID is already being used by another application. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc, table = dd....dd, J2EE application in table = ee....ee, context root in table = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

dd....dd: Name of the application information table

ee....ee: J2EE application name registered in the application information table

ff....ff: Context root name registered in the application information table

Description

The specified application identifier is already in use by another application.

Action

Take action with any of the following methods:

When you want to start an application same as the existing application

Make sure that the J2EE application name or the context root name are not different from the information of the same application that is already running. If the information is different, revise the settings, and start the application.

When you want to start an application different from the existing application

In the Web application, specify an application identifier that is not in use by another application, re-create the table, and then start the application. For details about how to create the table, see 6. Database session failover functionality in the manual uCosminexus Application Server Expansion Guide.

KDJE34341-W

A property of the session fail over (DB) function controlled by the URI is invalid. The URI will be ignored. (URI = aa....aa)

aa....aa: Invalid URI

Description

An invalid URI is specified in the property for stopping the database session failover functionality by URI. The specified URI will be ignored.

Action

Check whether an invalid URI is specified in the property for stopping the database session failover functionality by URI, and then specify a valid URI. The following URIs are invalid:

Not normalized.

The first character is not a forward slash (/).

KDJE34342-I

The database integrity mode of the session failover (database) functionality has been enabled. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description

The integrity assurance mode of the database session failover functionality is enabled.

KDJE34343-I

The database integrity mode of the session failover (database) functionality has been disabled. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description

The integrity assurance mode of the database session failover functionality is disabled.

KDJE34344-I

Transfer of global sessions at Web application startup will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

Start the process for inheriting the global session information executed during the startup of the Web application.

KDJE34345-W

Transfer of global sessions at Web application startup could not start. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information about the exception that occurred

Description

The process of inheriting the global session information during the startup of the Web application could not be started because a failure occurred during database communication.

Action

Make sure that the database is operating properly and that no problem has occurred in the communication path between the database and J2EE server.

If a failure occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, solve the problem of the communication path. If a problem occurs in the communication path, the exclusion in the database might not be released. Before restarting the business, check the invalid connections, and release the unreleased exclusion.

If no problem exists in the database and the communication path, make sure that the settings of the connection timeout of the DB Connector are correct. If the settings of the connection timeout is short, a timeout might occur before completing the recovery process when a failure occurs in the database. Tune the parameters of the DB Connector in view of the database recovery time.

Note that when this message is output, the global session information continues to remain in the database until the Web application is started again or a request is received and the global session information is inherited. Delete the remaining global session information by the global session information deletion command (cjclearsession).

KDJE34346-W

Transfer of global sessions at Web application startup failed because an error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, DB Connector = dd....dd, exception = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID that could not be inherited

dd....dd: Optional name of the DB Connector

ee....ee: Information about the exception that occurred

Description

The global session information could not be inherited during the startup of the Web application because a failure occurred during database communication.

Action

Make sure that the database is operating properly and that no problem has occurred in the communication path between the database and J2EE server.

If a failure occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, solve the problem of the communication path. If a problem occurs in the communication path, the exclusion in the database might not be released. Before restarting the business, check the invalid connections, and release the unreleased exclusion.

If no problem exists in the database and communication path, make sure that the settings of the connection timeout of the DB Connector are correct.

If the settings of the connection timeout is short, a timeout might occur before completing the recovery process when a failure occurs in the database. Tune the parameters of the DB Connector in view of the database recovery time.

Note that when this message is output, the global session information continues to remain in the database until the Web application is started again or a request is received and the global session information is inherited. Delete the remaining global session information by the global session information deletion command (cjclearsession).

KDJE34347-I

The global session has already been transferred. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description

The global session information that was attempted to be inherited during the startup of the Web application is already inherited in the J2EE server.

KDJE34348-I

The global session has already been transferred to another J2EE server. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description

The global session information that was attempted to be inherited during the startup of the Web application is inherited in another J2EE server.

KDJE34349-I

Transfer of global sessions at Web application startup finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The process of inheriting the global session information during the startup of the Web application has terminated.

KDJE34357-W

A property of the requests that only read HTTP session is invalid. The URI will be ignored. (URI = aa....aa)

aa....aa: Invalid URI

Description

An invalid URI is specified in the definition of the read-only requests of the read-only request definition functionality of HTTP session.

Action

Make sure that an invalid URI is not specified as a read-only request, and specify the correct URI. The following URIs are invalid:

Not normalized.

Not beginning with a forward slash (/).

The length of the URI exceeds 512 characters.

KDJE34358-I

A difference of parameters was detected by negotiation. Processing will continue. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, parameter defined by Web application = (dd....dd), parameter stored in database = (ee....ee))

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information that is currently set in the Web application

ee....ee: Information that is saved in the database

Description

The settings of the Web application saved in the database and the settings of the Web application that was attempted to be started did not match in the negotiation processing executed during the startup of the database session failover functionality; however, the start processing continues.

Regarding the parameter for which the settings did not match, the currently set information is output to dd....dd and the information saved in the database is output to ee....ee in the following format:

Parameter-name = Set-value

The contents of the parameter name are as follows:

max sessions: Maximum value of the number of HttpSession objects

max inactive interval: Valid time period of the HTTP session defined in the web.xml

If multiple setup items do not match, output them by demarcating with a comma (,).

KDJE34359-E

Usage: cjclearsession [-count] [-dbtype {hirdb|oracle}] <URL> <user> <password> <application ID> <server ID>

Description

An argument of the global session information deletion command (cjclearsession) is invalid. Output the usage method.

Action

Specify the correct argument of the global session information deletion command (cjclearsession).

KDJE34360-I

The number of global sessions was successfully acquired. (application ID = aa....aa, server ID = bb....bb, number of global sessions = cc....cc)

aa....aa: Application identifier

bb....bb: Server ID

cc....cc: Global session information count

Description

The global session information count was acquired successfully.

KDJE34361-I

The global sessions has been cleared successfully. (application ID = aa....aa, server ID = bb....bb, count of cleared global sessions = cc....cc)

aa....aa: Application identifier

bb....bb: Server ID

cc....cc: Deleted global session information count

Description

The global session information was deleted successfully.

KDJE34362-E

An attempt to clear the global sessions failed because an error occurred during communication with the database. (application ID = aa....aa, server ID = bb....bb, number of cleared global sessions = cc....cc)

aa....aa: Application identifier

bb....bb: Server ID

cc....cc: Deleted global session information count

Description

An attempt to delete the global session information has failed because an error occurred during database access. The processing will be interrupted.

Action

Make sure that the database is operating properly and that no problem has occurred in the communication path between the database and J2EE server.

If a problem occurs in the communication path, the exclusion in the database might not be released. Check the invalid connections, and release the unreleased exclusion.

After solving the problem, execute the global session information deletion command (cjclearsession).

KDJE34363-E

An attempt to load the JDBC driver class failed. (JDBC driver = aa....aa)

aa....aa: Class name of the JDBC driver

Description

An attempt to load a class of the JDBC driver has failed.

Action

Specify the correct path of the JDBC driver.

KDJE34364-E

An attempt to connect to the database failed. (URL = aa....aa, user = bb....bb)

aa....aa: Connection-destination URL

bb....bb: User connecting to the database

Description

An attempt to connect to the database has failed.

The possible causes of the error are as follows:

The connection-destination URL, connected user, or password is invalid.

The database is not operating normally.

A problem has occurred in the communication path between the database and the J2EE server.

Action

Take action according to the cause of the error.

KDJE34365-E

The table specified by the application ID was not found in the database. (application ID = aa....aa, URL = bb....bb, user = cc....cc)

aa....aa: Application identifier

bb....bb: Connection-destination URL

cc....cc: Users connected to the database

Description

The table corresponding to the specified application identifier did not exist in the database.

The possible causes of the error are as follows:

The application identifier is invalid.

The connection-destination database or user is invalid.

Action

Take action according to the cause of the error.

KDJE34366-E

An error occurred during a database access. (exception = aa....aa)

aa....aa: Information about the exception that occurred

Description

An error occurred during database access.

The possible causes of the error are as follows:

The database is not operating normally.

A problem has occurred in the communication path between the database and the J2EE server.

Action

Take action according to the cause of the error.

KDJE34367-W

An HTTP session was not stored in the database because the number of global sessions has reached the maximum. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

A redundant HTTP session exists because the number of global sessions has reached the maximum count during the creation of the global session information.

Action

Session failover is not performed for a redundant HTTP session.

Note that a redundant HTTP session is updated in the database when some space is made available in the database when operating HTTP sessions thereafter.

KDJE34368-W

An HTTP session was not stored in the database because an error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information about the exception that occurred recently

Description

A redundant HTTP session exists because a database failure occurred when operating the global session information.

Action

Session failover is not performed for a redundant HTTP session.

A redundant HTTP session is updated in the database when the database is accessed successfully during the operation of HTTP sessions thereafter.

KDJE34369-I

HTTP sessions that were not stored in the database were lost. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The redundant HTTP session no longer exists.

KDJE34370-W

An attempt to transfer global sessions at Web application startup failed because the number of HTTP sessions has reached the maximum for the J2EE server. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID that could not be inherited

Description

The global session information could not be inherited when the Web application was started because the number of HTTP sessions on the J2EE server has reached the maximum count.

Action

Check, and if necessary, revise the upper-limit setting of the number of HTTP sessions.

Note that when this message is output, the global session information continues to remain in the database until the Web application is started again or a request is received and the global session information is inherited. Delete the remaining global session information by the global session information deletion command (cjclearsession).

KDJE34371-E

The function that adds the server ID to the HTTP cookie is disabled.

Description

The functionality for adding a server ID to the HTTP Cookie is disabled.

Action

When the integrity assurance mode is disabled, you must enable the functionality for adding the server ID to an HTTP Cookie.

Set true in the webserver.session.server_id.enabled key of the user property file (usrconf.properties), and "different value for each redundant J2EE server" in the webserver.session.server_id.value key.

KDJE34376-W

Error 503 cannot be returned by the queue because thread control by Web application is disabled.

Description

The error 503 cannot be returned by the pending queue because controlling the count of concurrently executing threads of each Web application is disabled.

Action

If true is specified in the webserver.dbsfo.thread_control_queue.enabled key of the user property file (usrconf.properties), specify true in the webserver.container.thread_control.enabled key.

KDJE34377-E

An attempt to clear the global sessions failed because an error occurred during communication with the database. (J2EE application = aa....aa, context root = bb....bb, DB Connector = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Optional name of the DB Connector

dd....dd: Information about the exception that occurred

Description

An attempt to delete the global session information or the global session information whose valid period has expired failed because a failure occurred in the database communication.

Action

Make sure that the database is operating properly and that no problem has occurred in the communication path between the database and J2EE server.

If a failure occurs in the database, take action against the cause according to the procedure for database recovery.

If a problem occurs in the communication path between the database and J2EE server, the exclusion in the database might not be released. Check the invalid connections and release the unreleased exclusion.

If no problem exists in the database and communication path, make sure that the setting of the connection timeout of the DB Connector is correct. If the setting of the connection timeout is short, a timeout might occur before completing the recovery process when a failure occurs in the database. Tune the parameters of the DB Connector in view of the database recovery time.

Note that when this message is output, the global session information continues to remain in the database until the Web application is started again or a request is received and the global session information is inherited. Delete the remaining global session information by the global session information deletion command (cjclearsession).

KDJE34378-E

The output directory could not be created. (directory = aa....aa, cause = bb....bb)

aa....aa: Directory path

bb....bb: Cause message

Description

The output-destination directory for logs cannot be created. The execution of the global session information deletion command (cjclearsession) will be interrupted.

Action

Resolve the problem according to the contents of the cause message, and then re-execute the global session information deletion command (cjclearsession).

KDJE34379-E

An unexpected error occurred. (aa....aa)

aa....aa: Error message for an unexpected exception

Description

An unexpected exception occurred in the global session information deletion command (cjclearsession).

Action

Make sure that another error message is not output in the log.

If no problem exists, obtain the maintenance information and contact maintenance service.

KDJE34380-E

The HttpSession object could not be instantiated because the number of global sessions has reached the maximum. (J2EE application = aa....aa, context root = bb....bb, max global sessions = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Upper-limit value of the global session count

Description

The HttpSession object could not be generated because the global session count has reached the upper-limit value.

Action

The number of global sessions of the database might be too less. Increase the upper-limit value of the global session count of the database as and when required.

KDJE34400-I

The session failover (EADs) functionality will now start. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description

The EADs session failover functionality is started for the Web application with the J2EE application name aa....aa and context root name bb....bb.

KDJE34401-E

The session failover (EADs) functionality could not start. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

Description

The EADs session failover functionality could not be started. The Web application cannot be started.

Action

Take action for the message that is output before this message. After taking action, restart the J2EE server or J2EE application.

KDJE34402-I

The default value will be applied to the application ID. (default value = aa....aa)

aa....aa: Default value

Description

Apply the default value aa....aa to the application identifier.

KDJE34403-E

The session failover (EADs) functionality cannot be used at the same time as the memory session failover functionality or the database session failover functionality.

Description

The EADs session failover functionality cannot be used concurrently with the memory session failover functionality or the database session failover functionality. The Web application initialization will be stopped.

Action

Apply the EADs session failover functionality, memory session failover functionality, or database session failover functionality in conformity with the system configuration and requirements.

KDJE34404-E

The functionality that adds the server ID to HTTP cookies is disabled.

Description

The functionality that adds the server ID to HTTP Cookie is disabled.

Action

With the EADs session failover functionality, the functionality that adds a server ID to HTTP Cookie must be valid.

Specify true in the webserver.session.server_id.enabled property of the Easy Setup definition file and different values to each redundant J2EE server.

KDJE34405-I

Negotiation was successful. (J2EE application = aa....aa, context root = bb....bb, parameter = (cc....cc))

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Web application setup information

Description

The negotiation process was successful during startup of the EADs session failover functionality.

The setup information of the EADs session failover functionality that is specified in the Web application is output with the following format to cc....cc:

Parameter name = Setup value

The contents of the parameter name are as follows:

max sessions: Maximum value of the HttpSession object count

max inactive interval: Validity period of the HTTP session that is defined in web.xml

exclude url patterns: Settings of the EADs session failover inhibit functionality#

session read only url patterns#: Settings for the functionality to define requests to exclusively reference the HTTP session#

session persistence version: Version of the EADs session failover functionality

#

In the case of multiple setup values, the characters are demarcated with commas (,) and output.

KDJE34406-E

Negotiation failed. (J2EE application = aa....aa, context root = bb....bb, invalid parameter = (cc....cc), valid parameter = (dd....dd))

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Setup information that is the cause of negotiation failure

dd....dd: Correct setup information

Description

The negotiation process has failed when starting the EADs session failover functionality. The setup information of the Web application saved in the EADs server and the setup information of the Web application to be started is not in conformity.

The Web application startup is interrupted.

For the error parameters, information that is currently specified is output to cc....cc and information that is saved in the EADs server is output to dd....dd, in the following format:

Parameter name = Setup value

The contents of the parameter name is as follows:

exclude url patterns: Setting of the EADs session failover inhibition functionality#

session read only url patterns: Setting of the functionality to define the requests for referencing HTTP sessions#

session persistence version: Version of the EADs session failover functionality

#

In the case of multiple setup values, the characters are demarcated with commas (,) and output.

Action

Modify the settings in conformity with the setup information of the Web application saved on the EADs server that is displayed in dd....dd.

KDJE34407-E

The cache used by the session failover (EADs) functionality was not found in the EADs server. (J2EE application = aa....aa, context root = bb....bb, cache = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Name of the cache that was not found

Description

The cache used by the EADs session failover functionality was not found on the EADs server.

The startup of the Web application is interrupted.

Action

Confirm that the cache with the name that is output to cc....cc exists on the EADs server.

If the connected EADs server is incorrect, correct the settings of the J2EE server.

KDJE34409-I

A difference in the parameter settings was detected during negotiation. Processing will continue. (J2EE application = aa....aa, context root = bb....bb, parameter defined by Web application = (cc....cc), parameter stored in EADs server = (dd....dd))

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Information currently specified in the Web application

dd....dd: Information saved on the EADs server

Description

With the negotiation process during startup of the EADs session failover functionality, the setting information of the Web application saved on the EADs server and the setting information of the Web application to be started are not in conformity. However, the process will continue.

For a parameter in which setting information is not in conformity, the information that is currently set is output to cc....cc and the information saved on the EADs server is output to dd....dd, in the following format:

Parameter name = Setting value

The parameter contents are as follows:

max sessions: Maximum value of the HttpSession object count

max inactive interval: Validity period of the HTTP session defined with web.xml

If multiple setting information is not in conformity, the information is output with commas (,) as demarcators.

KDJE34410-W

The HTTP session contains an attribute that cannot be serialized. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

dd....dd: Name of the attribute that cannot be serialized

ee....ee: Class name of the object that cannot be serialized

Description

The HTTP session contains an attribute that cannot be serialized. This attribute is ignored and is not duplicated on the EADs server.

Action

The HTTP session contains an object that is not a class that can be serialized as an attribute. Check the contents of the Web application.

KDJE34411-E

An attempt to serialize the attribute information failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

dd....dd: Name of the attribute that failed to be serialized

ee....ee: Class name of the object that failed to be serialized

Description

An attempt to serialize the attribute information of the HTTP session is failed. The information of this HTTP session is not duplicated on the EADs server.

The cause of failure in serialization might be as follows:

The object, referenced from the object of the attribute that failed to be serialized, was not a class that can be serialized

The writeObject(java.io.ObjectOutputStream out) method was implemented, and an exception occurred during serialization.

Action

Identify the cause of the failed attempt to serialized the attribute information based on the contents of the stack trace that is output with the message ID KDJE34412-E to the Web servlet log, and then take any of the following actions:

Exclude the object in which the error occurred from the attribute of the HTTP session.

Change the Web application and remove the cause of the error, from the object that failed to be serialized.

KDJE34412-E

aa....aa

aa....aa: Exceptional stack trace

Description

The stack trace that is thrown with the serialize process of the attribute information of the HTTP session is output for each row.

The following might be the causes for the error in serialization:

The object that was referenced from the object of the attribute that failed to be serialized was not a class that can be serialized.

The writeObject(java.io.ObjectOutputStream out) method was implemented and an exception occurred during the serialization.

Action

Identify the cause of failure in serialization based on the contents of the stack trace and take one of the following actions:

Exclude the object in which the error occurred from the attribute of the HTTP session.

Change the Web application, and remove the cause of the error occurred, from the object that failed to be serialized.

KDJE34413-E

An attempt to deserialize the global session information failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

dd....dd: Name of the attribute that failed in deserialization

Description

An attempt to deserialize the global session information that was acquired from the EADs server failed, so the session cannot be inherited.

The following might be the causes for the error in deserialization:

The Web applications differed during serialization and deserialization, and the change that causes the failure of the attempt to deserialize was added in the Web application.

The readObject() method was implemented and an error occurred internally.

Action

Identify the cause of the deserialization error based on the contents of the stack trace that is output with the KDJE34414-E message ID to the Web servlet log, and take actions.

KDJE34414-E

aa....aa

aa....aa: Stack trace of exception

Description

The stack trace of the exception that is thrown with the deserialization process of the global session information is output to each row.

The following might be the causes for the error in deserialization:

The applications were different during serialization and deserialization and the change that caused the failure of the attempt to deserialize was added to the application.

The readObject() method is implemented and an error occurred independently.

Action

Idenfity the cause of the deserialization error based on the contents of the stack trace, and take actions.

KDJE34415-I

The functionality for outputting the size of the attribute information will now be enabled. The global session information will not be duplicated. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The functionality to output the size of the attribute information of the HTTP session will be enabled.

The global session information will not be duplicated.

KDJE34416-I

HTTP session attribute information was created. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, size (bytes) = dd....dd, HTTP session ID = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Size of the attribute information of the HTTP session (bytes)

ee....ee: Session ID of the HTTP session

Description

The size (unit: bytes) of the HTTP session attribute information duplicated on the EADs server will be displayed.

KDJE34417-I

An attribute registered in the HTTP session was serialized. (J2EE application = aa....aa, context root = bb....bb, request URL = cc....cc, attribute name = dd....dd, class name = ee....ee, size (bytes) = ff....ff, HTTP session ID = gg....gg)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URL

dd....dd: Name of the attribute registered in the HTTP session

ee....ee: Name of the class of the attribute to be registered in the HTTP session

ff....ff: Size in bytes of the array that is created by serializing the attribute registered in the HTTP session

gg....gg: Session ID of the HTTP session

Description

The size (unit: bytes) after partial serialization of the attribute that is registered in the HTTP session duplicated with the EADs session failover functionality will be displayed.

The information of the attribute name will be included in the output size.

KDJE34418-W

The HTTP session contains an attribute that cannot be serialized. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

dd....dd: Name of the attribute that cannot be serialized

ee....ee: Class name of the object that cannot be serialized

Description

The HTTP session contains an attribute that cannot be serialized. This attribute will be ignored, and cannot be duplicated on the EADs server.

Action

The HTTP session includes an object that cannot be serialized as an attribute. Check the Web application contents.

KDJE34419-E

An attempt to serialize the global session information failed. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, attribute name = dd....dd, invalid class = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

dd....dd: Name of the attribute that failed to be serialized

ee....ee: Class name of the object that failed to be serialized

Description

An attempt to serialize the attribute information of the HTTP session has failed. The information of this HTTP session cannot be duplicated.

The following might be the causes for the error in serialization:

The object that was referenced from the object of the attribute that failed to be serialized was not a class that can be serialized.

The writeObject(java.io.ObjectOutputStream out) method was implemented and an exception occurred during the serialization.

Action

Identify the cause of the error in serialization based on the contents of the stack trace that is output with the KDJE34412-E message ID to the Web servlet log, and take any of the following actions:

Exclude the object in which the error occurred from the attribute of the HTTP session.

Change the Web application and remove the cause of the error from the object that failed to be serialized.

KDJE34420-W

An HTTP session was not stored in the EADs slave server because an error occurred during communication with that server. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Information of the last occurred exception

Description

During operations of the global session information, an error occurred in the EADs server and an attempt to update the copy destination server of the session information has failed. Therefore, the HTTP session was degenerated.

Action

The HTTP session that was degenerated because of an error while updating the copy destination server of the session information might not be the target for the session failover.

The degenerated HTTP session will be updated on the EADs server, when access to the EADs server is successful with the operations of the HTTP session thereafter.

KDJE34421-E

An attempt to connect with the EADs server has failed. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Information of the occurred exception

Description

An attempt to connect with the EADs server has failed.

Action

If this message is output, check that the EADs server is operating correctly and that there is no error in the communication route of the EADs and J2EE servers.

If an error occurs on the EADs server, take an action according to the restoration procedures for the EADs server.

If an error occurs in the communication route of the EADs and J2EE server, remove the error.

KDJE34422-E

An attempt to clear the global session information failed because an error occurred during communication with the EADs slave server. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc, application ID = dd....dd, HTTP session ID =ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Information of the occurred exception

dd....dd: Application identifier

ee....ee: Session ID of the HTTP session

Descritpion

An attempt to delete the global session information on the copy destination server or delete the invalid global session information has failed, because an error occurred during communication with the copy destination server in the session information.

Action

If this message is output, the global session information of one level above is remained on the copy destination server.

If this message is output, check that the EADs server is operating correctly and that there is no error in the communication route of the EADs and J2EE servers.

If an error occurs on the EADs server, take action according to the restoration procedures for the EADs server.

If an error occurs in the communication route of the EADs and J2EE server, remove the error.

KDJE34423-E

An attempt to clear the global session information failed because an error occurred in the operation of the EADs server. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Information of the occurred exception

Description

An attempt to delete the global session information or delete the invalid global session information has failed, because an error occurred in communication with the EADs server or in the user functionality that is provided by the EADs session failover functionality.

Action

If this message is output, one or more global session information items remain on the EADs server.

The global session information remaining on the EADs server is inherited by the J2EE server as an available session when the Web application is restarted or when a request with the same session ID is received.

To delete the global session information remaining on the EADs server, use the command for deleting global session information (cjezclearsession command).

If this message is displayed, check whether the EADs server is running normally, and whether there is any problem in the communication channel between the EADs server and J2EE server.

If an error occurs on the EADs server, take action based on the EADs server restoration procedures.

If there is a problem in the communication channel between the EADs server and the J2EE server, resolve the problem.

Also, check whether the user application JAR files provided by the EADs session failover functionality are allocated to the EADs server, and whether any invalid operations are being performed for the EADs server from an external source.

KDJE34424-I

The global session information was inherited successfully. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

Description

The global session information was inherited successfully.

KDJE34425-W

An attempt to inherit the global session information failed because an error occurred in the operation of the EADs server. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Exception information

Description

The global session could not be inherited because an error occurred in communication with the EADs server or an error occurred in a user application provided by the EADs session failover functionality.

Action

Check whether the EADs server is running normally and whether there is any problem in the communication channel between the EADs and J2EE servers.

If an error occurs on the EADs server, take an action based on the EADs server restoration procedures.

If there is an error in the communication channel between the EADs and J2EE servers, resolve the error.

Also, check whether the user application JAR files provided by the EADs session failover functionality are allocated to the EADs server, and whether any invalid operations are being performed for the EADs server from an external source.

KDJE34426-W

An attempt to inherit the global session information failed because that information was not found in the EADs server. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Session ID of the HTTP session

Description

The HTTP session corresponding to the HTTP session ID received from the client has expired or has already been disabled due to the processing of the Web application on the J2EE server.

A global session could not be inherited because the global session information was not found on the EADs server.

Action

A request using an expired HTTP session is received from the client.

Check whether the validity period specified for the HTTP session is appropriate.

KDJE34427-W

An HTTP session was not stored in the EADs server because an error occurred during communication with the EADs server. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Latest exception information

Description

A degenerated HTTP session exists because an EADs server error occurred during the operation of global session information.

Action

A degenerated HTTP session is not subject to session failover.

A degenerated HTTP session is updated on the EADs server when the session can access the EADs server during the subsequent HTTP session operations.

KDJE34428-I

HTTP sessions that were not stored in the EADs server have been deleted. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The degenerated HTTP sessions were deleted.

KDJE34429-I

Processing to inherit global session information at Web application startup will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The processing to inherit global session information used at Web application startup will start.

KDJE34430-I

Processing to inherit global session information at Web application startup finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The processing to inherit the global session information used at Web application startup finished.

KDJE34431-W

Processing to inherit global session information at Web application startup could not start. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Exception information

Description

An error occurred in communication with the EADs server, or the processing to inherit global session information used for starting the Web applications, provided by the EADs session failover functionality, could not start.

Action

If this message is displayed, eliminate the cause of the error based on the following action and then restart the Web application, or global session information will remain on the EADs server until a request is received and information is inherited.

To delete the remaining global session information, use the command for deleting global session information (cjezclearsession command).

If this message is displayed, check whether the EADs server is running normally and whether there is any problem in the communication channel between the EADs and J2EE servers.

If an error occurs on the EADs server, take action based on the EADs server restoration procedures.

If there is an error in the communication channel between the EADs and J2EE servers, eliminate the error.

Also, check whether the user application JAR files provided by the EADs session failover functionality are allocated to the EADs server and whether any invalid operations are being performed for the EADs server from an external source.

KDJE34432-I

The global session information to be inherited has already been inherited. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

Description

The global session information to be inherited during Web application startup has already been inherited on the J2EE server.

KDJE34434-W

Processing to inherit global session information at Web application startup failed because an error occurred during communication with the EADs server. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, exception = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID that could not be inherited

dd....dd: Exception information

Description

The global session information could not be inherited during Web application startup because an error occurred during communication with the EADs server.

Action

If this message is displayed, eliminate the cause of the error based on the following action and then restart the Web application, or global session information will remain on the EADs server until a request is received and information is inherited.

To delete the remaining global session information, use the command for deleting global session information (cjezclearsession command).

If this message is displayed, check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

If there is an error in the communication channel between the EADs and J2EE servers, eliminate the error.

KDJE34435-W

Processing to inherit global session information at Web application startup failed because the number of HTTP sessions reached the maximum for the J2EE server. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID that could not be inherited

Description

The global session information could not be inherited at Web application startup because the number of HTTP sessions reached the maximum number for the J2EE server.

Action

If this message is displayed, eliminate the cause of the error based on the following action and then restart the Web application, or global session information will remain on the EADs server until a request is received and information is inherited.

To delete the remaining global session information, use the command for deleting global session information (cjezclearsession command).

When this message is displayed, review that the settings are appropriate for the maximum number of HttpSessions.

KDJE34436-E

The global session information obtained from the EADs server is invalid. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The content of global session information acquired from the EADs server is invalid.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs server and J2EE server.

Also, check whether any invalid operations are being performed for the EADs server from an external source.

KDJE34437-W

A definition of the session failover (EADs) functionality is invalid. The URL pattern will be ignored. (URL pattern = aa....aa)

aa....aa: Invalid URL pattern

Description

An invalid URL pattern has been specified in the definition of the EADs session failover control functionality.

Action

Check whether an invalid URL pattern has been specified in the definition of the EADs session failover control functionality, and specify a valid URL pattern. The following URL patterns are invalid:

A URL pattern that is not normalized.

A URL pattern that does not begin with / (forward slash) and *..

KDJE34438-W

A definition of a request that only reads HTTP sessions is invalid. The URL pattern will be ignored. (URL pattern = aa....aa)

aa....aa: invalid URL pattern

Description

An invalid URL pattern is specified in the definition of a reference request with the reference request definition functionality for an HTTP session.

Action

Check whether an invalid URL pattern is specified as the reference request for an HTTP session, and specify the valid URL pattern. The following URL patterns are invalid:

A URL pattern that is not normalized.

A URL pattern that does not begin with / (forward slash) and *..

KDJE34439-E

Usage: cjezclearsession [-count] <J2EE server name> <application ID> {-all | <server ID>}

Description

An argument of the cjezclearsession command is incorrect. The command usage will be output.

Action

Specify the correct argument for the cjezclearsession command.

KDJE34440-I

The number of items of global session information was acquired successfully. (application ID = aa....aa, server ID = bb....bb, number of items of global session information = cc....cc)

aa....aa: Application identifier

bb....bb: Server ID (empty string if -all is specified for the cjezclearsession command)

cc....cc: Number of items of global session information

Description

The number of items of global session information is acquired.

KDJE34441-I

The global session information was cleared successfully. (application ID = aa....aa, server ID = bb....bb, number of items of cleared global session information = cc....cc)

aa....aa: Application identifier

bb....bb: Server ID (empty string if -all is specified for the cjezclearsession command)

cc....cc: Number of global session information items that are deleted

Description

The deletion of global session information is complete.

KDJE34442-E

An attempt to clear the global session information failed because an error occurred during communication with the EADs server. (application ID = aa....aa, server ID = bb....bb, number of items of cleared global session information = cc....cc)

aa....aa: Application identifier

bb....bb: server ID (empty string if -all is specified for the cjezclearsession command)

cc....cc: Number of global session information items that are deleted

Description

An attempt to delete global session information failed because an error occurred while the EADs server was being accessed or an error occurred in the user application provided by the EADs session failover functionality. The processing will be cancelled.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

Also, check whether any invalid operations are being performed for the EADs server from an external source.

After eliminating the error, re-execute the cjezclearsession command.

KDJE34443-E

Initialization of the EADs client failed. (exception = aa....aa)

aa....aa: Exception and message

Description

An attempt to initialize the EADs client has failed.

Action

Check whether the EADs client is installed, whether the path of the JAR files provided by the EADs client is set in the CLASSPATH environment variable, and whether the J2EE server specified in the argument of the cjezclearsession command exists.

Check whether the EADs server is running normally, whether there is any error in the communication channel between the EADs server and the J2EE server, and whether the EADs client settings specified in the Easy Setup Definition file are correct.

After eliminating the error, re-execute the cjezclearsession command.

KDJE34444-E

An attempt to connect the session information cache in the EADs server failed. (cache name = aa....aa, exception = bb....bb)

aa....aa: Cache name

bb....bb: Exception and message

Description

An attempt to connect to the session information cache on the EADs server has failed.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

Check whether the name of the session information cache is correct.

After resolving the problem, re-execute the cjezclearsession command.

KDJE34445-E

An attempt to acquire the session ID list failed.

Description

An attempt to acquire the session ID list failed.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

Check whether the user application JAR files provided by the EADs session failover functionality are allocated to the EADs server.

After eliminating the error, re-execute the cjezclearsession command.

KDJE34446-E

An error occurred during access to EADs. (exception = aa....aa)

aa....aa: Exception and message

Description

An error occurred during the EADs access.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

KDJE34447-E

The output directory could not be created. (directory = aa....aa, cause = bb....bb)

aa....aa: Directory path

bb....bb: Message describing the cause

Description

The log output directory could not be created.

The execution of the cjezclearsession command will be cancelled.

Action

Resolve the error based on the message describing the cause, and then re-execute the cjezclearsession command.

KDJE34448-E

An unexpected error occurred. (aa....aa)

aa....aa: Error message for the unexpected exception

Description

An unexpected exception occurred in the cjezclearsession command.

Action

Check whether any other error message is output to the log.

KDJE34449-E

aa....aa

aa....aa: Stack trace

Description

An exception occurred. The stack trace will be output.

Action

Check the cause of the exception from stack trace information of the exception and the log output elsewhere.

KDJE34450-W

A property value is invalid. The default value will be used. (aa....aa = bb....bb, default value = cc....cc)

aa....aa: Property name

bb....bb: Value

cc....cc: Default value

Description

A property value is invalid. The default value will be used.

Action

To change the property aa....aa from the default value, correct the aa....aa property value, and then re-execute the command.

KDJE34451-W

A property value is not specified. The default value will be used. (property = aa....aa, default value = bb....bb)

aa....aa: Property name

bb....bb: Default value

Description

A property value is not specified. The default value will be used.

Action

To change the property aa....aa from the default value, correct the aa....aa property value, and then re-execute the command.

KDJE34452-E

The application information obtained from the EADs server is invalid. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The application information acquired from the EADs server is invalid.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs server and the J2EE server.

Also, check whether any invalid operations are being performed for the EADs server from an external source. If there is no error, collect the maintenance information, and then contact maintenance personnel.

KDJE34453-E

Another application is already using the specified application ID. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc, J2EE application in cache = dd....dd, context root in cache = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

dd....dd: J2EE application name registered in the application information cache

ee....ee: Context root name registered in the application information cache

Description

The specified application identifier is being used by a different application.

Action

To start the same application as the existing application, check whether the J2EE application name or context root name differs from the information of the same application that is already running. If the information is different, correct the settings and then start the application.

To start an application different from the existing application, specify an application identifier that is not used for other applications in the Web application, and then start the application.

KDJE34454-E

Initialization of the EADs client failed. (exception = aa....aa)

aa....aa: Exception information

Description

An attempt to initialize the EADs client has failed.

Action

Take the following action:

Check whether the EADs client is installed and whether the JAR file provided by the EADs client is specified in the option definition file for J2EE servers as the container extension library.

Check whether the EADs server is running normally, whether there is any error in the communication channel between the EADs and J2EE servers, and whether the EADs client settings specified in the Easy Setup Definition file are correct.

For details on the EADs client settings, see 4.11.2 Parameters used for setting up the user properties for the J2EE server in the uCosminexus Application Server Definition Reference Guide.

If the EADs client is not installed, install the EADs client and then set up the EADs session failover functionality.

If the JAR file provided by the EADs client is not specified in the option definition file for J2EE servers as the container extension library, specify the required settings.

If an error occurs on the EADs server, take actions based on the EADs server restoration procedure.

If there is an error in the communication channel between the EADs and J2EE servers, resolve the error.

If the EADs client settings specified in the Easy Setup Definition file are incorrect, correct the settings.

KDJE34455-E

An error occurred in a user function supplied by the session failover (EADs) functionality. (J2EE application = aa....aa, context root = bb....bb, application ID = cc....cc, function name = dd....dd, exception = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Application identifier

dd....dd: Name of the function where the exception occurred

ee....ee: Exception information

Description

An error occurred in the user function provided by the EADs session failover functionality.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

Also, check whether any invalid operations are being performed for the EADs server from an external source.

If there is no error, collect the maintenance information and then contact maintenance personnel.

KDJE34456-E

An error occurred in a user function supplied by the session failover (EADs) functionality. (function name = aa....aa, exception = bb....bb)

aa....aa: Name of the function where the exception occurred

bb....bb: Exception information

Description

An error occurred in the user function provided by the EADs session failover functionality.

Action

Check whether the EADs server is running normally and whether there is any error in the communication channel between the EADs and J2EE servers.

Also, check whether any invalid operations are being performed for the EADs server from an external source.

If there is no error, collect the maintenance information and then contact maintenance personnel.

KDJE34500-W

Occupied memory exceeded the threshold. A Full GC might be executed. (Rate1 = aa....aa , Rate2 = bb....bb , Rate3 = cc....cc , Free [New] = dd....dd , Total [New] = ee....ee , Max [New] = ff....ff , Free [Old] = gg....gg , Total [Old] = hh....hh , Max [Old] = ii....ii , Free [Permanent] = jj....jj , Total [Permanent] = kk....kk , Max [Permanent] = ll....ll , Threshold = mm....mm)

aa....aa:

When serial GC is valid:

Memory occupied (in %) by Old area

Ratio of the Old area consumption size and Old area total size

When G1 GC is valid:

Usage (in %) in the Java heap area

Ratio of the consumption size of the Java heap area with respect to the total size of the Java heap area

bb....bb:

When serial GC is valid:

The percentage (%) of total memory occupied by the New area with respect to the maximum free memory of the Old area

Ratio of the New area total size and Old area maximum free size

When G1 GC is valid: -1

cc....cc: Memory usage (in %) in the Metaspace area

Ratio of the Metaspace area consumption size with respect to the maximum memory size of the Metaspace area

dd....dd: Free memory size (in bytes) of New area

ee....ee: Total memory size (in bytes) of New area

ff....ff:

When serial GC is valid:

Maximum memory size (in bytes) of New area

When G1 GC is valid: -1

gg....gg: Free memory size (in bytes) of Old area

hh....hh: Total memory size (in bytes) of Old area

ii....ii:

When serial GC is valid:

Maximum memory size (in bytes) of Old area

When G1 GC is valid:

Maximum memory size (in bytes) of the Java heap area

jj....jj: Free memory size (in bytes) of Metaspace area

kk....kk: Total memory size (in bytes) of Metaspace area

ll....ll: Maximum memory size (in bytes) of Metaspace area

mm....mm: Threshold value

Description

The heap and memory usage has exceeded the threshold value.

A Full GC might be performed.

Action

This message is displayed when a constant amount of heap and memory is used. There is no problem even if this message is displayed at regular intervals. However, if a Full GC occurs more often than expected, confirm that the heap and memory size settings are appropriate and, if necessary, revise them. If there is no improvement even after changing to an appropriate heap and memory size, check whether a memory leak is occurring in the application, and if necessary, revise the settings.

KDJE34510-W

An invalid property value is specified (aa....aa = bb....bb).The default value (cc....cc) will be used.

aa....aa: Property key

bb....bb: Set value

cc....cc: Default value

Description

The default value will be used because an invalid value was acquired from the property file.

Take action based on the following causes:

An invalid value is specified in the properties.

A value outside the valid range has been specified.

Action

Revise the set value of the property key (aa....aa) of the user property file for the J2EE server (usrconf.properties).

KDJE34511-I

Full GC monitoring will now start.

Description

Full GC monitoring will start.

KDJE34512-I

Full GC monitoring will now stop.

Description

Full GC monitoring will stop.

KDJE34513-I

Full GC monitoring is not supported.

Description

The JDK you are using does not support Full GC monitoring.

Action

To monitor Full GC, use the JDK described in the preconditions.

KDJE34520-W

The number of used file descriptors has reached the threshold value. (Current = aa....aa, Max = bb....bb, Threshold = cc....cc)

aa....aa: Number of current file descriptors

bb....bb: Maximum number of usable file descriptors

cc....cc: Threshold value of number of file descriptors

Description

The number of used file descriptors has reached the threshold value.

Action

Revise the set value# of the property or the system, set the correct value, and then restart the J2EE server.

#

You need not check and change the settings for a platform on which the system settings cannot be changed.

KDJE34521-I

File descriptor monitoring will now start.

Description

File descriptor monitoring will start.

KDJE34522-I

File descriptor monitoring will now stop.

Description

File descriptor monitoring will stop.

KDJE34523-I

The monitoring of a file descriptor is not performed. (reason = aa....aa)

aa....aa: Reason

Not supported: Since monitoring is not supported

Description

File descriptor monitoring is not performed due to reason (aa....aa).

KDJE34524-W

The control method of the HTTP session in the received request does not match the control method of the global session. (J2EE application = aa....aa, context root = bb....bb, HTTP session ID = cc....cc, GS control = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP session ID

dd....dd: Control method of the global session specified in the Web application

cookie will be output in the case of the HTTP Cookie, while url-rewriting will be output in the case of the URL re-writing.

Description

The control method of the HTTP session in the received request is different from the control method of the global session set up in the Web application.

Take action based on the following causes:

The settings of the control method of the global session are invalid.

The settings for load balancing are invalid.

The settings of the HTTP Cookie of the Web client are different from the system request.

For this request, the HTTP session will continue, but the memory session failover functionality will not be enabled.

Note that if the HTTP session is disabled when this message is displayed, null might be output to the HTTP session ID (cc....cc).

Action

Take action as follows:

When the settings of the control method of the global session are erroneous

Confirm that the initialization parameters of the filter used for the session failover function and the value set in the parameter GSessionControl is appropriate, and in the case of a problem, modify to correct settings.

To change the settings, follow the procedure given below:

Stop and delete the J2EE applications of the system that contains the Web application whose settings are to be changed.

If a connection is established to the SFO server, restart the SFO server.

Create and start J2EE applications from the Web application in which the settings have been applied.

When the settings of load balancing are invalid

Check the settings of load balancing, and change the settings for load distribution to the appropriate J2EE server by the control method of the global session.

When the settings of the HTTP Cookie of the Web client are different from the system request

Even when the system configuration and the settings are correct, the Web client might send the HTTP session with a method different from the requested method. In a Web application, create an application by considering the case when the Web client sends an incorrect request.

KDJE34530-W

An invalid property value is specified (aa....aa = bb....bb). The default value (cc....cc) will be used.

aa....aa: Property key

bb....bb: Set value

cc....cc: Default value

Description

The default value will be used because an invalid value was acquired from the property file.

Take action based on the following causes:

An invalid value is specified in the properties.

A value outside the valid range has been specified.

Action

Revise the set value of the property key (aa....aa) of the user property file for the J2EE server (usrconf.properties).

KDJE34540-W

The number of generated threads has reached the threshold value. (Current = aa....aa, Max = bb....bb, Threshold = cc....cc)

aa....aa: Current number of threads

bb....bb: Maximum number of generated threads

cc....cc: Threshold value of number of threads

Description

The number of generated threads has reached the threshold value.

Action

Revise the set value# of the property or the system, set the correct value, and then restart the J2EE server.

#

You need not check and change the settings for a platform on which the system settings cannot be changed.

KDJE34541-I

Thread monitoring will now start.

Description

Thread monitoring will start.

KDJE34542-I

Thread monitoring will now stop.

Description

Thread monitoring will stop.

KDJE34543-I

The monitoring of a thread is not performed. (reason = aa....aa)

aa....aa: Reason

Not supported: Since monitoring is not supported

Description

Thread monitoring is not performed due to the reason (aa....aa).

KDJE34550-W

An invalid property value is specified (aa....aa = bb....bb). The default value (cc....cc) will be used.

aa....aa: Property key

bb....bb: Set value

cc....cc: Default value

Description

The default value will be used because an invalid value was acquired from the property file.

Take action based on the following causes:

An invalid value is specified in the properties.

A value outside the valid range has been specified.

Action

Revise the set value of the property key (aa....aa) of the user property file for the J2EE server (usrconf.properties).

KDJE34580-W

The number of thread dump files has exceeded the threshold. Move the existing thread dump files to another directory. (Rate = aa....aa, Current = bb....bb, Max = cc....cc, Threshold = dd....dd)

aa....aa: Ratio (%) of the current number with respect to the maximum number of thread dump files

bb....bb: Current number of thread dump files

cc....cc: Maximum number (set number) of the thread dump files

dd....dd: Threshold value (%) (set value) of thread dump monitoring

Description

The number of thread dump files has reached the threshold value.

Action

Immediately save the thread dump in another directory.

KDJE34581-E

The number of thread dump files has exceeded the maximum. New thread dump files cannot be created until the existing thread dump files are moved to another directory. (Rate = aa....aa, Current = bb....bb, Max = cc....cc, Threshold = dd....dd)

aa....aa: Ratio (%) of the current number with respect to the maximum number of thread dump files

bb....bb: Current number of thread dump files

cc....cc: Maximum number (set number) of the thread dump files

dd....dd: Threshold value (%) (set value) of thread dump monitoring

Description

The number of thread dump files has reached the maximum value.

New thread dump cannot be output until the existing thread dump is saved in another directory.

Action

Immediately save the thread dump in another directory.

KDJE34582-W

An invalid property value is specified (aa....aa = bb....bb). The default value (cc....cc) will be used.

aa....aa: Property key

bb....bb: Specified value (invalid value) of property

cc....cc: Default value of property

Description

The property value is invalid. The default value will be used.

Action

Revise the property, set the correct value, and then restart the J2EE server.

KDJE34583-I

Thread dump monitoring will now start.

Description

Thread dump monitoring will start.

KDJE34584-I

Thread dump monitoring will now stop.

Description

Thread dump monitoring will stop.

KDJE34621-W

The number of queued requests awaiting execution has exceeded the threshold. (J2eeApplicationName = aa....aa, ContextRootName = bb....bb, Rate = cc....cc, Current = dd....dd, Max = ee....ee, Threshold = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Ratio (%) of the current value to the maximum value of the requests stored in each Web application or the default pending queue

dd....dd: Current value of the requests stored in each Web application or the default pending queue

ee....ee: Maximum value (set value) of the requests stored in each Web application or the default pending queue

ff....ff: Threshold value (%) (set value) to monitor each Web application or the default HTTP request pending queue

Description

The number of requests stored in each Web application or the default pending queue has reached the threshold value.

In the case of default request pending queue, "-" is output for J2EE application name (aa....aa) and the context root name (bb....bb). When the maximum value of the number of requests stored in each Web application or the default pending queue is not specified, "-" is output for the ratio (cc....cc) of the current value to the maximum value of the requests stored in each Web application or the default pending queue, and for the maximum value of requests stored in each Web application or the default pending queue (ee....ee).

Action

The available resources are becoming lesser, therefore, revise the setting before they are depleted.

KDJE34622-I

HTTP request queue monitoring will now start.

Description

The monitoring of the default HTTP request pending queue will start.

KDJE34623-I

HTTP request queue monitoring will now stop.

Description

The monitoring of the default HTTP request pending queue will stop.

KDJE34624-I

HTTP request queue monitoring will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The monitoring of HTTP request pending queue of each Web application will start.

KDJE34625-I

HTTP request queue monitoring will now stop. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The monitoring of HTTP request pending queue of each Web application will stop.

KDJE34626-W

An invalid application attribute value was specified. The default value will be used. (J2EE application = aa....aa, context root = bb....bb, monitoring target resource = cc....cc, dd....dd = ee....ee, default value = ff....ff).

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Resource (request queue or session) to be monitored

dd....dd: Tag name

ee....ee: Value

ff....ff: Default value

Description

An invalid value was specified in the application attribute. The default value will be used.

Action

To change the application attribute to other than the default value, stop the application, and then change the application attribute. After this, restart the application.

KDJE34627-I

The monitoring of a HTTP request queue is not performed. (J2EE application = aa....aa, context root = bb....bb, reason = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Reason

Description

The monitoring of each Web application and default HTTP request pending queue is not performed.

In the case of default request pending queue, "-" is output for J2EE application name (aa....aa) and the context root name (bb....bb).

The reason for not monitoring each Web application and default HTTP request pending queue is displayed in cc....cc.

The contents displayed in cc....cc, and their meaning is described below:

No target

Since 0 is specified as the maximum value of each Web application and default request pending queue, monitoring target does not exist.

No upper limit

The upper limit for each Web application and default request pending queue is not set up, and therefore, the threshold value for output of alert becomes disabled.

If, however, file output of the monitoring results is enabled even when alert output is disabled, this message will not be output, and each Web application and default HTTP request pending queue will be monitored.

KDJE34630-W

An invalid property value is specified (aa....aa = bb....bb). The default value (cc....cc) will be used.

aa....aa: Property key

bb....bb: Set value

cc....cc: Default value

Description

The default value will be used because an invalid value was acquired from the property file.

Take action based on the following causes:

An invalid value is specified in the properties.

A value outside the valid range has been specified.

Action

Revise the set value of the property key (aa....aa) of the user property file for the J2EE server (usrconf.properties).

KDJE34640-W

The number of sessions has exceeded the threshold. (J2eeApplicationName = aa....aa, ContextRootName = bb....bb, Rate = cc....cc, Current = dd....dd, Max = ee....ee, Threshold = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Ratio (%) of current number of sessions with respect to the number of sessions that can be created

dd....dd: Current number of sessions that have been created

ee....ee: Number of sessions that can be created (set value)

ff....ff: Threshold value (%) (set value) of session monitoring

Description

The number of sessions has reached the threshold value.

When the maximum value is not set, "-" is output for the percentage and maximum value.

Action

The available resources are becoming lesser, therefore, revise the setting before they are depleted.

KDJE34641-I

Monitoring of the number of sessions will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

Monitoring of the number of sessions will start.

KDJE34642-I

Monitoring of the number of sessions will now stop. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

Monitoring of the number of sessions will stop.

KDJE34643-I

The monitoring of a number of sessions is not performed. (J2EE application = aa....aa, context root = bb....bb, reason = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Reason

Description

Monitoring of a number of sessions is not performed.

The reason for not monitoring a number of sessions is displayed in cc....cc.

The contents displayed in cc....cc, and their meaning is described below:

No target

Since 0 is specified as the upper limit of the number of sessions that can be created, monitoring target does not exist.

No upper limit

The upper limit of the number of sessions that can be created is not set, therefore, the threshold value for output of alert becomes disabled.

If, however, file output of the monitoring results is enabled even when alert output is disabled, this message is not output, and the number of sessions is monitored.

KDJE34660-W

The number of connections in use exceeded the threshold. (ResourceName = aa....aa, Rate = bb....bb, Active = cc....cc, Free = dd....dd, Current = ee....ee, Min = ff....ff, Max = gg....gg, Threshold = hh....hh, All = ii....ii)

aa....aa: Resource adapter name

bb....bb: Connection pool usage

cc....cc: Number of connections in use

dd....dd: Number of unused connections

ee....ee: Current number of connections

ff....ff: Minimum number of connections

gg....gg: Maximum number of connections

hh....hh: Threshold value

ii....ii: Total number of connections

Description

The number of connections in use has exceeded the threshold value.

Action

The number of free connections is becoming lesser, therefore, revise the setting.

KDJE34661-W

The number of connections in use reached the maximum number. (ResourceName = aa....aa, Rate = bb....bb, Active = cc....cc, Free = dd....dd, Current = ee....ee, Min = ff....ff, Max = gg....gg, Threshold = hh....hh, All = ii....ii)

aa....aa: Resource adapter name

bb....bb: Connection pool usage

cc....cc: Number of connections in use

dd....dd: Number of unused connections

ee....ee: Current number of connections

ff....ff: Minimum number of connections

gg....gg: Maximum number of connections

hh....hh: Threshold value

ii....ii: Total number of connections

For details about the information shown in the message, see Table 4-12 Contents output in the monitoring information for connection pool depletion in 4.3.5 (7) in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide.

Description

The number of connections in use has reached the maximum number.

Action

Revise the set values related to the connection pool.

KDJE34662-W

No value was specified for property aa....aa of pool monitoring. The default value will be used. (bb....bb)

aa....aa: Property key

bb....bb: Default value of property

Description

The property value is not specified. The default value will be used.

Action

Revise the property, and then set the correct value.

KDJE34663-W

An invalid value was specified for property aa....aa of pool monitoring. The default value will be used. (bb....bb)

aa....aa: Property key

bb....bb: Default value of property

Description

The specified property value is invalid. The default value will be used.

Action

Revise the property, and then set the correct value.

KDJE34670-I

Pool monitoring will now start. (resource display name = aa....aa)

aa....aa: Resource display name

Description

Pool monitoring will start.

KDJE34671-I

Pool monitoring will now stop. (resource display name = aa....aa)

aa....aa: Resource display name

Description

Pool monitoring will stop.

KDJE34672-I

The pool monitoring was not executed. (resource display name = aa....aa)

aa....aa: Resource display name

Description

Pool monitoring is not executed.

KDJE34990-W

The management event issuing function is unavailable. (reason = aa....aa)

aa....aa: Reason code

Description

The management event issuing functionality is unavailable.

Action

Take action based on the reason code.

Table 7‒2: List of reasons indicated in KDJE34990-W

Reason code

Action

-1

Management Server is not installed. When using the management event issuing functionality, install Management Server, specify the required settings in the management event issuing functionality, and then restart the J2EE server.

-2

The management event issuing functionality is unavailable. When using the management event issuing functionality, confirm that the necessary settings have been specified, and then restart the J2EE server.

When using the functionality for monitoring resource depletion instead of using the management event issuing functionality, set the following properties as false:

Table 7‒3: Properties for disabling the alert output of monitoring depletion of each resource

Function name

Property name

File

Memory monitoring

ejbserver.watch.memory.enabled

usrconf.properties

File descriptor monitoring

ejbserver.watch.fileDescriptor.enabled

Thread monitoring

ejbserver.watch.thread.enabled

Thread dump monitoring

ejbserver.watch.threaddump.enabled

HTTP request pending

queue monitoring

ejbserver.watch.defaultRequestQueue.enabled

<watcher-enabled> present below <thread-control>

HITACHI WAR property file

Session count monitoring

<watcher-enabled> present below <http-session>

Connection pool monitoring

WatchEnabled

HITACHI Connector property file

KDJE34991-W

An invalid property value is specified (aa....aa = bb....bb). The default value (cc....cc) will be used.

aa....aa: Property key

bb....bb: Specified value (invalid value) of property

cc....cc: Default value of property

Description

The property value is invalid. The default value will be used.

Action

Revise the property, set the correct value, and then restart the J2EE server.

KDJE37000-E

Usage:

Format1: cjimportapp [servername] [-nameserver providerURL] [-test] [-nodelete] -f applicationfilename [-f applicationfilename ...]

Format2: cjimportapp [servername] [-nameserver providerURL] [-test] -a applicationdirectorypath

Format3: cjimportapp [servername] [-nameserver providerURL] [-test] [-nodelete] -f applicationfilename -d extractdirectorypath

Description

This message describes the usage method of the cjimportapp command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37001-E

Usage : cjexportapp [servername] [-nameserver providerURL] -f applicationfilename -name applicationname [-raw | -normal]

Description

This message describes the usage method of the cjexportapp command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37004-E

Usage : cjstartapp [servername] [-nameserver providerURL] -name applicationname

Description

This message describes the usage method of the cjstartapp command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37005-E

Usage:

Format1: cjstopapp [servername] [-nameserver providerURL] [-test] -name applicationname

Format2: cjstopapp [servername] [-nameserver providerURL] [-test] -name applicationname -t timeoutseconds

Format3: cjstopapp [servername] [-nameserver providerURL] [-test] -name applicationname -cancel

Format4: cjstopapp [servername] [-nameserver providerURL] [-test] -name applicationname -t timeoutseconds -force

Description

This message describes the usage method of the cjstopapp command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37006-E

Usage:

Format1: cjdeleteapp [servername] [-nameserver providerURL] [-test] -name applicationname [-name applicationname ...]

Format2: cjdeleteapp [servername] [-nameserver providerURL] -type ejb -name applicationname -resname ejb-jardisplayname [-resname ejb-jardisplayname ...]

Format3: cjdeleteapp [servername] [-nameserver providerURL] -type war -name applicationname -resname wardisplayname [-resname wardisplayname ...]

Format4: cjdeleteapp [servername] [-nameserver providerURL] -type filter -name applicationname -resname wardisplayname/filterdisplayname [-resname wardisplayname/filterdisplayname ...]

Format5: cjdeleteapp [servername] [-nameserver providerURL] -type rar -name applicationname -resname rardisplayname [-resname rardisplayname ...]

Description

This message describes the usage method of the cjdeleteapp command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37007-E

The cjimportapp command failed. Contact the system administrator.

Description

The cjimportapp command has failed because an unexpected exception occurred.

If the exception messages starting with nnnn (n is a number) is followed by this message , see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37008-E

The cjexportapp command failed. Contact the system administrator.

Description

The cjexportapp command has failed because an unexpected exception has occurred.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37011-E

The cjstartapp command failed. Contact the system administrator.

Description

The cjstartapp command has failed because an unexpected exception occurred.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37012-E

The cjstopapp command failed. Contact the system administrator.

Description

The cjstopapp command has failed because an unexpected exception occurred.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37013-E

The cjdeleteapp command failed. Contact the system administrator.

Description

The cjdeleteapp command has failed because an unexpected exception has occurred.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37016-E

No option is specified.

Description

An argument other than the J2EE server name is specified, without specifying any option.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37020-E

The same options have been specified repeatedly. (option = [aa....aa] )

aa....aa: Option

Description

The same options have been specified multiple times.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37021-I

The server has been migrated successfully. Server name = aa....aa

aa....aa: Server name

Description

The environment of the server (aa....aa) is migrated successfully.

KDJE37022-E

The server failed to be migrated. Reason = aa....aa

aa....aa: Reason for failure

Description

Server migration will be interrupted because of failure during the migration of server environment.

Action

Take action based on the reason for failure (aa....aa). The following reasons for failure are displayed in aa....aa:

Internal error

contact maintenance personnel.

Messages beginning with nnnn (n is a number)

See 25.3 Messages when Errors Occur while Changing and Importing the Working Directory, and then take action.

Reason for failure other than the above

Remove the cause of failure based on the reason, and then re-execute the cjenvupdate command.

KDJE37023-E

Invalid option. Option=[aa....aa]

aa....aa: Option

Description

An undefined option is specified.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37024-E

Different export types have been specified simultaneously.

Description

Different export type options have been specified simultaneously.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37027-E

The server was not found. (name = [aa....aa])

aa....aa: Server name

Description

The J2EE server was not found.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37028-E

Application is running. Name=[aa....aa]

aa....aa: Application name

Description

The J2EE application is running.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37029-E

aa....aa was not found.

aa....aa: Application name or resource name

Description

The J2EE application or resource (aa....aa) was not found.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37033-E

The application is not running. (name = [aa....aa])

aa....aa: Application name

Description

The J2EE application is not running.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37035-E

Deploying failed.

Description

Deploying failed.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37037-E

The file does not exist. (path = [aa....aa])

aa....aa: File path

Description

The file does not exist.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37039-E

The specified file type is a directory. (path = [aa....aa])

aa....aa: File path

Description

The specified file path (aa....aa) is a directory.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37041-I

Application has been imported successfully. Name=[aa....aa]

aa....aa: EAR file name

Description

An attempt to import the EAR file was successful.

KDJE37042-I

Application has been exported successfully. Name=[aa....aa]

aa....aa: Application name

Description

An attempt to export the J2EE application was successful.

KDJE37045-I

Application has been started successfully. Name=[aa....aa]

aa....aa: Application name

Description

An attempt to start the J2EE application was successful.

KDJE37046-I

Application has been stopped successfully. Name=[aa....aa]

aa....aa: Application name

Description

An attempt to stop the J2EE application was successful.

KDJE37047-I

Application has been deleted successfully. Name=[aa....aa]

aa....aa: Application name

Description

An attempt to delete the J2EE option was successful.

KDJE37048-I

Connecting to aa....aa...

aa....aa: Server name

Description

Connecting to the J2EE server.

KDJE37049-I

Searching aa....aa...

aa....aa: Application name

Description

The J2EE application (aa....aa) is being searched.

KDJE37050-I

Importing aa....aa...

aa....aa: Application name

Description

The J2EE application (aa....aa) is being imported.

KDJE37051-I

Exporting aa....aa...

aa....aa: Application name

Description

The J2EE application (aa....aa) is being exported.

KDJE37054-I

Starting aa....aa.

aa....aa: Application name

Description

The J2EE application (aa....aa) is being started.

KDJE37055-I

Stopping aa....aa...

aa....aa: Application name

Description

The application (aa....aa) is being stopped.

KDJE37056-I

Deleting aa....aa...

aa....aa: Application name or resource name

Description

The J2EE application or the resource (aa....aa) is being deleted.

KDJE37057-E

Another command is already running.

Description

Another command is already running.

Action

Terminate the other command, and then re-execute the command this command.

KDJE37058-E

Usage: cjresetsv [servername] [-nameserver providerURL]

Description

This message describes the usage method of the cjresetsv command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37059-E

The Naming Service was not found.

Description

The Naming Service was not found.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37060-W

The server has been migrated with errors. Some applications or resources could not be migrated. Server name = aa....aa

aa....aa: Server name

Description

The applications or resources cannot be migrated because they contain DDs that cannot be converted.

Action

If you want to use the applications or resources that were not migrated, reset the resources and applications.

KDJE37061-W

The application definition cannot be converted because the resource specified for the reference resolution has a problem. display-name = aa....aa, res-name(in resource-ref) = bb....bb

aa....aa: Application display name

bb....bb: Maintenance information

Description

The application definition cannot be converted because the resource specified in the reference resolution has a problem.

An attempt to deploy an application, in which a resource with a problem is specified in the reference resolution, will fail

Action

After migration of the environment finishes, reset this resource.

KDJE37062-W

The application definition cannot be converted because the resource specified for the reference resolution has a problem. display-name = aa....aa, res-name(in cmp-map) = bb....bb

aa....aa: Application display name

bb....bb: Maintenance information

Description

The application definition cannot be converted because the resource specified in the reference resolution has a problem.

An attempt to deploy an application, in which a resource with a problem is specified in the reference resolution, will fail

Action

After migration of the environment finishes, reset this resource.

KDJE37063-W

The resource definition cannot be converted. display-name = aa....aa, Reason = bb....bb

aa....aa: Resource display name

bb....bb: Maintenance information

Description

The resource definition cannot be converted.

The resource containing this DD will not be migrated. The application, in which this resource is specified in the reference resolution, cannot be deployed.

Action

After migration of the environment finishes, reset this resource.

KDJE37064-W

An attempt to output the audit log has failed. (detail = aa....aa)

aa....aa: Detailed information

Description

An attempt to output the audit log failed.

Action

Remove the cause of the failure by referencing the detailed information or messages output before this message.

Alternatively, remove the cause of the failure by referencing the audit log.

KDJE37103-E

Usage:

Format1: cjimportres [servername] [-nameserver providerURL] -type ejb -f ejb-jarfilename [-f ejb-jarfilename ...]

Format2: cjimportres [servername] [-nameserver providerURL] -type war -f warfilename [-f warfilename ...]

Format3: cjimportres [servername] [-nameserver providerURL] -type datasource -resname datasourcedisplayname -c datasourcefilename -f JDBCdriverfilename [-f JDBCdriverfilename ...]

Description

This message describes the usage method of the cjimportres command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37105-E

Usage:

Format1: cjaddapp [servername] [-nameserver providerURL] -type ejb -name applicationname -resname ejb-jardisplayname [-resname ejb-jardisplayname ...]

Format2: cjaddapp [servername] [-nameserver providerURL] -type war -name applicationname -resname wardisplayname [-resname wardisplayname ...]

Format3: cjaddapp [servername] [-nameserver providerURL] -type filter -name applicationname -warname wardisplayname -c filterpropertyfilename [-c filterpropertyfilename ...]

Format4: cjaddapp [servername] [-nameserver providerURL] -type rar -name applicationname -resname rardisplayname [-resname rardisplayname ...]

Description

This message describes the usage method of the cjaddapp command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37107-E

Usage:

Format1: cjdeleteres [servername] [-nameserver providerURL] -type ejb -resname ejb-jardisplayname [-resname ejb-jardisplayname ...]

Format2: cjdeleteres [servername] [-nameserver providerURL] -type war -resname wardisplayname [-resname wardisplayname ...]

Format3: cjdeleteres [servername] [-nameserver providerURL] -type datasource -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format4: cjdeleteres [servername] [-nameserver providerURL] -type mail -resname maildisplayname [-resname maildisplayname ...]

Format5: cjdeleteres [servername] [-nameserver providerURL] -type rar -resname rardisplayname [-resname rardisplayname ...]

Description

This message describes the usage method of the cjdeleteres command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37108-E

Usage:

Format1: cjgetappprop [servername] [-nameserver providerURL] -name applicationname [-encoding encoding-name] -c applicationpropertyfilename

Format2: cjgetappprop [servername] [-nameserver providerURL] -name applicationname -type ejb -resname higherresourcename[/lowerresourcename] [-encoding encoding-name] -c applicationpropertyfilename

Format3: cjgetappprop [servername] [-nameserver providerURL] -name applicationname -type war -resname higherresourcename[/lowerresourcename] [-encoding encoding-name] -c applicationpropertyfilename

Format4: cjgetappprop [servername] [-nameserver providerURL] -name applicationname -type rar -resname rardisplayname [-encoding encoding-name] -c applicationpropertyfilename

Description

This message describes the usage method of the cjgetappprop command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37109-E

Usage:

Format1: cjgetresprop [servername] [-nameserver providerURL] -type ejb -resname higherresourcename[/lowerresourcename] [-encoding encoding-name] -c ejb-jarpropertyfilename

Format2: cjgetresprop [servername] [-nameserver providerURL] -type war -resname higherresourcename[/lowerresourcename] [-encoding encoding-name] -c warpropertyfilename

Format3: cjgetresprop [servername] [-nameserver providerURL] -type datasource -resname datasourcedisplayname [-encoding encoding-name] -c datasourcepropertyfilename

Format4: cjgetresprop [servername] [-nameserver providerURL] -type mail -resname maildisplayname [-encoding encoding-name] -c mailpropertyfilename

Format5: cjgetresprop [servername] [-nameserver providerURL] -type rar -resname rardisplayname [-encoding encoding-name] -c rarpropertyfilename

Description

This message describes the usage method of the cjgetresprop command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37110-E

Usage:

Format1: cjsetappprop [servername] [-nameserver providerURL] -name applicationname -c applicationpropertyfilename

Format2: cjsetappprop [servername] [-nameserver providerURL] -name applicationname -type ejb -resname higherresourcename[/lowerresourcename] -c applicationpropertyfilename

Format3: cjsetappprop [servername] [-nameserver providerURL] -name applicationname -type war -resname higherresourcename[/lowerresourcename] -c applicationpropertyfilename

Format4: cjsetappprop [servername] [-nameserver providerURL] -name applicationname -type rar -resname rardisplayname -c applicationpropertyfilename

Description

This message describes the usage method of the cjsetappprop command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37111-E

Usage:

Format1: cjsetresprop [servername] [-nameserver providerURL] -type ejb -resname higherresourcename[/lowerresourcename] -c ejb-jarpropertyfilename

Format2: cjsetresprop [servername] [-nameserver providerURL] -type war -resname higherresourcename[/lowerresourcename] -c warpropertyfilename

Format3: cjsetresprop [servername] [-nameserver providerURL] -type datasource -resname datasourcedisplayname -c datasourcepropertyfilename

Format4: cjsetresprop [servername] [-nameserver providerURL] -type mail -resname maildisplayname -c mailpropertyfilename

Format5: cjsetresprop [servername] [-nameserver providerURL] -type rar -resname rardisplayname -c rarpropertyfilename

Description

This message describes the usage method of the cjsetresprop command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37112-E

Usage:

Format1: cjcopyres [servername] [-nameserver providerURL] -type ejb -src ejb-jardisplayname -dst ejb-jardisplayname

Format2: cjcopyres [servername] [-nameserver providerURL] -type war -src wardisplayname -dst wardisplayname

Format3: cjcopyres [servername] [-nameserver providerURL] -type datasource -src datasourcedisplayname -dst datasourcedisplayname

Format4: cjcopyres [servername] [-nameserver providerURL] -type mail -src maildisplayname -dst maildisplayname

Format5: cjcopyres [servername] [-nameserver providerURL] -type rar -src rardisplayname -dst rardisplayname

Description

This message describes the usage method of the cjcopyres command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37113-E

Usage:

Format1: cjlistapp [servername] [-nameserver providerURL]

Format2: cjlistapp [servername] [-nameserver providerURL] [-test] -name applicationname -type ejb [-resname higherresourcename]

Format3: cjlistapp [servername] [-nameserver providerURL] [-test] -name applicationname -type war [-resname higherresourcename]

Format4: cjlistapp [servername] [-nameserver providerURL] [-test] -name applicationname -type rar [-spec | -resname rardisplayname -outbound | -resname rardisplayname -inbound | -resname rardisplayname -listenertype messagelistenertypename]

Description

This message describes the usage method of the cjlistapp command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37114-E

Usage:

Format1: cjlistres [servername] [-nameserver providerURL] -type ejb [-resname higherresourcename]

Format2: cjlistres [servername] [-nameserver providerURL] -type war [-resname higherresourcename]

Format3: cjlistres [servername] [-nameserver providerURL] -type datasource

Format4: cjlistres [servername] [-nameserver providerURL] -type mail

Format5: cjlistres [servername] [-nameserver providerURL] -type rar [-spec | -resname rardisplayname -outbound | -resname rardisplayname -inbound | -resname rardisplayname -listenertype messagelistenertypename]

Description

This message describes the usage method of the cjlistres command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37119-E

Usage:

Format1: cjaddsec [servername] [-nameserver providerURL] -type user -name username -password password

Format2: cjaddsec [servername] [-nameserver providerURL] -type role -name rolename

Description

This message describes the usage method of the cjaddsec command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37120-E

Usage:

Format1: cjdeletesec [servername] [-nameserver providerURL] -type user -name username

Format2: cjdeletesec [servername] [-nameserver providerURL] -type role -name rolename

Description

This message describes the usage method of the cjdeletesec command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37121-E

Usage:

Format1: cjlistsec [servername] [-nameserver providerURL] -type user

Format2: cjlistsec [servername] [-nameserver providerURL] -type user -name username

Format3: cjlistsec [servername] [-nameserver providerURL] -type role

Format4: cjlistsec [servername] [-nameserver providerURL] -type role -name rolename

Description

This message describes the usage method of the cjlistsec command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37122-E

Usage: cjmapsec [servername] [-nameserver providerURL] -role rolename -user username [-user username ...]

Description

This message describes the usage method of the cjmapsec command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37123-E

Usage: cjunmapsec [servername] [-nameserver providerURL] -role rolename -user username [-user username ...]

Description

This message describes the usage method of the cjunmapsec command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37125-E

Usage:

Format1: cjclearpool [servername] [-nameserver providerURL] [-type jdbc] [-mode {normal|plan}] -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format2: cjclearpool [servername] [-nameserver providerURL] -type connector [-mode {normal|plan}] -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format3: cjclearpool [servername] [-nameserver providerURL] -type connector [-mode {normal|plan}] [-test] -name applicationdisplayname -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format4: cjclearpool [servername] [-nameserver providerURL] [-mode {normal|plan}] -resall

Description

This message describes the usage method of the cjclearpool command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37126-E

Usage: cjgetrarprop [servername] [-nameserver providerURL] -resname displayname [-encoding encoding-name] -c propertyfilename

Description

This message describes the usage method of the cjgetrarprop command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37127-E

Usage: cjsetrarprop [servername] [-nameserver providerURL] -resname displayname -c propertyfilename

Description

This message describes the usage method of the cjsetrarprop command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37128-E

Usage:

Format1: cjclosecn [servername] [-nameserver providerURL] -l [-verbose] -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format2: cjclosecn [servername] [-nameserver providerURL] -l [-verbose] -resall

Format3: cjclosecn [servername] [-nameserver providerURL] -t seconds -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format4: cjclosecn [servername] [-nameserver providerURL] -t seconds -resall

Format5: cjclosecn [servername] [-nameserver providerURL] -resname datasourcedisplayname -cid connectionID [-cid connectionID ...]

Description

This message describes the usage method of the cjclosecn command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37129-E

Usage: cjdeployrar [servername] [-nameserver providerURL] -resname rardisplayname [-resname rardisplayname ...]

Description

This message describes the usage method of the cjdeployrar command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37130-E

Usage: cjundeployrar [servername] [-nameserver providerURL] -resname rardisplayname [-resname rardisplayname ...]

Description

This message describes the usage method of the cjundeployrar command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37131-E

Usage: cjstartrar [servername] [-nameserver providerURL] -resname rardisplayname

Description

This message describes the usage method of the cjstartrar command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37132-E

Usage: cjstoprar [servername] [-nameserver providerURL] -resname rardisplayname

Description

This message describes the usage method of the cjstoprar command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37133-E

Usage:

Format1: cjlistrar [servername] [-nameserver providerURL] [-clusterpool] [-spec]

Format2: cjlistrar [servername] [-nameserver providerURL] -resname displayname -outbound

Format3: cjlistrar [servername] [-nameserver providerURL] -resname displayname -inbound

Format4: cjlistrar [servername] [-nameserver providerURL] -resname displayname -listenertype messagelistenertypename

Description

This message describes the usage method of the cjlistrar command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37134-E

Usage: cjwebeditpool [-host hostname] [-port portnumber] -c poolsettingfilename

Description

This message describes the usage method of the cjwebeditpool command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37135-E

Usage: cjwebchangedbid [-host hostname] [-port portnumber] -olddbid DatabaseID -newdbid DatabaseID

Description

This message describes the usage method of the cjwebchangedbid command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37136-E

Usage: cjwebdeletepool [-host hostname] [-port portnumber] -dbid DatabaseID

Description

This message describes the usage method of the cjwebdeletepool command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37137-E

Usage:

Format1: cjweblistpool [-host hostname] [-port portnumber] -listtype dblist [-f outputfilename]

Format2: cjweblistpool [-host hostname] [-port portnumber] -dbid DatabaseID -listtype poollist [-f outputfilename]

Format3: cjweblistpool [-host hostname] [-port portnumber] -dbid DatabaseID -userid UserID -listtype connectionlist [-f outputfilename]

Format4: cjweblistpool [-host hostname] [-port portnumber] -listtype all [-f outputfilename]

Description

This message describes the usage method of the cjweblistpool command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37138-E

Usage: cjwebclearpool [-host hostname] [-port portnumber] [-mode {normal |plan}] [-dbid DatabaseID]

Description

This message describes the usage method of the cjwebclearpool command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37139-E

Usage:

Format1: cjwebclosepool [-host hostname] [-port portnumber] -dbid DatabaseID -type connectionid -cid connectionID

Format2: cjwebclosepool [-host hostname] [-port portnumber] -dbid DatabaseID -type timeout -time timeout

Description

This message describes the usage method of the cjwebclosepool command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37140-E

Usage: cjimportlibjar [servername] [-nameserver providerURL] [-test] -name applicationname -f libraryjarfilename [-f libraryjarfilename ...]

Description

This message describes the usage method of the cjimportlibjar command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37141-E

Usage: cjdeletelibjar [servername] [-nameserver providerURL] [-test] -name applicationname -f libraryjarfilename [-f libraryjarfilename ...]

Description

This message describes the usage method of the cjdeletelibjar command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37142-E

Usage: cjlistlibjar [servername] [-nameserver providerURL] [-test] -name applicationname

Description

This message describes the usage method of the cjlistlibjar command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37143-E

Usage: cjreplaceapp [servername] [-nameserver providerURL] [-test] -name applicationname -f {earfilename | warfilename} [-t timeoutseconds] [-replaceDD]

Description

This message describes the usage method of the cjreplaceapp command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37144-E

Usage: cjupdateapp [servername] [-nameserver providerURL] -name applicationname -c updatelistfilename [-t timeoutseconds]

Description

This message describes the usage method of the cjupdateapp command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37145-E

Usage:

Format1: cjchmodapp [servername] [-nameserver providerURL] -test -name applicationname -mode normal

Format2: cjchmodapp [servername] [-nameserver providerURL] -name applicationname -mode test

Description

This message describes the usage method of the cjchmodapp command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37146-E

Usage: cjgetstubsjar [servername] [-nameserver providerURL] [-test] -name applicationname -d stubsjardirectory

Description

This message describes the usage method of the cjgetstubsjar command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37147-E

Usage:

Format1: cjtestres [servername] [-nameserver providerURL] -type datasource -resname datasourcedisplayname [-resname datasourcedisplayname ...]

Format2: cjtestres [servername] [-nameserver providerURL] -type mail -resname maildisplayname [-resname maildisplayname ...]

Format3: cjtestres [servername] [-nameserver providerURL] -type rar -resname rardisplayname [-resname rardisplayname ...]

Format4: cjtestres [servername] [-nameserver providerURL] [-test] -name applicationname -type rar -resname rardisplayname [-resname rardisplayname ...]

Description

This message describes the usage method of the cjtestres command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37148-E

Usage:

Format1: cjlistthread [servername] [-nameserver providerURL]

Format2: cjlistthread [servername] [-nameserver providerURL] -detail

Description

This message describes the usage method of the cjlistthread command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37149-E

Usage: Format1: cjstopthread [servername] [-nameserver providerURL] -tid threadID [-tid threadID]

Description

This message describes the usage method of the cjstopthread command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37150-E

Usage: cjrenameapp [servername] [-nameserver providerURL] [-test] -name applicationname -newname newapplicationname

Description

This message describes the usage method of the cjrenameapp command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37151-E

Usage: cjexportrar [servername] [-nameserver providerURL] -f resourcefilename -resname displayname [ -raw | -normal]

Description

This message describes the usage method of the cjexportrar command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37152-E

Usage: cjlisttrn [servername] [-nameserver providerURL] [-gid globalTransactionId] [-pending] [-time elapsedTime] [-bqual] [-tp1]

Description

This message describes the usage method of the cjlisttrn command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37153-E

Usage: cjlisttrnfile [servername] [-gid globalTransactionId] [-bqual]

Description

This message describes the usage method of the cjlisttrnfile command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37154-E

Usage:

Format1: cjlistpool [servername] [-nameserver providerURL] -resname rardisplayname [-resname rardisplayname ...]

Format2: cjlistpool [servername] [-nameserver providerURL] [-test] -name applicationname -resname rardisplayname [-resname rardisplayname ...]

Format3: cjlistpool [servername] [-nameserver providerURL] -resall

Description

This message describes the usage method of the cjlistpool command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37155-E

Usage: cjdeletejb [servername] [-nameserver providerURL] -resname javabeansresourcedisplayname [-resname javabeansresourcedisplayname ...]

Description

This message describes the usage method of the cjdeletejb command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37156-E

Usage:cjgetjbprop [servername] [-nameserver providerURL] -resname javabeansresourcedisplayname [encoding encoding-name] -c javabeansresourcepropertyfilename

Description

This message describes the usage method of the cjgetjbprop command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37157-E

Usage:cjsetjbprop [servername] [-nameserver providerURL] -resname javabeansresourcedisplayname -c javabeansresourcepropertyfilename

Description

This message describes the usage method of the cjsetjbprop command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37158-E

Usage: cjlistjb [servername] [-nameserver providerURL]

Description

This message describes the usage method of the cjlistjb command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37159-E

Usage: cjstartjb [servername] [-nameserver providerURL] -resname javabeansresourcedisplayname

Description

This message describes the usage method of the cjstartjb command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37160-E

Usage: cjstopjb [servername] [-nameserver providerURL] -resname javabeansresourcedisplayname

Description

This message describes the usage method of the cjstopjb command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37161-E

Usage:cjreloadapp [servername] [-nameserver providerURL] [-test] -name applicationname [-t timeoutseconds]

Description

This message describes the usage method of the cjreloadapp command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37162-E

Usage:

Format1: cjimportjb [servername] [-nameserver providerURL] -f javabeansresourcejarfilename -c propertyfilename

Format2: cjimportjb [servername] [-nameserver providerURL] -d javabeansresourcedirectoryname -c propertyfilename

Description

This message describes the usage method of the cjimportjb command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37163-E

Usage: cjsuspendpool [servername] [-nameserver providerURL] -resname rardisplayname [-resname rardisplayname ...]

Description

This message describes the usage method of the cjsuspendpool command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37164-E

Usage: cjresumepool [servername] [-nameserver providerURL] -resname rardisplayname [-resname rardisplayname ...]

Description

This message describes the usage method of the cjresumepool command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37165-E

Usage: cjgencmpsql [servername] [-nameserver providerURL] [-test] -name applicationname [-resname ejbjardisplayname/ejbdisplayname]

Description

This message describes the usage method of the cjgencmpsql command.

Action

Check the arguments and value of the command, and then re-execute the command.

KDJE37166-E

Usage: cjcommittrn [servername] [-nameserver providerURL] -gid globalTransactionId

Description

This message describes how to use the cjcommittrn command.

Action

Check the arguments and values of the command, and then re-execute the command.

KDJE37167-E

Usage: cjrollbacktrn [servername] [-nameserver providerURL] -gid globalTransactionId

Description

This message describes how to use the cjrollbacktrn command.

Action

Check the arguments and values of the command, and then re-execute the command.

KDJE37168-E

Usage: cjforgettrn [servername] [-nameserver providerURL] -gid globalTransactionId

Description

This message describes how to use the cjforgettrn command.

Action

Check the arguments and values of the command, and then re-execute the command.

KDJE37170-E

Usage:

Format1: cjimportwar [servername] [-nameserver providerURL] -f warfilename [-name applicationname] [-contextroot contextroot] [-c cosminexus.xml]

Format2: cjimportwar [servername] [-nameserver providerURL] -a wardirectorypath [-name applicationname] [-contextroot contextroot] [-c cosminexus.xml]

Description

This message describes how to use the cjimportwar command.

Action

Check the arguments and values of the command, and then re-execute the command.

KDJE37171-E

Usage:

Format1: cjdeljbatchjobs [servername] [-nameserver providerURL] -list -name applicationname -day day [-all] -f file_path

Format2: cjdeljbatchjobs [servername] [-nameserver providerURL] -delete -f file_path [-t timeoutseconds]

Description

This message describes how to use the cjdeljbatchjobs command.

Action

Check the arguments and values of the command, and then re-execute the command.

KDJE37200-E

The required option aa....aa has not been specified.

aa....aa: Option name

Description

The required option is not specified.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37201-E

No value is specified. (option = [aa....aa])

aa....aa: Option name

Description

The value corresponding to the option name is not specified.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37202-E

No option is specified.

Description

Other than the server name, no option is specified in the parameters.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37203-E

The same options have been specified repeatedly. (option = [aa....aa])

aa....aa: Option name

Description

The same options have been specified multiple times.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37204-E

The specified option is invalid. (option = [aa....aa])

aa....aa: Option name

Description

An invalid option is specified.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37205-E

Different export types have been specified simultaneously.

Description

Different export type options have been specified simultaneously.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37206-E

The specified value is invalid. (option = [aa....aa], value = [bb....bb])

aa....aa: Option name

bb....bb: Option value

Description

An invalid option value is specified.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37207-E

aa....aa cannot be specified simultaneously with bb....bb.

aa....aa: Option name

bb....bb: Option name

Description

Options that cannot be specified simultaneously have been specified simultaneously.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37208-E

The necessary -type connector for -name has not been specified.

Description

The necessary -type connector for -name is not specified.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37209-E

The specified directory does not exist. [aa....aa]

aa....aa: File path

Description

The specified path does not exist.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37210-E

The specified path is not a directory. [aa....aa]

aa....aa: File path

Description

The specified path is not a directory.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37211-E

Cannot access directory. [aa....aa]

aa....aa: File path

Description

The specified path cannot be accessed.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37212-E

An invalid provider URL is specified. (error details = aa....aa)

aa....aa: Error details

Description

An invalid provider URL is specified.

The command execution will be interrupted.

Action

Revise the value of the provider URL, and then re-execute the command.

KDJE37213-E

The same tag is specified more than once. (name = [aa....aa])

aa....aa: Tag name

Description

The same tag is specified more than once.

The command execution will be interrupted.

Action

Check the tag specification in the property file.

KDJE37300-E

The aa....aa command failed. Contact the system administrator.

aa....aa: Command name

Description

The command has failed because an unexpected exception occurred.

The command execution will be interrupted.

Action

If the exception messages starting with nnnn (n is a number) is followed by this message , see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory. If you do not understand the cause, acquire the maintenance information, and then contact the system administrator.

KDJE37301-E

Another command is already running.

Description

Another command is already running.

The command execution will be interrupted.

Action

Wait for the command to finish, and then re-execute the command.

KDJE37302-E

The server was not found. (name = [aa....aa])

aa....aa: Server name

Description

The server was not found.

The command execution will be interrupted.

Action

Start the J2EE server if it is not already started. Alternatively, revise the command parameters, and then re-execute the command.

KDJE37303-E

The Naming Service was not found.

Description

The Naming Service was not found.

The command execution will be interrupted.

Action

Invoke the Naming Service if it is not already invoked. Alternatively, revise the command parameters, and then re-execute the command.

KDJE37304-E

aa....aa was not found.

aa....aa: Application name, parent resource display name, parent resource display name / subordinate resource display name, Resource adapter name, or JavaBeans resource display name, user name, or role name

Description

aa....aa was not found.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37305-E

aa....aa already exists. (name = [bb....bb])

aa....aa: Type (Application, Lookup name, EJB-JAR, Ejb-name, WAR, Datasource, Mail, User, Role, RAR, Library JAR, Filter, Filter-name, or JavaBeans resource)

bb....bb: Application name, Lookup name, EJB-JAR display name, Ejb-name, WAR display name, Datasource display name, Mail display name, User name, Role name, RAR display name, Library JAR name, Filter display name, Filter-name, or JavaBeans resource display name

Description

bb....bb already exists.

The command execution will be interrupted.

Action

Check the command parameters or check that the cjlist-series command corresponds to aa....aa, and then re-execute the command.

KDJE37307-E

aa....aa is running. (name = [bb....bb])

aa....aa: Type (Application)

bb....bb: Application name

Description

Application (bb....bb) is running.

The command execution will be interrupted.

Action

Terminate the application, and then re-execute the command.

KDJE37309-E

aa....aa is being used in one or more applications. (name = [bb....bb])

aa....aa: Type (Datasource or Mail)

bb....bb: Datasource display name or mail display name

Description

bb....bb is being used in one or more applications.

The command execution will be interrupted.

Action

Delete the applications in which bb....bb is in use, and then re-execute the command.

KDJE37310-E

aa....aa is being used by one or more running applications. (name = [bb....bb])

aa....aa: Type (Datasource or Mail)

bb....bb: Datasource display name or mail display name

Description

One or more running applications are using bb....bb.

The command execution will be interrupted.

Action

Terminate the applications in which bb....bb is in use, and then re-execute the command.

KDJE37311-E

The file type is set to directory. (path = [aa....aa])

aa....aa: File path

Description

The directory was specified.

The command execution will be interrupted.

Action

Specify the correct file path, and then re-execute the command.

KDJE37312-E

The file does not exist. (path = [aa....aa])

aa....aa: File path

Description

The file does not exist.

The command execution will be interrupted.

Action

Specify the correct file path, and then re-execute the command.

KDJE37313-E

aa....aa has already been mapped. (name = [bb....bb])

aa....aa: Type (User)

bb....bb: User name

Description

The user (bb....bb) has already been mapped.

The command execution will be interrupted.

Action

Un-map, and then re-execute the command.

KDJE37314-E

aa....aa has not been mapped yet. (name = [bb....bb])

aa....aa: Type (User)

bb....bb: User name

Description

The user (bb....bb) is not mapped yet.

The command execution will be interrupted.

Action

Map, and then re-execute the command.

KDJE37316-E

Deployment Descriptor was not found. (path = [aa....aa])

aa....aa: File path

Description

The DD was not found.

The command execution will be interrupted.

Action

Revise the file contents, and then re-execute the command.

KDJE37317-E

An attempt to read the aa....aa file has failed. (path = [bb....bb], detail = [cc....cc])

aa....aa: Type (Application All property, Application property, EJB-JAR property, Session Bean property, Entity Bean property, WAR property, Servlet property, Datasource property, Mail property, Datasource configuration, RAR property, Filter property or JavaBeans resource property)

bb....bb: File path

cc....cc: Exception information from the XML user

Description

An attempt to read the file (aa....aa) has failed. The command execution will be interrupted.

Action

Revise the file contents, and then re-execute the command.

KDJE37318-E

No DataSource or Driver interface is specified.

Description

No DataSource or Driver interface is specified.

The command execution will be interrupted.

Action

Revise the contents of the DataSource setup file, and then re-execute the command.

KDJE37319-E

No DataSource or Driver interface was found. (name = [aa....aa])

aa....aa: Interface class name

Description

No DataSource or Driver interface was found.

The command execution will be interrupted.

Action

Specify the correct file path of the JDBC driver, and then re-execute the command.

KDJE37321-E

No property value is specified. (name = [aa....aa])

aa....aa: Tag name

Description

Either aa....aa is not specified or the value of aa....aa is a null character.

The command execution will be interrupted.

Action

Confirm that the mandatory tags have been specified or the specification of aa....aa is correct, and then re-execute the command.

KDJE37322-E

The property value is invalid. (name = [aa....aa], value = [bb....bb])

aa....aa: Tag name

bb....bb: Tag value

Description

The value of aa....aa is invalid.

The command execution will be interrupted.

Action

Check the value of aa....aa, and then re-execute the command.

KDJE37323-E

The resource does not exist.

Description

The resource registered in the pool does not exist.

The command execution will be interrupted.

Action

Check the value of the option -resname, and then re-execute the command.

KDJE37324-E

aa....aa produced an error. The command has failed.

aa....aa: Type (J2EE server, I/O, Naming Service, and OTS)

Description

An error occurred in aa....aa.

The command execution will be interrupted.

Action

See the message displayed before this message, check the operation environment (J2EE server, Naming Service, and OTS) during the execution of the command, and then eliminate the cause of the error. Note that if the exception messages starting with nnnn (n is a number) are followed by this message, see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory.

Example causes and actions are as follows:

If this message is displayed in a node switching system

The IP address or host name specified in the webserver.connector.http.permitted.hosts key of the user property file for the connection destination J2EE server (usrconf.properties) is incorrect. Revise the IP address or host name.

If this error occurs due to the settings for the data source attribute

The settings for the data source attribute are invalid. Check whether the settings are invalid and, if necessary, revise the settings.

KDJE37325-E

No aa....aa tag is specified.

aa....aa: Tag name

Description

No aa....aa tag is specified.

The command execution will be interrupted.

Action

Set the value of the tag shown in the error message.

KDJE37326-E

aa....aa command failed.

bb....bb.

aa....aa: Type (Import, Replace or Reload)

bb....bb: Details

Description

An attempt to import, replace, or reload the application has failed. The command execution will be interrupted.

Action

Take action as per the error message.

KDJE37328-E

File format is invalid.

Description

The command execution will be interrupted because the file format is invalid.

Action

Revise the file format.

KDJE37329-E

aa....aa's connection was not found or is not being used.

aa....aa: Connection ID

Description

The connection (aa....aa) was not found or is not being used.

The command execution will be interrupted.

Action

Make sure that the specified connection ID is correct.

KDJE37330-E

The command could not be started in the current J2EE status. This command runs in basic mode.

Description

The J2EE server is not in the basic mode.

The command execution will be interrupted.

Action

Make sure that the startup mode of the J2EE server is set to Basic.

KDJE37331-E

aa....aa is already deployed. (name = [bb....bb])

aa....aa: Type (RAR)

bb....bb: RAR display name

Description

bb....bb is already deployed.

The command execution will be interrupted.

Action

Un-deploy, and then re-execute the command.

KDJE37332-E

The same display name as for aa....aa exists in the J2EE Application. (name = [bb....bb], J2EE Application name = [cc....cc])

aa....aa: Type (RAR)

bb....bb: RAR display name

cc....cc: J2EE application name

Description

A RAR with the same display name as bb....bb exists in the J2EE application (cc....cc).

The command execution will be interrupted.

Action

Change the display name so that it is not same, and then re-execute the command.

KDJE37334-E

aa....aa cannot be undeployed. Retry after rebooting the J2EE Server. (name = [bb....bb])

aa....aa: Type (RAR)

bb....bb: RAR display name

Description

bb....bb cannot be un-deployed.

The command execution will be interrupted.

Action

Restart the J2EE server, and then re-execute the command.

KDJE37335-E

aa....aa is running. (name=[bb....bb])

aa....aa: Type (RAR or JavaBeans resource)

bb....bb: RAR display name or JavaBeans resource display name

Description

bb....bb is running.

The command execution will be interrupted.

Action

Stop bb....bb, and then re-execute the command.

KDJE37336-E

aa....aa is not running. (name=[bb....bb])

aa....aa: Type (RAR or JavaBeans resource)

bb....bb: RAR display name or JavaBeans resource display name

Description

bb....bb is not running.

The command execution will be interrupted.

Action

Start bb....bb, and then re-execute the command.

KDJE37337-E

Deploying failed. (name = [aa....aa])

aa....aa: RAR display name

Description

Deploying failed.

The command execution will be interrupted.

Action

Contact the system administrator.

KDJE37341-E

DatabaseID = [aa....aa] was not found.

aa....aa: Database ID

Description

The pool management information of the database (aa....aa) does not exist.

The command execution will be interrupted.

Action

Check the pool management information with the cjweblistpool command, and then re-execute the command.

KDJE37342-E

DatabaseID already exists. (DatabaseID = [aa....aa])

aa....aa: Database ID

Description

The pool management information of the database (aa....aa) already exists.

The command execution will be interrupted.

Action

Check the pool management information with the cjweblistpool command, and then re-execute the command.

KDJE37343-E

The list does not exist. (listtype = [aa....aa], DatabaseID = [bb....bb])

aa....aa: List type

bb....bb: Database ID

Description

The database (bb....bb) is not in use.

The command execution will be interrupted.

Action

Display the database list with the -listtype dblist option, check the value of bb....bb, and then re-execute the command.

KDJE37344-E

The list does not exist. (listtype = [aa....aa], DatabaseID = [bb....bb], UserID = [cc....cc])

aa....aa: List type

bb....bb: Database ID

cc....cc: User ID

Description

The database ID (bb....bb) or the user ID (cc....cc) is not being used. The command execution will be interrupted.

Action

Display the database list and the pool list with the -listtype dblist and -listtype poollist options, check the value, and then re-execute the command.

KDJE37345-E

No DatabaseID, ClassName, or URL is specified.

Description

The database ID, class name, or URL is not specified.

The command execution will be interrupted.

Action

Check the contents of the pool management information setup file, and then re-execute the command.

KDJE37346-E

There is no scheduled bean.

Description

The Bean invoked through CTM is not the one specified.

The command execution will be interrupted.

Action

Make sure that the setting of the Bean is correct.

KDJE37347-E

The Parallel count of the Scheduling tag cannot be greater than the pooled instances maximum.

Description

In the Bean invoked through CTM, the value specified in Maximum is lesser than that specified in Parallel count.

The command execution will be interrupted.

Action

Make sure that the values of Maximum and Parallel count are correct.

KDJE37348-E

The aa....aa command failed. (detail = [bb....bb])

aa....aa: Command name (cjwebeditpool, cjwebchangedbid, cjwebdeletepool, cjweblistpool, cjwebclearpool, or cjwebclosepool)

bb....bb: Exception information from the connection pool API

Description

The command (aa....aa) has failed.

The command execution will be interrupted.

Action

Contact the system administrator.

KDJE37349-E

The aa....aa command failed due to a [bb....bb] error.

aa....aa: Command name (cjwebeditpool, cjwebchangedbid, cjwebdeletepool, cjweblistpool, cjwebclearpool, or cjwebclosepool)

bb....bb: Type (Connection, I/O, Permission, or Version)

Description

The command (aa....aa) has failed due to the occurrence of an error (bb....bb).

The command execution will be interrupted.

Action

When bb....bb is either Connection or I/O

Revise the host name and the port number, confirm that the Web container server is running, and then re-execute the command.

When bb....bb is Permission

Check the settings of the connection destination Web container server (webserver.connector.http.permitted.hosts), and then re-execute the command.

When bb....bb is Version

Match the version of the Cosminexus Component Container of the host executing the server and the command.

KDJE37350-E

aa....aa cannot be used with this Edition.

aa....aa: Tag name

Description

The tag (aa....aa) cannot be used with this edition of the Application Server.

The command execution will be interrupted.

Action

Check the edition settings of the Application Server.

KDJE37351-E

The property value is invalid.

Name = [thread-control-max-threads], Value = [aa....aa]

Name = [thread-control-exclusive-threads], Value = [bb....bb]

thread-control-max-threads must specify a value beyond that of thread-control-exclusive-threads.

aa....aa: Maximum number of concurrently executing threads of each Web application

bb....bb: Number of dedicated threads

Description

The value specified in the maximum number of concurrently executing threads (aa....aa) of each Web application is lesser than the number of dedicated threads (bb....bb).

The command execution will be interrupted.

Action

Make sure that the specified maximum number of concurrently executing threads of each Web application, or the number of dedicated threads is correct.

KDJE37352-E

aa....aa cannot be used with this configuration.

webserver.container.thread_control.enabled = false

aa....aa: Tag name

Description

The tag (aa....aa) cannot be used with this setting.

The command execution will be interrupted.

Action

Check the setting of webserver.container.thread_control.enabled.

KDJE37353-E

An access from aa....aa is not permitted. Host name = bb....bb

aa....aa: IP address

bb....bb: Host name

Description

Access from aa....aa is not permitted. Host name = bb....bb

Action

The command execution will be interrupted. Check the settings of the connection destination Web container server (webserver.connector.http.permitted.hosts), and then re-execute the command.

KDJE37354-E

The version of Cosminexus Component Container is incompatible.

Host name = aa....aa, Reason code = (bb....bb, cc....cc).

aa....aa: Host name

bb....bb: Maintenance information 1

cc....cc: Maintenance information 2

Description

The version of Cosminexus Component Container is incompatible. Host name = aa....aa, Maintenance information = (bb....bb, cc....cc)

Action

The command execution will be interrupted. Match the version of the Cosminexus Component Container of the host executing the server and the command.

If the responsible factors cannot be resolved, acquire the maintenance information, and then contact maintenance personnel.

KDJE37356-E

The communication timeout occurred.

Description

A timeout occurred during the execution of the server management command.

The command execution will be interrupted.

Action

Make sure that no problem exists in the network environment. If no problem exists in the network environment, take the following actions:

In the case of a command in which the time for timeout can be specified in the argument, increase the value of the timeout specified in the argument, and then re-execute the command.

In the case of a command in which the time for timeout cannot be specified in the argument, revise the value of the key ejbserver.rmi.request.timeout of the user property file, and then re-execute the command.

KDJE37357-E

The same aa....aa have been specified repeatedly. (name = [bb....bb])

aa....aa: Type (library jar names)

bb....bb: Library JAR file name

Description

The same options have been specified multiple times.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37358-E

The specified aa....aa does not exist. Path=[bb....bb]

aa....aa: Type (directory)

bb....bb: Path

Description

The specified path does not exist.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37359-E

File type is not directory. Path=[aa....aa]

aa....aa: Path

Description

The specified path is not a directory.

The command execution will be interrupted.

Action

Specify the correct directory path, and then re-execute the command.

KDJE37360-E

The connected test of aa....aa failed.

aa....aa: Datasource display name, mail display name, or resource adapter display name

Description

The connection test has failed.

The command execution will be interrupted.

Action

Revise the connection information, and then re-execute the command.

KDJE37361-E

The file including runtime information has been specified. Path=[aa....aa]

aa....aa: Path

Description

The file containing the runtime information is specified.

The command execution will be interrupted.

Action

Specify a file (extension .ear) that does not include the runtime information.

KDJE37362-E

The application name specified to be -name option differs from the value of the display-name tag of the application.xml in an EAR file. Value=[aa....aa]

aa....aa: Application name generated from the specified value of the <display-name> tag or from the EAR file name

Description

The application name specified in -name option is different from the application name specified in the <display-name> tag of application.xml in the EAR file.

In the case of an EAR file that does not include application.xml, the application name specified in the -name option and the application name generated from the EAR file name are different.

Action

The command execution will be interrupted.

Revise the value of the <display-name> tag of application.xml, and then re-execute the command.

In the case of an EAR file that does not include application.xml, because the application name is generated from the EAR file name, revise the EAR file name, and then re-execute the command.

KDJE37363-E

The specified path is invalid. Path=[aa....aa]

aa....aa: Path

Description

An invalid path is specified.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE37364-E

A command cannot be executed in the state of this application. (name = [aa....aa], status = [bb....bb])

aa....aa: Application name

bb....bb: Application status

Description

A command cannot be executed in this state of the application.

The command execution will be interrupted.

Action

Revise the state of the application, and then re-execute the command.

KDJE37365-E

The following error occurred, but an application has been imported successfully.

Description

The import was successful, but an error occurred. For details on the error, see the messages output in continuation to this message.

Action

Revise the set information of the application based on the information of the messages output in continuation to this message.

KDJE37366-E

The following error occurred, but a resource adapter has been deployed successfully.

Description

The deployment was successful, but an error occurred. For details on the error, see the messages output in continuation to this message.

Action

Revise the set information of the resource adapter based on the information of the messages output in continuation to this message.

KDJE37367-W

A property value is invalid. ([aa....aa] = [bb....bb]) The default value [cc....cc] will be used.

aa....aa: Property name

bb....bb: Set property value

cc....cc: Default value

Description

The property value (bb....bb) is invalid. The processing continues with the default value (cc....cc).

Action

Check if the property value set in the user property file is correct.

KDJE37368-E

This command cannot execute in the current J2EE server mode.

Description

This command cannot be executed in the current J2EE server mode.

The command execution will be interrupted.

Action

Check the startup mode of the J2EE server.

KDJE37369-E

aa....aa is not a member resource adapter of the cluster connection pool.

aa....aa: Resource adapter display name

Description

aa....aa is not a member resource adapter of the cluster connection pool.

The command execution will be interrupted.

Action

Confirm that aa....aa is a member resource adapter of the cluster connection pool, and then re-execute the command.

KDJE37370-E

The connection pool is not running. (name = [aa....aa], connection pool status = [bb....bb])

aa....aa: Resource adapter display name

bb....bb: Connection pool status

Description

The connection pool of aa....aa is not started or reserved for starting. The connection pool is in bb....bb state.

The command execution will be interrupted.

Action

Restart aa....aa with the cjresumepool command, and then re-execute the command.

KDJE37371-E

The connection pool is not suspended. (name = [aa....aa], connection pool status = [bb....bb])

aa....aa: Resource adapter display name

bb....bb: Connection pool status

Description

aa....aa is not automatically suspended, manually suspended, reserved for automatic suspension, or reserved for manual suspension. The connection pool is in bb....bb state.

The command execution will be interrupted.

Action

When the connection pool has started or is reserved for starting:

You need not take any action because the connection pool has already started.

When the connection pool is blocked automatically or manually:

Wait until the connection pool will be suspended either automatically or manually, and then re-execute the command.

When the connection pool is resuming automatically, or is being resumed manually:

The connection pool is now resuming. Please wait.

KDJE37372-E

The root resource adapter is not supported. (name = [aa....aa])

aa....aa: Resource adapter display name

Description

aa....aa is a root resource adapter. Commands cannot be executed for the root resource adapter.

The command execution will be interrupted.

Action

In -resname, specify a resource adapter display name other than the root resource adapter, and then re-execute the command.

KDJE37373-E

SQL cannot be generated because the CMP2.x entity bean field is not mapped to a table in the database. (name = [aa....aa])

aa....aa: Ejb-name

Description

The SQL cannot be generated because the CMP2.x Entity Bean field is not mapped to a table in the database.

Action

Map the CMP2.x Entity Bean field to a table in the database, and then re-execute the command.

KDJE37375-E

A command cannot be executed in an application with the deployment directory format. (name = [aa....aa])

aa....aa: Application name

Description

Commands cannot be executed in an expanded archive format application.

Action

Specify an archive format application, and then re-execute the command.

KDJE37376-E

A command cannot be executed in an application with the archive format. (name = [aa....aa])

aa....aa: Application name

Description

Commands cannot be executed in an archive format application.

Action

Specify an expanded archive format application, and then re-execute the command.

KDJE37377-E

aa....aa is not a CMP2.X Entity Bean.

aa....aa: Ejb-name

Description

aa....aa is not a CMP2.X Entity Bean.

Action

Specify the name of a CMP2.x Entity Bean in -resname, and then re-execute the command.

KDJE37378-E

The same attribute value tag has been specified more than once. (name = [aa....aa], attribute = [bb....bb], value = [cc....cc])

aa....aa: Tag name

bb....bb: Attribute name

cc....cc: Attribute value

Description

The same attribute value tag is specified more than once.

Action

Check the value of xml:lang attribute, and then re-execute the command.

KDJE37379-E

A tag having "en" as the value of the "xml:lang" attribute is not specified. (name = [aa....aa])

aa....aa: Tag name

Description

A tag having "en" as the value of the xml:lang attribute is not specified.

Action

Specify a tag having "en" as the value of the xml:lang attribute, and then re-execute the command.

KDJE37380-E

A Java Beans resource with the same implementation class name exists. (name = [aa....aa], class name = [bb....bb])

aa....aa: Display name of JavaBeans resource

bb....bb: Implementation class name

Description

A Java Beans resource with the same implementation class name already exists.

The command execution will be interrupted.

Action

Change the implementation class name so that there is no duplication, and then re-execute the command.

KDJE37381-W

The resource adaptor has been deleted or there is a problem with the work directory.

Description

The resource adaptor is deleted or there is a problem with the work directory. Check the message in the J2EE server.

Action

Check the message in the J2EE server.

KDJE37382-E

The tag which cannot be specified to [aa....aa] was specified.(name = [bb....bb])

aa....aa: EJB1.1, EJB2.0, EJB2.1, Servlet2.2, Servlet2.3, Servlet2.4, Connector1.0, Connector1.5

bb....bb: Tag name

Description

A tag that cannot be specified was specified.

Action

Check the specifications of the property file in the manual, and if necessary, revise the specification of the tags in the property file.

KDJE37383-E

Two or more tags were specified to [aa....aa]. (name = [bb....bb])

aa....aa: EJB1.1, EJB2.0, Servlet2.2, Servlet2.3, Servlet2.4, Connector1.0

bb....bb: Tag name

Description

Tags that can only be specified once were specified more than once.

Action

Check the specifications of the property file in the manual, and if necessary, revise the specification of the tags in the property file.

KDJE37384-E

A member resource adapter cannot be set in this tag. (tag = [aa....aa], tag value = [bb....bb])

aa....aa: Tag name

bb....bb: Tag value

Description

The display name of the member resource adapter cannot be specified at the following locations:

Resource reference of the J2EE applications

Mapping definition of the CMP Entity Bean

Action

Specify the display name of the root resource adapter in the invalid tag.

KDJE37385-E

aa....aa cannot be deleted. Reboot the J2EE server, and then retry. (name = [bb....bb])

aa....aa: Type (JavaBeans resource)

bb....bb: Display name of JavaBeans resource

Description

bb....bb cannot be deleted.

The command execution will be interrupted.

Action

Restart the J2EE server, and then re-execute the command.

KDJE37386-E

A command cannot be executed from a remote host in an application with the deployment directory format. (name = [aa....aa]).

aa....aa: Application name

WAR directory name if the -name option is omitted in the cjimportwar command

Description

Commands cannot be executed from a remote host, in the expanded archive format.

Action

Execute the commands from the local host.

KDJE37387-E

An empty directory have been specified. (path = [aa....aa])

aa....aa: Path

Description

An empty directory is specified. The command execution will be interrupted.

Action

Revise the command parameters and the contents of the directory, and then re-execute the command.

KDJE37388-E

The total of the property value is invalid. (name = [aa....aa], total = [bb....bb])

aa....aa: Tag name

bb....bb: Total of the tag values

Description

The total of the tag values is invalid. The command execution will be interrupted.

Action

Check the value of the tag names, and then re-execute the command.

KDJE37389-E

The type of the property file is illegal.

Description

The type of the property file is invalid.

Action

Confirm the following contents, and then re-execute the command:

Type of the executed command

Specification of the -type argument

Specification of the -c argument

KDJE37391-E

The connection pool status is illegal. An available status is "running", "runningReserved", "suspendedAutomatically" or "suspendedAutomaticallyReserved". (name = [aa....aa], connection pool status = [bb....bb])

aa....aa: Resource adapter display name

bb....bb: Connection pool status

Description

The connection pool status of aa....aa is invalid. The enabled states are "running", "reserved for running", "automatically suspended", or "reserved for automatic suspension". The command execution will be interrupted.

Action

Execute the following actions:

When the connection pool is blocked automatically or manually:

The suspension processing of the connection pool is in progress. Wait.

When the connection pool is "manually suspended" or "reserved for manual suspension":

The connection pool is already suspended. No action required.

When the connection pool is resuming automatically, or is being resumed manually:

Wait until the connection pool is started, and then re-execute the command.

KDJE37392-E

The length of display name of aa....aa is too long.

aa....aa: an application, a RAR, a data source, a mail, or JavaBeans resource

Description

The display name of the application or resource displayed in aa....aa is too long.

Action

Check the length of the display name, and then re-execute the command.

KDJE37393-E

The J2EE application "aa....aa" cannot be created.

aa....aa: Application name

Description

The application could not be created (name = aa....aa).

The command execution will be interrupted.

Action

The specified application cannot be used.

Check the application name, and then re-execute the command.

KDJE37394-E

The command cannot be executed because you do not have administrator privileges.

Description

The command cannot be executed because you do not have administrator privileges.

Action

Re-execute the command on a command prompt, as an administrator.

KDJE37395-E

An error occurred while the permissions were being checked.

Description

An error occurred while the permissions were being checked.

Action

The memory might be insufficient. Increase the free memory, and then re-execute the command. If the problem is not resolved, contact maintenance personnel.

KDJE37396-E

A command cannot be executed in the resource adapter of Connector1.0

Description

A command cannot be executed in the resource adapter of Connector1.0.

Action

Specify the resource adapter of Connector1.5, and then re-execute the command.

KDJE37397-W

An attempt to initialize the audit log has failed. (details = [aa....aa])

aa....aa: Detailed information

Description

An attempt to initialize the audit log failed. The audit log cannot be output, but the processing continues.

Action

Remove the cause of the failure by referencing the message log for the audit log.

KDJE37398-W

An attempt to output the audit log has failed. (details = [aa....aa])

aa....aa: Detailed information

Description

An attempt to output the audit log failed. The processing continues.

Action

Remove the cause of the failure by referencing the message log for the audit log. If the problem is not resolved, contact maintenance personnel.

KDJE37399-E

The tag [aa....aa] and the tag [bb....bb] cannot be specified simultaneously.

aa....aa: Tag name

bb....bb: Tag name

Description

Tags that cannot be specified simultaneously have been specified simultaneously.

The command execution will be interrupted.

Action

Check the specifications of the property file in the manual, and if necessary, revise the specification of the tags in the property file.

KDJE37400-I

Connecting to aa....aa...

aa....aa: Server name

Description

Connecting to the server.

KDJE37401-I

Searching aa....aa...

aa....aa: Application name, EJB-JAR display name, WAR display name, RAR display name, data source display name, mail display name, user name, role name, or JavaBeans resource display name

Description

aa....aa is being searched.

KDJE37402-I

Creating aa....aa...

aa....aa: Application name

Description

aa....aa is being created.

KDJE37404-I

Importing aa....aa...

aa....aa: WAR application name, EJB-JAR display name, WAR display name, RAR display name, data source display name, or JavaBeans resource display name

WAR file name or WAR directory name if the -name option is omitted in the cjimportwar command

Description

aa....aa is being created.

KDJE37405-I

Exporting [aa....aa] ...

aa....aa: Application name

Description

The J2EE application (aa....aa) is being exported.

KDJE37406-I

Adding aa....aa...

aa....aa: EJB-JAR display name, WAR display name, RAR display name, user name, role name, or Filter display name

Description

aa....aa is being added.

KDJE37407-I

Deleting aa....aa...

aa....aa: Application name, EJB-JAR display name, WAR display name, RAR display name, data source display name, mail display name, user name, role name, or JavaBeans resource display name

Description

aa....aa is being deleted.

KDJE37408-I

Acquiring aa....aa...

aa....aa: Application name, EJB-JAR display name, WAR display name, RAR display name, data source display name, mail display name, or JavaBeans resource display name

Description

The properties of aa....aa is being acquired.

KDJE37409-I

Setting aa....aa...

aa....aa: Application name, EJB-JAR display name, WAR display name, RAR display name, data source display name, mail display name, or JavaBeans resource display name

Description

The properties of aa....aa are being set.

KDJE37410-I

Copying aa....aa...

aa....aa: EJB-JAR display name, WAR display name, RAR display name, data source display name, or mail display name

Description

aa....aa is being copied.

KDJE37411-I

Testing aa....aa of bb....bb...

aa....aa: DataSource, Mail, or RAR

bb....bb: Datasource display name, mail display name, or resource adapter display name

Description

aa....aa is being tested.

KDJE37413-I

Starting aa....aa...

aa....aa: Application name

Description

aa....aa is running.

KDJE37414-I

Stopping aa....aa...

aa....aa: Application name

Description

aa....aa is being stopped.

KDJE37415-I

Mapping aa....aa...

aa....aa: User name

Description

aa....aa is being mapped.

KDJE37416-I

Unmapping aa....aa...

aa....aa: User name

Description

aa....aa is being un-mapped.

KDJE37417-I

Resetting exclusive information...

Description

The exclusive information of the command is being reset.

KDJE37418-I

Clearing out aa....aa...

aa....aa: Parent resource display name or all resources

Description

aa....aa or all resources are being deleted.

KDJE37419-I

Closing all aa....aa connections...

aa....aa: Parent resource display name, or resources

Description

All aa....aa connections are being closed.

KDJE37420-I

Closing the aa....aa connection...

aa....aa: Connection ID

Description

The connection (aa....aa) is being closed.

KDJE37421-I

Deploying aa....aa...

aa....aa: RAR display name

Description

aa....aa is being deployed.

KDJE37422-I

Undeploying aa....aa...

aa....aa: RAR display name

Description

aa....aa is being un-deployed.

KDJE37423-I

Starting aa....aa...

aa....aa: RAR display name or JavaBeans resource display name

Description

aa....aa is being started.

KDJE37424-I

Stopping aa....aa...

aa....aa: RAR display name or JavaBeans resource display name

Description

aa....aa is being stopped.

KDJE37425-I

Connecting to aa....aa...

aa....aa: Host name

Description

Connecting to the host (aa....aa) of the servlet to be executed.

KDJE37426-I

Replacing aa....aa...

aa....aa: Application name

Description

aa....aa is being replaced.

KDJE37427-I

Updating aa....aa...

aa....aa: Application name

Description

aa....aa is being updated.

KDJE37428-I

Changing aa....aa...

aa....aa: Application name

Description

aa....aa is being changed.

KDJE37429-I

Suspending aa....aa...

aa....aa: Resource adapter display name

Description

aa....aa is being stopped.

KDJE37430-I

Resuming aa....aa...

aa....aa: Resource adapter display name

Description

aa....aa is being resumed.

KDJE37431-I

Generating SQL of aa....aa...

aa....aa: EJB-JAR display name / EJB display name

Description

An SQL statement of aa....aa.is being generated.

KDJE37501-I

aa....aa has been imported successfully. (name = [bb....bb])

aa....aa: Type (WAR application, EJB-JAR, WAR, Datasource, RAR, or JavaBeans resource)

bb....bb: WAR application name, EJB-JAR display name, WAR display name, Datasource display name, RAR display name, or JavaBeans resource display name

Description

bb....bb is imported successfully.

KDJE37502-I

aa....aa has been exported successfully. Name=[bb....bb]

aa....aa: Type (Application or RAR)

bb....bb: Application display name or RAR display name

Description

bb....bb is exported successfully.

KDJE37503-I

aa....aa has been added successfully. (name = [bb....bb])

aa....aa: Type (Application, EJB-JAR, WAR, User, Role, RAR, Filter, or JavaBeans resource)

bb....bb: Application name, parent resource display name, or JavaBeans resource display name

Description

bb....bb is added successfully.

KDJE37504-I

aa....aa has been deleted successfully. (name = [bb....bb])

aa....aa: Type (Application, EJB-JAR, WAR, Datasource, Mail, User, Role, or RAR)

bb....bb: Application name or parent resource display name

Description

bb....bb is deleted successfully.

KDJE37505-I

aa....aa has been obtained successfully. (name = [bb....bb])

aa....aa: Type (Application, EJB-JAR, WAR, Datasource, Mail, RAR, or JavaBeans resource)

bb....bb: Application name, parent resource display name, parent resource display name / subordinate resource display name, or JavaBeans resource display name

Description

The properties of bb....bb have been acquired successfully.

KDJE37506-I

aa....aa has been set successfully. (name = [bb....bb])

aa....aa: Type (Application, EJB-JAR, WAR, Datasource, Mail, RAR, or JavaBeans resource)

bb....bb: Application name, parent resource display name, parent resource display name / subordinate resource display name, or JavaBeans resource display name

Description

The properties of bb....bb have been set successfully.

KDJE37507-I

aa....aa has been copied successfully. (name = [bb....bb])

aa....aa: Type (EJB-JAR, WAR, Datasource, Mail, or RAR)

bb....bb: Parent resource display name, or parent resource display name / subordinate resource display name

Description

bb....bb is copied successfully.

KDJE37508-I

All aa....aa have been listed successfully. (number = [bb....bb])

aa....aa: Applications, EJB-JARs, WARs, Datasources, Mails, Users, Roles, RARs, ejbs, javabeans resource, library jars, lower resources, or threads

bb....bb: Number

Description

All aa....aa have been listed successfully.

KDJE37509-I

aa....aa has been listed successfully. (name = [bb....bb])

aa....aa: Type (Connection, User, or Role)

bb....bb: Datasource display name, all resources, user name, or role name

Description

bb....bb is listed successfully.

KDJE37510-I

aa....aa of bb....bb has been tested successfully. Name=[bb....bb]

aa....aa: DataSource, Mail, or RAR

bb....bb: Datasource display name, mail display name, or resource adapter display name

Description

aa....aa of bb....bb is tested successfully.

KDJE37512-I

aa....aa has started successfully. (name = [bb....bb])

aa....aa: Type (Application)

bb....bb: Application name

Description

The application (bb....bb) has started successfully.

KDJE37513-I

aa....aa has stopped successfully. (name = [bb....bb])

aa....aa: Type (Application)

bb....bb: Application name

Description

The application (bb....bb) has stopped successfully.

KDJE37514-I

aa....aa has been mapped successfully. (name = [bb....bb])

aa....aa: Type (User)

bb....bb: User name

Description

The user (bb....bb) is mapped successfully.

KDJE37515-I

aa....aa has been unmapped successfully. (name = [bb....bb])

aa....aa: Type (User)

bb....bb: User name

Description

The user (bb....bb) is un-mapped successfully.

KDJE37516-I

The exclusive information for command execution has been reset successfully.

Description

The exclusive information of the command was reset successfully.

KDJE37517-I

aa....aa has been cleared successfully. (name = [bb....bb])

aa....aa: Type (JDBC or JCA)

bb....bb: Data source display name or resource adapter display name

Description

The data source or the resource adapter is deleted successfully.

KDJE37518-I

All resources have been cleared successfully.

Description

All resources have been deleted successfully.

KDJE37519-I

aa....aa

Connections have been closed successfully. (name = [bb....bb])

aa....aa: Detailed information from the server

bb....bb: Data source display name, or all resources

Description

The connections have been closed successfully.

KDJE37520-I

The connection has been closed successfully. (CID = [aa....aa])

aa....aa: Connection ID

Description

The connections have been closed successfully.

KDJE37521-I

aa....aa has been deployed successfully. (name = [bb....bb])

aa....aa: Type (RAR)

bb....bb: RAR display name

Description

bb....bb is deployed successfully.

KDJE37522-I

aa....aa has been undeployed successfully. (name = [bb....bb])

aa....aa: Type (RAR)

bb....bb: RAR display name

Description

bb....bb is un-deployed successfully.

KDJE37523-I

aa....aa has started successfully. (name = [bb....bb])

aa....aa: Type (RAR or JavaBeans resource)

bb....bb: RAR display name or JavaBeans resource display name

Description

bb....bb has started successfully.

KDJE37524-I

aa....aa has stopped successfully. (name = [bb....bb])

aa....aa: Type (RAR or JavaBeans resource)

bb....bb: RAR display name or JavaBeans resource display name

Description

bb....bb has stopped successfully.

KDJE37525-I

Pool management information has been set successfully. (DatabaseID = [aa....aa])

aa....aa: Database ID

Description

The pool management information is registered or changed successfully.

KDJE37526-I

DatabaseID has been changed successfully. (DatabaseID = [aa....aa])

aa....aa: Database ID

Description

The database ID is changed successfully.

KDJE37527-I

Pool management information has been deleted successfully. (DatabaseID = [aa....aa])

aa....aa: Database ID

Description

The database ID is deleted successfully.

KDJE37528-I

Pool information has been listed successfully. (listtype = [aa....aa], number = [bb....bb])

aa....aa: List operation type

bb....bb: Number of database lists, number of pool lists, or number of connection lists

Description

The list information is output successfully.

KDJE37529-I

Connection information has been cleared successfully. (mode = [aa....aa], DatabaseID = [bb....bb])

aa....aa: Clear operation type (normal or plan)

bb....bb: Database ID

Description

The connections related to bb....bb have been deleted successfully.

KDJE37530-I

Connection information has been cleared successfully. (mode = [aa....aa])

aa....aa: Clear operation type (normal or plan)

Description

The connection is deleted successfully.

KDJE37531-I

The connection has been closed successfully. (DatabaseID = [aa....aa], CID = [bb....bb])

aa....aa: Database ID

bb....bb: Connection ID

Description

The connections have been closed successfully.

KDJE37532-I

The connection has been closed successfully. (DatabaseID = [aa....aa], TIME = [bb....bb])

aa....aa: Database ID

bb....bb: Timeout period

Description

The connections have been closed successfully.

KDJE37533-I

If you changed class name or URL, you must restart the web container to finish setting it up.

Description

If you have changed the class name or the URL, restart the Web container.

KDJE37534-I

To finish setting up your changes, you must restart the web container.

Description

To apply the settings, restart the Web container.

KDJE37535-I

aa....aa has been replaced successfully. (name = [ bb....bb])

aa....aa: Type (Application)

bb....bb: Application name

Description

aa....aa is replaced successfully.

KDJE37536-I

aa....aa has been updated successfully. (name = [ bb....bb])

aa....aa: Type (Application)

bb....bb: Application name

Description

aa....aa is updated successfully.

KDJE37537-I

aa....aa has been changed successfully. (name = [ bb....bb])

aa....aa: Type (Application)

bb....bb: Application name

Description

aa....aa is changed successfully.

KDJE37538-I

The thread has been stopped successfully.

Description

The thread is stopped successfully.

KDJE37539-I

All transaction have been listed successfully.

Description

All transactions have been listed successfully.

KDJE37540-I

Connections have been listed successfully. name=[aa....aa]

aa....aa: Resource adapter display name

Description

The resource adapter connections have been listed successfully.

KDJE37541-I

All of connections have been listed successfully.

Description

The list of all connections have been listed successfully.

KDJE37542-I

Reloading aa....aa...

aa....aa: Application name

Description

aa....aa is being replaced.

KDJE37543-I

aa....aa has been reloaded successfully. (name=[aa....aa])

aa....aa: Type (Application)

Description

aa....aa is replaced successfully.

KDJE37544-I

The connection pool status was changed successfully. The connection pool which was blocked will now be suspended. (name = [aa....aa])

aa....aa: Resource adapter display name

Description

The status of aa....aa changed normally. The connection pool that was shut down will now be suspended. Use the cjlistrar command to confirm that the connection pool is suspended.

KDJE37545-I

Connection pool has been resumed successfully. (name = [aa....aa])

aa....aa: Resource adapter display name

Description

The connection pool is resumed successfully.

KDJE37546-I

SQL has been generated successfully. (name = [aa....aa])

aa....aa: Application name

Description

An SQL statement is generated successfully.

KDJE37547-I

Application has not been reloaded because a file has not been modified.

Description

An application is not reloaded because a file is not updated.

KDJE37548-I

The transaction has been committed successfully.

Description

The transaction has been committed successfully.

KDJE37549-I

The transaction has been rolled back successfully.

Description

The transaction has been rolled back successfully.

KDJE37550-I

The transaction has been terminated successfully.

Description

The transaction has been terminated successfully.

KDJE37552-I

The list of deleting batch jobs has been exported successfully.

Description

The list of deleting batch jobs has been exported successfully.

KDJE37553-I

Batch jobs have been deleted successfully.

Description

Batch jobs is deleted successfully.

KDJE37600-W

The parent tag [aa....aa], which contains the tag [bb....bb] with the same set value, has been specified more than once. (name = [bb....bb], value = [cc....cc])

The last specified parent tag will be used.

aa....aa: Parent tag name (<resource-external-property> or <property>)

bb....bb: Tag name

cc....cc: Tag value

Description

The aa....aa tag containing a bb....bb tag with the same set value is specified more than once.

The aa....aa tag specified in the end will be used.

Action

Revise the specification of aa....aa, and make sure that no problem exists.

KDJE37601-W

The parent tag [aa....aa] has been specified more than once as a value for the <method> tag. (value = [bb....bb])

The first specified parent tag will be used.

aa....aa: Parent tag name (<ejb-method-observation-timeout> or <ejb-transaction-timeout>)

bb....bb: Set value of the <method> tag

Description

The same aa....aa tag is specified more than once as the set value for the <method> tag.

The aa....aa tag specified first will be used.

Action

Revise the specification of aa....aa, and make sure that no problem exists.

KDJE37602-W

A specification that places one optional name at a higher or lower level than another optional name is not recommended. (name = [aa....aa,bb....bb])

aa....aa: Optional name

bb....bb: Optional name

Description

A specification for placing an optional name at a higher or lower level than another optional name is not recommended.

Action

If it is possible to indicate a specification other than the one for placing an optional name at a higher or lower level than another optional name, revise the specification of the optional name.

KDJE37603-W

The default interceptors cannot be specified before EJB2.1.

Description

A default interceptor cannot be specified for EJB2.1 or earlier.

Action

Do not specify a default interceptor for EJB2.1 or earlier.

KDJE37604-W

The parent tag [aa....aa], which contains the tag [bb....bb] with the same set value, has been specified more than once. (name = [bb....bb], value = [cc....cc])

The first specified parent tag will be used.

aa....aa: Parent tag name (<interceptor-binding>) or <application-exception>)

bb....bb: Tag name

cc....cc: Value of the duplicate tag

Description

The aa....aa tag containing a bb....bb tag with the same set value is specified more than once.

The aa....aa tag specified first will be used.

Action

Make sure that the value cc....cc specified in the bb....bb tag is not duplicate.

KDJE37605-W

<message-selector>,<acknowledge-mode>,<message-driven-destination> cannot be specified after EJB2.1 Message-driven Bean.

Description

<message-selector>, <acknowledge-mode>, and <message-driven-destination> cannot be specified for a Message-driven Bean of version EJB2.1 or later.

Action

Delete the <message-selector>, <acknowledge-mode>, and <message-driven-destination> tags from the MessageDrivenBean property file of the version EJB2.1 or the later versions, and then re-execute the command.

KDJE37606-E

The Filter property file cannot be added to WAR that does not contain web.xml.

Description

The Filter property file cannot be added to a WAR that does not contain web.xml.

Action

Do not add the Filter property file to a WAR that does not contain web.xml.

KDJE37607-E

A memory shortage has occurred. Check, and if necessary, revise aa....aa. (error details = [bb....bb])

aa....aa: Option definition file name

bb....bb: Error details

Description

The usable memory cannot be secured because a memory shortage has occurred in the server management command. Change the settings of the Java heap size and Metaspace area based on the error details, and then re-execute the command.

Action

When the option definition file name is usrconf.bat or usrconf

When the Java heap is insufficient

Specify the Java VM option -Xmx<size> in the USRCONF_JVM_ARGS key of the option definition file for server management commands, and then extend the maximum size of the Java heap memory allocation pool.

When the Metaspace area is insufficient

Specify the Java VM option -XX:MaxMetaspaceSize=<size> in the USRCONF_JVM_ARGS key of the option definition file for server management commands, and then extend the maximum size of the Metaspace area.

When the C heap is insufficient

Terminate the unnecessary applications running on the operating system on which the server management commands are running.

When the option definition file name is adminagentuser.cfg

When the Java heap is insufficient

Specify the Java VM option -Xmx<size> in the add.jvm.arg key of the option definition file for the Administration Agent, and then extend the maximum size of the Java heap memory allocation pool.

When the Metaspace area is insufficient

Specify the Java VM option -XX:MaxMetaspaceSize=<size> in the add.jvm.arg key of the option definition file for the Administration Agent, and then extend the maximum size of the Metaspace area.

When the C heap is insufficient

Terminate the unnecessary applications running on the operating system on which the APIs of the server management commands are running.

KDJE37608-E

An attempt to get the path has failed.(path name = aa....aa)

aa....aa: Argument

Description

An attempt to acquire the path has failed.

Action

Make sure that the Application Server is installed properly.

KDJE37609-E

The command lock was released on the J2EE server because the request from the command did not come for a long time.

Description

The command exclusion was released in the J2EE server because the request from the command did not come through for a long time.

Action

Re-execute the command.

KDJE37610-E

aa....aa has been deleted, or an error occurred in a work directory.

aa....aa: Application name, EJB-JAR name, WAR name, JavaBeans name, library JAR name, and Resource adapter name

Description

Either aa....aa is deleted, or an error such as the write permissions for the temporary directory for the OS being missing might have occurred in the temporary directory.

Action

Review, and if necessary, revise the temporary directory permissions, and then re-execute the command.

The temporary directories vary depending on the environment; however, the following directories generally serve as the temporary directory:

In Windows

Directories such as the directories specified in the environment variable TMP or the environment variable TEMP

In UNIX

Directories such as /tmp or /var/tmp

KDJE37612-W

The specified property value will be ignored, because it is invalid.(name = [aa....aa], value = [bb....bb])

aa....aa: Tag name

bb....bb: Tag value

Description

The value of the specified property will be ignored because it is invalid.

Action

Make sure that the value bb....bb is not invalid.

KDJE37613-W

The tag which cannot be specified to [aa....aa] was specified.(name = [bb....bb])

aa....aa: EJB1.1, EJB2.0, or EJB2.1

bb....bb: Tag name

Description

A tag that cannot be setup is specified. The settings are ignored and the processing will continue.

Action

Revise the specification of the tag in the property file.

KDJE37614-E

The tag [aa....aa] or the tag [bb....bb] must be specified.

aa....aa: Tag name

bb....bb: Tag name

Description

One of the two tags that must be specified is not specified. The execution of the command will be interrupted.

Action

Check the property file specifications in the manual, and review, and if necessary revise, the tags specified in the property file.

KDJE37615-E

File format is invalid. [aa....aa]

aa....aa: File path

Description

The execution of the command will be interrupted because the file format is invalid.

Action

Revise the file format.

KDJE37616-E

Exporting the list of deleting batch jobs is failed.

Description

An attempt to output the deletion-target list file failed.

Action

Check the error message in the message log of the J2EE server, and then take action according to the error message.

KDJE37617-E

Deleting batch jobs is failed.

Description

An attempt to delete job data failed.

Action

Check the error message in the message log of the J2EE server, and then take action according to the error message.

KDJE37618-W

The list of deleting batch jobs was not exported because no matching batch jobs found.

Description

The list of batch jobs to be deleted was not output because no data matched the deletion condition.

Action

Revise the deletion condition or check whether the job repository contains job data.

KDJE39001-I

The web container is now starting. (server name = aa....aa)

aa....aa: Server name

Description

The Web container will start.

KDJE39002-I

The web container is now stopping. (server name = aa....aa)

aa....aa: Server name

Description

The Web container will stop.

KDJE39003-I

The web container started. (server name = aa....aa)

aa....aa: Server name

Description

The Web container was started.

KDJE39004-I

The web container stopped. (server name = aa....aa)

aa....aa: Server name

Description

The Web container was stopped.

KDJE39005-E

The web container aa....aa cannot be started. bb....bb

aa....aa: Server name

bb....bb: Error contents

Description

The Web container cannot be started.

Action

Implement the action mentioned in the message output before this message.

If a message from which the cause can be identified is not output before this message, contact maintenance personnel.

KDJE39006-E

The web container aa....aa cannot be stopped. bb....bb

aa....aa: Server name

bb....bb: Error contents

Description

The Web container cannot be stopped.

Action

Implement the action mentioned in the message output before this message.

If a message from which the cause can be identified is not output before this message, contact maintenance personnel.

KDJE39007-E

The property file could not be accessed. (property file = aa....aa)

aa....aa: File name

Description

The system property file (sysconf.properties) or the user property file (usrconf.properties) cannot be accessed.

Action

Make sure that the file aa....aa can be accessed, and then re-execute the cjstartweb command or cjstopweb command.

KDJE39008-W

An invalid property is specified. The default value will be used. (aa....aa = bb....bb, default value = cc....cc)

aa....aa: Property name

bb....bb: Value

cc....cc: Default value

Description

The property value is invalid.

The default value will be used.

Action

When changing the property aa....aa from the default value, modify the property value of aa....aa, and then either stop or restart the Web container server or the J2EE server.

KDJE39009-W

The property value is not specified. The default value will be used. (property = aa....aa, default value = bb....bb)

aa....aa: Property name

bb....bb: Default value

Description

The property value is not specified.

The default value will be used.

Action

When changing the property aa....aa from the default value, modify the property value of aa....aa, and then either stop or restart the Web container server or the J2EE server.

KDJE39010-W

Adjusted property aa....aa : bb....bb to cc....cc.

aa....aa: Property name

bb....bb: Value before adjustment

cc....cc: Value after adjustment

Description

The property value will be adjusted.

Action

Adjust the value specified in webserver.connector.inprocess_http.*. If the value after adjustment is not correct, revise the relation between the property values, and then reset the correct value.

KDJE39011-E

An attempt to read aa....aa file has failed. bb....bb

aa....aa: File name

bb....bb: Error contents

Description

An attempt to read web-users.xml or hitachi_web.properties has failed.

Action

When aa....aa is web-users.xml

When the contents of bb....bb are 'Not found'

web-users.xml was not found. Start the server that is set up with the cjwebsetup command. If setup finishes properly, confirm that the corresponding files exist, and then restart the server.

When the contents of bb....bb are 'Invalid file'

Either the file cannot be accessed, or the contents are invalid. Check the file access permissions and the file contents, and then restart the server.

When aa....aa is hitachi_web.properties

When the contents of bb....bb are 'Invalid file'

Either the file cannot be accessed, or the contents are invalid. Check the file access permissions and the file contents. Redeploy in the case of the J2EE server mode. If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup. Restart in the case of the servlet engine mode.

KDJE39012-W

An invalid property is specified. The default value will be used. (J2EE application = aa....aa, context root = bb....bb, cc....cc = dd....dd, default value = ee....ee)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Property name

dd....dd: Value

ee....ee: Default value

Description

The property value specified in hitachi_web.properties is invalid.

The default value will be used. If the property is specified in the user property file, its value will become the default context value.

Action

When the property of bb....bb is changed from the default value, change the property value of bb....bb.

In the case of the J2EE server mode

Modify, and then redeploy. If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Modify, and then restart.

KDJE39013-W

The property value is not specified. The default value will be used. (J2EE application = aa....aa, context root = bb....bb, property = cc....cc, default value = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Property name

dd....dd: Default value

Description

The property value is not specified in hitachi_web.properties.

The default value will be used. If the property is specified in the user property file, its value will become the default context value.

Action

When the property of bb....bb is changed from the default value, change the property value of bb....bb.

In the case of the J2EE server mode

Modify, and then redeploy. If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Modify, and then restart.

KDJE39015-W

Exception occurred in stopping Web container aa....aa : bb....bb.

aa....aa: Server name

bb....bb: Exception information

Description

An exception occurred while the Web container was being stopped.

The stop process will continue.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KDJE39016-E

The WAR file could not be expanded. (WAR file = aa....aa, expanded file = bb....bb)

aa....aa: WAR file name

bb....bb: Expanded file name

Description

An attempt to expand a file (bb....bb) from the WAR file (aa....aa) has failed.

Either there might be no permission to access the file or the contents of the WAR file might be invalid.

Action

Check the file access permissions and the contents of the WAR file, and then redeploy.

KDJE39017-E

The http server on port aa....aa could not be started.

aa....aa: Port number

Description

The simple Web server cannot be started on the specified port number (aa....aa).

Another process might be using the specified port number of the simple Web server.

The port number of the simple Web server can be specified either in the key web.server.connector.http.port or the key ejbserver.http.port of the user property file.

If not specified in the user property file, use the port number 8080 as the default value.

Action

Specify a port number that is not in use by another process, and then restart the server.

KDJE39018-I

The web application reload processing has finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The web application reload processing has finished.

KDJE39019-E

An error occurred during a web application reload processing. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

An error occurred during the web application reload processing.

Action

Any of the following problems occurred during the reload processing. The error message indicating the cause of the problem is output just before this message, in the message log. Check, and then take action.

An error occurred during the initialization of the filter

An error occurred during the initialization of the listener

An error occurred during the initialization of the servlet for which 0 or a greater value is specified in the <servlet><load-on-startup> element of web.xml

An error occurred during the compilation or initialization of the JSP for which 0 or a greater value is specified in the <servlet><load-on-startup> element of web.xml

An error occurred during the re-reading of the persistent unit

The HTTP Cookie name indicating the HTTP session ID is duplicated with the Cookie name specified in the functionality for adding the server ID in a Cookie

KDJE39020-E

An error occurred in analyzing web.xml at line aa....aa. Initialization of the web application will be stopped. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Line number

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

Description

An error occurred during the analysis of web.xml.

Initialization of the web application will stop.

Action

Modify the location shown in the line number of web.xml, and then redeploy.

If the format or contents of XML are invalid, the message KDJE39308-Ewill be output in the Web servlet log. When message KDJE39308-E is output, modify web.xml on the basis of the detailed information.

If the specified order of the tag does not match the schema definition of XML, the line number of the end tag that includes this tag will be output. As a result, confirm that the specified order of the tag included in the tag shown in the line number matches the schema definition of XML.

Note that in the J2EE server mode, web.xml is re-written in the J2EE server, when the J2EE server imports and deploys an application. Since the line number becomes the line number after web.xml is re-written, for the error location, check the web.xml of the corresponding Web application present below the application directory when the expanded archive format is used. When deployment is performed in the archive format, check web.xml included in the exported EAR file.

KDJE39021-W

web.xml could not be found. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

web.xml was not found.

A Web application that does not contain WEB-INF/web.xml might be deployed or the corresponding web.xml might not be present in the deploy destination directory of the Web application, or access permissions might not be available.

Action

Enable reading of WEB-INF/web.xml, and then redeploy.

KDJE39022-E

A servlet class aa....aa or a class it depends on could not be found.

aa....aa: Servlet class name

Description

A servlet class or a class it depends on was not found.

Take action based on the following causes:

A WAR file that does not contain the class required for execution of the servlet might be deployed, or the class required for execution of the servlet might be deleted from the deploy destination directory of the WAR file.

Permission is not granted to access the class required for execution of the servlet.

Action

Include the class required for execution of the servlet, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39023-I

The web application resource was modified. (J2EE application = aa....aa, context root = bb....bb, resource = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the updated resource

Description

The resource (aa....aa) of the Web application was updated.

KDJE39024-I

The web application resource was removed. (J2EE application = aa....aa, context root = bb....bb, resource = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the deleted resource

Description

The resource (aa....aa) of the Web application was deleted.

KDJE39025-E

The web container server could not be connected. (server name = aa....aa)

aa....aa: Server name

Description

The Web container server (aa....aa) cannot be connected.

Either the Web container server is not started, or the webserver.shutdown.port value set in the user property file might be changed while starting the Web container server.

Action

Confirm that the Web container server aa....aa is started.

If the Web container server is running, take the following actions depending on the status:

If the webserver.shutdown.port value is changed, return to the settings during the startup of the Web container server, and then re-execute the cjstopweb command.

If the webserver.shutdown.port value is not changed, forcibly end the processes of the Web container server with the help of the task manager (in Windows).

Note that if the webserver.shutdown.port value is not specified, 8005 is set as the default value.

KDJE39027-E

The port aa....aa for the shutdown request could not be opened.

aa....aa: Port number

Description

The port (aa....aa) for receiving request to shut down the Web container server cannot be opened.

Another process might be using the specified port number for receiving the request to shut down the Web container server.

The port number for receiving request to shut down the Web container server can be specified in the key webserver.shutdown.port of the user property file. If it is not specified in the user property file, use the port number 8005 as a default value..

Action

Specify a port number that is not in use by another process, and then restart the server.

KDJE39028-W

Security manager denied the access to the resource. (resource = aa....aa)

aa....aa: Resource name

Description

The security manager has denied access to the resource (aa....aa) because the system resource to which access is not allowed as per the security policy was accessed.

Action

Make sure that access to the requested resource is appropriate.

KDJE39030-W

The web container server aa....aa received the shutdown request to the web container server bb....bb.

aa....aa: Server name

bb....bb: Server name

Description

The Web container server (aa....aa) has received the shutdown request to the Web container server (bb....bb).

KDJE39031-E

The port aa....aa for the communication with the web server could not be opened.

aa....aa: Port number

Description

The port for communication with the Web server (redirector) cannot be invoked with the specified port number (aa....aa).

Another process might be using the port number (aa....aa) for communication with the Web server (redirector) set in the user property file.

The port number for communication with the Web server (redirector) can be specified in the key webserver.connector.ajp13.port of the user property file. If it is not specified in the user property file, use the port number 8007 as a default value..

Action

Specify a port number that is not in use by another process, and then restart the server.

KDJE39032-I

The specified value of aa....aa property was applied to bb....bb property. (value = cc....cc)

aa....aa: Property name of an older version

bb....bb: Property name of the current version

cc....cc: Property value

Description

The property (aa....aa) of an older version is specified.

The value (cc....cc) specified in the property of an older version was applied to the currently supported property (bb....bb).

KDJE39033-E

Cosminexus Component Container is not installed correctly. (cause = aa....aa)

aa....aa: Maintenance information

Description

Cosminexus Component Container is not installed properly.

Action

Properly install the Web container server or the J2EE server.

KDJE39035-E

The user property file is invalid. (property file = aa....aa)

aa....aa: Property file name

Description

The contents of the user property file (aa....aa) are invalid.

Action

Revise the contents of the user property file, and then re-execute the cjstartweb command or cjstopweb command.

KDJE39036-E

The web container server was terminated because it is out of memory. (server name = aa....aa)

aa....aa: Server name

Description

The Web container server (aa....aa) will terminate because of insufficient memory.

Action

Secure the memory that can be used by the system, and then restart the Web container server.

KDJE39037-I

aa....aa

aa....aa: Character string specified in the argument, or stack trace of the exception object specified in the argument

Description

The character string specified in the log method of the javax.servlet.ServletContext class, or the argument of the log method of javax.servlet.GenericServlet class will be output. If an exception object is specified in the second argument, the stack trace of the specified exception object will be output row-wise.

KDJE39038-E

The user property file could not be found. (property file = aa....aa)

aa....aa: Property file name

Description

The user property file (aa....aa) was not found.

Action

Make sure that the property file exists, and then re-execute the cjstartweb command or cjstopweb command.

KDJE39039-E

The request data from the web server is invalid.

Description

The request information forwarded from the Web server (redirector) is invalid.

Either the redirector registered in the Web server has a version that is not supported by this version or the data other than the request sent from the redirector might have been received.

Action

Make sure that the version of the redirector is supported. Also make sure that the invalid data, such as the direct transmission of an HTTP request, is not sent to the port used by the Web container for communicating with the Web server.

KDJE39040-E

The web container server abnormally terminated. (server name = aa....aa)

aa....aa: Server name

Description

The Web container server (aa....aa) terminated abnormally because an unexpected error occurred.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KDJE39041-E

An error occurred in reading web.xml. Initialization of the web application will be stopped. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

An error occurred while web.xml was being read.

Initialization of the web application will stop. Permission to access web.xml might not be available.

Action

Set the appropriate access permissions, and then redeploy.

KDJE39042-W

An invalid property is specified. This property is ignored. (aa....aa = bb....bb)

aa....aa: Property name

bb....bb: Value

Description

The property value (bb....bb) is invalid.

The property (aa....aa) value will be ignored.

Action

When setting the property value of aa....aa, properly code the property value of aa....aa, and then restart.

KDJE39045-E

The temporary directory of the web application could not be created. Initialization of the web application will be stopped. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The temporary directory of the Web application that will be created below the temporary directory for JSP cannot be created.

Initialization of the web application will stop. The temporary directory of the Web application might not be created or the permission might not be available.

Action

Set the appropriate access permissions, and then redeploy.

KDJE39046-W

The temporary files of the web application could not be deleted. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The temporary files of the Web application cannot be deleted.

The permission to access the files of the temporary directory of the Web application might not be available.

Action

Delete the files of the temporary directory, and then set appropriate permissions.

KDJE39047-E

An invalid context root name is specified. Initialization of the web application will be stopped. (context root = aa....aa)

aa....aa: Context root name

Description

The context root name (aa....aa) is invalid.

Initialization of the web application will stop.

The context root name needs to be a string in an appropriate format, in the form of a URL created from the alphanumeric characters or the following symbols:

/ @ & + $ , - _ . ! ' ( ) %

%, however, can only be used as escape (such as %20).

Action

Modify the context root name, and then redeploy the application.

For details on the appropriate string format in the form of a URL, see RFC2396.

KDJE39048-E

The webapps directory could not be accessed.

Description

The webapps directory cannot be accessed.

The webapps directory does not exist or access permissions are not available.

Action

Create the webapps directory or set the appropriate permission, deploy the Web application, and then restart the Web container server.

KDJE39049-E

There is no web application to deploy.

Description

The Web application to be deployed does not exist.

Action

Deploy the Web application in the webapps directory, and then restart the Web container server.

KDJE39050-I

The web application resource was added. (J2EE application = aa....aa, context root = bb....bb, resource = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the added resource

Description

The Web application resource was added.

KDJE39051-E

The JSP file could not be found. (J2EE application = aa....aa, context root = bb....bb, JSP file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Path within the Web application of the JSP file

Description

The JSP file was not found.

Action

Add the JSP file, and then update the Web application.

In the case of the J2EE server mode

When the reload functionality of the J2EE application is being used, either add the JSP file or redeploy.

When the reload functionality of the J2EE application is not being used in an application with expanded directory format, either stop the application, add the JSP file, and then restart the application, or else redeploy.

In the case of an archive format application, redeploy.

In the case of the servlet engine mode

When application update detection and reload functionality are being used, either add the JSP file, or redeploy.

When application update detection and reload functionality are not being used, either stop the Web container server, add the JSP file, and then restart the Web container server, or else redeploy.

KDJE39052-I

The JSP file or the file used by the JSP file was modified. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the file

Description

In the case of the J2EE server mode

The JSP file or the file used by the JSP file (cc....cc) was modified.

The files used by the JSP file indicate the following files:

Tag files (excluding the tag files within the JAR file)

Files included by the include directive

Files included by include-prelude and include-coda of web.xml

Tag library descriptor (TLD) files (excluding the TLD file within the JAR file)

In the case of the servlet engine mode

The JSP file (cc....cc) was updated.

KDJE39053-I

The JSP file or the file used by the JSP file was removed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root

cc....cc: Absolute path of the file

Description

In the case of the J2EE server mode

The JSP file or the file used by the JSP file (cc....cc) was deleted.

The files used by the JSP file indicate the following files:

Tag files (excluding the tag files within the JAR file)

Files included by the include directive

Files included by include-prelude and include-coda of web.xml

Tag library descriptor (TLD) files (excluding the TLD file within the JAR file)

In the case of the servlet engine mode

The JSP file (cc....cc) is deleted.

KDJE39054-I

The JSP reload processing per JSP file has finished. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root

cc....cc: Absolute path of the class file generated from the JSP file, when the JSP pre-compile functionality is being used. Absolute path of the JSP file, when the JSP pre-compile functionality is not being used.

Description

When the JSP pre-compile functionality is being used

The class generated from the JSP file (cc....cc) is reloaded.

When the JSP pre-compile functionality is not being used

The JSP file (cc....cc) is recompiled, and the generated class is reloaded.

KDJE39055-E

An error occurred in analyzing the tag library descriptor file at line aa....aa. (J2EE application = bb....bb, context root = cc....cc, TLD = dd....dd)

aa....aa: Line number

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, the cjjspc command, or cjjsp2java command

cc....cc: The context root name in the case of the J2EE server mode or the servlet engine mode and a blank string in the case of the cjjspc command or cjjsp2java command

dd....dd: Path of the TLD file

Description

An error occurred while the tag library descriptor (TLD) file was being analyzed.

The path dd....dd of the TLD file will be output in the following format:

In the case of a TLD file within the Web application

Path within the Web application

In the case of a TLD file saved in the JAR file of the Web application

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

In the case of a TLD file within the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Modify the location shown in the line number of the TLD file. If the format or contents of XML are invalid when the application is started, the message KDJE39308-E will be output in either the Web servlet log or the console. When the message KDJE39308-E is output, modify the TLD file on the basis of the detailed information.

If the specified order of the tag does not match the schema definition of XML, the line number of the end tag that includes this tag will be output. As a result, confirm that the specified order of the tag included in the tag shown in the line number matches the schema definition of XML.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39056-E

An exception was raised in executing the request. (request URL = aa....aa, exception = bb....bb)

aa....aa: Resource name

bb....bb: Exception name

Description

An exception occurred during the execution of the request.

Action

Remove the cause due to which the exception was thrown.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39057-E

The status code aa....aa was returned in executing the request. (request URL = bb....bb)

aa....aa: Status code

bb....bb: Resource name (a blank character string, if URL cannot be normalized using the Web server integrated functionality or a simple Web server)

Description

The execution of the request ended with the status code (aa....aa).

Action

Remove the cause due to which the servlet or JSP returned the status code displayed in the message.

However, if the response was already committed when the error causing the message to display occurred, the status code when the response was committed might be output, rather than an error status code (from 400 to 599).

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

Check the cause if an unintended status code is displayed.

The displayed status codes and example causes are as follows:

Status code: 404

Meaning: The requested URL is not found.

Example cause 1: The specified browser URL is incorrect.

Example cause 2: A request was received when the application was not running.

Status code: 503

Meaning: The processing cannot be executed temporarily.

Example cause: A large number of requests were received temporarily.

KDJE39058-I

Could not output the error page because the response was already committed. (error page = aa....aa)

aa....aa: Resource name of the error page

Description

The error page cannot be displayed because the response was already committed.

KDJE39059-E

An exception was raised in outputting the error page. (error page = aa....aa, exception = bb....bb)

aa....aa: Resource name of the error page

bb....bb: Exception name

Description

An exception occurred while the error page was being displayed.

Action

Remove the cause due to which an exception was thrown from the servlet or JSP of the error page.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39060-E

The status code aa....aa was returned in outputting the error page. (error page = bb....bb)

aa....aa: Status code

bb....bb: Resource name of the error page

Description

The display of the error page ended with the status code (aa....aa).

Action

Remove the cause due to which the servlet or JSP of the error page returned the status code displayed in the message.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39061-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace will be output in each line because an exception was thrown by the servlet or JSP processing.

If the output exception is javax.servlet.ServletException exception, javax.servlet.jsp.JspException exception, or javax.servlet.jsp.el.ELException exception that specify the root cause, the stack trace of the root cause will also be output in each line.

Action

Check the servlet or JSP processing and remove the cause of the exception.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39062-W

An invalid value was specified in the cookie. This cookie was ignored. (aa....aa = bb....bb, request URL = cc....cc)

aa....aa: Name of the Cookie that includes invalid characters

bb....bb: Value of the Cookie that includes invalid characters

cc....cc: Requested URL

Description

A name or value including double-byte characters is being used in the Cookie.

This Cookie will be ignored and is not included in the response.

Action

If you want to include double-byte codes in the Cookie, perform URL encoding beforehand, and then set in the Cookie.

KDJE39096-E

The filter class aa....aa or a class it depends on could not be found. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Filter class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

Description

The filter class (aa....aa) or a class it depends on was not found.

When the Web application starts, the processing will be interrupted.

During reload, this filter will be ignored and the reload processing will continue.

Action

Include the class required for execution of the filter, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39097-E

An invalid filter class aa....aa is specified. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Filter class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

Description

An invalid filter class (aa....aa) was specified.

Initialization of the web application will stop.

The filter class must implement the interface javax.servlet.Filter, and must have a constructor without any arguments.

When the Web application starts, the processing will be interrupted.

During reload, this filter will be ignored and the reload processing will continue.

Action

Include the appropriate filter class in the Web application.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39098-E

An exception aa....aa was raised in initialization of the filter class bb....bb. Initialization of the web application will be stopped. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Filter class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

dd....dd: Context root name

Description

An exception occurred during the initialization of the filter class (bb....bb).

When the Web application starts, the processing will be interrupted.

During reload, this filter will be ignored and the reload processing will continue.

Action

Remove the cause due to which an exception occurred during the initialization of the filter class.

If an error occurs in the processing of the Dependency Injection, an error message is output in the message log just before this message. Check, and then take action.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39099-E

An exception aa....aa was raised in the destroy method of the filter class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Filter class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

dd....dd: Context root name

Description

An exception occurred while the filter class (bb....bb) was being released.

The exception will be ignored, and then the processing continues.

Action

Remove the cause due to which an exception occurred during the release of the filter class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39100-E

The listener class aa....aa or a class it depends on could not be found. Initialization of the web application will be stopped. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Listener class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

Description

The listener class (aa....aa) or a class it depends on was not found.

When the Web application starts, the processing will be interrupted.

During reload, this listener will be ignored, and then the reload processing will continue.

Action

Include the class required for execution of the listener, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39101-E

An invalid listener class aa....aa is specified. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Listener class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

Description

An invalid listener class (aa....aa) is specified. The listener class must implement one or more of the following interfaces, and must have a constructor without any arguments.

If the version of the Web application is Servlet 2.3, the listener must not implement an interface added from Servlet 2.4.

When the Web application starts, the processing will be interrupted.

During reload, this listener will be ignored, and then the reload processing will continue.

When the Web application version is Servlet 2.4 or later

javax.servlet.ServletContextListener

javax.servlet.ServletContextAttributeListener

javax.servlet.http.HttpSessionListener

javax.servlet.http.HttpSessionAttributeListener

javax.servlet.ServletRequestListener

javax.servlet.ServletRequestAttributeListener

When the Web application version is Servlet 2.3

javax.servlet.ServletContextListener

javax.servlet.ServletContextAttributeListener

javax.servlet.http.HttpSessionListener

javax.servlet.http.HttpSessionAttributeListener

Action

Include the appropriate listener classes in the Web application.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39102-E

An exception aa....aa was raised in initialization of the listener class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Listener class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

dd....dd: Context root name

Description

An exception occurred during the initialization of the listener class (bb....bb).

When the Web application starts, the processing will be interrupted.

During reload, this listener will be ignored and the reload processing will continue.

Action

Remove the cause due to which an exception occurred during the initialization of the listener class.

If an error occurs in the processing of the Dependency Injection, an error message is output in the message log just before this message. Check, and then take action.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39103-E

An exception aa....aa was raised in notification of the listener class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Listener class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

dd....dd: Context root name

Description

An exception occurred during the execution of the listener class (bb....bb).

When the Web application starts, the start processing will continue.

When the Web application is reloaded, the reload processing will continue.

Action

Remove the cause due to which an exception occurred during the execution of the listener class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39104-E

The tag library validator class aa....aa or a class it depends on could not be found. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Tag library validator class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or the cjjspc command or cjjsp2java command

cc....cc: The context root name in the case of the J2EE server mode or the servlet engine mode, and a blank string in the case of the cjjspc command or cjjsp2java command

Description

The tag library validator class (aa....aa) or a class it depends on was not found.

Take action based on the following causes:

Either the class required for execution of the tag library validator is not included, or the class required for execution of the tag library validator was deleted from the WAR file deploy destination directory, and then the JSP files using the tag library validator were compiled.

Permission to access the class required for execution of the tag library validator is not available.

Action

Include the class required for execution of the tag library validator, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39105-E

An invalid tag library validator class aa....aa is specified. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Tag library validator class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or the cjjspc command or cjjsp2java command

cc....cc: The context root name in the case of the J2EE server mode or the servlet engine mode, and a blank string in the case of the cjjspc command or cjjsp2java command

Description

An invalid tag library validator class (aa....aa) is specified.

The tag library validator class must inherit the class javax.servlet.jsp.tagext.TagLibraryValidator, and must have a constructor without any arguments.

Action

Include the appropriate tag library validator class in the Web application.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39106-E

An exception aa....aa was raised in initialization of the tag library validator class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Tag library validator class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

dd....dd: The context root name in the case of the J2EE server mode or the servlet engine mode, and a blank string in the case of the cjjspc command or cjjsp2java command

Description

An exception occurred during the initialization of the tag library validator class (bb....bb).

Action

Remove the cause due to which an exception occurred during the initialization of the tag library validator class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39107-E

An exception aa....aa was raised in validation of the JSP file or the tag file by the tag library validator class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Tag library validator class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

dd....dd: The context root name in the case of the J2EE server mode or the servlet engine mode, and a blank string in the case of the cjjspc command or cjjsp2java command

Description

In the case of the J2EE server mode or the cjjspc command

An exception occurred during the validation of the JSP file or the tag file of the tag library validator class (bb....bb).

In the case of the servlet engine mode or the cjjsp2java command

An exception occurred during the validation of the JSP file of the tag library validator class (bb....bb).

Action

Remove the cause due to which an exception occurred during the validation of the JSP file or the tag file by the tag library validator class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39108-E

An exception aa....aa was raised in the release method of the tag library validator class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Tag library validator class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

dd....dd: The context root name in the case of the J2EE server mode or the servlet engine mode, and a blank string in the case of the cjjspc command or cjjsp2java command

Description

An exception occurred during the release of the tag library validator class (bb....bb).

Action

Remove the cause due to which an exception occurred during the release of the tag library validator class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39111-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the initialization of the filter class will be output in each line.

Action

Remove the cause due to which the filter class throws the exception displayed in the message.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39112-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the release of the filter class will be output in each line.

Action

Remove the cause due to which an exception occurred during the release of the filter class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39113-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the initialization of the listener class will be output in each line.

Action

Remove the cause due to which the listener class throws the exception displayed in the message.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39114-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the execution of the listener class will be output row-wise.

Action

Remove the cause due to which an exception occurred during the execution of the listener class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39115-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the initialization of the tag library validator class will be output row-wise.

Action

Remove the cause due to which an exception occurred during the initialization of the tag library validator class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39116-E

aa....aa

aa....aa: Stack trace of the exception

Description

In the case of the J2EE server mode or the cjjspc command

The stack trace of the exception thrown during the validation of the JSP file or the tag file by the tag library validator class will be output row-wise.

In the case of the servlet engine mode or the cjjsp2java command

The stack trace of the exception thrown during the validation of the JSP file by the tag library validator class will be output row-wise.

Action

Remove the cause due to which an exception occurred during the validation of the JSP file or the tag file by the tag library validator class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39117-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the release of the tag library validator class will be output row-wise.

Action

Remove the cause due to which an exception occurred during the release of the tag library validator class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39130-W

An error occurred during the data acquisition. (request URL = aa....aa)

aa....aa: Request URL

Description

An error occurred during the acquisition of the POST data.

Take action based on the following causes:

The client might have terminated the transmission of POST data.

The communication between the client and the Web server might be disconnected.

The packet from the redirector might be corrupt.

A communication failure might have occurred between the Web server and the Web container.

Action

Confirm the following details:

The Web server is running properly

No application is sending invalid data to the Web container

No problem exists in the communication path between the Web server and the Web container.

No problem exists in the communication between the Web server and the external network.

KDJE39131-E

The TagExtraInfo class aa....aa or a class it depends on could not be found. (J2EE application = bb....bb, context root = cc....cc, JSP file = dd....dd, tag library = ee....ee)

aa....aa: TagExtraInfo class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or the cjjspc command or cjjsp2java command

cc....cc: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

dd....dd: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

ee....ee: uri attribute value of the taglib directive of this JSP file or tag file

Description

The TagExtraInfo class or a class it depends on was not found.

Action

Include the class required for execution of the TagExtraInfo class, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39132-E

An invalid TagExtraInfo class aa....aa is specified. (J2EE application = bb....bb, context root = cc....cc, file = dd....dd, tag library = ee....ee)

aa....aa: TagExtraInfo class name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or the cjjspc command or cjjsp2java command

cc....cc: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

dd....dd: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

ee....ee: uri attribute value of the taglib directive of this JSP file or tag file

Description

An invalid TagExtraInfo class was specified.

The TagExtraInfo class must fulfill the following conditions:

The class TagExtraInfo must be inherited.

It is not an interface or abstract class.

It must have a public constructor.

Action

Include the appropriate TagExtraInfo class in the Web application.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39133-E

An exception aa....aa was raised in initialization of the TagExtraInfo class bb....bb. (J2EE application = cc....cc, context root = dd....dd, file = ee....ee, tag library = ff....ff)

aa....aa: Exception name

bb....bb: TagExtraInfo class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

dd....dd: The context root name in the case of the J2EE server mode or the servlet engine mode, and a blank string in the case of the cjjspc command or cjjsp2java command

ee....ee: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

ff....ff: uri attribute value of the taglib directive of this JSP file or tag file

Description

An exception occurred during the initialization of the TagExtraInfo class.

Action

Remove the cause due to which an exception occurred during the initialization of the TagExtraInfo class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39134-E

The JSP translation failed because a JSP validation error message was reported from the tag library validator. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, tag library = dd....dd, number of message = ee....ee)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: uri attribute value of the taglib directive of this JSP file or tag file

ee....ee: Number of validation error messages

Description

In the case of the J2EE server mode or the cjjspc command

The tag library validator class has reported an error detected during the validation of the JSP file or the tag file.

In the case of the servlet engine mode or the cjjsp2java command

The tag library validator class has reported an error detected during the validation of the JSP file pages.

The validation error message is output in KDJE39135-E.

Action

See the validation error message, and then confirm the usage method of the tag library. The validation error message is output in the message log or the console with the message KDJE39135-E.

KDJE39135-E

A validation message. (id = aa....aa, message = bb....bb)

aa....aa: Return value of getId method of the ValidationMessage class

bb....bb: Return value of the getMessage method of the ValidationMessage class

Description

The message contents (javax.servlet.jsp.tagext.ValidationMessage class) of the validation error that occurred are described in KDJE39134-E.

If the ValidationMessage is null, aa....aa and bb....bb will also become null.

Action

See the output message, and then confirm the usage method of the tag library.

KDJE39136-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the generation of instances of the TagExtraInfo class, or during the failure in initialization will be output row-wise.

Action

Remove the cause due to which an exception occurred during the initialization of the TagExtraInfo class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39139-E

The host name specified in the property webserver.connector.http.permitted.hosts could not be resolved. (host name = aa....aa)

aa....aa: Host name that cannot be resolved

Description

The host name specified in webserver.connector.http.permitted.hosts cannot be resolved.

Allow access only from the local host, and then start.

Action

Make sure that the specified host name can be resolved, and then restart the server.

KDJE39140-W

Access to the internal http server from a forbidden host was rejected. (IP address = aa....aa)

aa....aa: IP address of the host that was denied access

Description

Access to the simple Web server from a forbidden host was denied.

Action

To allow access from a forbidden host, specify the IP address or the host name of the host that is allowed access in the property webserver.connector.http.permitted.hosts, and then restart the server.

KDJE39141-W

The J2EE server denies access to the URI starting with /ejb/ or /web/ through the web server. (request URI = aa....aa)

aa....aa: Request URI

Description

The accessed request was denied.

In the case of the J2EE server mode, the request beginning with /ejb/ or /web/ cannot be used through the Web server.

KDJE39142-E

An exception aa....aa was raised in the JSP page. The request bb....bb will be forwarded to the errorPage URL cc....cc specified by the JSP page.

aa....aa: Exception name

bb....bb: Request URI

cc....cc: Error page URL

Description

An exception occurred in JSP.

The request will be forwarded to the error page specified in the page directive.

Action

Remove the cause due to which an exception was thrown from JSP.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39143-E

aa....aa

aa....aa: Error message

Description

In the case of the J2EE server mode or the cjjspc command

An error occurred during the compilation of the source code of the servlet generated from the JSP file or the tag file.

The compilation of the error message will be output row-wise.

In the case of the servlet engine mode

An error occurred during the compilation of the source codes of the servlet generated from the JSP file.

The compilation of the error message will be output row-wise.

Action

Remove the cause due to which the compilation error occurred.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command

Re-execute the command.

KDJE39144-E

An exception aa....aa was raised in invocation of the filter class bb....bb. (filter name = cc....cc)

aa....aa: Exception name

bb....bb: Filter class name

cc....cc: Filter name

Description

An exception occurred during the execution of the doFilter method of the filter class (bb....bb).

Action

Remove the cause due which an exception occurred in the doFilter method of the filter class.

KDJE39145-E

The JSP translation failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc) detail = dd....dd

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: Cause of the error occurrence during the analysis of the JSP file or the tag file

Description

In the case of the J2EE server mode or the cjjspc command

An error occurred during the analysis of the JSP file or the tag file.

The error message will be output row-wise.

In the case of the servlet engine mode or the cjjsp2java command

An error occurred during the analysis of the JSP file.

The error message will be output row-wise.

Action

Remove the cause due to which an error occurred during the analysis of the JSP file or the tag file.

If an error occurs during the analysis of the JSP file or tag file of XML format, or an error occurs during the analysis of the tag library descriptor specified in JSP, a message with a message ID beginning with KECX will be output. For details on messages with the message ID beginning with KECX, see 11. KECX (Messages Output by Cosminexus XML Processor).

If you are using JSTL or JSF in a Web application conforming to Servlet 2.5 or later specifications, JSTL or JSF might not have been set up properly. Make sure that a JSTL or a JSF of the correct version is added to the class path.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

If the JSTL or the JSF is not set up properly, restart the J2EE server.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39146-E

An exception aa....aa was raised in invocation of the servlet or JSP. (request URL = bb....bb)

aa....aa: Exception name

bb....bb: request URL

Description

An exception occurred during the execution of the servlet or JSP.

Action

Remove the cause due to which an exception was thrown from the servlet or JSP.

If an error occurs in the processing of the Dependency Injection, an error message is output in the message log just before this message. Check, and then take action.

If JSP throws any of the following exceptions, an error might have occurred during the compilation of the JSP file or the tag file. Make sure that no problem exists in the JSP file or the tag file.

org.apache.jasper.JasperException

org.apache.jasper.compiler.ParseException

org.apache.jasper.compiler.CompileException

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39147-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception that has occurred during the execution of the doFilter method of the filter class will be output row-wise.

If the exception that has occurred is either the ServletException exception or the JspException exception that specifies the root cause, the stack trace of the root cause will be output next, row-wise.

Action

Remove the cause due to which the doFilter method of the filter class throws the exception displayed in the message.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39148-I

aa....aa

aa....aa: Java VM version

Description

This message indicates the Java VM version.

This message is output in cjstdout.log of the Web container server.

KDJE39149-E

The auth-method tag is not specified in web.xml. Initialization of the web application will be stopped. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

When the <auth-constraint> tag is coded in web.xml, the authentication method needs to be specified in the <auth-method> tag. The initialization of the Web application will terminate because the <auth-method> tag is not specified.

Action

Properly specify the <auth-constraint> tag in web.xml, and then redeploy.

KDJE39150-W

The login-config tag is not specified in web.xml. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

When the <auth-constraint> tag is coded in web.xml, a specific resource might not be accessible, if the authentication method is not specified in the <auth-method> tag in the <login-config> tag.

Action

Code the <login-config> tag in web.xml, specify the authentication method using the <auth-method> tag, and then redeploy application.

KDJE39151-E

The form-login-config tag is not specified in web.xml. Initialization of the web application will be stopped. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

When using FORM authentication, you need to specify the <form-login-config> tag in web.xml. The initialization of the Web application will terminate because the <form-login-config> tag is not specified.

Action

Specify the <form-login-config> tag in web.xml, and then redeploy the application.

KDJE39152-E

An exception aa....aa was raised in initialization of the servlet class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: Class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

dd....dd: Context root name

Description

An exception occurred during servlet initialization.

The exception might have occurred in the following processes:

Class loading

Instantiation

init processing of the servlet

Dependency Injection processing

Action

Remove the cause due to which an exception occurred during the initialization of the servlet. The stack trace is output in the Web servlet log. For details on the Web servlet logs, see 4.3.1 Acquiring the Cosminexus Component Container Logs in the uCosminexus Application Server Maintenance and Migration Guide.

If an error occurs in the processing of the Dependency Injection, an error message is output just before this message. The output destination is the message log. Check, and then take action.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39153-E

aa....aa

aa....aa: Stack trace

Description

The stack trace of the exception that has occurred during the initialization of the servlet will be output row-wise.

Action

Remove the cause due to which the exception displayed in the message occurred during the initialization of the servlet.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39154-E

An exception aa....aa was raised in initialization of the JSP. (J2EE application = bb....bb, context root = cc....cc, file = dd....dd)

aa....aa: Exception name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

dd....dd: Path of the JSP file or tag file within the Web application

(However, for a tag file saved in the JAR file, the output will be in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

Description

An exception occurred during the initialization of JSP.

The exception might have occurred in the following processes:

Class loading

Instantiation

init processing of JSP

Action

Remove the cause due to which an exception occurred during the initialization of JSP. The stack trace is output in the Web servlet log.

If the exception name is ClassNotFoundException, the loading of the class generated from JSP might have failed due to the following reasons.

File read permission is not available.

The file system has failed.

Memory is insufficient.

Correct the error location depending on the reason, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39155-E

aa....aa

aa....aa: Stack trace

Description

The stack trace of the exception that occurred during the initialization of JSP will be output row-wise.

Action

Remove the cause due to which the exception displayed in the message occurred during the initialization of JSP.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39156-I

A new request is kept waiting until the web application reload processing has finished. The web application reload processing is waiting until all processing requests are finished. (J2EE application = aa....aa, context root = bb....bb, number of processing requests = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of processing requests

Description

A resource update was detected.

The new requests will be kept waiting until the Web application reload processing has finished.

The Web application reload processing will be kept waiting until all processing requests are finished.

KDJE39157-I

The web application reload processing is waiting until all processing requests have finished. (J2EE application = aa....aa, context root = bb....bb, number of processing requests = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of processing requests

Description

A resource update was detected.

The Web application reload processing will be kept waiting until all processing requests are finished.

KDJE39158-I

The web application reload processing is waiting until all processing requests have finished. (J2EE application = aa....aa, context root = bb....bb, number of processing requests = cc....cc, timeout(sec) = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of processing requests

dd....dd: Period until a timeout occurs

Description

A resource update was detected.

The Web application reload processing will be kept waiting until all processing requests are finished. If the new requests after detection of resource update are either being processed or are within the maximum delay period, the processing will start as it is.

KDJE39159-I

A new request is kept waiting until the web application reload processing has finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The Web application reload processing is starting. The new requests will be kept waiting until the Web application reload processing has finished.

KDJE39160-I

A timeout occurred. A new request is kept waiting until the web application reload processing has finished. The web application reload processing is waiting until all processing requests have finished. (J2EE application = aa....aa, context root = bb....bb, number of processing requests = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of processing requests

Description

A timeout occurred.

The maximum delay period until the new requests are changed to pending status has elapsed. The new requests will be kept waiting until the Web application reload processing has finished. The Web application reload processing will be kept waiting until all processing requests are finished.

KDJE39161-I

The web application reload processing will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The Web application reload processing will start.

KDJE39162-I

The serialization of session objects will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The serialization of session objects will start.

KDJE39163-E

The session information file could not be written. All sessions in the web application are lost. (context root = aa....aa, file path = bb....bb)

aa....aa: Context root name

bb....bb: File path

Description

Writing is not possible in the session information file.

All sessions in the Web application will be lost.

Take action based on the following causes:

Write permission is not available for the session information file.

A directory exists with the same name as the session information file.

The directory that was created during the startup of the Web container server and that outputs the session information file is deleted.

Action

Take action depending on the cause.

KDJE39164-W

The session attribute that is not serializable was found. It will be deleted. (context root = aa....aa, attribute name = bb....bb, class = cc....cc)

aa....aa: Context root name

bb....bb: Attribute name

cc....cc: Class name of the object that cannot be serialized

Description

An object (cc....cc) that cannot be serialized was found in the session attribute (bb....bb).

The corresponding attribute will be deleted.

Action

Change the object registered in the session attribute to one that can be serialized. If the session attribute is used persistently even after reload, modify the corresponding object to one that can be serialized.

KDJE39165-E

An attempt to write the session information file has failed. All sessions in the web application are lost. (context root = aa....aa, file path = bb....bb)

aa....aa: Context root name

bb....bb: File path

Description

An attempt to write in the session information file has failed.

All sessions in the Web application will be lost.

Action

Make sure that the disk capacity is sufficient, and that no error exists.

KDJE39166-E

An attempt to serialize a session object has failed. All sessions in the web application are lost. (context root = aa....aa, attribute name = bb....bb)

aa....aa: Context root name

bb....bb: Attribute name

Description

An attempt to serialize the session object has failed.

All sessions in the Web application will be lost.

Action

Check the contents of the stack trace of message KDJE39167-E output in the Web servlet log, and then take action for the class responsible for the occurrence of the exception.

KDJE39167-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception that has occurred during the serialization of the session object will be output row-wise.

Action

Check the message output as the class responsible for the occurrence of the exception, and then take one of the following actions for that class:

Modify the class responsible for the occurrence of the exception, so that it can be serialized.

Modify the class responsible for the occurrence of the exception, so that it is not included in the session object.

Modify the class responsible for the occurrence of the exception, so that it is not included as a serialization target.

KDJE39168-I

The serialization of session objects has finished. (J2EE application = aa....aa, context root = bb....bb, number of sessions = cc....cc, session information file size(byte) = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of serialized sessions

dd....dd: Size of the session information file

Description

The serialization of session objects has finished.

KDJE39169-I

The deserialization of session objects will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The deserialization of session objects will start.

KDJE39170-E

The session information file could not be read. All sessions in the web application are lost. (context root = aa....aa, file path = bb....bb)

aa....aa: Context root name

bb....bb: File path

Description

The session information file cannot be read.

All sessions in the Web application will be lost.

Take action based on the following causes:

The session information file does not exist.

Read permission is not available for the session information file.

A directory exists with the same name as the session information file.

Action

Take action depending on the cause.

KDJE39171-E

The session information file is invalid. All sessions in the web application are lost. (context root = aa....aa, file path = bb....bb)

aa....aa: Context root name

bb....bb: File path

Description

The session information file is not updated properly.

All sessions in the Web application will be lost.

Action

Do not access the session information file.

KDJE39172-E

An attempt to read the session information file has failed. All sessions in the web application are lost. (context root = aa....aa, file path = bb....bb)

aa....aa: Context root name

bb....bb: File path

Description

An error occurred while the session information file was being read.

All sessions in the Web application will be lost.

Action

Make sure that no problem exists in the disk.

KDJE39173-E

An attempt to deserialize a session object has failed. All sessions in the web application are lost. (context root = aa....aa, attribute name = bb....bb)

aa....aa: Context root name

bb....bb: Attribute name

Description

An attempt to deserialize a session object has failed.

All sessions in the Web application will be lost.

Action

Check the contents of the stack trace of message KDJE39174-E output in the Web servlet log, and then take action for the class responsible for the occurrence of the exception.

KDJE39174-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception that has occurred during the de-serialization of the session object will be output row-wise.

Action

Check the message output as the class responsible for the occurrence of the exception, and confirm the following details:

Has the class of the session attribute, or the class referenced from there been deleted?

Has the class of the session attribute, or the class referenced from there been changed to a configuration not compatible with the data format during serialization?

KDJE39175-E

An attempt to delete the session information file has failed. (context root = aa....aa, file path = bb....bb)

aa....aa: Context root name

bb....bb: File path

Description

An attempt to delete the session information file has failed.

Permission to delete the session information file is not available.

Action

Specify the settings so that the session information file can be deleted.

KDJE39176-I

The deserialization of session objects has finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The deserialization of session objects has finished.

KDJE39177-I

The web application reload processing has finished. The waiting requests are resumed. (J2EE application = aa....aa, context root = bb....bb, number of waiting requests = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of pending requests

Description

The Web application reload processing has finished.

The pending requests will be resumed.

KDJE39178-E

The directory for the session information file could not be created. The session persistence of the web application is invalidated. (context root = aa....aa, directory path = bb....bb)

aa....aa: Context root name

bb....bb: Output destination directory path of the session information file

Description

The directory (bb....bb) for output of the session information file cannot be created.

The session is not persisted.

Take action based on the following causes:

Permission is not available to create the directory for output of the session information file.

Invalid characters have been used to create the directory name.

Files with the same name exist in the same directory.

Action

Take action depending on the cause.

KDJE39179-E

An error occurred in the serialization of session objects. All sessions in the web application are lost. (context root = aa....aa)

aa....aa: Context root name

Description

An error occurred during the serialization of the session object.

All sessions in the Web application will be lost.

Action

Identify the cause from the contents of the stack trace of message KDJE39180-E output in the Web servlet log, and then take action.

KDJE39180-E

aa....aa

aa....aa: Stack trace of the exception that has occurred during the serialization of the session object

Description

The stack trace of the exception that has occurred during the serialization of the session object will be output row-wise.

Action

Check the contents of the stack trace, and then take action.

In the case of java.lang.OutOfMemoryError

The memory is insufficient.

Increase the memory that can be used by the system, and then restart the Web container server.

In cases other than java.lang.OutOfMemoryError

Take action against the cause due to which the session attribute throws the exception displayed in the stack trace.

KDJE39181-E

An error occurred in the deserialization of session objects. All sessions in the web application are lost. (context root = aa....aa)

aa....aa: Context root name

Description

An error occurred during the de-serialization of the session object.

All sessions in the Web application will be lost.

Action

Identify the cause from the contents of the stack trace of message KDJE39182-E output in the Web servlet log, and then take action.

KDJE39182-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception that has occurred during the de-serialization of the session object will be output row-wise.

Action

Check the contents of the stack trace, and then take action.

In the case of java.lang.OutOfMemoryError

The memory is insufficient.

Increase the memory that can be used by the system, and then restart the Web container server.

In cases other than java.lang.OutOfMemoryError

Take action against the cause due to which the session attribute throws the exception displayed in the stack trace.

KDJE39183-I

The update of the file used by the JSP has been detected. The JSP reload processing will start after aa....aa second(s). (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Set value of the interval for updating the JSP file

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

Description

When the JSP pre-compile functionality is being used

An update was detected in the class file generated from the JSP file or the tag file.

The JSP reload processing will start after the time period (aa....aa) (in seconds) specified in the interval for updating the JSP file.

When the JSP pre-compile functionality is not being used

An update was detected in the JSP file or the file being used by the JSP file.

The JSP reload processing will start after the time period (aa....aa) (in seconds) specified in the interval for updating the JSP file.

In the case of the servlet engine mode

An update was detected in the JSP file.

The JSP reload processing will start after the time period (aa....aa) (in seconds) specified in the interval for updating the JSP file.

KDJE39184-E

The temporary files of the web application could not be delete. Initialization of the web application will be stopped. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The temporary files of the Web application for JSP cannot be deleted.

Initialization of the web application will stop.

The permission to access the files for JSP under the temporary directory of the Web application for JSP might not be available.

Action

Delete the files for JSP under the temporary directory for JSP, set the appropriate access permissions, and then redeploy the application.

KDJE39185-E

An error occurred in compiling the source code of the servlet that generate from the JSP file or the tag file. (file = aa....aa)

aa....aa: Path within the Web application of this JSP file or the tag file (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

Description

In the case of the J2EE server mode or the cjjspc command

An error occurred during the compilation of the source code of java generated from the JSP file or the tag file.

In the case of the servlet engine mode

An error occurred during the compilation of the source code of java generated from the JSP file.

Action

Remove the cause due to which the compilation error occurred. The details of the compilation error will be output in the Web servlet log or the console, with the message ID KDJE39143-E.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command

Re-execute the command.

KDJE39186-E

An error occurred in parsing the JSP file or the tag file. (file = aa....aa)

aa....aa: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

Description

In the case of the J2EE server mode or the cjjspc command

An error occurred during the analysis of the JSP file or the tag file.

In the case of the servlet engine mode or the cjjsp2java command

An error occurred during the analysis of the JSP file.

Action

Remove the cause due to which an error occurred during the analysis of the JSP file or the tag file. The details of the error during JSP analysis will be output to the Web servlet log or the console, with the message ID KDJE39145-E.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39187-W

The web container failed to read the request data from the redirector. (redirector = aa....aa:bb....bb, container = cc....cc:dd....dd)

aa....aa: IP address of the connection destination redirector

bb....bb: Port number of the connection destination redirector

cc....cc: IP address of the container

dd....dd: Port number of the container

Description

An error occurred while the request data from the redirector was being read.

The error will occur due to the following causes:

When the communication between the client and the Web server is disconnected (request processing is terminated in the browser and an update is requested)

When the Web server stops

When the data is sent to the Web container from an application other than the redirector

Action

Confirm the following details:

the Web server is running properly.

No application is sending invalid data to the Web container

No problem exists in the communication path between the Web server and the Web container.

KDJE39188-E

The timeout occurred in reading the request data from the redirector. (redirector = aa....aa:bb....bb, container = cc....cc:dd....dd)

aa....aa: IP address of the connection destination redirector

bb....bb: Port number of the connection destination redirector

cc....cc: IP address of the container

dd....dd: Port number of the container

Description

A timeout occurred while reading the data from the redirector.

Action

Confirm the following details:

the Web server is running properly.

No application is sending invalid data to the Web container

no problem exists in the communication path between the Web server and the Web container.

KDJE39189-E

The web application failed to start because the web application has illegal state. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

An attempt to initialize the Web application has failed because the Web application is in an illegal state.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KDJE39190-E

The web container failed to initialize because the web container is illegal state.

Description

An attempt to initialize the Web container has failed because the Web container is in an illegal state.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KDJE39191-E

A number of requests exceeds the waiting queue limit. The request fails. (request URL = aa....aa)

aa....aa: Requested URL

Description

The number of requests has exceeded the size of the pending queue. As a result, the requests will not be pending in the Web application, and will result in an error.

Action

Check whether the specified value of the following pending queue size is appropriate. If the specified value is not appropriate, adjust the value of the pending queue size:

Default pending queue size

Pending queue size of the Web application unit

Pending queue size of the URL group unit

KDJE39192-W

Parameters of the thread control per web application are ignored because they are disabled. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The setting to control the number of concurrently executing threads for each Web application is ignored because the setting to control the number of concurrently executing threads for each Web application is disabled.

Action

Make sure that the settings to control the number of concurrently executing threads for each Web application can be used, change the key webserver.container.thread_control.enabled of the user property file to true, and then restart the J2EE server.

KDJE39193-E

The tag library descriptor is invalid because the tei-class element cannot be used with the variable element in the tag element. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, taglib directive uri = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format:

'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: uri attribute value of the taglib directive of this JSP file or tag file

Description

In the case of the J2EE server mode or the cjjspc command

An attempt to analyze the JSP file or the tag file has failed. The tag library descriptor (TLD) file used from this JSP is invalid because both the elements <tei-class> and <variable> have been set in the tag element.

In the case of the servlet engine mode or the cjjsp2java command

An attempt to analyze the JSP file has failed. The TLD file used from this JSP is invalid because both the elements <tei-class> and <variable> have been set in the tag element.

Action

You cannot specify both the elements <tei-class> and <variable> in the same tag element. Modify the TLD file.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39194-I

The max threads limit of the web application is set to aa....aa. (J2EE application = bb....bb, context root = cc....cc, the configuration of max threads = dd....dd, a number of processing requests = ee....ee)

aa....aa: Maximum number of concurrently executing threads of Web application

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Set value of maximum number of concurrently executing threads

ee....ee: Number of currently executing requests

Description

The maximum number of concurrently executing threads of a Web application with context root aa....aa has become (bb....bb).

The maximum number of concurrently executing threads of the Web application might reduce from the upper limit of the set value based on the settings of other Web applications. If the number of requests that are currently being executed exceeds the maximum number of concurrently executing threads, after the processing of running requests finishes, the requests will be controlled to the current upper-limit value.

KDJE39195-I

The max threads limit of the web application is set to aa....aa. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Maximum number of concurrently executing threads of Web application

bb....bb: J2EE application name

cc....cc: Context root name

Description

The maximum number of concurrently executing threads of a Web application of the context root cc....cc is set to aa....aa.

KDJE39196-E

The contexts failed to deploy. (assignable threads = aa....aa)

aa....aa: Number of assignable threads

Description

An attempt to deploy the Web application has failed.

The setting of concurrently executing number of threads for each Web application is invalid.

The number of assignable threads is the number of threads that can be newly assigned as dedicated threads. When only a Web application, in which the number of dedicated threads is not specified, is deployed, it will fail to be deployed because the maximum number of concurrently executing threads for each Web container are all being used as dedicated threads. In such a case, the number of assignable threads needs to be one or more.

Action

Revise the setting of the concurrently executing number of threads in each Web application, and then redeploy the application.

The total number of dedicated threads of the Web application to be deployed needs to be lesser than or equal to the number of assignable threads. If the number of assignable threads is 0, new deployment will not be possible. Revise the value set as the concurrently executing number of threads of an already deployed Web application.

KDJE39197-I

The max threads limit of the web applications for which parameters of the thread control per web application have not been set are set to aa....aa. (a number of processing requests = bb....bb)

aa....aa: Maximum number of concurrently executing threads of Web application

bb....bb: Number of currently executing requests

Description

The maximum number of concurrently executing threads of a Web application, in which the setting to control the number of concurrently executing threads for each Web application is not specified, has become aa....aa.

If the number of currently executing requests exceeds the maximum number of concurrently executing threads, the requests will be controlled at the current upper-limit value, after the processing of running requests finishes.

KDJE39198-I

The max threads limit of the max threads of the web applications for which parameters of the thread control per web application have not been set are set to aa....aa.

aa....aa: Maximum number of concurrently executing threads of Web application

Description

The concurrently executing number of threads of a Web application, in which the setting to control the maximum number of concurrently executing threads for each Web application is not specified, has become aa....aa.

KDJE39199-I

The unexpected information is contained in the HTTP request header. (started with aa....aa)

aa....aa: Value of first byte

Description

The unexpected information is contained in the HTTP request header.

Action

Make sure that the version of the redirector and the container match.

KDJE39200-E

The value specified to jsp_precompile of a query is invalid. (value = aa....aa)

aa....aa: Value specified in jsp_precompile

Description

The value specified in the query string jsp_precompile is invalid.

Action

Specify the correct value in the query string jsp_precompile.

KDJE39201-E

The temporary directory aa....aa could not be accessed.

When the JSP pre-compile functionality is being used

aa....aa: JSP work directory name

When the JSP pre-compile functionality is not being used

aa....aa: Name of the temporary directory for JSP

Description

When the JSP pre-compile functionality is being used

The JSP work directory (aa....aa) of the Web application cannot be accessed.

When the JSP pre-compile functionality is not being used

The temporary directory (aa....aa) for JSP of the Web application cannot be accessed.

Action

When the JSP pre-compile functionality is being used

Permission might not be available to access the sub directories present below the JSP work directory of the Web application.

Set the appropriate access permissions.

When the JSP pre-compile functionality is not being used

Permission might not be available to access the sub directories present below the temporary directory for JSP, in the Web application.

Set the appropriate access permissions.

KDJE39202-E

An error occurred in reading the class file generated from the JSP file or the tag file. (class file = aa....aa)

aa....aa: Class file name generated from the JSP file or the tag file

Description

In the case of the J2EE server mode

An error occurred while the class file, generated during the compilation of the JSP file or the tag file, was being read.

In the case of the servlet engine mode

An error occurred while the class file, generated during the compilation of the JSP file, was being read.

Action

Remove the cause due to which an exception occurred while the class file generated during the JSP compilation was being read.

Take action based on the following causes:

File read permission is not available.

The file system has failed.

Memory is insufficient.

KDJE39203-W

An attempt to delete a java file generated from the JSP file or the tag file has failed. (file = aa....aa)

aa....aa: Absolute path of the Java source file generated from the JSP file or the tag file

Description

In the case of the J2EE server mode or the cjjspc command

An error occurred while the Java source file (aa....aa) generated during the compilation of the JSP file or the tag file was being deleted.

In the case of the servlet engine mode

An error occurred while the Java source file (aa....aa) generated during the compilation of the JSP file was being deleted.

Action

Remove the cause due to which an error occurred while the Java source file generated during the compilation of the JSP file or the tag file was being deleted.

The possible causes of error are as follows:

File deletion permission is not available.

The file is open.

KDJE39204-E

The temporary directory aa....aa could not be created.

aa....aa: Name of the temporary directory for JSP

Description

The temporary directory (aa....aa) for JSP of the Web application cannot be created.

Permission might not be available to create sub directories below the temporary directory for JSP, in the Web application.

Action

Set the appropriate access permissions.

KDJE39205-E

An attempt to read the tag library descriptor has failed. (TLD = aa....aa)

aa....aa: TLD file path

Description

An attempt to read the tag library descriptor (TLD) file has failed.

The path aa....aa of the TLD file will be output in the following format:

In the case of a TLD file within the Web application

Path within the Web application

In the case of a TLD file saved in the JAR file of a Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

In the case of a TLD file within the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Remove the cause due to which an attempt to read the TLD file has failed.

The possible causes of error are as follows:

The file does not exist.

File read permission is not available.

Read permission is not available for the JAR file that includes the TLD file.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39206-E

An I/O error occurred in reading the tag library descriptor. (TLD = aa....aa)

aa....aa: TLD file path

Description

An I/O error occurred while the tag library descriptor (TLD) file was being read.

The path aa....aa of the TLD file will be output in the following format:

In the case of a TLD file within the Web application

Path within the Web application

In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

In the case of a TLD file within the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Remove the cause due to which an error occurred while the TLD file was being read.

The possible causes of error are as follows:

The memory is insufficient.

File read permission is not available.

A file read error occurred due to disk failure.

When the JAR file containing the TLD file was specified, the JAR file was not in the JAR format.

When the TLD file present in another host was specified and a network error occurred.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39207-E

The tag library descriptor was not found inside the JAR file. (JAR file = aa....aa, TLD file entry = bb....bb)

aa....aa: JAR file path

bb....bb: Entry name of the TLD file

Description

The tag library descriptor (TLD) file was not found in the JAR file.

The path aa....aa of the JAR file will be output in the following format

In the case of a JAR file within the Web application

Path within the Web application

In the case of library JAR

LIB (Path from the root of the J2EE application)

In the case of a JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file)

Action

Use the correct JAR file that contains the TLD file.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39208-E

Unexpected error occurred in reading the tag library descriptor.

Description

An unexpected error occurred while the tag library descriptor (TLD) file was being read.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KDJE39209-W

The host name specified in property webserver.connector.ajp13.bind_host could not be resolved. (host name = aa....aa)

aa....aa: Specified host name

Description

The host (aa....aa) specified in the property webserver.connector.ajp13.bind_host cannot be resolved.

The wild card address will be used.

Action

When using an address other than the wild card address, specify the resolvable local host name or the IP address of the local host, and then restart the server.

KDJE39210-W

The host name specified in property webserver.connector.http.bind_host could not be resolved. (host name = aa....aa)

aa....aa: Specified host name

Description

The host (aa....aa) specified in the property webserver.connector.http.bind_host cannot be resolved.

The wild card address will be used.

Action

When using an address other than the wild card address, specify the resolvable local host name or the IP address of the local host, and then restart the server.

KDJE39211-E

An error occurred in initializing the pageContext object. (J2EE application = aa....aa, context root = bb....bb, JSP file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root

cc....cc: JSP file name

Description

An error occurred during the initialization of the pageContext object.

The stack trace will be output in the Web servlet log.

If the log is not output, the memory might be insufficient. The memory might be insufficient because the value specified in the buffer attribute of the page directive of JSP is too large.

Action

Check the stack trace output to the Web servlet log.

If the memory is insufficient, secure the memory that can be used by the system, and then restart the server.

KDJE39212-W

The host specified in property webserver.connector.ajp13.bind_host could not be bound. (host = aa....aa)

aa....aa: Specified host name

Description

The host (aa....aa) specified in the property webserver.connector.ajp13.bind_host cannot be bound.

A host other than the local host might be specified.

The wild card address will be used.

Action

When using an address other than the wild card address, specify the correct host, and then restart the server.

KDJE39213-W

The host specified in property webserver.connector.http.bind_host could not be bound. (host = aa....aa)

aa....aa: Specified host name

Description

The host (aa....aa) specified in the property webserver.connector.http.bind_host cannot be resolved.

A host other than the local host might be specified.

The wild card address will be used.

Action

When using an address other than the wild card address, specify the correct host, and then restart the server.

KDJE39214-E

An attempt to generate a java file from the JSP file or the tag file has failed. (file = aa....aa, java file = bb....bb)

aa....aa: Path within the Web application of this JSP file or the tag file (in the case of a tag file saved in a JAR file, however, output is in the following format:

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

bb....bb: Java source file name that cannot be generated

Description

In the case of the J2EE server mode or the cjjspc command

A Java source file (bb....bb) cannot be generated from the JSP file or the tag file (aa....aa).

In the case of the servlet engine mode or the cjjsp2java command

A Java source file (bb....bb) cannot be generated from the JSP file (aa....aa).

Action

Take action for the cause due to which the Java source file cannot be generated.

Take action based on the following causes for the error:

The disk space was not enough for generating the Java file.

The file system has failed.

KDJE39215-W

The host name specified in property webserver.connector.http.bind_host was a loopback address. (host name = aa....aa)

aa....aa: Specified host name

Description

A loopback address was specified in the property webserver.connector.http.bind_host.

The wild card address will be used.

Action

When using an address other than the wild card address, specify an appropriate host that is not a loopback address, and then restart the server.

KDJE39216-E

The URI in the taglib directive is invalid because a URI in a taglib directive is mapped absolute and the taglib element is not in web.xml. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, taglib directive uri = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format: 'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: uri attribute value of the taglib directive of this JSP file or tag file

Description

In the case of the J2EE server mode or the cjjspc command

An error occurred during the analysis of the JSP file or the tag file (cc....cc).

The uri attribute value (cc....cc) of the taglib directive of the JSP file or the tag file is invalid.

In the case of the servlet engine mode or the cjjsp2java command

An error occurred during the analysis of the JSP file (cc....cc).

The uri attribute value (cc....cc) of the taglib directive of the JSP file is invalid.

Action

If taglib is not mapped to the <taglib> tag of web.xml, or to the <uri> tag of the tag library descriptor (TLD) file, the absolute URI cannot be specified in the uri attribute of the taglib directive of JSP.

Either map taglib to the <taglib> tag of web.xml or to the <uri> tag of the TLD file, or specify the uri attribute of taglib directive of JSP with a relative path within the Web application.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39217-I

The web application which parameters of the thread control per web application have not been set is deployed. (J2EE application = aa....aa, context root = bb....bb, max threads = cc....cc, default queue size = dd....dd, max threads limit of the web container = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root

cc....cc: Maximum number of concurrently executing threads of a Web application, in which the control of concurrently executing number of threads for each Web application is not specified

dd....dd: Default size of the pending queue

ee....ee: Maximum number of concurrently executing threads for each Web container

Description

A Web application, in which the setting to control the number of concurrently executing threads in each Web application is not specified, is deployed.

No change exists in the maximum number of concurrently executing threads of an already deployed Web application.

KDJE39218-I

The web application which parameters of the thread control per web application have been set is deployed. (J2EE application = aa....aa, context root = bb....bb, max threads = cc....cc, exclusive threads = dd....dd, queue size = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root

cc....cc: Maximum number of concurrently executing threads for each Web application

dd....dd: Number of dedicated threads

ee....ee: Size of the pending queue of each Web application

Description

A Web application, in which the setting to control the number of concurrently executing threads in each Web application is specified, is deployed.

KDJE39219-I

The ClassLoader for the web application was initialized. (context root = aa....aa, initialized time= bb....bb)

aa....aa: Context root

bb....bb: Initialized time

Description

The Class Loader for the Web application is initialized.

KDJE39220-I

The ClassLoader for the web application was finalized. (context root = aa....aa, initialized time = bb....bb)

aa....aa: Context root

bb....bb: Initialized time

Description

This message indicates that a Web application class loader was destroyed.

This message is displayed when the finalize processing (processing of the finalize method) of the Web application class loader is executed after the J2EE application stops.

If this message is not displayed even after starting and stopping the Web applications repeatedly, a memory leak might have occurred.

By comparing the context root and time information output in the KDJE39219-I message, you can identify the Web application class loader that was destroyed. For details, see Appendix B Configuration of the Class Loaders in the uCosminexus Application Server Common Container Functionality Guide.

KDJE39221-W

The performance trace is unavailable due to failure of initialization. (reason = aa....aa)

aa....aa: Reason code

Description

The PRF trace cannot be used due to failure in initialization.

Action

Take action depending on the contents of the reason code shown in aa....aa.

The following reason codes are displayed in aa....aa:

Table 7‒4: List of failure reason codes displayed in KDJE39221-W

Reason code

Cause

Action

-1

Either the environment variable PRFSPOOL is not set, or the directory set in the environment variable PRFSPOOL does not exist.

Confirm that the environment variable PRFSPOOL is set.

-2

An error occurred in the service start processing of the PRF demon present in the process.

The PRF demon might not be invoked.

Confirm that the PRF demon is invoked. Also, check the PRFID of the definition file.

-3

An error (such as system call error) occurred in the service start processing of the PRF demon present in the process.

See the log file present below setup-directory-of-environment-variable-PRFSPOOL\log\PRF-identifier (in Windows) or $PRFSPOOL/log/PRF-identifier (in UNIX), check the Cosminexus Performance Tracer message, and then take action based on the cause.

-4

An attempt to load the library required for the service of PRF demon has failed.

Take action based on the following causes:

Cosminexus Performance Tracer is not installed.

PRF trace output library is not specified in the class path.

The environment variable is invalid.

Correct the cause of the error, and then re-execute the process.

KDJE39222-I

The parameters of the thread control per web application is modified. (J2EE application = aa....aa, context root = bb....bb, max threads = cc....cc, exclusive threads = dd....dd, queue size = ee....ee)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Maximum number of concurrently executing threads after change in settings

dd....dd: Number of dedicated threads after change in settings

ee....ee: Size of the pending queue of each Web application after change in settings

Description

The settings related to the number of concurrently executing threads in each Web application were changed.

KDJE39223-E

The specified number of exclusive threads was not able to be assigned. (assignable threads = aa....aa)

aa....aa: Number of assignable threads

Description

The specified number of dedicated threads cannot be assigned.

The number of dedicated threads of Web application after the change in settings needs to be lesser than or equal to the number of assignable threads. If the number of assignable threads is 0, the number of dedicated threads cannot be increased.

Action

Revise the set number of dedicated threads of the Web application.

KDJE39224-W

The specified property is invalid.(context root=aa....aa, resource=bb....bb, cc....cc=dd....dd)

aa....aa: Context root name

bb....bb: Resource name

cc....cc: Property name

dd....dd: Property value

Description

The specified value of the property is invalid.

The default value will be applied.

Action

If you want to apply a value other than the default value, revise the property value.

KDJE39225-E

The HttpSession object could not be instantiated because the number of HttpSession had reached the maximum. (J2EE application = aa....aa, context root = bb....bb, max sessions = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Maximum number of HttpSession

Description

An HttpSession object cannot be generated because the number of HttpSession has reached the maximum value.

If this message is output frequently, the maximum value of the number of HttpSession might be too small.

Action

If necessary, increase the maximum value of the number of HttpSession.

KDJE39226-I

The maximum number of the HttpSession is not specified. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The maximum value of the of HttpSession is not specified.

The default value will be used.

KDJE39227-I

The maximum number of the HttpSession was applied. (J2EE application = aa....aa, context root = bb....bb, max sessions = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Maximum number of HttpSession

Description

The maximum value of the number of HttpSession was set.

KDJE39228-E

The HTTP request body is too large. The internal http server refuses the request. (request URL = aa....aa, content length = bb....bb)

aa....aa: Request URL

bb....bb: Value specified in the Content-Length header

Description

The simple Web server has denied the accessed request because the body information of the HTTP request is too large.

Action

Remove the cause due to which the size of the body information of HTTP request has become inappropriately large, and then re-access the server.

KDJE39229-E

aa....aa

aa....aa: Stack trace of the exception

Description

An exception occurred during the execution of Servlet API.

Action

Remove the cause of the occurrence of the exception, and then re-execute the command.

KDJE39230-I

aa....aa

aa....aa: Stack trace of the exception

Description

An exception occurred during the execution of Servlet API. The exception output in this message might, however, be ignored.

KDJE39231-W

The number of lines in the generated _jspService method or doTag method has exceeded 1000. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, number of lines = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of this JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format: 'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: Number of lines including the blank lines or comment lines of the generated _jspService method or doTag method

Description

In the case of the J2EE server mode or the cjjspc command

The number of lines of the _jspService method or the doTag method generated from the JSP file or the tag file has exceeded 1000, including the comments and blank lines.

In the case of the servlet engine mode or the cjjsp2java command

The number of lines of the _jspService method generated from the JSP file has exceeded 1000, including the comments and blank lines.

Action

From the specifications of the Java virtual machine, the byte code of one method needs to be within 64 kilobytes. If the byte code of a method exceeds 64 kilobytes, it will result in an error during the generation of class file, or the exception java.lang.LinkageError will occur when the class is loaded.

If the size of one method is within 64 kilobytes, but is still extremely large, the following adverse effects might occur:

A lot of time would be taken for GC processing.

A lot of time would be taken for JIT compilation.

A lot of memory would be consumed for JIT compilation.

As a result, the size of one method on the Java source is recommended to be within 500 lines, excluding comments and blank lines.

Change JSP as follows to reduce the number of lines of Java code generated from JSP:

In the case of JSP file

Divide the JSP file through dynamic inclusion (include action).

In the case of tag file

Either divide the tag file used from the JSP file into multiple tag files, or divide the tag file so as to invoke other tag files from it.

KDJE39232-E

An attempt to delete a class file generated from the JSP file or the tag file has failed. (class file = aa....aa)

aa....aa: Absolute path of the class file generated from the JSP file or the tag file

Description

In the case of the J2EE server mode or the cjjspc command

An error occurred while the class file (aa....aa) generated during the compilation of the JSP file or the tag file was being deleted.

In the case of the servlet engine mode

An error occurred while the class file (aa....aa) generated during the compilation of the JSP file was being deleted.

Action

Take action for the cause of the error that occurred while the class file, generated during the JSP compilation, was being deleted.

The possible causes of error are as follows:

File deletion permission is not available.

The file is open.

KDJE39233-I

A cache function will be applied. (J2EE application = aa....aa, context root = bb....bb, cache size = cc....cc, file size threshold = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Value (in bytes) of the memory size that can be cached in each Web application

dd....dd: Maximum value (in bytes) of the file size that can be cached

Description

The cache functionality will be enabled.

KDJE39234-I

The total size and the number of a cache. (J2EE application = aa....aa, context root = bb....bb, total size = cc....cc, number of a cache = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Total size (in bytes) of the cache

dd....dd: Number of cache

Description

The total size and number of cache will be output.

KDJE39235-W

The value of the cache function specified by web.xml is invalid. (J2EE application = aa....aa, context root = bb....bb, tag name = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Invalid tag name

Description

The setting of the cache functionality specified in web.xml is invalid. The setting of web.xml will be ignored and the Web application will start.

Action

Stop the Web application, modify the corresponding tag in web.xml, and then start the Web application.

KDJE39248-W

The redirection definition is ignored because there are invalid settings. (definition name = aa....aa)

aa....aa: Ignored redirect definition name

Description

The redirect definition will be ignored because the setting is invalid.

Action

Correctly specify the properties of the redirect functionality, and then restart the J2EE server.

KDJE39249-W

The required property of the redirection definition is not specified. (property = aa....aa)

aa....aa: Property name

Description

The mandatory properties of the redirect definition have not been specified.

Action

Specify the mandatory properties, and then restart the J2EE server. The mandatory properties are as follows:

webserver.connector.inprocess_http.redirect.redirect-definition-name.request_url

webserver.connector.inprocess_http.redirect.redirect-definition-name.redirect_url

(when other than 200 is specified in webserver.connector.inprocess_http.redirect.redirect-definition-name.status)

webserver.connector.inprocess_http.redirect.redirect-definition-name.file

(when 200 is specified in webserver.connector.inprocess_http.redirect.redirect-definition-name.status)

KDJE39250-W

The forbidden property of the redirection definition is specified. (aa....aa = bb....bb)

aa....aa: Property name

bb....bb: Property value

Description

A forbidden property of the redirect definition is specified.

Action

Delete the forbidden property, and then restart the J2EE server. The following property cannot be specified under specific conditions:

webserver.connector.inprocess_http.redirect.redirect-definition-name.request_url

(when 200 is specified in webserver.connector.inprocess_http.redirect.redirect-definition-name.status)

KDJE39251-W

The response body file for the redirection definition cannot be read. (aa....aa = bb....bb)

aa....aa: Property name that specifies a file

bb....bb: Property value

Description

The file, sent as the response body of the redirect functionality, cannot be read.

Action

Either the file does not exist, or permission is not available for the file. Specify a file that exists, set appropriate permissions, and then restart the J2EE server.

KDJE39252-W

The error contents customization definition is ignored because there are invalid settings. (definition name = aa....aa)

aa....aa: Ignored error contents customization definition name

Description

The error contents customization definition will be ignored because of invalid settings.

Action

Correctly specify the properties of the error contents customization functionality and then restart the J2EE server.

KDJE39253-W

The required property of the error contents customization definition is not specified. (property = aa....aa)

aa....aa: Property name

Description

The mandatory properties of the error contents customization definition have not been specified.

Action

Specify the mandatory properties, and then restart the J2EE server. The following properties are mandatory:

webserver.connector.inprocess_http.error_custom.error-contents-customization-definition-name.status

webserver.connector.inprocess_http.error_custom.error-contents-customization-definition-name.file

(when webserver.connector.inprocess_http.error_custom.error-contents-customization-definition-name.redirect_url is not specified)

KDJE39254-W

The forbidden property of the error contents customization definition is specified. (aa....aa = bb....bb)

aa....aa: Property name

bb....bb: Property value

Description

The forbidden property of the error contents customization definition is specified.

Action

Delete the forbidden property, and then restart the J2EE server. The following property cannot be specified under specific conditions:

webserver.connector.inprocess_http.error_custom.error-contents-customization-definition-name.file

(when webserver.connector.inprocess_http.error_custom.error-contents-customization-definition-name.redirect_url is specified)

KDJE39255-W

The response body file for the error contents customization definition cannot be read. (aa....aa = bb....bb)

aa....aa: Property name that specifies a file

bb....bb: Property value

Description

The file, sent as the response body of the error contents customization functionality, cannot be read.

Action

Either the file does not exist, or permission is not available for the file. Specify a file that exists, set appropriate permissions, and then restart the J2EE server.

KDJE39264-W

An error occurred during the data acquisition. (request URL = aa....aa)

aa....aa: Request URL

Description

An error occurred during the acquisition of the POST data.

The value of the Content-Length header and the actually read parameter size do not match.

Action

Check the value of the Content-Length header and the size of the request body.

KDJE39266-E

The timeout occurred in writing the response data to the client. (client = aa....aa : bb....bb)

aa....aa: IP address of the client to which you will connect

(IP address of the reverse proxy, if reverse proxy is being used

bb....bb: Port number of the client to which you will connect

(Port number of the reverse proxy, if reverse proxy is being used)

Description

A timeout occurred while a response was being written to the client.

Action

Confirm the following details:

When the proxy server is not being used

No invalid connection exists from a Web client to the J2EE server.

No problem exists in the communication path.

When the proxy server is being used

Reverse proxy is running properly.

No problem exists in the communication path between the reverse proxy and the J2EE server.

Take the following action for the confirmed details:

If a Web client has established an invalid connection, restrict the client based on the address and the port number output in the message.

If a problem exists in the communication path, remove it.

If the reverse proxy is not running properly, resolve the problem of the reverse proxy.

KDJE39271-E

The thread ended abnormally.(name=aa....aa,hash=bb....bb,priority=cc....cc)

aa....aa: Thread name

bb....bb: Hash value

cc....cc: Priority

Description

The thread that receives requests from the redirector was terminated abnormally.

Action

The system resources (memory, file descriptor) might be insufficient.

Implement the action of the message KDJE39273-E output just before this message, and then restart the Web container.

KDJE39272-E

The illegal processing in the servlet or JSP was detected during executing the request.

Description

An invalid processing in the servlet or JSP was detected during the execution of a request. The operation for the request or the response might be executed from multiple threads.

Action

From the log, identify the servlet or JSP that was executed just before the output of this message, save the following objects in instance variables, and then confirm that these objects are not being executed from multiple threads.

javax.servlet.ServletOutputStream object

javax.servlet.http.HttpServletResponse object

java.io.PrintWriter object acquired by the getWriter method of the javax.servlet.ServletResponse class

KDJE39273-E

An exception was raised during connecting with the redirector. (exception = aa....aa)

aa....aa: Exception information notified from Java VM in the case of failure in establishing a connection with the redirector

Description

An attempt to establish a communication connection from the redirector has failed. This might be due to the occurrence of a problem that does not allow continuance of an operation, such as lack of resources of the system in which the Web container is running.

If message KDJE39275-W is output after this message, and if the connection from the redirector is successful after the occurrence of the failure notified by this message, the system might be recovered.

Even if the error is not output in the Web server log or the redirector log, the system might not recover from this failure when the message KDJE39275-W is not output.

Action

From the Web server access log and the redirector log, make sure that the request is being executed properly. In the case of the error occurrence during the communication with the Web container, the system resources, such as memory, file descriptor, or the TCP port might be insufficient. Check the usage status of the system resources, and then make sure whether the estimation of the system resources is correct.

If resources are insufficient, change the system settings.

KDJE39275-W

The connecting with the redirector has succeeded.

Description

An attempt to establish a connection with the redirector was successful, although an exception occurred while establishing a connection with the redirector. This message is output after the message KDJE39273-E, when a connection with the redirector is established successfully. Message KDJE39273-E is output when a connection with the redirector cannot be established due to insufficient system resources, such as memory, file descriptor, or the TCP port.

Action

From the Web server log and the Web container log, make sure whether the request is being executed properly.

If the request is not being executed properly, identify the cause of the error on the basis of the action of the message KDJE39273-E, and then counteract.

KDJE39280-E

The request header is invalid. The web container refused the request. (request uri = aa....aa, bb....bb = cc....cc)

aa....aa: Request URI

bb....bb: Name of the invalid request header

cc....cc: Value of the invalid request header

Description

The Web container server has denied the accessed request because an invalid request header was received.

Action

Make sure whether no problem exists in the Web client that has sent the invalid request, and avoid sending invalid request headers.

KDJE39281-E

An exception was raised during handling the exception. (exception = aa....aa, method = bb....bb , exception = cc....cc)

aa....aa: User-created exception whose method is invoked

bb....bb: Invoked method

cc....cc: Exception that has occurred during the method invocation of the user-created exception

Description

An exception occurred during the method invocation of the user-created exception class.

When the KDJE39059-E message ID is output immediately after this message, an exception occurred during the method invocation of the user-created exception class, while the error page was being displayed.

At this point, the error page is not displayed.

Action

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

KDJE39282-E

The JSP translation failed because a JSP validation error message was reported from the extra Tag info. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, tag library = dd....dd, tag name = ee....ee, number of message = ff....ff)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the cjjspc command

bb....bb: The context root name in the case of the J2EE server mode, and a null character string in the case of the cjjspc command

cc....cc: Path within the Web application of this JSP file or the tag file (in the case of a tag file saved in a JAR file, however, output is in the following format: 'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: uri attribute value of the taglib directive of this JSP file or tag file

ee....ee: Tag name specified in <taglib><tag><name> of the tag library descriptor

ff....ff: Number of validation error messages

Description

The TagExtraInfo class has reported an error detected during the validation of the attributes.

Action

See the validation error message, and then confirm the usage method of the tag library. The validation error message is output in the message log or the console with the message ID KDJE39283-E.

KDJE39283-E

A validation message. (id = aa....aa, message = bb....bb)

aa....aa: Return value of getId method of the ValidationMessage class

bb....bb: Return value of the getMessage method of the ValidationMessage class

Description

The message contents (javax.servlet.jsp.tagext.ValidationMessage class) of the validation error that occurred are described in KDJE39282-E.

If the ValidationMessage is null, aa....aa and bb....bb will also become null.

Action

See the output message, and then confirm the usage method of the tag library.

KDJE39284-W

The unknown element is described. (J2EE application = aa....aa, context root = bb....bb, element = cc....cc, file = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Defined element name

dd....dd: Path of the corresponding file

Description

In the case of the J2EE server mode

An element, not defined in the XML schema, is coded in the corresponding tag library descriptor (TLD) file. The contents of this element will be ignored.

The path dd....dd of the corresponding file will be output in the following format:

In the case of a file within the Web application

Path within the Web application

In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

In the case of the servlet engine mode

An element, not defined in the XML schema, is coded in the corresponding web.xml or TLD file. The contents of this element will be ignored.

The path dd....dd of the corresponding file will be output in the following format:

In the case of a file within the Web application

Path within the Web application

In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

In the case of the J2EE server mode

The message KDJE39286-W is output in the message log. Check the contents.

In the case of the servlet engine mode

If the target file is web.xml, the message KDJE39285-W is output in the message log, and if the target file is a TLD file, the message KDJE39286-W is output. Check the contents.

KDJE39285-W

The web.xml contains the unknown element. (context root = aa....aa)

aa....aa: Context root name

Description

An element, not defined in the XML schema, is coded in web.xml.

The invalid element will be ignored, and then the processing continues.

Action

The corresponding invalid element is output in the Web servlet log, with the ID KDJE39284-W. Check the contents of the invalid element.

KDJE39286-W

The tag library descriptor contains the unknown element. (J2EE application = aa....aa, context root = bb....bb, TLD = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Path of the corresponding file

Description

An element, not defined in the XML schema, is coded in the tag library descriptor (TLD) file. The invalid element will be ignored, and then the processing continues.

The path cc....cc of the corresponding file will be output in the following format:

In the case of a file within the Web application

Path within the Web application

In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

The corresponding invalid element is output in the Web servlet log, with the ID KDJE39284-W. Check the contents of the invalid element.

KDJE39287-W

The specified location of the JAR containing the tag library descriptor file defining the tag-file element is deprecated. (J2EE application = aa....aa, context root = bb....bb, JAR location = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the cjjspc command

bb....bb: The context root name in the case of the J2EE server mode, and a null character string in the case of the cjjspc command

cc....cc: Path within the Web application of the JAR file

Description

Deployment of the JAR file including the TLD file that defines the element <taglib><tag-file> specified in web.xml, JSP file, or the tag file is not recommended.

The Web container reads /META-INF/taglib.tld present in this JAR file, but ignores the <taglib><tag-file> tag.

Action

We recommend that you deploy the JAR file in the directory /WEB-INF/lib/.

When changes are made so as to deploy the JAR file in the directory /WEB-INF/lib, also modify the file that specifies the JAR file.

KDJE39288-I

The webserver.jsp.compile.options property is specified. (value = aa....aa)

aa....aa: Set value of webserver.jsp.compile.options

Description

The webserver.jsp.compile.options property is specified.

KDJE39289-W

The specified location of the tag library descriptor file is deprecated. (J2EE application = aa....aa, context root = bb....bb, TLD location = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of the TLD file

Description

In the case of the J2EE server mode or the cjjspc command

Deployment of the tag library descriptor (TLD) file specified in web.xml, JSP file or the tag file is not recommended.

In the case of the servlet engine mode or the cjjsp2java command

Deployment of the TLD file specified in web.xml, or the JSP file is not recommended.

Action

When the Web application version is Servlet 2.3

Deployment of the file is recommended below the directory /WEB-INF.

When the Web application version is Servlet 2.4 or later

Deployment of the file is recommended below the directory /WEB-INF, excluding the directory /WEB-INF/classes, or the directory /WEB-INF/lib.

KDJE39290-W

The tag library descriptor is invalid. The mustUnderstand attribute is specified in aa....aa element. (J2EE application = bb....bb, context root = cc....cc, file = dd....dd)

aa....aa: Element name in which true is set as the value of mustUnderstand attribute

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or cjjspc command

cc....cc: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of cjjspc command

dd....dd: Path of the corresponding file

Description

True is specified as the value of mustUnderstand attribute of element aa....aa. This tag library descriptor (TLD) file becomes disabled and cannot be used.

The path dd....dd of the corresponding file will be output in the following format:

In the case of a file within the Web application

Path within the Web application

In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

In the case of a TLD file within the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Check the contents of the element in which the mustUnderstand attribute of the TLD file are set.

KDJE39291-E

An exception aa....aa was raised in validation of the attribute by the TagExtraInfo class bb....bb. (J2EE application = cc....cc, context root = dd....dd)

aa....aa: Exception name

bb....bb: TagExtraInfo class name

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

dd....dd: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

Description

An exception occurred during the validation of the attribute by the TagExtraInfo class (bb....bb).

Action

Remove the cause due to which an exception occurred during the validation of the JSP file or the tag file by the TagExtraInfo class.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39292-W

The class file generated from the JSP by the earlier version of the web container exists. (J2EE application = aa....aa, context root = bb....bb, class file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the class file

Description

The class file generated from the JSP by the earlier version of the Web container exists. The Web container will compile JSP.

Action

The class file generated from the JSP with the earlier version of the Web container cannot be used. Delete it from the temporary directory for JSP.

KDJE39293-W

The version of the tag library descriptor is aa....aa although the version of the web application is bb....bb. The tag library descriptor is invalid. (J2EE application = cc....cc, context root = dd....dd, file = ee....ee)

aa....aa: Version of the TLD file

bb....bb: Version of the Web application

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

dd....dd: Context root name

ee....ee: Path of the corresponding file

Description

The version of the tag library descriptor (TLD) file is invalid. The specified TLD file cannot be used in the current version of the Web application.

The path dd....dd of the corresponding file will be output in the following format:

In the case of a file within the Web application

Path within the Web application

In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Implement one of the following actions in the Web application in which the problem occurred:

Change the TLD file version to a version supported by the Web application version.

Change the Web application version to a version supported by the TLD file version.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

When the reload functionality of the J2EE application is being used and the TLD file is modified, either reload or redeploy.

When the reload functionality of the J2EE application is not being used, or the version of the Web application is changed, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

KDJE39294-E

aa....aa

aa....aa: Stack trace of the exception

Description

The stack trace of the exception thrown during the validation of the attribute by the TagExtraInfo class will be output row-wise.

Action

Remove the cause due to which the TagExtraInfo class throws an exception.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39295-E

An attempt to start a web application has failed because the aa....aa version of the web application is not supported by the servlet engine mode. (context root = bb....bb)

aa....aa: Version of the Web application

bb....bb: Context root name

Description

The Web application version is aa....aa. This version is not supported in the servlet engine mode.

This Web application cannot be started.

Action

To use a Web application of Servlet2.4 or a later version, use the J2EE server mode.

KDJE39296-E

The function class aa....aa specified in the tag library descriptor could not be found. (J2EE application = bb....bb, context root = cc....cc, function name = dd....dd, tag library = ee....ee)

aa....aa: Name of the function class specified by the element <function-class> of the TLD file

bb....bb: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

cc....cc: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

dd....dd: Name of the function specified in the element <function><name> of the TLD file

ee....ee: uri attribute value of the taglib directive of this JSP file or tag file

Description

The function class specified by the element <function-class> of the tag library descriptor (TLD) file was not found.

Action

Include the class required for execution of the class defined in the element <function-class> of the TLD file, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39297-W

The specified listener class implementing the aa....aa interface was not registered because this interface is not supported in this web application version. (J2EE application = bb....bb, context root = cc....cc, listener class = dd....dd)

aa....aa: Implemented listener interface name

bb....bb: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

cc....cc: Context root name

dd....dd: Class name specified in web.xml

Description

The specified class implements the listener interface supported by the Servlet 2.4 specifications.

The Servlet 2.4 specifications support the following listener interfaces:

javax.servlet.ServletRequestListener

javax.servlet.ServletRequestAttributeListener

The specified class is not registered as a listener, and is ignored.

Action

To use the listener supported by the Servlet 2.4 specifications, use the Web application version in the application of Servlet 2.4 or later.

KDJE39298-E

An attempt to initialize the JSP has failed because a class file generated from the JSP file or a class file depended on it is invalid. (J2EE application = aa....aa, context root = bb....bb, JSP file = cc....cc, class file = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Path within the Web application of the JSP file that has failed in initialization

dd....dd: Absolute path of the invalid class file

Description

An attempt to initialize the JSP has failed because a class file generated from the JSP file or a class file dependent on it is invalid.

Action

The class file generated from the JSP file or the tag file is invalid.

When using JSTL or JSF in a Web application conforming to Servlet 2.5 or later specifications

The JSTL or the JSF might not be set up properly. Make sure that a JSTL or a JSF of the correct version is added to the class path, and then restart the J2EE server.

When the JSP pre-compile functionality used during application startup is used

Use the JSP pre-compile functionality used during application startup, and compile all JSPs included in the application.

When the JSP pre-compile functionality used during application startup is not used

Compile all JSPs included in the Web application. Update the Web application so that all the class files generated from the JSP file or the tag file are included.

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

KDJE39299-I

The class file generated from the JSP file or the tag file was modified. (J2EE application = aa....aa, context root = bb....bb, class file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Absolute path of the class file

Description

The class file generated from the JSP file or the tag file was updated.

KDJE39300-I

The class file generated from the JSP file or the tag file was removed. (J2EE application = aa....aa, context root = bb....bb, class file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Absolute path of the class file

Description

The class file generated from the JSP file or the tag file was deleted.

KDJE39301-E

An exception aa....aa was raised in initialization of the function class bb....bb. (J2EE application = cc....cc, context root = dd....dd, function name = ee....ee, tag library = ff....ff)

aa....aa: Occurred exception name

bb....bb: Name of the function class specified by the element <function-class> of the TLD file

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the cjjspc command

dd....dd: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

ee....ee: Name of the function specified in the element <function><name> of the TLD file

ff....ff: uri attribute value of the taglib directive of this JSP file or tag file

Description

An exception occurred while the function class specified by the element <function-class> of the tag library descriptor (TLD) file was being loaded.

Action

Remove the cause due to which an exception occurred while the class defined by the element <function-class> of the TLD file was being loaded.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39302-E

The method parameter class aa....aa specified in the tag library descriptor could not be found. (J2EE application = bb....bb, context root = cc....cc, function name = dd....dd, tag library = ee....ee)

aa....aa: Name of the parameter class specified by the element <function-signature> of the TLD file

bb....bb: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

cc....cc: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

dd....dd: Name of the function specified in the element <function><name> of the TLD file

ee....ee: uri attribute value of the taglib directive of this JSP file or tag file

Description

The parameter class of the function specified by the element <function-signature> of the tag library descriptor (TLD) file was not found.

Action

Include the class required for execution of the parameter class defined in the element <function-signature> of the TLD file, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39303-E

An exception aa....aa was raised in initialization of the function. (J2EE application = bb....bb, context root = cc....cc, function name = dd....dd, tag library = ee....ee)

aa....aa: Occurred exception name

bb....bb: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

cc....cc: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

dd....dd: Name of the function specified in the element <function><name> of the TLD file

ee....ee: uri attribute value of the taglib directive of this JSP file or tag file

Description

An exception occurred either while the parameter class of the function specified by the element <function-signature> of the tag library descriptor (TLD) file was being loaded or while the function class specified by the element <function-class> was being accessed.

Action

Remove the cause due to which an exception occurred while the parameter class of the function specified by the element <function-signature> of the TLD file was being loaded, or while the function class specified by the element <function-class> was being accessed.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39304-W

The url-pattern element in web.xml contains the carriage return or line feed character. (J2EE application = aa....aa, context root = bb....bb, element body = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Contents specified in the element <url-pattern>

Description

The linefeed code (CR(#xD) or LF(#xA)) is included in the contents of the element <url-pattern> defined in web.xml.

You cannot include the linefeed code in the contents specified in the element <url-pattern>.

The definition specified by this element will be disabled.

The contents of cc....cc will be displayed without linefeed code.

Action

Modify the contents of the corresponding element, and then redeploy the application.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

KDJE39305-E

The attribute type aa....aa specified for the attribute bb....bb could not be found. (J2EE application = cc....cc, context root = dd....dd, tag name = ee....ee, tag library = ff....ff)

aa....aa: Type of this attribute

bb....bb: Name of this attribute

cc....cc: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the cjjspc command

dd....dd: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

ee....ee: Name of the custom tag that defines this attribute

ff....ff: uri attribute value or tagdir attribute value of the taglib directive of this JSP file or tag file (in the case of the tagdir attribute, output is in the following format: tag library = urn:jsptagdir:value-of-tagdir-attribute)

Description

The class specified in the type attribute of the attribute directive of the class or tag file specified by the element <tag><attribute><type> of the tag library descriptor (TLD) file was not found.

Action

Include the class required for execution of the class defined in the type attribute of the <type> element or the attribute directive of the TLD file, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39306-E

An exception aa....aa was raised in initialization of the attribute type bb....bb specified for the attribute cc....cc. (J2EE application = dd....dd, context root = ee....ee, tag name = ff....ff, tag library = gg....gg)

aa....aa: Occurred exception name

bb....bb: Type of this attribute

cc....cc: Name of this attribute

dd....dd: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

ee....ee: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

ff....ff: Name of the custom tag that defines this attribute

gg....gg: uri attribute value or tagdir attribute value of the taglib directive of this JSP file or tag file (in the case of the tagdir attribute, output is in the following format: tag library = urn:jsptagdir:value-of-tagdir-attribute)

Description

An exception occurred while the class specified in the type attribute of the attribute directive of the class or tag file specified by the element <tag><attribute><type> of the tag library descriptor (TLD) file was being loaded.

Action

Remove the cause due to which an exception occurred while the class defined in the type attribute of the <type> element or the attribute directive of the TLD file was being loaded.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39307-E

The method aa....aa specified in the tag library descriptor could not be found. (J2EE application = bb....bb, context root = cc....cc, function name = dd....dd, function class = ee....ee, tag library = ff....ff)

aa....aa: Function specified by the element <function-signature> of the TLD file

bb....bb: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

cc....cc: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

dd....dd: Name of the function specified in the element <function><name> of the TLD file

ee....ee: Name of the function class specified by the element <function><function-class> of the TLD file

ff....ff: uri attribute value of the taglib directive of this JSP file or tag file

Description

The method specified by the element <function-signature> of the tag library descriptor (TLD) file was not found.

Action

Include the class required for execution of the class defined in the element <function-signature> of the TLD file, in the Web application. Also confirm that appropriate permissions are available for the class file and the JAR file, and if not, set the appropriate access permissions.

Correct the error location, and then update the Web application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39308-E

An error occurred in analyzing the xml. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, detail = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or the cjjspc command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command

cc....cc: Path of the corresponding file

dd....dd: Detailed information of the occurred error

Description

An attempt to analyze the corresponding web.xml, or the tag library descriptor (TLD) file has failed.

The path cc....cc of the corresponding file will be output in the following format:

In the case of a file within the Web application

Path within the Web application

In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

In the case of a TLD file within the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Remove the cause due to which an error occurred during the analysis of web.xml, or the TLD file.

A message with a message ID beginning with KECX will be output in the details of the occurred error. For details on messages with the message ID beginning with KECX, see 11. KECX (Messages Output by Cosminexus XML Processor).

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

When the reload functionality of the J2EE application is being used and the TLD file is modified, either reload or redeploy.

When the reload functionality of the J2EE application is not being used, or the version of the Web application is changed, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command

Re-execute the command.

KDJE39309-E

The class file generated from the JSP file could not be found. (J2EE application = aa....aa, context root = bb....bb, JSP file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Path within the Web application of the JSP file

Description

The class file generated from the JSP file was not found.

Action

When the JSP pre-compile functionality used during application startup is used

If the JSP file does not exist, add it, and then update the Web application.

If the JSP file exists, an error occurs during the JSP compilation. Remove the cause of the error, and then update the Web application.

When the reload functionality of the J2EE application is being used, either compile the added or modified JSP, or redeploy, and then execute the JSP pre-compile functionality used during application startup.

When the reload functionality of the J2EE application is not being used, redeploy, and then execute the JSP pre-compile functionality used during application startup.

When the JSP pre-compile functionality used during application startup is not used

To the JSP work directory, add the class file generated from the JSP file and from the tag file referenced by the JSP file, and then update the Web application.

When the reload functionality of the J2EE application is being used, either add the class file generated from the JSP file and from the tag file referenced by the JSP file, or redeploy.

When the reload functionality of the J2EE application is not being used in an expanded archive format application, either stop the application, add the class file generated from the JSP file and from the tag file referenced by the JSP file, and then restart the application, or else redeploy the application.

In the case of an archive format application, redeploy.

KDJE39310-I

The JSP reload processing will now start. (J2EE application = aa....aa, context root = bb....bb, number of JSP files = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Number of JSP files to be reloaded

Description

The JSP reload processing will start.

When multiple JSP files are updated, the updated JSP files will be reloaded sequentially.

KDJE39311-I

The JSP reload processing has finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

Description

The JSP reload processing has finished.

When multiple JSP files are updated, reload is executed for multiple JSP files.

KDJE39312-I

The JSP reload processing per JSP file will now start. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the class file generated from the JSP file, when the JSP pre-compile functionality is being used. Absolute path of the JSP file, when the JSP pre-compile functionality is not being used.

Description

When the JSP pre-compile functionality is being used

Reload processing of the class generated from the JSP file will start.

When the JSP pre-compile functionality is not being used

Recompilation of the JSP file will start.

KDJE39313-I

The JSP instance was destroyed because the JSP file or the class file generated from the JSP file was removed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Absolute path of the class file generated from the JSP file, when the JSP pre-compile functionality is being used. Absolute path of the JSP file, when the JSP pre-compile functionality is not being used.

Description

When the JSP pre-compile functionality is being used

The JSP instance was released because the class file generated from the JSP file is deleted.

When the JSP pre-compile functionality is not being used

The JSP instance was released because the JSP file is deleted.

KDJE39314-W

The uri to the tag library descriptor mapping is invalid because an uri element is a duplicate of the other file. (J2EE application = aa....aa, context root = bb....bb, uri = cc....cc, valid TLD = dd....dd, invalid TLD = ee....ee)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Duplicate uri

dd....dd: Path within the Web application of the TLD file in which mapping from the uri is valid (in the case of a TLD file saved in a JAR file, however, output is in the following format: Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

ee....ee: Path within the Web application of the TLD file in which mapping from the uri is invalid (in the case of a TLD file saved in a JAR file, however, output is in the following format: Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

Description

In the case of the J2EE server mode, servlet engine mode, or cjjspc command

The contents of the <uri> element and the mapping of the TLD file will become invalid because the contents of the <uri> element coded in the tag library descriptor (TLD) file are same as either the contents of the <taglib-uri> element of web.xml, or the contents of the <uri> element coded in another TLD file.

In the case of the cjjsp2java command

The contents of the <uri> element and the mapping of the TLD file will become invalid because the contents of the <uri> element coded in the tag library descriptor (TLD) file are same as either the contents of uri specified in the command argument -taglib, or the contents of the <uri> element coded in another TLD file.

Action

In the case of the J2EE server mode, servlet engine mode, or the cjjspc command

Specify a value in the <uri> element of the TLD file so that it is not the same as the contents defined in web.xml, and another TLD file.

In the case of the cjjsp2java command

Specify a value in the <uri> element of the TLD file so that it is not the same as the contents of uri specified in the command argument -taglib, and another TLD file.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39315-W

The uri to the tag library descriptor mapping is invalid because an uri element is a duplicate of the other file. (J2EE application = aa....aa, context root = bb....bb, uri = cc....cc, invalid TLD = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Duplicate uri

dd....dd: Path within the Web application of the TLD file in which mapping from the uri is invalid (in the case of a TLD file saved in a JAR file, however, output is in the following format: Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

Description

The contents of the <uri> element and the mapping of the TLD file will become invalid because the contents of the <uri> element coded in the tag library descriptor (TLD) file are same as the contents of the <uri> element coded in another TLD file.

Action

Specify a value in the <uri> element of the TLD file so that it is not the same as another TLD file.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command or cjjsp2java command

Re-execute the command.

KDJE39316-W

The taglib element in web.xml is invalid because a taglib-uri element is a duplicate of the other taglib element. (J2EE application = aa....aa, context root = bb....bb, taglib-uri element in the invalid taglib element = cc....cc, taglib-location element in the invalid taglib element = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, or the cjjspc command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command

cc....cc: Contents of the <taglib-uri> element present in the invalid <taglib> element

dd....dd: Contents of the <taglib-location> element present in the invalid <taglib> element

Description

The contents of the <taglib> element specified in web.xml will become invalid because another <taglib> element with the same <taglib-uri> element is specified.

Action

Specify a value in the <taglib-uri> element defined in web.xml so that it is not the same as the <taglib-uri> element specified in another <taglib> element.

Correct the error location, and then update the Web application.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the servlet engine mode

Redeploy.

In the case of the cjjspc command

Re-execute the command.

KDJE39317-E

The JSP reload processing per JSP file has failed because a class file is invalid. (J2EE application = aa....aa, context root = bb....bb, class file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Absolute path of the class file generated from the JSP file or the tag file

Description

An attempt to reload has failed because the class file generated from the JSP file or the tag file, or the class file on which this class depends is invalid.

Action

The class file generated from the JSP file or the tag file is invalid.

Compile all JSPs included in the Web application. Update the Web application so that all the class files generated from the JSP file or the tag file are included, and then reload or redeploy.

KDJE39318-I

The file used by the JSP file or the tag file was excluded from the update detection list. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Absolute path of the file

Description

The file used by the JSP file or the tag file was excluded from the update detection list due to the following factors:

The JSP file or the tag file using this file is updated, and this file is not in use any longer. No other JSP file or tag file is dependent on the corresponding file.

This file or the JSP file or the tag file, using this file, was updated, but a translation error occurred in the JSP file or the tag file. No other JSP file or tag file is dependent on the corresponding file.

KDJE39319-I

The class file generated from the tag file was excluded from the update detection list. (J2EE application = aa....aa, context root = bb....bb, class file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Absolute path of the class file

Description

The class file generated from the tag file was excluded from the update detection list due to the following factors:

The class file generated from the JSP file or the tag file that use this file is updated, and this file is not in use any longer. Other class files generated from the JSP file or tag files dependent on this file do not exist.

An error occurred while the class generated from the JSP file or the tag file using this file was being loaded. Other class files generated from the JSP file or tag files dependent on this file do not exist.

KDJE39320-I

The default encoding of web application is specified. (J2EE application = aa....aa, context root = bb....bb, request = cc....cc, response = dd....dd, JSP file = ee....ee, extension = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Character encoding used for decoding the request body and query (a null character string if not specified in the user property file, HITACHI Application Integrated Property File, or WAR property file)

dd....dd: Character encoding used for encoding the response body (a null character string if not specified in the user property file, HITACHI Application Integrated Property File, or WAR property file)

ee....ee: Character encoding of JSP (a null character string if not specified in the user property file, HITACHI Application Integrated Property File, or WAR property file)

ff....ff: Extension of the static contents when the default response character encoding is applied (a null character string if the extension of the static contents is not specified or if the default response character encoding is not specified)

Description

The default encoding setup functionality was used.

KDJE39321-W

The specified default encoding to J2EE server is not supported. (type = aa....aa, encoding = bb....bb)

aa....aa: Target for setting up the default character encoding

request: Request body and query

response: Response body

jsp: JSP file

bb....bb: Specified character encoding

Description

The specified character encoding cannot be used for decoding the request body and query, for encoding the response body, and as the character encoding of the JSP file.

Ignore the specified contents, and then start the J2EE server.

Action

The specified character encoding cannot be used for decoding the request body and query, for encoding the response body, and as the character encoding of the JSP file. Revise the character encoding.

The character encoding supported by Java VM can be specified. For details about the character encoding supported by Java VM, follow the Supported encoding section in the JDK document. The character strings that can be specified include "Formal name for java.nio API" and its optional name, and "Formal name for java.io and java.lang API" and its optional name described in the Supported encoding section.

KDJE39322-W

The JSP debugging function is enabled.

Description

The JSP debug functionality is enabled.

Action

We recommend not to use the JSP debug functionality in the execution environment because of its effect on the following performances:

Increase in Metaspace area usage

Increase in parsing during class loading

KDJE39324-E

An attempt to output JSP debugging information has failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Path within the Web application of the JSP file or tag file

Description

An attempt to create the JSP debug information has failed.

Action

Take action based on the following causes:

The disk space for embedding the SMAP information in the class file was not sufficient.

The file system has failed.

Check the cause, and take action.

KDJE39325-W

The uri in tag libraries specified Java EE specification cannot override the taglib element in web.xml or uri in tag library descriptor. (J2EE application = aa....aa, context root = bb....bb, uri = cc....cc, invalid TLD = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

bb....bb: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

cc....cc: URI with duplicate definitions

dd....dd: Path of the TLD file with invalid mapping from the URI

Description

The URI of the tag libraries stipulated in the Java EE specifications cannot be overwritten by the value of the <taglib> tag of web.xml, or the value of the <uri> tag of the tag library descriptor.

URI mapping is performed automatically for the tag libraries (JSTL and JSF) stipulated in the Java EE specifications.

When using JSTL 1.2 or later versions and JSF 1.2 or later versions, a TLD file need not be deployed separately.

The path dd....dd of the TLD file, with invalid mapping from the URI, will be output in the following format:

When an invalid definition exists in web.xml

Value of the <taglib-location> tag included in the disabled <taglib> tag

When an invalid definition exists in the TLD file that is not saved in the JAR file within the Web application

Path from the root of the Web application

When an invalid definition exists in the TLD file saved in the JAR file within the Web application

Path from the root of the Web application (entry = path-within-the-JAR-file)

When an invalid definition exists in the TLD file saved in the library JAR

LIB (Path from the root of the J2EE application) (entry = path-within-the-JAR-file)

When an invalid definition exists in the TLD file saved in the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

When using JSTL 1.2 or later versions and JSF 1.2 or later versions, delete the TLD file deployed in the Web application or in the library JAR.

When using a JSTL and JSF different from the above version, disable the automatic mapping of the tag libraries stipulated in Java EE specifications either by the property settings, or by the options of the cjjspc command.

After changing the settings, update the Web application with the following operation:

For J2EE Server

Restart the J2EE server.

In the case of the cjjspc command

Re-execute the command.

KDJE39326-W

The mapping for the URI that identifies the tag library descriptor in the library JAR file is invalid because the <uri> element is duplicated in other files. (J2EE application = aa....aa, context root = bb....bb, URI = cc....cc, valid TLD = dd....dd, invalid TLD = ee....ee)

aa....aa: The J2EE application name in the case of the J2EE server, and a null character string in the case of the cjjspc command

bb....bb: The context root name in the case of the J2EE server, and a null character string in the case of the cjjspc command

cc....cc: Duplicated URI

dd....dd: Path of the TLD file with valid mapping from the URI

ee....ee: Path of the TLD file with invalid mapping from the URI

Description

The mapping of the contents of the <uri> tag and the TLD file is disabled because the contents of the <uri> tag coded in the TLD file within the library JAR (the JAR file specified in the class path in the case of the cjjspc command) are same as the contents of the <taglib-uri> tag of web.xml or the contents of the <uri> tag coded in another TLD file.

Format of the path dd....dd of the TLD file with valid mapping from the URI

In the case of a TLD file within the Web application

Path within the Web application

In the case of a TLD file saved in the JAR file of the Web application

Path within the Web application of the JAR file (entry = path-within-the-JAR-file)

In the case of a TLD file within the library JAR

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

In the case of a TLD file within the JAR file specified in the class path with the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Format of the path ee....ee of the TLD file with invalid mapping from the URI

For J2EE Server

LIB (Path from the root of the J2EE application of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

In the case of the cjjspc command

LIB (Absolute path of the JAR file in which the TLD file is saved) (entry = path-within-the-JAR-file)

Action

Specify a value in the <uri> tag of the TLD file so that it is not the same as the contents defined in web.xml, and another TLD file.

Correct the error, and then update the J2EE application.

For J2EE Server

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

In the case of the cjjspc command

Re-execute the command.

KDJE39327-E

A given class must not have more than one method annotated with aa....aa. (J2EE application = bb....bb, context root = cc....cc, class = dd....dd)

aa....aa: "PostConstruct" or "PreDestroy"

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Class name

Description

The provided class cannot have more than one method annotated with PostConstruct or PreDestroy.

Action

Revise the J2EE application according to the Java EE specifications.

KDJE39328-E

A method annotated with aa....aa must not have any parameters. (J2EE application = bb....bb, context root = cc....cc, class = dd....dd, method = ee....ee)

aa....aa: "PostConstruct" or "PreDestroy"

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Class name

ee....ee: Method name

Description

A method annotated with PostConstruct or PreDestroy must not have any arguments.

Action

Revise the J2EE application according to the Java EE specifications.

KDJE39329-W

A method annotated with aa....aa must not throw checked exceptions. (J2EE application = bb....bb, context root = cc....cc, class = dd....dd, method = ee....ee)

aa....aa: "PostConstruct" or "PreDestroy"

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Class name

ee....ee: Method name

Description

A method annotated with PostConstruct or PreDestroy cannot throw inspected exceptions.

The method will operate, but will not conform to the Java EE specifications.

A method for which a warning is reported might be defined in web.xml. In such a case, the method is defined in the <post-construct> tag if aa....aa is PostConstruct, and in the <pre-destroy> tag if aa....aa is PreDestroy.

Action

Revise the J2EE application according to the Java EE specifications.

KDJE39330-W

A method annotated with aa....aa must not be declared as static. (J2EE application = bb....bb, context root = cc....cc, class = dd....dd, method = ee....ee)

aa....aa: "PostConstruct" or "PreDestroy"

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Class name

ee....ee: Method name

Description

A method annotated with PostConstruct or PreDestroy cannot be declared as static.

The method will operate, but will not conform to the Java EE specifications.

A method for which a warning is reported might be defined in web.xml. In such a case, the method is defined in the <post-construct> tag if aa....aa is PostConstruct, and in the <pre-destroy> tag if aa....aa is PreDestroy.

Action

Revise the J2EE application according to the Java EE specifications.

KDJE39331-W

The return type of a method annotated with aa....aa must be void. (J2EE application = bb....bb, context root = cc....cc, class = dd....dd, method = ee....ee)

aa....aa: "PostConstruct" or "PreDestroy"

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Class name

ee....ee: Method name

Description

The return-value type of a method annotated with PostConstruct or PreDestroy must be void.

The method will operate, but will not conform to the Java EE specifications.

A method for which a warning is reported might be defined in web.xml. In such a case, the method is defined in the <post-construct> tag if aa....aa is PostConstruct, and in the <pre-destroy> tag if aa....aa is PreDestroy.

Action

Revise the J2EE application according to the Java EE specifications.

KDJE39332-E

The specified value for the aa....aa tag in the web.xml is invalid. (J2EE application = bb....bb, context root = cc....cc, class = dd....dd, method = ee....ee)

aa....aa: "post-construct" or "pre-destroy"

bb....bb: J2EE application name

cc....cc: Context root name

dd....dd: Class name specified in web.xml

ee....ee: Method name specified in web.xml

Description

The value specified in the <post-construct> tag, or <pre-destroy> tag of the Deployment Descriptor is invalid.

Take action based on the following causes:

The class specified in the <lifecycle-callback-class> tag does not exist.

The method specified in the <lifecycle-callback-method> tag does not exist. Alternatively, the method exists, but it contains arguments.

Action

Revise the definition of web.xml, or the J2EE application.

KDJE39333-W

The number of lines in the method used to process a custom tag exceeded 1000. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc, tag = dd....dd, number of lines = ee....ee)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode, cjjspc command or cjjsp2java command

bb....bb: The context root name in the case of the J2EE server mode or the servlet engine mode, and a null character string in the case of the cjjspc command or cjjsp2java command

cc....cc: Path within the Web application of the concerned JSP file or the tag file, and the absolute path of the JSP file in the case of the cjjsp2java command (in the case of a tag file saved in a JAR file, however, output is in the following format: 'Path within the Web application of the JAR file (entry = path-within-the-JAR-file)')

dd....dd: Custom tag name

ee....ee: Number of lines including the blank lines and comment lines of the method for processing the generated tag file

Description

In the case of the J2EE server mode or the cjjspc command

The number of lines of the method for processing the custom tag in the JSP file or tag file has exceeded 1000, including the comments and blank lines.

In the case of the servlet engine mode or the cjjsp2java command

The number of lines of the custom tag processing method coded in the JSP file has exceeded 1000, including the comments and blank lines.

Action

From the specifications of the Java virtual machine, the byte code of one method needs to be within 64 kilobytes. If the byte code of a method exceeds 64 kilobytes, it will result in an error during the generation of class file, or the exception java.lang.LinkageError will occur when the class is loaded.

If the size of one method is within 64 kilobytes, but is still extremely large, the following adverse effects might occur:

A lot of time would be taken for GC processing.

A lot of time would be taken for JIT compilation.

A lot of memory would be consumed for JIT compilation.

As a result, the size of one method on the Java source is recommended to be within 500 lines, excluding comments and blank lines.

The number of lines of the Java code generated from the custom tag can be reduced by splitting the custom tag using dynamic include (include action).

KDJE39334-I

The version of the class file that was compiled from a JSP file or a tag file is different from the current version of the web application. As a result, the JSP file or tag file will be recompiled. (J2EE application = aa....aa, context root = bb....bb, web application version = cc....cc, file = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Version of the Web application to be executed

dd....dd: Path of the JSP file or the tag file in the Web application

Description

The version of the class file created by compiling the JSP file or the tag file differs from the current version.

Recompile the JSP file or the tag file.

KDJE39335-I

The web application version was changed. (J2EE application = aa....aa, context root = bb....bb, web.xml version = cc....cc, web application version = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: web.xml version

dd....dd: Version of the Web application to be executed

Description

The version of the Web application is changed.

KDJE39336-E

The POST form data has exceeded the maximum size. (request URI = aa....aa, size of the post form data = bb....bb, max size of the post form data = cc....cc)

aa....aa: Request URI

bb....bb: Size of POST form data

cc....cc: Maximum size of the POST form data

Description

The form data of the POST request sent by the client exceeds the maximum size.

If the value of the Content-Type header is application/x-www-form-urlencoded

If the Content-Length header exists

An error with status code 413 is returned to the client.

If the Content-Length header does not exist and the value of the Transfer-Encoding header is chunked

The java.lang.IllegalStateException exception is thrown because of the extension of the Servlet API invocation. The POST form data size read as the parameter is output to bb....bb.

If the value of the Content-Type header is multipart/form-data

The java.lang.IllegalStateException exception is thrown because of the extension of the Servlet API invocation. The POST form data size read as the parameter is output to bb....bb.

Action

Check whether the form data size of the POST request sent by the client is the assumed size of the Web application. If the form data has the assumed size, change the specified value of the webserver.connector.limit.max_post_form_data key of the user properties file (maximum size of the form data of the POST request) with an appropriate value. If the maximum form data size of the POST request is changed, you must restart the J2EE server or the Web container server.

KDJE39338-E

The name of the HTTP cookie showing the HTTP session ID is invalid. (J2EE application = aa....aa, context root = bb....bb, session tracking cookie name = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: HTTP Cookie name indicating the HTTP session ID

Description

The name of the HTTP Cookie indicating the HTTP session ID is invalid. The HTTP Cookie name indicating the HTTP session ID specified in the web.xml file or Servlet API is duplicated with the Cookie name specified in the functionality for adding the server ID in a Cookie.

Action

Change either the HTTP Cookie name indicating the HTTP session ID or the Cookie name specified in the functionality for adding the server ID in a Cookie, so that the names are not duplicated.

KDJE39339-E

No servlet class has been specified. (J2EE application = aa....aa, context root name = bb....bb, servlet name = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Servlet name

Description

The servlet cannot be executed because no servlet class has been specified.

Action

Specify the servlet class in the <servlet-class> element of the web.xml file.

KDJE39340-E

No filter class has been specified. (J2EE application = aa....aa, context root name = bb....bb, filter name = cc....cc)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Filter name

Description

The filter cannot be executed because no filter class has been specified.

Action

Specify the filter class in the <filter-class> element of the web.xml file.

KDJE39341-W

The request parameter count exceeded the maximum number. (J2EE application = aa....aa, context root = bb....bb, request URI = cc....cc, max parameter count = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URI

dd....dd: Maximum request parameter count

Description

The number of request parameters sent by the client exceeded the maximum number.

Action

Check whether the number of request parameters sent by the client exceeds the value (maximum request parameter count) set in the webserver.connector.limit.max_parameter_count key of the user property file. If the number of parameters used exceeds the maximum request parameter count, change the maximum request parameter count to an appropriate value. If you change the maximum request parameter count, you must restart the J2EE server or the Web Container server.

KDJE39342-E

The request parameter count exceeded the maximum number. (J2EE application = aa....aa, context root = bb....bb, request URI = cc....cc, max parameter count = dd....dd)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Request URI

dd....dd: Maximum request parameter count

Description

The acquisition of the Part objects was interrupted because the number of parameters included in the POST data of the multipart/form-data request sent by the client exceeded the maximum number.

Action

Check whether the number of parameters included in the POST data of the multipart/form-data request sent by the client exceeds the value (maximum request parameter count) set in the webserver.connector.limit.max_parameter_count key of the user property file. If the number of parameters used exceeds the maximum request parameter count, change the maximum request parameter count to an appropriate value. If you change the maximum request parameter count, you must restart the J2EE server or the Web Container server.

KDJE39400-W

The format form exceeded 1024 characters. The default value will be used.(aa....aa = bb....bb , default value = cc....cc)

aa....aa: Property name

bb....bb: Property value

cc....cc: Default value of property

Description

The format form exceeds 1024 characters. The default value will be used.(aa....aa = bb....bb, Default value = cc....cc)

Action

The character string specified for the property value contains more than 1024 characters.

Reduce the number of characters to be specified.

KDJE39401-W

An undefined format argument is specified. The default value will be used. (property = aa....aa, default value = bb....bb)

aa....aa: Property name

bb....bb: Default value of property

Description

An undefined format argument is specified. The default value will be used.

Action

An undefined format argument is specified.

Specify the defined format argument.

KDJE39402-W

AccessLog is unavailable due. (reason = aa....aa)

aa....aa: Detailed exception message

Description

The access log cannot be used.

Action

One of the following problems has occurred in the access log function of HTTP or WebSocket. Take action depending on the problem.

Permission is not available for the file.

Set appropriate access permissions.

Either the system resources are insufficient or the file system has failed.

Specify the usage status of the system resources of the OS, as well as any problems in the file system, and then take action.

KDJE39500-E

An attempt to deploy the web application failed because the number of shared threads set for deployed web applications is less than one.

Description

An attempt to deploy the Web application has failed.

The setting of concurrently executing number of threads for each Web application is invalid.

Deployment has failed because the number of shared threads for each Web application is less than one.

The number of shared threads for each Web application needs to be one or more.

Action

Set the number of shared threads for each Web application as one or more.

To increase the number of shared threads for each Web application, reduce the number of dedicated threads for each deployed Web application.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

KDJE39501-E

An attempt to deploy the web application failed because the number of shared threads set for web applications to be deployed is less than one. (J2EE application = aa....aa, context root list = bb....bb)

aa....aa: J2EE application name

bb....bb: List of context root of the Web application in which the number of shared threads in each Web application is less than one

Description

An attempt to deploy the Web application has failed.

Either the setting of concurrently executing number of threads for each Web application or the setting of concurrently executing number of threads in each URL group is invalid.

Deployment has failed because the number of shared threads for each Web application is less than one.

The number of shared threads for each Web application needs to be one or more.

Action

Set the number of shared threads for each Web application as one or more. If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

To increase the number of shared threads for each Web application, execute one of the following operations:

Increase the number of shared threads for each Web application with a context root name that is not displayed in the message.

Reduce the number of dedicated threads in each URL group for a Web application with a context root name that is displayed in the message.

KDJE39502-E

An attempt to dynamically change the web application failed because the number of shared threads set for deployed web applications is less than one.

Description

An attempt to dynamically change the settings to control the number of concurrently executing threads of Web application has failed.

The setting of concurrently executing number of threads for each Web application is invalid.

Deployment has failed because the number of shared threads for each Web application is less than one.

The number of shared threads for each Web application needs to be one or more.

Action

Revise the specified maximum number of concurrently executing threads and the number of dedicated threads of the Web application.

To increase the number of dedicated threads of the Web application after changing the settings, the number of shared threads for each Web application needs to be one or more.

KDJE39503-W

The max threads limit of the URL group thread control set to the max threads limit of the web application thread control, because the web application was dynamically changed. (J2EE application = aa....aa, context root = bb....bb, URL group thread control name = cc....cc, max threads = dd....dd, exclusive threads = ee....ee, a number of processing requests = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Definition name for each URL group

dd....dd: Maximum number of concurrently executing threads for each URL group

ee....ee: Number of dedicated threads for each URL group

ff....ff: Number of current processing requests for each URL group

Description

The maximum number of concurrently executing threads at the URL group level is set to the maximum number of concurrently executing threads of the Web application level, because the Web application has changed dynamically.

Action

To operate the maximum number of concurrently executing threads at the URL group level with the set value, set the maximum number of concurrently executing threads of the Web application to a value greater than the maximum number of concurrently executing threads at the URL group level by dynamically changing the Web application.

KDJE39504-I

The max threads limit of the URL group thread control set to the set value, because the web application was dynamically changed. (J2EE application = aa....aa, context root = bb....bb, URL group thread control name = cc....cc, max threads = dd....dd, exclusive threads = ee....ee, a number of processing requests = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Definition name for each URL group

dd....dd: Maximum number of concurrently executing threads for each URL group

ee....ee: Number of dedicated threads for each URL group

ff....ff: Number of current processing requests for each URL group

Description

The maximum number of concurrently executing threads at the URL group level will operate at the set value because the Web application has changed dynamically.

KDJE39505-W

The exclusive threads for a URL group set for this web application cannot be used because the Web application was dynamically changed. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The number of dedicated threads at the URL group level specified in this Web application cannot be used because the Web application was changed dynamically.

Action

To use the number of dedicated threads at the URL group level, set the number of dedicated threads of the Web application to a value greater than the total number of dedicated threads at the URL group level by dynamically changing the Web application. When increasing the number of dedicated threads by dynamically changing the Web application, set the number of shared threads at the Web application level as one or more.

KDJE39506-I

The exclusive threads for a URL group set for this web application can be used because the Web application was dynamically changed. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The number of dedicated threads at the URL group level specified in this Web application can be used because the Web application was changed dynamically.

KDJE39507-E

The timeout occurred in sending the response data to the redirector. (redirector = aa....aa : bb....bb, container = cc....cc : dd....dd)

aa....aa: IP address of the connection destination redirector

bb....bb: Port number of the connection destination redirector

cc....cc: IP address of the container

dd....dd: Port number of the container

Description

A timeout occurred while a response was being sent to the redirector.

Action

Confirm the following details:

the Web server is running properly.

no problem exists in the communication path between the Web server and the Web container.

KDJE39508-I

JSP precompilation has finished. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description

JSP precompilation has finished.

KDJE39510-E

The JSP work directory cannot be accessed. (J2EE application = aa....aa, context root = bb....bb, directory = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the JSP work directory

Description

The JSP work directory cannot be accessed.

Action

One of the following problems occurred. Take action depending on the problem.

Permission is not available to access the directory.

The file system has failed.

KDJE39511-W

A reserved property value is specified. The default value will be used. (aa....aa = bb....bb, default value = cc....cc)

aa....aa: Property name

bb....bb: Property value

cc....cc: Default value

Description

A reserved property value is specified. The default value will be used.

Action

The value specified in the JSP work directory is not case-sensitive, and lib, tags, or classes cannot be used. Check the set value of the key webserver.jsp.precompile.jsp_work_dir of the user property file, and then restart the J2EE server.

KDJE39512-I

The JSP precompilation function is enabled. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The JSP pre-compile functionality is enabled.

KDJE39513-I

The max threads limit of the URL group thread control is set to aa....aa. (J2EE application = bb....bb, context root = cc....cc, URL group thread control name = dd....dd, the configuration of max threads = ee....ee, a number of processing requests = ff....ff)

aa....aa: Context root name

bb....bb: Maximum number of concurrently executing threads for each URL group

cc....cc: J2EE application name

dd....dd: Context root name

ee....ee: Definition name for each URL group

ff....ff: Set value of the maximum number of concurrently executing threads for each URL group

Description

The maximum number of concurrently executing threads at the URL group level of the context root aa....aa has become (bb....bb).

Depending on the upper limit of the set value, the maximum number of concurrently executing threads at the URL group level might depend on the settings of this Web application or the settings of other Web applications, and therefore, the number might be reduced.

If the number of currently executing requests exceeds the maximum number of concurrently executing threads, the requests will be controlled at the current upper-limit value, after the processing of running requests finishes.

KDJE39515-I

The setting used to URL group thread control will now be applied to the web application to be deployed. (J2EE application = aa....aa, context root = bb....bb, URL group thread control name = cc....cc, max threads = dd....dd, exclusive threads = ee....ee, queue size = ff....ff)

aa....aa: J2EE application name

bb....bb: Context root name

cc....cc: Definition name for each URL group

dd....dd: Maximum number of concurrently executing threads for each URL group

ee....ee: Number of dedicated threads for each URL group

ff....ff: Size of the pending queue for each URL group

Description

The setting for controlling the concurrently executing number of threads at the URL group level will be applied to the Web application to be deployed.

KDJE39516-W

The URL pattern bb....bb does not match the definition name aa....aa of a URL group. (J2EE application = cc....cc, context root = dd....dd, URL group thread control name = ee....ee)

aa....aa: Definition name for each URL group

bb....bb: URL pattern

cc....cc: J2EE application name

dd....dd: Context root name

ee....ee: Definition name for each URL group

Description

The URL pattern bb....bb was not mapped to the definition name aa....aa of the URL group level.

Action

The URL mapping will not be performed for the specified URL pattern.

Revise the setting for control of the concurrently executing number of threads at the URL group level.

KDJE39517-E

An attempt to create the JSP work directory has failed. (J2EE application = aa....aa, context root = bb....bb, directory = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the JSP work directory

Description

An attempt to create the JSP work directory has failed.

Action

One of the following problems occurred. Take action depending on the problem.

Permission is not available to access the directory.

The available disk space is insufficient.

The file system has failed.

A file exists with the same name as the JSP work directory.

KDJE39518-E

The java source file to be compiled was not found. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the Java source file

Description

The Java source file translated from the JSP to be compiled was not found.

Action

Permission might not be available to access the file.

Set the appropriate access permissions.

KDJE39519-E

The web.xml was not be found. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description

The file web.xml was not found.

Action

A Web application that does not contain WEB-INF/web.xml might be deployed, the corresponding web.xml might not exists in the deploy destination directory of the Web application, or access permissions might not be available.

Set WEB-INF/web.xml to a state that it can be read.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-execute the command.

KDJE39520-E

An error occurred in while reading web.xml. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description

An error occurred while web.xml was being read.

Action

One of the following problems occurred. Take action depending on the problem.

File read permission is not available.

The file system has failed.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

If the cjjspc command is executed and this message is output, re-execute the cjjspc command.

KDJE39521-E

An error occurred while analyzing web.xml at line aa....aa. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Line number

bb....bb: J2EE application name (a null character string in the case of the cjjspc command)

cc....cc: Context root name (a null character string in the case of the cjjspc command)

Description

An error occurred while analyzing web.xml.

Action

Modify the location shown in the line number of web.xml.

If the format or contents of XML are invalid, the message KDJE39308-Ewill be output in the Web servlet log. When message KDJE39308-E is output, modify web.xml on the basis of the detailed information.

If the specified order of the tag does not match the schema definition of XML, the line number of the end tag that includes this tag will be output. As a result, make sure that the specified order of the tag shown in the line number matches the schema definition of XML.

web.xml is re-written in the J2EE server, when the J2EE server imports and deploys an application. The line number uses the line number after web.xml is re-written, therefore, for the error location, check the web.xml of this Web application present below the application directory, when the expanded archive format is used. When deployment is performed in the archive format, check web.xml included in the exported EAR file.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

If the cjjspc command is executed, re-execute the command.

KDJE39522-E

The class file generated from the JSP file or the tag file cannot be used because its version is invalid. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description

The class file generated by compiling the JSP file or the tag file cannot be used because its version is invalid.

Action

If using the Web application version change functionality, check that the -lowerversion option of the cjjspc command and the webserver.application.lower_version key of the J2EE server have the same values. If the settings are different, recompile to match the -lowerversion option of the cjjspc command with the J2EE server settings or match the webserver.application.lower_version key of the J2EE server with the settings of the -lowerversion option of the cjjspc command, and then restart the J2EE server. If the Web application version change functionality is not used, all the class files generated from the JSP present in the application need to be re-compiled.

If this message is output when the application is started, execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-compile the entire Web application, without specifying the -excludefile and -excludelist options, and the JSP single file.

KDJE39523-E

JSP precompilation at application startup cannot be executed because the JSP precompilation function is disable. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The JSP pre-compile functionality used during application startup cannot be used because the JSP pre-compile functionality is invalid.

Action

If the J2EE server startup mode is the basic mode, the JSP pre-compile functionality cannot be used. Check the set value of the key ejbserver.server.j2ee.feature of the user property file.

KDJE39524-W

The JSP precompilation function is disable. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

The JSP pre-compile functionality is invalid.

Action

If the J2EE server startup mode is the basic mode, the JSP pre-compile functionality cannot be used. Check the set value of the key ejbserver.server.j2ee.feature of the user property file.

KDJE39525-E

JSP precompilation has failed. Application startup will now stop. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

JSP pre-compilation has failed. Application invocation will stop.

Action

Check the error message output just before this message, and then take action.

KDJE39526-E

An attempt to read the version information file has failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the version information file

Description

An attempt to read the version information file has failed.

Action

One of the following problems occurred. Take action depending on the problem.

Permission is not available to access the file.

The file system has failed.

If this message is output when the application is started, execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-compile the entire Web application, without specifying the -excludefile and -excludelist options, and the JSP single file.

KDJE39527-E

An attempt to create the version information file has failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the version information file

Description

An attempt to create the version information file has failed.

Action

One of the following problems occurred. Take action depending on the problem.

Permission is not available to access the file.

The available disk space is insufficient.

The file system has failed.

If the JSP pre-compile functionality used during application startup is executed, re-execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-compile the entire Web application, without specifying the -excludefile and -excludelist options, and the JSP single file.

KDJE39528-I

JSP precompilation will now start. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description

JSP pre-compilation is started.

KDJE39529-W

A directory could not be accessed during a search for a JSP file. (J2EE application = aa....aa, context root = bb....bb, directory = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the directory that cannot be accessed

Description

A directory cannot be accessed while searching for a JSP file. The JSP files of this directory will not be compiled, and then the processing continues.

Action

One of the following problems occurred. Confirm if action needs to be taken, and if it is to be taken, it will depend on the occurred problem. If there are some files that need to be compiled, re-execute JSP pre-compile.

Permission is not available to access the file.

The file system has failed.

KDJE39530-E

An unexpected error occurred. (J2EE application = aa....aa, context root = bb....bb, message = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Exception message

Description

An unexpected exception occurred.

Action

From the exception message, check whether any problem exists.

If no problem exists, contact maintenance personnel.

KDJE39531-E

The contents of the version information file are invalid. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the version information file

Description

The contents of the version information file are invalid. Either the version information file is corrupt or contains invalid strings.

Action

If this message is output when the application is started, execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-compile the entire Web application, without specifying the -excludefile and -excludelist options, and the JSP single file.

KDJE39532-W

The url-pattern element in web.xml contains the carriage return or line feed character. (J2EE application = aa....aa, context root = bb....bb, element body = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Contents specified in the element <url-pattern>

Description

The linefeed code (CR(#xD) or LF(#xA)) is included in the contents of the element <url-pattern> defined in web.xml. You cannot include the linefeed code in the contents specified in the element <url-pattern>. The definition specified by this element will be disabled. The contents of cc....cc will be displayed without linefeed code.

Action

Modify the contents of the corresponding element, and then redeploy the application. If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

If the cjjspc command is executed, re-execute the command.

KDJE39533-E

The version information file does not exist. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description

The JSP work directory exists, but the version information file is not present below the JSP work directory.

Action

If this message is output when the application is started, re-execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-compile the entire Web application, without specifying the -excludefile and -excludelist options, and the JSP single file.

Note that in Windows, this message is output even when there are no access permissions.

KDJE39534-E

An error occurred during Dependency Injection. Initialization of the web application will be stopped. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

An error occurred in the processing of the Dependency Injection.

Initialization of the web application will stop.

Action

An error message of the processing of the Dependency Injection is output to the message log just before this message. Check, and then take action.

Correct the error location, and then redeploy.

KDJE39535-E

An attempt to create the lock file has failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the lock file

Description

An error occurred while the lock file was being created.

Action

One of the following problems occurred. Take action depending on the problem.

Permission is not available to access the JSP work directory.

Permission is not available to access the lock file.

The available disk space is insufficient.

The file system has failed.

If the JSP pre-compile functionality used during application startup is executed and this message is output, re-execute the JSP pre-compile functionality used during application startup.

When the cjjspc command is executed, re-compile the entire Web application, without specifying the -excludefile and -excludelist options, and the JSP single file.

KDJE39536-E

JSP precompilation is being executed. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description

The JSP pre-compile functionality used during application startup or the cjjspc command is being executed.

Action

After the JSP pre-compile functionality being executed finishes, re-execute JSP pre-compilation.

KDJE39537-W

An attempt to delete the lock file has failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the lock file

Description

An attempt to delete the lock file has failed.

Action

One of the following problems occurred.

JSP pre-compilation is already being executed in another process.

File deletion permission is not available.

The file is open.

The file system has failed.

There is no problem if JSP pre-compilation is already being executed in another process. If this message is output without any concern as to whether the JSP pre-compilation is being executed elsewhere, take action depending on the problem.

KDJE39538-E

An attempt to delete a java source file generated from the JSP file or the tag file has failed. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Absolute path of the Java source file generated from the JSP file or the tag file

Description

An error occurred while the Java source file (aa....aa) generated during the compilation of the JSP file or the tag file was being deleted.

Action

Take action for the cause of the error that occurred while the Java source file, generated during the compilation of the JSP file or the tag file was being deleted. Re-execute JSP pre-compilation.

The possible causes of error are as follows:

File deletion permission is not available.

The file is open.

The file system has failed.

KDJE39539-W

An invalid property is specified. The default property will be used. (invalid property = aa....aa, value = bb....bb, default property = cc....cc, value = dd....dd)

aa....aa: Property name for which an invalid value is set

bb....bb: Invalid value

cc....cc: Default property name

dd....dd: Set value

Description

The value bb....bb set in the property (aa....aa) is invalid.

The value (dd....dd) set in the default property (cc....cc) will be used. If a value is not specified in the default property, the default value of the default property will be used.

Action

When changing the property aa....aa from the value set in the default property, modify the property value of aa....aa, and then either stop or restart the Web container server or the J2EE server.

KDJE39540-I

aa....aa JSP files will be compiled. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Number of JSP files to be compiled

bb....bb: J2EE application name (a null character string in the case of the cjjspc command)

cc....cc: Context root name (a null character string in the case of the cjjspc command)

Description

The number of JSP files to be compiled will be displayed.

KDJE39541-I

JSP file does not exists. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

Description

There are no JSP files to be compiled.

KDJE39542-E

An exception was raised in executing the request to the static content. (request URL = aa....aa, exception = bb....bb, detail = cc....cc)

aa....aa: Request URL

bb....bb: Exception name

cc....cc: Detailed exception message

Description

An error occurred in a request to the static contents.

The possible causes of error are as follows:

The static contents have been deleted.

The OS resources have been consumed and the static contents cannot be opened.

The contents cannot be accessed because permission is not available for the file.

The file system has failed.

Action

One of the following problems occurred. Take action depending on the problem.

The static contents have been deleted.

In the case of the J2EE server mode

If the reload functionality of the J2EE application is being used, either reload or redeploy.

If the reload functionality of the J2EE application is not being used, redeploy.

In the case of the servlet engine mode

When the application update detection and the reload functionality are being used, either reload or redeploy.

When the application update detection and the reload functionality are not being used, redeploy.

Permission is not available to access the static contents.

Set appropriate access permissions.

Either the system resources are insufficient or the file system has failed.

Specify the usage status of the system resources of the OS, as well as any problems in the file system, and then take action.

KDJE39543-E

An unexpected exception was raised in the web application reload processing. (J2EE application = aa....aa, context root = bb....bb, exception = cc....cc, detail = dd....dd)

aa....aa: The J2EE application name in the case of the J2EE server mode, and a null character string in the case of the servlet engine mode

bb....bb: Context root name

cc....cc: Exception name

dd....dd: Detailed exception message

Description

An unexpected exception occurred in the reload processing of the Web application.

Action

If exception java.lang.OutOfMemoryError occurs, the memory is insufficient. Increase the memory that can be used by the system, and then restart the J2EE server or the Web container server.

If other than exception java.lang.OutOfMemoryError occurs, Acquire the maintenance information, and then contact maintenance personnel.

KDJE39544-I

The id attribute of a useBean action has been specified more than once. (J2EE application = aa....aa, context root = bb....bb, file = cc....cc(dd....dd,ee....ee), id = ff....ff)

aa....aa: J2EE application name (a null character string in the case of the cjjspc command)

bb....bb: Context root name (a null character string in the case of the cjjspc command)

cc....cc: Path within the Web application of the JSP file

dd....dd: Number of lines of the useBean action in the JSP file

ee....ee: Column of the useBean action in the JSP file

ff....ff: id attribute name of the useBean action

Description

The id attribute of the useBean action is duplicate.

KDJE39546-W

Invalid locale was detected in the Accept-Language header. This locale was ignored. (request uri = aa....aa, locale = bb....bb)

aa....aa: Request URI

bb....bb: Invalid locale

Description

An invalid locale was detected in the Accept-Language header. The invalid locale will be ignored.

KDJE39547-E

There is a problem in the JAX-WS settings. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name

bb....bb: Context root name

Description

A problem exists in the settings of JAX-WS.

Action

Initialization of the web application will stop.

See the JAX-WS document and revise the following settings. Next, execute the deployment process again.

webserver.container.jaxws.webservice.no_webxml.enabled property

webserver.container.jaxws.webservice.wsee.no_webxml.enabled property

Settings of the JAX-WS library of usrconf.cfg

KDJE39548-E

Processing of a JAR file failed during the scanning of a aa....aa. (JAR file = bb....bb, context root = cc....cc, message = dd....dd)

aa....aa: Static Resource or ServletContainerInitializer

bb....bb: JAR file path

cc....cc: Context root name

dd....dd: Exception message

Description

The processing of a JAR file failed while searching the implementation class of a static resource or ServletContainerInitializer.

Action

Check whether the specified JAR file is corrupted and whether the implementation class of the static resource or ServletContainerInitializer can be read.

KDJE39549-W

While searching for a class that extends or implements a class specified in the HandlesTypes annotation, or a class that has the annotation specified in the HandlesTypes annotation, the class or another class failed to load. (class name = aa....aa, message = bb....bb)

aa....aa: Class name

bb....bb: Exception message

Description

While searching for a class that extends or implements the class specified in the HandlesTypes annotation of the ServletContainerInitializer interface, or a class that has the annotation specified in the HandlesTypes annotation, the class failed to load. This class is ignored.

Action

Check whether the applicable class or the class required for loading that class is included in the Web application.

KDJE39550-E

Static content cannot be scanned because the syntax of the specified JAR file is invalid. (JAR file = aa....aa, context root = bb....bb)

aa....aa: JAR file path

bb....bb: Context root name

Description

The static contents cannot be searched because the configuration of the specified JAR file is incorrect.

Action

Check whether the JAR file has been created correctly.

KDJE39551-W

Processing of a JAR file that includes static content failed. (JAR file = aa....aa, message = bb....bb)

aa....aa: JAR file path

bb....bb: Exception message

Description

An attempt to process a JAR file including static content failed.

Action

Check whether the JAR file has been created correctly.

KDJE39552-W

A aa....aa cannot be added because it is already registered. The aa....aa will be ignored. (aa....aa name = bb....bb, context root = cc....cc)

aa....aa: Servlet or filter

bb....bb: Servlet name or filter name

cc....cc: Context root name

Description

The servlet or filter cannot be added because it is already registered. This servlet or filter is ignored.

Action

Check whether the servlet or filter has already been registered with the same name.

KDJE39553-W

The specified JAR file, which contains a ServletContainerInitializer interface class, was not found in the list of include files. (file = aa....aa)

aa....aa: Absolute path of the JAR file name

Description

The JAR file for ServletContainerInitializer specified in the include file list was not found.

Action

Check whether the JAR file exists in the specified path. If the file does not exist, store the JAR file.

KDJE39554-W

The specified JAR file, which contains a ServletContainerInitializer interface class, was not found at the class path. (file = aa....aa)

aa....aa: Absolute path of the JAR file name

Description

The JAR file for ServletContainerInitializer specified in the include file list was not found in the class path.

Action

Check whether the JAR file exists in the class path.

KDJE39555-W

The url pattern contains the carriage return or line feed character. (J2EE application = aa....aa, context root = bb....bb, urlPattern = cc....cc)

aa....aa: J2EE application

bb....bb: Context root

cc....cc: Value specified for the URL pattern

Description

The value specified in the URL pattern for the dynamic servlet definition contains a linefeed code (CR(#xD), or LF(#xA)). The contents specified in the URL pattern cannot contain a linefeed code.

This definition is invalid.

The cc....cc contents display the value excluding the linefeed code.

Action

Correct the contents of the applicable URL pattern, and then re-deploy the application.

KDJE39556-W

This application contains a JAR file with static content in the META-INF/resources directory. The static content was not reloaded. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application

bb....bb: Context root

Description

When the application contains a JAR file with static contents (including JSP) in META-INF/resources, even if the JAR file is updated and reloaded, the static contents included in the META-INF/resources of the JAR file can only access the pre-update JAR file.

Action

To update the static contents in the META-INF/resources of the JAR file, first stop and then re-deploy the application.

KDJE39557-W

This application includes a class that implements the ServletContainerInitializer interface. The reload function is not supported for this application. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application

bb....bb: Context root

Description

The reload functionality is not supported for applications containing the implementation class of the ServletContainerInitializer interface. The J2EE server operations might not function normally if the applications are reloaded. Do not reload the applications.

Action

Stop and then restart the J2EE server.

Note

This message is not output with the version 09-00-02 or later.

KDJE39558-W

This application includes servlet, filter, or listener classes added by the program. The reload function is not supported for this application. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application

bb....bb: Context root

Description

The reload functionality is not supported for applications containing the Servlet, Filter, or Listener classes added by the dynamic servlet definition. The J2EE server operations might not function normally if the applications are reloaded. Do not reload the applications.

Action

Stop and then restart the J2EE server.

Note

This message is not output with the version 09-00-02 or later.

KDJE39559-W

An invalid character is used for configuring SessionCookieConfig. This configuration may cause improper behavior for session. (aa....aa = bb....bb)

aa....aa: Set item

bb....bb: Set value

Description

An invalid character is used in the SessionCookieConfig settings. These settings might cause invalid session operations.

Action

Use the correct characters for the applicable items.

KDJE39560-I

The property is not specified. The default value will be used. (property = aa....aa, default value = bb....bb)

aa....aa: Property name

bb....bb: Default value

Description

The property is not specified. The default value will be used.

Action

To change the aa....aa property from the default value, add the aa....aa property, specify the property value, and then stop or re-start the Web container server or the J2EE server.

KDJE39562-I

The nio http server started. (port = aa....aa)

aa....aa: Port number

Description

The nio http server will start.

KDJE39563-W

The host name specified in the property webserver.connector.nio_http.permitted.hosts could not be resolved. (host name = aa....aa)

aa....aa: Host name that cannot be resolved

Description

The host name specified in webserver.connector.nio_http.permitted.hosts cannot be resolved.

Allow access only from the local host, and then start.

Action

Make sure that the specified host name can be resolved, and then restart the server.

KDJE39564-W

Access to the nio http server from a forbidden host was rejected. (IP address = aa....aa)

aa....aa: IP address of the host that was denied access

Description

Access to the nio http server from a forbidden host was denied.

Action

To allow access from a forbidden host, specify the IP address or the host name of the host that is allowed access in the property webserver.connector.nio_http.permitted.hosts, and then restart the server.

KDJE39565-W

The host name specified in property webserver.connector.nio_http.bind_host could not be resolved. (host name = aa....aa)

aa....aa: Specified host name

Description

The host (aa....aa) specified in the property webserver.connector.nio_http.bind_host cannot be resolved.

The wild card address will be used.

Action

When using an address other than the wild card address, specify the resolvable local host name or the IP address of the local host, and then restart the server.

KDJE39566-E

The nio http server on port aa....aa could not be started.

aa....aa: Port number

Description

The nio http server cannot be started on the specified port number (aa....aa).

Action

Another process might be using the specified port number of the nio http server. Specify a port number that is not in use by another process, and then restart the server. The port number of the nio http server can be specified in the key webserver.connector.nio_http.port of the user property file.

If not specified in the user property file, use the port number 8008 as the default value.

KDJE39567-W

The host specified in property webserver.connector.nio_http.bind_host could not be bound. (host = aa....aa)

aa....aa: Specified host name

Description

The host (aa....aa) specified in the property webserver.connector.nio_http.bind_host cannot be resolved.

The wild card address will be used.

Action

A host other than the local host might be specified.

When using an address other than the wild card address, specify the correct host, and then restart the server.

KDJE39568-E

The request header is exceeds the max size. (request uri = aa....aa, max size of the request header = bb....bb)

aa....aa: Request URI

bb....bb: Maximum size of the request header

Description

The request header of the sent request has exceeded the maximum size. An error with status 400 will be returned to the client.

Action

Check if the set value of the key webserver.connector.nio_http.limit.max_request_header of the user property file is correct. If the set value is incorrect, change the maximum size of the request header to the correct value. When the maximum size of the request header is changed, you need to restart the J2EE server.

KDJE39569-E

The request body is exceeds the max size. (request uri = aa....aa, max size of the request body = bb....bb)

aa....aa: Request URL

bb....bb: Maximum size of the request body

Description

The request body of the sent request has exceeded the maximum size. If the transfer encoding for the sent request is not chunked, an error with status 413 will be returned to the client.

Action

Check if the set value of the key webserver.connector.nio_http.limit.max_request_body of the user property file is correct. If the set value is incorrect, change the maximum size of the request body to the correct value. When the maximum size of the request body is changed, you need to restart the J2EE server.

KDJE39570-E

The http header is exceeds the max number. (request uri = aa....aa, max number of the http header = bb....bb)

aa....aa: Request URI

bb....bb: Maximum number of HTTP headers

Description

The number of HTTP headers included in the sent request has exceeded the maximum number. An error with status 400 will be returned to the client.

Action

Check if the set value of the key webserver.connector.nio_http.limit.max_headers of the user property file is correct. If the set value is incorrect, change the maximum number of HTTP headers to the correct value. When the maximum number of HTTP headers is changed, you need to restart the J2EE server.

KDJE39571-W

The nio http server denies access to the URI starting with /ejb/ or /web/. (request URI = aa....aa)

aa....aa: Request URI

Description

The accessed request was denied.

A request starting with ""/ejb/"" or ""/web/"" cannot be used on the NIO HTTP server.

KDJE39572-E

An exception was raised during connecting with the client. (exception = aa....aa)

aa....aa: Exception information notified from Java VM in the case of failure in establishing a connection with the client

Description

An exception occurred while establishing a connection with the client. This might be due to the occurrence of a problem that does not allow continuance of an operation, such as lack of resources of the system in which the Web container is running.

If message KDJE39573-W is output after this message, and if the connection from the client is successful after the occurrence of the failure notified by this message, the system might recover.

Even if no other error log is output, the system might not recover from this failure when this message KDJE39573-W is not output.

Action

From the J2EE server log, such as the access log of the nio http server, make sure that the request is being executed properly. In the case when the Web container does not receive the request, or an error occurs during the communication with the Web container, the system resources, such as memory, file descriptor, or the TCP port might be insufficient. Check the usage status of the system resources, and then make sure whether the estimation of the system resources is correct. If resources are insufficient, change the system settings.

KDJE39573-W

The connecting with the client has succeeded.

Description

An attempt to establish a connection with the client was successful, although an exception occurred while establishing connection with the client. This message is output after the message KDJE39572-E, when a connection with the client is established successfully. Message KDJE39572-E is output when a connection with the client cannot be established due to insufficient system resources, such as memory, file descriptor, or the TCP port.

Action

From the J2EE server log, such as the access log of the nio http server, make sure that the request is being executed properly. If the request is not being executed properly, identify the cause of the error and take action on the basis of the action for the message KDJE39572-E.

KDJE39574-E

The request header is invalid. The nio http server refused the request. (request uri = aa....aa, bb....bb = cc....cc, client = dd....dd: ee....ee)

aa....aa: Request URI

bb....bb: Name of the invalid request header

cc....cc: Value of the invalid request header

dd....dd: IP address of the client to which you will connect (IP address of the reverse proxy, if reverse proxy is being used)

ee....ee: Port number of the client to which you will connect (port number of the reverse proxy, if reverse proxy is being used)

Description

The nio http server has denied the accessed request because an invalid request header was received.

Action

Make sure whether no problem exists in the Web client that has sent the invalid request, and avoid sending invalid request headers.

KDJE39575-W

The timeout occurred during terminating the web container. Some processing threads may still be running. (thread pool = aa....aa, time = bb....bb seconds)

aa....aa: Name of the thread pool in which the timeout occurred

bb....bb: Timeout period

Description

A timeout occurred during termination of the Web container. Some processing threads might be still running.

KDJE39576-E

The timeout occurred in reading the request data from the client. (client = aa....aa: bb....bb)

aa....aa: IP address of the client to which you will connect (IP address of the reverse proxy, if reverse proxy is being used)

bb....bb: Port number of the client to which you will connect (port number of the reverse proxy, if reverse proxy is being used)

Description

A timeout occurred during reading of a request from the client. Confirm the following details:

If the proxy server is not being used

Make sure that no Web client has sent invalid data to the J2EE client.

Make sure that no failure has occurred in the communication path.

If the proxy server is being used

Make sure that the reverse proxy is running properly.

Make sure that no failure has occurred in the communication path between the reverse proxy and the J2EE server.

Action

Take the following action for the confirmed details:

If a Web client has sent invalid messages, identify the client based on the address and port number indicated in the message, and then take action.

If there is a problem in the communication path, resolve the problem.

If the reverse proxy is not running properly, resolve the problem of the reverse proxy.

KDJE39900-I

The response compression function will be applied. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

Description

The response compression functionality will be applied.

KDJE39901-I

The response compression rule aa....aa will be applied to the response of a request which matches the URL pattern bb....bb. (J2EE application = cc....cc, context root = dd....dd, compression rule name = ee....ee)

aa....aa: Response compression rule

bb....bb: URL pattern

cc....cc: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

dd....dd: Context root name

ee....ee: Response compression rule name

Description

The response compression rule aa....aa will be applied to the request that matches the URL pattern bb....bb.

KDJE39902-E

The URL pattern of the initialization parameter of the filter used for the response compression function is invalid. (J2EE application = aa....aa, context root = bb....bb, init param = cc....cc, url pattern = dd....dd)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Initialization parameter name

dd....dd: Specified URL pattern

Description

The URL pattern specified in the initialization parameter of the filter used for the response compression functionality is invalid.

Action

Modify the URL pattern specified in the initialization parameter of the filter used for the response compression functionality of the Deployment Descriptor (web.xml), and then redeploy.

KDJE39903-E

The compression rule name of the initialization parameter of the filter used for the response compression function is invalid. (J2EE application = aa....aa, context root = bb....bb, init param = cc....cc, compression rule name = dd....dd)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Initialization parameter name

dd....dd: Specified response compression rule name

Description

The response compression rule name specified in the initialization parameter of the filter used for the response compression functionality is invalid.

Action

Modify the response compression rule name specified in the initialization parameter of the filter used for the response compression functionality of the Deployment Descriptor (web.xml), and then redeploy.

KDJE39904-E

The compression rule name of the initialization parameter of the filter used for the response compression function is not found. (J2EE application = aa....aa, context root = bb....bb, init param = cc....cc, compression rule name = dd....dd)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Initialization parameter name

dd....dd: Specified response compression rule name

Description

The response compression rule name specified in the initialization parameter of the filter used for the response compression functionality is not found.

Action

Set the response compression rule name specified in the initialization parameter of the filter used for the response compression functionality of the Deployment Descriptor (web.xml), and then redeploy.

KDJE39905-E

The compression rule of the initialization parameter of the filter used for the response compression function is invalid. (J2EE application = aa....aa, context root = bb....bb, init param = cc....cc)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Initialization parameter name

Description

The response compression rule specified in the initialization parameter of the filter used for the response compression functionality is invalid.

Action

Modify the response compression rule specified in the initialization parameter of the filter used for the response compression functionality of the Deployment Descriptor (web.xml), and then redeploy.

KDJE39906-E

The compression threshold of the initialization parameter of the filter used for the response compression function is invalid. (J2EE application = aa....aa, context root = bb....bb, init param = cc....cc, compression threshold = dd....dd)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Initialization parameter name

dd....dd: Specified compression threshold value

Description

The response compression threshold value specified in the initialization parameter of the filter used for the response compression functionality is invalid.

Action

Modify the compression threshold value specified in the initialization parameter of the filter used for the response compression functionality of the Deployment Descriptor (web.xml), and then redeploy.

KDJE39907-W

The same media type has been specified more than once in the initialization parameters of the filter used for the response compression function. The compression threshold specified last will be applied. (J2EE application = aa....aa, context root = bb....bb, init param = cc....cc, media type = dd....dd, compression threshold = ee....ee)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Initialization parameter name

dd....dd: Specified media type

ee....ee: Applied compression threshold value

Description

The same media type is specified more than once in the initialization parameters of the filter used for the response compression functionality. The compression threshold value specified last will be applied.

KDJE39908-E

The url-mapping of the initialization parameter of the filter used for the response compression function is invalid. (J2EE application = aa....aa, context root = bb....bb)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

Description

The value of the url-mapping parameter specified in the initialization parameter of the filter used for the response compression functionality is invalid.

Action

Modify the value of the url-mapping specified in the initialization parameter of the filter used for the response compression functionality of the Deployment Descriptor (web.xml)and then redeploy.

KDJE39909-E

An error occurred in acquisition of the buffer area for compression. (request URL = aa....aa)

aa....aa: Request URL

Description

An error occurred while buffer area for the response compression functionality was being secured.

Action

The memory might be insufficient. Secure the memory that can be used by the system, and then restart. The insufficient memory might be because of the compression threshold value specified in the initialization parameter of the filter used for the response compression functionality is too large.

KDJE39910-I

The response will be compressed. (request URL = aa....aa)

aa....aa: Request URL

Description

The response will be compressed.

KDJE39911-W

The response will not be compressed. (request URL = aa....aa)

aa....aa: Request URL

Description

The Media-Type specified in the response compression rule was set in the response, when data was being written in the buffer of the HTTP response using either ServletOutputStream acquired with the getOutputStream method, or PrintWriter acquired with the getWriter method of javax.servlet.ServletResponse. The response will not be compressed.

Action

When compressing the response, invoke the setContentType method when data is not being written in the buffer of the HTTP response, and then set the Media-Type specified in the response compression rule for the response.

KDJE39912-I

The default response compression rule aa....aa will be applied to all responses. (J2EE application = bb....bb, context root = cc....cc)

aa....aa: Default value

bb....bb: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

cc....cc: Context root name

Description

The default response compression rule aa....aa will be applied to all responses.

KDJE39913-E

The filter name of the filter for the response compression function is invalid. (J2EE application = aa....aa, context root = bb....bb, filter name = cc....cc)

aa....aa: The J2EE application name (in the case of the J2EE server mode) or a null character (in the case of the servlet engine mode)

bb....bb: Context root name

cc....cc: Specified filter name

Description

The filter name of the filter used for the response compression functionality is invalid.

Action

Modify the filter name specified in the filter name of the filter used for the response compression functionality of the Deployment Descriptor (web.xml), and then redeploy.

7.3 Messages from KDJE40000 to KDJE49999

This section explains the messages from KDJE40000 to KDJE49999 that the Cosminexus Component Container or Cosminexus TPBroker outputs.

KDJE40000-E

An old version's server having the same name has been set up. The migration should be performed using the cjenvupdate command.

Description

An old version's server having the same name is set up. Migrate the environment using the cjenvupdate command.

Action

Use the cjenvupdate command to migrate the environment.

KDJE40001-I

The setup for the J2EE server has finished successfully. Server name = aa....aa

aa....aa: Server name

Description

The setup for the J2EE server (aa....aa) has finished successfully.

KDJE40002-E

The J2EE server has not been set up. Server name = aa....aa

aa....aa: Server name

Description

The J2EE server (aa....aa) is not set up.

Action

Run the cjsetup command to set up the server.

KDJE40003-E

The setup for the J2EE server has failed. Server name = aa....aa, Reason = bb....bb

aa....aa: Server name

bb....bb: Error contents

Description

An attempt to setup the J2EE server (aa....aa) has failed.

Action

Take action based on the error details.

Already been set up

The J2EE server is set up with the specified server name. To set up the J2EE server again, delete the server once using the cjsetup -d server-name command, and then re-execute the set up command.

Invalid server name

Invalid server name is specified. Single-byte alphanumeric characters, underscores (_), and hyphens (-) can be used in the server name within the range estimated by referencing the manual uCosminexus Application Server System Setup and Operation Guide. The first character of the server name must be an alphanumeric character.

Not supported edition

Execute in an edition of Application Server and Developer that supports the batch server.

In the case of *****

Take action based on the message displayed just before the error.

KDJE40004-E

aa....aa is too long: bb....bb

aa....aa: Target type

bb....bb: Target name

Description

When the target type is path name, the path up to the target name or the path specified in the definition of the target name is too long.

Action

When the target type is path name and the target name is ejb.server.log.directory or web.server.log.directory, specify a path of length 200 bytes or less.

When the target type is path name and the target name is a name other than those mentioned above, specify a path of length less than the MAX_PATH length of the OS.

KDJE40005-W

The specified value is invalid. The sleep processing will be performed with the default value (10 seconds).

Description

The specified value is invalid. The sleep processing will be performed with the default value (10 seconds).

Action

If the default value (10 seconds) causes an error, specify the correct value.

KDJE40006-I

Usage: cjsleep sleepTime

Description

This message describes the usage method of the cjsleep command.

KDJE40007-E

The system setting files aa....aa were not found. There is a possibility that the files are not installed properly, were removed or have permission problems. Reason = bb....bb

aa....aa: Path name

bb....bb: Reason

Description

The system setting file was not found or an attempt to read the file has failed.

Action

Re-install the files or revise the permissions.

KDJE40008-E

The file could not be copied from "aa....aa" to "bb....bb" because of the reason cc....cc. Check the file status.

aa....aa: Copy source file name

bb....bb: Copy destination file name

cc....cc: Details

Description

An attempt to copy the file has failed.

Action

Based on the details, remove the cause of the error, and then re-execute the command.

KDJE40010-I

Processing will wait for aa....aa seconds.

aa....aa: Numeric value

Description

This is the sleeping time of the cjsleep command.

KDJE40011-I

Usage: cjstartsv [serverName] [-nosecurity] [-nostartapp]

Description

This message describes the usage method of the cjstartsv command.

KDJE40012-I

Usage: cjstopsv [serverName] [-f | -fd [ThreadDumpInterval ThreadDumpCount]] [-wait [waitTime]]

Description

This message describes the usage method of the cjstopsv command.

KDJE40013-I

Start Time: aa....aa

Server Name: bb....bb

Server Version: cc....cc(dd....dd)

Process ID:ee....ee

aa....aa: Start time

bb....bb: Server name

cc....cc: Version

dd....dd: Build date

ee....ee: Process ID

Description

The start time (aa....aa), server name (bb....bb), version (cc....cc), build date (dd....dd), and process ID (ee....ee) of the server is displayed.

KDJE40014-E

The specified value for the aa....aa option is invalid.

aa....aa: Option name

Description

The specified value for the option is invalid.

Action

See the manual uCosminexus Application Server Command Reference Guide.

KDJE40016-E

An error has occurred in the internal function. (aa....aa)(errno = bb....bb)

aa....aa: Function name

bb....bb: Detailed message

Description

An error occurred in the function (aa....aa).

Action

When a J2EE server is started, if this message outputs and the server stops, write permission might not be there in the log output destination directory. Revise the permissions for the log output destination directory. If the error cannot be resolved even after revising the permissions, contact maintenance personnel.

KDJE40017-E

A memory shortage occurred. (aa....aa)(errno = bb....bb)

aa....aa: Function name

bb....bb: Detailed message

Description

An attempt to secure memory in function (aa....aa) has failed.

Action

Increase the free memory, and then re-execute the command.

KDJE40018-E

aa....aa was not found. (errno = bb....bb)

aa....aa: Shared library name

bb....bb: Detailed message

Description

The shared library (aa....aa) was not found.

Action

Confirm that the shared library is installed.

KDJE40019-E

The library of Java(TM) VM cannot be loaded. (errno = aa....aa)

aa....aa: Details

Description

The library of Java VM cannot be read.

Action

Revise the access permissions of the shared library.

KDJE40020-W

An invalid value was specified for the jvm.type key of the usrconf.cfg. aa....aa will be used.

aa....aa: Java VM(Java HotSpot Server VM or Java HotSpot Client VM) used during server startup.

Description

The user-specified Java VM type was invalid, therefore, the searched and found aa....aa will be used to start the server.

Action

Specify the correct value in jvm.type of usrconf.cfg.

KDJE40021-E

Invalid Java(TM) VM.

Description

The version of Java is not the one presumed by Cosminexus Component Container.

Action

Confirm the Java version.

KDJE40022-E

Initialization error of Java(TM) VM.

Description

An attempt to initialize Java VM has failed.

Action

If Unrecognized VM option option-name message is displayed just before this message, revise the specified value of add.jvm.arg defined in usrconf.cfg of the server.

Note that the Unrecognized VM option message is output only in the standard error output.

If the Unrecognized VM option message is not output immediately before this message, contact maintenance personnel.

KDJE40023-E

An attempt to open aa....aa has failed. (errno = bb....bb)

aa....aa: File name

bb....bb: Detailed message

Description

An attempt to open the file (aa....aa) has failed.

Action

Confirm that the relevant file exists, and then check the access permissions.

KDJE40024-E

The directory cannot be accessed. (aa....aa)

aa....aa: Directory name

Description

The directory (aa....aa) does not exist or the write permission is not available.

Action

Confirm that the directory exists, and then check the access permissions.

KDJE40025-E

The current working directory of the process cannot be changed. (aa....aa)

aa....aa: Directory name

Description

The current working directory cannot be changed to aa....aa.

Action

Confirm that the directory exists, and then check the access permissions.

KDJE40026-I

The deletion of the J2EE server has completed successfully. Server name = aa....aa

aa....aa: Server name

Description

The deletion of the J2EE server (aa....aa) was completed successfully.

KDJE40027-I

Usage: cjsetup [-d serverName | serverName [-compat setupVersionID] | -batch serverName]

Description

This message describes the usage method of the cjsetup command.

KDJE40028-E

The deletion of the J2EE server has failed. Server name = aa....aa, Reason = bb....bb

aa....aa: Server name

bb....bb: Error contents

Description

An attempt to unset up the J2EE server (aa....aa) has failed.

Action

Take action based on the error details.

Server is not found

A non-existing server name is specified.

Deletion of file failed

The file cannot be deleted. Confirm that the file to be deleted is not being accessed or is not a read-only file.

Invalid server name

Invalid server name is specified. Single-byte alphanumeric characters, underscores (_), and hyphens (-) can be used in the server name within the range estimated by referencing the manual uCosminexus Application Server System Setup and Operation Guide. The first character of the server name must be an alphanumeric character.

*****

Take the following actions based on the previously displayed message ID:

In case of KDJE40016-E

Contact the maintenance personnel.

In case of KDJE40035-E

The J2EE server is running.

Stop the J2EE server, and then re-execute the unset up command.

KDJE40029-E

The directory aa....aa was not found.

aa....aa: Directory name

Description

The directory (aa....aa) was not found.

Action

Confirm that the Cosminexus Component Container is installed properly.

KDJE40030-I

Usage: cjdumpsv [serverName]

Description

This message describes the usage method of the cjdumpsv command.

KDJE40031-E

The aa....aa server was not found.

aa....aa: Server type (J2EE: J2EE server or Web container: WEB Container server)

Description

The J2EE server or the Web Container server was not found.

Action

Confirm that the server is running, and then re-execute the command.

KDJE40032-E

The policy file cannot be accessed: aa....aa

aa....aa: Policy file name that cannot be accessed

Description

The policy file (aa....aa) cannot be accessed.

Action

Confirm that the relevant policy file exists, and then check the access permissions.

KDJE40033-E

A timeout has occurred during waiting for the response of the shutdown request from the J2EE server.

Description

There was no response to the shutdown request from the J2EE server.

Action

See the log of the J2EE server, and then resolve the cause of the error.

KDJE40034-E

An error has occurred in the J2EE server.

Description

An error occurred in the J2EE server that had received the shutdown request.

Action

See the log of the J2EE server, and then resolve the cause of the error.

KDJE40035-E

The J2EE server has already been started.

Description

The start request was cancelled because the J2EE server is already running.

Action

Confirm that the J2EE server is running.

When the running J2EE server is started properly, use that server as it is.

When the server is not started properly, restart the server if required.

KDJE40036-E

The J2EE server could not be shutdown. Reason = aa....aa

aa....aa: Details

Description

The J2EE server cannot be shutdown due to the reason described in the details (aa....aa).

Action

Take the following actions based on the details:

The server shutdown is in progress.

The J2EE server shutdown is in progress. Wait until the server shuts down.

Permission denied.

When the J2EE server is started from the Management Server, stop the J2EE server from the Management Server. When the Management Server is not started from the J2EE server, contact the maintenance personnel.

In cases other than above

Contact the maintenance personnel.

KDJE40037-E

The definition file cannot be accessed: aa....aa

aa....aa: The definition file name that cannot be accessed

Description

The definition file (aa....aa) cannot be accessed.

Action

Confirm that the relevant definition file exists, and then check the access permissions.

In the case of the batch execution command and the batch forced termination command, also check the following:

When the environment variable CJBATCHUSRCONFDIR for the directory, that stores the user definition file, is specified, make sure that the total value of the length of the specified path and the length of the user property file name (usrconf.properties) is lesser than the maximum path length stipulated in the operating system.

When the environment variable CJBATCHUSRCONFDIR for the directory, that stores the user definition, file is not specified, make sure that the length of the absolute path of the user option definition file (usrconf.cfg) or the user property file (usrconf.properties) that exists in the current directory is lesser than the maximum path length stipulated in the operating system.

KDJE40038-W

An invalid value was specified for aa....aa. The default value bb....bb will be used. (cc....cc = dd....dd)

aa....aa: Specified item (property or option)

bb....bb: Property or default value of the command option

cc....cc: Specification destination

Property key: Property key name

Option name: Command option name

dd....dd: Property key name or command option name

Description

An invalid value was specified for the property or command option, therefore, the processing continues with the default value.

Action

When the specified item is property, revise the specified value of the property (dd....dd) of the usrconf.cfg file.

When the specified item is option, revise the specified value of the option (dd....dd) of the command.

KDJE40039-I

Usage: cjenvsetup

Description

This message describes the usage method of the cjenvsetup command.

KDJE40040-I

The setup for the Cosminexus Component Container administrator has finished successfully.

Description

The setup for the Cosminexus Component Container administrator has finished successfully.

KDJE40041-E

The setup for the Cosminexus Component Container administrator has failed. Error = aa....aa (detail = bb....bb)

aa....aa: Error contents

bb....bb: Detail (file name or directory name)

Description

An attempt to setup the Cosminexus Component Container administrator has failed.

Action

Take action based on the error details.

Invalid installation directory

The Cosminexus Component Container might not be installed properly. Install the Cosminexus Component Container, and then perform the set up process again.

Renaming or deleting the output files failed

The output file of the cjenvsetup command is being used, and therefore the execution information cannot be saved successfully. Check that the file shown in the detail is not being used.

In cases other than above

Execute the cjenvsetup command after some time. If the error occurs again, contact the maintenance personnel.

KDJE40042-E

Only the Cosminexus Component Container administrator is permitted to execute this command.

Description

Only the Cosminexus Component Container administrator can execute this command.

Action

The Cosminexus Component Container administrator must execute this command. Make sure that the property (owner or group) of the installation directory (the link destination directory when /opt/Cosminexus/CC is linked symbolically) matches the Cosminexus Component Container Administrator and the primary group of the Cosminexus Component Container Administrator. If not, match the property.

KDJE40043-W

The library of HNTRLib2 cannot be loaded. (errno = aa....aa)

aa....aa: Details

Description

The Hitachi Trace Common Library cannot be read.

The command processing continues without acquiring the trace.

Action

Confirm that the Hitachi Trace Common Library is installed.

KDJE40044-E

The value specified for the environment variable is invalid. Environment variable name = aa....aa, Value = bb....bb

aa....aa: Environment variable name

bb....bb: Set value of the environment variable

Description

The value specified for the environment variable is invalid.

Action

When the environment variable name is CSCCFJ_SERVER_HOME, confirm that the installation directory of the Component Container is correct.

When the environment variable name is other than the name mentioned above, contact the maintenance personnel.

KDJE40045-I

Usage: cjgetsysinfo [-f SystemInformationOutputFile]

Description

This message describes the usage method of the cjgetsysinfo.

KDJE40046-E

The specified file aa....aa already exists. Specify another file.

aa....aa: Operation status output file path

Description

The specified file already exists.

Action

Specify another file, and then re-execute the command.

KDJE40047-E

An attempt to aa....aa a core file has failed. Core file name = bb....bb

aa....aa: Process contents

rename: Failed to rename.

delete: Failed to delete.

bb....bb: The name of the core file that cannot be renamed or deleted

Description

An attempt to rename or delete the core file has failed.

Action

Take action based on the process contents (aa....aa).

rename

The core file will be overwritten and deleted during next server shutdown. Save the core file by renaming it.

delete

Delete the core file.

KDJE40048-I

Specified option(s) = aa....aa

aa....aa: Specified option list

Description

The options specified for cjstartsv are displayed in aa....aa.

When the option is not specified, none is output.

KDJE40049-E

A timeout occurred in cjstopsv during normal stop monitor. Server name = aa....aa

aa....aa: The J2EE server name

Description

A timeout occurred during normal termination monitoring.

Action

Specify the forced termination option, and then re-execute the cjstopsv command.

KDJE40050-E

A timeout occurred in cjstopsv during normal stop monitor. The J2EE server will now be forcibly stopped. Server name = aa....aa

aa....aa: The J2EE server name

Description

A timeout occurred while monitoring the normal termination. The J2EE server will be forcibly stopped.

Action

No action is required.

KDJE40051-W

An invalid value was specified for the property. The default value aa....aa will be used. (property name = bb....bb)

aa....aa: Default value

bb....bb: Property name

Description

An invalid value was specified in the property. The default value will be used.

Action

Reset the property value, if necessary.

KDJE40052-E

The directory aa....aa cannot be accessed. Processing will now stop.

aa....aa: Directory name

Description

One of the following problems might have occurred:

The permission is not available to access the directory.

A file name is specified for the directory.

Exclusive processing of the following log files has failed:

- Operation log of the cjclstartap command

- Startup process standard output information

- Startup process standard error information

Action

Check the status of the directory aa....aa.

When concurrently starting multiple cjclstartap commands in subdirectory shared mode, if the KDJE40016-E (errno is 22), KDJE30043-E, or KDJE40052-E message is output to the standard error output, exclusive processing of the preceding log files might have failed during initialization. In this case, use ejb.client.log.lockRetryCount and ejb.client.log.lockInterval to increase the total retry count, retry interval, and timeout period for lock acquisition.

KDJE40053-I

The cjclstartap command will now start. (directory for the user definition file = aa....aa, PID = bb....bb)

aa....aa: Environment variable settings for storing the user definition file

bb....bb: Process ID

Description

The cjclstartap command will now start using the user definition of aa....aa directory.

KDJE40054-I

The cjclstartap command stopped. (PID = aa....aa, exit status = bb....bb)

aa....aa: Process ID

bb....bb: Exit status of the Java application

Description

The cjclstartap command was stopped.

KDJE40055-I

Usage: cjclstartap [Java option ...] class [args ...]

Description

This message describes the usage method of the cjclstartap command.

KDJE40056-E

An invalid value was specified for aa....aa. (bb....bb = cc....cc)

aa....aa: Specified item (either property or option)

bb....bb: Specification destination of the invalid value (either one of the Property keys (property key name) or Option name (command option name)

cc....cc: Property key name or command option name for which an invalid value is specified

Description

This process will be terminated because the values specified in the property or command options are invalid.

Action

When the specified item is property, revise the specified value of the property (cc....cc) of the usrconf.cfg file.

When the specified item is option, revise the specified value of the option (cc....cc) of the command.

KDJE40057-E

The cjclstartap process cannot be found. (PID = aa....aa)

aa....aa: Process ID

Description

The cjclstartap command corresponding to the process ID specified in the argument is not found.

Action

Check the process ID of the cjclstartap command. Use the verified process ID to re-execute the cjcldumpap command.

KDJE40058-I

Usage: cjcldumpap [PID]

Description

This message describes the usage method of the cjcldumpap command.

KDJE40059-W

The length of the directory name specified for the ejb.client.log.directory exceeds 180 bytes. The default value aa....aa will be used.

aa....aa: Default directory name

Description

The length of the directory name specified for ejb.client.log.directory exceeds 180 bytes. The default value (aa....aa) will be used.

Action

Revise the value of ejb.client.log.directory.

KDJE40060-E

Another process is now running in the same current directory. (directory = aa....aa)

aa....aa: Current directory of the cjclstartap command

Description

Cannot start up because another cjclstartap command is running in the same current directory.

Action

After the running cjclstartap command finishes, re-execute the command.

KDJE40061-E

The log directory is being used by another process. (directory = aa....aa)

aa....aa: Log output destination directory

Description

Cannot start up because another cjclstartap command is using the log output destination directory.

Action

Specify a different log output destination directory for each application.

KDJE40062-E

An error has occurred in the system call(name = aa....aa,errno = bb....bb,line = cc....cc,at = dd....dd).

aa....aa: System call name

bb....bb: Error code

cc....cc: Number of lines

dd....dd: Functionality in which an error has occurred

Description

aa....aa detected the error bb....bb in dd....dd.

Action

Contact the maintenance personnel.

KDJE40063-E

The cjclstartap command has not started, or has not been executed in the same current directory.

Description

The execution of the command will be terminated because the cjclstartap command is not executed in the same current directory.

Action

Make sure that the cjclstartap command is running, and then re-execute the command in the same current directory as the cjclstartap command.

KDJE40064-E

The command cannot be executed because you do not have administrator privileges.

Description

The command cannot be executed because you do not have administrator privileges.

Action

Re-execute the command on a command prompt, as an administrator.

KDJE40065-E

An error occurred while the permissions were being checked.

Description

An error occurred while the permissions were being checked.

Action

The memory might be insufficient. Increase the free memory, and then re-execute the command. If the problem is not resolved, contact the maintenance personnel.

KDJE40066-W

An attempt to initialize the audit log has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to initialize the audit log has failed. The audit log cannot be output, but the processing continues.

Action

See the message log of the audit log to remove the cause of the error.

KDJE40067-W

An attempt to output the audit log has failed. (aa....aa)(details = bb....bb, errno = cc....cc)

aa....aa: Audit log type

bb....bb: Details

cc....cc: Error code

Description

An attempt to output the audit log has failed. The processing continues.

Action

See the message log of the audit log to remove the cause of the error. If the problem is not resolved, contact maintenance personnel.

KDJE40068-W

A memory shortage occurred. (details = aa....aa, errno = bb....bb)

aa....aa: Details

bb....bb: Error code

Description

An attempt to allocate memory has failed. The audit log cannot be output, but the processing continues.

Action

Increase the size of the free memory.

KDJE40069-W

The library cannot be loaded. (path = aa....aa).

aa....aa: Path name (absolute path)

Description

The library could not be read. The processing continues.

Action

Make sure that the library exists in the path.

KDJE40070-W

An error has occurred in the system call. (name = aa....aa, details = bb....bb, errno = cc....cc).

aa....aa: System call name

bb....bb: Detailed message

cc....cc: Error code

Description

aa....aa detected the error cc....cc. The processing continues.

Action

Contact the maintenance personnel.

KDJE40074-I

Setup of the Cosminexus Component Container administrator started. (installation directory = aa....aa, UID = bb....bb, GID = cc....cc)

aa....aa: Installation directory

bb....bb: User ID

cc....cc: Group ID

Description

The setup of the Cosminexus Component Container administrator has started.

KDJE40075-E

The value specified in "-compat" option is invalid. (specifiable value = aa....aa)

aa....aa: Specifiable setup version identifier

Description

A setup version identifier outside the specifiable range is specified for the -compat option.

The command execution will be interrupted.

Action

Revise the command parameters, and then re-execute the command.

KDJE40076-E

An error has occurred during exporting the version information file.

Description

An error related to output of the version information file occurred.

Action

Take action according to the message output immediately before this message.

KDJE40077-E

The version information file is invalid.

Description

An attempt to output the version information file failed.

Action

The version information file is invalid. Run the J2EE server deletion command, and then re-construct the J2EE server. If the problem is not resolved, contact maintenance personnel.

KDJE41000-E

An attempt to connect to the web container has failed. (errno = aa....aa, addr = bb....bb, port = cc....cc, fds = dd....dd)

aa....aa: System-specific error number

bb....bb: IP address of the host on which the Web container (used in the communication with the Web server) is running

cc....cc: Port number of the Web container used in the communication with the Web server

dd....dd: File descriptor of the Web container used in the communication with the Web server

Description

An attempt to connect to the web container has failed.

Action

One of the following problems occurred.

Port number of the worker is invalid.

Host name or IP address of the worker is invalid.

The maximum value of the Listen queue of the Web container is exceeded.

Host on which the Web container is running is down.

A failure occurred in the communication route between the redirector and Web container.

The Web server has stopped.

Remove the cause based on the system-specific error number.

If KDJE41033-I message is displayed after this message, retry connecting to the Web container.

KDJE41001-E

Redirection to the worker failed. (worker name = aa....aa)

aa....aa: Worker name

Description

A failure occurred in the communication with the worker (aa....aa).

Action

The Web server might be stopped. Take action based on the message (KDJE41000-E and so on) displayed just before this message.

KDJE41002-E

The request could not be redirected to a worker. Because the redirector could not access the definition file. (definition file = aa....aa)

aa....aa: File name

Description

The request cannot be redirected to a worker because the redirector cannot access the definition file (aa....aa).

Action

Confirm that the relevant file exists, check the access permissions, and then restart the Web server.

KDJE41003-W

An invalid parameter value is specified in aa....aa file. The default parameter value will be used. (bb....bb = cc....cc, default value = dd....dd)

aa....aa: File name

bb....bb: Parameter name

cc....cc: Value

dd....dd: Default value

Description

The value specified in parameter (bb....bb) is invalid. The default value (dd....dd) will be used.

Action

When changing the default value of the parameter bb....bb of the file aa....aa, specify an appropriate value in the parameter bb....bb, and then restart the Web server.

KDJE41004-E

The request could not be redirected to a worker because request header was too long.

Description

The redirector cannot redirect the HTTP request to a worker because the request header was too long.

The reason might be because of the GET method was used instead of the POST method in those places where the POST method of HTTP was required.

Action

Remove the cause due to which the size of the HTTP request header information is too long and access again.

KDJE41005-E

The request could not be redirected to a worker because worker name which is specified in the mapping definition file was not defined to worker.list parameter in the workers definition file. (worker name = aa....aa)

aa....aa: Worker name

Description

The request cannot be redirected to a worker because the worker name, specified in the mapping definition file, was not defined in worker.list parameter of the worker definition file.

Action

Define the worker name (aa....aa) specified in the mapping definition file (default name: uriworkermap.properties) or the Redirector Operation definition file for Cosminexus HTTP Server (default name: mod_jk.conf) in the worker.list parameter of the worker definition file (default name: workers.properties), and then restart the Web server. Note that this message is output even when an invalid value is specified in the worker.list parameter. Check the value specified in the worker.list parameter.

KDJE41006-E

The request could not be redirected to a worker because a required parameter was not specified in the workers definition file. (parameter = worker.aa....aa.bb....bb)

aa....aa: Worker name

bb....bb: Parameter name

Description

The request cannot be redirected to a worker because a mandatory parameter (worker.aa....aa.bb....bb) was not specified in the workers definition file.

Action

Specify the parameter worker.aa....aa.bb....bb in the workers definition file (default name: workers.properties), and then restart the Web server.

KDJE41007-E

The request could not be redirected to a worker because invalid value was specified in the workers definition file. (worker.aa....aa.bb....bb = cc....cc)

aa....aa: Worker name

bb....bb: Parameter name

cc....cc: Value

Description

The redirector cannot redirect the request to a worker because invalid parameter value (worker.aa....aa.bb....bb) was specified in the workers definition file.

Action

Specify an appropriate value in the parameter (worker.aa....aa.bb....bb) of the workers definition file (default name: workers.properties), and then restart the Web server.

KDJE41008-W

An invalid parameter value is specified in the workers definition file. The default parameter value will be used. (worker.aa....aa.bb....bb = cc....cc, default value = dd....dd)

aa....aa: Worker name

bb....bb: Parameter name

cc....cc: Value

dd....dd: Default value

Description

An invalid parameter (worker.aa....aa.bb....bb) value is specified in the workers definition file. The default value (cc....cc) will be used.

Action

When changing the default value of the parameter (worker.aa....aa.bb....bb) of the workers definition file (default name: workers.properties), specify an appropriate value in the worker.aa....aa.bb....bb parameter, and then restart the Web server.

KDJE41009-E

Could not create worker because it is out of memory.

Description

The worker cannot be created because the memory was insufficient.

The cause of the error could be that the value specified in the parameter (worker.worker-name.cachesize) of the workers definition file might be too large.

The value of worker.worker-name.cachesize consumes the memory as per the following formula:

Memory-usage = (value-of-worker.worker-name.cachesize) x 10 kilobytes

Action

Secure the memory available to the system, and then restart the Web server.

KDJE41010-E

An attempt to connect to a web client has failed. (errno = aa....aa)

aa....aa: System-specific error number

Description

An attempt to connect to the client that has made a request has failed.

The request processing might have been interrupted in the browser, or an update might have been requested, or else, the client that made the request might have stopped during the communication. The data might not have been received while receiving requests from the client, and a timeout might have occurred.

Action

Remove the cause based on the system-specific error number (definition value of errno.h in UNIX, return value of the GetLastError method in Windows).

If this message is output as a result of a browser operation (interruption or update), no action is required.

If this message occurred because of a timeout, check the cause of the timeout, and revise the specified value of the time as required.

KDJE41012-E

A URI pattern that does not start with '/' was specified in the aa....aa file. This parameter is ignored. (URI pattern = bb....bb, worker name = cc....cc)

aa....aa: File name

bb....bb: uri pattern

cc....cc: Worker name

Description

An uri pattern specified in the definition file (aa....aa) must start with /. The parameter definition will be ignored.

Action

To enable the specified uri pattern and the worker name, prepend / to the uri pattern (bb....bb) of the worker name (cc....cc) specified in file (aa....aa), and then restart the Web server.

KDJE41015-I

The redirector redirected the request to the worker. (worker name = aa....aa, request URI = bb....bb, addr = cc....cc, port = dd....dd, fds = ee....ee)

aa....aa: Worker name

bb....bb: Request URI

cc....cc: IP address of the host on which the Web container (used in the communication with the Web server) is running

dd....dd: Port number of the Web container used in the communication with the Web server

ee....ee: File descriptor of the Web container used in the communication with the Web server

Description

The redirector redirected the request to the worker (aa....aa).

KDJE41016-E

The request could not be redirected because it is out of memory.

Description

The request cannot be redirected because memory was insufficient.

Action

Secure the memory available to the system, and then restart the Web server.

KDJE41017-E

The accessed request was refused. The request URI which starts with "/hitachi_ccfj/" cannot be used. (request URI = aa....aa)

aa....aa: Request URI

Description

The accessed request was denied. The request URI which starts with /hitachi_ccfj/ cannot be used.

An invalid request URI was received or the redirector was registered in duplicate in the Web server.

Action

When the request URI from the client differs from the request URI indicated in aa....aa, start the Internet Service Manager from the Internet Information Services displayed in the tree, choose * host-name. In the * host-name, right click the Default Web site to choose Properties.

Choose the ISAPI filter tag and confirm that the hitachi_ccfj is not registered.

KDJE41018-E

The request could not be redirected because the web server was not configured correctly.

Description

The redirector cannot redirect the request because the web server was not configured correctly.

The reason might be because of the internal information of the redirector is conflicting with the other registered ISAPI filters.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE41019-E

The response timeout happen to worker aa....aa. (uri = bb....bb, addr =cc....cc, port = dd....dd, fds = ee....ee, RootAp = ff....ff)

aa....aa: Worker name

bb....bb: Request URI

cc....cc: IP address of the host on which the Web container (used in the communication with the Web server) is running

dd....dd: Port number of the Web container used in the communication with the Web server

ee....ee: File descriptor of the Web container used in the communication with the Web server

ff....ff: Root AP information of PRF

Description

A timeout occurred while receiving the response from the worker.

Action

One of the following problems occurred. Take action against the cause of the corresponding problem.

For details on how to take the action, see 6.5.2 Troubleshooting when a response is delayed in the uCosminexus Application Server Maintenance and Migration Guide.

Response is not returned due to the infinite loop in the processing of servlets or JSPs.

Deadlock occurred in the Web application.

The server processing lags behind during the peak access time.

Host on which the Web container is running is down.

A failure occurred in the communication route between the redirector and the Web container.

KDJE41020-E

An error occurred in the aa....aa function. (bb....bb)

aa....aa: Function name

bb....bb: Error information

Cause

An unexpected error occurred.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE41021-I

The creating of error page is delegated to web server. (error status code = aa....aa, uri = bb....bb)

aa....aa: Error status code

bb....bb: Request URI

Description

The creation of the error page is delegated to the Web server.

KDJE41022-W

The performance trace is unavailable due to failure of initialization. (reason = aa....aa)

aa....aa: Reason code

Description

The PRF trace cannot be used due to failure in initialization.

Action

Take action based on the reason described in aa....aa. The following codes are displayed in aa....aa.

Table 7‒5: List of failure reason codes displayed in KDJE41022-W

Reason code

Cause

Action

-1

Either the environment variable PRFSPOOL is not set, or the directory set in the environment variable PRFSPOOL does not exist.

Confirm that the environment variable PRFSPOOL is set.

-2

An error occurred in the service start processing of the PRF demon present in the process.

The PRF demon might not be invoked.

Confirm that the PRF demon is invoked. Also, check the PRFID of the definition file.

-3

An error (such as system call error) occurred in the service start processing of the PRF demon present in the process.

See the log file present below setup-directory-of-environment-variable-PRFSPOOL\log\PRF-identifier (in Windows) or $PRFSPOOL/log/PRF-identifier (in UNIX), check the Cosminexus Performance Tracer message, and then take action based on the cause.

-4

An attempt to load the library required for the service of PRF demon has failed.

Cosminexus Performance Tracer is not installed. Reload the library after installing the Cosminexus Performance Tracer.

KDJE41023-E

The request header is invalid. An attempt to redirect a request has failed. (header name = aa....aa, header value = bb....bb)

aa....aa: Header name

bb....bb: Contents

Description

An HTTP request header is invalid. An attempt to redirect a request has failed.

Action

Remove the cause due to which the HTTP request header information is invalid from the client that has made a request and access again.

KDJE41024-E

The redirector is unavailable because the invalid value is specified in aa....aa file. (parameter = bb....bb, value = cc....cc)

aa....aa: File name

bb....bb: Parameter name

cc....cc: Value

Description

The redirector is unavailable because the invalid value (cc....cc) of the parameter (bb....bb) is specified in the file (aa....aa).

Action

Specify an appropriate value in the parameter of the file, and then restart the Web server.

KDJE41025-E

The redirector is unavailable because the required parameter is not specified in aa....aa file. (parameter = bb....bb)

aa....aa: File name

bb....bb: Parameter name

Description

The redirector is unavailable because the mandatory parameter is not specified in the file (aa....aa).

Action

Specify an appropriate value in the parameter of the file, and then restart the Web server.

KDJE41026-W

The trace log is not outputted because the specified trace log file cannot be accessed. (trace log file = aa....aa, api = bb....bb, reason = cc....cc, code = dd....dd)

aa....aa: Output destination

bb....bb: Maintenance information

cc....cc: Maintenance information

dd....dd: Maintenance information

Description

The maintenance trace log is not output because the output destination (aa....aa) of trace log for maintenance cannot be accessed.

Action

Check the output destination directory, access permissions of the file, and free disk space. Remove the cause due to which the log cannot be output, and then restart the Web server.

KDJE41027-E

The redirector is unavailable because the specified trace log file is being used as a message log file. (trace log file = aa....aa)

aa....aa: Output destination

Description

The redirector is unavailable because the output destination (aa....aa) of the maintenance trace log is already used as the output destination of the message log.

Action

Change the contents of the output destination, and then restart the Web server.

KDJE41028-W

The specified parameter is invalid. Delete the entry or make it comment. (parameter = aa....aa)

aa....aa: Parameter name

Description

The description contents are ignored since the specified parameter is invalid.

Action

Delete the description of the parameter or comment it, and then restart the Web server.

KDJE41029-I

The initialization of the trace log will now start. (trace log file = aa....aa)

aa....aa: Output destination of maintenance trace log

Description

The initialization of the maintenance trace log will start.

KDJE41030-I

The initialization of the trace log has finished.

Description

The initialization of the maintenance trace log has finished.

KDJE41031-W

The timeout occurred in connecting to the worker. (worker name = aa....aa, URI = bb....bb, addr = cc....cc, port = dd....dd, fds = ee....ee, RootAP = ff....ff)

aa....aa: Worker name

bb....bb: Request URI

cc....cc: IP address of the host on which the Web container (used in the communication with the Web server) is running

dd....dd: Port number of the Web container used in the communication with the Web server

ee....ee: File descriptor of the Web container used in the communication with the Web server

ff....ff: Root AP information of PRF

Description

A timeout occurred while establishing the connection with the worker.

Action

One of the following problems occurred.

Host on which the Web container is running is down.

A failure occurred in the communication route between the redirector and Web container.

If KDJE41033-I message is displayed after this message, retry connecting to the Web container.

KDJE41032-W

The timeout occurred in sending the request data to the worker. (worker name = aa....aa, URI = bb....bb, addr = cc....cc, port = dd....dd, fds = ee....ee, RootAP = ff....ff)

aa....aa: Worker name

bb....bb: Request URI

cc....cc: IP address of the host on which the Web container (used in the communication with the Web server) is running

dd....dd: Port number of the Web container used in the communication with the Web server

ee....ee: File descriptor of the Web container used in the communication with the Web server

ff....ff: Root AP information of PRF

Description

A timeout occurred in sending the request data to the worker.

Action

One of the following problems occurred.

Host on which the Web container is running is down.

A failure occurred in the communication route between the redirector and Web container.

If KDJE41033-I message is displayed after this message, retry connecting to the Web container.

KDJE41033-I

The request sending will retry.

Description

Retry will be performed because an attempt to send a request to the worker, based on the cause described in the message output before this message, has failed.

KDJE41034-I

An attempt to send the request was successful while retrying. (retry count = aa....aa, maximum retry count = bb....bb)

aa....aa: Count of retry count when the requests were successfully sent

bb....bb: Maximum retry count

Description

An attempt to send the request was successful while retrying.

KDJE41035-E

Retry could not continue because an error occurred. (retry count = aa....aa, maximum retry count = bb....bb)

aa....aa: Count of retry when retry cannot be continued due to an error

bb....bb: Maximum retry count

Description

Retry cannot continue when retrying to send a request to the Web container because an error occurred.

Action

Take action based on the message that describes the cause of the failure to send the requests, output before this message.

KDJE41036-E

It did retry for the maximum retry count, but the request could not be sent. (maximum retry count = aa....aa)

aa....aa: Maximum retry count

Description

An attempt was made to retry sending the requests for the maximum retry count but the requests cannot be sent.

Action

Take action based on the message that describes the cause of the failure to send the requests, output before this message.

KDJE41037-I

The redirector will redirect the POST requests that have the Content-Length header, to the worker defined in the worker.<post_size_lb worker name>.post_size_workers parameter in the worker definition file. (post_size_lb worker name = aa....aa, destination worker name = bb....bb, length = cc....cc-dd....dd)

aa....aa: Worker name of the POST request distribution worker

bb....bb: Worker name of the POST request transfer destination worker

cc....cc: Minimum value of the Content-Length header

dd....dd: Maximum value of the Content-Length header

Description

Using the distribution functionality based on the POST data size, transfer the POST requests with the Content-Length header value more than cc....cc and lesser than dd....dd to the worker bb....bb specified in the parameter worker.worker-name-of-the-POST-request-distribution-worker.post_size_workers of the worker definition file.

KDJE41038-I

The redirector will redirect, to the default worker, the requests that do not satisfy the conditions for redirecting to the worker defined in the worker.<post_size_lb worker name>.post_size_workers parameter in the worker definition file. (post_size_lb worker name = aa....aa, default worker name = bb....bb)

aa....aa: Worker name of the POST request distribution worker

bb....bb: Worker name of the default worker

Description

Using the distribution functionality based on the POST data size, transfer the requests that do not satisfy the conditions for distribution to the worker specified in the parameter worker.worker-name-of-the-POST-request-distribution-worker.post_size_workers of the worker definition file to the default worker bb....bb.

KDJE41039-E

The redirector cannot be used because an invalid worker type is specified in the worker definition file. (worker.aa....aa.type = bb....bb)

aa....aa: Worker name

bb....bb: Value

Description

The redirector cannot be used because the type of the worker specified in the worker definition file is invalid. The type of the worker specified as the request transfer destination in the POST request distribution worker is either ajp13 or ajp12.

Action

Specify an appropriate value in the parameter (worker.worker-name.type) of the workers definition file (default name: workers.properties), and then restart the Web server.

KDJE41040-E

The redirector cannot be used because the value specified for the worker.<worker-name>.post_data parameter in the worker definition file has already been defined for another worker. (worker.aa....aa.post_data = bb....bb, other worker = cc....cc)

aa....aa: Worker name of the worker, the value of which is duplicated

bb....bb: Value

cc....cc: Worker name

Description

The redirector cannot be used because the value obtained by adding 1 to the upper-limit value of the Content-Length header of the worker aa....aa specified in the worker definition file is same as the value specified in another worker cc....cc.

Action

Specify the appropriate value in the parameter worker.worker-name.post_data (the worker name is aa....aa) of the worker definition file, and then restart the Web server.

KDJE41041-W

The specified parameter is invalid. (parameter name = aa....aa, value = bb....bb)

aa....aa: Parameter name

bb....bb: Value

Description

The value of the specified parameter is invalid.

If the URL pattern setup during sorting of requests by URL pattern is invalid, urlpattern will be output in aa....aa, and the specified URL pattern will be output in bb....bb.

Action

Specify the appropriate value in the parameter, and then restart the Web server.

KDJE41800-I

The setup for the Web container server has finished successfully. Server name = aa....aa

aa....aa: Server name

Description

The setup for the Web container server (aa....aa) has finished successfully.

KDJE41801-E

The Web container directory aa....aa corresponding to the server name does not exist.

aa....aa: Server name

Description

The directory corresponding to the server name specified by the cjstartweb command and the cjstopweb command does not exist.

Action

Confirm that the server name is entered correctly by the cjstartweb command and the cjstopweb command. When the cjwebsetup command is not executed by the specified server name, set up the server using the cjwebsetup command.

KDJE41802-E

The setup for the Web container server has failed. Server name = aa....aa, Reason = bb....bb

aa....aa: Server name

bb....bb: Error contents

Description

An attempt to setup the Web container server (aa....aa) has failed.

Action

Take action based on the error details.

Already been set up

The Web container server has been set up with the specified server name. To set up the Web container server again, use the cjwebsetup -d server-name command to delete the server once, and then re-execute the set up command.

Invalid server name

Invalid server name is specified. Single-byte alphanumeric characters, underscores (_), and hyphens (-) can be used in the server name within the range estimated by referencing the manual uCosminexus Application Server System Setup and Operation Guide. The first character of the server name must be an alphanumeric character.

In the case of *****

Take action based on the message displayed just before the error.

KDJE41803-E

The definition file aa....aa cannot be accessed.

aa....aa: File name

Description

The definition file (aa....aa) cannot be accessed.

Action

Confirm that the relevant file exists, check the access permissions, and then re-execute the cjstartweb command or the cjstopweb command.

KDJE41804-E

The specified aa....aa is too long: bb....bb

aa....aa: Items with error (path name or server name)

bb....bb: Definition file key name or command name

Description

The specified path name or server name (aa....aa) is too long.

The path name is specified within 256 bytes.

The server name is specified within the range of the maximum length of the host name in the operating OS. Single byte alphanumeric characters, underscores (_), or hyphens (-) can be used. Note that the first character must be an alphanumeric character.

Action

Specify according to the restrictions.

KDJE41805-I

Usage: cjstartweb [serverName] [-security]

Description

This message describes the usage method of the cjstartweb command.

KDJE41806-I

Usage: cjstopweb [serverName] [-f | -fd [ThreadDumpInterval ThreadDumpCount]]

Description

This message describes the usage method of the cjstopweb command.

KDJE41807-I

The deletion of the Web container server has completed successfully. Server name = aa....aa

aa....aa: Server name

Description

The deletion of Web container server (aa....aa) has finished successfully.

KDJE41808-I

Usage: cjwebsetup [-d serverName | serverName]

Description

This message describes the usage method of the cjwebsetup command.

KDJE41809-E

The deletion of the Web container server has failed. Server name = aa....aa, Reason = bb....bb

aa....aa: Server name

bb....bb: Error contents

Description

An attempt to unset up the Web container server (aa....aa) has failed.

Action

Take action based on the error details.

Server is not found

A non-existing server name is specified.

Deletion of file failed

The file cannot be deleted. Confirm that the file to be deleted is not being accessed or is not a read-only file.

Invalid server name

Invalid server name is specified. Single-byte alphanumeric characters, underscores (_), and hyphens (-) can be used in the server name within the range estimated by referencing the manual uCosminexus Application Server System Setup and Operation Guide. The first character of the server name must be an alphanumeric character.

*****

Take the following actions based on the previously displayed message ID:

In case of KDJE40016-E

Contact the maintenance personnel.

In case of KDJE41813-E

The Web container server is running.

Stop the Web container server, and then re-execute the deletion command.

KDJE41810-E

The directory aa....aa was not found.

aa....aa: Directory name

Description

The directory (aa....aa) was not found.

Action

Confirm that the Cosminexus Component Container is installed properly.

KDJE41811-I

Usage: cjdumpweb [serverName]

Description

This message describes the usage method of the cjdumpweb command.

KDJE41813-E

The Web container server has already been started.

Description

The start request is cancelled because the Web container server is already running.

Action

Confirm that the Web container server is running.

If the Web container server is started properly, use that server as it is.

When the server is not started properly, restart the server if required.

KDJE41814-E

The Web container server is not found.

Description

The Web container server is not found.

Action

Confirm that the Web container server is running, and then re-execute the command.

KDJE42000-E

Deployment has abended. An invalid environment entry was found. Values could not converted to the specified types (aa....aa).

aa....aa: Target

Description

The deployment process has abended.

An invalid environment entry (aa....aa) was found. Values cannot be converted to the specified types.

Action

Revise the <env-entry> tag, and then set the appropriate contents.

KDJE42001-E

Deployment has abended. Resources (aa....aa) are unresolved.

aa....aa: Target

Description

The deployment process has abended.

The deployment process failed because the link for resource reference (aa....aa) cannot be resolved.

Action

Use the server management commands to resolve the links for the relevant application resources.

KDJE42002-E

Deployment has abended. EJBs (aa....aa) are unresolved.

aa....aa: Target

Description

The deployment process has abended.

The deployment process failed because the link for the EJB (aa....aa) reference cannot be resolved.

Action

Resolve the links of the EJBs of corresponding application.

When the settings of the property file are invalid

Set up appropriate contents in the <ejb-ref> tag or the <ejb-local-ref> tag of the property file.

When the settings of the Deployment Descriptor are invalid

Revise the <ejb-ref> tag or the <ejb-local-ref> tag of Deployment Descriptor, and set up the appropriate contents.

KDJE42004-E

Deployment has abended. Roles in the security constraint (aa....aa) are unresolved.

aa....aa: Target

Description

The deployment process has abended.

The reference definition of roles is unresolved.

Action

Use the server management commands to resolve the link for the relevant application roles.

KDJE42005-E

This EAR has an invalid context root (aa....aa). It may contain an invalid character such as "*".

aa....aa: Context root name

Description

This EAR has an invalid context root (aa....aa).

This might contain an invalid character such as "*".

Characters that can be specified in the Context Root

Alphanumeric characters and the symbols shown below

/ @ & + $ , - _ . ! ' ( ) % ~

However, the characters must be specified based on the following rules:

/ is valid only as the delimiter of the path and character such as // cannot be specified.

cannot be used to express relative path (such as ./).

% can only be used as escape (such as %20).

Action

Revise with appropriate characters.

KDJE42006-E

Exception while generating remote interface implementation for bean aa....aa. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description

An exception occurred while generating the remote interface implementation class for Bean (aa....aa).

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42007-E

Exception while generating home interface implementation for bean aa....aa. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description

An exception occurred while generating the home interface implementation class for Bean (aa....aa).

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42008-E

Error generating aa....aa stubs for bean interface bb....bb. Reason=cc....cc

aa....aa: Stub type

bb....bb: J2EE application name

cc....cc: Cause of the error

Description

An error occurred while generating aa....aa stubs for Bean interface (bb....bb).

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42009-E

Error compiling container generated java source files Detail=aa....aa

aa....aa: Details

Description

An error occurred while compiling the generated java source files.

Action

Reference the details, and then take action.

Take action based on the following cases:

If another error message is output

Reference the output message, and then take action.

If Generics is used in definitions of the Home/ Component interface

Do not use Generics in the definitions of the Home Component interface.

If Generics is used in definitions of the business interface

Set up the type variable as a parameter of the business interface.

If the method of the parameter in the business interface is redefined

Delete the redefined method.

If the cause is not known, collect the maintenance information, and then contact maintenance personnel.

KDJE42010-E

The native library file (aa....aa) and a native library file with the same name as the resource adapter "bb....bb" are already deployed, so importing or adding is not possible.

aa....aa: Native library file name

bb....bb: Resource adapter display name

Description

The native library file with the same name as the native library file (aa....aa) of resource adapter (bb....bb) is already deployed, therefore, importing or adding is not possible.

Action

Delete the resource adapter that is using the already existing native library file, and then import or add again.

KDJE42011-E

This file (aa....aa) and a file with the same name exist in the J2EE application, so importing is not possible.

aa....aa: File name

Description

This file (aa....aa) and a file with the same name exist in the J2EE application, so importing is not possible.

Action

Change the name of the library JAR file to be imported or delete the already existing file with the same name, and then re-import.

KDJE42012-E

Deployment has abended. An attempt to read the runtime deployment descriptor in the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended. An attempt to read the runtime deployment descriptor in the J2EE application (aa....aa) has failed.

Action

For the messages in which the exception information starts with nnnn (n is a number), see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42014-E

Deployment has abended. An attempt to create the configuration for the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended. An attempt to create the configuration information for the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42018-E

Deployment has abended. An attempt to check unresolved security roles in the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended. An attempt to check the role with unresolved link settings in the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42019-E

Deployment has abended. An attempt to check unresolved resource references in the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended. An attempt to check the resource reference information with unresolved link settings in the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42020-E

Deployment has abended. An attempt to check unresolved EJB references in the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended. An attempt to check the EJB references information with unresolved link setting in the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42021-E

Deployment has abended. An attempt to check invalid environment entries in the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended. An attempt to check invalid environment entries in the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42022-E

Deployment has abended. An attempt to deploy WARs in the J2EE application "aa....aa" has failed.

aa....aa: J2EE application name

Description

The deployment process has abended. An attempt to deploy WARs in the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42023-E

Deployment has abended. An attempt to deploy application clients in the J2EE application "aa....aa" has failed.

aa....aa: J2EE application name

Description

The deployment process has abended. An attempt to deploy application clients in the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42024-E

Deployment has abended. An attempt to generate IIOP stub/classes for the J2EE application "aa....aa" has failed.

aa....aa: J2EE application name

Description

The deployment process has abended. An attempt to generate IIOP stub and classes for the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42025-E

Deployment has abended. An attempt to deploy EJBs in the J2EE application "aa....aa" has failed.

aa....aa: J2EE application name

Description

The deployment process has abended. An attempt to deploy the EJBs in the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42026-E

Deployment has abended. The deploy component in the J2EE application "aa....aa" could not be found.

aa....aa: J2EE application name

Description

The deployment process has abended. The deploy component in the J2EE application (aa....aa) cannot be found.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42028-E

Deployment has abended. An attempt to clean up the J2EE application "aa....aa" has failed.

aa....aa: J2EE application name

Description

The deployment process has abended. An attempt to clean up the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42031-E

Deployment has abended. An invalid EJB exists.

Description

The deployment process has abended. An invalid EJB exists.

Action

Confirm that an invalid EJB does not exist. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42034-E

Deployment has abended. An attempt to copy the interface for the EJB "aa....aa" has failed.

aa....aa: EJB name

Description

The deployment process has abended.

An attempt to copy the interface for the EJB (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42035-E

Deployment has abended. An attempt to deploy the EJB "aa....aa" has failed.

aa....aa: EJB name

Description

The deployment process has abended.

An attempt to deploy the EJB (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42039-E

EJB error: aa....aa

aa....aa: Details of the error contents

Description

The error details of EJB are displayed.

Action

Reference the details, and then take action. For details, see 7.9 List of details for KDJE42039-E and KDJE42270-W.

Take action based on the following cases:

If another error message is output

Reference the output message, and then take action.

If Generics is used in definitions of the Home/Component interface

Do not use Generics in the definitions of the Home Component interface.

If the cause is not known, collect the maintenance information, and then contact maintenance personnel.

KDJE42040-I

The deploying environment setup has finished.

Description

The deploying environment setup has finished.

KDJE42041-I

Creation of the configuration for the J2EE application "aa....aa" is in progress.

aa....aa: J2EE application name

Description

The creation of the configuration information for the J2EE application (aa....aa) is in progress.

KDJE42042-I

Loading of the EJB-JAR deployment descriptors in the J2EE application "aa....aa" is in progress.

aa....aa: J2EE application name

Description

Loading of the EJB-JAR deployment descriptors in the J2EE application (aa....aa) is in progress.

KDJE42043-I

Deployment of all the application clients for the J2EE application "aa....aa" is in progress.

aa....aa: J2EE application name

Description

The deployment process of all the application clients for the J2EE application (aa....aa) is in progress.

KDJE42044-I

Generation of the IIOP stubs/classes for the J2EE application "aa....aa" is in progress.

aa....aa: J2EE application name

Description

The generation of the IIOP stubs and classes for the J2EE application (aa....aa) is in progress.

KDJE42046-I

Verification of the EJBs is in progress.

Description

Verification of the EJB contents is in progress.

KDJE42047-I

Verification of the EJB "aa....aa" is in progress.

aa....aa: EJB name

Description

Verification of the EJB (aa....aa) contents is in progress.

KDJE42048-I

The deployment environment will now be set.

Description

The deployment environment will now be set.

KDJE42050-I

Deployment of the EJB "aa....aa" is in progress.

aa....aa: EJB name

Description

The deployment process of the EJB (aa....aa) is in progress.

KDJE42051-I

Exporting of the client files is in progress.

Description

Exporting of the client files is in progress.

KDJE42052-I

Deployment of all the web components for the J2EE Application "aa....aa" is in progress.

aa....aa: J2EE application name

Description

The deployment process of all the web components for the J2EE Application (aa....aa) is in progress.

KDJE42053-I

Redeployment of the J2EE application "aa....aa" is in progress.

aa....aa: J2EE application name

Description

The J2EE application (aa....aa) to be redeployed is displayed.

KDJE42055-E

The native library file (aa....aa) that the resource adapter "bb....bb" has cannot be deleted. Reboot the J2EE server, and then redelete.

aa....aa: Native library file name

bb....bb: Resource adapter display name

Description

The native library file (aa....aa) included in the resource adapter (bb....bb), cannot be deleted.

Action

Reboot the J2EE server, and then re-delete.

KDJE42056-E

The file (hitachi-runtime.jar) with the reserved name cannot be imported.

Description

The file (hitachi-runtime.jar) with the reserved name cannot be imported.

Action

Change the file name, and then re-import.

KDJE42057-E

The connection factory class could not be found from the resource adapter "aa....aa", so importing or adding is not possible.

aa....aa: Resource adapter display name

Description

The connection factory class cannot be found from the resource adapter (aa....aa), therefore, you cannot import or add.

Action

Confirm that the contents of the DD for resource adapter are correct or the connection factory class of the resource adapter exists. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42058-E

Exception while generating local component interface implementation for bean aa....aa. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description

An exception occurred while generating a local interface implementation class for Bean (aa....aa).

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42059-E

Exception while generating local home interface implementation for bean aa....aa. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description

An exception occurred while generating local home interface implementation class for Bean (aa....aa).

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42060-E

Exception while generating cmp entity bean:aa....aa implementation. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description

An exception occurred while generating the CMP Entity Bean implementation class.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42061-E

Exception while generating cmp state object implementation for bean aa....aa. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description

An exception occurred while generating the CMP state object class for Bean (aa....aa).

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42062-E

Exception while generating cmp join object:aa....aa implementation. Detail=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description

An exception occurred while generating aa....aa.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42063-E

The JAR file (aa....aa) which the resource adapter "bb....bb" has cannot be deleted. Reboot the J2EE server, and then redelete.

aa....aa: JAR file name

bb....bb: Resource adapter display name

Description

The JAR file (aa....aa) included in the resource adapter (bb....bb), cannot be deleted.

Action

Reboot the J2EE server, and then re-delete.

KDJE42064-E

The WAR DD (aa....aa) has more than one filter with the same name "bb....bb".

aa....aa: WAR DD name

bb....bb: Filter name

Description

The WAR DD (aa....aa) has more than one filter with the same name (bb....bb).

The process of importing will be interrupted.

Action

Investigate the WAR file and change the contents of <filter-name> tag.

KDJE42065-E

The WAR file (aa....aa) has more than one filter with the same name "bb....bb".

aa....aa: WAR file name

bb....bb: Filter name

Description

The WAR file (aa....aa) has more than one filter with the same name (bb....bb).

The process of importing will be interrupted.

Action

Investigate the WAR file and change the contents of <filter-name> tag.

When the cjimportapp command is executed, the WAR file is included in EAR.

KDJE42066-E

The J2EE resource aa....aa could not start in the current J2EE server mode.

aa....aa: J2EE resource name

Description

The J2EE resource (aa....aa) cannot be started in the current J2EE functionality mode.

Action

Confirm that the J2EE functionality mode is correct. If the J2EE functionality mode is correct, delete the J2EE resource, and then re-create it.

KDJE42067-E

The J2EE resource adapter aa....aa could not start in the current J2EE server mode.

aa....aa: J2EE resource adapter name

Description

The J2EE resource adapter (aa....aa) cannot be started in the current J2EE functionality mode.

Action

Confirm that the J2EE functionality mode is correct. When the J2EE functionality mode is to be downgraded and used, reset the environment of the J2EE server.

KDJE42068-E

The extension of the library JAR file (aa....aa) is not ".jar", so importing is not possible.

aa....aa: Library JAR file name

Description

You cannot import because the extension of the library JAR file (aa....aa) is not .jar.

Action

Change the extension to .jar, or add the extension, and then re-import.

KDJE42069-E

Deployment has abended. An attempt to deploy the J2EE application "aa....aa" has failed.

aa....aa: J2EE application name

Description

An attempt to deploy the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42070-E

The resource adapter "aa....aa" has the native library file, so it cannot be added to the J2EE application.

aa....aa: Resource adapter display name

Description

The resource adapter (aa....aa) cannot be added to the J2EE application because it contains a native library file.

Action

Use the resource adapter that contains a native library file, in a stand-alone deployment.

KDJE42071-E

Deployment has abended. An attempt to check the resource reference in the J2EE application "aa....aa" has failed. Details = bb....bb

aa....aa: J2EE application name

bb....bb: Detailed message

Description

The deployment process has abended.

An attempt to check the resource reference in the J2EE application (aa....aa) has failed.

Action

See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42072-E

The stand-alone resource adapter "aa....aa" has been started once. Reboot the J2EE server, and then redelete.

aa....aa: Resource adapter display name

Description

The stand-alone resource adapter (aa....aa) is started once.

Action

Reboot the J2EE server, and then re-delete.

KDJE42073-E

Deployment has abended. The assembly descriptor (aa....aa) is invalid.

aa....aa: Target

Description

The deployment was abended because the assembly descriptor (aa....aa) is invalid.

Action

Check the values of ejb-name, method-intf, method-name, method-params, trans-attribute of the container-transaction. Also check the values of role-name, ejb-name, method-intf, method-name, method-params of the method-permission.

KDJE42074-E

Deployment has abended. An attempt to check the assembly descriptor in the J2EE Application "aa....aa" has failed. Exception=bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to check the assembly descriptor in the J2EE Application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42075-E

Deployment has abended. An attempt to verify the EJB components in the J2EE Application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to verify the EJB components in the J2EE Application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42076-E

Deployment has abended. A J2EE component unsupported by the current J2EE function mode is included: aa....aa

aa....aa: Details

Description

The deployment process has abended.

A J2EE component that is not supported by the current J2EE functionality mode is included in the J2EE functionality mode.

Action

Confirm that the J2EE functionality mode is correct. When the J2EE functionality mode is to be downgraded and used, reset the environment of the J2EE server.

KDJE42077-E

Deployment has abended. An attempt to verify the J2EE components in the J2EE Application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to verify the J2EE components in the J2EE Application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42078-E

Deployment has abended. The same abstract schema name is specified in Jar (aa....aa).

aa....aa: Target

Description

The deployment was abended because the same abstract-schema-name (aa....aa) is specified in the same JAR.

Action

Make sure that the value of abstract-schema-name is not duplicated in the EJB-JAR file.

KDJE42079-E

Deployment has abended. An attempt to check the abstract schema name in the J2EE application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to check the abstract-schema-name in the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42080-E

Deployment has abended. The JMS resource used in the application does not support XA (aa....aa).

aa....aa: Target

Description

The deployment process has abended.

The JMS resource (aa....aa) used in the application does not support the XA transactions.

Action

Change the value for the transaction-support of the resource adapter.

KDJE42081-E

Deployment has abended. An attempt to check the transaction type of the JMS resource in the J2EE Application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to check the transaction-support of the JMS resource used in the J2EE Application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42082-E

Deployment has abended. SQL statements have not been generated yet (aa....aa).

aa....aa: Details

Description

The deployment process has abended.

SQL statements for CMP2.x are not generated.

Action

Re-generate the SQL statement for each Entity Bean of the CMP using the server management command (cjgencmpsql).

KDJE42083-E

Deployment has abended. An attempt to check the SQL statements in the J2EE Application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to check the SQL statements used in the Entity Beans of CMP2.x in the J2EE application (aa....aa) has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42084-E

Deployment has abended. EJB lookup names are duplicated. Details = aa....aa

aa....aa: Details

Description

The deployment process has abended.

The EJB lookup names are duplicated.

Action

Change the EJB lookup names so that they are not duplicated, and then redeploy.

KDJE42085-E

Deployment has abended. An attempt to check duplicated EJB lookup names in the J2EE Application "aa....aa" has failed. Exception = bb....bb

aa....aa: J2EE application name

bb....bb: Exception information

Description

The deployment process has abended.

An attempt to check whether the EJB lookup names in the J2EE Application (aa....aa) are duplicated has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42086-E

Deployment has abended. The CMP EntityBean is not mapped correctly. (aa....aa)

aa....aa: Details

Description

The deployment process has abended.

The CMP Entity Bean is not mapped correctly.

Action

Map the CMP, and then redeploy.

KDJE42087-E

Deployment has abended. An attempt to check the CMP Entity Beans in the J2EE Application "aa....aa" has failed. Details = bb....bb

aa....aa: J2EE application name

bb....bb: Detailed message

Description

The deployment process has abended.

An attempt to check whether the CMP Entity Beans in the J2EE Application (aa....aa) are correctly mapped has failed.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42088-E

Deployment has abended. An attempt to check the connection factory reference in the J2EE Application "aa....aa" has failed. Details = bb....bb

aa....aa: J2EE application name

bb....bb: Detailed message

Description

The deployment process has abended.

An attempt to check the connection factory reference in the J2EE Application (aa....aa) has failed.

Action

See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42089-E

Deployment has abended. An attempt to check the resource environment reference in the J2EE Application "aa....aa" has failed. Details = bb....bb

aa....aa: J2EE application name

bb....bb: Detailed message

Description

The deployment process has abended.

An attempt to check the resource environment reference in the J2EE Application (aa....aa) has failed.

Action

See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42090-E

Deployment has abended. An attempt to check the destination reference in the J2EE application "aa....aa" has failed. Details = bb....bb

aa....aa: J2EE application name

bb....bb: Detailed message

Description

The deployment process has abended.

An attempt to check the destination reference in the J2EE application (aa....aa) has failed.

Action

See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42091-E

An attempt to deploy the J2EE resource adapter aa....aa has failed. (details = bb....bb)

aa....aa: J2EE resource adapter name

bb....bb: Detailed message of the exception

Description

An attempt to deploy the J2EE resource adapter (aa....aa) has failed.

Action

See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42092-E

An attempt to start the J2EE resource adapter aa....aa has failed. (detail=bb....bb)

aa....aa: J2EE resource adapter name

bb....bb: Detailed message of the exception

Description

An attempt to start the J2EE resource adapter (aa....aa) has failed.

Action

See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42093-E

An attempt to stop J2EE resource adapter aa....aa has failed. (detail=bb....bb)

aa....aa: J2EE resource adapter name

bb....bb: Detailed message of the exception

Description

An attempt to stop the J2EE resource adapter (aa....aa) has failed.

Action

See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42094-E

An attempt to un-deploy the J2EE resource adapter aa....aa has failed. (detail=bb....bb)

aa....aa: J2EE resource adapter name

bb....bb: Detailed message of the exception

Description

An attempt to undeploy the J2EE resource adapter (aa....aa) has failed.

Action

See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42095-E

An attempt to deploy the J2EE resource aa....aa has failed. (detail = bb....bb)

aa....aa: J2EE resource name

bb....bb: Detailed message of the exception

Description

An attempt to deploy the J2EE resource (aa....aa) has failed.

Action

See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42096-E

An attempt to start the J2EE resource aa....aa has failed. (detail=bb....bb)

aa....aa: J2EE resource name

bb....bb: Detailed message of the exception

Description

An attempt to start the J2EE resource (aa....aa) has failed.

Action

See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42097-E

An attempt to stop J2EE resource aa....aa has failed. (detail=bb....bb)

aa....aa: J2EE resource name

bb....bb: Detailed message of the exception

Description

An attempt to stop the J2EE resource (aa....aa) has failed.

Action

See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42098-E

An attempt to un-deploy the J2EE resource aa....aa has failed. (detail=bb....bb)

aa....aa: J2EE resource name

bb....bb: Detailed message of the exception

Description

An attempt to undeploy the J2EE resource (aa....aa) has failed.

Action

See the detailed message of the exception, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42099-E

An attempt to create the directory (aa....aa) has failed.

aa....aa: Directory name

Description

An attempt to create the directory (aa....aa) has failed.

Action

Confirm that the following conditions are fulfilled. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

If the disk space is insufficient, secure sufficient disk space.

When the path or name of the directory is longer than the length restricted by the OS, specify the following settings so that the length is shortened:

- When the root path of the working directory is long, specify a shallow directory tree by an absolute path in the ejb.public.directory key defined in the user definition file (usrconf.cfg) for the J2EE server.

- When the J2EE server name is long, perform operation in the environment with a short J2EE server name.

- When the name of the J2EE module (for example J2EE application, EJB-JAR, WAR, resource adapter, data source, mail configuration) is long, change it to a short name.

- When the file name to be imported or a value of the <display-name> tag defined by the DD in the file is long, use a shorter name and value.

If access permission is not available, assign the access permission.

KDJE42100-E

An attempt to create the file (aa....aa) has failed.

aa....aa: File name

Description

An attempt to create the file (aa....aa) has failed.

Action

Confirm that the following conditions are fulfilled. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

If the disk space is insufficient, secure sufficient disk space.

When the path or name of the directory is longer than the length restricted by the OS, specify the following settings so that the length is shortened:

- When the root path of the working directory is long, specify a shallow directory tree by an absolute path in the ejb.public.directory key defined in the user definition file (usrconf.cfg) for the J2EE server.

- When the J2EE server name is long, perform operation in the environment with a short J2EE server name.

- When the name of the J2EE module (for example J2EE application, EJB-JAR, WAR, resource adapter, data source, mail configuration) is long, change it to a short name.

- When the file name to be imported or a value of the <display-name> tag defined by the DD in the file is long, use a shorter name and value.

If access permission is not available, assign the access permission.

KDJE42101-I

aa....aa / bb....bb stubs are generated.

aa....aa: Number of generated stubs

bb....bb: Number of stubs to be generated

Description

The stubs of aa....aa interface are generated.

This message is displayed when the stubs are generated in multiple interfaces in case they cannot be generated collectively. The stubs cannot be generated collectively because the arguments in the stub generation command might be too long.

KDJE42102-W

aa....aa command failed. Length of arguments may be too long.(length= bb....bb) The command is executed again with reduced number of interfaces.

aa....aa: Command name

bb....bb: Length of the argument when the command is executed

Description

An attempt to execute the command has failed. Length of the arguments of stub generation command might be too long.

Action

Reduce the number of interfaces to be specified in the arguments, and then re-execute the command.

KDJE42103-E

The specified JDBC driver is not supported by the current J2EE feature. JDBC driver = aa....aa Details = bb....bb

aa....aa: File name[, file name]

bb....bb: Detailed message

Description

The specified JDBC driver is not supported by the operation mode of the current J2EE server mode.

Action

Take the following actions based on the details:

To the basic mode, need to import only JdbcDbpsv.jar.

In the case of basic mode, import only the JdbcDbpsv.jar of the Cosminexus Driver for Java Technology.

To the basic mode, need to import JDBC driver that implements the java.sql.Driver interface.

In the case of basic mode, import the JDBC driver containing the class that implements java.sql.Driver interface.

KDJE42105-E

The runtime deployment descriptor was not found. File path = aa....aa

aa....aa: Absolute path of the file

Description

The runtime deployment descriptor was not found.

Action

Re-create the J2EE application. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42106-E

The directories and files in the allstubs directory could not be deleted. allstubs directory path = aa....aa

aa....aa: Absolute path of allstubs directory

Description

The directories and files in the allstubs directory cannot be deleted.

Action

Confirm the following details, and then take action: If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

When the delete permission is not added in the allstubs directory, add the permission, and restart the J2EE server.

When the allstubs directory is referenced from some other process, restart the J2EE server after that process finishes.

KDJE42107-I

The J2EE application aa....aa will now be deployed and started.

aa....aa: J2EE application name

Description

This message indicates the start process of the J2EE application.

KDJE42108-I

The J2EE application aa....aa started successfully.

aa....aa: J2EE application name

Description

This message indicates that the application has started successfully.

KDJE42109-I

The home interface for aa....aa will now be published.

aa....aa: Home interface name

Description

This message indicates that the home interface will now be published.

KDJE42110-I

The Web component aa....aa will now be started.

aa....aa: WEB component

Description

This message indicates the start of WEB component.

KDJE42111-I

Importing "aa....aa" is in progress.

aa....aa: Target

Description

This message indicates the execution of import processing.

KDJE42112-I

Importing "aa....aa" was successful.

aa....aa: Target

Description

This message indicates that the import processing was successful.

KDJE42113-I

Exporting "aa....aa" is in progress.

aa....aa: Target

Description

This message indicates the execution of export processing.

KDJE42114-I

Sending export information of "aa....aa" was successful.

aa....aa: Target

Description

This message indicates that export processing was successful.

KDJE42115-E

An unexpected exception occurred. Details = aa....aa

aa....aa: Details

Description

An unexpected exception occurred.

Action

See the details, and then take action. For the messages in which the detailed information starts with nnnn (n is a number), see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42116-E

The composition of the file (aa....aa) is invalid. Re-create the J2EE application. If you cannot re-create the J2EE application, contact the system administrator.

aa....aa: File name

Description

The composition of the file (aa....aa) is invalid.

Action

Re-create the J2EE application. If you cannot re-create the J2EE application, contact the maintenance personnel.

KDJE42117-E

The value of the sequential number exceeded the limit. Contact the system administrator.

Description

The value of the sequential number has exceeded the limit.

Action

Contact the maintenance personnel.

KDJE42118-E

An attempt to convert the deployment descriptor file (hitachi-ejb-app.xml) in the file (aa....aa) has failed. Re-create the J2EE application. If you cannot re-create the J2EE application, contact the system administrator. Details = bb....bb

aa....aa: Name of the file with runtime information

bb....bb: Detailed message

Description

An attempt to convert the deployment descriptor in the file (aa....aa) has failed.

Action

Re-create the J2EE application. If you cannot re-create the J2EE application, contact the maintenance personnel.

KDJE42119-E

A J2EE resource adapter with the same name already exists. Display name = aa....aa

aa....aa: Display name

Description

A J2EE resource adapter with the same name already exists.

Action

Change the display name of the J2EE resource adapter, and then re-execute the operation.

KDJE42120-E

The context root "aa....aa" of the WAR file (bb....bb) in the file (cc....cc) is invalid. Re-create the J2EE application. If you cannot re-create the J2EE application, contact the system administrator.

aa....aa: Context root

bb....bb: WAR file name

cc....cc: File name

Description

The context root (aa....aa) of the WAR file (bb....bb) in the file (cc....cc) is invalid.

Action

Re-create the J2EE application. If you cannot re-create the J2EE application, contact the maintenance personnel.

KDJE42121-E

An attempt to import the file (aa....aa) has failed. Take action based on the detail message. If the cause is unknown, contact the system administrator. Details = bb....bb

aa....aa: File name

bb....bb: Detailed message

Description

An attempt to import the file (aa....aa) has failed.

Action

See the details, and then take action. For the messages in which the detailed information starts with nnnn (n is a number), see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory. If you do not understand the cause, contact the maintenance personnel.

KDJE42122-E

The value of the sequential number specified in the lookup name of the EJB exceeded the limit. EJB name = aa....aa, Lookup name = bb....bb

aa....aa: EJB name

bb....bb: Lookup name

Description

The value of the sequential number specified in the lookup name (bb....bb) of the EJB(aa....aa) has exceeded the limit.

Action

Change the lookup name of the existing EJB, and then re-execute the operation.

KDJE42123-E

A resource adapter that has the native library file in the file (aa....aa) exists. Delete the native library file, and then re-import.

aa....aa: File name

Description

A resource adapter that contains the native library file, exists in the file (aa....aa).

Action

Delete the native library file, and then re-import.

KDJE42124-E

The application aa....aa already exists. Check the application name. (Application names are not case-sensitive.)

aa....aa: Lookup name

Description

The J2EE application that contains the lookup name (aa....aa), already exists.

Action

Take action depending on the following status:

When creating a new J2EE application

Change the display-name of the J2EE application, and then re-create.

When importing an EAR file based on the J2EE specifications

Change the display-name of the EAR file to be imported, and then re-import, or delete the application with duplicate name, and then re-import.

When importing the file with runtime information

Delete the application with duplicate lookup name, and then re-import.

KDJE42125-W

The value of the tag in the deployment descriptors in the file is duplicated (aa....aa). Only the value found first or last is used. Details = bb....bb

aa....aa: Name of the file with runtime information

bb....bb: Detailed message

Description

The value of the tag in the deployment descriptors in the file (aa....aa) is duplicated. Only the value found first or last is used.

Action

See the details, and then revise the duplicated value of the tag.

KDJE42126-E

An attempt to execute an external program has failed. Details = aa....aa

aa....aa: Details

Description

An attempt to execute an external program has failed.

The environment settings might be invalid.

Action

See the details. Revise the environment settings. If you do not understand the cause, contact the maintenance personnel.

KDJE42127-E

The file could not be deleted. Path = aa....aa

aa....aa: File path

Description

The file cannot be deleted.

Action

Confirm the file to be deleted, and then take action. If you do not understand the cause, contact the maintenance personnel.

KDJE42128-E

An attempt to parse the XML has failed. Details = aa....aa

aa....aa: Details

Description

An attempt to parse the XML has failed.

Action

See the details, confirm the XML file to be processed, and then take action.

KDJE42129-E

The directory could not be deleted. Path = aa....aa

aa....aa: Directory path

Description

The directory cannot be deleted.

Action

Confirm the directory to be processed, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42130-E

This stand-alone resource adapter "aa....aa" is tested once. Reboot the J2EE server, and then delete.

aa....aa: Resource adapter name

Description

This stand-alone resource adapter (aa....aa) is tested once.

Action

Reboot the J2EE server, and then delete the target resource adapter.

KDJE42131-E

Another server management command is already running. Details = [aa....aa]

aa....aa: Details

Description

Either another operation is already being performed by the server management command or the recovery process of the work directory, that is performed when an error occurs in the server management command, has failed.

Action

Take action using any one of the following methods:

If another server management command is being executed, perform the operation again after the operation, that is in progress, terminates.

If the message KDJE42134-E is output before this message, the recovery process of the work directory has failed. See the action described in the message KDJE42134-E.

KDJE42132-I

The status of the public directory is invalid because a server management command operation was interrupted. Recovery will now start. Details = [aa....aa]

aa....aa: Details

Description

This message indicates that the recovery of the working directory has started.

The status of the working directory is invalid because a server management command operation was interrupted. Recovery of the working directory will now start.

KDJE42133-I

Recovery of the public directory has finished.

Description

This message indicates that the recovery of the working directory has finished.

KDJE42134-E

An attempt to recover the public directory has failed. Details = [aa....aa]

aa....aa: Details

Description

An attempt to recover the working directory has failed.

Action

See the details, and then take action. For the messages in which the detailed information starts with nnnn (n is a number), see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory. Check whether any other error message is displayed and if it is displayed, take action. If the problem is not resolved, restart the J2EE server. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42135-E

The directory cannot be accessed. Path = aa....aa

aa....aa: Directory path

Description

The directory cannot be accessed.

Action

Confirm that the access permissions are set to the directory. If access permissions are not set, set the appropriate permissions, and then re-execute the operation.

KDJE42136-E

The status of the public directory is invalid.

Description

The status of the working directory is invalid.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE42137-E

An internal error occurred. Contact the system administrator.

Description

An internal error occurred.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE42138-E

This application had failed in stopping. Please operate it by rebooting the J2EE server.

Description

This message indicates that the J2EE application cannot be started and deleted because an attempt to stop the J2EE application has failed earlier.

Action

Reboot the J2EE server, and then perform the operation.

KDJE42139-I

The J2EE application (aa....aa) will now be stopped.

aa....aa: J2EE application name

Description

This message indicates that the processing to stop the application (aa....aa), has started.

KDJE42140-I

The J2EE application (aa....aa) stopped.

aa....aa: J2EE application name

Description

This message indicates that the J2EE application (aa....aa) is stopped.

KDJE42141-I

The J2EE application (aa....aa) will now be undeployed.

aa....aa: J2EE application name

Description

This message indicates that the processing to undeploy the J2EE application (aa....aa), has started.

KDJE42142-I

The J2EE application (aa....aa) undeployed.

aa....aa: J2EE application name

Description

This message indicates that the J2EE application (aa....aa) is undeployed.

KDJE42143-I

The ClassLoader for the J2EE application was initialized. (display-name = aa....aa, initialized time = bb....bb)

aa....aa: J2EE application name

bb....bb: Initialized time

Description

This message indicates that the ClassLoader was initialized.

KDJE42144-I

The ClassLoader for the J2EE application was finalized. (display-name = aa....aa, initialized time = bb....bb)

aa....aa: J2EE application name

bb....bb: Initialized time

Description

This message indicates that the application class loader is destroyed.

This message is output when the finalize method process of the application class loader is executed, after the J2EE application stops.

If this message is not displayed even after repeatedly starting or stopping the application, memory leakage might have occurred.

By comparing the J2EE application name and time information output in the KDJE42143-I message, the destroyed application class loader can be identified. For details, see Appendix B Configuration of the Class Loader in the uCosminexus Application Server Common Container Functionality Guide. This message indicates that the ClassLoader was destroyed.

The timing of displaying this message depends on the garbage collector. If this message is not displayed even after repeatedly starting or stopping the application, memory leakage might have occurred.

KDJE42145-E

Usage:

Format 1: cjsweepout [servername] -inspect

Format 2: cjsweepout [servername] -allsweep

Format 3: cjsweepout [servername] -sweep id(key)

Description

This message describes the usage method of the cjsweepout command.

Action

Re-execute the cjsweepout command using the correct usage method.

KDJE42146-E

The configuration file for Cosminexus Component Container was not found. (path = aa....aa)

aa....aa: Path of the configuration file

Description

The configuration file of Cosminexus Component Container was not found.

Action

Confirm that the name of the J2EE server specified when executing the cjsweepout command is correct. If the name of the J2EE server is incorrect, specify the correct name, and then re-execute the cjsweepout command. If the configuration file is deleted, re-install the Cosminexus Component Container or set up the J2EE server again, and re-create the configuration file, and then, re-execute the cjsweepout command.

KDJE42147-E

The configuration file for Cosminexus Component Container could not be accessed. (path = aa....aa, detail = bb....bb)

aa....aa: Path of the configuration file

bb....bb: Detailed message

Description

The configuration file for Cosminexus Component Container cannot be accessed.

Action

When the access permissions are not assigned to the configuration file, assign the permissions, and then re-execute the cjsweepout command. When the access permissions are assigned to the configuration file, take action based on the details, and then re-execute the cjsweepout command.

KDJE42148-E

The value of the ejbserver.http.port property, defined in the J2EE server configuration file, is invalid. (path = aa....aa, value = bb....bb, detail = cc....cc)

aa....aa: Path of the configuration file

bb....bb: Value of ejbserver.http.port property

cc....cc: Details

Description

The value of the ejbserver.http.port property, defined in the J2EE server configuration file, is invalid.

Action

Correct the value of ejbserver.http.port property, and then re-execute the cjsweepout command.

KDJE42149-E

The J2EE server specified when the cjsweepout command was executed is already running. (server name = aa....aa, http server port number = bb....bb)

aa....aa: The J2EE server name

bb....bb: Port number of the HTTP server (simple Web server) in which the J2EE server is running internally

Description

The J2EE server specified when the cjsweepout command was executed is already running.

Do not execute the cjsweepout command for the running J2EE server.

Action

When executing the cjsweepout command, if the specified J2EE server is running, stop the J2EE server, and then re-execute the cjsweepout command. Confirm that the application (another J2EE server) using the same port number is not running when the J2EE server is being stopped. If the application (another J2EE server) is running, stop it, and then re-execute the cjsweepout command.

KDJE42150-E

The cjsweepout command was executed for an unsupported version of Cosminexus Component Container. (version = aa....aa)

aa....aa: Version information of Cosminexus Component Container

Description

The cjsweepout command was executed for an unsupported version of Cosminexus Component Container.

Action

Confirm that the version of Cosminexus Component Container supports the cjsweepout command.

KDJE42151-E

A file exists where the public directory for the J2EE server should be. (path = aa....aa)

aa....aa: File path

Description

A file exists on the location where the working directory for the J2EE server should exist.

Action

Delete the file, create the working directory, and then re-execute the cjsweepout command.

KDJE42152-E

The public directory for the J2EE server was not found. (path = aa....aa)

aa....aa: Path of the working directory

Description

The working directory for the J2EE server was not found.

Action

Create the working directory, and then re-execute the cjsweepout command.

KDJE42153-E

The public directory for the J2EE server could not be accessed. (path = aa....aa)

aa....aa: Path of the working directory

Description

The working directory for the J2EE server cannot be accessed.

Action

Confirm that the permissions to access the working directory are available, if not, assign the access permissions to the working directory, and then re-execute the cjsweepout command.

KDJE42154-I

Inspection result:

aa....aa

aa....aa: Inspection result

Description

This message is the result of inspecting the state of the directory configuration present under the working directory of the J2EE server.

The contents displayed in the inspection result (aa....aa) are as follows:

ID(Key)

Directory and the file name under the working directory for the J2EE server. The ID is displayed as the character string that can be identified by the cjsweepout command.

Display name

The display name of the J2EE application or the J2EE resource adapter, and the J2EE resource (EJB-JAR, resource adapter, WAR, data source, mail configuration) is displayed. Hyphen (-) is displayed when the display name cannot be obtained.

Condition

Valid is displayed when the directory and the file (ID(Key)) under the working directory for the J2EE server are in normal state, and invalid is displayed when the directory and the file are in abnormal state.

KDJE42155-I

The ID(Key) will now be deleted. (ID = aa....aa)

aa....aa: ID(Key)

Description

The ID(Key) will be deleted.

KDJE42156-I

The ID(Key) has been deleted. (ID = aa....aa)

aa....aa: ID(Key)

Description

The ID(Key) is deleted.

KDJE42157-W

The internal configuration of the J2EE server is in a normal state. (server name = aa....aa)

aa....aa: The J2EE server name

Description

The internal configuration of the J2EE server is in a normal state.

Action

Confirm that the name of the J2EE server specified when executing the cjsweepout command is correct. If the name of the J2EE server is incorrect, specify the correct name, and then re-execute the cjsweepout command.

KDJE42158-W

The ID(Key) is in a normal state. (ID = aa....aa)

aa....aa: ID(Key)

Description

The ID (Key) is in a normal state.

Action

Confirm that the ID (Key) specified while executing the cjsweepout command is correct. If the ID (Key) is incorrect, specify the correct ID (Key), and then re-execute the cjsweepout command.

KDJE42159-E

The ID(Key) was not found. (ID = aa....aa)

aa....aa: ID(Key)

Description

The ID (Key) was not found.

Action

Confirm that the ID (Key) specified while executing the cjsweepout command is correct. If the ID (Key) is incorrect, specify the correct ID (Key), and then re-execute the cjsweepout command.

KDJE42160-I

The cjsweepout command finished successfully.

Description

The cjsweepout command finished successfully.

KDJE42161-E

The attribute of the J2EE application "aa....aa" could not be set. The specification of a library class path is invalid. (invalid path = bb....bb)

aa....aa: J2EE application name

bb....bb: File or directory path

Description

This message indicates that the attribute of the J2EE application cannot be set since the specification of a class path is invalid.

Action

Confirm that the reference path of the class is correct. If the path is incorrect, specify the correct reference path. If the path is correct, confirm that the file specified in the reference path exists on the same machine as the J2EE server. If the file does not exist, place the file in the specified location.

KDJE42162-E

Deployment processing ended abnormally. The specification of a library class path in the J2EE application "aa....aa" is invalid. (invalid path = bb....bb)

aa....aa: J2EE application name

bb....bb: File or directory path

Description

This message indicates that the deployment processing of the J2EE application ended abnormally because the specification of a class path is invalid.

Action

Confirm that the reference path of the class is correct. If the path is incorrect, specify the correct reference path. If the path is correct, confirm that the file specified in the reference path exists on the same machine as the J2EE server. If the file does not exist, place the file in the specified location.

KDJE42163-E

The J2EE application "aa....aa" will not create an RMI-IIOP stub.

aa....aa: J2EE application name

Description

The specified J2EE application will not create an RMI-IIOP stub.

Action

Modify the configuration of the J2EE application, and then execute the command.

KDJE42164-E

This J2EE application has not once been executed. (display-name = aa....aa)

aa....aa: J2EE application name

Description

This J2EE application is not executed even once.

Action

Execute this application once, and then execute the command.

KDJE42165-E

A J2EE application having the same lookup name already exists. (J2EE application display name = aa....aa, J2EE application lookup name = bb....bb, J2EE application mode = cc....cc)

aa....aa: Display name of the J2EE application

bb....bb: Lookup name of the J2EE application

cc....cc: Mode of the J2EE application

Description

A J2EE application with the same lookup name already exists. The lookup name of the J2EE application must be unique in the mode (normal mode, test mode) of the J2EE application.

The lookup name of the J2EE application is auto generated from the display name of the J2EE application.

Action

Change the display name in such a way that the lookup name is not duplicated, and then re-execute the operation.

KDJE42166-I

The J2EE application will now be created. (display name = aa....aa)

aa....aa: Display name of the J2EE application

Description

This message indicates that the processing of creating the J2EE application has started.

KDJE42167-I

The J2EE application was created successfully. (display name = aa....aa)

aa....aa: Display name of the J2EE application

Description

This message indicates that the J2EE application was created successfully.

KDJE42168-I

The resource will now be added to the J2EE application. (resource = aa....aa, type =bb....bb, J2EE application = cc....cc)

aa....aa: Resource display name (file name when the type is LibJar)

bb....bb: Resource type

cc....cc: Display name of the J2EE application

Description

This message indicates that the processing to add the resource to the J2EE application has started.

KDJE42169-I

The resource was successfully added to the J2EE application. (resource = aa....aa, type =bb....bb, J2EE application = cc....cc)

aa....aa: Resource display name (file name when the type is LibJar)

bb....bb: Resource type

cc....cc: Display name of the J2EE application

Description

This message indicates that the resource was successfully added to the J2EE application.

KDJE42170-I

The resource will now be deleted from the J2EE application. (resource = aa....aa, type =bb....bb, J2EE application = cc....cc)

aa....aa: Resource display name (file name when the type is LibJar)

bb....bb: Resource type

cc....cc: Display name of the J2EE application

Description

This message indicates that the processing to delete the resource from the J2EE application has started.

KDJE42171-I

The resource was successfully deleted from the J2EE application. (resource = aa....aa, type =bb....bb, J2EE application = cc....cc)

aa....aa: Resource display name (file name when the type is LibJar)

bb....bb: Resource type

cc....cc: Display name of the J2EE application

Description

This message indicates that the resource was successfully deleted from the J2EE application.

KDJE42174-I

The resource's properties will now be set. (display name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description

This message indicates that the processing to set properties for resource has started.

KDJE42175-I

The resource's properties were set successfully. (display name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description

This message indicates that the properties for resource were set successfully.

KDJE42176-I

The properties for the internal resource of the J2EE application will now be set. (resource = aa....aa, type = bb....bb, J2EE application = cc....cc)

aa....aa: Resource display name

bb....bb: Resource type

cc....cc: Display name of the J2EE application

Description

This message indicates that the processing to set properties for the internal resource of the J2EE application has started.

KDJE42177-I

The properties for the internal resource of the J2EE application were set successfully. (resource = aa....aa, type = bb....bb, J2EE application = cc....cc)

aa....aa: Resource display name

bb....bb: Resource type

cc....cc: Display name of the J2EE application

Description

This message indicates that the properties for the internal resource of the J2EE application were set successfully.

KDJE42178-I

The resource will now be deleted. (display name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description

This message indicates that the processing to delete the resource has started.

KDJE42179-I

The resource was deleted successfully. (display name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description

This message indicates that the resource was deleted successfully.

KDJE42180-I

The resource will now be copied. (display name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description

This message indicates that the processing to copy the resource has started.

KDJE42181-I

The resource was copied successfully. (display name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description

This message indicates that the resource was copied successfully.

KDJE42182-I

The J2EE resource adapter will now be deployed. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description

This message indicates that the deployment process of the J2EE resource adapter has started.

KDJE42183-I

The J2EE resource adapter was deployed successfully. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description

This message indicates that the J2EE resource adapter was deployed successfully.

KDJE42184-I

The J2EE resource adapter will now be undeployed. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description

This message indicates that the undeployment process of the J2EE resource adapter has started.

KDJE42185-I

The J2EE resource adapter was undeployed successfully. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description

This message indicates that the undeployment process of the J2EE resource adapter has ended.

KDJE42186-I

The J2EE resource adapter will now start. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description

This message indicates that the J2EE resource adapter will now start.

KDJE42187-I

The J2EE resource adapter started successfully. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description

This message indicates that the J2EE resource adapter started successfully.

KDJE42188-I

The J2EE resource adapter will now stop. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description

This message indicates that the processing to stop the J2EE resource adapter has started.

KDJE42189-I

The J2EE resource adapter stopped successfully. (display name =aa....aa)

aa....aa: J2EE resource adapter display name

Description

This message indicates that the J2EE resource adapter stopped successfully.

KDJE42190-I

The mail configuration will now be created. (display name = aa....aa)

aa....aa: Display name of the mail configuration

Description

This message indicates that the processing to create the new mail configuration has started.

KDJE42191-I

The mail configuration was created successfully. (display name = aa....aa)

aa....aa: Display name of the mail configuration

Description

This message indicates that the new mail configuration was created successfully.

KDJE42192-I

The connection test for the J2EE resource adapter will now be performed. (display name = aa....aa)

aa....aa: J2EE resource adapter display name

Description

This message indicates that the connection test for the J2EE resource adapter will now be performed.

KDJE42193-I

The connection test for the J2EE resource adapter has finished. (display name = aa....aa, test result = bb....bb)

aa....aa: J2EE resource adapter display name

bb....bb: Test result

Description

This message indicates that the connection test for the J2EE resource adapter has finished.

KDJE42194-I

The connection test for the data source will now be performed. (display name = aa....aa)

aa....aa: Data source display name

Description

This message indicates that the connection test for the data source will now be performed.

KDJE42195-I

The connection test for the data source has finished. (display name = aa....aa, test result = bb....bb)

aa....aa: Data source display name

bb....bb: Test result

Description

This message indicates that the connection test for the data source has finished.

KDJE42196-I

The mail configuration will now be tested. (display name = aa....aa)

aa....aa: Display name of the mail configuration

Description

This message indicates that connection test used by mail configuration will now start.

KDJE42197-I

The mail configuration test has finished. (display name = aa....aa, test result = bb....bb)

aa....aa: Display name of the mail configuration

bb....bb: Test result

Description

This message indicates that the connection test used by mail configuration has finished.

KDJE42200-E

An attempt to move the J2EE application that is to be replaced has failed. (directory or file path to be moved = aa....aa)

aa....aa: Directory or file path to be moved

Description

An attempt to move the J2EE application that is to be replaced has failed.

The reason might be because either the file under the directory to be moved or the file to be moved is in use, or the directory or the file cannot be moved because the access permissions is not available.

Action

Remove the cause of the error, and then re-execute the process.

KDJE42201-E

An attempt to import the replacement-source J2EE application has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to import the replacement-source J2EE application has failed. The import processing might have failed because the disk space available was not sufficient.

Action

See the details or the message output before this message and remove the cause due to which the import processing failed, and then re-execute the process.

For the messages in which the detailed information starts with nnnn (n is a number), see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory.

KDJE42202-E

The configurations of the J2EE application before and after the replacement do not match. (details = aa....aa)

aa....aa: Details

Description

The configurations of the J2EE application before and after the replacement do not match.

Action

See the details, modify the J2EE application so that the configurations match, and then re-execute the process. If you cannot modify, import the configuration after deleting the J2EE application to be replaced.

KDJE42203-E

An attempt to start the J2EE application after completion of replacement processing has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to start the J2EE application after completing the replacement processing has failed.

Action

See the details or the message output before this message to remove the cause due to which the start process failed, and then restart the J2EE application.

KDJE42204-E

The development environment and the J2EE server are not running on the same machine. (IP address of the machine running the development environment = aa....aa, IP address of the machine running the J2EE server = bb....bb)

aa....aa: IP address of the machine on which the development environment is running

bb....bb: IP address of the machine on which the J2EE server is running

Description

The development environment and the J2EE server are not running on the same machine.

Action

Start the development environment and the J2EE server on the same machine, and then re-execute the process.

KDJE42205-E

The update list file does not exist. (update list file path = aa....aa)

aa....aa: Update list file path

Description

The update list file does not exist.

Action

Specify the correct update list file path, and then re-execute the process.

KDJE42206-E

An attempt to analyze the update list file has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to analyze the update list file has failed.

Action

See the details to remove the cause due to which the analysis processing failed, and then re-execute the analysis processing.

KDJE42207-E

The J2EE application is not in a stopped state. (J2EE application display name = aa....aa, J2EE application mode = bb....bb, J2EE application state = cc....cc)

aa....aa: Display name of the J2EE application

bb....bb: Mode of the J2EE application

cc....cc: State of the J2EE application

Description

The J2EE application is not in a stopped state. You cannot operate only when the J2EE application is not running.

Action

Stop the J2EE application, and then re-execute the operation.

KDJE42208-E

An attempt to update the target archive file has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to update the target archive file has failed.

The update processing might have failed because the available disk space was not sufficient.

Action

See the details or the message output before this message to remove the cause due to which the creation processing failed, and then re-execute the process.

KDJE42209-I

The command lock was released because there was no request from the command for a long period. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time = dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description

This message indicates that the command lock was released because there was no request from the command for a long period.

KDJE42210-I

The command lock was released because the cjresetsv command was executed. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time = dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description

This message indicates that the command lock was released because cjresetsv command was executed.

KDJE42211-I

The command status has changed to awaiting execution. (command name = aa....aa, host name = bb....bb, number of commands awaiting execution = cc....cc)

aa....aa: Command name excluding the directory path and the extension of the command awaiting execution

bb....bb: IP address of the host requesting the command awaiting execution

cc....cc: Number of commands awaiting execution

Description

This message indicates that the command is in pending state.

KDJE42212-E

Execution of a command was refused, either because the user did not have execution permission for the command, or the command was canceled. Re-execute the command. (command name = aa....aa)

aa....aa: Command name excluding the directory path and the extension of the command that failed to execute

Description

The processing cannot be continued because the command execution permission is not available with the user.

Take action based on the following causes:

The command processing cannot be finished within the response awaiting period of the J2EE server because of high load processing

Significant communication delay occurred in the network

The command execution process is remarkably delayed

The exclusive access control of the J2EE server was released by the cjresetsv command during the processing of the command

Action

Re-execute the cancelled command.

Make sure that the exclusion release message (KDJE42209-I or KDJE42210-I) is output in the J2EE server console during the iteration and when the processing is interrupted.

Confirm the following, and then take action when the exclusive release message is displayed:

Check the command execution terminal and the network status. If any problem exists, remove it, and then re-execute the command.

When a problem does not exist in the command execution terminal and the network status, use a larger value for the setting value of the response-awaiting period (ejbserver.deploy.exclusive.lockAliveInterval) from the command defined in the user properties file for the J2EE server. Reboot the server after changing the setting value, and then re-execute the command.

If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42213-E

Execution of a command was refused because the server is awaiting shutdown. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time= dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description

Acceptance of a new command was refused because the shutdown command is pending state.

Action

Reboot the server, and then re-execute the command.

KDJE42214-E

Execution of a command was refused because the server is waiting for a GUI command to end. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time = dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description

Acceptance of a new command was refused because the GUI command is in pending state.

When the GUI command is running or is in pending state, the server stops the acceptance of a new command.

Action

After the GUI command finishes on the server, re-execute the command for which execution was refused.

KDJE42215-I

The J2EE application aa....aa will now be blocked.

aa....aa: J2EE application name

Description

The J2EE application will be blocked.

KDJE42216-I

The J2EE application aa....aa was blocked successfully.

aa....aa: J2EE application name

Description

The J2EE application was blocked successfully. As a result, a new request will not be accepted. The processing of the request being processed will continue.

KDJE42217-I

The Web application will now be blocked.

Description

The Web application will be blocked.

KDJE42218-I

The Web application was blocked successfully.

Description

The Web application was blocked successfully.

KDJE42219-I

The CTM queue will now be blocked.

Description

The CTM queue will be blocked.

KDJE42220-I

The CTM queue was blocked successfully.

Description

The CTM queue was blocked successfully.

KDJE42221-I

The front EJB will now be blocked.

Description

The front EJB will be blocked.

KDJE42222-I

The front EJB was blocked successfully.

Description

The front EJB was blocked successfully.

KDJE42223-I

The J2EE application aa....aa will now be forcibly stopped.

aa....aa: J2EE application name

Description

The J2EE application will be forcibly stopped.

KDJE42224-I

The J2EE application aa....aa was forcibly stopped.

aa....aa: J2EE application name

Description

The J2EE application was forcibly stopped.

KDJE42225-E

An attempt to forcibly stop the J2EE application aa....aa has failed.

aa....aa: J2EE application name

Description

An attempt to forcibly stop the J2EE application has failed.

Action

Use the server management command (cjlistapp) to check the state of the J2EE application.

Take action by the following methods depending on the state:

When the J2EE application is in the stopped state

No problem exists because the termination was normal.

When the J2EE application is in the forceStopFailure state

Restart the J2EE server.

For other states

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE42226-E

The property value of the UAP forcible stop function is invalid.

Description

The set value for the property of the forced termination functionality of the J2EE application is incorrect.

Action

Revise the set value of the property.

KDJE42227-E

The forcible stop cannot be executed because the property ejbserver.deploy.app.stopforcibly.disabled is true.

Description

The forcible stop of the J2EE application cannot be executed because the property ejbserver.deploy.app.stopforcibly.disabled is true.

Action

Set the property value to false, restart the J2EE server, and then execute the forcible stop.

KDJE42228-E

The display name contains invalid characters. (display name = aa....aa)

aa....aa: Display name

Description

The display name contains invalid characters. Only single byte alphanumeric characters (a~z, A~Z, 0~9) and single byte underscores (_) can be specified in the display name.

Action

Change the display name, and then re-execute the operation.

KDJE42229-E

The server refused to execute the command because the command cannot wait for other commands to end. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time = dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description

The executed command cannot wait until the termination of other commands. The reception of the command has been denied by the J2EE server on which other commands are running.

Action

Confirm that other commands are not running on the J2EE server on which the command is to executed, and then re-execute the refused commands.

KDJE42230-E

Execution of a command was refused because an another privilege command is already running. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time= dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description

Execution of a command was refused because another privilege command was already running.

Action

Confirm that another privilege command is not running on the J2EE server on which the command is to be executed, and then re-execute the refused command.

KDJE42231-E

aa....aa processing cannot continue because monitoring of the UAP execution time is disabled.

aa....aa: Process contents

Description

The processing cannot be continued because the monitoring of UAP execution time is disabled.

Action

Enable the monitoring functionality of the UAP execution time using any one of the following methods:

Set false for the property ejbserver.deploy.app.stopforcibly.disabled

Specify a number greater than 0 in the property ejbserver.ext.method_observation.interval

KDJE42232-E

aa....aa processing cannot continue because of a discrepancy between the JDK vendor bb....bb and the version cc....cc.

aa....aa: Process contents

bb....bb: JDK vendor name

cc....cc: JDK version

Description

The processing cannot continue because either the JDK vendor or the version is different.

Action

Part of the operation functionality of the J2EE application cannot be used.

When the functionality for monitoring the J2EE application execution time is in use, disable the functionality.

KDJE42233-E

A valid RAR file was not found.

Description

A valid RAR file that can be used for migrating the resource adapter was not found.

Action

Create a valid RAR file.

KDJE42234-E

The server aa....aa has not been updated.

aa....aa: Server name

Description

The resource adapter cannot be migrated because the migration of the J2EE server has not finished.

Action

After the migration of the J2EE server finishes, again migrate the resource adapter.

KDJE42235-E

Migration of the resource adapters of the old version has finished, but some resource adapters could not be migrated.

Description

An error occurred during the migration of the resource adapters.

Action

Check whether KDJE42271-E is displayed.

If displayed, see the action of KDJE42271-E.

When another error message is displayed, if required, restore from the backup.

KDJE42236-I

Processing to migrate the server will now start. (server name = aa....aa)

aa....aa: Server name

Description

This message indicates that the processing to migrate the server has started.

KDJE42237-I

Processing to migrate the server has finished. (server name = aa....aa)

aa....aa: Server name

Description

This message indicates that the processing to migrate the server has finished.

KDJE42238-I

Processing to migrate the resource adapter will now start. (resource name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description

This message indicates that the processing to migrate the resource adapter has started.

KDJE42239-I

Processing to migrate the resource adapter of the J2EE application will now start. (resource name = aa....aa, J2EE application = bb....bb)

aa....aa: Resource display name

bb....bb: J2EE application name

Description

This message indicates that the processing to migrate the resource adapter of the J2EE application has started.

KDJE42240-E

An attempt to migrate the resource adapter has failed (resource name = aa....aa, type = bb....bb, detail = cc....cc).

aa....aa: Resource display name

bb....bb: Resource type

cc....cc: Details

Description

This message indicates that an attempt to migrate the resource adapter has failed.

Action

Take action using any one of the following methods:

When error level message is displayed just before

See the action of the message displayed just before.

In the other cases

See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42241-E

An attempt to migrate the internal resource adapter of the J2EE application has failed (resource name = aa....aa, J2EE application = bb....bb, detail = cc....cc).

aa....aa: Resource display name

bb....bb: J2EE application name

cc....cc: Details

Description

This message indicates that an attempt to migrate the internal resource adapter of the J2EE application has failed.

Action

Take action using any one of the following methods:

When error level message is displayed just before

See the action of the message displayed just before.

In the other cases

See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42242-I

Migration of the resource adapter has finished. (resource name = aa....aa, type = bb....bb)

aa....aa: Resource display name

bb....bb: Resource type

Description

This message indicates that the migration of the resource adapter has finished.

KDJE42243-I

Migration of the resource adapter of the J2EE application has finished. (resource name = aa....aa, J2EE application = bb....bb)

aa....aa: Resource display name

bb....bb: J2EE application name

Description

This message indicates that the migration of the resource adapter of the J2EE application has finished.

KDJE42244-E

The file format is invalid. (file = aa....aa)

aa....aa: File name

Description

The file format is invalid.

Action

Use a valid file to migrate the resource adapter again.

KDJE42245-E

The file aa....aa was not found.

aa....aa: File name

Description

The file aa....aa was not found.

Action

Confirm that the file exists in the path.

KDJE42246-E

Resource "aa....aa" cannot start because the data source is not supported.

aa....aa: Resource display name

Description

Resource cannot start because the data source is not supported.

Action

Use the resource adapter.

KDJE42247-I

Migrating version (file = aa....aa, old version = bb....bb, new version = cc....cc).

aa....aa: File name

bb....bb: Old version

cc....cc: New version

Description

This message indicates the version of the file before and after migration.

KDJE42248-E

The file version is invalid (file = aa....aa, old version = bb....bb, new version = cc....cc).

aa....aa: File name

bb....bb: Old version

cc....cc: New version

Description

This message indicates the version of the file before and after migration when the migration processing cannot be performed.

Action

Confirm the version of the file.

KDJE42249-W

Migration of the resource adapter will now stop. (resource name = aa....aa, type = bb....bb, detail = cc....cc)

aa....aa: Resource display name

bb....bb: Resource type

cc....cc: Details

Description

This message indicates that the migration of the resource adapter will now stop.

Action

When executing the migration forcibly, specify -force option, and then re-execute the cjrarupdate command.

KDJE42250-W

Migration of the resource adapter of the J2EE application will now stop. (resource name = aa....aa, J2EE application = bb....bb, detail = cc....cc)

aa....aa: Resource display name

bb....bb: J2EE application name

cc....cc: Details

Description

This message indicates that the migration of the resource adapter of the J2EE application will now stop.

Action

When executing the migration forcibly, specify -force option, and then re-execute the cjrarupdate command.

KDJE42251-E

The status of the public directory is invalid. (type = aa....aa)

aa....aa: Resource type

Description

The status of the working directory is invalid.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE42252-I

Processing to migrate the resource adapter will now start.

Description

This message indicates that the processing to migrate the resource adapter has started.

KDJE42253-I

Migration of the resource adapter has finished.

Description

This message indicates that the migration of the resource adapter has finished.

KDJE42254-I

Processing to back up the server will now start. (server name = aa....aa, the number of file = bb....bb)

aa....aa: Server name

bb....bb: Number of files for backup

Description

This message indicates that the processing to back up the server will now start.

KDJE42255-I

Processing to back up the server has finished. (server name = aa....aa)

aa....aa: Server name

Description

This message indicates that the processing to back up the server has finished.

KDJE42257-W

An invalid property value is specified. Default value is used. (key = aa....aa, value = bb....bb, default value = cc....cc)

aa....aa: Property key

bb....bb: Set value

cc....cc: Default value

Description

The default value will be used because an invalid value was acquired from the property file.

Take action based on the following causes:

An invalid value is specified in the properties.

A value outside the valid range has been specified.

Action

Revise the set value of the property (aa....aa) of the user properties file (usrconf.properties) for the J2EE server.

KDJE42258-I

Exporting the RMI-IIOP stub for J2EE application is in progress. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description

This message indicates that the processing to export the RMI-IIOP stub for the J2EE application is in progress.

KDJE42259-I

Sending the export information of the RMI-IIOP stub for the J2EE application was successful. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description

This message indicates that sending of the export information of the RMI-IIOP stub for the J2EE application was successful.

KDJE42260-I

The J2EE application name will now be renamed. (old name = aa....aa, new name = bb....bb)

aa....aa: Old name of the J2EE application

bb....bb: New name of the J2EE application

Description

This message indicates that the J2EE application name will now be renamed.

KDJE42261-I

The J2EE application name was renamed successfully. (old name = aa....aa, new name = bb....bb)

aa....aa: Old name of the J2EE application

bb....bb: New name of the J2EE application

Description

This message indicates that the J2EE application name was renamed successfully.

KDJE42262-I

The J2EE application mode will now be changed. (J2EE application = aa....aa, old mode = bb....bb, new mode = cc....cc)

aa....aa: J2EE application name

bb....bb: Old operating mode of the J2EE application

cc....cc: New operating mode of the J2EE application

Description

This message indicates that the processing for changing the operating mode of the J2EE application has started.

KDJE42263-I

The J2EE application mode was changed successfully. (J2EE application = aa....aa, old mode = bb....bb, new mode = cc....cc)

aa....aa: J2EE application name

bb....bb: Old operating mode of the J2EE application

cc....cc: New operating mode of the J2EE application

Description

This message indicates that the operating mode of the J2EE application was changed successfully.

KDJE42264-I

The command lock will now be released because the cjresetsv command was executed. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time = dd....dd)

aa....aa: Command name excluding the directory path and extension

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description

This message indicates that the command lock will now be released because the cjresetsv command was executed.

KDJE42268-I

The J2EE application will now be replaced. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description

This message indicates that the redeployment of the J2EE application has started.

KDJE42269-I

The J2EE application was replaced successfully. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description

This message indicates that the redeployment of the J2EE application was successful.

KDJE42270-W

The EJB violates the EJB specification. : aa....aa

aa....aa: Details of the error contents

Description

This message indicates that the EJB violates the EJB specification.

Action

See the details of the error, and then take action. For details, see 7.9 List of details for KDJE42039-E and KDJE42270-W.

If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42271-E

An attempt to create a backup for the server has failed. (server name = aa....aa, detail = bb....bb)

aa....aa: Server name

bb....bb: Detailed message

Description

An attempt to create a backup has failed.

Action

See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42272-E

An attempt to export the J2EE application has failed. (J2EE application = aa....aa, detail = bb....bb)

aa....aa: J2EE application name

bb....bb: Detailed message

Description

An attempt to export the J2EE application has failed.

Action

See the details, and then take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42274-E

The setting of the reload function is invalid.

Description

The property combination for the setting of the reload functionality is invalid.

In the case of ejbserver.deploy.context.reload_scope=app, ejbserver.rmi.localinvocation.scope=all cannot be selected.

Action

Check the property setting for the reload functionality.

KDJE42277-I

The J2EE application reload processing will now start.(J2EE application = aa....aa)

aa....aa: J2EE application name

Description

The J2EE application reload processing will now start.

KDJE42278-I

The J2EE application reload processing has finished.(J2EE application = aa....aa)

aa....aa: J2EE application name

Description

The J2EE application reload processing has finished.

KDJE42280-E

The update check for reloading failed. (J2EE application = aa....aa, detail = bb....bb)

aa....aa: J2EE application name

bb....bb: Exception

Description

An exception occurred in the update check for reloading.

Action

Contact the maintenance personnel.

KDJE42284-E

The reload function cannot be used. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description

The reload command was executed when the reload functionality was disabled.

Action

Check the property (ejbserver.deploy.context.reload_scope) that sets the scope of the reload functionality.

KDJE42285-I

A file subject to reloading was not modified. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description

The reload command was executed when a file subject to reloading was not modified.

KDJE42286-E

The command cannot be executed. (J2EE application = aa....aa, reason=bb....bb)

aa....aa: J2EE application name

bb....bb: Reason

Description

The command cannot be executed because of bb....bb.

Action

Reason: stopped

The command cannot be executed because the application has stopped. Start the application.

Reason: reload failure

The command cannot be executed because an attempt to reload has failed. Perform successful reloading or reboot the J2EE server.

KDJE42288-I

A file subject to reloading was modified. (J2EE application = aa....aa, filename = bb....bb)

aa....aa: J2EE application name

bb....bb: Updated file name

Description

A file subject to reloading was modified.

KDJE42290-E

The J2EE application reload processing failed. (J2EE application = aa....aa)

aa....aa: J2EE application name

Description

An attempt to reload the J2EE application has failed.

Action

Take the action for the error message that was output before this message.

KDJE42291-I

The application directory "aa....aa" will now be imported.

aa....aa: Application directory path

Description

The application directory aa....aa will be imported.

KDJE42292-I

The application directory "aa....aa" was imported successfully.

aa....aa: Application directory path

Description

The application directory aa....aa was imported successfully.

KDJE42293-E

The J2EE application "aa....aa" contains the resource adapter.

aa....aa: Application directory path, Ear file name, or ZIP file name

Description

The J2EE application contains the resource adapter.

Action

Delete the resource adapter from the application, and then re-import.

KDJE42294-E

The J2EE application "aa....aa" contains the application client.

aa....aa: Application directory path, Ear file name, or ZIP file name

Description

The J2EE application contains the application client.

Action

Delete the application client from the application, and then re-import.

KDJE42295-E

The module name of the component "bb....bb" in J2EE application "aa....aa" is incorrect.

aa....aa: Application directory path

bb....bb: Module name of the component

Description

The module name of the component in the J2EE application is incorrect.

Action

Change the module name described in application.xml based on the generation rules of the application directory, and then re-import.

KDJE42296-E

The directory of the module "aa....aa" does not exist. The directory name must be "bb....bb".

aa....aa: Module name

bb....bb: Directory name

Description

The directory of the module aa....aa does not exist. The directory name must be bb....bb.

Action

Create the directory with a correct name based on the generation rules of the application directory, and then re-import.

KDJE42297-E

The WAR module "aa....aa" does not have a deployment descriptor.

aa....aa: Module name

Description

The WAR module does not have a DeploymentDescriptor.

Action

Check the configuration of the application directory. Deploy the WAR directory and the Deployment Descriptor correctly, and then re-import.

KDJE42298-E

The EJB-JAR module "aa....aa" does not have an annotation or a deployment descriptor.

aa....aa: Module name

Description

The EJB-JAR module does not have an Annotation or a Deployment Descriptor.

Action

Check the configuration of the application directory. Deploy the EJB-JAR directory and the Deployment Descriptor correctly, and then re-import.

KDJE42299-I

An update of the configuration file of the J2EE application "aa....aa" was detected. (file name = bb....bb) The definition information is now being reread.

aa....aa: J2EE application name

bb....bb: File name

Description

An update of the configuration file of the J2EE application was detected. The definition information is now being reread.

KDJE42300-I

The definition information of the J2EE application "aa....aa" has been reread successfully.

aa....aa: J2EE application name

Description

The definition information of the J2EE application is reread successfully.

KDJE42301-E

An attempt to reread the definition information of J2EE application "aa....aa" has failed. (detailed message = "bb....bb")

aa....aa: J2EE application name

bb....bb: Details

Description

An error was detected when rereading the definition information of the J2EE application.

Action

Modify the contents under the application directory based on the detailed message, and then re-execute the command.

KDJE42302-I

"aa....aa" will now be imported in an archive format.

aa....aa: EAR file name, ZIP file name, or WAR file name

Description

aa....aa will now be imported in an archive format.

KDJE42303-I

"aa....aa" will now be imported in an deployment directory format.

aa....aa: EAR file name or ZIP file name

Description

aa....aa will now be imported in a deployment directory format.

KDJE42304-I

The application will now be expanded into the directory "aa....aa".

aa....aa: Directory name

Description

The application will now be expanded into the directory aa....aa.

KDJE42305-E

The specified directory "aa....aa" does not exist.

aa....aa: Directory name

Description

The specified directory does not exist.

Action

Create an expanded directory, and then re-import.

KDJE42306-E

The files cannot be written to the specified directory "aa....aa".

aa....aa: Directory name

Description

The files cannot be written to the specified directory.

Action

Assign write permission, and then re-import.

KDJE42307-E

The state of a J2EE resource adapter is invalid. (display name =aa....aa)

aa....aa: Display name of the J2EE resource adapter

Description

The state of a J2EE resource adapter is invalid.

Action

Undeploy the J2EE resource adapter, then deploy it again, and then re-execute the operations. In the case the action cannot be taken, acquire the maintenance information, and then contact the maintenance personnel.

KDJE42308-E

The deployment processing has abended. An element defined by a J2EE resource is invalid. (type = aa....aa, resname = bb....bb, parent element = cc....cc, element = dd....dd, detail = ee....ee)

aa....aa: J2EE resource type

bb....bb: Display name of the J2EE resource

cc....cc: Parent element name of the invalid element

dd....dd: Invalid element name

ee....ee: Details

Description

The deployment process has abended. An element defined by a J2EE resource is invalid.

The message displayed in the details and its cause are as follows:

The element is not supported.

The element is not supported.

Action

Take action based on the details. In the case the action cannot be taken, acquire the maintenance information, and then contact the maintenance personnel.

The element is not supported.

Remove the unsupported element, and then re-execute the operation..

KDJE42309-I

Loading annotation is in progress.

Description

Loading annotation is in progress.

KDJE42310-I

Loading annotation was successful.

Description

Loading annotation was successful.

KDJE42311-E

An unsupported Java type is set. (Java type = aa....aa)

aa....aa: Java Type of @Resource

Description

Java Type set in element type() of @Resource is not supported.

Action

Use a supported Java Type.

KDJE42312-E

The occurrence count from which the declaration of the "aa....aa"annotation is defined in the EJB specification is exceeded.

aa....aa: Annotation name exceeding the occurrence count of the EJB specification

Description

The declaration of the annotation exceeds the occurrence count defined in the Deployment Descriptor.

Action

Modify the setting of annotation and match it with the occurrence count defined in the EJB specification.

KDJE42313-I

The JavaBeans resource will now start. (display name = aa....aa)

aa....aa: JavaBeans resource display name

Description

This message indicates that the JavaBeans resource will now start.

KDJE42314-I

The JavaBeans resource started successfully. (display name = aa....aa)

aa....aa: Annotation name exceeding the occurrence count of the EJB specification

Description

This message indicates that the JavaBeans resource started successfully.

KDJE42315-I

The JavaBeans resource will now stop. (display name = aa....aa)

aa....aa: JavaBeans resource display name

Description

This message indicates that the JavaBeans resource will now stop.

KDJE42316-I

The JavaBeans resource stopped successfully. (display name =aa....aa)

aa....aa: JavaBeans resource display name

Description

This message indicates that the JavaBeans resource stopped successfully.

KDJE42317-E

This JavaBeans resource "aa....aa" has been started once. Restart the J2EE server, and then try to delete the resource again.

aa....aa: JavaBeans resource display name

Description

JavaBeans resource is started once.

Action

Restart the J2EE server and delete the resource again.

KDJE42318-W

Cannot get edition information. aa....aa is used as a protocol.

aa....aa: Protocol

Description

An attempt to acquire edition information has failed. Common library might not be installed. The processing continues.

Action

Confirm that the common library is installed.

KDJE42319-E

The required file or directory does not exists. (Path= aa....aa)

aa....aa: File path

Description

The file aa....aa under the application directory that was existing during import does not exist now.

Action

Restore the file or directory that exists on the path with an error when importing, and then re-execute the command.

KDJE42320-E

Deployment has abended. The JMS resource used in the application does not support transaction. (aa....aa)

aa....aa: Resource information

Description

The deployment process has abended. The JMS resource used in the application does not support transactions.

Action

Check the transaction level of the resource adapter. In this resource adapter, the transaction support levels that can be associated with the Message-driven Bean are the LocalTransaction and XATransaction.

KDJE42321-E

Deployment has abended. The transaction support level of the JMS resource is invalid.

Description

The deployment process has abended. The transaction support level of the JMS resource is invalid.

Action

Check the transaction level of the resource adapter.

KDJE42322-E

The application directory "aa....aa" does not have a deployment descriptor.

aa....aa: Application directory path

Description

The application directory does not have META-INF/application.xml.

Action

Create a META-INF/application.xml, and then re-import.

KDJE42323-E

The specified directory "aa....aa" is not empty.

aa....aa: Application directory path

Description

The directory that you tried to expand by specifying cjimportapp -d is not empty.

Action

Delete the files existing in the directory, and then re-import.

KDJE42324-E

The deployment directory format does not support in basic mode.

Description

An attempt was made to use the expanded archive format deployment functionality in the basic mode.

Action

Import to the J2EE server of 1.4 mode.

KDJE42325-E

The J2EE application having the same application directory "aa....aa" is already exists.

aa....aa: Application directory path or WAR directory path

Description

If a J2EE application having the same directory (as shown below) as an application directory or a WAR directory already exists in the J2EE server, a command execution error occurs:

Directory specified in the -a option or the -d option of the cjimportapp command

Directory specified in the -a option of the cjimportwar command

Action

Specify a different directory.

KDJE42326-E

The J2EE application "aa....aa" using an alt-dd element cannot be imported in a deployment directory format.

aa....aa: Application directory path, EAR file name or ZIP file name

Description

The user tried to import the application directory or EAR file or ZIP file with runtime information where alt-dd element is specified as application.xml.

Action

Edit the application.xml, delete the alt-dd element, and then re-import the application.

KDJE42327-E

The EJB-JAR having same display-name "aa....aa" exists in the J2EE application "bb....bb".

aa....aa: EJB-JAR display name

bb....bb: Application directory path

Description

The EJB-JAR display name contained in the application directory created by the user is duplicated.

Action

Change the EJB-JAR display name, and then re-import.

KDJE42328-E

The WAR having same display-name "aa....aa" exists in the J2EE application "bb....bb".

aa....aa: WAR display name

bb....bb: Application directory path

Description

The WAR display name contained in the application directory created by the user is duplicated.

Action

Change the duplicated WAR display name, and then re-import.

KDJE42329-E

The application directory cannot specified in UNC path. (path = aa....aa)

aa....aa: User-specified path

Description

UNC path was specified in cjimportapp -a/-d option argument.

Action

Do not specify the directory in UNC path.

KDJE42330-I

The JavaBeans resource "aa....aa" will now be imported.

aa....aa: JavaBeans resource display name

Description

The processing to import the JavaBeans resource is in progress.

KDJE42331-I

The JavaBeans resource "aa....aa" was imported successfully.

aa....aa: JavaBeans resource display name

Description

The JavaBeans resource was imported successfully.

KDJE42332-W

The J2EE application contains the application client. The application client is not supported.

Description

The J2EE application contains the application client. The application client is not supported.

Action

Delete the coding of <module><java> of application.xml in the J2EE application, and then re-package and import.

As a result of this action, the JAR file specified in <module><java> will be treated as a library JAR. The library JARs also exist in other JAR files, and if the same classes are included, delete the JAR file specified in <module><java>.

KDJE42333-I

The ignore J2EE annotations is specified.

Description

The functionality, for excluding the annotation references in the target J2EE application, will be enabled.

KDJE42334-W

The specified ignore J2EE annotations value is not supported. (value=aa....aa)

aa....aa: Specified value

Description

The functionality, for excluding the annotation references, will be disabled.

Action

true or false can be specified. Check if the specified value is a specifiable value.

KDJE42335-W

An element defined by a J2EE resource is not supported. (filename = aa....aa, element = bb....bb)

aa....aa: Deployment Descriptor for which an unsupported element is defined

In the case of the archive format: Archive file name or entry name

In the case of the expanded archive format: Relative path from the application directory

bb....bb: Unsupported element name

Description

The element (bb....bb) specified in aa....aa is an unsupported element. The element (bb....bb) will be ignored.

Action

Remove the element (bb....bb) specified in aa....aa.

KDJE42336-E

The file of the module does not exist. (file = aa....aa)

aa....aa: File name

Description

The module file (aa....aa) does not exist.

Action

Arrange the file according to the generation rules of the application directory, and then re-import the file.

KDJE42337-E

The "aa....aa" resource adapter cannot be included in the "bb....bb" J2EE application. (details = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

cc....cc: Details

Description

The resource adapter (aa....aa) cannot be included in the J2EE application.

The message displayed in the details and its cause are as follows:

The native library file.

The resource adapter includes the native library.

Tag name = transaction-support. Tag value = XATransaction.

The transaction-support tag is XATransaction.

The resource adapter is not supported.

The resource adapter is not supported.

Action

Take action based on the details.

The native library file.

Change to a supported resource adapter. Alternatively, deploy and use as a J2EE resource adapter.

Tag name = transaction-support. Tag value = XATransaction.

Change the value to NoTransaction or LocalTransaction. Alternatively, deploy and use as a J2EE resource adapter.

The resource adapter is not supported.

Change to a supported resource adapter. Alternatively, deploy and use as a J2EE resource adapter.

KDJE42338-E

"aa....aa" was not found in the "bb....bb" J2EE application.

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

Description

The resource adapter (aa....aa) is not found in the J2EE application (bb....bb).

Action

Revise the command parameters, and then re-execute the command.

KDJE42339-I

Recovery processing for the resource adapter will now start.

Description

The recovery process of the resource adapter will start.

KDJE42340-I

Recovery processing for the resource adapter has finished.

Description

The recovery process of the resource adapter has ended.

KDJE42341-E

The specified backup RAR directory is invalid. (backup RAR directory = aa....aa)

aa....aa: Backup RAR directory

Description

An invalid backup RAR directory (aa....aa) is specified.

Action

Revise the path specified for the backup RAR directory, and then re-execute the command.

KDJE42342-E

An attempt to copy the file from "aa....aa" to "bb....bb" has failed. (details = cc....cc)

aa....aa: Copy source file name

bb....bb: Copy destination file name

cc....cc: Details

Description

An attempt to copy from file aa....aa to file bb....bb has failed.

Action

Based on the details, remove the cause of the error, and then re-execute the command.

KDJE42343-W

The resource adapter in the J2EE server "aa....aa" is not recovered, because the resource adapter configuration has been changed.

aa....aa: The J2EE server name

Description

The resource adapter in the J2EE server (aa....aa) is not recovered because the resource adapter configuration is changed.

KDJE42344-E

This application could not be imported in test mode.

Description

This application cannot be imported in the test mode.

Action

Import without specifying the test mode.

KDJE42345-E

An invalid value is specified for the tag in the deployment descriptors in the resource adapter. (resource adapter = aa....aa, tag name = bb....bb, tag value = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Tag name

cc....cc: Tag value

Description

An invalid value is specified for a tag in the Deployment Descriptor of the resource adapter (resource adapter = aa....aa, tag name = bb....bb, tag value = cc....cc).

Action

Check the tag value, and then re-execute the command.

KDJE42346-E

The aa....aa with the same display name already exists in the J2EE application. (display name = bb....bb, J2EE application = cc....cc)

aa....aa: Resource type

bb....bb: Resource display name

cc....cc: Path of the J2EE application directory

Description

The aa....aa with the same display name already exists in the J2EE application (display name = bb....bb, J2EE application = cc....cc).

Action

Change the display name of bb....bb, and then re-import.

KDJE42347-I

The resource adapter in the J2EE application will now start. (resource adapter = aa....aa, J2EE application = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

Description

The resource adapter in the J2EE application will start (resource adapter = aa....aa, J2EE application = bb....bb).

KDJE42348-I

The resource adapter in the J2EE application started successfully. (resource adapter = aa....aa, J2EE application = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

Description

The resource adapter in the J2EE application has started successfully (resource adapter = aa....aa, J2EE application = bb....bb).

KDJE42349-I

The resource adapter in the J2EE application will now stop. (resource adapter = aa....aa, J2EE application = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

Description

The resource adapter in the J2EE application will stop (resource adapter = aa....aa, J2EE application = bb....bb).

KDJE42350-I

The resource adapter in the J2EE application stopped successfully. (resource adapter = aa....aa, J2EE application = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

Description

The resource adapter in the J2EE application has stopped successfully (resource adapter = aa....aa, J2EE application = bb....bb).

KDJE42351-E

An attempt to delete the file has failed. (file name = aa....aa)

aa....aa: File name

Description

An attempt to delete the file (aa....aa) has failed.

Action

Re-execute the command.

KDJE42352-E

An attempt to set the execution authority of the file has failed. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Detailed message

Description

An attempt to set up the execution permission for the file has failed (file name = aa....aa, details = bb....bb).

Action

Based on the details, resolve what caused the error in execution permission settings, and then re-execute the command.

KDJE42353-I

The connection test for the resource adapter in the J2EE application will now be performed. (resource adapter = aa....aa, J2EE application = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

Description

A connection test will be performed for the resource adapter of the J2EE application (resource adapter = aa....aa, J2EE application = bb....bb).

KDJE42354-I

The connection test for the resource adapter in the J2EE application has finished. (resource adapter = aa....aa, J2EE application = bb....bb, test result = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Display name of the J2EE application

cc....cc: Test result

Description

The connection test for the resource adapter in the J2EE application is complete (resource adapter = aa....aa, J2EE application = bb....bb, test result = cc....cc).

KDJE42355-W

The command lock cannot be released, because the command operation has been executed in J2EE server. (command name = aa....aa, user name = bb....bb, host name = cc....cc, execution time = dd....dd)

aa....aa: Name of the command that is now running

bb....bb: OS user name at the command execution side

cc....cc: IP address at the command execution side

dd....dd: Command execution time at the command execution side (in the format of dow mon dd hh:mm:ss zzz yyyy)

Description

The command exclusion cannot be released because the command processing is executed in the J2EE server.

Action

Check if the command processing is executed in the J2EE server.

If the command processing is executed in the J2EE server, wait until the processing finishes. If the command exclusion is not released even when the processing finishes, execute the cjresetsv command again.

If the command processing is not executed in the J2EE server or if the command exclusion cannot be released even when the cjresetsv command is executed after sometime, contact maintenance personnel.

KDJE42356-E

The resource adaptor based on the Connector 1.5 specification was specified. (RAR file = aa....aa)

aa....aa: RAR file name

Description

A resource adapter conforming to Connector 1.5 specifications was specified (RAR file = aa....aa).

Action

Specify a resource adapter conforming to the Connector 1.0 specifications. When upgrading the version of a resource adapter conforming to the Connector 1.5 specifications, re-import the resource adapter, and reset the definition.

KDJE42357-W

The value of mappedName is invalid. (EJB-JAR = aa....aa, Enterprise Bean = bb....bb, annotation = cc....cc, value = dd....dd)

aa....aa: EJB-JAR display name

bb....bb: Enterprise Bean display name

cc....cc: Annotation type

dd....dd: Value

Description

The value of mappedName is invalid (EJB-JAR = aa....aa, Enterprise Bean = bb....bb, annotation = cc....cc, value = dd....dd).

Action

Check if the optional name specified in the mappedName attribute of @Stateless or @Stateful is a specifiable character string.

KDJE42358-W

The value of mappedName is invalid. (J2EE application = aa....aa, EJB-JAR = bb....bb, Enterprise Bean = cc....cc, annotation = dd....dd, value = ee....ee)

aa....aa: Display name of the J2EE application

bb....bb: EJB-JAR display name

cc....cc: Enterprise Bean display name

dd....dd: Annotation type

ee....ee: Value

Description

The value of mappedName is invalid (J2EE application = aa....aa, EJB-JAR = bb....bb, Enterprise Bean = cc....cc, annotation = dd....dd, value = ee....ee).

Action

Check if the optional name specified in the mappedName attribute of @Stateless or @Stateful is a specifiable character string. Alternatively, specify the optional name in the <optional-name> tag or the <local-optional-name> tag of the property file.

KDJE42359-E

Deployment has ended. An attempt to check the reference to the resource adapter in the J2EE Application "aa....aa" failed. (details = bb....bb)

aa....aa: J2EE application name

bb....bb: Details

Description

The deployment process has abended. An attempt to check the referencing of the resource adapter in the J2EE Application aa....aa has failed. Details = bb....bb

Action

Take action based on the detailed message. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

Not resolve resource adapter.

The display name of the resource adapter is not specified. Revise the MessageDrivenBean property file.

Not exist resource adapter.

The resource adapter cannot be found. Make sure that the resource adapter coded in the MessageDrivenBean property file is already deployed.

Not start resource adapter.

The resource adapter is not started. Make sure that the resource adapter coded in the MessageDrivenBean property file is already running.

KDJE42360-E

The path specified for the library directory is invalid. (library directory = aa....aa)

aa....aa: Library directory

Description

A file is specified in the path of the library directory.

Action

Specify a directory instead of a file in the library directory.

When the <library-directory> tag of the application.xml file or the application.xml file is omitted, the library directory will become lib.

KDJE42361-E

aa....aa cannot be included in the J2EE application. (J2EE application (name = bb....bb, version = cc....cc), aa....aa (name = dd....dd, version = ee....ee))

aa....aa: Resource type

bb....bb: Display name of the J2EE application

cc....cc: Version of the J2EE application

dd....dd: Resource display name

ee....ee: Resource version

If a Deployment Descriptor does not exist in the resource, a hyphen (-) will be displayed in the resource display name ee....ee.

Description

The resource type aa....aa (name = dd....dd, version = ee....ee) cannot be included in the J2EE application (name = bb....bb, version = cc....cc).

Action

Revise the combination of the J2EE application version and the resource version.

KDJE42362-E

The value of <module> is invalid. (module = aa....aa)

aa....aa: Value specified in the <module> tag

Description

A file that exists below the library directory was specified in the <module> tag.

Action

The JAR file in the library directory cannot be specified in the <module> tag of the file application.xml. Revise the configuration of the J2EE application.

KDJE42363-E

The value of <module> is invalid. (module = aa....aa)

aa....aa: Value specified in the <module> tag

Description

The EJB-JAR directory or WAR directory determined from the <module> tag or the files below these directories configure the library directory.

Action

Revise the configuration of the J2EE application in such a way so that the EJB-JAR directory or the WAR directory, or the files below these directories do not configure the library directory.

KDJE42364-E

The value of the aa....aa tag is invalid. (value = bb....bb)

aa....aa: Tag name

bb....bb: Value specified in the tag

Description

An invalid value is specified in a tag of application.xml when importing in the expanded archive format.

Action

Specify a permitted value in the tags of application.xml.

KDJE42365-E

The existence of the file aa....aa differs before and after the replacement. (archive file = bb....bb)

aa....aa: Deployment Descriptor file name

bb....bb: Archive file name

Description

The existence of aa....aa file is not coincident before and after the replacement do not match.

Action

After comparing the archive files and revising the J2EE application in such a way so that the existence of the Deployment Descriptor is matching, re-execute the command. If you cannot modify, import the configuration after deleting the J2EE application to be replaced.

KDJE42366-E

A resource cannot be added to a J2EE application where the application.xml is not present. (J2EE application = aa....aa, resource = bb....bb, type = cc....cc, resource file = dd....dd)

aa....aa: Display name of the J2EE application

bb....bb: Resource display name

cc....cc: Resource type

dd....dd: Resource file name

Description

A resource cannot be added to a J2EE application in which application.xml does not exist.

Action

Add a file with an extension corresponding to the resource type in a J2EE application in which application.xml does not exist.

In the case of an EJB-JAR file, the extension is .jar

In the case of a WAR file, the extension is .war

In the case of a RAR file, the extension is .rar

KDJE42367-W

The context root determined from the WAR file or directory is duplicated. (path1 = aa....aa, path2 = bb....bb, context root = cc....cc)

aa....aa: Path to the WAR file or WAR directory

bb....bb: Path to the WAR file or WAR directory

cc....cc: Context root

Description

The context root determined from the path to the WAR file or WAR directory is duplicated.

Action

Change the context root. Change the path to the WAR file or WAR directory in such a way so that the context root is not duplicated.

KDJE42368-I

The file cosminexus.xml will now be loaded.

Description

The file cosminexus.xml will be read.

KDJE42369-E

The format of the file cosminexus.xml is invalid. (Detail = aa....aa)

aa....aa: Exception information when reading fails

Description

An attempt to read the file cosminexus.xml has failed because of invalid format.

Action

The format of the file cosminexus.xml is invalid. Check if the tag configuration of the file cosminexus.xml is correct.

KDJE42370-W

An element specified in the file cosminexus.xml was not found. This element has been ignored. (element = aa....aa, value = bb....bb)

aa....aa: Element name

bb....bb: Element value

Description

Information corresponding to the element specified in cosminexus.xml is not found in the application. The set value of this element will be ignored.

Action

An element, that cannot be included in the application, is specified in cosminexus.xml. Check the cosminexus.xml file contents.

KDJE42371-E

The specified value is invalid. (element = aa....aa, value = bb....bb)

aa....aa: Element name

bb....bb: Value of the element (Nothing will be output if the value is a space. Null will be output if the element is omitted).

Description

An error exists in the element specified in cosminexus.xml.

Action

An invalid element is specified in the file cosminexus.xml included in the application. Revise the set value of the element aa....aa of the file cosminexus.xml.

KDJE42372-I

The file cosminexus.xml has been loaded.

Description

The reading of the file cosminexus.xml is complete.

KDJE42373-E

The metadata-complete attribute in the deployment descriptor in the EJB-JAR file cannot be set to "true". (J2EE application = aa....aa, EJB-JAR = bb....bb)

aa....aa: J2EE application name (a null character string in the case of the cjimportres command)

bb....bb: EJB-JAR display name

Description

True cannot be specified in the attribute metadata-complete of the Deployment Descriptor of EJB-JAR.

Action

Either specify false in the attribute metadata-complete of the Deployment Descriptor of EJB-JAR or delete the attribute metadata-complete.

KDJE42374-W

The specified display name includes non-recommended characters. (display name = aa....aa, resource type = bb....bb)

aa....aa: Display name

bb....bb: Type (J2EE Application, EJB-JAR, WAR, RAR, Enterprise Bean, Servlet or JSP, or Filter)

Description

In a J2EE server, the display name set up in the J2EE application and resource (value of the <display-name> tag of the Deployment Descriptor) is used as an identifier. When importing a WAR file in which <servlet><display-name> does not exist, the display name is set up from the <servlet><servlet-name> value.

However, this message is displayed because you can specify a period in <servlet><display-name>; however the conversion to underscore (_) does not occur.

When this message is displayed, errors might occur in another processing.

Action

Change the display name of the J2EE Application, EJB-JAR, Web application, or resource adapter or change the display name of the Enterprise Bean, Servlet or JSP, or Filter included in to the character strings having only the single-byte alphanumeric characters and underscores (_).

KDJE42375-W

An interceptor-class specified in the file deployment descriptor was not found. This interceptor-class has been ignored. (ejb-jar name = aa....aa, interceptor-class = bb....bb)

aa....aa: EJB-JAR name

bb....bb: Interceptor class name

Description

The interceptor class specified in the Deployment Descriptor was not found.

Action

Specify an existing interceptor class.

KDJE42376-E

The specified interceptor-class was not found. (ejb-jar name = aa....aa, interceptor-class = bb....bb)

aa....aa: EJB-JAR name

bb....bb: Interceptor class name

Description

The specified interceptor class was not found. An interceptor class that actually exists must be specified.

Action

Revise the configuration of the application in such a way so that the interceptor class is included in the EJB-JAR or library JAR.

KDJE42377-W

An element was specified more than once. This element has been ignored. (element = aa....aa, value = bb....bb)

aa....aa: Element name

bb....bb: Element value

Description

More than one instance of the definition information exists for the same element. The first definition of the element found in the Deployment Descriptor is used. The value bb....bb of the element aa....aa is not used.

Action

Delete the unnecessary definition information.

KDJE42378-E

A module was not found in a J2EE application. (J2EE application = aa....aa)

aa....aa: Path to the EAR file or application directory

Description

A module was not found in the J2EE application.

Action

Make sure that the module is included in the J2EE application.

KDJE42379-W

The file cosminexus.xml has not been reloaded (application name = aa....aa).

aa....aa: Application name

Description

The definition information is not reloaded even when the file cosminexus.xml is changed.

Action

When the definition information of the file cosminexus.xml is to be applied in the application, restart the application after stopping it.

KDJE42380-W

There exist one or more classes from which annotation information could not be collected. (name = aa....aa, failure count = bb....bb)

aa....aa: File name or J2EE application display name

bb....bb: Number of times when information could not be collected

Description

The annotation information could not be collected for one or more classes (name = aa....aa, failure count = bb....bb).

Action

If java.lang.NoClassDefFoundError is output in the KDJE90001-E message, and a problem exists in the execution of the J2EE application, either revise the J2EE application or change the settings of the J2EE server in such a way so that the class output in the detailed message of java.lang.NoClassDefFoundError can be referenced from the J2EE application.

KDJE42385-W

The specified method was not found. (ejb name = aa....aa, method name = bb....bb, method parameters = cc....cc)

aa....aa: EJB name

bb....bb: Method name

cc....cc: Parameter format#

# Output the parameters in the following format:

When <method-param> does not exist

A null character string ("")

When <method-param> exists

A character string in which the value of all the <method-param> tags is connected by commas (,)

Description

The method is not defined.

Action

Revise the definition information of the <method> tag.

KDJE42386-E

A file operation on a resource adapter management file of the J2EE server has failed. (operation = aa....aa, details = bb....bb)

aa....aa: Failed operation (any one of write, read, delete, or rename)

bb....bb: Exception information (none, if no exception information exists)

Description

An attempt to operate the file, that manages the status of the resource adapter below the work directory for the J2EE server, has failed.

Action

The action to be taken will differ depending on the operation performed during the occurrence of the error:

When an error occurred in the database node during the cluster configuration of the connection pool

Remove the cause of failure in the file operation by referencing the details. After removing the cause of the problem, restart the J2EE server.

When a resource adapter is deployed

Remove the cause of failure in the file operation by referencing the details. After removing the cause of the problem, restart the J2EE server. After restarting the J2EE server, check if the resource adapter exists. If the resource adapter does not exist, re-deploy it. If the resource adapter exists, check if the executed operation was successful.

When the migration command (cjenvupdate) of the J2EE server is executed

Remove the cause of failure in the file operation by referencing the details. Remove the cause of the error, and then re-execute the operation.

In cases other than above

Remove the cause of failure in the file operation by referencing the details. After removing the cause of the problem, restart the J2EE server. After restarting the J2EE server, check if the executed operation was successful.

KDJE42387-E

The entry name in the EAR file is invalid. (entry name = aa....aa, EAR file = bb....bb)

aa....aa: Entry name

bb....bb: EAR file name

Description

The entry name in the EAR file is invalid.

Action

The entry name in the EAR file indicates a higher level than the root of the application package. Change to an entry name that indicates a lower level than the root of the application package.

KDJE42388-E

The resource adapter not supported in the edition. (resource adapter = aa....aa, edition = bb....bb)

aa....aa: Display name of resource adapter

bb....bb: Edition

Description

The specified resource adapter cannot be used in this edition.

Action

Check the resource adapter document, and then use the resource adapter with a supported edition.

KDJE42389-E

The entry name in component is invalid. (entry name = aa....aa, file = bb....bb, component type = cc....cc)

aa....aa: Entry name

bb....bb: File name

cc....cc: Component type

Description

The entry name in the component is invalid.

Action

The entry name in the component indicates a higher location than the root directory. Change to an entry name indicating a lower location than the root directory.

KDJE42390-E

The start of the application containing a Web Service EJB failed. Root context-root is already used. (application name = aa....aa)

aa....aa: Display name of the application

Description

The EJB of the Web Service cannot be deployed in the context root of the root. Another J2EE application might be using the context root of the root.

Action

Make sure that the application that is using the context root of the root does not already exist. If such an application exists, change the context root so that it is not duplicated.

KDJE42391-I

Working directory for Web Service EJB is created.

Description

A work directory required for executing the EJB of the Web Service is created successfully.

KDJE42392-E

An attempt to create the directory (aa....aa) has failed.

aa....aa: Directory name

Description

An attempt to create the (aa....aa) directory has failed.

Action

The possible causes of the error are described below. If the cause is not clear, obtain the maintenance information, and then contact Maintenance Service.

Failure of the disk drive

If the disk drive has failed due to breakage of the disk drive, contact the system administrator and replace the drive.

Insufficient disk space

Secure enough disk space.

No access permission

Assign access permission.

Characters that cannot be used are used in the path name

Do not use characters that cannot be used in the path name.

The length of the file path is inappropriate

Make sure that the total number of characters of the absolute path length in which the application in the exploded archive format is deployed, the path delimiter (one character), and the relative path length specified in the webservice.container.jaxws.webservice.wsee.warname key of the user property file (usrconf.properties) is 255 characters or less.

KDJE42393-W

The J2EE application contains a aa....aa. Automatic reloading and partial reloading cannot be performed. (J2EE application name = bb....bb)

aa....aa: Component type

bb....bb: J2EE application name

Description

Automatic reloading and partial reloading cannot be used in this J2EE application.

Action

To use the reload functionality, use the cjreloadapp command.

KDJE42394-E

The J2EE application contains a aa....aa. Partial reloading cannot be performed. (J2EE application name = bb....bb)

aa....aa: Component type

bb....bb: J2EE application name

Description

Partial reloading cannot be used in this J2EE application.

Action

To switch the J2EE application, delete the application once. If you want to use the reload functionality, specify app in the property ejbserver.deploy.context.reload.scope.

KDJE42395-I

The J2EE application contains a aa....aa. All of the application components were reloaded. (J2EE application name = bb....bb)

aa....aa: Component type

bb....bb: J2EE application name

Description

All the components included in the application were reloaded.

KDJE42396-E

Test mode cannot be used in CDI applications. (J2EE application name = aa....aa)

aa....aa: J2EE application name

Description

Test mode cannot be used in CDI applications.

Action

Change the operation mode of the J2EE application to a normal mode.

KDJE42397-W

The WebServlet annotation will be ignored because the value set for the name attribute is already set for another WebServlet annotation. (WAR file = aa....aa, class name = bb....bb)

aa....aa: WAR file name

bb....bb: Class name describing the @WebServlet annotation

Description

The @WebServlet annotation will be ignored because the name attribute value in the @WebServlet annotation is duplicated in another @WebServlet annotation.

Action

Change the value of the name attribute in the @WebServlet annotation so that the value is not duplicated in another @WebServlet annotation.

KDJE42398-W

The WebFilter annotation will be ignored because the value set for the filterName attribute is already set for another WebFilter annotation. (WAR file = aa....aa, class name = bb....bb)

aa....aa: WAR file name

bb....bb: Class name describing the @WebFilter annotation

Description

The @WebFilter annotation will be ignored because the filterName attribute value in the @WebFilter annotation is duplicated in another @WebFilter annotation.

Action

Change the value of the filterName attribute in the @WebFilter annotation so that the value is not duplicated in another @WebFilter annotation.

KDJE42399-W

The class file contains one or more generic methods or generic constructors. (class name = aa....aa)

aa....aa: Class name

Description

One or more generic methods or generic constructors are used in the class file contained in the application.

Action

The use of annotations for the application server is not supported for generic methods or generic constructors.

Do not use generics in the class displayed in the message. Alternatively, delete the annotation. There is no problem if the application server does not use the corresponding annotation in this class.

KDJE42400-E

The WAR application does not support the command. (command name = aa....aa)

aa....aa: Command name

Description

The WAR application does not support this command.

Action

Delete the WAR application, import a J2EE application with EAR format, and then execute the J2EE application.

KDJE42401-E

The WAR application does not support a command option. (command name = aa....aa)

aa....aa: Command name

Description

The WAR application does not support the option of this command.

Action

Delet the WAR application, import a J2EE application, and then execute the J2EE application.

KDJE42402-W

The application name was sanitized. (application name = aa....aa)

aa....aa: Application name

Description

When the cjimportwar command is executed, if the -name option is omitted; the WAR file/WAR directory name becomes the application name. Therefore, for the application name, the characters that cannot be used in the WAR file/WAR directory are replaced with underscores.

Action

When executing the server management commands for imported a WAR application, execute the cjlistapp command, and specify the application name to be output, in the -name option, and then execute the command.

KDJE42403-W

The context root was sanitized. (context root = aa....aa)

aa....aa: Application name

Description

When the cjimportwar command is executed, if the -contextroot option is omitted; the WAR file/WAR directory name becomes the context root. Therefore, for the context root of J2EE server, the characters that cannot be used in the WAR file/WAR directory are replaced with underscores.

Action

When accessing the imported WAR application, execute the cjlistapp command, and confirm the context root to be output.

KDJE42404-I

The war directory aa....aa will now be imported.

aa....aa: WAR directory path

Description

Import the WAR directory aa....aa.

KDJE42405-I

The war directory aa....aa was imported successfully.

aa....aa: WAR directory path

Description

WAR directory aa....aa is successfully imported.

KDJE42406-E

The J2EE application that has the upper directory of the directory aa....aa already exists.

aa....aa: Application directory path or WAR directory path

Description

If the J2EE application that has the upper most directory of the below directory as the application directory or the WAR directory already exists in the J2EE server, an error occurs in the command execution:

Directory specified in the -a option or the -d option of the cjimportapp command

Directory specified in the -a option of the cjimportwar command

Action

Check that the path of the application directory or WAR directory is not included in the directory (application directory or WAR directory) that is included in the J2EE application already existing in the J2EE server, and then specify an appropriate directory.

KDJE42407-E

The war directory cannot specified in UNC path. (path = aa....aa)

aa....aa: User specified path

Description

If the UNC path is specified in the -a option of the cjimportwar command, import fails.

Action

Do not specify the UNC path in the -a option of the cjimportwar command.

KDJE42408-E

The specified directory aa....aa is invalid.

aa....aa: Path of the user specified directory

Description

If the directory immediately below the Windows drive (such as C:\) or the root directory (/) in UNIX is specified in the -a option of the cjimportwar command, the import has fails.

Action

Specify a directory that is not immediately below the Windows drive or the root directory in UNIX.

KDJE42410-E

The J2EE application that has the lower directory of the directory aa....aa already exists.

aa....aa: Application directory path or WAR directory path

Description

If the J2EE application that has the lower most directory of the directory below as the application directory or the WAR directory already exists in the J2EE server, an error occurs in the command execution:

Directory specified in the -a option or the -d option of the cjimportapp command

Directory specified in the -a option of the cjimportwar command

Action

Check that the path of the application directory or WAR directory is not included in the directory (application directory or WAR directory) that is included in the J2EE application already existing in the J2EE server, and then specify an appropriate directory.

KDJE43001-E

Error occurred during generating SQL for aa....aa.

aa....aa: EJB class name

Description

An error occurred during generating SQL for aa....aa. Table mapping is wrong.

Action

Check the access to database and correct the table mapping.

KDJE43002-E

JMS Provider(TP1 Message Queue) notified an error to Message-driven Bean container. bean=aa....aa error message=bb....bb

aa....aa: Bean name

bb....bb: Error information of the JMS provider

Description

The Message-driven Bean container detected an error from the JMS provider.

Action

Reference the error information, and remove the cause of the error in the TP1/Message Queue.

KDJE43003-E

Failed to create CMR DB Table : aa....aa.

aa....aa: Display name of DB

Description

An attempt to create the table (aa....aa) for CMR failed.

Action

See the error information displayed in the database together with this message, and then remove the cause of the failure to create the table. For the details on the error information displayed in the database, see the manual supplied with the database products.

KDJE43004-E

Failed to generate SQL for CMR table creation. CMR table name is already used. : aa....aa

aa....aa: Display name of DB

Description

An attempt to generate SQL for CMR table creation has failed because the database table name is already in use.

Action

Re-execute SQL generation.

KDJE43005-E

Failed to generate SQL for CMR table creation. Two Entity Beans participating in a particular relationship must be on the same DB product.

Description

An attempt to generate SQL for CMR table creation has failed because the Entity Beans participating in a particular relationship with CMR are on the database of different DB products.

Action

Create a table corresponding to the Entity Beans on the database of the same DB products.

KDJE43006-I

CMR DB Table: aa....aa is verified.

aa....aa: Display name of DB

Description

CMR Table aa....aa is verified.

KDJE43007-I

CMR DB Table: aa....aa is created successfully.

aa....aa: Display name of DB

Description

CMR table aa....aa is created successfully.

KDJE43008-E

Failed to verify CMR DB Table: aa....aa.

aa....aa: Display name of DB

Description

An attempt to verify CMR table aa....aa has failed.

Action

Redeploy the table. However, after redeploying, a new table is created but the used CMR information is lost.

KDJE43009-I

CMR DB Table: aa....aa is deleted successfully.

aa....aa: Display name of DB

Description

CMR table aa....aa is deleted successfully.

KDJE43010-W

CMR DB Table: aa....aa is not deleted. Table has already been deleted or format has been changed.

aa....aa: Display name of DB

Description

CMR table aa....aa cannot be deleted.

The table might be already deleted or the table format might be changed.

Action

Confirm that the table is not shared or deleted when the application is running.

KDJE43011-E

Failed to delete CMR DB Table: aa....aa.

aa....aa: Display name of DB

Description

An attempt to delete the CMR Table aa....aa has failed.

Action

When an unnecessary table remains on the database, delete it manually.

KDJE43012-E

An error occurred when creating ORB/POA. (error details = aa....aa)

aa....aa: Exception message (Exception information of Cosminexus TPBroker is mainly output)

Description

An error occurred while creating ORB/POA.

When performing the operation by fixing the communication port and IP address, the environment might not be set properly.

Action

Revise the value of vbroker.se.iiop_tp.host key and vbroker.se.iiop_tp.scm.iiop_tp.listener.port key of user property file according to the message displayed in aa....aa, and then restart the J2EE server.

Revise the values from the following viewpoint:

Does the specified port number overlap with the port number that is being used?

Is the specified port number an invalid numeric value such as a negative value and a value out of range?

Is the specified value of fixed IP address correct in terms of the IP address format?

Is a space entered before and after the specified value?

KDJE43050-E

Unexpected error occurred during deploying Stateful Session Bean.

Description

An error occurred during deploying Stateful Session Bean.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE43051-E

Unexpected error occurred during deploying CMP Entity Bean. Bean = aa....aa, Detail = bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description

An error occurred during deploying CMP Entity Bean.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43052-E

An error occurred during deploying Message Driven Bean. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description

An error occurred during the deployment of the Message Driven Bean.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43053-E

An error occurred during loading home interface or component interface. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description

An error occurred during loading home interface or component interface.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43054-E

Failed to create object which is necessary for EJB. Detail = aa....aa.

aa....aa: Details

Description

An attempt to create an object necessary for the internal processing of EJB, has failed.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43055-E

Failed to instantiate EJBHome object. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description

An attempt to instantiate the EJBHome object has failed.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43056-E

Unexpected error occurred during instantiating EJBObject.

Description

An unexpected error occurred during instantiating the EJBObject.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE43057-E

Failed to create object which is necessary for Stateful Session Bean. Detail = aa....aa.

aa....aa: Details

Description

An attempt to create the object necessary for internal processing of the Stateful Session Bean, has failed.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43058-E

Failed to create EJB-specific namespace. Bean = aa....aa.

aa....aa: Bean name

Description

An attempt to create the EJB-specific namespace has failed.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE43059-E

Failed to register EJB to namespace. Bean = aa....aa, Type = bb....bb.

aa....aa: Bean name

bb....bb: type of namespace

Description

An attempt to register an EJB to namespace has failed.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE43060-E

Failed to instantiate Stateless Session Bean. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description

An attempt to instantiate the Stateless Session Bean has failed.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43061-E

An exception occurred in callback method aa....aa.bb....bb. Detail = cc....cc.

aa....aa: Bean name

bb....bb: Callback method name

cc....cc: Details

Description

An exception occurred in the user code that was called back due to extended instance-generation in Stateless Session Bean or Singleton Session Bean.

Action

See the method information and the details described in the message, and remove the cause of exception.

KDJE43062-E

Failed to instantiate Entity Bean. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description

An attempt to instantiate the Entity Beans has failed.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43063-E

An exception occurred in callback method aa....aa.bb....bb Detail = cc....cc.

aa....aa: Bean name

bb....bb: Callback method name

cc....cc: Details

Description

An exception occurred in the user code called back as an extension of generating instances for Entity Bean.

Action

See the method information and the details described in the message, and remove the cause of exception.

KDJE43064-E

Failed to create MDB container. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description

An attempt to create MDB container has failed.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43065-E

An exception occurred in callback method aa....aa.bb....bb. Detail = cc....cc.

aa....aa: Bean name

bb....bb: Callback method name

cc....cc: Details

Description

An exception occurred in the user code called back as an extension of generating instances for Message Driven Bean.

Action

See the method information and the details described in the message, and remove the cause of exception.

KDJE43066-E

Failed to connect to JMS service. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description

An attempt to connect to JMS service has failed.

The status of the resource adapter might be invalid.

Action

Restart the resource adapter, and then redeploy the J2EE application.

KDJE43067-E

Unexpected error occurred during generating stubs for bean interface. Detail = aa....aa.

aa....aa: Details

Description

An unexpected error occurred during generating the stubs for bean interface.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43068-E

Unexpected error occurred during creating implementation for bean. Detail = aa....aa.

aa....aa: Details

Description

An unexpected error occurred during creating the implementation class for bean.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43069-E

Unexpected error occurred during compiling container generated java source files. Detail = aa....aa.

aa....aa: Details

Description

An unexpected error occurred during compiling the generated Java source files.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43070-E

Unexpected error occurred during deploying EJB. Detail = aa....aa.

aa....aa: Details

Description

An unexpected error occurred during deploying the EJB.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43071-E

Unexpected error occurred during starting EJB. Detail = aa....aa.

aa....aa: Details

Description

An unexpected error occurred during EJB startup.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43072-I

J2EE Server connecting to CTM...

Description

The J2EE Server is connecting to CTM.

When the CTM functionality is installed in Enterprise Edition and ejbserver.ctm.enabled=true, the J2EE Server establishes connection with CTM and initializes during start-up. When the J2EE Server fails to establish connection with CTM and initialize, the J2EE server cannot be started.

Action

When the CTM functionality is not required and if you want to start the J2EE server, start it with ejbserver.ctm.enabled=false.

KDJE43073-I

No CTM mode: CTM initialization skipped. To deploy CTM application, start J2EE Server with CTM mode.

Description

CTM initialization was skipped.

When ejbserver.ctm.enabled=false, the J2EE Server will not connect to CTM and initialize during start-up. The application that uses CTM cannot be deployed in the J2EE Server started in this state.

Action

In order to deploy an application that uses CTM, set ejbserver.ctm.enabled=true (CTM integration is enabled) and start the J2EE Server.

KDJE43074-E

Failed to start CTM mode. If CTM function is not necessary, start J2EE Server with No CTM mode.

Description

An attempt to start in the CTM mode has failed.

If an attempt to connect to CTM and initialize fails, the J2EE Server will fail to start.

Action

If you want to use the CTM functionality, confirm that CTM is running and that the properties required for connecting to CTM are set, and then restart the J2EE Server.

When the CTM functionality is not required and if you want to start the J2EE Server, set ejbserver.ctm.enabled=false and start the J2EE Server.

KDJE43075-E

Failed to create object necessary for finder/select method of Entity Bean. Bean = aa....aa, Method = bb....bb, Detail = cc....cc.

aa....aa: Bean name

bb....bb: Method name

cc....cc: Details

Description

An attempt to create an object necessary for the execution of the finder or select method of Entity Bean has failed.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43076-E

Failed to get object necessary to generate SQLs. Detail = aa....aa.

aa....aa: Details

Description

An attempt to acquire the object of the J2EE server required to generate SQLs has failed.

The J2EE server might not be running properly.

Action

Confirm that the J2EE server is running. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43077-E

Failed to connect to J2EE Server. Detail = aa....aa

aa....aa: Details

Description

An error occurred when communicating with the J2EE Server.

The J2EE server might not be running properly.

Action

Confirm that the J2EE server is running. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43078-E

Failed to parse EJB QL. Detail = aa....aa

aa....aa: Details

Description

An attempt to generate an SQL from EJB QL has failed.

An error exists in the syntax of EJB QL.

Action

See the details, and then modify EJB QL.

KDJE43079-E

Unexpected error occurred during generating SQLs for CMP Entity Bean. Detail = aa....aa

aa....aa: Details

Description

An unexpected error occurred during generating SQLs for CMP Entity Bean.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43080-I

Pass-by-reference is defined. Bean: aa....aa.

aa....aa: Bean name

Description

Pass-by-reference is defined in Bean.

KDJE43081-E

Cannot set Entity Bean as CTM Bean.

Description

The Entity Bean cannot be set as a CTM Bean because the CTM functionality does not support Entity Beans.

Action

Do not use a CTM in the Entity Bean.

KDJE43082-E

Cannot set Message Driven Bean as CTM Bean.

Description

The Message Driven Bean cannot be set as a CTM Bean because the CTM functionality does not support Message Driven Bean.

Action

Do not use a CTM in the Message Driven Bean.

KDJE43083-E

Cannot set Stateful Session Bean as CTM Bean.

Description

The Stateful Session Bean cannot be set as a CTM Bean because the CTM functionality does not support Stateful Session Bean.

Action

Do not use a CTM in the Stateful Session Bean.

KDJE43084-E

aa....aa: Pooled instances max value should be more than Parallel Count.

aa....aa: Bean name

Description

A value greater than the max value of Pooled instance cannot be set in Parallel Count because Bean instances will become insufficient.

Action

Set the max value of Pooled instances to a value greater than the Parallel Count.

KDJE43085-E

Exception occurred in registering aa....aa with queue:bb....bb. cc....cc not found in NameSpace.

aa....aa: Bean name

bb....bb: Queue name

cc....cc: Bean name

Description

An error occurred in registering aa....aa with queue (bb....bb).

cc....cc was not found in Name Space.

Action

Confirm that the local CORBA naming service is running, and then redeploy.

KDJE43086-E

Exception occurred in registering aa....aa with queue:bb....bb. cc....cc HomeObject not found.

aa....aa: Bean name

bb....bb: Queue name

cc....cc: Bean name

Description

An attempt to acquire the EJBHomeObject reference while deploying the Bean with the specified CTM scheduling, failed.

An unusual error occurred.

Action

Contact the maintenance personnel.

KDJE43087-E

J2EE Server: No CTM mode. Restart J2EE Server after starting CTM.

Description

The J2EE Server is running in the No CTM mode.

CTM is not running. CTM must be running to use the scheduling functionality of CTM.

Action

Confirm that CTM is running, and then restart the J2EE Server.

KDJE43088-E

No CTM bean in aa....aa. More than one bean should be scheduling-enabled.

aa....aa: Application name

Description

No CTM Bean exists in the application (aa....aa).

More than one CTM Bean needs to be set.

Action

Set Enable scheduling for more than one Stateless Session Bean.

KDJE43089-E

Exception occurred in creating queue:aa....aa. CTM API MSG=bb....bb

aa....aa: Queue name

bb....bb: Detailed message

Description

An attempt to create queue (aa....aa) has failed.

Action

Take action based on the contents of the details.

KDJE43090-E

Number Format Exception: Parallel Count=aa....aa.

aa....aa: Parallel Count

Description

Number Format Error occurred because the numeric value is not entered for Parallel Count.

Action

Enter a numeric value in the specified range.

KDJE43091-E

Exception occurred in activating queue:aa....aa. CTM API MSG=bb....bb

aa....aa: Queue name

bb....bb: Detailed message

Description

An error occurred in activating the queue (aa....aa).

Action

Take action based on the contents of the details.

KDJE43092-I

CTM mode: CTM connection established.

Description

CTM connection is established and the J2EE Server is started in the CTM mode.

To deploy an application in which CTM usage is specified, the J2EE server must be started in the CTM mode.

KDJE43093-E

Failed to start CTM mode: Internal Error.

Description

An attempt to start the CTM mode has failed.

Action

Contact the maintenance personnel.

KDJE43094-E

Failed to start CTM mode: CTM not installed properly.

Description

The CTM functionality might not be installed or might not be installed properly.

Action

Confirm that CTM is installed properly. If CTM is not installed properly, re-install it.

KDJE43095-I

CTM mode stopped. J2EE Server disconnected CTM.

Description

The CTM mode is stopped.

The J2EE server is disconnected from CTM.

This message is displayed when the J2EE Server started in the CTM mode is stopped normally because the connection to CTM is disconnected.

KDJE43096-E

aa....aa does not have remote interface. Remote interface is required to enable scheduling.

aa....aa: Bean name

Description

aa....aa does not have remote interface.

Bean that does not have remote interface is not subject to scheduling by CTM.

Action

Remote interface is required to enable the CTM scheduling for the Bean.

KDJE43097-E

Unexpected error occurred after starting EJB. Bean = aa....aa, Detail = bb....bb.

aa....aa: Bean name

bb....bb: Detailed message

Description

An unexpected error occurred in the processing after EJB startup.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43098-I

aa....aa is registered with queue:bb....bb successfully.

aa....aa: Bean name

bb....bb: Queue name

Description

aa....aa was registered with queue (bb....bb).

This message is displayed when the Bean in which enable-scheduling is specified, is deployed successfully.

KDJE43099-I

Queue:aa....aa is activated successfully.

aa....aa: Queue name

Description

This message is output when an application using a CTM is deployed successfully or when a batch server using a CTM is registered successfully.

KDJE43100-I

Queue:aa....aa is deactivated successfully.

aa....aa: Queue name

Description

This message is output when an application using a CTM is undeployed successfully or when a batch server using a CTM is deleted successfully.

KDJE43101-E

Unexpected exception occurred while starting CTM application:aa....aa Detail=bb....bb.

aa....aa: Application name

bb....bb: Detailed message

Description

An unexpected exception occurred during a CTM application (aa....aa) startup.

Action

Contact the maintenance personnel.

KDJE43102-E

An error occurred when accessing a database. (error details = aa....aa)

aa....aa: Exception message (Exception information mainly related to database is output)

Description

An exception occurred when accessing a database.

The state probably does not allow access to the database.

Action

Based on the details, revise the environment settings to access the database, Remove the cause of the error, and then re-execute the process.

KDJE43103-E

An error occurred when getting information for connect database. (error details = aa....aa)

aa....aa: Items considered as cause and exception message

Description

An exception occurred when the user tried to acquire information for connecting to the database.

The Data-source or database connector is not set properly.

Action

Based on the details, revise the settings of the data-source or database connector, Remove the cause of the error, and then re-execute the process.

KDJE43104-E

Unexpected error occurred when getting information for database. (error details = aa....aa)

aa....aa: Exception message

Description

An unexpected error occurred when getting information for database.

The environment for accessing the database might not be set properly or the internal processing might have performed an unexpected operation.

Action

Based on the details, determine the action. If you do not understand the cause, contact the maintenance personnel.

KDJE43105-E

Exception occurred in setting Parallel Count to queue:aa....aa. CTM API MSG=bb....bb

aa....aa: Queue name

bb....bb: Detailed message

Description

An exception occurred when setting the Parallel Count for the queue (aa....aa).

Action

Take action based on the details.

KDJE43106-E

Unexpected exception occurred while stopping CTM application:aa....aa. Detail=bb....bb.

aa....aa: Application name

bb....bb: Details of the exception

Description

An unexpected exception occurred while stopping the CTM application (aa....aa).

Action

Contact the maintenance personnel.

KDJE43107-E

Unexpected exception occurred while finalizing CTM.

Description

An unexpected exception occurred while finalizing the CTM.

Action

Contact the maintenance personnel.

KDJE43108-E

Failed to start CTM Application:aa....aa. CTM not installed properly.

aa....aa: Application name

Description

An attempt to start a CTM Application (aa....aa) has failed.

The CTM functionality might not be installed or might not be installed properly.

Action

Check whether CTM is installed properly and if not, install it properly.

KDJE43109-E

Unexpected error occurred during deploying EJB-JAR. EJB-JAR = aa....aa, Detail = bb....bb.

aa....aa: display-name of EJB-JAR

bb....bb: Detailed message

Description

An unexpected error occurred during deploying the EJB-JAR.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43110-E

Unexpected error occurred during starting EJB-JAR. EJB-JAR = aa....aa, Detail = bb....bb.

aa....aa: display-name of EJB-JAR

bb....bb: Detailed message

Description

An unexpected error occurred during EJB-JAR startup.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43111-E

Exception occurred in registering aa....aa. CTM API MSG=bb....bb

aa....aa: Bean name

bb....bb: Detailed message

Description

An error occurred while registering aa....aa in CTM.

Action

See the details, and then take action.

KDJE43112-E

An exception occurred during deactivation of the CTM queue: aa....aa.

aa....aa: CTM queue name

Description

An error occurred during deactivation of the CTM queue (aa....aa).

Action

When restarting the J2EE application connected to the CTM queue where an error occurred, restart the J2EE Server, and then restart the application.

KDJE43113-E

Timeout occurred during awaiting the method completion of the bean: aa....aa.

aa....aa: Bean name

Description

A timeout occurred while awaiting the method completion of the Bean (aa....aa).

Action

When restarting the J2EE application, containing the Bean with an error, restart the J2EE server, and then restart the application.

KDJE43114-E

An exception occurred during terminating JMS connection or session of the bean: aa....aa.

aa....aa: Bean name

Description

An exception occurred while terminating JMS connection and JMS session of Message-driven Bean (aa....aa).

Action

When restarting the J2EE application, containing the Bean with an error, restart the J2EE server, and then restart the application.

KDJE43115-W

No CTM mode: CTM not installed properly.

Description

The J2EE server is running in the No CTM mode. When CTM is to be used, confirm that CTM is installed properly.

Action

When CTM is to be used, confirm that CTM is installed properly. if not, install it properly.

KDJE43116-I

The Remove timer of Stateful Session Bean has been started. (application = aa....aa, bean = bb....bb, removal timeout [min] = cc....cc)

aa....aa: J2EE application name

bb....bb: Enterprise Bean name

cc....cc: Timeout attribute value (Value set in Removal timeout (Units: Minutes))

Description

The timeout monitoring of Stateful Session Bean is started with the set timeout value (cc....cc) for the Enterprise Bean (bb....bb) in the J2EE application (aa....aa).

KDJE43117-I

The instance of Stateful Session Bean was removed by the Remove timer. (application = aa....aa, bean = bb....bb, removed instances = cc....cc)

aa....aa: J2EE application name

bb....bb: Enterprise Bean name

cc....cc: Number of removed instances

Description

The instances of (cc....cc) of the Enterprise Beans (bb....bb) in the J2EE application (aa....aa) were deleted by the timeout monitoring of Stateful Session Bean.

KDJE43118-E

The value of aa....aa is invalid. The ejb invoking cannot be performed. (value = bb....bb)

aa....aa: Property name

bb....bb: Specified value

Description

The EJB cannot be invoked because the value specified in the system property aa....aa is invalid.

Action

For J2EE Server

Set a correct value, and then restart the server.

For Web container (servlet engine mode)

Stop the server, set a correct value, and then restart the server.

For EJB client application

Stop the process, set a correct value, and then re-execute the process.

For a batch application

After stopping the batch execution command, set up the correct value in the user property file of the batch application, and then re-execute the command.

KDJE43119-I

The thread for Remove timer has been started.(remove scan interval [min] = aa....aa)

aa....aa: Interval for monitoring the timeout

Description

The timeout monitoring thread is started.

KDJE43120-I

The thread for Remove timer has not been started.(remove scan interval [min] = 0)

Description

The timeout monitoring thread is not started.

KDJE43121-W

The specified remove scan interval exceeds upper limit. The maximum value(153722867280912min) of scan interval will be used.

Description

The specified interval for monitoring the timeout has exceeded the upper limit.

The maximum value (153722867280912 minutes) of the interval for monitoring the timeout will be used.

KDJE43122-W

Invalid remove scan interval : aa....aa. The default value(5min) of remove scan interval will be used.

aa....aa: Value specified in property

Description

The interval for monitoring the timeout (aa....aa) is invalid.

The default value (5 minutes) of the interval for monitoring the timeout will be used.

KDJE43123-W

The specified remove scan interval is less than lower limit. The thread for Remove timer has not been started.

Description

The timeout monitoring thread is not started as the specified interval for monitoring the timeout is less than the lower limit.

KDJE43124-I

The Remove timer of Stateful Session Bean has not been started.(application = aa....aa, bean = bb....bb, removed timeout = cc....cc)

aa....aa: J2EE application name

bb....bb: Enterprise Bean name

cc....cc: Timeout attribute value (Value set in Removal timeout. Units: Minutes)

Description

The timeout monitoring of Stateful Session Bean is not started for the Enterprise Bean (bb....bb) in the J2EE application (aa....aa).

KDJE43125-W

The Remove timer of Stateful Session Bean has not been started. Since remove scan interval is zero or less value.(application = aa....aa, bean = bb....bb, removed timeout = cc....cc)

aa....aa: J2EE application name

bb....bb: Enterprise Bean name

cc....cc: Timeout attribute value (Value set in Removal timeout. Units: Minutes)

Description

Zero or a value less than zero is set in the interval for monitoring the timeout.

The timeout monitoring of Stateful Session Bean is not started for the Enterprise Bean (bb....bb) in the J2EE application (aa....aa).

KDJE43126-E

Unexpected error occurred while generating interface implementation for bean aa....aa. Detail=bb....bb

aa....aa: Enterprise Bean name

bb....bb: Details

Description

An unexpected exception occurred while generating interface implementation class for Enterprise Bean (aa....aa).

Action

See the detailed message, and then take action. Check whether any other error message is displayed and if it is displayed, take action.

If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43127-E

Unexpected error occurred during awaiting the method completion of the bean aa....aa. Detail=bb....bb

aa....aa: Enterprise Bean name

bb....bb: Details

Description

A timeout occurred during awaiting the method completion of the Enterprise Bean (aa....aa).

Action

When the J2EE application, containing the Enterprise Bean with an error, is to be restarted, once restart the J2EE Server, and then restart the application.

KDJE43128-I

Maximum instances for bean aa....aa set to bb....bb .

aa....aa: Bean name

bb....bb: Maximum number or "unlimited" of EJB objects that can be generated concurrently

Description

The maximum number of EJB objects that can be generated concurrently was specified. In the case of "unlimited", actually there are 2147483647 objects.

KDJE43129-I

Instantiating home for bean aa....aa.

aa....aa: Bean name

Description

Instantiating home for Bean (aa....aa).

KDJE43130-E

The request has refused because of the bean was blockaded. (application = aa....aa, bean = bb....bb)

aa....aa: Application name

bb....bb: Bean name

Description

The request was refused because the bean was locked.

Action

Start the J2EE application containing the Bean with an error, and then execute the client.

KDJE43131-I

Registering bean aa....aa to namespace.

aa....aa: Bean name

Description

Registering Bean (aa....aa) to namespace.

KDJE43132-I

Deploying bean aa....aa.

aa....aa: Bean name

Description

Deploying bean (aa....aa).

KDJE43133-I

Bean aa....aa deployed.

aa....aa: Bean name

Description

Bean (aa....aa) is deployed.

KDJE43134-I

Starting bean aa....aa.

aa....aa: Bean name

Description

Starting bean (aa....aa).

KDJE43135-I

Bean aa....aa started.

aa....aa: Bean name

Description

Bean (aa....aa) is started.

KDJE43136-I

Bean aa....aa stopped.

aa....aa: Bean name

Description

Bean (aa....aa) is stopped.

KDJE43137-I

Bean aa....aa undeployed.

aa....aa: Bean name

Description

Bean (aa....aa) is undeployed.

KDJE43138-E

Unexpected error occurred during instantiating EJBLocalObject.

Description

An unexpected error occurred during instantiating the EJBLocalObject.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE43139-E

Failed to start CTM Application:aa....aa. CTM definition is not found.

aa....aa: Application name

Description

The CTM integration definition related to the application was not found.

Action

Confirm that the CTM integration is defined for each application, and then restart the application.

KDJE43140-E

Failed to start CTM Application:aa....aa, Bean:bb....bb. CTM definition is not found.

aa....aa: Application name

bb....bb: Bean name

Description

The CTM integration definition related to the bean was not found.

Action

Confirm that the CTM integration is defined for each Bean, and then restart the application.

KDJE43141-E

Exception occurred in getting CTMQueueManager to start CTM Application:aa....aa. CTM API MSG=bb....bb

aa....aa: Application name or batch server name

bb....bb: Details of the exception

Description

An exception occurred in getting the CTMQueueManager to start the CTM application.

Action

Take action based on the contents of the details.

KDJE43142-E

Exception occurred in setting Queue Length to queue:aa....aa. CTM API MSG=bb....bb

aa....aa: Queue name

bb....bb: Details of the exception

Description

An exception occurred in setting schedule queue length.

Action

Take action based on the contents of the details.

KDJE43143-E

An attempt to blockade the CTM queue aa....aa has failed.

aa....aa: Queue name

Description

An attempt to lock the CTM queue has failed.

Action

Restart the J2EE Server, and then restart the J2EE application connected to the CTM queue in which an error occurred.

KDJE43144-E

Failed to get a bean instance. Application: aa....aa, Bean: bb....bb, Instance Timeout: cc....cc

aa....aa: Application name

bb....bb: Bean name

cc....cc: Set value of the timeout for acquiring instances

Description

An attempt to acquire a bean instance for processing a request within the set period has failed.

When this message is displayed frequently, the maximum value of instance pool might not match with multiple requests.

Action

Revise the setting of the upper-limit value of the instance pool, and then reset the property file.

When bb....bb is a Stateless Session Bean, revise the value of the following tag of HITACHI Session Bean Property file:

<stateless>

+ <pooled-instance>

+ <maximum>

When bb....bb is Entity Bean, revise the value of the following tag of HITACHI Entity Bean Property file:

<pooled-instance>

+ <maximum>

KDJE43145-E

Exception occurred in getting queue:aa....aa. CTM API MSG=bb....bb

aa....aa: Queue name

bb....bb: Detailed message

Description

An attempt to acquire the queue (aa....aa) has failed.

Action

Take action based on the contents of the details.

KDJE43146-E

Exception occurred while generating source files. (Bean=aa....aa, Class=bb....bb, Detail=cc....cc)

aa....aa: Bean name

bb....bb: Class name

cc....cc: Detailed message

Description

An exception occurred while generating the source file.

Action

See the details, and then take action. Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE43147-E

The AroundInvoke method threw an invalid exception that is not permitted by the business method. (AroundInvoke: class = aa....aa, method = bb....bb. BusinessMethod: bean = cc....cc, method = dd....dd)

aa....aa: AroundInvoke method definition class name

bb....bb: AroundInvoke method name

cc....cc: Bean name

dd....dd: Business method name

Description

The AroundInvoke method threw an invalid exception that is not permitted by the business method

Action

Check whether the AroundInvoke method throws an application exception not permitted by the business method.

KDJE43148-I

The EJB timer was created. (EJB name = aa....aa)

aa....aa: EJB name (Specification value of ejb-name tag)

Description

The EJB timer was created.

KDJE43149-I

The EJB timer was cancelled. (EJB name = aa....aa)

aa....aa: EJB name (Specification value of ejb-name tag)

Description

The EJB timer was cancelled.

KDJE43150-I

The EJB timer was deleted. (EJB name = aa....aa)

aa....aa: EJB name (Specification value of ejb-name tag)

Description

The EJB timer was deleted.

KDJE43151-I

The timeout method was invoked. (EJB name = aa....aa)

aa....aa: EJB name (Specification value of ejb-name tag)

Description

The timeout method was invoked.

KDJE43152-E

A method of the timer service was invoked from an unpermitted EJB method. (EJB name = aa....aa, calling EJB method = bb....bb, called timer service method = cc....cc)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Invoker method

cc....cc: Method of the invoked Timer Service

Description

A method of the Timer Service was invoked from an unpermitted EJB method.

Action

The method of Timer Service is not permitted to be executed from the invocation source. Confirm that the execution of the EJB method invoking the Timer Service method is permitted, and then take action.

KDJE43153-E

The EJB timer does not exist yet. (EJB name = aa....aa, calling EJB method = bb....bb, called timer service method = cc....cc)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Invoker method

cc....cc: Method of the invoked Timer Service

Description

The EJB timer already does not exist because it was cancelled or deleted. The EJB timer that does not exist cannot be operated.

Action

An attempt is made to operate the EJB timer that was already cancelled or deleted. Check the problem, and take action.

KDJE43154-E

There is an invalid value in an argument of the createTimer method of the TimerService class. (EJB name = aa....aa, calling EJB method = bb....bb, invalid argument = cc....cc, invalid argument value = dd....dd)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Invoker method

cc....cc: Invalid argument (initial duration, initial expiration, or interval duration)

dd....dd: Value of the invalid argument

Description

The value of relative time is negative and reference of absolute date is null or the time specified as absolute time in the argument of createTimer method of TimerService class is before January 1, 1970, 0 Hour 0 Minute 0 Second. These values cannot be specified.

Action

Confirm that the arguments passed to the createTimer method of TimerService class satisfy the following values, and then resolve the problem:

Relative time is 0 or a positive value

Reference of absolute time is not null

Date of absolute time is January 1, 1970, 0 Hour 0 Minute 0 Second onwards

KDJE43155-W

Invocation of the timeout method failed and will be retried. (EJB name = aa....aa, retry count = bb....bb)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Count of retry after the timeout method

Description

The timeout method failed due to one of the following reason:

The timeout method has thrown an exception.

Transaction of the container management of the timeout method has rolled back during the timeout method.

After retry interval has elapsed, the timeout method will be re-invoked.

Action

Confirm the following and accordingly take action:

When the timeout method throws an exception, remove the cause of exception.

When the transaction of the container management rolls back during the timeout method, remove the cause of the roll-back.

KDJE43156-E

The retry count for the timeout method reached the limit. Retries have stopped. (EJB name = aa....aa, retried count = bb....bb)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Count of retry of the timeout method

Description

The timeout method failed due to one of the following reason:

The timeout method has thrown an exception.

Transaction of the container management of the timeout method has rolled back during the timeout method.

Retry process is not performed since it has exceeded the upper limit.

Action

Check any one of the followings, and then take action:

When the timeout method throws an exception, remove the cause of exception.

When the transaction of the container management rolls back during the timeout method, remove the cause of the roll-back.

KDJE43157-W

The value of a timer service property is invalid. The default value will be used. (property name = aa....aa, specified value = bb....bb, default value = cc....cc)

aa....aa: Property name

bb....bb: Value set in property

cc....cc: Default value of property

Description

The value of property used by the Timer Service is invalid. The Timer Service uses the default value as the property value.

Action

Check the setting of property, and then set the appropriate value.

KDJE43158-E

An unsupported transaction attribute was specified for the timeout method. (EJB name = aa....aa, transaction attribute = bb....bb)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Transaction attribute

Description

An unsupported transaction attribute was specified for the timeout method.

Action

Specify the transaction attribute of the timeout method properly.

KDJE43159-E

The timer service cannot be used from the unsupported bean type. (EJB name = aa....aa, bean type = bb....bb)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Bean type

Description

The Timer Service cannot be used from the unsupported Bean type.

Action

Use the Timer Service from the Bean type in which its usage is permitted.

KDJE43160-W

The EJB timer was cancelled during execution of the timeout method. (EJB name = aa....aa)

aa....aa: EJB name (Specification value of ejb-name tag)

Description

The timeout method was terminated but the EJB timer was cancelled during execution of the timeout method.

KDJE43161-W

The container-managed transaction was rolled back because the EJB timer was cancelled during execution of the timeout method. (EJB name = aa....aa)

aa....aa: EJB name (Specification value of ejb-name tag)

Description

The timeout method was terminated but the transaction of the timeout method was rolled back because the EJB timer was cancelled during execution of the timeout method.

KDJE43162-E

A method of the timer service cannot be executed because the EJB timer has not been created. (method = aa....aa)

aa....aa: Method name

Description

An attempt was made to execute a method of Timer class for the EJB timer that is not created. When the EJB timer is not created, the method of Timer class cannot be executed for that EJB timer.

Action

Execute the method of EJB timer after concluding the transaction for creating the EJB timer or execute the method of EJB timer under the management of transaction that creates the EJB timer

KDJE43163-E

A method cannot be executed because the transaction is inactive. (method = aa....aa)

aa....aa: Method name

Description

An attempt was made to execute the method when the transaction is inactive. The transaction is inactive because the transaction has timed out.

Action

Revise the settings so that the method is executed before a transaction timeout occurs or set the transaction timeout period longer than the method execution period.

KDJE43164-E

The EJB timer cannot be created because the timeout method for the EJB is not defined. (EJB name = aa....aa, calling EJB method = bb....bb)

aa....aa: EJB name (Specification value of ejb-name tag)

bb....bb: Invoker method

Description

You can invoke the createTimer method of the TimerService class only from the Bean in which the timeout method is defined.

Action

When using the Timer Service from EJB, define the timeout method in that EJB.

KDJE43165-W

An invalid property value is specified (aa....aa = bb....bb). The default value (cc....cc) will be used.

aa....aa: Property name

bb....bb: Specified value

cc....cc: Default value

Description

The property value is invalid. The default value will be used.

Action

Specify a valid property value.

KDJE43166-E

An invalid property has been specified. (property name = aa....aa, value = bb....bb)

aa....aa: Property name

bb....bb: Specified value

Description

A mistake exists in the value specified in the property.

Action

Specify the correct value in the property, and then start the J2EE server.

KDJE43167-E

An attempt was made to use an interface that is not provided by the resource adapter using an MDB. (EJB name = aa....aa, resource name = bb....bb, interface name = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Interface name

Description

An attempt is made to use an interface that is not provided by the resource adapter, in the Message-driven Bean.

Action

Make sure that the interface specified in the <message-driven>-<messaging-type> tag of ejb-jar.xml is supported by the resource adapter.

KDJE43168-E

An error occurred during creation of an ActivationSpec instance. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Exception character string

Description

An exception occurred during creation of ActivationSpec instance.

Action

Make sure that the class name specified in the <activationspec-class> tag of ra.xml is correct, by checking the processing of the default constructor of the corresponding class.

KDJE43169-E

An attempt to set a configuration property for ActivationSpec has failed. (EJB name = aa....aa, resource name = bb....bb, property name = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Property name

Description

An attempt to set up a property in ActivationSpec has failed.

Action

Make sure that the setup of properties in the <message-driven>-<activation-config> tag of ejb-jar.xml is correct, by checking the documents of the resource adapter.

KDJE43170-E

An error occurred in the method ActivationSpec#validate. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Exception character string

Description

An exception occurred in the ActivationSpec#validate method.

Action

Make sure that the setup of properties in the <message-driven>-<activation-config> tag of ejb-jar.xml is correct, by checking the documents of the resource adapter.

KDJE43171-E

A required configuration property has not been set for ActivationSpec. (EJB name = aa....aa, resource name = bb....bb, property name = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Property name

Description

A mandatory property is not specified during the setup of properties in ActivationSpec.

Action

Make sure that the setup of properties in the <message-driven>-<activation-config> tag of ejb-jar.xml is correct, by checking the documents of the resource adapter.

KDJE43172-E

An attempt to cast an ActivationSpec class to javax.resource.spi.ActivationSpec has failed. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Exception character string

Description

An attempt to perform casting to javax.resource.spi.ActivationSpec from the class specified as ActivationSpec has failed.

Action

Check the source for providing the resource adapter.

KDJE43173-E

An attempt to associate ActivationSpec and javax.resource.spi.ResourceAdapter has failed. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Exception character string

Description

An attempt to correlate ActivationSpec with javax.resource.spi.ResourceAdapter has failed.

Action

Check the source that provides the resource adapters.

KDJE43174-E

An error occurred in the method ResourceAdapter#endpointActivation. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Details of the exception

Description

An exception occurred during the execution of endpointActivation of the resource adapter.

Action

Make sure that no problem exists in the settings of the Message-driven Bean or the resource adapter.

Revise the settings, and then restart the Message-driven Bean or the resource adapter.

KDJE43175-W

An error occurred in the method ResourceAdapter#endpointDeactivation. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Details of the exception

Description

An exception occurred during the execution of endpointDeactivation of the resource adapter.

Action

Revise the settings of the Message-driven Bean or the resource adapter.

KDJE43176-E

The XAResource object is specified as the argument of the method MessageEndpointFactory#createEndpoint. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Details of the exception

Description

XAResource is specified as an argument of the createEndpoint method of MessageEndpointFactory.

XAResource cannot be specified as an argument of createEndpoint because the XA transaction is not supported.

Action

Change the settings of the resource adapter so as to specify null in the argument of the createEndpoint method of MessageEndpointFactory, and then restart the resource adapter.

KDJE43177-E

The resource adapter used the message endpoint after execution of the method endpointDeactivation. (EJB name = aa....aa, resource name = bb....bb, details = cc....cc)

aa....aa: EJB name

bb....bb: Application display name: Resource display name

cc....cc: Details of the exception

Description

The resource adapter used the end point after the execution of the endpointDeactivation method.

Action

Check the source of providing the resource adapter.

KDJE43178-E

An exception occurred during loading interceptor class. aa....aa is not found.

aa....aa: Class name (specified value of the <interceptor-class> tag)

Description

An exception occurred while the interceptor class was being loaded.

Action

Make sure that the class name specified in the <interceptor-class> tag is correct.

KDJE43179-W

A transaction was automatically rolled back. (Transaction=aa....aa)

aa....aa: Transaction information

Description

Transaction rollback occurred automatically.

Action

Make sure that the transaction has concluded in the program.

KDJE43186-W

A null object was specified as the argument of the method MessageEndpointFactory#createEndpoint. (EJB name = aa....aa, method = bb....bb, method_params = cc....cc, resource name = dd....dd)

aa....aa: EJB name

bb....bb: Method name

cc....cc: Method argument

dd....dd: Resource display name

Description

null is specified in an argument of the createEndpoint method of MessageEndpointFactory. A transaction will not start when the EJB container executes a method of the Message-driven Bean.

Action

To start a transaction during the execution of a method of the Message-driven Bean, revise the settings of the resource adapter.

To prevent the output of the message, set the transaction attribute to be specified in the method of the Message-driven Bean to NotSupported.

KDJE43200-I

Cleaning up aa....aa async tasks for EJB bb....bb.

aa....aa: Number of deleted processing results of the asynchronous method

bb....bb: EJB name

Description

aa....aa processing results of the EJB bb....bb asynchronous method will be deleted. This message is output when the processing results of the asynchronous method of the EJB executed by remote invocation are deleted during the cleanup processing executed when the application is stopped.

KDJE43201-W

The value of an asynchronous property is invalid. The default value will be used. (property name = aa....aa, specified value = bb....bb, default value = cc....cc)

aa....aa: Property name

bb....bb: Specified value

cc....cc: Default value

Description

The default value will be used because the following asynchronous invocation properties are incorrectly specified in the cosminexus.xml file:

max-thread-pool-size

min-thread-pool-size

thread-pool-keep-alive

result-timeout-value

Action

Specify the correct asynchronous invocation properties.

KDJE43202-I

EJB asynchronous call result cannot be referenced. Timeout for the result of asynchronous call might be occurred.

Description

The objects in the processing results of the EJB asynchronous method were deleted due to timeout; therefore, the results cannot be referenced.

KDJE43203-I

Cleaning up async task (Task ID: aa....aa).

aa....aa: Object in the processing results of the EJB asynchronous method

Description

The processing results of the asynchronous method executed by remote invocation will be cleaned up.

KDJE43204-E

Cyclical dependency: aa....aa. The cyclical dependency graph is as follows bb....bb

aa....aa: Singleton Session Bean with cyclical dependency

bb....bb: Cyclical dependency

Description

A cyclical dependency exists in the @DependsOn annotation of the Singleton Session Bean.

Action

Remove the cyclical dependency from the @DependsOn annotation.

An example of cyclical dependency is as follows:

Example

@Singleton
@DependsOn("B")
class A {..}

@Singleton
@DependsOn("A")
class B{..}

KDJE43205-E

Singleton is unavailable because its original initialization failed. (EJB name = aa....aa)

aa....aa: EJB name

Description

An attempt was made to access a Singleton Session Bean that was not initialized properly.

Action

Remove the cause due to which the initialization of Singleton Session Bean failed.

The possible causes are as follows:

DI failure

Failure in the processing of the lifecycle callback method

KDJE43206-W

The schedule associated with the calendar based timer already expired. (EJB name = aa....aa, calling EJB method = bb....bb, schedule = cc....cc)

aa....aa: EJB name

bb....bb: Calling method name

cc....cc: Expired schedule

Description

The schedule expression specified in the createCalendarTimer method is already expired. Therefore, this timer will not time out.

Action

Specify a schedule expression that has not expired.

KDJE43207-E

There is an invalid value in an argument of the createSingleActionTimer method of the TimerService class. (EJB name = aa....aa, calling EJB method = bb....bb, invalid argument = cc....cc, invalid argument value = dd....dd)

aa....aa: EJB name

bb....bb: Method name

cc....cc: Argument type

dd....dd: Value

Description

The value for an argument of the createSingleActionTimer method is invalid.

Action

Check whether the arguments of the createSingleActionTimer method are appropriate.

KDJE43208-E

There is an invalid value in an argument of the createIntervalTimer method of the TimerService class. (EJB name = aa....aa, calling EJB method = bb....bb, invalid argument = cc....cc, invalid argument value = dd....dd)

aa....aa: EJB name

bb....bb: Calling method name

cc....cc: Argument type

dd....dd: Value

Description

An argument of the createIntervalTimer method is invalid.

Action

Check whether the arguments of the createIntervalTimer method are correct.

KDJE43209-E

The ScheduleExpression used in the createCalendarTimer method of the TimerService class is incorrect. (EJB name = aa....aa, calling EJB method = bb....bb, invalid argument = cc....cc, cause = dd....dd)

aa....aa: EJB name

bb....bb: Calling method name

cc....cc: Argument type

dd....dd: Invalid attribute and its value

Description

The schedule expression specified in the createCalendarTimer method of the TimerService class is incorrect.

Action

Check whether the attributes, such as hours and minutes, specified as the schedule are correct.

KDJE43210-E

Carendar based timers or automatic timers can invoke this method. (EJB name = aa....aa, calling EJB method = bb....bb, called javax.ejb.Timer method = cc....cc)

aa....aa: EJB name

bb....bb: Calling method name

cc....cc: Invoked Timer Service method

Description

A timer that is neither a calendar-based timer nor a timer that is auto-generated in the @Schedule annotation invoked the getSchedule() method.

Action

Check whether the invoked timer is a calendar-based timer or a timer that is auto-generated in the @Schedule annotation.

KDJE43211-W

No more timeout is there for this Timer. (EJB name = aa....aa, timer schedule = bb....bb)

aa....aa: EJB name

bb....bb: Timer schedule

Description

This timer will not time out.

Action

Check whether the timer settings are correct.

For example, if @Schedule(year ="2012", month="1", dayOfMonth="1", hour="17") is operated in 2011, deploy is successful and a timer that will time out in 2012/1/1 17:00:00 is generated. This timer is deleted after the 2012/1/1 17:00:00 timeout, but this message is displayed if you execute the getNextTimeout method just before the timer is deleted.

KDJE43216-E

Illegal Reentrant Access: Attempt to make a loopback call on a Write Lock method while a Read lock is already held. (Write Lock method = aa....aa, EJB name = bb....bb)

aa....aa: Method name for which a WRITE lock is specified

bb....bb: EJB name

Description

An attempt was made to execute a method defining WRITE in the @Lock annotation from a method defining READ in the @Lock annotation.

Action

Check whether the method lock is defined properly.

KDJE43217-E

The Lock is not acquired within the time limit. (Time=aa....aa, TimeUnit=bb....bb, EJB name = cc....cc)

aa....aa: Timeout value

bb....bb: Unit of timeout value

cc....cc: EJB name

Description

The lock could not be acquired within the specified limit.

Action

Check whether the specified timeout value is appropriate. Increase the timeout value as and when required.

KDJE43218-E

Illegal synchronous loopback call during Singleton initialization would have resulted in deadlock. (EJB name = aa....aa)

aa....aa: EJB name

Description

Initialization of the Singleton Session Bean failed because during the initialization, there was an invalid loopback invocation that might cause a deadlock.

During the initialization of a Singleton Session Bean, initialization was re-executed for the same Singleton Session Bean.

Action

Check whether the initialization processing is being executed for the same Singleton Session Bean from the @PostConstruct annotation method.

If a different Singleton Session Bean is being invoked from the @PostConstruct annotation method, the dependency based on the @DependsOn annotation becomes invalid and this message is displayed. The invalid example is as follows:

Example

@DependsOn("SingletonA")
@Singleton
@Startup
public class SingletonB implements BIntf {
}

@Singleton
public class SingletonA implements AIntf {
 @EJB
 BIntf b;
 @PostConstruct
 void init() {
  b.doB();
 }
}

KDJE43219-E

Client is not authorized for this invocation. Illegal non-business method access on no-interface view. (class name = aa....aa, method = bb....bb)

aa....aa: EJB name

bb....bb: Method name

Description

A method that is not a business method was invoked from the client.

Action

Do not invoke a method that is not a business method from the client.

KDJE43220-W

The schedule associated with the automatic timer is either already expired or invalid. (EJB name = aa....aa, schedule = bb....bb)

aa....aa: EJB name

bb....bb: Schedule

Description

An already expired schedule or an invalid schedule is specified in the timer that is auto-generated in the @Schedule annotation; therefore, the timer does not time out.

The respective examples are as follows:

Already expired schedule

@Schedule(year="1983")

Invalid schedule

@Schedule(year="2011", month="2", dayOfMonth="31")#

# Invalid because February does not have 31 days.

Action

Check whether the schedule format is correct.

KDJE43223-I

Cleaning up async task (Task ID: aa....aa), as timeout for Asynchronous call result is occurred.

aa....aa: Task ID

Description

The processing results (task ID: aa....aa) of the asynchronous method will be cleaned up because the asynchronous invocation results timed out.

KDJE43224-W

The values of asynchronous properties are invalid. The property value for max-thread-pool-size should be greater than or equal to the property value for min-thread-pool-size. Default values will be used for both properties. (property name = aa....aa, specified value = bb....bb, default value = cc....cc and property name = dd....dd, specified value = ee....ee, default value = ff....ff)

aa....aa: Property name

bb....bb: Value specified in aa....aa

cc....cc: Default value of aa....aa

dd....dd: Property name

ee....ee: Value specified in dd....dd

ff....ff: Default value of dd....dd

Description

The values specified in the asynchronous invocation properties min-thread-pool-size and max-thread-pool-size have the relationship min-thread-pool-size > max-thread-pool-size. Therefore, the default values will be used for both the properties.

The error also occurs in the following cases:

When the default value is used because one of the properties is omitted, and the property value becomes min-thread-pool-size > max-thread-pool-size due to the specification of the other value

In this case, the default value of the property is displayed as the value specified for the omitted property.

When the default value is used because an invalid value is specified for one of the properties, and the property value becomes min-thread-pool-size > max-thread-pool-size due to the specification of the other value

In this case, the default value of the property is displayed as the value specified for the property with an invalid value.

Action

Specify the correct value so that the specified value has the min-thread-pool-size ≤ max-thread-pool-size relationship.

KDJE45000-E

Unexpected error occurred during updating user or role information.

Description

An unexpected error occurred during updating user or role information.

Action

Contact the maintenance personnel.

KDJE45001-E

Failed to update user information.

Description

An attempt to update user information has failed.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE45002-E

Failed to update role information.

Description

An attempt to update role information has failed.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE47000-I

Specified url schema aa....aa is converted into default url schema bb....bb

aa....aa: URL schema name for compatibility

bb....bb: Default URL schema name

Description

Specified URL schema is converted into default schema.

KDJE47001-E

Could not initialize namespace. Reason = aa....aa

aa....aa: Reason for occurrence

Description

An attempt to initialize namespace has failed.

The messages output as reason for occurrence (aa....aa) and their cause are as follows:

Naming Service is not found. Start Naming Service and J2EE Server again.

The naming service might not be started.

Could not initialize ORB. Check the ORB version and setting.

ORB settings might not be correct or the version of ORB being used might be different.

Unexpected exception occurred. Please contact system administrator.

An unexpected problem such as the naming service stopped during the start of J2EE Server might have occurred.

Action

Take action according to the reason for occurrence.

Naming Service is not found. Start Naming Service and J2EE Server again.

Adjust the value of ejbserver.naming.startupWaitTime and ejbserver.naming.startupRetryCount and restart the naming service and the J2EE Server.

Could not initialize ORB. Check the ORB version and setting.

Confirm that the ORB setting is correct or ORB version being used is correct.

Unexpected exception occurred. Please contact system administrator.

Restart the naming service and the J2EE Server.

If the problem is not resolved, contact the maintenance personnel.

KDJE47100-E

Could not find the naming service list.

Description

The naming service list cannot be found.

The value of ejbserver.jndi.namingservice.group.list is not specified.

Action

Specify the value correctly.

KDJE47101-E

The group name aa....aa has already existed in the naming service group list.

aa....aa: Search group name

Description

Search group name (aa....aa) already exists.

You cannot specify the same group name in the ejbserver.jndi.namingservice.group.list.

Action

Delete the group name with same name from ejbserver.jndi.namingservice.group.list.

When same names are specified, they are treated as one group.

KDJE47102-E

Invalid group name is specified.name=aa....aa.

aa....aa: Search group name

Description

Search group name (aa....aa) is invalid.

Characters other than alphanumeric characters (A-Z, a-z, 0-9) and underscore (_) might be used for the group name.

Action

Specify the correct group name.

KDJE47103-E

Could not find the provider urls in the group name aa....aa.

aa....aa: Search group name

Description

The provider URLs cannot be found in the search group (aa....aa).

Provider url is not specified in ejbserver.jndi.namingservice.group.GROUP_NAME.providerurls.

Action

Specify the provider URL in ejbserver.jndi.namingservice.group.Specify-group-name.providerurls correctly.

KDJE47104-E

Invalid provider url is specified.name=aa....aa.

aa....aa: Provider URL

Description

The specified provider URL (aa....aa) is invalid.

An error exists in the syntax of provider URL.

Action

Specify a correct provider URL.

KDJE47105-E

Could not find the group name aa....aa defined in the naming service list.

aa....aa: Search group name

Description

The search group name (aa....aa) defined in the naming service list cannot be found.

Provider URL is not defined for the search group name defined in ejbserver.jndi.namingservice.group.list.

Action

Define a provider URL for the search group name defined in ejbserver.jndi.namingservice.group.list.

KDJE47106-W

Since the group name is not specified, search all naming services in the naming service list.

Description

The search group name is not specified; therefore, all CORBA naming services in the naming service list will be searched.

Correct value is not specified in ejbserver.jndi.namingservice.groupname.

Action

Specify a correct value in ejbserver.jndi.namingservice.groupname.

KDJE47107-I

Naming cache is off.

Description

Naming cache is OFF.

KDJE47108-W

Invalid property value is specified aa....aa=bb....bb. Default value is used. (default value = cc....cc)

aa....aa: Property name

bb....bb: Specified value

cc....cc: Default value

Description

The specified value of property (aa....aa) is invalid. The default value (cc....cc) will be used.

Action

Specify a correct value.

KDJE47109-I

Naming cache is cleared regularly.

Description

Naming cache is cleared regularly.

KDJE47110-I

Start to use the naming service : providerurl = aa....aa.

aa....aa: Provider URL

Description

Start to use the naming service of provider URL (aa....aa).

KDJE47111-I

Stop to use the naming service : providerurl = aa....aa.

aa....aa: Provider URL

Description

Stop to use the naming service of provider URL (aa....aa).

KDJE47112-E

A fatal error occurred during a JNDI method call. Restart the J2EE server and the naming service.

Description

A fatal error occurred during a JNDI method call.

An unexpected situation such as memory insufficiency might have occurred.

Action

Restart the J2EE server and the CORBA naming service.

KDJE47113-I

The specified properties were loaded. (ejbserver.ext.jndi.providerURL.list = aa....aa, ejbserver.ext.jndi.serverName.list = bb....bb, ejbserver.ext.jndi.list.initializeInterval = cc....cc)

aa....aa: Specified value of ejbserver.ext.jndi.providerURL.list

bb....bb: Specified value of ejbserver.ext.jndi.serverName.list

cc....cc: Specified value of ejbserver.ext.jndi.list.initializeInterval

Description

The specified properties were read (ejbserver.ext.jndi.providerURL.list = aa....aa, ejbserver.ext.jndi.serverName.list = bb....bb, ejbserver.ext.jndi.list.initializeInterval = cc....cc).

KDJE47114-E

The property aa....aa does not exist. The looking up cannot be performed.

aa....aa: Property name

Description

The property aa....aa does not exist. A lookup cannot be performed.

Action

Specify the appropriate value to the property.

KDJE47115-E

The value of aa....aa is empty. The looking up cannot be performed.

aa....aa: Property name

Description

The value of the property aa....aa is blank (""). A lookup cannot be performed.

Action

Specify the appropriate value to the property.

KDJE47116-E

The value of aa....aa is invalid. The looking up cannot be performed. (value = bb....bb)

aa....aa: Property name

bb....bb: Specified value of aa....aa

Description

The value of property aa....aa is invalid. A lookup cannot be performed (value = bb....bb).

Action

Specify the appropriate value to the property.

KDJE47117-E

The number of the specified server names and provider URLs must be equal. The looking up cannot be performed.

Description

The number of the specified server names and provider URLs is different. A lookup cannot be performed.

Action

Specify the appropriate value to the property.

KDJE47118-W

The looking up to aa....aa failed. The next candidate server is bb....bb.

aa....aa: Server name

bb....bb: Server name

Description

An attempt to look up aa....aa has failed. The next search candidate is bb....bb.

KDJE47119-E

The looking up to aa....aa failed.

aa....aa: Server name

Description

An attempt to look up aa....aa has failed.

Action

All servers might have encountered errors. Revise the environment.

KDJE47120-E

The object named aa....aa was not found.

aa....aa: Name

Description

An object named aa....aa was not found.

Action

The server might have encountered an error. Revise the environment.

KDJE47121-E

The specified lookup name is invalid. The looking up cannot be performed. (name = aa....aa)

aa....aa: Name

Description

The specified name is invalid. A lookup cannot be performed (name = aa....aa).

Action

Specify a correct name.

KDJE47500-E

Startup of the J2EE server will be cancelled because the specified naming service aa....aa has already started. Stop the running naming service aa....aa, and then restart the J2EE server.

aa....aa: Provider URL

Description

Startup of the J2EE server will be cancelled because the specified naming service (aa....aa) has already started.

Action

Stop the running naming service, and then restart the J2EE server.

KDJE47501-I

The naming service aa....aa will now start in bb....bb mode.

aa....aa: Provider URL

bb....bb: Naming service startup mode (manual, automatic, or inprocess)

Description

The naming service (aa....aa) will now start in bb....bb mode.

KDJE47502-I

The naming service has started.

Description

The naming service has started.

KDJE47503-E

Startup of the J2EE server will now stop because an error occurred during startup processing of the naming service. Check the J2EE server's running environment, and then restart the J2EE server. (error details = aa....aa)

aa....aa: Error details

Description

Startup of the J2EE server will now stop because an error occurred during startup processing of the naming service.

Action

See the error details, remove the cause of the error, and then restart the J2EE server.

KDJE47504-I

Processing will wait aa....aa seconds for the naming service to bb....bb.

aa....aa: Wait time set in ejbserver.naming.startupWaitTime key

bb....bb: Naming service wait type (search process or startup process)

Description

Processing will wait for aa....aa seconds because the naming service is being searched or started (bb....bb).

KDJE47505-I

Retry count is aa....aa times.

aa....aa: Count of retry to confirm the startup of naming service and is set in ejbserver.naming.startupRetryCount key

Description

The count of retry for confirming the startup status of naming service is aa....aa times.

KDJE47600-E

Could not bind the object with the name aa....aa, because another object with the same name has already existed in the naming service.

aa....aa: User-specified name

Description

The object with user-specified name (aa....aa) cannot be registered because another object with the same name already exists in the naming service.

When a distributed object or a context with a name is registered, the name already registered in the naming service cannot be used.

However, even if the name does not match completely, there are cases when the object can be registered and when the object cannot be registered. Each case is described below:

When the object can be registered

After assigning an optional name "A/B/C" to a certain object and deploying it, and if another object is assigned an optional name "A/B/D" and deployed, this message will not be displayed and the object can be registered without any problem. This is only because the context "A/B" with same name is used therefore another object that was newly registered is not recognized..

When the object cannot be registered

After assigning an optional name "A/B/C" to a certain object and deploying it, if another object is assigned an optional name "A/B/C/D" and deployed, this message will be displayed and the object cannot be registered. This is because an attempt is made to register the context with a name even though the distributed object is already registered in "A/B/C", therefore when another object is newly registered, it is recognized as another object.

Action

Check the erroneous user-specified name (aa....aa), change it to another name, and then re-execute the process.

KDJE47601-E

The mail configuration cannot be changed because a J2EE application status is "running". (resource name = aa....aa)

aa....aa: J2EE resource display name

Description

The mail attribute cannot be changed because a J2EE application status is "running".

Action

Stop all the running J2EE applications, and then set the resource attributes.

KDJE47602-I

The optional name was registered. (resource name = aa....aa, optional name = [bb....bb])

aa....aa: J2EE resource display name

bb....bb: Optional name

Description

The optional name assigned to the J2EE resource was registered in the namespace.

When the optional name is registered multiple times, it is displayed as "optA, optB, optC" in bb....bb.

KDJE47603-I

The optional name was deleted. (resource name = aa....aa, optional name = [bb....bb])

aa....aa: J2EE resource display name

bb....bb: Optional name

Description

The optional name given to the J2EE resource was deleted from the namespace.

When optional name is deleted multiple times, it is displayed as "optA, optB, optC" in bb....bb.

KDJE47604-E

A J2EE resource cannot be stopped or deleted because a J2EE application status is "running". (resource name = aa....aa)

aa....aa: J2EE resource display name

Description

A J2EE resource cannot be stopped or deleted because a J2EE application status is running.

Action

Stop or delete the resource after stopping all the running J2EE applications.

KDJE47605-I

The optional name was registered. (Enterprise Bean display name = aa....aa, type = bb....bb, optional name = cc....cc)

aa....aa: Enterprise Bean display name

bb....bb:

remote: Remotely invoked EJB

local: Locally invoked EJB

cc....cc: Optional name

Description

The optional name given to the Enterprise Bean was registered in the name space.

KDJE47606-I

The optional name was deleted. (Enterprise Bean display name = aa....aa, type = bb....bb, optional name = cc....cc)

aa....aa: Enterprise Bean display name

bb....bb:

remote: Remotely invoked EJB

local: Locally invoked EJB

cc....cc: Optional name

Description

The optional name given to the Enterprise Bean was deleted from the name space.

KDJE47607-W

The element value is invalid. (EJB-JAR = aa....aa, Enterprise Bean = bb....bb, annotation = cc....cc, element = dd....dd, value = ee....ee)

aa....aa: EJB-JAR display name

bb....bb: Enterprise Bean display name

cc....cc: Annotation

dd....dd: Attribute

ee....ee: Value

Description

The attribute value is invalid (EJB-JAR = aa....aa, Enterprise Bean = bb....bb, annotation = cc....cc, attribute = dd....dd, value = ee....ee).

Action

Revise the value of the attribute.

KDJE47608-E

The value of the mapped-name tag is invalid. (J2EE application = aa....aa, EJB-JAR = bb....bb, Enterprise Bean = cc....cc, value = dd....dd)

aa....aa: Display name of the J2EE application

bb....bb: EJB-JAR display name

cc....cc: Enterprise Bean display name

dd....dd: Value

Description

The value of the <mapped-name> tag is invalid (J2EE application = aa....aa, EJB-JAR = bb....bb, Enterprise Bean = cc....cc, value = dd....dd).

Action

Check if the optional name specified in the mappedName attribute of @Stateless or @Stateful is a specifiable character string. Alternatively, specify the optional name in the <optional-name> tag or the <local-optional-name> tag of the property file.

KDJE47701-I

A reference to an EJB object was registered in the Portable Global JNDI namespace. (ejbname = aa....aa, jndi name = [bb....bb])

aa....aa: Bean name (<ejb-name>)

bb....bb: JNDI name

Description

A reference to an EJB object is registered in the namespace with the Portable Global JNDI name. If multiple Portable Global JNDI names are registered, the names are displayed as java:global/xxx, java:global/yyy in bb....bb.

KDJE47709-W

The namespace for the Portable Global JNDI name was re-created because a namespace with the same name remains in the naming service. (name = aa....aa, jndi name = bb....bb)

aa....aa: Application display name

bb....bb: JNDI name

Description

The namespace for the Portable Global JNDI name was re-created because a namespace with the Portable Global JNDI name remains in the CORBA naming service operated by another process.

The possible causes are as follows:

The J2EE server was terminated forcibly.

The communication with the naming service failed when the J2EE application was being stopped.

Action

There is no problem because the namespace is re-created automatically. However, if this phenomenon occurs frequently, contact maintenance personnel.

KDJE47710-W

The specified application name is invalid. All objects in this application will not be bound as Portable Global JNDI names. (name = aa....aa, application name = bb....bb)

aa....aa: Application display name

bb....bb: Standard application name

Description

The standard application name contains characters that cannot be specified.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

However, action is required if one of the following cases is applicable:

If there is a client that looks up the objects in this application using the Portable Global JNDI name.

If a resource reference is defined in this application using a name beginning with java:app or java:module.

Action

If the objects must be registered in the Portable Global JNDI name for this application, take the following action to change the standard application name:

If <application-name> of application.xml is specified

Correct the value specified in <application-name> and then re-import.

If <application-name> of application.xml is not specified (if application.xml is omitted)

Correct the EAR file name (application directory name in the exploded archive format) and then re-import.

Note that if the objects need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47711-W

The specified module name is invalid. All objects in this module will not be bound as Portable Global JNDI names. (uri = aa....aa, module name = bb....bb)

aa....aa: Module URI

bb....bb: Standard module name

Description

The module name contains characters that cannot be specified.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

However, action is required if one of the following cases is applicable:

If there is a client that looks up the objects in this module using the Portable Global JNDI name.

If a resource reference is defined in this module using a name beginning with java:module.

Action

If the objects must be registered in the Portable Global JNDI name for this module, take the following action to change the standard module name:

For EJB-JAR modules

If <module-name> of ejb-jar.xml is specified

Correct the value specified in <module-name>, re-import, and then execute the module.

If <module-name> of ejb-jar.xml is not specified (if ejb-jar.xml is omitted)

Correct the EJB-JAR file name (EJB directory name in the exploded archive format) and then re-import.

For Web modules (Web application)

If <module-name> of web.xml is specified

Correct the value specified in <module-name> and then re-import.

If <module-name> of web.xml is not specified (if web.xml is omitted)

Correct the WAR file name (WAR directory name in the exploded archive format) and then re-import.

For resource adapter modules

Correct the RAR file name and then re-import.

Note that if the objects need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47712-W

The specified ejb-name is invalid as a Portable Global JNDI name. (ejbname = aa....aa)

aa....aa: Bean name (<ejb-name>)

Description

The EJB Bean name (<ejb-name>) contains characters that cannot be specified as the Portable Global JNDI name.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

However, action is required if there is a client that looks up this EJB object using the Portable Global JNDI name.

Action

If this EJB object must be registered in the Portable Global JNDI name, take the following action to change the EJB Bean name:

If <ejb-name> of ejb-jar.xml is specified

Review, and if necessary revise, the value specified for <ejb-name>.

If the Bean name is specified in the name attribute of the annotation

Review, and if necessary revise, the value specified for the name attribute.

If you change the Bean name, modify the calling lookup name of that Bean.

Note that if the EJB object need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47713-W

The Portable Global JNDI name of the bean is too long. (ejbname = aa....aa, jndi name = bb....bb)

aa....aa: Bean name (<ejb-name>)

bb....bb: JNDI name

Description

The Bean name or the fully-qualified-interface-name is too long. Therefore, the Portable Global JNDI name cannot be registered in the java:global/<app-name>/<module-name>/<ejb-name>!<fully-qualified-interface-name> format.

The length of <ejb-name>!<fully-qualified-interface-name> must be no more than 255 characters.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

Furthermore, there is no problem even if you use only the Portable Global JNDI name omitting the fully-qualified-interface-name.

However, action is required if there is a client that looks up this EJB object using the Portable Global JNDI name with the fully-qualified class name.

Action

If this EJB object must be registered in the Portable Global JNDI name with the fully-qualified class name, take the following action to change the EJB Bean name or the fully-qualified-interface-name.

If <ejb-name> of ejb-jar.xml is specified

Specify length-of-the-value-specified-for-<ejb-name> + length-of-the-fully-qualified-interface-name + 1 in 255 characters or less.

If the Bean name is specified in the name attribute of the annotation

Specify length-of-the-value-specified-for-name-attribute + length-of-the-fully-qualified-interface-name + 1 in 255 characters or less.

If the interface is omitted, the fully-qualified class name of the Bean class is applied instead of the fully-qualified-interface-name.

If you change the Bean name and the fully-qualified class name of the business interface, modify the calling lookup name of that Bean.

Note that if the EJB object need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47720-W

The objects in the J2EE application could not be bound as Portable Global JNDI names because there is already an application in the naming service with the same application name. (name = aa....aa, application name = bb....bb)

aa....aa: Application display name

bb....bb: Standard application name

Description

An application with the same standard application name already exists in the naming service. Therefore, the objects in the J2EE application could not be registered in the Portable Global JNDI name.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

However, action is required if one of the following cases is applicable:

If there is a client that looks up the objects in this application using the Portable Global JNDI name.

If a resource reference is defined in this application using a name beginning with java:app or java:module.

Action

If the objects must be registered in the Portable Global JNDI name for this application, take the following action to change the standard application name:

If <application-name> of application.xml is specified

Change the value specified in <application-name> to another name and then re-import.

If <application-name> of application.xml is not specified (if application.xml is omitted)

Change the EAR file name (application directory name in the exploded archive format) to another name and then re-import.

Note that if the objects need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47721-W

The objects in the EJB module could not be bound as Portable Global JNDI names because there are already modules with the same names under the same application in the naming service. (uri = aa....aa, module name = bb....bb)

aa....aa: Module URI

bb....bb: Standard module name

Description

A module in the same application with the same standard module name already exists in the naming service. Therefore, the objects in the EJB module could not be registered in the Portable Global JNDI name.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

However, action is required if one of the following cases is applicable:

If there is a client that looks up the objects in this EJB-JAR module using the Portable Global JNDI name.

If a resource reference is defined in this EJB-JAR module using a name beginning with java:module.

Action

If the objects must be registered in the Portable Global JNDI name for this EJB-JAR module, take the following action to change the standard module name:

If <module-name> of ejb-jar.xml is specified

Change the value specified in <module-name> to another name and then re-import.

If <module-name> of ejb-jar.xml is not specified (if ejb-jar.xml is omitted)

Change the EJB-JAR file name (EJB directory name in the exploded archive format) to another name and then re-import.

Note that if the objects need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47722-W

The objects in the Web module could not be bound as Portable Global JNDI names because there are already modules with the same names under the same application in the naming service. (uri = aa....aa, module name = bb....bb)

aa....aa: Module URI

bb....bb: Standard module name

Description

A module in the same application with the same standard module name already exists in the naming service. Therefore, the objects in the Web module could not be registered in the Portable Global JNDI name.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

However, action is required if one of the following cases is applicable:

If there is a client that looks up the objects in this Web module (Web application) using the Portable Global JNDI name.

If a resource reference is defined in this Web module (Web application) using a name beginning with java:module.

Action

If the objects must be registered in the Portable Global JNDI name for this Web module (Web application), take the following action to change the standard module name:

Change the WAR file name (WAR directory name in the exploded archive format) to another name and then re-import.

If <module-name> of web.xml is specified

Change the value specified in <module-name> to another name and then re-import.

If <module-name> of web.xml is not specified (if web.xml is omitted)

Change the WAR file name (WAR directory name in the exploded archive format) to another name and then re-import.

Note that if the objects need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47723-W

The objects in the RAR module could not be bound as Portable Global JNDI names because there are already modules with the same names under the same application in the naming service. (uri = aa....aa, module name = bb....bb)

aa....aa: Module URI

bb....bb: Standard module name

Description

A module in the same application with the same standard module name already exists in the naming service. Therefore, the objects in the resource adapter module could not be registered in the Portable Global JNDI name.

You can start the application as is, so there is no problem in the case of applications that do not use the Portable Global JNDI names.

Action

If the objects must be registered in the Portable Global JNDI name for this resource adapter module, take the following action to change the standard module name:

Change the RAR file name of the resource adapter module to another name and then re-import.

Note that if the objects need not be registered in the Portable Global JNDI names for all the applications in Application Server, you can control this message by specifying false in the user property ejbserver.jndi.global.enabled.

KDJE47730-E

The JNDI name specified in aa....aa is invalid. (name = bb....bb, JNDI name = cc....cc)

aa....aa: Tag name

bb....bb: Application display name

cc....cc: JNDI name

Description

The prefix of the JNDI name specified in the resource reference name is incorrect. You can use the following prefixes when you specify the resource reference name in the JNDI fully-qualified name (JNDI name beginning with java:):

java:app

java:comp

java:global

java:module

However, if one of the following conditions is applicable, the corresponding prefix cannot be used:

java:app

The registration of the Portable Global JNDI name is disabled.

The standard application name is invalid (KDJE47710-W is output).

The standard application name is duplicated (KDJE47720-W is output).

java:global

The registration of the Portable Global JNDI name is disabled.

java:module

The registration of the Portable Global JNDI name is disabled.

The standard application name is invalid (KDJE47710-W is output).

The standard application name is duplicated (KDJE47720-W is output).

The standard module name is invalid (KDJE47711-W is output).

The standard module name is duplicated (one of the messages from KDJE47721-W to KDJE47723-W is output).

Action

Identify the resource reference definition with the incorrect prefix based on the displayed tag name and JNDI name, and then revise the prefix of the JNDI name specified in the name.

Review, and if necessary revise, the standard application name and the standard module name.

If the registration of the Portable Global JNDI name is disabled, enable the registration of the name. If the version is upgraded from 08-70 or an earlier version, the registration might be disabled.

KDJE47731-E

There is already an object with the same JNDI name specified in aa....aa. (name = bb....bb, JNDI name = cc....cc)

aa....aa: Tag name

bb....bb: Application display name

cc....cc: JNDI name

Description

The JNDI name specified in the resource reference name is already registered as another object or context.

You cannot specify a JNDI name that is duplicated in other resource references, automatically handled objects, or reserved words determined in the standard specifications.

Action

Identify the resource reference definition with the duplicated name based on the displayed tag name and JNDI name, and then revise the JNDI name specified in the name.

Note that depending on the prefix of the JNDI name, the range of names considered as duplicated differ as follows:

For java:global

The Global JNDI name cannot be duplicated in all the J2EE servers sharing the same naming service.

For java:app

The Global JNDI name cannot be duplicated in the same application.

For java:module

The Global JNDI name cannot be duplicated in the same module.

For java:comp

The Global JNDI name cannot be duplicated in the same component.

KDJE48200-E

A format error occurred in a queue configuration file. (cause = aa....aa, file = bb....bb)

aa....aa: Reason

bb....bb: File name

Description

A format error was detected in a queue configuration file.

Action

Re-check the details of the definition file. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48201-W

No queue is registered in the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description

An exception occurred while registering the specified queue in the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48202-W

No queue has been deleted from the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred while deleting the specified queue from the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48203-W

No queue has been deleted from the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description

An exception occurred while deleting the specified queue from the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48204-W

JMSConnectionFactoryDummy is not registered in the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred while registering an object required for executing MDB in the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48205-W

JMSConnectionFactoryDummy is registered in the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description

An exception occurred while registering an object required for executing MDB in the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48206-W

JMSXAQueueConnectionFactory is not registered in the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred while registering an object required for executing MDB in the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48207-W

JMSXAQueueConnectionFactory is not registered in the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description

An exception occurred while registering an object required for executing MDB in the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48208-W

JMSConnectionFactoryDummy has not been deleted from the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred when deleting an object necessary for executing MDB from the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48209-W

JMSConnectionFactoryDummy has not been deleted from the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description

An exception occurred when deleting an object necessary for executing MDB from the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48210-W

JMSXAQueueConnectionFactory has not been deleted from the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred when deleting an object necessary for executing MDB from the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48211-W

JMSXAQueueConnectionFactory has not been deleted from the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description

An exception occurred when deleting an object necessary for executing MDB from the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48212-W

No queue is registered in the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred while registering the specified queue in the JNDI namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48213-W

An error was detected in the queue configuration file. (error property = aa....aa)

aa....aa: Property name

Description

An invalid queue definition was detected in the queue configuration file.

Action

Re-check the details of the definition file. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48214-I

The NonQueueConfigFile mode does not require a queue configuration file.

Description

The environment can be set up without using the queue definition file.

KDJE48215-I

The QueueConfigFile mode requires a queue configuration file.

Description

The queue definition information must be described in the queue definition file.

KDJE48216-E

The queue configuration information is not registered. (display name = aa....aa)

aa....aa: Resource adapter display name

Description

The queue information could not be collected because the queue definition information is not registered.

Action

Check again if the queue has been created properly. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48500-W

No resource reference is defined for the display name aa....aa.

aa....aa: Resource adapter display name

Description

The reference for the resource adapter is not set correctly.

Action

Set the reference for the resource adapter correctly.

KDJE48501-W

Logwriter is not set for the ManagedConnectionFactory instance. (display name = aa....aa)

aa....aa: Resource adapter display name

Description

Logwriter is not set for the ManagedConnectionFactory instance.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48502-W

Logwriter is not set for the ManagedConnection instance. (display name = aa....aa)

aa....aa: Resource adapter display name

Description

LogWriter is not set for the ManagedConnection instance.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48503-W

A Logwriter instance has not been created. (display name = aa....aa)

aa....aa: Resource adapter display name

Description

An exception occurred during creation of a LogWriter.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48504-W

An Mbean instance has not been created. (display name = aa....aa)

aa....aa: Resource adapter display name

Description

An exception occurred during creation of MBean.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48505-W

An Mbean instance has not been deleted. (display name = aa....aa)

aa....aa: Resource adapter display name

Description

An exception occurred during deletion of MBean.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48506-W

Recovery information cannot be deleted from the RecoveryManager. (display name = aa....aa)

aa....aa: Resource adapter display name

Description

An exception occurred while deleting recovery information.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48507-W

Connection factory cannot be deleted from the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred while deleting ConnectionFactory from the JNDI namespace.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48508-W

Connection factory cannot be deleted from the namespace. (JNDI name = aa....aa, application name = bb....bb)

aa....aa: JNDI name

bb....bb: Application name

Description

An exception occurred while deleting ConnectionFactory from the JNDI namespace.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48509-W

Configuration property has not been set for the ManagedConnectionFactory instance. (display name = aa....aa, method name = bb....bb, cause = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Method name

cc....cc: Exception name and detailed message of the exception

Description

An exception occurred while invoking the initialization method of the ManagedConnectionFactory.

Action

See the exception name, exception details, and log file of the resource adapter, and then resolve the problem.

KDJE48510-W

The value of aa....aa is outside the valid range. The default value (bb....bb) will be used.

aa....aa: Property name

bb....bb: Default value

Description

The property value is invalid.

The default value will be used.

Action

When you change the property from default value, modify the property value, and then restart the J2EE Server.

KDJE48511-E

Connection factory cannot be loaded. (class name = aa....aa, cause = bb....bb)

aa....aa: Class name

bb....bb: Exception name and detailed message of exception

Description

Connection factory cannot be loaded.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48512-E

An instance of the connection factory class could not be created. (class name = aa....aa, cause = bb....bb)

aa....aa: Class name

bb....bb: Exception name and detailed message of exception

Description

An instance of the connection factory cannot be created.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48513-E

An exception occurred during acquisition of a method. (cause = aa....aa)

aa....aa: Exception name and detailed message of exception

Description

An exception occurred during acquisition of a method.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48514-E

An exception occurred during setting of a property value. (object = aa....aa, setter method name = bb....bb, property value = cc....cc, cause = dd....dd)

aa....aa: Class name

bb....bb: Setter method name

cc....cc: Property value

dd....dd: Exception name and detailed message of exception

Description

An exception occurred while setting a property value.

Action

Confirm that the property is correct.

KDJE48515-E

An unexpected exception occurred during a connection test of a resource adapter. (cause = aa....aa)

aa....aa: Exception name and detailed message of exception

Description

An unexpected exception occurred during a connection test of a resource adapter.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48516-E

An attempt to create ManagedConnection has failed. (cause = aa....aa)

aa....aa: Exception name and detailed message of exception

Description

An attempt to create ManagedConnection has failed.

Action

Investigate based on the message exception name and the detailed message of the exception, and remove the cause.

KDJE48517-E

The transaction support level is invalid. (transaction support = aa....aa)

aa....aa: Transaction support

Description

The transaction support level is invalid.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48518-E

An unexpected exception occurred during invocation of a validate method. (class name = aa....aa, cause = bb....bb)

aa....aa: Class name

bb....bb: Exception name and detailed message of exception

Description

An unexpected exception occurred during invocation of a validate method.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48519-E

A connection test has failed. (cause = aa....aa)

aa....aa: Exception name and detailed message of exception

Description

The connection test has failed.

Action

Check the resource adapter settings and the server to be connected.

When you are using the Oracle JDBC driver, this message might be output if oracle.jdbc.autoCommitSpecCompliant=false is not set in usrconf.properties (user property file for J2EE servers).

For details about the necessity of the oracle.jdbc.autoCommitSpecCompliant=false setting, 3.6.6 Preconditions and notes on connecting to Oracle in the uCosminexus Application Server Common Container Functionality Guide.

KDJE48520-E

A resource adapter cannot be used in basic mode.

Description

A resource adapter cannot be used in basic mode.

Action

Use the 1.4 mode.

KDJE48521-E

An XA transaction cannot be used when light transaction is enabled.

Description

An XA transaction cannot be used when light transaction functionality is enabled.

Action

Set the ejbserver.distributedtx.XATransaction.enabled key of the user property file to true, and then restart the server.

KDJE48522-E

Logwriter creation has failed. (log channel name = aa....aa)

aa....aa: Log channel name

Description

An attempt to create Logwriter has failed.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48523-E

Logwriter creation has failed. (log component name = aa....aa)

aa....aa: Log component name

Description

An attempt to create Logwriter has failed.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48524-E

An attempt to set Logwriter to ManagedConnectionFactory has failed. (class name = aa....aa)

aa....aa: Class name

Description

An attempt to set Logwriter to ManagedConnectionFactory has failed.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48530-E

A data-source connection test cannot be performed except basic mode.

Description

A data-source connection test can be performed only in the basic mode.

Action

Switch the J2EE server mode to basic mode.

KDJE48531-E

An XA data-source connection test cannot be performed in basic mode.

Description

An XA data-source connection test cannot be performed in basic mode

Action

Switch the J2EE server mode to 1.4 mode.

KDJE48532-E

An XA data-source connection test cannot be performed when light transaction is enabled.

Description

An XA data-source connection test cannot be performed in the case of light transaction functionality.

Action

When performing XA data-source connection test, set ejbserver.distributedtx.XATransaction.enabled key of user property file to true.

KDJE48533-E

A resource descriptor is invalid. <java-impl> does not exist. (resource = aa....aa)

aa....aa: Resource name

Description

ResourceDescriptor is invalid. <java-impl>tag does not exist.

Action

Contact the maintenance personnel.

KDJE48534-E

A resource descriptor is invalid. <class-name> does not exist. (resource = aa....aa)

aa....aa: Resource name

Description

ResourceDescriptor is invalid. <class-name> tag does not exist.

Action

Contact the maintenance personnel.

KDJE48535-E

The resource descriptor aa....aa does not have an XA resource.

aa....aa: Display name

Description

The specified ResourceDescriptor does not have an XA resource.

Action

Contact the maintenance personnel.

KDJE48536-E

The mandatory property aa....aa does not exist.

aa....aa: Property name

Description

The mandatory property does not exist in the specified ResourceDescriptor.

Action

Contact the maintenance personnel.

KDJE48537-E

An attempt was make to connect the incorrect driver aa....aa to bb....bb.

aa....aa: JDBC driver name

bb....bb: URL

Description

The specified JDBC driver (aa....aa) cannot be connected to bb....bb URL.

Action

Incorrect URL might be specified.

Check the URL.

KDJE48538-E

A data-source connection test has failed. (cause = aa....aa)

aa....aa: Reason

Description

The data-source connection test has failed.

Action

Check the settings of the database to be connected or the data-source.

KDJE48539-E

An XA data-source connection test has failed. (cause = aa....aa)

aa....aa: Reason

Description

The XA data-source connection test has failed.

Action

Check the settings of the database to be connected or an XA data-source.

KDJE48540-E

An unexpected exception occurred. (cause = aa....aa)

aa....aa: Reason

Description

An unexpected exception occurred.

Action

Contact the maintenance personnel.

KDJE48541-E

ConnectorDescriptor was not found. (module name = aa....aa)

aa....aa: ConnectorDescriptor

Description

ConnectorDescriptor (aa....aa) was not found.

The status of the resource adapter might be invalid.

Action

Restart the resource adapter, and then redeploy the J2EE application.

KDJE48542-E

ResourceDescriptor was not found. Module name =aa....aa

aa....aa: ResourceDescriptor

Description

ResourceDescriptor (aa....aa) was not found.

The status of the resource adapter might be invalid.

Action

Restart the resource adapter, and then redeploy the J2EE application.

KDJE48543-E

The same name connector descriptor already exists. (display name = aa....aa)

aa....aa: Display name

Description

The same name ConnectorDescriptor already exists.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48544-E

A resource name that corresponds to the resource descriptor was not found. (display name = aa....aa)

aa....aa: Display name

Description

ResourceDescriptor corresponding to a resource name was not found.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48545-E

An error occurred during creation of a ManagedConnectionFactory instance.

Description

An error occurred during creation of a ManagedConnectionFactory instance.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48546-E

The display name of connectorDescriptor was not found. (display name=aa....aa)

aa....aa: Resource adapter name

Description

ConnectorDescriptor corresponding to the resource adapter name (aa....aa) was not found.

The status of the resource adapter might be invalid.

Action

Restart the resource adapter, and then redeploy the J2EE application.

KDJE48547-E

A resource adapter cannot be stopped while it is being used. (display name = aa....aa)

aa....aa: Resource adapter name

Description

A resource adapter (aa....aa) cannot be stopped while it is being used.

Action

Stop the J2EE application that is using the resource adapter, and then re-execute the operation.

KDJE48548-E

No queue was registered in the namespace. (display name = aa....aa)

aa....aa: Display name

Description

No queue was registered in the namespace.

The naming service might not be operating properly.

Action

Confirm that the naming service is operating normally.

KDJE48549-E

The QueueConfigFileName property was not found in the ra.xml file.

Description

The queue configuration file name property was not found in the ra.xml.

Action

Revise the queue configuration file. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48550-E

A queue configuration file was not found. (URL of key configuration file = aa....aa)

aa....aa: Queue configuration file URL

Description

A queue configuration file (aa....aa) was not found.

Action

Revise the queue configuration file name specified in the resource adapter property.

Revise the access permissions for the queue configuration file and queue configuration file storage directory.

KDJE48551-E

QueueImplClass was not found because a key configuration file was invalid.

Description

QueueImpl class was not found because a queue configuration file was invalid.

Action

Revise QueueImpl class defined in the queue configuration file.

KDJE48552-E

Format error queue configuration file reason: found no queue information.

Description

Queue information was not found because queue configuration file was invalid.

Action

Revise the queue configuration file.

KDJE48553-E

Queue placement information could not be acquired. (display name = aa....aa, cause = bb....bb)

aa....aa: Display name

bb....bb: Exception name and details of exception

Description

The queue placement information cannot be acquired.

Action

Revise the aa....aa queue configuration file.

KDJE48554-E

An error occurred during creation of an XADataSource instance.

Description

An error occurred during creation of a XADataSource instance.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48555-E

A J2EE resource does not exist. (URI = aa....aa)

aa....aa: URI

Description

A J2EE resource does not exist.

Action

Confirm that the J2EE resource of aa....aa exists.

KDJE48556-E

The service cannot start. (module name = aa....aa)

aa....aa: J2EE Module name

Description

The service cannot start.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48557-E

The service cannot be stopped. (module name = aa....aa)

aa....aa: J2EE Module name

Description

The service cannot be stopped.

Action

Check whether any other error message is displayed and if it is displayed, take action. If you do not understand the cause, acquire the maintenance information, and then contact the maintenance personnel.

KDJE48558-E

A J2EE connector does not exist. (URI = aa....aa)

aa....aa: URI

Description

A J2EE connector does not exist.

Action

Confirm that the J2EE connector of aa....aa exists.

KDJE48570-E

An exception occurred during setting logger object to Cosminexus Reliable Messaging. (cause = aa....aa, resource adapter name = bb....bb)

aa....aa: Detailed message of exception

bb....bb: Resource adapter name

Description

An attempt to set the logger to Cosminexus Reliable Messaging has failed.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48571-E

An exception occurred during Cosminexus Reliable Messaging starting. (cause = aa....aa, resource adapter name = bb....bb)

aa....aa: Detailed message of exception

bb....bb: Resource adapter name

Description

An attempt to start Cosminexus Reliable Messaging has failed.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE48580-E

Starting the J2EE resource adapter "aa....aa" failed. Detail=XA Transaction is not available when light transaction is enabled.

aa....aa: Resource adapter name

Description

An XA transaction cannot be used when light transaction functionality is enabled.

Therefore, resource adapter (aa....aa) cannot be started.

Action

In the case of using a distributed transaction, specify true in ejbserver.distributedtx.XATransaction.enabled key of user-defined file.

In the case of not using a distributed transaction, use the resource adapter that does not use an XA transaction.

KDJE48581-E

Starting the J2EE resource "aa....aa" failed. Detail=DataSource is not available when light transaction is enabled.

aa....aa: Data source name

Description

Data-source cannot be used when light transaction functionality is enabled.

Therefore, resource (aa....aa) cannot be started.

Action

In the case of using a distributed transaction, specify true in ejbserver.distributedtx.XATransaction.enabled key of user-defined file.

In the case of not using a distributed transaction, use a DB Connector that does not use an XA transaction.

KDJE48582-E

The linked resource adapter has not started. (linked resource adapter = aa....aa)

aa....aa: Linked resource adapter name

Description

The linked resource adapter has not started.

Action

Start the linked resource adapter.

KDJE48583-E

The linked resource adapter has not stopped. (linked resource adapter = aa....aa)

aa....aa: Linked resource adapter name

Description

The linked resource adapter has not stopped.

Action

Stop the linked resource adapter.

KDJE48584-E

The linked resource adapter is not Cosminexus Reliable Messaging. (linked resource adapter = aa....aa)

aa....aa: Linked resource adapter name

Description

The linked resource adapter is not Cosminexus Reliable Messaging.

Action

Specify Cosminexus Reliable Messaging for the linked resource adapter of DB Connector for Cosminexus Reliable Messaging.

KDJE48585-E

The linked resource adapter is not DB Connector for Cosminexus Reliable Messaging. (linked resource adapter = aa....aa)

aa....aa: Linked resource adapter name

Description

The linked resource adapter is not DB Connector for Cosminexus Reliable Messaging.

Action

Specify DB Connector of Cosminexus Reliable Messaging for the linked resource adapter of Cosminexus Reliable Messaging.

KDJE48586-E

The property that indicates the linked resource adapter is not defined. (resource adapter = aa....aa)

aa....aa: Resource adapter name

Description

The property that indicates the linked resource adapter is not defined.

Action

A link needs to be set as property in DB Connector for Cosminexus Reliable Messaging or Cosminexus Reliable Messaging. Revise the property settings.

KDJE48587-E

The linked resource adapter has already started. (linked resource adapter = aa....aa)

aa....aa: Linked resource adapter name

Description

The linked resource adapter is already running.

Action

Revise the settings paying attention to the following points:

DB Connector for Cosminexus Reliable Messaging needs to be started before the Cosminexus Reliable Messaging to be linked.

DB Connector for Cosminexus Reliable Messaging and Cosminexus Reliable Messaging can only be linked one-to-one.

KDJE48588-E

This resource adapter is linked to multiple resource adapters. (resource adapter = aa....aa)

aa....aa: Resource adapter name

Description

This resource adapter is linked to multiple resource adapters.

Action

DB Connector for Cosminexus Reliable Messaging and Cosminexus Reliable Messaging can only be linked one-to-one. Set this resource adapter at the destination to be linked so that only one resource adapter exists.

KDJE48589-E

An error occurred during creation of a javax.resource.spi.ResourceAdapter instance.(resname=aa....aa Detail = bb....bb)

aa....aa: Application display name: Resource display name

bb....bb: Exception character strings

Description

An exception occurred during creation of a javax.resource.spi.ResourceAdapter instance.

Action

Make sure that the class name specified in the <resourceadapter-class> tag of ra.xml is correct. Also check the processing of the default constructor of the corresponding class.

KDJE48590-E

An exception occurred in javax.resource.spi.ResourceAdapter.aa....aa(). (resname=bb....bb Detail = cc....cc)

aa....aa: Method name

bb....bb: Application display name: Resource display name

cc....cc: Exception character string

Description

An exception occurred in the javax.resource.spi.ResourceAdapter method.

Action

Check the processing of the method of javax.resource.spi.ResourceAdapter in which the exception has occurred.

KDJE48591-E

Cannot associate javax.resource.spi.ManagedConnectionFactory and javax.resource.spi.ResourceAdapter (resname=aa....aa,Detail=bb....bb).

aa....aa: Application display name: Resource display name

bb....bb: Exception character strings

Description

javax.resource.spi.ManagedConnectionFactory and javax.resource.spi.ResourceAdapter cannot be correlated.

Action

Check if the interface javax.resource.spi.ResourceAdapterAssociation is implemented in the class specified with the <managedconnectionfactory-class> tag of ra.xml.

If implemented, check the processing of the setResourceAdapter method.

KDJE48592-E

An exception occurred in javax.resource.spi.work.Work#run(). (resname=aa....aa Detail = bb....bb)

aa....aa: Application display name: Resource display name

bb....bb: Exception character strings

Description

An exception occurred in the run() method of javax.resource.spi.work.Work.

Action

Check the processing of the method of javax.resource.spi.work.Work in which the exception occurred.

KDJE48593-E

An exception occurred in javax.resource.spi.work.WorkListener#aa....aa(). (resname=bb....bb Detail = cc....cc)

aa....aa: Method name

bb....bb: Application display name: Resource display name

cc....cc: Exception character string

Description

An exception occurred in a method of javax.resource.spi.work.WorkListener.

Action

Check the processing of the method of javax.resource.spi.work.WorkListener in which the exception occurred.

KDJE48594-W

Configuration property has not been set for the javax.resource.spi.ResourceAdapter instance. (display name = aa....aa, method name = bb....bb, cause = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Method name

cc....cc: Exception name and detailed message of the exception

Description

An exception occurred while invoking the initialization method of the ResourceAdapter.

Action

See the exception name, exception details, and log file of the resource adapter, and then resolve the problem.

KDJE48595-E

The connection factory class does not implement the connection factory interface. (resname = aa....aa, connection factory class = bb....bb, connection factory interface = cc....cc).

aa....aa: Application display name: Resource display name

bb....bb: Specified value of the <connectionfactory-impl-class> tag

cc....cc: Specified value of the <connectionfactory-interface> tag

Description

The interface specified with the <connectionfactory-interface> tag is not implemented in the class specified with the <connectionfactory-impl-class> tag of ra.xml.

Action

Check if the specification of the <connectionfactory-impl-class> tag or <connectionfactory-interface> tag is correct.

KDJE48596-E

The connection factory interface could not be found. (resname = aa....aa,connection factory interface = bb....bb)

aa....aa: Application display name: Resource display name

bb....bb: Specified value of the <connectionfactory-interface> tag

Description

The interface specified with the <connectionfactory-interface> tag of ra.xml was not found from the class path.

Action

Check if the specification of the <connectionfactory-interface> tag is correct.

KDJE48597-E

An error occurred during creation of an administered object instance. (resource name = aa....aa, details = bb....bb)

aa....aa: Application display name: Resource display name

bb....bb: Exception character strings

Description

An exception occurred when generating an instance of the object to be managed.

Action

Make sure that the class name specified with the <adminobject-class> tag of ra.xml is correct by checking the processing of the default constructor of the corresponding class.

KDJE48598-W

An attempt to set a configuration property for the administered object failed. (resource name = aa....aa, property name = bb....bb)

aa....aa: Application display name: Resource display name

bb....bb: Property name

Description

An attempt to set up a property in the object to be managed has failed.

Action

For details about setting up the specifiable properties in the object to be managed, see the documents of the resource adapter.

KDJE48600-W

The timeout for connection-error detection is disabled because the connection pool is disabled. (resource name = aa....aa)

aa....aa: Resource name

Description

The timeout for connection-error detection is disabled because the connection pool is disabled.

Action

When using the timeout for connection-error detection, enable the connection pooling functionality.

KDJE48601-W

The timeout for connection-error detection is disabled because the maximum size of the connection pool is unlimited. (resource name = aa....aa)

aa....aa: Resource name

Description

The timeout for connection-error detection is disabled because the maximum size of the connection pool is unlimited.

Action

When using the timeout for connection-error detection, set a limit to the maximum size of the connection pool.

KDJE48602-W

A timeout for connection-error detection occurred.

(resource name = aa....aa, connection ID = bb....bb, thread = cc....cc, rootAP = dd....dd)

aa....aa: Resource name

bb....bb: Connection ID

cc....cc: Execution thread

dd....dd: Root AP information

Description

A timeout for connection error detection occurred because there was no response from the connection in the connection pool.

Action

Check the server to be connected and the connection circuit.

KDJE48603-W

Connection-error detection was not executed. (resource name = aa....aa)

aa....aa: Resource name

Description

The connection-error detection cannot be executed because the connection control threads were depleted.

Action

Check the server to be connected and the connection circuit.

KDJE48604-W

The value of connection-sweeper is under an hour(3600 seconds). (resource name = aa....aa, SweeperInterval = bb....bb, ConnectionTimeout = cc....cc)

aa....aa: Resource name

bb....bb: Connection sweeper operating time interval

cc....cc: Value of timeout until the connection is released

Description

The value of the connection sweeper is under one hour (3600 seconds). We recommend that you set one hour (3600 seconds) or more for both, the connection sweeper operating time interval and the value of the timeout until the connection is released.

Action

Revise the value specified for connection sweeper operating time interval and the value of a timeout until the connection is released. For details, see 3.15.7 Connection sweeper in the uCosminexus Application Server Common Container Functionality Guide.

KDJE48605-E

An error was detected during the processing to start J2EE connectors.

Description

An attempt to start the resource adapter during the startup of the J2EE server has failed.

Forcibly terminate the J2EE server without performing the recovery process for the transaction.

Action

From the message output immediately before this message, determine the resource adapter that could not be started, and then remove the cause of failure in starting the resource adapter.

KDJE48606-E

A resource adapter does not have a required connection definition for outbound communication.

Description

A resource adapter does not have the connection definition used for Outbound communication.

The test will be interrupted because the resource adapter is not a target for the resource connection test.

Action

Either a wrong resource adapter is specified or the definition of the resource adapter is invalid. Revise the settings, and then re-execute the command.

KDJE48901-E

The XA data-source connection test cannot be performed because the data source is not supported.

Description

The XA data-source connection test cannot be performed because the data-source is not supported.

Action

Connect to the database using the DB connector.

KDJE49000-W

No recovery information has been deleted from the RecoveryManager. (resource name = aa....aa)

aa....aa: Resource name

Description

An exception occurred while deleting recovery information.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE49001-W

No data source has been deleted from the namespace. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred while deleting the DataSource from JNDI namespace.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE49002-W

An Mbean instance has not been created. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred during creation of MBean.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE49003-W

An Mbean instance has not been removed. (JNDI name = aa....aa)

aa....aa: JNDI name

Description

An exception occurred during deletion of MBean.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE49510-I

The connection pool warmup was not executed. (resource name = aa....aa, resource type = bb....bb, minimum size = cc....cc, maximum size = dd....dd)

aa....aa: Resource display name

bb....bb: Resource type (jdbc: Datasource, or connector: Resource adapter)

cc....cc: Minimum size of connection pool

dd....dd: Maximum size of connection pool

Description

The connection pool warmup was not executed.

KDJE49511-I

The connection pool warmup started. (resource name = aa....aa, resource type = bb....bb, minimum size = cc....cc, maximum size = dd....dd)

aa....aa: Resource display name

bb....bb: Resource type (jdbc: Datasource, or connector: Resource adapter)

cc....cc: Minimum size of connection pool

dd....dd: Maximum size of connection pool

Description

The connection pool warmup was started.

KDJE49512-I

The connection pool warmup finished normally. (resource name = aa....aa, resource type = bb....bb, minimum size = cc....cc, maximum size = dd....dd, size = ee....ee)

aa....aa: Resource display name

bb....bb: Resource type (jdbc: Datasource, or connector: Resource adapter)

cc....cc: Minimum size of connection pool

dd....dd: Maximum size of connection pool

ee....ee: Connection pool size

Description

The connection pool warmup finished normally.

KDJE49513-W

The connection pool warmup failed. (resource name = aa....aa, resource type = bb....bb, minimum size = cc....cc, maximum size = dd....dd, size = ee....ee, cause = ff....ff)

aa....aa: Resource display name

bb....bb: Resource type (jdbc: Datasource, or connector: Resource adapter)

cc....cc: Minimum size of connection pool

dd....dd: Maximum size of connection pool

ee....ee: Connection pool size

ff....ff: Error information

Description

An attempt to warmup the connection pool has failed.

Action

See the error details, and then take action.

KDJE49514-I

The connection pool will now be cleared. (resource name = aa....aa, resource type = bb....bb, mode = cc....cc)

aa....aa: Resource name

bb....bb: Resource type (jdbc: Datasource or jca: Resource adapter)

cc....cc: Mode name (normal, or plan)

Description

The connection pool will now be cleared.

KDJE49515-I

The connection pool was cleared successfully. (resource name = aa....aa, resource type = bb....bb, mode = cc....cc)

aa....aa: Resource name

bb....bb: Resource type (jdbc: Datasource or jca: Resource adapter)

cc....cc: Mode name (normal, or plan)

Description

The connection pool was cleared successfully.

KDJE49516-E

An attempt to clear the connection pool has failed. (resource name = aa....aa, resource type = bb....bb, mode = cc....cc)

aa....aa: Resource name

bb....bb: Resource type (jdbc: Datasource or jca: Resource adapter)

cc....cc: Mode name (normal, or plan)

Description

An attempt to clear the connection pool has failed.

Action

See the error details of command execution, and then take action.

KDJE49517-I

The connection pool will now be cleared. (resource name = aa....aa, resource type = bb....bb, mode = cc....cc, application name = dd....dd)

aa....aa: Resource name

bb....bb: Resource type (jdbc: Datasource or jca: Resource adapter)

cc....cc: Mode name (normal, or plan)

dd....dd: Application name

Description

The connection pool will now be cleared.

KDJE49518-I

The connection pool was cleared successfully. (resource name = aa....aa, resource type = bb....bb, mode = cc....cc, application name = dd....dd)

aa....aa: Resource name

bb....bb: Resource type (jdbc: Datasource or jca: Resource adapter)

cc....cc: Mode name (normal, or plan)

dd....dd: Application name

Description

The connection pool was cleared successfully.

KDJE49519-E

An attempt to clear the connection pool has failed. (resource name = aa....aa, resource type = bb....bb, mode = cc....cc, application name = dd....dd)

aa....aa: Resource name

bb....bb: Resource type (jdbc: Datasource or jca: Resource adapter)

cc....cc: Mode name (normal, or plan)

dd....dd: Application name

Description

An attempt to clear the connection pool has failed.

Action

See the error details of command execution, and then take action.

KDJE49520-I

All connection pools will now be cleared.

Description

All connection pools will now be cleared.

KDJE49521-I

All connection pools were cleared successfully.

Description

All connection pools were cleared successfully.

KDJE49522-E

Some attempts to clear connection pools have failed.

Description

Few attempts to clear the connection pools have failed.

Action

See the error details of command execution, and then take action.

KDJE49523-I

Connections that exceed the specified time will now be closed. (time = aa....aa seconds, resource name = bb....bb)

aa....aa: Time (Seconds)

bb....bb: Resource name

Description

Connections that exceed the specified time will now be closed.

KDJE49524-I

Connections that exceed the specified time were closed successfully. (time = aa....aa seconds, resource name = bb....bb)

aa....aa: Time (Seconds)

bb....bb: Resource name

Description

Connections that exceed the specified time were closed successfully.

KDJE49525-E

An attempt to close a connection that exceeds the specified time has failed. (time = aa....aa seconds, resource name = bb....bb)

aa....aa: Time (Seconds)

bb....bb: Resource name

Description

An attempt to close a connection that exceeds the specified time has failed.

Action

See the error details of command execution, and then take action.

KDJE49526-I

Connections that exceed the specified time will now be closed. (time = aa....aa seconds)

aa....aa: Time (Seconds)

Description

Connections that exceed the specified time will now be closed.

KDJE49527-I

Connections that exceed the specified time were closed successfully. (time = aa....aa seconds)

aa....aa: Time (Seconds)

Description

Connections that exceed the specified time were closed successfully.

KDJE49528-E

Some attempts to close connections that exceed the specified time have failed. (time = aa....aa seconds)

aa....aa: Time (Seconds)

Description

An attempt to close a connection that exceeds the specified time has failed.

Action

See the error details of command execution, and then take action.

KDJE49529-I

The connection will now be closed. (resource name = aa....aa, connection ID = bb....bb)

aa....aa: Resource name

bb....bb: Connection ID

Description

The connection will now be closed.

KDJE49530-I

The connection was closed successfully. (resource name = aa....aa, connection ID = bb....bb)

aa....aa: Resource name

bb....bb: Connection ID

Description

The connection was closed successfully.

KDJE49531-E

An attempt to close the connection has failed. (resource name = aa....aa, connection ID = bb....bb)

aa....aa: Resource name

bb....bb: Connection ID

Description

An attempt to close the connection has failed.

Action

See the error details of command execution, and then take action.

KDJE49532-I

The number of connections was adjusted. (resource name = aa....aa, before = bb....bb, after = cc....cc)

aa....aa: Resource name

bb....bb: Number of connections before adjustment

cc....cc: Number of connections after adjustment

Description

The number of connections of connection pool was adjusted.

KDJE49533-W

A timeout occurred while deleting a connection. (resource name = aa....aa, connection ID = bb....bb)

aa....aa: Resource name

bb....bb: Connection ID

Description

A timeout occurred while deleting a connection by adjusting the number of connections.

Action

Check the server to be connected and the connection circuit.

KDJE49600-E

The memberResourceAdapterName[n] property is not defined. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description

The memberResourceAdapterName[n] property is not defined.

Action

Define one or more memberResourceAdapterName[n] properties.

KDJE49601-E

The property value is empty. (property name = aa....aa, root resource adapter = bb....bb)

aa....aa: Property name

bb....bb: Root resource adapter name

Description

The memberResourceAdapterName[n] property value is empty.

Action

Set the display name of member resource adapter in memberResourceAdapterName[n] property.

KDJE49602-E

Values of the memberResourceAdapterName[n] property are duplicated. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description

Values of memberResourceAdapterName[n] property are duplicated.

Action

Make the specification so that the value of memberResourceAdapterName[n] property is not duplicated.

KDJE49603-E

The member resource adapter does not exist. (member resource adapter = aa....aa, root resource adapter = bb....bb)

aa....aa: Member resource adapter name specified in memberResourceAdapterName[n] property

bb....bb: Root resource adapter name

Description

The member resource adapter specified in memberResourceAdapterName[n] property does not exist.

Action

Confirm that the member resource adapter specified in the memberResourceAdapterName[n] property exists.

KDJE49604-E

The resource adapter cannot be used as a member resource adapter. (resource adapter = aa....aa, root resource adapter = bb....bb)

aa....aa: Resource adapter name specified in memberResourceAdapterName[n] property

bb....bb: Root resource adapter name

Description

Resource adapter specified in memberResourceAdapterName[n] property cannot be used as a member resource adapter.

Action

Confirm that the resource adapter specified in the memberResourceAdapterName[n] property is the DB Connector for member resource adapter.

KDJE49605-E

The member resource adapter has not started. (member resource adapter = aa....aa, root resource adapter = bb....bb)

aa....aa: Member resource adapter name specified in memberResourceAdapterName[n] property

bb....bb: Root resource adapter name

Description

The member resource adapter specified in memberResourceAdapterName[n] property is not running. To start the root resource adapter, you must start all the member resource adapters.

Action

Confirm that the member resource adapter specified in the memberResourceAdapterName[n] property is running.

KDJE49606-E

The member resource adapter is being used as the member resource adapter of another root resource adapter. (member resource adapter = aa....aa, root resource adapter = bb....bb, duplicated root resource adapter = cc....cc)

aa....aa: Member resource adapter name specified in memberResourceAdapterName[n] property

bb....bb: Root resource adapter name

cc....cc: Duplicated root resource adapter name

Description

The member resource adapter specified in memberResourceAdapterName[n] property is used as the member resource adapter of another root resource adapter. The member resource adapter cannot be a member resource adapter of multiple root resource adapters.

Action

Specify the display name of member resource adapter that is not specified in memberResourceAdapterName[n] property of other root resource adapter in the memberResourceAdapterName[n] property.

KDJE49607-E

Not all member resource adapters have been imported from the same RAR file. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description

The member resource adapter specified in the memberResourceAdapterName[n] property is the resource adapter imported from a different rar file. All the member resource adapters need to be the resource adapters imported from the same rar file.

Action

Specify the display name of all the member resource adapters imported from the same rar file in the memberResourceAdapterName[n] property.

KDJE49608-E

A transaction support level of at least one member resource adapter is not supported by the root resource adapter. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description

A transaction support level of the member resource adapter specified in the memberResourceAdapterName[n] property is not supported by the root resource adapter.

Action

Confirm that the transaction support level of the member resource adapter specified in the memberResourceAdapterName[n] property is supported by the root resource adapter.

KDJE49609-E

Transaction support levels of all member resource adapters are not the same. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description

The transaction support levels of the member resource adapter specified in memberResourceAdapterName[n] property are different. All the transaction support levels of the member resource adapter need to be same.

Action

Confirm that all the transaction support levels of member resource adapter specified in memberResourceAdapterName[n] property are same.

KDJE49610-E

User names of all member resource adapters are not the same. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description

The database user names of member resource adapter specified in memberResourceAdapterName[n] property are different. All the database user names of member resource adapter need to be same.

Action

Confirm that all the database user names of member resource adapter specified in memberResourceAdapterName[n] property are same.

KDJE49611-E

The dbCheckInterval property value is not longer than the loginTimeout property value of a member resource adapter. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description

The dbCheckInterval property value is no longer than the loginTimeout property value of a member resource adapter specified in memberResourceAdapterName[n] property. The dbCheckInterval property value needs to be longer than the loginTimeout property value of all the member resource adapters.

Action

Confirm that the dbCheckInterval property value is longer than the loginTimeout property value of all the member resource adapters specified in the memberResourceAdapterName[n] property.

KDJE49612-W

The algorithm property is not defined. The default value will be used. (root resource adapter = aa....aa, default value = bb....bb)

aa....aa: Root resource adapter

bb....bb: Default algorithm property value

Description

The algorithm property is not defined. The default value will be used.

Action

Define the algorithm property.

KDJE49613-W

An invalid value is set in the algorithm property. The default value will be used. (root resource adapter = aa....aa, default value = bb....bb)

aa....aa: Root resource adapter

bb....bb: Default algorithm property value

Description

An invalid value is set in the algorithm property. The default value will be used.

Action

Set a valid value in the algorithm property.

KDJE49614-W

The enableAutoPoolSuspend property is not defined. The default value will be used. (root resource adapter = aa....aa, default value = bb....bb)

aa....aa: Root resource adapter

bb....bb: Default enableAutoPoolSuspend property value

Description

The enableAutoPoolSuspend property is not defined. The default value will be used.

Action

Define the enableAutoPoolSuspend property.

KDJE49615-W

The enableAutoPoolResume property is not defined. The default value will be used. (root resource adapter = aa....aa, default value = bb....bb)

aa....aa: Root resource adapter

bb....bb: Default enableAutoPoolResume property value

Description

The enableAutoPoolResume property is not defined. The default value will be used.

Action

Define the enableAutoPoolResume property.

KDJE49616-W

The dbCheckInterval property is not defined. The default value will be used. (root resource adapter = aa....aa, default value = bb....bb)

aa....aa: Root resource adapter

bb....bb: Default dbCheckInterval property value

Description

The dbCheckInterval property is not defined. The default value will be used.

Action

Define the dbCheckInterval property.

KDJE49617-W

An invalid value is set in the dbCheckInterval property. The default value will be used. (root resource adapter = aa....aa, default value = bb....bb)

aa....aa: Root resource adapter

bb....bb: Default dbCheckInterval property value

Description

An invalid value is set in the dbCheckInterval property. The default value will be used.

Action

Set a valid value in the dbCheckInterval property.

KDJE49620-E

The algorithm property is not defined. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description

The algorithm property is not defined.

Action

Define the algorithm property.

KDJE49621-E

An invalid value is set in the algorithm property. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description

An invalid value is set in the algorithm property.

Action

Set a valid value in the algorithm property.

KDJE49622-E

The enableAutoPoolSuspend property is not defined. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description

The enableAutoPoolSuspend property is not defined.

Action

Define the enableAutoPoolSuspend property.

KDJE49623-E

The enableAutoPoolResume property is not defined. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description

The enableAutoPoolResume property is not defined.

Action

Define the enableAutoPoolResume property.

KDJE49624-E

The dbCheckInterval property is not defined. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description

The dbCheckInterval property is not defined.

Action

Define the dbCheckInterval property.

KDJE49625-E

An invalid value is set in the dbCheckInterval property. (root resource adapter = aa....aa)

aa....aa: Root resource adapter

Description

An invalid value is set in the dbCheckInterval property.

Action

Set a valid value in the dbCheckInterval property.

KDJE49630-E

Connection pooling is disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description

Connection pooling functionality is disabled. This functionality is a prerequisite for member resource adapter.

Action

Set the maximum size of the connections in the connection pool to one or more.

KDJE49631-E

The maximum size of the connection pool is set to be unlimited. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description

The maximum size of the connections in the connection pool is set to unlimited. The maximum size of the connections for the member resource adapter cannot be unlimited.

Action

Set the maximum size of the connections in the connection pool to one or more.

KDJE49632-E

The function for detecting errors while getting a connection is disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description

The function for detecting the connection errors while getting a connection is disabled. This functionality is a prerequisite for member resource adapter.

Action

Enable the function for detecting the connection errors while getting a connection.

KDJE49633-E

The timeout function for detecting connection errors is disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description

The timeout function for detecting the connection errors is disabled. This functionality is a prerequisite for member resource adapter.

Action

Enable the timeout function for detecting the connection errors.

KDJE49634-E

The function to queue requests for getting a connection is disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description

The function to queue requests for getting a connection is disabled when the connections are depleted. This functionality is a prerequisite for member resource adapter.

Action

Enable the function to queue requests for getting a connection when the connections are depleted.

KDJE49635-E

The retry function for getting a connection is not disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description

The retry function for getting a connection is not disabled. This function cannot be used in the member resource adapter.

Action

Disable the retry function for getting a connection.

KDJE49636-E

The optional name function for J2EE resources is not disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description

The optional name function for the J2EE resources is not disabled. This function cannot be used in the member resource adapter.

Action

Disable the optional name function for the J2EE resources.

KDJE49637-E

The value of the loginTimeout property is not 1 or more. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description

Specify the value of the loginTimeout property to one or more. This setting is required when using Oracle JDBC Thin Driver in the member resource adapter.

Action

Specify the value of the loginTimeout property of the member resource adapter to one or more.

KDJE49640-W

Connection pooling has been enabled. (member resource adapter = aa....aa, default minimum pool size = bb....bb, default maximum pool size = cc....cc)

aa....aa: Member resource adapter name

bb....bb: Default minimum size of the number of connections of the connection pool

cc....cc: Default maximum size of the number of connections of the connection pool

Description

Connection pooling function is enabled. This functionality is a prerequisite for member resource adapter. The default value will be used for the connection pool size.

Action

Set the maximum size of the connections in the connection pool to one or more.

KDJE49641-W

The default value will be used for the connection pool size. (member resource adapter = aa....aa, default minimum pool size = bb....bb, default maximum pool size = cc....cc)

aa....aa: Member resource adapter name

bb....bb: Default minimum size of the number of connections of the connection pool

cc....cc: Default maximum size of the number of connections of the connection pool

Description

The default value will be used for the connection pool size since the maximum size of the connections in the connection pool is set to unlimited. The maximum size of the connections for the member resource adapter cannot be unlimited.

Action

Set the maximum size of the connections in the connection pool to one or more.

KDJE49642-W

The function for detecting errors while getting a connection has been enabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description

The function for detecting the connection errors while getting a connection is enabled. This functionality is a prerequisite for member resource adapter.

Action

Enable the function for detecting the connection errors while getting a connection.

KDJE49643-W

The timeout function for detecting connection errors has been enabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description

The timeout function for detecting the connection errors is enabled. This functionality is a prerequisite for member resource adapter.

Action

Enable the timeout function for detecting the connection errors.

KDJE49644-W

The function to queue requests for getting a connection has been enabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description

The function to queue requests for getting a connection is enabled when the connections are depleted. This functionality is a prerequisite for member resource adapter.

Action

Enable the function to queue requests for getting a connection when the connections are depleted.

KDJE49645-W

The retry function for getting a connection has been disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description

The retry function for getting a connection is disabled. This function cannot be used in the member resource adapter.

Action

Disable the retry function for getting a connection.

KDJE49646-W

The optional name function for J2EE resources has been disabled. (member resource adapter = aa....aa)

aa....aa: Member resource adapter name

Description

The optional name function for the J2EE resources is disabled. This function cannot be used in the member resource adapter.

Action

Disable the optional name function for the J2EE resources.

KDJE49647-E

The root resource adapter is not stopped. (root resource adapter = aa....aa, member resource adapter = bb....bb)

aa....aa: Root resource adapter

bb....bb: Member resource adapter name

Description

The root resource adapter is running. The root resource adapter must be stopped to stop the member resource adapter.

Action

Confirm that the root resource adapter is not running.

KDJE49650-I

The connection pool status has changed to "running". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The member connection pool status was changed to "running".

KDJE49651-I

The member resource adapter has started, and the connection pool status has changed to "running". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The member resource adapter was running, and the member connection pool status was changed to running.

KDJE49652-I

The connection pool status has changed to "runningReserved". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The member connection pool status was changed to runningReserved.

KDJE49653-I

The connection pool status has changed to "resumingAutomatically". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The connection pool status was changed to resumingAutomatically.

KDJE49654-I

The connection pool status has changed to "resumingManually". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The member connection pool status was changed to resumingManually.

KDJE49655-E

The connection pool status has changed to "blockedAutomatically". (resource name = aa....aa, previous pool status = bb....bb, cause = cc....cc)

aa....aa: Resource display name

bb....bb: Connection pool status before update

cc....cc: Reason for lock

Description

The member connection pool status was changed to blockedAutomatically.

Action

An error occurred in the database server. Restore the database server.

KDJE49656-I

The connection pool status has changed to "blockedManually". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The member connection pool status was changed to blockedManually.

KDJE49657-E

The connection pool status has changed to "suspendedAutomatically". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The member connection pool status was changed to suspendedAutomatically.

Action

Restore the database server and change the status of the connection pool to "running" by automatically resuming or by using the cjresumepool command.

KDJE49658-I

The member resource adapter started, and the connection pool status has changed to "suspendedAutomatically". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The member resource adapter was running, and the member connection pool status was changed to suspendedAutomatically.

KDJE49659-I

The connection pool status has changed to "suspendedAutomaticallyReserved". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The member connection pool status was changed to suspendedAutomaticallyReserved.

KDJE49660-I

The connection pool status has changed to "suspendedManually". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The member connection pool status was changed to suspendedManually.

KDJE49661-I

The member resource adapter started, and the connection pool status has changed to "suspendedManually". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The member resource adapter was running, and the member connection pool status was changed to suspendedManually.

KDJE49662-I

The connection pool status has changed to "suspendedManuallyReserved". (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The member connection pool status was changed to suspendedManuallyReserved.

KDJE49663-E

The connection pool status has changed to "suspendedAutomatically" because the member connection pool failed to resume. (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The member connection pool status was changed to suspendedAutomatically.

Action

Restore the database server and change the status of the connection pool to "running" by automatically resuming or by using the cjresumepool command.

KDJE49664-E

The connection pool status has changed to "suspendedManually" because the member connection pool failed to resume. (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

The member connection pool status was changed to suspendedManually.

Action

Use the cjresumepool command to restore the database server and change the status of the connection pool to "running".

KDJE49665-I

The member connection pool will be created now. (resource name = aa....aa, pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status

Description

The member connection pool will be created now because the member resource adapter was running.

KDJE49666-I

The member connection pool was registered in the cluster connection pool. (member resource name = aa....aa, root resource name = bb....bb)

aa....aa: Display name of member resource adapter

bb....bb: Display name of root resource adapter

Description

The member connection pool was registered in the cluster connection pool.

KDJE49667-E

An exception occurred while getting the connection pool status. (resource name = aa....aa)

aa....aa: Member resource adapter name

Description

An attempt to acquire the member connection pool status has failed. The processing will be interrupted.

Action

Undeploy the member resource adapter, and then restart the adapter after it is deployed. If action cannot be taken, acquire the maintenance information, and then contact the maintenance personnel.

KDJE49668-E

The connection pool status is invalid. (resource name = aa....aa)

aa....aa: Member resource adapter name

Description

The member connection pool status is invalid. The processing will be interrupted.

Action

Remove the cause of the invalid status of the member connection pool by referencing the messages output before this message. After removing the cause, restart the J2EE server. After restarting the J2EE server, check if the executed operation was successful.

KDJE49669-E

An exception occurred during updating of the member connection pool status. (resource name = aa....aa, previous pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status before update

Description

An attempt to update the member connection pool status has failed.

Action

Remove the cause of failure in updating the status of the member connection pool by referencing the messages output before this message. After removing the cause, restart the J2EE server. After restarting the J2EE server, check if the executed operation is successful.

KDJE49670-E

The connection pool cannot resume because the number of available connection control threads is fewer than the maximum size of the connection pool. (resource name = aa....aa)

aa....aa: Resource display name

Description

The connection pool cannot resume.

Action

Wait until the connection control threads are released.

KDJE49671-I

The number of available connection control threads has reached the maximum size of the connection pool. (resource name = aa....aa)

aa....aa: Resource display name

Description

The post-processing after the member resource adapters in the cluster connection pool paused automatically is complete, and the auto-resume processing can now be executed.

KDJE49672-E

The cjclearpool command cannot execute because the specified resource name is a root resource adapter name. (resource name = aa....aa)

aa....aa: Resource display name

Description

The display name of root resource adapter cannot be specified for the cjclearpool command.

Action

Specify the display name of the resource adapter other than the root resource adapter, and then re-execute the command.

KDJE49673-E

The cjclearpool command cannot execute because the status of the connection pool of the specified resource is not "running". (resource name = aa....aa, pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status

Description

The resource name whose connection pool status is not running cannot be specified for the cjclearpool command.

Action

Change the status of the connection pool to running, and then re-execute the command.

When the connection pool is blocked automatically or manually:

Wait for a while as the connection pool will be suspended. Execute the cjresumepool command when the status of the connection pool is suspended.

When the status of the connection pool is suspendedAutomatically or suspendedManually:

Execute the cjresumepool command.

When the connection pool is resumingAutomatically or resumingManually:

Wait for a while until the status of connection pool is running.

KDJE49674-E

The cjlistpool command cannot execute because the specified resource name is a root resource adapter name. (resource name = aa....aa)

aa....aa: Resource display name

Description

The display name of the root resource adapter cannot be specified for the cjlistpool command.

Action

Specify the display name of the resource adapter other than the root resource adapter, and then re-execute the command.

KDJE49675-E

The cjsuspendpool command cannot execute because the specified resource name is not a member resource adapter name. (resource name = aa....aa)

aa....aa: Resource display name

Description

Only the display name of the member resource adapter can be specified for the cjsuspendpool command.

Action

Specify the display name of member resource adapter, and then re-execute the command.

KDJE49676-E

The cjsuspendpool command cannot execute because the status of the specified connection pool is illegal. An available status is "running", "runningReserved", "suspendedAutomatically" or "suspendedAutomaticallyReserved". (resource name = aa....aa, pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status

Description

The resource name whose connection pool status is not running, runningReserved, suspendedAutomatically, or suspendedManually cannot be specified for the cjsuspendpool command.

Action

When the connection pool is blocked automatically or manually:

The connection pool is now being suspended. Please wait.

When the connection pool is manually suspended or reserved for manual suspension:

You need not take any action because the connection pool has already been suspended.

When the connection pool is resuming automatically, or is being resumed manually:

Wait until the connection pool is started, and then re-execute the command.

KDJE49677-E

The cjresumepool command cannot execute because the specified resource name is not a member resource adapter name. (resource name = aa....aa)

aa....aa: Resource display name

Description

Only the display name of the member resource adapter can be specified for the cjresumepool command.

Action

Specify the display name of member resource adapter, and then re-execute the command.

KDJE49678-E

The cjresumepool command cannot execute because the specified connection pool is not suspended. (resource name = aa....aa, pool status = bb....bb)

aa....aa: Resource display name

bb....bb: Connection pool status

Description

The resource name whose connection pool status is not suspendedAutomatically, suspendedManually, suspendedAutomaticallyReserved or suspendedManuallyReserved cannot be specified for the cjresumepool command.

Action

When the connection pool has started or is reserved for starting:

You need not take any action because the connection pool has already started.

When the connection pool is blocked automatically or manually:

Wait until the status of the connection pool is suspendedAutomatically or suspendedManually, and then re-execute the command.

When the connection pool is resuming automatically, or is being resumed manually:

The connection pool is now resuming. Please wait.

KDJE49679-E

The command cannot be used in basic mode. (command name = aa....aa)

aa....aa: Command name

Description

This command cannot be used in the basic mode.

Action

Make sure that the startup mode of the J2EE server is set to 1.4 mode.

KDJE49680-I

The connection pool status has been modified. (resource name = aa....aa, previous status = bb....bb, modified status = cc....cc)

aa....aa: Resource display name

bb....bb: Connection pool status before modification

cc....cc: Connection pool status after modification

Description

The status of the connection pool was modified to suspendedAutomatically or suspendedManually because the J2EE Server was forcibly stopped while the connection pool was being resumed or suspended.

KDJE49681-E

The cjresumepool command failed because the connection pool warm up failed. (resource name = aa....aa)

aa....aa: Resource display name

Description

An attempt to manually resume the connection pool has failed.

Action

Restore the database server, and then execute the cjresumepool command.

KDJE49682-W

The value of aa....aa property is invalid. The default value will be used. (default = bb....bb)

aa....aa: Property key

bb....bb: Default value

Description

The default value bb....bb will be applied because the value of the key (aa....aa) is invalid.

Action

Specify a value within the valid range in the key (aa....aa)

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.

7.5 Messages from KDJE55000 to KDJE59999

This section explains the messages from KDJE55000 to KDJE59999.

KDJE55000-I

Batch application aa....aa will now start.

aa....aa: Batch application class name

Description

The startup processing of the batch application has started.

KDJE55001-I

The main method will now start.

Description

The execution of the main method of the batch application has started.

KDJE55002-I

Batch application aa....aa will now end. (exit code = bb....bb)

aa....aa: Batch application class name

bb....bb: Exit code

Description

The termination processing of the batch application has started.

KDJE55003-I

Batch application aa....aa ended successfully. (exit code = bb....bb)

aa....aa: Batch application class name

bb....bb: Exit code

Description

The termination processing of the batch application is complete.

KDJE55004-I

Batch application will now be forcibly terminated.

Description

The forced termination processing of the batch application has started.

KDJE55005-I

Batch application aa....aa was forcibly terminated.

aa....aa: Batch application class name

Description

The forced termination processing of the batch application is complete.

KDJE55006-E

The main method was not found.

Description

The public static void main(String[]) method or the public static int main(String[]) method does not exist in the batch application.

Action

Execute a class in which a method containing the signature of public static void main(String[]) or public static int main(String[]) is defined.

KDJE55007-E

The batch application cannot be started. (details = aa....aa)

aa....aa: Details

Description

A problem occurred when starting up the batch application.

Action

See the detailed message, and then take action.

Remove the cause of the error, and then re-execute the process.

KDJE55008-E

An unexpected exception occurred. (details = aa....aa)

aa....aa: Details

Description

An unexpected exception occurred.

Action

See the detailed message, and then take action. If the cause is unknown, acquire the maintenance information, and then contact the maintenance personnel.

KDJE55009-E

An exception occurred in the main method. (exception = aa....aa)

aa....aa: Exception

Description

An exception is thrown from the main method during the execution of the batch application.

Action

Reference the exception, and then take action.

Remove the cause of the error, and then re-execute the process.

KDJE55010-E

Batch server aa....aa was not found.

aa....aa: Batch server name

Description

The batch server was not found.

Action

If the batch server name is incorrect, specify a correct name.

If the batch server is not running, start the batch server.

KDJE55011-I

The batch service will now start.

Description

The batch service starts.

KDJE55012-E

The batch service is not running.

Description

The batch service is not running.

Action

When a command is executed for the batch server, make sure that the batch service is running, and then re-execute the command. Furthermore, even if the cjexecjob command or the cjkilljob command is executed for a J2EE server, the command will be disabled. Execute the cjexecjob command or the cjkilljob command for the batch server.

KDJE55013-I

The batch application ClassLoader was initialized. (class name = aa....aa, time of operation = bb....bb)

aa....aa: Batch application class name

bb....bb: Time

Description

The class loader has been initialized.

KDJE55014-I

The batch application ClassLoader was removed. (class name = aa....aa, time of operation = bb....bb)

aa....aa: Batch application class name

bb....bb: Time

Description

The class loader has been discarded. The timing of displaying this message depends on the garbage collector. If this message is not output even when the batch application is executed repeatedly, a memory leakage might occur.

KDJE55015-E

Another batch application is already running.

Description

The batch application is running.

Action

Re-execute the command after the execution of the batch application is complete.

KDJE55016-W

The batch application is not running.

Description

The batch application is not running.

Action

Check the specified server name and job ID.

The correct server name and job ID indicate that the batch application has been terminated, and therefore, no action is required.

If the server name and job ID are incorrect, specify the correct server name and job ID in the forced termination command.

KDJE55017-E

Forcible termination of the batch application aa....aa has failed.

aa....aa: Batch application class name

Description

An attempt to perform the forced termination of the batch application has failed.

Action

Stop the batch server, and then restart.

KDJE55018-I

The cjexecjob command will now start. (aa....aa = bb....bb, directory string the user-definition file = cc....cc, process ID = dd....dd)

aa....aa: "server name" or "schedule group"

bb....bb: Batch server name or schedule group name

cc....cc: Storage destination directory of the user-defined files

dd....dd: Process ID

Description

The cjexecjob command will now start using the user definition of cc....cc directory.

KDJE55019-I

The cjexecjob command was stopped. (process ID = aa....aa, exit status = bb....bb)

aa....aa: Process ID

bb....bb: Exit status of the batch application

Description

The cjexecjob command was stopped.

KDJE55020-I

The batch server will now be forcibly stopped. (server name = aa....aa)

aa....aa: Batch server name

Description

The batch server will be terminated forcibly.

KDJE55021-E

The batch server stopped abnormally. (server name = aa....aa)

aa....aa: Batch server name

Description

The batch server is terminated abnormally during the processing of the command.

Action

Check the status of the batch server, and then re-execute the command. If the batch server name is not output, make sure that the batch server of the specified schedule group is not terminated abnormally, and then re-execute the command.

KDJE55024-I

The GC controller is waiting until resource access ends.

Description

The GC control functionality is placed in the GC execution standby status.

KDJE55025-I

The GC controller will now start GC. (rate 1 = aa....aa, rate 2 = bb....bb, rate 3 = cc....cc, free (new) = dd....dd, total (new) = ee....ee, max (new) = ff....ff, free (old) = gg....gg, total (old) = hh....hh, max (old) = ii....ii, free (permanent) = jj....jj, total (permanent) = kk....kk, max (permanent) = ll....ll, threshold value = mm....mm)

aa....aa:

When serial GC is valid:

Memory occupied (in %) by Old area

Ratio of the Old area consumption size and Old area total size

When G1 GC is valid:

Usage (in %) in the Java heap area

Ratio of the consumption size of the Java heap area with respect to the total size of the Java heap area

bb....bb:

When serial GC is valid:

The percentage (%) of total memory occupied by the New area with respect to the maximum free memory of the Old area

Ratio of the New area total size and Old area maximum free size

When G1 GC is valid: -1

cc....cc: Memory occupied (in %) by the Metaspace area

Ratio of the Metaspace area consumption size and Metaspace area total size

dd....dd: Free memory size (in bytes) of New area

ee....ee: Total memory size (in bytes) of New area

ff....ff:

When serial GC is valid:

Maximum memory size (in bytes) of New area

When G1 GC is valid: -1

gg....gg: Free memory size (in bytes) of Old area

hh....hh: Total memory size (in bytes) of Old area

ii....ii:

When serial GC is valid:

Maximum memory size (in bytes) of Old area

When G1 GC is valid:

Maximum memory size (in bytes) of the Java heap area

jj....jj: Free memory size (in bytes) of Metaspace area

kk....kk: Total memory size (in bytes) of Metaspace area

ll....ll: Maximum memory size (in bytes) of Metaspace area

mm....mm: Threshold value

Description

The GC control functionality performs a GC.

KDJE55026-E

The specified command parameter is too long.

Description

The specification of the command argument is too long.

Action

Use the usrconf.cfg or usrconf.properties file of the batch execution command to reduce the length of the argument, and then re-execute the command.

KDJE55027-I

The cjkilljob command will now start. (aa....aa = bb....bb)

aa....aa: "server name" or "schedule group"

bb....bb: Batch server name or schedule group name

Description

The cjkilljob command has started.

KDJE55028-I

The cjkilljob command was stopped. (aa....aa = bb....bb)

aa....aa: "server name" or "schedule group"

bb....bb: Batch server name or schedule group name

Description

The cjkilljob command was stopped.

KDJE55029-I

Usage:

Format1:cjexecjob serverName [Java options ...] class-name [args ...]

Format2:cjexecjob [scheduleGroup] [-jobID job ID] [Java options ...] class-name [args ...]

Description

This message describes the usage method of the cjexecjob command.

KDJE55030-I

Usage:

Format1:cjkilljob serverName

Format2:cjkilljob [scheduleGroup] -jobID jobID

Description

This message describes the usage method of the cjkilljob command.

KDJE55031-E

The resource adapter cannot be started or stopped while the batch application is running.

Description

The resource adapter cannot be started or stopped while the batch application is running.

Action

After the execution of the batch application is complete, start or stop the resource adapter again.

KDJE55032-E

The specified command cannot be used with the batch server. (server name = aa....aa, command = bb....bb)

aa....aa: Batch server name

bb....bb: Command name

Description

A command that cannot be used for the batch server is executed.

Action

If the server name is incorrect, specify the correct name.

KDJE55033-I

The batch server will suspend termination processing until the batch application has finished.

Description

The batch application is running. Wait for the batch application to terminate, and then stop the batch server.

KDJE55034-I

The batch service ended.

Description

The batch service ended.

KDJE55035-E

The batch server failed to read the user properties file for batch applications. (file = aa....aa)

aa....aa: Absolute path of the file

Description

An attempt to read the user property file for batch applications has failed. Either the file path is invalid or the read permission is not available.

Action

Specify the correct path for the user property file for batch applications.

KDJE55036-E

The communication data is invalid. (name = aa....aa, details = bb....bb, errno = cc....cc)

aa....aa: Name

bb....bb: Detailed message

cc....cc: Error code

Description

The communication data is invalid.

Action

Re-execute the command.

If the error occurs again, collect the maintenance information, and contact maintenance personnel.

KDJE55037-E

A protocol error occurred. (name = aa....aa, details = bb....bb, errno = cc....cc)

aa....aa: Name

bb....bb: Detailed message

cc....cc: Error code

Description

A protocol error occurred.

Action

Re-execute the command.

If the error occurs again, collect the maintenance information, and contact maintenance personnel.

KDJE55038-E

The server name specified for the command parameter is too long. (maximum length = aa....aa)

aa....aa: Maximum length

Description

The server name specified in the command argument is too long.

Action

Specify the server name with number of characters lesser than the displayed maximum length.

KDJE55039-W

The length of the directory name specified for aa....aa exceeds bb....bb bytes. The default value cc....cc will be used.

aa....aa: Option name

bb....bb: Directory length

cc....cc: default directory name

Description

The length of the directory name specified for aa....aa exceeds bb....bb bytes. The default value (cc....cc) will be used.

Action

Revise the value of aa....aa.

KDJE55040-E

An attempt to perform a forced stop of the batch server has failed. (server name = aa....aa)

aa....aa: Batch server name

Description

An attempt to perform the forced termination of the batch server aa....aa has failed.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE55042-E

An attempt to initialize the log has failed. (details = aa....aa, errno = bb....bb, path = cc....cc)

aa....aa: Details

bb....bb: Error code

cc....cc: Path name

Description

An attempt to initialize the log has failed.

Action

Take action based on the following causes:

The log output directory cannot be created

Check the value of the log output directory.

The log is initialized simultaneously by multiple commands

Increase the following defined values, and then re-execute the command:

batch.log.lockRetryCount

batch.log.lockInterval

KDJE55043-E

An attempt to output the log has failed. (details = aa....aa, errno = bb....bb)

aa....aa: Details

bb....bb: Error code

Description

An attempt to output the log has failed.

Action

Take action based on the following causes:

Insufficient free disk space

Delete the unnecessary files to increase the available space at the output destination or change to an output destination with available space.

Failure in the disk device

If the disk device is broken, contact the system administrator and replace the device.

No access permission

Check the access permission of the output directory.

When these factors are not applicable, collect the maintenance information, and then contact maintenance personnel.

KDJE55044-E

The server cannot be accessed. (server name = aa....aa, reason = bb....bb, details = cc....cc, errno = dd....dd)

aa....aa: Server name

bb....bb: Error contents

cc....cc: Details

dd....dd: Error code

Description

The server (aa....aa) cannot be accessed.

Action

Take action based on the error details.

Permission denied

In Windows, enable the administrator permission.

In UNIX, re-execute the command as Cosminexus Component Container administrator.

If the problem is not resolved by the above or for error contents other than the above, collect the maintenance information, and contact maintenance personnel.

KDJE55045-E

The path of the current directory is too long. (maximum length = aa....aa, details = bb....bb, errno = cc....cc)

aa....aa: Maximum length

bb....bb: Detailed message

cc....cc: Error code

Description

The path of the current directory is too long.

Action

Change the length of the absolute path of the current directory in which the command is executed in such a way so that the length is lesser than the maximum path length set by the OS.

KDJE55046-E

The smart agent was not started or the schedule group aa....aa was not found.

aa....aa: Schedule group name

Description

Either the Smart Agent is not running or the schedule group is not found.

Action

Make sure that all of the following processes are running:

Smart Agent

CTM regulator

CTM daemon

Batch server having the specified schedule group name

KDJE55047-E

The schedule group aa....aa was not found.

aa....aa: Schedule group name

Description

The schedule group was not found.

Action

Take action based on the following causes, and then restart the process:

The CTM regulator terminated abnormally.

The CTM daemon has been aborted.

The batch server having the specified schedule group name terminated abnormally.

KDJE55048-W

The job ID aa....aa was not found.

aa....aa: Job ID

Description

The job ID was not found.

Action

Check the specified job ID.

the CORRECT job ID indicates that the batch application has been terminated, and therefore, no action is required.

If the job ID is incorrect, specify the correct job ID in the forced termination command.

KDJE55049-I

The cjlistjob command will now start. (aa....aa = bb....bb)

aa....aa: "server name" or "job ID"

bb....bb: Server name or schedule group name

Description

The cjlistjob command has started.

KDJE55050-I

All batch applications have been listed successfully. (number = aa....aa)

aa....aa: Number of batch applications

Description

The list of all batch applications have been output successfully.

KDJE55051-I

The cjlistjob command was finished. (aa....aa = bb....bb)

aa....aa: "server name" or "schedule group"

bb....bb: Server name, schedule group name, or "-all"

Description

The cjlistjob command has finished.

KDJE55052-I

Usage:

Format1:cjlistjob serverName

Format2:cjlistjob [scheduleGroup[,scheduleGroup...]]|[-all]

Description

This message describes the usage method of the cjlistjob command.

KDJE55053-E

The job ID value is invalid. (value = aa....aa)

aa....aa: Job ID

Description

The value of the job ID is incorrect.

Action

Revise the value of job ID.

KDJE55054-E

The job ID aa....aa already exists. (job ID = aa....aa)

aa....aa: Job ID

Description

The job ID aa....aa already exists.

Action

Specify another value in the job ID, and then re-execute the command.

KDJE55055-E

The command aa....aa timed out.

aa....aa: Command

Description

A timeout occurred in the command aa....aa.

Action

Make sure that the timeout value is correct, and then re-execute the command.

KDJE55056-I

The cjkilljob command has reserved the batch application for deletion. (job ID = aa....aa)

aa....aa: Job ID

Description

The batch application is reserved for deletion by the cjkilljob command.

KDJE55057-W

The batch application is already reserved for deletion. (job ID = aa....aa)

aa....aa: Job ID

Description

The batch application is already reserved for deletion.

Action

Check the specified job ID.

The correct job ID indicates that the batch application is already reserved for deletion, and therefore, no action is required.

If the job ID is incorrect, specify the correct job ID in the forced termination command.

KDJE55058-E

An exception occurred in the CTM. (CTM API MSG = aa....aa)

aa....aa: Details

Description

An exception occurred in CTM.

Action

When detailed-information is output, reference the list of content codes of CTM, and then take action.

When detailed-information is output, reference the message log of CTM, and then take action.

KDJE55059-I

The batch application aa....aa will now be registered in the schedule queue bb....bb. (job ID = cc....cc)

aa....aa: Batch application name

bb....bb: Schedule queue name

cc....cc: Job ID

Description

The batch application aa....aa will be registered in the schedule queue bb....bb.

KDJE55060-E

This processing exceeded the maximum request registration. (queue = aa....aa)

aa....aa: Queue name

Description

The maximum number of registrations for the queue is exceeded.

Action

Re-execute the command after the queue application has executed.

KDJE55061-E

The CTM timed out.

Description

A timeout occurred in the CTM.

Action

Make sure that the timeout period is correct, and then re-execute the command.

KDJE55062-E

An invalid value was specified for option. (aa....aa = bb....bb)

aa....aa: "server name" or "job ID"

bb....bb: Server name or schedule group name

Description

The value specified in the command option is invalid.

Action

Check the availability of the scheduling functionality for usage, and then input the command in the correct format.

KDJE55063-E

Exception occurred in getting CTMQueueManager to start batch server:aa....aa. (CTM API MSG = bb....bb)

aa....aa: Batch server name

bb....bb: Exceptional detailed-information

Description

An exception occurred when acquiring CTMQueueManager during the startup of the batch server.

Action

After taking action based on detailed-information, start the batch server.

KDJE55064-E

Unexpected exception occurred while starting batch server:aa....aa. (details = bb....bb)

aa....aa: Batch server name

bb....bb: Exceptional detailed-information

Description

An unexpected exception occurred while starting the batch server aa....aa.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE55065-E

Unexpected exception occurred while stopping batch server:aa....aa. (details = bb....bb)

aa....aa: Batch server name

bb....bb: Exceptional detailed-information

Description

An unexpected exception occurred while stopping the batch server aa....aa.

Action

Acquire the maintenance information, and then contact the maintenance personnel.

KDJE55066-I

The batch application aa....aa will now start. (server name = bb....bb, job ID = cc....cc)

aa....aa: Batch application class name

bb....bb: Batch server name

cc....cc: Job ID

Description

The execution of the batch application aa....aa will start.

KDJE55067-E

The batch application to which the scheduling function is disabled cannot be accepted.

Description

The scheduling functionality is not enabled in the cjexecjob command.

Action

If settings are specified for using the scheduling functionality in the batch server, specify the following settings in the usrconf.cfg file of the cjexecjob command:

batch.ctm.enabled=true

KDJE55068-W

The cjexecjob command was not stopped successfully. (process ID = aa....aa, exit status = bb....bb)

aa....aa: Process ID

bb....bb: Exit status of the batch application

Description

The cjexecjob command did not terminate normally.

Action

Make sure that no other messages are output in the message log of the batch execution command.

If other messages are output, check the output message and then take action. If no other messages are output, check the error message output in the message log of the batch server, and then take action.

KDJE55069-I

The system sets the ejbserver.batch.application.exit.enabled property to false. The method that terminates this Java VM also stops the batch server. Java VM (vendor = aa....aa, version = bb....bb)

aa....aa: Vendor of used Java VM

bb....bb: Version of used Java VM

Description

Specify false in the ejbserver.batch.application.exit.enabled property. The method that terminates the batch server stops Java VM.

KDJE55500-E

An exception occurred during initialization to output log data. (detail = aa....aa)

aa....aa: Exception information

Description

An exception occurred during the initialization processing of log output.

Action

Check the exception information, and take action. If you cannot resolve the error, contact the maintenance personnel.

KDJE55501-E

An attempt to output a message has failed. (id = aa....aa, detail = bb....bb)

aa....aa: Message ID

bb....bb: Exception information

Description

An attempt to output a message has failed.

Action

Acquire the exception information, and then contact the maintenance personnel.

KDJE55502-E

An exception occurred during entity loading. This class could not be loaded. (class = aa....aa, detail = bb....bb)

aa....aa: Class name that failed to load

bb....bb: Exception information

Description

An exception occurred during the entity is loading. This class could not be loaded.

Action

Acquire the exception information, and then contact the maintenance personnel.

KDJE55503-E

An internal exception occurred during JPQL analysis. (detail = aa....aa)

aa....aa: Exception information

Description

An internal error occurred while analyzing JPQL.

Action

Acquire the exception information, and then contact the maintenance personnel.

KDJE55504-W

A Java field could not be converted to the column type of the database. The java.lang.String type will be applied to this field. (column = aa....aa, java type = bb....bb)

aa....aa: Database column name

bb....bb: Java type that failed to be mapped

Description

An attempt to convert a Java field into a database column type has failed. The java.lang.String type will be applied to this field.

Action

Make sure that the settings of the Java field types and database column types are correct.

KDJE55505-E

An invalid property value is specified. (property = aa....aa, value = bb....bb)

aa....aa: Property name

bb....bb: Value specified in property

Description

The property value is invalid.

Action

Check the property value set up in persistence.xml, and then specify the correct value.

KDJE55506-W

The table was not created because it already exists in the database. (table = aa....aa)

aa....aa: Table name

Description

Table is not created because the table already exists in the database.

Action

Check if a table with the same name exists in the database.

KDJE55507-W

The value specified for jta-data-source will be ignored because the transaction type is RESOURCE_LOCAL. (persistence unit = aa....aa)

aa....aa: Persistence unit name

Description

The transaction type is RESOURCE_LOCAL. The value specified in the <jta-data-source> tag of persistence.xml will be ignored.

Action

Check the transaction attribute of the <persistence-unit> tag of persistence.xml, and the specification contents of the <jta-data-source> tag.

KDJE55508-E

An exception occurred during processing to register a Synchronization object to the JTA. (status = aa....aa, detail = bb....bb)

aa....aa: Transaction status

bb....bb: Exception information

Description

An exception occurred during the processing for registering a Synchronization object in JTA.

Action

Acquire the exception information, and then contact the maintenance personnel.

KDJE55509-W

The hint specified for the query will be ignored because the hint is invalid. (query = aa....aa, hint = bb....bb)

aa....aa: Query name

bb....bb: Query hint name

Description

The hint specified for a query will be ignored because the hint is invalid.

Action

Confirm that the query hint is correctly set up.

KDJE55510-E

An exception occurred during the loading of an O/R mapping file. (file = aa....aa, detail = bb....bb)

aa....aa: File name used for O/R mapping

bb....bb: Exception information

Description

An exception occurred while loading the O/R mapping file.

Action

Check the file specified in the <mapping-file> tag of persistence.xml.

The causes of occurrence of this error might be that the file does not exist or the access permission to the file is not available.

KDJE55511-W

An attempt to load an entity class during persistence unit initialization has failed. (class = aa....aa, detail = bb....bb)

aa....aa: Class name specified in the entity

bb....bb: Exception information

Description

An attempt to load the entity class during the initialization of the persistent unit has failed.

Action

Make sure that the correct class name is specified in the class attribute of the <entity> tag of O/R mapping file.

If you cannot resolve the error acquire the maintenance information, and then contact the maintenance personnel.

KDJE55512-W

An optimistic lock was specified for an entity multiple times. The version specified for an element will be ignored. (entity = aa....aa, element = bb....bb)

aa....aa: Entity class

bb....bb: Field or property for which the version is to be specified

Description

An optimistic lock is specified more than once for an entity. The specification of the <version> tag will be ignored.

Action

Check the settings for the optimistic lock.

KDJE55513-W

The same mapping was specified for an entity element multiple times. This mapping specification will be ignored. (entity = aa....aa, element = bb....bb)

aa....aa: Entity class

bb....bb: Field or property for which the mapping is to be specified

Description

The same mapping is specified more than once for an entity element. The specification of the mapping will be ignored.

Action

Check the settings of the entity fields or properties of the O/R mapping file.

KDJE55514-W

The LAZY fetch element for an entity will be ignored. Basic mappings use EAGER fetching by default. (entity = aa....aa, element = bb....bb)

aa....aa: Entity class

bb....bb: Field or property for which the Lazy fetch type is to be specified

Description

The LAZY fetch element specified for an entity will be ignored. The EAGER fetching is used by default in the Basic mappings.

Action

Check the settings of the Basic fetch attribute.

LazyLoading for @Basic is not supported in the Cosminexus JPA provider. The default value FetchType.EAGER is applied at all times.

KDJE55515-W

The id specified for an element will be ignored because a primary key was specified for an entity multiple times. (entity = aa....aa, element = bb....bb)

aa....aa: Entity class

bb....bb: Field or property for which the <id> tag is to be specified

Description

The specification of the <id> tag will be ignored because the primary key is specified more than once for the entity.

Action

Check the settings of the primary key. If you cannot resolve the error, contact the maintenance personnel.

KDJE55516-W

The specified inheritance will be ignored because inheritance information was specified for an entity multiple times. (entity = aa....aa)

aa....aa: Entity class

Description

The specification of the <inheritance> tag will be ignored because the inheritance strategy is specified more than once for the entity.

Action

Check the settings of the inheritance strategy. If you cannot resolve the error, contact the maintenance personnel.

KDJE55517-W

The specified @SecondaryTable(s) information will be ignored because table information was specified for an entity multiple times. (entity = aa....aa)

aa....aa: Entity class for which @SecondaryTable(s) will be specified

Description

The specification of @SecondaryTable(s) will be ignored because the table information is specified more than once for the entity.

Action

Check the settings of the table information. If you cannot resolve the error, contact the maintenance personnel.

KDJE55518-W

The specified @Table information will be ignored because table information was specified for an entity multiple times. (entity = aa....aa)

aa....aa: Entity class for which @Table is to be specified

Description

The specification of @Table will be ignored because the table information is specified more than once for the entity.

Action

Check the settings of the table information. If you cannot resolve the error, contact the maintenance personnel.

KDJE55519-W

The specified id-class will be ignored because primary key information was specified for an entity multiple times. (entity = aa....aa, id-class = bb....bb)

aa....aa: Entity class

bb....bb: Entity class specified in the <id-class> tag

Description

The specification of the <id-class> tag will be ignored because the primary key information is specified more than once for the entity.

Action

Check the settings of the primary key. If you cannot resolve the error, contact the maintenance personnel.

KDJE55520-W

The specified @IdClass information will be ignored because primary key information was specified for an entity multiple times. (entity = aa....aa, @IdClass = bb....bb)

aa....aa: Entity class

bb....bb: Entity class for which @IdClass is specified

Description

The specification of @IdClass will be ignored because the primary key information is specified more than once for the entity.

Action

Check the settings of the primary key. If you cannot resolve the error, contact the maintenance personnel.

KDJE55521-W

The named-native-query defined in the O/R mapping file will be ignored because a query with that name already exists. (file = aa....aa, query = bb....bb)

aa....aa: File name in which the <named-native-query> tag is defined

bb....bb: Query name specified in the <named-native-query> tag

Description

The specification of the <named-native-query> tag defined in the O/R mapping file will be ignored because the query name is already in use.

Action

Check the specification contents of the <named-native-query> tag of O/R mapping file.

KDJE55522-W

Ignoring the @NamedNativeQuery specified on class since a query with that name already exists. (class = aa....aa, query = bb....bb)

aa....aa: Class name in which @NamedNativeQuery is defined

bb....bb: Query name of @NamedNativeQuery

Description

The specification of @NamedNativeQuery will be ignored because the query name is already in use.

Action

Check the specification contents of the <named-native-query> tag of the O/R mapping file and @NamedNativeQuery.

KDJE55523-W

The specified embedded-id will be ignored because primary key information was specified for an entity multiple times. (entity = aa....aa, element = bb....bb)

aa....aa: Entity class

bb....bb: Field or property in which the <embedded-id> tag is to be specified

Description

The specification of the <embedded-id> tag will be ignored because the primary key information is specified more than once for the entity.

Action

Check the settings of the primary key. If you cannot resolve the error, contact the maintenance personnel.

KDJE55524-W

The specified table will be ignored because table information was specified for an entity multiple times. (entity = aa....aa)

aa....aa: Entity class in which the <table> tag is to be specified

Description

The specification of the <table> tag will be ignored because the table information is specified more than once for the entity.

Action

Check the settings of the table information. If you cannot resolve the error, contact the maintenance personnel.

KDJE55525-W

The specified secondary-table will be ignored because table information was specified for an entity multiple times. (entity = aa....aa)

aa....aa: Entity class for which the <secondary-table> tag is to be specified

Description

The specification of the <secondary-table> tag will be ignored because the table information is specified more than once for the entity.

Action

Check the settings of the table information. If you cannot resolve the error, contact the maintenance personnel.

KDJE55526-W

The platform of the connected database was not able to be specified. There is a possibility that peculiar processing to the database cannot be executed. (platform = aa....aa)

aa....aa: Platform name of the database in use

Description

The platform of the connected database could not be determined. Processing specific to the database might not execute.

Action

Check if the connection-destination database is supported by the Cosminexus JPA provider.

KDJE55527-E

Transformation processing for a class has failed. (class = aa....aa, detail = bb....bb)

aa....aa: Class that failed in the conversion processing (class path)

bb....bb: Exception information

Description

The conversion processing for the class has failed.

Action

Acquire the exception information, and then contact the maintenance personnel.

KDJE55528-E

An attempt to output a message to the operation log file has failed. (detail = aa....aa, internal id = bb....bb, persistence unit = cc....cc)

aa....aa: Exception information

bb....bb: Internal ID of the operation log

cc....cc: Persistent unit name

Description

An attempt to output a message in the operation log has failed.

Action

Acquire the exception information, and then contact the maintenance personnel.

KDJE55529-E

A file system exception occurred during the transformation processing for a class. (class = aa....aa, detail = bb....bb)

aa....aa: Class that failed in the conversion processing (class path)

bb....bb: Exception information

Description

A file system exception occurred during the conversion processing for a class.

Action

Acquire the exception information, and then contact the maintenance personnel.

KDJE55530-E

An internal error occurred during the transformation processing for a class.

Description

An internal error occurred during the conversion processing for a class.

Action

Acquire the exception information, and then contact the maintenance personnel.

KDJE55531-W

Acquisition of entity information about a class to be transformed has failed. (class = aa....aa)

aa....aa: Class name that failed in the conversion processing

Description

An attempt to collect the entity information of a class to be converted has failed.

Action

Acquire the exception information, and then contact the maintenance personnel.

KDJE55532-W

The annotation specified for an element will be ignored because the metadata-complete has been specified for the O/R mapping file. (annotation = aa....aa, element = bb....bb)

aa....aa: Annotation name

bb....bb: Entity class, field, or property in which the annotation is to be specified

Description

The annotation specified in the tag will be ignored because the <metadata-complete> tag is specified in the O/R mapping file.

Action

Check the specification contents of the <metadata-complete> tag of O/R mapping file.

KDJE55533-W

The value specified for non-jta-data-source will be ignored because the transaction type is JTA. (persistence unit = aa....aa)

aa....aa: Persistence unit name

Description

The transaction type is JTA. A value is specified in the <non-jta-data-source> tag, but the value will be ignored.

Action

Check the transaction attribute of the <persistence-unit> tag of persistence.xml, and the specification contents of the <non-jta-data-source> tag.

KDJE55534-W

The named-query defined in the O/R mapping file will be ignored because a query with that name already exists. (file = aa....aa, query = bb....bb)

aa....aa: File name in which the <named-query> tag is defined

bb....bb: Query name of the <named-query> tag

Description

The specification of the <named-query> tag defined in the O/R mapping file will be ignored because the query name is already in use.

Action

Check the specification contents of the <named-query> tag of O/R mapping file.

KDJE55535-W

The specified @NamedQuery information will be ignored because a query with that name already exists. (class = aa....aa, query = bb....bb)

aa....aa: Class name in which @NamedQuery is defined

bb....bb: Query name of @NamedQuery

Description

The specification of @NamedQuery will be ignored because the query name is already in use.

Action

Check the specification contents of the <named-query> tag of the O/R mapping file and @NamedQuery.

KDJE55536-W

An invalid property value is specified. The default value will be used. (property = aa....aa, value = bb....bb, default = cc....cc)

aa....aa: Property name

bb....bb: Value specified in property

cc....cc: Default value

Description

The default value will be used because an invalid value is specified in the property.

Action

Check the property value of the user property file (usrconf.properties), and specify the correct value.

KDJE55537-E

An exception occurred during the construction of the SQL statement. (detail = aa....aa)

aa....aa: Exception information

Description

An exception occurred during the construction of the SQL statement.

Action

Acquire the exception information, and then contact the maintenance personnel.

KDJE55538-E

As a result of executing the SQL statement, an exception was received from the database. (detail = aa....aa)

aa....aa: Exception information

Description

As a result of executing the SQL statement, an exception is received from the database.

Action

Check the problem, and take action. If you cannot resolve the error, contact the maintenance personnel.

KDJE55539-W

An exception occurred during mapping of data acquired from the database. (column = aa....aa, java type = bb....bb, detail = cc....cc)

aa....aa: Database column name

bb....bb: Java type that failed to be mapped

cc....cc: Exception information

Description

An exception occurred during the mapping process of the data collected from the database.

Action

Make sure that the data in the database is appropriate for mapping in the Java type.

KDJE56500-W

Deployment of this persistence unit was skipped because a persistence unit that has same name has already been deployed. (persistence unit root = aa....aa, persistence unit name = bb....bb)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

Description

The deployment of the persistent unit is skipped because a persistent unit with the same name is already deployed.

Action

Make changes in such a way so that more than one persistent unit with the same name is not defined in a single EJB-JAR, and WAR or EAR.

KDJE56501-E

No persistence unit with the specified name has been defined. (persistence unit name = aa....aa)

aa....aa: Persistence unit name

Description

The persistent unit with the specified name is not defined.

Action

In the PersistenceContext, PersistenceUnit annotation, or the <persistence-context-ref> and <persistence-unit-ref> tabs of the Deployment Descriptor, specify the persistent unit name defined in the application.

KDJE56502-E

No persistence unit that has the specified persistence unit root has been defined. (persistence unit name = aa....aa)

aa....aa: Persistence unit name

Description

A persistent unit having the root of the specified persistent unit is not defined.

Action

When using the # syntax in PersistenceContext, PersistenceUnit annotation, or in the <persistence-context-ref> and <persistence-unit-ref> tabs of the Deployment Descriptor, specify the correct root of the persistent unit defined in the application.

KDJE56503-E

Instantiation of a persistence provider class has failed. (persistence provider class = aa....aa)

aa....aa: JPA provider class name

Description

An instance of the JPA provider class could not be created.

Action

Make sure that the JPA provider class name specified in the provider element or <ejbserver.jpa.defaultProviderClassName> tag of persistence.xml is correct and the specified class is included in the class path.

KDJE56504-E

The persistence unit to use cannot be identified because multiple persistence units exist within the scope but no persistence unit name is specified for the reference. Explicitly specify the persistence unit name for the reference.

Description

Irrespective of the fact that two or more persistent units are defined in the reference scope of the persistent unit, the persistent unit name has not been specified in the reference.

Action

Specify the persistent unit name in PersistenceContext, PersistenceUnit annotation, or the <persistence-context-ref> and <persistence-unit-ref> tabs of the Deployment Descriptor.

KDJE56505-E

The name of a persistence unit must not be an empty string. Specify at least one character for the name.

Description

Null characters cannot be specified in the persistent unit name in persistence.xml.

Action

Specify a character string of one or more characters in the persistent unit name of persistence.xml.

KDJE56506-E

The jar file specified for the jar-file element cannot be found. (persistence unit root = aa....aa, persistence unit name = bb....bb, jar file name = cc....cc)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: JAR file name

Description

The JAR file specified in the jar-file element of persistence.xml cannot be found.

Action

Specify a JAR file that can be referenced in the jar-file element of persistence.xml.

KDJE56507-E

An entity manager in the transaction scope could not be acquired because the transaction is not in the active status.

Description

The entity manager of the transaction scope could not be acquired because the transaction is not in an active status.

Action

Make sure that the transaction timeout has not occurred.

KDJE56508-E

This operation cannot be invoked using a container-managed entity manager. (operation = aa....aa)

aa....aa: Operation

Description

This operation cannot be invoked using a container-managed entity manager.

Action

Check the application codes to make sure that a method that cannot be invoked using a container-managed entity manager is not invoked.

KDJE56509-E

This operation must be invoked in a transaction context. (operation = aa....aa)

aa....aa: Operation

Description

An operation that cannot be invoked outside a transaction context is invoked.

Action

Check the application codes to make sure that an operation that cannot be invoked outside a transaction context is not invoked.

KDJE56510-E

This operation is not supported for a query object created when no transactions existed. (operation = aa....aa)

aa....aa: Operation

Description

An operation that is not supported by a query object created when no transactions exist is invoked.

Action

Check the application codes to make sure that an operation that is not supported by a query object created when no transactions exist is not invoked.

KDJE56511-E

An extended persistence context cannot be used except with a stateful session bean. (component = aa....aa)

aa....aa: Component

Description

A persistent context extended in other than a stateful session bean cannot be used.

Action

Check the application codes to make sure that a persistent context extended from other than a stateful session bean is not used.

KDJE56512-E

A stateful session bean that has a reference to an extended persistence context was invoked for a transaction already associated with another persistence context.

Description

A stateful session bean referencing an extended persistent context cannot be invoked in a transaction that is already associated with another persistent context.

Action

Check the application codes to make sure that a stateful session bean referencing an extended persistent context is not invoked in a transaction that is already associated with another persistent context.

KDJE56513-I

A persistence unit will now be deployed. (application name = aa....aa, persistence unit root = bb....bb, persistence unit name = cc....cc)

aa....aa: Application name

bb....bb: Root of the persistent unit

cc....cc: Persistent unit name

Description

The deployment of the persistent unit will start.

KDJE56514-I

A persistence unit was successfully deployed. (application name = aa....aa, persistence unit root = bb....bb, persistence unit name = cc....cc)

aa....aa: Application name

bb....bb: Root of the persistent unit

cc....cc: Persistent unit name

Description

A persistent unit has been deployed.

KDJE56515-E

Deployment of a persistence unit has failed. (application name = aa....aa, persistence unit root = bb....bb, persistence unit name = cc....cc)

aa....aa: Application name

bb....bb: Root of the persistent unit

cc....cc: Persistent unit name

Description

An attempt to deploy a persistent unit has failed.

Action

Follow the action described in the message reporting the cause of failure.

KDJE56516-I

All persistence units within the application will now be undeployed. (application name = aa....aa)

aa....aa: Application name

Description

The undeploy of the persistent units within the application will start.

KDJE56517-I

All persistence units within the application were successfully undeployed. (application name = aa....aa)

aa....aa: Application name

Description

All persistent units within the application have been undeployed.

KDJE56518-I

All persistence units within the WAR file will now be undeployed. (application name = aa....aa, path of the WAR file = bb....bb)

aa....aa: Application name

bb....bb: Path of the WAR file

Description

The undeploy of the persistent units within the WAR file will start.

KDJE56519-I

All persistence units within the WAR file were successfully undeployed. (application name = aa....aa, path of the WAR file = bb....bb)

aa....aa: Application name

bb....bb: Path of the WAR file

Description

The persistent units within the WAR file have been undeployed.

KDJE56520-E

Acquisition of the JTA data source specified for the jta-data-source element in the persistence.xml file has failed. (persistence unit root = aa....aa, persistence unit name = bb....bb, JTA data source = cc....cc)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: JTA data source

Description

An attempt to acquire the JTA data source specified in the jta-data-source element of persistence.xml has failed.

Action

Examine the exception that caused the error occurrence, and then take action.

KDJE56521-E

Acquisition of the non-JTA data source specified for the non-jta-data-source element in the persistence.xml file has failed. (persistence unit root = aa....aa, persistence unit name = bb....bb, non-JTA data source = cc....cc)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: Non-JTA data source

Description

An attempt to acquire the non-JTA data source specified in the non-jta-data-source element of persistence.xml has failed.

Action

Examine the exception that caused the error occurrence, and then take action.

KDJE56524-E

Creation of a URL or URI has failed. (path = aa....aa)

aa....aa: Path

Description

An attempt to create a URL or URI has failed.

Action

Examine the exception that caused the error occurrence, and then take action.

KDJE56525-E

An IOException occurred while deploying persistence units. (persistence unit root = aa....aa)

aa....aa: Persistence unit root

Description

An IOException occurred in the deployment processing of the persistent unit.

Action

Examine the exception that caused the error occurrence, and then take action.

KDJE56526-E

An attempt to parse the persistence.xml file has failed. (persistence unit root = aa....aa, cause = bb....bb)

aa....aa: Persistence unit root

bb....bb: Cause

Description

An attempt to parse persistence.xml has failed.

Action

Examine the cause, and check the contents of persistence.xml.

KDJE56527-E

A JTA data source must be specified when the transaction type of the persistence unit is JTA. (persistence unit root = aa....aa, persistence unit name = bb....bb)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

Description

If the transaction type of the persistent unit is JTA, a JTA data source must be specified.

Action

Correctly define the referencing of the resource adapter deployed and started as a standalone module in the jta-data-source element of persistence.xml, the system property ejbserver.jpa.defaultJtaDsName, or the system property ejbserver.jpa.overrideJtaDsName. When referencing a resource adapter conforming to Connector 1.0 specifications, specify the resource-adapter-display-name or resource-adapter-optional-name. When referencing a resource adapter conforming to Connector 1.5 specifications, specify the resource-adapter-display-name!connection-definition-identifier, or the optional name of the resource adapter.

KDJE56528-E

A non-JTA data source must be specified when the transaction type of the persistence unit is RESOURCE_LOCAL. (persistence unit root = aa....aa, persistence unit name = bb....bb)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

Description

If the transaction type of the persistent unit is RESOURCE_LOCAL, a non-JTA data source must be specified.

Action

Correctly define the referencing of the resource adapter deployed and started as a standalone module in the non-jta-data-source element of persistence.xml, the system property ejbserver.jpa.defaultNonJtaDsName, or the system property ejbserver.jpa.overrideNonJtaDsName. When referencing a resource adapter conforming to Connector 1.0 specifications, specify the resource-adapter-display-name or resource-adapter-optional-name. When referencing a resource adapter conforming to Connector 1.5 specifications, specify the resource-adapter-display-name!connection-definition-identifier, or the optional name of the resource adapter.

KDJE56529-E

The JTA data source specified for the system property ejbserver.jpa.defaultJtaDsName or the system property ejbserver.jpa.overrideJtaDsName or the jta-data-source element in the persistence.xml file cannot be found. (persistence unit root = aa....aa, persistence unit name = bb....bb, JTA data source = cc....cc)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: JTA data source

Description

The JTA data source specified in the jta-data-source element of persistence.xml, the system property ejbserver.jpa.defaultJtaDsName, or the system property ejbserver.jpa.overrideJtaDsName cannot be found.

Action

Correctly define the referencing of the resource adapter deployed and started as a standalone module in the jta-data-source element of persistence.xml, the system property ejbserver.jpa.defaultJtaDsName, or the system property ejbserver.jpa.overrideJtaDsName. When referencing a resource adapter conforming to Connector 1.0 specifications, specify the resource-adapter-display-name or resource-adapter-optional-name. When referencing a resource adapter conforming to Connector 1.5 specifications, specify the resource-adapter-display-name!connection-definition-identifier, or the optional name of the resource adapter.

KDJE56530-E

The non-JTA data source specified for the system property ejbserver.jpa.defaultNonJtaDsName or the system property ejbserver.jpa.overrideNonJtaDsName or the non-jta-data-source element in the persistence.xml file cannot be found. (persistence unit root = aa....aa, persistence unit name = bb....bb, non-JTA data source = cc....cc)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: Non-JTA data source

Description

The non-JTA data source specified in the non-jta-data-source element of persistence.xml, the system property ejbserver.jpa.defaultNonJtaDsName, or the system property ejbserver.jpa.overrideNonJtaDsName cannot be found.

Action

Correctly define the referencing of the resource adapter deployed and started as a standalone module in the non-jta-data-source element of persistence.xml, the system property ejbserver.jpa.defaultNonJtaDsName, or the system property ejbserver.jpa.overrideNonJtaDsName. When referencing a resource adapter conforming to Connector 1.0 specifications, specify the resource-adapter-display-name or resource-adapter-optional-name. When referencing a resource adapter conforming to Connector 1.5 specifications, specify the resource-adapter-display-name!connection-definition-identifier, or the optional name of the resource adapter.

KDJE56531-E

The transaction support level of a resource adapter referenced as a JTA data source must be LocalTransaction or XATransaction. (persistence unit root = aa....aa, persistence unit name = bb....bb, JTA data source = cc....cc, resource adapter name = dd....dd)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: JTA data source

dd....dd: Resource adapter name

Description

The transaction support level of the resource adapter referenced as a JTA data source must be LocalTransaction or XATransaction.

Action

Make sure that the transaction support level of the resource adapter referenced as a JTA data source is LocalTransaction or XATransaction.

KDJE56532-E

The transaction support level of a resource adapter referenced as a non-JTA data source must be NoTransaction. (persistence unit root = aa....aa, persistence unit name = bb....bb, non-JTA data source = cc....cc, resource adapter name = dd....dd)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: Non-JTA data source

dd....dd: Resource adapter name

Description

The transaction support level of the resource adapter referenced as a non-JTA data source must be NoTransaction.

Action

Make sure that the transaction support level of the resource adapter referenced as a non-JTA data source is NoTransaction.

KDJE56533-E

The connection factory interface of a resource adapter referenced by a persistence unit must be javax.sql.DataSource. (persistence unit root = aa....aa, persistence unit name = bb....bb, data source = cc....cc, resource adapter name = dd....dd, connection factory interface = ee....ee)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: Data source

dd....dd: Resource adapter name

ee....ee: Connection factory interface

Description

The connection factory interface of the resource adapter referenced from a persistent unit must be javax.sql.DataSource.

Action

Make sure that the connection factory interface of the resource adapter referenced from a persistent unit is javax.sql.DataSource.

KDJE56534-E

The transaction type of a persistence unit used by a container-managed entity manager must be JTA. (persistence unit root = aa....aa, persistence unit name = bb....bb, path of the WAR file or EJB-JAR file = cc....cc)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: Path of the WAR file or the EJB-JAR file

Description

The transaction type of a persistence unit used by a container-managed entity manager must be JTA.

Action

Make sure that the transaction type of a persistence unit used by a container-managed entity manager is specified as JTA.

KDJE56535-E

A reference to an extended persistence context can only be defined with a stateful session bean. (persistence unit root = aa....aa, persistence unit name = bb....bb, path of the WAR file or EJB-JAR file = cc....cc, EJB name = dd....dd)

aa....aa: Persistence unit root

bb....bb: Persistence unit name

cc....cc: Path of the WAR file or the EJB-JAR file

dd....dd: EJB name (only for an EJB)

Description

A referencing of the extended persistence context cannot be defined in other than a stateful session bean.

Action

Make sure that the referencing of the extended persistence context is not defined in other than a stateful session bean.

KDJE56536-E

Deployment of persistence units included in a Web application has failed. (path of the Web application = aa....aa, cause = bb....bb)

aa....aa: Path of the Web application

bb....bb: Cause

Description

An attempt to deploy the persistence units included in the Web application has failed.

Action

Follow the action described in the message included in the cause of the error.

KDJE56538-E

An entity manager cannot be invoked from this method. (method = aa....aa)

aa....aa: Method

Description

The entity manager cannot be invoked from this method.

Action

Check the user program to make sure that the entity manager is not invoked from a location at which invocation is not allowed.

KDJE56539-E

PersistenceProvider#createContainerEntityManagerFactory method of the JPA provider threw an exception.(persistence unit name = aa....aa, persistence provider class name = bb....bb, exception = cc....cc)

aa....aa: Persistence unit name

bb....bb: JPA provider class name

cc....cc: Exception

Description

An exception occurred in the createContainerEntityManagerFactory method of the JPA provider.

Action

Examine the exception that caused the error occurrence, and then take action.

KDJE58300-E

The specified property value is invalid. (resource adapter = aa....aa, property = bb....bb, value = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Property name

cc....cc: Specified value

Description

An invalid value is specified in the property of the TP1 inbound adapter.

Action

Specify an appropriate value in the property.

KDJE58301-W

The specified property value is invalid. The default value will be used. (resource adapter = aa....aa, property = bb....bb, specified value = cc....cc, default value = dd....dd)

aa....aa: Resource adapter display name

bb....bb: Property name

cc....cc: Specified value

dd....dd: Default value

Description

An invalid value is specified in the property of the TP1 inbound adapter. The default value will be used.

Action

If the problem of the default value occurs in the operation, stop the resource adapter, reset the property value, and then restart the resource adapter.

KDJE58302-E

A required property value is not specified. (resource adapter = aa....aa, property = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Property name

Description

A property that must be set up is not specified.

Action

Specify the property that must be set up.

KDJE58303-E

On the J2EE server, there is already a TP1 Inbound Adapter that has the same service group name.(resource adapter = aa....aa, service group = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Service group name of the resource adapter

Description

The service group name specified in the TP1 inbound adapter is already used by another TP1 inbound adapter.

Action

Check the settings of the service group name specified in the TP1 inbound adapter that has failed to start, correct the property value, and then restart the resource adapter.

KDJE58304-E

On the TP1 Inbound Adapter, there is already a service that has the same service name. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Service group name of the resource adapter

cc....cc: Service name of MDB (service)

Description

The service name specified in ActivationSpec of MDB (service) is already used by another MDB (service) within the same service group.

Action

Check the service name settings of the MDB (service) that has failed to start, correct the property value, and then restart the J2EE application.

KDJE58350-I

The TP1 Inbound Adapter started. (resource adapter = aa....aa, service group = bb....bb, scd_port = cc....cc, rn_port = dd....dd)

aa....aa: Resource adapter display name

bb....bb: Service group name of the resource adapter

cc....cc: Port number of port with pending RPC request

dd....dd: Port number of port with pending synchronous messages

Description

The TP1 inbound integrated functionality has started.

KDJE58351-I

The TP1 Inbound Adapter ended. (resource adapter = aa....aa, service group = bb....bb, scd_port = cc....cc, trn_port = dd....dd)

aa....aa: Resource adapter display name

bb....bb: Service group name of resource adapter

cc....cc: Port number of port with pending RPC request

dd....dd: Port number of port with pending synchronous messages

Description

The TP1 inbound integrated functionality has ended.

KDJE58352-E

The port aa....aa for the TP1 Inbound Adapter could not be opened. (resource adapter = bb....bb, service group = cc....cc)

aa....aa: Port number set up in the scd_port or trn_port property of TP1 inbound adapter

bb....bb: Resource adapter display name

cc....cc: Service group name of resource adapter

Description

While starting the TP1 inbound integrated functionality, the port number with pending communication from OpenTP1 did not open. The port might already be used. Starting of resource adapter will be interrupted.

Action

Check whether the port number set up in the scd_port or trn_port property of the TP1 inbound adapter is already used. If the port number is already used, stop the application using the port number or specify another port number in scd_port or trn_port, and then restart the resource adapter.

KDJE58354-E

An error occurred while the request was being received. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, exception = gg....gg, read count = hh....hh)

aa....aa: Resource adapter display name

bb....bb: Service group name (if the service group name cannot be determined, a single-byte hyphen (-) is displayed)

cc....cc: Service name (if the service name cannot be determined, a single-byte hyphen (-) is displayed)

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1 (if the listen port number cannot be determined, a single-byte hyphen (-) is displayed)

ff....ff: CommNo of root AP information

gg....gg: Information of occurring error

hh....hh: Occurrence count of the read method of each connection

Description

While receiving the RPC request using the TP1 inbound integrated functionality, the RPC request reception is interrupted because of a communication problem, such as a timeout and disconnection.

If a connection is established, the connection will be disconnected.

Action

Check whether the problem exists in the communication lines or OpenTP1, and then remove the problem.

KDJE58355-E

The request data is invalid. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, detail = gg....gg)

aa....aa: Resource adapter display name

bb....bb: Service group name (if the service group name cannot be determined, a single-byte hyphen (-) is displayed)

cc....cc: Service name (if the service name cannot be determined, a single-byte hyphen (-) is displayed)

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1 (if the listen port number cannot be determined, a single-byte hyphen (-) is displayed)

ff....ff: CommNo of root AP information

gg....gg: Details

Description

While receiving the RPC request using the TP1 inbound integrated functionality, an invalid data is received. An error has occurred in the settings of OpenTP1, or a client other than OpenTP1 client is connected.

The received data will be cancelled, and then the connection will be disconnected.

Action

Take the following action based on the details:

header: Received header contents (hexadecimal 12 digits)

Check whether an invalid client is connected. If an invalid client is connected, modify the settings in such a way so that the invalid client is disconnected.

Scheduler direct function is not used.

Check that the user service network definition uses the scheduler direct function.

dc_rpc_call function is not used.

Check that the dc_rpc_call function is used, and the service is invoked.

It is not the first request data.

The RPC request message received by the TP1 inbound adapter might not be the first message, and might be a later message. Re-execute the RPC request.

An illegal client is connected. (Maintenance information)

Check whether an invalid client is connected. If an invalid client is not connected, collect the maintenance information, and then contact maintenance personnel.

KDJE58356-E

The request data is not supported. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, detail = gg....gg)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

gg....gg: Detail

Description

The TP1 inbound integrated functionality received an unsupported data while receiving the RPC request.

The received data will be cancelled, and then the connection will be disconnected.

Action

Take the following action based on the detail:

The value of the flags argument of the dc_rpc_call function is illegal.

Check that DCNOFLAGS or DCNOFLAGS | DCRPC_TPNOTRAN is specified in the flags argument of the dc_rpc_call functionality.

Version of OpenTP1 is not supported.

Check that OpenTP1 version is a supported version.

User data compression function is not supported.

Check that the user data compression functionality (Y in the rpc_datacomp operand of the common system definitions) is not used.

TP1/ Online Tester is not supported.

Check that OpenTP1 does not use the online tester.

KDJE58357-E

The service group name specified in the request is invalid. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

The TP1 inbound integrated functionality received an invalid service group name of the RPC request.

An error exists in the service group name specified in the service_group property of the TP1 inbound adapter or in the service group name of the RPC request.

The received data will be cancelled, and then the connection will be disconnected.

Action

Check whether the service group name specified in the group argument of the dc_rpc_call functionality and the service group name set up in the service_group property of the TP1 inbound adapter are correct.

If the service group name specified in the group argument of the dc_rpc_call functionality is incorrect, remove the problem, and then resend the message.

If the service group name set up in the resource adapter properties is incorrect, stop the resource adapter, change the value of the property, and then restart the resource adapter.

Note that if the service group name is invalid, OpenTP1 resends the RPC request. For this reason, this message will be output only the number of times the RPC request is resent from OpenTP1.

KDJE58358-E

A timeout occurred while the request was being received. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

A timeout occurred while receiving the RPC request in the TP1 inbound integrated functionality.

The RPC request being received is cancelled, and then the connection is disconnected.

Action

Check whether a problem exists in the communication line and OpenTP1, and then remove the problem.

Also check whether a problem exists in the timeout value of the RPC request reception set up in the rpc_receive_timeout property of the TP1 inbound adapter. If the problem exists, stop the resource adapter, change the value of the property, and then restart the resource adapter.

KDJE58359-E

There is not enough space in the buffer to process the request. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

The temporary buffer area, required for RPC request reception with the TP1 inbound integrated functionality, is insufficient.

The RPC request being received will be cancelled, and then the connection will be disconnected.

Action

The message structure list for processing the RPC request temporarily is insufficient. Resend the RPC request. If this message is output continuously, leave the timeout time from the start of the message reception until the message reception ends (rpc_receive_timeout) for a while, and then resend the RPC request or stop and restart the resource adapter.

KDJE58360-E

The number of received requests exceeds the waiting schedule queue limit. The request failed. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

The number of RPC requests pending processing in the TP1 inbound integrated functionality has reached the full schedule queue size. New received RPC requests will be cancelled.

Action

Check whether the setting of the schedule queue size set up in the queue_max_length property of the TP1 inbound adapter is appropriate.

If the set up value is inappropriate, stop the J2EE application, change the value of the property, and then restart the J2EE application.

KDJE58361-W

The number of queued requests has reached the warning level. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, rate = dd....dd, current value = ee....ee, max = ff....ff, next warn interval = gg....gg)

aa....aa: Resource adapter display name

bb....bb: Service group name of resource adapter

cc....cc: Service name of MDB (service)

dd....dd: Current use rate

ee....ee: Current value

ff....ff: Maximum value

gg....gg: Interval until next warning

Description

The percentage of RPC requests retained in the schedule queue of the TP1 inbound integrated functionality has reached the warning area.

Action

Check whether the schedule queue size specified in the queue_max_length property of the TP1 inbound adapter is appropriate.

If this message is output frequently, check whether stay_watch_queue_rate and stay_watch_check_interval specified in the properties of the TP1 inbound adapter are appropriate.

If the specified values are inappropriate, stop the J2EE application, change the values of the property, and then restart the J2EE application.

KDJE58362-E

The service name specified in the request is invalid. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

The TP1 inbound integrated functionality received an invalid service name. The causes might be as follows:

An error exists in the service name specified in the service property of ActivationSpec of MDB (service) or in the RPC request service name.

J2EE application (MDB) does not exist or is not operating.

The received data will be cancelled, and then the connection will be disconnected.

Action

Check the following contents:

Check that the service name specified in the service argument of the dc_rpc_call functionality is correct. If the service name is incorrect, remove the problem, and then resend the RPC request. If the service name is correct, check whether MDB (service) is operating.

Check that the service name specified in the service property of ActivationSpec of MDB (service) is correct. If the service name is incorrect, stop the J2EE application, correct the service name, and then restart the J2EE application.

If MDB (service) is not operating, start the J2EE application.

KDJE58363-E

Transaction linkage could not be started. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

Transaction linkage could not be started in OpenTP1.

Action

Specify true in ejbserver.distributedtx.XATransaction.enabled key of usrconf.properties (User property file for J2EE server) for transaction linkage in OpenTP1.

KDJE58400-E

An attempt to connect with OpenTP1 has failed. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, exception = gg....gg)

aa....aa: Resource adapter display name

bb....bb: Service group name (When service group name cannot be determined, a single-byte hyphen (-) is displayed)

cc....cc: Service name (When service name cannot be determined, a single-byte hyphen (-) is displayed)

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

gg....gg: Information of occurring exception

Description

An attempt is made to respond to the RPC request received by the TP1 inbound integrated functionality, but the connection with OpenTP1 has failed.

The response will be cancelled.

Action

Check that OpenTP1 is operating normally and no problem has occurred in the communication lines of OpenTP1 and TP1 inbound adapter.

If problems of temporary communication lines such as depletion of port due to concentration of load occur, connection with OpenTP1 might succeed by retrying while sending a response.

Check whether settings of the retry interval while sending response (send_retry_interval) and the retry count (send_retry_count) are appropriate.

If there is no problem in OpenTP1 and the communication line, check whether the setting of the timeout time (connection_timeout) of the send connection of the TP1 inbound adapter is appropriate.

KDJE58401-E

An error occurred while the RPC response data was being sent to OpenTP1. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, exception = gg....gg)

aa....aa: Resource adapter display name

bb....bb: Service group name (When service group name cannot be determined, a single-byte hyphen (-) is displayed)

cc....cc: Service name (When service name cannot be determined, a single-byte hyphen (-) is displayed)

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

gg....gg: Information of occurring exception

Description

An attempt is made to respond to the RPC request received by the TP1 inbound integrated functionality, but an error occurred while sending the message.

The sending connection will be disconnected, and then the response will be cancelled.

Action

The connection with OpenTP1 might be connected. Check whether a problem exists in the communication line of OpenTP1 and the TP1 inbound adapter. If there is no problem, check whether the send timeout (tcp_send_timeout) setting of the TP1 inbound adapter is appropriate.

KDJE58402-W

An attempt to connect with OpenTP1 has failed. The connecting will retry. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, exception = gg....gg, retry count = hh....hh, retry interval = ii....ii)

aa....aa: Resource adapter display name

bb....bb: Service group name (When service group name cannot be determined, a single-byte hyphen (-) is displayed)

cc....cc: Service name (When service name cannot be determined, a single-byte hyphen (-) is displayed)

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

gg....gg: Information of occurring exception

hh....hh: Retry count

ii....ii: Retry intervals

Description

An attempt is made to respond to the RPC request received by the TP1 inbound integrated functionality, but an attempt to connect OpenTP1 has failed.

Execute retry.

Action

Check that OpenTP1 is operating normally, and no problem has occurred in the communication lines of OpenTP1 and the TP1 inbound adapter.

KDJE58403-W

An error occurred while the RPC response data was being sent to OpenTP1. The sending will retry. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, exception = gg....gg, retry count = hh....hh, retry interval = ii....ii)

aa....aa: Resource adapter display name

bb....bb: Service group name (When service group name cannot be determined, a single-byte hyphen (-) is displayed)

cc....cc: Service name (When service name cannot be determined, a single-byte hyphen (-) is displayed)

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

gg....gg: Information of occurring exception

hh....hh: Retry count

ii....ii: Retry intervals

Description

An attempt is made to respond to the RPC request received by the TP1 inbound integrated functionality, but an error occurred while sending the message.

Execute retry.

Action

The connection with OpenTP1 might be disconnected. Check whether a problem exists in the communication lines of OpenTP1 and the TP1 inbound adapter.

KDJE58450-I

The service started. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Service group name of the resource adapter

cc....cc: Service name of MDB (service)

Description

MDB (service) is started.

KDJE58452-W

The maximum for the message endpoint instance pool exceeds the number of message processing threads that can be executed at the same time. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, poolsize = dd....dd, threads = ee....ee)

aa....aa: Resource adapter display name

bb....bb: Service group name of the resource adapter

cc....cc: Service name of MDB (service)

dd....dd: Maximum number of instance pools of MDB (service)

ee....ee: Maximum number of invoked threads of MDB (service)

Description

The total of the maximum number of instance pools of MDB (service) invocation threads exceeds.

If the operation continues in this state, MDB (service) invocation threads might not be allocated, while executing the RPC request.

Action

Change the settings to "Sum up nodes of the maximum number of MDB (service) invocation threads ≥ the maximum number of instance pools of MDB (service)".

KDJE58453-I

The service ended. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc)

aa....aa: Resource adapter display name

bb....bb: Service group name of the resource adapter

cc....cc: Service name of MDB (service)

Description

MDB (service) is ended.

KDJE58455-E

The service was forcibly stopped. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

An executing MDB (service) is forced to terminate.

The stop process continues.

Action

Action is not required for canceling an executing MDB (service). If ending the execution of MDB (service), start MDB (service) after the forced termination, and then re-invoke the MDB (service).

KDJE58456-E

An error occurred while the service was being called. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

An ending MDB (service) is invoked.

Action

Action is not required if MDB (service) is not executed. To execute MDB (service) after ending MDB (service), re-start the MDB (service), and then re-invoke the MDB (service).

KDJE58457-E

A timeout occurred during execution of the service. The service will now be forcibly stopped. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

Description

A timeout occurred while executing MDB (service).

Action

Check whether the timeout setting value is appropriate. If the timeout setting value is appropriate, action is not required.

KDJE58459-E

A system exception occurred during execution of the service. (resource adapter = aa....aa, service group = bb....bb, service = cc....cc, client = dd....dd:ee....ee, RootAP CommNo = ff....ff, exception = gg....gg)

aa....aa: Resource adapter display name

bb....bb: Service group name

cc....cc: Service name

dd....dd: IP address of OpenTP1

ee....ee: Listen port number of OpenTP1

ff....ff: CommNo of root AP information

gg....gg: Information of occurring exception

Description

A system exception occurred in MDB (service).

Action

Remove the cause of the exception, and then make the changes to avoid occurrence of exceptions.

KDJE58501-E

A timeout occurred while waiting for a response to a temporary close request. (resource adapter = aa....aa, listen port = bb....bb)

aa....aa: Resource adapter display name

bb....bb: Listen port number

Description

The temporary close request could not be received though the maximum pending time of the temporary close response has lapsed, from the time the status of the request has changed to response pending status in temporary close processing,

The respective connection is disconnected forcibly.

Action

Determine whether there is a problem in communication channels or OpenTP1 and resolve the problem.

If KDJE58354-E is output for the same connection before and after this message, the timeout can be avoided when receiving messages from OpenTP1. In such cases, confirm that the maximum pending time for the temporary close response is applicable and if the problem still persists, perform the settings again.

KDJE58502-I

A connection to OpenTP1 has been established. (resource adapter = aa....aa, listen port = bb....bb, client = cc....cc:dd....dd)

aa....aa: Resource adapter display name

bb....bb: Listen port number

cc....cc: IP address of OpenTP1

dd....dd: Listen port number of OpenTP1 (When listen port number cannot be determined, a single-byte hyphen (-) is displayed)

Description

A connection to OpenTP1 has been established.

KDJE58503-I

A connection to OpenTP1 has been disconnected. (resource adapter = aa....aa, listen port = bb....bb, client = cc....cc:dd....dd)

aa....aa: Resource adapter display name

bb....bb: Listen port number

cc....cc: IP address of OpenTP1

dd....dd: Listen port number of OpenTP1 (When listen port number cannot be determined, a single-byte hyphen (-) is displayed)

Description

A connection to OpenTP1 has been disconnected.

KDJE58550-E

Transaction linkage could not be started. (resource adapter = aa....aa, client = bb....bb:cc....cc, TRNGID = dd....dd)

aa....aa: Resource adapter display name

bb....bb: IP address of OpenTP1

cc....cc: Listen port number of OpenTP1

dd....dd: Transaction global identifier

Description

Transaction linkage could not be started in OpenTP1.

Action

Specify true in ejbserver.distributedtx.XATransaction.enabled key of usrconf.properties (User property file for J2EE server) for transaction linkage in OpenTP1.

KDJE58551-E

An unexpected exception occurred. (resource adapter = aa....aa, client = bb....bb:cc....cc, global transaction ID = dd....dd, method = ee....ee, detail = ff....ff)

aa....aa: Resource adapter display name

bb....bb: IP address of OpenTP1

cc....cc: Listen port number of OpenTP1

dd....dd: Global transaction ID of OpenTP1

ee....ee: Method name

ff....ff: Details

Description

An unexpected exception occurred.

Action

Obtain the maintenance information and contact Maintenance Service.

KDJE59100-W

An invalid value is specified in the property. (property name = aa....aa, value = bb....bb, default value = cc....cc)

aa....aa: Property name

bb....bb: Specified character string

cc....cc: Default value of property

Description

An invalid value is specified in the property used by JavaMail. Use default value as the property value.

If the property name is mail.smtp.connectiontimeout, mail.smtps.connectiontimeout, mail.pop3.connectiontimeout, mail.smtp.timeout, mail.smtps.timeout, or mail.pop3.timeout, INFINITE is output as the default property value.

Action

Check property settings and specify appropriate values.

KDJE59101-E

An attempt to connect to the SMTP server failed. (host = aa....aa, port = bb....bb, connection timeout = cc....cc, message = dd....dd)

aa....aa: Specified host name

bb....bb: Specified port number

cc....cc: Timeout value until establishing connection

dd....dd: getMessage() result of the occurred exception

Description

JavaMail failed in an attempt to connect to the SMTP server.

If the user has not specified the mail.smtp.connectiontimeout property or the mail.smtps.connectiontimeout property, -1 is output as the timeout value.

Action

Check and, if necessary, revise the values specified in the host name, port number, and the mail.smtp.connectiontimeout property or the mail.smtps.connectiontimeout property. Also, check the environment settings of network if valid values are specified in the host name, port number, and property.

KDJE59102-E

An attempt to disconnect from the SMTP server failed. (host = aa....aa, port = bb....bb, message = cc....cc)

aa....aa: Host name

bb....bb: Port number

cc....cc: getMessage() result of the occurred exception

Description

JavaMail failed in an attempt to disconnect to the SMTP server.

Action

Check and, if necessary, revise the environment settings of network.

KDJE59103-E

An attempt to connect to the POP3 server failed. (host = aa....aa, port = bb....bb, connection timeout = cc....cc, message = dd....dd)

aa....aa: Specified host name

bb....bb: Specified port number

cc....cc: Timeout value until establishing the connection

dd....dd: getMessage() result of the occurred exception

Description

JavaMail failed in an attempt to connect to the POP3 server.

If the user has not specified the mail.pop3.connectiontimeout property, -1 is output as the timeout value.

Action

Check and, if necessary, revise the values specified in the host name, port number, and mail.pop3.connectiontimeout property. Also check the environment settings of network if valid values are specified in the host name, port number, and property.

KDJE59104-E

An attempt to disconnect from the POP3 server failed. (host = aa....aa, port = bb....bb, message = cc....cc)

aa....aa: Host name

bb....bb: Port number

cc....cc: getMessage() result of the occurred exception

Description

JavaMail failed in an attempt to disconnect with POP3 server.

Action

Check and, if necessary, revise the environment settings of network.

KDJE59105-E

An exception occurred during communication with the SMTP server. (communication processing = aa....aa, timeout = bb....bb, message = cc....cc)

aa....aa: Character string indicating communication processing

bb....bb: Communication timeout value

cc....cc: getMessage() result of the occurred exception

Description

An exception occurred in the JavaMail and SMTP server communication.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.1 For the SMTP and SMTPS related messages.

If the user has not specified the mail.smtp.timeout property or the mail.smtps.timeout property, -1 is output as the timeout value.

Action

Check and, if necessary, revise the value specified for the mail.smtp.timeout property or the mail.smtps.timeout property, when a timeout occurs. Alternatively, check the environment settings of network.

KDJE59106-E

An exception occurred during communication with the POP3 server. (communication processing = aa....aa, timeout = bb....bb, message = cc....cc)

aa....aa: Character string indicating communication processing

bb....bb: Communication timeout value

cc....cc: getMessage() result of the occurred exception

Description

An exception occurred in the JavaMail and POP3 server communication.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.2 For the POP3-related messages.

If the user has not specified the mail.pop3.timeout property, -1 is output as the timeout value.

Action

Check and, if necessary, revise the value specified for the mail.pop3.timeout property when timeout occurs. Alternatively, check the environment settings of network.

KDJE59107-E

While trying to connect to the SMTP server, JavaMail received an abnormal response code. (response = aa....aa, response code = bb....bb)

aa....aa: Response from server

bb....bb: Normally terminated response code

Description

When trying to connect to the SMTP server, JavaMail has received an abnormal response code.

Output the response code for the response from server.

Action

Determine the cause by referencing the response and log of the SMTP server and the SMTP server manual.

KDJE59108-E

While trying to communicate with the SMTP server, JavaMail received an abnormal response code. (communication processing = aa....aa, response = bb....bb, response code = cc....cc)

aa....aa: Character string indicating communication processing

bb....bb: Response from server

cc....cc: Normally terminated response code

Description

While trying to communicate with the SMTP server, JavaMail has received an abnormal response code.

Output the response code for the response from server.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.1 For the SMTP and SMTPS related messages.

Action

Determine the cause by referencing the response and log of the SMTP server and the SMTP server manual, and then take action.

KDJE59109-E

While trying to connect with the POP3 server, JavaMail received an abnormal response code. (response = aa....aa)

aa....aa: Response from server

Description

When trying to connect with the POP3 server, JavaMail received an abnormal response code.

Output the response code for the response from server.

Action

Determine the cause by referencing the response and log of POP3 server and the POP3 server manual, and then take action.

KDJE59110-E

While trying to communicate with the POP3 server, JavaMail received an abnormal response code. (communication processing = aa....aa, response = bb....bb)

aa....aa: Character string indicating communication processing

bb....bb: Response from server

Description

When trying to communicate with the POP3 server, JavaMail received an abnormal response code.

Output the response code for the response from server.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.2 For the POP3-related messages.

Action

Determine the cause by referencing the response and log of POP3 server and the POP3 server manual, and then take action.

KDJE59111-E

An invalid response was received from the SMTP server. (communication processing = aa....aa, response = bb....bb)

aa....aa: Character string indicating communication processing

bb....bb: Response from server

Description

An invalid response other than RFC specifications was received from the SMTP server.

Only the first row of response is output for the response received from the server. However, if no response exists, an empty string is displayed.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.1 For the SMTP and SMTPS related messages.

Action

Take actions according to the log and trace information.

KDJE59112-E

An invalid response was received from the POP3 server. (communication processing = aa....aa, response = bb....bb)

aa....aa: Character string indicating communication processing

bb....bb: Response from server

Description

An invalid response other than RFC specifications was received from the POP3 server.

Only the first row of response is output for the response received from the server. However, if no response exists, an empty string is displayed.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.2 For the POP3-related messages.

Action

Take actions according to the log and trace information.

KDJE59113-E

An argument of a response received from the POP3 server has an invalid format. (communication processing = aa....aa, response = bb....bb)

aa....aa: Character string indicating communication processing

bb....bb: Response from server

Description

An argument of a response received from the POP3 server has an invalid format.

Only the first row of response is output for the response received from the server. However, for the response from mail receiving commands (TOP, RETR), only the response code is output.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.2 For the POP3-related messages.

Action

Take actions according to the log and trace information.

KDJE59114-E

An argument of a response received from the SMTP server has an invalid format. (communication processing = aa....aa, response = bb....bb)

aa....aa: String indicating communication processing

bb....bb: Response passed from server

Description

An argument of response received from the SMTP server has an invalid format.

Only the first row of response is output for the response received from the server. However, for the response of completion of sending data (\r\n.) for the mail, only the response code is output.

For details on contents output to aa....aa and corresponding communication processing, see 7.10.1 For the SMTP and SMTPS related messages.

Action

Take actions according to the log and trace information.

KDJE59200-E

An error occurred in the aa....aa phase, during processing of the EL expression bb....bb for the attribute cc....cc. (detail = dd....dd)

aa....aa: Phase ID

bb....bb: EL expression (Expression Langage)

cc....cc: beforePhase or afterPhase

dd....dd: Exception information

Description

An error occurred due to the beforePhase attribute or afterPhase attribute of the <f:view> tag in the JSP file or Facelets file.

Action

Review, and if necessary revise, the EL expression set in the beforePhase attribute or afterPhase attribute of the <f:view> tag in the JSP file or Facelets file. Also, review, and if necessary revise, the implementation of the methods referenced by the EL expression.

See the exception information and then take action.

KDJE59201-E

An error occurred when actionListener aa....aa was invoked for the component bb....bb. (detail = cc....cc)

aa....aa: EL expression (Expression Langage)

bb....bb: Component ID

cc....cc: Exception information

Description

An error occurred due to the actionListener attribute of the <f:commandButton> tag or <f:commandLink> tag in the JSP file or Facelets file.

Action

Review, and if necessary revise, the EL expression set in the actionListener attribute of the <f:commandButton> tag or <f:commandLink> tag in the JSP file or Facelets file. Also, review, and if necessary revise, the implementation of the methods referenced by the EL expression.

See the exception information and then take action.

KDJE59202-E

An error occurred during beforePhase() processing of the aa....aa phase for UIComponent-ClientId=bb....bb. (detail = cc....cc)

aa....aa: Phase ID

bb....bb: Client ID

cc....cc: Exception information

Description

An error occurred during the processing of the beforePhase method of the PhaseListener class specified in the Faces configuration file.

Action

Review, and if necessary revise, the implementation of the beforePhase method of the PhaseListener class specified in the Faces configuration file.

See the exception information and then take action.

KDJE59203-E

An error occurred during afterPhase() processing of the aa....aa phase for UIComponent-ClientId=bb....bb. (detail = cc....cc)

aa....aa: Phase ID

bb....bb: Client ID

cc....cc: Exception information

Description

An error occurred during the processing of the afterPhase method of the user-defined PhaseListener class specified in the Faces configuration file.

Action

Review, and if necessary revise, the implementation of the afterPhase method of the PhaseListener class specified in the Faces configuration file.

See the exception information and then take action.

KDJE59204-E

An error occurred during processing of the aa....aa phase for UIComponent-ClientId=bb....bb. (detail = cc....cc)

aa....aa: Phase ID

bb....bb: Client ID

cc....cc: Exception information

Description

An error occurred due to the following tag attributes in the JSP file or Facelets file:

The actionListener attribute of the <f:commandButton> tag and <f:commandLink> tag

The valueChangeListener attribute of the <h:inputHidden> tag, <inputSecret> tag, <h:inputText> tag, <h:inputTextarea> tag, <h:selectBooleanCheckbox> tag, <h:selectManyCheckbox> tag, <h:selectManyListbox> tag, <h:selectManyMenu> tag, <h:selectOneListbox> tag, <h:selectOneMenu> tag, and <h:selectOneRadio> tag

The type attribute of the <f:actionListener> tag, <f:valueChangeListener> tag, and <f:phaseListener> tag

The value or type attributes of the <f:setPropertyActionListener> tag

Action

Review, and if necessary revise, the settings specified in the JSP file or Facelets file as follows:

Review, and if necessary revise, the EL expression set in the actionListener attribute. Also, review, and if necessary revise, the implementation of the methods referenced by the EL expression.

Review, and if necessary revise, the EL expression set in the valueChangeListener attribute. Also, review, and if necessary revise, the implementation of the methods referenced by the EL expression.

Review, and if necessary revise, the type attribute of the <f:actionListener> tag, <f:valueChangeListener> tag, or <f:phaseListener> tag.

Review, and if necessary revise, the EL expression set in the value or target attributes of the <f:setPropertyActionListener> tag.

See the exception information and then action.

KDJE59205-E

An error occurred when phaseListener was invoked. (detail = aa....aa)

aa....aa: Exception information

Description

An error occurred in a method of the PhaseListener class set in the <f:phaseListener> tag of the JSP file or Facelets file.

Action

Review, and if necessary revise, the implementation of the method of the PhaseListener class set in the <f:phaseListener> tag of the JSP file or Facelets file.

See the exception information and then take action.

KDJE59206-E

An error occurred during processing of the deployment descriptor for the context aa....aa. (detail = bb....bb)

aa....aa: Context root name

bb....bb: Exception information

Description

An error occurred while the web.xml file was being parsed.

Action

Review, and if necessary revise, the web.xml file settings.

See the exception information and then take action.

KDJE59207-E

An error occurred during processing of the action expression aa....aa for the component bb....bb. (detail = cc....cc)

aa....aa: EL expression (Expression Langage)

bb....bb: Client ID

cc....cc: Exception information

Description

An error occurred due to the action attribute of the <h:commandButton> tag or <h:commandLink> tag in the JSP file or Facelets file.

Action

Review, and if necessary revise, the EL expression set in the action attribute of the <h:commandButton> tag and <h:commandLink> tag in the JSP file or Facelets file. Also, review, and if necessary revise, the implementation of the methods referenced by the EL expression.

See the exception information and then take action.

KDJE59208-I

Initialization of the JSF application finished successfully. (context name = aa....aa)

aa....aa: Context root name

Description

The JSF application was initialized successfully.

KDJE59209-E

An error occurred during initialization of the JSF application. (context name = aa....aa, detail = bb....bb)

aa....aa: Context root name

bb....bb: Exception information

Description

An error occurred during the initialization of the JSF application.

Action

See the exception information and then take action.

KDJE59210-E

An error occurred during termination of the JSF application. (context name = aa....aa, detail = bb....bb)

aa....aa: Context root name

bb....bb: Exception information

Description

An error occurred during the termination of the JSF application.

Action

See the exception information and then take action.

KDJE59211-E

An error occurred during decoding of the flash data from an incoming cookie. Processing will continue, but the flash is unavailable for this request. (detail = aa....aa)

aa....aa: Exception information

Description

An error occurred while reading the Cookie for the Flash object data.

Action

See the exception information and then take action.

KDJE59212-E

An error occurred during rendering of the response for the component aa....aa. (detail = bb....bb)

aa....aa: Client ID

bb....bb: Exception information

Description

An error occurred while a response was being written to the client during Ajax communication.

Action

See the exception information and then take action.

KDJE59213-E

An error occurred during updating of the model phase for the component aa....aa. (detail = bb....bb)

aa....aa: Client ID

bb....bb: Exception information

Description

An error occurred when the value input by the user was being set in the ManagedBean.

Action

See the exception information and then take action.

KDJE59214-E

An error occurred during PreDestroy processing for the ManagedBean aa....aa. (detail = bb....bb)

aa....aa: ManagedBean name

bb....bb: Exception information

Description

An error occurred during the processing of the PreDestroy method of the ManagedBean.

Action

Review, and if necessary revise, the signature or implementation of the PreDestroy method of the ManagedBean.

See the exception information and then take action.

KDJE59215-I

Termination of the JSF application finished successfully. Context name = aa....aa

aa....aa: Context root name

Description

The JSF application was terminated successfully.

KDJE59216-W

The specified parameter value is invalid. The default value will be used. (aa....aa = bb....bb, default value = cc....cc)

aa....aa: Parameter name

bb....bb: Parameter value

cc....cc: Default value

Description

The value specified in the context parameter is invalid. The default value will be set up.

Action

Specify the correct value in the context parameter.

KDJE59217-W

The specified parameter value is invalid. This parameter setting will be ignored because a default value does not exist. (aa....aa = bb....bb)

aa....aa: Parameter name

bb....bb: Parameter value

Description

The value specified in the context parameter is invalid. The settings for this context parameter will be ignored.

Action

Specify the correct value in the context parameter.

KDJE59218-W

An empty string value is set for the parameter aa....aa. The default value will be used. (default value = bb....bb)

aa....aa: Parameter name

bb....bb: Default value

Description

The value set in the context parameter is a null character. The default value will be set up.

Action

Specify the correct value in the context parameter.

KDJE59219-W

An empty string value is set for the parameter aa....aa. This parameter setting will be ignored because a default value does not exist.

aa....aa: Parameter name

Description

The value specified in the context parameter is invalid. The settings for this context parameter will be ignored.

Action

Specify the correct value in the context parameter.

KDJE59220-W

The specified JNDI parameter value is invalid. The default value will be used. (aa....aa = bb....bb, default value = cc....cc)

aa....aa: Parameter name

bb....bb: Parameter value

cc....cc: Default value

Description

The value specified in the context parameter using JNDI is invalid. The default value will be set up.

Action

Specify the correct value in the context parameter.

KDJE59221-W

An empty string value is set for the JNDI parameter aa....aa. The default value will be used. (default value = bb....bb)

aa....aa: Parameter name

bb....bb: Default value

Description

The value specified in the context parameter using JNDI is a null character.The default value will be set up.

Action

Specify the correct value in the context parameter.

KDJE59222-W

The specified resource was not found. The resource will be ignored. (aa....aa = bb....bb)

aa....aa: Parameter name

bb....bb: Default value

Description

The specified config file name does not exist in javax.faces.CONFIG_FILES or javax.faces.FACELETS_LIBRARIES of the context parameter. The settings for this context parameter will be ignored.

Action

Specify the correct value in the context parameter.

KDJE59223-W

An invalid aa....aa is set for the parameter. (bb....bb = cc....cc)

aa....aa: Set value type

bb....bb: Parameter name

cc....cc: Parameter value

Description

The value specified in the context parameter is invalid.

Action

Specify the correct value in the context parameter.

KDJE59224-W

The specified parameter value is invalid. aa....aa will be used as the value. (bb....bb = cc....cc)

aa....aa: Value set for the parameter

bb....bb: Parameter name

cc....cc: Parameter value

Description

The value specified in the context parameter is invalid. aa....aa will be used as the value.

Action

Specify the correct value in the context parameter.

KDJE59225-W

An empty string value is set for the parameter aa....aa. bb....bb will be used as the value.

aa....aa: Parameter name

bb....bb: Value set for the parameter

Description

The value specified in the context parameter is a null character. aa....aa will be used as the value.

Action

Specify the correct value in the context parameter.

KDJE59226-W

The specified delimiter is invalid. The first character of the specified value aa....aa will be used as the delimiter. (bb....bb = cc....cc)

aa....aa: First character of the parameter value

bb....bb: Parameter name

cc....cc: Parameter value

Description

The value specified in the context parameter is invalid. aa....aa will be used as the value.

Action

Specify the correct value in the context parameter.

KDJE59227-I

A Facelets file was modified. (file name = aa....aa)

aa....aa: Changed Facelets file name

Description

A Facelets file of the JSF application has been modified.

KDJE59300-I

Application verification started. The beans.xml file will now be searched for in the application aa....aa.

aa....aa: Application name

Description

The verification of the application started. The beans.xml file will be searched in the application aa....aa.

KDJE59301-I

Verification completed. The beans.xml file was found in the module aa....aa of the application bb....bb.

aa....aa: Module name

bb....bb: Application name

Description

The verification is complete. The beans.xml file was found in the module aa....aa of the application bb....bb.

KDJE59302-I

Verification completed. The beans.xml file was not found in the application aa....aa.

aa....aa: Application name

Description

The verification is complete. The beans.xml file was not found in the application aa....aa.

KDJE59303-I

Pre-deployment processing started for the module bb....bb in the CDI application aa....aa.

aa....aa: Application name

bb....bb: Module name

Description

The pre-deployment processing started for the module bb....bb in the CDI application aa....aa.

KDJE59304-I

Pre-deployment processing ended for the module bb....bb in the CDI application aa....aa.

aa....aa: Application name

bb....bb: Module name

Description

The pre-deployment processing ended for the module bb....bb in the CDI application aa....aa.

KDJE59305-I

The CDI application is now being deployed. The application name is aa....aa.

aa....aa: Application name

Description

The CDI application is being deployed. The application name is aa....aa.

KDJE59306-I

The CDI application aa....aa was successfully deployed.

aa....aa: Application name

Description

The CDI application aa....aa was successfully deployed.

KDJE59307-I

The CDI application is now starting. The application name is aa....aa.

aa....aa: Application name

Description

The CDI application is starting. The application name is aa....aa.

KDJE59308-I

The CDI application aa....aa was successfully started.

aa....aa: Application name

Description

The CDI application aa....aa was successfully started.

KDJE59309-I

The CDI application is now stopping. The application name is aa....aa.

aa....aa: Application name

Description

The CDI application is stopping. The application name is aa....aa.

KDJE59310-I

The CDI application aa....aa was successfully stopped.

aa....aa: Application name

Description

The CDI application aa....aa was successfully stopped.

KDJE59311-E

An exception occurred while verifying the CDI application. (details = aa....aa).

aa....aa: Exception details

Description

An exception occurred while verifying the CDI application.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59312-E

An exception occurred during pre-deployment processing of the CDI application. (details = aa....aa)

aa....aa: Exception details

Description

An exception occurred during the pre-deployment processing of the CDI application.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59313-E

An exception occurred while deploying the CDI application. (details = aa....aa)

aa....aa: Exception details

Description

An exception occurred while deploying the CDI application.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59314-E

An exception occurred while starting the CDI application. (details = aa....aa)

aa....aa: Exception details

Description

An exception occurred while starting the CDI application.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59315-E

An exception occurred while stopping the CDI application. (details = aa....aa)

aa....aa: Exception details

Description

An exception occurred while stopping the CDI application.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59316-E

Acquisition of an EJB reference failed. (EJB name = aa....aa, JNDI name = bb....bb, details = cc....cc)

aa....aa: Class name

bb....bb: JNDI name

cc....cc: Exception details

Description

An attempt to acquire an EJB reference failed.

Action

An EJB cannot be injected using a CDI annotation. Check the application, and modify the settings so that an EJB is not injected using a CDI annotation.

KDJE59317-E

The JNDI name required to acquire an EJB reference could not be acquired. (EJB name = aa....aa)

aa....aa: Class name

Description

The JNDI name required to acquire an EJB reference could not be acquired.

Action

An EJB cannot be injected using a CDI annotation. Check the application, and modify the settings so that an EJB is not injected using a CDI annotation.

KDJE59319-E

The transaction status cannot be acquired. (details = aa....aa)

aa....aa: Exception details

Description

The transaction status cannot be acquired.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59320-E

An instance of the aa....aa class cannot be instantiated via the no-argument constructor. (details = bb....bb)

aa....aa: Class name

bb....bb: Exception details

Description

The aa....aa class cannot be instantiated using the no-argument constructor.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59321-E

The aa....aa class constructor contains an invalid argument. (details = bb....bb)

aa....aa: Class name

bb....bb: Exception details

Description

The argument of the aa....aa class constructor is invalid.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59322-E

An internal status is invalid.

Description

An internal status is invalid.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59323-E

The BeanManager interface cannot be resolved. (details = aa....aa)

aa....aa: Exception details

Description

The BeanManager interface cannot be resolved.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59325-E

The aa....aa class cannot be loaded. (details = bb....bb)

aa....aa: Class name

bb....bb: Exception details

Description

The aa....aa class cannot be loaded.

Action

Take action, if possible, based on the details output in the message log and exception log.

If the cause cannot be identified, collect the maintenance information, and then contact maintenance personnel.

KDJE59326-E

A class was not found while loading the local business interface aa....aa. (details = bb....bb)

aa....aa: Name

bb....bb: Exception details

Description

A class was not found while loading the local business interface aa....aa.

Action

An EJB cannot be injected using a CDI annotation. Check the application, and modify the settings so that an EJB is not injected using a CDI annotation.

KDJE59328-E

The remove method in the EJB aa....aa class cannot be resolved.

aa....aa: Class name

Description

The remove method in the EJB aa....aa class cannot be resolved.

Action

An EJB cannot be injected using a CDI annotation. Check the application, and modify the settings so that an EJB is not injected using a CDI annotation.

KDJE59329-E

A class was not found while loading the remote business interface aa....aa. (details = bb....bb)

aa....aa: Class name

bb....bb: Exception details

Description

A class was not found while loading the remote business interface aa....aa.

Action

An EJB cannot be injected using a CDI annotation. Check the application, and modify the settings so that an EJB is not injected using a CDI annotation.

7.6 Messages from KDJE60000 to KDJE69999

This section explains the messages from KDJE60000 to KDJE69999.

KDJE60001-I

The J2EE server will start as ''Java EE Container Mode''. (container version = aa....aa)

aa....aa: Value of the container version

Description

This message indicates that this J2EE server will run in Java EE container mode.

KDJE60003-E

Unexpected exception occurred during Java EE Container mode initialization. (detail = aa....aa)

aa....aa: Detailed information of the occurred exception

Description

Unexpected exception occurred during Java EE Container mode initialization.

Action

Contact maintenance personnel.

KDJE60004-E

Unexpected exception occurred during Java EE Container mode termination. (detail = aa....aa)

aa....aa: Detailed information of the occurred exception

Description

Unexpected exception occurred during Java EE Container mode termination.

Action

Contact maintenance personnel.

KDJE60005-E

An illegal configuration file is specified. (container version = aa....aa, configuration file version = bb....bb)

aa....aa: Value of the container version

bb....bb: Value of the definition file version

Description

Startup of the J2EE server is interrupted because the container version of the J2EE server does not match the expected version of the specified definition file.

Action

After the logical J2EE server having the same name created by using the management portal or Smart Composer functionality was deleted, unsetup of the J2EE server might not have been performed.

Delete the logical J2EE server, perform unsetup by using the cjsetup command (server management command), and then re-create and set up the logical J2EE server.

KDJE60010-W

Some message IDs for output suppression will be ignored, because the ones specified for the property ejbserver.javaeeLogfilter.msgids are invalid.

Description

The message ID specified for the property ejbserver.javaeeLogfilter.msgids is invalid.

Action

Revise the set value of the property ejbserver.javaeeLogfilter.msgids, set the correct value, and then restart the J2EE server.

KDJE60011-I

Message output will be suppressed. (message ID = aa....aa)

aa....aa: List of message IDs (separated by commas)

Description

Output of messages that match the specified message IDs to the public log is suppressed.

KDJE60014-W

Unexpected exception occurred during Java EE logger initialization. (detail = aa....aa)

aa....aa: Detailed information of the occurred exception

Description

Unexpected exception occurred during Java EE logger initialization.

Action

Contact maintenance personnel.

KDJE60110-W

The character string length of the constraint violation message which is used in the function that is based on the Bean Validation specification is longer than the value of the system property ejbserver.javaee.bv.message-interpolation.alert-threshold. (tid = aa....aa, property value = bb....bb, message length = cc....cc, message = dd....dd)

aa....aa: Thread ID

bb....bb: Value of the system property ejbserver.javaee.bv.message-interpolation.alert-threshold

cc....cc: Character string length of the constraint violation message to be used as the interpolation target of Bean Validation

dd....dd: Constraint violation message to be used as the interpolation target of Bean Validation. This message consists of the first part containing 100 characters, an asterisk (*), and the last part containing 100 characters.

Description

The character string length of the constraint violation message which is used in the function that is based on the Bean Validation specification is longer than the value of the system property ejbserver.javaee.bv.message-interpolation.alert-threshold.

Action

Revise the application configuration to confirm that excessively long constraint messages will not be used. Alternatively, confirm that the value of the system property is appropriate and, if necessary, revise it.

KDJE60111-W

An invalid property value is specified. The default value will be used. (property = aa....aa, value = bb....bb, default value = cc....cc)

aa....aa: Property name

bb....bb: User-specified value

cc....cc: Default value

Description

An invalid property value is specified. The default value will be used.

Action

Check the value specified for the relevant property, and then specify a value within the specifiable range.

KDJE60130-I

Exporting the list of deleting batch jobs is complete.

Description

The list of batch jobs to be deleted was output successfully.

Action

Check the contents of the list of deleting batch jobs.

KDJE60131-W

The list of deleting batch jobs was not exported because no matching batch jobs found.

Description

The list of batch jobs to be deleted was not output because no data matched the deletion condition.

KDJE60132-E

The specified path is invalid. (path = aa....aa)

aa....aa: Specified path name

Description

The specified path is invalid.

Action

Specify a nonexistent file path as an absolute path in the deletion-target list file.

KDJE60133-E

An exception occurred during obtaining the list of deleting batch jobs from database. (details = aa....aa)

aa....aa: Detailed information of the occurred exception

Description

An exception occurred while the database was being accessed.

Action

Remove the cause of the error by referencing the detailed information.

KDJE60134-E

An exception occurred during output the list of deleting batch jobs. (path = aa....aa, details = bb....bb)

aa....aa: Specified path name

bb....bb: Detailed information of the occurred exception

Description

An exception occurred while the file was being accessed.

Action

Remove the cause of the error by referencing the detailed information.

KDJE60135-I

Deleting batch jobs is complete.

Description

The batch job was deleted successfully.

KDJE60136-E

An exception occurred during reading the list of deleting batch jobs. (path = aa....aa, details = bb....bb)

aa....aa: Specified path name

bb....bb: Detailed information of the occurred exception

Description

An exception occurred while the file was being accessed.

Action

Remove the cause of the error by referencing the detailed information.

KDJE60137-E

The list of deleting batch jobs is invalid. (path = aa....aa)

aa....aa: Specified path name

Description

An attempt to analyze the deletion-target list file failed.

Action

Confirm that the file path to the deletion-target list file is correct. If the file path is correct, re-execute the cjdeljbatchjobs command (with -list specified).

KDJE60138-E

An exception occurred during deleting batch jobs from database. (details = aa....aa)

aa....aa: Detailed information of the occurred exception

Description

An exception occurred while the database was being accessed.

Action

Remove the cause of the error by referencing the detailed information.

KDJE60139-E

The number of records deleted from the database does not match with the specified file.

Description

The number of records to be deleted in the entered deletion-target list file does not match the number of records to be deleted when the cjdeljbatchjobs command (with -delete specified) is executed. One of the following operations might have been performed:

- The cjdeljbatchjobs command (with -delete specified) has already been executed.

- After the cjdeljbatchjobs command (with -list specified) was executed, batch processing is started before the cjdeljbatchjobs command (with -delete specified) is executed.

Action

Re-execute the cjdeljbatchjobs command (with -list specified) to create a deletion-target list file. Then, execute the cjdeljbatchjobs command (with -delete specified) by specifying the deletion-target list file you created.

KDJE60140-E

The configured application tag dose not match with the requested application tag.(apptag configured to J2EE server = aa....aa, requested apptag = bb....bb)

aa....aa: Application tag set for the J2EE server

bb....bb: Application tag obtained from the deletion-target list file

Description

The application tag set for the J2EE server (the value of the ejbserver.javaee.batch.J2EE-application-name.appTag system property or the default value) does not match the requested application tag (value of apptag in the deletion-target list file).

The followings might be the causes.

- The value of the system property is changed after the cjdeljbatchjobs command (with -list specified) was executed.

- The command is executed by specifying the J2EE server name that differs from the one used when the cjdeljbatchjobs command (with -list specified) was executed.

- The contents of the deletion-target list file are changed.

Action

Re-execute the cjdeljbatchjobs command (with -list specified) to create a deletion-target list file. Then, execute the cjdeljbatchjobs command (with -delete specified) by specifying the deletion-target list file you created.

KDJE60310-W

An invalid property value is specified. The default value will be used. (property = aa....aa, value = bb....bb, default value = cc....cc)

aa....aa: Property name

bb....bb: User-specified value

cc....cc: Default value

Description

An invalid property value is specified. The default value will be used.

Action

Check the value specified for the relevant property, and then specify a value within the specifiable range.

KDJE60311-E

A timeout occurred on the request operation of JAX-RS Client API. (reason = aa....aa, connect timeout = bb....bb, read timeout = cc....cc, RootAP = dd....dd, url = ee....ee)

aa....aa: Reason of timeout

bb....bb: Connection timeout set value (milliseconds)

cc....cc: Read timeout set value (milliseconds)

dd....dd: Root application information

ee....ee: Request destination URL

Description

A timeout occurred on the request operation of JAX-RS Client API.

Action

Remove the cause of the timeout.

KDJE60312-E

The JAX-RS Client API could not complete the requested operation. (detail = aa....aa, RootAP = bb....bb, url = cc....cc)

aa....aa: Detailed message

bb....bb: Root application information

cc....cc: Request destination URL

Description

The JAX-RS Client API could not complete the requested operation.

Action

Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJE60510-W

An invalid property value is specified. The default value will be used. (property = aa....aa, value = bb....bb, default value = cc....cc)

aa....aa: Property name

bb....bb: User-specified value

cc....cc: Default value

Description

An invalid property value is specified. The default value will be used.

Action

Check the value specified for the relevant property, and then specify a value within the specifiable range.

KDJE60511-I

The executor for Java Batch has registered. (jndiName = aa....aa, minThreads = bb....bb, maxThreads = cc....cc, queueSize = dd....dd, keepAliveTime = ee....ee)

aa....aa: JNDI name of the executor

bb....bb: Minimum number of threads in the thread pool

cc....cc: Maximum number of threads in the thread pool

dd....dd: Queue length of the thread pool

ee....ee: Maximum length of time to wait for a used thread to be reused (seconds)

Description

The executor for Java Batch has registered

KDJE60512-E

Unexpected exception occurred during registering the executor for Java Batch. (jndiName = aa....aa, minThreads = bb....bb, maxThreads = cc....cc, queueCapacity = dd....dd, keepAliveTime = ee....ee, details = ff....ff)

aa....aa: JNDI name of the executor

bb....bb: Minimum number of threads in the thread pool

cc....cc: Maximum number of threads in the thread pool

dd....dd: Queue length of the thread pool

ee....ee: Maximum length of time to wait for a used thread to be reused (seconds)

ff....ff: Detailed information of the occurred exception

Description

Unexpected exception occurred during registering the executor for Java Batch.

Action

Check the contents of the stack trace and then take action.

KDJE60513-E

Cannot find the specified executor for Java Batch. (jndiName = aa....aa, details = bb....bb)

aa....aa: JNDI name of the executor

bb....bb: Detailed information of the occurred exception

Description

Cannot find the specified executor for Java Batch.

Action

Check the KDJE60005-I message to make sure that the executor for Java Batch having the specified JNDI name has been registered correctly.

KDJE60514-E

Cannot find the specified data source for Java Batch. (jndiName = aa....aa, details = bb....bb)

aa....aa: JNDI name of the data source

bb....bb: Detailed information of the occurred exception

Description

Cannot find the specified data source for Java Batch.

Action

Make sure that the DB Connector having the specified JNDI name as an alias has started correctly.

KDJE60517-E

Can not find aa....aa for Job Repository of Java Batch. (name = bb....bb)

aa....aa: Check target

bb....bb: Name

Description

A job repository used to store information about batch jobs is not found.

Action

Create a job repository used to store information about batch jobs. If there is a remaining table or the like, clear the table, and then create a job repository.

KDJE60518-E

Failed to create aa....aa for Job Repository of Java Batch. (name = bb....bb)

aa....aa: Creation target

bb....bb: Name

Description

An attempt to create a job repository used to store information about batch jobs failed because repository generation was performed within the JTA transaction.

Action

Set ejbserver.javaee.batch.jobRepository.autoCreate.enabled as false.

KDJE60519-E

The data source used to store information about batch jobs is not HiRDB.

Description

The data source used to store information about batch jobs is not HiRDB.

Action

Make sure that the data source used to store information about batch jobs is HiRDB.

KDJE60810-W

An invalid property value is specified. The default value will be used. (property = aa....aa, value = bb....bb, default value = cc....cc)

aa....aa: Property name

bb....bb: User-specified value

cc....cc: Default value

Description

An invalid property value is specified. The default value will be used.

Action

Check the value specified for the relevant property, and then specify a value within the specifiable range.

KDJE60811-I

The specified ManagedExecutorService has been registered. (jndiName = aa....aa, hungAfterSeconds = bb....bb, longRunningTasks = cc....cc, corePoolSize = dd....dd, maxPoolSize = ee....ee, keepAliveSeconds = ff....ff, threadLifeTimeSeconds = gg....gg, threadPriority = hh....hh, taskQueueCapacity = ii....ii, awaitTerminationSeconds = jj....jj)

aa....aa: JNDI name

bb....bb: Task execution time after which the task is determined as no response (seconds)

cc....cc: Long-time task

dd....dd: Initial number of threads

ee....ee: Maximum number of threads

ff....ff: Maximum length of time to wait for a used thread to be reused (seconds)

gg....gg: Period of time to continuously reuse threads (seconds)

hh....hh: Priority of the thread

ii....ii: Queue length

jj....jj: Length of time to wait for the tasks to terminate when the server stops (seconds)

Description

The specified ManagedExecutorService has been registered.

KDJE60812-E

Unexpected exception occurred during registering the ManagedExecutorService. (jndiName = aa....aa, hungAfterSeconds = bb....bb, longRunningTasks = cc....cc, corePoolSize = dd....dd, maxPoolSize = ee....ee, keepAliveSeconds = ff....ff, threadLifeTimeSeconds = gg....gg, threadPriority = hh....hh, taskQueueCapacity = ii....ii, awaitTerminationSeconds = jj....jj, details = kk....kk)

aa....aa: JNDI name

bb....bb: Task execution time after which the task is determined as no response (seconds)

cc....cc: Long-time task

dd....dd: Initial number of threads

ee....ee: Maximum number of threads

ff....ff: Maximum length of time to wait for a used thread to be reused (seconds)

gg....gg: Period of time to continuously reuse threads (seconds)

hh....hh: Priority of the thread

ii....ii: Queue length

jj....jj: Length of time to wait for the tasks to terminate when the server stops (seconds)

kk....kk: Detailed information of the occurred exception

Description

Unexpected exception occurred during registering the ManagedExecutorService.

Action

Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJE60813-I

The specified ManagedScheduledExecutorService has been registered. (jndiName = aa....aa, hungAfterSeconds = bb....bb, longRunningTasks = cc....cc, corePoolSize = dd....dd, keepAliveSeconds = ee....ee, threadLifeTimeSeconds = ff....ff, threadPriority = gg....gg, awaitTerminationSeconds = hh....hh)

aa....aa: JNDI name

bb....bb: Task execution time after which the task is determined as no response (seconds)

cc....cc: Long-time task

dd....dd: Initial number of threads

ee....ee: Maximum length of time to wait for a used thread to be reused (seconds)

ff....ff: Period of time to continuously reuse threads (seconds)

gg....gg: Priority of the thread

hh....hh: Length of time to wait for the tasks to terminate when the server stops (seconds)

Description

The specified ManagedScheduledExecutorService has been registered.

KDJE60814-E

Unexpected exception occurred during registering the ManagedScheduledExecutorService. (jndiName = aa....aa, hungAfterSeconds = bb....bb, longRunningTasks = cc....cc, corePoolSize = dd....dd, keepAliveSeconds = ee....ee, threadLifeTimeSeconds = ff....ff, threadPriority = gg....gg, awaitTerminationSeconds = hh....hh, details = ii....ii)

aa....aa: JNDI name

bb....bb: Task execution time after which the task is determined as no response (seconds)

cc....cc: Long-time task

dd....dd: Initial number of threads

ee....ee: Maximum length of time to wait for a used thread to be reused (seconds)

ff....ff: Period of time to continuously reuse threads (seconds)

gg....gg: Priority of the thread

hh....hh: Length of time to wait for the tasks to terminate when the server stops (seconds)

ii....ii: Detailed information of the occurred exception

Description

Unexpected exception occurred during registering the ManagedScheduledExecutorService.

Action

Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJE60815-I

The specified ManagedThreadFactory has been registered. (jndiName = aa....aa, threadPriority = bb....bb)

aa....aa: JNDI name

bb....bb: Priority of the thread

Description

The specified ManagedThreadFactory has been registered.

KDJE60816-E

Unexpected exception occurred during registering the ManagedThreadFactory. (jndiName = aa....aa, threadPriority = bb....bb, details = cc....cc)

aa....aa: JNDI name

bb....bb: Priority of the thread

cc....cc: Detailed information of the occurred exception

Description

Unexpected exception occurred during registering the ManagedThreadFactory.

Action

Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJE60817-I

The long running task checker thread will now start. (hungCheckIntervalSeconds = aa....aa)

aa....aa: Execution time monitoring interval (seconds)

Description

The long running task checker thread will now start.

KDJE60818-W

The following task has been running for longer time than the configured hung task threshold setting. (jndiName = aa....aa, hungAfterSeconds = bb....bb, runningTimeSeconds = cc....cc, taskId = dd....dd, RootAP = ee....ee)

aa....aa: JNDI name of ExecutorService

bb....bb: Task execution time after which the task is determined as no response (seconds)

cc....cc: Task running time (seconds)

dd....dd: Task ID

ee....ee: Root application information

Description

The following task has been running for longer time than the configured hung task threshold setting.

Action

Check the log file and performance analysis trace, and then remove the cause due to which the relevant task does not terminate.

If the execution time is appropriate, revise the value specified for hungAfterSeconds of the relevant ExecutorService.

KDJE60819-I

The long running task checker thread will now stop.

Description

The long running task checker thread will now stop.

KDJE60820-I

Waiting for the remaining tasks in the ManagedExecutorService. (jndiName = aa....aa, awaitTerminationSeconds = bb....bb)

aa....aa: JNDI name

bb....bb: Length of time to wait for the tasks to terminate when the server stops (seconds)

Description

Waiting for the remaining tasks in the ManagedExecutorService.

KDJE60821-W

Timeout occurred during waiting for the remaining tasks in the ManagedExecutorService. (jndiName = aa....aa)

aa....aa: JNDI name

Description

Timeout occurred during waiting for the remaining tasks in the ManagedExecutorService.

Action

Some tasks have not terminated within the specified timeout period and other tasks remaining in the queue were not executed. Check the status of tasks by using, for example, the log file.

If the execution time is appropriate, revise the value specified for awaitTerminationSeconds of the relevant ExecutorService.

KDJE60822-W

Some tasks in the ManagedExecutorService has remained. (jndiName = aa....aa, numOfRemainedTasks = bb....bb)

aa....aa: JNDI name

bb....bb: Number of remaining tasks in the queue that were not executed

Description

Some tasks in the ManagedExecutorService has remained.

Action

Some tasks were forcibly terminated and other tasks remaining in the queue were not executed. Check the status of tasks by using, for example, the log file.

KDJE60823-I

The ManagedExecutorService has been unregistered successfully. (jndiName = aa....aa)

aa....aa: JNDI name

Description

The ManagedExecutorService has been unregistered successfully.

KDJE60824-E

Unexpected exception occurred during unregistering the ManagedExecutorService. (jndiName = aa....aa, details = bb....bb)

aa....aa: JNDI name

bb....bb: Detailed information of the occurred exception

Description

Unexpected exception occurred during unregistering the ManagedExecutorService.

Action

Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJE60825-I

Waiting for the remaining tasks in the ManagedScheduledExecutorService. (jndiName = aa....aa, awaitTerminationSeconds = bb....bb)

aa....aa: JNDI name

bb....bb: Length of time to wait for the tasks to terminate when the server stops (seconds)

Description

Waiting for the remaining tasks in the ManagedScheduledExecutorService.

KDJE60826-W

Timeout occurred during waiting for the remaining tasks in the ManagedScheduledExecutorService. (jndiName = aa....aa)

aa....aa: JND name

Description

Timeout occurred during waiting for the remaining tasks in the ManagedScheduledExecutorService.

Action

Some tasks have not terminated within the specified timeout period and other tasks remaining in the queue were not executed. Check the status of tasks by using, for example, the log file.

If the execution time is appropriate, revise the value specified for awaitTerminationSeconds of the relevant ExecutorService.

KDJE60827-W

Some tasks in the ManagedScheduledExecutorService has remained. (jndiName = aa....aa, numOfRemainedTasks = bb....bb)

aa....aa: JNDI name

bb....bb: Number of remaining tasks in the queue that were not executed

Description

Some tasks in the ManagedScheduledExecutorService has remained.

Action

Some tasks were forcibly terminated and other tasks remaining in the queue were not executed. Check the status of tasks by using, for example, the log file.

KDJE60828-I

The ManagedScheduledExecutorService has been unregistered successfully. (jndiName = aa....aa)

aa....aa: JNDI name

Description

The ManagedScheduledExecutorService has been unregistered successfully.

KDJE60829-E

Unexpected exception occurred during unregistering the ManagedScheduledExecutorService. (jndiName = aa....aa, details = bb....bb)

aa....aa: JNDI name

bb....bb: Detailed information of the occurred exception

Description

Unexpected exception occurred during unregistering the ManagedScheduledExecutorService.

Action

Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJE60830-I

The ManagedThreadFactory has been unregistered successfully. (jndiName = aa....aa)

aa....aa: JNDI name

Description

The ManagedThreadFactory has been unregistered successfully.

KDJE60831-E

Unexpected exception occurred during unregistering the ManagedThreadFactory. (jndiName = aa....aa, details = bb....bb)

aa....aa: JNDI name

bb....bb: Detailed information of the occurred exception

Description

Unexpected exception occurred during unregistering the ManagedThreadFactory.

Action

Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

7.7 Messages from KDJE70000 to KDJE79999

This section explains the messages from KDJE70000 to KDJE79999.

KDJE70130-I

The list of deleting batch jobs has been parsed. (timestamp = aa....aa, server-name = bb....bb, application-name = cc....cc, apptag = dd....dd, day = ee....ee, all = ff....ff, delete-timestamp = gg....gg, max-jobinstanceid = hh....hh, num-jobinstance = ii....ii, num-executioninstance = jj....jj, JobInstanceDataIds = kk....kk, ExecutionInstanceDataIds = ll....ll)

aa....aa: Time when the cjdeljbatchjobs command (with -list specified) was executed (YYYY-MM-DD hh:mm:ss)

bb....bb: Server name

cc....cc: Application name

dd....dd: Application tag

ee....ee: Value of the -day parameter (integer)

ff....ff: Whether the -all parameter exists ({true|false})

gg....gg: Deletion start time (YYYY-MM-DD hh:mm:ss.SSS)

hh....hh: Value of max-jobinstanceid (integer)

ii....ii: Value of num-jobinstance (integer)

jj....jj: Value of num-executioninstance (integer)

kk....kk: jobinstanceid list to be deleted ([integer,integer...])

ll....ll: jobexecid list to be deleted ([integer,integer...])

Description

The deletion-target list file has been read.

KDJE70131-I

The delete query has been executed by cjdeljbatchjobs -delete. (rows = aa....aa, statement = bb....bb)

aa....aa: Number of deleted rows

bb....bb: Issued delete query

Description

The delete query has been issued.

7.8 Messages from KDJE90000 to KDJE99999

This section explains the messages from KDJE90000 to KDJE99999.

KDJE90001-E

(aa....aa:bb....bb)cc....cc dd....dd(ee....ee)

aa....aa: File name

bb....bb: Line number

cc....cc: Method name

dd....dd: Exception class name

ee....ee: Exception string representation

Description

An exception occurred.

Action

Remove the cause of the error based on the message details.

KDJE90002-E

The log file aa....aa cannot be opened.

Method = bb....bb, Detailed message = cc....cc

aa....aa: Target file name

bb....bb: Hitachi Trace Common Library method name

cc....cc: Hitachi Trace Common Library detailed message

Description

Hitachi Trace Common Library log file (aa....aa) cannot be opened.

In the case of EJB client operated in subdirectory shared mode, exclusion of a log file might have failed.

Action

Remove the cause of the error based on the message details.

In the case of EJB client operated in subdirectory shared mode, when exclusion of log file fails, increase the retry interval and the retry count using the ejbserver.client.log.lockRetryCount and the ejbserver.client.log.lockInterval properties.

KDJE90003-E

The aa....aa method of HNTRLib returned an error.

aa....aa: Hitachi Trace Common Library method name

Description

The method of Hitachi Trace Common Library returned an error.

Resources might be insufficient.

In the case of EJB client operated in subdirectory shared mode, exclusion of a log file might have failed.

Action

Check the free disk space and memory usage of the directory to which the log is to be output, delete the unnecessary files, and then stop the unnecessary programs.

In the case of EJB client operated in subdirectory shared mode, when exclusion of log file fails, increase the retry interval and the retry count using the ejbserver.client.log.lockRetryCount and the ejbserver.client.log.lockInterval properties.

KDJE90005-W

The default value 2 will be used because the value of filenum property for aa....aa is invalid.

aa....aa: Channel name

Description

The default value 2 will be used because the value of filenum property for aa....aa is invalid.

Action

Revise the value of filenum property of the channel corresponding to usrconf.properties file.

KDJE90006-W

The default value 1MB will be used because the value of filesize property for aa....aa is invalid.

aa....aa: Channel name

Description

The default value 1 MB will be used because the value of the filesize property for aa....aa is invalid.

Action

Revise the value of the filesize property of the channel corresponding to the usrconf.properties file.

KDJE90009-W

An unknown log level is specified in the property key ejbserver.logger.enabled.*.

Description

Value other than Error, Warning, Information, Debug is specified in the property key ejbserver.logger.enabled.* of usrconf.properties file.

Action

Specify a correct value.

KDJE90010-E

The message was not found in the message resource file. ID = aa....aa

aa....aa: Message ID that could not be acquired

Description

An attempt to acquire the message (aa....aa) described by the ID from the resource has failed.

Action

Contact maintenance personnel.

KDJE90011-E

An exception aa....aa has occurred while outputting an exception log. Detail=bb....bb

aa....aa: Occurred exception class name

bb....bb: Class name where the exception was thrown

Description

An exception occurred when the log was being output to the exception log.

Action

Remove the cause due to which the exception aa....aa occurred.

KDJE90013-E

An attempt to get the path has failed. (path name = aa....aa)

aa....aa: Path name

Description

An attempt to acquire the path has failed.

Action

Make sure that the Application Server is installed properly.

KDJE90015-E

The aa....aa method of HULALib returned an error.

aa....aa: Name of the Hitachi Trace Common Library method

Description

The Hitachi Trace Common Library method returned an error.

Action

There might be a shortage of resources. Check the free disk space and memory usage of the log output directory, and then delete the files and stop the programs that are no longer required.

KDJE90016-W

An attempt to initialize an HNTRLib log file (aa....aa) failed, but processing will continue.

aa....aa: Name of the file that failed to be initialized

Description

An attempt to initialize the HNTRLib log file failed, but the processing continues.

Action

Take the action described in the KDJE90002-E message that was output immediately before this message.

7.9 List of details for KDJE42039-E and KDJE42270-W

This section describes the details of the message KDJE42039-E and message KDJE42270-W in the order of the codes.

7.9.1 Details from M00001 to M09999

M00001

The message-driven bean provider is responsible for providing the message-driven bean class. (ejb-name=aa....aa)

aa....aa: EJB name

Description

The EJB class is an interface.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.1

EJB 2.1 #15.7.1

M00002

The message-driven bean class must implement, directly or indirectly, the javax.ejb.MessageDrivenBean interface. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The EJB class does not inherit javax.ejb.MessageDrivenBean.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.2

EJB 2.1 #15.7.2

M00003

The message-driven bean class must implement, directly or indirectly, the message listener interface required by the messaging type that it supports. In the case of JMS, this is the javax.jms.MessageListener interface. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The EJB class does not inherit a message listener whose message type is supported (javax.jms.MessageListener in the case of JMS).

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.2

EJB 2.1 #15.7.2

M00004

The message-driven bean class must be defined as public, must not be final, and must not be abstract. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The EJB class is not public.

The EJB class is final.

The EJB class is abstract.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.2

M00005

The message-driven bean class must be defined as public, must not be final, and must not be abstract. The class must be a top level class. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The EJB class is not public.

The EJB class is final.

The EJB class is abstract.

The EJB class is not a top-level class.

Action

Modify the application according to the specifications.

Specification information

EJB 2.1 #15.7.2

M00006

The message-driven bean class must have a public constructor that takes no arguments. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The EJB class does not have a public constructor without any arguments.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.2

EJB 2.1 #15.7.2

M00007

The message-driven bean class must not define the finalize method. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The finalize method is defined in the EJB class.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.2

EJB 2.1 #15.7.2

M00008

The message-driven bean class must define one ejbCreate method which has no arguments. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

An ejbCreate method without any arguments is not defined in the EJB class.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.3

EJB 2.1 #15.7.3

M00009

The ejbCreate method of the message-driven bean class must be declared as public. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The ejbCreate method is not public.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.3

EJB 2.1 #15.7.3

M00010

The ejbCreate method of the message-driven bean class must not be declared as final or static. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The ejbCreate method is final.

The ejbCreate method is static.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.3

EJB 2.1 #15.7.3

M00011

The return type of the ejbCreate method of the message-driven bean class must be void. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The return-value type of the ejbCreate method is not void.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.3

EJB 2.1 #15.7.3

M00012

The throws clause of the ejbCreate method of the message-driven bean class must not define any application exceptions. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

An application exception is declared in the throws clause of the ejbCreate method.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.3

EJB 2.1 #15.7.3

M00013

The message-driven bean class must define one onMessage method which has a single argument of type javax.jms.Message. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

An onMessage method with javax.jms.Message as an argument is not defined in the EJB class.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.4

M00014

The onMessage method of the message-driven bean class must be declared as public. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The onMessage method is not public.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.4

M00015

The onMessage method of the message-driven bean class must not be declared as final or static. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The onMessage method is final.

The onMessage method is static.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.4

M00016

The message-driven bean class must define the message listener methods. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

A message listener method is not defined in the EJB class.

Action

Modify the application according to the specifications.

Specification information

EJB 2.1 #15.7.4

M00017

The message listener methods of the message-driven bean class must be declared as public. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The message listener method is not public.

Action

Modify the application according to the specifications.

Specification information

EJB 2.1 #15.7.4

M00018

The message listener methods of the message-driven bean class must not be declared as final or static. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The message listener method is final.

The message listener method is static.

Action

Modify the application according to the specifications.

Specification information

EJB 2.1 #15.7.4

M00019

The return type of the onMessage method of the message-driven bean class must be void. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The return-value type of the onMessage method is not void.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.4

M00020

The throws clause of the onMessage method of the message-driven bean class must not define any application exceptions. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

An application exception is declared in the throws clause of the onMessage method.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.4

M00021

The message-driven bean class must define one ejbRemove method which has no arguments. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

An ejbRemove method without any arguments is not defined in the EJB class.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.5

EJB 2.1 #15.7.5

M00022

The ejbRemove method of the message-driven bean class must be declared as public. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The ejbRemove method is not public.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.5

EJB 2.1 #15.7.5

M00023

The ejbRemove method of the message-driven bean class must not be declared as final or static. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The ejbRemove method is final.

The ejbRemove method is static.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.5

EJB 2.1 #15.7.5

M00024

The return type of the ejbRemove method of the message-driven bean class must be void. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

The return-value type of the ejbRemove method is not void.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.5

EJB 2.1 #15.7.5

M00025

The throws clause of the ejbRemove method of the message-driven bean class must not define any application exceptions. (ejb-name=aa....aa, ejb-class=bb....bb)

aa....aa: EJB name

bb....bb: EJB class

Description

An application exception is declared in the throws clause of the ejbRemove method.

Action

Modify the application according to the specifications.

Specification information

EJB 2.0 #15.7.5

EJB 2.1 #15.7.5

7.9.2 Details from S00001 to S09999

S00001

The session Bean Provider is responsible for providing the session bean class. (test name = aa....aa, ejb-name = bb....bb)

aa....aa: Test name

bb....bb: EJB name

Description

The Session Bean class must be provided.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.1

S00002

The session Bean Provider is responsible for providing the session bean's client view interface(s). (test name = aa....aa, ejb-name = bb....bb)

aa....aa: Test name

bb....bb: EJB name

Description

The client view of Session Bean must be provided.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.1

S00003

The session Bean Provider is responsible for providing the session bean's remote interface and remote home interface, if the session bean provides an EJB 2.x remote client view. (test name = aa....aa, ejb-name = bb....bb)

aa....aa: Test name

bb....bb: EJB name

Description

When an EJB 2.x remote client view is provided, the remote interface and the remote home interface must be provided.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.1

S00004

The session Bean Provider is responsible for providing the session bean's local interface and local home interface, if the session bean provides an EJB 2.x local client view. (test name = aa....aa, ejb-name = bb....bb)

aa....aa: Test name

bb....bb: EJB name

Description

When an EJB 2.x local client view is provided, the local interface and the local home interface must be provided.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.1

S00005

The web service client view is not supported. (test name = aa....aa, ejb-name = bb....bb)

aa....aa: Test name

bb....bb: EJB name

Description

The web service client view is not supported.

Action

Application servers do not support this functionality.

S01000

The EJB 2.x session bean class must implement, directly or indirectly, the javax.ejb.SessionBean interface. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

Description

The EJB 2.x Session Bean class must implement the javax.ejb.SessionBean interface.

Action

Modify the application according to the specifications.

Specification information

EJB 2.1 #7.11.2

S01001

The session bean class must be defined as public, must not be final, and must not be abstract. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

Description

The Session Bean class must be defined as public, must not be final, and must not be abstract.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.2

S01002

The session bean class must be a top level class. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

Description

The Session Bean class must be a top level class.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.2

S01003

The session bean class must have a public constructor that takes no parameters. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

Description

The Session Bean class must have a public constructor that does not take any parameters.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.2

S01004

The session bean class must not define the finalize method. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

Description

The Session Bean class must not define the finalize method.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.2

S01005

The stateless/singleton session bean class must not implement the javax.ejb.SessionSynchronization interface. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

Description

The Stateless Session Bean or Singleton Session Bean must not implement the javax.ejb.SessionSynchronization interface.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.2, EJB 3.1 Core Contracts and Requirements #4.3.7

S01006

The Remove annotation can only be specified on the business method of the bean class. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The Remove annotation can only be specified on the business method of the Bean class.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Simplified API #5.1.9

S01007

The stateless/singleton session bean class must not use any Session Synchronization Annotation. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

Description

The Session Synchronization annotation must not be defined in the Stateless Session Bean class or Singleton Session Bean class.

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #4.3.7

S01008

The AfterBegin Session Synchronization annotation method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

You cannot specify final or static in the method defining the @AfterBegin annotation.

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #4.9.4

S01009

The BeforeCompletion Session Synchronization annotation method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

You cannot specify final or static in the method defining the @BeforeCompletion annotation.

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #4.9.4

S01010

The AfterCompletion Session Synchronization annotation method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

You cannot specify final or static in the method defining the @AfterCompletion annotation.

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #4.9.4

S01011

Any method annotated as a AfterBegin, method must have the signature below: void <METHOD>( ) (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

Specify the following signature for the afterBegin method:

void <METHOD>()

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #4.9.4

S01012

Any method annotated as a BeforeCompletion, method must have the signature below: void <METHOD>( ) (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

Specify the following signature for the beforeCompletion method:

void <METHOD>()

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #4.9.4

S01013

Any method annotated as a AfterCompletion, method must have the signature below: void <METHOD>(boolean committed ) (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

Specify the following signature for the afterCompletion method:

void <METHOD>(boolean committed)

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #4.9.4

S01014

The business method annotated as @Asynchronous must have return type void or java.util.concurrent.Future. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The return value type of all the business methods of the class specifying the @Asynchronous annotation must be void or java.util.concurrent.Future.

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #4.5.2

S01015

The asynchronous method with return type void must not declare any application exceptions. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

You cannot specify an application exception in a business method specifying the @Asynchronous annotation and with the return value type void.

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #4.5.2

S01017

Invalid DependsOn value specified. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, DependsOn = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Value specified for DependsOn

Description

An invalid value is specified in the value of the @DependsOn annotation.

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #4.8.1

S01018

The processing of @Asynchronous annotation is not supported for Stateful session bean. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

Description

Application Server does not support the use of @Asynchronous annotation in Stateful Session Bean.

Action

Use the @Asynchronous annotation in Stateless Session Bean or Singleton Session Bean.

Specification information

None.

S01019

Singleton session bean in an EJB 2.1 client view is not allowed. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

Description

You cannot use Singleton Session Bean in the EJB 2.1 client view.

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #3.6

S01020

Asynchronous annotation in an EJB 2.1 client view is not supported. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

Description

The @Asynchronous annotation is not supported in the EJB 2.1 client view.

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #4.5.1

S03000

The same business interface cannot be both a local and a remote business interface of the bean. (test name = aa....aa, ejb-name = bb....bb, interface = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interface

Description

The same business interface cannot be specified as both a local and remote business interface.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.6

S03001

The session bean's business interface must not extend the javax.ejb.EJBObject or javax.ejb.EJBLocalObject interface. (test name = aa....aa, ejb-name = bb....bb, business-local = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: local business interface

Description

The business interface must not inherit the javax.ejb.EJBObject or the javax.ejb.EJBLocalObject interface.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.6

S03101

The business method names of the session bean's class can be arbitrary, but they must not start with "ejb". (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The business method names must not start with "ejb".

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S03102

The business method of the session bean's class must be declared as public. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The business method must be declared as public.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S03103

The business method of the session bean's class must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The business method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S03104

The enterprise bean should not throw the java.rmi.RemoteException from a business method. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The java.rmi.RemoteException must not be thrown from a business method.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S04001

The session bean's business interface must not extend the javax.ejb.EJBObject or javax.ejb.EJBLocalObject interface. (test name = aa....aa, ejb-name = bb....bb, business-remote = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: remote business interface

Description

The business interface must not inherit the javax.ejb.EJBObject or the javax.ejb.EJBLocalObject interface.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.6

S04002

The throws clause of a method in the session bean's remote business interface that does not extend java.rmi.Remote should not include the java.rmi.RemoteException. (test name = aa....aa, ejb-name = bb....bb, business-remote = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: remote business interface

dd....dd: Method

Description

The throws clause of a remote business interface method that does not inherit java.rmi.Remote cannot include java.rmi.RemoteException.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.6

S04003

The session bean's remote business interface methods must not expose local interface types, timers or timer handles as arguments or results. (test name = aa....aa, ejb-name = bb....bb, business-remote = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: remote business interface

dd....dd: Method

Description

The remote business interface methods must not expose the local interface types, the timers, or the timer handles as arguments or results.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.6

S04101

The business method names of the session bean's class can be arbitrary, but they must not start with "ejb". (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The business method names must not start with "ejb".

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S04102

The business method of the session bean's class must be declared as public. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The business method must be declared as public.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S04103

The business method of the session bean's class must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The business method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S04104

The enterprise bean should not throw the java.rmi.RemoteException from a business method. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The java.rmi.RemoteException must not be thrown from a business method.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S05000

All the exceptions defined in the throws clause of the matching method of the session bean class must be defined in the throws clause of the method of the remote interface. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, remote = dd....dd, method =ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: remote interface

ee....ee: Method

Description

The exceptions defined in the throws clause of the Session Bean class method corresponding to the method defined in the remote interface must be defined in the throws clause of the remote interface method.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.7

S05001

The session bean's remote interface must extend the javax.ejb.EJBObject interface. (test name = aa....aa, ejb-name = bb....bb, remote = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: remote interface

Description

The remote interface must inherit the javax.ejb.EJBObject interface.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.7

S05002

The throws clause of a method of the session bean's remote interface must include java.rmi.RemoteException. (test name = aa....aa, ejb-name = bb....bb, remote = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: remote interface

dd....dd: Method

Description

The throws clause of a method defined in the remote interface must include java.rmi.RemoteException.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.7

S05003

For each method defined in the session bean's remote interface, there must be a matching method in the session bean's class. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, remote = dd....dd, method = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: remote interface

ee....ee: Method

Description

For each method defined in the remote interface, there must be a matching method in the session bean class.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.7

S05004

The session bean's remote interface methods must not expose local interface types, local home interface types, timers or timer handles as arguments or results. (test name = aa....aa, ejb-name = bb....bb, remote = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: remote interface

dd....dd: Method

Description

The remote interface methods must not expose the local interface types, the local home interface types, and the timers, or the timer handles as arguments or results.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.7

S05101

The business method names of the session bean's class can be arbitrary, but they must not start with "ejb". (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The business method names must not start with "ejb".

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S05102

The business method of the session bean's class must be declared as public. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The business method must be declared as public.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S05103

The business method of the session bean's class must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The business method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S06000

Each create method must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, home = dd....dd, method = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: remote home interface

ee....ee: Method

Description

Each create method of the Session Bean must match one of the ejbCreate<METHOD> methods defined in the Session Bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments.

Action

Modify the application according to the specifications.

Specification information

EJB 2.1 #7.11.6

S06001

The session bean's remote home interface must extend the javax.ejb.EJBHome interface. (test name = aa....aa, ejb-name = bb....bb, home = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: remote home interface

Description

The remote home interface must inherit the javax.ejb.EJBHome interface.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.8

S06002

The throws clause of a method of the session bean's remote home interface must include java.rmi.RemoteException. (test name = aa....aa, ejb-name = bb....bb, home = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: remote home interface

dd....dd: Method

Description

The throws clause of a method defined in the remote interface must include java.rmi.RemoteException.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.8

S06003

The stateless session bean's remote home interface must define exactly one create method with no arguments. (test name = aa....aa, ejb-name = bb....bb, home = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: remote home interface

Description

The remote home interface of stateless session bean must define one create method with no arguments.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.8

S06004

The stateful session bean's remote home interface must define one or more create<METHOD> methods. (test name = aa....aa, ejb-name = bb....bb, home = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: remote home interface

Description

The remote home interface of stateful session bean must define one or more create<METHOD> methods.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.8

S06005

Each create method of a stateful session bean must match one of the Init methods or ejbCreate<METHOD> methods defined in the session bean class. The matching Init method or ejbCreate<METHOD> method must have the same number and types of arguments. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, home = dd....dd, method = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: remote home interface

ee....ee: Method

Description

Each create method of a stateful session bean must match one of the Init methods or the ejbCreate<METHOD> methods defined in the session bean class. The matching Init method or the ejbCreate<METHOD> method must have the same number and types of arguments.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.8

S06006

The return type for a create<METHOD> method defined in the session bean's remote home interface must be the session bean's remote interface type. (test name = aa....aa, ejb-name = bb....bb, home = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: remote home interface

dd....dd: Method

Description

The return type for a create<METHOD> method must be the remote interface type of the session bean.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.8

S06007

All the exceptions defined in the throws clause of an ejbCreate<METHOD> method of the session bean class must be defined in the throws clause of the matching create<METHOD> method of the remote home interface. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, home = dd....dd, method = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: remote home interface

ee....ee: Method

Description

The exceptions defined in the throws clause of an ejbCreate<METHOD> method of the session bean class must be defined in the throws clause of the matching create<METHOD> method of the remote home interface.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.8

S06008

The throws clause of a create<METHOD> method of the session bean's remote home interface must include javax.ejb.CreateException. (test name = aa....aa, ejb-name = bb....bb, home = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: remote home interface

dd....dd: Method

Description

The throws clause of a method defined in the remote home interface must include the javax.ejb.CreateException.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.8

S06009

If the stateless session bean has an ejbCreate method, the PostConstruct annotation (or deployment descriptor metadata) can only be applied to the bean's ejbCreate method. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, home = dd....dd, method = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: remote home interface

ee....ee: Method

Description

If the stateless session bean has an ejbCreate method, the PostConstruct annotation can only be applied to the ejbCreate method.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.3.10.2

S06010

The value element of the Init annotation must be specified when the Init annotation is used in association with an adapted home interface of a stateful session bean that has more than one create<METHOD> method. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, home = dd....dd, method = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: remote home interface

ee....ee: Method

Description

The value element of the Init annotation must be specified when the Init annotation is used in association with a home interface of a stateful session bean that has more than one create<METHOD> methods.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Simplified API #10.1.2.1

S06101

The ejbCreate<METHOD> method of the session bean's class must be declared as public. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The ejbCreate<METHOD> method must be declared as public.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.4

S06102

The ejbCreate<METHOD> method of the session bean's class must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The ejbCreate<METHOD> method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.4

S06103

The return type for the ejbCreate<METHOD> method of the session bean's class must be void. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The return type for the ejbCreate<METHOD> method must be void.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.4

S06201

The result type for the Init method must be void. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The result type for the Init method must be void.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Simplified API #10.1.2.1

S07000

All the exceptions defined in the throws clause of the matching method of the session bean class must be defined in the throws clause of the method of the local interface. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, local = dd....dd, method = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: local interface

ee....ee: Method

Description

The exceptions defined in the throws clause of the session bean class method corresponding to the method defined in the local interface must be defined in the throws clause of the local interface method.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.9

S07001

The session bean's local interface must extend the javax.ejb.EJBLocalObject interface. (test name = aa....aa, ejb-name = bb....bb, local = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: local interface

Description

The local interface must inherit the javax.ejb.EJBLocalObject interface.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.9

S07002

The throws clause of a method defined in the session bean's local interface must not include the java.rmi.RemoteException. (test name = aa....aa, ejb-name = bb....bb, local = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: local interface

dd....dd: Method

Description

The throws clause of a method defined in the local interface cannot include the java.rmi.RemoteException.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.9

S07003

For each method defined in the session bean's local interface, there must be a matching method in the session bean's class. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, local = dd....dd, method = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: local interface

ee....ee: Method

Description

For each method defined in the local interface, there must be a matching method in the Session Bean class.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.9

S07101

The business method names of the session bean's class can be arbitrary, but they must not start with "ejb". (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The business method names must not start with "ejb".

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S07102

The business method of the session bean's class must be declared as public. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The business method must be declared as public.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S07103

The business method of the session bean's class must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The business method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.5

S08000

Each create method must match one of the ejbCreate<METHOD> methods defined in the session bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, local-home = dd....dd, method = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: local home interface

ee....ee: Method

Description

Each create method of the Session Bean must match one of the ejbCreate<METHOD> methods defined in the Session Bean class. The matching ejbCreate<METHOD> method must have the same number and types of arguments.

Action

Modify the application according to the specifications.

Specification information

EJB 2.1 #7.11.8

S08001

The session bean's local home interface must extend the javax.ejb.EJBLocalHome interface. (test name = aa....aa, ejb-name = bb....bb, local-home = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: local home interface

Description

The local home interface must inherit the javax.ejb.EJBLocalHome interface.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.10

S08002

The throws clause of a method in the session bean's local home interface must not include the java.rmi.RemoteException. (test name = aa....aa, ejb-name = bb....bb, local-home = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: local home interface

dd....dd: Method

Description

The throws clause of a method defined in the local home interface cannot include the java.rmi.RemoteException.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.10

S08003

The stateless session bean's local home interface must define exactly one create method with no arguments. (test name = aa....aa, ejb-name = bb....bb, local-home = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: local home interface

Description

The local home interface of Stateless Session Bean must define one create method with no arguments.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.10

S08004

The stateful session bean's local home interface must define one or more create<METHOD> methods. (test name = aa....aa, ejb-name = bb....bb, local-home = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: local home interface

Description

The local home interface of Stateful Session Bean must define one or more create<METHOD> methods.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.10

S08005

Each create method of a stateful session bean must match one of the Init methods or ejbCreate<METHOD> methods defined in the session bean class. The matching Init method or ejbCreate<METHOD> method must have the same number and types of arguments. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, local-home = dd....dd, method = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: local home interface

ee....ee: Method

Description

Each create method of a Stateful Session Bean must match one of the Init methods or ejbCreate<METHOD> methods defined in the Session Bean class. The matching Init method or the ejbCreate<METHOD> method must have the same number and types of arguments.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.10

S08006

The return type for a create<METHOD> method defined in the session bean's local home interface must be the session bean's local interface type. (test name = aa....aa, ejb-name = bb....bb, local-home = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: local home interface

dd....dd: Method

Description

The return type for a create<METHOD> method must be the local interface type of the Session Bean.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.10

S08007

All the exceptions defined in the throws clause of an ejbCreate<METHOD> method of the session bean class must be defined in the throws clause of the matching create<METHOD> method of the local home interface. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, local-home = dd....dd, method = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: local home interface

ee....ee: Method

Description

The exceptions defined in the throws clause of an ejbCreate<METHOD> method of the Session Bean class must be defined in the throws clause of the matching create<METHOD> method of the local home interface.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.10

S08008

The throws clause of a create<METHOD> method of the session bean's local home interface must include javax.ejb.CreateException. (test name = aa....aa, ejb-name = bb....bb, local-home = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: local home interface

dd....dd: Method

Description

The throws clause of a method defined in the local home interface must include javax.ejb.CreateException.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.10

S08009

If the stateless session bean has an ejbCreate method, the PostConstruct annotation (or deployment descriptor metadata) can only be applied to the bean's ejbCreate method. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, local-home = dd....dd, method = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: local home interface

ee....ee: Method

Description

If the Stateless Session Bean has an ejbCreate method, the PostConstruct annotation can only be applied to the ejbCreate method.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.3.10.2

S08010

The value element of the Init annotation must be specified when the Init annotation is used in association with an adapted home interface of a stateful session bean that has more than one create<METHOD> method. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, local-home = dd....dd, method = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: local home interface

ee....ee: Method

Description

The value element of the Init annotation must be specified when the Init annotation is used in association with a home interface of a Stateful Session Bean that has more than one create<METHOD> methods.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Simplified API #10.1.2.1

S08101

The ejbCreate<METHOD> method of the session bean's class must be declared as public. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The ejbCreate<METHOD> method must be declared as public.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.4

S08102

The ejbCreate<METHOD> method of the session bean's class must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The ejbCreate<METHOD> method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.4

S08103

The return type for the ejbCreate<METHOD> method of the session bean's class must be void. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The return type for the ejbCreate<METHOD> method must be void.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.4

S08201

The result type for the Init method must be void. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The result type for the Init method must be void.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Simplified API #10.1.2.1

7.9.3 Details from S70001 to S79999

S70111

An AroundInvoke method must have the following signature: Object <METHOD>(InvocationContext) throws Exception (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

An AroundInvoke method must have the following signature:

Object <METHOD>(InvocationContext) throws Exception

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.3

S70112

An AroundInvoke method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

An AroundInvoke method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.3

S70113

Only one AroundInvoke method may be present on a given class. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, class = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Class name

Description

Only one AroundInvoke method can be specified for a given class.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.3

S70114

An AroundInvoke method cannot be a business method of the bean class. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

An AroundInvoke method cannot be specified as a business method of the Bean class.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.3

S70120

The method names of PostConstruct lifecycle callback interceptor method must not start with "ejb" except ejbCreate. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The method names of the PostConstruct lifecycle callback interceptor method must not start with "ejb" except ejbCreate.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.3

S70121

The PostConstruct lifecycle callback interceptor method defined on a bean class have the following signature: void <METHOD>() (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The PostConstruct lifecycle callback interceptor method defined on a Bean class must have the following signature:

void <METHOD>()

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70122

The PostConstruct lifecycle callback interceptor method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The PostConstruct lifecycle callback interceptor method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70123

The PostConstruct lifecycle callback interceptor method may not throw application exceptions. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The PostConstruct lifecycle callback interceptor method cannot throw application exceptions.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4.2

S70124

A given class may not have more than one lifecycle callback interceptor method for the PostConstruct lifecycle event. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, class = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Class name

Description

A given class cannot have more than one lifecycle callback interceptor methods for the PostConstruct lifecycle event.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70130

The method names of PreDestroy lifecycle callback interceptor method must not start with "ejb" except ejbRemove. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The method names of PreDestroy lifecycle callback interceptor method must not start with "ejb" except ejbRemove.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.3

S70131

The PreDestroy lifecycle callback interceptor method defined on a bean class have the following signature: void <METHOD>() (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The PreDestroy lifecycle callback interceptor method defined on a Bean class must have the following signature:

void <METHOD>()

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70132

The PreDestroy lifecycle callback interceptor method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The PreDestroy lifecycle callback interceptor method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70133

The PreDestroy lifecycle callback interceptor method may not throw application exceptions. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The PreDestroy lifecycle callback interceptor method cannot throw application exceptions.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4.2

S70134

A given class may not have more than one lifecycle callback interceptor method for the PreDestroy lifecycle event. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, class = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Class name

Description

A given class cannot have more than one lifecycle callback interceptor methods for the PreDestroy lifecycle event.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70135

If the session bean implements the SessionBean interface, the PreDestroy annotation can only be applied to the ejbRemove method. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

If the Session Bean implements the SessionBean interface, the PreDestroy annotation can only be applied to the ejbRemove method.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.3.5

S70140

The method names of PostActivate lifecycle callback interceptor method must not start with "ejb" except ejbActivate. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The method names of PostActivate lifecycle callback interceptor method must not start with "ejb" except ejbActivate.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.3

S70141

The PostActivate lifecycle callback interceptor method defined on a bean class have the following signature: void <METHOD>() (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The PostActivate lifecycle callback interceptor method defined on a Bean class must have the following signature:

void <METHOD>()

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70142

The PostActivate lifecycle callback interceptor method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The PostActivate lifecycle callback interceptor method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70143

The PostActivate lifecycle callback interceptor method may not throw application exceptions. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The PostActivate lifecycle callback interceptor method cannot throw application exceptions.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4.2

S70144

A given class may not have more than one lifecycle callback interceptor method for the PostActivate lifecycle event. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, class = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Class name

Description

The given class cannot have more than one lifecycle callback interceptor methods for the PostActivate lifecycle event.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70145

If the session bean implements the SessionBean interface, the PostActivate annotation can only be applied to the ejbActivate method. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

If the Session Bean implements the SessionBean interface, the PostActivate annotation can only be applied to the ejbActivate method.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.3.5

S70150

The method names of PrePassivate lifecycle callback interceptor method must not start with "ejb" except ejbPassivate. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The method names of PrePassivate lifecycle callback interceptor method must not start with "ejb" except ejbPassivate.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.3

S70151

The PrePassivate lifecycle callback interceptor method defined on a bean class have the following signature: void <METHOD>() (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The PrePassivate lifecycle callback interceptor method defined on a Bean class must have the following signature:

void <METHOD>()

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70152

The PrePassivate lifecycle callback interceptor method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The PrePassivate lifecycle callback interceptor method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70153

The PrePassivate lifecycle callback interceptor method may not throw application exceptions. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The PrePassivate lifecycle callback interceptor method cannot throw application exceptions.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4.2

S70154

A given class may not have more than one lifecycle callback interceptor method for the PrePassivate lifecycle event. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, class = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Class name

Description

A given class cannot have more than one lifecycle callback interceptor methods for the PrePassivate lifecycle event.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70155

If the session bean implements the SessionBean interface, the PrePassivate annotation can only be applied to the ejbPassivate method. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

If the Session Bean implements the SessionBean interface, the PrePassivate annotation can only be applied to the ejbPassivate method.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.3.5

S70201

An interceptor class must be distinct from the bean class itself. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

Description

An interceptor class must be distinct from the Bean class.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.1

S70202

An interceptor class must have a public no-arg constructor. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

Description

An interceptor class must have a public constructor without arguments.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.1

S70211

An AroundInvoke method must have the following signature: Object <METHOD>(InvocationContext) throws Exception (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

An AroundInvoke method must have the following signature:

Object <METHOD>(InvocationContext) throws Exception

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.3

S70212

An AroundInvoke method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

An AroundInvoke method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.3

S70213

Only one AroundInvoke method may be present on a given class. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, class = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Class name

Description

Only one AroundInvoke method can be specified for a given class.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.3

S70220

The method names of PostConstruct lifecycle callback interceptor method must not start with "ejb" except ejbCreate. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The method names of the PostConstruct lifecycle callback interceptor method must not start with "ejb" except ejbCreate.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.3

S70221

The PostConstruct lifecycle callback interceptor method defined on an interceptor class have the following signature: void <METHOD>(InvocationContext) (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The PostConstruct lifecycle callback interceptor method defined on an interceptor class must have the following signature:

void <METHOD> (InvocationContext)

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70222

The PostConstruct lifecycle callback interceptor method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The PostConstruct lifecycle callback interceptor method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70223

The PostConstruct lifecycle callback interceptor method may not throw application exceptions. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The PostConstruct lifecycle callback interceptor method cannot throw application exceptions.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4.2

S70224

A given class may not have more than one lifecycle callback interceptor method for the PostConstruct lifecycle event. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, class = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Class name

Description

A given class cannot have more than one lifecycle callback interceptor methods for the PostConstruct lifecycle event.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70225

If the PostConstruct lifecycle callback interceptor method is the ejbCreate method, that callback methods must be implemented on the bean class itself (or on its superclasses). (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

If the PostConstruct lifecycle callback interceptor method is the ejbCreate method, that callback method must be implemented on the Bean class (or on its super classes).

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.3

S70230

The method names of PreDestroy lifecycle callback interceptor method must not start with "ejb" except ejbRemove. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The method names of PreDestroy lifecycle callback interceptor method must not start with "ejb" except ejbRemove.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.3

S70231

The PreDestroy lifecycle callback interceptor method defined on an interceptor class have the following signature: void <METHOD>(InvocationContext) (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The PreDestroy lifecycle callback interceptor method defined on an interceptor class must have the following signature:

void <METHOD> (InvocationContext)

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70232

The PreDestroy lifecycle callback interceptor method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The PreDestroy lifecycle callback interceptor method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70233

The PreDestroy lifecycle callback interceptor method may not throw application exceptions. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The PreDestroy lifecycle callback interceptor method cannot throw application exceptions.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4.2

S70234

A given class may not have more than one lifecycle callback interceptor method for the PreDestroy lifecycle event. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, class = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Class name

Description

A given class cannot have more than one lifecycle callback interceptor methods for the PreDestroy lifecycle event.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70235

If the PreDestroy lifecycle callback interceptor method is the ejbRemove method, that callback methods must be implemented on the bean class itself (or on its superclasses). (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

If the PreDestroy lifecycle callback interceptor method is the ejbRemove method, that callback method must be implemented on the Bean class itself (or on its super classes).

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.3

S70240

The method names of PostActivate lifecycle callback interceptor method must not start with "ejb" except ejbActivate. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The method names of PostActivate lifecycle callback interceptor method must not start with "ejb" except ejbActivate.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.3

S70241

The PostActivate lifecycle callback interceptor method defined on an interceptor class have the following signature: void <METHOD>(InvocationContext) (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The PostActivate lifecycle callback interceptor method defined on an interceptor class must have the following signature:

void <METHOD> (InvocationContext)

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70242

The PostActivate lifecycle callback interceptor method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The PostActivate lifecycle callback interceptor method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70243

The PostActivate lifecycle callback interceptor method may not throw application exceptions. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The PostActivate lifecycle callback interceptor method cannot throw application exceptions.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4.2

S70244

A given class may not have more than one lifecycle callback interceptor method for the PostActivate lifecycle event. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, class = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Class name

Description

The given class cannot have more than one lifecycle callback interceptor methods for the PostActivate lifecycle event.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70245

If the PostActivate lifecycle callback interceptor method is the ejbActivate method, that callback methods must be implemented on the bean class itself (or on its superclasses). (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

If the PostActivate lifecycle callback interceptor method is the ejbActivate method, that callback method must be implemented on the Bean class (or on its super classes).

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.3

S70250

The method names of PrePassivate lifecycle callback interceptor method must not start with "ejb" except ejbPassivate. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The method names of PrePassivate lifecycle callback interceptor method must not start with "ejb" except ejbPassivate.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.3

S70251

The PrePassivate lifecycle callback interceptor method defined on an interceptor class have the following signature: void <METHOD>(InvocationContext) (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The PrePassivate lifecycle callback interceptor method defined on an interceptor class must have the following signature:

void <METHOD> (InvocationContext)

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70252

The PrePassivate lifecycle callback interceptor method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The PrePassivate lifecycle callback interceptor method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70253

The PrePassivate lifecycle callback interceptor method may not throw application exceptions. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

The PrePassivate lifecycle callback interceptor method cannot throw application exceptions.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4.2

S70254

A given class may not have more than one lifecycle callback interceptor method for the PrePassivate lifecycle event. (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, class = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Class name

Description

A given class cannot have more than one lifecycle callback interceptor methods for the PrePassivate lifecycle event.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #12.4

S70255

If the PrePassivate lifecycle callback interceptor method is the ejbPassivate method, that callback methods must be implemented on the bean class itself (or on its superclasses). (test name = aa....aa, ejb-name = bb....bb, interceptor-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: Interceptor class

dd....dd: Method

Description

If the PrePassivate lifecycle callback interceptor method is the ejbPassivate method, that callback method must be implemented on the Bean class (or on its super classes).

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #4.6.3

7.9.4 Details from S80001 to S89999

S80001

If the bean implements the TimedObject interface, the Timeout annotation or timeout-method deployment descriptor element can only be used to specify the ejbTimeout method. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

If the Bean implements the TimedObject interface, the Timeout annotation or the timeout-method deployment descriptor element can only be used to specify the ejbTimeout method.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #18.2.2

S80002

Any method annotated as a Timeout method (or designated in the deployment descriptor as such) must have the signature below: void <METHOD>(Timer timer) (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

A method added in a Timeout annotation or specified in the deployment descriptor must have the following signature:

void <METHOD>(Timer timer)

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #18.2.2

S80003

Timeout callback methods must not throw application exceptions. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The Timeout callback methods must not throw application exceptions.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #18.2.2

S80004

A Timeout method must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

A Timeout method must not be declared as final or static.

Action

Modify the application according to the specifications.

Specification information

EJB 3.0 Core Contracts and Requirements #18.2.2

S80005

Automatic timer related @Schedule attributes must not be incorrect. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd, cause = ee....ee)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

ee....ee: Cause

Description

The attributes of the @Schedule annotation that auto-generates the EJB timer, are invalid.

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #18.2.1

S80006

Automatic timeout methods must have either of the following two signatures below: void <METHOD>() OR void <METHOD>(Timer timer) (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

Specify one of the following signatures for the timeout methods of the EJB timer auto-generated by the @Schedule annotation:

void <METHOD>()

void <METHOD>(Timer timer)

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #18.2.5.3

S80007

Automatic timeout methods must not throw application exceptions. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The timeout methods of the EJB timer auto-generated by the @Schedule annotation must not throw application exceptions.

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #18.2.5.3

S80008

Automatic timeout methods must not be declared as final or static. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

The timeout methods of the EJB timer auto-generated by the @Schedule annotation must not be declared as final or static.

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #18.2.5.3

S80009

A stateful session bean cannot define automatic timeout methods. (test name = aa....aa, ejb-name = bb....bb, ejb-class = cc....cc, method = dd....dd)

aa....aa: Test name

bb....bb: EJB name

cc....cc: EJB class

dd....dd: Method

Description

Do not define the timeout methods of the EJB timer auto-generated by the @Schedule annotation in a Stateful Session Bean.

Action

Modify the application as per the specifications.

Specification information

EJB 3.1 Core Contracts and Requirements #18.2

7.9.5 Details from Z00001 to Z09999

Z00001

The enterprise bean must define specified interfaces and classes on the deployment descriptor. (ejb-name = aa....aa, exception = bb....bb)

aa....aa: EJB name

bb....bb: Exception information

Description

The ClassNotFoundException occurred during the EJB specification check process.

Action

Check the class name coded in the deployment descriptor of an EJB.

Z00002

Container must set the legal security policy for deploying enterprise beans. (ejb-name = aa....aa, exception = bb....bb)

aa....aa: EJB name

bb....bb: Exception information

Description

Security policy is invalid.

Action

Modify the security policy.

Z00003

The enterprise bean provider must provide session beans, entity beans and/or message-driven beans. (ejb-name = aa....aa, exception = bb....bb)

aa....aa: EJB name

bb....bb: Exception information

Description

The state of the deployment descriptor is invalid.

Action

Contact system administrator.

Z00004

Container has caught unexpected exception. (ejb-name = aa....aa, exception = bb....bb)

aa....aa: EJB name

bb....bb: Exception information

Description

An unexpected exception occurred during the EJB specification check process.

Action

Contact system administrator.

Z00005

The enterprise bean must define specified methods on the deployment descriptor. (ejb-name = aa....aa, exception = bb....bb)

aa....aa: EJB name

bb....bb: Exception information

Description

The NoSuchMethodException occurred during the EJB specification check process.

Action

Check the method name coded in the deployment descriptor of an EJB.

Z00006

The specified test name is invalid. (exception = aa....aa)

aa....aa: Exception information

Description

The test name is invalid.

Action

Modify the test name coded in the test item list.

7.10 Mapping the strings indicating communication processing to the communication processing

This section describes the mapping of the strings that indicate communication processing, output in messages, to the communication processing.

7.10.1 For the SMTP and SMTPS related messages

The following table describes the mapping between the strings that indicate communication processing, output in messages, and communication processing for the SMTP and SMTPS related messages:

No.

String indicating communication processing

Communication processing

1

--

Acquiring a connection

2

connect-mail-server

Acquiring the server response for the connection

3

EHLO command argument

Issuing the EHLO command

4

HELO command argument

Issuing the HELO command

5

AUTH LOGIN

Issuing the AUTH command

(LOGIN in the argument)

6

AUTH PLAIN

Issuing the AUTH command

(PLAIN in the argument)

7

AUTH DIGEST-MD5

Issuing the AUTH command

(DIGEST-MD5 in the argument)

8

SEND USER

Sending the user name

9

SEND PASS

Sending the password

10

SEND USER PASS

Sending the user name and password

11

AUTH END

Reporting the completion of authentication

12

QUIT

Issuing the QUIT command

13

MAIL command argument

Issuing the MAIL command

14

RCPT command argument

Issuing the RCPT command

15

RSET

Issuing the RSET command

16

NOOP

Issuing the NOOP command

17

DATA

Issuing the DATA command

18

SEND MAIL

Sending the mail data

19

.

Reporting that the mail is sent

20

STARTTLS

Issuing the STARTTLS command

7.10.2 For the POP3-related messages

The following table describes the mapping between the strings that indicate communication processing, output in messages, and communication processing for the POP3-related messages:

No.

String indicating communication processing

Communication processing

1

--

Acquiring a connection

2

connect-mail-server

Acquiring the server response for the connection

3

USER

Issuing the USER command

4

PASS

Issuing the PASS command

5

QUIT

Issuing the QUIT command

6

STAT

Issuing the STAT command

7

LIST command argument

Issuing the LIST command

8

UIDL command argument

Issuing the UIDL command

9

RETR command argument

Issuing the RETR command

10

TOP command argument

Issuing the TOP command

11

DELE command argument

Issuing the DELE command

12

NOOP

Issuing the NOOP command

13

RSET

Issuing the RSET command

14

CAPA

Issuing the CAPA command

8 KDJJ (Messages Output by Cosminexus Component Container)

This chapter describes the messages beginning with KDJJ from the messages output by Cosminexus Component Container.

8.1 Format for describing the messages

The format for describing the messages in this chapter is as follows:

XXXXnnnnn-Y

Message text

Description of variable values

Description

Supplementary description of the message text

Action

Action taken by the user

Note that for some messages, Description about the variable value, Description, and Action might not be described.

Each item is described as follows:

XXXXnnnnn

This describes the message ID.

The elements configuring a message ID are as follows:

XXXX

This describes the prefix of the messages output by Cosminexus Component Container with KDJJ.

nnnnn

This describes message numbers managed by Cosminexus Component Container. A five-digit unique number is attached to each message.

Y

This describes the message level. The message level is indicated by one alphabetic character.

The alphabetic characters indicating the message levels and their meanings are as follows:

E (Error)

This message reports the occurrence of an error-level problem.

When this message is displayed the processing is interrupted.

W (Warning)

This message reports the occurrence of a warning-level problem.

The processing continues even after this message is displayed.

I (Information)

This message reports a system operation.

The processing continues even after this message is displayed.

Message text

This describes the message text output by Cosminexus Component Container.

Note that the variable value (value that varies depending upon the status in which the message is output) within the message text is output with the format xx....xx (xx are lower-case alphabetical characters).

Description of variable values

The information displayed in the variable value within the message text is output with the format 'xx....xx: displayed-information' (xx are lower-case alphabetical characters). An example of the format for describing variable values is as follows:

Example:

aa....aa: File name

bb....bb: Application name

Description

This is the supplementary description of the message, such as the factors responsible for reporting the message and the Cosminexus Component Container operations that output the message.

Action

This is the action to be taken by the user. Note that 'Contact maintenance personnel' in the action indicates that the System Administrator needs to contact our helpdesk based on the purchase agreement.

8.2 Messages from KDJJ10000 to KDJJ19999

This section describes the messages from KDJJ00000 to KDJJ19999 and the corresponding actions.

KDJJ10002-E

The provider class, aa....aa, could not be instantiated. Processing will continue but the class will not be utilized

aa....aa: Provider class name

Description

The provider could not be instantiated. The provider cannot be used.

Action

See the displayed information and then take action. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJJ10003-E

A message body reader for the type, class aa....aa, could not be found

aa....aa: Java type corresponding to the received entity body

Description

Resource-side

MessageBodyReader that reads the received entity body could not be found. An unsupported MIME media type is specified in the Consumes annotation of the Web resource method, or an unsupported MIME media type is specified in the Content-Type HTTP header of the received HTTP message.

Client-side

MessageBodyReader that reads the received entity body could not be found. An unsupported MIME media type is specified in the Content-Type HTTP header of the received HTTP message.

Action

Specify a supported MIME media type in the Consumes annotation of the Web resource method. Check whether the HTTP client or the Web resource sent a message about the unsupported MIME media type.

KDJJ10005-E

The class aa....aa could not be found. This class is ignored.

aa....aa: Specified class name

Description

The class specified in the servlet initialization parameters com.sun.jersey.spi.container.ContainerResponseFilters and/ or com.sun.jersey.spi.container.ContainerRequestFilters in web.xml could not be found. The specified class is ignored.

Action

Specify com.cosminexus.jersey.api.container.filter.LoggingFilter in the servlet initialization parameters com.sun.jersey.spi.container.ContainerResponseFilters and com.sun.jersey.spi.container.ContainerRequestFilters.

KDJJ10006-E

The following errors and warnings have been detected with resource and/or provider classes: aa....aa

aa....aa: List of sub-messages

Description

An error and/ or warning were detected while a resource class and/ or provider was being initialized.

Action

See the displayed sub-message and resolve the error. For details on the examples of sub-messages, see 8.5 Sub-messages. If a sub-message not listed in 8.5 Sub-messages is displayed, determine the cause of the error based on the contents of the message and then resolve the error.

KDJJ10009-E

Error processing resource method, aa....aa, for ResourceMethodDispatchProvider, bb....bb.

aa....aa: Method name

bb....bb: ResourceMethodDispatchProvider class name used in the JAX-RS functionality

Description

An error occurred in the processing of the resource method. An exception is thrown during the process of injection in the parameter annotated in DefaultValue of the resource method or sub-resource method.

Action

See the details and then take action. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJJ10010-E

The RuntimeException could not be mapped to a response, re-throwing to the HTTP container

Description

The runtime exception could not be mapped to an HTTP response, and is re-thrown to the Web container.

Action

See the exception log to remove the cause of the runtime exception.

KDJJ10017-E

The exception contained within MappableContainerException could not be mapped to a response, re-throwing to the HTTP container

Description

A checked exception could not be mapped to an HTTP response, and is re-thrown to the Web container.

Action

See the exception log to remove the cause of the runtime exception.

KDJJ10018-E

Mapped exception to response: aa....aa bb....bb

aa....aa: HTTP header status code

bb....bb: Status string

Description

WebApplicationException occurred while a Web resource was being invoked. WebApplicationException is mapped to an HTTP response based on the response information in WebApplicationException.

Action

See the displayed information and then take action. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJJ10019-E

Mapped exception to response: aa....aa

aa....aa: HTTP header status code

Description

WebApplicationException occurred while a Web resource was being invoked. WebApplicationException is mapped to an HTTP response based on the response information in WebApplicationException.

Action

See the displayed information and then take action. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJJ10020-E

The ResourceConfig instance does not contain any root resource classes.

Description

The Web application (WAR file) does not contain valid root resource classes. The WAR file does not contain any root resource class, or the value specified in the servlet initialization parameter com.sun.jersey.config.property.packages in the web.xml file is incorrect.

Action

Check the following items:

Is the root resource class included correctly in the WAR file?

The root resource class must be deployed in \WEB-INF\lib and/or \WEB-INF\classes of the WAR file.

Is an appropriate package name described in the servlet initialization parameter com.sun.jersey.config.property.packages in the web.xml file

KDJJ10024-E

A message body reader for Java class aa....aa, and Java type bb....bb, and MIME media type cc....cc was not found

aa....aa: Instance class

bb....bb: Generic type

cc....cc: MIME media type

Description

MessageBodyReader that reads the received entity body could not be found. An unsupported MIME media type is specified in the Consumes annotation of the Web resource method, or an unsupported MIME media type is specified in the Content-Type HTTP header of the received HTTP message.

Action

Specify a supported MIME media type in the Consumes annotation of the Web resource method. Check whether the HTTP client sent a message about the unsupported MIME media type.

KDJJ10026-E

A message body writer for Java class aa....aa: , and Java type bb....bb: , and MIME media type cc....cc: was not found

aa....aa: Instance class

bb....bb: Generic type

cc....cc: MIME media type

Description

MessageBodyReader that writes the sent entity body could not be found. An unsupported MIME media type is specified in the Produces annotation of the Web resource method, or an unsupported MIME media type is specified in the Accept HTTP header of the received HTTP message.

Action

Specify a supported MIME media type in the Produces annotation of the Web resource method. Check whether the HTTP client requests a message about the unsupported MIME media type.

KDJJ10028-E

Exception mapper aa....aa for Throwable bb....bb threw a RuntimeException when attempting to obtain the response

aa....aa: Exception mapping provider name

bb....bb: Exception name

Description

A runtime exception occurred while creating a response with the exception mapping provider.

Action

See the exception log to remove the cause of the runtime exception.

KDJJ10031-E

A message body reader for Java class aa....aa, and Java type bb....bb, and MIME media type cc....cc was not found

aa....aa: Object class

bb....bb: Generic type

cc....cc: MIME media type

Description

MessageBodyReader that reads the received entity body could not be found. An unsupported MIME media type is specified in the Content-Type HTTP header of the received HTTP message.

Action

Specify a supported MIME media type in the Content-Type HTTP header of the received HTTP message.

KDJJ10032-E

A message body writer for Java class aa....aa, and Java type bb....bb, and MIME media type cc....cc was not found

aa....aa: Object class

bb....bb: Generic class

cc....cc: MIME media type

Description

MessageBodyWriter that writes the received entity body could not be found. An unsupported MIME media type is specified in the Content-Type HTTP header of the received HTTP message.

Action

Specify a supported MIME media type in the Content-Type HTTP header of the HTTP message.

KDJJ10039-E

Failed to invoke the resource.

Description

An exception occurred while an HTTP request was being processed.

Action

See the exception log to remove the cause of the runtime exception. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJJ10040-E

There are no matched resources that can consume aa....aa media type

aa....aa: MIME media type

Description

There are no Web resources that can process the MIME media type specified in the Content-Type HTTP header of the received HTTP request.

Action

Implement a Web resource that can process the MIME media type specified in the Content-Type HTTP header. Also, check whether the HTTP client sent a message about the unsupported MIME media type.

KDJJ10041-E

There are no matched resources that can produce aa....aa media type

aa....aa: MIME media type

Description

There are no Web resources that can process the MIME media type specified in the Accept HTTP header of the received HTTP request.

Action

Implement a Web resource that can process the MIME media type specified in the Accept HTTP header. Also, check whether the HTTP client requests a message about the unsupported MIME media type.

KDJJ10042-E

The request parameter count exceeded the maximum number (context root = aa....aa, request URI = bb....bb, max count = cc....cc)

aa....aa: Context root

bb....bb: Request URI

cc....cc: Maximum number of form parameters

Description

The number of form data parameters sent by the client exceeded the maximum value.

Action

Check whether the number of form data parameters sent by the client exceeds the value (maximum number of form parameters) set in the webserver.connector.limit.max_parameter_count key of the user property file for J2EE servers. If the number of form parameters used exceeds the maximum value, change the maximum number of form parameters to an appropriate value. If you change the maximum number of form parameters, you must restart the J2EE server.

KDJJ18888-E

Client API could not complete the requested operation. (detail=aa....aa)

aa....aa: Detail

Description

Client API could not complete the requested operation.

Action

Remove the cause of the error based on the detail. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJJ19999-E

Error Occurred: (details= aa....aa)

aa....aa: Details

Description

An error occurred.

Action

Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

8.3 Messages from KDJJ20000 to KDJJ29999

This section describes the messages from KDJJ20000 to KDJJ29999 and the corresponding actions.

KDJJ20003-W

The following warnings have been detected with resource and/or provider classes:aa....aa

aa....aa: List of sub-messages

Description

A warning was detected during the initialization of the resource class and/ or provider.

Action

Take action for each displayed sub-message. For details on the examples of sub-messages, see 8.5 Sub-messages. If a sub-message not listed in 8.5 Sub-messages is displayed, determine the cause of the error based on the contents of the message and then resolve the error.

KDJJ20007-W

A servlet POST request, to the URI aa....aa, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.

aa....aa: URI

Description

The entity body of the received HTTP request contains information injected into a parameter annotated with the FormParam annotation. However, the entity body of the HTTP request might already be accessed from a servlet or servlet filter other than the Cosminexus JAX-RS functionality.

Action

The entity body of the HTTP request must not be accessed in a servlet or servlet filter other than the Cosminexus JAX-RS functionality. If the entity body of the HTTP request must be accessed, do not reference the entity body using the entity parameter in the Web resource.

KDJJ20010-W

There are more than one constructor with same number of parameters. Hence the first constructor that has same number of parameters will be used to instantiate the Root Resource Class aa....aa

aa....aa: Root resource class name

Description

There are multiple constructors with the same number of parameters in the root resource class. The root resource class is instantiated by using the constructor defined first.

Action

Do not define constructors with the same number of parameters.

KDJJ20011-W

There are more than one constructor with same number of parameters. Hence the first constructor that has same number of parameters will be used to instantiate the Provider Class aa....aa

aa....aa: Custom Provider class name

Description

There are multiple constructor classes with the same number of parameters in the provider class. The provider class is initiated by using the constructor class defined first.

Action

Do not define constructors with the same number of parameters.

KDJJ20012-W

There are multiple entity parameters for bb....bb#aa....aa() method. Hence the first entity parameter is considered and rest of them are ignored

aa....aa: Method name

bb....bb: Resource class name

Description

A resource method or sub-resource method with multiple entity parameters was found. The entity body is injected into the entity parameter defined first, and the rest of the entity parameters are ignored.

Action

Do not define multiple entity parameters in a resource method or sub-resource method.

KDJJ20013-W

The Root and Client AP cannot be added to client request headers. Cause: aa....aa

aa....aa: Cause

Description

The Root and Client application information cannot be added to the HTTP header of the HTTP request.

Action

Remove the cause of the warning on the basis of the cause.

KDJJ29999-W

General Warning: (details= aa....aa)

aa....aa: Details

Description

This is a warning message. See the details.

Action

Remove the cause of the warning based on the details.

8.4 Messages from KDJJ30000 to KDJJ39999

This section describes the messages from KDJJ30000 to KDJJ39999 and the corresponding actions.

KDJJ30005-I

Scanning for root resource and provider classes in the packages: aa....aa

aa....aa: List of packages specified in the servlet initialization parameter com.sun.jersey.config.property.packages

Description

The reading of the root resource class and exception mapping provider included in the package specified in the servlet initialization parameter com.sun.jersey.config.property.packages, started.

KDJJ30007-I

No provider classes found.

Description

The exception mapping provider was not found.

KDJJ30008-I

Root resource classes found: aa....aa

aa....aa: Root resource class list

Description

The root resource class was read.

KDJJ30009-I

Scanning for root resource and provider classes in the Web app resource paths: aa....aa

aa....aa: List of paths to be read

Description

The reading of all the root resource classes and exception mapping providers included in the Web application (WAR file) was started because the servlet initialization parameter com.sun.jersey.config.property.packages was not specified in the web.xml file.

KDJJ30012-I

aa....aa * Server in-bound request

bb....bb

aa....aa: HTTP request number used for each Web application (WAR file)

bb....bb: Details of the HTTP request

Description

The received HTTP request is recorded in the communication log. The entity body is omitted.

KDJJ30013-I

aa....aa * Server in-bound request

bb....bb

aa....aa: HTTP request number used for each Web application (WAR file)

bb....bb: Details of the HTTP request

Description

The received HTTP request is recorded in the communication log.

KDJJ30014-I

aa....aa * Server out-bound response

bb....bb

aa....aa: HTTP response number used for each Web application (WAR file)

bb....bb: HTTP response details

Description

The sent HTTP response is recorded in the communication log. The entity body is ignored.

KDJJ30015-I

aa....aa * Server out-bound response

bb....bb

aa....aa: HTTP response number used for each Web application (WAR file)

bb....bb: HTTP response details

Description

The sent HTTP response is recorded in the communication log.

KDJJ30019-I

Initiating Cosminexus JAX-RS application, version aa....aa

aa....aa: Version name

Description

The initialization of the Web resource that uses the Cosminexus JAX-RS functionality starts.

KDJJ30021-I

Mapped exception to response: aa....aa (bb....bb)

aa....aa: HTTP status code

bb....bb: Status string

Description

WebApplicationException occurred while a Web resource was being invoked. WebApplicationException is mapped to an HTTP response based on the response information in WebApplicationException.

KDJJ30022-I

Mapped exception to response aa....aa

aa....aa: HTTP response status code

Description

WebApplicationException occurred while a Web resource was being invoked. WebApplicationException is mapped to an HTTP response based on the response information in WebApplicationException.

KDJJ30025-I

Provider classes found: aa....aa

aa....aa: List of exception mapping providers

Description

The exception mapping provider was read.

KDJJ30026-I

aa....aa * Client out-bound request

bb....bb

aa....aa: HTTP request number that is indexed for each Client object

bb....bb: Detail of HTTP request

Description

The sent HTTP request is recorded in the communication log.

KDJJ30027-I

aa....aa * Client in-bound response

bb....bb

aa....aa: HTTP request number that is indexed for each Client object

bb....bb: Detail of HTTP response

Description

The received HTTP response is recorded in the communication log.

KDJJ39999-I

General Information: (details= aa....aa)

aa....aa: Details

Description

This message provides information. See the displayed details.

8.5 Sub-messages

8.5.1 Details of sub-messages

The following table lists and describes the examples of sub-messages displayed in the KDJJ10006-E error message and the KDJJ20003-W warning message. If a sub-message not listed in this table is displayed, determine the cause of the error based on the contents of the message and then resolve the error.

Table 8‒1: Examples of sub-messages

No.

Sub-messages

1

Missing dependency for constructor aa....aa at parameter index bb....bb

2

Missing dependency for field: aa....aa

3

Illegal URI template for root resource class aa....aa: bb....bb

4

Illegal URI template for sub-resource method aa....aa: bb....bb

5

Illegal URI template for sub-resource locator aa....aa: bb....bb

6

Missing dependency for method aa....aa at parameter at index bb....bb

7

Method, aa....aa, annotated with bb....bb of resource, cc....cc, is not recognized as valid resource method.

8

The class aa....aa is an interface and cannot be instantiated.

9

A sub-resource locator, aa....aa, cannot have an entity parameter. Try to move the parameter to the corresponding resource method.

10

The class aa....aa does not have a public constructor and cannot be instantiated.

11

A (sub-)resource method, aa....aa, should have only one HTTP method designator. It currently has the following designators defined: bb....bb

12

Conflicting URI templates. The URI template aa....aa for root resource class bb....bb and the URI template cc....cc transform to the same regular expression dd....dd

13

Conflicting URI templates. The URI template aa....aa for sub-resource locator bb....bb and the URI template cc....cc transform to the same regular expression dd....dd

14

Consuming media type conflict. The resource methods aa....aa and bb....bb can consume the same media type

15

Producing media type conflict. The resource methods aa....aa and bb....bb can produce the same media type

16

A sub-resource locator, aa....aa, MUST return a non-void type.

17

A HTTP GET method, aa....aa, should not consume any entity.

18

A resource method, aa....aa, MUST be public scoped otherwise the method is ignored

19

A sub-resource method, aa....aa, MUST be public scoped otherwise the method is ignored

20

A sub-resource locator, aa....aa, MUST be public scoped otherwise the method is ignored

21

A HTTP GET method, aa....aa, MUST return a non-void type.

22

The class aa....aa is an abstract class and cannot be instantiated.

23

Return type aa....aa of method bb....bb is not resolvable to a concrete type

24

Parameter aa....aa of type bb....bb from cc....cc is not resolvable to a concrete type

The description and action corresponding to the example sub-messages are as follows:

(1) Missing dependency for constructor aa....aa at parameter index bb....bb

aa....aa: Constructor name

bb....bb: Position of the parameter

Description

The dependency for the constructor parameter cannot be resolved.

Action

Use a supported parameter type in the injection annotation.

(2) Missing dependency for field: aa....aa

aa....aa: Field name

Description

The dependency for the field cannot be resolved.

Action

Use a supported parameter type in the injection annotation.

(3) Illegal URI template for root resource class aa....aa: bb....bb

aa....aa: Class name

bb....bb: Details

Description

The URI template for the root resource class is invalid.

Action

Remove the cause of the error based on the displayed details. For the examples on details, see 8.6 Inner messages displayed in the sub-messages (details when the URI template is invalid). If details not existing in 8.6 Inner messages displayed in the sub-messages (details when the URI template is invalid) are displayed, determine the cause of the error based on the details and then resolve the error.

(4) Illegal URI template for sub-resource method aa....aa: bb....bb

aa....aa: Sub-resource method name

bb....bb: Details

Description

The URI template for the sub-resource method is invalid.

Action

Remove the cause of the error based on the displayed details. For the examples on details, see 8.6 Inner messages displayed in the sub-messages (details when the URI template is invalid). If details not existing in 8.6 Inner messages displayed in the sub-messages (details when the URI template is invalid) are displayed, determine the cause of the error based on the details and then resolve the error.

(5) Illegal URI template for sub-resource locator aa....aa: bb....bb

aa....aa: Sub-resource locator name

bb....bb: Details

Description

The URI template for the sub-resource locator is invalid.

Action

Remove the cause of the error based on the displayed details. For the examples on details, see 8.6 Inner messages displayed in the sub-messages (details when the URI template is invalid). If details not existing in 8.6 Inner messages displayed in the sub-messages (details when the URI template is invalid) are displayed, determine the cause of the error based on the details and then resolve the error.

(6) Missing dependency for method aa....aa at parameter at index bb....bb

aa....aa: Method name

bb....bb: Position of the parameter

Description

The dependency for the method parameter cannot be resolved.

Action

Use a supported parameter type in the injection annotation.

(7) Method, aa....aa, annotated with bb....bb of resource, cc....cc, is not recognized as valid resource method.

aa....aa: Method name

bb....bb: Request method identifier

cc....cc: Class name

Description

The annotated method is not recognized as a valid resource method.

Action

Check the conditions for the resource method, sub-resource method, and sub-resource locator. If the conditions do not match, make the corrections.

(8) The class aa....aa is an interface and cannot be instantiated.

aa....aa: Interface name

Description

The interface cannot be instantiated.

Action

Do not use the Path annotation and Provider annotation in the interface.

(9) A sub-resource locator, aa....aa, cannot have an entity parameter. Try to move the parameter to the corresponding resource method.

aa....aa: Method name

Description

A sub-resource locator containing an entity parameter was detected.

Action

Move the entity parameter to an appropriate resource method or sub-resource method.

(10) The class aa....aa does not have a public constructor and cannot be instantiated.

aa....aa: Class name

Description

The class does not have a public constructor and cannot be instantiated.

Action

Define a public constructor.

(11) A (sub-)resource method, aa....aa, should have only one HTTP method designator. It currently has the following designators defined: bb....bb

aa....aa: Method name

bb....bb: List of request method identifiers

Description

A resource method or sub-resource method containing multiple request method identifiers was detected.

Action

Use only one request method identifier for a resource method or sub-resource method.

(12) Conflicting URI templates. The URI template aa....aa for root resource class bb....bb and the URI template cc....cc transform to the same regular expression dd....dd

aa....aa: URI template

bb....bb: Class name

cc....cc: URI template

dd....dd: Expression after resolution

Description

The URI templates of the root resource classes are conflicting. Two URI templates are similar, or regular expressions resolved to the same expression are being used.

Action

Make sure that the URI template of each root resource class is different. Also, make sure that the regular expressions are not resolved to the same expression.

(13) Conflicting URI templates. The URI template aa....aa for sub-resource locator bb....bb and the URI template cc....cc transform to the same regular expression dd....dd

aa....aa: URI template

bb....bb: Class name

cc....cc: URI template

dd....dd: Expression after resolution

Description

The URI templates of the sub-resource locators are conflicting. Two URI templates are similar, or regular expressions resolved to the same expression are being used.

Action

Make sure that the URI template of each sub-resource locator is different. Also, make sure that the regular expressions are not resolved to the same expression.

(14) Consuming media type conflict. The resource methods aa....aa and bb....bb can consume the same media type

aa....aa: Method name

bb....bb: Method name

Description

The MIME media types specified in the Consumes annotation are conflicting.

Action

Specify a non-conflicting MIME media type in the Consumes annotation.

(15) Producing media type conflict. The resource methods aa....aa and bb....bb can produce the same media type

aa....aa: Method name

bb....bb: Method name

Description

The MIME media types specified in the Produces annotation are conflicting.

Action

Specify a non-conflicting MIME media type in the Produces annotation.

(16) A sub-resource locator, aa....aa, MUST return a non-void type.

aa....aa: Method name

Description

The return value of the sub-resource locator is void.

Action

The return value of the sub-resource locator must not be void.

(17) A HTTP GET method, aa....aa, should not consume any entity.

aa....aa: Method name

Description

The method annotated in the GET request method identifier has an entity parameter.

Action

The method annotated in the GET request method identifier must not include an entity parameter.

(18) A resource method, aa....aa, MUST be public scoped otherwise the method is ignored

aa....aa: Method name

Description

A non-public resource method was detected. The detected resource method is ignored.

Action

A resource method must be public scoped.

(19) A sub-resource method, aa....aa, MUST be public scoped otherwise the method is ignored

aa....aa: Method name

Description

A non-public sub-resource method was detected. The detected sub-resource method is ignored.

Action

A sub-resource method must be public scoped.

(20) A sub-resource locator, aa....aa, MUST be public scoped otherwise the method is ignored

aa....aa: Method name

Description

A non-public sub-resource locator was detected. The detected sub-resource locator is ignored.

Action

A sub-resource locator must be public scoped.

(21) A HTTP GET method, aa....aa, MUST return a non-void type.

aa....aa: Method name

Description

The return value of the method annotated in the GET request method identifier is void.

Action

The return value of the method annotated in the GET request method identifier must not be void.

(22) The class aa....aa is an abstract class and cannot be instantiated.

aa....aa: Class name

Description

An abstract class cannot be instantiated.

Action

Do not use the Path annotation and Provider annotation in the abstract class.

(23) Return type aa....aa of method bb....bb is not resolvable to a concrete type

aa....aa: Return value type

bb....bb: Method name

Description

A method having a return value with a non-resolvable type parameter was detected.

Action

Review, and if necessary revise, the return value type.

(24) Parameter aa....aa of type bb....bb from cc....cc is not resolvable to a concrete type

aa....aa: Position of the parameter

bb....bb: Type

cc....cc: Method signature

Description

A method having an entity parameter with a non-resolvable type parameter was detected.

Action

Review, and if necessary revise, the entity parameter type.

8.6 Inner messages displayed in the sub-messages (details when the URI template is invalid)

8.6.1 Details of inner messages

The following table lists and describes examples of inner messages displayed in the sub-messages indicating that the URI template is invalid. If an inner message not listed in this table is displayed, determine the cause of the error based on the contents of the message and then resolve the error.

Table 8‒2: Examples of inner messages (details when the URI template is invalid)

No.

Inner message (details when the URI template is invalid)

1

Invalid syntax for the template expression 'aa....aa'

2

Illegal character 'aa....aa' at position bb....bb is not as the start of a name

3

Illegal character 'aa....aa' at position bb....bb is not allowed as part of a name

4

Illegal character 'aa....aa' at position bb....bb is not allowed after a name

5

Invalid syntax for the template, "aa....aa". Check if a path parameter is terminated with a '}'.

6

Invalid syntax for the expression 'aa....aa' associated with the name 'bb....bb'

7

The name 'aa....aa' is declared more than once with different regular expressions

The description and action corresponding to the example inner messages are as follows:

(1) Invalid syntax for the template expression 'aa....aa'

aa....aa: Expression of the URI template

Description

The URI template has an invalid syntax.

Action

Modify the settings so that the URI template syntax becomes a valid expression.

(2) Illegal character 'aa....aa' at position bb....bb is not as the start of a name

aa....aa: Invalid character

bb....bb: Position of the character

Description

The first character of the template parameter identifier is an invalid character.

Action

Remove the invalid character specified at the beginning of the template parameter identifier.

(3) Illegal character 'aa....aa' at position bb....bb is not allowed as part of a name

aa....aa: Invalid character

bb....bb: Position of the character

Description

An invalid character is specified as a part of the template parameter identifier.

Action

Remove the invalid character specified in the template parameter identifier.

(4) Illegal character 'aa....aa' at position bb....bb is not allowed after a name

aa....aa: Invalid character

bb....bb: Position of the character

Description

An invalid character is specified immediately after the template parameter identifier.

Action

Remove the invalid character specified immediately after the template parameter identifier.

(5) Invalid syntax for the template, "aa....aa". Check if a path parameter is terminated with a '}'.

aa....aa: Expression of the URI template

Description

The expression of the URI template has an invalid syntax.

Action

Modify the settings so that the URI template syntax becomes a valid expression. Also, check whether the template parameter ends with '}'. If it does not, make sure the template parameter ends with '}'.

(6) Invalid syntax for the expression 'aa....aa' associated with the name 'bb....bb'

aa....aa: Normal expression

bb....bb: Identifier

Description

The regular expression for the template parameter has an invalid syntax.

Action

Modify the syntax of the regular expression for the template parameter.

(7) The name 'aa....aa' is declared more than once with different regular expressions

aa....aa: Identifier

Description

Two or more similar identifiers are used in multiple template parameters of the same URI template.

Action

Use specific identifiers for different template parameters in the same URI template.

9 Messages from KDJR00000 to KDJR99999 (Messages Output by Cosminexus Component Container)

This chapter describes the messages beginning with KDJR from the messages output by Cosminexus Component Container.

9.1 Format for describing messages

The format for describing the messages in this chapter is as follows:

XXXXnnnnn-Y

Message text

Description about the variable value

Description

Supplementary description of the message text

Action

Action taken by the user

Note that for some messages, Description about the variable value, Description, and Action might not be described.

Each item is described as follows:

XXXXnnnnn

This describes the message ID.

The elements configuring a message ID are as follows:

XXXX

This describes prefix KDJR of the messages output by Cosminexus Component Container.

nnnnn

This describes the message numbers managed by Cosminexus Component Container. A five-digit unique number is attached to each message.

Y

This describes the message level. The message level is indicated by one alphabetic character.

The alphabetic characters indicating the message levels and their meanings are as follows:

E (Error)

This message reports the occurrence of an error-level problem.

When this message is output, the processing is interrupted.

W (Warning)

This message reports the occurrence of a warning-level problem.

The processing continues even after this message is output.

I (Information)

This message reports a system operation.

The processing continues even after this message is output.

Message text

This describes the message text output by Cosminexus Component Container.

Note that the variable value (value that varies depending upon the status in which the message is output) within the message text is output in the xx....xx format (xx are lower-case alphabetical characters).

Description about the variable value

The information displayed in the variable value in the message text is output in the 'xx....xx: Displayed-information' (xx are lower-case alphabetical characters) format. An example of the format for describing variable values is as follows:

(Example)

aa....aa: File name

bb....bb: Application name

Description

This is the supplementary description of the message, such as the factors responsible for reporting the message and operation of Cosminexus Component Container that output the message.

Action

This is the action to be taken by the user. 'Contact maintenance personnel' mentioned in the action describes that the System Administrator must contact our helpdesk based on the purchase agreement.

9.2 Messages from KDJR00000 to KDJR09999

This section describes the messages from KDJR00000 to KDJR09999 and their corresponding actions.

KDJR01112-I

Waiting for message acknowledgements on a sequence aa....aa timed out after bb....bb milliseconds.

aa....aa: Sequence ID

bb....bb: Standby time

Description

When an attempt is made to terminate the sequence at the client side, there is a standby for a fixed time period until Ack messages are sent for all the messages by the service. When Ack messages are not sent after a fixed time period, this message is output and the sequence is terminated.

Action

The sequence is terminated forcibly. No additional processing is required at the client side. For details on the cause of not sending the Ack message, contact the service.

KDJR09999-I

Information message. (detail = aa....aa)

aa....aa: Detailed message

Description

Notification during the execution of the WS-RM functionality.

Action

Check the detailed message as and when required.

9.3 Messages from KDJR10000 to KDJR19999

This section describes the messages from KDJR10000 to KDJR19999 and their corresponding actions.

KDJR11001-W

A message will be resend. (SequenceID = aa....aa, MessageNumber = bb....bb, count = cc....cc, cause=dd....dd)

aa....aa: Sequence ID

bb....bb: Message number

cc....cc: Message resending count

dd....dd: Cause of resending

Description

The message is resend by the WS-RM functionality.

Action

Nothing in particular.For details on the cause of resending the message, reference the display contents of the cause.

KDJR11103-W

Unable to terminate RM sequence normally due to an unexpected exception.

Description

An attempt was made to invoke the close method to terminate the sequence in the client, but an error occurred. The sequence is terminated forcibly. The possible causes of the error are as follows:

When a sequence close message or a sequence termination message request is sent to the service, the service returns an invalid response.

When a sequence close message or a sequence termination message request is sent to the service, the connection is disconnected.

The sequence has expired.

Action

The addition processing need not be performed in the client. Review, and if necessary revise, the connection timeout value or read timeout value of the client and the sequence validity period, and then if the service returns an invalid response, contact the service.

KDJR11108-W

Response for the acknowledgement request is null.

Description

A request for Ack message has been sent at the background by the client; however, there is no response for the Ack message from the service side.

Initial message processing takes time. There are cases whereby the Ack message is not returned from the service side if the sending and receiving of the Ack message is performed at the background during the initial message processing.

Action

Contact the service for the cause.

KDJR11117-W

The sequence identifier in the terminate sequence response message aa....aa does not correspond to the terminating outbound sequence identifier bb....bb.

aa....aa: Received sequence ID

bb....bb: Sent sequence ID

Description

When the close method is invoked for terminating the sequence at the client side and when the request for terminating sequence message is sent at the service side, the sequence ID sent by the request and the sequence ID of the response returned by the service is different. The sequence is terminated forcibly.

Action

No additional processing is required at the client side. Contact the service for the cause.

KDJR11119-W

The sequence identifier in the close sequence response message aa....aa does not correspond to the closing outbound sequence identifier bb....bb.

aa....aa: Received sequence ID

bb....bb: Sent sequence ID

Description

When the close method is invoked for terminating the sequence at the client side and when the request for closing the sequence message is sent at the service side, the sequence ID sent by the request and the sequence ID of the response returned by the service is different. The sequence is terminated forcibly.

Action

No additional processing is required at the client side. Contact the service for the cause.

KDJR11127-W

An unexpected exception occurred while sending acknowledgement request.

Description

Received an invalid Ack message.

Action

Contact the message sender for the cause.

KDJR16017-W

The WS-RM property contains an invalid value. The default value will be used. (key = aa....aa, value = bb....bb, default = cc....cc)

aa....aa: Property name

bb....bb: Specified value

cc....cc: Applicable default value

Description

A value that is out of range is specified in the settings of the WS-RM 1.2 functionality of WSDL. Therefore, the default value is used.

Action

Check and, if necessary, revise the settings as and when required.

KDJR19999-W

An warning occurred during WS-RM execution. (detail=aa....aa)

aa....aa: Detailed message

Description

A minor error occurred during the execution of the WS-RM functionality.

Action

Check the detailed message, and determine the cause as and when required.

9.4 Messages from KDJR20000 to KDJR29999

This section describes the messages from KDJR20000 to KDJR29999 and their corresponding actions.

KDJR21001-E

A message will not be resend as maximum number of message resend attempts has been reached. (SequenceID = aa....aa, MessageNumber = bb....bb, count = cc....cc, cause=dd....dd)

aa....aa: Sequence ID

bb....bb: Message number

cc....cc: Message resending count

dd....dd: Cause of resending

Description

A message will not be resent as the maximum number of message resending attempts (3 times) has been reached during the execution of the WS-RM functionality.

Action

Determine the cause of resending, and eliminate the cause. Also, check the sequence ID and the message number, and determine the cause of resending the KDJR11001-W message for the same sequence ID and message number.

If the java.net.SocketTimeoutException exists in the cause, there might be read timeout of the client socket.

Check the processing time required at the service side and the definition file of the JAX-WS functionality, or the read timeout value of the client socket of the definition file for each process.

KDJR21120-E

Unable to process response packet - the packet was not identified as an RM protocol message.

Description

Received an Ack message indicating an invalid wsa:Action element value.

Action

Contact the message sender for the cause.

KDJR21122-E

Unable to unmarshall RM header aa....aa

aa....aa: SOAP header element name

Description

Received a message indicating that the element value of SOAP header of WS-RM is invalid.

Action

Contact the message sender for the cause.

KDJR21138-E

The maximum value for a message number on a sequence aa....aa has been exceeded: bb....bb

aa....aa: Sequence ID

bb....bb: Message number

Description

Exceeded the maximum number of messages that can be sent and received in a single sequence.

Action

Generate the sequence again. To generate a sequence again:

Cast the port objects that are being used to com.sun.xml.ws.Closeable type and invoke the close() method.

Re-create the port objects from the service class.

Invoke the Web Service method of the port objects that are re-created.

The sequence is generated automatically during the initial invocation of Web Service method of the port objects.

Set the maximum message count (cwsrm:MaxMessageNumber) of WSDL when changing the maximum message count that can be sent and received for a single sequence.

KDJR29999-E

An error occurred during WS-RM execution. (detail = aa....aa)

aa....aa: Detailed message

Description

An error occurred during the execution of the WS-RM functionality.

Action

Check the detailed message, and determine the cause.

10 Messages from KDJW00000 to KDJW99999 (Messages Output by Cosminexus Component Container)

This chapter describes the messages beginning with KDJW from the messages output by Cosminexus Component Container.

10.1 Format for describing the messages

The format for describing the messages in this chapter is as follows:

XXXXnnnnn-Y

Message text

Description of variable values

Description

Supplementary description of the message text

Action

Action taken by the user

Note that for some messages, Description about the variable value, Description, and Action might not be described.

Each item is described as follows:

XXXXnnnnn

This describes the message ID.

The elements configuring a message ID are as follows:

XXXX

This describes the prefix of the messages output by Cosminexus Component Container with KDJW.

nnnnn

This describes message numbers managed by Cosminexus Component Container. A five-digit unique number is attached to each message.

Y

This describes the message level. The message level is indicated by one alphabetic character.

The alphabetic characters indicating the message levels and their meanings are as follows:

E (Error)

This message reports the occurrence of an error-level problem.

When this message is displayed the processing is interrupted.

W (Warning)

This message reports the occurrence of a warning-level problem.

The processing continues even after this message is displayed.

I (Information)

This message reports a system operation.

The processing continues even after this message is displayed.

Message text

This describes the message text output by Cosminexus Component Container.

Note that the variable value (value that varies depending upon the status in which the message is output) within the message text is output in the format xx....xx (xx are lower-case alphabetical characters).

Description of variable values

The information displayed in the variable value in the message text is output in the format 'xx....xx: displayed-information' (xx are lower-case alphabetical characters). An example of the format for describing variable values is as follows:

Example:

aa....aa: File name

bb....bb: Application name

Description

This is the supplementary description of the message, such as the factors responsible for reporting the message and the Cosminexus Component Container operations that output the message.

Action

This is the action to be taken by the user. Note that 'Contact maintenance personnel' in the action indicates that the System Administrator needs to contact our helpdesk based on the purchase agreement.

10.2 Messages from KDJW00000 to KDJW09999

This section describes the messages from KDJW00000 to KDJW09999 and the corresponding actions.

KDJW00001-E

There is no attachment for the content ID. (content ID = aa....aa)

aa....aa: content ID

Description

The attached data containing the corresponding content ID does not exist.

Action

Revise the sent message.

KDJW00002-W

Exception ignored from invoking handler method annotated @PreDestroy annotation. (detail = aa....aa)

aa....aa: Detailed message

Description

An exception occurred during the invocation of a method using the @PreDestroy annotation.

Action

Check the detailed message, and then remove the causes of the error.

KDJW00003-E

Unable to create JAXBContext due to the security restriction.

Description

JAXBContext could not be created because of security restrictions.

Action

Check if the exception PrivilegedActionException is output in the exception log and if output, remove the cause.

KDJW00004-E

A @WebService annotation is not present on class. (class = aa....aa)

aa....aa: Class name

Description

The @WebService annotation is not specified.

Action

Specify the @WebService annotation in SEI.

KDJW00005-E

Service endpoint interface is invalid. (service endpoint interface = aa....aa)

aa....aa: Class name

Description

An invalid SEI is specified.

Action

Specify the correct SEI.

KDJW00006-E

Class could not be found. (class = aa....aa)

aa....aa: Class name

Description

The class was not found.

Action

Confirm whether the class exists.

KDJW00007-E

The serviceName cannot be retrieved from an interface. (class = aa....aa)

aa....aa: Class name

Description

An attempt to generate serviceName has failed because an interface is specified in the Web service implementation class.

Action

Revise the settings for specifying the Web service implementation class.

KDJW00008-E

A @WebService.targetNamespace must be specified on classes with no package. (class = aa....aa)

aa....aa: Class name

Description

For classes without a package, targetNamespace must be specified in the @WebService annotation.

Action

Either include the classes in a package or specify targetNamespace in the @WebService annotation.

KDJW00009-E

Given handler does not implement LogicalHandler nor SOAPHandler. (class = aa....aa)

aa....aa: Class name specified in the javaee:handler-class element

Description

Neither the LogicalHandler interface nor SOAPHandler interface is implemented in the class specified in the javaee:handler-class element of the handler chain setup file. Only a logical handler or SOAP handler can be used as the handler.

Action

Specify a class in which either the LogicalHandler interface or SOAPHandler interface is implemented.

KDJW00010-E

Could not find the handler chain file for the class. (class = aa....aa, file = bb....bb)

aa....aa: Class name

bb....bb: Path of the handler chain setup file

Description

The handler chain setup file specified in the file attribute of the @HandlerChain annotation cannot be opened.

Action

Make sure that the correct path is specified.

KDJW00011-E

Could not find the class specified in the handler chain file. (class = aa....aa)

aa....aa: Class name

Description

The class of the handler specified in the handler chain setup file is not found.

Action

Check the coding of the handler chain setup file to make sure that the correct class name is specified.

KDJW00016-W

Failed to remove the temporary file. (detail = aa....aa)

aa....aa: Details

Description

Failed to delete the temporary file.

Action

Reference the details and determine the cause.

KDJW00017-W

The method cannot be annotated with @SOAPBinding with Style "RPC".(class= aa....aa, method= bb....bb, annotation= cc....cc)

aa....aa: Class name

bb....bb: Method name

cc....cc: SOAPBinding annotation

Description

The SOAPBinding annotation with style RPC cannot be annotated to the method.

Action

Review, and if necessary revise, the SOAPBinding annotation annotated to the method.

10.3 Messages from KDJW10000 to KDJW19999

This section describes the messages from KDJW10000 to KDJW19999 and the corresponding actions.

KDJW10001-E

Failed to access the WSDL. (URL= aa....aa, detail = bb....bb)

aa....aa: Invalid URL

bb....bb: Detailed message

Description

The WSDL of the specified URL could not be accessed.

Action

Make sure that the URL is correct and can be accessed.

KDJW10002-E

Failed to access the WSDL.

Description

The WSDL cannot be accessed.

Action

Reference the message, output after this message, that describes the cause of failure, and then remove the cause.

KDJW10003-E

WsdlDocumentLocation is not set to the service instance.

Description

The URL of the WSDL is not specified in the service instance.

Action

Specify the URL of the WSDL in the service instance.

KDJW10005-E

JAX-WS engine cannot get port. (ports=empty)

Description

The port information could not be collected.

Action

The URL of the WSDL might not be specified in the service instance and the port might not be defined in the WSDL. Revise the settings.

KDJW10006-E

JAX-WS engine cannot create proxy because there is no WSDL metadata for service. (service = aa....aa)

aa....aa: Service name

Description

Proxy could not be generated because a WSDL does not exist.

Action

Specify the URL of the WSDL.

KDJW10007-E

Cannot set SOAP 1.2 role. (role = none)

Description

none is set up in the SOAP role.

Action

Set up a valid SOAP role.

KDJW10008-E

Binding is undefined. (binding = aa....aa)

aa....aa: Binding name

Description

Binding is not defined.

Action

Define the binding.

KDJW10009-E

Port type is undefined. (port type = aa....aa)

aa....aa: Port type name

Description

The port type (wsdl:portType element) is not defined in the WSDL.

Action

Define the port type (wsdl:portType element) in the WSDL.

KDJW10010-E

WSDL contains no service definition. (URL= aa....aa)

aa....aa: URL of WSDLL

Description

No service (wsdl:service element) is defined in WSDL.

Action

Define a service (wsdl:service element) in WSDL.

KDJW10011-E

Cannot set the specified class on binding. Handler must be a LogicalHandler. (class = aa....aa)

aa....aa: Class name

Description

Only a logical handler can be set up in the binding.

Action

Set up a logical handler.

KDJW10012-E

Invalid WSDL. (URL = aa....aa, expected element = bb....bb, found element = cc....cc, line = dd....dd)

aa....aa: URL of WSDL

bb....bb: Expected XML element name

cc....cc: Invalid XML element name

dd....dd: Invalid location of WSDL

Description

The coding of WSDL is incorrect.

Action

Revise the WSDL.

KDJW10013-E

Service is invalid. (service = aa....aa)

aa....aa: Invalid service name

Description

The service name is incorrect.

Action

Specify the correct service name.

KDJW10014-E

URL of WSDL is invalid. (URL = aa....aa)

aa....aa: Invalid URL of WSDL

Description

The URL of WSDL is incorrect.

Action

Revise the URL.

KDJW10015-E

Port is invalid. (invalid port = aa....aa, valid ports = bb....bb)

aa....aa: Invalid port name

bb....bb: Correct port name

Description

The port specification is incorrect.

Action

Revise the port settings.

KDJW10016-E

Service is invalid. (invalid service = aa....aa, valid services = bb....bb)

aa....aa: Invalid service name

bb....bb: Correct service name

Description

The service name is incorrect.

Action

An undefined service name might be specified in the service name of the Service class. Revise the service name.

KDJW10019-E

The method returned an unexpected value. (method = aa....aa, return value = bb....bb)

aa....aa: Method name

bb....bb: Return value

Description

The method returned an unexpected value.

Action

Revise the client application.

KDJW10020-E

Failed to create service.

Description

An exception occurred during the execution of API.

Action

Reference the message, output after this message, that describes the cause of failure, and then remove the cause.

KDJW10021-E

Failed to request service. (RootAP = aa....aa)

aa....aa: Root application information

Description

An exception occurred when invoking the service.

Action

Reference the message, output after this message, that describes the cause of failure, and then remove the cause.

KDJW10022-E

Exception occurred. (detail = aa....aa)

aa....aa: Detailed information

Description

An exception occurred during the execution of API.

Action

Check the detailed information, and then remove the causes of the error.

KDJW10023-E

The method was called with an invalid argument. (method = aa....aa, argument = bb....bb, value = cc....cc)

aa....aa: Method name

bb....bb: Class and name of the argument

cc....cc: Value of the argument

Description

The argument used when invoking a method is not correct.

Action

Revise the method argument.

KDJW10024-E

HTTP status code is invalid. (Status Code = aa....aa, Response Message= bb....bb)

aa....aa: Status code

bb....bb: Response message

Description

An invalid status code is returned during the service invocation.

Action

Check the status code, and then remove the causes of the error.

KDJW10025-W

The authentication information could not be established because a security exception occurred. (detail = aa....aa)

aa....aa: Detail

Description

The authentication information could not be established because a security exception occurred.

Action

Reference the detail, and then remove the cause.

KDJW10026-W

The directory specified by dir attribute of the @StreamingAttachment annotation or the StreamingAttachmentFeature class cannot be accessed. (directory = aa....aa)

aa....aa: Output destination directory name specified in the dir option

Description

The directory specified by the dir attribute of the @StreamingAttachment annotation or the StreamingAttachmentFeature class cannot be accessed.

Action

Check and, if necessary, revise the dir attribute value specification of the @StreamingAttachment annotation or the StreamingAttachmentFeature class.

KDJW10027-E

Failed to move the specified file. (file = aa....aa)

aa....aa: Path name of attached files or directories

Description

Failed in an attempt to move the specified file.

Action

Confirm that the specified file exists in the transition destination. If the file exists, specify a separate file name.

Also confirm that the parent directory of the specified file exists. If the parent directory does not exist, specify a file name for which a parent directory exists.

KDJW10028-E

javax.xml.ws.WebServiceFeature type cannot be specified. (service=aa....aa)

aa....aa: Service name

Description

The javax.xml.ws.WebServiceFeature type cannot be specified.

Action

Specify javax.xml.ws.WebServiceFeature in the method that acquires the port.

KDJW10029-I

The value cannot be set as wsa:Action of Addressing header.

Description

The value cannot be set in the wsa:Action element of the addressing header.

Action

Review, and if necessary revise, the value set up in wsam:Action or wsaw:Action, existing in the wsdl:output element and wsa:fault element.

10.4 Messages from KDJW20000 to KDJW29999

This section describes the messages from KDJW20000 to KDJW29999 and the corresponding actions.

KDJW20001-E

The class does not implement Provider. (class = aa....aa)

aa....aa: Class name

Description

Provider interface is not implemented.

Action

Implement the Provider interface.

KDJW20002-E

Not a primary WSDL. (path = aa....aa)

aa....aa: WSDL path

Description

The WSDL coding is incorrect.

Action

Check the WSDL coding.

KDJW20004-E

Cannot find dispatch method. (dispatchKey = aa....aa)

aa....aa: Service method name

Description

The method corresponding to the operation specified in the SOAP message is not found.

Action

Review the operation and the method.

KDJW20005-E

The class implements Provider<T> but its type parameter is incorrect. (class = aa....aa, type = bb....bb)

aa....aa: Implementation class name

bb....bb: Type parameter

Description

The type parameter of the class implementing the Provider<T> interface is not valid.

Action

Review the type parameter of the Provider<T> interface.

KDJW20006-E

Incorrect number of arguments for method. The method annotated @Resource annotation has only one argument of WebServiceContext class. (method = aa....aa)

aa....aa: Method name

Description

A method in which the @Resource annotation is specified must have only a single argument.

Action

Revise the number of arguments of the method in which the @Resource annotation is specified.

KDJW20007-E

Incorrect argument types for method. The method annotated @Resource annotation has only one argument of WebServiceContext class. (method = aa....aa)

aa....aa: Method name

Description

The argument type of the method is incorrect. When the @Resource annotation in which the WebServiceContext class is specified in the type attribute is specified in a method, the method argument must be set in the WebServiceContext class.

Action

Revise the argument type of the method in which the @Resource annotation is specified.

KDJW20008-E

Only one method should have the annotation. (annotation = aa....aa)

aa....aa: Annotation name

Description

An annotation that cannot be specified in more than one method is specified in more than one method.

Action

Revise the annotation. The @PostConstruct annotation or @PreDestroy annotation might be specified in more than one method.

KDJW20009-W

Non unique body parts. In a port, as per BP 1.1 R2710 operations must have unique operation signature on the wire for successful dispatch. (method = aa....aa, QName = bb....bb)

aa....aa: Method name

bb....bb: QName

Description

A method cannot be determined because more than one method corresponding to an operation exists.

Action

Revise the compliance between the operation and the method.

KDJW20010-W

Invalid annotation on service implementation class will be ignored. The class annotated with @WebService annotation MUST NOT be annotated with the following annotation. Put this annotation on the following service endpoint interface. (annotation = aa....aa, class = bb....bb, service endpoint interface = cc....cc)

aa....aa: Annotation name

bb....bb: Class name

cc....cc: Interface name

Description

The @SOAPBinding annotation specified in the Web service implementation class is ignored because the @SOAPBinding annotation is not specified in SEI.

Action

Revise the settings of the @SOAPBinding annotation.

KDJW20011-E

The class implements Provider<T> but does not specify the type parameter. (class = aa....aa)

aa....aa: Class name

Description

The type parameter is not specified in the class implementing the Provider<T> interface.

Action

Specify the type parameter of the Provider<T> interface.

KDJW20012-W

Ignoring wrong wsdl. It should start with the following path. Going to generate and publish a new WSDL. (WSDL = aa....aa, path = bb....bb)

aa....aa: WSDL

bb....bb: WSDL storage directory

Description

The WSDL path does not begin with WEB-INF/wsdl.

Action

Revise the WSDL path.

KDJW20013-E

The WSDL is not found in the WAR file. Package it in the WAR file or correct file path. (file = aa....aa)

aa....aa: File name

Description

The WSDL was not found.

Action

Revise the WSDL path.

KDJW20014-E

The class is not found in cosminexus-jaxws.xml. (class = aa....aa)

aa....aa: Non-existent class name

Description

A class specified in cosminexus-jaxws.xml does not exist.

Action

Specify the correct class name.

KDJW20015-E

Unsupported endpoint address. (URL= aa....aa)

aa....aa: Invalid URL

Description

An invalid URL is specified in the endpoint address.

Action

Specify the correct URL in the location attribute of the soap:address element in WSDL or in the javax.xml.ws.service.endpoint.address property of the message context.

KDJW20016-E

Exception occurred during WSDL parsing. (WSDL = aa....aa)

aa....aa: WSDL path

Description

An error occurred during the WSDL parsing.

Action

Code the WSDL correctly.

KDJW20017-E

Static resource cannot be injected to non-static field or method. (static resource = aa....aa, non-static field or method = bb....bb)

aa....aa: Interface name

bb....bb: Field or method name

Description

A static resource cannot be injected into a non-static field or method.

Action

Revise the arguments of the field and method. An error might occur in a field or method in which the @Resource annotation is specified.

KDJW20018-E

Method should not have any arguments. (method = aa....aa)

aa....aa: Method name

Description

A method cannot contain any arguments.

Action

Revise the method. The @PostConstract annotation or @PreDestroy annotation might be specified. The methods in which these annotations are specified cannot contain any arguments.

KDJW20019-E

Received SOAP message contains duplicate header for a bound parameter. (header = aa....aa)

aa....aa: Header name

Description

The received SOAP message contains a duplicate header.

Action

Revise the sent message.

KDJW20020-E

Unable to instantiate the class1 specified in the following annotation on the class2. (class1 = aa....aa, annotation = bb....bb, class2 = cc....cc)

aa....aa: Class name

bb....bb: Annotation name

cc....cc: Class name

Description

An instance of the class specified in the annotation could not be generated.

Action

Revise the annotation and class.

KDJW20021-E

Error occurred during parsing cosminexus-jaxws.xml. (detail = aa....aa)

aa....aa: Detailed message

Description

An error occurred while reading the cosminexus-jaxws.xml file.

Action

Check the detailed message, and then remove the causes of the error.

KDJW20022-E

Port namespace does not match service namespace. (port namespace = aa....aa, service namespace =bb....bb)

aa....aa: Namespace of the port

bb....bb: Namespace of the service

Description

The namespace of the port does not match the namespace of the service.

Action

Revise the namespace of the port and service.

KDJW20023-E

Could not get binding from WSDL. service or port not found in the WSDL. (service = aa....aa, port= bb....bb, WSDL = cc....cc)

aa....aa: Service name

bb....bb: Port name

cc....cc: URL of WSDL

Description

The binding cannot be acquired because the service name or port is not found from the WSDL.

Action

Make sure that the contents of the service name (wsdl:service element) specified in the WSDL, and the port (wsdl:port element) match the contents of the service name and port acquired from cosminexus-jaxws.xml and the @WebService annotation.

KDJW20025-E

XML stream error occurred during parsing WSDL. (detail = aa....aa, location= bb....bb)

aa....aa: Detailed message

bb....bb: Error location

Description

An exception occurred during WSDL parsing.

Action

Check the detailed message, and then remove the causes of the error.

KDJW20026-E

The class has neither @WebService annotation nor @WebServiceProvider annotation. (class = aa....aa)

aa....aa: Class name

Description

The WebService annotation or the WebServiceProvider annotation is not specified.

Action

Specify the WebService annotation or the WebServiceProvider annotation.

KDJW20027-E

The class has both @WebService annotation and @WebServiceProvider annotation. (class = aa....aa)

aa....aa: Class name

Description

Both the WebService and WebServiceProvider annotations are specified.

Action

Specify only the WebService annotation or the WebServiceProvider annotation.

KDJW20028-E

The class does not implement Provider interface. (class = aa....aa)

aa....aa: Class name

Description

Provider interface is not implemented.

Action

Implement the Provider interface.

KDJW20031-E

Invalid value for attribute of element in cosminexus-jaxws.xml. (line= aa....aa, element= bb....bb, attribute= cc....cc)

aa....aa: Line number

bb....bb: Element name

cc....cc: Attribute name

Description

The value of the attribute that is included in the cosminexus-jaxws.xml element is invalid.

Action

Code cosminexus-jaxws.xml correctly.

KDJW20036-E

SOAPFault occurred. (RootAP = aa....aa)

aa....aa: Root application information

Description

An exception occurred during the execution of the Web Services.

Action

Reference the message, output after this message, that describes the cause of failure, and then remove the cause.

KDJW20037-E

Exception occurred. (detail = aa....aa)

aa....aa: Detailed information

Description

An exception occurred during the execution of the Web Services.

Action

Check the detailed information, and then remove the causes of the error.

KDJW20039-E

The class is not found. (class = aa....aa)

aa....aa: Class name

Description

Class not found.

Action

Confirm that the class exists.

KDJW20040-E

The WSDL is not found in the EJB JAR file. Package it in the EJB JAR file or the correct file path. (file = aa....aa)

aa....aa: File name

Description

WSDL not found.

Action

Check and, if necessary, revise the WSDL path.

KDJW20041-E

The method annotated with javax.jws.Oneway annotation cannot have parameters using javax.xml.ws.Holder classes. (class = aa....aa, method = bb....bb)

aa....aa: SEI name or Service Implementation Class name

bb....bb: Method name

Description

The method annotated with the javax.jws.Oneway annotation cannot have parameters using the javax.xml.ws.Holder class.

Action

Specify only the in parameter in the method annotated with the javax.jws.Oneway annotation.

KDJW20042-E

The method annotated with javax.jws.Oneway annotation cannot throw exceptions except java.lang.RuntimeException, java.rmi.RemoteException and their subclasses. (class = aa....aa, method = bb....bb, exception class = cc....cc)

aa....aa: SEI name or Service Implementation Class name

bb....bb: Method name

cc....cc: Exception class name

Description

The method annotated with the javax.jws.Oneway annotation cannot throw exceptions except java.lang.RuntimeException and java.rmi.RemoteException, and their subclasses.

Action

Delete the exceptions except java.lang.RuntimeException and java.rmi.RemoteException, and their subclasses from the throw clause of the method that is annotated with the javax.jws.Oneway annotation.

10.5 Messages from KDJW30000 to KDJW39999

This section describes the messages from KDJW30000 to KDJW39999 and the corresponding actions.

KDJW30001-E

Fast Infoset decoding is not accepted.

Description

Decoding in Fast Infoset could not be executed.

Action

FastInfoset cannot be used. Revise the application.

KDJW30003-E

XML reader error occurred. (detail = aa....aa)

aa....aa: Detailed message

Description

An error occurred during XML parsing.

Action

Check the detailed message, and then remove the causes of the error.

KDJW30004-E

Unable to create StAX reader or writer.

Description

An attempt to generate a StAX reader or writer has failed.

Action

Check if the exception XMLReaderException is output in the exception log, and if output, remove the cause.

KDJW30005-E

XML reader found unexpected character content. (unexpected content = aa....aa)

aa....aa: Unexpected character string

Description

An unexpected character string is included in XML.

Action

Code the XML correctly.

KDJW30006-W

Import of specified WSDL is violation of BP 1.1 R2001. (WSDL = aa....aa)

aa....aa: URL of WSDL

Description

The coding of WSDL is incorrect.

Action

Revise the contents of WSDL. Use only the import coding of the WSDL because the DESCRIPTION includes the coding of another WSDL.

KDJW30011-I

http client message

Description

A request is sent by the Web service client.

KDJW30012-I

http client message

Description

A response is received by the Web service client.

KDJW30013-I

http server message

Description

A request is received at the Web service side.

KDJW30014-I

http server message

Description

A response is sent at the Web service side.

KDJW30017-E

The validation of the mapping information failed. (detail = aa....aa)

aa....aa: Detailed message

Description

An error occurred during the validation of the mapping information of the URL and Web service implementation class or the URL and provider implementation class.

Action

If cosminexus-jaxws.xml is coded, revise cosminexus-jaxws.xml, and code it correctly.

KDJW30018-E

PRF trace failed to be initialized. (detail = aa....aa)

aa....aa: Detailed message

Description

An error occurred in the initialization process of the PRF trace.

Action

Check the detailed message, and then remove the causes of the error.

KDJW30019-E

The validation of the handler chain file failed. (detail = aa....aa)

aa....aa: Detailed message

Description

An error occurred during the validation of the handler chain setup file.

Action

Check the detailed message, and then remove the causes of the error.

KDJW30020-E

SOAPAction HTTP header must be present to conform R2745 of WS-I BasicProfile 1.1.

Description

The SOAPAction HTTP header is not included in the received message. To conform R2745 of WS-I BasicProfile 1.1, the SOAPAction HTTP header must be included.

Action

Include the SOAPAction HTTP header in the message to be sent. Alternatively, revise the settings of the com.cosminexus.jaxws.fault_omit_soapaction property.

KDJW30021-E

The mapping from the service implementation class or the provider implementation class to URL failed.

Description

An attempt to map the URL and service implementation class or the URL and provider implementation class has failed.

Action

Check and, if necessary, revise that the WebService annotation or the WebServiceProvider annotation has been annotated in the service implementation class or the provider implementation class, and then code correctly.

If the annotation has been correctly annotated, confirm that the annotated annotation exists in the class path and that the annotation-reference suppression function is not enabled.

For details about the annotation-reference suppression function, see Annotation-reference suppression function in the uCosminexus Application Server Common Container Functionality Guide.

KDJW30022-W

The value of the SOAPAction HTTP header must be a quoted string to conform R1109 of WS-I BasicProfile 1.1.

Description

The SOAPAction value is not enclosed within quotation marks. The SOAPAction value must be enclosed within quotation marks in order to conform to R1109 of WS-I BasicProfile 1.1.

Action

Check the SOAPAction value in the request message.

KDJW30023-W

The XML is invalid against the schema(s) for catalog file. (file = aa....aa, detail= bb....bb)

aa....aa: Path of catalog file

bb....bb: Detail

Description

The syntx grammer for catelog file is invalid.

Action

Reference the detail, and if necessary revise the catalog file syntax to remove the cause of the error. If the error is because of the reading of the catalog file instead of syntax of the catalog file, check that the path and access permmission of the catalog file are correct.

KDJW30024-W

Failed to access the WSDL or schema was mapped in the catalog file. (uri = aa....aa, detail = bb....bb)

aa....aa: URI specified in the catalog file

bb....bb: Detail

Description

An attempt to access the WSDL or schema mapped with the catalog file has failed.

Action

Confirm the following for the URI that is specified in the uri attribute of the catalog file:

URI is correct

URI can be accessed

10.6 Messages from KDJW40000 to KDJW49999

This section describes the messages from KDJW40000 to KDJW49999 and the corresponding actions.

KDJW40001-I

Web Service(s) is/are being initialized.

Description

Initialization of the Web service will start.

KDJW40002-E

Web Service(s) failed to be initialized.

Description

A failure occurred in the initialization of the Web service.

Action

Reference the message, output after this message, that describes the cause of the initialization failure, and then remove the cause.

Note that when the Web Service is developed with SEI as the starting point, and an invalid annotation is included in the Web Service Implementation Class, an error might occur in the dynamic generation of the wrapper bean. For generating a wrapper bean, execute the hwsgen command, check the error in the Web Service Implementation Class, and remove the cause of the error.

KDJW40003-I

Web Service(s) was/were successfully initialized.

Description

The Web service is initialized successfully.

KDJW40004-I

Web Service(s) is/are being destroyed.

Description

The Web service will stop.

KDJW40006-I

Web Service(s) was/were successfully destroyed.

Description

The Web service has stopped.

KDJW40007-W

Duplicate endpoint name. (endpoint = aa....aa)

aa....aa: Endpoint name

Description

The end point name within cosminexus-jaxws.xml is duplicate.

Action

Revise the settings of the end point of cosminexus-jaxws.xml.

KDJW40009-W

Duplicate URL pattern in endpoint. (endpoint = aa....aa)

aa....aa: Endpoint name

Description

The URL within cosminexus-jaxws.xml is duplicate.

Action

Revise the settings of url-pattern of cosminexus-jaxws.xml.

KDJW40010-W

Unsupported implicit URL pattern in endpoint. (endpoint = aa....aa)

aa....aa: Endpoint name

Description

The coding of the URL pattern within cosminexus-jaxws.xml is not supported.

Action

Do not include *. in the URLpattern within cosminexus-jaxws.xml.

KDJW40011-E

Failed to instantiate service implementation class for port. (class = aa....aa)

aa....aa: Class name

Description

An attempt to instantiate the Web service implementation class has failed.

Action

Revise the class that failed to be instantiated.

KDJW40012-I

The web.xml was successfully generated.

Description

web.xml is generated successfully.

KDJW40013-E

Exception occurred. (detail = aa....aa)

aa....aa: Exception information

Description

An exception occurred when starting the Web service.

Action

Check the exception information, and then remove the causes of the error.

KDJW40014-E

Exception occurred. (detail = aa....aa)

aa....aa: Exception information

Description

An exception occurred when terminating the Web service.

Action

Check the exception information, and then remove the causes of the error.

KDJW40015-E

Web Service(s) failed to be destroyed.

Description

A problem occurred when terminating the Web service.

Action

Reference the message, output after this message, that describes the cause of the initialization failure, and then remove the cause.

KDJW40016-E

Failed to request service. (RootAP = aa....aa)

aa....aa: Root application information

Description

An attempt to execute the Web service has failed.

Action

Reference the message, output after this message, that describes the cause of the initialization failure, and then remove the cause.

KDJW40017-E

Exception occurred. (detail = aa....aa)

aa....aa: Exception information

Description

An exception occurred during the execution of the Web service.

Action

Check the exception information, and then remove the causes of the error.

KDJW40018-E

System property cosminexus.home is not specified.

Description

The system property cosminexus.home is not specified.

Action

Specify the system property cosminexus.home, and then re-execute the command.

KDJW40019-W

The property contains an invalid value. The default value will be used. (key = aa....aa, value = bb....bb, default = cc....cc)

aa....aa: Key name

bb....bb: Specified value

cc....cc: Applied default value

Description

The operation will be performed by using the default value because a value outside the range is specified.

Action

Revise the operation definition file.

KDJW40020-E

Logging Utility failed to be initialized. (detail = aa....aa)

aa....aa: Detailed information

Description

An attempt to initialize the log has failed.

Action

Check the detailed information, and then remove the causes of the error.

KDJW40021-W

Properties Utility failed to be initialized. (file = aa....aa, detail = bb....bb)

aa....aa: File name

bb....bb: Detailed information

Description

An attempt to initialize the operation definition file has failed. The operation will be performed by using the default value. The default value is used in the order of priority of the operation definition. For details about the priority of the operation definitions, see uCosminexus Application Server Web Service Development Guide.

Action

Check the detailed information, and then remove the causes of the error. If failure in reading the file is the cause of the error, make sure that the path of the operation definition file coded in the file name, and the access permission are correct.

KDJW40022-E

Logging Utility failed to be destroyed. (detail = aa....aa)

aa....aa: Detailed information

Description

An attempt to terminate the log has failed.

Action

Check the detailed information, and then remove the causes of the error.

KDJW40023-E

The web.xml failed to be generated. (detail = aa....aa)

aa....aa: Details

Description

An attempt to generate the web.xml file has failed.

Action

Revise the @WebService annotation, and then re-execute the process.

KDJW40026-I

The required information for generating web.xml was retrieved. (implementation class = aa....aa)

aa....aa: Class name

Description

Acquire the information required for generating web.xml.

KDJW40027-I

The property value was successfully retrieved. (key= aa....aa, value= bb....bb)

aa....aa: Property key

bb....bb: Contents set in the property

Description

The property has been set up.

KDJW40033-E

A @WebServiceRef annotation does not allowed on this element. (element=aa....aa)

aa....aa: Element name

Description

A WebServiceRef annotation is not permitted for the specified element.

Action

Check that the WebServiceRef annotation is allowed for the class, field, or method.

KDJW40035-E

The method annotated @WebServiceRef annotation requires a void return type.

Description

The method annotated with the WebServiceRef annotation must have a void return value.

Action

Check that the method annotated with the WebServiceRef annotation has a void type return value.

KDJW40037-E

Illegal use of static field on class that only supports instance-based injection. (field=aa....aa)

aa....aa: Field name

Description

An object cannot be inserted in the static field of class that only supports instance-based injection.

Action

Check that the field specifying the WebServiceRef annotation is not a static declared field.

KDJW40039-E

Illegal use of static method on class that only supports instance-based injection. (method=aa....aa)

aa....aa: Method name

Description

An object cannot be inserted in the static method of the class that only supports instance-based injection.

Action

Check that the method specifying the WebServiceRef annotation is not a static declared method.

KDJW40041-I

Injecting dependency into the field on class. (field=aa....aa, class=bb....bb)

aa....aa: Method name

bb....bb: Class name

Description

Insert an object in the field.

KDJW40042-I

Injecting dependency into the method on class. (method=aa....aa, class=bb....bb)

aa....aa: Method name

bb....bb: Class name

Description

Insert an object in the field.

KDJW40043-E

Exception occurred during injecting dependency. (object=aa....aa, class=bb....bb, detail=cc....cc)

aa....aa: Object name

bb....bb: Class name

cc....cc: Detail

Description

An exception occurred while inserting the object.

Action

Reference the detail, and remove the cause.

KDJW40044-E

Service class must be annotated with a @WebServiceClient annotation.

Description

The service class must be annotated with WebServiceClient annotation.

Action

Specify that the WebServiceRef annotation is a service class or in a port. Take an action as follows:

When specifying the WebServiceRef annotation in a service class

When the value element is specified in the WebServiceRef annotation, delete the value element.

When the WebServiceClient annotation is not specified in the class declaration of the service class that has the specified the WebServiceRef annotation, specify the service class that is specified with the specified WebServiceClient annotation.

When specifying the WebServiceRef annotation in a port

When the value element is not specified in the WebServiceRef annotation, specify a service class in the value element.

When the WebServiceClient annotation is not specified in the class declaration of the service class that is specified in the value element, specify a service class that is specified with the WebServiceClient annotation.

KDJW49999-W

A warning occurred in processing Web Services. (detail = aa....aa)

aa....aa: Detailed message

Description

A warning occurred during service execution.

Action

Reference the detailed message and determine the cause.

10.7 Messages from KDJW50000 to KDJW59999

This section describes the messages from KDJW50000 to KDJW59999 and the corresponding actions.

KDJW50001-I

cjwsimport started.

Description

The cjwsimport command has started.

KDJW50002-I

cjwsimport successfully ended.

Description

The cjwsimport command terminated normally.

KDJW50003-E

cjwsimport unsuccessfully ended.

Description

The cjwsimport command terminated abnormally.

Action

Remove the cause of the error, and then re-execute the command.

KDJW50004-I

The generating of Java source started.

Description

A Java source will be generated.

KDJW50005-E

The generating of Java source has failed.

Description

An attempt to generate the Java source has failed.

Action

Remove the cause of the error, and then re-execute the command.

KDJW50006-I

The compiling of generated Java source started.

Description

The generated Java source will be compiled.

KDJW50007-E

The compiling of generated Java source has failed.

Description

An attempt to compile the generated Java source has failed.

Action

Remove the cause of the error, and then re-execute the command.

KDJW51001-E

The specified option is invalid. (option = aa....aa)

aa....aa: Invalid option

Description

An invalid option was specified.

Action

Specify a correct option.

KDJW51002-E

The protocol besides http,urn cannot be specified for the namespace of WSDL. (WSDL file = aa....aa, line = bb....bb, targetNamespace = cc....cc)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: Value of the targetNamespace attribute

Description

A protocol other than http:// or urn: cannot be specified in the namespace of WSDL.

Action

Specify a URL beginning with http:// or urn: in the namespace of WSDL.

KDJW51003-E

The relative path cannot be specified for the namespace of WSDL. (WSDL file = aa....aa, line = bb....bb, targetNamespace = cc....cc)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: Value of the targetNamespace attribute

Description

A relative path cannot be specified in the namespace of WSDL.

Action

Specify a URL beginning with http:// or urn: in the namespace of WSDL.

KDJW51004-E

The form of the targetNamespace of WSDL is invalid. (WSDL file = aa....aa, line = bb....bb, targetNamespace = cc....cc)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: Value of the targetNamespace attribute

Description

The coding format of the namespace of WSDL is invalid.

Action

Code the namespace of WSDL in the correct format. You cannot code the following character strings and formats:

Blank characters

Query strings

Anchors

Port numbers

User name or password

KDJW51007-E

The keyword reserved for Java language cannot be used for the name attribute of wsdl:operation element in WSDL. (WSDL file = aa....aa, line = bb....bb, operation name = cc....cc)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:operation element name

Description

Java reserved terminology cannot be used in the wsdl:operation element name of WSDL.

Action

Do not use Java reserved terminology in the wsdl:operation element name of WSDL.

KDJW51008-E

The number of wsdl:portType elements is invalid. (WSDL file = aa....aa)

aa....aa: WSDL file path

Description

The number of wsdl:portType elements of WSDL is invalid.

Action

Specify 1 to 255 wsdl:portType elements of WSDL.

KDJW51009-W

The namespace attribute cannot be specified in soap:header element in WSDL. (WSDL file = aa....aa, line = bb....bb)

aa....aa: WSDL file path

aa....aa: Line number

Description

The namespace attribute cannot be specified in the soap:header element.

Action

Do not specify the namespace attribute in the soap:header element.

KDJW51016-E

The number of arguments of Java method is invalid when the mapping is done from WSDL to Java source. (WSDL file = aa....aa, operation name = bb....bb)

aa....aa: WSDL file path

bb....bb: wsdl:operation element name

Description

The number of arguments of a method after performing mapping from WSDL to Java is invalid.

Action

Specify a value within 254 as the number of arguments of the method after performing mapping from WSDL to Java.

KDJW51017-E

The keyword reserved for Java language cannot be used for the name attribute of wsdl:part element in WSDL. (WSDL file = aa....aa, line = bb....bb, part name = cc....cc)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:part element name

Description

Java reserved terminology cannot be used in the wsdl:part element name of WSDL.

Action

Do not use Java reserved terminology in the wsdl:part element name of WSDL.

KDJW51018-E

The keyword reserved for Java language cannot be used for the wrapper child element in WSDL. (WSDL file = aa....aa, line = bb....bb, wrapper child element name = cc....cc)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wrapper child element name

Description

Java reserved terminology cannot be used in the wrapper child element name of WSDL.

Action

Do not use Java reserved terminology in the wrapper child element name of WSDL.

KDJW51019-E

The number of wsdl:part child elements of input wsdl:message element referred from soap:body element is invalid. (WSDL file = aa....aa, message name = bb....bb)

aa....aa: WSDL file path

bb....bb: Input wsdl:message element name

Description

The number of wsdl:part child elements of the input message referenced from the soap:body element of the wsdl:operation element of WSDL is invalid.

Action

Specify only a single wsdl:part child element in the input message referenced from the soap:body element of the wsdl:operation element of WSDL.

KDJW51020-E

The number of wsdl:part child elements of output wsdl:message element referred from wsdl:operation element is invalid. (WSDL file = aa....aa, message name = bb....bb)

aa....aa: WSDL file path

bb....bb: Output wsdl:message element name

Description

The number of wsdl:part child elements of the output message referenced from the wsdl:operation element of WSDL is invalid.

Action

Specify only a single wsdl:part child element in the output message referenced from the wsdl:operation element of WSDL.

KDJW51021-E

The wsdl:part element specified for the parts attribute is not found. (WSDL file = aa....aa, line = bb....bb, parts = cc....cc, message name = dd....dd)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: Value of the parts attribute

dd....dd: wsdl:message element name

Description

The wsdl:part element specified in the parts attribute is not found.

Action

In the parts attribute of the soap:header element, specify the wsdl:part element declared under the wsdl:message element that is specified in the message attribute.

KDJW51022-E

The wsdl:part element specified for the part attribute is not found in the child element of the wsdl:message element. (WSDL file = aa....aa, line = bb....bb, part = cc....cc, operation name = dd....dd)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: Value of the parts attribute

dd....dd: wsdl:operation element name

Description

The wsdl:part element specified in the part attribute is not found in the child element of the wsdl:message element.

Action

Specify the element for binding in the soap:body element from the multiple wsdl:part child elements of the wsdl:message element that is referenced by the parent wsdl:input element or the wsdl:output element.

KDJW51025-E

The number of wsdl:part child elements of fault wsdl:message element referred from wsdl:fault element is invalid. (WSDL file = aa....aa, message name = bb....bb)

aa....aa: WSDL file path

bb....bb: Fault wsdl:message element name

Description

The number of wsdl:part child elements of the message referenced from the wsdl:fault element is invalid.

Action

Specify only a single wsdl:part child element of the wsdl:message element referenced from the wsdl:fault element.

KDJW51026-E

wsdl:fault elements specified as child elements of one wsdl:operation element must refer to unique wsdl:message elements. (WSDL file = aa....aa, operation name = bb....bb, fault name = cc....cc)

aa....aa: Path of the WSDL file

bb....bb: wsdl:operation element name

cc....cc: wsdl:fault element name

Description

More than one wsdl:fault elements are specified in the child element of a single wsdl:operation element, but the wsdl:message element referenced from these elements is not unique.

Action

When more than one wsdl:fault elements are specified in the child element of a single wsdl:operation element, the wsdl:message element referenced from these elements must be unique.

KDJW51027-W

The name attribute of the soap:fault element does not correspond to the name attribute of the wsdl:fault element in the wsdl:operation element. (WSDL file = aa....aa, soap:fault name = bb....bb, wsdl:fault name = cc....cc, wsdl:operation name = dd....dd)

aa....aa: WSDL file path

bb....bb: soap:fault element name

cc....cc: wsdl:fault element name

dd....dd: wsdl:operation element name

Description

The soap:fault element name does not match the wsdl:fault element name of the wsdl:operation element.

Action

Match the soap:fault element name, and then the wsdl:fault element name.

KDJW51029-E

The XML is invalid against the schema(s) for WSDL, XML schema, SOAP Binding and/or JAX-WS binding declarations. See detail message, check the elements and the attributes that belong in the namespaces of these and resolve the problem(s). (file = aa....aa, detail = bb....bb)

aa....aa: WSDL file path

bb....bb: Detailed message (JAXB message)

Description

The syntax of WSDL or XML Schema is grammatically invalid.

Action

Reference the detailed message, and revise the syntax of WSDL or XML Schema.

KDJW51030-E

The class or SEI name must be unique and must not collide with the others when the mapping is done from WSDL to Java source. (WSDL file = aa....aa, class = bb....bb)

aa....aa: WSDL file path

bb....bb: Collided name

Description

When mapping from WSDL to Java, the SEI or class name is overlapping.

Action

Revise the wsdl:portType element name and wsdl:service element name of WSDL such that the SEI or class names are unique.

KDJW51034-E

The jaxws:bindings child element cannot be specified in the jaxws:bindings element, in the embedded binding declarations . (WSDL file = aa....aa, line = bb....bb)

aa....aa: WSDL file path

bb....bb: Line number

Description

The jaxws:bindings element cannot be coded as the child element of the jaxws:bindings element in the embedded binding declarations.

Action

Do not code the jaxws:bindings element as the child element of the jaxws:bindings element in the embedded binding declarations.

KDJW51038-E

The form of the node attribute of jaxws:bindings element is invalid in the external binding file. (external binding file = aa....aa, node = bb....bb)

aa....aa: External binding file name

bb....bb: Value of the node attribute

Description

The coding format of the node attribute of the jaxws:bindings element is invalid in the external binding declaration.

Action

Revise the coding format of the node attribute of the jaxws:bindings element in the external binding declaration.

KDJW51039-E

JAXWS version attribute must be "2.0". (external binding file = aa....aa, version = bb....bb)

aa....aa: External binding file name

bb....bb: Value of the version attribute

Description

The specified value of the version attribute of jaxws:bindings element of the root in the external binding declaration is invalid.

Action

Specify 2.0 in the version attribute of jaxws:bindings element of the root in the external binding declaration.

KDJW51040-E

The element cannot be specified as child element of jaxws:bindings element. (customized WSDL element = aa....aa, element = bb....bb)

aa....aa: WSDL element to be customized

bb....bb: Invalid element name

Description

This element cannot be specified as the child element of the jaxws:bindings element.

Action

Specify an element that can be specified as the child element of the jaxws:bindings element.

KDJW51043-E

The form of the wsdlLocation attribute of jaxws:bindings element is invalid in the external binding file or specified WSDL file to be customized is not exist. (external binding file = aa....aa, pointed WSDL file = bb....bb)

aa....aa: External binding file name

bb....bb: Value of the wsdlLocation attribute

Description

Either the coding format of the wsdlLocation attribute of the jaxws:bindings element in the external binding declaration is erroneous or the file does not exist.

Action

Make sure that the coding format of the wsdlLocation attribute of the jaxws:bindings element in the external binding declaration is not erroneous. Also, make sure that the specified file exists.

KDJW51049-E

The number of wsdl:types child elements of wsdl:definitions element is invalid. (WSDL file = aa....aa)

aa....aa : WSDL file path

Description

The number of wsdl:types elements specified as child elements of wsdl:definitions is invalid.

Action

Specify only a single wsdl:types element as the child element of wsdl:definitions.

KDJW51050-E

The number of wsdl:message child elements of wsdl:definitions element is invalid. (WSDL file = aa....aa)

aa....aa: WSDL file path

Description

The number of wsdl:message elements specified as child elements of wsdl:definitions is invalid.

Action

Specify only a single wsdl:message element as the child element of wsdl:definitions.

KDJW51051-E

The number of soap:fault child elements of wsdl:fault element is invalid. (WSDL file = aa....aa)

aa....aa: WSDL file path

Description

The number of soap:fault elements specified as child elements of wsdl:fault is invalid.

Action

Specify only a single soap:fault element as the child element of wsdl:fault.

KDJW51052-E

The number of wsdl:import child elements of wsdl:definitions element is invalid. (WSDL file = aa....aa)

aa....aa: WSDL file path

Description

The number of wsdl:import elements specified as child elements of wsdl:definitions is invalid.

Action

Specify 0 to 255 wsdl:import elements as child elements of wsdl:definitions.

KDJW51053-E

The element cannot be specified as child element of wsdl:definitions element. (WSDL file = aa....aa, line = bb....bb, element = cc....cc)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: Invalid element name

Description

This element cannot be specified as the child element of wsdl:definitions.

Action

Specify an element that can be specified as a child element of wsdl:definitions.

KDJW51054-E

The element cannot be specified as child element of wsdl:import element. (WSDL file = aa....aa, line = bb....bb, element = cc....cc)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: Invalid element name

Description

This element cannot be specified as the child element of wsdl:import.

Action

Specify an element that can be specified as a child element of wsdl:import.

KDJW51055-E

The element cannot be specified as child element of wsdl:message element. (WSDL file = aa....aa, line = bb....bb, message name = cc....cc, element = dd....dd)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:message element name

dd....dd: Invalid element name

Description

This element cannot be specified as the child element of wsdl:message.

Action

Specify an element that can be specified as a child element of wsdl:message.

KDJW51056-E

The element cannot be specified as child element of wsdl:part element. (WSDL file = aa....aa, line = bb....bb, message name = cc....cc, part name = dd....dd, element = ee....ee)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:message element

dd....dd: wsdl:part element name

ee....ee: Invalid element name

Description

This element cannot be specified as the child element of wsdl:part.

Action

Specify an element that can be specified as a child element of wsdl:part.

KDJW51057-E

The element cannot be specified as child element of wsdl:input grandchild element of wsdl:portType element. (WSDL file = aa....aa, line = bb....bb, portType name = cc....cc, operation name = dd....dd, element = ee....ee)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:portType element name

dd....dd: wsdl:operation element name

ee....ee: Invalid element name

Description

This element cannot be specified as the child element of wsdl:input that itself is a grandchild element of wsdl:portType.

Action

Specify an element that can be specified as the child element of wsdl:input that itself is a grandchild element of wsdl:portType.

KDJW51058-E

The element cannot be specified as child element of wsdl:output grandchild element of wsdl:portType element. (WSDL file = aa....aa, line = bb....bb, portType name = cc....cc, operation name = dd....dd, element = ee....ee)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:portType element name

dd....dd: wsdl:operation element name

ee....ee: Invalid element name

Description

This element cannot be specified as the child element of wsdl:output that itself is a grandchild element of wsdl:portType.

Action

Specify an element that can be specified as the child element of wsdl:output that itself is a grandchild element of wsdl:portType.

KDJW51059-E

The element cannot be specified as child element of wsdl:types element. (WSDL file = aa....aa, line = bb....bb, element = cc....cc)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: Invalid element name

Description

This element cannot be specified as the child element of wsdl:types.

Action

Specify an element that can be specified as the child element of wsdl:types.

KDJW51074-E

The element cannot be specified as child element of wsdl:portType element. (WSDL file = aa....aa, line = bb....bb, portType name = cc....cc, element = dd....dd)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:portType element name

dd....dd: Invalid element name

Description

This element cannot be specified as the child element of wsdl:portType.

Action

Specify an element that can be specified as the child element of wsdl:portType.

KDJW51080-E

The element cannot be specified as child element of wsdl:operation element. (WSDL file = aa....aa, line = bb....bb, portType name = cc....cc, operation name = dd....dd, element = ee....ee)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:portType element name

dd....dd: wsdl:operation element name

ee....ee: Invalid element name

Description

This element cannot be specified as the child element of wsdl:operation.

Action

Specify an element that can be specified as the child element of wsdl:operation.

KDJW51083-E

The name of wsdl:operation child element of wsdl:portType element must be unique and must not collide with the others. (WSDL file = aa....aa, operation name = bb....bb)

aa....aa: WSDL file path

bb....bb: wsdl:operation element name

Description

The name of the wsdl:operation child element of the wsdl:portType element is duplicate.

Action

Revise the name of the wsdl:operation child element of the wsdl:portType element such that it is unique.

KDJW51096-E

The element cannot be specified as child element of wsdl:fault element. (WSDL file = aa....aa, line = bb....bb, portType name = cc....cc, operation name = dd....dd, fault name = ee....ee, element = ff....ff)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:portType element name

dd....dd: wsdl:operation element name

ee....ee: wsdl:fault element name

ff....ff: Invalid element name

Description

This element cannot be specified as the child element of wsdl:fault.

Action

Specify an element that can be specified as the child element of wsdl:fault.

KDJW51100-E

The number of wsdl:binding child elements of wsdl:definitions element is invalid. (WSDL file = aa....aa)

aa....aa: WSDL file path

Description

The number of wsdl:binding elements specified as child elements of wsdl:definitions is invalid.

Action

Specify 1 to 255 wsdl:binding elements as child elements of wsdl:definitions.

KDJW51102-E

The element cannot be specified as child element of wsdl:binding element. (WSDL file = aa....aa, line = bb....bb, binding name = cc....cc, element = dd....dd)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:binding element name

dd....dd: Invalid element name

Description

This element cannot be specified as the child element of wsdl:binding.

Action

Specify an element that can be specified as the child element of wsdl:binding.

KDJW51108-E

The element cannot be specified as child element of wsdl:operation child element of wsdl:binding element. (WSDL file = aa....aa, line = bb....bb, binding name = cc....cc, operation name = dd....dd, element = ee....ee)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:binding element name

dd....dd: wsdl:operation element name

ee....ee: Invalid element name

Description

This element cannot be specified as the child element of wsdl:operation that itself is a child element of wsdl:binding.

Action

Specify an element that can be specified as the child element of wsdl:operation that itself is a child element of wsdl:binding.

KDJW51112-E

The wsdl:operation child element of wsdl:portType element corresponding to the wsdl:operation child element of wsdl:binding element cannot be found. (WSDL name = aa....aa, line = bb....bb, binding name = cc....cc, operation name = dd....dd)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:binding element name

dd....dd: wsdl:operation element name

Description

A wsdl:operation child element of the wsdl:portType element corresponding to the wsdl:operation child element of the wsdl:binding element cannot be found.

Action

Define a wsdl:operation child element of the wsdl:portType element that corresponds to the wsdl:operation child element of the wsdl:binding element.

KDJW51114-E

The element cannot be specified as child element of wsdl:input grandchild element of wsdl:binding element. (WSDL file = aa....aa, line = bb....bb, binding name = cc....cc, operation name = dd....dd, element = ee....ee)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:binding element name

dd....dd: wsdl:operation element name

ee....ee: Invalid element name

Description

This element cannot be specified as the child element of wsdl:input that itself is a grandchild element of wsdl:binding.

Action

Specify an element that can be specified as the child element of wsdl:input that itself is a grandchild element of wsdl:binding.

KDJW51119-E

The element cannot be specified as child element of wsdl:output grandchild element of wsdl:binding element. (WSDL file = aa....aa, line = bb....bb, binding name = cc....cc, operation name = dd....dd, element = ee....ee)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:binding element name

dd....dd: wsdl:operation element name

ee....ee: Invalid element name

Description

This element cannot be specified as the child element of wsdl:output that itself is a grandchild element of wsdl:binding.

Action

Specify an element that can be specified as the child element of wsdl:output that itself is a grandchild element of wsdl:binding.

KDJW51123-E

The element cannot be specified as child element of wsdl:fault grandchild element of wsdl:binding element. (WSDL file = aa....aa, line = bb....bb, binding name = cc....cc, operation name = dd....dd, fault name = ee....ee, element = ff....ff)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:binding element name

dd....dd: wsdl:operation element name

ee....ee: wsdl:fault element name

ff....ff: Invalid element name

Description

This element cannot be specified as the child element of wsdl:fault that itself is a grandchild element of wsdl:binding.

Action

Specify an element that can be specified as the child element of wsdl:fault that itself is a grandchild element of wsdl:binding.

KDJW51127-E

The number of wsdl:service child elements of wsdl:definitions element is invalid. (WSDL file = aa....aa)

aa....aa: WSDL file path

Description

The number of wsdl:service elements specified as child elements of wsdl:definitions is invalid.

Action

Specify 1 to 255 wsdl:service elements as child elements of wsdl:definitions.

KDJW51129-E

The element cannot be specified as child element of wsdl:service child element of wsdl:definitions element. (WSDL file = aa....aa, line = bb....bb, service name = cc....cc, element = dd....dd)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:service element name

dd....dd: Invalid element name

Description

This element cannot be specified as the child element of the wsdl:service element that itself is the child element of wsdl:definitions.

Action

Specify an element that can be specified as the child element of the wsdl:service element that itself is the child element of wsdl:definitions.

KDJW51135-E

The element cannot be specified as child element of wsdl:port child element of wsdl:service element. (WSDL file = aa....aa, line = bb....bb, service name = cc....cc, port name = dd....dd, element = ee....ee)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:service element name

dd....dd: wsdl:port element name

ee....ee: Invalid element name

Description

This element cannot be specified as the child element of the wsdl:port element that itself is the child element of wsdl:service.

Action

Specify an element that can be specified as the child element of the wsdl:port element that itself is the child element of wsdl:service.

KDJW51143-E

The number of soap:binding child element of wsdl:binding element is invalid. (WSDL file = aa....aa)

aa....aa: WSDL file path

Description

The number of soap:binding elements specified as child elements of the wsdl:binding element is invalid.

Action

Specify only a single soap:binding element as the child element of the wsdl:binding element.

KDJW51147-E

The value of transport attribute of soap:binding element is invalid. (WSDL file = aa....aa, line = bb....bb, transport = cc....cc)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: Value of the transport attribute

Description

The value specified in the transport attribute of the soap:binding element specified as the child element of the wsdl:binding element is invalid.

Action

Specify http://schemas.xmlsoap.org/soap/http in the transport attribute of the soap:binding element specified as the child element of the wsdl:binding element.

KDJW51150-E

The number of soap:operation child elements of wsdl:operation element is invalid. (WSDL file = aa....aa, binding name = bb....bb, operation name = cc....cc)

aa....aa: WSDL file path

bb....bb: wsdl:binding element name

cc....cc: wsdl:operation element name

Description

The number of soap:operation elements specified as child elements of the wsdl:operation element is invalid.

Action

Specify only a single soap:operation element as the child element of the wsdl:operation element.

KDJW51156-E

The number of soap:body child elements of wsdl:input or wsdl:output element is invalid. (WSDL file = aa....aa, binding name = bb....bb, operation name = cc....cc)

aa....aa: WSDL file path

bb....bb: wsdl:binding element name

cc....cc: wsdl:operation element name

Description

The number of soap:body elements specified as child elements of the wsdl:input element or wsdl:output element is invalid.

Action

Specify only a single soap:body element as the child element of the wsdl:input element or wsdl:output element.

KDJW51175-E

The number of soap:address elements is invalid. (WSDL file = aa....aa)

aa....aa: WSDL file path

Description

The number of soap:address elements specified as child elements of the wsdl:port element is invalid.

Action

Specify only a single soap:address element as the child element of the wsdl:port element.

KDJW51179-E

The parts attribute must be specified when soap:header element is specified. (WSDL file = aa....aa, line = bb....bb)

aa....aa: WSDL file path

bb....bb: Line number

Description

The soap:header element is coded, but the parts attribute of the soap:body element is not specified.

Action

If the soap:header element is coded, specify the parts attribute of the soap:body element.

KDJW51180-E

WSDL is not found. (WSDL = aa....aa, detail = bb....bb)

aa....aa: WSDL file path

bb....bb: Detailed message

Description

The specified WSDL file is not found when the cjwsimport command is executed.

Action

Take one of the following actions:

When specifying the WSDL file using a file path, specify the correct path. Check whether the path of the WSDL file is incorrect. See the details to remove the cause of the error.

Check whether Web service initialization terminated normally. While deploying a Web service, if KDJW40003-I is output to the J2EE server console or the operation log of the JAX-WS functionality, the initialization terminated normally.

If EJB is used as the Web service, check whether EJB is being used in the range supported by the WSEE (JSR-109) specifications. If an unsupported Enterprise Bean is used as the Web service, the javax.jws.WebService annotation is ignored during deployment.

KDJW51181-E

Output directory is not found. (directory = aa....aa)

aa....aa: Output destination directory name specified by the -d or -s option

Description

The output destination directory specified by the cjwsimport command is not found.

Action

Make sure that the output destination directory specified by the option exists.

KDJW51182-E

The value specified by -d or -s option is not a directory. (value = aa....aa)

aa....aa: Output destination directory name specified by the -d or -s option

Description

The output destination specified by the cjwsimport command is not a directory.

Action

Make sure that a file is not specified by mistake in the output destination directory specified by the option.

KDJW51184-E

The external binding file specified by -b option is not found. (external binding file = aa....aa)

aa....aa: External binding file name specified by the -b option

Description

The external binding file specified by the cjwsimport command is not found.

Action

Make sure that the external binding file specified by the option exists.

KDJW51185-E

The value specified by -b option is not a file. (value = aa....aa)

aa....aa: Value specified by the -b option

Description

The external binding file specified by the cjwsimport command is a directory.

Action

Make sure that a directory is not specified by mistake in the external binding file specified by the option.

KDJW51187-E

The element specified for the node attribute of jaxws:bindings element that should be customized is not found in case of using external binding file. (external binding file = aa....aa, node = bb....bb)

aa....aa: External binding file name

bb....bb: Value of the node attribute

Description

When customizing with the external binding file, the element to be customized that is specified in the node attribute of the jaxws:bindings element is not found.

Action

Make sure that the XPath expression specified in the node attribute is not invalid. Alternatively, when the WSDL document read in the wsdl:import element is to be customized, make sure that the WSDL document at the wsdl:import source is not specified by mistake.

KDJW51188-E

Unsupported binding element is specified. (file = aa....aa, line = bb....bb, element = cc....cc)

aa....aa: WSDL file name or external binding file name

bb....bb: Line number

cc....cc: Unsupported binding element name

Description

This is an unsupported binding element.

Action

Do not use an unsupported binding element.

KDJW51189-E

WSDL is not found. (WSDL = aa....aa)

aa....aa: WSDL path

Description

The specified WSDL is not found during the execution of the cjwsimport command.

Action

When specifying a WSDL, specify the correct path. Make sure that the path of the WSDL file is not incorrect.

KDJW51190-E

The WSDL file specified for argument does not correspond to the WSDL to be customized in the external binding file. (external binding file = aa....aa, pointed WSDL file = bb....bb)

aa....aa: External binding file name

bb....bb: WSDL file path

Description

The WSDL file specified in the argument of the cjwsimport command and the WSDL file specified in the wsdlLocation attribute of the external binding file are not the same.

Action

Specify the same file name for the WSDL file specified in the argument of the cjwsimport command and the WSDL file specified in the wsdlLocation attribute of the external binding file.

KDJW51191-W

The value of namespace attribute of wsdl:import element in WSDL does not correspond to the value of targetNamespace attribute of wsdl:definitions element in WSDL. (WSDL file = aa....aa, namespace = bb....bb, targetNamespace = cc....cc)

aa....aa: Path of the import-source WSDL file

bb....bb: Namespace name of the import source

cc....cc: Target namespace name of the import destination

Description

The namespace of the namespace attribute of import-source wsdl:import element does not correspond to that of the targetNamespace attribute of import-destination wsdl:definitions element.

Action

Specify the same namespace in the namespace attribute of import-source wsdl:import element and the targetNamespace attribute of import-destination wsdl:definitions element.

KDJW51192-W

The value of targetNamespace attribute of wsdl:definitions element in WSDL and the value of targetNamespace attribute of wsdl:definitions element in imported WSDL are the same. (WSDL file = aa....aa, targetNamespace = bb....bb, imported targetNamespace = cc....cc)

aa....aa: Path of the import-source WSDL file

bb....bb: Target namespace name of the import source

cc....cc: Target namespace name of the import destination

Description

The namespace of the targetNamespace attribute of import-source wsdl:definitions element and the namespace of the targetNamespace attribute of import-destination wsdl:definitions element are the same.

Action

Specify a different namespace value in the targetNamespace attribute of import-source wsdl:definitions element and the targetNamespace attribute of import-destination wsdl:definitions element.

KDJW51197-E

WSDL specified in location attribute of wsdl:import element cannot be found. (WSDL file = aa....aa, line = bb....bb, location = cc....cc, detail = dd....dd)

aa....aa: Path of the import-source WSDL file

bb....bb: Line number

cc....cc: Value of the location attribute

dd....dd: Detailed message

Description

The WSDL specified in the location attribute of the wsdl:import element is not found.

Action

Make sure that the value specified in the location attribute of the wsdl:import element is correct. Check the detailed message, and then remove the causes of the error.

KDJW51198-E

WSDL specified in location attribute of wsdl:import element cannot be found. (WSDL file = aa....aa, line = bb....bb, location = cc....cc)

aa....aa: Path of the import-source WSDL file

bb....bb: Line number

cc....cc: Value of the location attribute

Description

The WSDL specified in the location attribute of the wsdl:import element is not found.

Action

Make sure that the value specified in the location attribute of the wsdl:import element is correct.

KDJW51199-E

The URL specified in location attribute of wsdl:import element is invalid. (WSDL file = aa....aa, line = bb....bb, location = cc....cc)

aa....aa: Path of the import-source WSDL file

bb....bb: Line number

cc....cc: Value of the location attribute

Description

The URL of the WSDL specified in the location attribute of the wsdl:import element is invalid.

Action

When specifying a remote WSDL file with a URL, specify the correct URL. Make sure that the URL of the WSDL file is not invalid.

KDJW51200-E

The root element in the file specified as WSDL is not wsdl:definitions element. (file = aa....aa, line = bb....bb)

aa....aa: Path of the specified file

bb....bb: Line number

Description

The file specified as WSDL is not a WSDL file with the root element as wsdl:definitions.

Action

Specify a WSDL file with the root element as the wsdl:definitions element.

KDJW51203-W

The skeleton class already exists in output directory. (skeleton class = aa....aa)

aa....aa: Skeleton class name

Description

A skeleton class with the same name already exists. The processing will continue without the generation of a skeleton class.

Action

To create a new skeleton class, either delete the skeleton class with the same name or assign a different name to the skeleton class.

KDJW51205-E

The local name of global elements referred from soap:header elements must be unique and must not collide with the others. (WSDL file = aa....aa, global element = bb....bb)

aa....aa: WSDL file path

bb....bb: Overlapping global element name

Description

The local name of global elements referenced from multiple soap:header messages is overlapping.

Action

If multiple soap:header elements are coded, the local name of all the global elements referenced from the message corresponding to each soap:header element must be unique.

KDJW51206-W

The SEI(s) is/ are not generated for the wsdl:port element(s) in which the jaxws:provider element(s) is/ are specified. (port name(s) = aa....aa)

aa....aa: Port name list

Description

If the jaxws:provider element is specified in the wsdl:port element, SEI will be generated.

Action

Take any of the following actions to create SEI:

Delete the jaxws:provider binding declaration

Specify false in boolean value

KDJW51207-W

The skeleton class(s) is/ are not generated for the wsdl:port element(s) in which the jaxws:provider element(s) is/ are specified. (port name(s) = aa....aa)

aa....aa: Port name list

Description

If the jaxws:provider element is specified in the wsdl:port element, the skeleton class will not be generated.

Action

Create a service implementation class implementing the javax.xml.ws.Provider interface. Take any of the following actions to generate a skeleton class:

Delete the jaxws:provider binding declaration

Specify false in boolean value

KDJW51208-E

R2716 of WS-I Basic Profile 1.1 does not allow namespace attribute in the element. (WSDL file = aa....aa, line = bb....bb, element = cc....cc, operation = dd....dd)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: Element name coded by the namespace attribute

dd....dd: wsdl:operation element name containing the element coded by the namespace attribute

Description

R2716 of WS-I Basic Profile 1.1 does not acknowledge, so the namespace attribute cannot be coded in the soap:body element.

Action

Do not code the namespace attribute in the soap:body element.

KDJW51219-W

The catalog file specified by -catalog option is not found. (catalog file = aa....aa)

aa....aa: Path of the catalog file specified with the -catalog option

Description

The catalog file specified with the -catalog option is not found.

Action

Check that the path of the catalog file specified with the -catalog option is correct.

KDJW51220-W

The value specified by -catalog option is not a file. (value = aa....aa)

aa....aa: Path of the catalog file specified with the -catalog option

Description

The value that is specified with the -catalog option of the cjwsimport command is a directory.

Action

Check that by mistake a directory is not specified in the value of the -catalog option.

KDJW51221-W

The XML is invalid against the schema(s) for catalog file. (file = aa....aa, detail = bb....bb)

aa....aa: Path of the catalog file specified with the catalog option

bb....bb: Detail

Description

The syntax grammar of catalog file is incorrect.

Action

Reference the detail, check the syntax of the catalog file, and remove the cause. If the cause of the failure is reading of the catalog file instead of the syntax of the catalog file, check that the path of the catalog file and access permission are correct.

KDJW51222-E

The wsdl:output grandchild element of wsdl:binding element corresponding to the wsdl:output grandchild element of wsdl:portType element cannot be found. (WSDL name = aa....aa, line = bb....bb, binding name = cc....cc, operation name = dd....dd)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: wsdl:binding element name

dd....dd: wsdl:operation element name

Description

The wsdl:output grandchild element of the wsdl:binding element corresponding to the wsdl:output grandchild element of the wsdl:portType element cannot be found.

Action

Define the wsdl:output grandchild element of the wsdl:binding element corresponding to the wsdl:output grandchild element of the wsdl:portType element.

KDJW51210-E

R2716 of WS-I Basic Profile 1.1 does not allow namespace attribute in the element. (WSDL file = aa....aa, line = bb....bb, element = cc....cc, fault name = dd....dd)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: Element name coded by the namespace attribute

dd....dd: wsdl:fault element name coded by the namespace attribute

Description

R2716 of WS-I Basic Profile 1.1 does not acknowledge, so the namespace attribute cannot be coded in the soap:fault element.

Action

Do not code the namespace attribute in the soap:fault element.

KDJW51212-E

Unknown required extensibility element was found at the element. (WSDL file = aa....aa, line = bb....bb, extensibility element = cc....cc)

aa....aa: WSDL file path

bb....bb: Line number

cc....cc: Extension element name coded by the wsdl:required attribute

Description

R2026 of WS-I Basic Profile 1.1 does not recommend, so the wsdl:required attribute cannot be coded in the extension element.

Action

Do not code the wsdl:required attribute in the extension element.

KDJW51901-E

Please set environment variable COSMINEXUS_HOME explicitly to the directory at which Cosminexus is installed.

Description

The system environment variable COSMINEXUS_HOME is not set up.

Action

Set up the directory in which Application Server is installed, in the system environment variable COSMINEXUS_HOME.

KDJW51902-E

Fatal error occurred. HNTRLib2 path could not be retrieved.

Description

The installation path of HNTRLib2 could not be acquired.

Action

Check that the directory in which Cosminexus is installed is set up in the system environment variable COSMINEXUS_HOME.

If set up, check that HNTRLib2 is installed.

KDJW59998-W

A warning occurred while cjwsimport command was executed. (detail = aa....aa)

aa....aa: Detail

Description

A negligible error occurred while executing the cjwsimport command.

Action

Reference the detail, and then eliminate the cause if required.

KDJW59999-E

An error occurred while cjwsimport command was executed. (detail = aa....aa)

aa....aa: Detailed message

Description

An error occurred while executing the cjwsimport command.

Action

Refer to the detailed message, remove the cause of the error, and then re-execute the command.

10.8 Messages from KDJW70000 to KDJW79999

This section describes the messages from KDJW70000 to KDJW79999 and the corresponding actions.

KDJW71901-E

Please set environment variable COSMINEXUS_HOME explicitly to the directory at which Cosminexus is installed.

Description

The system environment variable COSMINEXUS_HOME is not set up.

Action

In the system environment variable COSMINEXUS_HOME, set up the Cosminexus installation directory.

11 KECX (Messages Output by Cosminexus XML Processor)

This chapter describes the messages output by Cosminexus XML Processor.

Cosminexus XML Processor outputs messages beginning with KECX. The JAXB functionality of Cosminexus XML Processor also outputs messages without message IDs.

11.1 Message Description Format

This section describes the format for describing messages.

KECXnnnnn-Y

Message text

The following is the description for each item:

KECXnnnnn

This indicates the message ID.

The description of elements configuring the message ID is as follows:

KECX

This indicates the prefix for messages output by Cosminexus XML Processor.

nnnnn

This indicates the message number managed in the Cosminexus XML Processor. A five-digit specific number is attached to the respective messages.

Y

This indicates the message type. The message type is shown with one alphabetic character.

The characters showing message types and their meaning are mentioned below:

E: Error

W: Warning

I: Information

Message text

The messages output by Cosminexus XML Processor are displayed in English.

The Japanese text is described as the translation of English text.

The corresponding character string is output for the {numeric value} within messages. If the corresponding string contains more than one phrase, demarcate the phrases with comma (,) (for example, in the message KECX06223-E, the corresponding string is displayed as 'Target namespace, name').

When validating XML Schema, if the name of the type is unclear, "#AnonType_xxx" is displayed at the location of the string where name of the type is entered in the message (for example, in the message KECX06063-E, "#AnonType_xxx" will be displayed).

The messages output by the JAXB function of Cosminexus XML Processor do not have message IDs and message types.

11.2 Messages from KECX01001 to KECX01999

This section explains the messages from KECX01001 to KECX01999 that the Cosminexus XML Processor outputs.

KECX01001-E

The error message corresponding to the message key cannot be found.

The error message corresponding to the message key cannot be found.

KECX01002-E

An internal error occurred while formatting the following message:

An internal error occurred while formatting the next message.

KECX01003-E

Premature end of file.

Reached the end of the file during parsing.

KECX01004-E

The root element is required in a well-formed document.

The root element is required in a well-formed document.

KECX01005-E

An invalid XML character (Unicode: 0xaa....aa) was found in the CDATA section.

An invalid XML character (Unicode: 0xaa....aa) exists in the CDATA section.

KECX01006-E

An invalid XML character (Unicode: 0xaa....aa) was found in the element content of the document.

An invalid XML character (Unicode: 0xaa....aa) exists in the element content of the document.

KECX01010-E

An invalid XML character (Unicode: 0xaa....aa) was found in the XML declaration.

An invalid XML character (Unicode: 0xaa....aa) exists in the XML declaration.

KECX01011-E

The character sequence "]]>" must not appear in content unless used to mark the end of a CDATA section.

The character sequence ]]> must not be used for a purpose other than to indicate end of the CDATA section.

KECX01014-E

The ' = ' character must follow "aa....aa" in the XML declaration.

An equals sign (=) must follow aa....aa in the XML declaration.

KECX01015-E

The value following "aa....aa" in the XML declaration must be a quoted string.

In the XML declaration, the value of aa....aa must be enclosed within quotation marks.

KECX01016-E

The XML declaration must end with "?>".

The XML declaration must end with ?>.

KECX01017-E

The version is required in the XML declaration.

The version is required in the XML declaration.

KECX01018-E

White space is required before the version pseudo attribute in the XML declaration.

A space is required before the version pseudo attribute of the XML declaration.

KECX01019-E

White space is required before the encoding pseudo attribute in the XML declaration.

A space is required before the encoding pseudo attribute of the XML declaration.

KECX01020-E

White space is required before the encoding pseudo attribute in the XML declaration.

A space is required before the encoding pseudo attribute of the XML declaration.

KECX01021-E

The markup in the document preceding the root element must be well-formed.

The markup in the document preceding the root element must be well-formed.

KECX01022-E

The markup in the document following the root element must be well-formed.

The markup in the document following the root element must be well-formed.

KECX01023-E

Already seen doctype.

Doctype is already declared.

KECX01024-E

Content is not allowed in prolog.

Content cannot be specified in prolog. Alternatively, a null string can be specified in an argument of the parse method.

KECX01025-E

Reference is not allowed in prolog.

Reference cannot be specified in prolog.

KECX01026-E

Content is not allowed in trailing section.

Content cannot be specified in the trailing section.

KECX01027-E

Reference is not allowed in trailing section.

Reference cannot be specified in the trailing section.

KECX01028-E

The standalone document declaration value must be "yes" or "no", not "aa....aa".

The value of the standalone document declaration must be either yes or no, and not aa....aa.

KECX01030-E

The element type "aa....aa" must be terminated by the matching end-tag "</aa....aa>".

The element type aa....aa must end with the end tag </aa....aa>.

KECX01031-E

Element type "aa....aa" must be followed by either attribute specifications, ">" or "/>".

The element type aa....aa must be followed by either > or />.

KECX01032-E

Attribute name "bb....bb" associated with an element type "aa....aa" must be followed by the ' = ' character.

An equals sign (=) must be added after the attribute name bb....bb associated with the element type aa....aa.

KECX01033-E

Open quote is expected for attribute "bb....bb" associated with an element type "aa....aa".

The attribute specification bb....bb associated with the element type aa....aa does not have open quotation marks.

KECX01034-E

Close quote is expected for attribute "bb....bb" associated with an element type "aa....aa".

The attribute specification bb....bb associated with the element type aa....aa does not have close quotation marks.

KECX01035-E

Attribute "bb....bb" was already specified for element "aa....aa".

The attribute bb....bb is already specified for element aa....aa.

KECX01036-E

Attribute "bb....bb" bound to namespace "cc....cc" was already specified for element "aa....aa".

The attribute bb....bb to set boundary to the namespace cc....cc was already linked to the element aa....aa.

KECX01037-E

The end-tag for element type "aa....aa" must end with a '>' delimiter.

The end tag of the element type aa....aa must be >.

KECX01038-E

The content of elements must consist of well-formed character data or markup.

The contents of elements must have either the well-formed character data or markup.

KECX01039-E

A DOCTYPE is not allowed in content.

DOCTYPE cannot be specified in element contents.

KECX01042-E

The element "aa....aa" must start and end within the same entity.

The element aa....aa must start and end within the same entity.

KECX01043-E

XML document structures must start and end within the same entity.

The XML document must start and end within the same entity.

KECX01044-E

An invalid XML character (Unicode: 0xcc....cc) was found in the value of attribute "bb....bb" and element is "aa....aa".

An invalid XML character (Unicode: 0xcc....cc) exists in the attribute value bb....bb of element aa....aa.

KECX01045-E

An invalid XML character (Unicode: 0xaa....aa) was found in the comment.

An invalid XML character (Unicode: 0xaa....aa) exists in the comment.

KECX01046-E

An invalid XML character (Unicode: 0xaa....aa) was found in the processing instruction.

An invalid XML character (Unicode: 0xaa....aa) exists in the processing instruction.

KECX01048-E

An invalid XML character (Unicode: 0xaa....aa) was found in the text declaration.

An invalid XML character (Unicode: 0xaa....aa) exists in the text declaration.

KECX01050-E

The value of attribute "bb....bb" associated with an element type "aa....aa" must not contain the '<' character.

The attribute value bb....bb associated with the element type aa....aa must not contain a less-than sign (<).

KECX01052-E

Comment must start with "<!--".

A comment must start with <!--.

KECX01053-E

The string "--" is not permitted within comments.

-- cannot be used within comments.

KECX01056-E

The processing instruction must begin with the name of the target.

The processing instruction must begin with the target name.

KECX01057-E

White space is required between the processing instruction target and data.

A space is required between the processing instruction target and the data.

KECX01059-E

The processing instruction target matching "[xX][mM][lL]" is not allowed.

[xX][mM][lL] cannot be specified for the processing instruction target.

KECX01062-E

XML version "aa....aa" is not supported, only XML 1.0 is supported.

The XML version aa....aa is not supported. Only XML 1.0 is supported.

KECX01063-E

A decimal representation must immediately follow the "&#" in a character reference.

In the character reference, a decimal code must immediately follow &#.

KECX01064-E

A hexadecimal representation must immediately follow the "&#x" in a character reference.

In the character reference, a hexadecimal code must immediately follow &#x.

KECX01065-E

The character reference must end with the ';' delimiter.

The character reference must end with a semicolon (;).

KECX01066-E

Character reference "&#aa....aa;" is an invalid XML character.

The character reference &#aa....aa; is an invalid XML character specification.

KECX01067-E

The entity name must immediately follow the '&' in the entity reference.

The entity name must immediately follow & in the entity reference.

KECX01068-E

The reference to entity "aa....aa" must end with the ';' delimiter.

The reference to entity aa....aa must end with a semicolon (;).

KECX01070-E

The ' = ' character must follow "aa....aa" in the text declaration.

In the text declaration, aa....aa must be followed by an equals sign (=).

KECX01071-E

The value following "aa....aa" in the text declaration must be a quoted string.

In the text declaration, the value of aa....aa must be enclosed within quotation marks.

KECX01072-E

closing quote in the value following "aa....aa" in the text declaration is missing.

The close quotation marks for aa....aa do not exist in the text declaration.

KECX01073-E

White space is required before the version pseudo attribute in the text declaration.

A space is required before the version pseudo attribute in the text declaration.

KECX01074-E

White space is required before the encoding pseudo attribute in the text declaration.

A space is required before the encoding pseudo attribute in the text declaration.

KECX01076-E

The encoding declaration is required in the text declaration.

Encoding declaration must be performed in the text declaration.

KECX01077-E

No more pseudo attributes are allowed.

No more pseudo attributes can be specified.

KECX01078-E

More pseudo attributes are expected.

The number of pseudo attributes is insufficient.

KECX01079-E

A pseudo attribute name is expected.

A pseudo attribute name is not specified.

KECX01082-E

Invalid encoding name "aa....aa".

aa....aa is an invalid encoding name.

KECX01083-E

Given byte order for encoding "aa....aa" is not supported.

Byte order assigned to encoding aa....aa is not supported.

KECX01087-E

An invalid XML character (Unicode: 0xaa....aa) was found in the public identifier.

An invalid XML character (Unicode: 0xaa....aa) exists in the public identifier.

KECX01088-E

An invalid XML character (Unicode: 0xaa....aa) was found in the system identifier.

An invalid XML character (Unicode: 0xaa....aa) exists in the system identifier.

KECX01089-E

White space is required after keyword SYSTEM in DOCTYPE decl.

A space is required after the keyword SYSTEM in the DOCTYPE declaration.

KECX01090-E

The system identifier must begin with either a single or double quote character.

The system identifier must begin with either single or double quotation marks.

KECX01091-E

The system identifier must end with the matching quote character.

The system identifier must end with either single or double quotation marks.

KECX01092-E

White spaces are required after keyword PUBLIC in DOCTYPE decl.

A space is required after the keyword PUBLIC in the DOCTYPE declaration.

KECX01093-E

The public identifier must begin with either a single or double quote character.

The public identifier must begin with either single or double quotation marks.

KECX01094-E

The public identifier must end with the matching quote character.

The public identifier must end with either single or double quotation marks.

KECX01096-E

White spaces are required between publicId and systemId.

A space is required between the public identifier and the system identifier.

KECX01097-E

White space is required after "<!DOCTYPE" in the document type declaration.

A space is required after <!DOCTYPE in the DOCTYPE declaration.

KECX01098-E

The root element type must appear after "<!DOCTYPE" in the document type declaration.

A root element type must appear after <!DOCTYPE in the DOCTYPE declaration.

KECX01099-E

The document type declaration for root element type "aa....aa" must end with '>'.

The DOCTYPE declaration of the root element type aa....aa must end with a greater-than sign (>).

KECX01100-E

The parameter entity reference "%aa....aa;" cannot occur within markup in the internal subset of the DTD.

The parameter entity reference aa....aa cannot be coded within the markup in the internal subset of DTD.

KECX01101-E

The markup declarations contained or pointed to by the document type declaration must be well-formed.

The markup declaration must either include or point to a well-formed document type declaration.

KECX01103-E

White space is required after "<!ELEMENT" in the element type declaration.

A space is required after <!ELEMENT in the element type declaration.

KECX01104-E

The element type is required in the element type declaration.

The element type declaration is required for specifying the element type.

KECX01105-E

White space is required after the element type "aa....aa" in the element type declaration.

A space is required after the element type aa....aa in the element type declaration.

KECX01107-E

The declaration for element type "aa....aa" must end with '>'.

The element type declarationaa....aa must end with a greater-than sign (>).

KECX01108-E

A '(' character or an element type is required in the declaration of element type "aa....aa".

Either a left parenthesis (() or an element type is required in the declaration of the element type aa....aa.

KECX01109-E

A ')' is required in the declaration of element type "aa....aa".

A right parenthesis ')' is required in the declaration of the element type aa....aa.

KECX01110-E

An element type is required in the declaration of element type "aa....aa".

An element type is required in the declaration of the element type aa....aa.

KECX01112-E

The mixed content model "aa....aa" must end with ")*" when the types of child elements are constrained.

The mixed content model aa....aa must end with )* when the types of child elements are required.

KECX01113-E

White space is required after "<!ATTLIST" in the attribute-list declaration.

A space is required after <!ATTLIST in the attribute list declaration.

KECX01114-E

The element type is required in the attribute-list declaration.

An attribute-list declaration is required for the element type.

KECX01115-E

White space is required before the attribute name in the attribute-list declaration for element "aa....aa".

A space is required before attribute name in the attribute-list declaration for the element aa....aa.

KECX01116-E

The attribute name must be specified in the attribute-list declaration for element "aa....aa".

The attribute name must be specified in the attribute list of the element aa....aa.

KECX01117-E

White space is required before the attribute type in the declaration of attribute "bb....bb" for element "aa....aa".

A space is required before the attribute type in the declaration of the attribute bb....bb of element aa....aa.

KECX01118-E

The attribute type is required in the declaration of attribute "bb....bb" for element "aa....aa".

An attribute type is required in the declaration of the attribute bb....bb of element aa....aa.

KECX01119-E

White space is required before the attribute default in the declaration of attribute "bb....bb" for element "aa....aa".

A space is required before the default attribute in the declaration of the attribute bb....bb of element aa....aa.

KECX01120-W

More than one attribute definition is provided for the same attribute "bb....bb" of a given element "aa....aa".

More than one attribute definition is provided for the declaration of the same attribute bb....bb of the specified element aa....aa.

KECX01121-E

White space must appear after "NOTATION" in the "bb....bb" attribute declaration.

A space is required after NOTATION in the attribute declaration bb....bb.

KECX01122-E

The '(' character must follow "NOTATION" in the "bb....bb" attribute declaration.

A left parenthesis (() is required after NOTATION in the attribute declaration bb....bb.

KECX01123-E

The notation name is required in the notation type list for the "bb....bb" attribute declaration.

The notation name is required in the notation type specification for the attribute declaration bb....bb.

KECX01124-E

The notation type list must end with ')' in the "bb....bb" attribute declaration.

The notation type must end with a right parenthesis ')' in the notation type specification for the attribute declaration bb....bb.

KECX01125-E

The name token is required in the enumerated type list for the "bb....bb" attribute declaration.

The name token is required in the enumerated type list for the attribute declaration bb....bb.

KECX01126-E

The enumerated type list must end with ')' in the "bb....bb" attribute declaration.

The enumerated type list for the attribute declaration bb....bb must end with a right parenthesis ')'.

KECX01127-E

White space must appear after "FIXED" in the "bb....bb" attribute declaration.

A space is required after FIXED in the attribute declaration bb....bb.

KECX01128-E

The included conditional section must end with "]]>".

The included conditional section must end with ]]>.

KECX01129-E

The excluded conditional section must end with "]]>".

The excluded conditional section must end with ]]>.

KECX01130-E

The entity name must immediately follow the '%' in the parameter entity reference.

The entity name of the parameter entity reference must follow the percent sign (%).

KECX01131-E

The parameter entity reference "%aa....aa;" must end with the ';' delimiter.

The parameter entity reference aa....aa must end with a semicolon (;).

KECX01132-E

White space is required after "<!ENTITY" in the entity declaration.

A space is required after <!ENTITY in the entity declaration.

KECX01133-E

White space is required between "<!ENTITY" and the '%' character in the parameter entity declaration.

A space is required between <!ENTITY and the percent sign (%) in the parameter entity declaration.

KECX01135-E

The name of the entity is required in the entity declaration.

The name of the entity is required in the entity declaration.

KECX01136-E

White space is required between the entity name "aa....aa" and the definition in the entity declaration.

A space is required between the entity name aa....aa and the definition in the entity declaration.

KECX01137-E

White space is required between "NDATA" and the notation name in the declaration for the entity "aa....aa".

A space is required between NDATA and the notation name in the declaration for the entity aa....aa.

KECX01138-E

White space is required before "NDATA" in the declaration for the entity "aa....aa".

A space is required before NDATA in the declaration for the entity aa....aa.

KECX01139-E

The notation name is required after "NDATA" in the declaration for the entity "aa....aa".

The notation name is required after NDATA in the declaration for the entity aa....aa.

KECX01140-E

The declaration for the entity "aa....aa" must end with '>'.

The declaration for the entity aa....aa must end with a greater-than sign (>).

KECX01146-E

White space is required after "<!NOTATION" in the notation declaration.

A space is required after <!NOTATION in the notation declaration.

KECX01147-E

The name of the notation is required in the notation declaration.

The notation name is required in the notation declaration.

KECX01148-E

White space is required after the notation name "aa....aa" in the notation declaration.

A space is required after the notation name aa....aa in the notation declaration.

KECX01149-E

The declaration for the notation "aa....aa" must include a system or public identifier.

The declaration for the notation aa....aa must include a system identifier or a public identifier.

KECX01150-E

The declaration for the notation "aa....aa" must end with '>'.

The declaration for the notation aa....aa must end with a greater-than sign (>).

KECX01151-E

The element type "bb....bb" was already specified in the content model of the element decl "aa....aa".

The element type bb....bb is already declared in the content model of the element declaration aa....aa.

KECX01154-E

The ID attribute "aa....aa" must have a declared default of "#IMPLIED" or "#REQUIRED".

The ID attribute aa....aa must be a declared default value of #IMPLIED or #REQUIRED.

KECX01155-E

Attribute value "aa....aa" of type ID must be a name.

The attribute value aa....aa of the type ID must be a name.

KECX01156-E

Attribute value "aa....aa" of type ID must be unique within the document.

The attribute value aa....aa of the type ID must be unique within the document.

KECX01157-E

Attribute value "aa....aa" of type IDREF must be a name.

The attribute value aa....aa of the type IDREF must be a name.

KECX01158-E

Attribute value "aa....aa" of type IDREFS must be one or more names.

The attribute value aa....aa of the type IDREF must be one or more names.

KECX01159-E

The replacement text of parameter entity "aa....aa" must include properly nested declarations.

The replacement text of the parameter entity aa....aa must include properly nested declarations.

KECX01161-E

Attribute "bb....bb" must be declared for element type "aa....aa".

The attribute bb....bb must be the declaration for the element type aa....aa.

KECX01162-E

Attribute "aa....aa" with value "bb....bb" must have a value from the list "cc....cc".

The attribute aa....aa with the value bb....bb must have a value from the list cc....cc.

KECX01163-E

The value "bb....bb" of attribute "aa....aa" must not be changed by normalization (to "cc....cc") in a standalone document.

The value bb....bb of attribute aa....aa must not be changed (to cc....cc) by normalization in a standalone document.

KECX01164-E

The content of element type "aa....aa" is incomplete, it must match "bb....bb".

The contents of the element type aa....aa are incomplete and must match bb....bb.

KECX01165-E

The content of element type "aa....aa" must match "bb....bb".

The contents of the element type aa....aa must match bb....bb.

KECX01166-E

Attribute "bb....bb" for element type "aa....aa" has a default value and must be specified in a standalone document.

The attribute bb....bb of the element type aa....aa must have a default value and must be specified in a standalone document.

KECX01168-E

Element type "aa....aa" must not be declared more than once.

The element type aa....aa must not be declared two or more times.

KECX01169-E

Element type "aa....aa" must be declared.

The element type aa....aa must be declared.

KECX01170-E

Document is invalid: no grammar found.

Document is invalid. No syntax.

KECX01171-E

An element with the identifier "aa....aa" must appear in the document.

An element with the identifier aa....aa must exist in the document.

KECX01173-E

Attribute "bb....bb" with value "cc....cc" must have a value of "dd....dd".

The attribute bb....bb with value cc....cc must have a value of dd....dd.

KECX01174-E

Element type "aa....aa" already has attribute "bb....bb" of type ID, a second attribute "cc....cc" of type ID is not permitted.

The element type aa....aa already has the attribute bb....bb of the type ID. A second attribute cc....cc of the type ID is not allowed.

KECX01175-E

Element type "aa....aa" already has attribute "bb....bb" of type NOTATION, a second attribute "cc....cc" of type NOTATION is not permitted.

The element type aa....aa already has the attribute bb....bb of the type NOTATION. A second attribute cc....cc of the type NOTATION is not allowed.

KECX01176-E

The notation "bb....bb" must be declared when referenced in the notation type list for attribute "aa....aa".

The notation bb....bb must be declared when referenced in the notation type list for the attribute aa....aa.

KECX01177-E

The notation "bb....bb" must be declared when referenced in the unparsed entity declaration for "aa....aa".

The notation bb....bb must be declared when referenced in the unparsed entity for the attribute aa....aa.

KECX01178-E

The reference to entity "aa....aa" declared in an external parsed entity is not permitted in a standalone document.

The reference to the entity aa....aa declared in an external parsed entity is not allowed in a standalone document.

KECX01179-E

Attribute "bb....bb" is required and must be specified for element type "aa....aa".

The attribute bb....bb is required for specifying the element type aa....aa.

KECX01180-E

White space must not occur between elements declared in an external parsed entity with element content in a standalone document.

A space must not exist in the element declaration of an external parsed entity with element contents of the standalone document.

KECX01181-E

Attribute value "aa....aa" of type NMTOKEN must be a name token.

The attribute value aa....aa of the type NMTOKEN must be a name token.

KECX01182-E

Attribute value "aa....aa" of type NMTOKENS must be one or more name tokens.

The attribute value aa....aa of the type NMTOKENS must have one or more name tokens.

KECX01183-E

Document root element "bb....bb", must match DOCTYPE root "aa....aa".

The document root element bb....bb must match the DOCTYPE root aa....aa.

KECX01184-W

The content model of element "aa....aa" refers to the undeclared element "bb....bb".

The content model of element aa....aa references the undeclared element bb....bb.

KECX01185-E

ENTITYDatatype Validator: Failed Need to call initialize method with a valid Grammar reference.

Validity of ENTITYDatatype: An attempt to call the initialization method with valid syntax has failed.

KECX01186-E

ENTITY "aa....aa" is not unparsed.

The entity aa....aa is not unparsed.

KECX01188-E

Value of type ENTITIES, IDREFS, and NMTOKENS cannot be empty list.

An empty list cannot be specified in the value of the types ENTITIES, IDREFS, and NMTOKENS.

KECX01189-E

The external entity reference "&aa....aa;" is not permitted in an attribute value.

The external entity reference &aa....aa; is not allowed as an attribute.

KECX01190-E

The entity "aa....aa" was referenced, but not declared.

The entity aa....aa was referenced, but is not declared.

KECX01191-E

The unparsed entity reference "&aa....aa;" is not permitted.

The unparsed entity reference &aa....aa; is not allowed.

KECX01192-E

Recursive entity reference "aa....aa". (Reference path: bb....bb),

This is a recursive entity reference aa....aa. (See path bb....bb).

KECX01197-E

The prefix "aa....aa" for element "bb....bb" is not bound.

The prefix aa....aa of the element bb....bb is not bound.

KECX01198-E

The prefix "cc....cc" for attribute "bb....bb" associated with an element type "aa....aa" is not bound.

The prefix cc....cc of the attribute bb....bb associated to the element type aa....aa is not bound.

KECX01199-E

The value of the attribute "aa....aa" is invalid. Prefixed namespace bindings may not be empty.

The value of the attribute aa....aa is invalid. The prefixed namespace binding is not empty.

KECX01200-E

The namespace prefix "aa....aa" was not declared.

The namespace prefix aa....aa was not declared.

KECX01201-E

The defaultValue "bb....bb" of attribute "aa....aa" is not legal as for the lexical constraints of this attribute type.

The default value bb....bb of the attribute aa....aa consists of words that cannot be used in this attribute type.

KECX01202-E

OpenQuoteMissingInDecl

The declaration does not have open quotation marks.

KECX01203-E

InvalidCharInLiteral

Invalid characters exist in literal.

KECX01204-E

!!! unknown attribute type aa....aa

An unknown attribute type aa....aa was found.

KECX01206-W

Warning: validation was turned on but an org.xml.sax.ErrorHandler was not set, which is probably not what is desired. Parser will use a default ErrorHandler to print the first aa....aa errors. Please call the 'setErrorHandler' method to fix this.

Warning: Validation was performed, but org.xml.sax.ErrorHandler is not set. This is not desirable. The parser will use default ErrorHandler to report first error aa....aa. Call the setErrorHandler method to fix this problem.

KECX01207-E

Should never get here. : DeferredDocumentTypeImpl#synchronizeInfo: node.getNodeType() = aa....aa, class = bb....bb

This value must not be acquired. The value of DeferredDocumentTypeImpl#synchronizeInfo: node.getNodeType() is aa....aa and the class name is bb....bb.

KECX01208-E

Invalid byte aa....aa of bb....bb-byte UTF-8 sequence.

Byte aa....aa of the bb....bb-byte UTF-8 sequence is invalid.

KECX01209-E

Expected byte aa....aa of bb....bb-byte UTF-8 sequence.

Byte aa....aa of the bb....bb-byte UTF-8 sequence is required.

KECX01210-E

High surrogate bits in UTF-8 sequence must not exceed 0x10 but found 0xaa....aa.

Although the upper limit for the higher surrogate bits of UTF-8 must not exceed 0x10, the 0xaa....aa was found.

KECX01211-E

Operation "aa....aa" not supported by bb....bb reader.

The operation "aa....aa" is not supported by bb....bbreader.

KECX01212-E

Byte "aa....aa" is not a member of the (7-bit) ASCII character set.

Byte aa....aa is not a member of the 7-bit ASCII character set.

KECX01213-W

Entity "aa....aa" is declared more than once.

The entity aa....aa is declared two or more times.

KECX01214-E

Element "aa....aa" cannot have "xmlns" as its prefix.

xmlns cannot be specified as a prefix of the element aa....aa.

KECX01215-E

The prefix "xmlns" cannot be bound to any namespace explicitly; neither can the namespace for "xmlns" be bound to any prefix explicitly.

The prefix xmlns cannot be bound explicitly to a namespace. Also, the namespace for xmlns cannot be bound explicitly to any prefix.

KECX01216-E

The prefix "xml" cannot be bound to any namespace other than its usual namespace; neither can the namespace for "xml" be bound to any prefix other than "xml".

The prefix xml cannot be bound to a namespace other than its usual namespace. Also, the namespace for xml cannot be bound to any prefix other than xml.

KECX01217-E

The replacement text of parameter entity "aa....aa" must include properly nested declarations when the entity reference is used as a complete declaration.

When the entity reference is used as a complete declaration, the replacement text of the parameter entity aa....aa must include properly nested declarations.

KECX01218-E

The replacement text of parameter entity "aa....aa" must include the entire conditional section or just INCLUDE or IGNORE.

The replacement text of the parameter entity aa....aa must include the entire conditional section and not only INCLUDE or IGNORE.

KECX01219-E

A colon is not allowed in the name 'aa....aa' when namespaces are enabled.

When namespaces are enabled, a colon is not allowed within the name aa....aa.

KECX01220-E

DOCTYPE is disallowed when the feature http://apache.org/xml/features/disallow-doctype-decl set to true.

When the feature http://apache.org/xml/features/disallow-doctype-decl is set to true, DOCTYPE is not allowed.

KECX01221-E

XML version "aa....aa" is not supported, only XML 1.0 and XML 1.1 are supported.

The XML version aa....aa is not supported. Only XML1.0 and XML1.1 are supported.

KECX01222-E

Attribute value "aa....aa" of type ID must be an NCName when namespaces are enabled.

When namespaces are enabled, the attribute value aa....aa of the type ID must be an NCName.

KECX01223-E

Attribute value "aa....aa" of type IDREF must be an NCName when namespaces are enabled.

When namespaces are enabled, the attribute value aa....aa of the type IDREF must be an NCName.

KECX01224-E

Element or attribute do not match QName production: QName::=(NCName':')?NCName.

The element or attribute does not match Qname generation. QName::=(NCName':')?NCName

KECX01225-E

The parser has encountered more than "aa....aa" entity expansions in this document; this is the limit imposed by the application.

The parser has detected aa....aa or more entity expansions in this document. This limit is imposed by the application.

KECX01226-E

An entity determined to be in a certain encoding must not contain sequences illegal in that encoding.

An entity determined to be in a particular encoding cannot contain invalid sequences in that encoding.

KECX01227-E

The enumeration value "bb....bb" was specified more than once in the declaration of attribute "cc....cc" for element "aa....aa". The NMTOKENS in a single Enumeration attribute declaration must all be distinct.

The enumeration value bb....bb was specified more than once in the declaration for the attribute cc....cc of element aa....aa. All NMTOKENS in a single enumeration attribute declaration must be unique.

KECX01228-E

The enumeration value "bb....bb" was specified more than once in the declaration of attribute "cc....cc" for element "aa....aa". The NOTATION names in a single NotationType attribute declaration must all be distinct.

The enumeration value bb....bb was specified more than once in the declaration for the attribute cc....cc of element aa....aa. All NOTATION names in a single notation type attribute declaration must be unique.

KECX01229-E

The content of element type "aa....aa" must match "bb....bb". Children of type "cc....cc" are not allowed.

The contents of the element type aa....aa must match bb....bb. Children of the type cc....cc are not allowed.

KECX01230-E

Element type "aa....aa" which was declared EMPTY cannot declare attribute "bb....bb" of type NOTATION.

The element type aa....aa declared as EMPTY cannot declare the attribute bb....bb of the type NOTATION.

KECX01231-E

The declaration for the notation "aa....aa" is not unique. A given Name must not be declared in more than one notation declaration.

The declaration for the notation aa....aa is not unique. The same name must not be declared in more than one notation declaration.

KECX01232-E

The length of entity "aa....aa" is "bb....bb" that exceeds the "cc....cc" limit set by "dd....dd".

The length of entity "aa....aa" is "bb....bb" that exceeds the "cc....cc" limit set by "dd....dd".

KECX01233-E

The accumulated size "aa....aa" of entities exceeded the "bb....bb" limit set by "cc....cc".

The accumulated size "aa....aa" of entities exceeded the "bb....bb" limit set by "cc....cc".

KECX01301-E

The error message corresponding to the message key can not be found.

The error message corresponding to the message key is not found.

KECX01302-E

An internal error occurred while formatting the following message:\n

An internal error occurred while formatting the following message:

KECX01303-E

The specified range of text does not fit into a DOMString.

The specified range of text does not fit into a DOMString.

KECX01304-E

An attempt was made to insert a node where it is not permitted.

An attempt was made to insert a node at a prohibited location.

KECX01305-E

The index or size is negative, or greater than the allowed value.

The index or size has either a negative value or a value greater than the allowed value.

KECX01306-E

An attempt is made to add an attribute that is already in use elsewhere.

An attempt is made to add an attribute that is already in use elsewhere.

KECX01308-E

An invalid or illegal XML character is specified.

An invalid or disabled XML character is specified.

KECX01310-E

An attempt is made to use an object that is not, or is no longer, usable.

An attempt is made to use an object that either does not exist or cannot be used.

KECX01311-E

An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.

An attempt is made to create or change an object using an inappropriate method with regard to namespaces.

KECX01312-E

An attempt is made to reference a node in a context where it does not exist.

An attempt is made to reference a node in a non-existing context.

KECX01313-E

The implementation does not support the requested type of object or operation.

The implementation does not support the requested type of object or operation.

KECX01315-E

An attempt is made to modify an object where modifications are not allowed.

An attempt is made to modify an object at a location where modifications are not allowed.

KECX01318-E

A node is used in a different document than the one that created it.

A node is used in a document different from the one in which the node was created.

KECX01319-E

The parameter aa....aa is recognized but the requested value cannot be set.

The parameter aa....aa is recognized but the requested value is not set.

KECX01320-E

The parameter aa....aa is not recognized.

The parameter aa....aa is not recognized.

KECX01323-E

The Event's type was not specified by initializing the event before the method was called.

The type of the event was not specified during initialization of the event before the method invocation.

KECX01324-E

The resulting string is too long to fit in a DOMString: 'aa....aa'.

The character string generated as a result is too long to fit in a DOMString. aa....aa

KECX01325-E

The value type for this parameter name is incompatible with the expected value type.

The value type for this parameter name is incompatible with the expected value type.

KECX01326-E

The text aa....aa of the bb....bb node contains invalid XML characters.

The text aa....aa of the bb....bb node contains invalid XML characters.

KECX01327-E

The aa....aa node named bb....bb contains invalid XML characters.

The aa....aa node named bb....bb contains invalid XML characters.

KECX01328-E

CDATA sections containing the CDATA section termination marker ']]>'

The CDATA section contains the CDATA section termination marker ]]>.

KECX01329-E

DOCTYPE declaration is not allowed.

The DOCTYPE declaration is not allowed.

KECX01330-E

The encoding aa....aa is not supported.

The encoding aa....aa is not supported.

KECX01331-E

An invalid XML character (Unicode: 0xaa....aa) was found in the DOM during normalization.

An invalid XML character (Unicode: 0xaa....aa) was found in the DOM during normalization.

KECX01332-E

The attribute "aa....aa" value "bb....bb" referenced an entity that was not declared.

The value bb....bb of the attribute aa....aa referenced an entity that is not declared.

KECX01333-E

A null local name was encountered during namespace normalization of element aa....aa.

A null local name was found during namespace normalization of the element aa....aa.

KECX01334-E

A null local name was encountered during namespace normalization of attribute aa....aa.

A null local name was found during the namespace normalization of the attribute aa....aa.

KECX01335-E

The class name of the document factory "aa....aa" used to construct the DOM tree is not of type org.w3c.dom.Document.

The class name of the document factory aa....aa that is used to construct the DOM tree does not have the org.w3c.dom.Document type.

KECX01336-E

The class name of the document factory "aa....aa" used to construct the DOM tree could not be found.

The class name of the document factory aa....aa that is used to construct the DOM tree was not found.

KECX01337-E

The class named "aa....aa" could not be constructed as a org.w3c.dom.Document.

The class named aa....aa could not be constructed as org.w3c.dom.Document.

KECX01338-E

Property 'aa....aa' must be set before setting property 'bb....bb'.

The property aa....aa must be set before setting the property bb....bb.

KECX01339-E

The source specified cannot be null.

The specified source cannot be null.

KECX01401-E

Argument 'aa....aa' is null.

The argument aa....aa is null.

KECX01402-E

No writer supplied for serializer.

No writer provided for serializer.

KECX01403-E

The method 'aa....aa' is not supported by this factory.

The method aa....aa is not supported by this factory.

KECX01404-E

The serializer may not be reset in the middle of serialization.

The serializer might not be reset in the middle of serialization.

KECX01405-E

Internal error: element state is zero.

An internal error occurred. The element state is zero.

KECX01406-E

There is no rawName and localName is null.

There is no rawName. Also, the localName is null.

KECX01407-E

The element name 'aa....aa' is not a QName.

The element name aa....aa is not a QName.

KECX01408-E

Element 'aa....aa' does not belong to any namespace: prefix could be undeclared or bound to some namespace.

The element aa....aa does not belong to any namespace. Either the prefix is not declared or is bound to some namespace.

KECX01409-E

The attribute name 'aa....aa' is not a QName.

The attribute name aa....aa is not a QName.

KECX01410-E

Attribute 'aa....aa' does not belong to any namespace: prefix could be undeclared or bound to some namespace.

The attribute aa....aa does not belong to any namespace. Either the prefix is not declared or is bound to some namespace.

KECX01411-E

Namespace declaration syntax is incorrect: aa....aa.

The namespace declaration syntax is incorrect. aa....aa

KECX01412-E

The character sequence "]]>" must not appear in content unless used to mark the end of a CDATA section.

The character sequence ]]> must only be used to indicate the end of a CDATA section.

KECX01413-W

Splitting a CDATA section containing the CDATA section termination marker "]]>".

A CDATA section containing the CDATA section termination marker ]]> is split up.

KECX01414-E

The resource 'aa....aa' could not be found.

The resource aa....aa was not found.

KECX01415-E

The resource 'aa....aa' could not be loaded. bb....bb

The resource aa....aa could not be loaded. bb....bb

KECX01416-E

Serialization stopped at user request.

Serialization was stopped at user request.

KECX01417-E

no-output-specified: The output destination for data to be written to was null.

No output specified: The output destination for writing data was null.

KECX01418-E

unsupported-encoding: An unsupported encoding is encountered:aa....aa.

Unsupported encoding: An unsupported encoding was found: aa....aa

KECX01419-E

unable-to-serialize-node: The node could not be serialized.

Unable to serialize node: The node could not be serialized.

KECX01451-E

The error message corresponding to the message key can not be found.

The error message corresponding to the message key cannot be found.

KECX01452-E

An internal error occurred while formatting the following message:

An internal error occurred while formatting the following message:

KECX01453-E

no-input-specified

No input is specified.

KECX01600-E

parse may not be called while parsing.

The parse method was called again during the DOM parsing.

KECX01601-E

Element stack underflow.

An underflow occurred in the element stack.

KECX01701-E

The error message corresponding to the message key can not be found.

The error message corresponding to the message key is not found.

KECX01702-E

An internal error occurred while formatting the following message:

An internal error occurred while formatting the following message:

KECX01703-E

An 'include' failed, and no 'fallback' element was found.

The operation include failed, and the fallback element was not found.

KECX01704-E

The [children] of an 'include' element cannot contain more than one 'fallback' element.

More than one fallback element cannot be included in the child of an include element.

KECX01705-E

A 'fallback' element was found that did not have 'include' as the parent.

A fallback element that did not have include as the parent was found.

KECX01706-E

Elements from namespace 'http://www.w3.org/2001/XInclude', other than 'fallback', are not allowed to be children of 'include' elements. However, 'aa....aa' was found.

Elements from the namespace http://www.w3.org/2001/Xinclude, other than fallback, cannot be children of an include element. However, aa....aa was found.

KECX01707-E

The 'href' attribute of an 'include' element is missing.

The include element does not contain the href attribute.

KECX01708-E

Recursive include detected. Document 'aa....aa' was already processed.

This is a recursive include derivative. Document aa....aa is already processed.

KECX01709-E

Invalid value for 'parse' attribute on 'include' element: 'aa....aa'.

This is an invalid value for the parse attribute on the include element. aa....aa

KECX01710-E

Error attempting to parse XML file (href='aa....aa').

This error occurs while parsing the XML file (href='aa....aa').

KECX01711-W

Include operation failed, reverting to fallback. Resource error reading file as XML (href='aa....aa'). Reason: bb....bb

The include processing has failed. Reverting to fallback. This is a resource error that occurred while reading the file as XML (href='aa....aa'). The reason is bb....bb.

KECX01712-E

Include operation failed, reverting to fallback. Resource error reading file as text (href='aa....aa'). Reason: bb....bb

The include processing has failed, reverting to fallback. This is a resource error that occurred while reading the file as text (href='aa....aa'). The reason is bb....bb.

KECX01713-E

Multiple notations were used which had the name 'aa....aa', but which were not determined to be duplicates.

Multiple notations with the name "aa....aa" were used without knowing that they are duplicates.

KECX01714-E

Multiple unparsed entities were used which had the name 'aa....aa', but which were not determined to be duplicates.

Multiple unparsed entities containing the name "aa....aa" were used without knowing that they are duplicates.

KECX01715-E

The type of the NamespaceContext is incompatible with using XInclude; it must be an instance of XIncludeNamespaceSupport

The type of NamespaceContext is incompatible with the use of XInclude. It must be an instance of XIncludeNamespaceSupport.

KECX01716-E

Could not expand system id of included resource

The system ID of the included resource could not be extended.

KECX01717-E

Elements from namespace 'http://www.w3.org/2001/XInclude', other than 'include', are not allowed to be children of 'fallback' elements. However, 'aa....aa' was found.

Elements from the namespace http://www.w3.org/2001/Xinclude, other than include, cannot be children of the fallback element. However, aa....aa was found.

KECX01718-E

xpointer attribute must be present when href attribute is absent.

The xpointer attribute is required when the href attribute is absent.

KECX01719-E

Characters outside the range #x20 through #x7E are not allowed in the value of the 'accept' attribute of an 'include' element.

The characters outside the range from #x20 to #x7E cannot be included in the value of the accept attribute of the include element.

KECX01720-E

Characters outside the range #x20 through #x7E are not allowed in the value of the 'accept-language' attribute of an 'include' element.

The characters outside the range from #x20 to #x7E cannot be included in the value of the accept-language attribute of the include element.

KECX01721-E

A well-formed document requires a root element.

The well-formed document requires a root element.

KECX01722-E

A well-formed document must not contain multiple root elements.

Multiple root elements cannot be included in a well-formed document.

KECX01723-E

The replacement of an 'include' element appearing as the document element in the top-level source infoset cannot contain characters.

The replacement of the include element displayed as the document element in the top-level source infoset cannot contain characters.

KECX01724-E

The replacement of an 'include' element appearing as the document element in the top-level source infoset cannot contain unexpanded entity references.

The replacement of the include element displayed as the document element in the top-level source infoset cannot contain unexpanded entity references.

KECX01725-E

Fragment identifiers must not be used. The 'href' attribute value 'aa....aa' is not permitted.

Fragment identifiers cannot be used. The href attribute value aa....aa is not allowed.

KECX01726-E

href' attribute value 'aa....aa' is syntactically invalid. After applying escaping rules the value is neither a syntactically correct URI or IRI.

The href attribute value 'aa....aa' is syntactically invalid. After applying escape rules, the value is neither a syntactically correct URI nor an IRI.

KECX01727-E

An xpointer was specified that points to a location in the source infoset. This location cannot be accessed due to the streaming nature of the processor.

An xpointer that points to a location in the source infoset was specified. This location cannot be accessed due to the streaming nature of the processor.

KECX01728-E

XPointer resolution unsuccessful.

An attempt to resolve XPointer has failed.

KECX01801-E

Wrong character.

The character is invalid.

KECX01802-E

Invalid reference number.

This group number does not exist.

KECX01803-E

A character is required after \.

A character must follow \.

KECX01804-E

'?' is not expected. '(?:' or '(?=' or '(?!' or '(?<' or '(?#' or '(?>'?

A question mark (?) cannot be written here. Did you mean to write '(?:', or '(?=', or '(?!', or '(?<', or '(?#', or '(?>'?

KECX01805-E

'(?<=' or '(?<!' is expected.

Either '(?<=' or '(?<!' is required.

KECX01806-E

A comment is not terminated.

A comment is not closed.

KECX01807-E

')' is expected.

A right parenthesis ')' is required.

KECX01808-E

Unexpected end of the pattern in a modifier group.

The pattern has ended within a group with options.

KECX01809-E

':' is expected.

A colon (:) is required.

KECX01810-E

Unexpected end of the pattern in a conditional group.

The pattern has ended within a conditional group.

KECX01811-E

A back reference or an anchor or a lookahead or a lookbehind is expected in a conditional pattern.

You can use only back reference, anchor, lookahead, or a lookbehind in a conditional pattern.

KECX01812-E

There are more than three choices in a conditional group.

Three or more choices are available in a conditional group.

KECX01813-E

A character in U+0040-U+005f must follow \c.

The character with a code point in the range of U+0040 to U+005f must follow \c.

KECX01814-E

A '{' is required before a character category.

A single character category or a left curly bracket '{' is required.

KECX01815-E

A property name is not closed by '}'.

The property name is not closed with a right curly bracket '}'.

KECX01816-E

Unexpected meta character.

A meta character is at an invalid location.

KECX01817-E

Unknown property.

This is an unknown property name.

KECX01818-E

A POSIX character class must be closed by ':]'.

The POSIX character class must be closed with ':]'.

KECX01819-E

Unexpected end of the pattern in a character class.

The pattern has ended in a character class.

KECX01820-E

Unknown name for a POSIX character class.

This is an unknown POSIX character class name.

KECX01821-E

'-' is invalid here.

A hyphen (-) cannot be written here.

KECX01822-E

']' is expected.

A right square bracket (]) is required.

KECX01823-E

'[' is invalid in a character class. Write '\['.

A left square bracket ([) cannot be written directly in a character class. Write as '\['.

KECX01824-E

']' is invalid in a character class. Write '\]'.

A right square bracket (]) cannot be written directly in a character class. Write as '\]'.

KECX01825-E

'-' is an invalid character range. Write '\-'.

A hyphen (-) cannot be written directly in a character range specification. Write as '\-'.

KECX01826-E

'[' is expected.

A left square bracket ([) is required.

KECX01827-E

')' or '-[' or '+[' or '&[' is expected.

A right parenthesis ')', or '-[', or '+[', or '&[' is required.

KECX01828-E

The range end code point is less than the start code point.

The range end code point is less than the start code point.

KECX01829-E

Invalid Unicode hex notation.

An invalid character exists in the hexadecimal notation of the code point.

KECX01830-E

Overflow in a hex notation.

The numeric value of the code point is too big.

KECX01831-E

'\x{' must be closed by '}'.

'\x{' must be closed with a right curly bracket '}'.

KECX01832-E

Invalid Unicode code point.

This is an invalid Unicode code point.

KECX01833-E

An anchor must not be here.

An anchor cannot be written here.

KECX01834-E

This expression is not supported in the current option setting.

This expression cannot be used in the current option setting.

KECX01835-E

Invalid quantifier. A digit is expected.

The setting is invalid. Specify a digit.

KECX01836-E

Invalid quantifier. Invalid quantity or a '}' is missing.

The setting is invalid. Either the quantity is invalid, or a right curly bracket '}' is missing.

KECX01837-E

Invalid quantifier. A digit or '}' is expected.

The setting is invalid. Specify a digit or }.

KECX01838-E

Invalid quantifier. A min quantity must be <= a max quantity.

The setting is invalid. A min quantity must be lesser than or equal to a max quantity.

KECX01839-E

Invalid quantifier. A quantity value overflow.

The setting is invalid. The quantity value is overflowing.

KECX01853-E

Unknown option: aa....aa

aa....aa is an unknown option.

KECX01901-E

The error message corresponding to the message key can not be found.

The error message corresponding to the message key cannot be found.

KECX01902-E

An internal error occurred while formatting the following message:

An internal error occurred while formatting the following message:

KECX01903-E

The specified schema language is not supported.

The specified schema language is not supported.

KECX01904-E

Property 'aa....aa' must be set before setting property 'bb....bb'.

The property aa....aa must be set before setting the property bb....bb.

KECX01905-E

Property 'aa....aa' cannot be set when a non-null Schema object has already been specified.

The property aa....aa cannot be set if a non-null schema object is already specified.

KECX01906-E

Feature 'aa....aa' is not supported.

The feature aa....aa is not supported.

KECX01907-E

Feature 'aa....aa' is not recognized.

The feature aa....aa is not recognized.

KECX01908-E

True state for feature 'aa....aa' is not supported.

The true state for the feature aa....aa is not supported.

KECX01909-E

False state for feature 'aa....aa' is not supported.

The false state for the feature aa....aa is not supported.

KECX01910-E

Feature 'aa....aa' is read only.

The feature aa....aa is read only.

KECX01911-E

Property 'aa....aa' is not supported.

The property aa....aa is not supported.

KECX01912-E

Property 'aa....aa' is not recognized.

The property aa....aa is not recognized.

KECX01913-E

Property 'aa....aa' is read only.

The property aa....aa is read only.

KECX01914-E

Property 'aa....aa' is not supported while parsing.

The property aa....aa is not supported while parsing.

KECX01915-E

Cannot read DOM node property. No DOM tree exists.

The DOM node property cannot be read. The DOM tree does not exist.

KECX01916-E

The value specified for property 'aa....aa' cannot be casted to bb....bb.

The value specified in the property aa....aa cannot be converted to bb....bb.

11.3 Messages from KECX02001 to KECX02999

This section describes messages from KECX02001 to KECX02999 that are output by Cosminexus XML Processor.

KECX02001-E

Error: Can not have '{' within expression

This is an error. A left curly bracket ({) cannot be used within an expression.

KECX02002-E

aa....aa has an illegal attribute: bb....bb

aa....aa has an illegal attribute. bb....bb

KECX02003-E

sourceNode is null in xsl:apply-imports!

sourceNode is null in xsl:apply-imports.

KECX02004-E

Can not add aa....aa to bb....bb

aa....aa cannot be added to bb....bb.

KECX02005-E

sourceNode is null in handleApplyTemplatesInstruction!

sourceNode is null in handleApplyTemplatesInstruction.

KECX02006-E

aa....aa must have a name attribute.

A name attribute is required in aa....aa.

KECX02007-E

Could not find template named: aa....aa

A template named aa....aa was not found.

KECX02008-E

Could not resolve name AVT in xsl:call-template.

The name AVT could not be resolved in xls:call-template.

KECX02009-E

aa....aa requires attribute: bb....bb

The attribute bb....bb is required in aa....aa.

KECX02010-E

aa....aa must have a 'test' attribute.

A test attribute is required in aa....aa.

KECX02011-E

Bad value on level attribute: aa....aa

An invalid value is specified in the level attribute.aa....aa

KECX02012-E

processing-instruction name can not be 'xml'

The processing-instruction name cannot be xml.

KECX02013-E

processing-instruction name must be a valid NCName: aa....aa

The processing-instruction name must be a valid NCName. aa....aa

KECX02014-E

aa....aa must have a match attribute if it has a mode.

aa....aa must have a match attribute if it has a mode.

KECX02015-E

aa....aa requires either a name or a match attribute.

aa....aa requires either the name attribute or the match attribute.

KECX02016-E

Can not resolve namespace prefix: aa....aa

The namespace prefix aa....aa cannot be resolved.

KECX02017-E

xml:space has an illegal value: aa....aa

xml:space contains an invalid value. aa....aa

KECX02018-E

Child node does not have an owner document!

The child node does not have an owner document.

KECX02019-E

ElemTemplateElement error: aa....aa

This is an ElemTemplateElement error. aa....aa

KECX02020-E

Trying to add a null child!

An attempt was made to add a null child.

KECX02021-E

aa....aa requires a select attribute.

A select attribute is required in aa....aa.

KECX02022-E

xsl:when must have a 'test' attribute.

A test attribute is required in xsl:when.

KECX02023-E

xsl:with-param must have a 'name' attribute.

A name attribute is required in xsl:with-param.

KECX02024-E

context does not have an owner document!

Context does not have an owner document.

KECX02025-E

Could not create XML TransformerFactory Liaison: aa....aa

XML TransformerFactory Liaison aa....aa could not be created.

KECX02026-E

XML Processor: Process was not successful.

XML Processor: Process was not successful.

KECX02027-E

XML Processor: was not successful.

XML Processor: was not successful.

KECX02028-E

Encoding not supported: aa....aa

Encoding is not supported.aa....aa

KECX02029-E

Could not create TraceListener: aa....aa

TraceListener could not be created.aa....aa

KECX02030-E

xsl:key requires a 'name' attribute!

A name attribute is required in xsl:key.

KECX02031-E

xsl:key requires a 'match' attribute!

A match attribute is required in xsl:key.

KECX02032-E

xsl:key requires a 'use' attribute!

A use attribute is required in xsl:key.

KECX02033-E

(StylesheetHandler) aa....aa requires an 'elements' attribute!

(StylesheetHandler) The elements attribute is required in aa....aa.

KECX02034-E

(StylesheetHandler) aa....aa attribute 'prefix' is missing

(StylesheetHandler) The 'prefix' of the aa....aa attribute is missing.

KECX02035-E

Stylesheet URL is bad: aa....aa

The URL of the style sheet is invalid. aa....aa

KECX02036-E

Stylesheet file was not found: aa....aa

The stylesheet file was not found.aa....aa

KECX02037-E

Had IO Exception with stylesheet file: aa....aa

An I/O exception occurred in the style sheet. aa....aa

KECX02038-E

(StylesheetHandler) Could not find href attribute for aa....aa

(StylesheetHandler) The href attribute of aa....aa was not found.

KECX02039-E

(StylesheetHandler) aa....aa is directly or indirectly including itself!

(StylesheetHandler) aa....aa is including itself either directly or indirectly.

KECX02040-E

StylesheetHandler.processInclude error, aa....aa

This is a StylesheetHandler.processInclude error. aa....aa

KECX02041-E

(StylesheetHandler) aa....aa attribute 'lang' is missing

(StylesheetHandler) The 'lang' of the aa....aa attribute is missing.

KECX02042-E

(StylesheetHandler) misplaced aa....aa element?? Missing container element 'component'

(StylesheetHandler) The location of the aa....aa element might be wrong. The container element 'component' is missing.

KECX02043-E

Can only output to an Element, DocumentFragment, Document, or PrintWriter.

Can be output only to Element, DocumentFragment, Document, or PrintWriter.

KECX02044-E

StylesheetRoot.process error

This is a StylesheetRoot.process error.

KECX02045-E

UnImplNode error: aa....aa

This is a UnImplNode error. aa....aa

KECX02046-E

Error! Did not find xpath select expression (-select).

This is an error. The select expression (-select) of xpath was not found.

KECX02047-E

Can not serialize an XSLProcessor!

XSLProcessor cannot be serialized.

KECX02048-E

Stylesheet input was not specified!

The input of the style sheet was not specified.

KECX02049-E

Failed to process stylesheet!

An attempt to process the style sheet has failed.

KECX02050-E

Could not parse aa....aa document!

The aa....aa document could not be parsed.

KECX02051-E

Could not find fragment: aa....aa

The fragment: aa....aa could not be found.

KECX02052-E

Node pointed to by fragment identifier was not an element: aa....aa

The node indicated by the fragment identifier was not an element. aa....aa

KECX02053-E

for-each must have either a match or name attribute

Either the match attribute or the name attribute is required in for-each.

KECX02054-E

templates must have either a match or name attribute

Either the match attribute or the name attribute is required in templates.

KECX02055-E

No clone of a document fragment!

The document fragment does not have a clone.

KECX02056-E

Can not create item in result tree: aa....aa

Items cannot be created in the result tree. aa....aa

KECX02057-E

xml:space in the source XML has an illegal value: aa....aa

An invalid value exists in xml:space of the source XML. aa....aa

KECX02058-E

There is no xsl:key declaration for aa....aa!

There is no xls:key declaration for aa....aa.

KECX02059-E

Error! Cannot create url for: aa....aa

This is an error. A URL cannot be created for aa....aa.

KECX02060-E

xsl:functions is unsupported

xsl:functions is not supported.

KECX02061-E

XSLT TransformerFactory Error

This is the XSLT TransformerFactory error.

KECX02062-E

(StylesheetHandler) aa....aa not allowed inside a stylesheet!

(StylesheetHandler) aa....aa is not allowed inside a style sheet.

KECX02063-E

result-ns no longer supported! Use xsl:output instead.

result-ns is not supported. Instead, use xsl:output.

KECX02064-E

default-space no longer supported! Use xsl:strip-space or xsl:preserve-space instead.

default-space is not supported. Instead use xsl:strip-space or xsl:preserve-space.

KECX02065-E

indent-result no longer supported! Use xsl:output instead.

indent-result is not supported. Instead, use xsl:output.

KECX02066-E

(StylesheetHandler) aa....aa has an illegal attribute: bb....bb

(StylesheetHandler) aa....aa contains an invalid attribute. bb....bb

KECX02067-E

Unknown XSL element: aa....aa

This is an unknown XSL element. aa....aa

KECX02068-E

(StylesheetHandler) xsl:sort can only be used with xsl:apply-templates or xsl:for-each.

You can use (StylesheetHandler) xsl:sort only with xsl:apply-templates or xsl:for-each.

KECX02069-E

(StylesheetHandler) misplaced xsl:when!

(StylesheetHandler) The location of xsl:when is incorrect.

KECX02070-E

(StylesheetHandler) xsl:when not parented by xsl:choose!

(StylesheetHandler) xsl:choose is not the parent of xsl:when.

KECX02071-E

(StylesheetHandler) misplaced xsl:otherwise!

(StylesheetHandler) The location of xsl:otherwise is incorrect.

KECX02072-E

(StylesheetHandler) xsl:otherwise not parented by xsl:choose!

(StylesheetHandler) xsl:choose is not the parent of xsl:otherwise.

KECX02073-E

(StylesheetHandler) aa....aa is not allowed inside a template!

(StylesheetHandler) aa....aa is not allowed inside a template.

KECX02074-E

(StylesheetHandler) aa....aa extension namespace prefix bb....bb unknown

(StylesheetHandler) The prefix bb....bb of the aa....aa extension namespace is unknown.

KECX02075-E

(StylesheetHandler) Imports can only occur as the first elements in the stylesheet!

(StylesheetHandler) Import can be performed only for the first element of the style sheet.

KECX02076-E

(StylesheetHandler) aa....aa is directly or indirectly importing itself!

(StylesheetHandler) aa....aa is importing itself either directly or indirectly.

KECX02077-E

(StylesheetHandler) xml:space has an illegal value: aa....aa

(StylesheetHandler) xml:space has an invalid value. aa....aa

KECX02078-E

processStylesheet not successful!

processStylesheet is not successful.

KECX02079-E

SAX Exception

This is a SAX exception.

KECX02080-E

Function not supported!

This is an unsupported function.

KECX02081-E

XSLT Error

This is an XSLT error.

KECX02082-E

currency sign is not allowed in format pattern string

The currency sign is not allowed in the format pattern string.

KECX02083-E

Document function not supported in Stylesheet DOM!

The Document function is not supported in Stylesheet DOM.

KECX02084-E

Can't resolve prefix of non-Prefix resolver!

The prefix of non-Prefix resolver cannot be resolved.

KECX02085-E

Redirect extension: Could not get filename - file or select attribute must return valid string.

Redirect extension: The file name could not be acquired. The - file attribute or the select attribute must return a valid string.

KECX02086-E

Can not build FormatterListener in Redirect extension!

FormatterListener cannot be built in Redirect extension.

KECX02087-E

Prefix in exclude-result-prefixes is not valid: aa....aa

The prefix of exclude-result-prefixes is not valid. aa....aa

KECX02088-E

Missing namespace URI for specified prefix

The specified prefix does not have a namespace URI.

KECX02089-E

Missing argument for option: aa....aa

The option does not have an argument. aa....aa

KECX02090-E

Invalid option: aa....aa

The option is invalid.aa....aa

KECX02091-E

Malformed format string: aa....aa

This character string has an invalid format. aa....aa

KECX02092-E

xsl:stylesheet requires a 'version' attribute!

xsl:stylesheet requires a version attribute.

KECX02093-E

Attribute: aa....aa has an illegal value: bb....bb

The aa....aa attribute has an invalid value. bb....bb

KECX02094-E

xsl:choose requires an xsl:when

xsl:when is required in xsl:choose.

KECX02095-E

xsl:apply-imports not allowed in a xsl:for-each

xsl:apply-imports is not allowed in xsl:for-each.

KECX02096-E

Cannot use a DTMLiaison for an output DOM node... pass a com.cosminexus.jaxp.impl.xpath.DOM2Helper instead!

DTMLiaison cannot be used in an output DOM node. Instead, pass com.cosminexus.jaxp.impl.xpath.DOM2Helper.

KECX02097-E

Cannot use a DTMLiaison for a input DOM node... pass a com.cosminexus.jaxp.impl.xpath.DOM2Helper instead!

DTMLiaison cannot be used in an input DOM node. Instead, pass com.cosminexus.jaxp.impl.xpath.DOM2Helper.

KECX02098-E

Call to extension element failed: aa....aa

An attempt to call the extension element has failed.aa....aa

KECX02099-E

Prefix must resolve to a namespace: aa....aa

The prefix must be resolved in the namespace. aa....aa

KECX02100-E

Invalid UTF-16 surrogate detected: aa....aa ?

An invalid UTF-16 surrogate was detected. aa....aa

KECX02101-E

xsl:attribute-set aa....aa used itself, which will cause an infinite loop.

An infinite loop might occur because xsl:attribute-set aa....aa is using itself.

KECX02102-E

Can not mix non XML Processor-DOM input with XML Processor-DOM output!

A non-XML Processor-DOM input cannot be combined with an XML Processor-DOM output.

KECX02103-E

addTraceListenersToStylesheet - TooManyListenersException

Excessive addTraceListenersToStylesheet ListenersException.

KECX02104-E

In ElemTemplateElement.readObject: aa....aa

ElemTemplateElement.readObject contains aa....aa.

KECX02105-E

Found more than one template named: aa....aa

More than one template with the following name was found. aa....aa

KECX02106-E

Invalid function call: recursive key() calls are not allowed

This is an invalid function call. A recursive key() call is not allowed.

KECX02107-E

Variable aa....aa is directly or indirectly referencing itself!

The variable aa....aa is referencing itself either directly or indirectly.

KECX02108-E

The input node can not be null for a DOMSource for newTemplates!

The input node for DOMSource of newTemplates cannot be null.

KECX02109-E

Class file not found for option aa....aa

The class file for the option aa....aa is not found.

KECX02110-E

Required Element not found: aa....aa

The required element is not found. aa....aa

KECX02111-E

InputStream cannot be null

InputStream cannot be null.

KECX02112-E

URI cannot be null

A URI cannot be null.

KECX02113-E

File cannot be null

A file cannot be null.

KECX02114-E

InputSource cannot be null

InputSource cannot be null.

KECX02116-E

Could not initialize BSF Manager

The BSF Manager could not be initialized.

KECX02117-E

Could not compile extension

The extensions could not be compiled.

KECX02118-E

Could not create extension: aa....aa because of: bb....bb

The extension aa....aa could not be created. Reason bb....bb

KECX02119-E

Instance method call to method aa....aa requires an Object instance as first argument

The Object instance is required in the first argument of an instance method call to the method aa....aa.

KECX02120-E

Invalid element name specified aa....aa

An invalid element name was specified.aa....aa

KECX02121-E

Element name method must be static aa....aa

The element name method must be static. aa....aa

KECX02122-E

Extension function aa....aa : bb....bb is unknown

The extension function aa....aa: bb....bb is unknown.

KECX02123-E

More than one best match for constructor for aa....aa

The constructor for aa....aa has more than one best match.

KECX02124-E

More than one best match for method aa....aa

The method aa....aa has more than one best match.

KECX02125-E

More than one best match for element method aa....aa

The element method aa....aa has more than one best match.

KECX02126-E

Invalid context passed to evaluate aa....aa

An invalid context was passed to evaluate aa....aa.

KECX02127-E

Pool already exists

A pool already exists.

KECX02128-E

No driver Name specified

Driver name is not specified.

KECX02129-E

No URL specified

A URL is not specified.

KECX02130-E

Pool size is less than one!

Pool size is less than 1.

KECX02131-E

Invalid driver name specified!

An invalid driver name was specified.

KECX02132-E

Did not find the stylesheet root!

The style sheet root was not found.

KECX02133-E

Illegal value for xml:space

xml:space has an invalid value.

KECX02134-E

processFromNode failed

processFromNode has failed.

KECX02135-E

The resource [ aa....aa ] could not load: bb....bb cc....cc dd....dd

The resource aa....aa could not load bb....bb, cc....cc, and dd....dd

KECX02136-E

Buffer size <=0

The buffer size is less than or equal to 0.

KECX02137-E

Unknown error when calling extension

An unknown error occurred when calling the extension.

KECX02138-E

Prefix aa....aa does not have a corresponding namespace declaration

The prefix aa....aa does not have a corresponding namespace declaration.

KECX02139-E

Element content not allowed for lang=javaclass aa....aa

The element contents are not allowed for lang=javaclass aa....aa.

KECX02140-E

Stylesheet directed termination

Termination was directed by the style sheet.

KECX02143-E

Could not load aa....aa (check CLASSPATH), now using just the defaults

aa....aa could not be loaded (Check CLASSPATH). Only the default value will be used.

KECX02144-E

Cannot initialize default templates

The default template cannot be initialized.

KECX02145-E

Result should not be null

Result cannot be null.

KECX02146-E

Result could not be set

Result could not be set.

KECX02147-E

No output specified

An output destination is not specified.

KECX02148-E

Can't transform to a Result of type aa....aa

Cannot convert to a Result of type aa....aa.

KECX02149-E

Can't transform a Source of type aa....aa

Cannot convert to a Source of type aa....aa.

KECX02150-E

Null content handler

The contents handler is null.

KECX02151-E

Null error handler

The error handler is null.

KECX02152-E

parse can not be called if the ContentHandler has not been set

Parsing cannot be called if ContentHandler is not set.

KECX02153-E

No parent for filter

There is no parent for filter processing.

KECX02154-E

No stylesheet found in: aa....aa, media= bb....bb

The style sheet is not found in aa....aa, media = bb....bb.

KECX02155-E

No xml-stylesheet PI found in: aa....aa

xml-stylesheet PI was not found in aa....aa.

KECX02171-E

Not supported: aa....aa

Not supported. aa....aa

KECX02177-E

Value for property aa....aa should be a Boolean instance

The value of property aa....aa must be a Boolean instance.

KECX02195-E

Could not get to external script at aa....aa

The external script in aa....aa could not be acquired.

KECX02196-E

The resource [aa....aa] could not be found. bb....bb

The resource aa....aa could not be found.bb....bb

KECX02197-E

Output property not recognized: aa....aa

The output property is not recognized. aa....aa

KECX02203-E

Failed creating ElemLiteralResult instance

An attempt to create the ElemLiteralResult instance has failed.

KECX02204-E

Value for aa....aa should contain a parsable number

Specify a number that can be parsed in the value of aa....aa.

KECX02205-E

Value for aa....aa should equal yes or no

The value of aa....aa must be either yes or no.

KECX02206-E

Failed calling aa....aa method

An attempt to call the method has failed.

KECX02207-E

Failed creating ElemTemplateElement instance

An attempt to call the ElemTemplateElement instance has failed.

KECX02208-E

Characters are not allowed at this point in the document

A string is not allowed in this part of the document.

KECX02209-E

"aa....aa" attribute is not allowed on the bb....bb element!

The "aa....aa" attribute is not allowed in the bb....bb element.

KECX02211-E

aa....aa bad value bb....bb

An invalid value of aa....aa is bb....bb.

KECX02212-E

aa....aa attribute value not found

The aa....aa attribute value is not found.

KECX02213-E

aa....aa attribute value not recognized

The aa....aa attribute value is not recognized.

KECX02216-E

Attempting to generate a namespace prefix with a null URI

An attempt is made to generate the namespace prefix with a null URI.

KECX02217-E

Attempting to format a number bigger than the largest Long integer

An attempt is made to format a number bigger than the maximum value of Long.

KECX02218-E

Cannot find SAX1 driver class aa....aa

The SAX1 driver class aa....aa is not found.

KECX02219-E

SAX1 driver class aa....aa found but cannot be loaded

The SAX1 driver class aa....aa was found but cannot be loaded.

KECX02220-E

SAX1 driver class aa....aa loaded but cannot be instantiated

The SAX1 driver class aa....aa was loaded but cannot be instantiated.

KECX02221-E

SAX1 driver class aa....aa does not implement org.xml.sax.Parser

The SAX1 driver class aa....aa does not implement org.xml.sax.Parser.

KECX02222-E

System property org.xml.sax.parser not specified

The system property org.xml.sax.parser was not specified.

KECX02223-E

Parser argument must not be null

The parser argument cannot be null.

KECX02224-E

Feature: aa....aa

Feature is aa....aa.

KECX02225-E

Property: aa....aa

Property is aa....aa.

KECX02226-E

Null entity resolver

This is a null entity resolver.

KECX02227-E

Null DTD handler

This is a null DTD handler.

KECX02228-E

No Driver Name Specified!

A driver name is not specified.

KECX02229-E

No URL Specified!

A URL is not specified.

KECX02230-E

Pool size is less than 1!

The pool size is less than 1.

KECX02231-E

Invalid Driver Name Specified!

An invalid driver name was specified.

KECX02232-E

ErrorListener

ErrorListener is invalid.

KECX02233-E

Programmer's error! The expression has no ElemTemplateElement parent!

This is a programmer's error. The expression does not have ElemTemplateElement as the parent.

KECX02234-E

Programmer's assertion in RedundentExprEliminator: aa....aa

This is a programmer's specification in RedundentExprEliminator. aa....aa

KECX02237-E

aa....aa is not allowed in this position in the stylesheet!

aa....aa cannot be specified at this location in the style sheet.

KECX02238-E

Non-whitespace text is not allowed in this position in the stylesheet!

Non space text cannot be specified at this location in the style sheet.

KECX02239-E

Illegal value: bb....bb used for CHAR attribute: aa....aa. An attribute of type CHAR must be only 1 character!

An invalid value bb....bb is used in the CHAR attribute aa....aa. An attribute of CHAR type must be only a single character.

KECX02242-E

Illegal value: bb....bb used for QNAME attribute: aa....aa

An invalid value bb....bb was used in the QNAME attribute aa....aa.

KECX02243-E

Illegal value: bb....bb used for ENUM attribute: aa....aa. Valid values are: cc....cc.

An invalid value bb....bb was used in the ENUM attribute aa....aa. The valid value is cc....cc.

KECX02244-E

Illegal value: bb....bb used for NMTOKEN attribute: aa....aa

An invalid value bb....bb was used in the NMTOKEN attribute aa....aa.

KECX02245-E

Illegal value: bb....bb used for NCNAME attribute: aa....aa

An invalid value bb....bb was used in the NCNAME attribute aa....aa.

KECX02246-E

Illegal value: bb....bb used for boolean attribute: aa....aa

An invalid value bb....bb was used in the boolean attribute aa....aa.

KECX02247-E

Illegal value: bb....bb used for number attribute: aa....aa

An invalid value bb....bb was used in the number attribute aa....aa.

KECX02248-E

Argument to aa....aa in match pattern must be a literal.

The argument to aa....aa in the matching pattern must be a literal.

KECX02249-E

Duplicate global variable declaration.

The global variable declaration is duplicated.

KECX02250-E

Duplicate variable declaration.

The variable declaration is duplicated.

KECX02251-E

xsl:template must have a name or match attribute (or both)

The name attribute or the match attribute (or both) is required in xsl:template.

KECX02252-E

Prefix in exclude-result-prefixes is not valid: aa....aa

The prefix in exclude-result-prefixes is invalid. aa....aa

KECX02253-E

attribute-set named aa....aa does not exist

An attribute-set named aa....aa does not exist.

KECX02254-E

The function named aa....aa does not exist

A function named aa....aa does not exist.

KECX02256-E

The value of param aa....aa must be a valid Java Object

The value of param aa....aa must be a valid Java object.

KECX02257-E

The result-prefix attribute of an xsl:namespace-alias element has the value '#default', but there is no declaration of the default namespace in scope for the element

The result-prefix attribute of the xsl:namespace-alias element has the value #default, but there is no declaration of the default namespace in the scope of the corresponding element.

KECX02258-E

The result-prefix attribute of an xsl:namespace-alias element has the value 'aa....aa', but there is no namespace declaration for the prefix 'aa....aa' in scope for the element.

The result-prefix attribute of the xsl:namespace-alias element has the value aa....aa, but there is no namespace declaration for the prefix aa....aa in the scope of corresponding element.

KECX02259-E

The feature name cannot be null in TransformerFactory.setFeature(String name, boolean value).

The feature name cannot be null in TransformerFactory.setFeature (String name, boolean value).

KECX02260-E

The feature name cannot be null in TransformerFactory.getFeature(String name).

The feature name cannot be null in TransformerFactory.getFeature (String name).

KECX02261-E

Cannot set the feature 'aa....aa' on this TransformerFactory.

The feature aa....aa cannot be set in TransformerFactory.

KECX02262-E

Use of the extension element 'aa....aa' is not allowed when the secure processing feature is set to true.

The use of the extension element aa....aa is not allowed when the secure processing feature is set to true.

KECX02263-E

Cannot get the prefix for a null namespace uri.

A prefix corresponding to an invalid namespace URI cannot be acquired.

KECX02264-E

Cannot get the namespace uri for null prefix.

A namespace URI corresponding to an invalid prefix cannot be acquired.

KECX02265-E

The function name cannot be null.

The feature name cannot be null.

KECX02266-E

The arity cannot be negative.

The number of arguments cannot be a negative value.

KECX02288-E

The aa....aa element must not have both content and a select attribute.

The element aa....aa cannot have both contents and the select attribute.

KECX02289-E

aa....aa attribute name="bb....bb" is already used with same import precedence

The attribute name=bb....bb of aa....aa is already in use with the same import precedence.

KECX02304-E

getAssociatedStylesheets failed

getAssociatedStylesheets has failed.

KECX02309-E

Invalid ConnectionPool name or JNDI Datasource path: aa....aa

This is an invalid ConnectionPool name or JNDI Datasource path: aa....aa

KECX02311-E

handler can not be null for a SAXResult

The SAXResult handler cannot be null.

KECX02312-E

Could not load any resource bundles.aa....aa

The resource bundles aa....aa cannot be loaded.

KECX02313-E

Could not load any resource bundles.

No resource bundles can be loaded.

KECX02314-E

Can't clone node: aa....aa

Cannot clone node aa....aa.

KECX02320-E

For extension aa....aa, could not find bb....bb cc....cc

bb....bb and cc....cc are not found in extension specifications aa....aa.

KECX02321-W

Warning: Could not get charToByteConverterClass!

Warning: charToByteConverterClass cannot be acquired.

KECX02322-W

Warning: encoding "aa....aa" not supported, using bb....bb

Warning: Encoding aa....aa is not supported. Use bb....bb.

KECX02323-W

Warning: aa....aa

Warning: aa....aa

KECX02324-W

Warning: InvocationTargetException in canConvert!

Warning: InvocationTargetException occurred in the canConvert method.

KECX02325-W

Warning: IllegalAccessException in canConvert!

Warning: IllegalAccessException occurred in the canConvert method.

KECX02326-E

Error! parent of xsl:fallback must be an extension or unknown element!

Error: The parent of xsl:fallback must be either an extension element or an unknown element.

KECX02327-E

Programmers error! countMatchPattern should never be null!

This is a programmer's error. countMatchPattern cannot be null.

KECX02328-W

TODO: Need to write the hooks for QNAME sort data type

The hooks for the sort data type of QNAME must be coded.

KECX02329-W

# WARNING: -out aa....aa threw bb....bb

Warning: -out aa....aa has thrown bb....bb.

KECX02330-W

# WARNING: -out argument should have a filename, output sent to console

Warning: The argument of -out must be a file name. The output was sent to the console.

KECX02331-W

appendEnvironmentReport threw: aa....aa

The appendEnvironmentReport method has thrown aa....aa.

KECX02501-W

Found '}' but no attribute template open!

A right curly bracket (}) was found, but the attribute template is not open.

KECX02502-W

Warning: count attribute does not match an ancestor in xsl:number! Target = aa....aa

Warning: The count attribute does not match the ancestor of xsl:number. Target=aa....aa

KECX02503-W

Old syntax: The name of the 'expr' attribute has been changed to 'select'.

Old syntax. The attribute name expr is changed to select.

KECX02504-W

XML Processor doesn't yet handle the locale name in the format-number function.

The XML Processor does not yet handle the locale name in the format-number function.

KECX02505-W

Warning: Could not find locale for xml:lang=aa....aa

Warning: The locale for xml:lang=aa....aa cannot be found.

KECX02506-W

Can not make URL from: aa....aa

A URL cannot be created from aa....aa.

KECX02507-W

Can not load requested doc: aa....aa

The requested doc aa....aa cannot be loaded.

KECX02508-W

Could not find Collator for <sort xml:lang=aa....aa

The Collator for <sort xml:lang=aa....aa cannot be found.

KECX02509-W

Old syntax: the functions instruction should use a url of aa....aa

Old syntax. The function instruction must use the URL of aa....aa.

KECX02510-W

encoding not supported: aa....aa, using UTF-8

The encoding aa....aa is not supported. Use UTF-8.

KECX02511-W

encoding not supported: aa....aa, using Java bb....bb

The encoding aa....aa is not supported. Use Javabb....bb.

KECX02512-W

Specificity conflicts found: aa....aa Last found in stylesheet will be used.

A conflict was found in specifications. aa....aa that is used at the end in the style sheet is being used.

KECX02513-W

========= Parsing and preparing aa....aa ==========

Executing and preparing for the parser. aa....aa

KECX02514-W

Attr Template, aa....aa

Attr Template, aa....aa

KECX02515-W

Match conflict between xsl:strip-space and xsl:preserve-space

There is a conflict between xsl:strip-space and xsl:preserve-space.

KECX02516-W

XML Processor does not yet handle the aa....aa attribute!

The XML Processor does not handle the aa....aa attribute.

KECX02517-W

No declaration found for decimal format: aa....aa

A declaration for the decimal format is not found. aa....aa

KECX02518-E

Missing or incorrect XSLT Namespace.

The namespace for XSLT is either missing or invalid.

KECX02519-W

Only one default xsl:decimal-format declaration is allowed.

There is only one default value allowed in the xsl:decimal-format declaration.

KECX02520-W

xsl:decimal-format names must be unique. Name "aa....aa" has been duplicated.

xsl:decimal-format names must be unique. The name aa....aa is duplicated.

KECX02521-W

aa....aa has an illegal attribute: bb....bb

aa....aa contains an invalid attribute bb....bb.

KECX02522-W

Could not resolve namespace prefix: aa....aa. The node will be ignored.

The namespace prefix aa....aa could not be resolved. The node will be ignored.

KECX02523-W

xsl:stylesheet requires a 'version' attribute!

xsl:stylesheet requires the version attribute.

KECX02524-W

Illegal attribute name: aa....aa

The attribute name is invalid.aa....aa

KECX02525-W

Illegal value used for attribute aa....aa: bb....bb

An invalid value is used in the attribute aa....aa. bb....bb

KECX02526-W

Resulting nodeset from second argument of document function is empty. Return an empty node-set.

The nodeset acquired from the second argument of the document function is empty. Returns an empty node-set.

KECX02527-W

The value of the name attribute of xsl:processing-instruction name must not be xml

The value of the name attribute of xsl:processing-instruction cannot be xml.

KECX02528-W

The value of the name attribute of xsl:processing-instruction must be a valid NCName: aa....aa

The value of the name attribute of xsl:processing-instruction must be a valid NCName. aa....aa

KECX02529-W

Cannot add attribute aa....aa after child nodes or before an element is produced. Attribute will be ignored.

The attribute aa....aa cannot be added after a child node or before an element is expressed. The attribute will be ignored.

KECX02530-E

An attempt is made to modify an object where modifications are not allowed.

An attempt is made to modify an object at a location where modifications are not allowed.

KECX02701-E

Parameter to createMessage was out of bounds

A parameter to createMessage was out of the boundary.

KECX02702-E

Exception thrown during messageFormat call

An exception was thrown during the messageFormat call.

KECX02703-E

Xalan-J command line Process class options:

Xalan-J command line Process class options:

KECX02704-W

The option aa....aa is not supported in XSLTC mode.

The option aa....aa is not supported in the XSLTC mode.

KECX02705-W

The option aa....aa can only be used with -XSLTC.

The option aa....aa can be used only with -XSLTC.

KECX02706-E

Error: No stylesheet or input xml is specified. Run this command without any option for usage instructions.

Error: Either there is no style sheet or the input xml is not specified. As regards the usage method, execute this command without any option.

KECX02707-E

Template nesting too deep. nesting = aa....aa, template bb....bb cc....cc

The template nesting is too deep. Nest = aa....aa, template bb....bb cc....cc

KECX02708-E

Could not prime the pump!

Could not invoke.

KECX02709-E

ParseException aa....aa

ParseException occurred in aa....aa.

11.4 Messages from KECX03001 to KECX03999

This section describes the messages from KECX03001 to KECX03999 that are output by Cosminexus XML Processor.

KECX03001-E

The current() function is not allowed in a match pattern!

The current() function is not allowed in pattern matching.

KECX03002-E

The current() function does not accept arguments!

The current() function does not accept arguments.

KECX03003-E

document() function implementation has been replaced by com.cosminexus.jaxp.impl.transform.xslt.FuncDocument!

The document() function implementation has been replaced by com.cosminexus.jaxp.impl.transform.xslt.FuncDocumentdocument().

KECX03004-E

context does not have an owner document!

The context does not have an owner document.

KECX03005-E

local-name() has too many arguments.

local-name() has too many arguments.

KECX03006-E

namespace-uri() has too many arguments.

namespace-uri() has too many arguments.

KECX03007-E

normalize-space() has too many arguments.

normalize-space() has too many arguments.

KECX03008-E

number() has too many arguments.

number() has too many arguments.

KECX03009-E

name() has too many arguments.

name() has too many arguments.

KECX03010-E

string() has too many arguments.

string() has too many arguments.

KECX03011-E

string-length() has too many arguments.

string-length() has too many arguments.

KECX03012-E

The translate() function takes three arguments!

Three arguments are specified for the translate() function.

KECX03013-E

The unparsed-entity-uri function should take one argument!

The unparsed-entity-uri function has one argument.

KECX03014-E

namespace axis not implemented yet!

The namespace axis is not yet implemented.

KECX03015-E

unknown axis: aa....aa

This is an unknown axis. aa....aa

KECX03016-E

unknown match operation!

This is an unknown match operation.

KECX03017-E

Arg length of processing-instruction() node test is incorrect!

The length of an argument of processing-instruction() node test is invalid.

KECX03018-E

Can not convert aa....aa to a number

aa....aa cannot be converted to a number.

KECX03019-E

Can not convert aa....aa to a NodeList!

aa....aa cannot be converted to a NodeList.

KECX03020-E

Can not convert aa....aa to a NodeSetDTM!

aa....aa cannot be converted to a NodeSetDTM.

KECX03021-E

Can not convert aa....aa to a type#bb....bb

aa....aa cannot be converted to a type#bb....bb.

KECX03022-E

Expected match pattern in getMatchScore!

An expected match pattern was found in getMatchScore.

KECX03023-E

Could not get variable named aa....aa

A variable named aa....aa could not be acquired.

KECX03024-E

ERROR! Unknown op code: aa....aa

Error! This is an unknown option code aa....aa

KECX03025-E

Extra illegal tokens: aa....aa

This is an extra invalid token. aa....aa

KECX03026-E

misquoted literal... expected double quote!

There is an error in the quotation of the literal. Double quotation marks must be used.

KECX03027-E

misquoted literal... expected single quote!

There is an error in the quotation of the literal. Single quotation marks must be used.

KECX03028-E

Empty expression!

The expression is empty.

KECX03029-E

Expected aa....aa, but found: bb....bb

aa....aa was expected, but bb....bb was found.

KECX03030-E

Programmer assertion is incorrect! - aa....aa

An invalid programmer was specified. - aa....aa

KECX03031-E

boolean(...) argument is no longer optional with 19990709 XPath draft.

The boolean(...) argument is not optional for the 19990709 XPath draft.

KECX03032-E

Found ',' but no preceding argument!

A comma (,) is found, but there is no argument preceding the comma.

KECX03033-E

Found ',' but no following argument!

A comma (,) is found, but there is no argument following the comma.

KECX03034-E

'..[predicate]' or '.[predicate]' is illegal syntax. Use 'self::node()[predicate]' instead.

..[predicate] or .[predicate] is invalid syntax. Instead, use self::node()[predicate].

KECX03035-E

illegal axis name: aa....aa

An invalid axis name was specified.aa....aa

KECX03036-E

Unknown nodetype: aa....aa

This is an invalid node type. aa....aa

KECX03037-E

Pattern literal (aa....aa) needs to be quoted!

The literal (aa....aa) pattern must be enclosed within quotation marks.

KECX03038-E

aa....aa could not be formatted to a number!

aa....aa could not be formatted to a number.

KECX03039-E

Could not create XML TransformerFactory Liaison: aa....aa

XML TransformerFactory Liaison could not be created. aa....aa

KECX03040-E

Error! Did not find xpath select expression (-select).

This is an error. The xpath select expression (-select) could not be found.

KECX03041-E

ERROR! Could not find ENDOP after OP_LOCATIONPATH

This is an error. ENDOP could not be found after OP_LOCATIONPATH.

KECX03042-E

Error occurred!

An error occurred.

KECX03043-E

VariableReference given for variable out of context or without definition! Name = aa....aa

VariableReference was specified for a variable either out of context or without a definition. Name = aa....aa

KECX03044-E

Only child:: and attribute:: axes are allowed in match patterns! Offending axes = aa....aa

Only child:: and attribute:: axes are allowed in matching patterns. aa....aaaxis is not allowed.

KECX03045-E

key() has an incorrect number of arguments.

The number of arguments of key() is invalid.

KECX03046-E

The count function should take one argument!

You can use only one argument with the count function.

KECX03047-E

Could not find function: aa....aa

The function: aa....aa could not be found.

KECX03048-E

Unsupported encoding: aa....aa

This is an unsupported encoding aa....aa.

KECX03049-E

Problem occurred in DTM in getNextSibling... trying to recover

A problem occurred in DTM of getNextSibling. An attempt is being made to recover.

KECX03050-E

Programmer error: EmptyNodeList can not be written to.

This is a programmer error. An attempt to write to EmptyNodeList has failed.

KECX03051-E

setDOMFactory is not supported by XPathContext!

SetDOMFactory is not supported by XpathContext.

KECX03052-E

Prefix must resolve to a namespace: aa....aa

The prefix must be resolved in a namespace. aa....aa

KECX03053-E

parse (InputSource source) not supported in XPathContext! Can not open aa....aa

Parsing (InputSource source) is not supported by XpathContext. Cannot open aa....aa.

KECX03057-E

SAX API characters(char ch[]... not handled by the DTM!

SAX API characters (char ch[]... are not processed by DTM.

KECX03058-E

ignorableWhitespace(char ch[]... not handled by the DTM!

IgnorableWhitespace (char ch[]... is not processed by DTM.

KECX03059-E

DTMLiaison can not handle nodes of type aa....aa

DTMLiaison cannot process nodes of type aa....aa.

KECX03060-E

DOM2Helper can not handle nodes of type aa....aa

DOM2Helper cannot process nodes of type aa....aa.

KECX03061-E

DOM2Helper.parse error: SystemID - aa....aa line - bb....bb

DOM2Helper.parse error: SystemID - aa....aa Line no. - bb....bb

KECX03062-E

DOM2Helper.parse error

This is a DOM2Helper.parse error.

KECX03065-E

Invalid UTF-16 surrogate detected: aa....aa ?

An invalid UTF-16 surrogate is detected: aa....aa?

KECX03066-E

IO error

An I/O error occurred.

KECX03067-E

Cannot create url for: aa....aa

The URL for aa....aa cannot be created.

KECX03068-E

In XPath.readObject: aa....aa

XPath.readObject exists. aa....aa

KECX03069-E

function token not found.

The function token is not found.

KECX03071-E

Can not deal with XPath type: aa....aa

The XPath type aa....aa cannot be processed.

KECX03072-E

This NodeSet is not mutable

This NodeSet is not variable.

KECX03073-E

This NodeSetDTM is not mutable

This NodeSetDTM is not variable.

KECX03074-E

Variable not resolvable: aa....aa

This is an un-resolvable variable. aa....aa

KECX03075-E

Null error handler

The error handler is null.

KECX03076-E

Programmer's assertion: unknown opcode: aa....aa

The programmer specification is an unknown option code. aa....aa

KECX03078-E

rtf() not supported by XRTreeFragSelectWrapper

rtf() is not supported by XRTreeFragSelectWrapper.

KECX03079-E

asNodeIterator() not supported by XRTreeFragSelectWrapper

asNodeIterator() is not supported by XRTreeFragSelectWrapper.

KECX03080-E

fsb() not supported for XStringForChars

XstringForChars does not support fsb().

KECX03081-E

Could not find variable with the name of aa....aa

A variable named aa....aa could not be found.

KECX03082-E

XStringForChars can not take a string for an argument

A character string cannot be used as an argument in XstringForChars.

KECX03083-E

The FastStringBuffer argument can not be null

The FastStringBuffer argument cannot be null.

KECX03085-E

Variable accessed before it is bound!

A variable was accessed before it could be defined.

KECX03086-E

XStringForFSB can not take a string for an argument!

XStringForFSB cannot take a string for an argument.

KECX03087-E

!!!! Error! Setting the root of a walker to null!!!

This is an error. The walker root will be set to null.

KECX03088-E

This NodeSetDTM can not iterate to a previous node!

This NodeSetDTM cannot iterate to the previous node.

KECX03089-E

This NodeSet can not iterate to a previous node!

This NodeSet cannot iterate to the previous node.

KECX03090-E

This NodeSetDTM can not do indexing or counting functions!

This NodeSetDTM cannot perform the indexing or counting functions.

KECX03091-E

This NodeSet can not do indexing or counting functions!

This NodeSet cannot perform the indexing or counting functions.

KECX03092-E

Can not call setShouldCacheNodes after nextNode has been called!

setShouldCacheNodes cannot be called after calling nextNode.

KECX03093-E

aa....aa only allows bb....bb arguments

Only bb....bb arguments are allowed for aa....aa.

KECX03094-E

Programmer's assertion in getNextStepPos: unknown stepType: aa....aa

The programmer's assertion in getNextStepPos is an unknown stepType aa....aa.

KECX03095-E

A relative location path was expected following the '/' or '//' token.

A relative location path is required after the / or // token.

KECX03096-E

A location path was expected, but the following token was encountered: aa....aa

A location path was required, but the following token was detected. aa....aa

KECX03097-E

A location step was expected following the '/' or '//' token.

A location step is required after the / or // token.

KECX03098-E

A node test that matches either NCName:* or QName was expected.

A node test that matches either NCName:* or QName is required.

KECX03099-E

A step pattern was expected, but '/' was encountered.

A step pattern was required, but / was detected.

KECX03100-E

A relative path pattern was expected.

A relative path pattern is required.

KECX03103-E

The XPathResult of XPath expression 'aa....aa' has an XPathResultType of bb....bb which cannot be converted to a boolean.

The XPathResult of the XPath expression aa....aa contains XPathResultType of bb....bb that cannot be converted to a boolean.

KECX03104-E

The XPathResult of XPath expression 'aa....aa' has an XPathResultType of bb....bb which cannot be converted to a single node. The method getSingleNodeValue applies only to types ANY_UNORDERED_NODE_TYPE and FIRST_ORDERED_NODE_TYPE.

The XPathResult of the XPath expression aa....aa contains XPathResultType of bb....bb that cannot be converted to a single node. The getSingleNodeValue method is applicable only to the ANY_UNORDERED_NODE_TYPE and FIRST_ORDERED_NODE_TYPE types.

KECX03105-E

The method getSnapshotLength cannot be called on the XPathResult of XPath expression 'aa....aa' because its XPathResultType is bb....bb. This method applies only to types UNORDERED_NODE_SNAPSHOT_TYPE and ORDERED_NODE_SNAPSHOT_TYPE.

The getSnapshotLength method cannot be called in XPathResult of the XPath expression aa....aa because its XPathResultType is bb....bb. This method is applicable only to the UNORDERED_NODE_SNAPSHOT_TYPE and ORDERED_NODE_SNAPSHOT_TYPE types.

KECX03106-E

The method iterateNext cannot be called on the XPathResult of XPath expression 'aa....aa' because its XPathResultType is bb....bb. This method applies only to types UNORDERED_NODE_ITERATOR_TYPE and ORDERED_NODE_ITERATOR_TYPE.

The iterateNext method cannot be called in XPathResult of the XPath expression aa....aa because its XPathResultType is bb....bb. This method is applicable only to the UNORDERED_NODE_ITERATOR_TYPE and ORDERED_NODE_ITERATOR_TYPE types.

KECX03107-E

Document mutated since result was returned. Iterator is invalid.

The document was changed after the result was returned. The iterator is invalid.

KECX03108-E

Invalid XPath type argument: aa....aa

This is an invalid XPath type argument. aa....aa

KECX03109-E

Empty XPath result object

This is an empty XPath result object.

KECX03110-E

The XPathResult of XPath expression 'aa....aa' has an XPathResultType of bb....bb which cannot be coerced into the specified XPathResultType of cc....cc.

The XPathResult of the XPath expression aa....aa has XPathResultType of bb....bb that cannot be coerced into the specified XPathResultType of cc....cc.

KECX03111-E

Unable to resolve prefix with null prefix resolver.

A prefix cannot be resolved with a null prefix resolver.

KECX03112-E

The XPathResult of XPath expression 'aa....aa' has an XPathResultType of bb....bb which cannot be converted to a string.

XPathResult of the XPath expression aa....aa has XPathResultType of bb....bb that cannot be converted to a character string.

KECX03113-E

The method snapshotItem cannot be called on the XPathResult of XPath expression 'aa....aa' because its XPathResultType is bb....bb. This method applies only to types UNORDERED_NODE_SNAPSHOT_TYPE and ORDERED_NODE_SNAPSHOT_TYPE.

The snapshotItem method cannot be called in XPathResult of the XPath expression aa....aa because its XPathResultType is bb....bb. This method is applicable only to the UNORDERED_NODE_SNAPSHOT_TYPE and ORDERED_NODE_SNAPSHOT_TYPE types.

KECX03114-E

Context node does not belong to the document that is bound to this XPathEvaluator.

The context node does not belong to a document that is bound to this XPathEvaluator.

KECX03115-E

The context node type is not supported.

The context node type is not supported.

KECX03116-E

Unknown error in XPath.

An unknown error occurred in XPath.

KECX03117-E

detach() not supported by XRTreeFragSelectWrapper

detach() is not supported by XRTreeFragSelectWrapper.

KECX03118-E

num() not supported by XRTreeFragSelectWrapper

num() is not supported by XRTreeFragSelectWrapper.

KECX03119-E

xstr() not supported by XRTreeFragSelectWrapper

xstr() is not supported by XRTreeFragSelectWrapper.

KECX03120-E

str() not supported by XRTreeFragSelectWrapper

str() is not supported by XRTreeFragSelectWrapper.

KECX03121-E

A location path was expected, but the end of the XPath expression was found instead.

A location path was expected, but the end of the XPath expression was found.

KECX03122-E

The XPathResult of XPath expression 'aa....aa' has an XPathResultType of bb....bb which cannot be converted to a number

The XPathResult of the XPath expression aa....aa has XPathResultType of bb....bb that cannot be converted to a number.

KECX03123-E

Extension function: 'aa....aa' can not be invoked when the XMLConstants.FEATURE_SECURE_PROCESSING feature is set to true.

Extension function: aa....aa cannot be invoked when the XMLConstants.FEATURE_SECURE_PROCESSING feature is set to true.

KECX03124-E

resolveVariable for variable aa....aa returning null

resolveVariable of the variable aa....aa has returned null.

KECX03125-E

UnSupported Return Type : aa....aa

Return type that is not supported: aa....aa

KECX03126-E

Source and/or Return Type can not be null

The Source type or Return type, or both cannot be null.

KECX03127-E

Source and/or Return Type can not be null

The Source type or Return type, or both cannot be null.

KECX03128-E

aa....aa argument can not be null

The aa....aa argument cannot be null.

KECX03129-E

aa....aa#isObjectModelSupported( String objectModel ) cannot be called with objectModel == null

aa....aa#isObjectModelSupported ( String objectModel ) cannot be called simultaneously with objectModel == null.

KECX03130-E

aa....aa#isObjectModelSupported( String objectModel ) cannot be called with objectModel == \"\"

aa....aa#isObjectModelSupported (String objectModel) cannot be called simultaneously with objectModel == \"\".

KECX03131-E

Trying to set a feature with a null name: aa....aa#setFeature( null, bb....bb)

An attempt was made to set a feature with a null name: aa....aa#setFeature( null, bb....bb)

KECX03132-E

Trying to set the unknown feature \"aa....aa\":bb....bb#setFeature(aa....aa,cc....cc)

An attempt was made to set an unknown feature \"aa....aa\": bb....bb#setFeature(aa....aa,cc....cc)

KECX03133-E

Trying to get a feature with a null name: aa....aa#getFeature(null)

An attempt was made to acquire a feature with a null name: aa....aa#getFeature(null)

KECX03134-E

Trying to get the unknown feature \"aa....aa\":bb....bb#getFeature(aa....aa)

An attempt was made to acquire an unknown feature \"aa....aa\": bb....bb#getFeature(aa....aa)

KECX03135-E

Attempting to set a null XPathFunctionResolver:aa....aa#setXPathFunctionResolver(null)

An attempt was made to set a null XpathFunctionResolver: aa....aa#setXPathFunctionResolver(null)

KECX03136-E

Attempting to set a null XPathVariableResolver:aa....aa#setXPathVariableResolver(null)

An attempt was made to set a null XPathVariableResolver: aa....aa#setXPathVariableResolver(null)

KECX03306-E

This NodeSetDTM can not do indexing or counting functions!

This NodeSetDTM cannot perform indexing or counting functions.

KECX03307-E

Programmer's Error! putDocumentInCache found reparse of doc: aa....aa

This is a programmer's error. Re-parsing of doc was found by putDocumentInCache. aa....aa

KECX03314-E

Could not load any resource bundles.

No resource bundle can be loaded.

KECX03315-E

Error! Function.execute should not be called!

This is an error. Function.execute cannot be called.

KECX03316-W

Warning: popContextNodeList when stack is empty!

Warning: This is popContextNodeList when the stack is empty.

KECX03501-W

locale name in the format-number function not yet handled!

The locale name is not yet processed in the format-number function.

KECX03502-W

XSL Property not supported: aa....aa

The XSL property aa....aa is not supported.

KECX03503-W

Do not currently do anything with namespace aa....aa in property: bb....bb

Currently, nothing is executed in the namespace aa....aa of the property bb....bb.

KECX03504-W

SecurityException when trying to access XSL system property: aa....aa

SecurityException occurred when the XSL system property aa....aa was accessed.

KECX03505-W

Old syntax: quo(...) is no longer defined in XPath.

Old syntax: quo(...) is not defined in XPath.

KECX03506-W

XPath needs a derived object to implement nodeTest!

A derived object is required in XPath to implement nodeTest.

KECX03507-W

function token not found.

The function token is not found.

KECX03508-W

Could not find function: aa....aa

The function: aa....aa could not be found.

KECX03509-W

Can not make URL from: aa....aa

The URL cannot be created from aa....aa.

KECX03510-W

-E option not supported for DTM parser

The -E option is not supported for DTM parser.

KECX03511-W

VariableReference given for variable out of context or without definition! Name = aa....aa

VariableReference was specified for a variable either out of context or without a definition. Name = aa....aa

KECX03512-W

Unsupported encoding: aa....aa

Unsupported encoding: aa....aa

KECX03701-E

Parameter to createMessage was out of bounds

A parameter to createMessage was out of the bounds.

KECX03702-E

Exception thrown during messageFormat call

An exception was thrown during the messageFormat call.

KECX03901-E

A predicate or a location step is applicable to only a NodeSet.

A predicate or a location step is applicable only to a NodeSet.

KECX03902-E

A XPathVariableResolver is not set.

A variable resolver is not set.

KECX03903-E

A XPathFunctionResolver is not set.

A function resolver is not set.

11.5 Messages from KECX04001 to KECX04999

This section describes the messages from KECX04001 to KECX04999 that are output by Cosminexus XML Processor.

KECX04012-E

Configuration Error

This is the Configuration error.

KECX04014-E

Coding error; Don't try to mark/rewind an indexed DTM

This is a coding error. Do not mark or rewind a DTM for which an index is coded.

KECX04016-E

Cannot construct URI with null/empty scheme!

A URI cannot be constructed with a null or empty schema.

KECX04017-E

Cannot construct URI with null/empty scheme-specific part!

A URI cannot be constructed with a null or an empty scheme-specific part.

KECX04018-E

aa....aa is invalid. Port should only contain digits!

aa....aa is invalid. Use only numeric characters to specify a port.

KECX04019-E

Cannot initialize path from null string!

A path cannot be initialized with a null character string.

KECX04020-E

Query string contains invalid escape sequence!

The query string contains an invalid escape sequence.

KECX04021-E

Query string contains invalid character:aa....aa

The query string contains an invalid character. aa....aa

KECX04022-E

Fragment contains invalid escape sequence!

The fragment contains an invalid escape sequence. aa....aa

KECX04023-E

Fragment contains invalid character:aa....aa

Fragment contains invalid characters.aa....aa

KECX04024-E

Userinfo cannot be set when host is null!

Userinfo cannot be specified unless the host is specified.

KECX04025-E

Userinfo contains invalid escape sequence!

Userinfo contains an invalid escape sequence. aa....aa

KECX04026-E

Userinfo contains invalid character:aa....aa

Userinfo contains invalid characters.aa....aa

KECX04027-E

Query string can only be set for a generic URI!

The query string can only be set in a general URI.

KECX04028-E

Query string cannot be set when path is null!

The query string cannot be set when the path is null.

KECX04029-E

Query string contains invalid character!

The query string contains invalid characters.

KECX04030-E

Could not load any resource bundles.

No resource bundle can be loaded.

KECX04038-W

*****WARNING: ChunkedIntArray(aa....aa) wasting bb....bb words per slot

Warning: ChunkedIntArray (aa....aa) consumes bb....bb words per slot.

KECX04039-W

Can not absolutize URL: aa....aa

This URL cannot be changed to an absolute URL. aa....aa

KECX04040-E

CODING ERROR in Source Location: aa....aa != bb....bb

This is a coding error of the source location. aa....aa != bb....bb

KECX04046-E

DOM ERROR! class: aa....aa

This is the DOM error. Class aa....aa

KECX04047-E

Could not load any resource bundles.aa....aa

No resource bundle can be loaded. aa....aa

KECX04101-E

Function not supported!

The function is not supported.

KECX04102-E

Cannot overwrite cause

cause cannot be overwritten.

KECX04103-E

No default implementation found

The default implementation is not found.

KECX04104-E

ChunkedIntArray(aa....aa) not currently supported

Currently, ChunkedIntArray (aa....aa) is not supported.

KECX04105-E

Offset bigger than slot

The offset is bigger than the slot.

KECX04106-E

Coroutine not available, id=aa....aa

Coroutine cannot be used. id = aa....aa

KECX04107-E

CoroutineManager received co_exit() request

CoroutineManager received the co_exit() request.

KECX04108-E

co_joinCoroutineSet() failed

co_joinCoroutineSet() has failed.

KECX04109-E

Coroutine parameter error (aa....aa)

This is the Coroutine parameter error. (aa....aa)

KECX04110-E

UNEXPECTED: Parser doTerminate answers aa....aa

Unexpected: The parser doTerminate is answering aa....aa.

KECX04111-E

parse may not be called while parsing

parse cannot be called during parsing.

KECX04112-E

Error: typed iterator for axis aa....aa not implemented

Error: The typed iterator for the axis aa....aa is not implemented.

KECX04113-E

Error: iterator for axis aa....aa not implemented

Error: The iterator for the axis aa....aa is not implemented.

KECX04114-E

Iterator clone not supported

Copying the iterator is not supported.

KECX04115-E

Unknown axis traversal type: aa....aa

This is an unknown axis traverse type. aa....aa

KECX04116-E

Axis traverser not supported: aa....aa

The axis traverser is not supported. aa....aa

KECX04117-E

No more DTM IDs are available

There are no more usable DTM IDs.

KECX04118-E

Not supported: aa....aa

Not supported. aa....aa

KECX04119-E

Node must be non-null for getDTMHandleFromNode

The node of getDTMHandleFromNode must not be null.

KECX04120-E

Could not resolve the node to a handle

The node could not be resolved to a handle.

KECX04121-E

startParse may not be called while parsing

startParse must not be called during parsing.

KECX04122-E

startParse needs a non-null SAXParser

An SAXParser other than null is required for startParse.

KECX04123-E

could not initialize parser with

The parser could not be initialized with the following.

KECX04124-E

exception creating new instance for pool

An exception occurred while creating new instances for the pool.

KECX04125-E

Path contains invalid escape sequence

The path contains an invalid escape sequence.

KECX04126-E

Scheme is required!

A scheme is required.

KECX04127-E

No scheme found in URI: aa....aa

The scheme is not found in the URI aa....aa.

KECX04128-E

No scheme found in URI

The scheme is not found in the URI.

KECX04129-E

Path contains invalid character: aa....aa

The path contains an invalid character aa....aa.

KECX04130-E

Cannot set scheme from null string

The scheme cannot be set from a null character string.

KECX04131-E

The scheme is not conformant.

The scheme does not match.

KECX04132-E

Host is not a well formed address

The host is not a well-formed address.

KECX04133-E

Port cannot be set when host is null

The port cannot be set unless the host is specified.

KECX04134-E

Invalid port number

This is an invalid port number.

KECX04135-E

Fragment can only be set for a generic URI

A fragment can only be set for a general URI.

KECX04136-E

Fragment cannot be set when path is null

The fragment cannot be set if the path is null.

KECX04137-E

Fragment contains invalid character

The fragment contains an invalid character.

KECX04138-E

Parser is already in use

The parser is already in use.

KECX04139-E

Cannot change aa....aa bb....bb while parsing

aa....aa bb....bb cannot be changed during parsing.

KECX04140-E

Self-causation not permitted

Self-causation is not allowed.

KECX04141-E

Userinfo may not be specified if host is not specified

Userinfo cannot be specified unless the host is specified.

KECX04142-E

Port may not be specified if host is not specified

The port cannot be specified unless the host is specified.

KECX04143-E

Query string cannot be specified in path and query string

A Query string cannot be specified in the path and Query string.

KECX04144-E

Fragment cannot be specified in both the path and fragment

A fragment cannot be specified in both the path and fragment.

KECX04145-E

Cannot initialize URI with empty parameters

The URI cannot be initialized with empty parameters.

KECX04146-E

Method not yet supported

The method is not supported.

KECX04147-E

IncrementalSAXSource_Filter not currently restartable

Currently, IncrementalSAXSource_Filter cannot be restarted.

KECX04148-E

XMLReader not before startParse request

XMLReader is not before the startParse request.

KECX04149-E

Axis traverser not supported: aa....aa

The axis traverser is not supported. aa....aa

KECX04150-E

ListingErrorHandler created with null PrintWriter!

ListingErrorHandler was created with null PrintWriter.

KECX04151-E

SystemId Unknown

SystemId is unknown.

KECX04152-E

Location of error unknown

The location of the error is unknown.

KECX04153-E

Prefix must resolve to a namespace: aa....aa

The prefix must be resolved to a namespace. aa....aa

KECX04154-E

createDocument() not supported in XPathContext!

createDocument() is not supported in XPathContext.

KECX04155-E

Attribute child does not have an owner document!

The attribute child does not have an owner document.

KECX04156-E

Attribute child does not have an owner document element!

The attribute child does not have an owner document element.

KECX04157-E

Warning: can't output text before document element! Ignoring...

Warning: Text cannot be output before a document element. Ignoring...

KECX04158-E

Can't have more than one root on a DOM!

A DOM cannot have more than one root.

KECX04159-E

Argument 'localName' is null

The argument localName is null.

KECX04160-E

Localname in QNAME should be a valid NCName

The local name within QNAME must be a valid NCName.

KECX04161-E

Prefix in QNAME should be a valid NCName

The prefix within QNAME must be a valid NCName.

KECX04162-E

Parameter to createMessage was out of bounds

A parameter to createMessage was out of bounds.

KECX04163-E

Exception thrown during messageFormat call

An exception was thrown during the messageFormat call.

KECX04164-E

The serializer class 'aa....aa' does not implement org.xml.sax.ContentHandler.

The serializer class aa....aa does not implement org.xml.sax.ContentHandler.

KECX04165-E

The resource [ aa....aa ] could not be found. bb....bb

The resource aa....aa was not found. bb....bb

KECX04166-E

The resource [ aa....aa ] could not load: bb....bb cc....cc dd....dd

The resource aa....aa could not load the following: bb....bb cc....cc dd....dd

KECX04167-E

Buffer size <=0

The buffer size is less than or equal to 0.

KECX04168-E

Invalid UTF-16 surrogate detected: aa....aa ?

An invalid UTF-16 surrogate is detected. aa....aa

KECX04169-E

IO error

An I/O error occurred.

KECX04170-E

Cannot add attribute aa....aa after child nodes or before an element is produced. Attribute will be ignored.

The attribute aa....aa cannot be added after a child node or before expressing an element. The attribute will be ignored.

KECX04171-E

Namespace for prefix 'aa....aa' has not been declared.

The namespace for the prefix aa....aa is not declared.

KECX04172-E

Attribute 'aa....aa' outside of element.

The attribute aa....aa is outside the element.

KECX04173-E

Namespace declaration 'aa....aa'='bb....bb' outside of element.

The namespace declaration aa....aa=bb....bb is outside the element.

KECX04174-E

Could not load 'aa....aa' (check CLASSPATH), now using just the defaults

aa....aa could not be loaded (check CLASSPATH). Currently, just the defaults are being used.

KECX04175-E

Could not load the property file 'aa....aa' for output method 'bb....bb' (check CLASSPATH)

The property file aa....aa of the output method bb....bb could not be loaded (check CLASSPATH).

KECX04176-E

Attempt to output character of integral value aa....aa that is not represented in specified output encoding of bb....bb.

The character that is attempted to be output with the integer value aa....aa cannot be represented in the output encoding specified by bb....bb.

KECX04177-E

Invalid port number

This is an invalid port number.

KECX04178-E

Port cannot be set when host is null

The port cannot be set if the host is null.

KECX04179-E

Host is not a well formed address

The host is not a well-formed address.

KECX04180-E

The scheme is not conformant.

The scheme is not compatible.

KECX04181-E

Cannot set scheme from null string

The scheme cannot be set from a null character string.

KECX04182-E

Path contains invalid escape sequence

The path contains an invalid escape sequence.

KECX04183-E

Path contains invalid character: aa....aa

The path contains an invalid character: aa....aa

KECX04184-E

Fragment contains invalid character

The fragment contains an invalid character.

KECX04185-E

Fragment cannot be set when path is null

The fragment cannot be set when the path is null.

KECX04186-E

Fragment can only be set for a generic URI

The fragment can only be set in a general URI.

KECX04187-E

No scheme found in URI

The URI does not contain a scheme.

KECX04188-E

Cannot initialize URI with empty parameters

The URI cannot be initialized with empty parameters.

KECX04189-E

Fragment cannot be specified in both the path and fragment

A fragment cannot be specified in both the path and fragment.

KECX04190-E

Query string cannot be specified in path and query string

A query string cannot be specified in the path and query string.

KECX04191-E

Port may not be specified if host is not specified

The port cannot be specified unless the host is specified.

KECX04192-E

Userinfo may not be specified if host is not specified

Userinfo cannot be specified unless the host is specified.

KECX04193-W

Warning: The version of the output document is requested to be 'aa....aa'. This version of XML is not supported. The version of the output document will be '1.0'.

Warning: aa....aa is requested as the version of the output document. The XML of this version is not supported. The version of the output document will be 1.0.

KECX04194-E

Scheme is required!

A scheme is required.

KECX04195-E

The Properties object passed to the SerializerFactory does not have a 'aa....aa' property.

The Properties object passed to SerializerFactory does not have a aa....aa property.

KECX04196-W

Warning: The encoding 'aa....aa' is not supported by the Java runtime.

Warning: Encoding aa....aa is not supported by Java runtime.

KECX04197-E

The message key 'aa....aa' is not in the message class 'bb....bb'

The message key aa....aa does not exist in the message class bb....bb.

KECX04198-E

The format of message 'aa....aa' in message class 'bb....bb' failed.

The format of message aa....aa in the message class bb....bb has failed.

KECX04199-E

Name cannot start with a colon

A name cannot start with a colon (:).

KECX04301-E

The error message corresponding to the message key can not be found.

An error message corresponding to the message key cannot be found.

KECX04302-E

An internal error occurred while formatting the following message:\n

An internal error occurred while formatting the following message: \n

KECX04303-E

The schema language specified cannot be null.

The specified schema language cannot be null.

KECX04304-E

The schema language specified cannot have a length of zero characters.

The specified schema language cannot have a length of zero characters.

KECX04305-E

The Source array parameter cannot be null.

The Source array parameter cannot be null.

KECX04306-E

The Source array parameter cannot contain any items that are null.

The Source array parameter cannot contain items that are null.

KECX04307-E

Source parameter of type 'aa....aa' is not recognized this SchemaFactory.

The Source parameter of type aa....aa does not recognize this SchemaFactory.

KECX04308-E

Source parameter cannot be null.

The Source parameter cannot be null.

KECX04309-E

Source parameter of type 'aa....aa' is not accepted by this validator.

The Source parameter of type aa....aa cannot be accepted by this validator.

KECX04310-E

Source parameter of type 'aa....aa' is not compatible with result parameter of type 'bb....bb'.

The Source parameter of type aa....aa is not compatible with the result parameter of type bb....bb.

KECX04311-E

A TypeInfoProvider cannot be queried outside of a startElement callback.

TypeInfoProvider cannot be queried outside the startElement callback.

KECX04312-E

The feature name cannot be null.

The feature name cannot be null.

KECX04313-E

The property name cannot be null.

The property name cannot be null.

KECX04314-E

The SAXSource specified contains no InputSource.

The specified SAXSource does not have InputSource.

KECX04401-E

The error message corresponding to the message key can not be found.

The error message corresponding to the message key cannot be found.

KECX04402-E

An internal error occurred while formatting the following message:\n

An internal error occurred while formatting the following message: \n

KECX04403-E

XPointerProcessingError: An error occurred while processing the XPointer expression.

XPointerProcessingError: An error occurred while processing the XPointer expression.

KECX04404-E

InvalidXPointerToken: The XPointer expression contains the invalid token 'aa....aa'

InvalidXPointerToken: The XPointer expression contains the invalid token aa....aa.

KECX04405-E

InvalidXPointerExpression: The XPointer expression 'aa....aa' is invalid.

InvalidXPointerExpression: The XPointer expression aa....aa is invalid.

KECX04406-E

MultipleShortHandPointers: The XPointer expression 'aa....aa' is invalid. It has more than one ShortHand Pointer.

MultipleShortHandPointers: The XPointer expression aa....aa is invalid. The expression contains more than one ShortHand Pointer.

KECX04407-E

SchemeDataNotFollowedByCloseParenthesis: The XPointer expression 'aa....aa' is invalid. The SchemeData was not followed by a ')' character.

SchemeDataNotFollowedByCloseParenthesis: The XPointer expression aa....aa is invalid. SchemeData is not followed by a right parenthesis ')'.

KECX04408-W

SchemeUnsupported: The XPointer scheme 'aa....aa' is not supported.

SchemeUnsupported: The XPointer scheme aa....aa is not supported.

KECX04409-E

InvalidShortHandPointer: The NCName of the ShortHand Pointer 'aa....aa' is invalid.

InvalidShortHandPointer: The NCName of the ShortHand Pointer aa....aa is invalid.

KECX04410-E

UnbalancedParenthesisInXPointerExpression: The XPointer expression 'aa....aa' is invalid. The number of open parenthesis 'bb....bb' is not equal to the number of close parenthesis 'cc....cc'.

UnbalancedParenthesisInXPointerExpression: The XPointer expression aa....aa is invalid. The number of open parenthesis bb....bb is not equal to the number of close parenthesis cc....cc.

KECX04411-E

InvalidSchemeDataInXPointer: The XPointer expression 'aa....aa' contains invalid SchemeData.

InvalidSchemeDataInXPointer: The XPointer expression aa....aa contains invalid SchemeData.

KECX04412-E

InvalidElementSchemeToken: The element() scheme XPointer expression contains the invalid token 'aa....aa'

InvalidElementSchemeToken: The element() scheme XPointer expression contains the invalid token aa....aa.

KECX04413-E

InvalidElementSchemeXPointer: The Element Scheme XPointer expression 'aa....aa' is invalid.

InvalidElementSchemeXPointer: The Element Scheme XPointer expression aa....aa is invalid.

KECX04414-E

XPointerElementSchemeProcessingError: An error occurred while processing the XPointer element() Scheme expression.

XPointerElementSchemeProcessingError: An error occurred while processing the XPointer element() Scheme expression.

KECX04415-E

InvalidNCNameInElementSchemeData: The element() Scheme contains a ShortHand Pointer 'aa....aa' with an invalid NCName.

InvalidNCNameInElementSchemeData: The element() Scheme contains ShortHand Pointer aa....aa with an invalid NCName.

KECX04416-E

InvalidChildSequenceCharacter: The element() Scheme contains an invalid child sequence character 'aa....aa'.

InvalidChildSequenceCharacter: The element() Scheme contains an invalid child sequence character aa....aa.

11.6 Messages from KECX06001 to KECX06999

This section describes the messages from KECX06001 to KECX06999 that are output by Cosminexus XML Processor.

KECX06001-E

The error message corresponding to the message key can not be found.

The error message corresponding to the message key cannot be found.

KECX06002-E

An internal error occurred while formatting the following message:

An internal error occurred while formatting the following message:

KECX06003-E

Internal error: aa....aa.

An internal error occurred.aa....aa

KECX06004-E

Whitespace facet value is not available for the union simpleType 'aa....aa'

A space facet value cannot be used in the union simple type aa....aa.

KECX06005-W

One of the grammar(s) returned from the user's grammar pool is in conflict with another grammar.

One of the syntax returned from the user's syntax pool conflicts with another syntax.

KECX06006-E

Identity Constraint error (cvc-identity-constraint.4.2.1): element "aa....aa" has a key with no value.

This is an identity constraint error (cvc-identity-constraint.4.2.1). A key without a value is specified in the element aa....aa.

KECX06007-E

Duplicate match in scope for field "aa....aa".

There is a duplicate match in the scope for the field aa....aa.

KECX06008-E

Duplicate key value [aa....aa] declared for identity constraint of element "bb....bb".

The value aa....aa of a key is duplicated in the identity constraint declaration of the element bb....bb.

KECX06009-E

Duplicate unique value [aa....aa] declared for identity constraint of element "bb....bb".

The unique value aa....aa is duplicated in the identity constraint declaration of the element bb....bb.

KECX06010-E

Identity constraint error: field "aa....aa" matches more than one value within the scope of its selector; fields must match unique values.

An identity constraint error occurred. The field aa....aa matches more than one value within the scope of its selector. Fields must have unique values.

KECX06011-E

The content of this element is not equivalent to the value of the "fixed" attribute in the element's declaration in the schema.

The contents of the element are not equivalent to the value of the fixed attribute in the element declaration within the schema.

KECX06012-E

Identity Constraint error (cvc-identity-constraint.4.2.3): element "aa....aa" has a key which matches an element which has nillable set to true.

This is an identity constraint error (cvc-identity-constraint.4.2.3). A key matching an element in which true is set for the empty element specification nillable is specified in the element aa....aa.

KECX06013-E

Not enough values specified for <key name="bb....bb"> identity constraint specified for element "aa....aa".

Not enough values are specified for the <key name=bb....bb> identity constraint definition of the element aa....aa.

KECX06014-E

Key 'aa....aa' with value 'bb....bb' not found for identity constraint of element 'cc....cc'.

The key aa....aa, for which the value bb....bb is specified, does not exist in the identity constraint definition of the element cc....cc.

KECX06015-E

Not enough values specified for <keyref name="bb....bb"> identity constraint specified for element "aa....aa".

Not enough values are specified for the <keyref name=bb....bb> identity constraint definition of the element aa....aa.

KECX06016-E

Identity Constraint error: identity constraint "aa....aa" has a keyref which refers to a key or unique that is out of scope.

An identity constraint error occurred. A keyref that references a key or unique out of scope is specified in the identity constraint aa....aa.

KECX06017-E

Key reference declaration "aa....aa" refers to unknown key with name "bb....bb".

The key reference definition aa....aa references an unknown key with the name bb....bb.

KECX06018-E

Not enough values specified for <unique> identity constraint specified for element "aa....aa".

Enough values are not specified for the <unique> identity constraint definition of the element aa....aa.

KECX06019-E

Internal identity constraint error; unknown field "aa....aa".

An internal identity constraint error. This is an unknown field aa....aa.

KECX06020-E

cvc-attribute.3: The value 'cc....cc' of attribute 'bb....bb' on element 'aa....aa' is not valid with respect to its type, 'dd....dd'.

The value cc....cc specified in the attribute bb....bb of element aa....aa is not valid with respect to its type dd....dd.

KECX06021-E

cvc-attribute.4: The value 'cc....cc' of attribute 'bb....bb' on element 'aa....aa' is not valid with respect to its fixed {value constraint}. The attribute must have a value of 'dd....dd'.

The value cc....cc specified in the attribute bb....bb of element aa....aa is not valid with respect to its fixed value constraint. The attribute must have a value of dd....dd.

KECX06022-E

cvc-complex-type.2.1: Element 'aa....aa' must have no character or element information item [children], because the type's content type is empty.

Text or child element information items cannot be specified in the element aa....aa because the content type of the type is empty.

KECX06023-E

cvc-complex-type.2.2: Element 'aa....aa' must have no element [children], and the value must be valid.

A child element cannot be specified in the element aa....aa. Furthermore, the value must be valid.

KECX06024-E

cvc-complex-type.2.3: Element 'aa....aa' cannot have character [children], because the type's content type is element-only.

Child text cannot be specified in the element aa....aa because the content type of the type is only element.

KECX06025-E

cvc-complex-type.2.4.a: Invalid content was found starting with element 'aa....aa'. One of 'bb....bb' is expected.

Contents beginning with the element aa....aa are invalid. One of bb....bb is expected.

KECX06026-E

cvc-complex-type.2.4.b: The content of element 'aa....aa' is not complete. One of 'bb....bb' is expected.

The element aa....aa is not complete. One of bb....bb is expected.

KECX06027-E

cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'aa....aa'.

An element declaration is required in an optional element definition, but the declaration for the element aa....aa is not found.

KECX06028-E

cvc-complex-type.2.4.d: Invalid content was found starting with element 'aa....aa'. No child element is expected at this point.

Contents beginning with the element aa....aa are invalid. No child element is expected at this point.

KECX06029-E

cvc-complex-type.3.1: Value 'cc....cc' of attribute 'bb....bb' of element 'aa....aa' is not valid with respect to the corresponding attribute use. Attribute 'bb....bb' has a fixed value of 'dd....dd'.

The value cc....cc specified in the attribute bb....bb of the element aa....aa is invalid. The attribute bb....bb has a fixed value of dd....dd.

KECX06030-E

cvc-complex-type.3.2.1: Element 'aa....aa' does not have an attribute wildcard for attribute 'bb....bb'.

The element aa....aa does not have an attribute wildcard for the attribute bb....bb.

KECX06031-E

cvc-complex-type.3.2.2: Attribute 'bb....bb' is not allowed to appear in element 'aa....aa'.

The attribute bb....bb cannot be specified in the element aa....aa.

KECX06032-E

cvc-complex-type.4: Attribute 'bb....bb' must appear on element 'aa....aa'.

The element aa....aa requires the attribute bb....bb.

KECX06033-E

cvc-complex-type.5.1: In element 'aa....aa', attribute 'bb....bb' is a Wild ID. But there is already a Wild ID 'cc....cc'. There can be only one.

The attribute bb....bb of the element aa....aa is a Wild ID. However, a Wild ID cc....cc already exists. Only one Wild ID can be specified.

KECX06034-E

cvc-complex-type.5.2: In element 'aa....aa', attribute 'bb....bb' is a Wild ID. But there is already an attribute 'cc....cc' derived from ID among the {attribute uses}.

The attribute bb....bb is a Wild ID in the element aa....aa. However, an attribute cc....cc, derived from ID, already exists among the attribute uses.

KECX06036-E

cvc-datatype-valid.1.2.1: 'aa....aa' is not a valid value for 'bb....bb'.

aa....aa is not a valid value for bb....bb.

KECX06037-E

cvc-datatype-valid.1.2.2: 'aa....aa' is not a valid value of list type 'bb....bb'.

aa....aa is not a valid list type for bb....bb.

KECX06038-E

cvc-datatype-valid.1.2.3: 'aa....aa' is not a valid value of union type 'bb....bb'.

aa....aa is not a valid union type for bb....bb.

KECX06039-E

cvc-elt.1: Cannot find the declaration of element 'aa....aa'.

The declaration for the element aa....aa is not found.

KECX06040-E

cvc-elt.2: The value of {abstract} in the element declaration for 'aa....aa' must be false.

False must be specified for the value of the attribute abstract in the element declaration for aa....aa.

KECX06041-E

cvc-elt.3.1: Attribute 'bb....bb' must not appear on element 'aa....aa', because the {nillable} property of 'aa....aa' is false.

The attribute bb....bb cannot be specified in the element aa....aa because the nillable property is false.

KECX06042-E

cvc-elt.3.2.1: Element 'aa....aa' cannot have character or element information [children], because 'bb....bb' is specified.

Text or element information cannot be specified in the element aa....aa because bb....bb is specified.

KECX06043-E

cvc-elt.3.2.2: There must be no fixed {value constraint} for element 'aa....aa', because 'bb....bb' is specified.

The element aa....aa cannot have a fixed value constraint as bb....bb is specified.

KECX06044-E

cvc-elt.4.1: The value 'cc....cc' of attribute 'bb....bb' of element 'aa....aa' is not a valid QName.

The value cc....cc of the attribute bb....bb of element aa....aa is not a valid QName.

KECX06045-E

cvc-elt.4.2: Cannot resolve 'bb....bb' to a type definition for element 'aa....aa'.

bb....bb cannot be resolved as the type definition for the element aa....aa.

KECX06046-E

cvc-elt.4.3: Type 'bb....bb' is not validly derived from the type definition, 'cc....cc', of element 'aa....aa'.

Type bb....bb is not a valid derivation from the type definition, cc....cc of the element aa....aa.

KECX06047-E

cvc-elt.5.1.1: {value constraint} 'cc....cc' of element 'aa....aa' is not a valid default value for type 'bb....bb'.

The value constraint cc....cc of the element aa....aa is not a valid default value for the type bb....bb.

KECX06048-E

cvc-elt.5.2.2.1: Element 'aa....aa' must have no element information item [children].

Child element information items cannot be specified in the element aa....aa.

KECX06049-E

cvc-elt.5.2.2.2.1: The value 'bb....bb' of element 'aa....aa' does not match the fixed {value constraint} value 'cc....cc'.

The value bb....bb of the element aa....aa does not match the value cc....cc of the fixed value constraint.

KECX06050-E

cvc-elt.5.2.2.2.2: The value 'bb....bb' of element 'aa....aa' does not match the {value constraint} value 'cc....cc'.

The value bb....bb of the element aa....aa does not match the value cc....cc of the value constraint.

KECX06051-E

cvc-enumeration-valid: Value 'aa....aa' is not facet-valid with respect to enumeration 'bb....bb'. It must be a value from the enumeration.

The value aa....aa is invalid for bb....bb that is specified in the enumeration facet. A value from enumeration must be specified.

KECX06052-E

cvc-fractionDigits-valid: Value 'aa....aa' has bb....bb fraction digits, but the number of fraction digits has been limited to cc....cc.

The number of fraction digits bb....bb of the value aa....aa exceeds the number of digits cc....cc specified in the fractionDigits facet.

KECX06053-E

cvc-id.1: There is no ID/IDREF binding for IDREF 'aa....aa'.

There is no ID or IDREF bound to IDREF aa....aa.

KECX06054-E

cvc-id.2: There are multiple occurrences of ID value 'aa....aa'.

There are multiple occurrences of the ID value aa....aa.

KECX06055-E

cvc-id.3: A field of identity constraint 'aa....aa' matched element 'bb....bb', but this element does not have a simple type.

A field of the identity constraint aa....aa matches the element bb....bb, but this element does not have a simple type.

KECX06056-E

cvc-length-valid: Value 'aa....aa' with length = 'bb....bb' is not facet-valid with respect to length 'cc....cc' for type 'dd....dd'.

The value aa....aa with a length of bb....bb does not match the length cc....cc specified in the length facet of the type dd....dd.

KECX06057-E

cvc-maxExclusive-valid: Value 'aa....aa' is not facet-valid with respect to maxExclusive 'bb....bb' for type 'cc....cc'.

The value aa....aa is out of the range of the value bb....bb specified in the maxExclusive facet of the type cc....cc.

KECX06058-E

cvc-maxInclusive-valid: Value 'aa....aa' is not facet-valid with respect to maxInclusive 'bb....bb' for type 'cc....cc'.

The value aa....aa is out of the range of the value bb....bb specified in the maxInclusive facet of the type cc....cc.

KECX06059-E

cvc-maxLength-valid: Value 'aa....aa' with length = 'bb....bb' is not facet-valid with respect to maxLength 'cc....cc' for type 'dd....dd'.

The length bb....bb of the value aa....aa is out of the range of the length cc....cc specified in the maxLength facet of type dd....dd.

KECX06060-E

cvc-minExclusive-valid: Value 'aa....aa' is not facet-valid with respect to minExclusive 'bb....bb' for type 'cc....cc'.

The value aa....aa is out of the range of the value bb....bb specified in the minExclusive facet of type cc....cc.

KECX06061-E

cvc-minInclusive-valid: Value 'aa....aa' is not facet-valid with respect to minInclusive 'bb....bb' for type 'cc....cc'.

The value aa....aa is out of the range of the value bb....bb specified in the minInclusive facet of type cc....cc.

KECX06062-E

cvc-minLength-valid: Value 'aa....aa' with length = 'bb....bb' is not facet-valid with respect to minLength 'cc....cc' for type 'dd....dd'.

The length bb....bb of the value aa....aa is out of the range of the length cc....cc specified in the minLength facet of type dd....dd.

KECX06063-E

cvc-pattern-valid: Value 'aa....aa' is not facet-valid with respect to pattern 'bb....bb' for type 'cc....cc'.

The value aa....aa does not match the pattern bb....bb specified in the pattern facet of the type cc....cc.

KECX06064-E

cvc-totalDigits-valid: Value 'aa....aa' has bb....bb total digits, but the number of total digits has been limited to cc....cc.

The number of digits bb....bb of the value aa....aa exceeds the number of digits cc....cc specified in the totalDigits facet.

KECX06065-E

cvc-type.2: The type definition cannot be abstract for element aa....aa.

The type definition for the element aa....aa cannot be an abstract type.

KECX06066-E

cvc-type.3.1.1: Element 'aa....aa' is a simple type, so it cannot have attributes, excepting those whose namespace name is identical to 'http://www.w3.org/2001/XMLSchema-instance' and whose [local name] is one of 'type', 'nil', 'schemaLocation' or 'noNamespaceSchemaLocation'. However, the attribute, 'bb....bb' was found.

Element aa....aa is a simple type, and therefore, it cannot have attributes other than those for which namespace name matches http://www.w3.org/2001/XMLSchema-instance and for which local name is one of type, nil, schemaLocation or noNamespaceSchemaLocation. However, the attribute bb....bb was found.

KECX06067-E

cvc-type.3.1.2: Element 'aa....aa' is a simple type, so it must have no element information item [children].

Element aa....aa is a simple type, and therefore, it cannot have children of element information items.

KECX06068-E

cvc-type.3.1.3: The value 'bb....bb' of element 'aa....aa' is not valid.

The value bb....bb of the element aa....aa is invalid.

KECX06069-E

schema_reference.4: Failed to read schema document 'aa....aa', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.

An attempt to read the schema document aa....aa has failed because the document was not found, the document could not be read, or the root element of the document was not <xsd:schema>.

KECX06070-E

src-annotation: <annotation> elements can only contain <appinfo> and <documentation> elements, but 'aa....aa' was found.

Only appinfo or documentation can be specified in the annotation element. However, aa....aa was found.

KECX06071-E

src-attribute.1: The properties 'default' and 'fixed' cannot both be present in attribute declaration 'aa....aa'. Use only one of them.

default and fixed cannot be specified concurrently in the attribute declaration aa....aa. Use only one of them.

KECX06072-E

src-attribute.2: : The property 'default' is present in attribute 'aa....aa', so the value of 'use' must be 'optional'.

As default is specified in the attribute aa....aa, optional must be specified in use.

KECX06073-E

src-attribute.3.1: One of ''ref'' or ''name'' must be present in a local attribute declaration.

Either ref or name is required in a local attribute declaration.

KECX06074-E

src-attribute.3.2: The content must match (annotation?) for the attribute reference 'aa....aa'.

Only an annotation can be specified in the contents of the attribute reference aa....aa.

KECX06075-E

src-attribute.4: Attribute 'aa....aa' has both a 'type' attribute and an anonymous 'simpleType' child. Only one of these is allowed for an attribute.

The attribute aa....aa has both a type attribute and an anonymous simpleType child. An attribute can have only one of these.

KECX06076-E

src-attribute_group.2: The intersection of wildcards is not expressible for attribute group 'aa....aa'.

The common sets of wildcards cannot be expressed for the attribute group aa....aa.

KECX06077-E

src-attribute_group.3: Circular definitions detected for attribute group 'aa....aa'. Recursively following attribute group references eventually leads back to itself.

The reference for the attribute group aa....aa has an infinite loop declaration. Recursively following attribute group references eventually leads back to itself.

KECX06078-E

src-ct.1: Complex Type Definition Representation Error for type 'aa....aa'. When <complexContent> is used, the base type must be a complexType. 'bb....bb' is a simpleType.

An error occurred in the complex type definition representation for the type aa....aa. When complexContent is used, the base type must be a complexType. bb....bb is simpleType.

KECX06079-E

src-ct.2.1: Complex Type Definition Representation Error for type 'aa....aa'. When <simpleContent> is used, the base type must be a complexType whose content type is simple, or, only if restriction is specified, a complex type with mixed content and emptiable particle, or, only if extension is specified, a simple type. 'bb....bb' satisfies none of these conditions.

An error occurred in the complex type definition representation for the type aa....aa. When simpleContent is being used, the base type must be complexType for which content type is simple, or only if restriction is specified, complexType with mixed content and empty particle or only if an extension is specified, simpleType. bb....bb does not specify any of these conditions.

KECX06080-E

src-ct.2.2: Complex Type Definition Representation Error for type 'aa....aa'. When a complexType with simpleContent restricts a complexType with mixed content and emptiable particle, then there must be a <simpleType> among the children of <restriction>.

An error occurred in the complex type definition representation for the type aa....aa. When complexType with simpleContent is restricted to complexType with mixed content and empty particle, there must be simpleType among the children of restriction.

KECX06081-E

src-ct.4: Complex Type Definition Representation Error for type 'aa....aa'. The intersection of wildcards is not expressible.

An error occurred in the complex type definition representation for the type aa....aa. The common sets of wildcards cannot be expressed.

KECX06082-E

src-element.1: The properties 'default' and 'fixed' cannot both be present in element declaration 'aa....aa'. Use only one of them.

default and fixed cannot be specified concurrently in the element declaration aa....aa. Use only one of them.

KECX06083-E

src-element.2.1: : One of ''ref'' or ''name'' must be present in a local element declaration.

Either ref or name is required in a local element declaration.

KECX06084-E

src-element.2.2: Since 'aa....aa' contains the 'ref' attribute, its content must match (annotation?). However, 'bb....bb' was found.

As aa....aa contains the ref attribute, only annotations can be specified in its contents. However, bb....bb was found.

KECX06085-E

src-element.3: Element 'aa....aa' has both a 'type' attribute and a 'anonymous type' child. Only one of these is allowed for an element.

The element aa....aa has both the type attribute and the anonymous type child. An element can have only one of these attributes.

KECX06086-E

src-import.1.1: The namespace attribute 'aa....aa' of an <import> element information item must not be the same as the targetNamespace of the schema it exists in.

The namespace attribute aa....aa of the import element information item must not be the same as the target namespace of the schema in which it exists.

KECX06087-E

src-import.2: The root element of document 'aa....aa' has to have the namespace name 'http://www.w3.org/2001/XMLSchema' and the local name 'schema'.

The root element of the document aa....aa must have the namespace name http://www.w3.org/2001/XMLSchema and the local name schema.

KECX06088-E

src-import.3.1: The namespace attribute, 'aa....aa', of an <import> element information item must be identical to the targetNamespace attribute, 'bb....bb', of the imported document.

The namespace attribute aa....aa of the import element information item must be the same as the target namespace bb....bb of the imported document.

KECX06089-E

src-import.3.2: An <import> element information item that had no namespace attribute was found, so the imported document cannot have a targetNamespace attribute. However, the targetNamespace 'bb....bb' was found in the imported document.

The import element information item does not have a namespace attribute. Therefore, the imported document cannot have a target namespace attribute. However, the target namespace bb....bb was found in the imported document.

KECX06090-E

src-include.1: The root element of document 'aa....aa' has to have the namespace name 'http://www.w3.org/2001/XMLSchema' and the local name 'schema'.

The root element of the document aa....aa must have the namespace name http://www.w3.org/2001/XMLSchema and the local name schema.

KECX06091-E

src-include.2.1: The targetNamespace of the referenced schema, currently 'bb....bb', must be identical to that of the including schema, currently 'aa....aa'.

The target namespace of the referenced schema, which is currently bb....bb, must be the same as the target namespace of the including schema, which is currently aa....aa.

KECX06092-E

src-redefine.2: The root element of document 'aa....aa' has to have the namespace name 'http://www.w3.org/2001/XMLSchema' and the local name 'schema'.

The root element of the document aa....aa must have the namespace name http://www.w3.org/2001/XMLSchema and the local name schema.

KECX06093-E

src-redefine.3.1: The targetNamespace of the referenced schema, currently 'bb....bb', must be identical to that of the redefining schema, currently 'aa....aa'.

The target namespace of the schema that is read with redefine, which is currently bb....bb, must be the same as the target namespace of the schema at the reading source, which is currently aa....aa.

KECX06094-E

src-redefine.5.a.a: No non-annotation children of <simpleType> were found. <simpleType> children of <redefine> elements must have <restriction> descendants, with ''base'' attributes that refer to themselves.

No non-annotation children were found in simpleType. The simpleType children of the redefine element must have restriction descendants with base attributes that reference themselves.

KECX06095-E

src-redefine.5.a.b: 'aa....aa' is not a valid child element. <simpleType> children of <redefine> elements must have <restriction> descendants, with 'base' attributes that refer to themselves.

aa....aa is not a valid child element. The simpleType children of the redefine element must have restriction descendants with base attributes that reference themselves.

KECX06096-E

src-redefine.5.a.c: 'aa....aa' does not have a 'base' attribute that refers to the redefined element, 'bb....bb'. <simpleType> children of <redefine> elements must have <restriction> descendants, with 'base' attributes that refer to themselves.

aa....aa does not have a base attribute that references the redefined element bb....bb. The simpleType children of the redefine element must have restriction descendants with base attributes that reference themselves.

KECX06097-E

src-redefine.5.b.a: No non-annotation children of <complexType> were found. <complexType> children of <redefine> elements must have <extension> or <restriction> descendants, with ''base'' attributes that refer to themselves.

No non-annotation children were found in complexType. The complexType children of the redefine element must have extension or restriction descendants with base attributes that reference themselves.

KECX06098-E

src-redefine.5.b.b: No non-annotation grandchildren of <complexType> were found. <complexType> children of <redefine> elements must have <extension> or <restriction> descendants, with ''base'' attributes that refer to themselves.

No non-annotation grandchildren were found in complexType. The complexType children of the redefine element must have extension or restriction descendants with base attributes that reference themselves.

KECX06099-E

src-redefine.5.b.c: 'aa....aa' is not a valid grandchild element. <complexType> children of <redefine> elements must have <extension> or <restriction> descendants, with 'base' attributes that refer to themselves.

aa....aa is not a valid grandchild element. The complexType children of the redefine element must have extension or restriction descendants with base attributes that reference themselves.

KECX06100-E

src-redefine.5.b.d: 'aa....aa' does not have a 'base' attribute that refers to the redefined element, 'bb....bb'. <complexType> children of <redefine> elements must have <extension> or <restriction> descendants, with 'base' attributes that refer to themselves.

aa....aa does not have a base attribute that references the redefined element bb....bb. The complexType children of the redefine element must have extension or restriction descendants with base attributes that reference themselves.

KECX06101-E

src-redefine.6.1.1: If a group child of a <redefine> element contains a group referring itself, it must have exactly 1; this one has 'aa....aa'.

A child group of a redefine element can contain only one group that references itself. This one has aa....aa.

KECX06102-E

src-redefine.6.1.2: The group 'aa....aa', which contains a reference to a group being redefined, must have 'minOccurs' = 'maxOccurs' = 1.

minOccurs and maxOccurs of the group aa....aa that includes the reference to a group being redefined must be 1.

KECX06103-E

src-redefine.6.2.1: No group in the redefined schema has a name matching 'aa....aa'.

No group is found in the redefined schema with a name matching aa....aa.

KECX06104-E

src-redefine.6.2.2: Group 'aa....aa' does not properly restrict the group it redefines; constraint violated: 'bb....bb'.

The group aa....aa does not properly restrict the group it redefines. The constraint violated the following: bb....bb

KECX06105-E

src-redefine.7.1: If an attributeGroup child of a <redefine> element contains an attributeGroup referring itself, it must have exactly 1; this one has aa....aa.

A child attributeGroup of a redefine element can contain only one group that references itself. This one has aa....aa.

KECX06106-E

src-redefine.7.2.1: No attributeGroup in the redefined schema has a name matching 'aa....aa'.

No attributeGroup is found in the redefined schema with a name matching aa....aa.

KECX06107-E

src-redefine.7.2.2: AttributeGroup 'aa....aa' does not properly restrict the attributeGroup it redefines; constraint violated: 'bb....bb'.

The attributeGroup aa....aa does not properly restrict the attributeGroup it redefines. The constraint violated the following: bb....bb

KECX06108-E

src-resolve: Cannot resolve the name 'aa....aa' to a(n) 'bb....bb' component.

The name aa....aa specified in the bb....bb component is not found.

KECX06109-E

src-resolve.4.1: Error resolving component 'cc....cc'. It was detected that 'cc....cc' has no namespace, but components with no target namespace are not referenceable from schema document 'aa....aa'. If 'cc....cc' is intended to have a namespace, perhaps a prefix needs to be provided. If it is intended that 'cc....cc' has no namespace, then an 'import' without a "namespace" attribute should be added to 'aa....aa'.

This is an error resolving the component cc....cc. It was detected that cc....cc does not have a namespace. However, components with no target namespace cannot be referenced from the schema document aa....aa. If cc....cc is intended to have a namespace, perhaps a prefix needs to be provided. If cc....cc is not intended to have a namespace, import without a namespace attribute must be added to aa....aa.

KECX06110-E

src-resolve.4.2: Error resolving component 'cc....cc'. It was detected that 'cc....cc' is in namespace 'bb....bb', but components from this namespace are not referenceable from schema document 'aa....aa'. If this is the incorrect namespace, perhaps the prefix of 'cc....cc' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'aa....aa'.

This is an error resolving the component cc....cc. It was detected that cc....cc exists in the namespace bb....bb. However, components from this namespace cannot be referenced from the schema document aa....aa. If this is an incorrect namespace, the prefix of cc....cc might needs to be changed. If this is the correct namespace, an appropriate import tag must be added to aa....aa.

KECX06111-E

src-simple-type.2.a: A <restriction> element was found that has both a base [attribute] and a <simpleType> element among its [children]. Only one is allowed.

A restriction element has both the base attribute and the simpleType element among its children. Only one is allowed.

KECX06112-E

src-simple-type.2.b: A <restriction> element was found that has neither a base [attribute] nor a <simpleType> element among its [children]. One is required.

A restriction element has neither the base attribute nor the simpleType element among its children. One is required.

KECX06113-E

src-simple-type.3.a: A <list> element was found that has both an itemType [attribute] and a <simpleType> element among its [children]. Only one is allowed.

A list element has both the itemType attribute and the simpleType element among its children. Only one is allowed.

KECX06114-E

src-simple-type.3.b: A <list> element was found that has neither an itemType [attribute] nor a <simpleType> element among its [children]. One is required.

A list element has neither the itemType attribute nor the simpleType element among its children. It must have one of them.

KECX06115-E

src-single-facet-value: The facet 'aa....aa' is defined more than once.

The facet aa....aa is specified more than once.

KECX06116-E

src-union-memberTypes-or-simpleTypes: A <union> element must have either a non-empty memberTypes [attribute] or at least one <simpleType> element among its [children].

A union element must have either a non-empty memberTypes attribute or one or more simpleType elements among its children.

KECX06117-E

ag-props-correct.2: Error for attribute group 'aa....aa'. Duplicate attribute uses with the same name and target namespace are specified. Name of duplicate attribute use is 'bb....bb'.

This is an error for attribute group aa....aa. Duplicate attribute usage with the same name and target namespace is specified. The name of the duplicate attribute usage is bb....bb.

KECX06118-E

ag-props-correct.3: Error for attribute group 'aa....aa'. Two attribute declarations, 'bb....bb' and 'cc....cc' have types which are derived from ID.

This is an error for attribute group aa....aa. Two attribute declarations bb....bb and cc....cc have the type derived from the ID.

KECX06119-E

a-props-correct.2: Invalid value constraint value 'bb....bb' in attribute 'aa....aa'.

The value constraint value bb....bb of the attribute aa....aa is invalid.

KECX06120-E

a-props-correct.3: Attribute 'aa....aa' cannot use 'fixed' or 'default', because the attribute's {type definition} is ID, or is derived from ID.

fixed or default cannot be specified in the attribute aa....aa because either the {type definition} of the attribute is ID or it is derived from the ID.

KECX06121-E

au-props-correct.2: In the attribute declaration of 'aa....aa', a fixed value of 'bb....bb' was specified. So if the attribute use referring to 'aa....aa' also has a {value constraint}, it must be fixed and its value must be 'bb....bb'.

A fixed value bb....bb was specified in the attribute declaration aa....aa. Therefore, if the attribute usage referencing aa....aa also has a value constraint, it must be fixed and its value must be bb....bb.

KECX06122-E

cos-all-limited.1.2: An 'all' model group must appear in a particle with {min occurs} = {max occurs} = 1, and that particle must be part of a pair which constitutes the {content type} of a complex type definition.

An all model group must appear in the particle with minOccurs=maxOccurs=1. That particle must be part of the pair configuring the content type of a complex type definition.

KECX06123-E

cos-all-limited.2: The {max occurs} of an element in an 'all' model group must be 0 or 1. The value 'aa....aa' for element 'bb....bb' is invalid.

0 or 1 must be specified in maxOccurs of an element within an all model group. The value aa....aa of the element bb....bb is invalid.

KECX06124-E

cos-applicable-facets: Facet 'aa....aa' is not allowed by type bb....bb.

The facet aa....aa is not allowed in the type bb....bb.

KECX06125-E

cos-ct-extends.1.1: Type 'aa....aa' was derived by extension from type 'bb....bb'. However, the 'final' attribute of 'bb....bb' forbids derivation by extension.

The type aa....aa was derived from the type bb....bb by extension. However, the final attribute of bb....bb prohibits derivation by extension.

KECX06126-E

cos-ct-extends.1.4.3.2.2.1.a: The content type of a derived type and that of its base must both be mixed or both be element-only. Type 'aa....aa' is element only, but its base type is not.

Both the content type of a derived type and the content type of its base must be mixed or must be element-only. The content type of type aa....aa is element, but the content type of its base is different.

KECX06127-E

cos-ct-extends.1.4.3.2.2.1.b: The content type of a derived type and that of its base must both be mixed or both be element-only. Type 'aa....aa' is mixed, but its base type is not.

Both the content type of a derived type and the content type of its base must be mixed or must be element-only. The content type of type aa....aa is mixed, but the content type of its base is different.

KECX06128-E

cos-element-consistent: Error for type 'aa....aa'. Multiple elements with name 'bb....bb', with different types, appear in the model group.

This is an error for type aa....aa. Multiple elements of different types with the name bb....bb exist in the model group.

KECX06129-E

cos-list-of-atomic: In the definition of list type 'aa....aa', type 'bb....bb' is an invalid list element type because it is not atomic ('bb....bb' is either a list type, or a union type which contains a list).

In the definition of the list type aa....aa, the type bb....bb is an invalid list element type because it is not atomic (bb....bb is either a list type or a union type that contains a list).

KECX06130-E

cos-nonambig: aa....aa and bb....bb (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.

aa....aa and bb....bb (or the elements from their substitution group) violate the Unique Particle Attribution. During verification of the schema, two particles might not be according to the rules.

KECX06131-E

cos-particle-restrict.a: Derived particle is empty, and base is not emptiable.

The derived particle is empty. The base is not empty.

KECX06132-E

cos-particle-restrict.b: Base particle is empty, but derived particle is not.

The base particle is empty. However, the derived particle is not empty.

KECX06133-E

cos-particle-restrict.2: Forbidden particle restriction: 'aa....aa'.

This is a prohibited particle restriction. aa....aa

KECX06134-E

cos-st-restricts.1.1: The type 'bb....bb' is atomic, so its {base type definition}, 'aa....aa', must be an atomic simple type definition or a built-in primitive datatype.

The type bb....bb is atomic. Therefore, its base type definition aa....aa must be an atomic simple type definition or a built-in data type.

KECX06135-E

cos-st-restricts.2.1: In the definition of list type 'aa....aa', type 'bb....bb' is an invalid item type because it is either a list type, or a union type that contains a list.

In the definition of the list type aa....aa, the type bb....bb is an invalid item type because it is either a list type or a union type that contains a list.

KECX06136-E

cos-st-restricts.2.3.1.1: The {final} component of the {item type definition}, 'aa....aa', contains 'list'. This means that 'aa....aa' cannot be used as an item type for list type 'bb....bb'.

The final component of the item type definition aa....aa contains a list. This means that aa....aa cannot be used as an item type for the list type bb....bb.

KECX06137-E

cos-st-restricts.3.3.1.1: The {final} component of the {member type definitions}, 'aa....aa', contains 'union'. This means that 'aa....aa' cannot be used as an member type for union type 'bb....bb'.

The final component of the member type definition aa....aa contains a union. This means that aa....aa cannot be used as a member type for the union type bb....bb.

KECX06138-E

cos-valid-default.2.1: Element 'aa....aa' has a value constraint and must have a mixed or simple content model.

Element aa....aa must have a mixed or simple content model because it has a value constraint.

KECX06139-E

cos-valid-default.2.2.2: Since element 'aa....aa' has a {value constraint} and its type definition has mixed {content type}, then the particle of the {content type} must be emptiable.

As element aa....aa has a value constraint and its type definition has a mixed content type, the particle of the content type must be empty.

KECX06140-E

c-props-correct.2: Cardinality of Fields for keyref 'aa....aa' and key 'bb....bb' must match each other.

The number of field specifications for keyref aa....aa and key bb....bb must match.

KECX06141-E

ct-props-correct.3: Circular definitions detected for complex type 'aa....aa'. This means that 'aa....aa' is contained in its own type hierarchy, which is an error.

The complex type aa....aa has an infinite loop declaration. This means that aa....aa is contained in its own type hierarchy, which is an error.

KECX06142-E

ct-props-correct.4: Error for type 'aa....aa'. Duplicate attribute uses with the same name and target namespace are specified. Name of duplicate attribute use is 'bb....bb'.

This is an error for type aa....aa. Duplicate attribute usage with the same name and target namespace is specified. The name of the duplicate attribute usage is bb....bb.

KECX06143-E

ct-props-correct.5: Error for type 'aa....aa'. Two attribute declarations, 'bb....bb' and 'cc....cc' have types which are derived from ID.

This is an error for the type aa....aa. Two attribute declarations bb....bb and cc....cc have the type derived from the ID.

KECX06144-E

derivation-ok-restriction.1: Type 'aa....aa' was derived by restriction from type 'bb....bb'. However, 'bb....bb' has a {final} property that forbids derivation by restriction.

The type aa....aa was derived with restrictions from the type bb....bb. However, bb....bb of the final attribute prohibits derivation by restriction.

KECX06145-E

derivation-ok-restriction.2.1.1: Error for type 'aa....aa'. The attribute use 'bb....bb' in this type has a 'use' value of 'cc....cc', which is inconsistent with the value of 'required' in a matching attribute use in the base type.

This is an error for the type aa....aa. The attribute usage bb....bb in this type has a use value of cc....cc. This value contradicts the value of required in the matching attribute usage of the base type.

KECX06146-E

derivation-ok-restriction.2.1.2: Error for type 'aa....aa'. The attribute use 'bb....bb' in this type has type 'cc....cc', which is not validly derived from 'dd....dd', the type of the matching attribute use in the base type.

This is an error for type aa....aa. The attribute usage bb....bb in this type has the type cc....cc. This type is not validly derived from type dd....dd of the matching attribute usage in the base type.

KECX06147-E

derivation-ok-restriction.2.1.3.a: Error for type 'aa....aa'. The attribute use 'bb....bb' in this type has an effective value constraint which is not fixed, and the effective value constraint of the matching attribute use in the base type is fixed.

This is an error for type aa....aa. The attribute usage bb....bb in this type has an effective value constraint that is not fixed. The effective value constraint of the matching attribute usage in the base type is fixed.

KECX06148-E

derivation-ok-restriction.2.1.3.b: Error for type 'aa....aa'. The attribute use 'bb....bb' in this type has an effective value constraint fixed with a value of 'cc....cc', which is not consistent with the value of 'dd....dd' for the fixed effective value constraint of the matching attribute use in the base type.

This is an error for type aa....aa. The attribute usage bb....bb in this type has an effective value constraint with a fixed value of cc....cc. This value contradicts the value dd....dd for the fixed effective value constraint of the matching attribute usage in the base type.

KECX06149-E

derivation-ok-restriction.2.2.a: Error for type 'aa....aa'. The attribute use 'bb....bb' in this type does not have a matching attribute use in the base, and the base type does not have a wildcard attribute.

This is an error for type aa....aa. The attribute usage bb....bb in this type does not have a matching attribute usage in the base. The base type does not have a wildcard attribute.

KECX06150-E

derivation-ok-restriction.2.2.b: Error for type 'aa....aa'. The attribute use 'bb....bb' in this type does not have a matching attribute use in the base, and the wildcard in the base type does not allow the namespace 'cc....cc' of this attribute use.

This is an error for type aa....aa. The attribute usage bb....bb in this type does not have a matching attribute usage in the base. The wildcard of the base type does not allow the namespace cc....cc of this attribute usage.

KECX06151-E

derivation-ok-restriction.3: Error for type 'aa....aa'. The attribute use 'bb....bb' in the base type has REQUIRED as true, but there is no matching attribute use in the derived type.

This is an error for type aa....aa. The attribute usage bb....bb of the base type has a REQUIRED specification, but there is no matching attribute usage in the derived type.

KECX06152-E

derivation-ok-restriction.4.1: Error for type 'aa....aa'. The derivation has an attribute wildcard, but the base does not have one.

This is an error for the type aa....aa. The derivation has an attribute wildcard, but the base does not have one.

KECX06153-E

derivation-ok-restriction.4.2: Error for type 'aa....aa'. The wildcard in the derivation is not a valid wildcard subset of the one in the base.

This is an error for the type aa....aa. The wildcard in the derivation is not a subset of the valid wildcard in the base.

KECX06154-E

derivation-ok-restriction.4.3: Error for type 'aa....aa'. The process contents of the wildcard in the derivation (bb....bb) is weaker than that in the base (cc....cc).

This is an error for the type aa....aa. The processor validation specification of the wildcard in the derivation (bb....bb) is weaker than the processor validation specification in the base (cc....cc).

KECX06155-E

derivation-ok-restriction.5.2.2.1: Error for type 'aa....aa'. The simple content type of this type, 'bb....bb', is not a valid restriction of the simple content type of the base, 'cc....cc'.

This is an error for the type aa....aa. The simple content type bb....bb of this type is an invalid restriction of the simple content type cc....cc of the base.

KECX06156-E

derivation-ok-restriction.5.3.2: Error for type 'aa....aa'. The content type of this type is empty, but the content type of the base, 'bb....bb', is not empty or emptiable.

This is an error for the type aa....aa. The content type of this type is empty, but the content type bb....bb of the base is not empty.

KECX06157-E

derivation-ok-restriction.5.4.1.2: Error for type 'aa....aa'. The content type of this type is mixed, but the content type of the base, 'bb....bb', is not.

This is an error for the type aa....aa. The content type of this type is mixed, but the content type bb....bb of the base is different.

KECX06158-E

derivation-ok-restriction.5.4.2: Error for type 'aa....aa'. The particle of the type is not a valid restriction of the particle of the base.

This is an error for the type aa....aa. The particle of the type is an invalid restriction of the particle of the base.

KECX06159-E

enumeration-required-notation: The NOTATION type, 'aa....aa' used by cc....cc 'bb....bb', must have an enumeration facet value which specifies the notation elements used by this type.

The NOTATION type (aa....aa used by cc....cc bb....bb) must have an enumeration facet value that specifies the notation elements used by this type.

KECX06160-E

enumeration-valid-restriction: Enumeration value 'aa....aa' is not in the value space of the base type, bb....bb.

The enumeration value aa....aa is not in the value space of the base type bb....bb.

KECX06161-E

e-props-correct.2: Invalid value constraint value 'bb....bb' in element 'aa....aa'.

The value bb....bb in the element aa....aa is invalid as a value constraint.

KECX06162-E

e-props-correct.4: The {type definition} of element 'aa....aa' is not validly derived from the {type definition} of the substitutionHead 'bb....bb', or the {substitution group exclusions} property of 'bb....bb' does not allowed this derivation.

The type definition of the element aa....aa is not derived in a valid manner from the type definition of the head element bb....bb. Alternatively, the features of the substitution group exclusion of bb....bb do not allow this derivation.

KECX06163-E

e-props-correct.5: A {value constraint} must not be present on element 'aa....aa', because the element's {type definition} or {type definition}s {content type} is ID, or is derived from ID.

A {value constraint} must not exist in the element aa....aa because the {type definition} of the element or the {content type} of the {type definition} is the ID, or is derived from the ID.

KECX06164-E

e-props-correct.6: Circular substitution group detected for element 'aa....aa'.

A substitution group of an infinite loop was detected in the element aa....aa.

KECX06165-E

fractionDigits-valid-restriction: In the definition of cc....cc, the value 'aa....aa' for the facet 'fractionDigits' is invalid, because it must be <= the value for 'fractionDigits' which was set to 'bb....bb' in one of the ancestor types.

In the definition of cc....cc, the value aa....aa of the facet fractionDigits is invalid. The value must be less than or equal to the value bb....bb of fractionDigits that is set in one of the ancestor types.

KECX06166-E

fractionDigits-totalDigits: In the definition of cc....cc, the value 'aa....aa' for the facet 'fractionDigits' is invalid, because the value must be <= the value for 'totalDigits' which is 'bb....bb'.

In the definition of cc....cc, the value aa....aa of the facet fractionDigits is invalid. The value must be less than or equal to the value bb....bb of totalDigits.

KECX06167-E

length-minLength-maxLength.a: It is an error to specify both length and either of minLength or maxLength. However, aa....aa has length = 'bb....bb', minLength = 'cc....cc' and maxLength = 'dd....dd'.

The length facet cannot be specified simultaneously with the minLength facet or maxLength facet. However, aa....aa contains the length facet bb....bb, minLength facet cc....cc, and maxLength facet dd....dd.

KECX06168-E

length-minLength-maxLength.b: It is an error to specify both length and either of minLength or maxLength. However, aa....aa has length = 'bb....bb' and minLength = 'cc....cc'.

The length facet cannot be specified simultaneously with the minLength facet or maxLength facet. However, aa....aa contains the length facet bb....bb and the minLength facet cc....cc.

KECX06169-E

length-minLength-maxLength.c: It is an error to specify both length and either of minLength or maxLength. However, aa....aa has length = 'bb....bb' and maxLength = 'cc....cc'.

The length facet cannot be specified simultaneously with the minLength facet or maxLength facet. However, aa....aa contains the length facet bb....bb and the maxLength facet cc....cc.

KECX06170-E

length-valid-restriction: Error for type 'cc....cc'. The value of length = 'aa....aa' must be = the value of that of the base type 'bb....bb'.

This is an error for the type cc....cc. The value aa....aa of the length facet must be the same as the value of the base type bb....bb.

KECX06171-E

maxExclusive-valid-restriction.1: Error for type 'cc....cc'. The maxExclusive value ='aa....aa' must be <= maxExclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The maxExclusive value aa....aa must be less than or equal to maxExclusive of the base type bb....bb.

KECX06172-E

maxExclusive-valid-restriction.2: Error for type 'cc....cc'. The maxExclusive value ='aa....aa' must be <= maxInclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The maxExclusive value aa....aa must be less than or equal to maxInclusive of the base type bb....bb.

KECX06173-E

maxExclusive-valid-restriction.3: Error for type 'cc....cc'. The maxExclusive value ='aa....aa' must be > minInclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The maxExclusive value aa....aa must be greater than minInclusive of the base type bb....bb.

KECX06174-E

maxExclusive-valid-restriction.4: Error for type 'cc....cc'. The maxExclusive value ='aa....aa' must be > minExclusive of the base type 'bb....bb'.

The maxExclusive value aa....aa must be greater than minExclusive of the base type bb....bb.

KECX06175-E

maxInclusive-maxExclusive: It is an error for both maxInclusive and maxExclusive to be specified for the same datatype. In cc....cc, maxInclusive = 'aa....aa' and maxExclusive = 'bb....bb'.

maxInclusive and maxExclusive cannot be specified simultaneously in the same data type. cc....cc contains maxInclusive aa....aa and maxExclusive bb....bb.

KECX06176-E

maxInclusive-valid-restriction.1: Error for type 'cc....cc'. The maxInclusive value ='aa....aa' must be <= maxInclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The maxInclusive value aa....aa must be less than or equal to maxInclusive of the base type bb....bb.

KECX06177-E

maxInclusive-valid-restriction.2: Error for type 'cc....cc'. The maxInclusive value ='aa....aa' must be < maxExclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The maxInclusive value aa....aa must be less than maxExclusive of the base type bb....bb.

KECX06178-E

maxInclusive-valid-restriction.3: Error for type 'cc....cc'. The maxInclusive value ='aa....aa' must be >= minInclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The maxInclusive value aa....aa must be more than or equal to minInclusive of the base type bb....bb.

KECX06179-E

maxInclusive-valid-restriction.4: Error for type 'cc....cc'. The maxInclusive value ='aa....aa' must be > minExclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The maxInclusive value aa....aa must be greater than minExclusive of the base type bb....bb.

KECX06180-E

maxLength-valid-restriction: In the definition of cc....cc, maxLength value = 'aa....aa' must be <= that of the base type 'bb....bb'.

In the definition of cc....cc, the maxLength value aa....aa must be less than or equal to the maxLength value of the base type bb....bb.

KECX06181-E

mg-props-correct.2: Circular definitions detected for group 'aa....aa'. Recursively following the {term} values of the particles leads to a particle whose {term} is the group itself.

The reference for the group aa....aa has an infinite loop declaration. Recursively if the group reference is continued, linked to the particle for which item is the group itself.

KECX06182-E

minExclusive-less-than-equal-to-maxExclusive: In the definition of cc....cc, minExclusive value = 'aa....aa' must be <= maxExclusive value = 'bb....bb'.

In the definition of cc....cc, aa....aa is specified in minExclusive, but it must be less than or equal to the value bb....bb specified in maxExclusive.

KECX06183-E

minExclusive-less-than-maxInclusive: In the definition of cc....cc, minExclusive value = 'aa....aa' must be < maxInclusive value = 'bb....bb'.

In the definition of cc....cc, aa....aa is specified in minExclusive, but it must be less than the value bb....bb specified in maxInclusive.

KECX06184-E

minExclusive-valid-restriction.1: Error for type 'cc....cc'. The minExclusive value ='aa....aa' must be >= minExclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The minExclusive value aa....aa must be more than or equal to minExclusive of the base type bb....bb.

KECX06185-E

minExclusive-valid-restriction.2: Error for type 'cc....cc'. The minExclusive value ='aa....aa' must be <= maxInclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The minExclusive value aa....aa must be less than or equal to maxInclusive of the base type bb....bb.

KECX06186-E

minExclusive-valid-restriction.3: Error for type 'cc....cc'. The minExclusive value ='aa....aa' must be >= minInclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The minExclusive value aa....aa must be more than or equal to minInclusive of the base type bb....bb.

KECX06187-E

minExclusive-valid-restriction.4: Error for type 'cc....cc'. The minExclusive value ='aa....aa' must be < maxExclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The minExclusive value aa....aa must be less than maxExclusive of the base type bb....bb.

KECX06188-E

minInclusive-less-than-equal-to-maxInclusive: In the definition of cc....cc, minInclusive value = 'aa....aa' must be <= maxInclusive value = 'bb....bb'.

In the definition of cc....cc, aa....aa is specified in minInclusive, but it must be less than or equal to the value bb....bb specified in maxInclusive.

KECX06189-E

minInclusive-less-than-maxExclusive: In the definition of cc....cc, minInclusive value = 'aa....aa' must be < maxExclusive value = 'bb....bb'.

In the definition of cc....cc, aa....aa is specified in minInclusive, but it must be less than the value bb....bb specified in maxExclusive.

KECX06190-E

minInclusive-minExclusive: It is an error for both minInclusive and minExclusive to be specified for the same datatype. In cc....cc, minInclusive = 'aa....aa' and minExclusive = 'bb....bb'.

minInclusive and minExclusive cannot be specified simultaneously in the same data type. cc....cc contains minInclusive aa....aa and minExclusive bb....bb.

KECX06191-E

minInclusive-valid-restriction.1: Error for type 'cc....cc'. The minInclusive value ='aa....aa' must be >= minInclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The minInclusive value aa....aa must be more than or equal to minInclusive of the base type bb....bb.

KECX06192-E

minInclusive-valid-restriction.2: Error for type 'cc....cc'. The minInclusive value ='aa....aa' must be <= maxInclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The minInclusive value aa....aa must be less than or equal to maxInclusive of the base type bb....bb.

KECX06193-E

minInclusive-valid-restriction.3: Error for type 'cc....cc'. The minInclusive value ='aa....aa' must be > minExclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The minInclusive value aa....aa must be greater than minExclusive of the base type bb....bb.

KECX06194-E

minInclusive-valid-restriction.4: Error for type 'cc....cc'. The minInclusive value ='aa....aa' must be < maxExclusive of the base type 'bb....bb'.

This is an error for the type cc....cc. The minInclusive value aa....aa must be less than maxExclusive of the base type bb....bb.

KECX06195-E

minLength-less-than-equal-to-maxLength: In the definition of cc....cc, value of minLength = 'aa....aa' must be < value of maxLength = 'bb....bb'.

In the definition of cc....cc, the value aa....aa specified in minLength must be less than the value bb....bb specified in maxLength.

KECX06196-E

minLength-valid-restriction: In the definition of cc....cc, minLength = 'aa....aa' must be >= than that of the base type, 'bb....bb'.

In the definition of cc....cc, the minLength value aa....aa must be greater than the minLength value of the base type bb....bb.

KECX06197-E

no-xmlns: The '{'name'}' of an attribute declaration must not match ''xmlns''.

The name of an attribute declaration must not match xmlns.

KECX06198-E

no-xsi: The {target namespace} of an attribute declaration must not match 'aa....aa'.

The target namespace of an attribute declaration must not match aa....aa.

KECX06199-E

p-props-correct.2.1: In the declaration of 'aa....aa', the value of 'minOccurs' is 'bb....bb', but it must not be greater than the value of 'maxOccurs', which is 'cc....cc'.

In the declaration of aa....aa, the value bb....bb specified in minOccurs must not be greater than the value cc....cc of maxOccurs.

KECX06200-E

rcase-MapAndSum.1: There is not a complete functional mapping between the particles.

There is no complete functional mapping between particles.

KECX06201-E

rcase-MapAndSum.2: Group's occurrence range, (aa....aa, bb....bb), is not a valid restriction of base group's occurrence range, (cc....cc, dd....dd).

The occurrence range (aa....aa, bb....bb) of the group is an invalid restriction of the occurrence range (cc....cc, dd....dd) of the base group.

KECX06202-E

rcase-NameAndTypeOK.1: Elements have names and target namespaces which are not the same: Element 'aa....aa' in namespace 'bb....bb' and element 'cc....cc' in namespace 'dd....dd'.

Elements have different names and target namespaces. These elements are the element aa....aa in the namespace bb....bb and the element cc....cc in the namespace dd....dd.

KECX06203-E

rcase-NameAndTypeOK.2: Error for the particle whose {term} is the element declaration 'aa....aa'. The element declaration's {nillable} is true, but the corresponding particle in the base type has an element declaration whose {nillable} is false.

This is an error for a particle whose item is the element declaration aa....aa. Nillable of the element declaration is true, but nillable of the element declaration of particle of the corresponding base type is false.

KECX06204-E

rcase-NameAndTypeOK.3: Error for the particle whose {term} is the element declaration 'aa....aa'. Its occurrence range, (bb....bb, cc....cc), is not a valid restriction of the range, (dd....dd, ee....ee), of the corresponding particle in the base type.

This is an error for a particle in which the item is the element declaration aa....aa. The occurrence range (bb....bb, cc....cc) is an invalid restriction of the occurrence range (dd....dd, ee....ee) of the base.

KECX06205-E

rcase-NameAndTypeOK.4.a: Element 'aa....aa' is not fixed, but the corresponding element in the base type is fixed with value 'bb....bb'.

The element aa....aa is not fixed, but the corresponding element in the base type is fixed with the value bb....bb.

KECX06206-E

rcase-NameAndTypeOK.4.b: Element 'aa....aa' is fixed with value 'bb....bb', but the corresponding element in the base type is fixed with value 'cc....cc'.

Element aa....aa is fixed with the value bb....bb, but the corresponding element in the base type is fixed with the value cc....cc.

KECX06207-E

rcase-NameAndTypeOK.5: Identity constraints for element 'aa....aa' are not a subset of those in base.

The identity constraints for the element aa....aa are not a subset of the base.

KECX06208-E

rcase-NameAndTypeOK.6: The disallowed substitutions for element 'aa....aa' are not a superset of those in the base.

The element aa....aa has a type that is not derived from the type of the base element.

KECX06209-E

rcase-NameAndTypeOK.7: The type of element 'aa....aa', 'bb....bb', is not derived from the type of the base element, 'cc....cc'.

The type bb....bb of the element aa....aa is not derived from the type cc....cc of the base element.

KECX06210-E

rcase-NSCompat.1: Element 'aa....aa' has a namespace 'bb....bb' which is not allowed by the wildcard in the base.

The element aa....aa has a namespace bb....bb that is not allowed by the wildcard in the base.

KECX06211-E

rcase-NSCompat.2: Error for the particle whose {term} is the element declaration 'aa....aa'. Its occurrence range, (bb....bb,cc....cc), is not a valid restriction of the range, (dd....dd, ee....ee), of the corresponding particle in the base type.

This is an error for a particle in which the item is the element declaration aa....aa. The occurrence range (bb....bb, cc....cc) is an invalid restriction of the occurrence range (dd....dd, ee....ee) of the corresponding particle in the base type.

KECX06212-E

rcase-NSRecurseCheckCardinality.1: There is not a complete functional mapping between the particles.

There is no complete functional mapping between particles.

KECX06213-E

rcase-NSRecurseCheckCardinality.2: Group's occurrence range, (aa....aa,bb....bb), is not a valid restriction of base wildcard's range, (cc....cc,dd....dd).

The occurrence range of the group is not a valid restriction of the range of wildcard in the base.

KECX06214-E

rcase-NSSubset.1: Wildcard is not a subset of corresponding wildcard in base.

The wildcard is not a subset of the corresponding wildcard in the base.

KECX06215-E

rcase-NSSubset.2: Wildcard's occurrence range, (aa....aa,bb....bb), is not a valid restriction of that in the base, (cc....cc,dd....dd).

The occurrence range (aa....aa, bb....bb) of the wildcard is an invalid restriction of the occurrence range (cc....cc, dd....dd) of the base.

KECX06216-E

rcase-NSSubset.3: Wildcard's process contents, 'aa....aa', is weaker than that in the base, 'bb....bb'.

The processor validation specification aa....aa of the wildcard is weaker than the processor validation specification bb....bb of the wildcard in the base.

KECX06217-E

rcase-Recurse.1: Group's occurrence range, (aa....aa,bb....bb), is not a valid restriction of base group's occurrence range, (cc....cc,dd....dd).

The occurrence range (aa....aa, bb....bb) of the group is an invalid restriction of the occurrence range (cc....cc, dd....dd) of the base group.

KECX06218-E

rcase-Recurse.2: There is not a complete functional mapping between the particles.

There is no complete functional mapping between particles.

KECX06219-E

rcase-RecurseLax.1: Group's occurrence range, (aa....aa,bb....bb), is not a valid restriction of base group's occurrence range, (cc....cc,dd....dd).

The occurrence range (aa....aa, bb....bb) of the group is an invalid restriction of the occurrence range (cc....cc, dd....dd) of the base group.

KECX06220-E

rcase-RecurseLax.2: There is not a complete functional mapping between the particles.

There is no complete functional mapping between particles.

KECX06221-E

rcase-RecurseUnordered.1: Group's occurrence range, (aa....aa,bb....bb), is not a valid restriction of base group's occurrence range, (cc....cc,dd....dd).

The occurrence range (aa....aa, bb....bb) of the group is an invalid restriction of the occurrence range (cc....cc, dd....dd) of the base group.

KECX06222-E

rcase-RecurseUnordered.2: There is not a complete functional mapping between the particles.

There is no complete functional mapping between particles.

KECX06223-E

sch-props-correct.2: A schema cannot contain two global components with the same name; this schema contains two occurrences of 'aa....aa'.

A schema cannot contain two global components with the same name. aa....aa has duplicate specification.

KECX06224-E

st-props-correct.2: Circular definitions have been detected for simple type 'aa....aa'. This means that 'aa....aa' is contained in its own type hierarchy, which is an error.

The reference for the simple type aa....aa has an infinite loop declaration. This means that aa....aa is in its own type hierarchy, which is an error.

KECX06225-E

st-props-correct.3: Error for type 'aa....aa'. The value of {final} of the {base type definition}, 'bb....bb', forbids derivation by restriction.

This is an error for the type aa....aa. The value of final of the base type definition bb....bb prohibits derivation by restriction.

KECX06226-E

totalDigits-valid-restriction: In the definition of cc....cc, the value 'aa....aa' for the facet 'totalDigits' is invalid, because it must be <= the value for 'totalDigits' which was set to 'bb....bb' in one of the ancestor types.

In the definition of cc....cc, the value aa....aa of the totalDigits facet is invalid. It must be less than or equal to the value bb....bb of totalDigits that is set in one of the ancestor types.

KECX06227-E

whiteSpace-valid-restriction.1: In the definition of aa....aa, the value 'bb....bb' for the facet 'whitespace' is invalid, because the value for 'whitespace' has been set to 'collapse' in one of the ancestor types.

In the definition of aa....aa, the value bb....bb of the whiteSpace facet is invalid. Collapse is set in one of the ancestor types.

KECX06228-E

whiteSpace-valid-restriction.2: In the definition of aa....aa, the value 'preserve' for the facet 'whitespace' is invalid, because the value for 'whitespace' has been set to 'replace' in one of the ancestor types.

In the definition of aa....aa, the value preserve of the whiteSpace facet is invalid. Replace is set in one of the ancestor types.

KECX06229-E

s4s-att-invalid-value: Invalid attribute value for 'bb....bb' in element 'aa....aa'. Recorded reason: cc....cc

An invalid value is specified in the attribute bb....bb of the element aa....aa. The recorded reason is cc....cc.

KECX06230-E

s4s-att-must-appear: Attribute 'bb....bb' must appear in element 'aa....aa'.

The element aa....aa requires the attribute bb....bb.

KECX06231-E

s4s-att-not-allowed: Attribute 'bb....bb' cannot appear in element 'aa....aa'.

The attribute bb....bb cannot be specified in the element aa....aa.

KECX06232-E

s4s-elt-invalid: Element 'aa....aa' is not a valid element in a schema document.

The element aa....aa cannot be specified in the schema document.

KECX06233-E

s4s-elt-must-match.1: The content of 'aa....aa' must match bb....bb. A problem was found starting at: cc....cc.

The contents of aa....aa must match bb....bb. This problem starts from cc....cc.

KECX06234-E

s4s-elt-must-match.2: The content of 'aa....aa' must match bb....bb. Not enough elements were found.

The contents of aa....aa must match bb....bb. Enough elements were not found.

KECX06235-E

s4s-elt-invalid-content.1: The content of 'aa....aa' is invalid. Element 'bb....bb' is invalid, misplaced, or occurs too often.

The contents of aa....aa are invalid. The element bb....bb is invalid, inappropriate, or duplicated.

KECX06236-E

s4s-elt-invalid-content.2: The content of 'aa....aa' is invalid. Element 'bb....bb' cannot be empty.

The contents of aa....aa are invalid. The element bb....bb cannot be empty.

KECX06237-E

s4s-elt-invalid-content.3: Elements of type 'aa....aa' cannot appear after declarations as children of a <schema> element.

The elements of type aa....aa cannot appear as children of the schema element.

KECX06238-E

s4s-elt-schema-ns: The namespace of element 'aa....aa' must be from the schema namespace, 'http://www.w3.org/2001/XMLSchema'.

The namespace of the element aa....aa must be from the schema namespace http://www.w3.org/2001/XMLSchema.

KECX06239-E

s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw 'aa....aa'.

Non-space characters are not allowed as schema elements in other than xs:appinfo and xs:documentation. aa....aa is the corresponding part.

KECX06240-E

c-fields-xpaths: The field value = 'aa....aa' is not valid.

The field value aa....aa is invalid.

KECX06241-E

c-general-xpath: The expression 'aa....aa' is not valid with respect to the XPath subset supported by XML Schema.

The expression aa....aa is not valid with respect to the XPath subset supported by XML Schema.

KECX06242-E

c-general-xpath-ns: A namespace prefix in XPath expression 'aa....aa' was not bound to a namespace.

The namespace prefix in the XPath expression aa....aa was not bound to the namespace.

KECX06243-E

c-selector-xpath: The selector value = 'aa....aa' is not valid; selector xpaths cannot contain attributes.

The value aa....aa of the selector is invalid. The selector xpath cannot contain an attribute.

KECX06244-W

EmptyTargetNamespace: In schema document 'aa....aa', the value of the 'targetNamespace' attribute cannot be an empty string.

An empty character string cannot be specified in the target namespace of the schema document aa....aa.

KECX06245-E

FacetValueFromBase: In the declaration of type 'aa....aa', value 'bb....bb' of facet 'cc....cc' must be from the value space of the base type, 'dd....dd'.

In the declaration of the type aa....aa, the value bb....bb of the facet cc....cc must be within the range of the value dd....dd of the base type.

KECX06246-E

FixedFacetValue: In the definition of dd....dd, the value 'bb....bb' for the facet 'aa....aa' is invalid, because the value for 'aa....aa' has been set to 'cc....cc' in one of the ancestor types, and {fixed} = true.

In the definition of dd....dd, the value bb....bb of the facet aa....aa is invalid. The value of aa....aa has been set to cc....cc in one of the ancestor types. Also, fixed is true.

KECX06247-E

InvalidRegex: Pattern value 'aa....aa' is not a valid regular expression. The reported error was: 'bb....bb'.

The pattern value aa....aa is not a valid regular expression. The error reported was as follows: bb....bb.

KECX06248-E

Current configuration of the parser doesn't allow the expansion of a content model for a complex type to contain more than aa....aa nodes.

In the current configuration of the parser, the content model of a complex type cannot be expanded to include more than aa....aa nodes.

KECX06249-W

SchemaLocation: schemaLocation value = 'aa....aa' must have even number of URI's.

The value aa....aa of schemaLocation must have an even number of URIs.

KECX06250-E

TargetNamespace.1: Expecting namespace 'aa....aa', but the target namespace of the schema document is 'bb....bb'.

The expected namespace is aa....aa, but the target namespace of the schema document is bb....bb.

KECX06251-E

TargetNamespace.2: Expecting no namespace, but the schema document has a target namespace of 'bb....bb'.

A namespace is not expected, but the schema document has the target namespace bb....bb.

KECX06252-E

UndeclaredEntity: Entity 'aa....aa' is not declared.

The entity aa....aa is not declared.

KECX06253-E

UndeclaredPrefix: Cannot resolve 'aa....aa' as a QName: the prefix 'bb....bb' is not declared.

aa....aa cannot be resolved as a QName. The prefix bb....bb is not declared.

KECX06254-E

length-minLength-maxLength.d: For type aa....aa, it is an error for the value of length 'bb....bb' to be less than the value of minLength 'cc....cc'.

For type aa....aa, an error occurs if the value of length bb....bb is set to a value lesser than the value of minLength cc....cc.

KECX06255-E

length-minLength-maxLength.e: For type aa....aa, it is an error for the value of length 'bb....bb' to be greater than the value of maxLength 'cc....cc'.

For type aa....aa, an error occurs if the value of length bb....bb is set to a value greater than the value of maxLength cc....cc.

KECX06256-E

PublicSystemOnNotation: At least one of 'public' and 'system' must appear in element 'notation'.

The notation element must have at least one public or system.

KECX06301-E

The error message corresponding to the message key can not be found.

The error message corresponding to the message key cannot be found.

KECX06302-E

An internal error occurred while formatting the following message:

An internal error occurred while formatting the following message:

KECX06303-E

aa....aa cannot be called with 'null' parameter.

aa....aa cannot be called with a null parameter.

KECX06304-E

aa....aa called with an unknown field:bb....bb

aa....aa was called with an unknown field:bb....bb

KECX06305-E

Year = aa....aa, Month = bb....bb, Day = cc....cc, Hour = dd....dd, Minute = ee....ee, Second = ff....ff, fractionalSecond = gg....gg, Timezone = hh....hh , is not a valid representation of an XML Gregorian Calendar value.

Year = aa....aa, Month = bb....bb, Day = cc....cc, Hour = dd....dd, Minute = ee....ee, Second = ff....ff, Fractional second = gg....gg, and Timezone = hh....hh are not valid representations of XML Gregorian Calendar values.

KECX06306-E

Year = aa....aa, Month = bb....bb, Day = cc....cc, Hour = dd....dd, Minute = ee....ee, Second = ff....ff, fractionalSecond = gg....gg, Timezone = hh....hh , is not a valid representation of an XML Gregorian Calendar value.

Year = aa....aa, Month = bb....bb, Day = cc....cc, Hour = dd....dd, Minute = ee....ee, Second = ff....ff, Fractional second = gg....gg, and Timezone = hh....hh are not valid representations of XML Gregorian Calendar values.

KECX06307-E

Invalid set of fields set for XMLGregorianCalendar

An invalid field set was set for XMLGregorianCalendar.

KECX06308-E

Invalid value aa....aa for fractional second.

The value aa....aa of fractional second is invalid.

KECX06309-E

aa....aa is not a valid representation of an XML Gregorian Calendar value.

aa....aa is not a valid representation of an XML Gregorian Calendar value.

KECX06310-E

Invalid value aa....aa for bb....bb field.

An invalid value aa....aa is set for the field bb....bb.

KECX06311-E

aa....aa field is negative

The field aa....aa is negative.

KECX06312-E

All the fields (javax.xml.datatype.DatatypeConstants.Field) are null.

All fields (javax.xml.datatype.DatatypeConstants.Field) are null.

KECX06313-E

aa....aa value "bb....bb" too large to be supported by this implementation

bb....bb of aa....aa value is too large to be supported by this implementation.

KECX06501-E

ImplementationMessages.VAL_BST

An internal error occurred.

KECX06502-E

ImplementationMessages.VAL_UST

An internal error occurred.

KECX06503-E

ImplementationMessages.VAL_NIICM

An internal error occurred.

KECX06504-E

parse may not be called while parsing

parse cannot be called while parsing.

KECX06507-E

Schema factory class aa....aa does not extend from SchemaDVFactory.

An internal error occurred. The schema factory class aa....aa cannot be extended from SchemaDVFactory.

KECX06508-E

internal error

An internal error occurred.

KECX06509-E

TargetNamespace.3: In schema document 'aa....aa', the value of the targetNamespace attribute must not be equal to "http://www.w3.org/2001/XMLSchema-instance".

In the schema document aa....aa, the value of the target namespace cannot be http://www.w3.org/2001/XMLSchema-instance.

11.7 Messages from KECX07001 to KECX07999

This section describes the messages from KECX07001 to KECX07999 that are output by Cosminexus XML Processor.

KECX07001-E

More than one stylesheet defined in the same file.

Multiple style sheets are defined within the same file.

KECX07002-E

Template 'aa....aa' already defined in this stylesheet.

The template aa....aa is already defined in this style sheet.

KECX07003-E

Template 'aa....aa' not defined in this stylesheet.

The template aa....aa is not defined in this style sheet.

KECX07004-E

Variable 'aa....aa' is multiply defined in the same scope.

The variable aa....aa is defined more than once in the same scope.

KECX07005-E

Variable or parameter 'aa....aa' is undefined.

The variable or parameter aa....aa is undefined.

KECX07006-E

Cannot find class 'aa....aa'.

The class aa....aa is not found.

KECX07007-E

Cannot find external method 'aa....aa' (must be public).

The external method aa....aa is not found (must be public).

KECX07008-E

Cannot convert argument/return type in call to method 'aa....aa'

The argument or return type cannot be converted in call to the method aa....aa.

KECX07009-E

File or URI 'aa....aa' not found.

The file or URI aa....aa is not found.

KECX07010-E

Invalid URI 'aa....aa'.

This is an invalid URI aa....aa.

KECX07011-E

Cannot open file or URI 'aa....aa'.

The file or URI aa....aa cannot be opened.

KECX07012-E

<xsl:stylesheet> or <xsl:transform> element expected.

The <xsl:stylesheet> element or the <xsl:transform> element is required.

KECX07013-E

Namespace prefix 'aa....aa' is undeclared.

The namespace prefix aa....aa is not declared.

KECX07014-W

Unable to resolve call to function 'aa....aa'.

The call to the function aa....aa cannot be resolved.

KECX07015-E

Argument to 'aa....aa' must be a literal string.

The argument to aa....aa must be a literal string.

KECX07016-E

Error parsing XPath expression 'aa....aa'.

An error occurred while the XPath expression aa....aa was being parsed.

KECX07017-E

Required attribute 'aa....aa' is missing.

The mandatory attribute aa....aa is missing.

KECX07018-E

Illegal character 'aa....aa' in XPath expression.

The character aa....aa in the XPath expression is invalid.

KECX07019-E

Illegal name 'aa....aa' for processing instruction.

The name aa....aa for instruction processing is invalid.

KECX07020-W

Attribute 'aa....aa' outside of element.

The attribute aa....aa is outside the element.

KECX07021-W

Illegal attribute 'aa....aa'.

The attribute aa....aa is invalid.

KECX07022-E

Circular import/include. Stylesheet 'aa....aa' already loaded.

import and include are called alternately. The style sheet aa....aa is already loaded.

KECX07023-W

Result-tree fragments cannot be sorted (<xsl:sort> elements are ignored). You must sort the nodes when creating the result tree.

The result tree fragments cannot be sorted (the <xsl:sort> element will be ignored). This node must be sorted when creating the result tree.

KECX07024-W

Decimal formatting 'aa....aa' is already defined.

The decimal formatting aa....aa is already defined.

KECX07025-E

XSL version 'aa....aa' is not supported by XSLTC.

The XSL version aa....aa is not supported by XSLTC.

KECX07026-E

Circular variable/parameter reference in 'aa....aa'.

The reference to the variable and parameter within aa....aa is called alternately.

KECX07027-E

Unknown operator for binary expression.

The operator for the binary expression is unknown.

KECX07028-E

Illegal argument(s) for function call.

The argument(s) of the function call are invalid.

KECX07029-E

Second argument to document() function must be a node-set.

The second argument to the document() function must be a node set.

KECX07030-E

At least one <xsl:when> element required in <xsl:choose>.

At least one <xsl:when> element is required in <xsl:choose>.

KECX07031-E

Only one <xsl:otherwise> element allowed in <xsl:choose>.

Only one <xsl:otherwise> element is allowed in <xsl:choose>.

KECX07032-E

<xsl:otherwise> can only be used within <xsl:choose>.

You can use <xsl:otherwise> only within <xsl:choose>.

KECX07033-E

<xsl:when> can only be used within <xsl:choose>.

You can use <xsl:when> only within <xsl:choose>.

KECX07034-E

Only <xsl:when> and <xsl:otherwise> elements allowed in <xsl:choose>.

Only elements <xsl:when> and <xsl:otherwise> are allowed in <xsl:choose>.

KECX07035-E

<xsl:attribute-set> is missing the 'name' attribute.

There is no name attribute in <xsl:attribute-set>.

KECX07036-E

Illegal child element.

The child element is invalid.

KECX07037-W

You cannot call an element 'aa....aa'

The element aa....aa cannot be called.

KECX07038-E

You cannot call an attribute 'aa....aa'

The attribute aa....aa cannot be called.

KECX07039-E

Text data outside of top-level <xsl:stylesheet> element.

The text is outside the top-level <xsl:stylesheet> element.

KECX07040-E

JAXP parser not configured correctly

The JAXP parser is not configured correctly.

KECX07041-E

Unrecoverable XSLTC-internal error: 'aa....aa'

An unrecoverable internal error occurred in XSLTC. aa....aa

KECX07042-E

Unsupported XSL element 'aa....aa'.

The XSL element aa....aa is not supported.

KECX07043-E

Unrecognised XSLTC extension 'aa....aa'.

The XSLTC extension aa....aa is not recognized.

KECX07044-E

The input document is not a stylesheet (the XSL namespace is not declared in the root element).

The input document is not a style sheet (the XSL namespace is not declared in the root element).

KECX07045-E

Could not find stylesheet target 'aa....aa'.

The stylesheet target aa....aa could not be found.

KECX07046-E

Not implemented: 'aa....aa'.

aa....aa is not implemented.

KECX07047-E

The input document does not contain an XSL stylesheet.

The input document does not contain an XSL style sheet.

KECX07048-E

Could not parse element 'aa....aa'

The element aa....aa cannot be parsed.

KECX07049-E

The use attribute of <key> must be node, node-set, string or number.

The use attribute of <key> must be node, node-set, string, or number.

KECX07050-E

Output XML document version should be 1.0

The version of the output XML document must be 1.0.

KECX07051-E

Unknown operator for relational expression

The operator of the relational expression is unknown.

KECX07052-E

Attempting to use non-existing attribute set 'aa....aa'.

An attempt was made to use a non-existing attribute set aa....aa.

KECX07053-E

Cannot parse attribute value template 'aa....aa'.

The attribute value template aa....aa cannot be parsed.

KECX07054-E

Unknown data-type in signature for class 'aa....aa'.

The data type in the signature of class aa....aa is unknown.

KECX07055-E

Cannot convert data-type 'aa....aa' to 'bb....bb'.

The data type aa....aa cannot be converted to bb....bb.

KECX07056-E

This Templates does not contain a valid translet class definition.

This template does not contain a valid translet class definition.

KECX07057-E

This Templates does not contain a class with the name 'aa....aa'.

This template does not contain a class with the name aa....aa.

KECX07058-E

Could not load the translet class 'aa....aa'.

The translet class aa....aa could not be loaded.

KECX07059-E

Translet class loaded, but unable to create translet instance.

The translet class was loaded, but the translet instance cannot be created.

KECX07060-E

Attempting to set ErrorListener for 'aa....aa' to null

An attempt is made to set the ErrorListener for aa....aa to null.

KECX07061-E

Only StreamSource, SAXSource and DOMSource are supported by XSLTC

XSLTC supports only StreamSource, SAXSource, and DOMSource.

KECX07062-E

Source object passed to 'aa....aa' has no contents.

The source object passed to aa....aa has no contents.

KECX07063-E

Could not compile stylesheet

The style sheet could not be compiled.

KECX07064-E

TransformerFactory does not recognize attribute 'aa....aa'.

TransformerFactory does not recognize the attribute aa....aa.

KECX07065-E

setResult() must be called prior to startDocument().

setResult() must be called before startDocument().

KECX07066-E

The Transformer has no encapsulated translet object.

The conversion program does not have an encapsulated translet object.

KECX07067-E

No defined output handler for transformation result.

The output handler of the transformation result is not defined.

KECX07068-E

Result object passed to 'aa....aa' is invalid.

The Result object passed to aa....aa is invalid.

KECX07069-E

Attempting to access invalid Transformer property 'aa....aa'.

An attempt is made to access an invalid Transformer property aa....aa.

KECX07070-E

Could not create SAX2DOM adapter: 'aa....aa'.

The SAX2DOM adapter aa....aa cannot be created.

KECX07071-E

XSLTCSource.build() called without systemId being set.

XSLTCSource.build() is called without setting systemId.

KECX07072-E

The value of param aa....aa must be a valid Java Object

The value of param aa....aa must be a valid Java Object.

KECX07073-E

Result should not be null

The Result parameter cannot be null.

KECX07075-E

<xsl:sort> can only be used within <xsl:for-each> or <xsl:apply-templates>.

You can use <xsl:sort> only in <xsl:for-each> or <xsl:apply-templates>.

KECX07076-W

Output encoding 'aa....aa' is not supported on this JVM.

Output encoding aa....aa is not supported by this JVM.

KECX07077-E

Syntax error in 'aa....aa'.

A syntax error occurred in aa....aa.

KECX07078-E

Cannot find external constructor 'aa....aa'.

No external constructor aa....aa is found.

KECX07079-E

The first argument to the non-static Java function 'aa....aa' is not a valid object reference.

The first argument to the non-static Java function aa....aa is not a valid object reference.

KECX07080-E

Error checking type of the expression 'aa....aa'.

An error occurred while checking type of the expression aa....aa.

KECX07081-E

Error checking type of an expression at an unknown location.

An error occurred while checking type of an expression at an unknown location.

KECX07082-E

The command-line option 'aa....aa' is not valid.

The command-line option aa....aa is invalid.

KECX07083-E

The command-line option 'aa....aa' is missing a required argument.

The command-line option aa....aa does not have a required attribute.

KECX07084-W

WARNING:'aa....aa' :'bb....bb'

Warning: aa....aa, bb....bb

KECX07085-W

WARNING:'aa....aa'

Warning: aa....aa

KECX07086-E

FATAL ERROR:'aa....aa' :'bb....bb'

A fatal error occurred. aa....aa, bb....bb

KECX07087-E

FATAL ERROR:'aa....aa'

A fatal error occurred.aa....aa

KECX07088-E

ERROR:'aa....aa' :'bb....bb'

An error occurred.aa....aa, bb....bb

KECX07089-E

ERROR:'aa....aa'

An error occurred.aa....aa

KECX07090-E

Transform using translet 'aa....aa'

This conversion uses the translet aa....aa.

KECX07091-E

Transform using translet 'aa....aa' from jar file 'bb....bb'

This conversion uses the translet 'aa....aa' from the JAR file 'bb....bb'.

KECX07092-E

Could not create an instance of the TransformerFactory class 'aa....aa'.

An instance of the TransformerFactory class aa....aa could not be created.

KECX07093-E

Compiler errors:

A compiler error occurred.

KECX07094-W

Compiler warnings:

A compiler warning occurred.

KECX07095-E

Translet errors:

A translet error occurred.

KECX07096-E

An attribute whose value must be a QName or whitespace-separated list of QNames had the value 'aa....aa'

The value of the attribute is aa....aa. This value must be either a QName or a list of QNames separated with a space.

KECX07097-E

An attribute whose value must be an NCName had the value 'aa....aa'

The value of the attribute is aa....aa. This value must be an NCName.

KECX07098-E

The feature name cannot be null in TransformerFactory.getFeature(String name).

The feature name cannot be null in TransformerFactory.getFeature(String name).

KECX07099-E

The feature name cannot be null in TransformerFactory.setFeature(String name, boolean value).

The feature name cannot be null in TransformerFactory.setFeature(String name, boolean value).

KECX07100-E

Cannot set the feature 'aa....aa' on this TransformerFactory.

The feature aa....aa cannot be set in this TransformerFactory.

KECX07101-E

The method attribute of an <xsl:output> element had the value 'aa....aa'. The value must be one of 'xml', 'html', 'text', or qname-but-not-ncname

The method attribute of the <xsl:output> element had the value aa....aa. The specifiable values must be xml, html, text, or qname-but-not-ncname.

KECX07102-E

Internal XSLTC error: the generated byte code contains a try-catch-finally block and cannot be outlined.

Internal XSLTC error: the generated byte code contains a try-catch-finally block and cannot be outlined.

KECX07103-E

Internal XSLTC error: OutlineableChunkStart and OutlineableChunkEnd markers must be balanced and properly nested.

Internal XSLTC error: OutlineableChunkStart and OutlineableChunkEnd markers must be balanced and properly nested.

KECX07104-E

Internal XSLTC error: an instruction that was part of a block of byte code that was outlined is still referred to in the original method.

Internal XSLTC error: an instruction that was part of a block of byte code that was outlined is still referred to in the original method.

KECX07105-E

Internal XSLTC error: a method in the translet exceeds the Java Virtual Machine limitation on the length of a method of 64 kilobytes. This is usually caused by templates in a stylesheet that are very large. Try restructuring your stylesheet to use smaller templates.

Internal XSLTC error: a method in the translet exceeds the Java Virtual Machine limitation on the length of a method of 64 kilobytes. This is usually caused by templates in a stylesheet that are very large. Try restructuring your stylesheet to use smaller templates.

KECX07106-E

When Java security is enabled, support for deserializing TemplatesImpl is disabled.

When Java security is enabled, support for deserializing TemplatesImpl is disabled.

KECX07203-E

Couldn't load the class

The class could not be loaded.

KECX07204-E

Method not found

The method was not found.

KECX07205-E

Error: Method is inaccessible

The method could not be accessed.

KECX07206-E

Error: Number of actual and formal argument differ

The number of temporary and actual arguments is different.

KECX07207-E

Error: underlying constructor throws an exception

The base constructor threw an exception.

KECX07208-E

Constructor not found

The constructor was not found.

KECX07209-E

Error: constructor throws an exception

The constructor threw an exception.

KECX07210-E

Error: constructor is inaccessible

The constructor could not be accessed.

KECX07211-E

Error: Class that declares the underlying constructor represents an abstract class

The class that declares the base constructor represents an abstract class.

KECX07212-E

CONSTRUCTOR_NOT_FOUND_ERR aa....aa: bb....bb

CONSTRUCTOR_NOT_FOUND_ERR Class name: Method name

KECX07213-E

METHOD_NOT_FOUND_ERR aa....aa : bb....bb

METHOD_NOT_FOUND_ERR Class name: Method name

KECX07301-E

Run-time internal error in 'aa....aa'

A runtime internal error occurred in aa....aa.

KECX07302-E

Run-time error when executing <xsl:copy>.

An error occurred while executing <xsl:copy>.

KECX07303-E

Invalid conversion from 'aa....aa' to 'bb....bb'.

The conversion from aa....aa to bb....bb is invalid.

KECX07304-E

External function 'aa....aa' not supported by XSLTC.

The external function aa....aa is not supported by XSLTC.

KECX07305-E

Unknown argument type in equality expression.

The argument type within the equality expression is unknown.

KECX07306-E

Invalid argument type 'aa....aa' in call to 'bb....bb'

The argument type aa....aa in the call to bb....bb is invalid.

KECX07307-E

Attempting to format number 'aa....aa' using pattern 'bb....bb'.

An attempt is made to format the number aa....aa using the pattern bb....bb.

KECX07308-E

Cannot clone iterator 'aa....aa'.

The iterator aa....aa cannot be duplicated.

KECX07309-E

Iterator for axis 'aa....aa' not supported.

The iterator for the axis aa....aa is not supported.

KECX07310-E

Iterator for typed axis 'aa....aa' not supported.

The iterator for the typed axis aa....aa is not supported.

KECX07311-E

Attribute 'aa....aa' outside of element.

The attribute aa....aa is outside the element.

KECX07312-E

Namespace declaration 'aa....aa'='bb....bb' outside of element.

The namespace declaration aa....aa=bb....bb is outside the element.

KECX07313-E

Namespace for prefix 'aa....aa' has not been declared.

The namespace for the prefix aa....aa is not declared.

KECX07314-E

DOMAdapter created using wrong type of source DOM.

DOMAdapter was created using a wrong type of source DOM.

KECX07315-E

The SAX parser you are using does not handle DTD declaration events.

The SAX parser in use does not process DTD declaration events.

KECX07316-E

The SAX parser you are using does not have support for XML Namespaces.

The SAX parser in use does not support XML namespaces.

KECX07317-E

Could not resolve the URI reference 'aa....aa'.

The URI reference aa....aa cannot be resolved.

KECX07318-E

Unsupported XSL element 'aa....aa'

The XSL element aa....aa is not supported.

KECX07319-E

Unrecognized XSLTC extension 'aa....aa'

The XSLTC extension aa....aa is not recognized.

KECX07320-E

The specified translet, 'aa....aa', was created using a version of XSLTC more recent than the version of the XSLTC run-time that is in use. You must recompile the stylesheet or use a more recent version of XSLTC to run this translet.

The specified translet aa....aa was created using a version of XSLTC more recent than the version of the XSLTC runtime that is in use. You must either recompile the style sheet or use a recent version of XSLTC to run this translet.

KECX07321-E

An attribute whose value must be a QName had the value 'aa....aa'

An attribute, for which the value must be a Qname, had the value aa....aa.

KECX07322-E

An attribute whose value must be an NCName had the value 'aa....aa'

An attribute, for which the value must be an NCName, had the value aa....aa.

KECX07323-E

Use of the extension function 'aa....aa' is not allowed when the secure processing feature is set to true.

The use of the extension function aa....aa is not allowed, when the secure processing feature is set to true.

KECX07324-E

Use of the extension element 'aa....aa' is not allowed when the secure processing feature is set to true.

The use of the extension element aa....aa is not allowed, when the secure processing feature is set to true.

KECX07501-E

Can not absolutize URL: aa....aa

The URL cannot be made into an absolute URL: aa....aa

KECX07503-E

com.cosminexus.jaxp.impl.transform.xsltc.trax.SmartTransformerFactoryImpl could not create an com.cosminexus.jaxp.impl.transform.processor.TransformerFactoryImpl.

com.cosminexus.jaxp.impl.transform.xsltc.trax.SmartTransformerFactoryImpl could not create com.cosminexus.jaxp.impl.transform.processor.TransformerFactoryImpl.

KECX07701-E

You must supply a filename with the -stdin option.

The file name must be provided with the -stdin option.

KECX07702-E

Could not open file aa....aa

The file aa....aa could not be opened.

KECX07703-E

No permission to file aa....aa

There is no permission to the file aa....aa.

KECX07704-E

Missing -stdin option!

The -stdin option does not exist.

KECX07705-E

Error running JavaCUP:

This is the JavaCUP execution error.

KECX07900-E

Source cannot be null

The Source parameter cannot be null.

KECX07901-E

Variable reference is not allowed in either the 'match' or the 'use' attribute of the 'xsl:key' element.

Variable reference is not allowed in the match attribute or the use attribute of the xsl:key element.

11.8 Messages from KECX09001 to KECX09999

This section explains the messages from KECX09001 to KECX09999 that the Cosminexus XML Processor outputs.

KECX09501-I

J2EE Server 'aa....aa': schema cache: bb....bb

J2EE server 'aa....aa': Schema cache functionality: bb....bb

KECX09502-W

Property 'aa....aa' must be set in the user configuration file of J2EE server 'usrconf.properties'.

The property 'aa....aa' is not set up in the user-defined file usrconf.properties of the J2EE server.

KECX09503-W

Property 'bb....bb' must be set in the schema definition file 'aa....aa'.

The property 'bb....bb' is not set up in the schema definition file 'aa....aa'.

KECX09504-W

Can not access the schema definition file 'aa....aa'.

The schema definition file 'aa....aa' cannot be accessed.

KECX09505-W

Can not access the diskcache_path 'bb....bb' specified in the schema definition file 'aa....aa'.

diskcache_path 'bb....bb' specified in the schema definition file 'aa....aa' cannot be accessed.

KECX09506-E

Can not access the internal file for executing the command.

The internal file that is required for executing the command cannot be accessed.

KECX09507-W

The value of diskcache_path in the schema definition file 'aa....aa' must be absolute path.

The value of diskcache_path in the schema definition file 'aa....aa' must be an absolute path.

KECX09508-W

The value of schema_path in the schema definition file 'aa....aa' must be absolute path.

The value of schema_path in the schema definition file 'aa....aa' must be an absolute path.

KECX09509-W

The value of 'aa....aa' in the schema definition file 'bb....bb' must be relative path.

The value of 'aa....aa' in the schema definition file 'bb....bb' must be a relative path.

KECX09510-E

Invalid server name. 'aa....aa'

The server name is invalid. 'aa....aa'

KECX09511-W

Can not write schema grammar corresponding to the XMLSchema document 'aa....aa' to disk cache.

The schema grammar corresponding to the XML schema document 'aa....aa' cannot be written to the disk cache.

KECX09512-W

Can not read schema grammar corresponding to the XMLSchema document 'aa....aa' from disk cache.

The schema grammar corresponding to the XML schema document 'aa....aa' cannot be read from the disk cache.

KECX09513-E

'aa....aa': Invalid parameter.

usage: 'bb....bb'

'aa....aa': Invalid argument.

Usage: 'bb....bb'

KECX09601-E

An error occurred while pre-parsing the document : aa....aa

An error occurred while pre-parsing the document.aa....aa

KECX09602-E

XML file cannot be null.

Specify a value that is not null for the XML file.

KECX09603-E

Error occurs in Tuning Information : aa....aa

An error occurred in tuning information.aa....aa

KECX09604-E

Cannot access to file : aa....aa

The file aa....aa could not be accessed.

KECX09605-E

I/O Error occurs in temporary directory of fast parse function : aa....aa

An I/O error occurred in the temporary directory of the high-speed parse support function. aa....aa

KECX09606-E

Illegal value for preparsedobject-load property.

The specified value of the preparsedobject-load property is invalid.

KECX09607-E

Error occurs in custom scanner loading : aa....aa

An error occurred while loading the custom scanner.aa....aa

KECX09608-E

XML InputStream cannot be null.

Specify a value that is not null in the XML input stream.

11.9 Messages related to JAXB

From all the messages output by Cosminexus XML Processor, this section describes the messages related to JAXB.

Directory "aa....aa" doesnt exist.

The directory "aa....aa" does not exist.

Unrecognized option aa....aa is not valid.

aa....aa is an invalid option.

Option "aa....aa" is missing an operand.

An operand is missing from the option "aa....aa".

Prefix "aa....aa" is undeclared

The prefix "aa....aa" has not been declared.

extensionBindingPrefixes attribute must be declared at the root element

The extensionBindingPrefixes attribute must be declared in the root element.

vendor extension bindings (jaxb:extensionBindingPrefixes) are not allowed in the strict mode.

The vendor extension binding (jaxb:extensionBindingPrefixes) cannot be executed in the strict mode.

Unsupported binding namespace "aa....aa". Perhaps you meant "bb....bb"?

The binding namespace "aa....aa" is not supported. A corrected choice is "bb....bb".

Binding declaration namespace "aa....aa" will be ignored because it is not designated by the jaxb:extensionBindingPrefixes attribute.

The binding declaration namespace "aa....aa" will be ignored because the namespace is not specified by the jaxb:extensionBindingPrefixes attribute.

The following location is relevant to the above error

The above error occurred at this location.

Unable to find type "aa....aa". Without knowing the proper inheritance hierarchy of this type, XJC may fail to generate some signatures correctly.

The type "aa....aa" is not found. If the correct inheritance hierarchy of this type is not known, XJC might fail to correctly generate some signatures.

Property "aa....aa" is already defined. Use &lt;jaxb:property> to resolve this conflict.

The property "aa....aa" is already defined. Use <jaxb:property> to resolve this conflict.

Element "aa....aa" shows up in more than one properties.

The element "aa....aa" has been defined in more than one property.

Property name "Class" is reserved by java.lang.Object.

Class is the reserved property name of java.lang.Object.

"aa....aa" is not a valid customization.

The "aa....aa" customization is invalid.

Using "bb....bb" customizations requires the "-aa....aa" switch to enable this plug-in.

For using the "bb....bb" customization, you must specify the"-aa....aa" switch to enable this plugin.

A class/interface with the same name "aa....aa" is already in use. Use a class customization to resolve this conflict.

A class or interface with the same name as "aa....aa" is already in use. Use the class customization to resolve this conflict.

(Relevant to above error) another "aa....aa" is generated from here.

(Related to the above error) A class or interface same as "aa....aa" is generated from here.

Invalid class name "aa....aa". Either XJC has failed to derive a class name from XML name, or invalid name is given. Use <jaxb:class> customization to override a name.

"aa....aa" is an invalid class name. Either XJC has failed to derive a class name from the XML name or an invalid class name has been specified. Use the <jaxb:class> customization to override the class name.

This error is caused because on Windows you cannot have both "aa....aa.java" and "bb....bb.java" in the same directory.

This error occurred because you cannot place both "aa....aa.java" and "bb....bb.java" in the same directory for Windows.

(Relevant to above error) This confusing error happened most likely because the schema uses a technique called "chameleon schema", which causes a single definition to be loaded multiple times into different namespaces.

(Related to the above error) This error occurs mostly because of the use of a technique called chameleon schema. If you use chameleon schema, you can multiple times load a single definition into different namespaces.

the object parameter to marshal() is not marshallable

The object parameter passed to marshal()cannot be marshalled.

unsupported javax.xml.transform.Result parameter

The javax.xml.transform.Result parameter is not supported.

unsupported encoding: aa....aa

Encode aa....aa is not supported.

DOM implementation (aa....aa from bb....bb) is broken. It does not support the createElementNS method.

The DOM implementation (aa....aa from bb....bb) is damaged. The createElementNS method is not supported.

Unexpected text "aa....aa"

Text "aa....aa" is incorrect.

undefined prefix: aa....aa

The prefix aa....aa is not defined.

reader can not be null

Null cannot be specified for a reader.

reader must be on a START_ELEMENT event, not a aa....aa event

Set up the reader in the START_ELEMENT event, and not in the aa....aa event.

illegal entry: "aa....aa", entries should be of the form "ClassName" or "OuterClass.InnerClass", not "ClassName.class" or "fully.qualified.ClassName"

"aa....aa" is an invalid entry. Change the format of the entry to either ClassName or OuterClass.InnerClass. ClassName.class. fully.qualified.ClassName is an invalid format.

error loading class "aa....aa" listed in bb....bb, make sure that entries are accessible on CLASSPATH and of the form "ClassName" or "OuterClass.InnerClass", not "ClassName.class" or "fully.qualified.ClassName"

An attempt to load the class "aa....aa" listed in bb....bb has failed. Confirm that the entry can be accessed with CLASSPATH, and is either in the ClassName or OuterClass.InnerClass format. ClassName.class and fully.qualified.ClassName are invalid formats.

bb....bb is not a valid value for property "aa....aa"

bb....bb is not a valid value for the property "aa....aa".

property "aa....aa" is not supported

The property "aa....aa" is not supported.

"aa....aa" doesnt contain ObjectFactory.class or jaxb.index

ObjectFactory.class or jaxb.index do not exist in "aa....aa".

"aa....aa" is an inner class, and therefore it can never have a default zero argument constructor. Add static.

As "aa....aa" is an inner class, it does not contain a default zero argument constructor. Specify static.

Map contains a wrong type

Map contains invalid type.

JDK's tools.jar was not found in aa....aa.

The tools.jar file of JDK was not found in aa....aa.

Cannot derive a valid Java identifier from "aa....aa". Specify a customization to change the name.

A valid Java identifier cannot be derived from "aa....aa". Specify a customization to change the name.

Type-safe enum has more than one values that share the same name "aa....aa". Use a typesafeEnumMemberName customization to resolve this conflict.

A type-safe enumeration has more than one value with the same name "aa....aa". Use the typesafeEnumMemberName customization to resolve this conflict.

Illegal constructor parameter aa....aa

The parameter aa....aa of the constructor is invalid.

Two declarations cause a collision in the ObjectFactory class.

A conflict has occurred in the ObjectFactory class because of two declarations.

(Related to above error) This is the other declaration.

(Related to the above error) This is one of the conflicting declarations.

Unable to parse "aa....aa" : bb....bb

"aa....aa" cannot be parsed. bb....bb

"aa....aa" is not a part of this compilation. Is this a mistake for "bb....bb"?

"aa....aa" is not included in this compilation. A corrected choice is "bb....bb"

XPath error: aa....aa

This is an XPath error. aa....aa

XPath evaluation of "aa....aa" results in empty target node

The target node returned as a result of the XPath evaluation of "aa....aa" is empty.

XPath evaluation of "aa....aa" results in too many (bb....bb) target nodes

There are excessive target nodes (bb....bb) returned as a result of the XPath evaluation of "aa....aa".

XPath evaluation of "aa....aa" needs to result in an element.

Only an element can be returned as a result of the XPath evaluation of "aa....aa".

XPath evaluation of "aa....aa" needs to result in an element of the schema language, but it results in bb....bb

An element of the schema language must be returned as a result of XPath evaluation of "aa....aa", however, bb....bb is returned.

Context node is not an element.

The context node is not an element.

The "aa....aa" customization is not associated with any schema element.

The "aa....aa" customization is not associated with any schema element.

A value of JAXB version attribute is wrong.

The value of the JAXB version attribute is incorrect.

JAXB version attribute must be present

The JAXB version attribute does not exist.

Both jaxb:version and version are present

Both the jaxb:version attribute and the version attribute exist.

We were unable to ensure the correctness of the schema: aa....aa

The validity of the schema aa....aa could not be confirmed.

Schema component designator support is disabled by default.

The support for the Schema Component Designator (SCD) is disabled by default.

Invalid SCD: aa....aa

The SCD is invalid.aa....aa

SCD "aa....aa" didnt match any schema component

A schema component matching the SCD "aa....aa" does not exist.

File name is not an URI.

The file name is not a URI.

IOException thrown when processing "aa....aa". Exception: bb....bb.

IOException was thrown while aa....aa was being processed.

An xmime:expectedContentTypes attribute is present on an incorrect element

The element, in which the xmime:expectedContentTypes attribute is specified, is incorrect.

Multiple <schemaBindings> are defined for the target namespace "aa....aa"

Multiple <schemaBindings> are defined in the target namespace "aa....aa".

Another <schemaBindings> is defined here

Another <schemaBindings> is defined here.

Cannot derive a name from schema. A name attribute specified to the <class> customization.

The name cannot be derived from a schema. The name attribute is specified in the <class> customization.

Specified name "aa....aa" is not a valid Java identifier.

The specified name "aa....aa" is not a valid Java identifier.

The package name "bb....bb" used for this schema is not a valid package name.

The package name "bb....bb" used in this schema is invalid.

Attempt to create a class having the same name as the reserved word "aa....aa".

An attempt is made to create a class with the name same as the reserved word "aa....aa".

The field name "aa....aa" is used by two different parts of a schema. See:

bb....bb

cc....cc

The field name "aa....aa" is used at two places within the same schema. See the following:

bb....bb

cc....cc

A type safe enum customization is specified to a simple type that cannot be mapped to a type safe enum.

The customization of a type-safe enumeration is specified for a simple type that cannot be mapped to a type-safe enumeration.

The relevant simple type declaration is specified at this location

The declaration of the simple type is specified here.

A name attribute is required to customize an anonymous simple type to type-safe enum.

The name attribute must be specified when customizing an anonymous simple type to a type-safe enumeration.

enum class customization is specified on a type that has no enumeration facet.

enum class customization is specified on a type that has no enumeration facet.

Unable to parse the expected MIME type "aa....aa". bb....bb.

The required MIME type "aa....aa".bb....bb cannot be parsed.

Unable to generate a property name from a model group. A customization is required.

The property name cannot be generated from a model group. A customization is required.

<javaType> customization in this context must be nested (JAXB spec sec 7.9.1):

<property>

<baseType>

<javaType ...>

</baseType>

</property>

The customization of the javaType element within this context must be nested. (Section 7.9.1 JAXB Specifications):

<property>

<baseType>

<javaType ...>

</baseType>

</property>

compiler was unable to honor this aa....aa customization. It is attached to a wrong place, or its inconsistent with other bindings.

The aa....aa customization could not be processed with the compiler. Either the customization is set at an incorrect place or contradicts with other bindings.

Two enum members yield the same constant name aa....aa

Two enumeration members have generated the same constant name aa....aa.

Simple type "aa....aa" was not mapped to Enum due to EnumMemberSizeCap limit. Facets count: bb....bb, current limit: cc....cc. You can use customization attribute "typesafeEnumMaxMembers" to extend the limit.

Simple type aa....aa was not mapped to the enumeration type due to the EnumMemberSizeCap limit. Facets count: bb....bb, current limit: cc....cc. You can use the customization attribute typesafeEnumMaxMembers to extend the limit.

Cannot generate a constant name from the enumeration value "aa....aa". Use <jaxb:typesafeEnumMember name="..."/> to specify one.

A constant name cannot be generated from the enumeration value "aa....aa". Use <jaxb:typesafeEnumMember name="..."/> to specify a constant name.

only one globalBindings customization is allowed in a whole compilation

Only one globalBindings customization can be executed in the entire compilation.

aa....aa is in a referenced schema and do not have the corresponding Java class specified by <jaxb:class ref="..."/> customization. Therefore it cannot be referenced from outside.

Although aa....aa exists in the referenced schema, aa....aa does not contain corresponding Java class specified by the <jaxb:class ref="..."/> customization. Therefore, it cannot be referenced from outside.

Cannot generate default value for primitive type "aa....aa".

The default value for the primitive type aa....aa cannot be generated.

the object parameter to marshal() is not marshallable

The object parameter passed to marshal() cannot be marshalled.

unsupported javax.xml.transform.Result parameter

The javax.xml.transform.Result parameter is not supported.

Object "aa....aa" is found in an IDREF property but this object doesnt have an ID.

Although the object "aa....aa" exists in the IDREF property, no ID is allocated to this object.

This feature is not available

This feature could not be used.

"bb....bb" property of a "aa....aa" object contains an object of type "cc....cc" but this is not allowed. See javadoc of this property for what this property can accept.

An object of type "cc....cc" is included in the property "bb....bb" of the object "aa....aa", but this type cannot be used. See javadoc to confirm which object types are supported by this property.

a required field "aa....aa" is missing an object

An object is missing in the required field "aa....aa".

An object is referenced as IDREF but its ID field is null

The ID field of an object referenced as IDREF is null.

A tree contains a reference to ID "aa....aa" but its not a part of the object graph

A tree has a reference to the ID "aa....aa", but is not included in the object graph.

schema output resolver must not be null

Null cannot be specified for the schema output resolver.

unable to marshal type "aa....aa" as an element because it is missing an @XmlRootElement annotation

The type "aa....aa" cannot be marshalled as an element because the @XmlRootElement annotation is not assigned.

unable to marshal type "aa....aa" as an element because it is not known to this context.

Type aa....aa cannot be marshaled as an element because it is not registered in this context.

"aa....aa" is not a supported property

The property "aa....aa" is not supported.

property name parameter can not be null

Null cannot be specified for the parameter of a property name.

property "aa....aa" must be an instance of type bb....bb, not cc....cc

The property "aa....aa" must be set as an instance of type bb....bb instead of type cc....cc.

Instance of "bb....bb" is substituting "aa....aa", but "cc....cc" is bound to an anonymous type.

An instance of type "bb....bb" can substitute type "aa....aa", but type "cc....cc" is bound to an anonymous type.

A cycle is detected in the object graph. This will cause infinitely deep XML: aa....aa

A loop was detected in the object graph. This will increase the XML hierarchy to a large extent. aa....aa

Unable to list methods of "aa....aa". If there is any event callback handler on this class, it will be ignored.

The methods of "aa....aa" cannot be listed. If an event callback handler is set up in this class, it will be ignored.

A DOM document "aa....aa" is found but an element is needed. Use Document.getDocumentElement() and set that object instead.

An element must be allocated to the DOM document "aa....aa". Use Document.getDocumentElement() to set the object.

aa....aa nor any of its super class is known to this context.

Neither aa....aa nor any of its super classes are registered in this context.

Failed to generate schema.

An attempt to generate the schema has failed.

Anonymous types form an infinite cycle: aa....aa

Anonymous types form an infinite loop. aa....aa

undefined simple type "aa....aa"

The simple type "aa....aa" is not defined.

undefined complex type "aa....aa"

The complex type "aa....aa" is not defined.

undefined simple or complex type "aa....aa"

The simple and complex type "aa....aa" are not defined.

undefined element declaration "aa....aa"

The element declaration "aa....aa" is not defined.

undefined model group "aa....aa"

The model group "aa....aa" is not defined.

undefined attribute "aa....aa"

The attribute "aa....aa" is not defined.

undefined attribute group "aa....aa"

The attribute group "aa....aa" is not defined.

undefined identity constraint "aa....aa"

The identity constraint "aa....aa" is not defined.

unbounded prefix "aa....aa"

The prefix "aa....aa" is not bound.

the target namespace of the included schema "aa....aa" doesn't agree with the expected value "bb....bb"

The target namespace of the included schema "aa....aa" does not match the expected value "bb....bb".

the target namespace of the imported schema "aa....aa" doesn't agree with the expected value "bb....bb"

The target namespace of the imported schema "aa....aa" does not match the expected value "bb....bb".

"aa....aa" is already defined

"aa....aa" is already defined.

a "schemaLocation" attribute is required

The schemaLocation attribute is required.

failed to retrieve "aa....aa": bb....bb

An attempt to acquire aa....aa has failed.bb....bb

A complex type with a simple content or a simple type is expected but found "aa....aa":bb....bb

A complex type with simple contents or a simple type is required, but "aa....aa" is being used. bb....bb

fixedAttributeAsConstantProperty is allowed only with attributes with a fixed value constraint.

You can use fixedAttributeAsConstantProperty only in an attribute to which a fixed value constraint is assigned.

undefined simple type "aa....aa".

The simple type "aa....aa" is not defined.

Simple type "aa....aa" is not allowed by the spec to be bound to a type-safe enum.

The simple type "aa....aa" cannot be bound to a type-safe enumeration according to the specifications.

Base complex type "aa....aa" is derived by restriction, while this complex type "bb....bb" is derived by extension. This is not currently handled by XJC.

The base complex type "aa....aa" is derived by restriction while the complex type "bb....bb" is derived by extension. Currently, these cannot be processed in XJC.

Specified aa....aa customization is not used.

The specified aa....aa customization is not used.

Unable to check the correctness of the schema due to OutOfMemoryError. This typically happens when your schema contains constructs like maxOccurs="999".

The validity of the schema could not be confirmed due to OutOfMemoryError. This error normally occurs when a constructor such as maxOccurs="999" exists within the schema.

No JAXB customization was detected in the schema but the prefix "jaxb" is used for other namespace URIs. If you did intend to use JAXB customization, make sure the namespace URI is "aa....aa"

A JAXB customization was not detected in the schema, but the "jaxb" prefix is being used in another namespace URI. When using the JAXB customization, set the namespace URI to "aa....aa".

Annotation "aa....aa" is present on both "bb....bb" and "cc....cc"

The annotation "aa....aa" is assigned to both "bb....bb" and "cc....cc".

Property "aa....aa" has an XmlID annotation but its type is not String.

The property "aa....aa" has the XmlID annotation but its type is not String.

aa....aa has mutually exclusive annotations @bb....bb and @cc....cc

Annotations @bb....bb and @cc....cc that cannot be specified concurrently are assigned to aa....aa.

@aa....aa annotation is found on two places; one would be suffice.

The @aa....aa annotation was found at two places. It can be specified only at one place.

aa....aa does not have a no-arg default constructor.

The zero argument default constructor is missing in aa....aa.

aa....aa is an interface, and JAXB can't handle interfaces.

aa....aa is an interface. Interfaces cannot be processed in JAXB.

aa....aa is a non-static inner class, and JAXB can't handle those.

aa....aa is a non-static inner class. Such a class cannot be processed in JAXB.

JAXB annotation is placed on a method that is not a JAXB property

A JAXB annotation is assigned to a method that does not have a JAXB property.

The type of the getter is aa....aa but that of the setter is bb....bb. They have to be the same.

The getter method has the type aa....aa, while the setter method has the type bb....bb. Set a same type for both the methods.

Property "aa....aa" appears more than once in the @XmlType.propOrder

The property "aa....aa" appears more than once in @XmlType.propOrder.

There are two properties named "aa....aa"

Two properties exist with the name "aa....aa".

The aa....aa method has @XmlElementMapping on it, but it doesn't return a sub-type of JAXBElement.

The @XmlElementMapping annotation is set in the aa....aa method, but it does not return a sub type of JAXBElement.

aa....aa is not bound to a complex type, and therefore illegal as the scope.

The aa....aa is not bound to a complex type, so the valid scope is incorrect.

The element name '{'aa....aa'}'bb....bb has more than one mapping.

The element name '{'aa....aa'}'bb....bb has more than one mapping.

No element mapping exists for "aa....aa":"bb....bb"

No element mapping exists for "aa....aa":"bb....bb".

aa....aa has two properties with the @XmlAnyAttribute annotation.

Two properties with the @XmlAnyAttribute annotation exist in aa....aa.

Can't have @XmlAnyAttribute when a base class has it already.

The @XmlAnyAttribute annotation cannot be set if it is already assigned to a base class.

@XmlAnyAttribute is placed on a property whose type is aa....aa but it needs to be assignable to java.util.Map.

The @XmlAnyAttribute annotation is assigned to a property with type aa....aa. However, you must be able to assign it to java.util.Map.

Property aa....aa is present but not specified in @XmlType.propOrder

The property aa....aa exists but is not specified in @XmlType.propOrder.

Property aa....aa appears in @XmlType.propOrder, but no such property exists. Maybe you meant bb....bb?

The property aa....aa is specified in @XmlType.propOrder, but no such property exists.

Corrected choice:bb....bb.

"aa....aa" is not a valid value for bb....bb.

"aa....aa" is not a valid value for bb....bb.

Failed to initialize JAXP 1.3 DatatypeFactory class.

An attempt to initialize the DatatypeFactory interface of JAXP1.3 has failed.

No javax.imageio.ImageWriter is available for the specified MIME type "aa....aa"

No javax.imageio.ImageWriter is available for the specified MIME type "aa....aa".

"aa....aa" is not a valid MIME type: bb....bb

"aa....aa" is an invalid MIME type. bb....bb

aa....aa annotation cannot be placed here

The aa....aa annotation cannot be assigned here.

@XmlValue is only allowed one per class, but two properties are annotated with @XmlValue.

You can use only a single @XmlValue annotation in each class. However, there are two properties with the @XmlValue annotation.

@XmlValue is not allowed on a class that derives another class.

The @XmlValue annotation cannot be used in a class derived from another class.

If a class has @XmlElement property, it cannot have @XmlValue property.

A class containing a property with @XmlElement cannot have a property with @XmlValue.

Two classes have the same XML type name "aa....aa". Use @XmlType.name and @XmlType.namespace to assign different names to them.

Two classes have the same XML type name "aa....aa". Use @XmlType.name and @XmlType.namespace to assign different names to the classes.

@XmlAttribute/@XmlValue need to reference a Java type that maps to text in XML.

@XmlAttribute or @XmlValue must reference the Java type mapped to the text within the XML.

Class has two properties of the same name "aa....aa"

Two properties with the same name "aa....aa" exist in a class.

XmlIDREF property is referencing a type "aa....aa" that doesn't have an XmlID property.

The XmlIDREF property is referencing the type "aa....aa" that does not have the XmlID property.

Invalid @XmlElementRef : Type "aa....aa" or any of it's subclasses are not known to this context.

Invalid XmlElementRef: Type aa....aa and the subclasses of type aa....aa are not registered in this context.

There's no ObjectFactory with an @XmlElementDecl for the element '{'aa....aa'}'bb....bb.

ObjectFactory with @XmlElementDecl does not exist in the element '{'aa....aa'}'bb....bb.

@XmlElementWrapper is only allowed on a collection property but "aa....aa" is not a collection property.

You can use the @XmlElementWrapper annotation only in a collection property. However, "aa....aa" is not a collection property.

aa....aa annotation is not allowed on this kind of property.

The aa....aa annotation cannot be used in this kind of properties.

aa....aa maps to a structured XML fragment (AKA complex type), and therefore incompatible with @XmlList.

As aa....aa is mapped to a structured XML fragment (Alias complex type), aa....aa is incompatible with @XmlList.

@XmlList cannot be placed on a single-value property

The @XmlList annotation cannot be assigned to properties having single value.

Factory class "aa....aa" does not have static zero args factory method "bb....bb".

The factory class "aa....aa" does not have a zero argument static factory method "bb....bb".

XmlType has not defined a factory method for Factory class "aa....aa".

The factory method of the factory class "aa....aa" is not defined in XmlType.

Package "aa....aa" is missing jaxb.properties file. Have you copied this from the generated source directory or include it in the classpath?

The jaxb.properties file does not exist in the package "aa....aa". Either copy the file from the source directory in which the jaxb.properties file was generated or include it in the class path.

Transient field "aa....aa" cannot have any JAXB annotations.

A JAXB annotation cannot be assigned to the transient field "aa....aa".

Object must have some value in its @XmlValue field: aa....aa

An object must have some value in its @XmlValue field. aa....aa

You are trying to run JAXB 2.0 runtime (from bb....bb) but you have old JAXB 1.0 runtime earlier in the classpath (at aa....aa) Please remove the JAXB 1.0 runtime for 2.0 runtime to work correctly.

An attempt is made to execute JAXB 2.0 runtime (from bb....bb), but an old JAXB 1.0 runtime exists before the classpath (at aa....aa). Remove the JAXB 1.0 runtime for the 2.0 runtime to work properly.

Adapter aa....aa is not applicable to the field type bb....bb.

The adapteraa....aa is not applicable to the field type bb....bb.

Unable to create instance of AccessorFactory, aa....aa for class bb....bb.

The AccessorFactory instance aa....aa cannot be created for class bb....bb.

Unable to access instance of AccessorFactory, aa....aa for class bb....bb.

The AccessorFactory instance aa....aa of class bb....bb cannot be accessed.

Custom AccessorFactory, aa....aa, is reporting an error accessing a property. bb....bb

An error is reported from Custom AccessorFactoryaa....aa when property bb....bb is accessed.

Custom AccessorFactory, aa....aa, is reporting an error accessing a field. bb....bb

An error is reported from Custom AccessorFactoryaa....aa when field bb....bb is accessed.

aa....aa is used as an array component type, so it cannot be anonymous.

As the aa....aa is used as an array component type, it cannot be set to anonymous.

Invalid set of fields set for XMLGregorianCalendar type aa....aa.

An invalid field set is specified for the XMLGregorianCalendar type aa....aa.

Unable to make aa....aa.bb....bb accessible.

aa....aa.bb....bb cannot be set to an accessible state.

The type of the field is aa....aa, but the type of the object is bb....bb

The type of the field is aa....aa while the type of the object is bb....bb.

The property has a getter "aa....aa" but no setter. For unmarshalling, please define setters. (Or if this is a collection property, make sure that the getter returns a collection instance.)

This property has a getter "aa....aa", but no setter. A setter must be defined for unmarshalling (for a collection property, confirm that the getter returns a collection instance).

The property has a setter "aa....aa" but no getter. For marshaller, please define getters.

This property has a setter "aa....aa", but no getter. A getter must be defined for marshalling.

aa....aa is not a valid Qname

aa....aa is an invalid Qname.

unrecognized type name: aa....aa

The type name aa....aa cannot be recognized.

unrecognized type name: aa....aa. Did you mean bb....bb?

The type name aa....aa cannot be recognized. A corrected choice is bb....bb.

Undefined ID "aa....aa".

The ID "aa....aa" is not defined.

unexpected element (uri:"aa....aa", local:"bb....bb"). Expected elements are cc....cc

This is an unexpected element (uri: "aa....aa", local name: "bb....bb"). The required element is cc....cc.

unexpected text "aa....aa"

"aa....aa" is an unexpected text.

The type of the field is aa....aa, but JAXB doesnt know how to create an instance assignable to it. Create an instance in the constructor, or use a type that can be assignable from HashMap.

The type of the field is aa....aa, but the method of creating an instance that can be assigned to this field is not clear. Either create the instance with the constructor or use an assignable type from HashMap.

Namespace URIs and local names to the unmarshaller needs to be interned.

The namespace URIs and local names to be passed to the Unmarshaller must be registered with the intern function.

java content interface Class object must not be null

The java content interface class object must not be null.

unable to locate "aa....aa". Check if this file is in the classpath.

"aa....aa" could not be found. Confirm that this file exists in the class path.

unable to extract the schema information

The schema information cannot be acquired.

root element collision detected for '{'aa....aa'}'bb....bb - unable to create JAXBContext with the given contextPath

A root element collision was detected for {'aa....aa'}'bb....bb. JAXBContext cannot be created with the provided contextPath.

neither map contained contentInterface: aa....aa

Neither of maps contains contentInterface. aa....aa

a required field "aa....aa" is missing an object

A required field "aa....aa" is missing from the object.

Element "'{'aa....aa'}'bb....bb" is not allowed by the wildcard

The element "'{'aa....aa'}'bb....bb" is not allowed as a wildcard.

another object has the ID value of ''aa....aa''

Another object has the ID value ''aa....aa'.

the object pointed by IDREF is not a part of the content tree

The object indicated by IDREF is not a part of the content tree.

a required object is missing

A required object is missing.

the object parameter to validate() or validateRoot() is not validatable

The arguments of validate() or validateRoot() are not to be validated.

the content tree forms a cycle

The content tree forms a loop.

aa....aa parameter must not be null

The aa....aa parameter must not be null.

derivation from type "aa....aa" by list is prohibited.

The type aa....aa cannot be derived by list.

derivation from type "aa....aa" by union is prohibited.

The type aa....aa cannot be derived by union.

derivation from type "aa....aa" by restriction is prohibited.

The type aa....aa cannot be derived by restriction.

facet "aa....aa" must be an integer greater than or equal to 0

An integer value of 0 or more must be set in the facet aa....aa.

facet "aa....aa" must be an integer greater than zero

An integer value of 1 or more must be set in the facet aa....aa.

facet "aa....aa" is specified as fixed in the base type.

The facet aa....aa is specified as fixed in the base type, and therefore, it cannot be specified anymore.

union type is derived with no member type

A member type is required for defining the union type.

specified pattern is invalid: aa....aa

The specified regular expression is invalid. aa....aa

values of the aa....aa facet and the bb....bb facet are inconsistent

The value of the facet aa....aa contradicts the value of the facet bb....bb.

values of the aa....aa facet is inconsistent with the cc....cc facet of "bb....bb" type, which is used as the base type.

The value of the facet aa....aa contradicts the value of the facet cc....cc that is specified in the base type bb....bb.

The facets aa....aa and bb....bb are mutually exclusive

The facet aa....aa cannot be specified concurrently with the facet bb....bb.

the value of the aa....aa facet is looser than the same facet on the "bb....bb" type.

The value of the facet aa....aa is lesser than the value specified in the base type bb....bb.

the specified value "aa....aa" is not a/an bb....bb

"aa....aa" is not a valid value for the facet bb....bb.

"aa....aa" is not a valid whiteSpace facet value: it must be preserve, replace, or collapse

"aa....aa" is not a valid value of the whiteSpace facet. Specify any one from preserve, replace, or collapse.

facet aa....aa is specified more than once

The facet aa....aa cannot be specified more than once.

facet aa....aa is not applicable to this datatype

The facet aa....aa cannot be used in this data type.

"aa....aa" does not satisfy the "bb....bb" type

aa....aa is not a value of the type bb....bb.

the value has aa....aa digits, where precision must be within bb....bb.

The value has aa....aa digit, whereas it must be within bb....bb digit.

the value has aa....aa fractional digits, where scale must be within bb....bb.

The value has aa....aa fractional digit, whereas it must be within bb....bb digit.

the value is not a member of the enumeration.

The value is not from the enumerated values.

the value is not a member of the enumeration: aa....aa

The value must be one of the following: aa....aa

the value is out of the range (aa....aa specifies bb....bb).

The value exceeds the limited range (the facet aa....aa is bb....bb).

the length of the value is aa....aa, but the required length is bb....bb.

The length of the value is aa....aa. However, the length must be bb....bb.

the length of the value is aa....aa, but the required minimum is bb....bb.

The length of the value is aa....aa. However, the length must be bb....bb or more.

the length of the value is aa....aa, but the required maximum is bb....bb.

The length of the value is aa....aa. However, the length must be bb....bb or less.

the value does not match the regular expression "aa....aa".

The value does not match the specified regular expression "aa....aa".

the value does not match any of the regular expressions.

The value does not match any of the specified regular expressions.

element "aa....aa" is not allowed here

The element "aa....aa" cannot be written here.

character data not allowed: aa....aa

Character data is not allowed. aa....aa

"bb....bb" attribute is not allowed for "aa....aa" element.

The "bb....bb" attribute cannot be specified in the "aa....aa" element.

"bb....bb" attribute is required for "aa....aa" element, but is not specified

The "bb....bb" attribute is required for the "aa....aa" element, but is not specified.

"bb....bb" or "cc....cc" attribute is required for "aa....aa" element, but none is specified

The "bb....bb" attribute or the "cc....cc" attribute is required in the "aa....aa" element, but neither of them is specified.

"bb....bb" is invalid value for "aa....aa" attribute

The value "bb....bb" cannot be specified in the "aa....aa" attribute.

"aa....aa" and "bb....bb" are mutually exclusive, so cannot be specified at the same time.

The "aa....aa" attribute and the "bb....bb" attribute cannot be specified concurrently as they are contradictory.

more than one child type is specified

Multiple child types are specified.

no child type is specified

No child type is specified.

unrecognized value "aa....aa" in final attribute.

"aa....aa" is an invalid value for the final attribute.

recursive inclusion is detected ( aa....aa )

A recursive inclusion is detected (aa....aa).

URL "aa....aa" contains a fragment identifier.

The URL "aa....aa" contains a fragment identifier.

data type "aa....aa" is not defined

The "aa....aa" data type is not defined.

data type "aa....aa" is already defined

The "aa....aa" data type is already defined.

perhaps namespace URI "aa....aa" is incorrect?

The namespace URI "aa....aa" might be incorrect.

Datatype "aa....aa" is obsolete name. Please use "bb....bb" instead.

"aa....aa" is an old name. Use "bb....bb" instead.

Recursive datatype definition.

The data type definition is recursive.

child model group is missing

There is no child content model.

more than one model group is specified whereas only one is allowed

Multiple content models are specified.

the following model groups form a infinite recursion ( aa....aa )

Some model group definitions are recursive (aa....aa).

this can't be used because XML Schema does not have notion of the root element

The XML Schema is not used as it does not have the concept of the root element.

maxOccurs attribute is required when minOccurs is more than 1

The maxOccurs attribute is required as the minOccurs attribute is more than one.

Unimplemented feature: "aa....aa"

The feature is not supported."aa....aa"

namespace prefix "aa....aa" is not declared

The namespace prefix "aa....aa" is not declared.

schema's target namespace is "aa....aa", although "bb....bb" is expected

"aa....aa" is specified as the target namespace of the schema. However, "bb....bb" is expected at the calling side.

importing a schema of the same namespace

The schema, belonging to the same namespace, is imported.

namespace "aa....aa" is already defined by a schema

The namespace "aa....aa" is already defined by another schema.

type "aa....aa" is not a simple type nor a complex type

The "aa....aa" type is neither a simple type nor complex type.

reference to the undefined attribute declaration: "aa....aa"

An undefined attribute declaration "aa....aa" is referenced.

reference to the undefined attribute group: "aa....aa"

An undefined attribute group "aa....aa" is referenced.

reference to the undefined complex type: "aa....aa"

An undefined complex type "aa....aa" is referenced.

reference to the undefined simple type: "aa....aa"

An undefined simple type "aa....aa" is referenced.

reference to the undefined element declaration: "aa....aa"

An undefined element declaration "aa....aa" is referenced.

reference to the undefined group: "aa....aa"

An undefined group "aa....aa" is referenced.

reference to the undefined simple or complex type: "aa....aa"

An undefined complex type or simple type "aa....aa" is referenced.

reference to the undefined key: "aa....aa"

An undefined key "aa....aa" is referenced.

namespace "aa....aa" is referenced but no schema definition of this namespace was found.

The namespace "aa....aa" is referenced, but the schema defining this namespace does not exist.

the base type "aa....aa" cannot be used as a base type for a complex type with simple content.

"aa....aa" cannot be used as the base type for a complex type with simple content.

"http://www.w3.org/2000/10/XMLSchema" is obsolete as XML Schema namespace. use "http://www.w3.org/2001/XMLSchema" instead.

http://www.w3.org/2000/10/XMLSchema is the old namespace. Use http://www.w3.org/2001/XMLSchema.

attempt to redefine undefined component "aa....aa".

An attempt is made to redefine the component "aa....aa", but the original definition is not found.

attribute "aa....aa" is already defined.

The attribute declaration "aa....aa" is already defined.

complex type "aa....aa" is already defined.

The complex type"aa....aa" is already defined.

attribute group "aa....aa" is already defined.

The attribute group "aa....aa" is already defined.

model group "aa....aa" is already defined.

The group "aa....aa" is already defined.

element "aa....aa" is already defined.

The element declaration "aa....aa" is already defined.

identity constraint "aa....aa" is already defined.

The identity constraint "aa....aa" is already defined.

bad XPath "aa....aa".

XPath aa....aa is incorrect.

"aa....aa" is not a key.

"aa....aa" is not a key name.

The specified key "aa....aa" has bb....bb fields but this keyref "cc....cc" has dd....dd fields.

The referenced key "aa....aa" has bb....bb fields, but the key reference "cc....cc" has only dd....dd fields.

The element "aa....aa" is designated as the substitution affiliation of "bb....bb", but they have unrelated types.

The element declaration "bb....bb" is included in the substitution group of the element declaration "aa....aa", however, their types are not related.

The element "aa....aa" and bb....bb" forms cyclic substitution relationship.

Element declarations "aa....aa" and "bb....bb" configure cyclic substitution groups.

"anyType" is implicitly used as the content model of this element. Is this your intention? If so, please consider to write it explicitly as type="anyType".

As the type attribute does not exist, the contents of this element are not validated at all. Is this what you intend to do? If yes, please write it explicitly as type="anyType".

unexpected character literal

Character data is not allowed here.

unexpected attribute "aa....aa"

The attribute "aa....aa" is incorrect.

unexpected start tag "aa....aa".

The element "aa....aa" is not allowed here.

some attributes are missing for the element "aa....aa".

The element "aa....aa" does not contain all required attributes.

Content of element "aa....aa" is incomplete

The contents of the element "aa....aa" are incomplete.

"aa....aa" is referenced by an IDREF, but not defined.

"aa....aa" is referenced by an IDREF, but is not defined.

"aa....aa" is used as an ID value more than once.

"aa....aa" is used as an ID value more than once.

unexpected element "aa....aa"

The element "aa....aa" is not allowed here.

field #cc....cc of the key constraint "bb....bb" is not found

The field #cc....cc of key constraint "bb....bb" does not exist.

this element does not satisfy the uniqueness imposed by "bb....bb"

This element does not satisfy the unique constraint "bb....bb".

The same key value is used

The same key value is used here.

more than one elements/attributes match the field #cc....cc of the identity constraint "bb....bb"

More than one element or attribute matches the field #cc....cc of the id constraint "bb....bb".

keyref "bb....bb" does not have a corresponding key

No key corresponds to keyref "bb....bb".

element "aa....aa" was found where no element may occur

The element "aa....aa" was found at a location where no elements can be written.

The content model of this element can never be satisfied as declared. It may be a bug of the schema.

The content model of this element can never be satisfied. Some part of the schema might be missing.

tag name "aa....aa" is not allowed

The element "aa....aa" cannot be written here.

tag name "aa....aa" is not allowed. Possible tag names are: bb....bb

The element "aa....aa" cannot be written here, though bb....bb can be written.

namespace URI of tag "aa....aa" is wrong. It must be "bb....bb"

The namespace of the element "aa....aa" is incorrect. It must be "bb....bb".

Probably namespace URI of tag "aa....aa" is wrong (correct one is "bb....bb")

The namespace of the element "aa....aa" might be incorrect. The correct namespace is "bb....bb".

unexpected attribute "aa....aa"

The attribute "aa....aa" cannot be written here.

attribute "aa....aa" has a bad value

The value of the attribute "aa....aa" is incorrect.

attribute "aa....aa" has a bad value: bb....bb

The value of the attribute "aa....aa" is incorrect. bb....bb

attribute "aa....aa" has a bad value. Possible values are: bb....bb

The value of the attribute "aa....aa" must be any one of the following: bb....bb

element "aa....aa" is missing "bb....bb" attribute

The attribute "bb....bb" is required in the element "aa....aa".

required attribute(s) is/are missing

Some required attributes are missing.

at least one of the following attributes is required for element "aa....aa": bb....bb

At least one of the following attributes is required for the element "aa....aa": bb....bb

uncompleted content model. expecting: bb....bb

An element cannot be closed here. One of the following is required: bb....bb

unexpected character literal. expecting: aa....aa

This is an incorrect character string. One of the following is required: aa....aa

bad character literal.

The character literal is invalid.

the value must be "aa....aa"

The text must be "aa....aa".

elements of "aa....aa" namespace

This is an element of the namespace "aa....aa".

elements of any namespace other than "aa....aa"

This is an element of any namespace other than "aa....aa".

character data is not allowed here

Character data cannot be written here.

ID "aa....aa" is already defined.

The ID "aa....aa" is already in use.

duplicate key value "aa....aa" for the symbol space "bb....bb"

The key "aa....aa" is already in use in the symbol space "bb....bb".

element "aa....aa" is not nillable

The element "aa....aa" is not nillable.

specified type "aa....aa" cannot substitute the current type

The current type cannot be substituted with the specified type "aa....aa".

undefined type "aa....aa"

"aa....aa" is not defined as a type.

Argument(s) "aa....aa" can't be null.

You cannot specify null in the argument aa....aa.

aa....aa is a primitive

aa....aa is a primitive type.

? super T not implemented

<? super T> is not implemented.

only extends/super can follow ?, but found aa....aa

Although only extends or super can be added after ? (question mark), aa....aa is added.

Expected ']' but found aa....aa

aa....aa was found at a location in which ']' must be used.

Missing '>' in aa....aa

A greater-than sign (>) is missing from aa....aa.

JClass name empty

The JClass name is empty.

JClass name aa....aa contains illegal character for beginning of identifier: bb....bb

An invalid character bb....bb is included at the beginning of the identifier in the JClass name aa....aa.

JClass name aa....aa contains illegal character bb....bb

An invalid character bb....bb is included in the JClass name aa....aa.

unable to set the super class for an interface

This super class cannot be set in the interface.

Illegal class inheritance loop. Outer class aa....aa may not subclass from inner class: bb....bb

An invalid loop occurred in class inheritance. The outer class aa....aa cannot be sub classed from the inner class bb....bb.

trying to create the same field twice: aa....aa

An attempt is made to create the same field aa....aa twice.

Field name contains '.': aa....aa

The field name contains a period (.). aa....aa

name aa....aa is already in use

The name aa....aa is already in use.

method name contains '.': aa....aa

The method name contains a period (.). aa....aa

Cannot have two varargs in a method,

Check if varParam method of JMethod is invoked more than once

Two variable-length arguments (varargs) cannot be used in one method. Confirm that the varParam method of Jmethod is not invoked two or more times.

Illegal modifiers for aa....aa: bb....bb

An invalid modifier is used for aa....aa. bb....bb

Package name . is not allowed

A period (.) cannot be used in the package name.

the specified class is not a member of this package, or it is a referenced class

The specified class is not a member of this package, but a referenced class.

JClass name contains '.': aa....aa

A period (.) is included in the JClass name. aa....aa

the root package cannot be annotated

An annotation cannot be assigned to the root package.

Not a primitive type: aa....aa

This is not a primitive type. aa....aa

Not an array type

This is not an array type.

type variable has an existing class bound aa....aa

An existing class bind aa....aa is included in the type variable.

Unable to handle this method call aa....aa

The method call aa....aa cannot be processed.

Unexpected return type aa....aa

The return type aa....aa is incorrect.

Unable to handle this method call

This method call cannot be processed.

Expected aa....aa but found bb....bb

A location that must be aa....aa is actually bb....bb.

unable to process aa....aa line:bb....bb

cc....cc

Lines bb....bb and cc....cc of aa....aa cannot be processed.

aa....aa: non-existent directory

aa....aa: This directory does not exist.

aa....aa: Can't delete previous version

aa....aa: The old version cannot be deleted.

The current event is not START_ELEMENT

but aa....aa

The current event is aa....aa instead of START_ELEMENT.

processing event: aa....aa

The event aa....aa is being processed.

getAttributes() attempting to process: aa....aa

An attempt is made to process aa....aa with getAttributes().

Loaded outside a jar aa....aa

Loaded outside jar aa....aa.

Error starting apt

An error occurred while starting apt.

the same namespace is specified twice

The same namespace is specified twice.

should throw a MirroredTypeException

MirroredTypeException must be thrown.

Attempt to modify attribute at illegal index: aa....aa

An attempt is made to modify the attribute aa....aa of an invalid index.

Unexpected aa....aa appears at line bb....bb column cc....cc

An unexpected value aa....aa appears at line bb....bb column cc....cc.

There's no JAXB 2.2 API in the classpath

JAXB 2.2 API does not exist in the classpath.

Unrecognized language: aa....aa. Did you mean bb....bb ?

The language aa....aa cannot be recognized. The corrected choice is bb....bb.

Unrecognizable stack size: aa....aa

The stack size aa....aa cannot be recognized.

aa....aa is not a valid version number. Perhaps you meant @destdir?

aa....aa is an invalid version number. Specify @destdir.

unable to parse the schema. Error messages should have been provided

The schema cannot be parsed. An error message must be displayed.

failed to compile a schema

An attempt to compile the schema has failed.

unable to write files: aa....aa

An attempt to write to the file has failed.aa....aa

Illegal version aa....aa

aa....aa is an invalid version.

nulls in additionalElementDecls

additionalElementDecls is null.

aa....aa was not specified to JavaCompiler.bind

aa....aa is not specified in JavaCompiler.bind.

system ID 'aa....aa' isn't absolute

The system ID 'aa....aa' is not complete.

Class not foundaa....aa

The class aa....aa is not found.

Unable to load source code of aa....aa as a resource

The source code of aa....aa cannot be loaded as a resource.

system id cannot be null

The system ID cannot be null.

Unable to find a JAXB implementation to delegate

The JAXB implementation to be delegated is not found.

Not a number: aa....aa

aa....aa is not a number.

input is empty

The input value is empty.

prefix aa....aa is not bound to a namespace

The prefix aa....aa is not bound to the namespace.

hexBinary needs to be even-length: aa....aa

hexBinary must have an even length. aa....aa

contains illegal character for hexBinary: aa....aa

hexBinary contains invalid characters.aa....aa

Attempt to modify attribute at illegal index: aa....aa

An attempt is made to modify the attribute aa....aa of an invalid index.

Unknown constant type aa....aa

aa....aa is an unknown constant type.

no encoder for MIME type aa....aa

No encoder is available for the MIME type aa....aa.

The factory method didn't return a correct object

The object returned from the factory method is not correct.

Failed to find the constructor for aa....aa with bb....bb

The constructor for aa....aa containing bb....bb is not found.

aa....aa is not known to this context

aa....aa cannot be recognized by this context.

aa....aa is not a bean

aa....aa is not a bean.

aa....aa is not a valid property on bb....bb

aa....aa is an invalid property for bb....bb.

prefix 'aa....aa' isn't bound

The prefix 'aa....aa' is not bound.

The current event is not START_ELEMENT but aa....aa

The current event is aa....aa and not START_ELEMENT.

Unexpected node type: aa....aa

aa....aa is an unexpected node type.

Error escaping one of these uris:

aa....aa

bb....bb

An error occurred during the escape processing of the following URIs:

aa....aa

bb....bb

Malformed URL aa....aa(base bb....bb )

The URL has an invalid format. aa....aa (Base bb....bb)

start tag has already been written

The start tag has already been coded.

Illegal return type: aa....aa

The return type is invalid. aa....aa

argument contains null

Null is included in the argument.

Unexpected use of prefixes aa....aa

The use of the prefix aa....aa is incorrect.

The empty namespace cannot have a non-empty prefix

A non-empty prefix cannot be assigned to an empty namespace.

The empty namespace can be only bound to the empty prefix

An empty namespace can be bound only to an empty prefix.

Prefix 'aa....aa' is already bound to 'bb....bb'

The prefix 'aa....aa' is already bound to 'bb....bb'.

The start tag of aa....aa has already been written.

The start tag of aa....aa is already coded.

Your DOM provider doesn't support the createElementNS method properly

Your DOM provider does not support the properties of the createElementNS method.

Unsupported Result type: aa....aa

The result type aa....aa is not supported.

LexicalHandler is needed to write PCDATA

LexicalHandler is required to code PCDATA.

LexicalHandler is needed to write comments

LexicalHandler is required to code comments.

not a keyref

This is not a keyref.

unresolved reference

This is an unresolved reference.

Unexpected aa....aa appears at line bb....bb column cc....cc

An unexpected value aa....aa appears at line bb....bb column cc....cc.

Attempt to modify attribute at illegal index: aa....aa

An attempt is made to modify the attribute aa....aa of an invalid index.

unable to process aa....aa

aa....aa cannot be processed.

Unexpected aa....aa appears at line bb....bb column cc....cc

An unexpected value aa....aa appears at line bb....bb column cc....cc.

Unbound prefix: aa....aa

The prefix aa....aa is not bound.

Missing return statement in function

The return statement is missing in the function.

ERROR: Cannot use a static CharStream class with a non-static lexical analyzer.

You cannot use a static CharStream class with a non-static lexical analyzer.

Error: Ignoring invalid lexical state : aa....aa. State unchanged.

The invalid lexical state aa....aa will be ignored. The state will not change.

Unknown node

This is an unknown node.

Unable to resolve relative URI aa....aa without a base URI

The relative URI aa....aa cannot be resolved without a base URI.

Unable to resolve relative URI aa....aa because base URI is not absolute: bb....bb

The relative URI aa....aa cannot be resolved as the base URI bb....bb is not an absolute URI.

This product does not work in JDK1.2.

This product does not operate in JDK1.2.

--------------- linked to ------------------

--------------- linked to ------------------

can't declare any more prefixes in this context

No more prefixes can be declared in this context.

anonymous type

This is an anonymous type.

multiple definition

The definition is duplicated.

undefined type name: aa....aa

This is an undefined type. aa....aa

invalid value type: aa....aa

This is an invalid value type. aa....aa

Unknown Processing Mode

This is an unknown processing mode.

no implementation of regexp was found.

No implementation of regexp was found.

undefined process mode: aa....aa

This is an undefined processing mode. aa....aa

aborted. Errors should have been reported

The processing will be interrupted. No error is reported.

parser factory must be namespace-aware

The namespace must be enabled in the parser factory.

aa....aa doesn't implement any of TypeOwner

The aa....aa does not implement any of TypeOwner.

unexpected system ID: aa....aa

This is an unexpected system ID. aa....aa

unable to load schema-for-schema for W3C XML Schema

schema-for-schema for the W3C XML Schema cannot be loaded.

Illegal Namespace prefix: aa....aa

This is an invalid Namespace prefix. aa....aa

Undeclared prefix: aa....aa

This is an undefined prefix. aa....aa

namespace URI is null

The namespace URI is null.

local name is null

The local name is null.

unable to parse the schema

The schema cannot be parsed.

the document is invalid

The document is not valid.

unrecognized value type: aa....aa

This is an unrecognized value type. aa....aa

unknown location

The location is not known.

line aa....aa of bb....bb

This is line aa....aa of bb....bb.

unknown file

This is an unknown file.

aa....aa is not supported.

aa....aa is not supported.

cowardly refuses to write to a non-existent directory "aa....aa"

Writing to a non-existent directory "aa....aa" was denied.

an operand is missing

There is no operand.

"aa....aa" is not a valid target version. "2.0", "2.1" and "2.2" are supported.

"aa....aa" is not a valid version. "2.0", "2.1" and "2.2" are supported.

No such file: aa....aa

The specified file aa....aa is not found.

"aa....aa" is not a valid proxy format. The format is [user[:password]@]proxyHost:proxyPort

"aa....aa" is not a valid proxy format. The format is [user[:password]@]proxyHost:proxyPort.

unrecognized mode aa....aa

The mode aa....aa cannot be recognized.

unrecognized parameter aa....aa

The parameter aa....aa cannot be recognized.

grammar is not specified

Grammar is not specified.

Stack overflow. you are compiling a large schema that requires more resources.

A stack overflow occurred. This could be because of an attempt to compile a large schema for which resources are insufficient.

Too many schema files for this schema language. Compile one file at a time.

There are too many schema files for this schema language. Compile one file at a time.

Default Java package specified. You will not be able to access the generated code from classes in any other package.

The default Java package is specified. The generated code cannot be accessed from classes of another package.

"aa....aa" is not a valid file name: bb....bb

"aa....aa" is not a valid file name. bb....bb

Failed to parse "aa....aa": bb....bb

An attempt to parse "aa....aa" has failed. bb....bb

"aa....aa" is neither a file name nor a URL

"aa....aa" is neither a file name nor a URL.

"-aa....aa" and "-bb....bb" are mutually exclusive since both affect the code generation

"-aa....aa" and "-bb....bb" cannot be specified concurrently as both affect code generation.

Failed to load "aa....aa": bb....bb

An attempt to load aa....aa has failed.bb....bb

Failure to load a plugin: "aa....aa".

An attempt to load the plugin "aa....aa" has failed.

A command could not be executed. (details = aa....aa)

The command could not be executed due to aa....aa.

JDK 1.5.0_01 or later is necessary

JDK 1.5.0_01 or a later version is required.

The error message corresponding to the message key can not be found.

An error message corresponding to the message key cannot be found.

An internal error occurred while formatting the following message:

An internal error occurred while formatting the following message:

Premature end of file.

Reached the end of the file during analysis.

The root element is required in a well-formed document.

The root element is required for a well-formed document.

An invalid XML character (Unicode: 0xaa....aa) was found in the CDATA section.

An invalid XML character (Unicode:0xaa....aa) exists in the CDATA section.

An invalid XML character (Unicode: 0xaa....aa) was found in the element content of the document.

An invalid XML character (Unicode:0xaa....aa) exists in the element content of the document.

An invalid second ':' was found in the element type or attribute name.

An invalid second entry of a colon (:) was found in the element type or the attribute name.

An invalid XML character (Unicode: 0xaa....aa) was found in markup after the end of the element content.

An invalid XML character (Unicode: 0xaa....aa) was found in the markup after the end of the element content.

An invalid XML character (Unicode: 0xaa....aa) was found in the prolog of the document.

An invalid XML character (Unicode: 0xaa....aa) was found in the prolog of the document.

An invalid XML character (Unicode: 0xaa....aa) was found in the XML declaration.

An invalid XML character (Unicode: 0xaa....aa) exists in the XML declaration.

The character sequence "]]>" must not appear in content unless used to mark the end of a CDATA section.

The character sequence ]]> must not be used for a purpose other than to indicate the end of the CDATA section.

The CDATA section must end with "]]>".

The CDATA section must end with ]]>.

The XML declaration may only appear at the very beginning of the document.

The XML declaration can appear only at the beginning of a document.

The '' = '' character must follow "aa....aa" in the XML declaration.

An equals sign (=) must follow aa....aa in the XML declaration.

The value following "aa....aa" in the XML declaration must be a quoted string.

In the XML declaration, the value of aa....aa must be enclosed within quotation marks.

The XML declaration must end with "?>".

An XML declaration must end with ?>.

The version is required in the XML declaration.

The version is required for the XML declaration.

White space is required before the version pseudo attribute in the XML declaration.

A space is required before the version pseudo attribute of the XML declaration.

White space is required before the encoding pseudo attribute in the XML declaration.

A space is required before the encoding pseudo attribute of the XML declaration.

The markup in the document preceding the root element must be well-formed.

The markup in the document, preceding the root element, must be well-formed.

The markup in the document following the root element must be well-formed.

The markup in the document, following the root element, must be well-formed.

Already seen doctype.

Doctype is already declared.

Content is not allowed in prolog.

Content cannot be specified in prolog. Alternatively, a null string might be specified in an argument of the parse method.

Reference is not allowed in prolog.

Reference cannot be specified in prolog.

Content is not allowed in trailing section.

Content cannot be specified in the trailing section.

Reference is not allowed in trailing section.

Reference cannot be specified in the trailing section.

The standalone document declaration value must be "yes" or "no", not "aa....aa".

The value of the standalone document declaration must be either yes or no. The value cannot be aa....aa.

The xml:lang attribute value "aa....aa" is an invalid language identifier.

The xml:lang attribute value aa....aa is an invalid language identifier.

The element type "aa....aa" must be terminated by the matching end-tag "</aa....aa>".

The element type aa....aa must end with the end tag </aa....aa>.

Element type "aa....aa" must be followed by either attribute specifications, ">" or "/>".

The element type aa....aa must be followed by either > or />.

Attribute name "aa....aa" must be followed by the '' = '' character.

An equals sign (=) must be added after the attribute name "aa....aa".

Open quote is expected for attribute "aa....aa".

The attribute "aa....aa" must have open quotation marks.

Close quote is expected for attribute "aa....aa".

The attribute "aa....aa" must have close quotation marks.

Attribute "bb....bb" was already specified for element "aa....aa".

The attribute bb....bb is already specified for the element aa....aa.

Attribute "bb....bb" bound to namespace "cc....cc" was already specified for element "aa....aa".

The attribute bb....bb bound to the namespace cc....cc was already specified for the element aa....aa.

The end-tag for element type "aa....aa" must end with a ''>'' delimiter.

The end tag of the element type aa....aa must be >.

The content of elements must consist of well-formed character data or markup.

The contents of elements must either consist of the well-formed characters or the markup.

doctype not allowed in content.

DOCTYPE cannot be specified in element contents.

The reference must be terminated by a ';' delimiter.

Reference must be demarcated with a semicolon (;).

The reference must be entirely contained within the same parsed entity.

Reference must be configured with the same parsed entity.

The element "aa....aa" must start and end within the same entity.

The element aa....aa must start and end within the same entity.

XML document structures must start and end within the same entity.

The XML document must start and end within the same entity.

An invalid XML character (Unicode: 0xcc....cc) was found in the value of attribute "bb....bb".

An invalid XML character (Unicode: 0xcc....cc) was found in the value of the attribute "bb....bb".

An invalid XML character (Unicode: 0xaa....aa) was found in the comment.

An invalid XML character (Unicode: 0xaa....aa) exists in the comment.

An invalid XML character (Unicode: 0xaa....aa) was found in the processing instruction.

An invalid XML character (Unicode: 0xaa....aa) exists in the processing instruction.

An invalid XML character (Unicode: 0xaa....aa) was found in the internal subset of the DTD.

An invalid XML character (Unicode: 0xaa....aa) exists in the internal subset of DTD.

An invalid XML character (Unicode: 0xaa....aa) was found in the text declaration.

An invalid XML character (Unicode: 0xaa....aa) exists in the text declaration.

The value of attribute "bb....bb" must begin with either a single or double quote character.

The attribute specification bb....bb must begin with either single or double quotation marks.

The value of attribute "bb....bb" must not contain the ''<'' character.

A less-than sign (<) cannot be used in the value of the attribute "bb....bb".

The value for attribute "bb....bb" must end with the matching quote character.

The attribute specification bb....bb must end with the corresponding quotation marks.

Comment must start with "<!--".

A comment must start with <!--.

The string "--" is not permitted within comments.

-- cannot be used within a comment.

The comment must end with "-->".

A comment must end with -->.

The comment is not enclosed xin the same entity.

The comment is not enclosed within the same entity.

The processing instruction must begin with the name of the target.

The processing instruction must begin with the name of the target.

White space is required between the processing instruction target and data.

A space is required between the processing instruction target and the data.

The processing instruction must end with "?>".

The processing instruction must end with ?>.

The processing instruction target matching "[xX][mM][lL]" is not allowed.

[xX][mM][lL] cannot be specified for the processing instruction target.

The processing instruction is not enclosed in the same entity.

The processing instruction is not enclosed within the same entity.

Invalid version "aa....aa".

An invalid version is specified in aa....aa.

XML version "aa....aa" is not supported, only XML 1.0 is supported.

The XML version aa....aa is not supported. Only XML 1.0 is supported.

A decimal representation must immediately follow the "&#" in a character reference.

In a character reference, a decimal code must immediately follow &#.

A hexadecimal representation must immediately follow the "&#x" in a character reference.

In a character reference, a hexadecimal code must immediately follow &#x.

The character reference must end with the ';' delimiter.

A character reference must end with a semicolon (;).

Character reference "&#aa....aa" is an invalid XML character.

The character reference &#aa....aa; is an invalid XML character specification.

The entity name must immediately follow the '&' in the entity reference.

The entity name must be immediately after & in the entity reference.

The reference to entity "aa....aa" must end with the '';'' delimiter.

The reference to the entity aa....aa must end with a semicolon (;).

The text declaration may only appear at the very beginning of the external parsed entity.

The text declaration can only be specified immediately after the beginning of the external parsed entity.

The '' = '' character must follow "aa....aa" in the text declaration.

The text declaration can only be specified immediately after the beginning of the external parsed entity.

The value following "aa....aa" in the text declaration must be a quoted string.

In the text declaration, the value of aa....aa must be enclosed within quotation marks.

closing quote in the value following "aa....aa" in the text declaration is missing.

The close quotation marks for aa....aa do not exist in the text declaration.

White space is required before the version pseudo attribute in the text declaration.

A space is required before the version pseudo attribute in the text declaration.

White space is required before the encoding pseudo attribute in the text declaration.

A space is required before the version pseudo attribute in the text declaration.

The text declaration must end with "?>".

The text declaration must end with ?>.

The encoding declaration is required in the text declaration.

Encoding declaration must be performed within the text declaration.

no more pseudo attributes is allowed.

No more pseudo attributes can be specified.

more pseudo attributes is expected.

The number of pseudo attributes is insufficient.

a pseudo attribute name is expected.

A pseudo attribute name is not specified.

The comment must be entirely contained within the same parsed entity.

A comment must be enclosed within the same parsed entity.

The processing instruction must be entirely contained within the same parsed entity.

A processing instruction must be enclosed within the same parsed entity.

Invalid encoding name "aa....aa".

aa....aa is an invalid encoding name.

Given byte order for encoding "aa....aa" is not supported.

The byte order assigned to encoding aa....aa is not supported.

Invalid byte aa....aa of bb....bb-byte UTF-8 sequence.

Byte aa....aa of the bb....bb-byte UTF-8 sequence is invalid.

Expected byte aa....aa of bb....bb-byte UTF-8 sequence.

Byte aa....aa of the bb....bb-byte UTF-8 sequence is required.

High surrogate bits in UTF-8 sequence must not exceed 0x10 but found 0xaa....aa.

Although the upper limit for the higher surrogate bits of UTF-8 is 0x10, but 0xaa....aa was found.

Operation "aa....aa" not supported by bb....bb reader.

The operation "aa....aa" is not supported by the reader bb....bb.

Byte "aa....aa" not 7-bit ASCII.

Byte "aa....aa" is not 7-bit ASCII.

An invalid XML character (Unicode: 0xaa....aa) was found in the literal entity value.

An invalid XML character (Unicode: 0xaa....aa) exists in the literal entity value.

An invalid XML character (Unicode: 0xaa....aa) was found in the external subset of the DTD.

An invalid XML character (Unicode: 0xaa....aa) exists in the external subset of the DTD.

An invalid XML character (Unicode: 0xaa....aa) was found in the excluded conditional section.

An invalid XML character (Unicode: 0xaa....aa) exists in the excluded conditional section.

An invalid XML character (Unicode: 0xaa....aa) was found in the public identifier.

An invalid XML character (Unicode: 0xaa....aa) exists in the public identifier.

An invalid XML character (Unicode: 0xaa....aa) was found in the system identifier.

An invalid XML character (Unicode: 0xaa....aa) exists in the system identifier.

White space is required after keyword SYSTEM in DOCTYPE decl.

A space is required after the keyword SYSTEM in the DOCTYPE declaration.

The system identifier must begin with either a single or double quote character.

The system identifier must begin with either single or double quotation marks.

The system identifier must end with the matching quote character.

The system identifier must end with either single or double quotation marks.

White spaces are required after keyword PUBLIC in DOCTYPE decl.

A space is required after the keyword PUBLIC in the DOCTYPE declaration.

The public identifier must begin with either a single or double quote character.

The public identifier must begin with either single or double quotation marks.

The public identifier must end with the matching quote character.

The public identifier must end with the corresponding quotation marks.

The character (Unicode: 0xaa....aa) is not permitted in the public identifier.

The character (Unicode: 0xaa....aa) is not allowed in the public identifier.

White spaces are required between publicId and systemId.

A space is required between the public identifier and the system identifier.

White space is required after "<!DOCTYPE" in the document type declaration.

A space is required after <!DOCTYPE in the DOCTYPE declaration.

The root element type must appear after "<!DOCTYPE" in the document type declaration.

A root element type must appear after <!DOCTYPE in the DOCTYPE declaration.

The document type declaration for root element type "aa....aa" must end with ''>''.

The DOCTYPE declaration of the root element type aa....aa must end with a greater-than sign (>).

The parameter entity reference "%aa....aa;" cannot occur within markup in the internal subset of the DTD.

The parameter entity reference aa....aa cannot be coded inside the markup within the internal subset of the DTD.

The markup declarations contained or pointed to by the document type declaration must be well-formed.

The markup declaration must either include or point to a well-formed document type declaration.

The attribute declaration for "xml:space" must be given as an enumerated type whose only possible values are "default" and "preserve".

The xml:space attribute declaration must be an enumeration type for which only default or preserve can be specified.

White space is required after "<!ELEMENT" in the element type declaration.

A space is required after <!ELEMENT in the element type declaration.

The element type is required in the element type declaration.

The element type declaration is required for specifying an element type.

White space is required after the element type "aa....aa" in the element type declaration.

A space is required after the element type aa....aa in the element type declaration.

The constraint is required after the element type "aa....aa" in the element type declaration.

A constraint is required after the element type aa....aa in the element type declaration.

The declaration for element type "aa....aa" must end with ''>''.

The element type declaration must end with a greater-than sign (>).

A ''('' character or an element type is required in the declaration of element type "aa....aa".

Either a left parenthesis '(' or an element type is required in the declaration of the element type aa....aa.

A '')'' is required in the declaration of element type "aa....aa".

A right parenthesis ')' is required in the declaration of the element type aa....aa.

An element type is required in the declaration of element type "aa....aa".

An element type is required in the declaration of the element type aa....aa.

A '')'' is required in the declaration of element type "aa....aa".

A right parenthesis ')' is required in the declaration of the element type aa....aa.

The mixed content model "aa....aa" must end with ")*" when the types of child elements are constrained.

The mixed content model aa....aa must end with )* when the types of child elements are required.

White space is required after "<!ATTLIST" in the attribute-list declaration.

A space is required after <!ATTLIST in the attribute list declaration.

The element type is required in the attribute-list declaration.

The element type declaration is required for an element type.

White space is required before the attribute name in the attribute-list declaration for element "aa....aa".

A space is required before the attribute name in the attribute-list declaration for the element aa....aa.

The attribute name must be specified in the attribute-list declaration for element "aa....aa".

The attribute name must be specified in the attribute list declaration for the element aa....aa.

White space is required before the attribute type in the declaration of attribute "bb....bb" for element "aa....aa".

A space is required before the attribute type in the declaration of the attribute bb....bb for the element aa....aa.

The attribute type is required in the declaration of attribute "bb....bb" for element "aa....aa".

An attribute type is required in the declaration of the attribute bb....bb for the element aa....aa.

White space is required before the attribute default in the declaration of attribute "bb....bb" for element "aa....aa".

A space is required before the default attribute in the declaration of the attribute bb....bb of the element aa....aa.

More than one attribute definition is provided for the same attribute "bb....bb" of a given element "aa....aa".

More than one attribute definition is provided in the declaration of the same attribute bb....bb for the specified element aa....aa.

White space must appear after "NOTATION" in the "bb....bb" attribute declaration.

A space is required after NOTATION in the attribute declaration bb....bb.

The ''('' character must follow "NOTATION" in the "bb....bb" attribute declaration.

A left parenthesis '(' is required after NOTATION in the attribute declaration bb....bb.

The notation name is required in the notation type list for the "bb....bb" attribute declaration.

The notation name is required in the notation type specification for the attribute declaration bb....bb.

The notation type list must end with '')'' in the "bb....bb" attribute declaration.

The notation name must end with a right parenthesis ')' in the notation type specification for the attribute declaration bb....bb.

The name token is required in the enumerated type list for the "bb....bb" attribute declaration.

The name token is required in the enumerated type list for the attribute declaration bb....bb.

The enumerated type list must end with '')'' in the "bb....bb" attribute declaration.

The enumerated type list for the attribute declaration bb....bb must end with a right parenthesis ()).

White space must appear after "FIXED" in the "bb....bb" attribute declaration.

A space is required after FIXED in the attribute declaration bb....bb.

The included conditional section must end with "]]>".

The included conditional section must end with ]]>.

The excluded conditional section must end with "]]>".

The excluded conditional section must end with ]]>.

The entity name must immediately follow the '%' in the parameter entity reference.

The entity name of the parameter entity reference must be coded after the percent sign (%).

The parameter entity reference "%aa....aa;" must end with the '';'' delimiter.

The parameter entity reference aa....aa must end with a semicolon (;).

White space is required after "<!ENTITY" in the entity declaration.

A space is required after <!ENTITY in the entity declaration.

White space is required between "<!ENTITY" and the '%' character in the parameter entity declaration.

A space is required between <!ENTITY and the percent sign (%) in the parameter entity declaration.

White space is required between the '%' and the entity name in the parameter entity declaration.

A space is required between the percent sign (%) and the entity name in the parameter entity declaration.

The name of the entity is required in the entity declaration.

The name of the entity is required in the entity declaration.

White space is required between the entity name "aa....aa" and the definition in the entity declaration.

A space is required between the entity name aa....aa and the definition in the entity declaration.

White space is required between "NDATA" and the notation name in the declaration for the entity "aa....aa".

A space is required between NDATA and the notation name in the declaration for the entity aa....aa.

White space is required before "NDATA" in the declaration for the entity "aa....aa".

A space is required before NDATA in the declaration for the entity aa....aa.

The notation name is required after "NDATA" in the declaration for the entity "aa....aa".

The notation name is required after NDATA in the declaration for the entity aa....aa.

The declaration for the entity "aa....aa" must end with ''>''.

The declaration for the entity aa....aa must end with a greater-than sign (>).

Entity "aa....aa" is declared more than once.

The entity aa....aa is declared two or more times.

The external entity declaration must begin with either "SYSTEM" or "PUBLIC".

The external entity declaration must begin with either SYSTEM or PUBLIC.

White space is required between "PUBLIC" and the public identifier.

A space is required between PUBLIC and the public identifier.

White space is required between the public identifier and the system identifier.

A space is required between the public identifier and the system identifier.

White space is required between "SYSTEM" and the system identifier.

A space is required between SYSTEM and the system identifier.

The fragment identifier should not be specified as part of the system identifier "aa....aa".

The fragment identifier must not be specified as a part of the system identifier aa....aa.

White space is required after "<!NOTATION" in the notation declaration.

A space is required after <!NOTATION in the notation declaration.

The name of the notation is required in the notation declaration.

The notation name is required in the notation declaration.

White space is required after the notation name "aa....aa" in the notation declaration.

A space is required after the notation name aa....aa in the notation declaration.

The declaration for the notation "aa....aa" must include a system or public identifier.

The declaration for the notation aa....aa must include a system or a public identifier.

The declaration for the notation "aa....aa" must end with ''>''.

The declaration for the notation aa....aa must end with a greater-than sign (>).

The element type "bb....bb" was already specified in the content model of the element decl "aa....aa".

The element type bb....bb is already declared in the content model of the element declaration aa....aa.

Attribute value "bb....bb" of type ENTITIES must be the names of one or more unparsed entities.

The attribute value bb....bb of the type ENTITIES must be the names of one or more unparsed entities.

Attribute value "bb....bb" of type ENTITY must be the name of an unparsed entity.

The attribute value bb....bb of the type ENTITIES must be the name of an unparsed entity.

The ID attribute "aa....aa" must have a declared default of "#IMPLIED" or "#REQUIRED".

The ID attribute aa....aa must be the declared default value of #IMPLIED or #REQUIRED.

Attribute value "aa....aa" of type ID must be a name.

The attribute value aa....aa of the type ID must be a name.

Attribute value "aa....aa" of type ID must be unique within the document.

The attribute value aa....aa of the type ID must be unique within a document.

Attribute value "aa....aa" of type IDREF must be a name.

The attribute value aa....aa of the type IDREF must be a name.

Attribute value "aa....aa" of type IDREFS must be one or more names.

The attribute value aa....aa of the type IDREF must be one or more names.

The replacement text of parameter entity "aa....aa" must include properly nested declarations when the entity reference is used as a complete declaration.

When the entity reference is used as a complete declaration, the replacement text of the parameter entity aa....aa must include the properly nested declarations.

The replacement text of parameter entity "aa....aa" must include properly nested declarations.

The replacement text of the parameter entity aa....aa must include the properly nested declarations.

The replacement text of parameter entity "aa....aa" must include properly nested pairs of parentheses.

The replacement text of the parameter entity aa....aa must include the properly nested pairs of parentheses.

The replacement text of parameter entity "aa....aa" must include the entire conditional section or just INCLUDE or IGNORE.

The replacement text of the parameter entity aa....aa must include either the entire conditional section or only INCLUDE or IGNORE.

Attribute "bb....bb" must be declared for element type "aa....aa".

The attribute bb....bb must be the declaration for the element type aa....aa.

Attribute "aa....aa" with value "bb....bb" must have a value from the list "cc....cc".

The attribute aa....aa with the value bb....bb must have a value from the list cc....cc.

The value "bb....bb" of attribute "aa....aa" must not be changed by normalization (to "cc....cc") in a standalone document.

The value bb....bb of the attribute aa....aa must not be changed (to cc....cc) by normalization in a standalone document.

The content of element type "aa....aa" is incomplete, it must match "bb....bb".

The contents of the element type aa....aa are incomplete. They must match bb....bb.

The content of element type "aa....aa" must match "bb....bb".

The contents of the element type aa....aa must match bb....bb.

Attribute "bb....bb" for element type "aa....aa" has a default value and must be specified in a standalone document.

The attribute bb....bb of the element type aa....aa must have a default value and must be specified in a standalone document.

Attribute "bb....bb" is already declared for element type "aa....aa".

The attribute bb....bb is already declared for the element type aa....aa.

Element type "aa....aa" must not be declared more than once.

The element type aa....aa must not be declared two or more times.

Element type "aa....aa" must be declared.

The element type aa....aa must be declared.

Document is invalid: no grammar found.

The document is invalid. Syntax not found.

An element with the identifier "aa....aa" must appear in the document.

An element with the identifier aa....aa must exist in the document.

The reference to external entity "aa....aa" is not permitted in a standalone document.

The reference to the external entity aa....aa is not allowed in a standalone document.

Attribute "bb....bb" with value "cc....cc" must have a value of "dd....dd".

The attribute bb....bb with value cc....cc must have a value of dd....dd.

Element type "aa....aa" already has attribute "bb....bb" of type ID, a second attribute "cc....cc" of type ID is not permitted.

The element type aa....aa already has the attribute bb....bb of the type ID. A second attribute cc....cc of the type ID is not allowed.

Element type "aa....aa" already has attribute "bb....bb" of type NOTATION, a second attribute "cc....cc" of type NOTATION is not permitted.

The element type aa....aa already has the attribute bb....bb of the type NOTATION. A second attribute cc....cc of the type NOTATION is not allowed.

The notation "bb....bb" must be declared when referenced in the notation type list for attribute "aa....aa".

The notation bb....bb must be declared when referenced in the notation type list for the attribute aa....aa.

The notation "bb....bb" must be declared when referenced in the unparsed entity declaration for "aa....aa".

The notation bb....bb must be declared when referenced in the unparsed entity for the attribute aa....aa.

The reference to entity "aa....aa" declared in an external parsed entity is not permitted in a standalone document.

The reference to the entity aa....aa declared in an external parsed entity is not allowed in a standalone document.

Attribute "bb....bb" is required and must be specified for element type "aa....aa".

The attribute bb....bb is required for specifying the element type aa....aa.

White space must not occur between elements declared in an external parsed entity with element content in a standalone document.

There must be no space in the element declaration of an external parsed entity with element contents in a standalone document.

Attribute value "aa....aa" of type NMTOKEN must be a name token.

The attribute value aa....aa of the type NMTOKEN must be a name token.

Attribute value "aa....aa" of type NMTOKENS must be one or more name tokens.

The attribute value aa....aa of the type NMTOKENS must be one or more name tokens.

Document root element "bb....bb", must match DOCTYPE root "aa....aa".

The document root element bb....bb must match the DOCTYPE root aa....aa.

The content model of element "aa....aa" refers to the undeclared element "bb....bb".

The content model of the element aa....aa references the undeclared element bb....bb.

ENTITYDatatype Validator: Failed Need to call initialize method with a valid Grammar reference.

Validity of ENTITYDatatype: An attempt to call the initialization method with valid syntax has failed.

ENTITY "aa....aa" is not unparsed.

The entity aa....aa is not unparsed.

ENTITY "aa....aa" is not valid.

The entity aa....aa is invalid.

Value of type ENTITIES, IDREFS, and NMTOKENS cannot be empty list.

An empty list cannot be specified for the value of the type ENTITIES, IDREFS, and NMTOKENS.

The external entity reference "&aa....aa;" is not permitted in an attribute value.

The external entity reference &aa....aa; is not allowed as an attribute.

The entity "aa....aa" was referenced, but not declared.

The entity aa....aa was referenced, but is not declared.

The unparsed entity reference "&aa....aa;" is not permitted.

The unparsed entity reference &aa....aa; is not allowed.

Recursive entity reference "aa....aa". (Reference path: bb....bb),

This is a recursive entity reference aa....aa. (Refer path bb....bb).

Recursive general entity reference "&aa....aa;". (Reference path: bb....bb),

This is a recursive general entity reference &aa....aa;. (Refer path bb....bb).

Recursive parameter entity reference "%aa....aa;". (Reference path: bb....bb),

This is a recursive parameter entity reference %aa....aa;. (Refer path bb....bb).

The encoding "aa....aa" is not supported.

The encoding aa....aa is not supported.

A parsed entity not encoded in either UTF-8 or UTF-16 must contain an encoding declaration.

A parsed entity that is not encoded in either UTF-8 or UTF-16 must contain an encoding declaration.

Element "aa....aa" cannot have "xmlns" as its prefix.

xmlns cannot be added as a prefix to the element "aa....aa".

The prefix "aa....aa" for element "bb....bb" is not bound.

The prefix aa....aa of the element bb....bb is not bound.

The prefix "aa....aa" for attribute "bb....bb" is not bound.

The prefix aa....aa of the attribute bb....bb is not bound.

The value of the attribute "aa....aa" is invalid. Prefixed namespace bindings may not be empty.

The value of the attribute aa....aa is invalid. A prefixed namespace binding might not be empty.

The namespace prefix "aa....aa" was not declared.

The namespace prefix aa....aa was not declared.

The prefix "xmlns" cannot be bound to any namespace explicitly; neither can the namespace for "xmlns" be bound to any prefix explicitly.

The prefix xmlns cannot be bound explicitly to a namespace. Also, the namespace for xmlns cannot be bound explicitly to any prefix.

The prefix "xml" cannot be bound to any namespace other than its usual namespace; neither can the namespace for "xml" be bound to any prefix other than "xml".

The prefix xml cannot be bound to a namespace other than its usual namespace. Also, the namespace for xml cannot be bound to any prefix other than xml.

The defaultValue "bb....bb" of attribute "aa....aa" is not legal as for the lexical constraints of this attribute type.

The default value bb....bb of the attribute aa....aa consists of words that cannot be used in this attribute type.

OpenQuoteMissingInDecl

The declaration does not have open quotation marks.

InvalidCharInLiteral

Invalid characters exist in literal.

Doctype declaration is not allowed.

The Doctype declaration cannot be used.

http://www.w3.org/TR/1998/REC-xml-19980210#"aa....aa"?"bb....bb"&"cc....cc"...

A syntax that does not conform to the W3C XML1.0 standard was detected.

http://www.w3.org/TR/1999/REC-xml-names-19990114#"aa....aa"?"bb....bb"&"cc....cc"...

A syntax that does not conform to W3C Namespaces in XML standard was detected.

true value of isValidating not supported

The true value of isValidating is not supported.

false value of aa....aa feature is not supported

The false value of the aa....aa feature is not supported.

Encoding byte order not supported

Encoding based on the byte order is not supported.

Encoding declaration aa....aa not valid

The encoding declaration aa....aa is invalid.

Encoding aa....aa not supported

The encoding aa....aa is not supported.

Scanner State aa....aa not Recognized

The Scanner State aa....aa cannot be recognized.

DTDDriver#dispatch: scanner state=aa....aa (bb....bb)

DTDDriver#dispatch: scanner state=aa....aa (bb....bb)

No more events to be parsed

There are no more events to be parsed.

Scanner State aa....aa not Recognized

The Scanner State aa....aa cannot be recognized.

parser must be on START_ELEMENT to read next text

The parser must be set on START_ELEMENT to read the following text:

getElementText() function expects text only element but START_ELEMENT was encountered.

The getElementText() function can process text-only elements, however, START_ELEMENT was detected.

unexpected end of document when reading element text content

Reached the end of the document while reading the contents of element text.

getElementText() function expects text only element but START_ELEMENT was encountered.

The getElementText() function can process text-only elements, however, START_ELEMENT was detected.

Unexpected event type aa....aa

The event type aa....aa cannot be processed.

expected start or end tag

The start or end tag is required.

Method getLocalName() cannot be called for aa....aa event.

The getLocalName() method cannot be called for the aa....aa event.

Current state of the parser is aa....aa But expected state is bb....bb

The current state of the parser is aa....aa, but it must be set to bb....bb.

Current state = aa....aa is not among the states bb....bb , cc....cc , dd....dd , ee....ee valid for getTextCharacters()

The valid states for getTextCharacters() are bb....bb, cc....cc, dd....dd, and ee....ee, however, the current state aa....aa is not from these states.

Current state = aa....aa is not among the states bb....bb , cc....cc , dd....dd , ee....ee valid for getTextLength()

The valid states for getTextLength() are bb....bb, cc....cc, dd....dd, and ee....ee, however, the current state aa....aa is not from these states.

Current state = aa....aa is not among the states bb....bb , cc....cc , dd....dd , ee....ee valid for getTextStart()

The valid states for getTextStart() are bb....bb, cc....cc, dd....dd, and ee....ee, however, the current state aa....aa is not from these states.

END_DOCUMENT reached: no more elements on the stream.

Reached the END_DOCUMENT. The stream does not contain any more elements.

Current state is not among the states aa....aa , bb....bb valid for getAttributeCount()

The valid states for getAttributeCount() are aa....aa and bb....bb, however, the current state is not from these states.

Current state is not among the states aa....aa , bb....bb valid for getAttributeName()

The valid states for getAttributeName() are aa....aa and bb....bb, however, the current state is not from these states.

Current state is not among the states aa....aa , bb....bb valid for getAttributeLocalName()

The valid states for getAttributeLocalName() are aa....aa and bb....bb, however, the current state is not from these states.

Current state is not among the states aa....aa , bb....bb valid for getAttributeNamespace()

The valid states for getAttributeNamespace() are aa....aa and bb....bb, however, the current state is not from these states.

Current state is not among the states aa....aa , bb....bb valid for getAttributePrefix()

The valid states for getAttributePrefix() are aa....aa and bb....bb, however, the current state is not from these states.

Current state is not among the states aa....aa , bb....bb valid for getAttributeQName()

The valid states for getAttributeQName() are aa....aa and bb....bb, however, the current state is not from these states.

Current state is not among the states aa....aa , bb....bb valid for getAttributeType()

The valid states for getAttributeType() are aa....aa and bb....bb, however, the current state is not from these states.

Current state is not among the states aa....aa , bb....bb valid for getAttributeValue()

The valid states for getAttributeValue() are aa....aa and bb....bb, however, the current state is not from these states.

parser must be on START_ELEMENT to read next text

The parser must be set to START_ELEMENT to read the following text:

unexpected end of document when reading element text content

Reached the end of the document while reading the contents of the element text.

getElementText() function expects text only element but START_ELEMENT was encountered.

The getElementText() function can process text-only elements, however, START_ELEMENT was detected.

Unexpected event type aa....aa

The event type aa....aa cannot be processed.

Illegal to call getName() when event type is aa....aa . Valid states are bb....bb, cc....cc

The process of calling getName() when the event type is aa....aa is invalid. The valid states are bb....bb and cc....cc.

Current state aa....aa is not among the states bb....bb, cc....cc, dd....dd valid for getNamespaceCount().

The valid states for getNamespaceCount() are bb....bb, cc....cc, and dd....dd. However, the current state aa....aa is not from these states.

Current state aa....aa is not among the states bb....bb, cc....cc, dd....dd valid for getNamespacePrefix().

The valid states for getNamespacePrefix() are bb....bb, cc....cc, and dd....dd. However, the current state aa....aa is not from these states.

Current state aa....aa is not among the states bb....bb, cc....cc, dd....dd valid for getNamespaceURI().

The valid states for getNamespaceURI() are bb....bb, cc....cc, and dd....dd. However, the current state aa....aa is not from these states.

Current state aa....aa is not among the states bb....bb, cc....cc, dd....dd, ee....ee, ff....ff, gg....gg valid for getText()

The valid states for getText() are bb....bb, cc....cc, dd....dd, ee....ee, ff....ff, and gg....gg. However, the current state aa....aa is not from these states.

Event type aa....aa specified did not match with current parser event bb....bb

The specified event type aa....aa does not match the current parser event bb....bb.

Namespace URI aa....aa specified did not match with current namespace URI

The specified namespace URI aa....aa does not match the current namespace URI.

LocalName aa....aa specified did not match with current local name

The specified local name aa....aa does not match the current local name.

target char array can't be null

The target character array cannot be null.

sourceStart is greater than number of characters associated with this event

sourceStart has exceeded the number of characters associated with this event.

Current state is not among the states aa....aa , bb....bb valid for isAttributeSpecified()

The valid states for isAttributeSpecfied() are aa....aa and bb....bb. However, the current state is not from these states.

expected start or end tag

The start or end tag is required.

getNamespaceURI(String prefix) is called with a null prefix.

getNamespaceURI(String prefix) is called with a null prefix.

The stream reader has reached the end of the document, or there are no more items to return

Either the stream reader has reached the end of the document or there are no more items to return.

Property not supported

The property is not supported.

Property aa....aa is not supported

The property aa....aa is not supported.

aa....aa type is not supported

The aa....aa type is not supported.

result of type aa....aa is not supported

The result type aa....aa is not supported.

Property aa....aa is not supported: XMLStreamWriters are not Thread safe

The property aa....aa is not supported. XMLStreamWriters are not thread-safe.

FWK008 Element stack underflow

Underflow of the FWK008 element stack has occurred.

Reader cannot be null

The Reader cannot be null.

Prefix can't be null

The prefix cannot be null.

URI can't be null or empty String

The URI cannot be null or an empty character string.

Illegal access to Namespace prefixes enumeration.

This is an invalid access to the namespace prefixes enumeration.

Cannot construct URI with null/empty scheme!

The URI cannot be configured with a null or an empty scheme.

Cannot construct URI with null/empty scheme-specific part!

The URI cannot be configured with a null or an empty scheme-specific part.

Scheme is required!

A scheme is required.

Userinfo may not be specified if host is not specified!

Userinfo cannot be specified unless the host is specified.

Port may not be specified if host is not specified!

The port cannot be specified unless the host is specified.

Query string cannot be specified in path and query string!

A Query string cannot be specified in a path and Query String.

Fragment cannot be specified in both the path and fragment!

A Fragment cannot be specified in both the path and Fragment.

Cannot initialize URI with empty parameters.

The URI cannot be initialized with empty parameters.

No scheme found in URI.

The URI does not contain a scheme.

aa....aa is invalid. Port should only contain digits!

aa....aa is invalid. Use only numerals to specify the port.

Cannot initialize path from null string!

A path cannot be initialized from a null string.

Path contains invalid escape sequence!

The path contains an invalid escape sequence.

Path contains invalid character: aa....aa

The path contains an invalid character aa....aa.

Query string contains invalid escape sequence!

The Query String contains an invalid escape sequence.

Query string contains invalid character:aa....aa

The Query String contains an invalid character aa....aa.

Fragment contains invalid escape sequence!

The Fragment contains an invalid escape sequence.

Fragment contains invalid character:aa....aa

The Fragment contains an invalid character aa....aa.

Cannot set scheme from null string!

A scheme cannot be set with a null string.

The scheme is not conformant.

The scheme does not conform to the specifications.

Userinfo cannot be set when host is null!

Userinfo cannot be set when the host is null.

Userinfo contains invalid escape sequence!

Userinfo contains an invalid escape sequence.

Userinfo contains invalid character:aa....aa

Userinfo contains an invalid character aa....aa.

Host is not a well formed address!

The format of the host address is incorrect.

Port cannot be set when host is null!

The port cannot be set when the host is null.

Invalid port number!

The port number is invalid.

Path contains invalid character!

The path contains invalid characters.

Query string can only be set for a generic URI!

The Query String can only be set in a general URI.

Query string cannot be set when path is null!

The Query String cannot be set when the path is null.

Query string contains invalid character!

The Query String contains invalid characters.

Fragment can only be set for a generic URI!

The Fragment can only be set in a general URI.

Fragment cannot be set when path is null!

The Fragment cannot be set when the path is null.

Fragment contains invalid character!

Fragment contains invalid characters.

Remove operation is not supported

The Delete operation is not supported.

Attempting to write invalid Unicode code point 'aa....aa'

An attempt is made to write an invalid Unicode code point 'aa....aa'.

Attempting to close a UTF8OutputStreamWriter while awaiting for a UTF-16 code unit

An attempt is made to close UTF8OutputStreamWriter while waiting for a UTF-16 code unit.

Prefix cannot be null

The prefix cannot be null.

Current DOM Node type is aa....aa and does not allow attributes to be set

The current DOM node type is aa....aa, and attributes cannot be set.

NamespaceURI cannot be null

NamespaceURI cannot be null.

Local name cannot be null

The local name cannot be null.

Namespace URI aa....aa is not bound to any prefix

The namespace URI aa....aa is not bound to a prefix.

CDATA cannot be null

CDATA cannot be null.

Target cannot be null

The target cannot be null.

Event reader shouldn't be null

The event reader cannot be null.

close() Must be called before calling reset()

close() must be called before calling reset().

Property 'aa....aa' is not supported

The property 'aa....aa' is not supported.

URI cannot be null

The URI cannot be null.

Attribute not associated with any element

The attribute is not associated with any element.

Prefix aa....aa is already bound to bb....bb. Trying to rebind it to cc....cc is an error.

The prefix aa....aa is already bound to bb....bb. An error will occur if an attempt is made to rebind it to cc....cc.

cdata cannot be null

cdata cannot be null.

Namespace Attribute not associated with any element

The namespace attribute is not associated with an element.

xmlns has been already bound to aa....aa. Rebinding it to bb....bb is an error

xmlns is already bound to aa....aa. An error will occur if an attempt is made to rebind it to bb....bb.

NamespaceURI aa....aa has not been bound to any prefix

The namespace URI aa....aa is not bound to any prefix.

No more elements to write

There are no more elements to code.

No element was found to write

No element to be code was found.

No element was found to write: aa....aa

No element was found to code aa....aa.

Invalid state: start tag is not opened at writeNamespace(aa....aa, bb....bb)

An invalid state has occurred. The start tag is not opened at writeNamespace (aa....aa, bb....bb).

prefix aa....aa has been already bound to bb....bb. Rebinding it to cc....cc is an error

The prefix aa....aa is already bound to bb....bb. An error will occur if an attempt is made to rebind it to cc....cc.

PI target cannot be null

The PI target cannot be null.

Underlying stream encoding 'aa....aa' and input parameter for writeStartDocument() method 'bb....bb' do not match.

The encoding 'aa....aa' of the base stream and the input parameter 'bb....bb' of the writeStartDocument() method do not match.

Stream closed

The stream is closed.

parsing a schema...

Parsing a schema...

Failed to parse a schema.

Failed in parsing the schema.

compiling a schema...

Compiling a schema...

Failed to produce code.

An attempt to generate the code has failed.

Writing aa....aa

Writing to file aa....aa is in progress.

Provider aa....aa not found

The provider aa....aa is not found.

Provider aa....aa could not be instantiated: bb....bb

The provider aa....aa could not be instantiated. bb....bb

Unable to locate jaxb.properties for package aa....aa

The jaxb.properties file of the package aa....aa is not found.

You may not mix JAXB Providers on the context path

Multiple JAXB providers cannot be mixed on the same context path.

jaxb.properties in package aa....aa does not contain the bb....bb property.

The property bb....bb is not coded in the jaxb.properties file of the package aa....aa.

No package name is given

A package name is not specified.

name: aa....aa value: bb....bb

Name: aa....aa Value: bb....bb.

The DatatypeConverterInterface parameter must not be null

Null cannot be specified for the DatatypeConverterInterface parameter.

ClassCastException: attempting to cast aa....aa to bb....bb. Please make sure that you are specifying the proper ClassLoader.

ClassCastException: An attempt is made to cast aa....aa to bb....bb. Confirm that the correct class loader is specified.

InputStream can not be null

Null cannot be specified for InputStream.

aa....aa must be boolean

Specify a boolean value in aa....aa.

aa....aa must be a String

Specify a String in aa....aa.

"DefaultValidationEventHandler: aa....aa bb....bb

Location: cc....cc"

"DefaultValidationEventHandler: aa....aa bb....bb

Location: cc....cc"

unavailable

Cannot be used.

Unrecognized event severity field "aa....aa"

The event severity field "aa....aa" cannot be recognized.

Illegal severity

The severity invalid.

aa....aa parameter must not be null

Null cannot be specified for the aa....aa parameter.

Unrecognized event severity field "aa....aa"

The event severity field "aa....aa" cannot be recognized.

JAXBContext can not be null

Null cannot be specified for JAXBContext.

Unmarshaller can not be null

Null cannot be specified for Unmarshaller.

Content object can not be null

Null cannot be specified for the contents object.

Marshaller can not be null

Null cannot be specified for Marshaller.

Not a number: aa....aa

aa....aa is not a numeric value.

Input is empty

The input value is blank.

String "aa....aa" is not valid boolean value.

String aa....aa is not a valid boolean value.

input is empty

The input value is blank.

prefix aa....aa is not bound to a namespace

The prefix aa....aa is not bound to the namespace.

hexBinary needs to be even-length: aa....aa

The length aa....aa of hexBinary type must be an even length.

contains illegal character for hexBinary: aa....aa

aa....aa contains an invalid character for the hexBinary type.

no XML is given

An XML is not specified.

I don't understand how to handle aa....aa

The method of processing aa....aa is not clear.

Provider aa....aa not found

The provider aa....aa is not found.

Provider aa....aa could not be instantiated: bb....bb

The provider aa....aa could not be instantiated. bb....bb

Provider for aa....aa cannot be found

The provider for aa....aa is not found.

12 KEDT (Messages Output by Developer)

This chapter describes the messages output by Developer.

12.1 Message Description Format

The format of message descriptions in this manual is as follows:

KEDTnnnnn-Y

Message text

Description

Supplementary explanation for the message text

Action

Action performed by the user

The description of each item is as follows:

KEDTnnnnn

This indicates a message ID.

The description of elements configuring the message ID is as follows:

KEDT

This describes the prefix of the messages output by Developer.

nnnnn

This describes message numbers managed by Developer. A five-digit unique number is attached to each message.

Y

This indicates the message level. The message level is shown with one alphabetic character.

The characters showing message levels and their meaning are mentioned below:

E (Error)

This message reports that an error level problem has occurred.

The process is interrupted when this message is output.

W (Warning)

This message reports that a warning level problem has occurred.

The process continues even after the message is output.

I (Information)

This message reports a system operation.

The process continues even after the message is output.

Message text

This describes the message text output by Developer.

Description

This indicates the supplementary message explanation items such as the factors due to which the message is reported and configuration software operations that output the message.

Action

This indicates the actions performed by the user.

12.2 Messages beginning with KEDT

This section describes the messages from KEDT10001 to KEDT99999 output by Developer.

KEDT10001-I

Setup of the Instant Setup functionality has started.

Description

This message indicates that the Development Environment Instant Setup functionality has started.

KEDT10002-I

Copying file has started. (details=<absolute-path-for-the-file>)

Description

This message indicates that copying of the file has started.

KEDT10003-I

Copying file has finished. (details=<absolute-path-for-the-file>)

Description

This message indicates that copying of the file has finished.

KEDT10004-I

Editing file has started. (details=<absolute-path-for-the-file>)

Description

This message indicates that file editing has started.

KEDT10005-I

Editing file has finished. (details=<absolute-path-for-the-file>)

Description

This message indicates that the file editing has finished.

KEDT10006-I

Executing file has started. (details=<absolute-path-for-the-file>)

Description

This message indicates that execution of the file has started.

KEDT10007-I

Executing file has finished. (details=<absolute-path-for-the-file>)

Description

This message indicates that execution of the file has finished.

KEDT10010-I

Setup of the Instant Setup functionality has finished.

Description

This message indicates that the Development Environment Instant Setup functionality has finished.

KEDT10011-I

Making folder has started. (details=<absolute-path-for-the-folder>)

Description

This message indicates that the creation of a folder has started.

KEDT10012-I

Making folder has finished. (details=<absolute-path-for-the-folder>)

Description

This message indicates that the creation of the folder has finished.

KEDT10013-E

The error occurred by the copying file. (details=<absolute-path-for-the-file-or-directory>)

Description

An error occurred while copying the file or the directory.

Action

Confirm the following details:

A file or directory exists in absolute-path-for-the-file-or-directory.

The user has read permission for the file or the directory in absolute-path-for-the-file-or-directory.

The user has write permission for the copy destination directory.

Also confirm the following if you want to copy a file:

A folder with the same name does not exist in the copy destination directory.

If a file with the same name exists in the copy destination directory, the user has read and write permission.

Also confirm the following if you want to copy a directory:

A file with the same name does not exist in the copy destination directory.

If a folder with the same name exists in the copy destination directory, the user has the write permission.

KEDT10014-E

The error occurred by the editing file.(details=<absolute-path-for-the-file>)

Description

An error occurred while editing the file.

Action

Confirm the following details:

A file exists in the absolute-path-for-the-file.

The user has read and write permission for the file in absolute-path-for-the-file.

KEDT10015-E

The error occurred by the executing file.(details=<absolute-path-for-the-file>)

Description

An error occurred while executing the file.

Action

See the message displayed before and after this message, and then take action.

If the action to be performed is not clear from the above description, see the following log files:

If the call destination command name (file name) begins with cmx

A log file outputs to Developer-installation-directory\manager\log\message

If the call destination command name (file name) begins with cj

A log file outputs to Developer-installation-directory\CC\admin\logs

KEDT10016-E

The error occurred by the making folder.(details=<absolute-path-for-the-folder>)

Description

An error occurred while creating the folder.

Action

Confirm the following details:

There is no folder or file in absolute-path-for-the-folder.

The user has write permission to the parent directory of absolute-path-for-the-folder.

KEDT10017-I

Extracting archive files has started. (details=<absolute-path-for-the-file>)

Description

This message indicates that the deployment of archive files has started.

KEDT10018-I

Extracting archive files has finished. (details=<absolute-path-for-the-file>)

Description

This message indicates that the deployment of archive files has finished.

KEDT10019-E

The error occurred by the extracting archive files.(details=<absolute-path-for-the-file>)

Description

An error occurred while deploying archive files.

Action

Confirm the following details:

A file exists in absolute-path-for-the-file.

The user has read permission for the file in absolute-path-for-the-file.

The user has write permission to the directory for deploying archive files.

A file, having the path same as the directory for deploying the archive files, does not exist.

The drive on which archive files are deployed has adequate free space.

If an error occurs, even if the above conditions are satisfied, the files in absolute-path-for-the-file might be damaged. In such cases, acquire archive files again.

KEDT10029-I

Deleting folder has started. (details=<absolute-path-for-the-folder>)

Description

This message indicates that the deletion of the folder has started.

KEDT10030-I

Deleting folder has finished. (details=<absolute-path-for-the-folder>)

Description

This message indicates that the deletion of the folder has finished.

KEDT10031-E

The error occurred by the deleting folder. (details=<absolute-path-for-the-folder>)

Description

An error occurred while deleting the folder.

Action

Confirm the following details:

A folder exists in absolute-path-for-the-folder.

The user has write permission for the folder in absolute-path-for-the-folder.

KEDT10033-I

Checking folder has started. (details=<absolute-path-for-the-folder>)

Description

This message indicates that checking of the folder has started.

KEDT10034-I

Checking folder has finished. (details=<absolute-path-for-the-folder>)

Description

This message indicates that checking of the folder has finished.

KEDT10035-E

The error occurred by the checking folder. (details=<absolute-path-for-the-folder>)

Description

An error occurred while checking the folder.

Action

Confirm that the folder exists in absolute-path-for-the-folder.

KEDT11001-I

Setup of the Eclipse Setup functionality has started.

Description

This message indicates that the Eclipse Setup functionality has started.

KEDT11002-I

Setup functionality has finished.

Description

This message indicates that the Eclipse Setup functionality has finished.

KEDT20001-E

%1 has occurred. (details=%2) The stack trace is output after this message.

%1: Exception name

%2: Detailed information

Description

An exception (%1) occurred during the internal processing of the Development Environment Instant Setup functionality.

Action

Remove the cause due to which the exception occurred.

KEDT31001-W

line %1: The trace collection point cannot be recognized.

Line %1: The trace collection point cannot be recognized.

Description

(%1) line: The trace collection point cannot be recognized.

Action

Check the syntax format of the trace collection point.

KEDT31002-W

line %1: The trace collection point was not imported because the same trace collection point already exists.

Line %1: The trace collection point was not imported because the same trace collection point already exists.

Description

(%1) line: The trace collection point was not imported because the same trace collection point already exists.

Action

Clear the "Overwrite, if conforming to the specified trace collection point" check box in the "Importing the user-extended performance analysis trace configuration file" dialog box, and check that the specified trace collection point is defined.

KEDT31003-W

line %1: The trace collection point does not correspond to any Java element in the workspace.

Line %1: The trace collection point does not correspond to any Java element in the workspace.

Description

Line (%1): The trace collection point does not correspond to any Java element in the workspace.

Action

Check that Eclipse Java Element is correctly specified.

13 KEOS (Messages Output during Setup, Operation, and Maintenance Using Cosminexus Manager)

This chapter describes the messages from KEOS02000 to KEOS29999 among the messages output when Cosminexus Manager is used for system setup, operation, and maintenance.

13.1 Message Description Format

The format of message descriptions in this manual is as follows:

KEOSnnnnn-Y (Z)

Message text

Explanation of variable values

Description

Supplementary explanation for the message text

Action

Action performed by the user

Note that depending upon the message, Explanation of variable values, Description, and Action may not be described.

The description of each item is as follows:

KEOSnnnnn

This indicates message IDs.

The description of elements configuring a message ID is as follows:

KEOS

This indicates a prefix of messages output when building, operating, or maintaining a system using Cosminexus Manager.

nnnnn

This indicates a message number that is managed when building, operating, or maintaining a system using Cosminexus Manager. A five-digit specific number in the range from 02000 to 29999 is attached to the respective messages.

Y

This indicates the message level. The message level is shown with one alphabetic character.

The characters showing message levels and their meaning are mentioned below:

E (Error)

This message reports that an error level problem has occurred.

The process is interrupted when this message is output.

W (Warning)

This message reports that a warning level problem has occurred.

The process continues even after the message is output.

I (Information)

This message reports a system operation.

The process continues even after the message is output.

Q (Question)

This message reports a user response for the output message.

When this message is output, the system waits for the user response.

R (Request)

This message reports that the system is waiting for a user response to output message.

Note that if the output destination of a message beginning with KEOS is the Management Server window, the color of the message text differs depending on the message level.

The colors indicating message levels and their meanings are as follows:

Red: Indicates an error-level message.

Yellow: Indicates a warning-level message.

Black: Indicates a message that reports the system operation.

(Z)

This indicates the output destination of the message. The output destination is indicated with one alphabetic character.

The characters showing the output destination and their meaning are described below:

C: Output to the console.

F: Output to the log file.

L: Output to the event log.

S: Output to syslog (in UNIX).

W: Output to the Management Server window.

V: Output to logs of the products using the remote management function.

Important note

Message output destination is additional information used in the manual.

Message text

This indicates the message text output when Cosminexus Manager is used for setup, operations, and maintenance.

Note that the variable value (value that varies depending on the status in which the message is output) in the message text is described in one of the following formats:

Bold

xx....xx (xx are English lower-case alphabetical characters)

Explanation of variable values

The information displayed in the variable value within the message text is shown in the format of 'xx....xx: displayed information' (xx are lower case alphabetic characters). A format example of the explanation of variable values is shown below:

(Example)

aa....aa: File name

bb....bb: Application name

Description

This indicates the supplementary message explanation items such as the factors due to which the message is reported and configuration software operations that output the message.

Action

This indicates the actions performed by the user. Note that 'Contact the maintenance personnel' in the action indicates that the system administrator needs to contact our helpdesk based on the purchase agreement.

13.2 Messages from KEOS02000 to KEOS09999

This section describes the messages from KEOS02000 to KEOS09999 output when building, operating, or maintaining a system using Cosminexus Manager.

KEOS02001-E (C)

The option is specified incorrectly.

Description

The option specified for the command argument is invalid.

The processing will be interrupted.

Action

Specify the option correctly, and then re-execute the command.

KEOS02002-E (C)

The required option is not specified.

Description

Mandatory parameters are not specified in the command argument.

The processing will be interrupted.

Action

Specify the option correctly, and then re-execute the command.

KEOS02003-E (C)

Starting the Java application launcher failed. aa....aa is missing.

aa....aa: File name

Description

An attempt to start the Java application startup command has failed.

The processing will be interrupted.

The installation may have failed.

Action

Re-install the Java application.

KEOS02010-E (C)

The file cannot be accessed. File=aa....aa

aa....aa: File name

Description

The process cannot continue because the applicable file cannot be accessed.

The processing will be interrupted.

Action

Check the following details, and then re-execute the process:

Is the file open?

Is the file corrupt?

KEOS02011-E (C)

The specified file is not found. File=aa....aa

aa....aa: File name

Description

The processing will be interrupted.

Action

Enter the correct file name.

KEOS02012-E (C)

The required item is not specified in configuration file. File=aa....aa

aa....aa: File name

Description

The configuration contents coded in the applicable file are invalid.

The processing will be interrupted.

Action

Check the following details corresponding to the value specified in com.cosminexus.admin.auth.sso.ldap.w of the user management configuration file, and then re-execute the process:

LDAP server URL specification (java.naming.provider.url specification)

Base DN specification (com.cosminexus.admin.auth.ldap.basedn specification) when accessing the LDAP server

KEOS02020-E (C)

(Message text is omitted.)

For details on this message, see KEOS02020-E in the uCosminexus Application Server Security Management Guide.

KEOS02021-E (C)

Failed to access the LDAP directory server. Exception=aa....aa

aa....aa: Exception code

Description

An exception occurred in JNDI when accessing the LDAP directory server.

The processing will be interrupted.

Action

Check the following details, and then re-execute the process:

Is the LDAP directory server running?

Are the following items specified correctly in the user management configuration file?

- LDAP directory server URL

- Base DN

- Bind DN

- Password

Does the bind DN of the LDAP directory server, specified in the user management configuration file, have the access permission to refer or update the entries in the base DN?

Is there an upper level entry of the base DN of the LDAP directory server specified in the user management configuration file?

Are the extension object class and attributes for single sign-on registered correctly on the LDAP directory server?

Are invalid character strings specified as user ID in the -u option of the ssoexport command?

If the setup is correct, the memory may be insufficient. Contact administrator of the host that executes the process, and then resolve the insufficient memory problem.

In cases other than the above, wait for some time, and then re-execute the process because the LDAP directory server may not be accessible due to temporary load.

KEOS02030-E (C)

The format of the specified file is incorrect. File=aa....aa, Line=bb....bb

aa....aa: File name

bb....bb: Number of lines

Description

An invalid value was found in the code in the line bb....bb in the code of the specified file. The file cannot be read because the file entered is not a CSV format file or the file coding is invalid. The processing will be interrupted.

Action

Check the CSV format, and then re-execute the process.

Are double quotations (") specified for the same lines?

Are there characters other than comma (,) before and after the character strings enclosed in double quotations (")?

KEOS02031-E (C)

The item ID is required. Item ID=aa....aa, File=bb....bb, Line=1

aa....aa: Item ID

bb....bb: File name

Description

Data could not be read because the coding of the specified file is invalid.

The processing will be interrupted.

Action

Always enter item ID on the first line of the CSV format file. Modify the file coding, and then re-execute the process.

KEOS02032-E (C)

The item ID already exists. Item ID=aa....aa, File=bb....bb, Line=1

aa....aa: Item ID

bb....bb: File name

Description

Data could not be read because the coding of the specified file is invalid.

The processing will be interrupted.

Action

Use a non-duplicate ID on the first line of the CSV format file. Modify the file coding, and then re-execute the process.

KEOS02036-W (C)

The column must have a value. File=aa....aa, Line=bb....bb, column=cc....cc

aa....aa: File name

bb....bb: Number of lines

cc....cc: Number of columns

Description

An invalid value was found in column cc....cc of line bb....bb in the code of the specified file.

This process is skipped and the next line is processed.

The value of the column cc....cc is not specified.

Action

Code a value in the column cc....cc of the line bb....bb, and then re-execute the process. Always specify the value of the column cc....cc.

KEOS02037-W (C)

The specified value of the column is invalid. File=aa....aa, Line=bb....bb, column=cc....cc

aa....aa: File name

bb....bb: Number of lines

cc....cc: Number of columns

Description

A value that cannot be specified was found in column cc....cc of line bb....bb in the code of the specified file. This process is skipped and the next line is processed.

If the invalid column is "OPERATION", a value not permitted in the operation mode (A: added, M: changed, D: deleted) is specified.

Action

Change to a valid value, and then re-execute the process.

KEOS02038-W (C)

The specified value of the property name is invalid. Default will be used instead.

Description

The value specified for properties is invalid. The processing continues with the default value.

Action

Revise the settings file.

KEOS02102-E (C)

(Message text is omitted.)

For details on this message, see KEOS02102-E in the uCosminexus Application Server Security Management Guide.

KEOS02111-W (C)

The user already exists. User ID=aa....aa, Realm=bb....bb, Line=cc....cc

aa....aa: User ID

bb....bb: Realm name

cc....cc: Number of lines

Description

An attempt was made to add an already registered user.

This process is skipped and the next line is processed.

Action

Confirm that the user ID and the realm name to be added are valid, modify the values if not valid, and then re-execute the process.

KEOS02112-W (C)

The user does not exist. User ID=aa....aa, Realm=bb....bb, Line=cc....cc

aa....aa: User ID

bb....bb: Realm name

cc....cc: Number of lines

Description

An attempt was made to delete a non-existing user.

This process is skipped and the next line is processed.

Action

Confirm that the user ID and realm name to be deleted are valid, modify the values if not valid, and then re-execute the process.

KEOS02152-E (C)

(Message text is omitted.)

For details on this message, see KEOS02152-E in the uCosminexus Application Server Security Management Guide.

KEOS02202-E (C)

(Message text is omitted.)

For details on this message, see KEOS02202-E in the uCosminexus Application Server Security Management Guide.

KEOS02250-E (C)

Failed to scramble the password. detail=aa....aa

aa....aa: Details

Description

Failed to scramble the password.

The processing will be interrupted.

Action

Check that the password is correct, and then re-execute the process.

KEOS02251-W (C)

The specified access information is invalid. detail=aa....aa

aa....aa: Details

Description

The access information specified in the configuration file of integrated user management is missing.

The processing will be interrupted.

Action

Revise the option.

KEOS02300-E (C/F)

(Message text is omitted.)

For details on this message, see KEOS02300-E in the uCosminexus Application Server Security Management Guide.

KEOS02501-W (C)

access denied: aa....aa

aa....aa: File name (reason)

Description

The user management settings file cannot be accessed.

Processing continues, using the default settings.

Action

Check the following contents, and then restart:

Are the com.cosminexus.admin.auth.config system properties specified?

Is a settings file specified in the com.cosminexus.admin.auth.config system properties and does it have read permissions?

13.3 Messages from KEOS10000 to KEOS19999

This section describes the messages from KEOS10000 to KEOS19999 output when Cosminexus Manager is used for system setup, operation, and maintenance.

KEOS10001-E (W/F)

No administrator's user account is specified.

Description

The management user account is not registered in the setting file of the Management Server.

The Management user account settings link will be displayed.

Action

Click the Management user account settings link, and then set the management user account.

KEOS10002-E (W/F)

An administrator's user ID or a password is incorrect.

Description

The management user ID and password when logging to the Management Server login are incorrect.

The specified request is ignored, and then the Login screen link will be displayed.

If you click the Login screen link, you will return to the Login screen.

Action

Set a valid management user ID or password.

KEOS10003-E (W/F)

No administrator's user ID is specified.

Description

The management user ID is not specified in the management user account settings screen.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

Set the management user ID in the management user account settings screen.

KEOS10004-E (W/F)

The password and re-entered password differ.

Description

The confirmation input of the password entered in the settings screen of the management user account is invalid.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

Set the same information as that of the password for the confirmation input in the management user account settings screen.

KEOS10005-E (W/F)

No host name is specified.

Description

The host name is not set in the settings screen for connecting to the Naming Service.

The specified request is ignored, and then the Return link will be displayed.

Action

Set the host name in the settings screen of the connection to the Naming Service. If you click the Return link, you will return to the most recently used screen.

KEOS10006-E (W/F)

The port number is specified incorrectly.

Description

The input format of the port number in the settings screen for connecting to the Naming Service is invalid.

The specified request is ignored, and then the Return link will be displayed.

Action

In the setting screen for connecting to the Naming Service, set the port number as an integer value in a valid format (1 to 65535). If you click the Return link, you will return to the most recently used screen.

KEOS10007-E (W/F)

The Management Server connection HTTP port number is specified incorrectly.

Description

In the network settings screen, the input format of HTTP port number for connecting to the Management Server is invalid.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

In the network settings screen, set the HTTP port number for connecting to the Management Server as an integer value in a valid format (1 to 65535).

KEOS10008-E (W/F)

The port number for the inside communication of Management Server is specified incorrectly.

Description

In the network-settings screen, the input format of the port number for Management Server internal communication is invalid.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

In the network settings screen, set the port number for Management Server internal communication as an integer value in a valid format (1 to 65535).

KEOS10009-E (W/F)

The administrator's user ID does not log in or has already logged out for the timeout.

Description

At present, you are not logged on to the Management Server.

The specified request is ignored, and then the Login screen link will be displayed.

If you click the Login screen link, you will return to the Login screen.

If the settings of the administrator's user account have been omitted, the Login link is displayed.

Action

Log on from the Login screen.

If the settings of the administrator's user account have been omitted, you can log in by clicking the Login link.

KEOS10010-I (W/F)

The administrator's user ID logged out normally.

Description

The process of logging out from the Management Server has ended normally.

KEOS10011-I (W/F)

The settings of the administrator's user account were changed.

Description

The settings of the administrator's user account were changed.

The new settings will be applied when logging on the next time.

KEOS10012-I (W/F)

The settings of the network were changed.

Description

The settings of the network were changed.

The new settings will be applied when the Management Server is restarted.

KEOS10013-I (W/F)

The settings of the connection to Naming Service were changed.

Description

The settings for the connection to the Naming Service are changed.

The new settings will be applied when the Management Server is restarted.

KEOS10014-I (W/F)

The settings of the log were changed.

Description

The settings of the log were changed.

The new settings of the log level will be applied immediately. However, the new settings regarding the number of log files, log file size, and the maximum log entries to be displayed will be applied when the Management Server is restarted.

KEOS10015-E (W/F)

The configuration file could not be saved. detail=aa....aa

aa....aa: Details

Description

While setting the Management Server, the settings file of the Management Server could not be saved.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

Remove the cause of the error based on the details. The following messages are displayed in the details:

In the case of management user account settings, Naming Service connection settings, log settings, start settings, performance analysis trace collection settings, JP1 integration settings

If an error occurs even after resetting, check whether the following files are deleted or the file permissions are changed:

In Windows

Cosminexus-installation-directory\manager\config\mserver.xml

In UNIX

/opt/Cosminexus/manager/config/mserver.xml

In the case of network settings

If an error occurs even after resetting, check whether the following files are deleted or the file permissions are changed:

In Windows

Cosminexus-installation-directory\manager\config\mserver.properties

In UNIX

/opt/Cosminexus/manager/config/mserver.properties

KEOS10019-I (W/F)

Management Server has started.

Description

The Management Server has started.

KEOS10020-I (W/F)

Management Server ended.

Description

The Management Server is terminated.

KEOS10021-E (W/F)

The portal definition file storage directory does not exist.

Description

The portal definition file storage directory does not exist.

The processing will be interrupted.

Action

Confirm that the following directories exist:

In Windows

Cosminexus-installation-directory\manager\containers\m\webapps\mngsvr\mportal\config

In UNIX

/opt/Cosminexus/manager/containers/m/webapps/mngsvr/mportal/config

KEOS10022-E (W/F)

The page could not be called.

Description

The corresponding processes cannot be executed because the Management Server is started by specifying the direct URL.

The processing will be interrupted.

Action

Invoke the page using the correct steps from the tree pane.

KEOS10023-E (W/F)

Chosen node does not exist.

Description

The selected node cannot be used because it is either already deleted, or it is changed.

The processing will be interrupted.

Action

Select the Initialize tree from the tree pane, update the tree, and then select the valid node.

KEOS10024-E (W/F)

The Management Server shutdown port number is specified incorrectly.

Description

The input format of the port number that receives the Management Server termination request in the network-setting screen is invalid.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

In the network setting screen, set the port number that receives the Management Server termination request as an integer value in the valid format (1 to 65535).

KEOS10025-E (W/F)

An attempt to initialize the tree has failed.

Description

An attempt to read the tree definition file has failed.

The processing will be interrupted.

Action

Display the target screen from the Management Portal screen once again.

If the same event occurs in this case, the tree definition file might also become corrupt. Contact maintenance personnel.

Also, if an error occurs during the JP1/IM start monitor operation, a domain server or a logical server related to the selected JP1 event does not exist in the current Management Server configuration. In this case, the start monitor operation cannot be executed from the applicable JP1 event.

KEOS10026-E (W/F)

The management information could not be initialized.

Description

The management information could not be initialized.

The processing will be interrupted.

Action

Restart after recovering the configuration information. If the problem cannot be resolved even after restarting the server, contact maintenance personnel.

KEOS10027-I (W/F)

The Management Domain configuration was saved.

Description

The Management Domain configuration was saved.

KEOS10028-E (W/F)

The Management Domain configuration could not be saved.

Description

The Management Domain configuration could not be saved.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

If an error occurs even after resetting, confirm that the specified directory exists.

KEOS10029-I (W/F)

The Management Domain configuration was recovered.

Description

The Management Domain configuration was recovered.

The new settings will be applied after you select the Initialize tree from the tree pane and update the tree.

KEOS10030-E (W/F)

The Management Domain configuration could not be recovered.

Description

The Management Domain configuration could not be recovered.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

If an error occurs even after resetting, confirm that the specified directory exists, and that the specified file was saved while saving the configuration information.

KEOS10031-Q (W)

The specified file aa....aa already exists. Do you want to overwrite this file?

aa....aa: Absolute path name of the file that already exists

Description

This message is displayed when saving to an existing file.

Yes and No buttons are displayed.

Action

Click Yes to overwrite the configuration information. If you select the No button, the process is not executed.

KEOS10032-E (W/F)

The file name of the Management Domain configuration is invalid.

Description

In the Save and Recover Screen of the configuration information, the input format of the configuration information file name is invalid.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

Set the configuration information file name in the Save and Recover Screen of the configuration information in a valid format (absolute path of not more than 256 characters).

KEOS10034-E (W)

Specified URL cannot be accessed.

Description

Specified URL cannot be accessed.

Action

Use the correct steps to access the Management Server.

KEOS10035-I (W/F)

The settings of the Start were changed.

Description

The settings of the Start were changed.

The new settings will be applied when the Management Server is started the next time.

KEOS10036-I (W/F)

The settings of the Performance Tracer were changed.

Description

The settings of the Performance Tracer were changed.

The new settings will be applied immediately.

KEOS10037-I (W/F)

The settings of the JP1 Collaboration Function were changed.

Description

The settings of the JP1 Collaboration Function were changed.

The new settings of filtering of system JP1 event will be applied immediately. However, the settings regarding the validity of system JP1 event issue functionality will be applied after the Management Server is restarted.

KEOS10038-I (F)

Management Server will be terminated because the logical server status is "abnormally stopped". Logical server = aa....aa (bb....bb)

aa....aa: Logical server name

bb....bb: Logical server type

Description

The operational status of the logical server is "abnormally stopped" (if the automatic restart count exceeds or a failure is detected, when the settings for the automatic restart count is 0), so Management Server will be terminated.

KEOS10101-I (L/F)

Management Server service has started.

Description

Management Server Service has started.

KEOS10102-I (L/F)

Management Server service ended.

Description

The Management Server Service was stopped.

KEOS10103-E (L/F)

Management Server service could not be initialized.

Description

An attempt to initialize the Management Server Service has failed.

The processing will be interrupted.

Action

A message describing the details is output. See the message, and then remove the cause of the error.

KEOS10104-E (L/F)

Management Server service could not be started.

Description

The Management Server Service cannot be started.

The processing will be interrupted.

Action

If the problem cannot be resolved even after restarting the server, contact maintenance personnel.

KEOS10105-E (F)

Management Server could not be output information to Event Log service.(ec = aa....aa)

aa....aa: Error code

Description

The information cannot be output to the event log.

The process will continue without output to the event log.

Action

Confirm that the event log service is operating normally.

KEOS10106-E (L/F)

Management Server could not be started.

Description

The Management Server cannot be started.

The processing will be interrupted.

Action

A message describing the details is output. See the message, and then remove the cause of the error.

KEOS10108-E (L/F)

The command of Management Server could not be acquired from the registry.

Description

The Management Server command cannot be acquired from the registry.

The processing will be interrupted.

Action

If the problem cannot be resolved even after restarting the server, contact maintenance personnel.

KEOS10109-E (L/F)

Management Server could not be executed.(ec = aa....aa)

aa....aa: Error code

Description

The Management Server cannot be executed.

The processing will be interrupted.

Action

The possible causes are as follows: Take the necessary action depending on the cause.

The contents of mserver.properties file are incorrect.

Check the contents of mserver.properties file.

The prerequisite programs are not installed.

Confirm that the prerequisite programs of the product are installed, and then re-execute the command.

If you are unable to resolve the problem with the actions mentioned above, see mngsvr.exe.1~16.log, mngsvr.exe.out, mngsvr.exe.err, mngsvrctl.exe.1~16.log in Windows, and mngsvrctlstart.1~16.log and the message output on the console in UNIX, remove the cause of the error, and then re-execute the command.

KEOS10110-I (C/F)

Management Server service has started from command line.

Description

The Management Server Service has started from the command line.

KEOS10111-I (C/F)

Management Server service ended from command line.

Description

The Management Server Service is stopped from the command line.

KEOS10112-E (C/F)

Management Server service could not be started from command line.

Description

An attempt to start the Management Server Service from the command line has failed.

The command execution will be suspended.

Action

The possible causes are as follows. Take the necessary action depending on the cause.

Management Server Service is already running.

Continue the process or stop the service, and then restart the Management Server Service.

Setup command is not executed.

Execute the setup.

The contents of mserver.properties file are incorrect.

Check the contents of mserver.properties file.

The prerequisite programs are not installed.

Confirm that the prerequisite programs of the product are installed, and then re-execute the command.

The synchronous execution is timed out (when the command completion code is 3).

After a pause, use the mngsvrutil check command, and confirm that Management Service is operating.

If you are unable to resolve the problem with the actions mentioned above, see mngsvr.exe.1~16.log, mngsvr.exe.out, mngsvr.exe.err, mngsvrctl.exe.1~16.log in Windows, and mngsvrctlstart.1~16.log and the message output on the console in UNIX, remove the cause of the error, and then re-execute the command.

KEOS10113-E (C/F)

Management Server service could not be ended from command line.

Description

An attempt to stop the Management Server Service from the command line has failed.

The command execution will be suspended.

Action

The possible causes are as follows. Take the necessary action depending on the cause:

The Management Server service is already stopped.

Check the operation status of the Management Server service.

The synchronous execution is timed out (when the command completion code is 3).

After a pause, confirm that Management Service is operating.

Check the operation state of the Management Server service.

If no problem exists in the operation state of the Management Server, see mngsvr.exe.1~16.log, mngsvr.exe.out, mngsvr.exe.err, mngsvrctl.exe.1~16.log in Windows, and to mngsvrctlstart.1~16.log and the message output on the console in UNIX, remove the cause of the error, and then re-execute the command.

KEOS10114-E (C) (Windows)

usage : mngsvrctl setup [<setup options>]|{start|stop} [<start/stop options>]

<setup options>:

[<server name>] [-u <uid>] [-p <password>]

[-nu <new uid>] [-np <new password>]

<start/stop options>:

[-sync [-timeout <timeout>]]

setup - initializing Management Server environment

start - starting Management Server service

stop - stopping Management Server service

<setup options>:

<server name> - Server name of Web container(default "cosmi_m")

-u <uid> - administrator's user ID

-p <password> - administrator's user password

-nu <new uid> - new administrator's user ID

-np <new password> - new administrator's user password

<start/stop options>:

-sync - Synchronously executes the command.

-timeout <timeout> - Sets the timeout for synchronous execution.

Description

The method of starting the command is incorrect.

The command execution will be suspended.

Action

Enter the correct command, and then re-execute the command.

KEOS10114-E (C) (UNIX)

usage : mngsvrctl setup [<setup options>]|{start|stop} [<start/stop options>]

<setup options>:

[<server name>] [-u <uid>] [-p <password>]

[-nu <new uid>] [-np <new password>]

<start/stop options>:

[-sync [-timeout <timeout>]] [-daemon]

setup - initializing Management Server environment

start - starting Management Server service

stop - stopping Management Server service

<setup options>:

<server name> - Server name of Web container(default "cosmi_m")

-u <uid> - administrator's user ID

-p <password> - administrator's user password

-nu <new uid> - new administrator's user ID

-np <new password> - new administrator's user password

<start/stop options>:

-sync - Synchronously executes the command.

-timeout <timeout> - Sets the timeout for synchronous execution.

-daemon - Starts the command as a daemon process.

Description

The method of starting the command is incorrect.

The command execution will be suspended.

Action

Enter the correct command, and re-execute the command.

KEOS10117-E (L/F)

Management Server could not make a temporary file.

Description

An attempt to create a temporary file has failed.

The command execution will be suspended.

The contents of the mserver.properties file may be invalid.

Action

Check the file contents.

If you are unable to resolve the problem, take the following actions:

In Windows

Overwrite the initial mserver.properties file stored in Cosminexus-installation-directory\manager\config\templates into Cosminexus-installation-directory\manager\config, and then re-execute the operation.

In UNIX

Copy the initial mserver.properties file present in /opt/Cosminexus/manager/config/templates into /opt/Cosminexus/manager/config, and then re-execute the command.

KEOS10118-I (C/F)

Management Server was initialized normally.

Description

An attempt to set up the Management Server was successful.

KEOS10119-E (C/F)

Management Server could not be initialized normally.

Description

An attempt to set up the Management Server has failed.

The command execution will be suspended.

Action

The possible causes are as follows: Take the necessary action depending on the cause.

Management Server is already set up.

Continue the process.

The specified server name is invalid.

Change the server name, and then re-execute the command.

The specified server name is already in use.

Change the server name, and then re-execute the command.

The prerequisite programs are not installed.

Confirm that the prerequisite programs of the product are installed, and then re-execute the command.

Management Server is started. (In Windows)

Stop Management Server, and then re-execute Management Server.

If you are unable to resolve the problem with the actions as mentioned above, see mngsvr.exe.1~16.log, mngsvr.exe.out, mngsvr.exe.err, mngsvrctl.exe.1~16.log in Windows, and to mngsvrctlstart.1~16.log and the message output on the console in UNIX, remove the cause of the error, and then re-execute the command.

KEOS10120-E (L/F)

Management Server could not acquired the server name.

Description

The server name cannot be acquired.

The command execution will be suspended.

A possible cause of the error is non-execution of the setup command.

Action

Execute the setup command.

If you are not able to remove the cause of the error, see mngsvr.exe.1~16.log, mngsvr.exe.out, mngsvr.exe.err, mngsvrctl.exe.1~16.log in Windows, and mngsvrctlstart.1~16.log in UNIX, and then re-execute the command.

KEOS10121-E (C/F)

Management Server could not be started.(ec = aa....aa)

aa....aa: Error code

Description

The Management Server cannot be started.

Action

Check the operating environment and the settings.

KEOS10122-E (L/F)

Since an error occurred, Management Server service stopped.

Description

The Management Server is stopped.

The processing will be interrupted.

Action

Investigate the cause based on the message displayed before this message, and then take necessary action.

KEOS10123-E (W/F)

The management portal cannot be used in aa....aa.

aa....aa: Product name

Description

The management portal cannot be used in the product name of the Cosminexus integrated format name specified in aa....aa. The processing will be interrupted.

Action

The management portal cannot be used.

KEOS10124-W (L/F)

The specified value of property aa....aa is invalid. The default setting will be used instead.

aa....aa: Property name

Description

The specified value of the property is invalid. The already set value will be used. The processing continues.

Action

Check the contents of the environment variable definition file.

KEOS10126-E (W/F)

An internal error occurred in the common library. (details = aa....aa)

aa....aa: Details

Description

An internal error occurred in the common library. The processing will be interrupted.

Action

If the problem is not resolved even after restarting and re-installing the server, contact maintenance personnel.

KEOS10127-E (L/F)

An attempt to copy the file has failed. (src=aa....aa, dest=bb....bb)

aa....aa: Copy Source

bb....bb: Copy Destination

Description

An attempt to copy the file has failed. The processing will be interrupted.

Action

If the problem is not resolved even after restarting the server, contact maintenance personnel.

KEOS10128-I (C/F)

The settings of the administrator's user account were changed.

Description

The settings of the administrator's user account were changed.

KEOS10129-E (C/F)

An administrator's user ID or a password is incorrect.

Description

An administrator's user ID or a password is incorrect. The processing will be interrupted.

Action

Set up a valid management user ID or password, and then re-execute the process.

KEOS10130-E (C/F)

The configuration file could not be saved.

Description

The configuration file could not be saved. The processing will be interrupted.

Action

Confirm whether the mserver.xml file stored in Cosminexus-installation-directory\manager\config has not been deleted or the file permission has been changed.

KEOS10131-E (C/F)

A connection to Management Server could not be established.

Description

A connection with the Management Server could not be established. The processing will be interrupted.

Action

The contents of the mserver.properties file might be incorrect. Check the file contents. If the problem is not resolved, terminate the Management Server and then re-execute the process.

KEOS10132-E (C)

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. The processing will be interrupted.

Action

Re-execute the command on a command prompt, as an administrator.

KEOS10133-E (C)

An error occurred while the permissions were being checked.

Description

An error occurred while the permissions were being checked. The processing will be interrupted.

Action

The memory may be insufficient. Increase the free memory, and then re-execute the command. If the problem is not resolved, contact maintenance personnel.

KEOS10134-I (C/F)

The user ID and password of the Management Server administrator account is not set up because the management user account is disabled.

Description

The user ID and password of the Management Server administrator account is not set up because the management user account is disabled.

KEOS10135-E (W/F)

An attempt to store the configuration information failed because there is an error either in the configuration information file or in the storage destination of the configuration information file. file name =aa....aa

aa....aa: File name

Description

An attempt to store the configuration information failed because there is an error either in the configuration information file or in the storage destination of the configuration information file.

The processing continues.

Action

The disk might be full. Make sure that the disk drive on which the Management Server is installed has sufficient free space. If there is no free space, allocate sufficient free space and then re-execute the previous operation. For details on the action to be taken, see 7.6.5 Action to be taken when KEOS10135-E message is displayed on the operation window in the uCosminexus Application Server Management Portal User Guide.

KEOS10136-W (F)

Synchronous execution of Management Server failed.

Description

The synchronous execution of Management Server has failed.

The synchronous execution will be interrupted.

Action

After a pause, use the mngsvrutil check command, and confirm that Management Service is operating. If you are unable to confirm the operation, reference the message output to mngsvr.exe.[1~16].log, mngsvr.exe.out, mngsvr.exe.err, and mngsvrctl.exe.[1~16].log remove the cause of the error, and then re-execute the command.

KEOS10137-I (F)

Specified options: aa....aa

aa....aa: Specified option

Description

This option is specified during the execution of the mngautorun command, adminagentctl command, or mngsvrctl command to start or stop the command.

KEOS11020-E (W/F)

Output of Management Domain configuration failed. detail=aa....aa

aa....aa: Details

Description

Output of Management Domain configuration failed.

The management domain configuration definition file is not output.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

Confirm that sufficient free space exists on the disk drive on which the Management Server is to be installed.

KEOS11038-I (W/F)

Management Domain was edited. Domain Name=[aa....aa] Display Name=[bb....bb]

aa....aa: Domain name

bb....bb: Display name

Description

Management Domain was edited.

KEOS11040-I (W/F)

Host was defined. Host Name=[aa....aa] Display Name=[bb....bb]

aa....aa: Host name

bb....bb: Display name

Description

Host was defined.

KEOS11041-I (W/F)

Host was edited. Host Name=[aa....aa] Display Name=[bb....bb]

aa....aa: Host name

bb....bb: Display name

Description

Host was edited.

KEOS11042-I (W/F)

Host was deleted. Host Name=[aa....aa] Display Name=[bb....bb]

aa....aa: Host name

bb....bb: Display name

Description

Host was deleted.

KEOS11043-I (W/F)

Hosts was deleted. Deleted Hosts=[aa....aa]

aa....aa: Display name

Description

Host was deleted.

KEOS11050-I (W/F)

Logical Server was added. Kind=[aa....aa] Logical Server Name=[bb....bb] Display Name=[cc....cc]

aa....aa: Type

bb....bb: Logical server name

cc....cc: Display name

Description

Logical Server was added.

KEOS11051-I (W/F)

Logical Server was edited. Kind=[aa....aa] Logical Server Name=[bb....bb] Display Name=[cc....cc]

aa....aa: Type

bb....bb: Logical server name

cc....cc: Display name

Description

Logical Server was edited.

KEOS11052-I (W/F)

Logical Server was deleted. Kind=[aa....aa] Logical Server Name=[bb....bb] Display Name=[cc....cc]

aa....aa: Type

bb....bb: Logical server name

cc....cc: Display name

Description

Logical Server was deleted.

KEOS11053-I (W/F)

Logical Servers was deleted. Deleted Servers=[aa....aa]

aa....aa: Display name

Description

Logical Server was deleted.

KEOS11060-E (W/F)

Host is not defined.

Description

Host is not defined.

The screen corresponding to the selected node is not displayed.

Action

Define the host that deploys the logical server.

KEOS11061-E (W/F)

Definition of Host failed. detail=aa....aa

aa....aa: Details

Description

Definition of Host failed.

The host is not defined.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

Resolve the problem displayed in the details, and then re-execute the command.

KEOS11062-E (W/F)

Edit of Host failed. detail=aa....aa

aa....aa: Details

Description

Edit of Host failed.

The host is not edited.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

Resolve the problem displayed in the details, and then re-execute the command.

KEOS11063-E (W/F)

Deletion of Host failed. detail=aa....aa

aa....aa: Details

Description

Deletion of Host failed.

The host is not deleted.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

Resolve the problem displayed in the details, and then re-execute the command.

KEOS11064-W (W/F)

Some Hosts cannot delete. failed Hosts=[aa....aa]

aa....aa: Display name

Description

An attempt to delete some hosts has failed.

Only the hosts that can be deleted are deleted.

Action

An attempt to delete some of the hosts has failed because the logical server is deployed in the host. Delete the deployed logical server, and then re-execute the process.

KEOS11070-E (W/F)

An attempt to add a logical server has failed. Details=aa....aa

aa....aa: Details

Description

An attempt to add a logical server has failed.

The logical server is not added.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will be returned to the most recently used screen.

Action

Resolve the problem displayed in the details, and then re-execute the command.

KEOS11071-E (W/F)

Edit of Logical Server failed. detail=aa....aa

aa....aa: Details

Description

Edit of Logical Server failed.

The logical server is not edited.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will return to the most recently used screen.

Action

Resolve the problem displayed in the details, and then re-execute the command.

KEOS11072-E (W/F)

Deletion of Logical Server failed. detail=aa....aa

aa....aa: Details

Description

Deletion of Logical Server failed.

The logical server is not deleted.

Action

Resolve the problem displayed in the details, and then re-execute the command.

KEOS11080-I (W/F)

The real server name was edited. Edited logical server = [aa....aa]

aa....aa: Display name

Description

The real server name was edited.

KEOS11081-E (W/F)

An attempt to edit the real server name has failed. Details = aa....aa

aa....aa: Failure information

Description

An attempt to edit the real server name has failed.

The real server name is not edited.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will be returned to the most recently used screen.

Action

Resolve the problem displayed in the details, and then re-execute the command.

KEOS11082-I (W/F)

aa....aa was set up. Host = [bb....bb] Real server = [cc....cc]

aa....aa: Display name

bb....bb: Host name

cc....cc: Real server name

Description

The J2EE server was set up.

KEOS11083-E (W/F)

The setup of aa....aa failed. Details = bb....bb

aa....aa: Display name

bb....bb: Details

Description

An attempt to set up the J2EE server has failed.

The J2EE server is not set up.

Action

Confirm the contents displayed in the details, resolve the problem, and then re-execute the command. The following contents are displayed in the details:

Could not communicate with the Administration Agent.

Is the Administration Agent running on the operating host of the applicable logical server?

Is the port number of the Administration Agent that is defined in the Management Server configuration definition same as the port number of the Administration Agent running on the host where the J2EE server is set up?

Is there a problem with the host name defined in the Management Server configuration definition (is proper communication possible with the commands such as the ping command?)?

Is the Management Server host that is being accessed when adminagent.adapter.allowedHosts is specified in the Administration Agent properties (adminagent.properties) permitted?

The setup command terminated abnormally.

Is a J2EE server, with a name differing only in the upper and lower cases, already set up (if the setup platform is Windows)?

Does the string length of the set up real server name satisfy the following conditional expression:

(String length of the real server name) = 220 - (Length of the Cosminexus Component Container installation directory path name) [unit: bytes]

The execution environment of the setup command is invalid.

Confirm that the prerequisite products are installed on the host where the J2EE server will be set up.

If the prerequisite products are installed, the operating environment might be corrupted. If the problem cannot be resolved even after restarting and re-installing the prerequisite products, contact maintenance personnel.

KEOS11084-E (W/F)

The setup of the real server could not be started. Details=aa....aa

aa....aa: Details

Description

An error occurred while starting the J2EE server setup.

The J2EE server is not set up.

The specified request is ignored, and then the Return link will be displayed.

If you click the Return link, you will be returned to the most recently used screen.

Action

Resolve the problem displayed in the details, and then re-execute the command.

KEOS11091-I (C)

Usage:

aa....aa

aa....aa: Usage of the command

Description

The processing will be interrupted. The command execution will be suspended.

Action

Check the command execution method.

KEOS11092-I (C)

The Management Server managed file was saved.

Description

The Management Server managed file was saved.

KEOS11093-E (C)

The Management Server managed file could not be saved. (cause = aa....aa)

aa....aa: Cause

Description

An attempt to save the Management Server managed file has failed. The command execution will be suspended.

Action

Check whether you have specified a non-existent definition file.

KEOS11094-I (C)

The Management Server managed file was recovered.

Description

The Management Server managed file was recovered.

KEOS11095-E (C)

The Management Server managed file could not be recovered. (cause = aa....aa)

aa....aa: Cause

Description

An attempt to recover the Management Server managed file has failed. The command execution will be suspended.

Action

Check whether you have specified a non-existing file, whether you have included a file that cannot be over-written, or whether the specified file is saved while saving the management file.

KEOS12001-E (W)

Cannot connect J2EE Server.

Description

An attempt was made to access the J2EE server to be monitored, but the connection failed.

The monitoring process will be interrupted.

Action

Confirm the following details:

Is the CORBA Naming Service running?

Is the setting (port number) of the running CORBA Naming Service the same as the value set in the Management Server?

Is the J2EE server to be monitored running?

Is a monitoring agent set for the J2EE server to be monitored?

If it is not set, then set it, and then restart the server.

Do the contents set in J2EE server to be monitored and the contents defined in 'configuration file of management domain' match?

If the settings of J2EE server to be monitored are incorrect, restart the server after you change the settings. Select the node that you want to reference from the tree pane.

If the logical server name of the J2EE server defined in 'Configuration definition of management domain' is invalid, change the definition of 'Configuration definition of management domain' and refresh 'Operation monitoring of the logical server'. Select Initialize tree in the tree pane, refresh the tree state, and then select the node that you want to reference from the tree pane.

If you select the node while the J2EE server is running, the communication may fail as the circuit is overloaded temporarily. Select the node that you want to reference once again from the tree pane.

KEOS12002-E (W)

The monitor target was not found.

Description

MBean to be monitored was not found.

The metric will not be extracted.

Action

Check the following details:

Is monitoring disabled in the resource to be monitored?

Is the resource to be monitored deleted due to un-deployment?

KEOS12003-E (W)

An unexpected exception occurred. detail=aa....aa

aa....aa: Details

Description

An unexpected event has occurred as displayed in the details.

The monitoring process will be interrupted.

Action

Contact maintenance personnel.

KEOS12004-E (W)

Cannot refer to the Management Domain configuration.

Description

An attempt to reference the J2EE server cluster or J2EE server to be monitored has failed because the configuration definition information is changed.

The monitoring process will be interrupted.

Action

Select Initialize tree in the tree pane, and then refresh the tree state. Select the node that you want to reference from the tree pane.

KEOS12005-E (W)

Cannot connect J2EE Server for SFO Server.

Description

An attempt was made to access the J2EE server for SFO server to be monitored, but the connection failed. The monitoring process will be interrupted.

Action

Confirm the following details:

Is the CORBA Naming Service running?

Is the setting (port number) of the running CORBA Naming Service the same as the value set in the Management Server?

Is the J2EE server for SFO server to be monitored running?

Is the monitoring agent in the J2EE server, for SFO server to be monitored, set up?

If it is not set, then set it, and then restart the server.

Do the contents set in J2EE server for SFO server to be monitored and the contents defined in 'configuration definition of management domain' match?

If the setting of J2EE server for SFO server to be monitored is invalid, restart the J2EE server after you change the setting. Select the node that you want to reference from the tree pane.

If the logical server name of J2EE server for SFO server defined in 'Configuration definition of management domain' is invalid, change the definition of 'Configuration definition of management domain' and refresh 'Operation monitoring of the logical server'. Select Initialize tree in the tree pane, refresh the tree state, and then select the node that you want to reference from the tree pane.

If you select the node while the J2EE server for SFO server is running, the communication may fail as the circuit is overloaded temporarily. Select the node that you want to reference once again from the tree pane.

KEOS13000-E (W/F)

Could not connect to the J2EE server.

Description

An attempt was made to access the J2EE server to be monitored, but the connection failed.

The processing will not be performed.

Action

Confirm the following details:

Is the CORBA Naming Service running?

Is the port number of the used CORBA Naming Service the same as the value defined in the Management Server?

Is the J2EE server to be monitored running?

Is a monitoring agent set up in the J2EE server to be monitored?

If it is not set, then set it, and then restart the server.

Do the contents set in J2EE server to be monitored and the contents defined in 'configuration file of management domain' match?

If the settings of J2EE server to be monitored are incorrect, restart the server after you change the settings. Select the node that you want to reference from the tree pane.

If the logical server name of the J2EE server defined in 'Configuration definition of management domain' is invalid, change the definition of 'Configuration definition of management domain' and refresh 'Operation monitoring of the logical server'. Select Initialize tree in the tree pane, refresh the tree state, and then select the node that you want to reference from the tree pane.

If you select the node while the J2EE server is running, the communication may fail as the circuit is overloaded temporarily. Select the node that you want to reference once again from the tree pane.

KEOS13001-E (W/F)

Cannot monitor selected J2EE server because it does not use Integrated User Administration.

Description

The configuration file for using the integrated user management in J2EE server is not set up.

The processing will not be performed.

Action

Set the integrated user management if the integrated user management functionality is to be used in the J2EE server.

KEOS13009-E (W/F)

An unexpected exception occurred. detail=aa....aa

aa....aa: Details

Description

An unexpected event has occurred as displayed in the details.

The processing will not be performed.

Action

Contact maintenance personnel.

KEOS13010-W (W/F)

Failed to access the repository. detail= aa....aa

aa....aa: Exception code

Description

The repository (LDAP directory server or RBD) specified in the connection destination URL can be accessed, however, the access failed as an exception (shown in details) has occurred.

This process is ignored, and then the following processes are implemented:

When the information indicating communication failure of javax.naming.CommunicationException is output to the details, the repository may not be running or the connection destination URL may be invalid.

Action

Check that the configuration file of integrated user management set up on the J2EE server being monitored is specified. If the correct value is set up, wait for some time, and then re-execute the command, because the repository may have become inaccessible due to temporary load.

KEOS13100-Q (W)

aa....aa in bb....bb already exists. Do you want to overwrite?

aa....aa: User ID

bb....bb: Realm

Description

This message is displayed when the registration process is executed for the user entries that already exist.

Yes and No buttons are displayed.

Action

Click Yes when you want to overwrite the user information. If you click the No button, this process is not executed.

KEOS13101-Q (W)

aa....aa will be removed. All managed entries will be removed. Are you sure?

aa....aa: Realm

Description

All the sub-entries are deleted when a realm is deleted, so the user is asked for confirmation.

The Delete button is displayed.

Action

Click the Delete button if you want to delete the realm.

KEOS13102-Q (W)

aa....aa in bb....bb will be removed. Are you sure?

aa....aa: User ID

bb....bb: Realm

Description

The user is asked to confirm the deletion of the user entry.

The Delete button is displayed.

Action

Click Delete if you want to delete the user entry.

KEOS13103-E (W/F)

aa....aa already exists.

aa....aa: Realm

Description

The specified realm already exists in the LDAP directory server.

The Return link will be displayed. If you click the Return link, you will return to Create realm screen.

Action

Change the registered realm name, and then re-register.

KEOS13104-E (W/F)

Failed to access the LDAP directory server. detail=aa....aa

aa....aa: Exception code

Description

This error occurs when the LDAP directory server cannot be accessed with the information specified in the Bind information screen.

The Return link will be displayed. If you select the Return link, you will return to the invoked screen.

Action

Confirm that the contents that are entered in the Bind information screen are appropriate. Confirm that the LDAP directory server is running. When the server is running and the settings are valid, the repository may be temporarily loaded and you may not be able to access it. Wait for some time, and then re-execute the command.

KEOS13105-E (W/F)

(Message text is omitted.)

For details on this message, see KEOS13105-E in the uCosminexus Application Server Security Management Guide.

KEOS13106-E (W/F)

(Message text is omitted.)

For details on this message, see KEOS13106-E in the uCosminexus Application Server Security Management Guide.

KEOS13107-E (W/F)

(Message text is omitted.)

For details on this message, see KEOS13107-E in the uCosminexus Application Server Security Management Guide.

KEOS13108-E (W)

aa....aa is already removed.

aa....aa: Realm

Description

In the user administration screen, there was an operation from the tree pane or tab for an already deleted realm.

Only the message is displayed.

Action

Initialize the tree from the tree pane. Select an existing realm from the tree pane. If you have selected an existing realm, the repository may be temporarily loaded and you may not be able to access it. Wait for some time, and then re-execute the operation.

KEOS13109-E (W)

aa....aa in bb....bb is already removed.

aa....aa: User ID

bb....bb: Realm

Description

In the user search screen, there was an operation from the tree pane or tab for an already deleted realm.

Only the message is displayed.

Action

In the user search screen, select a user entry that is not deleted. If you have selected an existing user entry, the repository may be temporarily loaded and you may not be able to access it. Wait for some time, and then re-execute the operation.

KEOS13110-E (W/F)

Incorrect password.

Description

The entered password and the re-entered password do not match.

The Return link will be displayed.

If you select the Return link, you will return to the invoked screen.

Action

Re-enter the password.

KEOS13111-E (W/F)

The indispensable parameter is not specified.

Description

The mandatory items are not entered.

The Return link will be displayed.

If you select the Return link, you will return to the invoked screen.

Action

Enter an appropriate value in the item name displayed on the screen, and then request once again.

KEOS13112-E (W/F)

aa....aa is already registered.

aa....aa: Item name

Description

The contents to be registered are already registered.

The Return link will be displayed.

If you select the Return link, you will return to the invoked screen.

Action

Take action depending on the state in which the error occurred.

In the case of defining the schema for user entry

Confirm that the object class to be added is not registered.

Confirm that the display name of optional attribute to be added is not registered.

Confirm that the listener class to be added is not registered.

In the case of create and compile screen of the user entry

Confirm that the connection destination realm name of the mapping information to be added is not registered.

KEOS13113-W (W)

Failed to register the listener class. Listener class= aa....aa detail=bb....bb

aa....aa: Listener class name

bb....bb: Exception code

Description

An attempt was made to apply the listener class to the settings information but failed.

The Return link will be displayed.

If you select the Return link, you will return to the invoked screen.

Action

Check that the specified listener class exists in the storage destination directory of the listener class. Also, check that it is a class that implements the SSODataListener interface provided by the integrated user management framework.

KEOS13114-W (W)

Failed to register the listener class. Listener class= aa....aa detail=bb....bb

aa....aa: Listener class name

bb....bb: Exception code

Description

The process is suspended because an exception from the listener class is caught.

The Return link will be displayed.

If you select the Return link, you will return to the invoked screen.

Action

Check that the used listener class meets the specifications for usage.

KEOS13115-E (W/F)

Failed to read the configuration file. detail=aa....aa

aa....aa: Exception code

Description

Failed to read the configuration file.

Only the message is displayed.

The default value is applied in each screen. If you perform create, apply, update, and delete operations in each screen, the settings used at that time are saved.

Action

Confirm that editusersConfig.dtd and editusersConfig.xml exist in the following directories, and that read permissions are available:

In Windows

Cosminexus-installation-directory\manager\containers\m\j2eeapps\mngsvr\mportal\useradmin\config\data

In UNIX

/opt/Cosminexus/manager/containers/m/j2eeapps/mngsvr/mportal/useradmin/config/data

Re-install the product if editusersConfig.dtd and editusersConfig.xml do not exist.

The contents may be invalid even if the file exists. Change the name of the file editusersConfig.xml.bak to editusersConfig.xml, and then restart the user management screen.

KEOS13116-E (W/F)

Failed to write the configuration file. detail=aa....aa

aa....aa: Exception code

Description

An attempt to save the settings information file has failed.

The Return link will be displayed.

If you select the Return link, you will return to the invoked screen.

Action

Confirm that sufficient free space exists on the disk drive on which the Management Server is to be installed.

KEOS13117-I (W/F)

The bind information was applied.

Description

The bind information was applied.

The Return link will be displayed.

Action

Select the Return link. If you select the Return link, you will return to the setting screen of the bind information.

KEOS13118-I (W/F)

aa....aa was created.

aa....aa: Realm

Description

The realm was created.

The Return link will be displayed.

Action

Select the Return link. If you select the Return link, you will return to the screen that creates the realm.

KEOS13119-I (W/F)

(Message text is omitted.)

For details on this message, see KEOS13119-I in the uCosminexus Application Server Security Management Guide.

KEOS13120-I (W/F)

The schema definition of user entry was modified.

Description

The schema definition of user entry was modified.

The Return link will be displayed.

Action

Select the Return link. If you select the Return link, you will return to the screen that defines the schema of the user entry.

KEOS13121-I (W/F)

aa....aa in bb....bb was created.

aa....aa: User ID

bb....bb: Realm

Description

The user entry was created.

The Return link will be displayed.

Action

Select the Return link. If you select the Return link, you will return to the user entry creation screen.

KEOS13122-I (W/F)

aa....aa in bb....bb was modified.

aa....aa: User ID

bb....bb: Realm

Description

The user entry was updated.

The Return link will be displayed.

Action

Select the Return link. If you select the Return link, you will return to the user entry edit screen.

KEOS13123-I (W/F)

aa....aa was removed successfully.

aa....aa: Realm

Description

The realm and all the sub-entries managed under it were deleted.

Only the message is displayed.

Action

Initialize the tree from the tree pane, and then move to another screen in the tree pane.

KEOS13124-I (W/F)

aa....aa in bb....bb was removed successfully.

aa....aa: User ID

bb....bb: Realm

Description

The user entry was deleted.

Only the message is displayed.

Action

Move to the other screen in the tree pane.

KEOS13125-E (W/F)

(Message text is omitted.)

For details on this message, see KEOS13125-E in the uCosminexus Application Server Security Management Guide.

KEOS13126-E (W/F)

(Message text is omitted.)

For details on this message, see KEOS13126-E in the uCosminexus Application Server Security Management Guide.

KEOS13127-W (W/F)

Failed to add aa....aa

aa....aa: Realm

Description

An entered realm cannot be operated from the screen that manages the repository.

The Return link will be displayed.

An entry of the same name as that of the entered realm name already exists in the repository to be connected but an attempt to add a realm has failed because it does not conform to the DIT standards that are recommended by integrated user management framework.

If you select the Return link, you will return to the invoked screen.

Action

Change the realm name to be created or specify an entry according to the DIT standards.

KEOS13128-E (W/F)

aa....aa is already registered as an indispensable attribute.

aa....aa: Attribute name

Description

An entered attribute name is already used as a mandatory attribute.

The Return link will be displayed.

If you select the Return link, you will return to the invoked screen.

Action

Change the attribute name to be registered. If you cannot change the attribute name to be registered, change the attribute name similar to the name specified in the mandatory attribute.

KEOS13129-E (W/F)

aa....aa is already registered as an optional attribute.

aa....aa: Attribute name

Description

The Attribute name is already registered as an optional attribute.

The Return link will be displayed.

If you select the Return link, you will return to the invoked screen.

Action

Change the attribute name to be registered. If you cannot change the attribute name to be registered, delete the attribute name of the same name from the list of optional attributes.

KEOS14000-I (F)

Start management agent.

Description

The management agent operations are started.

KEOS14001-I (F)

Stop management agent.

Description

The management agent operations are stopped.

KEOS14002-E (F)

Cannot start management agent.

Description

An attempt to start the management agent has failed.

Action

Check the operating environment and the settings.

KEOS14003-E (F)

Stopping management agent failed.

Description

An attempt to stop the management agent has failed.

Action

Check the operating environment and the settings.

KEOS14004-E (C)

Cannot open file: aa....aa

aa....aa: File name

Description

An attempt to open the file has failed.

The operations of the management agent continue if possible, and stop if they cannot be continued.

Action

Check the operating environment and the settings such as file name and permissions.

KEOS14005-E (F)

Cannot initialize ORB.

Description

The ORB cannot be initialized.

The management agent operations are stopped.

Action

Check the operating environment and the settings.

KEOS14006-E (C)

Domain name is not specified.

Description

The domain name of the management agent is not specified correctly.

The management agent operations are stopped.

Action

Set the domain name of the management agent correctly.

KEOS14007-E (C)

Agent name is not specified.

Description

The agent name of the management agent is not specified correctly.

The management agent operations are stopped.

Action

Set the agent name of the management agent correctly.

KEOS14008-E (F)

Agent name is already used.

Description

The agent name of the management agent is already in use.

The management agent operations are stopped.

Action

Check the operating environment and the settings.

KEOS14009-E (F)

Trouble occurred about ORB. reason=aa....aa

aa....aa: Details

Description

Some failure related to ORB occurred.

The operations of the management agent continue if possible, and stop if they cannot be continued.

Action

Check the operating environment and the settings.

KEOS14010-E (F)

Trouble occurred about Naming Service. reason=aa....aa

aa....aa: Details

Description

Some failure related to CORBA Naming Service occurred.

The operations of the management agent continue if possible, and stop if they cannot be continued.

Action

Check the operating environment and the settings.

KEOS14011-E (C)

Invalid log file number was specified.

Description

The specified number of log files of the management agent is invalid.

The management agent operations continue with the default value.

Action

Check the operating environment and the settings.

KEOS14012-E (C)

Invalid log file size was specified.

Description

The specified log file size of the management agent is invalid.

The management agent operations continue with the default value.

Action

Check the operating environment and the settings.

KEOS14013-E (C)

Invalid log file name was specified.

Description

The specified log file name of the management agent is invalid.

The management agent operations continue with the default value.

Action

Check the operating environment and the settings.

KEOS14014-E (C)

Invalid domain name is specified.

Description

The specified domain name of the management agent is invalid.

The management agent operations are stopped.

Action

Set the domain name of the management agent correctly.

KEOS14015-E (C)

Invalid agent name is specified.

Description

The specified agent name of the management agent is invalid.

The management agent operations are stopped.

Action

Set the agent name of the management agent correctly.

KEOS14016-E (F)

Failed to connect to the RMI registry. reason=aa....aa

aa....aa: Error detailed information and its reason

Description

Failed to connect to the RMI registry. The management agent operations are stopped.

Action

Revise the settings related to the RMI registry of the J2EE server.

KEOS14017-E (F)

Trouble occurred about RMI registry. reason=aa....aa

aa....aa: Error detailed information and its reason

Description

Some failure related to RMI registry occurred. The operations of the management agent continue if possible, and stop if they cannot be continued.

Action

See the details, check the operating environment and the settings.

KEOS16001-I (F)

Authentication succeeded. (remote address = aa....aa)

aa....aa: Client IP address

Description

The client authentication was successful.

A message is displayed in the log file, and the processing continues.

KEOS16002-E (F)

Authentication failed. (remote address = aa....aa)

aa....aa: Client IP address

Description

The client authentication has failed.

A message is displayed in the log file, and the processing continues.

Action

Check the management user ID or password to be used for logging in to the Management Server.

KEOS16003-I (F)

Authentication was challenged. (remote address = aa....aa)

aa....aa: Client IP address

Description

The access by HTTP was checked.

A message is displayed in the log file, and the processing continues.

KEOS16004-E (F)

Access was denied. (remote address = aa....aa)

aa....aa: Client IP address

Description

The access was denied to the client.

A message is displayed in the log file, and the processing continues.

Action

Confirm that the access from the client is valid.

KEOS16005-W (F)

Access was denied. (property file = aa....aa)

aa....aa: Property file name

Description

The property file cannot be accessed.

A message is displayed in the log file, and the processing continues.

Action

Confirm that the property file exists and that the access permission to the property file is available.

KEOS16100-I (C)

Usage:

mngsvrutil [-m <host>[:<port>] -u <uid> [-p <password>]

[[-o <output file>] [-h] [-f <format>] [-t <target name>]

[-k <target kind>] [-s] [-i <watching time interval>]

[-l <maximum watching time>] [-w <waiting time>] <command> <args>]]

For more information, type

mngsvrutil -m <host>[:<port>] -u <uid> [-p <password>]

where:

-m <host>[:<port>]

Specifies the host and the port number of the management server to be

connected.

<host> - host name or IP address (in dotted-decimal form)

<port> - port number (the default is 28080)

-u <uid>

Specifies the user ID of the administrative account of the management server

to be connected.

-p <password>

Specifies the password of the administrative account of the management server

to be connected.

--

Version aa....aa (mngsvrutil)

aa....aa: mngsvrutil version

Description

This message describes the usage method of the mngsvrutil command.

A message is displayed in the standard error output, and then the processing terminates.

Action

See the message, and check the usage method of the command.

KEOS16101-E (C)

An argument is empty.

Description

A null character is specified in the argument.

A message is displayed in the standard error output, and then the processing continues.

Action

Check the format of the mngsvrutil command.

KEOS16102-E (C)

The option aa....aa is invalid.

aa....aa: Specified option

Description

The option is invalid.

A message is displayed in the standard error output, and then the processing continues.

Action

Check the format of the mngsvrutil command.

KEOS16103-E (C)

The option aa....aa is unknown.

aa....aa: Specified option

Description

A relevant option does not exist.

A message is displayed in the standard error output, and then the processing continues.

Action

Check the format of the mngsvrutil command.

KEOS16104-E (C)

No argument was specified for the option aa....aa.

aa....aa: Option for which an argument is not specified

Description

An argument was not specified for the option.

A message is displayed in the standard error output, and then the processing continues.

Action

Specify an argument for the option.

KEOS16105-E (C)

An argument of option aa....aa is empty.

aa....aa: Option for which a null character is specified in the argument

Description

A null character was specified in the argument of the option.

A message is displayed in the standard error output, and then the processing continues.

Action

Check the format of the mngsvrutil command.

KEOS16106-E (C)

The Management Server host to which you will connect was not specified.

Description

The host name of the Management Server to which you will connect was not specified.

A message is displayed in the standard error output, and then the processing continues.

Action

Check the host name and port number of the Management Server to which you will connect, and then specify the host name.

KEOS16107-E (C)

The user ID of the administrative account of Management Server was not specified.

Description

The user ID of the management account of the Management Server is not specified.

A message is displayed in the standard error output, and then the processing continues.

Action

Check the management user ID and password to be used while logging on to the Management Server, and then specify the user ID.

KEOS16108-E (C)

A connection to Management Server could not be established. (aa....aa)

aa....aa: Specified host name and port number

Description

A connection with the Management Server could not be established.

A message is displayed in the standard error output, and then the processing continues.

Action

Check the host name and port number of the Management Server to which you will connect, and then specify the host name.

Also, if the communication fails since the circuit is overloaded, change the value of mngsvrutil.session.max_inactive_interval of the server side-settings file (mngsvrutil.properties) into an appropriate value, and then re-execute the command.

KEOS16109-E (C)

The client cannot access the specified file aa....aa.

aa....aa: Specified file name

Description

The client cannot access the specified file.

A message is displayed in the standard error output, and then the processing continues.

Action

Confirm that the access permission for the relevant file is available.

KEOS16110-E (C)

Authentication has failed.

Description

An attempted authentication has failed.

A message is displayed in the standard error output, and then the processing continues.

Action

Check the IP address and port number of the Management Server to which you will connect.

KEOS16111-E (C)

An internal error occurred.

Description

An internal error occurred.

A message is displayed in the standard error output, and then the processing continues.

Action

If the cause of the error cannot be removed even after restarting the Management Server, contact maintenance personnel.

KEOS16112-E (C)

A Java command call has failed.

Description

An attempt to invoke a java command has failed.

A message is displayed in the standard error output, and then the processing continues.

A pre-requisite product may not have been installed or the operating environment may have been damaged.

Action

Check the pre-requisite products. If no problem exists in the pre-requisite products, restart and re-install the products.

If the problem is not resolved with the above actions, contact maintenance personnel

KEOS16113-W (C)

An attempt to access the file .aa....aa has failed.

aa....aa: Absolute path of the mngsvrutilrc file

Description

An attempt to read the .mngsvrutilrc file has failed.

A message is displayed in the standard error output, and then the processing continues.

Action

Confirm that the access permission to the .mngsvrutilrc file is available.

KEOS16114-E (C)

An invalid number was specified as the argument for the option aa....aa.

aa....aa: Specified option

Description

An invalid number is specified as the argument for the option.

A message is displayed in the standard error output, and then the processing terminates.

Action

Check the arguments for the option.

KEOS16115-E (C)

Command processing has failed.

Description

The subcommand processing has failed.

A message is displayed in the standard error output, and then the processing terminates.

Action

Investigate the cause of the error from the Management Server log. Remove the cause of the error, and then re-execute the process.

KEOS16116-E (C)

Command processing could not finish within the time limit.

Description

The processing did not terminate within the time specified in the maximum monitoring time.

Action

Increase the value specified in the maximum monitoring time, and then re-execute the command.

KEOS16117-E (C)

An error response was received from the Web container. (response code = aa....aa)

aa....aa: Response code

Description

An error response is received from the Web container. A message is displayed in the standard error output, and then the processing terminates.

Action

Check the response code to examine the cause of error, remove the error, and then re-execute the command.

KEOS16200-I (C)

Usage:

mngsvrutil [-m <host>[:<port>] -u <uid> [-p <password>]

[[-o <output file>] [-h] [-f <format>] [-t <target name>]

[-k <target kind>] [-s] [-i <watching time interval>]

[-l <maximum watching time>] [-w <waiting time>] <command> <args>]]

where:

-m <host>[:<port>]

Specifies the host and the port number of the management server to be

connected.

<host> - host name or IP address (in dotted-decimal form)

<port> - port number (the default is 28080)

-u <uid>

Specifies the user ID of the administrative account of the management server

to be connected.

-p <password>

Specifies the password of the administrative account of the management server

to be connected.

-o <output file>

Specifies a file name to which results are output.

-h

Suppresses the header.

-f <format>

Formats the output. <format>:=csv|snmp (the default is csv)

-t <target name>

Specifies a target name, such as a logical server or host.

-k <target kind>

Indicates the kind of a target. <target kind>:=logicalServer|host (the default

is logicalServer)

-s

Waits for the completion of the starting or stopping of the logical server

and the J2EE application.

-i <watching time interval>

Specifies a watching time interval for operations such as the starting or

stopping of the logical server and the J2EE application.

-l <maximum watching time>

Specifies the maximum watching time for operations such as the starting or

stopping of the logical server and the J2EE application.

-w <waiting time>

Specifies the waiting time for checks whether specified target is working.

<command>

"list" - Lists the values of the arguments.

"get" - Acquires the value of the argument for the target logical server

specified.

"set" - Sets the value of the 1st argument to the 2nd argument for the

target logical server specified.

"start" - Starts the logical server specified.

Starts the J2EE application or the J2EE resource of the

target logical server specified.

"stop" - Stops the logical server specified.

Stops the J2EE application or the J2EE resource of the

target logical server specified.

"reload" - Reloads the settings files specified by the argument.

"hold" - Holds the service specified by the argument.

"release" - Releases the service specified by the argument.

"collect" - Collects the value of the arguments.

"change" - Changes the value of the arguments.

"check" - Checks whether specified target is working.

"dump" - Dumps the javacore of the arguments.

"add" - Add logical server.

"delete" - Delete logical server.

<args>

For the "list" command:

"logicalServers" - Lists the logical server names of the management domain

and shows whether each server is alive or not. [DEPRECATED]

"status" - Lists statuses and information for logical servers.

"appStatus" - Lists the J2EE application names imported to the

specified target logical server and shows the status.

"resStatus" - Lists the J2EE resource names imported to the

specified target logical server and shows the status.

"resJavaBeansStatus" - Lists the J2EE JavaBeans resource names imported

to the specified target logical server and shows the status.

"queues" - Lists the CTM queues in the target specified by the argument

and shows the status.

For the "get" command:

"domainName" - Acquires the management domain name managed by the

connecting management server.

"j2eeContainer" - Acquires information about the J2EE container.

"webContainer" - Acquires information about the Web container.

"jvm" - Acquires information about Java VM.

"transaction" - Acquires information about transactions.

"httpServer" - Acquires information about the included HTTP server.

[DEPRECATED]

"httpSvrConn" - Acquires information about the HTTP server connector.

"inprocHttpSvr" - Acquires information about the In-process HTTP server.

"dataSource" - Acquires information about DataSources (JDBC).

"dataSrcFull" - Acquires information about DataSources (FullJTA).

"resAdapter" - Acquires information about ResourceAdapters.

"j2eeApps" - Acquires information about J2EE applications.

"ejbApps" - Acquires information about EJB applications(EJB-JARs).

"statelessBean" - Acquires information about Stateless Session Beans.

"statelessBeanHome" - Acquires information about the RemoteHome interface

of Stateless Session Beans.

"statelessBeanHomeMethod" - Acquires information about the method of the

RemoteHome interface of Stateless Session Beans.

"statelessBeanLocalHome" - Acquires information about the LocalHome

interface of Stateless Session Beans.

"statelessBeanLocalHomeMethod" - Acquires information about the method of

the LocalHome interface of Stateless Session Beans.

"statelessBeanRemote" - Acquires information about the RemoteComponent

interface of Stateless Session Beans.

"statelessBeanRemoteMethod" - Acquires information about the method of

the RemoteComponent interface of Stateless Session Beans.

"statelessBeanLocalComponent" - Acquires information about the

LocalComponent interface of Stateless Session Beans.

"statelessBeanLocalComponentMethod" - Acquires information about the

method of the LocalComponent interface of Stateless Session Beans.

"statefulBean" - Acquires information about Stateful Session Beans.

"statefulBeanHome" - Acquires information about the RemoteHome interface

of Stateful Session Beans.

"statefulBeanHomeMethod" - Acquires information about the method of the

RemoteHome interface of Stateful Session Beans.

"statefulBeanLocalHome" - Acquires information about the LocalHome

interface of Stateful Session Beans.

"statefulBeanLocalHomeMethod" - Acquires information about the method of

the LocalHome interface of Stateful Session Beans.

"statefulBeanRemote" - Acquires information about the RemoteComponent

interface of Stateful Session Beans.

"statefulBeanRemoteMethod" - Acquires information about the method of

the RemoteComponent interface of Stateful Session Beans.

"statefulBeanLocalComponent" - Acquires information about the

LocalComponent interface of Stateful Session Beans.

"statefulBeanLocalComponentMethod" - Acquires information about the

method of the LocalComponent interface of Stateful Session Beans.

"entityBean" - Acquires information about Entity Beans.

"entityBeanHome" - Acquires information about the RemoteHome interface of

Entity Beans.

"entityBeanLocalHome" - Acquires information about the LocalHome

interface of Entity Beans.

"entityBeanRemote" - Acquires information about the RemoteComponent

interface of Entity Beans.

"entityBeanLocalComponent" - Acquires information about the LocalComponent

interface of Entity Beans.

"msgDrivenBean" - Acquires information about Message Driven Beans.

"webApps" - Acquires information about Web applications.

"servlets" - Acquires information about servlets.

"requestUrl" - Acquires information about requested URLs.

"queues" - Acquires information about CTM queues.

"queueApps" - Acquires information about J2EE Application that connected

to CTM queues.

For the "set" command:

"jvmSamplingTime <n>" - Sets the sampling time of statistics about

Java VM to <n> sec.

If <n> is less than or equal to zero, statistics are disabled.

"webContainerSamplingTime <n>" - Sets the sampling time of statistics

about Web containers to <n> sec.

If <n> is less than or equal to zero, statistics are disabled.

"tranSamplingTime <n>" - Sets the sampling time for statistics about

transactions to <n> sec.

If <n> is less than or equal to zero, statistics are disabled.

"httpSvrSamplingTime <n>" - Sets the sampling time for statistics about

the included HTTP server to <n> sec. [DEPRECATED].

If <n> is less than or equal to zero, statistics are disabled.

"httpSvrConnSamplingTime <n>" - Sets the sampling time for statistics

about the HTTP server connector to <n> sec.

If <n> is less than or equal to zero, statistics are disabled.

"inprocHttpSvrSamplingTime <n>" - Sets the sampling time of statistics

about the In-process HTTP server to <n> sec.

If <n> is less than or equal to zero, statistics are disabled.

"dataSrcFullSamplingTime <n>" - Sets the sampling time for statistics

about data sources (Full JTA) to <n> sec.

If <n> is less than or equal to zero, statistics are disabled.

"resAdapterSamplingTime <n>" - Sets the sampling time for statistics

about resource adapters to <n> sec.

If <n> is less than or equal to zero, statistics are disabled.

"ejbSamplingTime <n>" - Sets the sampling time for statistics about

Enterprise Beans to <n> sec.

If <n> is less than or equal to zero, statistics are disabled.

"webAppSamplingTime <n>" - Sets the sampling time for statistics about

Web Applications to <n> sec.

If <n> is less than or equal to zero, statistics are disabled.

"servletSamplingTime <n>" - Sets the sampling time for statistics about

Servlets to <n> sec.

If <n> is less than or equal to zero, statistics are disabled.

"reqUrlSamplingTime <n>" - Sets the sampling time for statistics about

requested URLs to <n> sec.

If <n> is less than or equal to zero, statistics are disabled.

"prfTraceLevel STANDARD|DETAIL|<traceLevel>" - Sets the PRF trace level.

"allPrfTraceLevel STANDARD|DETAIL|<traceLevel>" - Sets the PRF trace level

in the management domain.

For the "start" command:

"allServers" - Starts all logical servers in order.

"server" - Starts the logical server.

"app <displayName>" - Starts the J2EE application of <displayName>.

"resAdapter <displayName>" - Starts the resource adapter of <displayName>.

"resJavaBeans <displayName>" - Starts the JavaBeans resource of

<displayName>.

For the "stop" command:

"allServers" - Stops all logical servers in order.

"server [graceful[:<waitTime>]]" - Stops the logical server.

"app <displayName> [force]" - Stops the J2EE application of <displayName>.

"resAdapter <displayName>" - Stops the resource adapter of <displayName>.

"resJavaBeans <displayName>" - Stops the JavaBeans resource of

<displayName>.

For the "reload" command:

"userAdmin" - Reloads the settings files used by Integrated User

Administration facilities.

"env" - Reloads the settings files from host at destination of

connection with J2EE server and SFO server.

For the "hold" command:

"queue <queueName> {in[:<waitTime>] | out | force[:<waitTime>]}" - Holds

the CTM queue specified by the argument.

"queues {in[:<waitTime>] | out | force[:<waitTime>]}" - Holds the CTM

queues in the target specified by the argument.

"allQueues {in[:<waitTime>] | out | force[:<waitTime>]}" - Holds all CTM

queues in the management domain.

For the "release" command:

"queue <queueName>" - Releases the CTM queue specified by the argument.

"queues" - Releases the CTM queues in the target specified by the

argument.

"allQueues" - Releases all CTM queues in the management domain.

For the "collect" command:

"prfTrace" - Collects the PRF trace.

"allPrfTraces" - Collects the PRF trace in the Management domain.

"ctmStatistics" - Collects the CTM statistics.

"allCtmStatistics" - Collects the CTM statistics in the Management domain.

"snapshot" - Collects the snapshotlog.

For the "change" command:

"webAppThreadCtrl <webApplicationContextRoot> <maxThreads>,

<exclusiveThreads>,<queueSize>" - Changes the Web application thread

control group values in the target specified by the argument.

For the "check" command:

"mngsvr" - Checks whether the management server is working.

"adminAgent" - Checks whether the AdminAgent of specified host is working.

For the "dump" command:

"server [addition]" - Dumps the javacore of specified logical server.

For the "add" command:

"userserver <userServerDefinitionFile>" - Add user server.

For the "delete" command:

"userserver <logicalServerName>" - Delete user server.

--

Version aa....aa (management server connected)

Version bb....bb (mngsvrutil)

aa....aa: Connected Management Server version

bb....bb: mngsvrutil version

Description

This message describes the usage method of the mngsvrutil command.

A message is displayed in the standard error output, and then the processing terminates.

Action

See the message, and check the usage method of the command.

KEOS16201-E (C)

Authentication failed.

Description

An attempted authentication has failed.

A message is displayed in the standard error output, and then the processing terminates.

Action

Check the management user ID or password to be used for logging in to the Management Server.

KEOS16202-E (C)

The command aa....aa is unknown.

aa....aa: Specified sub-command

Description

The specified command is an un-supported subcommand.

A message is displayed in the standard error output, and then the processing terminates.

Action

Check the subcommands supported by the Management Server to which you will connect.

KEOS16203-E (C)

The option aa....aa is unknown.

aa....aa: Specified option

Description

The option is not supported.

A message is displayed in the standard error output, and then the processing terminates.

Action

Check the options supported by the Management Server to which you will connect.

KEOS16204-E (C)

The logical server aa....aa is unknown.

aa....aa: Specified logical server name

Description

The specified logical server is either not defined in the management domain, not set up, or not running. Furthermore, a logical server of a type 0that is not the target of the command (that can only handle logical servers of a specific type) may have been specified in the command.

A message is displayed in the standard error output, and then the processing terminates.

Action

Confirm the following details:

The specified logical server is defined in the management domain.

The defined logical server is running, and the monitoring functionality of the management portal can be used to confirm that the logical server is running.

The defined logical server is set up.

A logical server of a type handled by the command is specified.

If the command is executed when the logical server is running or if the circuit is temporarily overloaded, the communication may fail. Re-execute the command.

KEOS16205-E (C)

No argument was specified.

Description

An argument is not specified for the subcommand.

A message is displayed in the standard error output, and then the processing terminates.

Action

Specify an argument for the subcommand.

KEOS16206-E (C)

There are too few arguments. (aa....aa)

aa....aa: Argument specified for the subcommand

Description

The arguments for the subcommand are not sufficient.

A message is displayed in the standard error output, and then the processing terminates.

Action

Check the arguments for the subcommand.

KEOS16207-E (C)

There are too many arguments. (aa....aa)

aa....aa: Argument specified for the subcommand

Description

There are too many arguments specified for the subcommand.

A message is displayed in the standard error output, and then the processing terminates.

Action

Check the arguments for the subcommand.

KEOS16208-E (C)

The argument aa....aa is invalid.

aa....aa: Argument specified for the subcommand

Description

The arguments for the subcommand are invalid.

A message is displayed in the standard error output, and then the processing terminates.

Action

Check the subcommands supported by the Management Server to which you will connect.

KEOS16209-E (C)

The format aa....aa is unknown.

aa....aa: Specified output format

Description

The output format is not supported.

A message is displayed in the standard error output, and then the processing terminates.

Action

Check the output formats supported by the Management Server to which you will connect.

KEOS16210-E (C)

The value aa....aa is invalid.

aa....aa: Specified value

Description

An invalid value is entered as a number.

A message is displayed in the standard error output, and then the processing terminates.

Action

Specify a valid number.

KEOS16211-E (C)

An internal error occurred.

Description

An internal error occurred.

A message is displayed in the standard error output, and then the processing terminates.

Action

Confirm that the version of the Management Server of the host to be monitored is the same or later than the version of the Management Server to which you will connect. If the version is the same, restart the Management Server. If the cause of the error cannot be removed even after the Management Server is restarted, contact maintenance personnel.

KEOS16212-E (C)

The target logical server name was not specified.

Description

The logical server name that forms the command target is not specified.

A message is displayed in the standard error output, and then the processing terminates.

Action

Specify the -t option or specify the mngsvrutil.target_name property in the mngsvrutilrc file.

Confirm that the target type for the command is specified.

KEOS16213-E (C)

A request failed. (aa....aa)

aa....aa: Detailed information on the reason for request failure

Description

A start or stop request has failed.

A message is displayed in the standard error output, and then the processing terminates.

Action

Check the details on the cause for the request failure.

KEOS16214-E (C)

Setting files cannot be reloaded because the specified logical server does not use Integrated User Administration.

Description

The specified logical server does not use Integrated User Management, so the configuration file cannot be reloaded.

A message is displayed in the standard error output, and then the processing terminates.

Action

To use the Integrated User Management functionality in the logical server, set up Integrated User Management.

KEOS16215-E (C)

An attempt to reload the setting file aa....aa has failed.

aa....aa: Name of the file that cannot be read

Description

An attempt to reload the configuration file of the integrated user management has failed.

A message is displayed in the standard error output, and then the processing terminates.

Action

Confirm that the configuration file exists in the path specified in the integrated user management, that the access permission to the file is available, and that the file contents are valid.

KEOS16216-E (C)

A target host name was not specified.

Description

The host name that forms the command target is not specified.

A message is displayed in the standard error output, and then the processing terminates.

Action

Specify the -t option and the -k host option or set up mngsvrutil.target_name and mngsvrutil.target_type=host in the mngsvrutilrc file.

KEOS16217-E (C)

The host aa....aa is unknown.

aa....aa: Specified host name

Description

The specified host is not defined in the management domain.

A message is displayed in the standard error output, and then the processing terminates.

Action

Confirm that the specified host is defined in the management domain.

KEOS16218-I (C)

File collection succeeded. (file = aa....aa)

aa....aa: Collected file name

Description

The file was collected.

A message is displayed in the standard error output, and then the processing terminates.

KEOS16219-W (C)

File collection succeeded. (file = aa....aa, details = bb....bb)

aa....aa: Collected file name

bb....bb: Detailed message

Description

The file was collected, but an error occurred.

A message is displayed in the standard error output, and then the processing terminates.

Action

Remove the cause of the error based on the details, and then re-execute the command, if required.

KEOS16220-E (C)

File collection has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to collect the file has failed.

A message is displayed in the standard error output, and then the processing terminates.

Action

Remove the cause of the error based on the details, and then re-execute the command.

KEOS16221-W (C)

Setup succeeded. (details = aa....aa)

aa....aa: Details

Description

An attempted setup was successful, but an error occurred.

A message is displayed in the standard error output, and then the processing terminates.

Action

Remove the cause of the error based on the details, and then re-execute the command, if required.

KEOS16222-E (C)

Setup failed. (details = aa....aa)

aa....aa: Details

Description

The setup has failed.

A message is displayed in the standard error output, and then the processing terminates.

Action

Remove the cause of the error based on the details, and then re-execute the command.

KEOS16223-E (C)

The specified logical server aa....aa is not J2EE.

aa....aa: Logical server specified by the argument

Description

The specified logical server is not a J2EE server.

A message is displayed in the standard error output, and then the processing terminates.

Action

Specify a J2EE server or a J2EE server cluster in the -t option, and then re-execute the command.

KEOS16224-E (C)

The J2EE application aa....aa is not registered.

aa....aa: J2EE application specified by the argument

Description

The specified J2EE application is not registered.

A message is displayed in the standard error output, and then the processing terminates.

Action

Specify the J2EE application registered in the argument, and then re-execute the command.

KEOS16225-E (C)

The resource adapter aa....aa is not registered.

aa....aa: Resource adapter specified by the argument

Description

The specified resource adapter is not registered.

A message is displayed in the standard error output, and then the processing terminates.

Action

Specify the resource adapter registered in the argument, and then re-execute the command.

KEOS16226-E (C)

aa....aa is running.

aa....aa: Name of the function that is being executed

Description

This operation cannot be executed since another operation is running.

A message is displayed in the standard error output, and then the processing terminates.

Action

Re-execute the operation after some time.

KEOS16227-E (C)

A CTM queue operation has failed. (details = aa....aa)

aa....aa: Details

Description

The CTM queue operation has failed.

A message is displayed in the standard error output, and then the processing terminates.

Action

Remove the cause of the error based on the details, and then re-execute the command.

KEOS16228-E (C)

The number of simultaneous execution threads is not specified in this Web application.

Description

The number of simultaneous execution threads is not specified in the Web application, so the application cannot be executed.

The processing terminates.

Action

Specify the number of simultaneous execution threads, redeploy the application, and then re-execute the process.

KEOS16229-E (C)

The simultaneous execution thread control function cannot be used when webserver.container.thread_control.enabled=false.

Description

The simultaneous execution thread control functionality cannot be executed as it is disabled.

The processing terminates.

Action

Enable the simultaneous execution thread control functionality, and then re-execute the command.

KEOS16230-E (C)

aa....aa was not found.

aa....aa: Context-root of the Web application

Description

The context-root of the Web application was not found.

The processing terminates.

Action

Check the context-root of the Web application, and then re-execute the command.

KEOS16231-E (C)

The maximum number of threads must be greater than the number of exclusive threads. (maximum number of threads = aa....aa, number of exclusive threads = bb....bb)

aa....aa: Maximum number of threads

bb....bb: Number of dedicated threads

Description

The value specified in the maximum number of threads is smaller than the number of exclusive threads.

The processing terminates.

Action

Specify the maximum number of threads so that the value is greater than the number of exclusive threads, and then re-execute the command.

KEOS16232-E (C)

The maximum number of threads is greater than the maximum number of simultaneously executable Web container threads. (maximum number of threads = aa....aa, maximum number of Web container threads = bb....bb)

aa....aa: Maximum number of threads

bb....bb: Number of concurrently executable Web container threads

Description

The maximum number of threads is greater than the number of concurrently executable Web container threads.

The processing will be terminated.

Action

Specify settings so that the maximum number of threads is no more than the number of concurrently executable Web container threads, and then re-execute the operation.

Check the following settings for the number of concurrently executable Web container threads:

When management portal is used

If the in-process HTTP server functionality is used to connect to the Web server, in the Communication and Thread Control Settings window, check Number of concurrently executable threads in Thread Control Settings

If connected to the Web server redirector (ajp13), in the Web Container Settings window, check Maximum number of threads in Connection with Web server

When the Smart Composer functionality is used

If true is specified in the webserver.connector.inprocess_http.enabled parameter, check the value set in the webserver.connector.inprocess_http.max_execute_threads parameter

If false is specified in the webserver.connector.inprocess_http.enabled parameter, check the value set in the webserver.connector.ajp13.max_threads parameter

KEOS16233-E (C)

The thread control is the Call condition error.(aa....aa)

aa....aa: Dynamic change value specified by the argument

Description

An attempt to change the settings has failed. A call condition error occurred.

A message is displayed in the standard error output, and then the processing terminates.

Action

Revise the call conditions.

KEOS16234-E (C)

The thread control is the Setup value range error.(aa....aa)

aa....aa: Dynamic change value specified by the argument

Description

An attempt to change the settings has failed. A setup value range error occurred.

A message is displayed in the standard error output, and then the processing terminates.

Action

Revise the range of the setup value.

KEOS16235-E (C)

The thread control is the Setup value validity error.(aa....aa)

aa....aa: Dynamic change value specified by the argument

Description

An attempt to change the settings has failed. A setup value validity error occurred.

A message is displayed in the standard error output, and then the processing terminates.

Action

Revise the validity of the setup value.

KEOS16239-E (C)

The operation which was not supported was required.

Description

An unsupported operation was required.

A message is displayed in the standard error output, and then the processing terminates.

Action

Confirm that the version of the Cosminexus Management Server for the host on which the target server is running is the same or later than the version of the Cosminexus Management Server to which you are connecting.

KEOS16240-E (C)

The J2EE Server cannot be accessed.

Description

The J2EE server cannot be accessed.

A message is displayed in the standard error output, and then the processing terminates.

Action

Confirm that the target J2EE server is running, and that the settings are specified so as to implement operation monitoring.

KEOS16241-E (C)

A command failed on the agent.

Description

The command error occurred in the Administration Agent.

A message is displayed in the standard error output, and then the processing terminates.

Action

See the Management Server Log, remove the failure, and then re-execute the command.

When performing core output of J2EE server or SFO server, a timeout may occur if the output information quantity is big. In such cases, this message is displayed, and then the command is terminated, however, it is continued until the core output process is completed, therefore, check whether the core file is output after some time.

KEOS16242-E (C)

The specified logical server aa....aa is not running.

Description

The logical server is not running.

A message is displayed in the standard error output, and then the processing terminates.

Action

Start the logical server then re-execute the command.

KEOS16243-E (C)

aa....aa is not installed.

aa....aa: Required package name

Description

The required package is not installed. A message is displayed in the standard error output, and then the processing terminates.

Action

Install the required package, and then re-execute the command.

KEOS16244-E (C)

The specified Java Beans resource aa....aa is not registered.

aa....aa: JavaBeans resource specified by the argument

Description

The specified JavaBeans resource is not registered. A message is displayed in the standard error output, and then the processing terminates.

Action

Specify the JavaBeans resource registered in the argument, and then re-execute the command.

KEOS16245-E (C)

The definition file is invalid. file name = aa....aa line number = bb....bb column number = cc....cc details = dd....dd

aa....aa: File name

bb....bb: Line number

cc....cc: Column number

dd....dd: Details

Description

An attempt to analyze the xml file has failed. A message is displayed in the standard error output, and then the processing terminates.

Action

Check the xml file specified in the argument, and then re-execute the command.

KEOS16246-E (C)

An attempt to add a logical server has failed. (details=aa....aa)

aa....aa: Details

Description

Addition of Logical Server failed. A message is displayed in the standard error output, and then the processing terminates.

Action

Check the xml file specified in the argument, and then re-execute the command.

KEOS16247-E (C)

A parser error occurred. (details = aa....aa)

aa....aa: Details

Description

A parser error occurred. A message is displayed in the standard error output, and then the processing terminates.

Action

Contact maintenance personnel.

KEOS16248-E (C)

An existing logical server name aa....aa was specified.

aa....aa: Specified logical server name

Description

Addition of Logical Server failed.

An existing logical server name was specified. A message is displayed in the standard error output, and then the processing terminates.

Action

Check the logical server name, and then re-execute the command.

KEOS16249-E (C)

Nonexistent host name aa....aa was specified.

aa....aa: Specified host name

Description

Addition of Logical Server failed.

A non-existing host name was specified. A message is displayed in the standard error output, and then the processing terminates.

Action

Check the host name, and then re-execute the command.

KEOS16250-E (C)

An attempt to delete a logical server failed because a nonexistent logical server name aa....aa was specified.

aa....aa: Specified logical server name

Description

Deletion of Logical Server failed.

A non-existing logical server name was specified. A message is displayed in the standard error output, and then the processing terminates.

Action

Check the logical server name, and then re-execute the command.

KEOS16251-E (C)

An attempt to delete a logical server failed because a specified logical server name aa....aa is not among the logical user servers.

aa....aa: Specified logical server name

Description

Deletion of Logical Server failed.

The logical server name not existing on the logical user server was specified. A message is displayed in the standard error output, and then the processing terminates.

Action

Check the logical server name, and then re-execute the command.

KEOS16252-E (C)

A connection to an external server cannot be established using aa....aa

aa....aa: Application Server product name

Description

A connection with an external server cannot be established using this product. A message is displayed in the standard error output, and then the processing terminates.

Action

Check the host name of the Management Server specified in the command argument.

KEOS16253-E (C)

An internal error occurred in the common library.(details = aa....aa)

aa....aa: Details

Description

An internal error occurred in the common library. If the problem is not resolved even after restarting and re-installing the server, contact maintenance personnel.

Action

If the problem is not resolved even after restarting and re-installing the server, contact maintenance personnel.

KEOS16254-E (C)

An attempt to add a logical server failed because the start command is not specified.

Description

Addition of Logical Server failed.

The start command is not specified. A message is displayed in the standard error output, and then the processing terminates.

Action

Add the start command, and then re-execute the process.

KEOS16255-E (C)

An attempt to add a logical server failed because the getProcessID command cannot be specified for a direct startup.

Description

Addition of Logical Server failed.

The getProcessID command cannot be specified for direct startup. A message is displayed in the standard error output, and then the processing terminates.

Action

Delete the getProcessID command, and then re-execute the process.

KEOS16256-E (C)

An attempt to add a logical server failed because the getProcessID command is not specified.

Description

Addition of Logical Server failed.

The getProcessID command is not specified. A message is displayed in the standard error output, and then the processing terminates.

Action

Add the getProcessID command, and then re-execute the process.

KEOS16257-E (C)

The host aa....aa cannot be converted to an IP address.

aa....aa: Host name

Description

The host name cannot be converted to the IP address. A message is displayed in the standard error output, and then the processing terminates.

Action

Add the getProcessID command, and re-execute the process.

KEOS16258-E (C)

The command (aa....aa) cannot be used with the product (bb....bb).

aa....aa: Specified subcommand

bb....bb: Product name

Description

The subcommand aa....aa cannot be used with the product bb....bb. The processing will be interrupted.

Action

No action needs to be taken.

KEOS17000-E (C/F)

Memory became insufficient.

Description

The memory cannot be secured.

The processing terminates.

The memory may be insufficient.

Action

Contact administrator of the host that executes the process, and then resolve the insufficient memory problem.

KEOS17001-E (C/F)

Java VM was not found.

Description

Java VM cannot be loaded.

The processing terminates.

The operating environment may have been damaged.

Action

If the problem is not resolved even after restarting and re-installing the server, contact maintenance personnel.

KEOS17002-E (C/F)

Java VM could not start.

Description

Java VM cannot be started.

The processing terminates.

The operating environment may have been damaged.

Action

If the problem is not resolved even after restarting and re-installing the server, contact maintenance personnel.

KEOS17003-E (C/F)

The specified class was not found:aa....aa

aa....aa: Class name

Description

The class specified in the aa....aa cannot be found.

The processing terminates.

The operating environment may have been damaged.

Action

If the problem is not resolved even after restarting and re-installing the server, contact maintenance personnel.

KEOS17004-E (C/F)

The specified method was not found: aa....aa.bb....bb

aa....aa: Class name

bb....bb: Method name

Description

The method indicated in the aa....aa and bb....bb cannot be found.

The processing terminates.

The operating environment may have been damaged.

Action

If the problem is not resolved even after restarting and re-installing the server, contact maintenance personnel.

KEOS17006-E (C/F)

An internal error occurred.

Description

An internal error occurred.

The processing terminates.

The operating environment may have been damaged.

Action

If the problem is not resolved even after restarting and re-installing the server, contact maintenance personnel.

KEOS18001-E (W)

A required item is not specified.

Description

A required item is not specified.

The operation will not be performed.

Action

Specify the required items.

KEOS18002-E (W)

A J2EE Application is not chosen.

Description

The J2EE application may not have been selected or the registration of the application may have been cancelled.

The operation will not be performed.

Action

Select the items for executing the operation.

KEOS18003-E (W)

Invalid request.

Description

Invalid request.

The operation will not be performed.

Action

Execute the request using the correct procedures.

KEOS18101-E (W)

The J2EE Application file is already registered. File=aa....aa

aa....aa: Specified J2EE application file

Description

The specified J2EE application file is already registered in the Management Server.

The J2EE application will not be registered.

Action

You cannot register identical J2EE application files or register J2EE application files at same time.

KEOS18102-E (W)

The J2EE Application is not registered.

Description

The J2EE application is not registered.

The operation will not be performed.

Action

Execute the operations for the registered J2EE application.

KEOS18103-E (W)

The file does not exist. File=aa....aa

aa....aa: Specified file

Description

The specified file does not exist.

The operation will not be performed.

Action

Confirm that the specified file exists.

KEOS18104-E (W)

The contents of the file are invalid. File=aa....aa

aa....aa: Specified file

Description

The contents of the specified file are invalid.

The operation will not be performed.

Action

Check the contents of the specified file.

KEOS18105-E (W)

The J2EE Application registration failed. File= aa....aa, Detail=bb....bb

aa....aa: Specified file

bb....bb: Detailed information

Description

An attempt to register the J2EE application has failed due to the cause displayed in the details.

The operation will not be performed.

Action

See the detailed information, and then remove the cause of the error.

If the detailed information specifies messages beginning with nnnn (n is a number), see 25.3 Messages when Errors Occur while Changing and Importing the Working Directory to take appropriate action.

KEOS18106-E (W)

Absolute path is required. File=aa....aa

aa....aa: Specified file

Description

The file needs to be specified with the absolute path.

The operation will not be performed.

Action

Specify the file with the absolute path of the host on which the Management Server is running.

KEOS18107-E (W)

"aa....aa" is running.

aa....aa: Name of the function that is being executed

Description

This operation cannot be executed since another operation is running.

The operation will not be performed.

Action

Terminate the other operations, and then execute the operation.

KEOS18108-E (W)

The specified J2EE application is not registered.

Description

The specified J2EE application is not registered.

The operation will not be performed.

The specified J2EE application might be unregistered.

Action

Re-select the logical server application management from the management portal, and then check that the applicable J2EE application is registered.

KEOS18109-E (W)

The specified registration directory is invalid.

Description

The specified registration directory is invalid.

The operation will not be performed.

In the registration directory, the absolute path of the host on which the Management Server is running needs to be specified. This specification cannot be omitted.

Action

Specify the registration directory correctly.

KEOS18110-E (W)

The J2EE application name is already registered.

Description

The specified J2EE application name is already registered in the Management Server. The J2EE application will not be registered.

Action

The same J2EE application name cannot be registered.

KEOS18111-E (W)

The specified import directory is invalid.

Description

The specified value of the import directory is invalid. The operation will not be performed.

Action

In the import directory, it is required to specify absolute path of the host on which Management Server is running. This path cannot be omitted.

KEOS18201-E (W)

The J2EE Application does not exist.

Description

The import history of the specified J2EE application does not exist in the relevant server.

The operation will not be performed.

A possible cause of the error is the addition of elements into the cluster after importing the J2EE application into the J2EE cluster.

Action

Re-import the J2EE application into the J2EE cluster, confirm that the J2EE application is imported into all the cluster elements, and then execute the operation.

KEOS18202-E (W)

The J2EE Server cannot be accessed.

Description

The J2EE server cannot be accessed.

Action

For the V8 mode, confirm that the J2EE server is running.

For the V7 compatible mode, confirm that the target J2EE server is running, and that the settings are specified so as to implement operation monitoring.

KEOS18300-I (W/F)

The J2EE Application was registered. ApplicationName=aa....aa, RegistrationTime=bb....bb, Description=cc....cc

aa....aa: Application name

bb....bb: Registration time

cc....cc: Description

Description

The J2EE application was registered.

The operation terminates.

KEOS18301-I (W/F)

The J2EE Application was unregistered. Success=[[aa....aa:bb....bb], Failure=[cc....cc:dd....dd]

aa....aa: Succeeded J2EE Application display name

bb....bb: Registration time

cc....cc: Failed J2EE Application display name

dd....dd: Registration time

Description

The J2EE application was unregistered.

The operation terminates.

The following could be details of the failed J2EE applications:

The J2EE application is imported into the logical J2EE server.

The operation is being performed.

The J2EE application is already unregistered.

KEOS18302-I (W)

The information of the registered J2EE Application was edited. Success=[aa....aa:bb....bb]

aa....aa: Succeeded J2EE Application display name

bb....bb: Registration time

Description

The information of the registered J2EE application was edited.

The operation terminates.

KEOS18404-I (W/F)

The operation to aa....aa will now start. Operation=bb....bb, Name=cc....cc

aa....aa: Target logical J2EE server name

bb....bb: Operation name

cc....cc: Target name

Description

The operation for the logical J2EE server is started.

KEOS18405-I (W/F)

The operation to aa....aa ended. Operation=bb....bb, Name=cc....cc

aa....aa: Target logical J2EE server name

bb....bb: Operation name

cc....cc: Target name

Description

The operation for the logical J2EE server is terminated.

Action

Of the J2EE servers forming the configuration elements, even if one operation fails, remove the cause of the error, and then re-execute the operation.

KEOS18406-I (W/F)

Operation was successful. J2EE Server name=aa....aa, Operation=bb....bb, Name=cc....cc

aa....aa: Target J2EE server name

bb....bb: Operation name

cc....cc: Target name

Description

Operation was successful.

The operation for the target J2EE server terminates.

KEOS18407-E (W/F)

Cannot connect with Administration Agent. Host name=aa....aa, J2EE Server name=bb....bb, Operation=cc....cc, Name=dd....dd

aa....aa: Target host name

bb....bb: Target J2EE server name

cc....cc: Operation name

dd....dd: Target name

Description

The operation has failed because connection to the administration agent cannot be established.

The operation terminates.

Action

Check the contents that are displayed in the details, resolve the problem, and then re-execute the operation:

Is the Administration Agent running on the operation host of the appropriate J2EE server?

Is the port number of the running Administration Agent the same as that of the port number of the Administration Agent defined in the host by configuration definition?

Can you communicate with the host defined in the configuration definition?

In the administration agent properties (adminagent.properties), is connection permitted to the operation host of the Cosminexus Management Server being accessed?

Does the Cosminexus version of the Management Server match with the Administration Agent?

When the Cosminexus editions of the Management Server and the Administration Agent are different, confirm that both the Cosminexus editions can be connected.

KEOS18408-E (W/F)

Command failed in the remote host. Host name=aa....aa, J2EE Server name=bb....bb, Operation=cc....cc, Name=dd....dd

aa....aa: Target host name

bb....bb: Target J2EE server name

cc....cc: Operation name

dd....dd: Target name

Description

The operation has failed because the command has failed on the remote host.

The operation terminates.

Action

Check the following contents and then re-execute the operation:

For an updated import, generation recovery, and deletion of an application

Check whether that J2EE application has been stopped.

For starting or stopping an application

Check whether that J2EE application is stopped or is running.

For importing a new application, or for importing a data source/ resource adapter

Check whether an application or data source/ resource adapter with the same display name has already been imported.

For starting or stopping a resource adapter

- Check whether that resource adapter is stopped or is running.

- Check whether all the J2EE applications using the resource adapter you want to stop, have been terminated.

For deleting a data source

Check whether all the J2EE applications using that data source have been terminated.

For deleting a resource adapter

- Check whether that resource adapter has been stopped.

- Check whether the J2EE server was restarted after terminating the running resource adapter.#

# To delete a running resource adapter, you must first stop the resource adapter, and then restart the J2EE server.

For the resource adapter connection test

Check whether the correct connection definition (configuration properties and runtime properties) is set for that resource adapter.

For setting up the resource adapter properties (Basic Settings and Edit HITACHI Connector property file)

Check whether that resource adapter has been stopped.

If the cause of the error cannot be eliminated using the above information, see the following log files on the host where that J2EE server is running, and then take action.

Note that the log file to be referenced depends on the value of the ejbserver.cui.logfile.compatible key in the system property file for server management commands (usrconf.properties). Note that the system property file for server management commands is stored in Cosminexus-installation-directory/CC/admin/usrconf/ (in UNIX), or Cosminexus-installation-directory\CC\admin\usrconf\ (in Windows). The log files to be referenced are as follows:

If the value of the ejbserver.cui.logfile.compatible property is false

Cosminexus-installation-directory/CC/admin/logs/cjmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjmessage?.log #1 (in Windows)

If the value of the ejbserver.cui.logfile.compatible property is true

The log file to be referenced differs based on the application or resource operations.

Importing a new application

Cosminexus-installation-directory/CC/admin/logs/cjimportappmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjimportappmessage?.log #1 (in Windows)

Updated import and generation recovery of an application

Cosminexus-installation-directory/CC/admin/logs/cjdeleteappmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjdeleteappmessage?.log #1 (in Windows)

Cosminexus-installation-directory/CC/admin/logs/cjimportappmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjimportappmessage?.log #1 (in Windows)

Deleting an application

Cosminexus-installation-directory/CC/admin/logs/cjdeleteappmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjdeleteappmessage?.log #1 (in Windows)

Starting an application

Cosminexus-installation-directory/CC/admin/logs/cjstartappmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjstartappmessage?.log #1 (in Windows)

Stopping an application

Cosminexus-installation-directory/CC/admin/logs/cjstopappmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjstopappmessage?.log #1 (in Windows)

Importing a data source

Cosminexus-installation-directory/CC/admin/logs/cjimportresmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjimportresmessage?.log #1 (in Windows)

Cosminexus-installation-directory/CC/admin/logs/cjsetrespropmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjsetrespropmessage?.log #1 (in Windows)

Deleting a data source

Cosminexus-installation-directory/CC/admin/logs/cjdeleteresmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjdeleteresmessage?.log #1 (in Windows)

Importing a resource adapter

Cosminexus-installation-directory/CC/admin/logs/cjimportresmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjimportresmessage?.log #1 (in Windows)

Cosminexus-installation-directory/CC/admin/logs/cjsetrespropmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjsetrespropmessage?.log #1 (in Windows)

Cosminexus-installation-directory/CC/admin/logs/cjdeployrarmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjdeployrarmessage?.log #1 (in Windows)#2

Cosminexus-installation-directory/CC/admin/logs/cjcopyresmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjcopyresmessage?.log #1 (in Windows)

Deleting a resource adapter

Cosminexus-installation-directory/CC/admin/logs/cjundeployrarmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjundeployrarmessage?.log #1 (in Windows)

Cosminexus-installation-directory/CC/admin/logs/cjdeleteresmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjdeleteresmessage?.log #1 (in Windows)

Starting a resource adapter

Cosminexus-installation-directory/CC/admin/logs/cjstartrarmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjstartrarmessage?.log #1 (in Windows)

Stopping a resource adapter

Cosminexus-installation-directory/CC/admin/logs/cjstoprarmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjstoprarmessage?.log #1 (in Windows)

Resource adapter connection test

Cosminexus-installation-directory/CC/admin/logs/cjtestresmessage?.log #1 (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjtestresmessage?.log #1 (in Windows)

Setting up resource adapter properties (Basic settings/ Edit HITACHI Connector property file)

See the log file to be used when the value of the ejbserver.cui.logfile.compatible property is false.

#1 ? indicates the number of log files.

#2 If KDJE37366-E is output in that log file, the resource adapter remains deployed. Restart the J2EE server and use the server management commands to un-deploy the resource adapter.

For details on the log files, see the manual uCosminexus Application Server Maintenance and Migration Guide.

KEOS18409-E (W)

The J2EE Application already exists. J2EE Server name=aa....aa, J2EE Application name=bb....bb

aa....aa: Target J2EE server name

bb....bb: Specified J2EE application

Description

The application with the same display name as the specified J2EE application is already imported.

The importing process is suspended.

Action

Re-execute the operation.

KEOS18410-E (W/F)

Data source operation failed. Host name = aa....aa, J2EE server name = bb....bb, Operation = cc....cc, Name=dd....dd

aa....aa: Target host name

bb....bb: Target J2EE server name

cc....cc: Operation name

dd....dd: Target name

Description

An attempt to set up the data source property file has failed, and an incomplete data source might have been imported.

The operation will be terminated.

Action

Implement the following:

Use the server management commands for Cosminexus Component Container and if the data source, for which an attempt to import into the applicable J2EE server was made, exists, delete the data source.

If an attempt to set up the data source property file has failed, see the following log files on the host where the applicable J2EE server is running, remove the cause of error, and then re-execute the operation:

Cosminexus-installation-directory/CC/admin/logs/cjsetrespropmessage?.log# (in UNIX) or Cosminexus-installation-directory\CC\admin\logs\cjsetrespropmessage?.log# (in Windows)

# "?" indicates the number of log files.

For details about the log files, see the manual uCosminexus Application Server Maintenance and Migration Guide.

KEOS18411-E (W)

Imported history does not exist. J2EE Server name=aa....aa, J2EE Application=bb....bb

aa....aa: Target J2EE server name

bb....bb: Target J2EE application

Description

Imported history does not exist.

The operation for the target J2EE server terminates.

Action

Re-execute the operation.

KEOS18412-E (W/F)

Operation failed. J2EE Server name=aa....aa, Operation=bb....bb, Name=cc....cc, Detail=dd....dd

aa....aa: Target J2EE server name

bb....bb: Operation name

cc....cc: Target name

dd....dd: Details

Description

Operation failed.

The operation for the target J2EE server terminates.

Action

Check the detailed information, remove the cause of the error, and then re-execute the operation.

Check the following details, when an unexpected exception occurs:

Are the prerequisite products installed properly?

If 1. is appropriate, is the Administration Agent of the host on which the relevant J2EE server runs, running?

If 2. is appropriate, are the import history managed by the Management Server and the import status of the J2EE resource or J2EE application in the relevant J2EE server synchronized?

If it is not synchronized, it needs to be synchronized using the server management commands of the Cosminexus Component Container. For details about how to use the server management commands, see Appendix L.1 Configuration and operation procedure of the sample execution environment by server management commands in the uCosminexus Application Server System Setup and Operation Guide.

If the cause of the error cannot be removed even after checking, re-operating and restarting the J2EE server, contact maintenance personnel.

KEOS18413-E (W)

Old version is not registered.

Description

Operation failed.

The generation recovery operation terminates.

Action

The generation recovery operation cannot be performed because the previous version is unregistered.

KEOS18414-W (W/F)

Some commands failed on the remote host. Host name = aa....aa, J2EE server name = bb....bb, operation = cc....cc, name = dd....dd, details = ee....ee

aa....aa: Target host name

bb....bb: Target J2EE server name

cc....cc: Operation name

dd....dd: Target name

ee....ee: Details

Description

Some commands failed on the remote host.

The processing continues.

Action

Check the details to remove the error, and then re-execute the commands as and when required.

If the message "The resource could not be deleted." is output in the details, the resource might be retained because the deletion of the resource failed. Use the server management command cjlistres (-type rar) to check whether the resource exists. To delete the resource, use the server management command cjdeleteres.

KEOS18500-E (W)

An unexpected error occurred. Detail=aa....aa

aa....aa: Exception information

Description

An unexpected event has occurred as displayed in the details.

The operation will not be performed.

Action

If the problem is not resolved even after re-operating, restarting and reinstalling, contact maintenance personnel.

KEOS18501-W (F)

Access denied. File=aa....aa

aa....aa: Setting file

Description

Access denied.

The settings file cannot be read.

Action

Check the settings file.

KEOS18502-E (W)

An unexpected error occurred.

Description

An unexpected event occurred.

The operation will not be performed.

Action

If the problem is not resolved even after re-operating, restarting and reinstalling, contact maintenance personnel.

KEOS18503-E (W)

The J2EE Server does not exists.

Description

The logical J2EE server is deleted from the management domain or the J2EE server is not defined in J2EE cluster.

The operation will not be performed.

Action

Check the details of the configuration definition, and then re-execute the operation.

KEOS18504-E (W)

The data source does not exist.

Description

The import log of the specified data source does not exist on the relevant server.

The operation will not be performed.

A possible cause of the error is the addition of elements to the cluster after importing the data source into the J2EE cluster.

Action

Re-import the data source into the J2EE cluster, confirm that the data source is imported into all the cluster elements, and then execute the operation.

KEOS18505-E (W)

The Resource Adapter does not exists.

Description

The import history of the specified resource adapter does not exist in the relevant server.

The operation will not be performed.

A possible cause of the error is the addition of elements to cluster after importing the resource adapter into the J2EE cluster.

Action

Re-import the resource adapter into the J2EE cluster, confirm that the resource adapter is imported in all the cluster elements, and then execute the operation.

KEOS18506-E (W)

The Application name is invalid. Name=aa....aa, File=bb....bb

aa....aa: Application name

bb....bb: File name

Description

The application name defined in the specified J2EE application file contains invalid characters.

The operation will not be performed.

Action

Check the contents of the J2EE application file.

KEOS18507-E (W)

The Resource name is invalid. Name=aa....aa, File=bb....bb

aa....aa: Resource name

bb....bb: File name

Description

The resource name defined in the specified file contains invalid characters.

The operation will not be performed.

Action

Check the file contents.

KEOS18508-E (W/F)

The specified resource adapter property cannot be obtained. Resource adapter name = aa....aa, details = bb....bb

aa....aa: Resource adapter name

bb....bb: Details

Description

An attempt to obtain the HITACHI Connector property file from the resource adapter failed.

The processing will be interrupted.

Action

See the details or the server management command message displayed on the window, remove the cause of the error, and then re-execute the operation.

The possible causes are as follows:

Cannot connect to the Administration Agent.

Cannot connect to the J2EE server.

The applicable resource adapter has been deleted.

The disk space on the host on which the Management Server or the host on which the Administration Agent is running has depleted.

KEOS18509-E (W/F)

The Basic Settings window for the resource adapters cannot be displayed. Resource adapter name = aa....aa, details = bb....bb

aa....aa: Resource adapter name

bb....bb: Details

Description

The basic settings window for resource adapters cannot be displayed because that resource adapter is not the DB Connector provided by Application Server.

The processing will be interrupted.

Action

Check whether the resource adapter is the following DB Connector provided by Application Server:

DBConnector_Oracle_CP.rar

DBConnector_HiRDB_Type4_CP.rar

DBConnector_SQLServer2005_CP.rar (prior to 0950)

DBConnector_SQLServer_CP.rar (0950 or later)

If you want to display or edit resource adapter properties other than those of the DB Connectors provided by Application Server, use the Edit HITACHI Connector Property File window of the resource adapter.

KEOS18510-I (W/F)

The resource adapter properties were set up successfully. Resource adapter name = aa....aa

aa....aa: Resource adapter name

Description

The resource adapter properties were set up successfully.

KEOS18511-E (W/F)

The resource adapter properties could not be set up. Resource adapter name = aa....aa, details = bb....bb

aa....aa: Resource adapter name

bb....bb: Details

Description

An attempt to set up the resource adapter properties failed.

The processing will be interrupted.

Action

See the details or the server management command message displayed on the window, remove the cause of the error, and then re-execute the operation.

The possible causes are as follows:

Cannot connect to the Administration Agent.

Cannot connect to the J2EE server.

The applicable resource adapter has been deleted.

The entered property is incorrect.

The disk space on the host on which the Management Server or the host on which the Administration Agent is running has depleted.

KEOS18512-I (W/F)

The J2EE application file was uploaded successfully. File name = aa....aa

aa....aa: File name

Description

The J2EE application file was uploaded successfully.

KEOS18513-E (W/F)

The request size (aa....aa) for upload exceeds the maximum request size (bb....bb).

aa....aa: Request size

bb....bb: Maximum request size

Description

The request size for upload exceeded the maximum request size.

The processing will be interrupted.

Action

Check the request size output in the message, and then review, and if necessary revise, the value of the com.cosminexus.mngsvr.upload_app.maxsize key in the mserver.properties file. If you change the value, restart the Management Server, and then re-execute the operation.

KEOS18514-E (W/F)

A J2EE application file that cannot be uploaded has been specified. File name = aa....aa

aa....aa: File name

Description

The specified J2EE application file cannot be uploaded because its extension is not ear or zip.

The processing will be interrupted.

Action

Check whether the extension of the specified file is ear or zip.

Specify a file with an ear or zip extension, and then re-execute the operation.

KEOS18515-E (W/F)

The J2EE application file does not exist, or the file size is 0 bytes. File name = aa....aa

aa....aa: File name

Description

The J2EE application file cannot be uploaded because the specified J2EE application file does not exist, or the file size is 0 bytes.

The processing will be interrupted.

Action

The possible causes are as follows:

The specified file does not exist.

The size of the specified file is 0 bytes.

The user does not have the permission to access the specified file.

Specify a J2EE application file for which the user has access permissions and the file size is greater than 0 bytes, and then re-execute the operation.

KEOS18516-E (W/F)

An attempt to upload the J2EE application file failed. File name = aa....aa, details = bb....bb

aa....aa: File name or null character

bb....bb: Details

Description

An attempt to upload the J2EE application file failed.

The processing will be interrupted.

Action

Check the details to remove the cause of the error, and then re-execute the operation.

The possible causes are as follows:

The disk space on the host on which the Management Server is running has depleted.

The upload directory does not exist or cannot be created.

The user does not have the permission to access the upload directory.

KEOS18601-E (W/F)

Invalid filter. Detail=aa....aa

aa....aa: Details

Description

A syntax error exists in the defined filter.

The operation will not be performed.

Action

Revise the filter definition contents, and then re-execute the operation.

KEOS18701-E (W)

aa....aa information cannot be acquired. bb....bb

aa....aa: Resource type

bb....bb: Detailed message

Description

The resource type information cannot be acquired. The operation will not be performed.

One of the following is output to the resource type:

Application

Resource adapter

One of the following is output to the detailed information:

Confirm that the J2EE server is running.

Confirm that one or more J2EE servers in the J2EE cluster are running.

Action

Take the following actions depending on the J2EE server status, and then re-execute the command:

If the status of the J2EE server is Stop, start the J2EE server.

If adminagent.j2ee.watch.level=1 is set in adminagent.properties (Administration Agent property file), the J2EE server functionality might not have started completely even after the J2EE server started and its status changed to Running. In this case, check the message log of the J2EE server, wait until the KDJE30028-I message is output, and then re-execute the command.

If the status of the J2EE server is Communication Error or Running, confirm that the Administration Agent is running and if the Administration Agent is not running, start the Administration Agent. If the problem is not resolved by the above actions, review and if necessary, revise the network status.

KEOS19000-E (W)

aa....aa is not specified.

aa....aa: Parameter name

Description

The mandatory parameters are not defined.

The update process will be interrupted.

Action

Enter the mandatory parameters, and then re-execute the process.

KEOS19001-E (W)

The value of aa....aa is not chosen.

aa....aa: Parameter name

Description

Select the displayed value.

The update process will be interrupted.

Action

Select the required value, and then re-execute the process.

KEOS19002-E (W)

The value specified to be aa....aa is too long. allowed length=bb....bb value length=cc....cc

aa....aa: Parameter name

bb....bb: Allowed length

cc....cc: Specified value length

Description

The parameter is too long.

The update process will be interrupted.

Action

Revise the length of the value, and then re-execute the process.

KEOS19003-E (W)

An error is in the form of a value of having been inputted into aa....aa. value=bb....bb

aa....aa: Parameter name

bb....bb: Inputted value

Description

The format of the value is invalid.

The update process will be interrupted.

Action

Revise the format of the value correctly, and then re-execute the process.

KEOS19004-E (W)

The value specified to be aa....aa is already used in the same host. Value=bb....bb

aa....aa: Parameter name

bb....bb: Inputted value

Description

The parameter values are duplicated.

The update process will be interrupted.

Action

Enter or select the required value, and then re-execute the process.

KEOS19005-E (W)

Specified handler class does not use handlerName.aa....aa

aa....aa: Handler class name

Description

The handler name cannot be specified in the specified handler class.

The update process will be interrupted.

Action

Re-execute the process without specifying the handler name.

KEOS19100-E (W/F)

Cannot connect Administration Agent. Server Type=aa....aa Logical Server Name=bb....bb

aa....aa: Logical server type

bb....bb: Logical server name (display name)

Description

An attempt to connect to the Administration Agent has failed.

The distribution process of the settings file will be interrupted.

Action

Check the contents that are displayed in the details, resolve the problem, and then re-execute the process.

Is the Administration Agent running in the operation host of the appropriate logical server?

Is the port number of the Administration Agent defined in the configuration definition of the Management Server the same as the port number of the Administration Agent running on the operation host of the logical server?

Is there any problem in the host name defined in the configuration definition of the Management Server (can you communicate correctly with the ping command)?

If adminagent.adapter.allowedHosts is specified in the property (adminagent.properties) of Administration Agent, is the Management Server host being accessed permissible?

Does the Cosminexus version of the Management Server match with the Administration Agent?

When the Cosminexus editions of the Management Server and the Administration Agent are different, confirm that both the Cosminexus editions can be connected.

KEOS19101-E (W/F)

Distribution of a configuration file the attempt failed. The server corresponding to a logical server does not exist. Server Type=aa....aa Logical Server Name=bb....bb

aa....aa: Logical server type

bb....bb: Logical server name (display name)

Description

An attempt to distribute the settings file has failed because the logical server does not exist.

The distribution process of the settings file will be interrupted.

The prerequisite products are not installed on the host on which the logical server is running or the server is not created (in the case of J2EE server, you need to create the server using the configuration definition functionality). Also, The operating environment may have been damaged.

Action

Check the pre-requisite products. If no problem exists in the pre-requisite products, restart and re-install the products.

If the problem is not resolved with the above actions, contact maintenance personnel

KEOS19102-E (W/F)

Distribution of a configuration file the attempt failed. Server Type=aa....aa Logical Server Name=bb....bb detail=cc....cc

aa....aa: Logical server type

bb....bb: Logical server name (display name)

cc....cc: Details

Description

An attempt to create the file in the host on which the logical server is running has failed because the required products may not have been installed, the memory may be insufficient, or an attempt to write to the file has failed.

The distribution process of the settings file will be interrupted.

Action

Confirm that the required products are installed. If there is no problem, see the detailed information, remove the cause of the error, and then re-execute the process.

KEOS19103-E (W/F)

Reading of a configuration file the attempt failed. The server corresponding to a logical server does not exist.

Description

An attempt to read the settings file has failed because the logical server does not exist.

The process of reading the settings file will be interrupted.

The prerequisite products are not installed in the host on which the logical server is running or the server is not created (in the case of J2EE server, you need to create the server using the configuration definition functionality). Also, The operating environment may have been damaged.

Action

Check the pre-requisite products. If no problem exists in the pre-requisite products, restart and re-install the products.

If the problem is not resolved with the above actions, contact maintenance personnel

KEOS19104-E (W/F)

Reading of a configuration file the attempt failed. detail=aa....aa

aa....aa: Details

Description

An attempt to read the file in the host on which the logical server is running has failed because the memory was insufficient or an attempt to write to the file has failed.

The process of reading the settings file will be interrupted.

Action

See the detail, remove the cause of the error, and then re-execute the process.

KEOS19105-Q (W)

A setup of aa....aa servers is read. Is it all right?

aa....aa: Logical server name

Description

The settings of the logical server being displayed can be read.

Yes and No buttons are displayed.

Action

Click Yes to overwrite the environment settings information of the relevant logical server. If you select the No button, you will return to the original screen.

KEOS19106-Q (W)

A setup of a server is read from a connection place host. Is it all right?

Description

The settings file can be read from the server of the host on which the logical server is running.

Yes and No buttons are displayed.

Action

Click Yes to overwrite the environment settings information of the relevant logical server. If you select the No button, you will return to the original screen.

KEOS19107-I (W/F)

Reflection of a setup was completed. Server Type=aa....aa Logical Server Name=bb....bb

aa....aa: Logical server type

bb....bb: Logical server name (display name)

Description

The settings file is updated from the server of the host on which the logical sever is running.

KEOS19108-E (W/F)

The setup failed. Server Type=aa....aa Logical Server Name=bb....bb Detail=cc....cc

aa....aa: Logical server type

bb....bb: Logical server name (display name)

cc....cc: Details

Description

The setup has failed. The setup process will be terminated.

Action

Confirm that the prerequisite products are properly installed on the host on which the logical server is running.

If the problem is not resolved with the above actions, contact maintenance personnel

KEOS19109-I (W/F)

The setup was completed. Server Type=aa....aa Logical Server Name=bb....bb

aa....aa: Logical server type

bb....bb: Logical server name (display name)

Description

The setup process is completed.

KEOS19110-E (W/F)

Communication with Administration Agent failed. Server Type=aa....aa Logical Server Name=bb....bb

aa....aa: Logical server type

bb....bb: Logical server name (display name)

Description

The setup has failed because an attempt to communicate with the Administration Agent has failed.

The setup process will be terminated.

Action

Confirm that the Administration Agent is running on the host that operates the logical server, and then re-execute the process.

Check the following details if the Administration Agent is running:

Does the Cosminexus version of the Management Server match with the Administration Agent?

If the Cosminexus editions in the Administration Agent and Management server are different, confirm that both the Cosminexus editions can be connected.

KEOS19111-W (W/F)

The applicable Performance Tracer is not defined in this management domain. Performance Tracer to use was not defined.

Description

The Performance Tracer having the identifier specified with the ejbserver.server.prf.PRFID key of the usrconf.properties file is not defined in the management domain. The ejbserver.server.prf.PRFID key is ignored, and the Performance Tracer is not defined.

Action

Configure the Performance Tracer on the host same as the J2EE server of the operation management domain, and then revise the settings.

KEOS19112-W (W/F)

The applicable Smart Agent is not defined in this management domain. Corresponding property key was defined as the system parameter of JVM.

Description

The Smart Agent having the port number specified using the vbroker.agent.port key of the usrconf.properties file is not defined in the management domain. The vbroker.agent.port key is defined in the system parameters of the Java VM.

Action

If necessary, configure the Smart Agent on the operation management domain, and then revise the settings. If the Smart Agent is configured outside the operation management domain, there will not be any problem.

KEOS19113-W (W/F)

The applicable Naming Service is not defined in this management domain. Corresponding property key was defined as the system parameter of JVM.

Description

The Naming Service having the port specified with the ejbserver.naming.port key is not defined in the management domain, for the host specified with the ejbserver.naming.host key of the usrconf.properties file. The ejbserver.naming.startupMode key, ejbserver.naming.host key, or ejbserver.naming.port key is defined in system parameters of the Java VM.

Action

If necessary, configure the Smart Agent on the operation management domain, and then revise the settings. If the applicable Smart Agent is configured outside the management domain, there will not be any problem.

KEOS19114-W (W/F)

The applicable CTM is not defined in this management domain. CTM to use was not defined.

Description

The CTM having the identifier specified with the ejbserver.ctm.CTMID key of the usrconf.properties file is not defined in the management domain. The ejbserver.ctm.CTMID key is ignored, and the CTM is not defined.

Action

Configure the CTM on the same host as the J2EE server of the operation management domain, and then revise the settings.

KEOS19115-W (W/F)

The applicable SFO Server is not defined in this management domain. Corresponding property key was defined as the system parameter of JVM.

Description

The SFO server corresponding to the IP address or host name, and port number specified with the webserver.sfo.sfo_server.server-definition-name-of-SFO-filter.naming key of the usrconf.properties file is not defined in the management domain. The webserver.sfo.sfo_servers key or webserver.sfo.sfo_server.server-definition-name-of-SFO-filter.naming key is defined in system parameters of the Java VM.

Action

If necessary, configure the SFO server on the operation management domain, and then revise the settings. If the applicable SFO server is configured outside the operation management domain, there will not be any problem.

KEOS19116-W (W/F)

The applicable Logical Server to naming service specified by round Robin reference is not defined in this management domain. Corresponding property key was defined as the system parameter of JVM.

Description

The logical server corresponding to the URL specified with the ejbserver.indi.namingservice.group.definition-name.providerurls key of the usrconf.properties file is not defined in the management domain. The ejbserver.indi.namingservice.group.list key or ejbserver.indi.namingservice.group.definition-name.providerurls key is defined in system parameters of the Java VM.

Action

If necessary, configure the CTM, Naming Service, or J2EE server on the operation management domain, and then revise the settings. If the applicable CTM, Naming Service, or J2EE server is configured outside the operation management domain, there will not be any problem.

KEOS19117-E (W/F)

The re-setup failed. Server Type=aa....aa Logical Server Name=bb....bb Detail=cc....cc

aa....aa: Logical server type

bb....bb: Logical server name

cc....cc: Details

Description

The re-setup is failed. The re-setup processing will be terminated.

Action

Contact maintenance personnel.

KEOS19118-I (W/F)

The re-setup was completed. Server Type=aa....aa Logical Server Name=bb....bb

aa....aa: Logical server type

bb....bb: Logical server name (display name)

Description

The re-setup was completed.

KEOS19119-W (W/F)

The specified value differs from the Administration Agent host name of the host set up by the logical server. aa....aa=bb....bb will be ignored.

aa....aa: Key name

bb....bb: Specified value

Description

The host set in one of the following keys is not the Administration Agent host name, so the key is ignored.

manager.mevent.sender.bind.host

mngagent.connector.host

vbroker.se.iiop_tp.host

The processing continues.

Action

As and when required, reset the Administration Agent host name of the host set up by the logical server to the displayed key, and then re-read.

KEOS19120-W (W/F)

The specified value differs from the host name of the host set up by the logical server. aa....aa=bb....bb will be ignored.

aa....aa: Key name

bb....bb: Specified value

Description

The host set in one of the following keys is not the host name of the host set up by the logical server, so the key is ignored.

webserver.connector.http.bind_host

webserver.connector.inprocess_http.bind_host

The processing continues.

Action

As and when required, reset the host name of the host set up by the logical server to the displayed key, and then re-read.

KEOS19121-W (W/F)

The specified value differs from the host name of the host set up by the logical server, or "localhost". aa....aa=bb....bb will be ignored.

aa....aa: Key name

bb....bb: Value

Description

The host set in one of the following keys is not the host name of the host set up by the logical server or localhost, so the key is ignored.

webserver.connector.ajp13.bind_host

ejbserver.rmi.naming.host

vbroker.se.iiop_tp.host

webserver.connector.nio_http.bind_host

The processing continues.

Action

As and when required, reset the host name of the host set up by the logical server or localhost to the displayed key, and then re-read.

KEOS19122-W (W/F)

All the specified values differ from the Administration Agent host name of the host set up by the logical server. aa....aa=bb....bb, and cc....cc=dd....dd will be ignored.

aa....aa: mngagent.connector.host

bb....bb: Value of mngagent.connector.host

cc....cc: vbroker.se.iiop_tp.host

dd....dd: Value of vbroker.se.iiop_tp.host

Description

The Administration Agent host name of the host set up by the logical server is not set up in any of the following keys, so the keys are ignored.

mngagent.connector.host

vbroker.se.iiop_tp.host

The processing continues.

Action

As and when required, reset the Administration Agent host name of the host set up by the logical server to one of the displayed keys, and then re-read.

KEOS19123-W (W/F)

In-process is specified in the naming service to be used.

Description

inprocess was set up because either the ejbserver.naming.startupMode key is not set up, or automatic was specified.

The processing continues.

Action

As and when required, specify manual in the ejbserver.naming.startupMode key, and then re-read.

KEOS19124-W (W/F)

The naming service to be used cannot be allocated. aa....aa=bb....bb will be ignored.

aa....aa: ejbserver.naming.startupMode

bb....bb: Value

Description

The value specified in the ejbserver.naming.startupMode key is not automatic, inprocess, or manual, so the value is ignored.

The processing continues.

Action

As and when required, reset automatic, inprocess, or manual in the ejbserver.naming.startupMode key, and then re-read.

KEOS19125-W (W/F)

The specified JVM invocation parameter cannot be set in the Java heap settings. aa....aa=bb....bb was set up in the extension invocation parameter.

aa....aa: Key name

bb....bb: Value

Description

The specified parameter was set up in the extension invocation parameter because the parameter cannot be set in the Java heap settings of JVM.

The processing continues.

Action

As and when required, reset the invocation parameter, and then re-read.

KEOS19126-W (W/F)

The performance tracer to be used is not defined. The performance tracer to be used was set to undefined.

Description

The ejbserver.server.prf.PRFID key is not defined in usrconf.properties. The performance tracer to be used was set to undefined.

The processing continues.

Action

Set up the ejbserver.server.prf.PRFID key, and then re-execute the operation.

KEOS19127-E (W/F)

An attempt to reference the configuration file failed. Logical server type=aa....aa, logical server name=bb....bb, details =cc....cc

aa....aa: Logical server type

bb....bb: Logical server name (display name)

cc....cc: Details

Description

An attempt to reference the configuration file failed.

The processing will be interrupted.

Action

Remove the cause of the error based on the details, and then re-execute the operation.

KEOS19128-W (W/F)

An attempt to validate the configuration file failed. Logical server type =aa....aa, logical server name=bb....bb, details =cc....cc

aa....aa: Logical server type

bb....bb: Logical server name (display name)

cc....cc: Details

Description

An attempt to validate the configuration file failed.

The processing continues.

Action

The contents of the distributed configuration file are invalid. Review, and if necessary revise, the settings, and then re-distribute the file.

KEOS19201-E (W)

The port number already used was specified. Used Port Number=aa....aa

aa....aa: Used port number

Description

The specified port number is already used in the identical logical servers. Specify a different port number.

The processing will now stop.

Action

Specify the port number that will not duplicate in the identical logical servers.

KEOS19202-W (W/F)

The same port number is specified within the same host. Used Port Number=aa....aa

aa....aa: Used port number

Description

The definition information is updated even if the same port number is specified in the identical hosts.

The processing continues.

Action

If required, change the port number so that it will not duplicate.

KEOS19203-E (W)

aa....aa Since naming service of a server was not defined or naming service was deleted, distribution of a configuration file the attempt failed.

aa....aa: Logical server name (display name)

Description

Distribution was not possible either because the Naming Service is not defined in the logical server being displayed or the corresponding Naming Service (logical server) was deleted.

The processing will now stop.

Action

Define the Naming Service in the logical server, and then re-execute the process.

KEOS19207-W (W/F)

Specified path is already used in the same host. Used path=aa....aa

aa....aa: Used path

Description

The definition information is updated though the same path is specified in the identical hosts.

The processing continues.

Action

If required, change the path so that it will not duplicate.

KEOS19208-W (W/F)

Specified logical server is already used in the same host. Used logical server=aa....aa

aa....aa: Used logical server

Description

The definition information is updated though the same logical server is specified in the identical hosts.

The processing continues.

Action

If required, change the logical server so that it will not duplicate.

KEOS19209-W (W/F)

Specified logical server is already used in the management domain. Used logical server=aa....aa

aa....aa: Used logical server

Description

The definition information is updated though the same logical server is specified in the management domain.

The processing continues.

Action

If required, change the logical server so that it will not duplicate.

KEOS19210-W (W/F)

Specified value is already used in the same host. Value=aa....aa

aa....aa: Used value

Description

The definition information is updated though the same value is specified in the management domain.

The processing continues.

Action

If required, change the value so that it will not duplicate.

KEOS19211-W (W/F)

Specified value is already used in the management domain. Value=aa....aa

aa....aa: Used value

Description

The definition information is updated though the same value is specified in the management domain.

The processing continues.

Action

If required, change the value so that it will not duplicate.

KEOS19212-E (W/F)

Specified host does not exist in the management domain. Host=aa....aa

aa....aa: Specified host

Description

The specified host cannot be specified because it was deleted from the management domain.

The processing continues.

Action

If required, define the host in the 'Configuration definition of the logical server', and then specify the host.

KEOS19213-W (W)

The value of aa....aa is not selected.

aa....aa: Parameter name

Description

The smart agent is not selected.

The processing continues.

Action

Select the required value, and then re-execute the process.

KEOS19214-W (W)

aa....aa does not match SmartAgent used by aa....aa.

aa....aa: Parameter name

Description

The selected smart agent does not match with the smart agent used on the related logical server.

The processing continues.

Action

Select the required value, and then re-execute the process.

KEOS19215-E (W)

Please specify a filter name.

Description

The contents cannot be added or applied because the URL pattern is not entered.

The processing will now stop.

Action

Enter the server definition name of an SFO filter.

KEOS19216-E (W)

Please specify another filter name. Logical Server Name=aa....aa same filter name=bb....bb

aa....aa: Logical server name (display name)

bb....bb: SFO filter server definition name

Description

The URL pattern cannot be defined because the specified URL pattern is the same.

The processing will now stop.

Action

Specify a different URL pattern.

KEOS19217-W (W/F)

If the storage destination if the status file is changed while unconcluded transactions remain, the consistency of the transactions might be lost. Logical Server Name=aa....aa

aa....aa: Logical server name (display name)

Description

The storage destination of the status file of in-process OTS is changed. If the unconcluded transactions remain in the previous status file, the consistency of transactions is lost.

The processing continues.

Action

Confirm that the unconcluded transactions are cancelled, and then perform 'Information distribution'. Move the status file being referenced presently to a new storage destination.

KEOS19218-W (W/F)

If the storage destination (spare) for the status file is changed while unconcluded transactions remain, the consistency of the transactions might be lost. Logical Server Name=aa....aa

aa....aa: Logical server name (display name)

Description

The (spare) storage destination of the status file of in-process OTS is changed. If the unconcluded transactions remain in the previous status file, the consistency of transactions is lost.

The processing continues.

Action

Confirm that the unconcluded transactions are cancelled, and then perform 'Information distribution'. Move the status file being referenced presently to a new storage destination.

KEOS19219-W (W/F)

If the fixed port for JTA recovery is changed while unconcluded transactions remain, those transactions might not be cancelled. Logical Server Name=aa....aa

aa....aa: Logical server name (display name)

Description

The fixed port of JTA recovery is changed. If the unconcluded transactions remain in the status file of the following J2EE servers, such transactions may not have been cancelled.

J2EE server for which you are trying to change the JTA recovery fixed port.

All the J2EE servers that are participating in the distributed transaction processing along with the above J2EE servers.

The processing continues.

Action

Confirm that the unconcluded transactions are cancelled, and then perform 'Information distribution'.

KEOS19220-W (W/F)

If fixing of the host for the EJB container is changed while unconcluded transactions remain, those transactions might not be cancelled. Also, if fixing of the host for the EJB container is changed while a status file exists for an in-process OTS, the J2EE server cannot be started by using that status file. Logical Server Name=aa....aa

aa....aa: Logical server name (display name)

Description

The fixing of the host of EJB container (fixed/not fixed/loop back address) is changed. If unconcluded transactions remain in the status file and database of the following J2EE server, such transactions may not have been cancelled.

J2EE server for which you are trying to change fixing of the port.

All the J2EE servers that are participating in the distributed transaction processing along with the above J2EE servers.

Database being accessed from the J2EE server for which you are trying to change the fixing of the host.

If the status file of in-process OTS created using the old settings remains, then the J2EE server cannot be started after change.

The processing continues.

Action

Confirm that the unconcluded transactions are cancelled, and then perform 'Information distribution'. Also, in the 'Transaction Settings', delete the directory specified in the 'Status file storage destination of in-process OTS', and then start the J2EE server.

KEOS19221-E (W)

Please specify a definition name.

Description

The contents cannot be added or applied because the definition name is not entered.

The processing will now stop.

Action

Enter the definition name.

KEOS19222-E (W)

Please specify a different definition name. Specified Definition Name = aa....aa

aa....aa: Definition name

Description

The specified definition name is same so it cannot be defined. Specify a different definition name.

The processing will now stop.

Action

Enter a different definition name.

KEOS19223-E (W)

A redirect URL and a file name (absolute path) cannot be set at the same time.

Description

When setting the redirect URL, the file name (absolute path) cannot be set. When setting the file name (absolute path), the redirect URL cannot be set.

The processing will now stop.

Action

Enter the redirect URL or the file name (absolute path).

KEOS19224-E (W)

Use an absolute path to specify the file name.

Description

Enter the file name with the absolute path.

The processing will now stop.

Action

Check whether the file name is entered and whether it is entered with the absolute path and, if necessary, revise it.

KEOS19225-E (W)

Please specify a redirect URL. Status=aa....aa

aa....aa: Status

Description

The redirect URL must be specified in the specified status.

The processing will now stop.

Action

Check the status, and then revise the redirect URL.

KEOS19226-E (W)

The redirect URL cannot be specified. Status=aa....aa

aa....aa: Status

Description

The redirect URL cannot be specified in the specified status.

The processing will be interrupted.

Action

Check the status, and then revise the redirect URL.

KEOS19227-E (W)

Please specify the file name (absolute path). Status=aa....aa

aa....aa: Status

Description

The file name (absolute path) must be entered in the specified status.

The processing will be interrupted.

Action

Check the status, and then revise the file name (absolute path).

KEOS19228-E (W)

Please specify a different request URL. Status=aa....aa

aa....aa: Status

Description

The combination of the specified status and request URL cannot be defined because it is already in use. Specify a different request URL or change the status.

The processing will now stop.

Action

Check the status, and then revise the request URL.

KEOS19229-E (W)

Please specify a format name.

Description

The contents cannot be added or applied because the format name is not entered.

The processing will now stop.

Action

Enter the format name.

KEOS19230-E (W)

Please specify a format form.

Description

The contents cannot be added or applied because the format form is not entered.

The processing will now stop.

Action

Enter the format form.

KEOS19231-E (W)

The value specified for the aa....aa parameter is invalid. Detail=bb....bb

aa....aa: Parameter name

bb....bb: Detailed message

Description

The specified parameter is invalid.

The processing will now stop.

Action

Revise the settings.

KEOS19232-W (W)

The in-process HTTP server functionality is not being used.

Description

The in-process HTTP server functionality is not used.

The processing continues.

Action

Confirm that the in-process HTTP server functionality is used.

KEOS19233-E (W)

Please specify a different format name. Specified Format Name=aa....aa

aa....aa: Format name

Description

The specified format name is same so it cannot be defined. Specify a different format name.

The processing will now stop.

Action

Enter a different format name.

KEOS19234-W (W)

The request cannot be redirected because the specified J2EE server or a member of the J2EE server cluster is using the in-process HTTP server. Logical Server Name=aa....aa

aa....aa: Logical J2EE server name (display name)

Description

The request cannot be redirected because the J2EE server or J2EE server cluster specified in the redirect destination use the in-process HTTP server functionality.

The processing continues.

Action

Specify a J2EE server or J2EE server cluster that does not use the in-process HTTP server functionality.

KEOS19235-E (W)

Please specify a request URL.

Description

The contents cannot be added or applied because the request URL is not entered. The processing will now stop.

Action

Enter the request URL.

KEOS19236-E (W)

You cannot define multiple variables that have the same name. Variable Name=aa....aa

aa....aa: Multiple variable name

Description

The definition of multiple variables with the same name must be case sensitive.

The processing will now stop.

Action

Specify a variable name so that it will not duplicate.

KEOS19237-W (W)

The default value is applied to the server ID appended to the session ID. Logical Server Name=aa....aa

aa....aa: Logical J2EE server name (display name)

Description

The server ID appended to the session ID is not specified. When the server ID is omitted, the default value of the Cosminexus Component Container is used, but if the default value is sent to the client, it may contain sensitive information that may not be recommended for security purpose, therefore, we recommend that you specify the server ID explicitly.

Action

In the server ID, explicitly specify a value that is unique and does not include any machine specific information such as IP address.

KEOS19238-W (W)

The default value is applied to the server ID appended to the HTTP response. Logical Server Name=aa....aa

aa....aa: Logical J2EE server name (display name)

Description

The server ID appended to the HTTP response is not specified. When the server ID is omitted, the default value of the Cosminexus Component Container is used, but if the default value is sent to the client, it may contain sensitive information that may not be recommended for security purpose, therefore, we recommend that you specify the server ID explicitly.

Action

In the server ID, explicitly specify a value that is unique and does not include any machine specific information such as IP address.

KEOS19239-W (W)

The reload function cannot be used because the operation mode of the J2EE server is now in basic mode.

Description

The reload functionality by update detection cannot be used because the operation mode of the J2EE server is the basic mode. The processing continues.

Action

When using the reload functionality by update detection, specify a mode other than basic mode as an operation mode.

KEOS19240-W (W)

When all local calls are selected for the call method of the J2EE application, EJB-JAR, the servlet, and JSP reloads cannot be used in the applicable range of the reload function.

Description

If you select the invocation method of J2EE application as [All local invocation], [Reload EJB-JAR, servlets, and JSPs] cannot be used in the scope of the reload functionality.

The processing continues.

Action

When using [Reload EJB-JAR, servlets, and JSPs] in the scope of the reload functionality, specify any method other than [All local invocation] as the J2EE application invocation method.

KEOS19241-E (W)

The same maximum value cannot be specified for components in the same J2EE server cluster. J2EE Server cluster name=aa....aa

aa....aa: Logical J2EE server cluster name (display name)

Description

You cannot specify the same upper-limit value for the components of the J2EE server cluster. The processing will now stop.

Action

Specify an upper-limit value that is different from the rest for the components of the J2EE server cluster.

KEOS19242-E (W)

When setting POST data distribution as the worker type, you must specify the maximum value. J2EE Server name=aa....aa

aa....aa: Logical J2EE server name (display name)

Description

When the worker type is POST data distribution, specify the upper-limit value of the POST data size. The processing will now stop.

Action

If this J2EE server is not set up as the default worker, always specify the upper-limit value of the POST data size. Note that even when the J2EE server is set up as the default worker, if the J2EE server is the only component of the J2EE server cluster, always specify the upper-limit value of the POST data size.

KEOS19243-W (W/F)

aa....aa bytes have been specified for bb....bb. Make sure it is the intended value.

aa....aa: Parameter name

bb....bb: Specified value

Description

If the character (k, m, or g), indicating a unit, is not included in the specified value bb....bb of aa....aa, the unit of the specified value is considered to be a byte. A character indicating a unit is not required; however, we recommend that you specify the character. The specified value becomes enabled, and the processing continues.

Action

Check if you can use byte as a unit for the specified value.

To specify a unit other than byte, include a character indicating the unit (k, m, or g) in the value, and then specify the value again.

KEOS19244-W (W/F)

The specified JVM invocation parameter cannot be set up in the Explicit Memory Management settings. aa....aa=bb....bb was set up in the extension invocation parameter.

aa....aa: Key name

bb....bb: Value

Description

The specified parameter was set up in the extension invocation parameter because it cannot be set up in the Explicit Memory Management settings of JVM.

The processing continues.

Action

If necessary, reset the invocation parameter, and then re-read.

KEOS19245-W (W/F)

The specified JVM invocation parameter cannot be set up in the user-extended performance analysis trace settings. aa....aa=bb....bb was set up in the extension invocation parameter.

aa....aa: Key name

bb....bb: value

Description

The specified parameter was set up in the extension invocation parameter because it cannot be set up in the user-extended performance analysis trace settings of JVM.

The processing continues.

Action

If necessary, reset the invocation parameter, and then re-read.

KEOS19246-E (W)

The specified value of http/ajp13 field is incorrect.

Description

The specification of http/ajp13 is invalid.

In-process HTTP and ajp13 cannot be specified in any mode other than V9 compatibility mode.

NIO HTTP cannot be specified in V9 compatibility mode.

The processing will be interrupted.

Action

Correct the value according to the compatibility mode, and then re-execute the command.

KEOS19300-E (W)

An attempt to save environment settings information has failed. Detail=aa....aa

aa....aa: Details

Description

An attempt to save the environment settings information in the file has failed.

The processing will now stop.

Action

Remove the cause of the error, and then click the Apply button once again.

KEOS19301-I (W)

Environment settings information has been saved.

Description

An attempt to save the environment settings information was successful.

KEOS19999-E (W/F)

An internal error occurred. Detail=aa....aa

aa....aa: Details

Description

An internal error occurred.

The processing will now stop.

Action

If the cause of the error cannot be removed even after restarting the Management Server, contact maintenance personnel.

13.4 Messages from KEOS20000 to KEOS29999

This section describes the messages from KEOS20000 to KEOS29999 output when Cosminexus Manager is used for system setup, operation, and maintenance.

KEOS20001-I (W/F)

The start/stop settings of aa....aa(bb....bb) was changed.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The start and stop settings were changed.

KEOS20002-E (W)

The start/stop settings contain an error. detail=aa....aa

aa....aa: Details

Description

An invalid value was specified in the start or stop settings.

The update process will not be performed.

Action

Enter a correct settings value.

KEOS20003-E (W/F)

The start/stop cannot be execute because the status of aa....aa(bb....bb)is cc....cc.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Status

Description

The logical server cannot be started or stopped, because a process is being executed.

The logical server will not be started or stopped.

Action

Perform the process after the logical server becomes executable.

Re-confirm the following details if the administration agent is running but the status does not change from communication failure even after sometime:

Does the application server version of the Administration Agent match with the Management Server?

If the application server editions of the Administration Agent and the Management Server are different, confirm that these editions can be connectable each other.

KEOS20004-I (W/F)

cc....cc request of aa....aa(bb....bb) was accepted.

aa....aa: Logical server name (management domain name or host name)

bb....bb: Logical server type (management domain or host)

cc....cc: Start/ Stop/ Batch Start/ Batch Stop/ Batch Restart

Description

A request was issued to the Management Agent.

KEOS20005-E (W/F)

The start of aa....aa(bb....bb) failed. detail=cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

An attempt to start the logical server has failed.

The startup process will be interrupted after starting the logical server in the same startup order.

Action

Confirm that the settings information is distributed. See the detailed information and the Management Agent log, remove the errors, and then re-execute the process.

For details on how to collect the material and investigate cause of the error, see 6.4.2 Troubleshooting during operations in the uCosminexus Application Server Maintenance and Migration Guide.

KEOS20007-I (W/F)

aa....aa(bb....bb) has started.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The logical server starts.

KEOS20008-E (W/F)

The collective start canceled.

Description

Collective startup was suspended.

Action

See the detailed information and the Management Agent log generated so far, remove the errors, and then re-execute the process.

KEOS20009-I (W/F)

The collective start has started.

Description

The collective start has started.

KEOS20010-I (W/F)

The collective start ended.

Description

The collective start process ends.

KEOS20011-E (W/F)

The stop of aa....aa(bb....bb) failed. detail= cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

An attempt to stop the logical server has failed.

The processing continues if there are other logical servers to be stopped.

Action

See the detailed information and the Management Agent log, remove the errors, and then re-execute the process.

For details on how to collect the material and investigate the cause, see 4.3.1(2) Acquiring the log of Administration agent, Management agent, and Management Server in the uCosminexus Application Server Maintenance and Migration Guide.

If the detailed information indicates that the termination monitoring time has expired, confirm that the specified operation check interval for the logical server is not greater than the termination check interval.

KEOS20012-I (W/F)

aa....aa(bb....bb) was stopped.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The logical server was stopped.

KEOS20014-I (W/F)

The collective stop has started.

Description

The collective stop has started.

KEOS20015-I (W/F)

The collective stop ended.

Description

The collective start process ends.

KEOS20016-I (W/F)

The collective restart has started.

Description

The collective restart has started.

KEOS20017-I (W/F)

The collective restart ended.

Description

The collective restart process ends.

KEOS20018-E (W/F)

The logical server for processing does not exist.

Description

There are no logical servers to be collectively processed in the specified domain, host, and cluster.

The collective processing will not be performed.

Action

The possible causes are as follows: Take the necessary action depending on the cause.

Logical server is not created in the specified domain, host, and cluster.

Create the logical server.

The startup order is not specified in the logical server, so the server is not out of scope of collective processing.

Specify the startup order.

KEOS20019-E (W)

The starting order of aa....aa(bb....bb) contains an error. input=cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Inputted value

Description

An invalid value is entered in the startup order.

The startup order will not be updated.

Action

Enter a numeric value from 0 to 99 in the startup order or do not enter anything (do not specify the startup order).

KEOS20020-E (W)

The starting order of aa....aa(bb....bb) is before the starting order of cc....cc(dd....dd) to use.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Logical server name

aa....aa: Logical server type

Description

The startup order of dependent logical servers is invalid.

The startup order will not be updated.

Action

Specify the startup order of the J2EE servers after the startup order of the naming services to be used.

KEOS20021-E (W/F)

The stating order could not be changed. detail=aa....aa

aa....aa: Details

Description

The stating order could not be changed.

The startup order will not be updated.

Action

See the detailed information, remove the error, and then re-execute the process.

KEOS20022-I (W/F)

The stating order has changed.

Description

The stating order has changed.

KEOS20023-E (W/F)

The starting order of cc....cc(dd....dd) which aa....aa(bb....bb) is used for is invalid.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Logical server name

aa....aa: Logical server type

Description

The startup order is invalid.

The startup order will not be updated.

The startup order is not specified in the applicable logical server, but is specified in the logical server that uses the applicable logical server.

Action

Revise the startup order.

KEOS20024-E (W/F)

The collective start failed. detail=aa....aa

aa....aa: Details

Description

The collective start failed.

The collective startup will not be performed.

Action

See the detailed information, remove the cause of the error, and then re-execute the process.

KEOS20025-E (W/F)

The collective stop failed. detail=aa....aa

aa....aa: Details

Description

The collective stop failed.

The collective termination will not be performed.

Action

See the detailed information, remove the cause of the error, and then re-execute the process.

KEOS20026-E (W/F)

The collective restart failed. detail=aa....aa

aa....aa: Details

Description

The collective restart failed.

The collective restart will not be performed.

Action

See the detailed information, remove the cause of the error, and then re-execute the process.

KEOS20027-E (W/F)

The auto restart of aa....aa (bb....bb) failed. detail=cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

An attempted auto restart has failed.

The auto restart will not be performed.

Action

See the detailed information, remove the error, and then start from the start or stop screen.

KEOS20028-E (W/F)

The automatic restart count specified in aa....aa (bb....bb) has exceeded. Restart count =cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Restart count

Description

The specified automatic restart count has exceeded. Automatic restart will end.

Action

Remove the causes of the error output to the logical server, and then start the logical server.

KEOS20029-E (F)

The thread for the watcher of a force stop could not be created. detail=aa....aa

aa....aa: Details

Description

The thread for the watcher of a force stop could not be created.

The forced termination process will not be performed.

Action

See the detailed information, remove the error, and then restart the Management Server.

KEOS20030-E (W/F)

aa....aa(bb....bb) cannot start because invalid settings. detail=cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

The logical servers cannot be started or stopped individually.

The starting or stopping process will not be performed.

Action

See the detailed information, remove the cause of the error, and then re-execute the process.

KEOS20031-E (W/F)

aa....aa(bb....bb) stopped abnormally.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The logical server has abended.

Action

Run auto restart if auto restart is specified.

For details on how to collect the material and investigate the cause of the error, see 6.4.2 Troubleshooting during operations in the uCosminexus Application Server Maintenance and Migration Guide.

KEOS20032-I (W/F)

aa....aa(bb....bb) was stopped automatically.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The logical server was stopped automatically.

KEOS20033-E (W/F)

The auto stop of aa....aa(bb....bb) failed. detail=cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

An attempt to stop the logical server automatically has failed.

Automatic stopping of the logical server will not be performed.

The process exists in the logical server, but does not operate normally.

Action

See the detailed information, remove the error, and then stop the server.

If the detailed information indicates that the termination monitoring time has expired, confirm that the specified operation check interval for the logical server is not greater than the termination check interval.

KEOS20034-I (W/F)

The auto stop of aa....aa(bb....bb) has started.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The auto stop process starts.

KEOS20035-I (W/F)

The auto stop of aa....aa(bb....bb) ended.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The auto stop process ends.

KEOS20036-I (W/F)

The auto restart of aa....aa(bb....bb) has started.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The auto restart process starts.

KEOS20037-I (W/F)

The auto restart of aa....aa(bb....bb) ended.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The auto restart process ends.

KEOS20040-E (W/F)

The force stop of aa....aa(bb....bb) failed. detail=cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

An attempt to stop the logical server forcibly has failed.

The forced termination will not be performed.

Action

See the detailed information, remove the error, and then terminate the process manually.

If the detailed information indicates that the termination monitoring time has expired, confirm that the specified operation check interval for the logical server is not greater than the termination check interval.

KEOS20042-I (W/F)

cc....cc status of aa....aa(bb....bb) was received.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Status

Description

Received the status of the logical server.

KEOS20050-E (W/F)

The start/stop settings of aa....aa(bb....bb) could not be changed. detail=cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

An attempt to update the start or stop settings of the logical server has failed.

The update process will not be performed.

Action

See the detailed information, remove the error, and then re-execute the termination process.

KEOS20051-I (W/F)

The snapshot log of aa....aa(bb....bb) was collected. file name=cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: snapshot log file name

Description

The snapshot log was acquired.

KEOS20052-E (W/F)

The snapshot log of aa....aa(bb....bb) could not be collected. detail=cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

An error occurred while the snapshot log was being collected.

Action

See the details, remove the cause of the error, and then re-execute the processing.

If "A timeout occurred while collecting the snapshot log." is displayed in the details, take action using one of the following:

Collect the snapshot log manually from mngsvrutil command and management portal.

Increase the value of the com.cosminexus.mngsvr.snapshot.auto_collect.timeout key in the Management Server configuration file (mserver.properties).

Review, and if necessary revise, the snapshot log collection definition file (snapshotlog.conf and snapshotlog.2.conf).

KEOS20053-I (W/F)

The snapshot log of aa....aa(bb....bb) was not collected because the target file does not exist.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The snapshot log was not collected because there were no target files.

KEOS20054-I (W/F)

aa....aa(bb....bb) is starting.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The logical server will start.

KEOS20055-I (W/F)

aa....aa(bb....bb) is stopping.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The logical server will terminate.

KEOS20056-I (W/F)

aa....aa(bb....bb) is stopping forcefully.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The logical server will forcibly be stopped.

KEOS20057-I (W/F)

The snapshot log of aa....aa(bb....bb) is collecting.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The snapshot log will be collected.

KEOS20058-I (W/F)

The auto restart of aa....aa(bb....bb) and the Logical Server cc....cc premised has started.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: List of logical server names

Description

The auto restart process starts.

KEOS20059-I (W/F)

The auto restart of aa....aa(bb....bb) and the Logical Server cc....cc premised ended.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: List of logical server names

Description

The auto restart ended.

KEOS20060-W (W/F)

The logical server specified for use in the environment configuration is not set up as a prerequisite logical server.

Description

The logical server specified for using the environment configuration is not set up as a prerequisite logical server.

The processing continues.

KEOS20061-I (W/F)

The auto stop of aa....aa (bb....bb) and the logical server cc....cc premised has started.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: List of logical server names

Description

The automatic stop process starts.

KEOS20062-I (W/F)

The auto stop of aa....aa(bb....bb) and the Logical Server cc....cc premised ended.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: List of logical server names

Description

The auto stop ended.

KEOS20063-I (W/F)

The auto stop of the Logical Server cc....cc premised on aa....aa(bb....bb) has started.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: List of logical server names

Description

The auto stop process starts.

KEOS20064-I (W/F)

The auto stop of the Logical Server cc....cc premised on aa....aa(bb....bb) ended.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: List of logical server names

Description

The auto stop ended.

KEOS20065-E (W)

The starting order of aa....aa(bb....bb) is not set up before other logical servers.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The startup order of the logical servers is invalid.

The startup order will not be updated.

Action

Specify the startup order of the applicable logical servers before the startup order of other logical servers.

KEOS20067-I (W/F)

The snapshot log of aa....aa(bb....bb) was interrupted.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The process of collecting the snapshot log was interrupted.

KEOS20068-E (W/F)

The snapshot log of aa....aa(bb....bb) could not be interrupted. detail=cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

The collection process of the snapshot log cannot be interrupted.

The collection process of the snapshot log continues.

Action

See the detailed information, remove the error, and then re-execute the process.

KEOS20069-I (W/F)

The command at the time of abnormal end detection for aa....aa(bb....bb) is starting.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The failure detection command of the logical server starts.

KEOS20070-I (W/F)

The command at the time of abnormal end detection for aa....aa(bb....bb)is complete.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The failure detection command of the logical server has finished.

KEOS20071-E (W/F)

The command at the time of abnormal end detection for aa....aa(bb....bb) failed. detail=cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

An attempt to execute the failure detection command of the logical server has failed.

The failure detection command will not run.

Action

See the detailed information, remove the error, and then re-execute the process.

KEOS20072-I (W/F)

The command at the time of abnormal end detection for aa....aa(bb....bb) is not defined.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The failure detection command is not defined.

The failure detection command will not run.

KEOS20073-I (W/F)

aa....aa(bb....bb) is stopping gracefully.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The planned termination process was started.

KEOS20074-E (W/F)

The graceful stop of aa....aa(bb....bb) failed. detail=cc....cc

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

An attempted planned termination has failed.

Action

See the detailed information and the Management Agent log, remove the error, and then re-execute the process.

If the detailed information indicates that the termination monitoring time has expired, confirm that the specified operation check interval for the logical server is not greater than the termination check interval.

KEOS20075-I (W/F)

The snapshot log(cc....cc) of aa....aa(bb....bb) is collecting.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: snapshot log collection target

Description

The snapshot log will be acquired.

KEOS20076-I (W/F)

The snapshot log(cc....cc) of aa....aa(bb....bb) was collected. file name=dd....dd

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: snapshot log collection target

dd....dd: snapshot log file name

Description

The snapshot log was acquired.

KEOS20077-I (W/F)

The snapshot log(cc....cc) of aa....aa(bb....bb) was not collected because the target file does not exist.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: snapshot log collection target

Description

The snapshot log was not collected because there were no target files.

KEOS20078-E (W/F)

The snapshot log(cc....cc) of aa....aa(bb....bb) could not be collected. detail=dd....dd

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: snapshot log collection target

dd....dd: Details

Description

The snapshot log cannot be acquired.

Action

See the detailed information, remove the error, and then re-execute the process.

KEOS20079-W (W/F)

The snapshot log(cc....cc) of aa....aa(bb....bb) was collected. file name=dd....dd detail=ee....ee

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: snapshot log collection target

dd....dd: snapshot log file name

ee....ee: Detailed information

Description

The snapshot log was collected, but an error occurred.

Action

See the detailed information, remove the error, and then re-execute the process.

KEOS20080-I (F)

The environment variable for starting aa....aa(bb....bb) was get. cc....cc=dd....dd

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Environment variable

dd....dd: Environment variable value

Description

The environment variable information used during logical server startup was acquired.

KEOS20100-E (W/F)

An unexpected exception occurred. detail=aa....aa

aa....aa: Details

Description

An unexpected exception occurred.

The specified request will not be performed.

Action

See the detailed information, remove the error, and then re-execute the termination process.

If the error recurs and it cannot be resolved even after restarting, contact maintenance personnel.

KEOS20501-I (F)

The watcher of aa....aa(bb....bb) was started.

aa....aa: Logical server name

bb....bb: Logical server type

Description

Monitoring the logical server was started.

KEOS20502-I (F)

The watcher of aa....aa(bb....bb) was stopped.

aa....aa: Logical server name

bb....bb: Logical server type

Description

Monitoring the logical server was stopped.

KEOS20505-E (F)

Administration Agent on cc....cc(Host) could not be connected in aa....aa(bb....bb) processing.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Host name

Description

A connection cannot be established with the Administration Agent.

The start and stop process will be interrupted.

Action

Start and stop once again from the start/stop screen of the logical server. If the same phenomenon occurs even if started and stopped once again, check whether the Administration Agent is running in the operation host of the applicable logical server.

Check the following details if the Administration Agent is running:

Does the application server version of the Administration Agent match with the Management Server?

If the application server editions of the Administration Agent and the Management Server are different, confirm that these editions can be connectable each other.

KEOS20506-E (F)

The host name and the port number of aa....aa(bb....bb) could not be acquired.

aa....aa: Logical server name

bb....bb: Logical server type

Description

An attempt to acquire the host name and the port number has failed.

The monitoring process will be interrupted.

Action

Confirm whether the following files are deleted or whether the file permissions are changed:

In Windows

Cosminexus-HTTP-Server-installation-directory\conf\httpsd.conf

In UNIX

/opt/hitachi/httpsd/conf/httpsd.conf

KEOS20507-E (F)

The process ID of aa....aa(bb....bb)could not be acquired.

aa....aa: Logical server name

bb....bb: Logical server type

Description

An attempt to acquire the process ID has failed.

The monitoring process will be interrupted.

A reason may be that the service account of the Administration Agent is being changed.

Action

Change the service account of the Administration Agent to system account, restart the Administration Agent, and then restart the logical server. When the error cannot be removed by this action, restart the logical server.

If the same phenomenon occurs even after the logical server is restarted, contact maintenance personnel.

KEOS20508-E (F)

The period of watching aa....aa(bb....bb)start up was expired.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The start monitoring time was exceeded.

The logical server will terminate.

Action

Specify the start monitoring time of the logical server according to the environment.

In the logical J2EE server or the logical SFO server, a possible cause might be that the naming service to which Management Server will connect is not running. Confirm that the naming service set up in the Naming Service Connection Settings screen of the management portal is running.

KEOS20509-I (F)

The process ID(cc....cc) of aa....aa(bb....bb) could be acquired.

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Process ID

Description

The process ID was acquired successfully.

KEOS20510-E (F)

Cannot open file: aa....aa

aa....aa: File name

Description

An attempt to open the file has failed.

The monitoring process will be interrupted.

Action

Check the operating environment and the settings such as file name and permissions.

KEOS20511-E (F)

A hang-up was detected during watch of aa....aa(bb....bb)

aa....aa: Logical server name

bb....bb: Logical server type

Description

The logical server was found to have hung up.

The errors in the logical server will be reported to the Management Server.

Action

Extract the data through actions such as collection of snapshot log, and then investigate the causes that led to the hang up.

KEOS21000-I (F)

The administration agent has started.

Description

The administration agent has started.

KEOS21001-I (F)

The administration agent has finished.

Description

The administration agent has finished.

KEOS21002-E (F)

An attempt to start the administration agent has failed.

Description

An attempt to start the Administration Agent has failed.

Action

Check the operating environment and the settings.

KEOS21003-E (F)

An attempt to stop the administration agent has failed.

Description

An attempt to stop the administration agent has failed.

Action

Check the operating environment and the settings.

KEOS21004-E (F)

An attempt to open the file has failed. (file name = aa....aa)

aa....aa: File name

Description

An attempt to open the file has failed.

The operations of the Administration Agent will continue if possible, and will terminate if operations cannot be continued.

Action

Check the operating environment and the settings such as file name and permissions.

KEOS21005-E (F)

The port number is invalid. (port number = aa....aa)

aa....aa: Port number

Description

An invalid value is set in the port number.

The processing will be interrupted.

Action

Check the operating environment and the settings.

KEOS21006-E (F)

A port number is already in use. (port number = aa....aa)

aa....aa: Port number

Description

The specified port number is already being used.

The processing will be interrupted.

Action

Check the operating environment and the settings.

KEOS21007-W (F)

An attempt to execute the command has failed. (command = aa....aa)

aa....aa: Command line string

Description

An attempt to execute the displayed command has failed.

The processing continues.

Action

Confirm the following details:

The command path is correct (whether it exists).

The command is executable (there are executable attributes).

The command access permission is appropriate.

Memory and disk space is sufficient.

KEOS21008-W (F)

The command finished with an error. (command = aa....aa; exit code = bb....bb)

aa....aa: Command line string

bb....bb: Exit code

Description

The displayed command finished with an error.

The processing continues.

Action

Confirm whether the preconditions (such as settings and environment variables) for executing the command are fulfilled, and remove the cause of the error in the command.

KEOS21009-I (F)

The log file specified in aa....aa does not exist.

aa....aa: Path of the snapshot log settings file

Description

The log file described in the displayed snapshot log settings file does not exist.

The processing continues. The snapshot log file (zip) will not be created.

KEOS21010-I (F)

An access from aa....aa was refused.

aa....aa: IP address

Description

There was an access from a host that is not permitted access.

This access will be ignored, and then the processing continues.

Action

Specify settings so that access is permitted as and when required.

KEOS21011-E (F)

The connection was refused. (host = aa....aa; port = bb....bb)

aa....aa: Host name or IP address

bb....bb: Port number

Description

The connection was refused.

The operations will continue if possible, and will terminate if operations cannot be continued.

Action

Check the operating environment and settings shown below:

Is the Administration Agent running on the specified host?

Is the port number valid?

Is the access to the Administration Agent to which you will connect denied?

KEOS21012-I (F)

The command has started. (command = aa....aa ; pid = bb....bb ; cc....cc, dd....dd)

aa....aa: Command line string

bb....bb: Process ID

cc....cc: Environment variable

dd....dd: Environment information (In Windows, owner and group are always blank)

Description

The command described in the command starts.

KEOS21013-I (F)

The command has finished. (command = aa....aa; pid = bb....bb, exit code = cc....cc)

aa....aa: Command line string

bb....bb: Process ID

cc....cc: Exit code

Description

The command described in the command has finished.

KEOS21014-E (F)

An attempt to execute the command has failed. (command = aa....aa; cause = bb....bb)

aa....aa: Command line string

bb....bb: Cause

Description

An attempt to execute the command described in the command has failed.

The processing will now stop.

Action

Remove the error described in the cause, and then re-execute the command.

KEOS21015-I (F)

Collection of Snapshotlog was canceled.

Description

A request was received to interrupt Snapshotlog collection while collection is in process.

KEOS21016-I (C)

Usage: snapshotlog output

Description

This message is the usage method the snapshotlog command.

A message is displayed in the standard error output, and then the processing terminates.

Action

See the message, and check the usage method of the command.

KEOS21017-I (C)

Collection of Snapshotlog has started.

Description

The collection of Snapshotlog has started.

KEOS21018-I (C)

Collection of Snapshotlog has finished.

Description

The collection of Snapshotlog has finished.

KEOS21019-E (C)

An attempt to collect Snapshotlog has failed. (cause = aa....aa)

aa....aa: Cause

Description

An attempt to collect the Snapshotlog has failed.

Action

Check the cause.

KEOS21020-E (F)

An attempt to initialize the administration agent has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to initialize the administration agent has failed.

Action

Check the operating environment and the settings. When checking, confirm the following details:

Has a used port number been specified?

If specifying the settings for bind address, are those settings valid?

If the bind address is specified with the IP address pattern, does the pattern match with the local IP address?

KEOS21021-W (F)

The setting for Snapshotlog is invalid. (details = aa....aa)

aa....aa: Details

Description

The specified Snapshotlog collection target is invalid. This specification will be ignored and the processing continues.

Action

Revise the settings.

KEOS21022-W (F)

The specified property aa....aa is invalid. bb....bb will be used instead.

aa....aa: Property name

bb....bb: Default value

Description

The specified property value is invalid.

The default value will be used.

Action

Revise the settings.

KEOS21023-W (F)

An attempt to delete the file has failed. (file name = aa....aa)

aa....aa: File name

Description

The file cannot be deleted.

The operations of the Administration Agent will continue if possible, and will terminate if operations cannot be continued.

Action

Check the operating environment and the settings such as file name and permissions.

KEOS21024-E (F)

An attempt to create the directory has failed. (directory name = aa....aa)

aa....aa: Directory name

Description

The directory cannot be created.

The operations of the Administration Agent will continue if possible, and will terminate if operations cannot be continued.

Action

Check the operating environment and the settings such as file name and permissions.

KEOS21025-E (F)

An attempt to write to the file has failed. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Detailed message

Description

An attempt to write to the file has failed.

The operations of the Administration Agent will continue if possible, and will terminate if operations cannot be continued.

Action

Check the operating environment and the settings such as file name and permissions.

KEOS21026-I (F)

Process monitoring will now start. (command = aa....aa, pid = bb....bb)

aa....aa: Command line string

bb....bb: Process ID

Description

The monitoring of the process used in logical server monitoring will be restarted. The command line is the command line used in logical server startup.

KEOS21027-I (F)

The process has completed. (command = aa....aa, pid = bb....bb)

aa....aa: Command line string

bb....bb: Process ID

Description

The process to be used in logical server monitoring was terminated. The command line is the command line used in logical server startup.

KEOS21028-W (F)

The specified property(aa....aa) is over. (bb....bb) is used.

aa....aa: Property name

bb....bb: Default value

Description

The property specification has exceeded the permissible range. The default value will be used.

Action

Revise the settings.

KEOS21029-W (F)

The period of watching the server dumping its thread information was expired.

Description

The monitoring time of the thread dump output during forced termination was exceeded.

The termination process of the logical server will continue.

Action

Revise the settings.

KEOS21030-I (F)

Collection of Snapshotlog specified in aa....aa has started.

aa....aa: Path of the snapshot log settings file

Description

The collection of the snapshot log starts.

KEOS21031-I (F)

Collection of Snapshotlog specified in aa....aa has finished.

aa....aa: Path of the snapshot log settings file

Description

The collection of the Snapshotlog has finished.

KEOS21032-W (F)

The IP address applicable to specified IP address pattern(aa....aa) found more than one. (bb....bb) is used.

aa....aa: IP address pattern string

bb....bb: Used IP address

Description

Multiple local IP addresses were found corresponding to the IP address pattern specified in the adminagent.adapter.bind_host key in adminagent.properties file. Bind will be performed with the smallest IP address from among the corresponding IP addresses.

Action

Change to an IP address pattern applicable only to one IP address.

KEOS21033-W (F)

Processing to check the operation of aa....aa (bb....bb) timed out. A retry will now be performed. (set value = cc....cc, current value = dd....dd)

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Setup value of the retry count

dd....dd: Current value of the retry count

Description

Retry will be executed as the operation confirmation process has timed out. The operation confirmation process will be re-executed.

Action

Extract the data through actions such as collection of snapshot log, and then investigate the causes that led to the timeout.

KEOS21034-W (F)

Processing to check the operation of aa....aa(bb....bb) has failed. A retry will now be performed. (set value = cc....cc, current value = dd....dd)

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Setup value of the retry count

dd....dd: Current value of the retry count

Description

Retry will be executed as the operation confirmation process has failed. The operation confirmation process will be re-executed.

Action

Extract the data through actions such as collection of snapshot log, and then investigate the causes for the failure in the operation confirmation process.

KEOS21035-E (F)

An abnormal status was detected during monitoring of aa....aa (bb....bb).

aa....aa: Logical server name

bb....bb: Logical server type

Description

An abnormal status of the logical server was found. The errors in the logical server will be reported to the Management Server.

Action

Extract the data through actions such as collection of snapshot log, and then investigate the causes for the detection of the abnormal status.

KEOS21036-I (F)

The log file specified in aa....aa and bb....bb does not exist.

aa....aa: Path of the Snapshot log settings file for primary data

bb....bb: Path of the Snapshot log settings file for secondary data

Description

The log file described in the displayed snapshot log settings file does not exist. The processing continues. The Snapshot log file (zip) will not be created.

KEOS21037-I (F)

Collection of Snapshotlog specified in aa....aa and bb....bb has started.

aa....aa: Path of the Snapshot log settings file for primary data

bb....bb: Path of the Snapshot log settings file for secondary data

Description

The collection of the Snapshotlog starts.

KEOS21038-I (F)

Collection of Snapshotlog specified in aa....aa and bb....bb has finished.

aa....aa: Path of the Snapshot log settings file for primary data

bb....bb: Path of the Snapshot log settings file for secondary data

Description

The collection of the Snapshotlog has finished.

KEOS21039-E (F)

The local address was not found. A forced stop will be performed. (address = aa....aa)

aa....aa: IP address

Description

The logical server was terminated forcefully, and the Administration Agent was terminated on detection of the standby node.

Action

Check the operating environment and the settings.

KEOS21040-W (F)

Cannot specify the unique user name from the owner of the file aa....aa, because there are two or more users related to user ID bb....bb. The user name cc....cc is used to execute dd....dd.

aa....aa: File name

bb....bb: User ID

cc....cc: User name

dd....dd: Command

Description

The user name could not be specified because more than one user is registered in relation to the file owner. The user name displayed in the message is used, and the processing is continued.

Action

For any problem with the user name displayed in the message, enable the specification of the user name from the user ID.

KEOS21041-W (F)

Could not connect to the RMI registry. detail=aa....aa

aa....aa: Details

Description

Could not connect to the RMI registry. The processing of the Administration Agent will be continued.

Action

If any error occurs after this message, see the detailed information, and then check the operating environment or settings.

KEOS21042-W (F)

An attempt to substitute the variable for collecting Snapshotlog has failed using the snapshotlog command. Variable name= aa....aa, Details= bb....bb within the collection target definition file

aa....aa: Variable name within the collection target definition file

bb....bb: Details

Description

An attempt to substitute the variable for collecting Snapshotlog has failed using the snapshotlog command. The variable will be ignored for which an attempt to substitute has failed, and the process will be continued.

Action

See the details of the message, and if necessary, revise the variable settings.

KEOS21100-I (L/F)

The administration agent service has started.

Description

The Administration Agent service has started.

KEOS21101-I (L/F)

The administration agent service has stopped.

Description

The Administration Agent service has stopped.

KEOS21102-E (L/F)

The administration agent service could not be initialized.

Description

An attempt to initialize the Administration Agent service has failed.

The processing will be interrupted.

Action

A message describing the details is output. See the message, and then remove the error.

KEOS21103-E (L/F)

The administration agent service could not be started.

Description

The Administration Agent service cannot be started.

The processing will be interrupted.

Action

Check the operating environment and the settings.

KEOS21104-E (F)

The administration agent service could not output information to the Event Log service. (ec = aa....aa)

aa....aa: Error code

Description

The information cannot be output to the event log.

The process will continue without output to the event log.

Action

Confirm that the event log service is operating normally.

KEOS21105-E (L/F)

The administration agent could not be started.

Description

The Administration Agent cannot be started.

The processing will be interrupted.

Action

A message describing the details is output. See the message, and then remove the error.

KEOS21106-E (L/F)

The administration agent command could not be acquired from the registry.

Description

The Administration Agent command cannot be acquired from the registry.

The processing will be interrupted.

Action

If the problem cannot be resolved even after restarting the server, contact maintenance personnel.

KEOS21107-E (L/F)

The administration agent could not be started. (ec = aa....aa)

aa....aa: Error code

Description

An attempt to start the Administration Agent service has failed.

Action

Check the operating environment and the settings.

KEOS21108-E (L)

The administration agent could not be started. (detail = aa....aa)

aa....aa: Detail

Description

The Administration Agent service could not be started. The processing will be interrupted.

Action

Reference the message details, and then remove the cause of the error. If the details are "The logon user is not using a local system account, or does not belong to the Administrators group", specify a local system account or an account belonging to the Administrators group in the Administration Agent log on account.

KEOS21109-W (F)

Synchronous execution of Administration Agent failed.

Description

The synchronous execution of Administration Agent has failed.

The synchronous execution will be interrupted.

Action

After a pause, use the mngsvrutil check command or the adminagentcheck command, and confirm that Administration Agent is operating. If you are unable to confirm the operation, see the message output to adminagentctl.exe.[1 through 16].log and adminagentsv.exe.[1 through 16].log, remove cause of the error, and then re-execute the command.

KEOS21120-I (L/F)

The executing TerminateProcess() will now start. (handle = aa....aa, pid = bb....bb, command = cc....cc)

aa....aa: Handle of the process to be stopped

bb....bb: Process ID of the process to be stopped

cc....cc: Command line string used for starting the process to be stopped

Description

The execution of TerminateProcess() will start.

KEOS21121-I (L/F)

The executing TerminateProcess() ended. (handle = aa....aa, pid = bb....bb, rc = cc....cc, ec = dd....dd, command = ee....ee)

aa....aa: Handle of the process to be stopped

bb....bb: Process ID of the process to be stopped

cc....cc: Return value of TerminateProcess()

dd....dd: Error code of TerminateProcess()

ee....ee: Command line string used for starting the process to be stopped

Description

The execution of TerminateProcess() has ended.

KEOS21200-I (C/F)

The administration agent has started.

Description

The Administration Agent service has started.

KEOS21201-I (C/F)

The administration agent has stopped.

Description

The Administration Agent service has stopped.

KEOS21202-E (C/F)

An attempt to start the administration agent has failed.

Description

An attempt to start the Administration Agent service has failed.

The command execution will be suspended.

Action

If end code is 1

Check the operating environment and settings.

If end code is 3

After a pause, use the mngsvrutil check command or the adminagentcheck command, and check that Administration Agent is operating.

If you are unable to check the operations, see the messages output to adminagentctl.exe.[1 through 16].log and adminagentsv.exe.[1~16].log console in Windows, and adminagentctl.[1 through 16].log and the console in UNIX, remove the cause of the error, and re-execute the command.

KEOS21203-E (C/F)

An attempt to stop the administration agent service has failed.

Description

An attempt to stop the Administration Agent service has failed.

The command execution will be suspended.

Action

If end code is 1

Check the operating environment and settings.

If end code is 3

After a pause, check that Administration Agent is stopped.

If you are unable to check that Administration Agent is stopped, see the messages output to adminagentctl.exe.[1 through 16].log and adminagentsv.exe.[1 through 16].log in Windows, and adminagentctl.[1 through 16].log and the console in UNIX, remove the cause of the error, and re-execute the command.

KEOS21206-E (C) (Windows)

Usage : adminagentctl {start|stop} [-sync [-timeout <timeout>]]

start : start Administration Agent Service

stop : stop Administration Agent Service

-sync : Synchronously executes the command.

-timeout <timeout> : Sets the timeout for synchronous execution.

Description

The method of starting the command is incorrect.

The command execution will be suspended.

Action

Enter the correct command again.

KEOS21206-E (C) (UNIX)

Usage : adminagentctl {start|stop} [-sync [-timeout <timeout>]] [-daemon]

start : start Administration Agent Service

stop : stop Administration Agent Service

-sync : Synchronously executes the command.

-timeout <timeout> : Sets the timeout for synchronous execution.

-daemon : Starts the command as a daemon process.

Description

The method of starting the command is incorrect.

The command execution will be suspended.

Action

Enter the correct command again.

KEOS21207-E (C/F)

The administration agent service could not be started. (ec = aa....aa)

aa....aa: Error code

Description

An attempt to start the Administration Agent service has failed.

Action

Check the operating environment and the settings.

KEOS21300-I (C)

Usage: mngautorun -d | [once|respawn] {server|agent|both} [-sync [-timeout <timeout>]]

-d: Restores the setting to its installation time state.

once : Sets automatic starting.

respawn: Sets automatic restarting.

server: Configures Management Server to run automatically

when this computer is started.

agent : Configures Administration Agent to run automatically

when this computer is started.

both : Configures both Management Server and Administration Agent

to run automatically, IN ORDER, when this computer is started.

-sync : Synchronously executes the command.

-timeout <timeout> : Sets the timeout for synchronous execution.

Description

This message describes the usage method of the mngautorun command.

A message is displayed in the standard error output, and then the processing terminates.

Action

See the message, and check the usage method of the command.

KEOS21301-E (C)

An internal error occurred. [aa....aa failed. ec=bb....bb]

aa....aa: API name

bb....bb: Error code

Description

An API has failed.

The command execution will be suspended.

This command may have been used when some other application was operating the registry.

Action

Re-execute the command later or terminate the other application, and then re-execute the command.

KEOS21302-E (C)

An attempt to allocate memory has failed.

Description

An attempt to secure memory has failed.

The command execution will be suspended.

Action

Secure sufficient memory by actions such as terminating other applications, and then re-execute the command.

KEOS21303-I (C)

Settings have been successfully completed.

Description

The settings are successfully completed.

KEOS21304-I (F)

A network drive was successfully allocated. (drive = aa....aa, path = bb....bb)

aa....aa: Allocated drive name

bb....bb: Allocated path name

Description

A network drive was successfully allocated.

KEOS21305-W (F)

An attempt to allocate a network drive has failed. (drive = aa....aa, path = bb....bb, winapi ec = cc....cc)

aa....aa: Allocated drive name

bb....bb: Allocated path name

cc....cc: WindowsAPI error code

Description

An attempt to allocate a network drive has failed. The processing continues.

Action

Check the error code contents, and revise the network drive settings.

Also, if the path specified in add.network.drive ends with \, the network drive might fail to connect. Revise the settings.

KEOS21306-E (F)

System call error. (func=aa....aa, ec=bb....bb)

aa....aa: API name

bb....bb: Error code

Description

An attempt to process API has failed. The processing will be interrupted.

Action

Contact maintenance personnel.

KEOS21307-W (F)

The network drives are not allocated because the logon account of the administration agent is a local system account.

Description

The network drives are not allocated because the log on account of the Administration Agent is a local system account. The processing continues.

Action

Start the Administration Agent using an account belonging to the Administrators group other than the local system account.

KEOS21309-E (C/F)

Configuration failed. (detail = aa....aa)

aa....aa: Details

Description

The configuration failed. The processing will be cancelled.

Action

See the message output in the details to remove the cause of the error, and then re-execute the command.

KEOS21310-I (C)

Usage: mngautorun -d | [once|respawn] {server|agent|both} [-runlevel <runlevel>] [-sync [-timeout <timeout>]]

-d: Restores the setting to its installation time state.

once : Sets automatic starting.

respawn: Sets automatic restarting.

server: Configures Management Server to run automatically

when this computer is started.

agent : Configures Administration Agent to run automatically

when this computer is started.

both : Configures both Management Server and Administration Agent

to run automatically, IN ORDER, when this computer is started.

-runlevel <runlevel> : Specifies the runlevel for performing

automatic starting and restarting.

-sync : Synchronously executes the command.

-timeout <timeout> : Sets the timeout for synchronous execution.

Description

This message is the usage method of the mngautorun command.

KEOS21400-E (F)

An attempt to open the file has failed. (file = aa....aa)

aa....aa: Path of the defined file

Description

An attempt to open the defined file has failed.

Action

Check the environment such as the permissions for the defined file.

KEOS21401-E (F)

The specified option is invalid. (line = aa....aa)

aa....aa: Line number

Description

The option in line number aa....aa is not specified properly.

Action

Check the contents of the adminagentuser.cfg file.

KEOS21500-I (C)

Usage: adminagentcheck [-t <time>][<host>[:<port>]]

-t <time>

Specifies the command timeout limit

<time> - command timeout limit

<host>[:<port>]

Specifies the host and the port number of the Administration Agent to be connected.

<host> - host name or IP address

<port> - port number

Description

This message describes the usage method of the adminagentcheck command.

A message is displayed in the standard error output, and then the processing terminates.

Action

See the message, and check the usage method of the command.

KEOS22000-I (C)

The process was successfully killed. (pid=aa....aa)

aa....aa: Process ID

Description

The process was stopped successfully.

KEOS22001-E (C)

The pid is invalid. (pid = aa....aa)

aa....aa: Process ID

Description

The process ID is invalid.

The processing continues for the next process.

Action

Check the command argument.

KEOS22002-E (C)

The process does not exist. (pid = aa....aa)

aa....aa: Process ID

Description

The process does not exist.

The processing continues for the next process.

Action

Check the command argument.

KEOS22003-E (C)

Access for execution of the command was denied.

Description

The command execution was rejected.

The processing terminates.

Action

A user belonging to the Administrators group needs to execute the command.

KEOS22004-E (C)

An attempt to kill the process has failed. (aa....aa)

aa....aa: Details

Description

An attempt to stop the process has failed.

The processing will continue if possible, and will terminate if processing cannot be continued.

Action

Contact maintenance personnel.

KEOS22005-I (C)

Usage: kill pid ...

Description

This message describes the usage method of the Kill command.

A message is displayed in the standard error output, and then the processing terminates.

Action

See the message, and check the usage method of the command.

KEOS22006-W (F)

The writing of the entry to a Zip file has failed. File=aa....aa detail=bb....bb

aa....aa: File name

bb....bb: Detailed message

Description

The writing of the entry to a Zip file has failed.

The processing continues.

Action

See the detailed information, remove the cause of the error, and then re-execute the process.

KEOS22100-I (C)

Usage:

mngsvrupdate [-t <target name>] [-k <target kind>] <command> [<args>]

where:

-t <target name>

Specifies a target name, such as a logical server or host.

-k <target kind>

Indicates the kind of a target. <target kind>:=logicalServer|host (the default is logicalServer)

<command>

"d2r" - Convert DataSource to Resource Adapter.

<args>

For the "d2r" command:

[<dataSource> [<resAdapter>]]

<dataSource> - DataSource

<resAdapter> - Resource Adapter

Description

This message describes the usage method of the mngsvrupdate command.

A message is displayed in the standard error output, and then the processing terminates.

Action

See the message, and check the usage method of the command.

KEOS22101-I (C/F)

No convertible datasource was found for the specified parameters.

Description

There was not data source that can be converted.

KEOS22102-I (C/F)

The conversion ended successfully. (Logical Server = aa....aa, Datasource = bb....bb, Resource Adapter= cc....cc)

aa....aa: Logical server name

bb....bb: Display name of the data source before conversion

cc....cc: Display name of the resource adapter after conversion

Description

The data source was converted to a resource adapter.

KEOS22103-W (C/F)

The conversion cannot be performed. (Logical Server = aa....aa, Datasource = bb....bb)

aa....aa: Logical server name

bb....bb: Display name of the data source before conversion

Description

The conversion cannot be performed as the display name may have been changed.

The processing will be skipped, and then the processing for the next data source continues.

Action

Specify the display name of the data source and resource adapter, and then execute the conversion command.

KEOS22104-E (C/F)

An attempt to convert the datasource has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to convert the data source has failed.

Action

See the detailed information, remove the cause of the error, and then re-execute the process.

KEOS22300-W (F)

The default settings will be used because the manager.cfg file cannot be read.

Description

The manager.cfg file cannot be read. The default value will be used. The processing continues using the default value.

Action

Confirm whether:

manager.cfg file exists.

There are access permissions to manager.cfg file.

The format of the manager.cfg file is valid.

KEOS22301-W (F)

The specified property aa....aa is invalid. bb....bb will be used instead.

aa....aa: Property name

bb....bb: Default value

Description

The specified property value is invalid. The processing continues using the default value.

Action

Revise the settings.

KEOS22302-E (C)

An attempt to initialize the log has failed. (file name = aa....aa, reason = bb....bb)

aa....aa: Log file name

bb....bb: Cause of failure

Description

An attempt to initialize the log has failed. The processing will be executed without log output.

Action

Confirm the environment of the location where the log is to be output.

Supplementary note

The processing continues after this message is output, but an error occurs in the subsequent processing due to causes related to the cause of this message, and the Management Server and Administration Agent might fail to start.

KEOS22303-I (F)

aa....aa

aa....aa: Continuation message

Description

This message is a continuation message.

This message and the process ID and thread ID are the same and the message is a continuation of the message output just before this message.

KEOS22304-I (F)

The command has started. (command = aa....aa, pid = bb....bb, start time = cc....cc)

aa....aa: Command line

bb....bb: Process ID

cc....cc: Command start time

Description

The command described in the message starts.

KEOS22305-I (F)

The command has finished. (pid = aa....aa, start time = bb....bb, exit code = cc....cc)

aa....aa: Process ID

bb....bb: Command start time

cc....cc: Exit code

Description

The command, described in the process ID and the command start time, has finished.

KEOS22400-E (C)

Usage: mngenvsetup [-mng | -ua] { <Management User Group> | -d }

Description

This message displays the usage method of the mngenvsetup command. The message code and message will be displayed in standard error output, and the processing will be suspended.

Action

Execute the command with the correct syntax.

KEOS22401-I (C/F)

The configuration of permission has succeeded.(Command Name = aa....aa)

aa....aa: Name of the command for change

Description

An attempt to set up the permission using the command for change was successful.

KEOS22402-I (C/F)

The configuration of group has succeeded.(Command Name = aa....aa, Group Name = bb....bb)

aa....aa: Name of the command for change

bb....bb: Specified group name

Description

An attempt to set up the specified group using the command for change was successful.

KEOS22403-I (C/F)

The both configurations of MNG Administration Group and Integration User Administration Group have succeeded.(Group Name = aa....aa)

aa....aa: Specified group name

Description

The Management Server Management Group and Integrated User Management Group are set up in the specified group.

KEOS22404-I (C/F)

The configuration of MNG Administration Group has succeeded.(Group Name = aa....aa)

aa....aa: Specified group name

Description

The Management Server Management Group is set up in the specified group.

KEOS22405-I (C/F)

The configuration of Integration User Administration Group has succeeded.(Group Name = aa....aa)

aa....aa: Specified group name

Description

The Integrated User Management Group is set up in the specified group.

KEOS22406-E (C)

Specified group is not in existence. (Group name = aa....aa)

aa....aa: Specified group name

Description

The specified group is not registered in the OS. A message will be displayed in the standard error output, and the processing will be suspended.

Action

Specify an existent group.

KEOS22407-E (C/F)

The configuration of permission has failed.(Command Name = aa....aa, errno = bb....bb)

aa....aa: Name of the command for change

bb....bb: Detailed message

Description

An attempt for setting the permission using the command for change has failed. A message is displayed in the standard error output, and then the processing continues.

Action

Confirm that the process is executed with root authority. If executed with other than root authority, re-execute the process with root authority. If the problem is still not resolved, contact maintenance personnel.

KEOS22408-E (C/F)

The configuration of group has failed.(Command Name = aa....aa, Group Name = bb....bb, errno = cc....cc)

aa....aa: Name of the command for change

bb....bb: Specified group name

cc....cc: Details

Description

An attempt for setting the specified group with the command for change has failed. A message will be displayed in the standard error output, and the processing will be continued.

Action

Confirm that the process is executed with root authority. If executed with other than root authority, re-execute the process with root authority. If the problem is still not resolved, contact maintenance personnel.

KEOS22409-E (C/F)

The both configurations of MNG Administration Group and Integration User Administration Group have failed.(Group Name = aa....aa)

aa....aa: Specified group name

Description

An attempt for setting the Management Server Management Group and Integrated User Management Group in the specified group has failed. A message will be displayed in the standard error output, and the processing will be suspended.

Action

Confirm that the process is executed with root authority. If executed with other than root authority, re-execute the process with root authority. If the problem is still not resolved, contact maintenance personnel.

KEOS22410-E (C/F)

The configuration of MNG Administration Group has failed.(Group Name = aa....aa)

aa....aa: Specified group name

Description

An attempt for setting up the Management Server Management Group in the specified group has failed. A message will be displayed in the standard error output, and the processing will be suspended.

Action

Confirm that the process is executed with root authority. If executed with other than root authority, re-execute the process with root authority. If the problem is still not resolved, contact maintenance personnel.

KEOS22411-E (C/F)

The configuration of Integration User Administration Group has failed.(Group Name = aa....aa)

aa....aa: Specified group name

Description

An attempt for setting the Integrated User Management Group in the specified group has failed. A message will be displayed in the standard error output, and the processing will be suspended.

Action

Confirm that the process is executed with root authority. If executed with other than root authority, re-execute the process with root authority. If the problem is still not resolved, contact maintenance personnel.

KEOS22415-E (C/F)

The memory allocation has failed.

Description

An attempt to allocate the memory has failed. A message will be displayed in the standard error output, and the processing will be suspended.

Action

Remove the cause of the error, and then re-execute the process.

KEOS22416-E (C)

The process of the log initialization has failed.

Description

An attempt to initialize the log has failed. A message will be displayed in the standard error output, and the processing will be suspended.

Action

Confirm the environment of the location where the log is to be output.

KEOS22417-E (C/F)

An attempt to open the file has failed.(File Path = aa....aa, errno = bb....bb)

aa....aa: File path

bb....bb: Detailed message

Description

An attempt to open the file has failed.

The processing continues.

Action

When an error occurs, delete the aa....aa file displayed in the message, and then re-execute the process.

KEOS22418-E (C/F)

An attempt to remove the file has failed.(File Path = aa....aa, errno = bb....bb)

aa....aa: File path

bb....bb: Detailed message

Description

The deletion of the file has failed.

The processing continues.

Action

When an error occurs, delete the aa....aa file displayed in the message, and then re-execute the process.

KEOS22419-E (C/F)

An attempt to change the process authority has failed.(Detail = aa....aa )

aa....aa: Details

Description

An attempt to change the process permission has failed.

The processing will be interrupted.

Action

Contact maintenance personnel.

KEOS23001-E (C)

The option is specified incorrectly.

Description

An invalid option is specified in the command argument.

The command process will be interrupted.

Action

Specify the option correctly, and then re-execute the command.

KEOS23002-E (C)

JP1/Base was not properly installed.

Description

The JP1/BASE product is not installed.

The command process will be interrupted.

Action

Install the JP1/BASE product, and then re-execute the command.

KEOS23003-I (C)

The adapter command setup has started.

Description

The adapter command setup starts.

The processing continues.

KEOS23004-I (C)

The adapter command setup finished successfully.

Description

The adapter command setup finished successfully.

The processing terminates.

KEOS23005-E (C)

Access to the adapter command settings file (aa....aa) was denied.

aa....aa: Name of the adapter command settings file

Description

An attempt to access the adapter command settings file has failed.

The command process will be interrupted.

Action

Check whether the user who executes the command has permissions to create or delete files. Also, check whether any free space is available on the disk where the file exists.

KEOS23006-I (C)

The adapter command unsetup has started.

Description

The adapter command un-setup starts.

The processing continues.

KEOS23007-I (C)

The adapter command unsetup finished successfully.

Description

The adapter command un-setup finished normally.

The processing terminates.

KEOS23008-E (C)

usage : mngsvr_adapter_setup [-i|-u] [-t IM_CS|IM_CM]

-i installing adapter command(default)

-u uninstalling adapter command

-t selection of the target JP1 product(default IM_CS)

Description

This message describes the usage method of the mngsvr_adapter_setup command.

A message is displayed in the standard error output, and then the processing terminates.

Action

See the message, and check the usage method of the command.

KEOS23053-E (C)

An error exists in the parameter set up in the standard input.

Description

The parameter set up in the standard input is invalid.

The command process will be interrupted.

Action

Check the prerequisite version of the related JP1 products.

KEOS23054-E (C)

The parameter of the format version set up in the standard input cannot be processed.

Description

The parameter of the format version set up in the standard input cannot be processed.

The command process will be interrupted.

Action

Check the prerequisite version of the related JP1 products.

KEOS23101-E (C)

The option is specified incorrectly.

Description

An invalid option is specified in the command argument.

The command process will be interrupted.

Action

Specify the option correctly, and then re-execute the command.

KEOS23102-E (C)

An attempt to access the registry has failed.

Description

An attempt to access the registry has failed.

The command process will be interrupted.

The operating environment such as a registry may be corrupt.

Action

Restart the OS, and then re-execute the process. If the problem is not resolved even after re-execution, contact maintenance personnel.

KEOS23103-E (C)

An internal error occurred.

Description

An internal error occurred.

The command process will be interrupted.

Action

If the error is not removed even after the command is re-executed, contact maintenance personnel.

KEOS23201-I (F)

The JP1 event was successfully sent. (pid = aa....aa, tid = bb....bb, time of occurrence = cc....cc)

aa....aa: Process identifier

bb....bb: Thread identifier

cc....cc: JP1 event request time

Description

The JP1 event was successfully sent.

The processing continues.

KEOS23202-W (F)

An attempt to send the JP1 event has failed. (pid= aa....aa, tid= bb....bb, time of occurrence = cc....cc, status = dd....dd)

aa....aa: Process identifier

bb....bb: Thread identifier

cc....cc: JP1 event request time

dd....dd: Status code indicating cause of the failure

Description

An attempt to send the JP1 event has failed.

The processing continues.

Action

Remove the cause of the error based on actions for each of the following status codes:

40:

The JP1 event service cannot be connected. Check that the JP1 event service to which you will connect is running.

43:

An file I/O error occurred. Check the usage status of the system resources.

51:

Memory is insufficient. Check the usage status of the system resources.

52:

The number of open files has reached the limit. Check the usage status of the system resources.

Others:

Contact maintenance personnel.

KEOS23203-E (F)

An attempt to read the settings file has failed. (file = aa....aa)

aa....aa: File name

Description

Access denied.

The processing continues, but JPI events will not be issued hereafter.

Action

Confirm that the settings file exists and also check the access permissions. Then, restart the J2EE server or the Management Server.

KEOS23204-I (F)

The processing to send a JP1 event was successfully initialized.

Description

The processing to send a JP1 event was successfully initialized.

The processing continues.

KEOS23205-E (F)

Initialization of the processing to send a JP1 event has failed. (details = The function to initialize the processing to send a JP1 event has failed with status = aa....aa)

aa....aa: Status code indicating cause of the failure

Description

The function to initialize JP1 event issue processing has been aborted.

The processing continues, but JPI events will not be issued hereafter.

Action

Remove the cause of the error based on the actions for each of the following status codes, and then restart the J2EE server, the Management Server, or the Administration Agent.

50:

The library was not found. Check that JP1/Base of the prerequisite version is installed.

51:

Memory is insufficient. Check the usage status of the system resources.

Others:

Contact maintenance personnel.

KEOS23206-E (F)

An attempt to initialize the processing to send a JP1 event has failed. (details = An attempt to load aa....aa failed.)

aa....aa: Shared library name that has been failed to load

Description

An attempt to load the shared library has failed.

The processing continues, but JPI events will not be issued hereafter.

Action

Contact maintenance personnel.

KEOS23207-E (F)

An internal error occurred.

Description

An internal error occurred.

The processing continues, but JPI events will not be issued hereafter.

Action

If the errors are not removed even after restarting the J2EE server, Management Server, or Administration Agent, contact maintenance personnel.

KEOS23301-I (F)

The web system aa....aa was added.

aa....aa: Name of the added Web system

Description

The Web system was added.

KEOS23302-I (F)

The web system aa....aa was deleted.

aa....aa: Name of the deleted Web system

Description

The Web system was deleted.

KEOS23303-I (F)

The web system aa....aa was modified.

aa....aa: Name of the modified Web system

Description

The Web system was modified.

KEOS24000-E (C)

Usage:

aa....aa

aa....aa: Usage of the command

Description

An invalid value is specified in the command argument.

Action

See the message, and check the usage method of the command.

The possible errors are as follows:

The required option is not specified.

Specification of common arguments is omitted, and the client settings property file (.cmxrc) cannot be correctly read. The client settings property file is not created under the home directory of the OS login user or an error exists in the file access permissions.

Option that cannot be specified is specified.

A mistake exists in the relationship specified for the option and option argument. The option argument is not specified when the specification is mandatory, or the option argument is specified for options where the option argument cannot be specified.

KEOS24001-E (C)

The specified file is not a normal file. file name = aa....aa

aa....aa: File name

Description

A special file is specified.

The processing will be interrupted.

Action

Check the specified file.

KEOS24002-E (C)

An exception occurred during an attempt to read .cmxrc. (details =aa....aa)

aa....aa: Details

Description

An attempt to read the .cmxrc file has failed.

The processing will be interrupted.

Action

Check the access permissions of the .cmxrc file.

If no error exists in the file access permissions, but if the error is not resolved even after re-executing the command, contact maintenance personnel.

KEOS24003-E (C)

The host or userid common option has not been specified.

Description

The host or user ID has not been specified in the common argument.

The processing will be interrupted.

Action

Check that the cmx.connect.host key and cmx.connect.userid key is set in the client settings property file (.cmxrc).

KEOS24004-E (C)

aa....aa and bb....bb cannot be specified simultaneously.

aa....aa: Option

bb....bb: Option

Description

These options cannot be specified simultaneously.

The processing will be interrupted.

Action

Check the arguments specified in the command.

KEOS24005-E (C)

The file does not exist. file name = aa....aa

aa....aa: File name

Description

The specified file does not exist.

The processing will be interrupted.

Action

Check the arguments specified in the command.

KEOS24006-E (C)

A parser error occurred. (details = aa....aa)

aa....aa: Details

Description

An error occurred in the parser.

The processing will be interrupted.

Action

Confirm that the Cosminexus XML Processor is installed and that no mistake exists in the version of the installed Cosminexus XML Processor.

KEOS24007-E (C)

The definition file is invalid. file name = aa....aa line number = bb....bb column number = cc....cc details = dd....dd

aa....aa: File name

bb....bb: Line number

cc....cc: Column number

dd....dd: Details

Description

An error occurred while analyzing the file. The contents of the specified Easy Setup definition file or the configuration change definition file are invalid.

The processing will be interrupted.

Action

Correct the errors in the Easy Setup definition file or Configuration Change definition file, and then re-execute the command. Note that a Cosminexus XML Processor message is output in the details. For details on the message, see 11. KECX (Messages Output by Cosminexus XML Processor).

KEOS24008-E (C)

An exception occurred while reading the file. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Detailed message

Description

An Error occurred while reading the file.

The processing will be interrupted.

Action

Check the file access permissions.

If no error exists in the file access permissions, but if the error is not resolved even after re-executing the command, contact maintenance personnel.

KEOS24009-E (C)

The host is invalid. (details = aa....aa)

aa....aa: Details

Description

The specified host name or port number is invalid.

The processing will be interrupted.

Action

Confirm how to specify the host name and the port number.

KEOS24010-E (C)

A communication error occurred. (details =aa....aa)

aa....aa: Details

Description

A communication error occurred.

The processing will be interrupted.

Action

Confirm that the Management Server is running or check the values specified in the host name and the port number that are specified in the -m option of the common arguments. Also, check that the products of the connection source and the connection destination can be connected.

KEOS24011-E (C)

An exception occurred while creating the temporary file. (details = aa....aa)

aa....aa: Details

Description

An error occurred while creating the temporary file.

The processing will be interrupted.

Action

Contact maintenance personnel.

KEOS24012-E (C)

The option value is invalid. (option = aa....aa, value = bb....bb)

aa....aa: Option

bb....bb: Option value

Description

An invalid value was specified in the option.

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file or the configuration change definition file.

KEOS24013-E (C)

The parameter aa....aa cannot be specified for a logical server of type bb....bb. (line number = cc....cc)

aa....aa: Parameter

bb....bb: Logical server type

cc....cc: Line number

Description

An invalid parameter is specified in the logical server type. The processing will be interrupted at the location of the displayed line number.

Action

Check the contents of the configuration definition file.

KEOS24014-E (C)

Multiple parameter values cannot be specified for the parameter aa....aa. (line number = bb....bb)

aa....aa: Parameter

bb....bb: Line number

Description

Multiple values cannot be specified in the parameter. The processing will be interrupted at the location of the displayed line number.

Action

Check the contents of the configuration definition file.

KEOS24015-E (C)

The parameter value aa....aa cannot be specified for the parameter bb....bb. (line number = cc....cc)

aa....aa: Parameter value

bb....bb: Parameter

cc....cc: Line number

Description

An invalid value is specified in the parameter. The processing will be interrupted at the location of the displayed line number.

Action

Check the contents of the configuration definition file.

KEOS24016-E (C)

An invalid namespace was used in the XML file.

Description

An invalid name space is used.

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file or the configuration change definition file.

KEOS24017-E (C)

File open failed. File Name=aa....aa detail=bb....bb

aa....aa: File name

bb....bb: Detailed message

Description

An attempt to open the file has failed.

The processing will be interrupted.

Action

Check the file access permissions.

KEOS24018-E (C)

Invalid Tier combinations have been specified.

Description

The combination of physical tiers is invalid.

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file or the configuration change definition file.

KEOS24019-E (C)

Two or more aa....aa were allocated for a unit. (unit name = bb....bb)

aa....aa: Physical tier type

bb....bb: Service unit name

Description

Multiple allocated-host elements specified with the same physical tier type (aa....aa) are coded in the service unit bb....bb.

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file or the configuration change definition file.

KEOS24020-E (C)

No tier (tier type = aa....aa) was allocated for a unit (unit name = bb....bb).

aa....aa: Physical tier type

bb....bb: Service unit name

Description

The allocated-host element with the physical tier type specified is not defined in a service unit.

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file or the configuration change definition file.

KEOS24021-E (C)

A aa....aa and other tiers were allocated for a unit. (unit name = bb....bb)

aa....aa: Physical tier type

bb....bb: Service unit name

Description

Multiple allocated-host elements specified with the physical tier type (aa....aa) and other physical tier types are defined in the service unit bb....bb.

The processing will be interrupted.

Action

Check the contents of the configuration change definition file.

KEOS24022-E (C)

An invalid logical server type (aa....aa) is defined in bb....bb.

aa....aa: Logical server type

bb....bb: Physical tier type

Description

A logical server type that cannot be specified in the physical tier type is specified.

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file or the configuration change definition file.

KEOS24023-I (C)

The translations of the abstract parameters were successful.

Description

An attempt to expand the abstract parameters was successful.

KEOS24024-E (C)

An invalid server ID rule (aa....aa) is defined.

aa....aa: Server ID rule

Description

An invalid server ID rule is specified.

The processing will be interrupted.

Action

Revise the server ID rule.

KEOS24025-E (C)

A number of units exceeding the number that can be generated for the server ID rule was specified.

Description

Service units exceeding the number of server IDs that can be generated for the server ID rule cannot be registered.

The processing will be interrupted.

Action

Revise the server ID rule.

KEOS24026-E (C)

An invalid number of elements is specified.

Description

The number of elements in the option argument is invalid.

The processing will be interrupted.

Action

Check the command execution method.

KEOS24027-E (C)

An invalid element is specified. (option = aa....aa, element = bb....bb)

aa....aa: Option

bb....bb: Element in the option argument

Description

An invalid element is specified in the option argument.

The processing will be interrupted.

Action

Check the command execution method.

KEOS24028-E (C)

A duplicated element is specified. (option = aa....aa, element = bb....bb)

aa....aa: Option

bb....bb: Element in the option argument

Description

A duplicated element is specified in the option argument.

The processing will be interrupted.

Action

Check the command execution method.

KEOS24029-E (C)

An invalid combination of tiers is specified.

Description

An invalid combination of physical tiers is specified.

The processing will be interrupted.

Action

Check the command execution method.

KEOS24030-E (C)

An invalid command is specified. (command = aa....aa)

aa....aa: Command

Description

An invalid command is specified.

The processing will be interrupted.

Action

Check the command execution method.

KEOS24031-E (C)

The sfo-tier and other tiers are allocated to the unit. (unit name = aa....aa)

aa....aa: Service unit name

Description

An sfo-tier and other tiers are allocated to the service unit.

The processing will be interrupted.

Action

Check the contents of the configuration definition file.

KEOS24032-E (C)

The parameter aa....aa cannot be used with the product bb....bb. (line number =cc....cc)

aa....aa: Parameter

bb....bb: Product name

cc....cc: Line number of the definition file

Description

The parameter aa....aa cannot be used in the product bb....bb.

The processing will be interrupted.

Action

Delete this parameter from the definition file.

KEOS24033-E (C)

The aa....aa cannot be used with the product bb....bb.

aa....aa: Tier

bb....bb: Product name

Description

The tier aa....aa cannot be used in the product bb....bb.

The processing will be interrupted.

Action

Delete the tier specification from the definition file.

KEOS24035-E (C)

In the product aa....aa, you must specify the IP address of the local host (the host executing the command) for the management IP or operational IP address. (host name = bb....bb)

aa....aa: Product name

bb....bb: Host name

Description

In the product aa....aa, you must specify the IP address of the local host (the host executing the command) for the operationalIP or managementIP.

The processing will be interrupted.

Action

Change the IP address specified for the host in the definition statement to the IP address of the local host.

KEOS24036-E (C)

The load balancer cannot be defined in the ctm-tier. (Web system name = aa....aa)

aa....aa: Web system name

Description

The load balancer cannot be defined in the CTM tier.

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file.

KEOS24037-E (C)

The j2ee-server-count cannot be specified for the aa....aa. (Web system name = bb....bb)

aa....aa: Physical tier type

bb....bb: Web system name

Description

You cannot specify the j2ee-server-count tag in the physical tier aa....aa (Web system name = bb....bb).

The processing will be interrupted.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

Action

Delete the j2ee-server-count tag of the tier aa....aa from the Easy Setup definition file.

KEOS24038-E (C)

When the j2ee-server-count is specified as 0, the j2ee-server cannot be specified for the logical-server-type. (Web system name = aa....aa)

aa....aa: Web system name

Description

When the specified value of the j2ee-server-count tag is 0, you cannot specify j2ee-server as the logical server type (Web system name = aa....aa).

The processing will be interrupted.

Action

Delete the specification of the logical server type aa....aa from the Easy Setup definition file.

KEOS24039-E (C)

When the logical-server-type is specified as aa....aa, the server-no cannot be specified. (Web system name = bb....bb)

aa....aa: Logical server type

bb....bb: Web system name

Description

You cannot specify the server-no tag in the logical server type aa....aa (Web system name = bb....bb).

The processing will be interrupted.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

Action

Delete the server-no tag of the logical server type aa....aa from the Easy Setup definition file.

KEOS24040-E (C)

The server-no(aa....aa) is larger than the j2ee-server-count(bb....bb). (Web system name = cc....cc)

aa....aa: Specified value of the server-no tag

bb....bb: Specified value of the j2ee-server-count tag

cc....cc: Web system name

Description

A value greater than the specified value of the j2ee-server-count tag (bb....bb) is specified for the server-no tag (aa....aa) (Web system name = cc....cc).

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file.

KEOS24041-E (C)

The server-no is not specified for the define-server. (Web system name = aa....aa, unit name = bb....bb)

aa....aa: Web system name

bb....bb: Unit name

Description

The server-no tag is not specified in the server definition of the unit (Web system name = aa....aa, unit name = bb....bb).

The processing will be interrupted.

Action

Specify the server-no tag in the server definition (j2ee-server tag) of the unit bb....bb.

KEOS24042-E (C)

When the j2ee-server-count is not specified, the server-no cannot be specified. (Web system name = aa....aa)

aa....aa: Web system name

Description

When the j2ee-server-count tag is not specified, you cannot specify the server-no tag (Web system name = aa....aa).

The processing will be interrupted.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

Action

Delete the server-no tag from the Easy Setup definition file.

KEOS24043-E (C)

Multiple logical-server-type of the aa....aa are specified. (Web system name = bb....bb)

aa....aa: Logical server type

bb....bb: Web system name

Description

There is more than one specification of the logical server type aa....aa (Web system name = bb....bb).

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file.

KEOS24044-E (C)

aa....aa cannot be specified in this Web system. (Web system name = bb....bb)

aa....aa: Tier type

bb....bb: Web system name

Description

You cannot specify aa....aa in this Web system.

The processing will be interrupted.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

Action

When free-tier is specified in tier type, omit the Web system name. If the Web system name is specified, free-tier cannot be specified in the tier type. Check the contents of the Easy Setup definition file.

KEOS24045-E (C)

A configuration tag cannot be specified for a free-tier tier tag.

Description

A configuration tag cannot be specified for a tier tag in free-tier. The processing will be interrupted.

Action

Delete the configuration tag specified in the tier tag, and then specify the configuration tag for the unit tag.

KEOS24046-E (C)

A user-server configuration cannot be specified for the aa....aa. (Web system name = bb....bb)

aa....aa: Tier type

bb....bb: Web system name

Description

You cannot specify the user-server configuration in the tier tag.

The processing will be interrupted.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

Action

Delete the user-server configuration tag specified in the tier tag, and specify the user-server configuration tag in the unit tag.

KEOS24047-E (C)

The logical server type (aa....aa) cannot be used with the product (bb....bb).

aa....aa: Logical server type

bb....bb: Product name

Description

You cannot use the logical server type aa....aa with the product bb....bb.

The processing will be interrupted.

Action

Delete the specification of the logical server type aa....aa from the Easy Setup definition file.

KEOS24048-E (C)

The load balancer cannot be defined.

Description

If the Web system name is omitted, you cannot specify the load-balancer tag.

The processing will be interrupted.

Action

Delete the definition of the load-balancer tag.

KEOS24049-E (C)

The cluster-ref aa....aa is invalid.(Web system name = bb....bb)

aa....aa: Cluster name

bb....bb: Web system name

Description

Clustering is specified for a logical server that cannot be clustered. Either the specified value aa....aa of the cluster-ref tag is not defined or the cluster type is different.

The processing will be interrupted.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

Action

Check the contents of the Easy Setup definition file.

KEOS24050-E (C)

The logical-server-name must be specified for the free-tier.

Description

The logical-server-name tag cannot be omitted for free-tier.

The processing will be interrupted.

Action

Specify the logical-server-name tag.

KEOS24051-E (C)

The configuration cannot be specified for the cluster aa....aa.

aa....aa: Cluster name

Description

You cannot specify the configuration tag in the cluster.

The processing will be interrupted.

Action

Delete the definition of the configuration tag of the cluster.

KEOS24052-E (C)

More than one Web system does not have a name.

Description

More than one Web system does not have a name. The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file.

KEOS24053-E (C)

More than one unit does not have a name.

Description

More than one unit does not have a name. The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file.

KEOS24054-E (C)

A unit for a Web system that does not have a name, or a Web system that does have a name but for which the unit is omitted, is specified.(Web system name = aa....aa)

aa....aa: Web system name

Description

The service unit name is specified in the unit tag of a Web system for which the Web system name is not defined. Alternatively, the unit tag is omitted in a Web system for which the Web system name is defined.

The processing will be interrupted.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

Action

Check the contents of the Easy Setup definition file.

KEOS24055-E (C)

In the product aa....aa, you must specify the IP address or host name of the local host (the host executing the command) for the host-name or agent-host. (host name = bb....bb)

aa....aa: Product name

bb....bb: Host name

Description

In the product aa....aa, you cannot specify other than the IP address or host name of the local host (the host that executes the command) in the host-name tag or agent-host tag.

The processing will be interrupted.

Action

Change the IP address specified for the host in the definition statement to the IP address of the local host.

KEOS24056-E (C)

The logical-server-type must be specified for the configuration of tier. (Web system name = aa....aa, tier type = bb....bb)

aa....aa: Web system name

bb....bb: Tier type

Description

You cannot omit the logical-server-type tag for the configuration tag of the tier.

The processing will be interrupted.

Action

Specify the logical-server-type tag.

KEOS24057-E (C)

The command (aa....aa) cannot be used with the product (bb....bb).

aa....aa: Command name

bb....bb: Product name

Description

The command aa....aa cannot be used with the product bb....bb. The processing will be interrupted.

KEOS24058-W (C/F)

The parameter (aa....aa) cannot be used with the product (bb....bb). (line number = cc....cc)

aa....aa: Parameter

bb....bb: Product name

cc....cc: Line number in the definition file

Description

The parameter aa....aa cannot be used with the product bb....bb. The error is ignored, and the processing continues.

Action

Delete the parameter aa....aa from the definition file.

KEOS24059-I (C)

The user ID and password of the Management Server administrator account is not set because the management user account is disabled.

Description

The user ID and password of the Management Server administrator account is not set up because the management user account is disabled.

KEOS24100-I (F)

CMX processing will now start. (client = aa....aa)

aa....aa: Connection source

Description

The setup process will start using the Smart Composer.

KEOS24101-I (F)

CMX processing has finished.

Description

The setup process will terminate using the Smart Composer.

KEOS24102-E (C)

A communication error occurred. (details = aa....aa)

aa....aa: Details

Description

A communication error occurred.

The processing will be interrupted.

Action

If the error is not resolved even after re-executing the command, contact maintenance personnel.

KEOS24103-E (C)

An exception occurred while creating a temporary file. (details = aa....aa)

aa....aa: Details

Description

An error occurred while creating the temporary file.

The processing will be interrupted.

Action

Contact maintenance personnel.

KEOS24104-E (C)

An administrator's user ID or a password is incorrect.

Description

The administrator user ID or password is invalid.

The processing will be interrupted.

Action

Check the specified administrator user ID and password.

KEOS24105-E (C)

An administrator's user account is already specified.

Description

The administrator user ID and password of the Management Server are already registered.

The processing will be interrupted.

Action

With this command, you cannot change a registered administrator user ID and password. If you need to change the management user ID and the password, use the management portal.

KEOS24106-E (C)

The configuration file could not be saved. (details = aa....aa)

aa....aa: Details

Description

An attempt to save the settings file has failed.

Action

Contact maintenance personnel.

KEOS24107-I (F)

The processing for aa....aa will now start.

aa....aa: Details

Description

The command process starts.

KEOS24108-I (F)

The processing for aa....aa has finished.

aa....aa: Details

Description

The command process has finished.

KEOS24109-E (C)

The specified Web system (Web system name = aa....aa) is not registered.

aa....aa: Web system name

Description

The Web system specified in the -s option of the command or the configuration change definition file is not registered.

The processing will be interrupted.

Action

Check the argument specified in the command or the configuration change definition file contents.

KEOS24110-E (C)

The specified unit (Web system name = aa....aa, unit name = bb....bb) is not registered.

aa....aa: Web system name

bb....bb: Service unit name

Description

The service unit specified in the -unit option of the command is not registered in the Web system.

The processing will be interrupted.

Action

Check the argument specified in the command or the configuration change definition file contents.

KEOS24111-E (C)

The specified tier (Web system name = aa....aa, tier type = bb....bb) is not registered.

aa....aa: Web system name

bb....bb: Physical tier type

Description

The physical tier type specified in the configuration change definition file is not registered in the Web system.

The processing will be interrupted.

Action

In the physical tier type (tier-type tag of physical tier definition or host-for tag of the service unit definition) of the configuration change definition file, the specified tier type is other than the physical tier defined while building the Web system.

Modify the configuration change definition file, and then re-execute the command.

KEOS24112-E (C)

No units are registered in the Web system. (Web system name = aa....aa)

aa....aa: Web system name

Description

The service unit is not registered in the Web system.

All service units are deleted.

The processing will be interrupted.

Action

Check the arguments specified in the command.

Add the service unit if errors do not exist in the command arguments.

KEOS24113-E (C)

The Web system (Web system name = aa....aa) is already registered.

aa....aa: Web system name

Description

The Web system specified in the Easy Setup definition file is already registered.

The processing will be interrupted.

Action

Check the Easy Setup definition file contents and how to execute the command.

KEOS24114-E (C)

The unit (Web system name = aa....aa, unit name = bb....bb) is already registered.

aa....aa: Web system name

bb....bb: Service unit name

Description

The service unit specified in the configuration change definition file is already registered in the Web system.

The processing will be interrupted.

Action

Check the configuration change definition file contents and how to execute the command.

KEOS24115-E (C)

The host (host name/IP address = aa....aa) is already registered.

aa....aa: Host name or operation IP address

Description

The host is already registered.

The processing will be interrupted.

Action

Check the Easy Setup definition file contents and how to execute the command.

Check that a host with the same operation IP address is not specified in another Web system or that the same host name is not used in the Web system.

KEOS24116-E (C)

An attempt to register the host that registers the naming service for the management server (host name = aa....aa) has failed.

aa....aa: Host name that registers the naming service used by the Management Server

Description

An attempt to register the host that registers the naming service used by the Management Server has failed.

The processing will be interrupted.

Action

If the error is not resolved even after re-executing the command, contact maintenance personnel.

KEOS24117-I (C)

The settings of the administrator's user account were changed.

Description

The settings of the administrator's user account were changed.

KEOS24119-I (C)

The naming service for the management server (logical server name = aa....aa) has already started.

aa....aa: Host name that registers the naming service used by the Management Server

Description

The naming service used by the Management Server has already started.

KEOS24120-E (C)

An attempt to start the naming service for the management server (logical server name = aa....aa) has failed.

aa....aa: Host name that registers the naming service used by the Management Server

Description

An attempt to start the naming service used by the Management Server has failed.

The processing will be interrupted.

Action

Examine the log file of the Management Server, check the log related to the logical server start and stop, remove the error, and then re-execute the command.

KEOS24121-I (C)

The naming service for the management server (logical server name = aa....aa) has started.

aa....aa: Host name that registers the naming service used by the Management Server

Description

An attempt to start the naming service used by the Management Server was successful.

KEOS24122-E (C)

The logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has been deleted.

aa....aa: Web system name

bb....bb: Service unit name

cc....cc: Logical server name

Description

The logical server is deleted.

The logical server might have been deleted by using the management portal.

Action

Add the service unit after deleting it once.

KEOS24123-I (C)

The logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has already started.

aa....aa: Web system name

bb....bb: Service unit name

cc....cc: Logical server name

Description

The logical server has already started.

KEOS24124-E (C)

An attempt to start the logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has failed.

aa....aa: Web system name

bb....bb: Service unit name

cc....cc: Logical server name

Description

An attempt to start the logical server has failed.

Action

Examine the log file of the Management Server, check the log related to the logical server start and stop, remove the error, and then re-execute the command.

KEOS24125-I (C)

The logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has started.

aa....aa: Web system name

bb....bb: Service unit name

cc....cc: Logical server name

Description

An attempt to start the logical server was successful.

KEOS24126-I (C)

The logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has already stopped.

aa....aa: Web system name

bb....bb: Service unit name

cc....cc: Logical server name

Description

The logical server has already stopped.

KEOS24127-E (C)

An attempt to stop the logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has failed.

aa....aa: Web system name

bb....bb: Service unit name

cc....cc: Logical server name

Description

An attempt to stop the logical server has failed.

Action

Examine the log file of the Management Server, check the log related to the logical server start and stop, remove the error, and then re-execute the command.

KEOS24128-I (C)

The logical server (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc) has stopped.

aa....aa: Web system name

bb....bb: Service unit name

cc....cc: Logical server name

Description

An attempt to stop the logical server was successful.

KEOS24129-I (C)

The Web system (Web system name = aa....aa) was successfully built.

aa....aa: Web system name

Description

The Web system was successfully built.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

KEOS24130-I (C)

The Web system (Web system name = aa....aa) was successfully changed.

aa....aa: Web system name

Description

The Web system was successfully changed.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

KEOS24131-E (C/F)

This command is not supported. (details = aa....aa)

aa....aa: Details

Description

This command is not supported.

The processing will be interrupted.

Action

Check the version of the product installed in the operation management machine and the version of the product installed in the machine executing the command.

KEOS24132-I (C)

The operation on the load balancer was successful. (load balancer = aa....aa)

aa....aa: Management IP address of the load balancer

Description

The operation on the load balancer was successful.

KEOS24133-E (C/F)

The attempted operation on the load balancer has failed. (load balancer = aa....aa, details = bb....bb)

aa....aa: Management IP address of the load balancer

bb....bb: Detailed message

Description

An attempted operation on the load balancer has failed.

The processing will be interrupted.

Action

Remove the error based on the detailed information described in the following table, and then re-execute the command.

Table 13‒1: List of error details described in KEOS24133-E

Details

Description

Action

ncm.host is null or empty.

The ncm.host key of the load balancer definition property file (lb.properties) is not set or the value of the ncm.host key is null.

Set the ncm.host key of the lb.properties file appropriately.

Invalid xxx

The value of the xxx key of the load balancer definition property file (lb.properties) is invalid.

Set the xxx key of the lb.properties file appropriately.

ncm.user is null or empty.

The ncm.user key of the load balancer definition property file (lb.properties) is not set or the value of the ncm.user key is null.

Set the ncm.user key of the lb.properties file appropriately.

ncm.passwd is null.

The ncm.passwd key of the load balancer definition property file (lb.properties) is not set.

Set the ncm.passwd key of the lb.properties file appropriately.

The LB named xxx.xxx.xxx.xxx is not configured.

The load balancer of xxx.xxx.xxx.xxx is not defined in the lb.list key of the load balancer definition property file (lb.properties).

Set the lb.list key of the lb.properties file appropriately.

Access denied: <file>

The <file> either does not exist, is not a normal file, or is not readable.

Confirm that the <file> exists, is a normal file, and that it is readable.

The script named xxx does not exist: <file>

The script (xxx) is not defined in the script definition file <file>.

Copy the latest script definition file supported in <file> to the following locations:

In Windows

Cosminexus-installation-directory\manager\config

In UNIX

/opt/Cosminexus/manager/config

The connection failed.

An attempted connection has failed.

Set the lb.telnet.port.xxx, lb.ssh.port.xxx, and lb.API.port.xxx key of the lb.properties file or the management IP address of the Easy Setup file load balancer definition appropriately.

An I/O error occurred during data transfer from the load balancer.

An I/O error has occurred while receiving the data.

Re-execute the cmx command. If the problem is not resolved, contact maintenance personnel.

An I/O error occurred during data transfer to the load balancer.

An I/O error has occurred while sending the data.

Re-execute the cmx command. If the problem is not resolved, contact maintenance personnel.

A timeout occurred while waiting for a response to the user prompt.

A timeout occurred while receiving the user prompt.

Set the lb.telnet.user_prompt.xxx key of the lb.properties file appropriately. If the above keys are appropriate, set a value greater than the value of the lb.telnet.login_timeout.xxx key.

A timeout occurred while waiting for a response to the password prompt.

A timeout occurred while receiving the password prompt.

Set the lb.telnet.user_prompt.xxx key of the lb.properties file appropriately. If the above keys are appropriate, set a value greater than the value of the lb.telnet.login_timeout.xxx key.

A timeout occurred while waiting for a response to the login prompt.

A timeout occurred while receiving the login prompt.

Se the lb.telnet.user.xxx, lb.telnet.passwd.xxx, lb.telnet.login_prompt.xxx keys appropriately. If the above keys are appropriate, set a value greater than the value of the lb.telnet.login_timeout.xxx key.

A timeout occurred.

A timeout occurred.

Set a value greater than the value of the lb.telnet.command_timeout.xxx, lb.ssh.timeout.xxx, or lb.API.timeout.xxx keys. If the problem is not resolved, contact maintenance personnel.

An I/O error occurred.

An I/O error occurred.

Re-execute the cmx command. If the problem is not resolved, contact maintenance personnel.

The connection closed.

The connection to the load balancer was disconnected.

Set the lb.telnet.user.xxx, lb.telnet.passwd.xxx, lb.telnet.user_prompt.xxx, lb.telnet.passwd_prompt.xxx, lb.telnet.login_prompt.xxx keys of the lb.properties file appropriately. If the problem is not resolved, contact maintenance personnel.

xxx is null or empty.

The xxx key of the load balancer definition property file (lb.properties) is not set or the value of the xxx key is null.

Set the xxx key of the lb.properties file appropriately.

Authentication has failed.

An attempted authentication has failed.

Set the lb.ssh.user.xxx, lb.ssh.passwd.xxx keys of the lb.properties file appropriately.

A command execution error occurred: (<returncode>, <errormessage>)

An error occurred in command execution.

Specify the error cause from the command return code <returncode> and error message <errormessage>.

An API processing error occurred: (<returncode>, <errormessage>)

An error occurred in API processing.

Identify the cause of the error from the return code <returncode> and the error message <errormessage>.

An unexpected exception occurred.

An unexpected exception occurred.

Contact maintenance personnel.

The load balancer type is incorrect.

The load balancer type is incorrect.

Set up an appropriate value in the <load-balancer-type> tag of the Easy Setup definition file.

Others

An attempt to execute the CLI command of load balancer has failed.

Re-execute the cmx command. If the problem is not resolved, contact maintenance personnel.

KEOS24135-E (C)

An attempt to register the host (host name = aa....aa) has failed.

aa....aa: Host name

Description

An attempt to register the host has failed.

The logical server and application might have been updated by using the management portal.

Action

If the error is not resolved even when the command is re-executed after some time, contact maintenance personnel.

KEOS24138-W (C)

The load balancer is not defined on the Web system (Web system name = aa....aa).

aa....aa: Web system name

Description

The load balancer is not defined in the specified Web system (The connection test of the load balancer is not implemented with the cmx_test_lb command).

The processing will be interrupted.

Action

Check how to execute the command and the Easy Setup definition file contents.

KEOS24139-E (C)

The load balancer (Web system name = aa....aa, load balancer name = bb....bb) is not registered.

aa....aa: Web system name

bb....bb: Load balancer name

Description

The load balancer is not registered.

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file.

KEOS24140-E (C)

The virtual server (Web system name = aa....aa, load balancer name = bb....bb, virtual server name = cc....cc) is not registered.

aa....aa: Web system name

bb....bb: Load balancer name

cc....cc: Virtual server name

Description

The virtual server is not registered.

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file.

KEOS24141-E (C)

An internal error occurred. (details = aa....aa)

aa....aa: Details

Description

An internal error occurred.

The processing will be interrupted.

Action

Contact maintenance personnel.

KEOS24142-E (F/C)

A timeout occurred.

Description

A timeout occurred.

Commands that cannot be executed concurrently are being executed.

The processing will be interrupted.

Action

Re-execute after some time.

KEOS24143-E (F/C)

An exclusion error occurred.

Description

An exclusion error has occurred.

Commands that cannot be executed concurrently are being executed.

The processing will be interrupted.

Action

Re-execute after some time.

KEOS24144-I (F)

Processing for aa....aa(Web system name = aa....aa) has been accepted.

aa....aa: Command name

bb....bb: Web system name

Description

Received a command process for the Web system.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

KEOS24145-E (C)

An attempt to set up the logical server (Web system name=aa....aa, unit name=bb....bb, logical server name=cc....cc) has failed.

aa....aa: Web system name

bb....bb: Unit name

cc....cc: Logical server name

Description

An attempt to set up the logical server has failed.

The processing will be interrupted.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name and the unit name.

Action

Examine the log file of the Management Server, remove the error, and then re-execute the command.

KEOS24146-I (C)

An attempt to set up the logical server (Web system name=aa....aa, unit name=bb....bb, logical server name=cc....cc) was successful.

aa....aa: Web system name

bb....bb: Unit name

cc....cc: Logical server name

Description

An attempt to set up the logical server was successful.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name and the unit name.

KEOS24147-E (C)

An attempt to distribute the configuration file has failed. Web system name=aa....aa, unit name=bb....bb, logical server name=cc....cc

aa....aa: Web system name

bb....bb: Unit name

cc....cc: Logical server name

Description

An attempt to distribute the environment settings of the logical server has failed.

The processing will be interrupted.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name or the unit name.

Action

Examine the log file of the Management Server, remove the error, and then re-execute the command.

KEOS24148-I (C)

An attempt to distribute the configuration file was successful. Web system name=aa....aa, unit name=bb....bb, logical server name=cc....cc

aa....aa: Web system name

bb....bb: Unit name

cc....cc: Logical server name

Description

An attempt to distribute the environment settings of the logical server was successful.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name and the unit name.

KEOS24149-I (C)

The logical server (Web system name=aa....aa, unit name=bb....bb, logical server name=cc....cc) has already set upped.

aa....aa: Web system name

bb....bb: Unit name

cc....cc: Logical server name

Description

The logical server has already been set up.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name and the unit name.

KEOS24150-I (C)

The configuration file has already distributed. Web system name=aa....aa, unit name=bb....bb, logical server name=cc....cc

aa....aa: Web system name

bb....bb: Unit name

cc....cc: Logical server name

Description

The environment settings of the logical server have already been distributed.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name and the unit name.

KEOS24151-E (C)

An invalid XML Schema(aa....aa) was used.

aa....aa: XML schema

Description

An invalid XML schema is used.

The processing will be interrupted.

Action

Check the version of the server and the client.

KEOS24153-E (C)

An attempt to allocate memory has failed.

Description

An attempt to secure memory has failed. A standard error message will be displayed, and the processing will be terminated.

Action

Allocate sufficient memory by terminating the other applications, and re-execute the process.

KEOS24154-E (C)

An error occurred in the system function. function name = aa....aa, errno = bb....bb

aa....aa: Function name

bb....bb: Error number

Description

An error has occurred in the system function. A standard error message will be displayed, and the processing will be terminated.

Action

See the error number of the function, remove the error, and re-execute the process.

KEOS24157-E (C)

The host(Web system name=aa....aa, unit name=bb....bb, host name=cc....cc) is not registered.

aa....aa: Web system name

bb....bb: Unit name

cc....cc: Host name

Description

The host (host name = cc....cc) is not registered.

The processing will be interrupted.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name and the unit name.

Action

Check the contents of the Easy Setup definition file.

KEOS24158-W (C/F)

The setting value aa....aa of the specified parameter bb....bb is already being used. (logical server name = cc....cc)

aa....aa: Parameter value

bb....bb: Parameter

cc....cc: Logical server wherein an error occurred

Description

The settings value of the parameter specified in the logical server is being used elsewhere. The error will be ignored, and then the processing continues.

Action

The settings value of this parameter must be a unique value in the same server machine. Revise the settings value of the parameter specified in each logical server, and then change the Web system.

KEOS24159-W (C/F)

The aa....aa part of the specified parameter bb....bb is not defined as the setting value of the parameter cc....cc. (logical server name = dd....dd)

aa....aa: Value of part of the parameter name

bb....bb: Parameter

cc....cc: Parameter in which the settings for value of the parameter name is not defined

dd....dd: Logical server wherein an error occurred

Description

The value of part of the parameter specified in the logical server is not defined as the settings value of the parameter. The error will be ignored, and then the processing continues.

Action

Revise the settings value of the parameter specified in the configuration tag, and then change the Web system.

KEOS24160-W (C/F)

The logical server aa....aa specified in the parameter bb....bb of the logical server cc....cc is not defined.

aa....aa: Logical server name

bb....bb: Parameter

cc....cc: Logical server wherein an error occurred

Description

The logical server specified in the logical server parameter is not defined. The error will be ignored, and then the processing continues.

Action

Revise the settings value of the parameter specified in the configuration tag, and then change the Web system.

KEOS24161-W (C/F)

There is a correlation error in the setting value of the parameter aa....aa(value = bb....bb) and the parametercc....cc(value = dd....dd).(logical server name = ee....ee)

aa....aa: Parameter 1

bb....bb: Setting value of parameter 1

cc....cc: Parameter 2

dd....dd: Setting value of parameter 2

ee....ee: Logical server name wherein an error occurred

Description

A correlation error (such as maximum or minimum related errors) exists in the values of parameter 1 and parameter 2. The error will be ignored, and then the processing continues.

Action

Revise the settings value of the parameter specified in the configuration tag, and then change the Web system.

KEOS24162-W (C/F)

The attempted operation on the load balancer has failed. (load balancer = aa....aa, details = bb....bb)

aa....aa: Management IP address of the load balancer

bb....bb: Detailed message

Description

An attempted operation on the load balancer has failed. The error will be ignored, and then the processing continues.

For the detailed information, see Table 13-1 List of error details described in KEOS24133-E.

Action

Remove the error in the load balancer, and then test the load balancer with cmx_test_lb.

KEOS24163-W (C/F)

The attempted operation on the load balancer has failed. The operation on this load balancer will be suspended.(load balancer = aa....aa, details = bb....bb)

aa....aa: Management IP address of the load balancer

bb....bb: Detailed message

Description

An attempted operation on the load balancer has failed. The proceeding operations of this load balancer will be suspended.

For the detailed information, see Table 13-1 List of error details described in KEOS24133-E.

Action

Remove the error in the load balancer, and then test the load balancer with cmx_test_lb.

KEOS24164-I (C/F)

The operation on the suspended load balancer was successful.(load balancer = aa....aa)

aa....aa: Management IP address of the load balancer

Description

The operation on the suspended load balancer was successful.

Action

If the other load balancer is normal, issue an instruction (cmx_recover_lb) of error recovery to the Smart Composer after recovering the settings of this load balancer.

In the case of an error, remove the error, and then test the load balancer with cmx_test_lb.

KEOS24165-W (C/F)

The attempted operation on the suspended load balancer has failed. (load balancer = aa....aa, details =bb....bb)

aa....aa: Management IP address of the load balancer

bb....bb: Detailed message

Description

An attempted operation of a suspended load balancer has failed. The error will be ignored, and then the processing continues.

For the detailed information, see Table 13-1 List of error details described in KEOS24133-E.

Action

Remove the error in the load balancer, and then test the load balancer with cmx_test_lb.

KEOS24166-W (C/F)

The operation on the load balancer canceled because it was suspended. (load balancer = aa....aa)

aa....aa: Management IP address of the load balancer

Description

The load balancer operations could not be performed because the load balancer was suspended. The error will be ignored, and then the processing continues.

Action

Remove the error in the load balancer, and then test the load balancer with cmx_test_lb.

KEOS24167-E (C)

The logical server (logical server name = aa....aa) is already registered.

aa....aa: Logical server ID

Description

The logical server is already registered. The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file or the configuration change definition file.

KEOS24168-I (C)

The host (host name=aa....aa) has been registered.

aa....aa: Host name (if there are one or more host names, demarcate with commas)

Description

The host is registered.

KEOS24169-E (C)

The operation is not available on this unit(Web system name =aa....aa, unit name = bb....bb).

aa....aa: Web system name

bb....bb: Service unit name

Description

This operation is not valid for this service unit. The processing will be interrupted.

Action

Check that no error exists in the specified service unit name.

KEOS24170-E (C)

The host cannot be identified because a host with the same name exists. (host name = aa....aa)

aa....aa: Host name

Description

The host cannot be identified because a host with the same name exists. The processing will be interrupted.

Action

This host cannot be used. Re-create (add after deleting) the service unit such that the host name within the domain becomes unique.

KEOS24171-I (C)

The logical servers were successfully added to the Web system.

Description

An attempt to add the logical servers to the Web system was successful.

KEOS24172-I (C)

The logical server was successfully deleted from the Web system.

Description

An attempt to delete the logical server from the Web system was successful.

KEOS24173-E (C)

The logical server has already been added to the Web system. (Logical Server Name = aa....aa)

aa....aa: Logical server name

Description

The logical server aa....aa is already added in the Web system. The processing will be interrupted.

Action

Check the logical server name.

KEOS24174-E (C)

The logical server has not been added to the Web system. (Logical Server Name = aa....aa)

aa....aa: Logical server name

Description

The logical server aa....aa is not added to the Web system. The processing will be interrupted.

Action

Check the logical server name.

KEOS24175-E (C)

A nonexistent logical server has been specified. (Logical Server Name = aa....aa)

aa....aa: Logical server name

Description

A logical server aa....aa that does not exist is specified. The processing will be interrupted.

Action

Check the logical server name.

KEOS24176-E (C)

A logical server that is not a user server has been specified. (Logical Server Name = aa....aa)

aa....aa: Logical server name

Description

A logical server aa....aa that is not a user server is specified. The processing will be interrupted.

Action

Check the logical server name.

KEOS24177-E (C)

An invalid logical server type (aa....aa) is specified in the unit (unit name = bb....bb).

aa....aa: Logical server type

bb....bb: Service unit name

Description

An invalid logical server type aa....aa is specified in the server definition in the service unit bb....bb. The processing will be interrupted.

Action

Check the definition file contents.

KEOS24178-I (C/F)

The settings for the load balancer have resumed. (load balancer = aa....aa)

aa....aa: Management IP address of the load balancer

Description

The settings for the load balancer, suspended because of an error, have resumed.

KEOS24179-E (C)

The suspended load balancer does not exist.

Description

The suspended load balancer does not exist. The processing will be interrupted.

Action

The cmx_resume_lb command is valid only when the load balancer, suspended because of an error, exists.

KEOS24180-E (C)

A combination of the values specified to hosts-for element(aa....aa) and host-ref element(bb....bb) is invalid .(Web system name = cc....cc, unit name = dd....dd)

aa....aa: Tier type

bb....bb: Host name

cc....cc: Web system name

dd....dd: Service unit name

Description

The combination of the values specified for hosts-for element and host-ref element is invalid.

Action

Modify the values specified for hosts-for element and host-ref element specified in the service unit (service unit name) of the configuration change definition file to the combination of values specified while building the Web system or while adding the service unit, and then re-execute the command.

KEOS24181-I (C/F)

The Web system host information was changed successfully.

Description

An attempt to change the Web system host information was successful.

KEOS24182-E (C/F)

An attempt to change the Web system host information has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to change the Web system host information has failed. The processing will be interrupted.

Action

Check the detailed information, and remove the cause of the error.

KEOS24183-W (C/F)

The same CTMID is specified more than once for the same host. (logical server name = aa....aa)

aa....aa: Logical server name

Description

The same CTMID is specified more than once for the same host. The error will be ignored, and then the processing continues.

Action

You cannot define the same CTM more than once for the same host. Revise the configuration of the Web system.

KEOS24184-E (C/F)

The settings information for the load balancer is invalid. (Web system name = aa....aa, details = bb....bb)

aa....aa: Web system name

bb....bb: Detailed message

Description

The settings information for the load balancer is incorrect. The processing will be interrupted.

Action

Check the detailed information and the contents of the definition file.

KEOS24185-E (C)

The operation is not available on this web system(Web system name = aa....aa).

aa....aa: Web system name

Description

The executed operation is not valid for this Web system. The processing will be interrupted.

Action

Check that no errors exist in the specified Web system name.

KEOS24186-W (C)

The host aa....aa specified in the parameter bb....bb of the logical server cc....cc is not defined.

aa....aa: Host name

bb....bb: Parameter name

cc....cc: Logical server name wherein an error occurred

Description

The host name specified in the parameter of the logical server where an error occurred is not defined. The error will be ignored, and then the processing continues.

Action

Revise the settings value of the parameter specified in the configuration tag, and then change the Web system.

KEOS24187-W (C)

A recommended parameter and a non-recommended parameter were specified together. (parameter name - aa....aa ,bb....bb)

aa....aa: Recommended parameter

bb....bb: Non-recommended parameter

Description

A recommended parameter and non-recommended parameter were specified together. The recommended parameter will be enabled.

The error will be ignored, and then the processing continues.

Action

Check the settings of the recommended parameter and non-recommended parameter.

KEOS24188-W (C)

The logical server corresponding to the specified parameter was not found. (parameter name = aa....aa, logical server name = bb....bb)

aa....aa: Parameter

bb....bb: Logical server name

Description

The logical server corresponding to the specified parameter aa....aa was not found.

The error will be ignored, and then the processing continues.

Action

Check the specified parameter.

KEOS24189-E (C)

No hosts are defined for the management server.

Description

Not even a single host is defined in the Management Server. The processing will be interrupted.

Action

Define one or more hosts in the Management Server, and then re-execute the process.

KEOS24191-E (C)

The host name aa....aa cannot be converted to an IP address.

aa....aa: Host name

Description

The host name cannot be converted to the IP address. The processing will be interrupted.

Action

In the host name mentioned in the definition, specify a resolvable name as the host name or IP address.

KEOS24192-E (C)

The host name cannot be converted because more than one host will be replaced.

Description

The host name cannot be converted because more than one host name will be converted to the same name. The processing will be interrupted.

Action

Execute the command without specifying the -myhost option.

KEOS24193-E (C)

The host name cannot be converted because the host name and agent host do not match.

Description

The host name cannot be converted because the host-name and agent-host tags are different. The processing will be interrupted.

Action

Execute the command without specifying the -myhost option.

KEOS24194-E (C)

The host name cannot be converted because the host name aa....aa cannot be converted to IP addresses.

aa....aa: Host name

Description

The host name cannot be converted because either a local host or an undecided host exists. The processing will be interrupted.

Action

Execute the command without specifying the -myhost option.

KEOS24195-W (C)

A parameter specification linked to worker settings is incorrect. (logical server name = aa....aa)

aa....aa: Logical server name

Description

A parameter specification linked to worker settings is incorrect. The processing will be interrupted.

Action

Check the specified parameter.

KEOS24196-W (C)

The logical server aa....aa cannot be exported.

aa....aa: Logical server name

Description

The logical server aa....aa could not be exported. A member of the cluster not related to the Web system cannot be exported.

KEOS24197-I (C)

The management server information was exported successfully.

Description

An attempt to export the Management Server information was successful.

KEOS24198-E (C)

There are no logical servers that are not linked to the Web system.

Description

There is not even a single logical server that is not related to the Web system to be distributed. The processing will be interrupted.

Action

Examine the log file of the Management Server, remove the error, and then re-execute the command.

KEOS24200-E (C)

The specified application file is invalid. file name = aa....aa

aa....aa: File name

Description

An invalid application file is specified.

The processing will be interrupted.

Action

Check the file contents.

KEOS24201-E (C)

The application (display name = aa....aa, version = bb....bb) has already been deployed.

aa....aa: Application display name

bb....bb: Application version ID

Description

An application with the same display name as the specified application has already been deployed.

The processing will be interrupted.

Action

Check the arguments specified in the command.

If no mistake exists in the command argument, un-deploy the application, and then re-execute the command.

KEOS24202-E (C)

An attempt to operate the model has failed. (details = aa....aa)

aa....aa: Details

Description

An attempted operation of the Web system information model has failed.

The processing will be interrupted.

The logical server and the application might have been updated by using the management portal.

Action

If the error is not resolved even when the command is re-executed after some time, contact maintenance personnel.

KEOS24203-E (C)

The application (display name = aa....aa, version = bb....bb) is already registered.

aa....aa: Application display name

bb....bb: Application version ID

Description

The application is already registered.

The processing will be interrupted.

Action

Check the arguments specified in the command.

If no error exists in the command arguments and if the application is re-registered, specify the -replace option, and re-execute the cmx_register_application command.

KEOS24204-I (C)

The application (display name = aa....aa, version = bb....bb) was successfully registered.

aa....aa: Application display name

bb....bb: Application version ID

Description

An attempt to register the application was successful.

KEOS24205-E (C)

The application (display name = aa....aa, version = bb....bb) is defined for a Web system. (Web system name = cc....cc)

aa....aa: Application display name

bb....bb: Application version ID

cc....cc: Web system name

Description

The operation cannot be performed because the application was correlated to the Web system.

The processing will be interrupted.

Action

Check the arguments specified in the command.

If no error exists in the command arguments, delete the correlation between the application and the Web system, and then re-execute the command.

KEOS24206-E (C)

The application (display name = aa....aa, version = bb....bb) does not exist.

aa....aa: Application display name

bb....bb: Application version ID

Description

The specified application does not exist.

The processing will be interrupted.

Action

Check the arguments specified in the command.

KEOS24207-I (C)

The application (display name =aa....aa, version = bb....bb) does not exist.

aa....aa: Application display name

bb....bb: Application version ID

Description

The specified application does not exist.

The specified application is already deleted with other operations in the deletion process.

KEOS24208-E (C)

The application (display name=aa....aa, version=bb....bb) was deleted.

aa....aa: Application display name

bb....bb: Application version ID

Description

The applicable application does not exist.

The application might have been deleted by using the management portal.

Action

Re-register the application with the cmx_register_application command.

KEOS24209-I (C)

The application (display name = aa....aa, version = bb....bb) was successfully unregistered.

aa....aa: Application display name

bb....bb: Application version ID

Description

An attempt to delete the application was successful.

KEOS24210-E (C)

The application (display name = aa....aa, version = bb....bb) is already defined for a Web system. (Web system name = cc....cc)

aa....aa: Application display name

bb....bb: Application version ID

cc....cc: Web system name

Description

The application is already correlated to the Web system.

The processing will be interrupted.

Action

Check the Web system information model contents and how to execute the command.

KEOS24211-I (C)

The application (display name = aa....aa, version = bb....bb) was successfully defined for the Web system (Web system name = cc....cc).

aa....aa: Application display name

bb....bb: Application version ID

cc....cc: Web system name

Description

An attempt to correlate the application to the Web system was successful.

KEOS24212-E (C)

The application (display name = aa....aa, version = bb....bb) has no definitions for the Web system (Web system name = cc....cc).

aa....aa: Application display name

bb....bb: Application version ID

cc....cc: Web system name

Description

The application is not correlated to the Web system.

The processing will be interrupted.

Action

Check the arguments specified in the command.

If no error exists in the command arguments, execute the cmx_define_application command, and then correlate the application to the Web system.

KEOS24213-E (C)

There is no logical server in the Web system (Web system name = aa....aa).

aa....aa: Web system name

Description

The logical server does not exist in the Web system.

The processing will be interrupted.

Action

Check the Web system information model contents and how to execute the command.

KEOS24215-I (C)

The application's (display name = aa....aa version = bb....bb) Web system definition was successfully deleted (Web system name = cc....cc).

aa....aa: Application display name

bb....bb: Application version ID

cc....cc: Web system name

Description

The correlation between the application and the Web system was cancelled.

KEOS24216-E (C)

The application has no definitions for the Web system (Web system name = aa....aa).

aa....aa: Web system name

Description

The application is not correlated to the Web system.

The processing will be interrupted.

Action

Check the arguments specified in the command.

If no error exists in the command arguments, execute the cmx_define_application command, and then correlate the application to the Web system.

KEOS24217-E (C)

The application (display name = aa....aa) has no definitions for the Web system (Web system name = bb....bb).

aa....aa: Application display name

bb....bb: Web system name

Description

The application is not correlated to the Web system.

The processing will be interrupted.

Action

Check the arguments specified in the command.

If no error exists in the command arguments, execute the cmx_define_application command, and then correlate the application to the Web system.

KEOS24218-I (C)

The application (display name =aa....aa) was successfully deployed to the logical server (logical server name = bb....bb).

aa....aa: Application display name

bb....bb: Logical server name

Description

An attempt to deploy the application was successful.

KEOS24219-E (C)

An attempt to deploy the application (display name = aa....aa) to the logical server (logical server name = bb....bb) has failed.

aa....aa: Application display name

bb....bb: Logical server name

Description

An attempt to deploy the application has failed.

Action

Examine the log file of the Management Server, check the application operations-related log, remove the error, and then re-execute the command.

KEOS24220-E (C)

The application (display name = aa....aa) was undeployed from the logical server (logical server name = bb....bb).

aa....aa: Application display name

bb....bb: Logical server name

Description

The application is not deployed.

The application may have been un-deployed in other operations during command execution.

Action

Deploy the application.

KEOS24221-I (C)

The application (display name = aa....aa) has already been deployed to the logical server (logical server name = bb....bb).

aa....aa: Application display name

bb....bb: Logical server name

Description

The application is already deployed.

KEOS24222-E (C)

The application (display name = aa....aa) has not been deployed to the logical server (logical server name = bb....bb).

aa....aa: Application display name

bb....bb: Logical server name

Description

The application is not deployed.

Action

Check the arguments specified in the command.

If no error exists in the command arguments, deploy the application.

KEOS24223-I (C)

The application (display name = aa....aa) was successfully undeployed from the logical server (logical server name = bb....bb).

aa....aa: Application display name

bb....bb: Logical server name

Description

An attempt to un-deploy the application was successful.

KEOS24224-E (C)

An attempt to undeploy the application (display name = aa....aa) from the logical server (logical server name = bb....bb) has failed.

aa....aa: Application display name

bb....bb: Logical server name

Description

An attempt to un-deploy the application has failed.

Action

Examine the log file of the Management Server, check the application operations-related log, remove the error, and then re-execute the command.

KEOS24225-E (C)

The system is busy. (logical server name = aa....aa, application display name = bb....bb)

aa....aa: Logical server name

bb....bb: Application display name

Description

The operations cannot be executed because other operations are being executed for the application.

Action

Terminate other operations, and then re-execute the operation.

KEOS24227-I (C)

The application (display name = aa....aa) was successfully started on the logical server (logical server name = bb....bb).

aa....aa: Application display name

bb....bb: Logical server name

Description

An attempt to starting the application was successful.

KEOS24228-E (C)

An attempt to start the application (display name = aa....aa) on the logical server (logical server name = bb....bb) has failed.

aa....aa: Application display name

bb....bb: Logical server name

Description

An attempt to start the application has failed.

Action

Examine the log file of the Management Server, check the application operations-related log, remove the error, and then re-execute the command.

KEOS24229-I (C)

The application (display name = aa....aa) on the logical server (logical server name = bb....bb) was successfully stopped.

aa....aa: Application display name

bb....bb: Logical server name

Description

An attempt to stop the application was successful.

KEOS24230-E (C)

An attempt to stop the application (display name = aa....aa) on the logical server (logical server name = bb....bb) has failed.

aa....aa: Application display name

bb....bb: Logical server name

Description

An attempt to stop the application has failed.

Action

Examine the log file of the Management Server, check the application operations-related log, remove the error, and then re-execute the command.

KEOS24231-I (C)

The application (display name = aa....aa) has already started on the logical server (logical server name = bb....bb).

aa....aa: Application display name

bb....bb: Logical server name

Description

The application is already running.

KEOS24232-I (C)

The application (display name = aa....aa) has already stopped on the logical server (logical server name = bb....bb).

aa....aa: Application display name

bb....bb: Logical server name

Description

The application has already stopped.

KEOS24233-I (C)

The application (display name = aa....aa) does not exist on the logical server (logical server name = bb....bb).

aa....aa: Application display name

bb....bb: Logical server name

Description

The application is not deployed. The application need not be un-deployed.

KEOS24234-E (C)

A J2EE application with a different format is already registered. (display name = aa....aa)

aa....aa: Application display name

Description

A J2EE application with a different format is already registered. The processing will be interrupted.

Action

Check the command execution method.

KEOS24300-I (C)

The resource (display name = aa....aa) was successfully registered.

aa....aa: Resource display name

Description

An attempt to register the resource was successful.

KEOS24301-I (C)

The resource (display name = aa....aa) was successfully unregistered.

aa....aa: Resource display name

Description

An attempt to delete the resource was successful.

KEOS24302-I (C)

The resource (display name = aa....aa) was successfully defined for the Web system (Web system name = bb....bb).

aa....aa: Resource display name

bb....bb: Web system name

Description

The resource was correlated to the Web system (resource name = aa....aa, Web system name = bb....bb).

KEOS24303-I (C)

The resource's (display name = aa....aa) definition for the Web system (Web system name = bb....bb) was successfully deleted.

aa....aa: Resource display name

bb....bb: Web system name

Description

The correlation between the resource and the Web system was deleted (resource name = aa....aa, Web system name = bb....bb).

KEOS24304-I (C)

The resource (display name = aa....aa) was successfully deployed to the logical server (logical server name = bb....bb).

aa....aa: Resource display name

bb....bb: Logical server name

Description

An attempt to deploy the resource was successful.

KEOS24305-I (C)

The resource (display name = aa....aa) was successfully undeployed from the logical server (logical server name = bb....bb).

aa....aa: Resource display name

bb....bb: Logical server name

Description

An attempt to un-deploy the resource was successful.

KEOS24306-I (C)

The resource (display name = aa....aa) on the logical server (logical server name = bb....bb) was successfully started.

aa....aa: Resource display name

bb....bb: Logical server name

Description

An attempt to start the resource was successful.

KEOS24307-I (C)

The resource (display name = aa....aa) on the logical server (logical server name = bb....bb) was successfully stopped.

aa....aa: Resource display name

bb....bb: Logical server name

Description

An attempt to stop the resource was successful.

KEOS24308-E (C)

The resource display name has not been set.

Description

The display name of the resource has not been set.

Action

Check the resource file contents.

KEOS24309-E (C)

The resource (display name = aa....aa) is already registered.

aa....aa: Resource display name

Description

The resource is already registered.

Action

Check the arguments specified in the command.

If no error exists in the command arguments and while re-registering the resource, specify the -replace option, and then re-execute the cmx_register_resource command.

KEOS24310-E (C)

The resource was not defined for the Web system (Web system name = aa....aa).

aa....aa: Web system name

Description

A resource correlated to the Web system does not exist (Web system name = aa....aa).

The processing will be interrupted.

Action

Check the arguments specified in the command.

If no error exists in the command arguments, execute the cmx_define_resource command, and then correlate the resource to the Web system.

KEOS24311-E (C)

The resource (display name = aa....aa) does not exist.

aa....aa: Resource display name

Description

The resource does not exist.

Action

Check the arguments specified in the command.

If no error exists in the command arguments, execute the cmx_register_resource command, and then register the resource.

KEOS24312-E (C)

The resource (display name = aa....aa) is already defined for the Web system (Web system name = bb....bb).

aa....aa: Resource display name

bb....bb: Web system name

Description

The resource is already correlated to the Web system (resource name = aa....aa, Web system name = bb....bb).

Action

Check the Web system information model contents and how to execute the command.

KEOS24314-E (C)

The resource (display name = aa....aa) is not defined for the Web system (Web system name = bb....bb).

aa....aa: Resource display name

bb....bb: Web system name

Description

The specified resource is not correlated to the Web system (resource name = aa....aa, Web system name = bb....bb).

Action

Check the arguments specified in the command.

If no error exists in the command arguments, execute the cmx_define_resource command, and then correlate the resource to the Web system.

KEOS24315-E (C)

The resource (display name = aa....aa) has already been deployed for the Web system (Web system name = bb....bb).

aa....aa: Resource display name

bb....bb: Web system name

Description

The resource is already deployed (resource name = aa....aa, Web system name = bb....bb).

Action

Check the arguments specified in the command.

If no error exists in the command arguments, un-deploy the resource, and then re-execute the command.

KEOS24316-E (C)

The resource (display name = aa....aa) has not been deployed to the logical server (logical server name = bb....bb).

aa....aa: Resource display name

bb....bb: Logical server name

Description

The resource has not been deployed.

Action

Check the arguments specified in the command.

If no error exists in the command arguments, deploy the resource, and then re-execute the command.

KEOS24317-E (C)

An attempt to deploy the resource (display name = aa....aa) to the logical server (logical server name = bb....bb) has failed.

aa....aa: Resource display name

bb....bb: Logical server name

Description

An attempt to deploy the resource has failed.

Action

Examine the log file of the Management Server, check the resource operations-related log, remove the error, and then re-execute the command.

KEOS24318-E (C)

An attempt to undeploy the resource (display name = aa....aa) from the logical server (logical server name = bb....bb) has failed.

aa....aa: Resource display name

bb....bb: Logical server name

Description

An attempt to un-deploy the resource has failed.

Action

Examine the log file of the Management Server, check the resource operations-related log, remove the error, and then re-execute the command.

KEOS24319-E (C)

The system is busy. (logical server name = aa....aa, resource display name = bb....bb)

aa....aa: Logical server name

bb....bb: Resource display name

Description

The operations cannot be executed because other operations are being executed for the resource.

Action

Terminate other operations, and then re-execute the operation.

KEOS24320-I (C)

The resource (deployed resource display name = aa....aa) has already been deployed. (resource display name = bb....bb)

aa....aa: Resource display name (imported)

bb....bb: Resource display name

Description

The resource is already deployed.

KEOS24321-I (C)

The resource (display name = aa....aa) has already started on the logical server (logical server name = bb....bb).

aa....aa: Resource display name

bb....bb: Logical server name

Description

The resource has already started.

KEOS24322-I (C)

The resource (display name = aa....aa) has already stopped on the logical server (logical server name = bb....bb).

aa....aa: Resource display name

bb....bb: Logical server name

Description

The resource has already stopped.

KEOS24323-E (C)

An attempt to start the resource (display name = aa....aa) on the logical server (logical server name = bb....bb) has failed.

aa....aa: Resource display name

bb....bb: Logical server name

Description

An attempt to start the resource has failed.

Action

Examine the log file of the Management Server, check the resource operations-related log, remove the error, and then re-execute the command.

KEOS24324-E (C)

An attempt to stop the resource (display name = aa....aa) on the logical server (logical server name = bb....bb) has failed.

aa....aa: Resource display name

bb....bb: Logical server name

Description

An attempt to stop the resource has failed.

Action

Examine the log file of the Management Server, check the resource operations-related log, remove the error, and then re-execute the command.

KEOS24325-I (C)

The resource (display name = aa....aa) does not exist on the logical server (logical server name = bb....bb).

aa....aa: Resource display name

bb....bb: Logical server name

Description

The resource does not exist.

KEOS24326-E (C)

The specified file is invalid. file name = aa....aa

aa....aa: File name

Description

An invalid file is specified.

The processing will be interrupted.

Action

Check the file contents.

KEOS24401-I (C)

The operation on the Web system (Web system name = aa....aa) was successful.

aa....aa: Web system name

Description

The operation on the Web system was successful.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

KEOS24402-W (C)

The operation on the Web system (Web system name = aa....aa) was partially successful.

aa....aa: Web system name

Description

The operation on the Web system was partially successful.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

Action

Examine the log file of the Management Server, remove the error, and then re-execute the command.

KEOS24403-E (C)

The attempted operation on the Web system (Web system name = aa....aa) has failed.

aa....aa: Web system name

Description

The attempted operation on the Web system has failed.

Note that if the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

Action

Examine the log file of the Management Server, remove the error, and then re-execute the command.

KEOS24404-I (C)

The operation on the unit (Web system name = aa....aa, unit name = bb....bb) was successful.

aa....aa: Web system name

bb....bb: Service unit name

Description

The operation on the service unit was successful.

KEOS24405-E (C)

The attempted operation on the unit (Web system name = aa....aa, unit name = bb....bb) has failed.

aa....aa: Web system name

bb....bb: Service unit name

Description

The attempted operation of the service unit has failed.

Action

Examine the log file of the Management Server, remove the error, and then re-execute the command.

KEOS24406-I (C/F)

The operation was executed successfully.

Description

The operation was executed successfully.

KEOS24407-E (C/F)

An attempt to execute the operation has failed.

Description

An attempt to execute the operation has failed.

KEOS24408-E (C/F)

An attempt to build the model of Web systems has failed.

Description

An attempt to build the Web system information model has failed.

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file, and then re-execute the operation.

KEOS24409-E (C/F)

An attempt was made to modify unmodifiable definitions of Web system.

Description

An attempt was made to modify unmodifiable tags and parameters of the Web system.

The processing will be interrupted.

Action

Check the Web system contents in the Easy Setup definition file, and re-execute the operation.

KEOS24410-E (C/F)

An attempt was made to modify unmodifiable definitions of host.

Description

An attempt was made to modify unmodifiable tags in the host definition.

The processing will be interrupted.

Action

Check the contents of host definition in the Easy Setup definition file, and re-execute the operation.

KEOS24411-E (C/F)

An attempt to modify definitions of the Web system (Web system name = aa....aa) has failed.

aa....aa: Web system name

Description

An attempt to change tags and parameters of the Web system has failed.

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file, and then re-execute the operation.

KEOS24412-E (C/F)

An attempt to build the Web system (Web system name = aa....aa) has failed.

aa....aa: Web system name

Description

An attempt to build the Web system has failed.

The processing will be interrupted.

Action

If an Easy Setup definition file is specified, check the contents of the Easy Setup definition file, and then re-execute the operation.

If a Web system name is specified, check the registered Web system information model.

KEOS24500-E (C)

The logical server or host not linked to the Web system is not registered.

Description

The logical server or host not linked to the Web system is not registered.

The processing will be interrupted.

Action

Check the command execution method.

KEOS24501-I (C)

A logical server or host not linked to the Web system was deleted successfully.

Description

An attempt to delete the logical server and host not linked to the Web system was successful.

KEOS24502-E (C)

An attempt to change the model has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to change the model has failed. (details = aa....aa).

The processing will be interrupted.

Action

Check the contents of the Easy Setup definition file based on the detailed information described in the following table:

Table 13‒2: List of detailed information of errors described in KEOS24502-E

Details

Description

Action

The Web system does not exist. (Web system name = aa....aa)

aa....aa: Web system name

The Web system does not exist (Web system name = aa....aa)#.

Make sure that the specified Web system is registered in the model.

The number of tiers in the Web system does not match the number of tiers in the model. (Web system name = aa....aa)

aa....aa: Web system name

The number of tiers in the Web system is not matching (Web system name = aa....aa)#.

Make sure that tiers are not added or deleted from the specified Web system.

The tier type cannot be changed. (tier type = aa....aa, Web system name = bb....bb)

aa....aa: Tier type

bb....bb: Web system name

The tier type cannot be changed (Tier type = aa....aa, Web system name = bb....bb)#.

Make sure that the specified tier is registered in the model.

The number of J2EE servers for the tier cannot be changed. (tier type = aa....aa, Web system name = bb....bb)

aa....aa: Tier type

bb....bb: Web system name

The number of J2EE servers for the tier cannot be changed (Tier type = aa....aa, Web system name = bb....bb).

Make sure that the number of J2EE servers for the specified tier is not changed.

The number of units in the Web system does not match the number of units in the model. (Web system name = aa....aa)

aa....aa: Web system name

The number of units in the Web system is not matching (Web system name = aa....aa).

Make sure that units are not added or deleted from the specified Web system.

The unit does not exist. (unit name = aa....aa, Web system name = bb....bb)

aa....aa: Unit name

bb....bb: Web system name

The unit does not exist (Unit name = aa....aa, Web system name = bb....bb).

Make sure that the specified unit name is registered in the model.

The number of hosts in the unit does not match the number of hosts in the model. (unit name = aa....aa, Web system name = bb....bb)

aa....aa: Unit name

bb....bb: Web system name

The number of hosts in the unit is not matching (Unit name = aa....aa, Web system name = bb....bb)#.

Make sure that hosts are not added or deleted from the specified unit.

The host specified in the unit does not exist. (unit name = aa....aa, host name = bb....bb, Web system name = cc....cc)

aa....aa: Unit name

bb....bb: Host name

cc....cc: Web system name

The host specified in the unit does not exist (Unit name = aa....aa, host name = bb....bb, Web system name = cc....cc)#.

Make sure that the specified host is registered in the model.

The specified logical server does not exist. (logical server name = aa....aa, Web system name = bb....bb)

aa....aa: Logical server name

bb....bb: Web system name

The specified logical server does not exist (Logical server name = aa....aa, Web system name = bb....bb)#.

Make sure that the specified logical server is registered in the model.

The logical server name cannot be changed. (host name = aa....aa, Web system name = bb....bb)

aa....aa: Host name

bb....bb: Web system name

The logical server name cannot be changed (Host name = aa....aa, Web system name = bb....bb).

Make sure that the specified logical server is registered in the model.

The number of logical servers cannot be changed. (Web system name = aa....aa)

aa....aa: Web system name

The number of logical servers cannot be changed (Web system name = aa....aa)#.

Make sure that the definitions of the logical server are not added or deleted.

The load balancer definition cannot be changed. (Web system name = aa....aa)

aa....aa: Web system name

The load balancer definition cannot be changed (Web system name = aa....aa).

Make sure that the definition of the LoadBalancer tag is not changed from the definition file used when the previous system was built.

The host does not exist. (host name = aa....aa)

aa....aa: Host name

The host does not exist (Host name = aa....aa).

Make sure that the specified host is registered in the model.

The definition of the administration agent cannot be changed. (host name = aa....aa)

aa....aa: Host name

The definition of the host agent cannot be changed (Host name = aa....aa).

Make sure that the definition of the host agent is not changed from the definition file used when the previous system was built.

# If the logical server defined in the management portal or the Smart Composer free-tier is to be processed, no-name is output to the Web system name.

KEOS24503-E (C)

An enabled In-process HTTP server cannot be disabled. (Web system name = aa....aa, parameter = bb....bb)

aa....aa: Web system name

bb....bb: Parameter

Description

You cannot disable an enabled in-process HTTP server.

The processing will be interrupted.

Action

Check the specified parameter bb....bb.

KEOS24504-E (C)

An error occurred in the starting process of the previous level. (Web system name = aa....aa, logical server name = bb....bb)

aa....aa: Web system name

bb....bb: Logical server name

Description

An error occurred in the starting process of the previous level, and therefore, the corresponding logical server cannot be started.

The processing will be interrupted.

Action

Check that the setup information of the logical server, which is failed to start first, is distributed.

See the detailed information and the Management Agent log, remove the errors, and then re-execute the process.

KEOS24505-W (C)

An attempt to verify the configuration file failed. (Web system name = aa....aa, unit name = bb....bb, logical server name = cc....cc, details = dd....dd)

aa....aa: Web system name

bb....bb: Unit name

cc....cc: Logical server name

dd....dd: Details

Description

An attempt to verify the configuration file failed.

The processing continues.

Action

Check the logical server settings, and then re-execute the operation.

KEOS24506-W (C/F)

Specified value is duplicated. (Web system name = aa....aa, parameter name = bb....bb, parameter value = cc....cc)

aa....aa: Web system name

bb....bb: Parameter name

cc....cc: Parameter value

Description

Specified value is duplicated.

The changes are ignored and the processing continues.

Action

Correct the definition file so that the specified value of the relevant parameter is not duplicated, and then re-execute the operation.

KEOS24507-W (C/F)

The specified J2EE server was not found. (logical server name = aa....aa, parameter name = bb....bb, parameter value = cc....cc)

aa....aa: Logical server name

bb....bb: Parameter name

cc....cc: Parameter value

Description

The specified J2EE server was not found.

The error will be ignored, and then the processing continues.

Action

Correct the logical server name of the specified J2EE server, and then re-execute the operation.

KEOS24508-W (C/F)

There is a correlation error in the setting values of the parameters. (logical server name = aa....aa, parameter name 1 = bb....bb, parameter value 1 = cc....cc, parameter name 2 = dd....dd, parameter value 2 = ee....ee, parameter name 3 = ff....ff, parameter value 3 = gg....gg)

aa....aa: Logical server name

bb....bb: Parameter name 1

cc....cc: Parameter value 1

dd....dd: Parameter name 2

ee....ee: Parameter value 2

ff....ff: Parameter name 3

gg....gg: Parameter value 3

Description

A correlation error between parameter 2 and parameter 3 (such as errors related to maximums or minimums) exists in the value of parameter 1. The error is ignored and processing continues.

Action

Revise the set value of the parameter specified in the configuration tag, and then change the Web system configuration.

KEOS24700-I (F)

Connecting to the load balancer of aa....aa will now start.

aa....aa: IP address of load balancer

Description

The load balancer will be connected.

KEOS24701-I (F)

The connection to the load balancer of aa....aa was terminated.

aa....aa: IP address of load balancer

Description

The load balancer will be disconnected.

KEOS24710-I (F)

Sending the following command to the load balancer of aa....aa will now start: script-name=[bb....bb], command-name=[cc....cc], command=[dd....dd]

aa....aa: IP address of load balancer

bb....bb: Script name

cc....cc: Command name

dd....dd: Command

Description

A command will be sent to the load balancer.

KEOS24711-I (F)

Output of the previous command was received from the load balancer of aa....aa: [bb....bb]

aa....aa: IP address of load balancer

bb....bb: Output of command

Description

The output of the command was received from the load balancer.

KEOS26000-I (F)

The management event sending function has started.

Description

The management event sending function has started.

The processing continues.

KEOS26001-I (F)

The management event sending function has stopped.

Description

The management event sending function has stopped.

The processing continues.

KEOS26002-E (F)

An attempt to start the management event sending function has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to start the management event sending function has failed.

The processing continues.

Action

See the detailed information, and then revise the operating environment and settings.

KEOS26010-E (F)

An attempt to read the settings file has failed. (file = aa....aa)

aa....aa: File name

Description

An attempt to read the property file or message ID list file for Management event invocation has failed.

The processing continues, but the Management event will not be issued.

Action

Confirm that the settings file exists, check the specified contents and access permissions, and then restart the J2EE server.

KEOS26011-E (F)

A required property (aa....aa) is not specified.

aa....aa: Property key

Description

The necessary properties are not specified in the Management event issue properties file.

The operations of the Management event issue function will stop.

Action

Revise the contents of the Management event issue properties file.

KEOS26012-E (F)

The specified property (aa....aa) is invalid.

aa....aa: Property key

Description

The contents specified in the Management event issue properties file are invalid.

Action

Revise the contents of the Management event issue properties file.

KEOS26013-E (F)

The message ID was not specified.

Description

The contents specified in the Management event issue message ID list file are invalid.

The operations of the Management event issue function will stop.

Action

Revise the contents of the Management event issue message ID list file.

KEOS26014-W (F)

The specified property (aa....aa) is invalid. The default value (bb....bb) will be used.

aa....aa: Property key

bb....bb: Default value

Description

The contents specified in the Management event issue properties file are invalid.

The operations of the Management event issue function will continue using the default value.

Action

Revise the contents of the Management event issue properties file.

KEOS26050-I (F)

The management event was sent successfully. (message ID = aa....aa, occurred time = bb....bb, optional information = cc....cc)

aa....aa: Message ID

bb....bb: Management event request time

cc....cc: Additional information (demarcate with colon if there is one or more additional information)

Description

The management event was sent successfully.

KEOS26051-E (F)

An attempt to send the management event has failed. (message ID = aa....aa, occurred time = bb....bb, optional information = cc....cc, details = dd....dd)

aa....aa: Message ID

bb....bb: Management event request time

cc....cc: Additional information (demarcate with colon if there is one or more additional information)

dd....dd: Details

Description

An attempt to send the management event has failed.

The processing continues. If the resend settings are specified, an attempt will be made to resend the Management event.

The possible causes are as follows:

The Management Server described in the settings file is not running.

An error or temporary load occurred in the network.

Action

See the detailed information, and then revise the operating environment and the contents of the Management event issue properties file.

KEOS26052-E (F)

The management event could not be sent. (details = aa....aa)

aa....aa: Details

Description

The management event could not be sent.

The operations of the Management event issue function will stop.

Action

See the detailed information, and then revise the operating environment and the contents of the Management event issue properties file.

KEOS26053-W (F)

The retry limit for sending management events was exceeded. (message ID = aa....aa, occurred time = bb....bb, optional information = cc....cc)

aa....aa: Message ID

bb....bb: Management event request time

cc....cc: Additional information (demarcate with colon if there is one or more additional information)

Description

The retry limit for sending management events was exceeded.

The applicable Management event will be destroyed.

Action

Revise the operating environment and the contents of the Management event issue properties file.

KEOS26054-W (F)

The management events could not be sent, because the maximum number of simultaneous send operations was exceeded. (message ID = aa....aa, optional information = bb....bb)

aa....aa: Message ID

bb....bb: Additional information (demarcate with colon if there is one or more additional information)

Description

The maximum number of concurrently-issued Management events was exceeded.

The applicable Management event will be destroyed.

Action

Revise the operating environment and the contents of the Management event issue properties file.

KEOS26100-E (F)

An internal error occurred. (details = aa....aa)

aa....aa: Details

Description

An internal error occurred in the Management event issue functionality.

The operations of the Management event issue functionality will continue if possible, and will terminate if operations cannot be continued.

Action

If the error cannot be removed even after restarting the J2EE server, contact maintenance personnel.

KEOS26500-E (F)

An attempt to initialize the management action has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to initialize the management action has failed.

The processing continues, but the Management action will not run.

Action

See the detailed information, and then revise the operating environment and the contents of the settings file.

KEOS26510-I (F)

A management event was received. (logical server name = aa....aa, message ID = bb....bb, optional information = cc....cc, occurred time = dd....dd)

aa....aa: Logical server name

bb....bb: Message ID

cc....cc: Additional information (demarcate with colon if there is one or more additional information)

dd....dd: Event issuing time

Description

A management event was received.

KEOS26520-W (F)

The management action was not defined. (logical server name = aa....aa, message ID = bb....bb)

aa....aa: Logical server name

bb....bb: Message ID

Description

The management action was not defined.

The processing continues.

Action

Revise the settings of the Management action.

KEOS26521-E (F)

The definition of the management action is invalid. (management action ID = aa....aa)

aa....aa: Management action ID

Description

The definition of the management action is invalid.

The processing continues.

Action

Revise the settings of the Management action.

KEOS26522-W (F)

A management event had already been received. (logical server name = aa....aa, message ID = bb....bb, optional information = cc....cc, occurred time = dd....dd)

aa....aa: Logical server name

bb....bb: Message ID

cc....cc: Additional information (demarcate with colons if there is one or more additional information)

dd....dd: Original event issuing time when the management event was requested

Description

The Management event that was received has already been received.

The processing continues without executing the Management action.

The causes for the error may be duplicate sending of Management events due to temporary load and network error.

Action

Revise the operating environment or the contents of the following settings files:

Management event issue properties file

- manager.mevent.send.timeout

- manager.mevent.retry.limit

KEOS26523-W (F)

The oldest receiving information of management event is deleted, because the number of receiving information exceeded the maximum number. (maximum number = aa....aa, deleted receiving information = [bb....bb])

aa....aa: Maximum number of stored receiving information

bb....bb: Receiving information to be deleted

Description

The oldest receiving information of management event is deleted, because the number of receiving information exceeded the maximum number.

The processing continues.

Multiple Management events may have been issued.

Action

Revise the operating environment or the contents of the following settings files:

Management action execution properties file

- maction.mevent.receiving_info.keep_size.max

KEOS26530-I (F)

The management action will now be executed. (management action ID = aa....aa)

aa....aa: Management action ID

Description

The management action will now be executed.

The processing continues.

KEOS26531-I (F)

The management action execution has finished. (management action ID = aa....aa, exit code = bb....bb)

aa....aa: Management action ID

bb....bb: Exit code

Description

The management action execution has finished.

The processing continues.

KEOS26532-W (F)

The management action execution has exceeded the timeout limit. (management action ID = aa....aa)

aa....aa: Management action ID

Description

The management action execution has exceeded the timeout limit.

The processing continues.

Action

Revise the settings of the Management action.

KEOS26533-E (F)

An attempt to execute the management action has failed. (management action ID = aa....aa, details = bb....bb)

aa....aa: Management action ID

bb....bb: Detailed message

Description

An attempt to execute the management action has failed.

The processing continues.

Action

See the detailed information, and then revise the operating environment and the contents of the settings file.

KEOS26534-W (F)

Execution of management action was controlled because execution was requested during a lock period. (management action ID = aa....aa)

aa....aa: Management action ID

Description

Execution of management action was controlled because execution was requested during a lock period. The processing continues without executing the Management action.

Action

If this problem occurs frequently, revise the operating environment and the contents of the settings file.

KEOS26535-W (F)

Execution of management action was controlled because the maximum number of simultaneous executions was exceeded. (management action ID = aa....aa)

aa....aa: Management action ID

Description

The execution of the Management action was controlled by limiting the concurrently executing Management actions. The processing continues without executing the Management action.

Action

If this problem occurs frequently, revise the operating environment and the contents of the settings file.

KEOS26600-E (F)

An internal error occurred. (details = aa....aa)

aa....aa: Details

Description

An internal error occurred in the Management action execution function.

The operations of the Management Server will continue if possible, and will terminate if operations cannot be continued.

Action

If the error cannot be removed even after restarting the Management Server, contact maintenance personnel.

KEOS27000-I (F)

Authentication was successful. (user ID = aa....aa)

aa....aa: User ID

Description

Authentication was successful.

KEOS27001-E (F)

Authentication failed. An administrator's user ID or a password is incorrect. (userID = aa....aa)

aa....aa: User ID

Description

An attempted authentication has failed. An administrator's user ID or a password is incorrect. The processing will be interrupted.

Action

Enter the correct administrator user ID or password.

KEOS27002-E (F)

Authentication failed. Authentication request expired. (userID=aa....aa)

aa....aa: User ID

Description

An attempted authentication has failed. Authentication request expired. The processing will be interrupted.

Action

Review the operating environment if the error occurs frequently. The possible causes are as follows:

The network is highly loaded.

The computer is highly loaded.

KEOS27010-I (F)

The external MBean was successfully registered. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)

aa....aa: Class name

bb....bb: Object name

cc....cc: File name

dd....dd: Definition order

Description

An attempt to register an external Mbean was successful.

KEOS27011-I (F)

The external MBean was successfully unregistered. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)

aa....aa: Class name

bb....bb: Object name

cc....cc: File name

dd....dd: Definition order

Description

An attempt to cancel the registration of the external Mbean was successful.

KEOS27012-E (F)

An attempt to read the MBean plug-in definition file (aa....aa) has failed.

aa....aa: File name

Description

An attempt to read the Mbean plug definition file has failed. The registration process of the external Mbean will be interrupted.

Action

Check the read permission of the Mbean plug definition file.

KEOS27013-E (F)

The MBean plug-in definition file is invalid. file name = aa....aa line number = bb....bb column number = cc....cc details = dd....dd

aa....aa: File name

bb....bb: Line number

cc....cc: Column number

dd....dd: Details number

Description

An attempt to parse the external Mbean plugin definition file has failed. The registration process of the external Mbean will be interrupted.

Action

Check the contents of the Mbean plugin definition file.

KEOS27014-E (F)

An object name that is invalid in external MBean has been specified. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)

aa....aa: Class name

bb....bb: Object name

cc....cc: File name

dd....dd: Definition order

Description

An attempt to register the external Mbean has failed. An invalid object name is specified. The proceeding the registration process of the external Mbean will continue.

Action

Specify a valid object name.

KEOS27015-E (F)

An external MBean class was not found. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)

aa....aa: Class name

bb....bb: Object name

cc....cc: File name

dd....dd: Definition order

Description

An attempt to register the external Mbean has failed. Class implementation could not be found. The proceeding the registration process of the external Mbean will continue.

Action

Check that the external JAR file supporting Mbean plug-in definition files exists. Specify a valid object name.

KEOS27016-E (F)

An attempt to create an external MBean instance has failed. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)

aa....aa: Class name

bb....bb: Object name

cc....cc: File name

dd....dd: Definition order

Description

An attempt to register the external Mbean has failed. An attempted instance generation has failed. The proceeding the registration process of the external Mbean will continue.

Action

Contact maintenance personnel.

KEOS27017-E (F)

The external MBean is already registered. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)

aa....aa: Class name

bb....bb: Object name

cc....cc: File name

dd....dd: Definition order

Description

An attempt to register the external Mbean has failed. An already registered object name is specified. The proceeding the registration process of the external Mbean will continue.

Action

Check that an MBean plug-in definition file with the same contents exists.

KEOS27018-E (F)

An attempt to register an external MBean has failed. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd, details = An exception was thrown by the MBeanRegistration#preRegister method.)

aa....aa: Class name

bb....bb: Object name

cc....cc: File name

dd....dd: Definition order

Description

An attempt to register the external Mbean has failed. An exception was thrown in the MBeanRegistration#preRegister method. The proceeding the registration process of the external Mbean will continue.

Action

Contact maintenance personnel.

KEOS27019-E (F)

The external MBean is not a JMX compliant MBean. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd)

aa....aa: Class name

bb....bb: Object name

cc....cc: File name

dd....dd: Definition order

Description

An attempt to register the external Mbean has failed. An Mbean not complying with JMX was specified. The proceeding the registration process of the external Mbean will continue.

Action

Contact maintenance personnel.

KEOS27020-E (F)

An attempt to unregister the external MBean has failed. (class name = aa....aa, object name = bb....bb, file name = cc....cc, definition order = dd....dd, details = An exception was thrown by the MBeanRegistration#preDeregister method.)

aa....aa: Class name

bb....bb: Object name

cc....cc: File name

dd....dd: Definition order

Description

An attempt to cancel the registration of an external Mbean has failed. An exception was thrown in the MBeanRegistration#preRegister method. The proceeding the registration process of the external Mbean will continue.

Action

Contact maintenance personnel.

KEOS27021-E (F)

The MBean plug-in definition file is invalid. file name = aa....aa details = bb....bb

aa....aa: File name

bb....bb: Detailed message

Description

An analysis error occurred in the Mbean plug-in function. The registration process of the external Mbean will be interrupted.

Action

Contact maintenance personnel.

KEOS27030-I (F)

The manager remote access function has started.

Description

The Manager Server remote access function has started.

KEOS27031-I (F)

The manager remote access function has stopped.

Description

The Manager Server remote access function has stopped.

KEOS27032-I (F)

The external connection function of the manager remote access function has started.

Description

The external connection function of the Management Server remote access function has started.

KEOS27033-I (F)

The external connection function of the manager remote access function has stopped.

Description

The external connection function of the Management Server remote access function has stopped.

KEOS27034-E (F)

An attempt to start the external connection function of the manager remote access function has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to start the external connection function of the Management Server remote access function has failed. The processing continues.

Action

Check the contents of the settings file, and then restart the Management Server.

KEOS27040-E (C)

A communication error occurred.

Description

An error occurred while communicating with the Administration Agent. The processing will be interrupted.

Action

Check the contents of the settings file, and then restart the Management Server.

KEOS27099-E (F)

An internal error occurred. (details = aa....aa)

aa....aa: Details

Description

An internal error occurred in the Mbean server function. The processing continues.

Action

If the error cannot be removed even after restarting the Management Server, contact maintenance personnel.

KEOS27101-E (V)

Authentication failed. An administrator's user ID or a password is incorrect.

Description

An attempted authentication has failed. An administrator's user ID or a password is incorrect. The processing will be interrupted.

Action

Enter the correct administrator user ID or password.

KEOS27102-E (V)

Authentication failed. Authentication request expired.

Description

An attempted authentication has failed. Authentication request expired. The processing will be interrupted.

Action

Review the operating environment if the error occurs frequently. The possible causes are as follows:

The network is highly loaded.

The computer is highly loaded.

KEOS27103-E (V)

An internal error occurred. Detail=aa....aa

aa....aa: Details

Description

An internal error occurred. The processing will be interrupted.

Action

If the error cannot be removed even after restarting the Management Server, contact maintenance personnel.

KEOS27105-E (V)

An error occurred while connecting to the RMI registry. Detail=aa....aa

aa....aa: Details

Description

An error occurred while connecting to the RMI registry. The processing will be interrupted.

Action

See the detailed information, and then revise the operating environment and the contents of the settings file.

Is the Management Server running?

Are the specified host name and the port number invalid?

KEOS27106-E (V)

An error occurred during JMXConnector generation. Detail=aa....aa

aa....aa: Details

Description

An error occurred during JMXConnector generation. The processing will be interrupted.

Action

See the detailed information, and then revise the operating environment and the contents of the settings file.

Is the Management Server running?

Are the specified host name and the port number invalid?

KEOS28001-I (F)

The Setup Wizard (aa....aa) has started.

aa....aa: GUI/CUI

Description

The Setup Wizard has started.

KEOS28002-I (F)

The Setup Wizard (aa....aa) has ended.

aa....aa: GUI/CUI

Description

The Setup Wizard has ended.

KEOS28003-E (C/F)

An error occurred in the Setup Wizard (aa....aa). (details = bb....bb)

aa....aa: GUI/CUI

bb....bb: Detailed message

Description

An error occurred in the Setup Wizard.

The processing will be interrupted.

Action

See details, remove the cause of the error, and then re-execute the Setup Wizard.

Table 13‒3: List of the detailed information in KEOS28003-E

Details

Description

Action

An I/O error occurred in the lock file for mutual exclusion. file name = aa....aa, details = bb....bb

An I/O error occurred in the lock file for exclusion. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Detailed message

An I/O error occurred in the lock file for mutual exclusion.

The processing will be interrupted.

Contact maintenance personnel.

KEOS28004-I (F)

The setup has started.

Description

The setup has started.

KEOS28005-I (F)

The setup has ended.

Description

The setup has ended.

KEOS28006-E (F)

An error occurred in the setup.

Description

An error occurred during the setup process.

The processing will be interrupted.

Action

See the action for the error-level message that is output before this message.

KEOS28007-I (F)

The unsetup has started.

Description

The unsetup process has started.

KEOS28008-I (F)

The unsetup has ended.

Description

The unsetup process has ended.

KEOS28009-E (F)

An error occurred in the unsetup.

Description

An error occurred during the unsetup process.

The processing will be interrupted.

Action

See the action for the error-level message that is output before this message.

KEOS28010-I (F)

Command execution has started. (command = aa....aa)

aa....aa: Command name

Description

The Setup Wizard has executed the command.

KEOS28011-I (F)

Command execution has ended. (command = aa....aa, exit code = bb....bb)

aa....aa: Command name

bb....bb: Exit code

Description

The command executed by the Setup Wizard has ended.

KEOS28012-E (C/F)

An error occurred during command execution. (command = aa....aa, details = bb....bb)

aa....aa: Command name

bb....bb: Detailed message

Description

An error occurred in the command executed by the Setup Wizard.

The processing will be interrupted.

Action

See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard. If one of the following messages is output in the detailed information, re-execute the Setup Wizard:

hwsserveredit: cannot delete

KDJE40028-E The deletion of the J2EE server has failed. Server name = aa....aa, Reason = Deletion of file failed

aa....aa: Server name

KEOS28014-E (C/F)

An error occurred during an attempt to access the file. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Detailed message

Description

An error occurred while accessing to the file from the Setup Wizard.

The processing will be interrupted.

Action

See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.

KEOS28015-I (F)

The setup information file has been output. (file name = aa....aa)

aa....aa: File name

Description

The setup information file is output.

KEOS28016-I (F)

The setup information list has been output. (file name = aa....aa)

aa....aa: File name

Description

The setup information list is output.

KEOS28017-I (F)

Collection of the snapshot log files has started.

Description

The Setup Wizard has started collecting the snapshot log.

KEOS28018-I (F)

Collection of the snapshot log files has ended. (file name = aa....aa)

aa....aa: File name

Description

The collection of the snapshot log by the Setup Wizard has ended.

KEOS28019-E (C/F)

An error occurred during collection of the snapshot log files. (details = aa....aa)

aa....aa: Details

Description

An error occurred in the collection of the snapshot log by the Setup Wizard.

The processing will be interrupted.

Action

Contact maintenance personnel.

KEOS28020-I (F)

Backup has started.

Description

The Setup Wizard has started the backup process.

KEOS28021-I (F)

Backup has ended.

Description

The backup process in the Setup Wizard has ended.

KEOS28022-E (C/F)

An error occurred during backup. (details = aa....aa)

aa....aa: Details

Description

An error occurred during the backup process in the Setup Wizard.

The processing will be interrupted.

Action

Contact maintenance personnel.

KEOS28023-I (F)

The port number check has started.

Description

The port number check has started in the setup.

KEOS28024-I (F)

The port number check has ended.

Description

The port number check has ended in the setup.

KEOS28025-I (F)

The Component Container administrator has been changed.

Description

The Component Container administrator was changed in the setup.

KEOS28026-E (C/F)

An error occurred during an attempt to change the Component Container administrator. (details = aa....aa)

aa....aa: Details

Description

An error occurred during an attempt to change the Component Container administrator in the setup.

The processing will be interrupted.

Action

See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.

KEOS28027-E (C)

An instance of the Setup Wizard is already running.

Description

The Setup Wizard cannot be started because the Setup Wizard is already running for some another process on the same machine.

The processing will be interrupted.

Action

Stop the running Setup Wizard.

KEOS28028-E (C/F)

The setup cannot be executed by the Setup Wizard, because it has already done by a utility other than the Setup Wizard.

Description

The Setup Wizard cannot be started because the Management Server is already set up using another method.

The processing will be interrupted.

Action

Delete the entire Application Server environment, and then re-install the Management Server.

KEOS28029-E (C/F)

The setup information file does not exist. (file name = aa....aa)

aa....aa: File name

Description

The specified setup information file does not exist.

The processing will be interrupted.

Action

Revise file name or path of the setup information file.

KEOS28030-E (C/F)

The setup information file is corrupted. (file name = aa....aa)

aa....aa: File name

Description

The specified setup information file has corrupted.

The processing will be interrupted.

Action

Check the specified file.

KEOS28031-E (C/F)

A specified command option is invalid. (details = aa....aa)

aa....aa: Details

Description

The specified command option is invalid.

The processing will be interrupted.

Action

Revise command options.

Table 13‒4: List of the detailed information in KEOS28031-E

Details

Description

Action

The same option is specified more than once. Option = aa....aa

The same option has been specified more than once. (option = aa....aa)

aa....aa: Option

The same option is specified more than once in the command option.

The processing will be interrupted.

Revise command options.

A value was not specified for the option. Option = aa....aa

An option value is not specified. (option = aa....aa)

aa....aa: Option

A value was not specified for the option.

The processing will be interrupted.

Revise command options.

An invalid option is specified. Option = aa....aa

An invalid option is specified. (option = aa....aa)

aa....aa: Option

An invalid option is specified.

The processing will be interrupted.

Revise command options.

The option aa....aa and the option bb....bb cannot be specified simultaneously.

The option aa....aa and the option bb....bb cannot be specified simultaneously.

aa....aa: Option 1

bb....bb: Option 2

Option that cannot be specified at the same time is specified.

The processing will be interrupted.

Revise command options.

A required option is not specified. Option = aa....aa

A required option is not specified. (option = aa....aa)

aa....aa: Option

A required option is not specified.

The processing will be interrupted.

Revise command options.

KEOS28032-E (C/F)

The Setup Wizard was forced to terminate.

Description

The Setup Wizard was terminated forcibly.

The processing will be interrupted.

Action

Re-execute the Setup Wizard. Restart the OS, if an error occurs even after re-executing the Setup Wizard.

KEOS28033-E (C)

Usage :

setupwizard

setupwizard -f <setup information file> [-force]

setupwizard -f <setup information file> -md <definition file> [-force]

setupwizard -export -omd <definition file>

setupwizard -view -f <setup information file>

setupwizard -clean [-force]

setupwizard -h | -help

Description

The method of starting the command is incorrect. The command execution will be suspended.

Action

Enter the correct command, and then re-execute the command.

KEOS28034-E (C/F)

A value from 1024 to 65535 must be specified because aa....aa has been specified for the Component Container administrator. (bb....bb=cc....cc)

aa....aa: Component Container administrator

bb....bb: Corresponding item

cc....cc: Port number

Description

A user other than root has been specified for the Component Container administrator, and therefore, a value outside the range of 1024 to 65535 cannot be specified in the port number.

The processing will be interrupted.

Action

If a user other than root has been specified for the Component Container administrator, specify a value in the range of 1024 to 65535 in the port number.

KEOS28035-E (C/F)

A duplicate port number is specified. (port number = aa....aa, duplicate item = bb....bb)

aa....aa: Port number

bb....bb: Duplicate item

Description

A duplicate port number is specified in the Setup Wizard, and therefore, the setup cannot be started.

The processing will be interrupted.

Action

Revise the port number specified in the Setup Wizard.

KEOS28036-E (C/F)

This version(aa....aa) does not support the specified setup information file. (file name = bb....bb, file version = cc....cc)

aa....aa: Application server version

bb....bb: File name

cc....cc: Application Server version in which the file is created

Description

The setup cannot be executed with the setup information file having version later than that of the Setup Wizard version.

The processing will be interrupted.

Action

Check the specified file.

KEOS28037-E (C/F)

The Cosminexus environment is corrupted. (details = aa....aa)

aa....aa: Details

Description

Cannot continue processing because the Application Server environment has corrupted.

The processing will be interrupted.

Action

Contact maintenance personnel.

KEOS28038-E (C/F)

An attempt to start the Setup Wizard has failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to start the Setup Wizard has failed.

The processing will be interrupted.

Action

If the following message is output in the detailed information, revise the log settings for the Setup Wizard definition file:

Failed to initialize trace file.

Failed to make directory

For other than the above-mentioned cases, contact maintenance personnel.

KEOS28040-I (F)

The Management Server administrator's group has been changed.

Description

The Setup Wizard modified the Management Server administrator group.

KEOS28041-E (C/F)

An error occurred during an attempt to change the Management Server administrator's group. (details = aa....aa)

aa....aa: Details

Description

An error occurred during an attempt to modify the Management Server administrator group by the Setup Wizard.

The processing will be interrupted.

Action

See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.

KEOS28042-E (C/F)

An error occurred during analysis of the simple configuration definition file. (file name = aa....aa)

aa....aa: File name

Description

An error occurred during the analysis of the Easy Setup definition file. A cording error exists in the Easy Setup definition file.

The processing will be interrupted.

Action

See the message displayed after this message, remove the cause of error, and then re-execute the Setup Wizard.

KEOS28043-E (C/F)

A syntax error exists in the simple configuration definition file. (line number = aa....aa, column number = bb....bb, details = cc....cc)

aa....aa: Line number

bb....bb: Column number

cc....cc: Details

Description

A syntax error exists in coding of the Easy Setup definition file.

The processing will be interrupted.

Action

See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.

KEOS28044-E (C/F)

Contents that cannot be specified for the Setup Wizard exist. (details = aa....aa)

aa....aa: Details

Description

The Easy Setup definition file contains coding that cannot be specified for the Setup Wizard.

The processing will be interrupted.

Action

See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.

Table 13‒5: List of detailed information in KEOS28044-E

Details

Description

Action

An unusable XML namespace is specified in the xmlns attribute of <model-definition>. Value=aa....aa

An unusable XML namespace is specified for the xmlns attribute of <model-definition>. (value = aa....aa)

aa....aa: Value specified in the xmlns attribute of <model-definition>

An unusable XML namespace is specified in <model-definition> of the Easy Setup definition file.

The processing will be interrupted.

Change the definition of <model-definition> in the Easy Setup definition file.

The XML namespace of the Easy Setup definition file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5.

An XML namespace is not specified in the xmlns attribute of <model-definition>.

An XML namespace is not specified for the xmlns attribute of <model-definition>

An XML namespace is not specified in the xmlns attribute of <model-definition> in the Easy Setup definition file.

The processing will be interrupted.

Change the definition of <model-definition> in the Easy Setup definition file.

The XML namespace for the Easy Setup definition file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5.

<model-definition>-<web-system> is not defined.

No definition of <model-definition>-<web-system> exists.

The definition of <model-definition>-<web-system> does not exist in the Easy Setup definition file.

The processing will be interrupted.

Add the Web system definition (<model-definition>-<web-system>) in the Easy Setup definition file.

Multiple <model-definition>-<web-system> are defined.

Multiple definitions of <model-definition>-<web-system> exist.

Multiple <model-definition>-<web-system> are defined in the Easy Setup definition file.

The processing will be interrupted.

Consolidate the definitions of <model-definition>-<web-system> in the Easy Setup definition file.

<web-system>-<load-balancer> is defined.

A definition of <web-system>-<load-balancer> exists.

A definition of <web-system>-<load-balancer> exists in the Easy Setup definition file.

The processing will be interrupted.

Delete the definition of <web-system>-<load-balancer> from the Easy Setup definition file.

Multiple <web-system>-<tier> are defined.

Multiple definitions of <web-system>-<tier> exist.

Multiple <web-system>-<tier> are defined in the Easy Setup definition file.

The processing will be interrupted.

Consolidate the definitions of <web-system>-<tier> in the Easy Setup definition file.

A value other than "combined-tier" or "j2ee-tier" is specified in <tier>-<tier-type>. Value=aa....aa

The value of <tier>-<tier-type> is not "combined-tier" or "j2ee-tier". (value = aa....aa)

aa....aa: Value specified in <tier-type>.

A value other than "combined-tier" or "j2ee-tier" is specified in <tier>-<tier-type> in the Easy Setup definition file.

The processing will be interrupted.

Specify "combined-tier" or "j2ee-tier" as the value of <tier>-<tier-type> in the Easy Setup definition file.

A value other than "1" is specified in <tier>-<j2ee-server-count>. Value=aa....aa

The value of <tier>-<j2ee-server-count> is not "1". (value = aa....aa)

aa....aa: Value specified in <j2ee-server-count>

A value other than "1" is specified in <tier>-<j2ee-server-count> in the Easy Setup definition file.

The processing will be interrupted.

Delete the <tier>-<j2ee-server-count> tag from the Easy Setup definition file or specify "1" as the value of <tier>-<j2ee-server-count>.

Multiple <web-system>-<unit> are defined.

Multiple definitions of <web-system>-<unit> exist.

Multiple <web-system>-<unit> are defined in the Easy Setup definition file.

The processing will be interrupted.

Consolidate the definitions of <web-system>-<unit> in the Easy Setup definition file.

A value other than "@myhost" is specified in <unit>-<allocated-host>-<host-ref>. Value=aa....aa

The value of <unit>-<allocated-host>-<host-ref> is not "@myhost". (value = aa....aa)

aa....aa: Value specified in <host-ref>

A value other than "@myhost" is specified in <unit>-<allocated-host>-<host-ref> in the Easy Setup definition file.

The processing will be interrupted.

Specify "@myhost" as the value of <unit>-<allocated-host>-<host-ref> in the Easy Setup definition file.

The <logical-server-name> is not defined for the item in which the <unit>-<allocated-host>-<define-server>-<logical-server-type> value is aa....aa.

No definition of <logical-server-name> exists that corresponds to the item whose <unit>-<allocated-host>-<define-server>-<logical-server-type> value is aa....aa.

aa....aa: Logical server type

The <logical-server-name> is not defined for the item in which the <unit>-<allocated-host>-<define-server>-<logical-server-type> value is aa....aa in the Easy Setup definition file. The processing will be interrupted.

For the logical server definition in which logical server type is aa....aa in the Easy Setup definition file, add the following <logical-server-name> tag and define the logical server name:

<unit> - <allocated-host> - <define-server>

<logical-server-type>aa....aa</logical-server-type>

<logical-server-name>logical server name</logical-server-name>

A value other than "web-server", "j2ee-server", or "performance-tracer" is specified in <unit>-<allocated-host>-<define-server>-<logical-server-type>. Value=aa....aa

The value of <unit>-<allocated-host>-<define-server>-<logical-server-type> is not "web-server", "j2ee-server", or "performance-tracer". (value = aa....aa)

aa....aa: Logical server type

A value other than "web-server", "j2ee-server", or "performance-tracer" is specified in <unit>-<allocated-host>-<define-server>-<logical-server-type> in the Easy Setup definition file.

The processing will be interrupted.

Specify "web-server", "j2ee-server", or "performance-tracer" as the value of <web-system>-<unit>-<allocated-host>-<define-server>-<logical-server-type> in the Easy Setup definition file.

Multiple <model-definition>-<host> are defined.

Multiple definitions of <model-definition>-<host> exist.

Multiple <model-definition>-<host> are defined in the Easy Setup definition file.

The processing will be interrupted.

Consolidate the definitions of <model-definition>-<host> in the Easy Setup definition file.

A value other than "@myhost" is specified in <model-definition>-<host>-<host-name>. Value=aa....aa

The value of <model-definition>-<host>-<host-name> is not "@myhost". (value = aa....aa)

aa....aa: Value specified in <host-name>

A value other than "@myhost" is specified in <model-definition>-<host>-<host-name> in the Easy Setup definition file.

The processing will be interrupted.

Specify "@myhost" as the value of <model-definition>-<host>-<host-name> in the Easy Setup definition file.

A value other than "@myhost" is specified in <model-definition>-<host>-<agent-host>. Value=aa....aa

The value of <model-definition>-<host>-<agent-host> is not "@myhost". (value = aa....aa)

aa....aa: Value specified in <agent-host>

A value other than "@myhost" is specified in <model-definition>-<host>-<agent-host> in the Easy Setup definition file.

The processing will be interrupted.

Specify "@myhost" as the value of <model-definition>-<host>-<agent-host> in the Easy Setup definition file.

The value of <model-definition>-<host>-<agent-port> is not equal to the port number (aa....aa) of the Administration Agent specified in the setup information file.

The value of <model-definition>-<host>-<agent-port> is not equal to aa....aa, the port number specified for the Administration Agent in the setup information file.

aa....aa: Port number specified for the Administration Agent in the setup information file

The value of <model-definition>-<host>-<agent-port> in the Easy Setup definition file is not equal to the port number of Administration Agent specified in the Easy Setup definition file.

The processing will be interrupted.

For the value of <model-definition>-<host>-<agent-port> in the Easy Setup definition file, specify port number of the Administration Agent that was specified when the setup information file was created.

KEOS28045-E (C/F)

No simple configuration definition file exists. (file name = aa....aa)

aa....aa: File name

Description

The specified Easy Setup definition file does not exist.

The processing will be interrupted.

Action

Revise the file name or path of the Easy Setup definition file.

KEOS28046-W (C/F)

A warning-level problem occurred during command execution. (command = aa....aa, details = :bb....bb)

aa....aa: Command name

bb....bb: Detailed message

Description

A warning-level problem occurred in the command executed by the Setup Wizard.

The processing continues.

KEOS28047-I (C/F)

The simple configuration definition file was correctly exported.

Description

The Easy Setup definition file was exported correctly.

KEOS28048-I (F)

The export of the simple configuration definition file has started.

Description

The export of the Easy Setup definition file has started.

KEOS28049-I (F)

The export of the simple configuration definition file has ended. (file name = aa....aa)

aa....aa: File name

Description

The export of the Easy Setup definition file has ended.

KEOS28050-E (C/F)

The simple configuration definition file cannot be exported.

Description

The Easy Setup definition file cannot be exported.

The processing will be interrupted.

Action

See the message displayed after this message, remove the cause of error, and then re-execute the export process.

KEOS28051-E (C/F)

A change that cannot be exported exists. (details = aa....aa)

aa....aa: Details

Description

A change in the system that cannot be exported exists in the Setup Wizard.

The processing will be interrupted.

Action

See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.

Table 13‒6: List of detailed information in KEOS28051-E

Details

Description

Action

A valid Web system does not exist.

No valid Web system exists.

A valid Web system does not exist.

The processing will be interrupted.

Contact maintenance personnel.

Multiple Web systems are defined.

Multiple Web systems are defined.

Multiple Web systems are defined.

The processing will be interrupted.

Delete the added Web system. Alternatively, delete the logical server that is added using the management portal.

A load balancer is defined.

A load balancer is defined.

A load balancer is defined.

The processing will be interrupted.

Delete the added load balancer definition.

Multiple tiers are defined.

Multiple tiers are defined.

Multiple tiers are defined.

The processing will be interrupted.

Delete the added tier definition.

A tier other than "combined-tier" or "j2ee-tier" is defined. Tier type=aa....aa

A tier other than "combined-tier" or "j2ee-tier" is defined. (tier type = aa....aa)

aa....aa: Tier type

A tier other than "combined-tier" or "j2ee-tier" is defined.

The processing will be interrupted.

Change the tier type to "combined-tier" or "j2ee-tier".

Multiple J2EE servers are defined.

Multiple J2EE servers are defined.

Multiple J2EE servers are defined.

The processing will be interrupted.

Delete the added J2EE server.

Multiple units are defined.

Multiple units are defined.

Multiple units are defined.

The processing will be interrupted.

Delete the added units.

A logical server is added using a method other than the Setup Wizard.

A logical server has been added using a method other than the Setup Wizard.

A logical server is added using a method other than the Setup Wizard.

The processing will be interrupted.

Delete the added logical server.

Multiple hosts are defined.

Multiple hosts are defined.

Multiple hosts are defined.

The processing will be interrupted.

Delete the definition of added hosts.

A host other than a local host is defined. Host name= aa....aa

A host other than a local host is defined. (host name = aa....aa)

aa....aa: Host name

A host other than a local host is defined.

The processing will be interrupted.

Change the host definition to local host.

A host other than a local host is defined for the Administration Agent host. Host name= aa....aa

An Administration Agent host other than a local host is defined. (host name = aa....aa)

aa....aa: Host name

A host other than a local host is defined for the Administration Agent host.

The processing will be interrupted.

Change the host definition to the local host.

The port number of the Administration Agent is changed. Value=aa....aa

The port number of the Administration Agent has been changed. (value = aa....aa)

aa....aa: Port number of Administration Agent

The port number of the Administration Agent is changed.

The processing will be interrupted.

Change the port number of the Administration Agent to the value specified when the setup information file was created.

KEOS28052-E (C/F)

The simple configuration definition file cannot be exported because the management user ID or password has been changed.

Description

The management user ID or password is changed, and therefore, the Easy Setup definition file cannot be exported.

The processing will be interrupted.

Action

Change the management user ID or password to the one specified during the set up by the Setup Wizard, and then re-execute the export process.

KEOS28053-E (C/F)

An error occurred during connection to the Management Server. (details = aa....aa)

aa....aa: Details

Description

An error occurred when connecting to the Management Server, and therefore, the Easy Setup definition file cannot be exported.

The processing will be interrupted.

Action

Confirm that the Management Server is running. Also check whether the HTTP port number connected to the Management Server was changed after executing setup using the Setup Wizard.

KEOS28054-E (C/F)

The export cannot be executed because the environment was not set up using the Setup Wizard

Description

Export cannot be executed in an environment that was not set up using the Setup Wizard.

The processing will be interrupted.

Action

Export and system replication cannot be executed using the Setup Wizard in an environment that is already set. Execute export and system migration using a method that supports the setup environment.

KEOS28055-W (C)

The specified value of property (aa....aa) is invalid. The default value (bb....bb) will be used. (file name = cc....cc)

aa....aa: Property name

bb....bb: Default value

cc....cc: File name

Description

The specified property value is invalid. The processing continues using the default value.

Action

Revise the settings.

KEOS28056-E (C)

An attempt to read the SetupWizard definition file has failed.(file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Detailed message

Description

An attempt to read the Setup Wizard definition file has failed.

The processing will be interrupted.

Action

The following messages are displayed in the details: See the detailed information, remove the cause of the error, and then re-execute the Setup Wizard.

Failed to open the configuration file.

Check that the Cosminexus-installation-directory/manager/setup/config/setup.cfg file exists and the user has read permission for the file.

The line of 64 kilobytes or more exists.

Check that lines of 64 kilobytes or more exist in the contents of the Setup Wizard definition file.

KEOS28057-E (C/F)

The port number is already in use by another process. (port number = aa....aa, duplicate item = bb....bb)

aa....aa: Port number

bb....bb: Duplicate item

Description

Setup cannot start because the port number specified in the Setup Wizard is being used in another process.

The processing will be cancelled.

Action

Change the port number specified in the Setup Wizard to a value that is not being used in another process or stop the process that is using the duplicated port number.

KEOS28058-I (C/F)

An environment cannot be removed because no environment has been set up by the Management Server.

Description

Unsetup need not be executed because no environment has been set up by the Management Server.

KEOS28500-I (F)

Removal of the environment built by the Management Server is started.

Description

The unset up of the environment set up by the Management Server will start.

KEOS28501-I (C/F)

Removal of the environment built by the Management Server was succeeded.

Description

The environment set up by the Management Server was unset up successfully.

KEOS28502-E (C/F)

Removal of the environment built by the Management Server was failed.

Description

An attempt to unset up the environment set up by the Management Server failed.

The processing will be cancelled.

Action

Check the message output before this message.

Remove the cause of the error, and then re-execute the command.

KEOS28503-E (C)

Removal of the environment built by the Management Server is already executing.

Description

The environment set up by the Management Server is being unset up.

The processing will be cancelled.

Action

Re-execute the command after the unsetup processing terminates.

KEOS28504-I (F)

The Management Server has stopped.

Description

The Management Server has stopped.

KEOS28505-E (C/F)

An attempt to stop the Management Server has failed.

Description

An attempt to stop the Management Server failed.

The processing will be cancelled.

Action

Check the Management Server log.

Remove the cause of the error, and then re-execute the command.

KEOS28506-I (F)

The Management Server has deleted.

Description

The Management Server has been deleted.

KEOS28507-E (C/F)

An attempt to delete the Management Server has failed.

Description

An attempt to delete the Management Server failed.

The processing will be cancelled.

Action

If the mngautorun respawn command was used to specify auto-restart settings for the Management Server, the Management Server might have been restarted by the init program of the OS.

If the settings to auto-restart the Management Server are specified, cancel the auto-restart settings in the -d option of the mngautorun, restart the computer, and then re-execute the command.

If the settings to auto-restart the Management Server are not specified, see the Management Server log, remove the cause of the error, and then re-execute the command.

KEOS28508-I (F)

The Administration Agent has stopped.

Description

The Administration Agent has stopped.

KEOS28509-E (C/F)

An attempt to stop the Administration Agent has failed.

Description

An attempt to stop the Administration Agent failed.

The processing will be cancelled.

Action

Check the Administration Agent log.

Remove the cause of the error, and then re-execute the command.

KEOS28510-E (C/F)

An internal error occurred. (detail = aa....aa)

aa....aa: Details

Description

An internal error occurred in the unsetup functionality.

The processing will be cancelled.

Action

Check the details.

Remove the cause of the error, and then re-execute the command.

KEOS28511-I (F)

aa....aa(bb....bb) was stopped.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The logical server has stopped.

KEOS28512-E (C/F)

The stop of aa....aa(bb....bb) failed. (detail = cc....cc)

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

An attempt to stop the logical server failed.

The processing will be cancelled.

Action

Check the details.

Remove the cause of the error, and then re-execute the command.

KEOS28513-I (F)

aa....aa(bb....bb) was deleted.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The logical server is deleted.

KEOS28514-E (C/F)

The delete of aa....aa(bb....bb) failed. (detail = cc....cc)

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

An attempt to delete the logical server failed.

The processing will be cancelled.

Action

Check the details.

Remove the cause of the error, and then re-execute the command.

KEOS28515-I (F)

The Component Container administrator was removed.

Description

The Component Container administrator was removed.

KEOS28516-E (C/F)

Removal of the Component Container administrator failed. (detail = aa....aa)

aa....aa: Details

Description

An attempt to remove the Component Container administrator failed.

The processing will be cancelled.

Action

Check the details.

Remove the cause of the error, and then re-execute the command.

KEOS28517-E (C/F)

An attempt to write to the file failed. (file name = aa....aa, detail = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An attempt to write to the file failed.

The processing continues.

Action

The possible causes are as follows:

The user does not the permission to access the write destination file and directory.

The disk space at the write destination has depleted.

The write destination directory does not exist.

Check the access permissions and the disk space for the output destination file and directory.

See the details, remove the cause of the error, and then re-execute the command.

KEOS28518-E (C/F)

An attempt to read the file failed. (file name = aa....aa, detail = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An attempt to read the file failed.

The processing will be cancelled.

Action

Check the access permissions for the file and directory.

See the details, remove the cause of the error, and then re-execute the command.

KEOS28522-E (C/F)

An attempt to delete file failed. (file name = aa....aa)

aa....aa: File name

Description

An attempt to delete the file failed.

The processing will be cancelled.

Action

Check whether the file exists.

If the file does not exist, and then re-execute the command.

If the file exists, check the access permissions for the file and directory. Remove the cause of the error, and then re-execute the command.

KEOS28525-I (C)

Usage: mngunsetup [options]

options

-force: Executes without requesting confirmation for execution.

Description

This message describes the usage method of the command.

KEOS28526-E (C/F)

An attempt to execute the command has failed. (command name = aa....aa, detail = bb....bb)

aa....aa: Command name

bb....bb: Details

Description

An attempt to execute a command during unsetup failed.

The processing will be cancelled.

Action

Check the details.

Remove the cause of the error, and then re-execute the mngunsetup command.

KEOS28527-I (F)

The automatic starting and automatic restarting settings for the Management Server and the Administration Agent were removed.

Description

The auto-start and auto-restart settings for the Management Server and Administration Agent were cancelled.

KEOS28528-E (C/F)

Removal of the automatic starting and automatic restarting settings for the Management Server and the Administration Agent failed. (detail = aa....aa)

aa....aa: Details

Description

An attempt to cancel the auto-start and auto-restart settings for the Management Server and Administration Agent failed.

The processing will be cancelled.

Action

Check the details.

Remove the cause of the error, and then re-execute the command.

KEOS28529-I (F)

The CTM domain information has deleted.

Description

The CTM domain information was deleted.

KEOS28530-E (C/F)

An attempt to delete the CTM domain information has failed. (detail = aa....aa)

aa....aa: Details

Description

An attempt to delete the CTM domain information failed.

The processing will be cancelled.

Action

Check the access permissions for the following file and directory:

In Windows

Windows-directory\TPBrokerOTM.dat

In Linux

/var/spool/TPBrokerOTM/TPBrokerTSC

Other than above

/usr/spool/TPBrokerOTM/TPBrokerTSC

Remove the cause of the error, and then re-execute the command.

KEOS28532-E (C/F)

The built and status for the logical server cannot be acquired.

Description

The setup and operation status of the logical server cannot be acquired.

The processing will be cancelled.

Action

Check whether the following file exists:

Cosminexus-installation-directory/manager/spool/logicalserver.xml.bak

Take the following action based on whether the logicalserver.xml.bak file exists:

If the logicalserver.xml.bak file exists

Rename the logicalserver.xml.bak file to logicalserver.xml, and then re-execute the command.

Note that even if unsetup is successful with this action, a stopped or undeleted logical server might exist and the rebuilding of the environment might fail. In such a case, stop the running logical server processes manually and then delete the real server.

If the logicalserver.xml.bak does not exist

Stop the running logical server processes manually, delete the real server, and then re-execute the command.

KEOS28533-E (F)

An attempt to save the built and status for logical server failed. (file name = aa....aa)

aa....aa: File name

Description

An attempt to save the setup and operation information for the logical server failed.

The processing will be cancelled.

Action

Take action in the following order:

Check whether the disk drive on which the Administration Agent is installed has sufficient free space.

The disk might be full. If there is no free space, allocate sufficient free space.

Take one of the following actions based on the file name:

If Cosminexus-installation-directory/manager/spool/logicalserver.xml is output in the file name

Take action in the following order:

Delete Cosminexus-installation-directory/manager/spool/logicalserver.xml.

Rename Cosminexus-installation-directory/manager/spool/logicalserver.xml.bak to Cosminexus-installation-directory/manager/spool/logicalserver.xml.

Re-execute the operations that were performed just before this message was displayed.

If Cosminexus-installation-directory/manager/spool/logicalserver.xml.bak is output in the file name

Re-execute the operations that were performed just before this message was displayed.

KEOS28534-W (F)

The period of watching aa....aa(bb....bb) stopped was expired.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The monitoring time of the termination for the logical server is expired.

The process will be continued.

Action

Set up the monitoring time of the termination for the logical server in conformity to the environment.

KEOS28535-W (F)

The period of watching aa....aa(bb....bb) force stopped was expired.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The monitoring time of the forced termination for the logical server is expired.

The process will be continued.

Action

Set up the monitoring time of the forced termination for the logical server in conformity to the environment.

KEOS28536-I (F)

aa....aa(bb....bb) is stopping.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The logical server will be stopped.

KEOS28537-I (F)

aa....aa(bb....bb) is stopping forcefully.

aa....aa: Logical server name

bb....bb: Logical server type

Description

The logical server will be forcefully terminated.

KEOS28538-E (C/F)

The force stop of aa....aa(bb....bb) failed. (detail = cc....cc)

aa....aa: Logical server name

bb....bb: Logical server type

cc....cc: Details

Description

An attempt to forcefully terminate the logical server has failed.

The process will be interrupted.

Action

See the detail, remove the cause of the error, and then re-execute the command.

KEOS28700-I (C)

Usage: mngenvupdate

Description

This message describes the usage method of the command.

KEOS28701-I (C/F)

The conversion of the Management Server is started.

Description

The migration of the Management Server will start.

KEOS28702-I (C/F)

The conversion of the Management Server was successfully.

Description

The migration of the Management Server was successful.

KEOS28703-E (C/F)

An attempt to convert the Management Server has failed.

Description

An attempt to migrate the Management Server failed.

The processing will be cancelled.

Action

Check the message output before this message.

Remove the cause of the error, and then re-execute the command.

KEOS28704-E (C/F)

An attempt to convert file failed. (file name = aa....aa, detail = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An attempt to migrate file failed.

The processing will be cancelled.

Action

Make sure that the file to be migrated exists, or that the disk space at the migration destination has not depleted.

Check the details.

Remove the cause of the error, and then re-execute the command.

KEOS28705-W (C/F)

An attempt to delete file or directory has failed. (file name or directory name = aa....aa)

aa....aa: File name or directory name

Description

An attempt to delete a file or directory failed.

The processing continues.

Action

Check whether the user has the permission to delete the file or directory, and whether a running process is being used.

Remove the cause of the error, and then re-execute the command.

KEOS28706-E (C/F)

An internal error occurred. (detail = aa....aa)

aa....aa: Details

Description

An internal error occurred.

The processing will be cancelled.

Action

Check the details.

Remove the cause of the error, and then re-execute the command. If this action does not resolve the error, contact maintenance personnel.

KEOS28707-E (C/F)

An attempt to setup the Management Server has failed. (detail = aa....aa)

aa....aa: Detail

Description

An attempt to set up Management Server has failed.

The process will be interrupted.

Action

Check the detail.

Remove the cause of the error, and then re-execute the command. If this action does not resolve the error, contact maintenance personnel.

KEOS29001-E (C)

Usage:

aa....aa

aa....aa: Command usage

Description

The command usage is incorrect. The processing will be interrupted.

Action

Check the command usage, and then re-execute the command.

KEOS29002-E (C)

The host or user ID has not been specified in the common option.

Description

The host or user ID has not been specified in the common option. The processing will be interrupted.

Action

Check that the vmx.connect.host and vmx.connect.userid keys are set up in the client settings property file (vmxclient.properties).

KEOS29003-E (C)

The host name or port number is invalid. (details = aa....aa)

aa....aa: Details

Description

The host name or the port number is invalid. The processing will be interrupted.

Action

Check the specification method of the host name and the port number.

KEOS29004-E (C)

A communication error occurred. (details = aa....aa)

aa....aa: Details

Description

A communication error occurred. The processing will be interrupted.

Action

Check that Management Server is running or check the values of the host name and the port number specified in the -m option of the common arguments. Also, confirm that the products at the connection source and the connection destination can be connected.

KEOS29005-E (C)

An exception occurred during creation of a temporary file. (details = aa....aa)

aa....aa: Details

Description

An exception occurred during creation of a temporary file. The processing will be interrupted.

Action

Contact maintenance personnel.

KEOS29006-I (F)

The command started. (command = aa....aa, process id = bb....bb, start time = cc....cc)

aa....aa: Command line

bb....bb: Process ID

cc....cc: Command start time

Description

The command described in the message will start.

KEOS29007-I (F)

The command finished. (process id = aa....aa, start time = bb....bb, code = cc....cc)

aa....aa: Process ID

bb....bb: Command start time

cc....cc: End code

Description

The command indicated in the process ID and the command start time will end.

KEOS29008-E (C)

The specified file does not exist. (file name = aa....aa)

aa....aa: File name

Description

The specified file does not exist. The processing will be interrupted.

Action

Check the arguments specified in the command.

KEOS29009-E (C)

The specified file is not a normal file. (file name = aa....aa)

aa....aa: File name

Description

The specified file is not a normal file. The processing will be interrupted.

Action

Check the specified file.

KEOS29010-E (C)

An exception occurred during creation of a temporary file. (details = aa....aa)

aa....aa: Details

Description

An attempt to create a temporary file has failed. The processing will be interrupted.

Action

Contact maintenance personnel.

KEOS29011-E (C)

An exception occurred while reading the file. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An exception occurred while reading the file. The processing will be interrupted.

Action

Check the file access permission. If the file access permission is correct and the exception is not recovered even after re-executing the command, contact maintenance personnel.

KEOS29012-E (C)

An attempt to write to the file failed. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An attempt to write to the file failed. The processing continues.

Action

Check the file permissions, and then restart the virtual server manager.

KEOS29051-E (W/F)

No administrator user account has been configured.

Description

No administrator user account has been registered in the Cosminexus Management Server configuration file. The processing will be interrupted.

Action

Use the mngsvrctl setup command to set up the administrator user account.

KEOS29052-E (W/F)

The administrator user ID or password is incorrect.

Description

The administrator user ID or password for logging into the Cosminexus Virtual Server Manager is different. The specified request is ignored, and the Login Screen anchor will be displayed.

Action

Set up the correct administration user ID or password into the login screen.

If you click the Login Screen anchor, you will return to the login screen.

KEOS29053-E (W/F)

The administrator user ID is logged out either because it is not logged in, or the session has timed out.

Description

The user is currently not logged into Cosminexus Virtual Server Manager. The specified request is ignored, and the Login Screen anchor will be displayed.

Action

Log in from the login screen.

If you click the Login Screen anchor, you will return to the login screen.

KEOS29054-I (W/F)

The administrator user ID logged out normally.

Description

The administrator user ID logged out normally from the Cosminexus Virtual Server Manager.

KEOS29055-Q (W)

All virtual servers on management unit aa....aa will be started. Are you sure?

aa....aa: Management unit name

Description

Confirm the batch start of management unit. The OK and Cancel buttons is displayed. If you click the OK button, the processing continues. If you click the Cancel button, the processing will be interrupted.

Action

If you want to batch start the management unit, click the OK button.

KEOS29056-I (W/F)

The start for management unit aa....aa completed normally.

aa....aa: Management unit name

Description

The batch start processing of the management unit completed normally.

Action

Check the virtual server manager log for the execution result of batch start.

KEOS29057-E (W/F)

The start for management unit aa....aa failed.

aa....aa: Management unit name

Description

An attempt to batch start the management unit has failed. The batch start processing is interrupted, and the Return anchor is displayed.

Action

Check the virtual server manager log, remove the cause of the error, and then re-execute the process.

KEOS29058-Q (W)

All virtual servers on management unit aa....aa will be stopped. Are you sure?

aa....aa: Management unit name

Description

The batch stop of the management unit will be confirmed. The OK and Cancel buttons will be displayed. If you click the OK button, the processing continues. If you click the Cancel button, the processing will be interrupted.

Action

If you want to batch stop the management unit, click the OK button.

KEOS29059-I (W/F)

The stop for management unit aa....aa completed normally.

aa....aa: Management unit name

Description

The batch stop processing of the management unit completed normally.

Action

Check the virtual server manager log for the execution result of batch stop.

KEOS29060-E (W/F)

The stop for management unit aa....aa failed.

aa....aa: Management unit name

Description

An attempt to batch stop the management unit has failed. The batch stop processing is interrupted, and then the Return anchor is displayed.

Action

Check the virtual server manager log, remove the cause of the error, and then re-execute the process.

KEOS29101-I (W/F)

The virtual server manager started.

Description

The virtual server manager is started.

KEOS29102-E (W/F)

An attempt to start the virtual server manager failed.

Description

An attempt to start the virtual server manager has failed. The processing will be interrupted.

Action

Take action according to the message output just before this message.

KEOS29103-I (W/F)

The virtual server manager finished.

Description

The virtual server manager is finished.

KEOS29104-E (W/F)

A required property was not specified. (property = aa....aa, file name = bb....bb)

aa....aa: Property key

bb....bb: File name

Description

A required property was not specified. The processing continues.

Action

Check the contents of the file, and then restart the virtual server manager.

KEOS29105-E (W/F)

An invalid value was specified for the property. (property = aa....aa, invalid value = bb....bb, file name = cc....cc)

aa....aa: Property key

bb....bb: Value specified for the property (invalid value)

cc....cc: File name

Description

An invalid value was specified for the property. The processing continues.

Action

Check the contents of the file, and then restart the virtual server manager.

KEOS29106-W (W/F)

An invalid value was specified for the property. The default value will be used. (property = aa....aa, invalid value = bb....bb, default value = cc....cc, file name = dd....dd)

aa....aa: Property key

bb....bb: Value specified for the property (invalid value)

cc....cc: Default property value

dd....dd: File name

Description

An invalid value was specified for the property, so the default value is used and the processing continues.

Action

Check the contents of the file, and restart the virtual server manager as and when required.

KEOS29107-I (W/F)

The directory was created. (directory type = aa....aa, directory name = bb....bb).

aa....aa: Directory type

bb....bb: Directory name

Description

The directory was created.

KEOS29108-E (W/F)

An attempt to create a directory failed. (directory type = aa....aa, directory name = bb....bb)

aa....aa: Directory type

bb....bb: Directory name

Description

An attempt to create the directory has failed. The processing continues.

Action

Check the directory permissions, and restart the virtual server manager as and when required.

KEOS29109-E (W/F)

An attempt to connect to VMware vCenter Server failed.

Description

An attempt to connect to VMware vCenter Server has failed. The processing continues.

Action

Check the settings for connecting to VMware vCenter Server in vmx.properties, and then restart the virtual server manager.

KEOS29110-E (W/F)

An attempt to read the file failed. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An attempt to read the file has failed. The processing continues.

Action

Check the file permissions, and then restart the virtual server manager.

KEOS29111-E (C/W/F)

An attempt to write to the file failed. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An attempt to write to the file has failed. The processing continues.

Action

Check the file permissions and the empty disk space, and then perform the following process for every trigger:

If the message occurs when the virtual server manager starts, restart the virtual server manager.

If the message occurs when the virtual server manager commands are executed, take the action specified for the message that is output just before this message.

KEOS29112-I (W/F)

The sub-process (Agent for VMware vCenter Server) will now start.

Description

The sub-process (Agent for VMware vCenter Server) will start.

KEOS29113-E (W/F)

An attempt to start the sub-process (Agent for VMware vCenter Server) failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to start the sub-process (Agent for VMware vCenter Server) has failed. The processing will be interrupted.

Action

Check the details, and then restart the virtual server manager. If timeout has occurred, revise the value of vmx.vcenterserver.agent.start.timeout in the virtual server manager property file.

KEOS29114-I (W/F)

The sub-process (Agent for VMware vCenter Server) started.

Description

The sub-process (Agent for VMware vCenter Server) has started.

KEOS29116-I (W/F)

Operation of the virtual machine will now start. (operation type = aa....aa, operation target = bb....bb)

aa....aa: Operation type (reproduce, start, stop, suspend, shutdown, delete, confirm start, and confirm stop)

bb....bb: Operation target (reproduction source virtual machine, reproduction destination virtual machine, reproduction destination host, and virtual machine)

Description

The virtual machine operations will be executed.

KEOS29117-I (W/F)

Operation of the virtual machine successfully finished. (operation type = aa....aa, operation target = bb....bb)

aa....aa: Operation type (reproduce, start, stop, suspend, shutdown, delete, confirm start, and confirm stop)

bb....bb: Operation target (reproduction source virtual machine, reproduction destination virtual machine, reproduction destination host, and virtual machine)

Description

The virtual machine operations were successful.

KEOS29118-E (W/F)

Operation of the virtual machine failed. (operation type = aa....aa, operation target = bb....bb)

aa....aa: Operation type (reproduce, start, stop, suspend, shutdown, delete, confirm start, and confirm stop)

bb....bb: Operation target (reproduction source virtual machine, reproduction destination virtual machine, reproduction destination host, and virtual machine)

Description

An attempt to execute the virtual machine operations has failed. The processing continues.

Action

Take action according to the error messages output before and after this message.

KEOS29119-E (W/F)

The virtual server manager will now end because the sub-process (Agent for VMware vCenter Server) has stopped abnormally.

Description

The virtual server manager will stop because the sub-process (Agent for VMware vCenter Server) terminated abnormally. The processing will be interrupted.

Action

Restart the virtual server manager.

KEOS29131-E (C/W/F)

A timeout occurred in communicating with the VMware vCenter Server communication process. (details = aa....aa)

aa....aa: Details

Description

A timeout occurred during communication with the process for VMware vCenter Server communication. The processing will be interrupted.

Action

The processing in VMware vCenter Server did not finish within the specified time. Check the settings, and then re-execute the processing.

KEOS29132-E (C/W/F)

An attempt to communicate with the VMware vCenter Server communication process failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to communicate with the process for VMware vCenter Server communication has failed. The processing will be interrupted.

Action

Restart the virtual server manager.

KEOS29133-E (C/W/F)

An attempt to communicate with VMware vCenter Server failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to communicate with VMware vCenter Server has failed. The processing will be interrupted.

Action

Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.

KEOS29134-E (C/W/F)

An attempt to log in to VMware vCenter Server failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to login to VMware vCenter Server has failed. The processing will be interrupted.

Action

Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.

KEOS29135-E (C/W/F)

An operation in VMware vCenter Server failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to execute operations in VMware vCenter Server has failed. The processing will be interrupted.

Action

Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.

KEOS29136-E (C/W/F)

An operation in VMware vCenter Server failed because a file operation in a virtual server failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to execute operations in VMware vCenter Server failed because the virtual server file operations failed. The processing will be interrupted.

Action

Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.

KEOS29137-E (C/W/F)

An operation target does not exist in VMware vCenter Server. (details = aa....aa)

aa....aa: Details

Description

The operation target in VMware vCenter Server does not exist. The processing will be interrupted.

Action

Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.

KEOS29138-E (C/W/F)

An operation in VMware vCenter Server failed because resources are insufficient. (details = aa....aa)

aa....aa: Details

Description

An attempt to execute operations in VMware vCenter Server has failed because of insufficient resources. The processing will be interrupted.

Action

Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.

KEOS29139-E (C/W/F)

An operation in VMware vCenter Server failed because there is a problem in the current state of the system. (details = aa....aa)

aa....aa Details

Description

An attempt to execute operations in VMware vCenter Server has failed because of an incorrect status. The processing will be interrupted.

Action

Check the status of VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.

KEOS29140-E (C/W/F)

An operation in VMware vCenter Server failed because another operation is being performed. (details = aa....aa)

aa....aa: Details

Description

An attempt to execute operations in VMware vCenter Server has failed because another operation is running. The processing will be interrupted.

Action

Check status of the VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.

KEOS29141-E (C/W/F)

An operation in VMware vCenter Server failed because there is a configuration problem. (details = aa....aa)

aa....aa: Details

Description

An attempt to execute operations in VMware vCenter Server has failed because of incorrect settings. The processing will be interrupted.

Action

Check status of the VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.

KEOS29142-E (C/W/F)

An operation in VMware vCenter Server failed because there is a datastore problem. (details = aa....aa)

aa....aa: Details

Description

An attempt to execute operations in VMware vCenter Server has failed because of incorrect data store. The processing will be interrupted.

Action

Check status of the VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.

KEOS29143-E (C/W/F)

An attempt to migrate the virtual server failed. (details = aa....aa)

aa....aa: Details

Description

An attempt to migrate the virtual server has failed. The processing will be interrupted.

Action

Check status of the VMware vCenter Server, and then re-execute the processing. If the problem is not resolved, restart the virtual server manager.

KEOS29144-E (C/W/F)

It is required that the number of network adaptors is one.

Description

The number of network adapters must be one. The processing will be interrupted.

Action

Check the virtual machine settings, and then re-execute the processing.

KEOS29145-E (C/W/F)

There are no network adapters that attached network label aa....aa.

aa....aa: Network label name

Description

A network adapter to which the specified network label is allocated does not exist. The processing will be interrupted.

Action

Check the virtual machine settings, and then re-execute the processing.

KEOS29146-E (C/W/F)

There are more than one network adapters that attached network label aa....aa.

aa....aa: Network label name

Description

There are two or more network adapters to which the specified network label is allocated. The processing will be interrupted.

Action

Check the virtual machine settings, and then re-execute the processing.

KEOS29151-I (W/F)

Processing of the virtual server manager command will now start. (client = aa....aa)

aa....aa: Connection source host

Description

The processing of the virtual server manager commands will start.

KEOS29152-I (W/F)

Processing of the virtual server manager command ended.

Description

The processing of the virtual server manager commands will end.

KEOS29153-E (C/W/F)

This command is not supported. (details = aa....aa)

aa....aa: Details

Description

This command is not supported. The processing will be interrupted.

Action

Check the product version installed on the management machine and the product version installed on the machine executing the command.

KEOS29154-E (C/W/F)

An internal error occurred. (details = aa....aa)

aa....aa: Details

Description

An internal error occurred. The processing will be interrupted.

Action

Contact maintenance personnel.

KEOS29155-I (W/F)

Processing of aa....aa was received.

aa....aa: Command name

Description

A command processing was received.

KEOS29156-I (W/F)

Processing of the aa....aa command will now start.

aa....aa: Command name

Description

The command processing will start.

KEOS29157-I (W/F)

Processing of the aa....aa command ended.

aa....aa: Command name

Description

The command processing ended.

KEOS29159-E (C)

A communication error occurred. (details = aa....aa)

aa....aa: Details

Description

A communication failure occurred. The processing will be interrupted.

Action

If the failure is not recovered even after re-executing the command, contact maintenance personnel.

KEOS29161-E (C/W/F)

This operation cannot be executed because other operations are executing.

Description

This operation cannot be executed because another operation is running. The processing will be interrupted.

Action

Wait for some time, and then execute the operation again.

KEOS29162-E (C)

The administrator user ID or password is invalid.

Description

The management user ID or password is invalid. The processing will be interrupted.

Action

Check the specified management user ID and the password.

KEOS29163-E (C/W)

The connection failed because either the virtual server manager is not enabled, or startup of the virtual server manager is in progress.

Description

The connection cannot be established because the virtual server manager is not enabled or the virtual server manager is running. The processing will be interrupted.

Action

Specify the settings to enable the virtual server manager, and then restart the virtual server manager. If the settings for enabling the virtual server manager are already specified, wait for some time, and then re-execute the operation.

KEOS29164-E (C/W/F)

The file cannot be accessed because it is not a normal file. (file name = aa....aa)

aa....aa: File name

Description

The specified file is not a regular file, so the file cannot be accessed. The processing will be interrupted.

Action

Specify a regular file, and then re-execute the operation.

KEOS29165-E (C/W/F)

An attempt to read the file failed. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An attempt to read the file has failed. The processing will be interrupted.

Action

Check whether the file exists or whether you have the permission to access the file.

KEOS29167-E (C/W/F)

A connection to VMware vCenter Server could not be established. (details = aa....aa)

aa....aa: Details

Description

Connection could not be established with VMware vCenter Server. The processing will be interrupted.

Action

See the details, remove the cause of the error, and then re-execute the operation.

KEOS29168-E (C/W/F)

Information from VMware vCenter Server could not be acquired. (details = aa....aa)

aa....aa: Details

Description

Information could not be acquired from VMware vCenter Server. The processing will be interrupted.

Action

See the details, remove the cause of the error, and then re-execute the operation.

KEOS29169-E (C/W/F)

An exception occurred during creation of a temporary file. (details = aa....aa)

aa....aa: Details

Description

A failure occurred while creating the temporary file. The processing will be interrupted.

Action

Contact maintenance personnel.

KEOS29170-E (C/W/F)

A virtual server does not exist for the management unit. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The virtual server does not exist in the management unit. The processing will be interrupted.

Action

The virtual server does not exist in the specified management unit. Use the vmx_deploy_unit command to deploy, and then re-execute the operation.

KEOS29172-E (C/W/F)

Creation of the management unit is not complete. (management unit name = aa....aa)

aa....aa: Management unit name

Description

Creation of the management unit is not complete. The processing will be interrupted.

Action

Create the management unit, and then re-execute the operation.

KEOS29173-E (W/F)

An error response was returned from the HTTP server. (details = aa....aa)

aa....aa: Response code

Description

The HTTP server returned an error response. The processing will be interrupted.

Action

See the details, and then take action according to the response code of the server communication agent.

KEOS29174-E (W/F)

An error occurred during file transfer. (details = aa....aa)

aa....aa: Error information

Description

An error occurred during file transfer. The processing will be interrupted.

Action

Take action according to the details.

FileNotFoundException

Revise the transfer destination directory specified in the virtual server manager.

IOException

Check the file in which the error occurred.

SocketIOException

Revise the network environment or settings.

KEOS29175-E (W/F)

An error occurred during processing of the server communication agent. (details = aa....aa)

aa....aa: Error information

Description

An error occurred in the processing of the server communication agent. The processing will be interrupted.

Action

Take action according to the details.

DuplicateFileNameException

Revise the file or the directory to be transmitted that is specified in the server communication agent.

FileNotFoundException

Revise the file or the directory to be transmitted that is specified in the server communication agent.

IOException

Check the file in which the error occurred.

SocketIOException

Revise the network environment or settings.

KEOS29176-E (W/F)

The version of the server communication agent is inconsistent with the version of the virtual server manager.

Description

The version of the server communication agent is inconsistent with the version of the virtual server manager. The processing will be interrupted.

Action

Use a Cosminexus version supported by the virtual server manager for Application Servers running on the virtual application server.

KEOS29177-E (W/F)

A timeout occurred during command execution. (details = aa....aa)

aa....aa: Process ID

Description

A timeout occurred during the execution of the command. The processing will be interrupted.

Action

Check the process status output to details. If necessary, terminate the process forcibly.

KEOS29179-E (C/W/F)

The specified management unit does not exist. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The specified management unit does not exist. The processing will be interrupted.

Action

Specify an existing management unit name.

KEOS29180-E (C/W/F)

The specified management unit already exists. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The specified management unit already exists. The processing will be interrupted.

Action

Check the management unit name, and then re-execute the operation.

KEOS29181-E (C/W/F)

Information for the management target host is not set.

Description

The information about the administered machine is not set up. The processing will be interrupted.

Action

Use the vmx_set_machine_info command to set up the information about the administered machine.

KEOS29182-E (W/F)

An error occurred during file transfer. (details = aa....aa)

aa....aa: Error information

Description

An error occurred in the file transmit processing.

The processing continues for the vmx_deploy_unit, vmx_start_unit, and vmx_stop_unit commands.

The processing will be cancelled for other commands.

Action

Take action according to the details.

DuplicateFileNameException

Revise the file or the directory to be transmitted that is specified in the virtual server manager.

FileNotFoundException

Revise the file or the directory to be transmitted that is specified in the virtual server manager.

IOException

Check the file in which the error occurred.

SocketIOException

Revise the network environment or settings.

KEOS29183-E (W/F)

An error occurred during processing of the server communication agent. (details = aa....aa)

aa....aa: Error information

Description

An error occurred in the processing of the server communication agent.

The processing continues for the vmx_deploy_unit, vmx_start_unit, and vmx_stop_unit commands.

The processing will be cancelled for other commands.

Action

Take action according to the details.

FileNotFoundException

Revise the transmission destination directory specified in the server communication agent.

IOException

Check the file in which the error occurred.

SocketIOException

Revise the network environment or settings.

KEOS29184-E (W/F)

An error occurred during processing of the server communication agent. (details = aa....aa)

aa....aa Details

Description

An error occurred in the processing of the server communication agent.

The processing continues for the vmx_deploy_unit, vmx_start_unit, and vmx_stop_unit commands.

The processing will be cancelled for other commands.

Action

Take action according to the details.

CommandInterruptedException

The processing was interrupted while waiting for the command to terminate, so check the status of the server communication agent and the status of the running process. If necessary, terminate the process forcibly.

IOException

Check the file in which the error occurred.

SocketIOException

Revise the network environment or settings.

KEOS29201-W (C/W/F)

An attempt to output a snapshot log failed. (virtual server name = aa....aa, details = bb....bb)

aa....aa: Virtual server name

bb....bb: Details

Description

An attempt to output the snapshotlog has failed. The processing continues.

Action

Check whether snapshotlog can be executed on the virtual server.

KEOS29202-W (C/W/F)

An attempt to collect the event log failed. (virtual server name = aa....aa, details = bb....bb)

aa....aa: Virtual server name

bb....bb: Details

Description

An attempt to collect the event log has failed. The processing continues.

Action

Check whether the event log can be collected on the virtual server.

KEOS29203-W (C/W/F)

An attempt to collect the system log failed. (virtual server name = aa....aa, details = bb....bb)

aa....aa: Virtual server name

bb....bb: Details

Description

An attempt to collect the system log has failed. The processing continues.

Action

Check whether the system log can be collected on the virtual server.

KEOS29204-E (C/W/F)

An attempt to create a ZIP file failed. (virtual server name = aa....aa, details = bb....bb)

aa....aa: Virtual server name

bb....bb: Details

Description

An attempt to create the Zip file has failed. The processing will be interrupted.

Action

Check whether you have the file write permission.

KEOS29213-E (C/W/F)

An attempt to confirm whether the virtual server is working has failed. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

An attempt to check the virtual server operations has failed. Virtual server failure monitoring will be interrupted.

Action

See the user action for the error message output just before this message. After finishing the investigation, delete the virtual server from VMware vCenter Server, and then execute the vmx_deploy_unit command as and when required.

KEOS29214-W (C/W/F)

An attempt to stop a virtual server failed. (management target host name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Administered machine name

bb....bb: Virtual server name

cc....cc: Details

Description

An attempt to stop the virtual server has failed. The processing will be interrupted.

Action

Check the network settings or check whether the virtual server is running normally. If the network settings are incorrect, specify the correct settings. If the virtual server has stopped, use the hypervisor functionality to start and check the failed virtual server. Remove the cause of the error, update the management unit, and then apply the settings to the virtual server. After this, start the virtual server.

KEOS29221-E (C/W/F)

An invalid entry was found. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

Contents that cannot be specified in the Easy Setup definition file exist. The processing will be interrupted.

Action

Remove the cause of the error based on the details described in the following table, and then re-execute the vmx_create_unit command.

Table 13‒7: List of error details described in KEOS29221-E

Details

Description

Action

An unusable XML namespace is specified for the xmlns attribute of <model-definition>. (value = aa....aa)

An XML namespace that cannot be used is specified in <model-definition> of the Easy Setup definition file. The processing will be interrupted.

Change the <model-definition> definition in the Easy Setup definition file. The XML namespace for the Easy Setup definition file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5.

An XML namespace is not specified for the xmlns attribute of <model-definition>.

XML namespace is not specified in the xmlns attribute of <model-definition> in the Easy Setup definition file. The processing will be interrupted.

Change the <model-definition> definition in the Easy Setup definition file. The XML namespace for the Easy Setup definition file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5.

No definition of <model-definition>-<web-system> exists.

<model-definition>-<web-system> is not defined in the Easy Setup definition file. The processing will be interrupted.

Add the Web system definition (<model-definition>-<web-system>) in the Easy Setup definition file.

Multiple definitions of <model-definition>-<web-system> exist.

Multiple <model-definition>-<web-system> are defined in the Easy Setup definition file. The processing will be interrupted.

Unify the <model-definition>-<web-system> definitions in the Easy Setup definition file.

Multiple definitions of <web-system>-<tier> exist.

Multiple <web-system>-<tier> are defined in the Easy Setup definition file. The processing will be interrupted.

Unify the <web-system>-<tier> definitions in the Easy Setup definition file.

The value of <tier>-<tier-type> is not "combined-tier". (value = aa....aa)

A value other than combined-tier is specified as the value of <tier>-<tier-type> in the Easy Setup definition file. The processing will be interrupted.

Specify combined-tier as the value of <tier>-<tier-type> in the Easy Setup definition file.

The value of <tier>-<j2ee-server-count> is not "1". (value = aa....aa)

A value other than 1 is specified as the value of <tier>-<j2ee-server-count> in the Easy Setup definition file. The processing will be interrupted.

Delete the <tier>-<j2ee-server-count> tag specified in the Easy Setup definition file or specify 1 as the value of <tier>-<j2ee-server-count>.

Multiple definitions of <web-system>-<unit> exist.

Multiple <web-system>-<unit> are defined in the Easy Setup definition file. The processing will be interrupted.

Unify the <web-system>-<unit> definitions in the Easy Setup definition file.

No definition of <logical-server-name> exists that corresponds to the item whose <unit>-<allocated-host>-<define-server>-<logical-server-type> value is aa....aa.

<logical-server-name> is not defined for the items that have aa....aa as the value of <unit>-<allocated-host>-<define-server>-<logical-server-type> in the Easy Setup definition file. The processing will be interrupted.

Add the following <logical-server-name> tag, and define the logical server name in the definition for the logical server with the logical server type aa....aa in the Easy Setup definition file:

<unit>

<allocated-host>

<define-server>

<logical-server-type>aa....aa</logical-server-type>

<logical-server-name>logical-server-name</logical-server-name>

The value of <unit>-<allocated-host>-<define-server>-<logical-server-type> is not "web-server", "j2ee-server", or "performance-tracer". (value = aa....aa)

A value other than web-server, j2ee-server, or performance-tracer is specified as the value of <unit>-<allocated-host>-<define-server>-<logical-server-type> in the Easy Setup definition file. The processing will be interrupted.

Specify web-server, j2ee-server, or performance-tracer as the value of <unit>-<allocated-host>-<define-server>-<logical-server-type> in the Easy Setup definition file.

Multiple definitions of <model-definition>-<host> exist.

Multiple <model-definition>-<host> are defined in the Easy Setup definition file. The processing will be interrupted.

Unify the <model-definition>-<host> definitions in the Easy Setup definition file.

The value of <unit>-<allocated-host>-<host-ref> is not "localhost". (value = aa....aa)

A value other than localhost is specified as the value of <unit>-<allocated-host>-<host-ref> in the Easy Setup definition file. The processing will be interrupted.

Specify localhost as the value of <unit>-<allocated-host>-<host-ref> in the Easy Setup definition file.

The value of <model-definition>-<host>-<host-name> is not "localhost". (value = aa....aa)

A value other than localhost is specified as the value of <model-definition>-<host>-<host-name> in the Easy Setup definition file. The processing will be interrupted.

Specify localhost as the value of <model-definition>-<host>-<host-name> in the Easy Setup definition file.

The value of <model-definition>-<host>-<agent-host> is not "localhost". (value = aa....aa)

A value other than localhost is specified as the value of <model-definition>-<host>-<agent-host> in the Easy Setup definition file. The processing will be interrupted.

Specify localhost as the value of <model-definition>-<host>-<agent-host> in the Easy Setup definition file.

KEOS29222-E (C/W/F)

A syntax error was found in the simple configuration definition file. (line number = aa....aa, column number = bb....bb, details = cc....cc)

aa....aa: Line number

bb....bb: Column number

cc....cc: Details

Description

There is a syntax error in the Easy Setup definition file. The processing will be interrupted.

Action

See the details, remove the cause of the error, and then re-execute the vmx_create_unit command.

KEOS29224-E (C/W/F)

An invalid value was specified for the file. (parameter name = aa....aa, value = bb....bb, file name = cc....cc)

aa....aa: Parameter name

bb....bb: Value

cc....cc: File name

Description

An invalid value was specified in the file. The processing will be interrupted.

Action

Check the contents specified in the file, and then re-execute the command.

KEOS29231-E (C/W/F)

An XML namespace is not specified for the xmlns attribute of <machine-info>. (file name = aa....aa)

aa....aa: File path

Description

The XML namespace is not specified in the xmlns attribute of the <machine-info> tag in the administered machine information file. The processing will be interrupted.

Action

Change the <machine-info> definition in the administered machine information file. The XML namespace for the administered machine information file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/MachineInfo-1.0.

KEOS29232-E (C/W/F)

An unusable XML namespace is specified for the xmlns attribute of <machine-info>. (value = aa....aa, file name = bb....bb)

aa....aa: Value specified in the xmlns attribute of the <machine-info> tag

bb....bb: File path

Description

An unavailable XML namespace is specified in the <machine-info> tag of the administered machine information file. The processing will be interrupted.

Action

Change the <machine-info> definition in the administered machine information file. The XML namespace for the administered machine information file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/MachineInfo-1.0.

KEOS29233-E (C/W/F)

An invalid value is specified. (tag name = aa....aa, invalid value = bb....bb, file name = cc....cc)

aa....aa: Tag name

bb....bb: Value specified for the tag (Invalid value)

cc....cc: File name

Description

The specified value is invalid. The processing will be interrupted.

Action

Check the file contents, and then re-execute the command.

KEOS29234-E (C/W/F)

A syntax error was found in the information file for the management target host. (line number = aa....aa, column number = bb....bb, details = cc....cc)

aa....aa: Line number

bb....bb: Column number

cc....cc: Details

Description

There is a syntax error in the administered machine information file. The processing will be interrupted.

Action

See the details, remove the cause of the error, and then re-execute the operation.

KEOS29301-E (C/W/F)

An error occurred during analysis of the XML file. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An error occurred while parsing the xml file. The processing will be interrupted.

Action

See the details, remove the cause of the error, and then re-execute the operation.

KEOS29302-E (C/W/F)

The specified management target host does not exist. (management target host name = aa....aa)

aa....aa: Management target machine name

Description

The specified management target machine does not exist. The processing will be interrupted.

Action

Specify an existing management target machine name, and then re-execute the operation.

KEOS29303-E (C/W/F)

The management target host specified for deletion contains a virtual server that is working. (management target host name = aa....aa, virtual server name = bb....bb)

aa....aa: Management target machine name

bb....bb: Virtual server name

Description

A virtual server is running in the management target machine you want to delete. The processing will be interrupted.

Action

Stop all the virtual servers (including the failed virtual servers) running on the management target machine.

KEOS29304-E (C/W/F)

An attempt to delete a virtual server failed. (virtual server name = aa....aa, details = bb....bb)

aa....aa: Virtual server name

bb....bb: Details

Description

An attempt to delete the virtual server has failed. The processing continues and another virtual server will be deleted.

Action

See the details, remove the cause of the error, and then delete the virtual server manually.

KEOS29305-I (C/W/F)

Setting the information for the management target host succeeded.

Description

The management target machine information was set up successfully.

KEOS29306-E (C/W/F)

The management target host specified for deletion is being used by a management unit. (management target host name = aa....aa, management unit name = bb....bb)

aa....aa: Management target machine name

bb....bb: Management unit name

Description

The management target machine you tried to delete is being used in a management unit. The processing will be interrupted.

Action

From the management unit operation rule, delete the management target machine you want to delete, and then re-execute the command.

KEOS29311-E (C/W/F)

The information file for the management target host cannot be acquired.

Description

The administered machine information file cannot be acquired. The processing will be interrupted.

Action

Use the vmx_set_machine_info command to execute the processing in an environment where the administered machine information is set up.

KEOS29312-I (C/W/F)

Acquisition of the management target host information succeeded.

Description

The management target machine information was acquired successfully.

KEOS29321-E (C/W/F)

An attempt to copy a master virtual server failed. (server image store host name = aa....aa, details = bb....bb)

aa....aa: Virtual server image management host name at the copy destination

bb....bb: Details

Description

An attempt to copy the master virtual server has failed. The processing will be interrupted.

Action

See the details, remove the cause of the error, and then re-execute the operation.

KEOS29322-E (C/W/F)

An attempt to save the file failed. (file name = aa....aa)

aa....aa: File name

Description

An attempt to save the file has failed. The processing will be interrupted.

Action

Confirm that there is sufficient disk space on the virtual server manager host, and then re-execute the operation.

KEOS29323-E (C/W/F)

An attempt to copy a virtual application server failed. (server image store host name = aa....aa, details = bb....bb)

aa....aa: Virtual server image management host name at the copy destination

bb....bb: Details

Description

An attempt to copy the virtual application server has failed. The processing will be interrupted.

Action

See the details, remove the cause of the error, and then re-execute the operation.

KEOS29324-E (C/W/F)

An attempt to allocate an IP address on an operational network failed. (minimum value = aa....aa, maximum value = bb....bb)

aa....aa: Minimum value

bb....bb: Maximum value

Description

IP address could not be allocated to the business network. The processing will be interrupted.

Action

Revise the range of IP addresses allocated to the business network, and then re-execute the operation.

KEOS29326-E (C/W/F)

An attempt to start a virtual application server failed. (server image store host name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Virtual server image management host name

bb....bb: Virtual server name

cc....cc: Details

Description

An attempt to start the virtual application server has failed. The processing will be interrupted.

Action

See the details, as and when required, remove the cause of the error, use the vmx_delete_unit command to delete the management unit, and then re-execute the operation.

KEOS29328-E (C/W/F)

An attempt to copy an application information file directory failed. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

An attempt to copy the application information file directory has failed. The processing will be interrupted.

Action

See the server communication agent log of the virtual server, and then remove the cause of the error. Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.

KEOS29329-E (C/W/F)

An attempt to build a web system failed. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

An attempt to set up the Web system has failed. The processing will be interrupted.

Action

See the following virtual server log and remove the cause of the error:

Log output by the rasetup command.

ManagementServer log.

Server communication agent log.

Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.

KEOS29331-E (C/W/F)

An attempt to import an application failed. (management unit name = aa....aa, virtual server name = bb....bb, Management Server port number = cc....cc, J2EE server name = dd....dd, port number = ee....ee, file name = ff....ff)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: ManagementServer port number

dd....dd: J2EE server name

ee....ee: Naming service port number

ff....ff: File name

Description

An attempt to import the application has failed. The processing will be interrupted.

Action

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server management command log.

Server communication agent log.

Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.

KEOS29333-E (C/W/F)

An attempt to start an application failed. (management unit name = aa....aa, virtual server name = bb....bb, Management Server port number = cc....cc, J2EE server name = dd....dd, port number = ee....ee, application name = ff....ff)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: ManagementServer port number

dd....dd: J2EE server name

ee....ee: Naming service port number

ff....ff: Application name

Description

An attempt to start the application has failed. The processing will be interrupted.

Action

See the following virtual server log and remove the cause of the error:

ManagementServer log.

Server management command log.

Server communication agent log.

Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.

KEOS29334-E (C/W/F)

An attempt to stop an application failed. (management unit name = aa....aa, virtual server name = bb....bb, Management Server port number = cc....cc, J2EE server name = dd....dd, port number = ee....ee, application name = ff....ff)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: ManagementServer port number

dd....dd: J2EE server name

ee....ee: Naming service port number

ff....ff: Application name

Description

An attempt to stop the application has failed. The processing will be interrupted.

Action

See the following virtual server log, and remove the cause of the error:

ManagementServer log

Server management command log.

Server communication agent log.

Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.

KEOS29335-E (C/W/F)

A batch stop of the logical servers failed. (management unit name = aa....aa, virtual server name = bb....bb, Management Server port number = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: ManagementServer port number

Description

An attempt to batch stop the logical servers has failed. The processing will be interrupted.

Action

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server communication agent log.

Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.

KEOS29336-E (C/W/F)

An attempt to stop Management Server failed. (management unit name = aa....aa, virtual server name = bb....bb, Management Server port number = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: ManagementServer port number

Description

An attempt to stop the Management Server has failed. The processing will be interrupted.

Action

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server communication agent log.

Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.

KEOS29337-E (C/W/F)

An attempt to stop Administration Agent failed. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

An attempt to stop the Administration Agent has failed. The processing will be interrupted.

Action

See the following virtual server log, and remove the cause of the error:

Administration Agent log.

Server communication agent log.

Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.

KEOS29339-E (C/W/F)

The value specified for the parameter is invalid. (option = aa....aa, value = bb....bb)

aa....aa: Option name

bb....bb: Value

Description

The value specified in the argument is invalid. The processing will be interrupted.

Action

Check the value, and then re-execute the operation.

KEOS29343-E (C/W/F)

In the virtual server property file, the specified minimum value for allotment of IP addresses is above the maximum value. (file name = aa....aa, parameter name = bb....bb, minimum value = cc....cc, parameter name = dd....dd, maximum value = ee....ee)

aa....aa: File name

bb....bb: Parameter name

cc....cc: Value

dd....dd: Parameter name

ee....ee: Value

Description

The minimum value of the allocated IP address specified in the property file for virtual server setup exceeds the maximum value. The processing will be interrupted.

Action

Check the parameters and values in such a way so that the minimum value of the allocated IP address of the management unit does not exceed the maximum value, and then re-execute the operation.

KEOS29344-E (C/W/F)

In the virtual server property file, the range for allotment of operation IP addresses overlaps with the range for management IP addresses. (file name = aa....aa, operation IP parameter name = bb....bb, operation IP minimum value = cc....cc, operation IP parameter name = dd....dd, operation IP maximum value = ee....ee, management IP parameter name = ff....ff, management IP minimum value = gg....gg, management IP parameter name = hh....hh, management IP maximum value = ii....ii)

aa....aa: File name

bb....bb: Parameter name of the minimum operation IP value

cc....cc: Value of the minimum operation IP value

dd....dd: Parameter name of the maximum operation IP value

ee....ee: Value of the maximum operation IP value

ff....ff: Parameter name of the minimum management IP value

gg....gg: Value of the minimum management IP value

hh....hh: Parameter name of the maximum management IP value

ii....ii: Value of the maximum management IP value

Description

The allocated IP address range of the property file for virtual server setup overlaps the allocated IP address range for the other management units. The processing will be interrupted.

Action

Check the parameters and values in such a way so that the allocated IP address range does not overlap with the range set up in the other management units, and then re-execute the operation.

KEOS29345-I (C/W/F)

Creation of management unit succeeded. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The management unit was created successfully.

KEOS29347-E (C/W/F)

An attempt to allocate an IP address on a management network failed. (minimum value = aa....aa, maximum value = bb....bb)

aa....aa: Minimum value

bb....bb: Maximum value

Description

The management network IP address could not be allocated. The processing will be interrupted.

Action

Revise the allocation range of the management network IP address, and then re-execute the operation.

KEOS29348-E (C/W/F)

An attempt to stop a virtual application server failed. (server image store host name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Virtual server image management host name

bb....bb: Virtual server name

cc....cc: Details

Description

An attempt to stop the virtual application server has failed. The processing will be interrupted.

Action

See the details, and then remove the cause of the error. Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.

KEOS29349-E (C/W/F)

An attempt to confirm whether the virtual application server started has failed. (server image store host name = aa....aa, virtual server name = bb....bb)

aa....aa: Administered machine name

bb....bb: Virtual server name

Description

An attempt to confirm the start of the virtual application server has failed. The processing will be interrupted.

Action

If "Connection timed out" is output in the details for the previous message, revise the value of vmx.virtualserver.start.timeout in the virtual server manager property file. In the case of any other message, see the server communication agent log of the virtual server, and then remove the cause of the error. Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.

KEOS29350-E (C/W/F)

Application name cannot be acquired. (application file name = aa....aa, details = bb....bb)

aa....aa: Application file name

bb....bb: Details

Description

An attempt to acquire the application name has failed. The processing will be interrupted.

Action

See the details, and then remove the cause of the error. Use the vmx_delete_unit command to delete the failed virtual application server, and then re-execute the operation.

KEOS29355-I (C/W/F)

Deployment of the management unit succeeded. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The management unit was deployed successfully.

KEOS29356-W (C/W/F)

Deployment of the management unit partially succeeded. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The deployment of the management unit was partially successful. The processing continues.

Action

See the log, remove the cause of the error, and then re-execute the operation.

KEOS29357-E (C/W/F)

Deployment of the management unit failed. (management unit name = aa....aa)

aa....aa: Management unit name

Description

An attempt to deploy the management unit has failed. The processing will be interrupted.

Action

See the log, remove the cause of the error, and then re-execute the operation.

KEOS29358-E (C/W/F)

An attempt to delete a virtual server failed. (host name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Management target machine name or virtual server image management host name

bb....bb: Virtual server name

cc....cc: Details

Description

An attempt to delete the virtual server has failed. If the vmx_deploy_unit command was executed, the processing continues and another virtual server will be started. If the vmx_update_unit command or the vmx_delete_unit command was executed, the processing will be interrupted.

Action

If an error occurs in the vmx_deploy_unit command, see the details, remove the cause of the error, and then manually delete the virtual server from VMware vCenter Server. If an error occurs in the vmx_update_unit command or vmx_delete_unit command, see the details, remove the cause of the error, and then re-execute the command.

KEOS29359-E (C/W/F)

An attempt to start Administration Agent failed. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

An attempt to start the Administration Agent has failed. The processing will be interrupted.

Action

See the following virtual server log, and remove the cause of the error:

Administration Agent log.

Server communication agent log.

After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.

KEOS29360-E (C/W/F)

An attempt to start Management Server failed. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

An attempt to start the Management Server has failed. The processing will be interrupted.

Action

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server communication agent log.

After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.

KEOS29361-E (C/W/F)

An attempt to create a host definition file for scale-out failed. (management unit name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Details

Description

An attempt to create the host definition file for scale out has failed. The processing will be interrupted.

Action

See the details, remove the cause of the error, and then re-execute the operation.

KEOS29362-E (C/W/F)

An attempt to copy a file using the server communication agent failed. (management unit name = aa....aa, virtual server name = bb....bb, copy source local path = cc....cc, copy target remote path = dd....dd)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Copy source local path

dd....dd: Copy destination remote path

Description

An attempt to copy the file in the server communication agent has failed. The processing will be interrupted.

Action

See the server communication agent log of the virtual server, and then remove the cause of the error. After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.

KEOS29363-E (C/W/F)

An attempt to execute the cmx_scaleout_host command failed. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

An attempt to execute the cmx_scaleout_host command has failed. The processing will be interrupted.

Action

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server communication agent log.

After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.

KEOS29364-E (C/W/F)

An attempt to create a configuration change definition file failed. (management unit name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Details

Description

An attempt to create the configuration change definition file has failed. The processing will be interrupted.

Action

See the details, remove the cause of the error, and then re-execute the operation.

KEOS29365-E (C/W/F)

An attempt to execute the cmx_change_mode command failed. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

An attempt to execute the cmx_change_model command has failed. The processing will be interrupted.

Action

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server communication agent log.

After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.

KEOS29366-E (C/W/F)

An attempt to execute the cmx_build_system command failed. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

An attempt to execute the cmx_build_system command has failed. The processing will be interrupted.

Action

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server communication agent log.

After finishing the investigation, delete the virtual server from VMware vCenter Server, and re-execute the processing as and when required.

KEOS29367-E (C/W/F)

An attempt to start a logical server failed. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

An attempt to start the logical server has failed. The processing will be interrupted.

Action

See the following virtual server log and remove the cause of the error:

ManagementServer log.

Server communication agent log.

After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.

KEOS29368-E (C/W/F)

An attempt to start an application failed. (management unit name = aa....aa, virtual server name = bb....bb, application name = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Application name

Description

An attempt to start the application has failed. The processing will be interrupted.

Action

See the following virtual server log and remove the cause of the error:

ManagementServer log.

Server management command log.

Server communication agent log.

After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.

KEOS29369-E (C/W/F)

An attempt to stop a logical server failed. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

An attempt to stop the logical server has failed. The processing will be interrupted.

Action

See the following virtual server log and remove the cause of the error:

ManagementServer log.

Server communication agent log.

After finishing the investigation, delete the virtual server from VMware vCenter Server, and then re-execute the processing as and when required.

KEOS29371-E (C/W/F)

An exception occurred during creation of a temporary file. (details = aa....aa)

aa....aa: Details

Description

An attempt to create a temporary file has failed. If the vmx_deploy_unit command is executed, the processing continues, and then another virtual server starts. If the vmx_rolling_update command is executed, the processing will be interrupted.

Action

See the details, remove the cause of the error, and then delete manually.

KEOS29372-E (C/W/F)

An attempt to read the file failed. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An attempt to read the file has failed. If the vmx_deploy_unit command is executed, the processing continues, and then another virtual server starts. If the vmx_rolling_update command is executed, the processing will be interrupted.

Action

Confirm that you have the permission to access the file.

KEOS29374-W (C/W/F)

The specified management unit is already deployed. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The specified management unit is already deployed. The processing will be interrupted.

Action

Check whether there is an error in the specified management unit name. If there is an error, specify the correct management unit name, and then re-execute the operation.

KEOS29375-E (C/W/F)

An attempt to deploy a virtual application server failed. (management target host name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Administered machine name

bb....bb: Virtual server name

cc....cc: Details

Description

An attempt to deploy the virtual application server has failed. The processing continues, and another virtual application server is deployed.

Action

Remove the cause of the error based on the details described in the following table, and then delete the virtual application server manually.

Table 13‒8: List of error details described in KEOS29375-E

Details

Description

Action

An exception occurred during creation of a temporary file. (details = aa....aa)

aa....aa: Details

A failure occurred while creating the temporary file. If the vmx_deploy_unit command or the vmx_start_unit command was executed, the processing continues, and another virtual server starts. If the vmx_scaleout_unit command is executed, the processing will be interrupted.

See the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to start Administration Agent failed.

An attempt to start the Administration Agent has failed. If the vmx_deploy_unit command or the vmx_start_unit command was executed, the processing continues and another virtual server will be started. If the vmx_scaleout_unit command was executed, the processing will be interrupted.

See the following virtual server log, and remove the cause of the error:

Administration Agent log.

Server communication agent log.

When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to start the Management Server failed.

An attempt to start the Management Server has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server communication agent log.

When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to create a host definition file for scale-out failed. (details = aa....aa)

aa....aa: Details

An attempt to create the host definition file for scale out has failed. The processing continues, and another virtual server will start.

See the details, remove the cause of the error, and then re-execute the operation.

An attempt to copy a file failed. (copy source local path = aa....aa, copy target remote path = bb....bb, details = cc....cc)

aa....aa: Copy source local path

bb....bb: Copy destination remote path

cc....cc: Details

An attempt to copy the file has failed. The processing continues and another virtual server will start.

See the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to execute the cmx_scaleout_host command failed.

An attempt to execute the cmx_scaleout_host command has failed. The processing continues and another virtual server will start.

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server communication agent log.

When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to create a configuration change definition file failed. (details = aa....aa)

aa....aa: Details

An attempt to create the configuration change definition file has failed. The processing continues and another virtual server will start.

See the details, remove the cause of the error, and then re-execute the operation.

An attempt to execute the cmx_change_model command failed.

An attempt to execute the cmx_change_model command has failed. The processing continues and another virtual server will start.

See the following virtual server log and remove the cause of the error:

ManagementServer log.

Server communication agent log.

When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to execute the cmx_build_system command failed.

An attempt to execute the cmx_build_system command has failed. The processing continues and another virtual server will start.

See the following virtual server log and remove the cause of the error:

ManagementServer log.

Server communication agent log.

When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to start a logical server failed.

An attempt to start the logical server has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server communication agent log.

When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to stop a logical server failed.

An attempt to stop the logical server has failed. If the vmx_deploy_unit command is executed, the processing continues and another virtual server will start. If the vmx_stop_unit command is executed, the processing continues and another virtual server will stop. If the vmx_scalein_unit command is executed, the processing will be interrupted.

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server communication agent log.

When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to start an application failed. (application name = aa....aa)

aa....aa: Application name

An attempt to start the application has failed. The processing continues, and another virtual server will start.

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server management command log.

Server communication agent log.

When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to stop a virtual server failed. (details = aa....aa)

aa....aa: Details

An attempt to stop the virtual server has failed. The processing continues, and another virtual server will start.

See the details, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to confirm whether the virtual server stopped has failed. (details = aa....aa)

aa....aa: Details

An attempt to confirm the stopping of the virtual server has failed. If the vmx_deploy_unit command is executed, the processing continues and another virtual server will start. If the vmx_stop_unit command is executed, the processing continues and another virtual server will stop. If the vmx_scalein_unit command is executed, the processing will be interrupted.

Revise the value of vmx.virtualserver.stop.timeout in the virtual server manager property file. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to start a virtual server failed. (details = aa....aa)

aa....aa: Details

An attempt to start the virtual server has failed. The processing continues, and another virtual server will start.

See the details, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to confirm whether the virtual server started has failed.

An attempt to confirm the starting of the virtual server has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.

If "Connection timed out" is output to the details for the previous message, revise the value of vmx.virtualserver.start.timeout in the virtual server manager property file. In the case of any other message, see the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to copy a virtual application server failed. (details = aa....aa)

aa....aa: Details

An attempt to copy the virtual application server has failed. The processing continues, and another virtual application server is copied.

See the details, remove the cause of the error, and then re-execute the command when required.

An attempt to copy a user script failed.

An attempt to copy the virtual server runtime user script has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.

See the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to execute a user script failed.

An attempt to execute the virtual server runtime user script has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.

See the server communication agent log of the virtual server, and then remove the cause of the error. Also, use the vmx_create_unit command or the vmx_update_unit command to confirm that the description of the specified virtual server runtime user script is correct. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to set the server communication agent to start automatically failed.

An attempt to specify settings to automatically start the server communication agent has failed. The processing continues, and another virtual server will start.

See the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to rewrite the hosts file failed.

An attempt to rewrite the hosts file failed. The processing continues, and the other virtual servers will be started.

See the action to be taken for the error message output just before this message. If no error message was output, see the server communication agent log of the virtual server, and then remove the cause of the error.

When the investigation is complete, stop and delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

KEOS29376-W (C/W/F)

The management unit cannot be deployed because a management target host has not been configured for it. (management unit name = aa....aa, management target host name = bb....bb)

aa....aa: Management unit name

bb....bb: Management target machine name

Description

The management unit cannot be deployed because the management target host to be used in the management unit has not been configured. The processing continues, and the processing for the other management target hosts will be executed.

Action

Use the vmx_set_machine_info command to set up the administered machine that will be used in the management unit, and then re-execute the command.

KEOS29377-W (C/W/F)

A virtual server cannot be deployed because it is working. (management unit name = aa....aa, management target host name = bb....bb, virtual server name = cc....cc)

aa....aa: Management unit name

bb....bb: Management target machine name

cc....cc: Virtual server name

Description

The virtual server cannot be deployed because the server is running. The processing continues and the processing for another virtual server will be executed.

Action

Scale in the virtual servers that are not the current version, and then re-execute the command.

KEOS29378-I (C/W/F)

A virtual server cannot be deployed because it is the current version. (management unit name = aa....aa, management target host name = bb....bb, virtual server name = cc....cc)

aa....aa: Management unit name

bb....bb: Management target machine name

cc....cc: Virtual server name

Description

The virtual server cannot be deployed because the server version is the current version. The processing continues, and the processing for another virtual server will be executed.

KEOS29379-W (C/W/F)

A virtual server cannot be deployed because it is currently malfunctioning. (management unit name = aa....aa, management target host name = bb....bb, virtual server name = cc....cc)

aa....aa: Management unit name

bb....bb: Management target machine name

cc....cc: Virtual server name

Description

The virtual server cannot be deployed because the server has failed. The processing continues and the processing for another virtual server will be executed.

Action

To deploy the virtual server, delete the virtual server from VMware vCenter Server manually, and then re-execute the command.

KEOS29380-W (C/W/F)

One or more working or malfunctioning virtual servers exist in management target hosts that are not used by a management unit. (management target host name = aa....aa, virtual server name = bb....bb)

aa....aa: Administered machine name

bb....bb: Virtual server name

Description

A failed or running virtual server exists on an administered machine other than the administered machine to be used in the management unit. The processing continues and the deploy processing will be executed.

Action

Delete or stop the virtual servers existing on the administered machines that are not used in the management unit, and then re-execute the command.

KEOS29381-I (C/W/F)

Management unit updated. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The management unit was successfully updated.

KEOS29382-E (C/W/F)

An attempt was made to delete the oldest version of the specified management unit, but a current version cannot be deleted. (management unit name = aa....aa, virtual application server version = bb....bb)

aa....aa: Management unit name

bb....bb: Version number of the virtual application server

Description

An attempt was made to delete the oldest version of the specified management unit, but the version could not be deleted because it is the current version. The processing will be interrupted.

Action

Check the versions of the virtual application server belonging to the management unit, delete the virtual application server versions that are not required, and then re-execute the operation.

KEOS29394-I (C/W/F)

Management unit deleted. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The management unit was successfully deleted.

KEOS29395-E (C/W/F)

An attempt to delete management unit failed, because a working virtual server exists. (virtual server name = aa....aa)

aa....aa: Virtual server name

Description

The management unit cannot be deleted because a virtual server is running. The processing will be interrupted.

Action

Stop the virtual server, and then re-execute the operation.

KEOS29396-E (C/W/F)

An attempt to delete management unit failed, because a malfunctioning virtual server exists. (virtual server name = aa....aa)

aa....aa: Virtual server name

Description

The management unit cannot be deleted because a virtual server has failed. The processing will be interrupted.

Action

Manually delete the checked virtual servers from VMware vCenter Server, and then re-execute the operation.

KEOS29401-E (C/W/F)

An invalid value was specified as the argument for the aa....aa option.

aa....aa: Specified option

Description

An invalid number was specified in the argument for the option aa....aa. The processing will be interrupted.

Action

Check whether the argument has an error. If an error exists, correct it, and then execute the command.

KEOS29402-E (C/W/F)

The specified version is already set as the current version. (management unit name = aa....aa, version = bb....bb)

aa....aa: Management unit name

bb....bb: Version

Description

The specified version is already set up as the current version. The processing of the command will be interrupted.

Action

Check the management unit name and version number where the current version will be set up, and then re-execute the operation.

KEOS29403-E (C/W/F)

The specified version is malfunctioning. (management unit name = aa....aa, version = bb....bb)

aa....aa: Management unit name

bb....bb: Version

Description

The specified version is an error. The processing will be interrupted.

Action

Confirm that a failure does not occur in the version, and then re-execute the operation.

KEOS29404-E (C/W/F)

The specified version number does not exist in the specified management unit. (management unit name = aa....aa, version = bb....bb)

aa....aa: Management unit name

bb....bb: Version

Description

The specified version number does not exist in the specified management unit. The processing of the command will be interrupted.

Action

Specify an existing version number.

KEOS29405-I (C/W/F)

Setting the status of the virtual application server completed normally. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The setup status of the virtual application server has finished successfully.

KEOS29411-E (C/W/F)

The specified management unit does not exist. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The specified management unit does not exist. The processing of the command will be interrupted.

Action

Check the management unit name, and then re-execute the operation.

KEOS29413-E (C/W/F)

An attempt to update a virtual server failed because copying of the image of a virtual application server failed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Administered machine name

Description

An attempt to copy the virtual application server image has failed because the update failed. The processing of the command will be interrupted.

Action

Check whether a virtual server with the same name exists. If such a virtual server exists, confirm that the virtual server with the same name is not used, and then delete the virtual server. After this, re-execute the command.

KEOS29414-E (C/W/F)

An attempt to delete an older-version virtual server failed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Administered machine name

Description

An attempt to delete a virtual server of an old version has failed. The processing of the command will be interrupted.

Action

Check whether you have the permission to access the administered machine.

KEOS29416-E (C/W/F)

An attempt to deploy a new virtual server failed because acquisition of an IP address failed. (management unit name = aa....aa, management target host name = bb....bb)

aa....aa: Management unit name

bb....bb: Administered machine name

Description

An attempt to deploy the new virtual server has failed because an attempt to acquire the IP address failed. The processing of the command will be interrupted.

Action

Check whether the IP address is missing.

KEOS29417-E (C/W/F)

An attempt to update a virtual server failed because configuration of the virtual server failed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Administered machine name

Description

An attempt to update the virtual server has failed because the virtual server setup failed. The processing of the command will be interrupted.

Action

See the previous error message, remove the cause of the error, and then re-execute the command.

KEOS29418-E (C/W/F)

An attempt to update a virtual server failed because stopping the virtual server failed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Administered machine name

Description

An attempt to update the virtual server has failed because an attempt to stop the virtual server failed. The processing of the command will be interrupted.

Action

Check why the virtual server cannot be stopped, remove the cause of the error, and then re-execute the command.

KEOS29419-W (C/W/F)

A virtual server will be deployed because the number of deployed servers is less than the initial number. (management unit name = aa....aa, management target host name = bb....bb)

aa....aa: Management unit name

bb....bb: Administered machine name

Description

The virtual server will be deployed because the number is less than the initial deployment count. The processing of the command will be interrupted.

KEOS29420-E (C/W/F)

An attempt to update a virtual server failed because the current status of the virtual server does not allow updates. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc, virtual server status = dd....dd)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Administered machine name

dd....dd: Virtual server status

Description

An attempt to update the virtual server has failed because the virtual server status cannot be updated. The processing of the command will be interrupted.

Action

Check the cause of the error for the virtual server with the failed status, and then delete that virtual server.

KEOS29423-E (C/W/F)

An attempt to update a virtual server failed because startup of the virtual server failed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc, details = dd....dd)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Administered machine name

dd....dd: Details

Description

An attempt to update the virtual server has failed because an attempt to start the virtual server failed. The processing of the command will be interrupted.

Action

See the details, remove the cause of the error, and then re-execute the command.

KEOS29424-I (C/W/F)

The stopped virtual server has been updated. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Administered machine name

Description

A stopped virtual server was updated.

KEOS29425-I (C/W/F)

The working virtual server has been updated. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Administered machine name

Description

A running virtual server was updated.

KEOS29426-I (C/W/F)

A virtual server has been deployed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Administered machine name

Description

The virtual server is deployed.

KEOS29427-E (C/W/F)

An attempt to start a web system failed. (unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Administered machine name

Description

An attempt to start the Web system has failed. The processing of the command will be interrupted.

Action

See the error message, remove the cause of the error, and then re-execute the command.

KEOS29428-E (C/W/F)

An attempt to stop a web system failed. (unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Administered machine name

Description

An attempt to stop the Web system has failed. The processing of the command will be interrupted.

Action

See the error message, remove the cause of the error, and then re-execute the command.

KEOS29429-W (C/W/F)

The virtual server has already been updated. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Administered machine name

Description

The virtual server has already been updated.

KEOS29430-I (C/W/F)

Rolling update of the virtual servers completed successfully. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The rolling update of the virtual servers was successful.

KEOS29431-W (C/W/F)

An attempt to perform a rolling update of the virtual servers was made, but some virtual servers failed to update. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The rolling update of the virtual servers was executed, but an attempt to update some of the virtual servers has failed.

KEOS29432-E (C/W/F)

An attempt to perform a rolling update of the virtual servers failed. (management unit name = aa....aa)

aa....aa: Management unit name

Description

An attempt to perform rolling update of the virtual servers has failed.

Action

See the error message, remove the cause of the error, and then re-execute the command.

KEOS29433-E (C/W/F)

An attempt to create a temporary directory to store user scripts failed. (management unit name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Details

Description

An attempt to create the temporary directory for storing the virtual server runtime user script has failed. The processing will be interrupted.

Action

See the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

KEOS29434-E (C/W/F)

An attempt to execute a user script failed. (management unit name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Details

Description

An attempt to execute the virtual server runtime user script has failed. The processing will be interrupted.

Action

See the server communication agent log of the virtual server, and then remove the cause of the error. Also, use the vmx_create_unit command or vmx_update_unit command to confirm that the description of the specified virtual server runtime user script is correct. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

KEOS29435-W (C/W/F)

The virtual server will be undeployed because the default deploy count has been exceeded. (management unit name = aa....aa, management target host name = bb....bb)

aa....aa: Management unit name

bb....bb: Management target host name

Description

The virtual server will be undeployed because the number of deployed virtual servers exceeded the value in the unit.rule.deploy.num property of the management unit operation tool. The processing continues, and the other virtual servers will be updated.

KEOS29436-I (C/W/F)

The virtual server has been undeployed. (management unit name = aa....aa, virtual server name = bb....bb, management target host name = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Management target host name

Description

The virtual server has been undeployed.

KEOS29437-W (C/W/F)

The undeploy operation could not be completed because a running or failed virtual server was found. (management unit name = aa....aa, management target host name = bb....bb)

aa....aa: Management unit name

bb....bb: Management target host name

Description

The undeploy operation could not be completed because a running or failed virtual server was found. The processing continues, and the other virtual servers will be updated.

KEOS29438-E (C/W/F)

An attempt to set the server communication agent to start automatically failed.(management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

An attempt to specify settings to automatically start the server communication agent has failed. The processing will be interrupted.

Action

See the server communication agent log of the virtual server, and then remove the cause of the error. After finishing the investigation, delete the virtual server from VMware vCenter Server, and re-execute the processing as and when required.

KEOS29441-E (C/W/F)

A virtual server that is not the current version is working. (management target host name = aa....aa, virtual server name = bb....bb)

aa....aa: Management target machine name

bb....bb: Virtual server name

Description

A virtual server of a version that is not the current version is running. The processing will be interrupted.

Action

Use the vmx_scalein_unit command to stop the virtual server of the version that is not the current version, and then re-execute the operation.

KEOS29442-I (C/W/F)

A virtual server is already working. (management target host name = aa....aa, virtual server name = bb....bb)

aa....aa: Management target machine name

bb....bb: Virtual server name

Description

The virtual server is already running. The processing continues.

KEOS29443-W (C/W/F)

The number of virtual servers that are expected to be working are already running. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The number of virtual servers that must be started are already running. The processing continues.

Action

If the virtual servers are not sufficient, use the vmx_scaleout_unit command to start the virtual servers.

KEOS29444-I (C/W/F)

A management unit started. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The management unit is started. The processing will end.

KEOS29445-E (C/W/F)

An attempt to start a management unit failed. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The management unit cannot be started. The processing will end.

Action

Check the previous message. If an error has occurred, remove the cause of the error.

KEOS29446-W (C/W/F)

Some virtual servers could not be started. (management unit name = aa....aa)

aa....aa: Management unit name

Description

Some of the virtual servers could not be started. The processing will end.

Action

Check the previous message. If an error has occurred, remove the cause of the error. If no error has occurred, revise the value of unit.rule.start.num in the management unit operation rule.

KEOS29447-E (C/W/F)

An attempt to start a virtual server failed. (management target host name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Administered machine name

bb....bb: Virtual server name

cc....cc: Details

Description

An attempt to start the virtual server has failed. If the vmx_start_unit command was executed, the processing continues and another virtual server will be started. If the vmx_scaleout_unit command was executed, the processing will be interrupted.

Action

Remove the cause of the error based on the details described in the following table, and then delete the virtual server manually.

Table 13‒9: List of error details described in KEOS29447-E

Details

Description

Action

An exception occurred during creation of a temporary file. (details = aa....aa)

aa....aa: Details

An attempt to create a temporary file has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.

See the server communication agent log of the virtual server, and remove the cause of the error. After finishing the investigation, delete the virtual server from VMware vCenter Server, and re-execute the processing as and when required.

An attempt to start Administration Agent failed.

An attempt to start the Administration Agent has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, and the processing will be interrupted.

See the following virtual server log, and remove the cause of the error:

Administration Agent log.

Server communication agent log.

When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to start Management Server failed.

An attempt to start the Management Server has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server communication agent log.

When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to start a logical server failed.

An attempt to start the logical server has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server communication agent log.

When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to confirm whether the virtual server started has failed.

An attempt to confirm the starting of the virtual server has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.

If "Connection timed out" is output in the details for the previous message, revise the value of vmx.virtualserver.start.timeout in the virtual server manager property file. In the case of any other message, see the server communication agent log of the virtual server, and then remove the cause of the error. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to copy a user script failed.

An attempt to copy the virtual server runtime user script has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.

See the server communication agent log of the virtual server, and then remove the cause of the error. After finishing the investigation, delete the virtual server from VMware vCenter Server, and re-execute the processing as and when required.

An attempt to execute a user script failed.

An attempt to execute the virtual server runtime user script has failed. If the vmx_deploy_unit command or the vmx_start_unit command is executed, the processing continues, and another virtual server will start. If the vmx_scaleout_unit command is executed, the processing will be interrupted.

See the server communication agent log of the virtual server, and then remove the cause of the error. Also, use the vmx_create_unit command or the vmx_update_unit command to confirm that the description of the specified virtual server runtime user script is correct. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

KEOS29449-I (C/W/F)

A virtual server started. (management target host name = aa....aa, virtual server name = bb....bb)

aa....aa: Management target machine name

bb....bb: Virtual server name

Description

The virtual server was started.

KEOS29451-W (C/W/F)

The management target host specified in the management unit operational rules does not exist. (management unit name = aa....aa, management target host name = bb....bb)

aa....aa: Management unit

bb....bb: Management target machine name

Description

The management target machine specified in the management unit operation rule does not exist. The processing continues.

Action

Use the vmx_set_machine_info command to set up the management target machine information.

KEOS29461-E (C/W/F)

No virtual servers are working. (management unit name = aa....aa)

aa....aa: Management unit name

Description

A running virtual server does not exist. The processing will be interrupted.

Action

If no virtual server is running, the processing cannot be executed.

KEOS29462-I (C/W/F)

A management unit stopped. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The management unit was stopped. The processing will end.

KEOS29463-E (C/W/F)

One or more of the virtual servers managed by the management unit could not be stopped. (management unit name = aa....aa)

aa....aa: Management unit name

Description

All or some of the virtual servers managed by the management unit could not be stopped. The processing will end.

Action

Manually stop the virtual servers that are already running.

KEOS29465-E (C/W/F)

An attempt to collect vm log data failed. (management target host name = aa....aa, virtual server name = bb....bb)

aa....aa: Management target machine name

bb....bb: Virtual server name

Description

An error occurred during the collection of the vm log. The processing continues and another virtual server will be stopped.

Action

See the following virtual server log, and then remove the cause of the error:

ManagementServer log.

Server communication agent log.

After the investigation is complete, re-execute the operation as and when required.

KEOS29466-E (C/W/F)

An attempt to stop a virtual server failed. (management target host name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Management target machine name

bb....bb: Virtual server name

cc....cc: Details

Description

An attempt to stop the virtual server has failed. If the vmx_stop_unit command is executed, the processing continues and another virtual server will be stopped. If the vmx_scalein_unit command was executed, the processing will be interrupted.

Action

Remove the cause of the error based on the details described in the following table, and then use the vmx_scalein_unit command to stop the virtual server.

Table 13‒10: List of error details described in KEOS29466-E

Details

Description

Action

An attempt to stop a logical server failed.

An attempt to stop the logical server has failed. If the vmx_deploy_unit command is executed, the processing continues, and another virtual server will start. If the vmx_stop_unit command is executed, the processing continues, and another virtual server will stop. If the vmx_scalein_unit command is executed, the processing will be interrupted.

See the following virtual server log, and remove the cause of the error:

ManagementServer log.

Server communication agent log.

When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the operation as and when required.

An attempt to confirm whether the virtual server stopped has failed. (details = aa....aa)

aa....aa: Details

An attempt to confirm the stopping of the virtual server has failed. If the vmx_deploy_unit command is executed, the processing continues, and another virtual server will start. If the vmx_stop_unit command is executed, the processing continues, and another virtual server will stop. If the vmx_scalein_unit command is executed, the processing will be interrupted.

Revise the value of vmx.virtualserver.stop.timeout in the virtual server manager property file. When the investigation is complete, delete the virtual server from VMware vCenter Server, and then re-execute the command as and when required.

KEOS29471-E (C/W/F)

The specified management target host does not exist. (management target host name = aa....aa)

aa....aa: Management target machine name

Description

The specified management target machine does not exist. The processing will be interrupted.

Action

Specify an existing management target machine name, and then re-execute the operation.

KEOS29472-E (C/W/F)

An attempt to start a virtual server failed. (management target host name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Management target machine name

bb....bb: Virtual server name

cc....cc: Details

Description

An attempt to start the virtual server has failed. The processing continues and another virtual server will be started.

Action

If an error occurs, see the details and remove the cause of the error as and when required.

KEOS29473-E (C/W/F)

The management unit does not contain any virtual servers that can be started. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The virtual servers that can be started in the management unit do not exist. The processing will be interrupted.

Action

Check whether the management unit is already deployed or whether all the virtual servers have failed.

KEOS29474-I (C/W/F)

The management unit completed scale-out successfully. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

The management unit was successfully scaled out.

KEOS29475-E (C/W/F)

The specified management target host is not used by the management unit. (management unit name = aa....aa, management target host name = bb....bb)

aa....aa: Management unit name

bb....bb: Management target machine name

Description

The specified management target machine cannot be used in the management unit. The processing will be interrupted.

Action

Specify an management target machine that is used in the management unit, and then re-execute the command.

KEOS29481-E (C/W/F)

The specified virtual server does not exist. (virtual server name = aa....aa)

aa....aa: Virtual server name

Description

The specified virtual server does not exist. The processing will be interrupted.

Action

Check the specified virtual server name, and then re-execute the operation.

KEOS29482-E (C/W/F)

The specified virtual is either malfunctioning or already stopped. (virtual server name = aa....aa)

aa....aa: Virtual server name

Description

The specified virtual server has already stopped or failed. The processing will be interrupted.

Action

Select a virtual server that has not stopped or failed, and then re-execute the operation.

KEOS29484-I (C/W/F)

The management unit completed scale-in successfully. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

The management unit was successfully scaled in.

KEOS29491-E (C/W/F)

The management unit operational rules could not be opened. (management unit name = aa....aa, details = bb....bb)

aa....aa: Management unit name

bb....bb: Details

Description

The management unit operation rule does not open. The processing of the command will be interrupted.

Action

The management unit operation rule is corrupted. Contact maintenance personnel.

KEOS29492-I (C/W/F)

The management unit operational rules have been exported. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The management unit operation rule was exported.

KEOS29501-E (C/W/F)

An attempt to delete deployed virtual servers that are not management target hosts used by the management unit failed. (management target host name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Management target machine name

bb....bb: Virtual server name

cc....cc: Details

Description

An attempt to delete the virtual server of the management target machine that is not used in the management unit has failed. The processing continues and another virtual server will be started.

Action

See the details, remove the cause of the error, and then delete the virtual server.

KEOS29502-E (C/W/F)

An attempt to rewrite the hosts file failed. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

An attempt to rewrite the hosts file failed. The processing will be cancelled.

Action

See the action to be taken for the error message output just before this message.

If no error message was output, see the server communication agent log of the virtual server, and then remove the cause of the error.

When the investigation is complete, stop the virtual server from VMware vCenter Server as and when required.

If an error occurs in the vmx_create_unit or vmx_update_unit commands, use the vmx_delete_unit command to delete the virtual application server with error, and then re-execute the operation.

If an error occurs in the vmx_rolling_update command, stop and delete the virtual server from VMware vCenter Server, and then re-execute the command.

KEOS29601-I (C)

Usage :

Description

This message describes the usage method of the command.

KEOS29602-E (C)

Usage :

Description

The command format is incorrect.

The processing will be cancelled.

Action

Check the usage method displayed in the Usage.

Specify the correct command format, and then re-execute the command.

KEOS29603-E (C/F)

The host or user ID is not specified in the common arguments.

Description

The host or user ID are not specified in any of the following common arguments:

Command line arguments

.vmirc (client settings property file)

vmiclient.properties (client common configuration file)

The processing will be cancelled.

Action

To specify the host or user ID in common arguments

Make sure that the host or user ID are specified, and then re-execute the command.

To use the default values

Make sure that the vmi.connect.m key and vmi.connect.u key is set up in .vmirc (client settings property file) or vmiclient.properties (client common configuration file), and then re-execute the command.

KEOS29604-E (C/F)

The specified host name or port number is invalid. (details = aa....aa)

aa....aa: Details

Description

An invalid value has been specified in the host name or port number.

The processing will be cancelled.

Action

To specify the host name or port number in the common arguments

Check how the host name and port number have been specified, and then re-execute the command.

To use the default value

Make sure that an invalid value has not been set up in the vmi.connect.m key of .vmirc (client settings property file) or vmiclient.properties (client common configuration file), and then re-execute the command.

KEOS29605-E (C/F)

There was a communication failure with the client. (details = aa....aa)

aa....aa: Details

Description

There was a communication failure with the client.

The processing will be cancelled.

Action

The possible causes are as follows. Remove the cause of the error, and then re-execute the command.

The virtual server manager is not running.

Check the running status of the virtual server manager.

The host name or port number specified in the -m option of the common arguments is incorrect.

Check the value specified for the host name and port number in the -m option of the common arguments. If the default value is being used, make sure that the vmi.connect.m key and vmi.connect.u key are set up in the .vmirc (client settings property file) or vmiclient.properties (client common configuration file).

The combination of the connection source and destination products cannot be connected.

Check whether the combination of the connection source and destination products can be connected.

There is a network problem.

Check the network status.

KEOS29606-E (C/F)

An error occurred while a temporary file was being created. (details = aa....aa)

aa....aa: Details

Description

An error occurred while a temporary file was being created. The possible causes are as follows. If the file name is output in the details, check the following errors in that file, and if the file name is not output in the details, check the following errors in the directory storing the processing data of the virtual server manager (directory specified in the vmi.spool.dir key of vmi.properties):

There is no access permission.

The disk space has depleted.

The directory does not exist.

The directory could not be created.

The processing will be cancelled.

Action

Check the access permissions and disk space for the file name output in the details, or the directory storing the processing data of the virtual server manager, remove the cause of the error, and then re-execute the command.

KEOS29607-I (F)

The command will start now. (command = aa....aa, process ID = bb....bb, start time = cc....cc)

aa....aa: command line

bb....bb: Process ID

cc....cc: Command start time

Description

The command described in the message will start.

KEOS29608-I (F)

The command will terminate now. (process ID = aa....aa, start time = bb....bb, exit code = cc....cc)

aa....aa: Process ID

bb....bb: Command start time

cc....cc: Exit code

Description

The command described in the process ID and command start time will terminate.

KEOS29609-E (C/F)

The specified directory does not exist. (directory path = aa....aa)

aa....aa: Directory path

Description

The specified directory does not exist. The possible causes are as follows:

The specified directory name or directory path is incorrect.

The specified directory path is a file.

The user does not have the permission to access the specified directory path.

The processing will be cancelled.

Action

Check whether the specified directory path is a directory, or check the directory name and directory path. If there is no error in the directory path, check whether the user has the access permissions.

Specify the correct directory, and then re-execute the command.

KEOS29610-E (C/F)

The specified file does not exist. (file path = aa....aa)

aa....aa: File path

Description

The specified file does not exist.

The processing will be cancelled.

Action

The possible causes are as follows. Take action based on the respective causes.

The file path name or path is incorrect.

Check the name and path.

The file path is a directory.

Check whether the file path is a file.

The user does not have permission to access the file path.

If there is no error in the file path, check if the user has access permissions.

Specify a file with the correct file path and access permissions, and then re-execute the command.

KEOS29611-E (C/F)

An error occurred while reading the file. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An error occurred while reading the file. The possible causes might be the access permissions for the file and directory, or an error in the I/O environment.

The processing will be cancelled.

Action

Check the details.

If the user does not have the permission to read the file, grant the required permissions. If the file access permissions are correct, and the failure is not recovered even after re-executing the command, contact maintenance personnel.

KEOS29612-E (C/F)

A required file does not exist. (management unit name = aa....aa, file name = bb....bb)

aa....aa: Management unit name

bb....bb: File name

Description

The distinguished-name-of-LB-connection-information.properties or tierlb.properties (load balancer connection configuration property file) does not exist in the virtual server manager or definition directory.

The processing will be cancelled.

Action

Check whether the distinguished-name-of-LB-connection-information.properties or tierlb.properties (load balancer connection configuration property file) exists in the following directory:

If the virtual server manager is Windows

The Cosminexus-installation-directory\manager\vmi\config\lb directory of the virtual server manager.

If the virtual server manager is UNIX

The /opt/Cosminexus/manager/vmi/config/lb directory of the virtual server manager

Definition directory

Store distinguished-name-of-LB-connection-information.properties or tierlb.properties (load balancer connection configuration property file) at an appropriate location, and then re-execute the command.

KEOS29613-I (F)

The virtual server manager was started.

Description

The virtual server manager was started.

KEOS29614-E (F)

The virtual server manager failed to start.

Description

The virtual server manager failed to start. A possible cause is an error in the execution environment of the virtual server manager.

The processing will be cancelled.

Action

See the message output just before this message, remove the cause of the error, and then restart the virtual server manager.

KEOS29615-I (F)

The virtual server manager was terminated.

Description

The virtual server manager was terminated.

KEOS29616-E (F)

A required property is not specified. (aa....aa) (file name = bb....bb)

aa....aa: Property key

bb....bb: File name

Description

A required property is not specified.

The processing will be cancelled.

Action

Check the contents of the file, remove the cause of the error, and then restart the virtual server manager.

KEOS29618-W (F)

An invalid value is specified for the property. (aa....aa = bb....bb) default value (cc....cc) will be used. (file name = dd....dd)

aa....aa: Property key

bb....bb: Value specified for the property (invalid value)

cc....cc: Default value of property

dd....dd: File name

Description

An invalid value is specified for the property. The default value will be used.

The processing continues.

Action

Check the file contents.

Remove the cause of the warning as and when required, and then restart the virtual server manager.

KEOS29619-I (F)

The directory (aa....aa = bb....bb) has been created.

aa....aa: Directory type

bb....bb: Directory name

Description

The directory has been created.

KEOS29620-E (F)

An attempt to create the directory (aa....aa = bb....bb) failed.

aa....aa: Directory type

bb....bb: Directory name

Description

An attempt to create the directory failed. A possible cause is that the access permissions for the directory are invalid.

The processing continues.

Action

Check the directory access permissions.

Remove the cause of the error as and when required, and then restart the virtual server manager.

KEOS29621-E (F)

An attempt to read the file failed. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An attempt to read the file failed. A possible cause is that the access permissions for the file are invalid. The processing continues.

Action

Check the file access permissions.

Remove the cause of the error as and when required, and then restart the virtual server manager.

KEOS29622-E (C/F)

An attempt to store the internal status failed. (processing result = aa....aa, file name = bb....bb, details = cc....cc)

aa....aa: Processing results other than the stored internal status (return value of the command when the storage operation is successful)

bb....bb: File name for which storage failed

cc....cc: Details

Description

An attempt to store the internal status failed. The possible causes are as follows:

The file permissions are invalid.

The disk does not have free space.

An error occurred on the disk.

The processing continues.

Action

Check the file permissions and the disk status.

If the processing result is 0, remove the cause of the error, and then take the following action based on the executed command:

Command name

Action

vmiaccount

create

Delete the added account, and then add that account again.

delete

Add the deleted account, and then delete that account again.

password

Change the password again.

vmiunitadmin

changeowner

Change the owner to the old account, and then change that owner again.

create

Delete the created management unit, and then create that management unit again.

delete

Create the deleted management unit, and then delete that management unit again.

vmiunit

attach

Un-register the registered virtual server, and then register that virtual server again.

detach

Register the un-registered virtual server, and then un-register that virtual server again.

Other than above

Register a new virtual server, and then un-register that virtual server.

If the processing result is not 0, remove the cause of the error, and then take action according to the message output just before this message.

KEOS29623-I (F)

The processing of the virtual server manager command will start now. (client = aa....aa)

aa....aa: Connection source host

Description

The processing of the virtual server manager command will start now.

KEOS29624-I (F)

The processing of the virtual server manager command will end now.

Description

The processing of the virtual server manager command will end now.

KEOS29626-E (C/F)

An internal error occurred. (details = aa....aa)

aa....aa: Details

Description

An internal error occurred.

The processing will be cancelled.

Action

Contact maintenance personnel.

KEOS29627-I (C/F)

A request to process aa....aa was received.

aa....aa: Command name

Description

A request to process the command was received. Command name =aa....aa

KEOS29628-I (F)

The processing of the aa....aa command will start now.

aa....aa: Command name

Description

The processing of the command will start.

KEOS29629-I (F)

The processing of the aa....aa command terminated. (exit code = bb....bb)

aa....aa: Command name

bb....bb: Exit code

Description

The processing of the command terminated.

KEOS29630-E (C/F)

A communication error occurred in the virtual server manager. (details = aa....aa)

aa....aa: Details

Description

A communication error occurred in the virtual server manager. A possible cause is that there is an error in the communication between the virtual server manager and the client that executed the command.

The processing will be cancelled.

Action

Remove the cause of the error based on the details, and then re-execute the command. If the failure is not recovered even after re-executing the command, contact maintenance personnel.

KEOS29631-E (C/F)

The user ID or user password is invalid.

Description

The user ID or user password is incorrect.

The processing will be cancelled.

Action

Check the specified user ID and user password.

Specify the correct user ID and user password, and then re-execute the operation.

KEOS29632-E (C/F)

Connection cannot be established because the settings for using the virtual server manager functionality are not specified, or the virtual server manager has not yet started.

Description

Connection cannot be established because the settings for operating the Management Server as the virtual server manager are not specified, or the start processing of the virtual server manager is not complete.

The processing will be cancelled.

Action

Check whether true is specified in the com.cosminexus.mngsvr.vmi.enabled key of mserver.properties (Management Server configuration file). If false is specified, change the value to true, and then restart the virtual server manager. If true is already specified, wait for some time and then re-execute the command.

Check whether the start processing of the virtual server manager is complete.

KEOS29633-E (F)

The server communication agent returned an error response. (details = aa....aa)

aa....aa: Response code

Description

The server communication agent returned an error response. The possible causes are that the server communication agent does not allow access to the virtual server manager, or there is an error in communication with the server communication agent.

If the virtual server identifier is specified in the following commands, the processing will be cancelled.

Commands for starting the management unit or virtual server

Commands for stopping the management unit or virtual server

The processing continues in all other cases.

Action

Check the sinaviagent.permitted.hosts property of sinaviagent.properties in the server communication agent, and the response code in the details.

Set up the IP address of the virtual server manager in the sinaviagent.permitted.hosts property of sinaviagent.properties to allow access. If access is already allowed, take action according to the response code of the server communication agent.

KEOS29634-E (F)

An error occurred while the file was being downloaded. (details = aa....aa)

aa....aa: Exception

Description

An error occurred while the file was being downloaded. A possible cause is an error in communication with the server communication agent.

If the virtual server identifier is specified in the following commands, the processing will be cancelled.

Commands for starting the management unit or virtual server

Commands for stopping the management unit or virtual server

The processing continues in all other cases.

Action

Check the details, or the server communication agent log. If the following exceptions are thrown, perform a check for each exception.

Also, remove the cause of the error based on the details.

If there is an error in the vmi.properties (virtual server manager property file) settings, change the settings, and then restart the virtual server manager.

FileNotFoundException

Check whether the directory storing the processing data of the virtual server manager (directory specified in the vmi.spool.dir key of vmi.properties) exists.

IOException

Check the access permissions and disk space of the directory storing the processing data of the virtual server manager (directory specified in the vmi.spool.dir key of vmi.properties).

SocketIOException

Check the network environment, the port number of the server communication agent, and the settings for the following keys in vmi.properties (virtual server manager property file):

vmi.serverconnectionagent.connect.timeout

vmi.serverconnectionagent.socket.timeout

KEOS29635-E (F)

An error occurred in the processing of the server communication agent while a file was being downloaded. (details = aa....aa)

aa....aa: Exception

Description

An error occurred in the processing of the server communication agent while a file was being downloaded. A possible cause is an error in the communication with the server communication agent.

If the virtual server identifier is specified in the following commands, the processing will be cancelled.

Commands for starting the management unit or virtual server

Commands for stopping the management unit or virtual server

The processing continues in all other cases.

Action

Check the details, or the server communication agent log. If the following exceptions are thrown, perform a check for each exception.

Also, remove the cause of the error based on the details.

If there is an error in the vmi.properties (virtual server manager property file) settings, change the settings, and then restart the virtual server manager.

DuplicateFileNameException

Check whether the output file or directory, transmitted by the server communication agent, is duplicated.

FileNotFoundException

Check whether the output file or directory, transmitted by the server communication agent, exists.

IOException

Check the access permissions and disk space for the output file or directory, transmitted by the server communication agent.

SocketIOException

Check the network environment, the port number of the server communication agent, and the settings for the following keys in vmi.properties (virtual server manager property file):

vmi.serverconnectionagent.connect.timeout

vmi.serverconnectionagent.socket.timeout

KEOS29636-E (F)

The version of the server communication agent is inconsistent.

Description

The version of the server communication agent is inconsistent. A possible cause is an error in the communication with the server communication agent.

If the virtual server identifier is specified in the following commands, the processing will be cancelled.

Commands for starting the management unit or virtual server

Commands for stopping the management unit or virtual server

The processing continues in all other cases.

Action

Check whether the Cosminexus version supported by the virtual server manager is being used for Application Server running on the virtual server.

KEOS29637-E (F)

A timeout occurred during command execution. (details = aa....aa)

aa....aa: Process ID

Description

A timeout occurred during command execution. A possible cause is that the processes running on the server communication agent have not terminated or are taking time to terminate.

If the virtual server identifier is specified in the following commands, the processing will be cancelled.

Commands for starting the management unit or virtual server

Commands for stopping the management unit or virtual server

The processing continues in all other cases.

Action

Check the statuses of the processes output in the details. Also, check the statuses of the child processes started from this process.

To check the timeout value, check the settings for the following key in vmi.properties (virtual server manager property file):

vmi.serverconnectionagent.exec.timeout

As and when required , terminate the processes forcibly. If there is an error in the vmi.properties (virtual server manager property file) settings, change the settings, and then restart the virtual server manager.

KEOS29638-E (C/F)

The specified management unit does not exist. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The specified management unit does not exist. A possible cause is that the specified management unit name is incorrect.

The processing will be cancelled.

Action

Check the management unit name. If the management unit name is correct, contact the virtual server manager administrator to check whether the management unit exists.

Specify the correct management unit name, and then re-execute the command.

KEOS29639-E (C/F)

The specified management unit already exists. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The specified management unit already exists. A possible cause is that a management unit has already been created using the specified management unit name.

The processing will be cancelled.

Action

Check the specified management unit name. If the management unit name is correct, contact the virtual server manager administrator to check whether another user has created a management unit with the same name.

Specify a management unit name that is not duplicated with a created management unit, and then re-execute the command.

KEOS29640-E (F)

An error occurred while a file was being uploaded. (details = aa....aa)

aa....aa: Exception

Description

An error occurred while a file was being uploaded. A possible cause is an error in the communication with the server communication agent.

If the virtual server identifier is specified in the following commands, the processing will be cancelled.

Commands for starting the management unit or virtual server

Commands for stopping the management unit or virtual server

The processing continues in all other cases.

Action

Check the details, or the server communication agent log. If the following exceptions are thrown, perform a check for each exception.

Also, remove the cause of the error based on the details.

If there is an error in the vmi.properties (virtual server manager property file) settings, change the settings, and then restart the virtual server manager.

DuplicateFileNameException

Check whether the output file or directory, transmitted by the virtual server manager, is duplicated.

FileNotFoundException

Check whether the output file or directory, transmitted by the virtual server manager, exists.

IOException

Check the access permissions and disk space for the directory storing the processing data of the virtual server manager (vmi.spool.dir key of vmi.properties).

SocketIOException

Check the network environment, the port number of the server communication agent, and the settings for the following keys in vmi.properties (virtual server manager property file):

vmi.serverconnectionagent.connect.timeout

vmi.serverconnectionagent.socket.timeout

KEOS29641-E (F)

An error occurred in the processing of the server communication agent while a file was being uploaded. (details = aa....aa)

aa....aa: Exception

Description

An error occurred in the processing of the server communication agent while a file was being uploaded. A possible cause is an error in the communication with the server communication agent.

If the virtual server identifier is specified in the following commands, the processing will be cancelled.

Commands for starting the management unit or virtual server

Commands for stopping the management unit or virtual server

The processing continues in all other cases.

Action

Check the details, or the server communication agent log. If the following exceptions are thrown, perform a check for each exception.

Also, remove the cause of the error based on the details.

If there is an error in the vmi.properties (virtual server manager property file) settings, change the settings, and then restart the virtual server manager.

FileNotFoundException

Check whether the output, transmission destination directory for the server communication agent, exists.

IOException

Check the access permissions and disk space for the output, transmission destination directory for the server communication agent.

SocketIOException

Check the network environment, the port number of the server communication agent, and the settings for the following keys in vmi.properties (virtual server manager property file):

vmi.serverconnectionagent.connect.timeout

vmi.serverconnectionagent.socket.timeout

KEOS29642-E (F)

An error occurred in the processing of the server communication agent. (details = aa....aa)

aa....aa: Exception

Description

An error occurred in the processing of the server communication agent. A possible cause is an error in the communication with the server communication agent.

If the virtual server identifier is specified in the following commands, the processing will be cancelled.

Commands for starting the management unit or virtual server

Commands for stopping the management unit or virtual server

The processing continues in all other cases.

Action

Check the details, or the server communication agent log. If the following exceptions are thrown, perform a check for each exception.

Also, remove the cause of the error based on the details. Terminate the processes forcibly as and when required

If there is an error in the vmi.properties (virtual server manager property file) settings, change the settings, and then restart the virtual server manager.

CommandInterruptedException

Check the status of the server communication agent and the status of the running processes.

IOException

Check the access permissions of the file that is output.

SocketIOException

Check the network environment, the port number of the server communication agent, and the settings for the following keys in vmi.properties (virtual server manager property file):

vmi.serverconnectionagent.connect.timeout

vmi.serverconnectionagent.socket.timeout

KEOS29643-E (C/F)

The description cannot be specified in the Easy Setup definition file. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

The description of Easy Setup definition file (DefModel.xml) stored in the specified definition directory is incorrect.

The processing will be cancelled.

Action

Remove the cause of the error based on the details described in the following table, and then re-execute the vmiunit import command.

Table 13‒11: List of error details described in KEOS29643-E

Details

Description

Action

An XML namespace that cannot be used is specified in the xmlns attribute of <model-definition>. (value = aa....aa)

aa....aa: Value specified in the xmlns attribute of <model-definition>

An XML namespace that cannot be used is specified in <model-definition> in the Easy Setup definition file.

Change the <model-definition> definition in the Easy Setup definition file.

The XML namespace for the Easy Setup definition file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5.

The XML namespace is not specified in the xmlns attribute of <model-definition>.

The XML namespace is not specified in the xmlns attribute of <model-definition> in the Easy Setup definition file.

Change the <model-definition> definition in the Easy Setup definition file.

The XML namespace for the Easy Setup definition file specifiable in this version is http://www.cosminexus.com/mngsvr/schema/ModelDefinition-2.5.

<model-definition>-<web-system> is not defined.

<model-definition>-<web-system> is not defined in the Easy Setup definition file.

Add the Web system definition (<model-definition>-<web-system>) in the Easy Setup definition file.

Multiple <model-definition>-<web-system> tags are defined.

Multiple <model-definition>-<web-system> tags are defined in the Easy Setup definition file.

Define only one <model-definition>-<web-system> tag in the Easy Setup definition file.

Multiple <web-system>-<tier> tags are defined.

Multiple <web-system>-<tier> tags are defined in the Easy Setup definition file.

Define only one <web-system>-<tier> tag in the Easy Setup definition file.

A value that cannot be specified is specified in <tier>-<tier-type>. (value = aa....aa)

aa....aa: Value specified in <tier-type>

A value that cannot be used as the <tier>-<tier-type> value is specified in the Easy Setup definition file.

Specify a value that can be used in <tier>-<tier-type> in the Easy Setup definition file.

A value other than 1 is specified as the value of <tier>-<j2ee-server-count>. (value = aa....aa)

aa....aa: Value specified in <j2ee-server-count>

A value other than 1 is specified as the value of <tier>-<j2ee-server-count> in the Easy Setup definition file.

Delete the <tier>-<j2ee-server-count> tag in the Easy Setup definition file, or specify 1 as the value of <tier>-<j2ee-server-count>.

Multiple <web-system>-<unit> tags are defined.

Multiple <web-system>-<unit> tags are defined in the Easy Setup definition file.

Define only one <web-system>-<unit> tag in the Easy Setup definition file.

<logical-server-name> is not defined for items wherein the value of <unit>-<allocated-host>-<define-server>-<logical-server-type> is aa....aa.

aa....aa: Logical server type

<logical-server-name> is not defined for items wherein the value of <unit>-<allocated-host>-<define-server>-<logical-server-type> is aa....aa in the Easy Setup definition file.

Add the following <logical-server-name> tag to define the logical server name in the logical server definition where the logical server type is aa....aa in the Easy Setup definition file:

<unit>

<allocated-host>

<define-server>

<logical-server-type>aa....aa</logical-server-type>

<logical-server-name>logical server name</logical-server-name>

A value that cannot be specified is specified in <unit>-<allocated-host>-<define-server>-<logical-server-type>. (value = aa....aa)

aa....aa: Logical server type

A value that cannot be used as the <unit>-<allocated-host>-<define-server>-<logical-server-type> value is specified in the Easy Setup definition file.

Specify a value that can be used as the value of <unit>-<allocated-host>-<define-server>-<logical-server-type> in the Easy Setup definition file.

Multiple <model-definition>-<host> tags are defined.

Multiple <model-definition>-<host> tags are defined in the Easy Setup definition file.

Define only one <model-definition>-<host> tag in the Easy Setup definition file.

A value other than localhost is specified as the value of <unit>-<allocated-host>-<host-ref>. (value = aa....aa)

aa....aa: Value specified in <host-ref>

A value other than localhost is specified as the value of <unit>-<allocated-host>-<host-ref> in the Easy Setup definition file.

Specify localhost as the value of <unit>-<allocated-host>-<host-ref> in the Easy Setup definition file.

A value other than localhost is specified as the value of <model-definition>-<host>-<host-name>. (value = aa....aa)

aa....aa: Value specified in <host-name>

A value other than localhost is specified as the value of <model-definition>-<host>-<host-name> in the Easy Setup definition file.

Specify localhost as the value of <model-definition>-<host>-<host-name> in the Easy Setup definition file.

A value other than localhost is specified as the value of <model-definition>-<host>-<agent-host>. (value = aa....aa)

aa....aa: Value specified in <agent-host>

A value other than localhost is specified as the value of <model-definition>-<host>-<agent-host> in the Easy Setup definition file.

Specify localhost as the value of <model-definition>-<host>-<agent-host> in the Easy Setup definition file.

<web-system>-<load-balancer> is defined.

<web-system>-<load-balancer> is defined in the Easy Setup definition file.

Delete the definition of <web-system>-<load-balancer> from the Easy Setup definition file.

<tier>-<j2ee-server-count> cannot be specified in logical tier aa....aa.

aa....aa: Tier type

<tier>-<j2ee-server-count> is defined in the Easy Setup definition file.

Delete the definition of <tier>-<j2ee-server-count> from the Easy Setup definition file.

In the logical server classification aa....aa, <server-no> cannot be specified.

aa....aa: Logical server classification

In the Easy Setup definition file, <server-no> is defined with the logical server having a logical server classification other than "j2ee-server".

Delete the definition of <server-no> corresponding to the logical server having a logical server classification other than "j2ee-server", in the Easy Setup definition file.

If the specified value of <tier>-<j2ee-server-count> is 0, the logical server classification j2ee-server cannot be specified.

In the Easy Setup definition file, if <tier>-<j2ee-server-count> value is "0", the logical server "j2ee-server" is defined.

Delete definition of the logical server classification "j2ee-server" in the Easy Setup definition file.

In the <server-no> value (aa....aa), a value greater than the <tier>-<j2ee-server-count> value (bb....bb) is specified.

aa....aa: Value specified in <server-no>

bb....bb: Value specified in <j2ee-server-count>

In the Easy Setup definition file, a value greater than the <tier>-<j2ee-server-count> value is defined as the <server-no> value.

Specify a value smaller than the <tier>-<j2ee-server-count> value as the <server-no> value in the Easy Setup definition file.

The definition of <unit>-<allocated-host>-<define-server> corresponding to <tier>-<j2ee-server-count> value (aa....aa) is insuffecient.

aa....aa: Value specified in <j2ee-server-count>

The definition of <unit>-<allocated-host>-<define-server> corresponding to the <tier>-<j2ee-server-count> value is insuffecient in the Easy Setup definition file.

Define <unit>-<allocated-host>-<define-server> having the same count of logical server classification "j2ee-server" as the <tier>-<j2ee-server-count> value, in the Easy Setup definition file.

If <tier>-<j2ee-server-count> is not specified, <server-no> cannot be specified.

If <tier>-<j2ee-server-count> is not defined in the Easy Setup definition file, <server-no> cannot be specified.

Delete the definition of <server-no> from the Easy Setup defiition file.

<server-no> is not specified in the logical server definition having the logical server classification "j2ee-server". (Unit name = aa....aa)

aa....aa: Unit name

In the Easy Setup definition file, <server-no> is not defined corresponding to the logical server definition having logical server classification "j2ee-server".

Define <server-no> in the logical server definition having the logical server classification "j2ee-server", in the Easy Setup definition file.

KEOS29644-E (C/F)

There is a syntax error in the Easy Setup definition file. (file name = aa....aa, row number = bb....bb, column number = cc....cc, details = dd....dd)

aa....aa: File name

bb....bb: Row number

cc....cc: Column number

dd....dd: Details

Description

There is a syntax error in the specified Easy Setup definition file (DefModel.xml).

The processing will be cancelled.

Action

Check the contents of the Easy Setup definition file.

Remove the cause of the error based on the details, and then re-execute the command.

KEOS29645-E (C/F)

There is a syntax error in the virtual server group information file. (file name = aa....aa, row number = bb....bb, column number = cc....cc, details = dd....dd)

aa....aa: File name

bb....bb: Row number

cc....cc: Column number

dd....dd: Details

Description

There is a syntax error in the virtual server group information file.

The processing will be cancelled.

Action

Check the contents of the virtual server group information file.

Remove the cause of the error based on the details, and then re-execute the command.

KEOS29646-E (C/F)

An error occurred while the xml file was being parsed. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An error occurred while the xml file was being parsed. There is a critical syntax error in the specified Easy Setup definition file (DefModel.xml).

The processing will be cancelled.

Action

Check the contents of the Easy Setup definition file.

Remove the cause of the error based on the details, and then re-execute the operation.

KEOS29647-E (C/F)

The value specified in the argument is invalid. (option = aa....aa, value = bb....bb)

aa....aa: Option name

bb....bb: Value

Description

The value specified in the argument is invalid.

The processing will be cancelled.

Action

Check the character restrictions that can be specified in the argument where the error occurred. For details on the character restrictions that can be specified in the arguments, see 9. Commands Used with Virtual Systems in the manual uCosminexus Application Server Command Reference Guide.

Set up the values that can be specified, and then re-execute the command.

KEOS29648-E (C/F)

The specified user ID already exists in the virtual server manager administrator account. (user ID = aa....aa)

aa....aa: User ID

Description

The user ID of the specified system builder account is duplicated with the virtual server manager administrator account.

The processing will be cancelled.

Action

Check the user ID of the virtual server manager administrator account that is being managed.

Specify a different user ID than the virtual server manager administrator account, and then re-execute the command.

KEOS29649-E (C/F)

The specified user ID already exists. (user ID = aa....aa)

aa....aa: User ID

Description

The specified user ID is already being used in the system builder account.

The processing will be cancelled.

Action

Execute the vmiaccount list command to check the registered user IDs. Specify a user ID different from the registered user IDs, and then re-execute the command.

KEOS29650-I (C/F)

The system builder account was added successfully. (user ID = aa....aa)

aa....aa: User ID

Description

The system builder account was added successfully.

KEOS29651-E (C/F)

The operation cannot be executed because the specified user ID is the user ID of the virtual server manager administrator account. (user ID = aa....aa)

aa....aa: User ID

Description

The password cannot be changed or deleted because the specified user ID is for the virtual server manager administrator account.

The processing will be cancelled.

Action

Check the user ID of the virtual server manager administrator account that is being managed. Also, execute the vmiaccount list command to check the registered user IDs.

Specify the correct user ID for the system builder account, and then re-execute the command.

To change the password of the virtual server manager administrator account, use the mngsvrctl command.

KEOS29652-E (C/F)

The specified user ID cnanot be deleted because it owns the management unit. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The user ID of the specified system builder account cannot be deleted because it owns the management unit.

The processing will be cancelled.

Action

Execute the vmiunit info command to check the owner.

Change the settings so that the user ID of the specified system builder account is no longer the owner of the management unit, and then re-execute the command.

KEOS29653-I (C/F)

The system builder account was deleted successfully. (user ID = aa....aa)

aa....aa: User ID

Description

The system builder account was deleted successfully.

KEOS29654-E (C/F)

The command option is incorrect. (details = aa....aa)

aa....aa: Details

Description

The specified option is incorrect.

The processing will be cancelled.

Action

Check the specified command options.

Remove the cause of the error based on the details described in the following table, and then re-execute the command.

Table 13‒12: List of error details described in KEOS29654-E

Details

Description

Action

An incorrect option is specified. (option = aa....aa)

aa....aa: Option

The specified command option is incorrect.

Review, and if necessary revise, the command options.

A required option is not specified. (option = aa....aa)

aa....aa: Option

A required option is not specified.

Review, and if necessary revise, the command options.

KEOS29655-E (C/F)

The specified user ID does not exist. (user ID = aa....aa)

aa....aa: User ID

Description

The specified user ID does not exist in the system builder account. A possible cause is that the specified user ID is incorrect.

The processing will be cancelled.

Action

Execute the vmiaccount list command to check whether the user ID exists.

Specify an existing system builder user ID, and then re-execute the command.

KEOS29656-I (C/F)

The user password of the system builder account was changed successfully. (user ID = aa....aa)

aa....aa: User ID

Description

The user password of the system builder account was changed successfully.

KEOS29657-W (C/F)

The specified management unit is the owner of the specified user ID. (management unit name = aa....aa, user ID = bb....bb)

aa....aa: Management unit name

bb....bb: User ID

Description

The specified user ID is already the owner of the management unit.

The command will terminate without processing.

Action

Check the specified management unit name and the owner name. If there is no error, contact the virtual server manager administrator to check the management unit owner.

KEOS29658-I (C/F)

The owner of the management unit was changed successfully. (management unit name = aa....aa, owner = bb....bb)

aa....aa: Management unit name

bb....bb: Owner

Description

The owner of the management unit was changed successfully.

KEOS29659-E (C/F)

A processing was interrupted while it was at standby. (details = aa....aa)

aa....aa: Details

Description

A processing was interrupted while it was at standby.

The processing will be cancelled.

Action

Check the details.

Remove the cause of the error based on the details, and then re-execute the command.

KEOS29660-E (C/F)

The processing could not be started within the specified time.

Description

The processing could not be started within the specified time. A possible cause is that another command was not terminated within the standby time.

The processing will be cancelled.

Action

Check the following standby time values:

Value specified in the -wait option of the common arguments.

Value specified in the vmi.connect.wait key of .vmirc (client settings property file) or vmiclient.properties (client common configuration file).

Re-execute the command after the other commands terminate or after extending the standby time value.

KEOS29661-I (C/F)

The management unit was created successfully. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The management unit was created successfully.

KEOS29662-E (C/F)

The virtual server cannot be deleted because it is registered in the specified management unit. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The virtual server cannot be deleted because it is registered in the specified management unit.

The processing will be cancelled.

Action

Execute the vmiunit list command to check the existence of the virtual server in the management unit.

Execute the vmiunit detach command to unregister all the virtual servers registered in the management unit, and then re-execute the command.

KEOS29663-I (C/F)

The management unit was deleted successfully. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The management unit was deleted successfully.

KEOS29664-W (C/F)

The virtual server is not registered in the specified management unit. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The virtual server is not registered in the specified management unit.

The command will terminate without processing.

Action

Execute the vmiunit list command to check the existence of the virtual server in the management unit.

Register the virtual server, apply the definition to the management unit, and then re-execute the command.

KEOS29665-E (C/F)

The virtual server is not registered in the specified management unit. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The virtual server is not registered in the specified management unit.

The processing will be cancelled.

Action

Execute the vmiunit list command to check the existence of the virtual server in the management unit.

Specify the correct management unit name, and then re-execute the command.

KEOS29666-I (C/F)

The virtual server has started successfully. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

The virtual server started successfully.

KEOS29667-I (C/F)

The management unit has started successfully. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))

aa....aa: Management unit name

bb....bb: Number of virtual servers belonging to the management unit

cc....cc: Number of successfully started virtual servers

dd....dd: Number of skipped virtual servers

ee....ee: Number of virtual servers that could not be started

ff....ff: Number of successful load balancer operations

gg....gg: Number of failed load balancer operations

Description

The management unit started successfully.

KEOS29668-W (C/F)

An attempt to start some of the virtual servers in the management unit failed. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))

aa....aa: Management unit name

bb....bb: Number of virtual servers belonging to the management unit

cc....cc: Number of successfully started virtual servers

dd....dd: Number of skipped virtual servers

ee....ee: Number of virtual servers that could not be started

ff....ff: Number of successful load balancer operations

gg....gg: Number of failed load balancer operations

Description

An attempt to start some of the virtual servers in the management unit failed.

The management units contain the following virtual servers:

Successfully started virtual servers

Virtual servers that could not be started

Action

Make sure that the message output before this message contains an information message about the successfully started virtual servers and an error message about the virtual servers that could not be started.

Take action for the error message about the virtual servers that could not be started.

KEOS29669-E (C/F)

An attempt to start a management unit failed. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))

aa....aa: Management unit name

bb....bb: Number of virtual servers belonging to the management unit

cc....cc: Number of successfully started virtual servers

dd....dd: Number of skipped virtual servers

ee....ee: Number of virtual servers that could not be started

ff....ff: Number of successful load balancer operations

gg....gg: Number of failed load balancer operations

Description

An attempt to start a management unit failed. The management unit contains virtual servers that could not be started, but does not contain successfully started virtual servers.

The processing will be cancelled.

Action

Make sure that the message output before this message contains an error message about the virtual servers that could not be started.

Take action for the error message about the virtual servers that could not be started.

KEOS29670-I (C/F)

The operation to start a virtual server was not performed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

A virtual server was not started.

Table 13‒13: List of error details described in KEOS29670-I

Details

Description

Action

The virtual server is already running.

The virtual server is already running.

--

Legend:

--: Not applicable.

KEOS29673-I (F)

The virtual server will start now. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

The virtual server will start.

KEOS29674-W (F)

The virtual server will start now. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

The virtual server will start now.

The logical status and real status does not match.

The processing continues.

Action

Execute the vmiunit status command to check the logical status and real status of the virtual server.

Check the details described in the following table. Also, stop the virtual server as and when required.

Table 13‒14: List of error details described in KEOS29674-W

Details

Description

Action

The statuses do not match. (logical status = aa....aa, real status = bb....bb)

aa....aa: Logical status

bb....bb: Real status

The logical status and real status of the virtual server does not match.

Execute the vmiunit status command to check the logical status and real status of the virtual server.

To match the statuses, execute the vmiunit start or vmiunit stop commands for this virtual server.

KEOS29675-E (C/F)

An attempt to write to the file failed. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

An attempt to write to the file failed. The possible causes are as follows:

The user does not have the permission to access the write destination file or directory.

The disk space at the write destination has depleted.

The write destination directory does not exist.

The directory could not be created.

The processing will be cancelled.

Action

Check whether the path of the output destination directory is incorrect, or check the access permissions and disk space for the output destination directory. Remove the cause of the error based on the details, and then re-execute the command.

KEOS29676-E (C/F)

An attempt to start a virtual server failed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

An attempt to start a virtual server failed. The possible causes are that an error occurred in the virtual server start processing, or that the conditions for executing the start processing are not satisfied.

The processing will be cancelled if the virtual server identifier is specified. The processing continues if the virtual server identifier is not specified.

Action

Take action based on the details.

To restore the virtual server with a failed logical status, execute the vmiunit detach command to remove the virtual server that could not be started from the management unit, then execute the vmiunit attach command to re-register the virtual server into the management unit, and then execute the vmiunit update command to apply the settings. Re-execute the command thereafter.

Table 13‒15: List of error details described in KEOS29676-E

Details

Description

Action

The logical status is not set up.

The logical status is not set up.

Execute the vmiunit status command to check the logical status.

Execute the vmiunit update command to set up the virtual server, and then re-execute the command.

The virtual server definition differs from the management unit definition.

The virtual server definition differs from the management unit definition.

Execute the vmiunit status command to check the scope of change in the definition.

Execute the vmiunit update command to update the definition, and then re-execute the command.

An attempt to start the Administration Agent failed.

An attempt to start the Administration Agent failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in the Administration Agent settings in the definition file.

Check the following virtual server log, and then remove the cause of the error:

Administration Agent log

Server communication agent log

An attempt to start the Management Server failed.

An attempt to start the Management Server failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in the Management Server settings in the definition file.

Check the following virtual server log, and then remove the cause of the error:

Management Server log

Server communication agent log

An attempt to start a Web system failed.

An attempt to start a Web system failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in the Easy Setup definition file settings in the definition file.

Check the following virtual server log, and then remove the cause of the error:

Management Server log

Server communication agent log

The logical status is failed.

The operation cannot be executed because the logical status of the virtual server is failed.

Execute the vmiunit status command to check the logical status of the virtual server.

To restore this virtual server, execute the vmiunit detach command to un-register the virtual server from the management unit, and then execute the vmiunit attach command to re-register the virtual server into the management unit.

The logical status does not enable processing. (logical status = aa....aa)

aa....aa: Logical status

The processing cannot be executed because the logical status of the virtual server is Running, Stopping, or Updating.

Execute the vmiunit status command to check the logical status of the virtual server.

To restore this virtual server, execute the vmiunit detach command to un-register the virtual server from the management unit, and then execute the vmiunit attach command to re-register the virtual server into the management unit.

Cannot connect to the virtual server.

A connection cannot be established to the virtual server. A possible cause is an error in the communication with the server communication agent.

Check the status of the virtual server power supply.

If the power is ON: Check the server communication agent log on the virtual server, and then remove the cause of the error.

If the virtual server power supply is OFF: Switch the power to ON.

An error occurred while a temporary file was being created. (details = aa....aa)

aa....aa: Details

An error occurred while a temporary file was being created. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

The user does not have the permission to access the parent directory of the file or directory to be created.

Check the details, or the server communication agent log of the virtual server, and then remove the cause of the error.

An attempt to start the application failed. (J2EE server name = aa....aa, port number = bb....bb, application name = cc....cc)

aa....aa: J2EE server name

bb....bb: Port number of the naming service

cc....cc: Application name

An attempt to start the application failed. The possible causes are as follows:

There is an error in the communication with the server communication agent.

There is an error in the application.

Check the details, or the following virtual server log, and then remove the cause of the error:

Server management command log

Server communication agent log

An attempt to check the Administration Agent operations failed.

An attempt to check the Administration Agent operations failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in an Administration Agent process.

Check the return code, or the following virtual server log, and then remove the cause of the error:

Administration Agent log

Server communication agent log

An attempt to check the Management Server operations failed.

An attempt to check the Management Server operations failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in a Management Server process.

Check the return code, or the following virtual server log, and then remove the cause of the error:

Management Server log

Server communication agent log

An attempt to check the Web system operations failed. (Web system name = aa....aa, service unit name = bb....bb)

aa....aa: Web system name

bb....bb: Service unit name

An attempt to check the Web system operations failed. The possible causes are as follows:

There is an error in the communication with the server communication agent.

The disk space of the virtual server has depleted.

An attempt to execute the cmx_list_status command failed.

Check the return code, or the following virtual server log, and then remove the cause of the error:

Management Server log

Server communication agent log

The application status could not be acquired. (J2EE server name = aa....aa, port number = bb....bb)

aa....aa: J2EE server name

bb....bb: Port number of the naming service

The application status could not be acquired. The possible causes are as follows:

There is an error in the communication with the server communication agent.

The disk space of the virtual server has depleted.

An attempt to execute the cjlistapp command failed.

Check the return code, or the following virtual server log, and then remove the cause of the error.

Server management command log

Server communication agent log

KEOS29677-I (C/F)

The virtual server was stopped successfully. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

The management unit was stopped successfully.

KEOS29678-I (C/F)

The management unit was stopped successfully. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))

aa....aa: Management unit name

bb....bb: Number of virtual servers belonging to the management unit

cc....cc: Number of successfully stopped virtual servers

dd....dd: Number of skipped virtual servers

ee....ee: Number of virtual servers that could not be stopped

ff....ff: Number of successful load balancer operations

gg....gg: Number of failed load balancer operations

Description

The management unit was stopped successfully.

KEOS29679-W (C/F)

An attempt to stop some of the virtual servers in the management unit failed. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))

aa....aa: Management unit name

bb....bb: Number of virtual servers belonging to the management unit

cc....cc: Number of successfully stopped virtual servers

dd....dd: Number of skipped virtual servers

ee....ee: Number of virtual servers that could not be stopped

ff....ff: Number of successful load balancer operations

gg....gg: Number of failed load balancer operations

Description

An attempt to stop some of the virtual servers in the management unit failed. The management unit contains successfully stopped virtual servers and virtual servers that could not be stopped.

Action

Make sure that the message output before this message contains an information message about the successfully stopped virtual servers and an error message about the virtual servers that could not be stopped.

Take action for the error message about the virtual servers that could not be stopped.

KEOS29680-E (C/F)

An attempt to stop the management unit failed. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))

aa....aa: Management unit name

bb....bb: Number of virtual servers belonging to the management unit

cc....cc: Number of successfully stopped virtual servers

dd....dd: Number of skipped virtual servers

ee....ee: Number of virtual servers that could not be stopped

ff....ff: Number of successful load balancer operations

gg....gg: Number of failed load balancer operations

Description

An attempt to stop the management unit failed. The management unit contains virtual servers that could not be stopped, but does not contain successfully stopped virtual servers.

The processing will be cancelled.

Action

Make sure that the message output before this message contains an error message about the virtual servers that could not be stopped.

Take action for the error message about the virtual servers that could not be stopped.

KEOS29681-I (C/F)

The operation to stop a virtual server was not performed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

The virtual server was not stopped.

Table 13‒16: KEOS29681-I List of error details described in

Details

Description

Action

The virtual server has already been stopped.

The virtual server has already been stopped.

--

Legend:

--: Not applicable.

KEOS29684-I (F)

The virtual server will stop now. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

The virtual server will stop.

KEOS29685-W (F)

The virtual server will stop now. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

The virtual server will stop now. The logical status and real status do not match.

The processing continues.

Action

Execute the vmiunit status command to check the logical status and real status of the virtual server. Then check the details. Stop the virtual server as and when required.

Table 13‒17: List of error details described in KEOS29685-W

Details

Description

Action

The real status is invalid. (real status = aa....aa)

aa....aa: Real status

The real status of the virtual server is invalid.

Execute the vmiunit status command to check the real status of the virtual server.

Re-execute the command based on the results of command execution.

The statuses do not match. (logical status = aa....aa, real status = bb....bb)

aa....aa: Logical status

bb....bb: Real status

The logical status and real status of the virtual server does not match.

Execute the vmiunit status command to check the logical status and real status of the virtual server.

To match the statuses, execute the vmiunit start or vmiunit stop commands for this virtual server.

KEOS29686-I (C/F)

The load balancer operations were successful. (management unit name = aa....aa, tier identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Tier identifier

Description

The load balancer operations were successful.

KEOS29687-E (C/F)

An attempt to stop the virtual server failed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

An attempt to stop the virtual server failed. The possible causes are that an error occurred in the virtual server stop processing, or that the conditions for executing the stop processing are not satisfied.

The processing will be cancelled if the virtual server identifier is specified. The processing continues if the virtual server identifier is not specified.

Action

Take action based on the details.

To restore the virtual server with a failed logical status, execute the vmiunit detach command to remove the virtual server that could not be stopped from the management unit, then execute the vmiunit attach command to re-register the virtual server into the management unit, and then execute the vmiunit update command to apply the settings.

Table 13‒18: List of error details described in KEOS29687-E

Details

Description

Action

The logical status is not set up.

The logical status is not set up.

Execute the vmiunit status command to check the logical status.

Execute the vmiunit update command to set up the virtual server, and then re-execute the command.

An attempt to stop the Administration Agent failed.

An attempt to stop the Administration Agent failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in the Administration Agent process.

Check the following virtual server log, and then remove the cause of the error:

Administration Agent log

Server communication agent log

An attempt to stop the Management Server failed.

An attempt to stop the Management Server failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in the Management Server process.

Check the following virtual server log, and then remove the cause of the error:

Management Server log

Server communication agent log

An attempt to stop the Web system failed.

An attempt to stop the Web system failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in the Web system settings.

Check the following virtual server log, and then remove the cause of the error:

Management Server log

Server communication agent log

The logical status does not enable processing. (logical status = aa....aa)

aa....aa: Logical status

The processing cannot be executed because the logical status of the virtual server is Running, Stopping, or Updating.

Execute the vmiunit status command to check the logical status of the virtual server.

To restore this virtual server, execute the vmiunit detach command to un-register the virtual server from the management unit, and then execute the vmiunit attach command to re-register the virtual server into the management unit.

Cannot connect to the virtual server.

A connection cannot be established to the virtual server. A possible cause is an error in the communication with the server communication agent.

Check the status of the virtual server power supply.

If the power is ON: Check the server communication agent log on the virtual server, and then remove the cause of the error.

If the virtual server power supply is OFF: Switch the power to ON.

An error occurred while a temporary file was being created. (details = aa....aa)

aa....aa: Details

An error occurred while a temporary file was being created. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

The user does not have the permission to access the parent directory of the file or directory to be created.

Check the details, or the server communication agent log of the virtual server, and then remove the cause of the error.

An attempt to check the Administration Agent operations failed.

An attempt to check the Administration Agent operations failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in an Administration Agent process.

Check the return code, or the following virtual server log, and then remove the cause of the error.

Administration Agent log

Server communication agent log

An attempt to check the Management Server operations failed.

An attempt to check the Management Server operations failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in a Management Server process.

Check the return code, or the following virtual server log, and then remove the cause of the error.

Management Server log

Server communication agent log

An attempt to check the Web system operations failed. (Web system name = aa....aa, service unit name = bb....bb)

aa....aa: Web system name

bb....bb: service unit name

An attempt to check the Web system operations failed. The possible causes are as follows:

There is an error in the communication with the server communication agent.

The disk space of the virtual server has depleted.

An attempt to execute the cmx_list_status command failed.

Check the return code, or the following virtual server log, and then remove the cause of the error.

Management Server log

Server communication agent log

KEOS29688-E (C/F)

A required property is not specified. (aa....aa) (management unit name = bb....bb, tier identifier = cc....cc, file name =dd....dd)

aa....aa: Property key

bb....bb: Management unit name

cc....cc: Tier identifier

dd....dd: File name

Description

A required property is not specified.

The processing will be cancelled.

Action

Check the contents of the file.

Remove the cause of the error, and then re-execute the command.

KEOS29689-E (C/F)

The specified virtual server identifier is already being used as the virtual server identifier or business IP address of another virtual server belonging to the specified management unit. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Specified management unit name

bb....bb: Specified virtual server identifier

Description

The specified virtual server identifier is incorrect, or is already registered in the management unit as a virtual server identifier or business IP address.

The processing will be cancelled.

Action

Use the vmiunit list command to check the existence of the specified virtual server identifier or business IP address.

Change the virtual server identifier, and then re-execute the command.

KEOS29690-I (C/F)

The virtual server group was registered successfully. (management unit name = aa....aa, number of new virtual server groups = bb....bb, number of new virtual servers = cc....cc)

aa....aa: Management unit name

bb....bb: Number of added virtual server groups

cc....cc: Number of added virtual servers

Description

The virtual server group was registered successfully.

KEOS29691-E (C/F)

The specified virtual server does not exist. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

The specified virtual server does not exist. The specified virtual server identifier is incorrect, or is not registered in the management unit.

The processing will be cancelled.

Action

Execute the vmiunit list command to check whether the specified virtual server identifier exists. Specify the correct virtual server identifier, and then re-execute the command.

KEOS29692-I (C/F)

The virtual server group was un-registered successfully. (management unit name = aa....aa, virtual server group name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server group name

Description

The virtual server group was un-registered successfully.

KEOS29693-E (C/F)

The definition directory is not imported into the management unit. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The definition file and business application have not been imported into the management unit.

The processing will be cancelled.

Action

Execute the vmiunit status command to check the definition status.

Execute the vmiunit import command to import the definition directory, and then re-execute the command.

KEOS29694-E (C/F)

An error occurred while a temporary file was being created. (management unit name = aa....aa, details = bb....bb)

aa....aa: Management unit name

bb....bb: Details

Description

An error occurred while a temporary file was being created. The possible causes are the file and directory access permissions, or that the disk space at the creation destination has depleted.

The processing will be cancelled.

Action

Check the details, and the access permissions or disk space at the creation destination. Remove the cause of the error, and then re-execute the command.

KEOS29695-E (C/F)

An attempt to acquire the application name failed. (management unit name = aa....aa, application file = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Application file name

cc....cc: Details

Description

An attempt to acquire the application name failed. A possible cause is an error in the EAR file for the J2EE application stored in the definition directory.

The processing will be cancelled.

Action

Check the EAR file. Also, remove the cause of the error based on the details, and then re-execute the command.

KEOS29696-E (C/F)

The user ID is not the owner of the specified management unit. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The user ID is not the owner of the specified management unit. The specified management unit name or user ID is incorrect.

The processing will be cancelled.

Action

Check the management unit name and user ID.

Specify the correct management unit name and user ID, and then re-execute the command.

KEOS29697-I (C/F)

The definition directory was registered successfully. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The definition directory was registered successfully.

KEOS29698-E (C/F)

An invalid value is specified for the property. (management unit name = aa....aa, tier identifier = bb....bb, cc....cc = dd....dd) (file name = ee....ee)

aa....aa: Management unit name

bb....bb: Tier identifier

cc....cc: Property key

dd....dd: Value specified for the property (invalid value)

ee....ee: File name

Description

An invalid value is specified for the file property.

The processing will be cancelled.

Action

Check the contents of the file.

Change the value to the correct value, and then re-execute the command.

KEOS29699-E (C/F)

An invalid value is specified for the file. (management unit name = aa....aa, tier identifier = bb....bb, cc....cc = dd....dd) (file name = ee....ee)

aa....aa: Management unit name

bb....bb: Tier identifier

cc....cc: Parameter name

dd....dd: Value

ee....ee: File name

Description

An invalid value is specified for the file.

The processing will be cancelled.

Action

Check the contents of the file.

Change the value to the correct value, and then re-execute the command.

KEOS29700-E (C/F)

An error occurred while reading the file. (management unit name = aa....aa, tier identifier = bb....bb, file name = cc....cc, details = dd....dd)

aa....aa: Management unit name

bb....bb: Tier identifier

cc....cc: File name

dd....dd: Details

Description

An error occurred while reading the file. A possible cause is an error in the access permissions for the definition directory or the file stored in the definition directory.

The processing will be cancelled.

Action

Check the access permissions for the definition directory and definition file. Remove the cause of the error based on the details, and then re-execute the command.

KEOS29701-W (C/F)

The error mark has already been set up. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

The virtual server identifier is incorrect, or the error mark has already been set up.

The command will terminate without processing.

Action

Check the virtual server identifier. If there is no error in the virtual server identifier, execute the vmiunit status command to check the error mark setup time and error mark comments.

Specify the correct virtual server identifier, and then re-execute the command.

To change the error mark comments, execute the vmiunit unmark command to remove the error mark, and then re-execute the vmiunit mark command.

KEOS29702-I (C/F)

The error mark has been set up. (management unit name = aa....aa, virtual server identifier = bb....bb, setup time = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Setup time

Description

The error mark has been set up.

KEOS29703-W (C/F)

The error mark has not been set up. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

The virtual server identifier is incorrect, or the error mark has already been removed.

The command will terminate without processing.

Action

Check the virtual server identifier. If there is no error in the virtual server identifier, execute the vmiunit status command to check the error mark setup time and error mark comments.

Specify the correct virtual server identifier, and then re-execute the command.

KEOS29704-I (C/F)

The error mark has been removed. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

The error mark is removed.

KEOS29705-W (F)

An invalid value is specified for the property. (management unit name = aa....aa, tier identifier = bb....bb, cc....cc = dd....dd) The default value (ee....ee) will be used. (file name = ff....ff)

aa....aa: Management unit name

bb....bb: Tier identifier

cc....cc: Property key

dd....dd: Value specified for the property (invalid value)

ee....ee: Default value of property

ff....ff: File name

Description

An invalid value is specified for the property of the file stored in the definition directory. The default value will be used.

The processing continues.

Action

Check the contents of the file.

Remove the cause of the warning as and when required, and then re-execute the command.

KEOS29706-I (C/F)

The virtual server was applied successfully. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

The virtual server was applied successfully.

KEOS29707-I (C/F)

The definitions were successfully applied to the management unit. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))

aa....aa: Management unit name

bb....bb: Number of virtual servers belonging to the management unit

cc....cc: Number of successfully applied virtual servers

dd....dd: Number of skipped virtual servers

ee....ee: Number of virtual servers that could not be applied

ff....ff: Number of successful load balancer operations

gg....gg: Number of failed load balancer operations

Description

The definitions were successfully applied to the management unit.

KEOS29708-W (C/F)

An attempt to apply some of the definitions to the management unit failed. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))

aa....aa: Management unit name

bb....bb: Number of virtual servers belonging to the management unit

cc....cc: Number of successfully applied virtual servers

dd....dd: Number of skipped virtual servers

ee....ee: Number of virtual servers that could not be applied

ff....ff: Number of successful load balancer operations

gg....gg: Number of failed load balancer operations

Description

An attempt to apply some of the definitions to the management unit failed. There are virtual servers that could not be applied.

Action

Check the message output before this message.

Remove the cause of the error, and then re-execute the command.

KEOS29709-E (C/F)

An attempt to apply the definitions to the management unit failed. (management unit name = aa....aa, number of virtual servers belonging to the management unit = bb....bb (successful: cc....cc, skipped: dd....dd, failed: ee....ee) (load balancer operations successful: ff....ff, failed: gg....gg))

aa....aa: Management unit name

bb....bb: Number of virtual servers belonging to the management unit

cc....cc: Number of successfully applied virtual servers

dd....dd: Number of skipped virtual servers

ee....ee: Number of virtual servers that could not be applied

ff....ff: Number of successful load balancer operations

gg....gg: Number of failed load balancer operations

Description

An attempt to apply the definitions to the management unit failed. There are no successfully applied virtual servers.

The processing will be cancelled.

Action

Check the message output before this message.

Remove the cause of the error, and then re-execute the command.

KEOS29710-I (C/F)

The definitions were not applied to the virtual server. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

The definitions were not applied to the virtual server.

Table 13‒19: List of error details described in KEOS29710-I

Details

Description

Action

The latest definitions are already applied.

The latest definitions are already applied.

--

Legend:

--: Not applicable.

KEOS29712-E (C/F)

An attempt to apply a virtual server failed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

An attempt to apply a virtual server failed. The possible causes are that there is an error in the virtual server apply processing, or that the conditions for executing the apply processing are not satisfied.

The processing for the other virtual servers continues.

Action

Take action based on the details.

To re-apply a virtual server with a failed logical status, execute the vmiunit detach command to remove the virtual server from the management unit, then execute the vmiunit attach command to re-register the virtual server in the management unit, and then re-execute the command.

Table 13‒20: List of error details described in KEOS29712-E

Details

Description

Action

An attempt to start the Administration Agent failed.

An attempt to start the Administration Agent failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in the Administration Agent settings in the definition file.

Check the following virtual server log, and then remove the cause of the error:

Administration Agent log

Server communication agent log

An attempt to start the Management Server failed.

An attempt to start the Management Server failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in the Management Server settings in the definition file.

Check the following virtual server log, and then remove the cause of the error:

Management Server log

Server communication agent log

An attempt to start a Web system failed.

An attempt to start a Web system failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in the Easy Setup definition file settings in the definition file.

Check the following virtual server log, and then remove the cause of the error:

Management Server log

Server communication agent log

An attempt to stop the Administration Agent failed.

An attempt to stop the Administration Agent failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in the Administration Agent process.

Check the following virtual server log, and then remove the cause of the error:

Administration Agent log

Server communication agent log

An attempt to stop the Management Server failed.

An attempt to stop the Management Server failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in the Management Server process..

Check the following virtual server log, and then remove the cause of the error:

Management Server log

Server communication agent log

An attempt to stop the Web system failed.

An attempt to stop the Web system failed. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

There is an error in the Web system settings.

Check the following virtual server log, and then remove the cause of the error:

Management Server log

Server communication agent log

The logical status is failed.

The operation cannot be executed because the logical status of the virtual server is failed.

Execute the vmiunit status command to check the logical status of the virtual server.

To restore this virtual server, execute the vmiunit detach command to un-register the virtual server from the management unit, and then execute the vmiunit attach command to re-register the virtual server into the management unit.

The logical status does not enable processing. (logical status = aa....aa)

aa....aa: Logical status

The processing cannot be executed because the logical status of the virtual server is Running, Stopping, or Updating.

Execute the vmiunit status command to check the logical status of the virtual server.

To restore this virtual server, execute the vmiunit detach command to un-register the virtual server from the management unit, and then execute the vmiunit attach command to re-register the virtual server into the management unit.

Cannot connect to the virtual server.

A connection cannot be established to the virtual server. A possible cause is an error in the communication with the server communication agent.

Check the status of the virtual server power supply.

If the power is ON: Check the server communication agent log on the virtual server, and then remove the cause of the error.

If the virtual server power supply is OFF: Switch the power to ON.

The statuses do not match. (logical status = aa....aa, real status = bb....bb)

aa....aa: Logical status

bb....bb: Real status

The logical status and real status of the virtual server does not match.

Execute the vmiunit status command to check the logical status and real status of the virtual server.

To match the statuses, execute the vmiunit start or vmiunit stop commands for this virtual server.

An error occurred while a temporary file was being created. (details = aa....aa)

aa....aa: Details

An error occurred while a temporary file was being created. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

The user does not have the permission to access the parent directory of the file or directory to be created.

Check the details, or the server communication agent log of the virtual server, and then remove the cause of the error.

The logical status is Running.

The logical status of the virtual server is Running.

Execute the vmiunit status command to check the logical status of the virtual server.

To apply this virtual server, execute the vmiunit stop command to stop the virtual server.

An attempt to upload the definition directory failed. (details = aa....aa)

aa....aa: Details

An attempt to upload the definition directory failed. The possible causes are as follows:

There is an error in the communication with the server communication agent.

The user does not have the permission to access the parent directory of the upload destination.

The disk space of the virtual server has depleted.

Check the details, or the server communication agent log of the virtual server, and then remove the cause of the error.

An attempt to set up the Web system failed.

An attempt to set up the Web system failed. The possible causes are as follows:

There is an error in the communication with the server communication agent.

There is an error in the contents of the definition directory set up in the management unit.

Also, if JP1 auto-setup is specified using the hook script, the deletion of the file fails because the log file trap functionality is running.

Check the details, or the following virtual server log, and then remove the cause of the error:

Log output by the rasetup -vm command

Management Server log

Server communication agent log

Also, if JP1 auto-setup is specified using the hook script, check whether the log file trap functionality is running in th virtual server.

An attempt to import the application failed. (J2EE server name = aa....aa, port number = bb....bb, file name = cc....cc)

aa....aa: J2EE server name

bb....bb: Port number of the naming service

cc....cc: File name

An attempt to import the application failed. The possible causes are as follows:

There is an error in the communication with the server communication agent.

There is an error in the application.

Check the details, or the following virtual server log, and then remove the cause of the error.

Server management command log

Server communication agent log

An attempt to start the application failed. (J2EE server name = aa....aa, port number = bb....bb, application name = cc....cc)

aa....aa: J2EE server name

bb....bb: Port number of the naming service

cc....cc: Application name

An attempt to start the application failed. The possible causes are as follows:

There is an error in the communication with the server communication agent.

There is an error in the application.

Check the details, or the following virtual server log, and then remove the cause of the error.

Server management command log

Server communication agent log

An attempt to delete the application failed. (J2EE server name = aa....aa, port number = bb....bb, J2EE application name = cc....cc)

aa....aa: J2EE server name

bb....bb: Port number of the naming service

cc....cc: J2EE application name

An attempt to delete the application failed. The possible causes are as follows:

There is an error in the communication with the server communication agent.

There is an error in the J2EE server environment or the application.

Check the details, or the following virtual server log, and then remove the cause of the error.

Server management command log

Server communication agent log

An attempt to stop the application failed. (J2EE server name = aa....aa, port number = bb....bb, J2EE application name = cc....cc)

aa....aa: J2EE server name

bb....bb: Port number of the naming service

cc....cc: J2EE application name

An attempt to stop the application failed. The possible causes are as follows:

There is an error in the communication with the server communication agent.

There is an error in the J2EE server environment or the application.

Check the details, or the following virtual server log, and then remove the cause of the error.

Server management command log

Server communication agent log

An attempt to execute the hook script failed. (return code = aa....aa)

aa....aa: Return code of the hook script

An attempt to execute the hook script failed. The possible causes are as follows:

There is an error in the communication with the server communication agent.

There is an error in the contents of the hook script.

Check the return code, or server communication agent log of the virtual server, and then remove the cause of the error.

The application status could not be acquired. (J2EE server name = aa....aa, port number = bb....bb)

aa....aa: J2EE server name

bb....bb: Port number of the naming service

The application status could not be acquired. The possible causes are as follows:

There is an error in the communication with the server communication agent.

The disk space of the virtual server has depleted.

An attempt to execute the cjlistapp command failed.

Check the return code, or the following virtual server log, and then remove the cause of the error.

Server management command log

Server communication agent log

An attempt to create the Easy Setup definition file failed. (details = aa....aa)

aa....aa: Details

An attempt to create the Easy Setup definition file failed.

There is an error in the directory storing the processing data of the virtual server manager. The possible causes are as follows:

The user does not have access permissions.

The disk space has depleted.

A disk error occurred.

Check the message details. Remove the cause of the error, and then re-execute the command.

KEOS29713-E (C/F)

A required file does not exist in the definition directory. (file name = aa....aa)

aa....aa: File name

Description

A required file does not exist in the definition directory.

The processing will be cancelled.

Action

Make sure that all the required files have been stored.

Store the missing file in the definition directory, and then re-execute the command.

KEOS29714-E (C/F)

The definition directory contains files that cannot be specified at the same time. (file = aa....aa, bb....bb)

aa....aa: File name 1

bb....bb: File name 2

Description

An EAR file with the same name as the specified EAR file exists in the definition directory.

The processing will be cancelled.

Action

Make sure that the definition directory does not contain an EAR file with the same name. Note that the name is not case sensitive. "A" and "a" are treated as the same character.

If an EAR file with the same name exists, review the file name. Specify an EAR file with the changed file name in the definition directory, and then re-execute the command.

KEOS29715-E (C/F)

The specified path is not a blank directory. ( path = aa....aa)

aa....aa: path

Description

The specified path is not a blank directory. The possible causes are as follows:

The specified path is incorrect.

The specified path is a file.

The directory in the specified path is not blank.

The user does not have the permission to access the specified path.

The processing will be cancelled.

Action

Check whether the specified path is a blank directory, or check the path. If there is no error in the path, check whether the user has the access permissions.

Create a blank directory with access permissions, specify the correct path, and then re-execute the command.

KEOS29716-E (C/F)

An attempt to fetch the definition directory failed. (management unit name = aa....aa, details = bb....bb)

aa....aa: Management unit name

bb....bb: Details

Description

An attempt to fetch the definition directory failed. The possible causes are as follows. If the file name is output in the details, check the following errors in that file, and if the file name is not output in the details, check the following errors in the directory storing the processing data of the virtual server manager (directory specified in the vmi.spool.dir key of vmi.properties):

There is no access permission.

The disk space has depleted.

The directory does not exist.

The directory could not be created.

The processing will be cancelled.

Action

Check the access permissions and disk space for the file name output in the details, or the directory storing the processing data of the virtual server manager, remove the cause of the error, and then re-execute the command.

KEOS29717-I (C/F)

The definition directory was fetched successfully. (management unit name = aa....aa, output destination directory path = bb....bb)

aa....aa: Management unit name

bb....bb: Output destination directory path

Description

The definition directory was fetched successfully.

KEOS29718-I (F)

The virtual server operation will be executed. (management unit name = aa....aa, tier identifier = bb....bb, virtual server identifier = cc....cc, operation type = dd....dd, operation target = ee....ee)

aa....aa: Management unit name

bb....bb: Tier identifier

cc....cc: Virtual server identifier

dd....dd: Operation type (Start, Stop, Run, Setup, Delete, Import)

ee....ee: Operation target (Administration Agent, Management Server, Web system, J2EE application, hook script)

Description

The virtual server operation will be executed.

KEOS29719-I (F)

The virtual server operation was successful. (management unit name = aa....aa, tier identifier = bb....bb, virtual server identifier = cc....cc, operation type = dd....dd, operation target = ee....ee)

aa....aa: Management unit name

bb....bb: Tier identifier

cc....cc: Virtual server identifier

dd....dd: Operation type (Start, Stop, Run, Setup, Delete, Import)

ee....ee: Operation target (Administration Agent, Management Server, Web system, J2EE application, hook script)

Description

The virtual server operation was successful.

KEOS29720-W (C/F)

The file will be ignored because it is not a valid component as a definition directory. (file name = aa....aa)

aa....aa: Ignored file name

Description

The file will be ignored because it is not a valid component as a definition directory. The possible causes are as follows:

The file deployed in the definition directory is incorrect.

The configuration of the definition directory is incorrect.

Files not required for setting up Application Server have been deployed.

The processing continues.

Action

Check the file name output in the message.

If the file name is incorrect, change the name to the correct file name, and if the file storage location is incorrect, move the file to the correct location, and then re-execute the command.

KEOS29721-E (C/F)

The load balancer operations failed. (management unit name = aa....aa, tier identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Tier identifier

cc....cc: Details

Description

The load balancer operations failed. A possible cause is an error in the load balancer operations.

The processing will be cancelled.

Action

Check the details. Take action based on the details, and then re-execute the command.

Table 13‒21: List of error details described in KEOS29721-E

Details

Description

Action

An attempt to set up the load balancer control script failed. (details =aa....aa)

aa....aa: Details

An attempt to set up the load balancer control script failed.

A possible cause is that the configuration of the load balancer is incorrect.

Check the message details.

Remove the cause of the error, and then re-execute the command.

An attempt to execute the load balancer control script failed. (details =aa....aa)

aa....aa: Details

An attempt to execute the load balancer control script failed.

The possible causes are that the configuration of the load balancer is incorrect, or the load balancer is not operating normally.

Check the operation status of the load balancer. Also, check the message details.

Remove the cause of the error, and then re-execute the command.

An attempt to read the load balancer connection configuration property file failed. (details =aa....aa)

aa....aa: Details

An attempt to read the load balancer connection configuration property file failed.

A possible cause is that the configuration of the load balancer is incorrect.

Check the message details.

Remove the cause of the error, and then re-execute the command.

An attempt to log in to the load balancer failed. (details =aa....aa)

aa....aa: Details

An attempt to log in to the load balancer failed.

A possible cause is that the load balancer account information is incorrect.

Check the lb.user key and lb.password key set in the load balancer connection configuration property file and the message details.

Remove the cause of the error, and then re-execute the command.

An attempt to communicate with the load balancer failed. (details =aa....aa)

aa....aa: Details

An attempt to communicate with the load balancer failed.

The possible causes are that the load balancer is not operating normally, or there is a network error.

Check the network status. Also, check the message details.

Remove the cause of the error, and then re-execute the command.

The load balancer type is incorrect.

The load balancer type is incorrect.

A possible cause is that the specified load balancer type is different from the connected load balancer type.

Check the value of the lb.type key specified in the load balancer connection configuration property file.

Remove the cause of the error, and then re-execute the command.

KEOS29722-W (C/F)

The operation for starting the virtual server was not performed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

The virtual server was not started. The real status of the virtual server is Running, but the logical status is Stopped.

The command will terminate without processing if the virtual server identifier is specified. The processing continues if the virtual server identifier is not specified.

Action

Execute the vmiunit status command to check the logical status and real status of the virtual server. Take action based on the details, and then re-execute the command.

Table 13‒22: List of error details described in KEOS29722-W

details

Description

Action

The statuses do not match. (logical status = aa....aa, real status = bb....bb)

aa....aa: Logical status

bb....bb: Real status

The logical status and real status of the virtual server does not match.

Execute the vmiunit status command to check the logical status and real status of the virtual server.

To match the statuses, execute the vmiunit start or vmiunit stop commands for this virtual server.

KEOS29723-E (C/F)

The specified business IP address is already being used as the virtual server identifier or business IP address of another virtual server belonging to the specified management unit. (management unit name = aa....aa, business IP address = bb....bb)

aa....aa: Specified management unit name

bb....bb: Specified business IP address

Description

The specified business IP address is incorrect, or is already registered in the management unit as the virtual server identifier or business IP address.

The processing will be cancelled.

Action

Execute the vmiunit list command to check the existence of the specified virtual server identifier or business IP address.

Change the business IP address, and then re-execute the command.

KEOS29724-E (C/F)

The specified virtual server identifier is already being used in another management unit. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Specified management unit name

bb....bb: Specified virtual server identifier

Description

The specified virtual server identifier is incorrect, or is already registered in another management unit as the virtual server identifier or business IP address.

The processing will be cancelled.

Action

Check the virtual server identifier.

If there is no error in the virtual server identifier, then contact the virtual server manager administrator to check whether the specified virtual server identifier exists.

Change the virtual server identifier, and then re-execute the command.

KEOS29725-E (C/F)

The specified business IP address is already being used in another management unit. (management unit name = aa....aa, business IP address = bb....bb)

aa....aa: Specified management unit name

bb....bb: Specified business IP address

Description

The specified business IP address is incorrect, or is already registered in another management unit as the virtual server identifier or business IP address.

The processing will be cancelled.

Action

Check the business IP address.

If there is no error in the business IP address, then contact the virtual server manager administrator to check whether the specified business IP address exists.

Change the business IP address, and then re-execute the command.

KEOS29726-I (C/F)

The virtual server was locked successfully. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

The virtual server was locked successfully.

KEOS29727-E (C/F)

An attempt to lock the virtual server failed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

An attempt to lock the virtual server failed. The possible causes are that the configuration of the load balancer is incorrect, or the logical status is Not Setup.

The processing will be cancelled.

Action

Execute the vmiunit status command to check the logical status of the virtual server.

Remove the cause of the error based on the details, and then re-execute the command.

Table 13‒23: List of error details described in KEOS29727-E

Details

Description

Action

The logical status is not set up.

The logical status is not set up.

A possible cause is that the logical status of the virtual server is Not Setup.

Execute the vmiunit status command to check the logical status.

Execute the vmiunit update command to set up the virtual server, and then re-execute the command.

An attempt to set up the load balancer control script failed. (details =aa....aa)

aa....aa: Details

An attempt to set up the load balancer control script failed.

A possible cause is that the configuration of the load balancer is incorrect.

Check the message details.

Remove the cause of the error, and then re-execute the command.

An attempt to execute the load balancer control script failed. (details =aa....aa)

aa....aa: Details

An attempt to execute the load balancer control script failed.

The possible causes are that the configuration of the load balancer is incorrect, or the load balancer is not operating normally.

Check the operation status of the load balancer. Also, check the message details.

Remove the cause of the error, and then re-execute the command.

An attempt to read the load balancer connection configuration property file failed. (details =aa....aa)

aa....aa: Details

An attempt to read the load balancer connection configuration property file failed.

A possible cause is that the configuration of the load balancer is incorrect.

Check the message details.

Remove the cause of the error, and then re-execute the command.

An attempt to log in to the load balancer failed. (details =aa....aa)

aa....aa: Details

An attempt to log in to the load balancer failed.

A possible cause is that the load balancer account information is incorrect.

Check the lb.user key and lb.password key set in the load balancer connection configuration property file and the message details.

Remove the cause of the error, and then re-execute the command.

An attempt to communicate with the load balancer failed. (details =aa....aa)

aa....aa: Details

An attempt to communicate with the load balancer failed.

The possible causes are that the load balancer is not operating normally, or there is a network error.

Check the network status. Also, check the message details.

Remove the cause of the error, and then re-execute the command.

The load balancer type is incorrect.

The load balancer type is incorrect.

A possible cause is that the specified load balancer type is different from the connected load balancer type.

Check the value of the lb.type key specified in the load balancer connection configuration property file.

Remove the cause of the error, and then re-execute the command.

KEOS29728-I (C/F)

The virtual server was unlocked successfully. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

The virtual server was unlocked successfully.

KEOS29729-E (C/F)

An attempt to unlock the virtual server failed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

An attempt to unlock the virtual server failed. The possible causes are that the configuration of the load balancer is incorrect, or the logical status is Not Setup.

The processing will be cancelled.

Action

Execute the vmiunit status command to check the logical status of the virtual server.

Remove the cause of the error based on the details, and then re-execute the command. For the details, see Table 13-23 List of error details described in KEOS29727-E.

KEOS29730-I (C/F)

The management unit was locked successfully. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The management unit was locked successfully.

KEOS29731-E (C/F)

An attempt to lock the management unit failed. (management unit name = aa....aa, details = bb....bb)

aa....aa: Management unit name

bb....bb: Details

Description

An attempt to lock the management unit failed. The possible causes are that the configuration of the load balancer is incorrect, or the logical status is Not Setup.

The processing will be cancelled.

Action

Execute the vmiunit status command to check the logical status of the virtual server.

Remove the cause of the error based on the details, and then re-execute the command. For the details, see Table 13-23 List of error details described in KEOS29727-E.

KEOS29732-I (C/F)

The management unit was unlocked successfully. (management unit name = aa....aa)

aa....aa: Management unit name

Description

The management unit was unlocked successfully.

KEOS29733-E (C/F)

An attempt to unlock the management unit failed. (management unit name = aa....aa, details = bb....bb)

aa....aa: Management unit name

bb....bb: Details

Description

An attempt to unlock the management unit failed. The possible causes are that the configuration of the load balancer is incorrect, or the logical status is Not Setup.

The processing will be cancelled.

Action

Execute the vmiunit status command to check the logical status of the virtual server.

Remove the cause of the error based on the details, and then re-execute the command. For the details, see Table 13-23 List of error details described in KEOS29727-E.

KEOS29734-E (C/F)

The load balancer integration functionality is not enabled. (management unit name = aa....aa)

aa....aa: Management unit name

Description

Load balancer integration is not enabled. A possible cause is that the -lb option is specified in the command, but the connection information of the load balancer to be used is not specified in the tier-wise property file.

The processing will be cancelled.

Action

Check the value of the lb.use key in the tier-wise property file.

Specify the connection information of the load balancer to be used in the tier-wise property file, apply the definition to the management unit, and then re-execute the command.

KEOS29735-I (C/F)

The load balancer operations were successful. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

The load balancer operations were successful.

KEOS29736-E (C/F)

The load balancer operations failed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

The load balancer operations failed. A possible cause is that an error occurred during the load balancer operations.

The processing will be cancelled.

Action

Check the message details.

Remove the cause of the error based on the details, and then re-execute the command.

For the details, see Table 13-21 List of error details described in KEOS29721-E.

KEOS29737-W (C/F)

An error mark has been set for a running virtual server. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

A virtual server with an error mark will be operated.

The processing continues.

Action

Execute the vmiunit status command to check the error mark setup time and error mark comments.

Execute the vmiunit unmark command to remove the error mark as and when required, and then re-execute the command.

KEOS29738-E (C/F)

An error occurred during authentication. (details = aa....aa)

aa....aa: Details

Description

An error occurred during authentication.

The processing will be cancelled.

Action

Check the details output in the message.

See the details, remove the cause of the error, and then re-execute the command.

Table 13‒24: List of error details described in KEOS29738-E

Details

Description

Action

A memory shortage occurred.

A memory shortage occurred. The processing will be cancelled.

Check whether the memory required for execution is available.

Increase the free memory space, and then re-execute the operation.

The authentication processing cannot be started. (details = aa....aa)

aa....aa: Details

The authentication processing cannot be started.

The processing will be cancelled.

Contact maintenance personnel.

Cannot connect to JP1/Base.

A connection could not be established with JP1/Base. The possible causes are as follows:

JP1/Base is not running.

The host name of the authentication server in the JP1/Base settings is incorrect.

The processing will be cancelled.

Check whether JP1/Base is running. Also, check the host name of the authentication server specified in JP1/Base.

If JP1/Base is not running, start JP1/Base. Also, set up an appropriate host name for the authentication server specified in JP1/Base.

An error occurred in JP1/Base.

An error occurred in JP1/Base.

The processing will be cancelled.

See the JP1/Base log.

Remove the cause of the error based on the log check results.

KEOS29739-E (C/F)

The processing of the aa....aa command cannot be started because the settings for using the JP1 user authentication integration functionality are specified.

aa....aa: Command name

Description

The processing of the command cannot be started because the settings for using the JP1 user authentication integration functionality are specified.

The processing will be cancelled.

Action

When using the JP1 user authentication integration functionality, manage the accounts by operating the authentication server directly.

If you do not want to use the JP1 user authentication integration functionality, disable the JP1 user authentication integration functionality.

KEOS29740-W (C/F)

The virtual server manager administrator account will not be set up because the settings for using the JP1 user authentication integration functionality are specified.

Description

The virtual server manager administrator account will not be set up because the settings for using the JP1 user authentication integration functionality are specified.

The processing continues without setting up the virtual server manager administrator account.

Action

When using the JP1 user authentication integration functionality, manage the accounts by operating the authentication server directly.

If you do not want to use the JP1 user authentication integration functionality, disable the JP1 user authentication integration functionality.

KEOS29741-I (C/F)

The user script was executed successfully. (management unit name = aa....aa, result = successful:bb....bb warning:cc....cc failed: dd....dd)

aa....aa: Management unit name

bb....bb: Number of successful results

cc....cc: Number of results terminated with a warning

dd....dd: Number of results terminated with an error

Description

The user script was executed successfully.

KEOS29742-W (C/F)

The user script has been executed. (management unit name = aa....aa, result = successful: bb....bb warning: cc....cc failed: dd....dd)

aa....aa: Management unit name

bb....bb: Number of successful results

cc....cc: Number of results terminated with a warning

dd....dd: Number of results terminated with an error

Description

An attempt to delete the distributed user script failed.

KEOS29743-E (C/F)

An attempt to execute the user script failed. (management unit name = aa....aa, result = successful:bb....bb warning:cc....cc failed:dd....dd)

aa....aa: Management unit name

bb....bb: Number of successful results

cc....cc: Number of results terminated with a warning

dd....dd: Number of results terminated with an error

Description

An attempt to distribute or execute the user script failed.

The processing will be cancelled.

Action

See the virtual server manager log.

See the virtual server manager log for the virtual servers in which user script execution failed, check the details, remove the cause of the error, and then re-execute the command.

KEOS29744-E (C/F)

An error occurred while the user script was being executed. (management unit name = aa....aa, details = bb....bb)

aa....aa: Management unit name

bb....bb: Details

Description

An error occurred while the user script was being executed.

The processing will be cancelled.

Action

Remove the cause of the error based on the details described in the following table, and then re-execute the command.

Table 13‒25: List of error details described in KEOS29744-E

Details

Description

Action

The user script does not exist in the user script deployment directory.

The user script does not exist in the user script deployment directory.

Check the file configuration of the user script deployment directory. Assign the user script in the user script deployment directory.

The virtual server executing the user script does not exist.

The virtual server does not exist in the specified management unit.

Check whether the virtual server exists in the management unit. Register the virtual server for executing the user script in the management unit.

An attempt to expand the user script failed.

The user does not have the file operation permissions for Cosminexus-installation-directory/manager/vmi/spool.

Check the directory permissions.

An error occurred while a temporary file was being created. (details = aa....aa)

aa....aa: Details

An error occurred while a temporary file was being created.

The user does not have the permission to access the parent directory of the file or directory to be created.

Check the details. Remove the cause of the error.

Cannot connect to the virtual server. (virtual server name = aa....aa)

aa....aa: Virtual server name

The connection to the virtual server cannot be established.

There is an error in the communication with the server communication agent.

Check the status of the virtual server power supply.

If the power is ON, check the server communication agent log on the virtual server. Remove the cause of the error based on the log information.

If the virtual server power supply is OFF, switch the power to ON.

KKEOS29745-I (C/F)

The user script was executed successfully on the virtual server. (management unit name = aa....aa, virtual server name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server name

Description

The user script was executed successfully.

KEOS29746-W (C/F)

The user script has been executed on the virtual server. (management unit name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Details

Description

The user script has been executed.

Action

Remove the cause of the error based on the details described in the following table, and then re-execute the command.

Table 13‒26: List of error details described in KEOS29746-W

details

Description

Action

An attempt to delete the temporary directory on the virtual server failed.

The temporary directory Cosminexus-installation-directory/manager/sinagent/work/vmi on the virtual server cannot be deleted.

Check the directory permissions, and then delete the temporary directory.

An attempt to delete the user script on the virtual server failed.

The user script file Cosminexus-installation-directory/manager/sinagent/work/userscript_dir on the virtual server cannot be deleted.

Check the directory permissions, and then delete the user script.

KEOS29747-E (C/F)

The execution of the user script on the virtual server failed. (management unit name = aa....aa, virtual server name = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server name

cc....cc: Details

Description

The execution of the user script failed.

The processing will be cancelled.

Action

Remove the cause of the error based on the details described in the following table, and then re-execute the command.

Table 13‒27: List of error details described in KEOS29747-E

Details

Description

Action

An attempt to upload failed. (details = aa....aa)

aa....aa: Details

An attempt to upload the user script failed.

The possible causes are as follows:

There is an error in the communication with the server communication agent.

The user does not have the permission to access the parent directory at the upload destination.

The disk space of the virtual server has depleted.

Check the details or the server communication agent log of the virtual server.

The user script terminated abnormally. (return code = aa....aa)

aa....aa: Return code of the user script

The user script terminated abnormally.

There is an error in the user script contents.

Check the return code.

An error occurred while a temporary file was being created. (details = aa....aa)

aa....aa: Details

An error occurred while a temporary file was being created. The possible causes are as follows:

An error occurred in the communication with the server communication agent.

The user does not have the permission to access the parent directory of the file or directory to be created.

Check the details, or the server communication agent log of the virtual server, and then remove the cause of the error.

KEOS29748-E (C/F)

The virtual server group information file contains an unspecifiable description. (file name = aa....aa, details = bb....bb)

aa....aa: File name

bb....bb: Details

Description

The description in the specified virtual server group information file is incorrect.

The processing will be cancelled.

Action

Remove the cause of the error based on the details described in the following table, and then re-execute the command.

Table 13‒28: List of error details described in KEOS29748-E

Details

Description

Action

Multiple <virtualserver> tags with the same tier identifier are specified in <virtualserver-info>-<group>. (virtual server group name = aa....aa, tier identifier = bb....bb)

aa....aa: Virtual server group name

bb....bb: Tier identifier

Multiple <virtualserver> tags with the same tier identifier are specified in <virtualserver-info>-<group>.

Check the value of <virtualserver-info>-<group>-<virtualserver> in the virtual server group information file, and then specify the correct tier identifier.

A required <virtualserver> tag is not specified. (virtual server group name = aa....aa, tier identifier = bb....bb)

aa....aa: Virtual server group name

bb....bb: Tier identifier

The <virtualserver> tag is not specified.

Check <virtualserver-info>-<group>-<virtualserver> in the virtual server group information file, and then add the settings for <virtualserver>.

The attribute value specified in <virtualserver-info>-<group>-<virtualserver> is invalid. (attribute name = aa....aa, value = bb....bb)

aa....aa: Attribute name

bb....bb: Value

The attribute value specified in <virtualserver-info>-<group>-<virtualserver> of the virtual server group information file is invalid.

Check the attribute value of <virtualserver-info>-<group>-<virtualserver> in the virtual server group information file, and then specify a specifiable value.

The attribute value specified in <virtualserver-info>-<group> is invalid. (attribute name = aa....aa, value = bb....bb)

aa....aa: Attribute name

bb....bb: Value

The attribute value specified in <virtualserver-info>-<group> of the virtual server group information file is invalid.

Check the attribute value of <virtualserver-info>-<group> in the virtual server group information file, and then specify a specifiable value.

Multiple <virtualserver-info>-<group> tags have been specified for the same name attribute. (value of the name attribute = aa....aa)

aa....aa: Value of the name attribute

Multiple <virtualserver-info>-<group> tags have been specified for the same name attribute.

Check the name attribute value in <virtualserver-info>-<group> in the virtual server group information file, and then specify an appropriate value.

The same virtual server group name has been specified using a different case. (virtual server group name 1 = aa....aa, virtual server group name 2 = bb....bb)

aa....aa: Virtual server group name 1

bb....bb: Virtual server group name 2

The same virtual server group name has been specified using a different case in the name attribute of <virtualserver-info>-<group>.

Check the name attribute value in <virtualserver-info>-<group> in the virtual server group information file, and then specify an appropriate value.

The same virtual server group name has already been registered using a different case. (specified virtual server group name = aa....aa, registered virtual server group name = bb....bb)

aa....aa: Specified virtual server group name

bb....bb: Registered virtual server group name

A virtual server group with a virtual server group name has already been registered using a different case than the virtual server group name specified in the name attribute of <virtualserver-info>-<group>.

Check the name attribute value in <virtualserver-info>-<group> in the virtual server group information file, and then specify an appropriate value.

KEOS29749-E (C/F)

The specified virtual server group does not exist. (management unit name = aa....aa, virtual server group name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server group name

Description

The specified virtual server group does not exist. The possible causes are that the specified virtual server group name is incorrect or is not registered in the management unit.

The processing will be cancelled.

Action

Execute the vmiunit list command to check whether the virtual server group name exists.

Specify the correct virtual server group name, and then re-execute the command.

KEOS29750-E (C/F)

An attempt to lock the virtual server group failed. (management unit name = aa....aa, virtual server group name = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server group name

cc....cc: Details

Description

An attempt to lock the virtual server group failed. The possible causes are that the configuration of the load balancer is incorrect, or the logical status is Not Setup.

The processing will be cancelled.

Action

Execute the vmiunit status command to check the logical status of the virtual server. Also, check the message details.

Remove the cause of the error based on the details, and then re-execute the command.

KEOS29751-I (C/F)

The virtual server group was locked successfully. (management unit name = aa....aa, virtual server group name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server group name

Description

The virtual server group was locked successfully.

KEOS29752-E (C/F)

The specified definition directory contains an invalid tier-wise definition directory. (management unit name = aa....aa, tier identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Tier identifier

Description

The name of the tier-wise definition directory differs from the tier identifier defined in the management unit.

The processing will be cancelled.

Action

Execute the vmiunit compare command to compare the definition directories.

Specify the correct definition directory, and then re-execute the command.

KEOS29753-E (C/F)

The specified definition directory does not contain a required tier-wise definition directory. (management unit name = aa....aa, tier identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Tier identifier

Description

A tier-wise definition directory with the same name as the tier identifier defined in the management unit, does not exist.

The processing will be cancelled.

Action

Execute the vmiunit compare command to compare the definition directories.

Specify the correct definition directory, and then re-execute the command.

KEOS29754-E (C/F)

The name of the tier-wise definition directory is inappropriate as the tier identifier. (directory path = aa....aa)

aa....aa: Directory path

Description

The name of the tier-wise definition directory is inappropriate as the tier identifier.

The processing will be cancelled.

Action

Check the name of the tier-wise definition directory displayed in the message.

The possible causes are that the name of the tier-wise definition directory below the definition directory specified in the -dir argument contains characters that cannot be used as a tier identifier, or the length of the string exceeds 31 bytes.

Change the name of the tier-wise definition directory to an appropriate name, and then re-execute the command.

KEOS29755-W (C/F)

The error mark has already been set up. (management unit name = aa....aa, virtual server group name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server group name

Description

The virtual server group name is incorrect, or the error mark has already been set up.

The processing will be cancelled.

Action

Check the virtual server group name. If there is no error in the virtual server group name, execute the vmiunit status command to check the error mark setup time and the error mark comments.

Specify the correct virtual server group name, and then re-execute the command.

To change the error mark comments, execute the vmiunit unmark command to remove the error mark, and then re-execute the vmiunit mark command.

KEOS29756-I (C/F)

The error mark has been set up. (management unit name = aa....aa, virtual server group name = bb....bb, setup time = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server group name

cc....cc: Setup time

Description

The error mark has been set up.

KEOS29757-W (C/F)

The error mark has not been set up. (management unit name = aa....aa, virtual server group name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server group name

Description

The virtual server identifier is incorrect, or the error mark has already been removed.

The processing will be cancelled.

Action

Check the virtual server group name. If there is no error in the virtual server group name, execute the vmiunit status command to check the error mark setup time and the error mark comments.

Specify the correct virtual server group name, and then re-execute the command.

KEOS29758-I (C/F)

The error mark has been removed. (management unit name = aa....aa, virtual server group name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server group name

Description

The error mark has been removed.

KEOS29759-E (C/F)

The load balancer integration functionality is not enabled. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server identifier

Description

Load balancer integration is not enabled.

The -lb option is specified in the command, but the connection information of the load balancer to be used is not specified in the tier-wise property file.

The processing will be cancelled.

Action

Check the value of the lb.use key in the tier-wise property file.

Specify the connection information of the load balancer to be used in the tier-wise property file, apply the definition to the management unit, and then re-execute the command.

KEOS29760-I (C/F)

The virtual server group was started successfully. (management unit name = aa....aa, virtual server group name = bb....bb, number of virtual servers belonging to the virtual server group = cc....cc (successful: dd....dd, skipped: ee....ee, failed: ff....ff) (load balancer operations successful: gg....gg, failed: hh....hh))

aa....aa: Management unit name

bb....bb: Virtual server group name

cc....cc: Number of virtual servers belonging to the virtual server group

dd....dd: Number of successfully started virtual servers

ee....ee: Number of skipped virtual servers

ff....ff: Number of virtual servers that could not be started

gg....gg: Number of successful load balancer operations

hh....hh: Number of failed load balancer operations

Description

The virtual server group was started successfully.

KEOS29761-W (C/F)

An attempt to start some of the virtual servers in the virtual server group failed. (management unit name = aa....aa, virtual server group name = bb....bb, number of virtual servers belonging to the virtual server group = cc....cc (successful: dd....dd, skipped: ee....ee, failed: ff....ff) (load balancer operations successful: gg....gg, failed: hh....hh))

aa....aa: Management unit name

bb....bb: Virtual server group name

cc....cc: Number of virtual servers belonging to the virtual server group

dd....dd: Number of successfully started virtual servers

ee....ee: Number of skipped virtual servers

ff....ff: Number of virtual servers that could not be started

gg....gg: Number of successful load balancer operations

hh....hh: Number of failed load balancer operations

Description

An attempt to start some of the virtual servers in the virtual server group failed.

A possible cause is that the virtual server group contains successfully started virtual servers and virtual servers that could not be started.

Action

Make sure that the message output before this message contains an information message about the successfully started virtual servers and an error message about the virtual servers that could not be started.

Take action for the error message about the virtual servers that could not be started.

KEOS29762-E (C/F)

An attempt to start the virtual server group failed. (management unit name = aa....aa, virtual server group name = bb....bb, number of virtual servers belonging to the management unit = cc....cc (successful: dd....dd, skipped: ee....ee, failed: ff....ff) (load balancer operations successful: gg....gg, failed: hh....hh))

aa....aa: Management unit name

bb....bb: Virtual server group name

cc....cc: Number of virtual servers belonging to the virtual server group

dd....dd: Number of successfully started virtual servers

ee....ee: Number of skipped virtual servers

ff....ff: Number of virtual servers that could not be started

gg....gg: Number of successful load balancer operations

hh....hh: Number of failed load balancer operations

Description

An attempt to start the virtual server group failed.

A possible cause is that the virtual server group contains virtual servers that could not be started, does not contain successfully started virtual servers.

The processing will be cancelled.

Action

Make sure that the message output before this message contains an error message about the virtual servers that could not be started.

Take action for the error message about the virtual servers that could not be started.

KEOS29763-I (C/F)

The virtual server group was stopped successfully. (management unit name = aa....aa, virtual server group name = bb....bb, number of virtual servers belonging to the virtual server group = cc....cc (successful: dd....dd, skipped: ee....ee, failed: ff....ff) (load balancer operations successful: gg....gg, failed: hh....hh))

aa....aa: Management unit name

bb....bb: Virtual server group name

cc....cc: Number of virtual servers belonging to the virtual server group

dd....dd: Number of successfully stopped virtual servers

ee....ee: Number of skipped virtual servers

ff....ff: Number of virtual servers that could not be stopped

gg....gg: Number of successful load balancer operations

hh....hh: Number of failed load balancer operations

Description

The virtual server group was stopped successfully.

KEOS29764-W (C/F)

An attempt to stop some of the virtual servers in the virtual server group failed. (management unit name = aa....aa, virtual server group name = bb....bb, number of virtual servers belonging to the virtual server group = cc....cc (successful: dd....dd, skipped: ee....ee, failed: ff....ff) (load balancer operations successful: gg....gg, failed: hh....hh))

aa....aa: Management unit name

bb....bb: Virtual server group name

cc....cc: Number of virtual servers belonging to the virtual server group

dd....dd: Number of successfully stopped virtual servers

ee....ee: Number of skipped virtual servers

ff....ff: Number of virtual servers that could not be stopped

gg....gg: Number of successful load balancer operations

hh....hh: Number of failed load balancer operations

Description

An attempt to stop some of the virtual servers in the virtual server group failed.

A possible cause is that the virtual server group contains successfully stopped virtual servers and virtual servers that could not be stopped.

Action

Make sure that the message output before this message contains an information message about the successfully stopped virtual servers and an error message about the virtual servers that could not be stopped.

Take action for the error message about the virtual servers that could not be stopped.

KEOS29765-E (C/F)

An attempt to stop the virtual server group failed. (management unit name = aa....aa, virtual server group name = bb....bb, number of virtual servers belonging to the virtual server group = cc....cc (successful: dd....dd, skipped: ee....ee, failed: ff....ff) (load balancer operations successful: gg....gg, failed: hh....hh))

aa....aa: Management unit name

bb....bb: Virtual server group name

cc....cc: Number of virtual servers belonging to the virtual server group

dd....dd: Number of successfully stopped virtual servers

ee....ee: Number of skipped virtual servers

ff....ff: Number of virtual servers that could not be stopped

gg....gg: Number of successful load balancer operations

hh....hh: Number of failed load balancer operations

Description

An attempt to stop the virtual server group failed.

A possible cause is that the virtual server group contains virtual servers that could not be stopped, but does not contain successfully stopped virtual servers.

The processing will be cancelled.

Action

Make sure that the message output before this message contains an error message about the virtual servers that could not be stopped.

Take action for the error message about the virtual servers that could not be stopped.

KEOS29766-E (C/F)

An attempt to unlock the virtual server group failed. (management unit name = aa....aa, virtual server group name = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server group name

cc....cc: Details

Description

An attempt to unlock the virtual server group failed.

The possible causes are as follows:

The configuration of the load balancer is incorrect.

The logical status is not set up.

The processing will be cancelled.

Action

Execute the vmiunit status command to check the logical status of the virtual server. Also, check the message details.

Remove the cause of the error based on the details, and then re-execute the command.

KEOS29767-I (C/F)

The virtual server group was unlocked successfully. (management unit name = aa....aa, virtual server group name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server group name

Description

The virtual server group was unlocked successfully.

KEOS29768-W (C/F)

The information for the virtual server group specified in the virtual server group information file differs from the registered virtual server group information. (file name = aa....aa, virtual server group name = bb....bb, tier identifier = cc....cc, attribute name = dd....dd, registered value = ee....ee, specified value = ff....ff)

aa....aa: File name

bb....bb: Virtual server group name

cc....cc: Tier identifier

dd....dd: Attribute name

ee....ee: Registered value

ff....ff: Specified value

Description

The information for the virtual server group specified in the virtual server group information file differs from the registered virtual server group information.

This virtual server group information is ignored and the processing continues.

Action

Compare the information for the virtual server group specified in the virtual server group information file and the information displayed with the vmiunit list command.

Take one of the following actions, and then re-execute the command.

If the information specified in the virtual server group information file is incorrect

Revise the information in the virtual server group information file.

If the information displayed with the vmiunit list command is incorrect

Use the vmiunit detach command to delete the incorrect virtual server group information.

KEOS29769-E (C/F)

The newly registered information is not specified in the virtual server group information file. (file name = aa....aa)

aa....aa: File name

Description

The newly registered information is not specified in the virtual server group information file.

A possible cause is that the specified virtual server group information file is incorrect.

The processing will be cancelled.

Action

Check the path and the contents of the specified virtual server group information file.

Specify the correct virtual server group information file, and then re-execute the command.

KEOS29770-E (C/F)

The operation to start a virtual server was not performed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

The virtual server is not started because the status does not enable the virtual server to start.

The command will terminate without processing if the virtual server identifier is specified. If the virtual server identifier is not specified, the processing continues.

Action

Execute the vmiunit status command to check the virtual server status.

Remove the cause of the error based on the details, and then re-execute the command.

Table 13‒29: List of error details described in KEOS29770-E

Details

Description

Action

An attempt to start the virtual server that should have started before this virtual server failed. (Identifier of virtual server that should have started first = aa....aa)

aa....aa: Virtual server identifier

An attempt to start the virtual server that should have started before this virtual server failed.

Take the action for the message output before this message.

KEOS29771-E (C/F)

The operation to stop a virtual server was not performed. (management unit name = aa....aa, virtual server identifier = bb....bb, details = cc....cc)

aa....aa: Management unit name

bb....bb: Virtual server identifier

cc....cc: Details

Description

The virtual server is not stopped because the status does not enable the virtual server to stop.

The command will terminate without processing if the virtual server identifier is specified. If the virtual server identifier is not specified, the processing continues.

Action

Execute the vmiunit status command to check the virtual server status.

Remove the cause of the error based on the details, and then re-execute the command.

Table 13‒30: List of error details described in KEOS29771-E

Details

Description

Action

An attempt to stop the virtual server that should have stopped before this virtual server failed. (Identifier of virtual server that should have stopped first = aa....aa)

aa....aa: Virtual server identifier

An attempt to stop the virtual server that should have stopped before this virtual server failed.

Take the action for the message output before this message.

KEOS29772-E (C/F)

The same tier-wise definition directory has been specified using a different case. (directory path 1 = aa....aa, directory path 2 = bb....bb)

aa....aa: Directory path 1

bb....bb: Directory path 2

Description

The same tier-wise definition directory has been specified using a different case.

The processing will be cancelled.

Action

Check the tier-wise definition directory below the definition directory specified in the -dir argument.

Change the name of the tier-wise definition directory, and then re-execute the command.

KEOS29773-E (C/F)

The specified virtual server identifier is already being used as the virtual server identifier or business IP address of another virtual server specified in the virtual server group information file. (management unit name = aa....aa, virtual server identifier = bb....bb)

aa....aa: Specified management unit name

bb....bb: Specified virtual server identifier

Description

The specified virtual server identifier is already being used as the virtual server identifier or business IP address of another virtual server specified in the virtual server group information file.

The possible causes are that the specified virtual server identifier is incorrect, or the virtual server identifier or business IP address of another virtual server is incorrect.

The processing will be cancelled.

Action

Check the contents of the virtual server group information file.

Change the virtual server identifier, and then re-execute the command.

KEOS29774-E (C/F)

The specified business IP address is already being used as the virtual server identifier or business IP address of another virtual server specified in the virtual server group information file. (management unit name = aa....aa, business IP address = bb....bb)

aa....aa: Specified management unit name

bb....bb: Specified business IP address

Description

The specified business IP address is already being used as the virtual server identifier or business IP address of another virtual server specified in the virtual server group information file.

The processing will be cancelled.

Action

Check the contents of the virtual server group information file.

Change the business IP address, and then re-execute the command.

KEOS29775-W (C/F)

An error mark has been set for a running virtual server group. (management unit name = aa....aa, virtual server group name = bb....bb)

aa....aa: Management unit name

bb....bb: Virtual server group name

Description

A virtual server group with an error mark will be operated.

The processing continues.

Action

Execute the vmiunit status command to check the error mark setup time and the error mark comments.

Execute the vmiunit unmark command to remove the error mark as and when required, and then re-execute the command.

KEOS29776-E (C/F)

The OS type defined in the tier-wise property file is not compatible with the virtual server OS. (management unit name = aa....aa, tier identifier = bb....bb, virtual server identifier = cc....cc, defined OS type = dd....dd, virtual server OS name = ee....ee)

aa....aa: Management unit name

bb....bb: Tier identifier

cc....cc: Virtual server identifier

dd....dd: Defined OS type

ee....ee: Virtual server OS name

Description

The OS type defined in the tier-wise property file is not compatible with the virtual server OS.

The processing will be cancelled.

Action

The possible causes are as follows. Take action based on the respective causes, and then re-execute the command.

The OS type specified in tier.target.os in the tier-wise property file is incorrect.

Revise the value specified for tier.target.os in the tier-wise property file, and then execute the vmiunit import command to re-import the definition.

The virtual server OS is incorrect.

Re-install the virtual server OS.

14 KEQR (Messages Output by the Virtual Server Manager Setup Tool) (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

14.1 (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

15 KEUC (Messages Output when Switching Between Execution Environments)

This chapter describes the messages output when switching between execution environments.

15.1 Message Description Format

The format of message descriptions in this manual is as follows:

KEUCnnnnn-Y (Z)

Message text

Explanation of variable values

Description

Supplementary explanation for the message text

Action

Action performed by the user

Note that depending upon the message, Explanation of variable values, Description, and Action may not be described.

The description of each item is as follows:

KEUCnnnnn

This indicates message IDs.

The description of elements configuring a message ID is as follows:

KEUC

This indicates a prefix of messages output when switching between the built execution environments.

nnnnn

This indicates a message number managed when switching between the built execution environments. A five-digit specific number is attached to the respective messages.

Y

This indicates the message level. The message level is shown with one alphabetic character.

The characters showing message levels and their meaning are mentioned below:

E (Error)

This message reports that an error level problem has occurred.

The process is interrupted when this message is output.

W (Warning)

This message reports that a warning level problem has occurred.

The process continues even after the message is output.

I (Information)

This message reports a system operation.

The process continues even after the message is output.

Q (Question)

This message reports a user response for the output message.

When this message is output, the system waits for the user response.

R (Request)

This message reports that the system is waiting for a user response.

(Z)

This indicates the output destination of the message. The output destination is indicated with one alphabetic character.

The characters showing the output destination and their meaning are described below:

C: Output to the console.

F: Output to the log file.

L: Output to the event log.

M: Output to the Log Monitor screen.

S: Output to syslog (in UNIX).

W: Output to the Management Server window.

Important note

Message output destination is additional information used in the manual.

Message text

This indicates the message text output when switching between the built execution environments.

Note that the variable value (value that changes according to the message output status) in the message text is shown in the format of 'xx....xx' (xx are lower case alphabetic characters).

Explanation of variable values

The information displayed in the variable value within the message text is shown in the format of 'xx....xx: displayed information' (xx are lower case alphabetic characters). A format example of the explanation of variable values is shown below:

(Example)

aa....aa: File name

bb....bb: Application name

Description

This indicates the supplementary message explanation items such as the factors due to which the message is reported and configuration software operations that output the message.

Action

This indicates the actions performed by the user. Note that 'Contact the maintenance personnel' in the action indicates that the system administrator needs to contact our helpdesk based on the purchase agreement.

15.2 Messages beginning with KEUC

This section describes the messages from KEUC00001 to KEUC09999 that are output when you switch an already built execution environment.

KEUC00001-I (C)

The cosmienv aa....aa command will now start.

aa....aa: -s, -d, -r, or -l

Description

The cosmienv aa....aa command is started.

KEUC00002-I (C)

The cosmienv aa....aa command ended successfully.

aa....aa: -s, -d, -r, or -l

Description

The cosmienv aa....aa command ended successfully.

KEUC00003-E (C)

Execution of the cosmienv aa....aa command failed. (code = bb....bb[, cc....cc])

aa....aa: -s, -d, -r, or -l

bb....bb: Return code

cc....cc: Maintenance code

Description

An attempt to execute the cosmienv aa....aa command has failed.

Action

Check the return code output to the message, and take action. Note that when the return code is 143, the maintenance code is also displayed in sync.

For details about return codes and actions, reference the following table.

Table 15‒1: Return codes and actions

Return code

Meaning

Action

0

Normal termination

--

128

Abnormal termination

Acquire the output message and log, and contact maintenance personnel.

129

The information which is the basis of storage or restoration operation is incorrect

130

An error has occurred in the post-processing of storage or restoration operation

131

The information required for storage or restoration operation is incorrect

Check that the installed product version supports switching of the built execution environments. If the problem is still not resolved, acquire the output message and log, and contact maintenance personnel.

133

Disk access error

Acquire the output message and log, and contact maintenance personnel.

135

File open error

Acquire the output message and log, and contact maintenance personnel.

138

An invalid argument is specified

Check the command syntax.

139

An unsupported function is requested

Check the installed products.

140

An execution request is sent for an already running command

Make sure that the command is not running.

141

The operating environment is invalid

Before you execute the recovery function, check the following contents:

Cosminexus must be uninstalled

Unnecessary files must not be present in the installation destination

142

Execution permission is not available

Check the permissions when the command is issued.

143

A failure has occurred while processing the component software

Check the maintenance code (cc....cc of bb....bb[,cc....cc]) of the component software displayed in the message. For details about maintenance codes, reference the following table.

For the error-generating component software, check the cosmienv command log.

Table 15‒2: Maintenance codes of the component software

Component software

Maintenance code

Meaning

Action

Cosminexus Component Container

145

An attempt to install HNTRLib has failed

Re-install Cosminexus Component Container.

146

An attempt to execute the storage operation has failed

Take action with any of the following methods:

Create the specified storage directory.

Specify an existent directory path.

147

Abnormal termination

Collect the files present below /opt/Cosminexus/env/log, and then contact maintenance personnel.

Cosminexus Component Transaction Monitor

129

The information which is the basis of storage or restoration operation is incorrect

Acquire the output message and log, and contact maintenance personnel.

130

A post-processing error of storage or restoration operation

131

The information required for storage or restoration operation is incorrect

138

An invalid argument is specified

142

The executing user is an unauthorized user

Confirm that the process is executed with root authority.

146

The storage directory does not exist

Take action with any of the following methods:

Create the specified storage directory.

Specify an existent directory path.

147

Other errors

Acquire the output message and log, and contact maintenance personnel.

148

An attempt to delete the file or directory has failed

Cosminexus DABroker Library

128

Abnormal termination

Acquire the output message and log, and contact maintenance personnel.

131

The information required for storage or restoration operation is incorrect

138

An invalid argument is specified

Check the command arguments, and re-execute the process.

144

The Cosminexus DABroker Library is running

Terminate all programs that are currently accessing the Cosminexus DABroker Library, and re-execute the process.

Cosminexus Developer's Kit for Java

131

The information required for storage or deletion operation is incorrect

Acquire the output message and log, and contact maintenance personnel.

138

An invalid argument is specified

Acquire the output message and log, and contact maintenance personnel.

144

An attempt to execute the Recover operation has failed

Acquire the output message and log, and contact maintenance personnel.

145

/opt/Cosminexus/jdk is a symbolic link file

/opt/Cosminexus/jdk is not supported if it is a symbolic link file. Set the entity file.

146

Other errors

Acquire the output message and log, and contact maintenance personnel.

Cosminexus Performance Tracer

129

The information which is the basis of storage or restoration operation is incorrect

Acquire the output message and log, and contact maintenance personnel.

130

A post-processing error of storage or restoration operation

131

The information required for storage or restoration operation is incorrect

138

An invalid argument is specified

142

The executing user is an unauthorized user

Confirm that the process is executed with root authority.

145

An attempt to install HccLib has failed

Re-install the Java application.

146

The storage directory does not exist

Take action with any of the following methods:

Create the specified storage directory.

Specify an existent directory path.

147

Other errors

Acquire the output message and log, and contact maintenance personnel.

148

An attempt to delete the file or directory has failed

Cosminexus Reliable Messaging

129

The information which is the basis of storage or restoration operation is incorrect

Acquire the output message and log, and contact maintenance personnel.

130

An error has occurred in the post-processing of storage or restoration operation

144

An attempt to install HNTRLib2 has failed

Re-install the Java application.

145

The storage directory does not exist

Take action with any of the following methods:

Create the specified storage directory.

Specify an existent directory path.

146

Other errors

Acquire the output message and log, and contact maintenance personnel.

Cosminexus TPBroker

129

The information which is the basis of storage or restoration operation is incorrect

Acquire the output message and log, and contact maintenance personnel.

130

An error has occurred in the post-processing of storage or restoration operation

131

The information required for storage or restoration operation is incorrect

133

Disk access error

135

File open error

144

An attempt to install HCCLib has failed

Re-install Cosminexus TPBroker.

145

An attempt to install HNTRLib2 has failed

146

An attempt to execute the storage operation has failed

Take action with any of the following methods:

Create the specified storage directory.

Specify an existent directory path.

147

An attempt to acquire or set up Hitachi PP installer information has failed

Acquire the output message and log, and contact maintenance personnel.

Cosminexus Web Services - Security

129

The information which is the basis of storage or restoration operation is incorrect

Acquire the output message and log, and contact maintenance personnel.

130

An error has occurred in the post-processing of storage or restoration operation

Acquire the output message and log, and contact maintenance personnel.

131

The information required for storage or restoration operation is incorrect

138

An invalid argument is specified

146

An attempt to execute the storage operation has failed

Take action with any of the following methods:

Create the specified storage directory.

Specify an existent directory path.

147

Other errors

Acquire the output message and log, and contact maintenance personnel.

148

An attempt to delete the file or directory has failed

Cosminexus XML Processor

128

Abnormal termination

Acquire the output message and log, and contact maintenance personnel.

138

An invalid argument is specified

Check the command arguments, and re-execute the process.

144

An attempt to execute the storage operation has failed

Take action using the following procedure:

Create the specified storage directory. or specify an existent directory path.

Terminate the usage of Cosminexus XML Processor.

145

An attempt to install HNTRLib2 has failed

Re-install Cosminexus XML Processor.

Cosminexus HTTP Server

128

Abnormal termination

Acquire the output message and log, and contact maintenance personnel.

138

An invalid argument is specified

144

An attempt to execute the storage operation has failed

Take action with any of the following methods:

Create the specified storage directory.

Specify an existent directory path.

KEUC00004-I (C)

Command usage: cosmienv <options> [-I<identifier>] [-P<save-path>] [-f]

<options>:

-s - saves the Cosminexus environment

-d - deletes the saved Cosminexus environment

-r - restores the saved Cosminexus environment

-l - lists the saved Cosminexus environment

-h - displays this help information

<identifier>:

Specify a unique identifier to distinguish the Cosminexus environment to be saved.

Use a maximum of 20 alphanumeric characters.

This identifier must be specified when the -s,-d, or -r option is used.

<save-path>:

Specify the full path of the Cosminexus environment to be saved.

You cannot specify a 1-byte space, 2-byte space, or tab character in a path name.

The save destination of the Cosminexus environment becomes <save-path>/<identifier>.

This save path must be specified when the -s option is used.

<-f>:

When the -r option is specified, specify the -f option to force restoration of the Cosminexus environment.

If the -f option is specified, the Cosminexus environment will be restored even if there are files remaining in the Cosminexus installation directory.

If the -f option is not specified, the Cosminexus environment will not be restored if there are files remaining in the Cosminexus installation directory.

The -f option is ignored if it is specified with any option other than the -r option.

Description

This message describes the usage method of the cosmienv command.

KEUC00005-E (C)

To save, restore, or delete the Cosminexus system environment, use the cosmienv command.

Description

The operation for storing, restoring, or deleting the Cosminexus system environment is invalid.

Action

Use the cosmienv command to store, restore, and delete the Cosminexus system environment.

KEUC00006-E (C)

Command usage: cosmienv <options> [-I<identifier>] [-P<save-path>] [-f]

Description

The usage method of the cosmienv command is invalid.

Action

Make sure that the specification method for arguments of the cosmienv command is not invalid.

If the specification method of arguments is not invalid, execute echo $?, acquire the return codes of the cosmienv command, and take action for the return codes.

For details about return codes of the cosmienv command, see KEUC00003-E (C).

16 KEXS (Messages Output By Cosminexus XML Security - Core) (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

16.1 (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

17 KFCB (Messages Output by TPBroker) (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

17.1 (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

18 KFCB (Messages Output by TPBroker Operations) (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

18.1 (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

19 KFCT (Messages Output by CTM and PRF)

This chapter describes the messages output by CTM and PRF.

19.1 Message Description Format

The format of message descriptions in this manual is as follows:

KFCTnnnnn-Y

Message text

Explanation of variable values

Description

Supplementary explanation for the message text

Action

Action performed by the user

Note that depending upon the message, Explanation of variable values, Description, and Action may not be described.

The description of each item is as follows:

KFCTnnnnn

This indicates message IDs.

The description of elements configuring a message ID is as follows:

KFCT

This indicates a prefix of messages output by CTM and PRF.

nnnnn

This indicates the message number managed in the CTM or PRF. A unique five-digit number is assigned to each message.

Y

This indicates the message level. The message level is shown with one alphabetic character.

The characters showing message levels and their meaning are mentioned below:

E (Error)

This message reports that an error level problem has occurred.

The process is interrupted when this message is output.

W (Warning)

This message reports that a warning level problem has occurred.

The process continues even after the message is output.

I (Information)

This message reports a system operation.

The process continues even after the message is output. In Windows, the message output by PRF is output to the standard error output.

Q (Question)

This message reports a user response for the output message.

When this message is output, the system waits for the user response.

R (Request)

This message reports that the system is waiting for a user response.

Message text

This indicates the message text output by CTM and PRF.

Note that the variable value (value that changes according to the message output status) in the message text is shown in the format of 'xx....xx' (xx are lower case alphabetic characters).

Explanation of variable values

The information displayed in the variable value within the message text is shown in the format of 'xx....xx: displayed information' (xx are lower case alphabetic characters). A format example of the explanation of variable values is shown below:

(Example)

aa....aa: File name

bb....bb: Application name

Description

This indicates supplementary explanation for a message, such as the factors for notifying messages or the CTM and PRF operations.

Action

This indicates the actions performed by the user. Note that 'Contact the maintenance personnel' in the action indicates that the system administrator needs to contact our helpdesk based on the purchase agreement.

19.2 Messages from KFCT20000 to KFCT29999

This section describes the messages from KFCT20000 to KFCT29999, output by CTM and PRF.

KFCT26949-E

"aa....aa(bb....bb)" failed.errno=cc....cc

aa....aa: System call in which the error occurred

bb....bb: Internal information (Name of the file that invoked the system call)

cc....cc: errno value of the system call

Description

An error occurred in the system call. The processing will be interrupted.

Action

Check the reason for the system call error.

KFCT26999-W

trace data was not able to output, because the buffer area was insufficient.

Description

The buffer area is temporarily insufficient; therefore, the trace data is not output. After displaying this message, the trace data is not output until some space is made available in the buffer area. The trace data is output automatically when the buffer area has sufficient space.

Action

We recommend that the buffer size for PRF trace collection to be larger than the set value. Change the buffer size with the -PrfTraceBufferSize option of the cprfstart command. For details on the cprfstart command, see the manual uCosminexus Application Server Command Reference Guide.

KFCT27600-I

aa....aa was assigned as current trace file. ID:bb....bb

aa....aa: Assigned file name

bb....bb: PRF identifier or CTM identifier

Description

The file that outputs a PRF trace or the file that outputs statistical information was assigned. The processing continues.

19.3 Messages from KFCT70000 to KFCT79999

This section describes the messages from KFCT70000 to KFCT79999 output by CTM and PRF.

KFCT70002-E

cannot open file : aa....aa

aa....aa: Name of the file that cannot be opened

Description

The file aa....aa cannot be opened.

The command process will be interrupted.

Action

Confirm that the file described in aa....aa exists, and that the read permission is available.

KFCT70003-E

invalid command argument.

Description

A command argument is invalid.

The command process will be interrupted.

Action

Revise the command argument.

KFCT70004-E

TSCDIR variable undefined.

Description

The environment variable TSCDIR is not defined.

The command process will be interrupted.

Action

Define the environment variable TSCDIR.

KFCT70322-E

not enough memory.

Description

Memory is insufficient.

The command process will be interrupted.

Action

Terminate other programs to secure sufficient memory, and then re-execute the command.

KFCT70332-E

aa....aa failed.bb....bb.

aa....aa: Name of the failed command

bb....bb: Reason for the failure (message from the command)

Description

An attempt to execute an internal command has failed.

The command process will be interrupted.

Action

See the information described in bb....bb, and then remove the cause of the error.

KFCT70450-E

the error occurred while initializing idl function. reason=aa....aa kind=bb....bb code1=cc....cc code2=dd....dd.

aa....aa: Reason for occurrence of error

bb....bb: Process type (ctmd: CTM daemon or ctmregltd: CTM regulator, ORB gateway)

cc....cc: Maintenance information 1

dd....dd: Maintenance information 2

Description

An error occurred while initializing the daemon process.

The program startup process will be interrupted.

Action

Take action based on the reasons for the error occurrence described in aa....aa, and then re-execute the command. The following table lists the reasons for the error occurrence described in aa....aa and the corresponding actions.

Table 19‒1: List of causes described in KFCT70450-E

Cause of error

Cause

Action

BAD_ENVIRONMENT

An attempt to acquire the environment variables has failed.

Confirm that the environment variables CTMSPOOL and CTMDIR are setup and, if necessary, revise them.

FILE_ACCESS

An attempt to access the file has failed.

Confirm that the CTMSPOOL directory exists, that you have access permissions, and also that enough free space is available on the disk and, if necessary, revise.

NO_MEMORY

Memory is insufficient.

Terminate the unnecessary processes or increase the memory.

LOCK_ERROR

An attempted exclusive control has failed.

If the memory is insufficient, terminate the unnecessary processes or increase the memory.

In other cases, contact maintenance personnel.

ACTIVATE

An attempt to activate the receive functionality has failed.

Acquire the contents of reason (aa....aa), kind (bb....bb), code1 (cc....cc), code2 (dd....dd), and then contact maintenance personnel.

PORT_ALREADY_USED

A duplicate EJB request receiving port number was detected.

The EJB request receiving port number may already be in use.

You can adjust the port number with the -CTMEjbPort option.

EJBPORT

The specified ORB gateway receiving port is invalid.

If the -CTMIDLConnect option is specified, specify the -CTMEjbPort option.

INVALID_OPTION

The specified option is invalid.

Specify the -CTMAgent 1 or -CTMIDLConnect option.

INTERNAL

An internal contradiction occurred.

Acquire the contents of reason (aa....aa), kind (bb....bb), code1 (cc....cc), code2 (dd....dd), and then contact maintenance personnel.

UNKNOWN

An unknown error occurred.

Acquire the contents of reason (aa....aa), kind (bb....bb), code1 (cc....cc), code2 (dd....dd), and then contact maintenance personnel.

OTHER

An error other than that specified above occurred.

Acquire the contents of reason (aa....aa), kind (bb....bb), code1 (cc....cc), code2 (dd....dd), and then contact maintenance personnel.

KFCT70451-E

the error occurred while communicating with J2EE Server. exception=aa....aa detail=bb....bb code1=cc....cc code2=dd....dd.

aa....aa: Name of the CORBA exception that occurred

bb....bb: Minor code of the CORBA exception that occurred or Completion status of the CORBA exception that occurred

If this information cannot be acquired, " - " is displayed.

cc....cc: Maintenance information 1

dd....dd: Maintenance information 2

Description

An error occurred when communicating with the J2EE Server.

The processing of the daemon process continues.

Action

See the exception (aa....aa) and detail (bb....bb) in this message, and then remove the cause of the error.

KFCT70452-E

the error occurred while processing aa....aa message. reason=bb....bb code1=cc....cc code2=dd....dd.

aa....aa: Message type (request: Request message to the J2EE server or reply: Reply message from the J2EE server)

bb....bb: Reason for occurrence of error

cc....cc: Maintenance information 1

dd....dd: Maintenance information 2

Description

An error occurred while processing the request or reply message.

The processing of the daemon process continues.

Action

Take action based on the reasons for the error occurrence described in bb....bb, and then re-execute the command. The following table lists the reasons for the error occurrence described in bb....bb and the corresponding actions.

Table 19‒2: List of errors described in KFCT70452-E

Cause of error

Cause

Action

NO_MEMORY

Memory is insufficient.

Terminate the unnecessary processes or increase the memory.

NOT_SUPPORT_VER

A GIOP message of an unsupported version was received.

Use the appropriate versions for the pre-requisite products of the user application and the application server.

INTERNAL

An internal contradiction occurred.

Acquire the contents of aa....aa, reason (bb....bb), code1 (cc....cc), code2 (dd....dd), and then contact maintenance personnel.

UNKNOWN

An unknown error occurred.

Acquire the contents of aa....aa, reason (bb....bb), code1 (cc....cc), code2 (dd....dd), and then contact maintenance personnel.

OTHER

An error other than that specified above occurred.

Acquire the contents of aa....aa, reason (bb....bb), code1 (cc....cc), code2 (dd....dd), and then contact maintenance personnel.

KFCT70453-E

the error occurred while processing aa....aa message. exception=bb....bb detail=cc....cc reason=dd....dd code1=ee....ee code2=ff....ff.

aa....aa: Message type (request: Request message to the J2EE server or reply: Reply message from the J2EE server)

bb....bb: Name of the thrown CORBA exception

cc....cc: Minor code of the thrown CORBA exception or Completion status of the thrown CORBA exception

dd....dd: Reason for occurrence of error

ee....ee: Maintenance information 1

ff....ff: Maintenance information 2

Description

An error occurred while processing the request or reply message; hence, a CORBA system exception is thrown.

The processing of the daemon process continues.

Action

Take action based on the reasons for the error occurrence described in dd....dd, and then re-execute the command. The following table lists the reasons for the error occurrence described in dd....dd and the corresponding actions.

Table 19‒3: List of causes described in KFCT70453-E

Cause of error

Cause

Action

NO_MEMORY

Memory is insufficient.

Terminate the unnecessary processes or increase the memory.

NOT_SUPPORT_VER

A GIOP message of an unsupported version was received.

Use the appropriate versions for the pre-requisite products of the user application and the application server.

INTERNAL

An internal contradiction occurred.

Acquire the contents of aa....aa, exception (bb....bb), detail (cc....cc), reason (dd....dd), code1 (ee....ee), code2 (ff....ff), and then contact maintenance personnel.

UNKNOWN

An unknown error occurred.

Acquire the contents of aa....aa, exception (bb....bb), detail (cc....cc), reason (dd....dd), code1 (ee....ee), code2 (ff....ff), and then contact maintenance personnel.

OTHER

An error other than that specified above occurred.

Acquire the contents of aa....aa, exception (bb....bb), detail (cc....cc), reason (dd....dd), code1 (ee....ee), code2 (ff....ff), and then contact maintenance personnel.

KFCT70457-E

the error occurred while getting aa....aa reference. reason=bb....bb code1=cc....cc code2=dd....dd.

aa....aa: EJB reference type (Home interface: home interface reference or EJB object: EJB object reference)

bb....bb: Reason for occurrence of error

cc....cc: Maintenance information 1

dd....dd: Maintenance information 2

Description

An error occurred while acquiring the home interface reference or the EJB object reference.

The processing of the daemon process continues.

Action

Take action based on the reasons for the error occurrence described in bb....bb, and then re-execute the command. The following table lists the reasons for the error occurrence described in bb....bb and the corresponding actions.

Table 19‒4: List of causes described in KFCT70457-E

Cause of error

Cause

Action

NO_MEMORY

Memory is insufficient.

Terminate the unnecessary processes or increase the memory.

NOT_SUPPORT_VER

A GIOP message of an unsupported version was received.

Use the appropriate versions for the pre-requisite products of the user application and the application server.

INTERNAL

An internal contradiction occurred.

Acquire the contents of aa....aa, reason (bb....bb), code1 (cc....cc), code2 (dd....dd), and then contact maintenance personnel.

UNKNOWN

An unknown error occurred.

Acquire the contents of aa....aa, reason (bb....bb), code1 (cc....cc), code2 (dd....dd), and then contact maintenance personnel.

OTHER

An error other than that specified above occurred.

Acquire the contents of aa....aa, reason (bb....bb), code1 (cc....cc), code2 (dd....dd), and then contact maintenance personnel.

KFCT70458-E

the error occurred while propagating information of remote exception. reason=aa....aa code1=bb....bb code2=cc....cc.

aa....aa: Reason for occurrence of error

bb....bb: Maintenance information 1

cc....cc: Maintenance information 2

Description

An error occurred while propagating the details of an exception thrown in the J2EE server to the EJB client.

The processing of the daemon process continues.

Action

Take action based on the reasons for the error occurrence described in aa....aa, and then re-execute the command. The following table lists the reasons for the error occurrence described in aa....aa and the corresponding actions.

Table 19‒5: List of causes described in KFCT70458-E

Cause of error

Cause

Action

NO_MEMORY

Memory is insufficient.

Terminate the unnecessary processes or increase the memory.

LOCK_ERROR

An attempted exclusive control has failed.

If the memory is insufficient, terminate the unnecessary processes or increase the memory.

In other cases, acquire the contents of reason (aa....aa), code1 (bb....bb), code2 (cc....cc), and then contact maintenance personnel.

INTERNAL,INVALID_PARAM

An internal contradiction occurred.

Acquire the contents of reason (aa....aa), code1 (bb....bb), code2 (cc....cc), and then contact maintenance personnel.

OTHER, INVALID_STATUS, -

An error other than that specified above occurred.

Acquire the contents of reason (aa....aa), code1 (bb....bb), code2 (cc....cc), and then contact maintenance personnel.

KFCT70459-E

the timeout occurred while communicating with J2EE Server. time=aa....aa detail=bb....bb code1=cc....cc code2=dd....dd.

aa....aa: Timeout period (seconds)

bb....bb: Minor code of the CORBA exception that occurred or Completion status of the CORBA exception that occurred

cc....cc: Maintenance information 1

dd....dd: Maintenance information 2

Description

A timeout occurred while communicating with the J2EE Server.

The processing of the daemon process continues.

Action

See the contents of time (aa....aa) in this message, and then remove the cause of the error.

KFCT70460-E

command argument is invalid. option=aa....aa value=bb....bb code=cc....cc.

aa....aa: Invalid option name

bb....bb: Invalid option argument

cc....cc: Maintenance information

Description

The option is invalid. The daemon processing will be interrupted.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT70470-I

usage: ctmjava2idl [-h] | [-g] [-o output-file] [-c class-path] class-file.

Description

This message describes the usage method of the ctmjava2idl command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT70471-I

usage: ctmidl2cpp [-h] | [-TSCclient_ext ext-string] [-TSChdr_suffix hdr-suffix] [-TSCsrc_suffix src-suffix] [-client_ext ext-string] [-hdr_suffix hdr-suffix] [-src_suffix src-suffix] [-TSCroot_dir directory] [-TSCsrc_dir directory] [-TSChdr_dir directory] [-root_dir directory] [-TSCexport tag-string] [-export tag-string] [-type_code_info] [-namespace] [-gen_included_files] [[-I directory[;directory...]]...] [-A] idlfile

Description

This message describes the usage method of the ctmidl2cpp command. This error message is displayed when the command format is invalid or when the -h option is specified.

If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT70472-I

usage: ctmidl2j [-h] | [-package package_name][-TSCroot_dir directory][-root_dir directory] [-gen_included_files][[-I directory[;directory...]]...][-A] idlfile

Description

This message describes the usage method of the ctmidl2j command. This error message is displayed when the command format is invalid or when the -h option is specified.

If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT70473-E

usage: the internal error occurred. reason=aa....aa code=bb....bb.

aa....aa: Name of the process

bb....bb: Error code

Description

This message is displayed when an error occurs in the internal invocation process. The command terminates with an error.

Action

Confirm the following details:

The IDL definition file contents

The specification of the environment variable

If a problem does not exist in the IDL definition file and the environment variable, contact maintenance personnel.

KFCT70474-E

usage: unsupported version. code=aa....aa.

aa....aa: Acquired OTM version

Description

This message is displayed when the version of OTM being used is invalid. The command terminates with an error.

Action

Revise the environment specified for the environment variable TSCDIR.

KFCT70500-I

now starting ctmdmd.

Description

The CTM domain manager is being started.

The startup process of the CTM domain manager continues.

KFCT70501-E

cannot start ctmdmd because another ctmdmd with the same domain name is operating. domain name = aa....aa

aa....aa: CTM domain name

Description

A CTM domain manager with the same CTM domain name is running; hence, the CTM domain manager cannot be started.

The startup process of the CTM domain manager will be interrupted.

Action

Wait for the running CTM domain manager to stop and restart the CTM domain manager or change the CTM domain name, and then restart the CTM domain manager.

KFCT70502-I

ctmdmd is now online.

Description

The startup process of the CTM domain manager is complete.

The processing of the CTM domain manager continues.

KFCT70503-I

now terminating ctmdmd. terminate type=aa....aa

Termination type (NORMAL STOP: Normal termination or FORCE STOP: Forced normal termination)

Description

The CTM domain manager is being terminated.

The processing of the CTM domain manager continues.

KFCT70504-I

ctmdmd stop.

Description

The CTM domain manager has stopped.

KFCT70505-I

now starting ctmd.

Description

The CTM daemon is being started.

The processing of the CTM daemon continues.

KFCT70506-E

cannot start ctmd because another ctmd with the same CTMID is operating in the same domain. CTMID=aa....aa

aa....aa: CTM identifier

Description

A CTM daemon with the same CTM identifier is running; hence, the CTM daemon cannot be started.

The startup process of the CTM daemon will be interrupted.

Action

Wait for the termination of the running CTM daemon, and then re-execute the process. Alternatively, change the CTM identifier and then restart the CTM daemon.

KFCT70507-E

the combination of domain name and CTMSPOOL directory is invalid.

Description

The combination of the CTM domain name and CTMSPOOL is invalid.

The startup process of the CTM domain manager and the CTM daemon will be interrupted.

Action

Check if the following items are applicable to the combination of the CTM domain name and CTMSPOOL:

The specified CTMSPOOL is already being used for a CTM domain manager with another CTM domain name.

The CTM domain manager with the specified CTM domain name is already being operated by using another CTMSPOOL.

If the above points are applicable to the combination, specify a valid combination again, and then restart the process. However, check the environment when starting the CTM domain manager. If the applicable CTMSPOOL directory is not used and you want to operate using a new combination, use the ctmdminfo command to delete the CTM domain information, and then restart the CTM domain manager.

KFCT70508-W

CTMSPOOL directory is not specified. $CTMDIR/spool suppose to $CTMSPOOL.

Description

The environment variable CTMSPOOL is not specified.

The directories $CTMDIR/spool (in UNIX) or %CTMDIR%\spool (in Windows) will be assumed as $CTMSPOOL (in UNIX) or %CTMSPOOL% (in Windows) and the processing continues.

KFCT70509-E

cannot start aa....aa because of improper operational environment. reason code=bb....bb

aa....aa: CTM daemon (ctmd: CTM daemon or ctmdmd: CTM domain manager)

bb....bb: Cause of inability to start the daemon

Description

The operational environment is improper; hence, the daemon process cannot be started.

The daemon startup process will be interrupted.

Action

Check the causes that are described in bb....bb, and then take action.

The following causes are described in bb....bb:

MEMORY

Check whether the actual memory size and swap memory size of the OS is sufficient.

ENV_CTMDIR

Define the environment variable CTMDIR. Check whether CTMDIR directory can be accessed.

ENV_CTMSPOOL

Check whether CTMSPOOL directory can be accessed.

KFCT70510-I

ctmd is now online.

Description

The startup process of the CTM daemon is complete and online business can be started.

The processing of the CTM daemon continues.

KFCT70511-I

now terminating ctmd. terminate type=aa....aa

aa....aa: Termination type (NORMAL STOP: Normal termination or FORCE STOP: Forced termination)

Description

The CTM daemon is being terminated.

The processing of the CTM daemon continues.

KFCT70512-I

ctmd stop.

Description

The CTM daemon has stopped.

KFCT70513-E

command argument is invalid. option=aa....aa

aa....aa: Invalid option name

Description

The specification of the command argument is invalid.

The command terminates with an error.

Action

Confirm the following details:

Is the specified option invalid?

Is the option that cannot be omitted, omitted?

Can the specified option be specified at the same time as other options?

Modify the specified option that was invalid, specify an option with a valid combination, and then re-execute the command.

KFCT70514-I

usage:ctmstart [-h] [-CTMDomain domain_name] [-CTMID ctmid]

[-CTMPort port_no] [-CTMEjbPort port_no] [-CTMMyHost host_name]

[-CTMEntryCount count] [-CTMNice nice] [-CTMRegStart count]

[-CTMRegOption file] [-CTMEnviron file] [-CTMStartTimeOut time]

[-CTMTSCGwStart count] [-CTMTSCGwOption file]

-CTMINSRef host_name:port_number [-CTMDCSendTimeOut time]

[-CTMClientConnectCount count] [-CTMServerConnectCount count]

[-CTMLogFileSize file_size] [-CTMLogFileCount file_count]

[-PRFID cprfid] [-CTMQueueCount count] [-CTMQueueRegistCount count]

[-CTMServerCacheSize size] [-CTMDispatchPolicy normalDispatch | priorDispatch]

[-CTMDispatchParallelCount count] [-CTMMaxRequestCount count]

[-CTMQueueDeleteWait time] [-CTMWatchQueue percent,percent,interval,mode]

[-CTMCreatePolicy normalDispatch | priorDispatch]

[-CTMWatchRequest count,interval] [-CTMLoadCheckInterval interval]

[-CTMStatsUse Y|N] [-CTMStatsFileCount file_count] [-CTMStatsFileSize file_size]

Description

This message describes the usage method of the ctmstart command. This error message is displayed when the command format is invalid or when the -h option is specified.

If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT70515-I

usage:ctmstop [-h] [-CTMDomain domain_name] [-CTMID ctmid][-CTMMyHost host_name] [-CTMForce [-CTMDebugInfo]]

Description

This message describes the usage method of the ctmstop command. This error message is displayed when the command format is invalid or when the -h option is specified.

If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT70516-I

usage:ctmdmstart [-h] [-CTMDomain domain_name] [-CTMMaxCTM ctmd_cnt] [-CTMPort port_no] [-CTMMyHost host_name] [-CTMForceStart | -CTMAutoForce] [-CTMSendInterval value] [-CTMSubnetMask value] [-CTMSendHost host_name] [-CTMSendHostInterval value][-CTMAliveCheckCount value]

Description

This message describes the usage method of the ctmdmstart command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT70517-I

usage:ctmdmstop [-h] [-CTMDomain domain_name] [-CTMMyHost host_name] [-CTMForce [-CTMDebugInfo]]

Description

This message describes the usage method of the ctmdmstop command.

This message is displayed when the command format is invalid, or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT70518-E

the number of processes (EJBRegulator and J2EE server) is over connection count

Description

The number of connection processes exceeds the number of connections.

The registration process will be interrupted and the processing of the CTM daemon continues.

Action

Check whether the number of connection processes exceeds the value specified in the -CTMEntryCount option.

KFCT70520-E

internal error occurred. err_code=aa....aa-bb....bb exception=cc....cc

aa....aa: Reason code 1

bb....bb: Reason code 2

cc....cc: Exception information

Description

An exception occurred in the internal processing.

The daemon processing will be interrupted.

Action

Acquire the reason code (aa....aa and bb....bb) and exception information (cc....cc), and then contact System Administrator.

KFCT70522-E

the number of ctmd processes is over connection count.

Description

The number of registered CTM daemons exceeds the number of connections.

The registration process will be interrupted and the processing of the CTM daemon continues.

Action

Check whether the number of connection processes exceeds the number of connections.

KFCT70523-E

cannot access shared memory.

Description

An error occurred while accessing the shared memory.

The daemon processing will be interrupted.

Action

Confirm the following details, and then take action:

Is the shared memory created?

Confirm that the daemon is running, and then re-execute the command.

Does the shared memory size exceed the maximum size that can be acquired?

Increase the memory or change the size to be acquired.

Is the relationship between the CTM domain name and CTMSPOOL specified in the -CTMDomain option invalid?

Specify an appropriate value in the -CTMDomain option.

KFCT70524-E

CTMDIR directory is not specified.

Description

The environment variable CTMDIR is not specified.

The daemon processing will be interrupted.

Action

Check the environment variable.

KFCT70525-E

too many files are open in this process.

Description

The number of files that can be opened in the process exceeds the maximum value.

In the case of the daemon, an error message will be displayed and the processing continues. In the case of the command, the processing will be interrupted.

Action

Check the maximum number of files that can be opened in the process.

KFCT70526-E

internal error occurred. err_code=aa....aa-bb....bb

aa....aa: Reason code 1

bb....bb: Reason code 2

Description

An error occurred in the internal processing.

The daemon processing will be interrupted.

Action

Acquire the reason code (aa....aa and bb....bb), and then contact System Administrator.

KFCT70527-E

cannot find ctmd with specified CTMID in this domain. CTMID=aa....aa.

aa....aa: CTM identifier

Description

A CTM daemon with the specified CTM identifier cannot be found.

The daemon processing will be interrupted.

Action

Check whether the CTM daemon with the specified CTM identifier is running.

This message may also be displayed when the CTM daemon is present. In such cases, you check whether the specified option is invalid or whether the option does not enable communication with the CTM daemon. Confirm that the -CTMDomain option and the -CTMID option is valid.

In cases other than above, execute ctmstop -TMForce -CTMDebugInfo and then forcibly terminate the CTM daemon.

KFCT70528-E

cannot find ctmdmd with specified domain name. domain name = aa....aa.

aa....aa: CTM domain name

Description

A CTM domain manager with the specified CTM domain name cannot be found.

When this message is displayed in the CTM domain manager, the processing of the daemon continues. In other cases, the processing of the command or the daemon will be interrupted.

This message is also displayed when the CTM domain manager is present. In such cases, you check whether the specified option is invalid or whether the option does not enable communication with the CTM domain manager.

Action

Confirm that the CTM domain manager with the specified CTM domain name is running.

Take the following actions based on the process output by this message:

In the case of the ctmdmstop command

Check whether the -CTMDomain option is valid. In other cases, execute "ctmdmstop -CTMForce -CTMDebugInfo", and then forcibly terminate the CTM domain manager.

In the case of ctmstart command

Check whether the -CTMDomain option is valid. In other cases, execute ctmdmstop -CTMForce -CTMDebugInfo, forcibly terminate the CTM domain manager, collect the data, and then restart the CTM domain manager. Restart the CTM daemon after this.

KFCT70529-E

the specified CTMPort number may be repeated.

Description

The daemon processing will be interrupted.

The port number specified in the -CTMPort option may already be in use.

Action

Change the port number, and then restart the daemon.

KFCT70530-E

the initialization of domain manager is failed. error_code1=aa....aa error_code2=bb....bb.

aa....aa: Maintenance information 1

bb....bb: Maintenance information 2

Description

An attempt to initialize the CTM domain manager has failed.

The daemon processing will be interrupted.

The port number specified in the -CTMPort option may have already been used in the other processes.

Action

See the error message displayed before this message, and then take action. If you do not understand the troubleshooting method from the error message, acquire the value of error_code1 (aa....aa) and error_code2 (bb....bb), and then contact System Administrator.

KFCT70531-E

cannot start sending UDP.

Description

The CTM domain manager has failed to start sending the UDP.

The daemon processing will be interrupted.

Action

See the error message displayed before this message, and then take action.

KFCT70532-E

the initialization of ctmd is failed. error_code1=aa....aa error_code2=bb....bb.

Description

An attempt to initialize the CTM daemon has failed.

The daemon processing will be interrupted.

Action

See the error message displayed before this message, and then take action. If you do not understand the troubleshooting method from the error message, acquire the value of error_code1 (aa....aa) and error_code2 (bb....bb), and then contact System Administrator.

KFCT70533-I

CTMDIR directory=aa....aa

CTM version=bb....bb

CTMSPOOL directory=cc....cc

CTMDomain=dd....dd

CTMPort=ee....ee

aa....aa: CTMDIR directory

bb....bb: Version

cc....cc: CTMSPOOL directory

dd....dd: CTM domain name

ee....ee: CTMPort value

Description

The information related to the running CTM domain manager is output.

The startup process of the CTM domain manager continues.

KFCT70534-I

CTMDIR directory=aa....aa

CTM version=bb....bb

CTMSPOOL directory=cc....cc

CTMDomain=dd....dd

CTMID=ee....ee

CTMPort=ff....ff

aa....aa: CTMDIR directory

bb....bb: Version

cc....cc: CTMSPOOL directory

dd....dd: CTM domain name

ee....ee: CTM identifier

ff....ff: CTMPort value

Description

The information related to the running CTM daemon is displayed.

The startup process of the CTM daemon continues.

KFCT70535-I

ctmdmd determined start type. start type=aa....aa.

aa....aa: Starting type (NORMAL START: Normal start, FORCE START: Forced normal start, or AUTO FORCE START: Automatic forced start)

Description

The starting type of the CTM domain manager is determined.

The processing of the CTM domain manager continues.

KFCT70536-E

too many files are open in this system.

Description

The number of files that can be opened in the system exceeds the maximum value.

In the case of the daemon, an error message will be displayed and the processing continues.

In the case of the command, the processing will be interrupted.

Action

Check the maximum number of files that can be opened in the system.

KFCT70537-E

cannot get system resources. resource_code = aa....aa resource_value = bb....bb.

aa....aa: Resource name (RLIMIT_NOFILE: file descriptor)

bb....bb: Value that the user is trying to secure

Description

The process of acquiring the system resources has failed.

The daemon processing will be interrupted.

Action

Check the maximum number of system resources and the number of resources that you are trying to secure.

KFCT70538-E

ctmd with specified CTMID is on the other host.

Description

The CTM daemon with the specified CTM identifier is running on a different host.

The daemon processing will be interrupted.

Action

Confirm that the CTM daemon with the specified CTM identifier is running on the same host.

KFCT70539-I

now starting ctmregltd.

Description

The CTM regulator is being started.

The startup process of the CTM regulator continues.

KFCT70540-I

usage:ctmregltd [-h] [-CTMDomain domain_name] [-CTMID ctmid]

[-CTMEjbPort port_no] [-CTMMyHost host_name] [-CTMTimeOut time]

[-CTMAgent 0|1] [-CTMIDLConnect [0|1]] [-PRFID cprfid] [-CTMClientConnectCount count]

Description

This message describes the usage method of the CTM regulator.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT70542-I

ctmregltd is now online.

Description

The startup process of the CTM regulator is complete and online business can be started.

The processing of the CTM regulator continues.

KFCT70543-E

the error occurred while accessing domain manager information file.

Description

An error occurred while accessing the CTMSPOOL information file.

The processing of the command and the daemon will be interrupted.

Action

Confirm the following details:

An attempt to acquire the lock for the CTMSPOOL information file may have failed. Check whether a command is running for 10 or more seconds and whether a daemon is being started up for 10 or more seconds at the same time as the command or daemon that outputs this message.

The CTMSPOOL information file may not exist. Check whether the CTM domain manager is not started even once after installation.

Check whether a message was output before this message.

Check the above details, and then take actions as follows:

When a running command and a starting up daemon do not exist, restart the command or the daemon.

Start the CTM domain manager. See the message that was output before this message, and then remove the cause of the error.

KFCT70544-E

input number is invalid.

Description

The input number of the ctmdminfo command is invalid.

The processing of the command will be interrupted.

Action

Enter the valid number.

KFCT70545-I

now terminating ctmregltd

Description

The CTM regulator is being terminated.

The processing of the CTM regulator continues.

KFCT70546-I

ctmregltd stop

Description

The CTM regulator was stopped.

KFCT70547-W

ctmdmd is restarted, so -CTMMaxCTM value is ignored. now -CTMMaxCTM value is aa....aa

aa....aa: Value of the -CTMMaxCTM option used for startup now

Description

The CTM domain manager will be restarted.

In this case, the value specified in the -CTMMaxCTM option is disregarded and the value of the -CTMMaxCTM option used for the previous startup is used.

The processing of the CTM domain manager continues.

Action

To apply the value specified in the -CTMMaxCTM option, specify the -CTMForceStart option, and then re-execute the ctmdmstart command.

KFCT70548-E

cannot stop aa....aa. reason code=bb....bb.

aa....aa: Daemon

bb....bb: Reason for not being able to terminate the daemon

Description

The daemon cannot be stopped.

The daemon termination process will be interrupted.

Action

Check the operating state of the daemon. If the daemon is not stopped, stop the daemon again.

When checking the operating state of the daemon, check the cause described in bb....bb, and then take action. The following table lists the causes of the error described in bb....bb and the corresponding actions.

Table 19‒6: List of causes described in KFCT70548-E

Cause of error

Cause

Action

SHARED_MEMORY

The shared memory cannot be referenced.

Check whether the daemon is running or whether the file under the environment variable CTMSPOOL is deleted.

STATUS

The daemon is starting or terminating.

Check whether the daemon is starting or terminating.

DAEMON_STARTING

The daemon is starting.

Check whether the daemon is starting. After the daemon startup process finishes, re-execute the termination process.

DAEMON_TERMINATING

The daemon is terminating.

Check whether the daemon is terminating.

PRC_STARTING

The registration process is starting. This message is displayed only during the termination of the CTM daemon.

Check whether the registration process is starting. After the startup process of the registration process finishes, re-execute the termination process.

PRC_TERMINATING

The registration process is terminating. This message is displayed only during the termination of the CTM daemon.

Check whether the registration process is terminating. After the termination process of the registration process finishes, re-execute the termination process.

MAYBE_DOWN

The daemon that is being terminated may have been terminated forcibly or abnormally.

If aa....aa is ctmdmd, forcibly start the daemon when the CTM domain manager is started up next time.

SYSTEM_CALL

The command detected a system call error during daemon termination. The daemon may have terminated normally.

Check whether the daemon is terminated normally. If the daemon has abended, see the message, and then remove the cause of the error.

KFCT70549-I

there is no domain information.

Description

The CTM domain and the $CTMSPOOL information (in UNIX) or %CTMSPOOL% information (in Windows) are not registered in the local host.

The processing of the ctmdminfo command terminates.

KFCT70550-E

cannot delete domain information, because now ctmdmd is running.

Description

The CTM domain manager with the specified CTM domain name is running, therefore, the CTM domain and CTMSPOOL information cannot be deleted.

The processing of the ctmdminfo command terminates.

Action

Check the operating status of the CTM domain manager, and then re-execute the command.

KFCT70551-E

the error occurred while terminating process. name=aa....aa reason=bb....bb.

aa....aa: Executable format file name

When the corresponding process is in a Java application, "-" is output.

bb....bb: Reason for occurrence of error

Description

An error occurred while terminating the CTM daemon registration process.

The process of terminating the corresponding CTM daemon registration process will be interrupted.

Action

Check the executable format file name of the process in which the error occurred and the cause of the error. The reason for the error occurrence described in bb....bb and the corresponding actions are as follows:

TIMEOUT

The termination of the CTM daemon registration process has not finished within the allocated time.

The termination of the registration process is taking some time. If required, use the ctmstopprc command to terminate the registration process forcibly.

MAYBE_DOWN

The termination request cannot be executed for the CTM daemon registration process.

The registration process may have abended. Check whether the registration process has abended. If the registration process has abended, see the details such as the exception, and then remove the cause of the error.

KFCT70552-I

usage:ctmdminfo [-h] [-d]

Description

This message describes the usage method of the ctmdminfo command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT70553-E

the initialization of ctmregltd is failed. error_code1=aa....aa error_code2=bb....bb.

aa....aa: Maintenance information 1

bb....bb: Maintenance information 2

Description

An attempt to initialize the CTM regulator has failed.

The daemon processing will be interrupted.

Action

See the error message displayed before this message, and then take action. If you do not understand the troubleshooting method from the error message, acquire the value of error_code1 and error_code2, and then contact System Administrator.

KFCT70554-E

cannot stop ctmdmd, because ctmd is now running.

Description

The registered CTM daemon is running; therefore, the CTM domain manager cannot be terminated.

The processing of the command will be interrupted.

Action

Check the operating state of the registered CTM daemon, terminate the CTM daemon, and then re-execute the command.

KFCT70556-E

cannot entry this process, because of status.

Description

The CTM daemon where the process is to be registered is either running or being terminated; therefore, the process cannot be registered.

The daemon processing will be interrupted.

Action

If the CTM daemon where the process is to be registered is running, execute the command after the process becomes online. If the CTM daemon is terminated, restart the CTM daemon, and then execute the command.

KFCT70558-E

cannot get shared memory, because its size is too large. size = aa....aa.

aa....aa: Shared memory size that the user tried to acquire

Description

An attempt was made to acquire shared memory (aa....aa) exceeding the maximum value determined by the system.

The daemon processing will be interrupted.

Action

Use the formula for computing the shared memory size and adjust the shared memory size to be acquired or change the maximum value of the system.

KFCT70559-E

the error occurred while starting ctmd. process terminated.

Description

An error occurred while starting the CTM daemon.

The processing of the command will be interrupted.

Action

If another message is displayed before this message, see the displayed message, and then take action. If no other message is displayed, the CTM daemon may have abended. Acquire the file that exists under the environment variable CTMSPOOL, and then contact System Administrator.

KFCT70560-E

the error occurred while starting ctmdmd. process terminated.

Description

An error occurred while starting the CTM domain manager.

The processing of the command will be interrupted.

Action

If another message is displayed before this message, see the displayed message, and then take action. If no other message is displayed, the CTM domain manager may have abended. Acquire the file that exists under the environment variable CTMSPOOL, and then contact System Administrator.

KFCT70561-E

memory allocation failed.

Description

An attempt to acquire memory has failed.

The processing of the daemon and the command will be interrupted.

Action

Contact system administrator.

Terminate the unnecessary processes or increase the memory.

KFCT70566-W

an error occurred during the starting of aa....aa. pid=bb....bb

aa....aa: Process name

bb....bb: Process ID of the process that failed to start

Description

An attempt to auto-start or restart the system process (bb....bb) has failed.

When starting the CTM daemon, the processing of the CTM daemon terminates. When restarting the system process, the processing of the CTM daemon continues.

Action

Confirm that the command option file of the specified CTM regulator is valid, specify the correct file, and then restart the CTM daemon.

KFCT70567-W

an error occurred during the accessing of the option file for aa....aa.pid=bb....bb

aa....aa: Process name

bb....bb: Process ID of the process that failed to start

Description

An error occurred while accessing the command option file of the system process (bb....bb).

When starting the CTM daemon, the processing of the CTM daemon terminates. When restarting the system process, the processing of the CTM daemon continues.

Action

When starting the CTM daemon, confirm that the command option file of the specified CTM regulator is valid, and then restart the CTM daemon. If the CTM daemon is already running, check whether the file that exists under the environment variable CTMSPOOL is deleted.

KFCT70568-W

the specified option for aa....aa is invalid. pid=bb....bb

aa....aa: Process name

bb....bb: Process ID of the process that failed to start

Description

The contents of the command option file of the system process (bb....bb) are invalid.

When starting the CTM daemon, the processing of the CTM daemon terminates. When restarting the system process, the processing of the CTM daemon continues.

Action

When starting the CTM daemon, check the following details, and then restart the CTM daemon:

Are the contents of the command option file of the CTM regulator invalid?

You can use alphanumeric characters, spaces, hyphens (-), periods (.), and slants (/) in the command option file.

Is the specified command option file name invalid?

When restarting the system process, contact System Administrator.

KFCT70569-I

restart the system process. name=aa....aa.

aa....aa: Executable format file name of the process

Description

The abended system process will be restarted.

KFCT70570-E

cannot restart system process. name=aa....aa.

aa....aa: Executable format file name of the process

Description

An attempt to restart the system process has failed.

The processing of the CTM daemon continues.

Action

See details such as an error message displayed before this message, remove the cause of the error, and then restart the system process, if required. If no error message is output, contact System Administrator.

Furthermore, if the system process is restarted using direct startup, the system process is not restarted even if it has abended. If you want to restart the system process when it has abended, terminate the CTM daemon, and then restart the process.

KFCT70571-I

usage:ctmrasget { [-h] | [-p] [-s] [-CTMSpool spool_directory | -CTMDomain domain_name] [-PRFSpool spool_directory] dest_directory }

Description

This message describes the usage method of the ctmrasget command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT70572-I

Cosminexus Component Transaction Monitor: RAS completed collection of aa....aa

aa....aa: Information and message to be collected

Description

The information and messages of the ctmrasget command will be displayed.

KFCT70573-E

cannot create the process. process_name=aa....aa.

aa....aa: Process name (ctmd: CTM daemon, ctmdmd: CTM domain manager, or ctmregltd: CTM regulator)

Description

An attempt to generate the process has failed.

The startup process of each daemon terminates.

Action

Check the following details or restart after some time:

Are the system file resources insufficient?

Has the generation of child processes failed?

Is the memory insufficient?

KFCT70574-I

usage:ctmgetpid [-h] | -CTMDomain domain_name [-CTMID ctmid] [-CTMMyHost host_name] [-CTMGWID prc_id]

Description

This message describes the usage method of the ctmgetpid command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT70575-E

the error occurred while getting process ID.

Description

An error occurred while acquiring the process ID.

The processing of the command terminates.

Action

Confirm that the CTM daemon and CTM domain manager that are to be acquired are running or check whether the file that exists under the environment variable CTMSPOOL is deleted.

KFCT70576-I

now starting the application. prc_id=aa....aa name=bb....bb.

aa....aa: Process identifier

bb....bb: Executable format file name

If the program to be started is the ORB gateway, ctmregltd is output.

Description

The startup process of the ORB gateway will start.

The startup processing of the program continues.

KFCT70577-E

the error occurred while starting the application. prc_id=aa....aa name=bb....bb pid=cc....cc reason=dd....dd.

aa....aa: Process identifier

bb....bb: Executable format file name

If the program to be started is the ORB gateway, ctmregltd is output.

cc....cc: Process ID of the program

dd....dd: Reason for occurrence of error

Description

The processing of the command will be interrupted. However, even if this message is output, the startup processing of the program might continue.

To confirm that the program has started, see the message log and confirm that the KFCT70594-I message is output.

The following information is displayed in dd....dd.

SHM_LOCK_ERROR

An attempt to lock the access to the shared memory failed.

PRC_MAYBE_DOWN

An attempt to generate a process failed. Alternatively, termination of the process was detected.

NOT_ENOUGH_MEMORY

The memory is insufficient.

ENV_ERROR

The operation environment is not set up.

PRC_NUM_OVER

The number of registered processes exceeded the upper limit.

SAME_PRCID

A program having the same identifier has already been registered.

TIMEOUT

The program has not started within the allocated time.

CTMD_STARTING

The CTM daemon is being started.

CTMD_TERMINATING

The CTM daemon is being terminated.

CTMD_NOT_FOUND

The CTM daemon is not running.

INAVALID_SHM

The shared memory is invalid.

INTERNAL_ERROR

An error occurred in the internal processing.

ENV_ANALYZE

An error occurred during analysis of the user environment variable definition.

PRE_PROC

The processing prior to generating a process failed.

Action

Revise the command argument.

KFCT70578-I

the application is now online. prc_id= aa....aa name=bb....bb pid=cc....cc.

aa....aa: Process identifier

bb....bb: Executable format file name

If the program to be started is the ORB gateway, ctmregltd is output.

cc....cc: Process ID of the startup process

Description

The startup processing of the ORB gateway finished.

The processing of the program continues.

KFCT70580-I

now terminating the application. prc_id=aa....aa terminate type=bb....bb.

aa....aa: Process identifier

bb....bb: Termination type

Description

The termination processing of the ORB gateway has started.

The termination processing of the program continues.

The following contents are displayed in bb....bb.

NORMAL STOP

Normal termination

FORCE STOP

Forced termination

KFCT70581-E

the error occurred while terminating the application. prc_id=aa....aa pid=bb....bb reason=cc....cc.

aa....aa: Process identifier

bb....bb: Process ID of the program

If the process ID of the program cannot be determined, -1 is output.

cc....cc: Reason for occurrence of error

Description

An error occurred during termination processing of the ORB gateway.

The processing of the command will be interrupted. However, even if this message is output, the termination processing of the program might continue.

The following contents are displayed in cc....cc.

SHM_LOCK_ERROR

An attempt to lock the access to the shared memory failed.

PRC_MAYBE_DOWN

Abnormal termination of the program is detected.

NOT_ENOUGH_MEMORY

The memory is insufficient.

ENV_ERROR

The operation environment is not set up.

PRCID_NOT_FOUND

A program having the specified process identifier is not registered.

TIMEOUT

The program did not terminate within the allocated time.

CTMD_STARTING

The CTM daemon is performing the startup processing.

CTMD_TERMINATING

The CTM daemon is performing the termination processing.

CTMD_NOT_FOUND

The CTM daemon is not running.

INAVALID_SHM

The shared memory is invalid.

PRC_STARTING

The program having the specified process identifier is performing the startup processing.

PRC_TERMINATING

The program having the specified process identifier is performing the termination processing.

INTERNAL_ERROR

An error occurred in the internal processing.

Action

To confirm that the program has terminated, see the message log and confirm that the KFCT70596-I message is output.

KFCT70582-I

the application stop. prc_id=aa....aa pid=bb....bb.

aa....aa: Process type

bb....bb: Process ID of the program

Description

The termination processing of the ORB gateway finished.

The termination processing of the program will finish.

KFCT70589-E

the error occurred in lock control for shared memory access.

Description

An error occurred in the acquisition or release of lock when accessing the shared memory.

The processing will be interrupted.

Action

Confirm the following details, and then take action:

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

Is the file under the CTMSPOOL directory deleted and are the access permissions changed?

Terminate the CTM daemon and CTM domain manager forcibly, and then restart the process.

KFCT70593-I

the entry of process is completed. process_kind=aa....aa prc_id=bb....bb pid=cc....cc.

aa....aa: Process type (Reg: CTM regulator, or J2ee: J2EE server)

bb....bb: Application identifier

In the case of a J2EE server and CTM regulator, "-" is output.

cc....cc: Process ID of the startup process

Description

The process of registering the startup process (aa....aa) in the CTM daemon has finished.

The startup processing of the process continues.

KFCT70594-I

the process is ready for request. process_kind=aa....aa prc_id=bb....bb pid=cc....cc.

aa....aa: Process type (Reg: CTM regulator)

bb....bb: Process identifier

In the case of the CTM regulator, "-" is output.

In the case of the ORB gateway, the gateway identifier is output.

cc....cc: Process ID of the startup process

Description

The CTM daemon registration process waits for a request.

The startup processing of the process continues.

KFCT70596-I

the release of process is completed. process_kind=aa....aa prc_id=bb....bb pid=cc....cc.

aa....aa: Process type (Reg: CTM regulator, ORB gateway, or J2ee: J2EE server)

bb....bb: Process identifier

In the case of a J2EE server and CTM regulator, "-" is output.

In the case of the ORB gateway, the gateway identifier is output.

cc....cc: Process ID of the process for which the termination process has finished

Description

The termination process of the CTM daemon registration process has finished.

The processing of the registration process continues.

KFCT70601-E

execution of process is failed. name=aa....aa reason=bb....bb.

aa....aa: Executable format file name

bb....bb: Reason for occurrence of error

Description

An attempt to execute the startup process has failed.

The startup processing of the process will be interrupted.

The reason for the error occurrence describes the errno value of the system call execvp(2) provided in the operating environment.

Action

See the message KFCT75500-E displayed before this message or the operating environment-specific reasons for the occurrence of error, and then take action. Note that this message is not displayed if Windows is used.

KFCT70603-W

shared memory is invalid. initialize shared memory. reason=aa....aa. kind=bb....bb.

aa....aa: Reason for occurrence of error

bb....bb: Shared memory type (ctmd: shared memory for CTM daemon, or ctmdmd: shared memory for CTM domain manager)

Description

The shared memory is invalid. New shared memory will be created. The daemon startup process continues.

The following contents are described in aa....aa.

INVALID_VERSION

The version of shared memory is invalid.

CRITICAL_NG

The management information in the shared memory is destroyed.

KFCT70604-E

shared memory is invalid. process terminated. reason=aa....aa. kind=bb....bb.

aa....aa: Reason for occurrence of error

bb....bb: Shared memory type (ctmd: shared memory for CTM daemon, or ctmdmd: shared memory for CTM domain manager)

Description

The shared memory that you tried to reference is invalid.

The processing of the command or the daemon terminates.

Action

Check the following details for each reason for error occurrence described in aa....aa, and then take action:

In the case of INVALID_VERSION

Is the version of the CTM domain manager and the CTM daemon running currently, different from the version of the process that outputs this message?

The CTM domain manager and the CTM daemon are not running, but is the previously shared memory remaining during the abnormal or forced termination of a daemon in the previous process?

Is a version conflict detected when the previously shared memory is referenced while restarting the CTM domain manager?

In the case of 1. and 2., the version of the process that outputs this message and the version of the created shared memory are different, so the shared memory cannot be used. When using the shared memory, restart the CTM domain manager and the CTM daemon of the same version as that of the process that outputs this message.

In the case of 3., you cannot reuse the shared memory that you are trying to use. Specify the -CTMForceStart option or -CTMAutoForce option in the ctmdmstart command, and then start the CTM domain manager.

In the case of CRITICAL_NG

When the CTM daemon or the CTM domain manager is terminated abnormally or forcibly, you cannot reuse the shared memory that you are trying to use. Specify the -CTMForceStart option or -CTMAutoForce option in the ctmdmstart command, and then start the CTM domain manager.

KFCT70606-I

the creation of process is succeeded. prc_id=aa....aa program_name=bb....bb pid=cc....cc dir_id=dd....dd.

aa....aa: Process identifier

If the process does not have a process identifier, "-" is output.

bb....bb: Executable format file name

cc....cc: Process ID of the generated process

dd....dd: Current directory ID

If the process does not have a directory ID, "-" is output.

Description

An attempt to generate the process was successful.

The startup processing of the CTM daemon registration process continues.

KFCT70607-E

the error occurred while accessing environment definition file. CTMEnviron=aa....aa

aa....aa: User environment variable definition file name

Description

An error occurred while accessing the user environment variable definition file.

The processing of the command terminates.

Action

See the message KFCT75500-E displayed before this message, and then remove the cause of the error.

KFCT70608-E

the definition of environment is invalid. CTMEnviron=aa....aa line=bb....bb.

aa....aa: User environment variable definition file name

bb....bb: Line number with the analysis error

Description

The contents of the user environment variable definition file are invalid.

If a single definition is coded across multiple lines using the continuation symbol (\), the line number describing the first line of the definition with an error will be displayed.

The processing of the command terminates.

Action

Check the following details in the description of the user environment variable definition file:

Is there a line in which equal sign (=) is missing?

Is there a line with the equal sign (=) at the beginning or the end of the line?

Is there an environment variable name beginning with "CTM" or "ctm"?

Is there a line with only spaces and tabs?

If invalid, modify the contents of the user environment variable definition file.

KFCT70611-W

load library failed. library=aa....aa reason=bb....bb.

aa....aa: Library name that failed to load

bb....bb: Reason for the load failure

Description

An attempt to load the library (aa....aa) has failed.

The processing continues.

Action

Contact system administrator.

The System Administrator will reference the reason for the load failure described in bb....bb, and then take action. The reasons for the load failure described in bb....bb and the corresponding actions are as follows:

unsatisfied

The library symbol cannot be resolved.

The environment variable that specifies the library storage directory may be invalid or an invalid version of Cosminexus TPBroker may have been used. Modify the environment variable that specifies the library storage directory or install the correct version of Cosminexus TPBroker, and then re-execute the command. Revise the specified value of cpp.library.version.

security

The loading of the library is not permitted.

Contact maintenance personnel.

init

An attempt to initialize the library has failed.

Contact maintenance personnel.

KFCT70612-E

the fatal error occurred. so process is aborted. reason=aa....aa.

aa....aa: Reason for occurrence of error

Description

A fatal error occurred.

The process being executed will be interrupted.

The following contents are described in aa....aa.

SHM_LOCK_ERROR

An attempt to control the locking of the shared memory has failed.

Action

Confirm the following details, and then take action:

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

Is the file under the CTMSPOOL directory deleted and are the access permissions changed?

Terminate the CTM domain manager and the CTM daemon forcibly, and then restart the process.

KFCT70613-E

system process may be down. name=aa....aa pid=bb....bb end_status=cc....cc.

aa....aa: Executable format file name of the process

bb....bb: Process ID of the process for which abnormal termination is detected

cc....cc: End status

Description

An abended system process was detected.

The following contents are displayed in the termination state of cc....cc:

The displayed termination state

In the case of a system process that is started automatically when starting the CTM daemon

When the CTM daemon is online, the termination state of the process will be displayed. When the CTM daemon is running or being terminated (including forced termination), "*" will be displayed.

In the case of other system processes

"-" will be displayed.

If an automatically terminated process is a system process that is automatically started during the startup of the CTM daemon, re-execute the startup process. In other cases, the processing of the CTM daemon continues.

Action

Check whether the message KFCT70569-I is output after this message.

If the message KFCT70569-I is output, the applicable system process is restarted. If the message is not output, see details such as the error message displayed before this message, remove the cause of the error, and then restart, if required.

When the applicable system process is not restarted and if no error message is displayed, contact System Administrator.

KFCT70617-E

cannot get the connecting information from specified domain. domain_name=aa....aa ip_address=bb....bb reason=cc....cc.

aa....aa: Name of the CTM domain for which information acquisition failed

bb....bb: IP address of the CTM domain manager for which information acquisition failed. If this message is output for the ctmgetior command, * is output.

cc....cc: Reason for occurrence of error

Description

IOR information cannot be acquired from the CTM domain. If other CTM domains are specified, the system will continue to acquire IOR information for the next CTM domain.

Action

Check the causes for the error occurrence described in cc....cc, and then take action. The following table lists the reasons for the error occurrence described in cc....cc and the corresponding actions.

Table 19‒7: List of causes described in KFCT70617-E

Cause of error

Cause

Action

COMM_FAILURE

A failure occurred during connection to the relevant CTM domain manager.

See the CTM domain log of each CTM domain manager to investigate the failure in IOR information acquisition, and then remove the failure.

If the failure information is not output to the CTM domain log, a failure might have occurred during connection to the CTM domain manager. If necessary, forcibly terminate the relevant CTM domain manager, collect the data, and then restart the CTM domain manager.

GET_INFO_ERROR

An attempt to acquire IOR information from the relevant CTM domain failed.

See the CTM domain log of each CTM domain manager to investigate the failure in IOR information acquisition, and then remove the failure.

INVALID_VERSION

The relevant CTM domain manager does not have a function for acquiring IOR information.

Check the version of the relevant CTM domain manager.

Specify the CTM domain name of a CTM domain manager of CTM 01-02 or later.

TIMEOUT

IOR information acquisition processing has not finished within the allocated time.

See the CTM domain log of each CTM domain manager to investigate the failure in IOR information acquisition, and then remove the failure.

If the failure information is not output to the CTM domain log, a failure might have occurred during connection to the CTM domain manager. If necessary, forcibly terminate the relevant CTM domain manager, collect the data, and then restart the CTM domain manager.

STATUS

The CTM domain manager is being started or terminated.

If the CTM domain manager is being started, wait until it is online. If the CTM domain manger is being terminated, restart it as required.

INTERNAL_ERROR

An error occurred in the internal processing.

KFCT70618-W

there is no connecting information in specified domain. domain_name= aa....aa ip_address=bb....bb.

aa....aa: CTM domain name

bb....bb: IP address of the CTM domain manager

Description

The relevant CTM domain does not contain the IOR information that meets the specified conditions.

If other CTM domains are specified, the system will continue to acquire IOR information for the next CTM domain.

Action

Check whether the conditions specified with the ctmgetior command are satisfied. For example, check the following:

Check whether the CTM daemon, ORB gateway, and J2EE application are running in the relevant CTM domain.

Check whether -CTMIDLConnect 1 is specified for the ORB gateway.

If the -CTMInterfaceName option or -CTMLookupName is specified, check whether the corresponding EJB exists in the CTM node in which the ORB gateway (with -CTMIDLConnect 1 specified) is running. Note that the EJB must have the remote interface or INS registration name that matches the specified value (-CTMInterfaceName option or -CTMLookupName).

KFCT70619-E

there is no connecting information in the specified domains.

Description

IOR information that satisfies the specified conditions was not acquired.

The command will terminate without outputting an IOR file.

Action

For the CTM domains specified with the ctmgetior command, check the same items as for the KFCT70618-W message. If the check result indicates that the specified conditions have no problems in the operation environment, check for a failure in the CTM domain manager from which the IOR information is acquired. For details about failures that occurred in the CTM domain managers, see the standard error output or CTM domain log of the CTM domain manager.

KFCT70621-E

an error occurred during the acquiring of connecting information. reason=aa....aa

aa....aa: Reason for occurrence of error

Description

The IOR information acquisition processing in the CTM domain manager failed.

The IOR information acquisition processing will be interrupted.

Action

Check the causes for the error occurrence described in aa....aa, and then take action. The following table lists the reasons for the error occurrence described in aa....aa and the corresponding actions.

Table 19‒8: List of causes described in KFCT70621-E

Cause of error

Cause

Action

INVALID_DATA

The contents of the IOR information are invalid.

Terminate the CTM domain manager, CTM daemon, ORB gateway, and J2EE in the relevant CTM domain, and then restart them.

ACCESS_ERROR

A failure occurred during access to IOR information.

Make sure that no file was deleted from under the CTMSPOOL directory used by the relevant CTM domain manager. Also make sure that the access permissions were not changed.

NOT_ENOUGH_MEMORY

The memory is insufficient.

Terminate the unnecessary processes or increase the memory.

KFCT70622-W

an error occurred during the initialization of connecting information. reason=aa....aa

aa....aa: Reason for occurrence of error

Description

An attempt to initialize IOR information failed.

The processing of the CTM domain manager will be interrupted.

Action

Check the causes for the error occurrence described in aa....aa, and then take action. The following table lists the reasons for the error occurrence described in aa....aa and the corresponding actions.

Table 19‒9: List of causes described in KFCT70622-W

Cause of error

Cause

Action

ACCESS_ERROR

A failure occurred during access to IOR information.

Make sure that no file was deleted from under the CTMSPOOL directory used by the relevant CTM domain manager. Also make sure that the access permissions were not changed.

NOT_ENOUGH_MEMORY

The memory is insufficient.

Terminate the unnecessary processes or increase the memory.

KFCT70624-W

the error occurred while updating the connecting information. type=aa....aa reason=bb....bb.

aa....aa: Update type

bb....bb: Reason for occurrence of error

Description

An attempt to update the IOR information failed.

The processing of the daemon continues.

The following contents are displayed in aa....aa.

ADD_INFORMATION

Addition of IOR information

DELETE_INFORMATION

Deletion of IOR information

Action

Check the causes for the error occurrence described in bb....bb, and then take action. The following table lists the reasons for the error occurrence described in bb....bb and the corresponding actions.

Table 19‒10: List of causes described in KFCT70624-W

Cause of error

Cause

Action

INVALID_DATA

The contents of the IOR information are invalid.

Make sure that no file was deleted from under the CTMSPOOL directory used by the relevant CTM domain manager. Also make sure that the access permissions were not changed.

ACCESS_ERROR

A failure occurred during access to IOR information.

Make sure that no file was deleted from under the CTMSPOOL directory used by the relevant CTM domain manager. Also make sure that the access permissions were not changed.

NOT_ENOUGH_MEMORY

The memory is insufficient.

Terminate the unnecessary processes or increase the memory.

KFCT70634-E

timeout occurred.

Description

When executing the ctmstart command, the CTM daemon startup process was not terminated even after the lapse of the timeout period specified in the -CTMStartTimeOut option.

The processing of the command will be interrupted.

Action

Revise the value specified in the -CTMStartTimeOut option used when executing the command.

Modify the specified timeout value, and then re-execute the command.

KFCT70638-I

ctmgetior [-h] | [ { -CTMDomain domain_name[,domain_name...] | -CTMDomainAll } ] [ { -CTMID ctmid[,ctmid...] | -CTMIDAll } ] [-CTMHost host_name[,host_name...] ] [-CTMMyHost host_name] [-CTMInterfaceName interface_name[,interface_name...] ] [-CTMLookupName lookup_name[,lookup_name...] ] [-CTMOutPath directory]

Description

This message describes the usage method of the ctmgetior command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it. If the specified option is invalid, modify the specified option, and then re-execute the command.

KFCT70639-E

the error occurred while accessing file. name=aa....aa reason=bb....bb.

aa....aa: File name

bb....bb: Reason for occurrence of error

Description

The error occurred while accessing file.

Action

Check the causes for the error occurrence described in bb....bb, and then take action. The following table lists the reasons for the error occurrence described in bb....bb and the corresponding actions.

Table 19‒11: List of causes described in KFCT70639-E

Cause of error

Cause

Action

SYSTEM_CALL

A system call error occurred.

See the KFCT75500-E message displayed before this message, and then remove the cause of the failure.

PATH_LENGTH

The file name is too long.

Revise the value specified for the -CTMOutPath option.

KFCT70641-W

cannot terminate ctmd, because shared memory has been broken. error_code=aa....aa.

aa....aa: Maintenance information

Description

Some of the management information in the shared memory is destroyed because the CTM domain manager was terminated forcibly or abnormally.

The previously managed CTM daemon cannot be terminated forcibly. The startup process of the CTM domain manager continues.

Action

Check whether a previously started CTM daemon exists in the CTM domain specified in the CTM domain manager startup command.

If a previously started CTM daemon is found in the CTM domain specified with the ctmdmstart command, directly terminate that CTM daemon.

KFCT70643-I

ctmdmd determined restart mode. mode= aa....aa.

aa....aa: Inheritance status of the previous system state

Description

This message describes whether the CTM domain manager was started with the previous system state inherited or the CTM domain manager was started in the initial state since the system state cannot be inherited during automatic forced startup of the CTM domain manager. The startup process of the CTM domain manager continues.

The following contents are displayed in aa....aa:

REUSE

The management information is inherited, so the CTM domain manager will start with the system state prior to the previous termination recovered.

INITIALIZE

The management information is not inherited, so the CTM domain manager will start in the initial state.

KFCT70648-I

now starting ctmtscgwd.

Description

The OTM gateway is being started.

The startup process of the OTM gateway continues.

KFCT70649-I

usage:ctmtscgwd [-h] [-CTMDomain domain_name] [-CTMID ctmid] [-CTMMyHost host_name] [-CTMPort port_no] [-CTMTPool] [-CTMClientConnectCount count]

Description

This message describes the usage method of the OTM gateway.

This error message is displayed when the command format is invalid or when the -h option is specified.

If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT70650-I

ctmtscgwd is now online.

Description

The startup process of the OTM gateway has finished and online business can be started.

The processing of the OTM gateway continues.

KFCT70651-I

now terminating ctmtscgwd.

Description

The OTM gateway is being terminated.

The processing of the OTM gateway continues.

KFCT70652-I

ctmtscgwd stop.

Description

The OTM gateway was stopped.

KFCT70653-E

the initialization of ctmtscgwd is failed. error_code1=aa....aa error_code2=bb....bb.

aa....aa: Maintenance information 1

bb....bb: Maintenance information 2

Description

An attempt to initialize the OTM gateway has failed.

The processing of the OTM gateway will be interrupted.

Action

See the message displayed before this message, and then take action. If you do not understand the troubleshooting method from the error message, acquire the value of error_code1 (aa....aa) and error_code2 (bb....bb), and then contact System Administrator.

KFCT70654-I

usage:ctmstartgw [-h] -CTMGWID prc_id [-CTMDomain domain_name] [-CTMID ctmid] [-CTMMyHost host_name] [-CTMEjbPort port_no] [-CTMEnviron file] [-CTMTimeOut time] [-CTMAgent 0|1] [-CTMIDLConnect [0|1]] [-CTMClientConnectCount count]

Description

This message describes the usage method of the ctmstartgw command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

KFCT70655-I

usage:ctmstopgw [-h] -CTMGWID prc_id [-CTMDomain domain_name] [-CTMID ctmid] [-CTMMyHost host_name] [-CTMForce [-CTMDebugInfo] ]

Description

This message describes the usage method of the ctmstopgw command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

KFCT70700-I

now initializing CTM for J2EE server.

Description

The CTM functionality in the J2EE server is being initialized.

The initialization process of the CTM functionality continues.

KFCT70701-I

the initialization of CTM is completed.

Description

The initialization of the CTM functionality for the J2EE server has finished.

The processing continues.

KFCT70702-E

the initialization of CTM is failed.

Description

An attempt to initialize the CTM functionality for the J2EE server has failed.

The startup process of the J2EE server continues, but the CTM functionality cannot be used.

Action

Take action based on the previous message, and then restart the J2EE server.

KFCT70703-I

now finalizing CTM for J2EE server.

Description

The CTM functionality for the J2EE server is being terminated.

The termination process of the CTM functionality continues.

KFCT70704-I

the finalization of CTM is completed.

Description

The termination process of the CTM functionality for the J2EE server has finished.

The processing continues.

KFCT70705-E

the finalization of CTM is failed.

Description

An attempt to terminate the CTM functionality for the J2EE server has failed.

The termination process of the J2EE server continues.

Action

Take action based on the previous message before you next start the J2EE server.

KFCT70706-E

the property is invalid. property. name=aa....aa inter=bb....bb.

aa....aa: Invalid property name

bb....bb: Maintenance information

Description

The property (aa....aa) is invalid.

Action

Revise the property definition, and then restart the J2EE server.

KFCT70710-E

the error occurred while initializing CTM for J2EE server. kind=aa....aa detail=bb....bb inter=cc....cc.

aa....aa: Error type

bb....bb: Maintenance information 1

cc....cc: Maintenance information 2

Description

An error occurred while initializing the CTM functionality for the J2EE server

The CTM functionality cannot be used.

Action

Take action based on the error type described in aa....aa, and then restart the J2EE server. The following table lists the types of errors described in aa....aa and the corresponding actions.

Table 19‒12: List of error types described in KFCT70710-E

Cause of error

Cause

Action

LOAD_LIBRARY

An attempt to read the library has failed.

Check whether the library path environment variables are set correctly and, if necessary, revise them.

ENVIRON

An attempt to acquire the environment variables has failed.

Check whether the environment variables CTMDIR and CTMSPOOL are set correctly and, if necessary, revise them.

COMMUNICATION

An error occurred in the communication process.

Check whether the Cosminexus TPBroker environment and properties are set correctly and, if necessary, revise them.

SH_MEM

An attempt to access shared memory has failed.

Check whether the environment variables CTMDIR and CTMSPOOL are set correctly and, if necessary, revise them.

In addition, check whether the CTMSPOOL directory exists, whether the library or directory under CTMSPOOL is deleted or changed, and whether the permissions have been changed and, if necessary, revise them.

MEMORY

The memory is insufficient.

Terminate the unnecessary processes.

Others

An error occurred in the internal processing.

Acquire kind (aa....aa), detail (bb....bb), and inter (cc....cc), and then contact maintenance personnel.

KFCT70711-E

the error occurred while finalizing CTM for J2EE server. kind=aa....aa detail=bb....bb inter=cc....cc.

aa....aa: Error type

bb....bb: Maintenance information 1

cc....cc: Maintenance information 2

Description

An error occurred in the termination process of the CTM functionality for the J2EE server.

The termination process of CTM will be interrupted, but the process of stopping the J2EE server continues.

Action

Take action based on the error type described in aa....aa, and then restart the J2EE server. The error type described in aa....aa and the corresponding actions are as follows:

NOT_INITIALIZED

The initialization of CTM is not complete. Check whether an error occurred during the CTM initialization process.

If an error occurred during the initialization process, remove the error.

In cases other than above

An error occurred in the internal processing.

Acquire kind (aa....aa), detail (bb....bb), and inter (cc....cc), and then contact maintenance personnel.

KFCT70712-E

Performance trace is unavailable due to failure of initialization. (reason=aa....aa)

aa....aa: Reason code

Description

An attempt to initialize the PRF trace has failed; therefore, the PRF trace cannot be used.

The CTM functionality cannot be used.

Action

Take action as per the reason code described in aa....aa, and then restart the J2EE server. The following table lists the reason codes described in aa....aa and the corresponding actions.

Table 19‒13: List of reason codes displayed in KFCT70712-E

Reason code

Cause

Action

-1

The environment variable PRFSPOOL is not set.

Confirm that the environment variable PRFSPOOL is set.

-2

An error occurred during startup processing of the PRF trace service of the process.

The PRF demon may not have been invoked.

Confirm that the PRF demon is invoked.

-3

An error such as a system call error occurred during startup processing of the PRF trace service of the process.

See the log file present below setup-directory-of-environment-variable-PRFSPOOL\log\PRF-identifier (in Windows) or $PRFSPOOL/log/PRF-identifier (in UNIX).

Check the Cosminexus Performance Tracer messages, confirm the cause of the error, and then take action.

KFCT70713-E

cannot entry J2EE server. reason=aa....aa detail=bb....bb.

aa....aa: Reason

bb....bb: Maintenance information

Description

The J2EE process cannot be registered.

The registration process of the J2EE server will be interrupted.

Action

Take action based on the reason described in aa....aa, and then restart the J2EE server. The following table lists the reasons described in aa....aa and the corresponding actions.

Table 19‒14: List of reasons described in KFCT70713-E

Cause of error

Cause

Action

STARTING

The CTM daemon is starting.

Start the J2EE server when the CTM daemon is online.

STOPPING

The CTM daemon is being stopping.

Start the J2EE server when the CTM daemon is online.

OVER

The number of processes that can be registered in the CTM daemon is exceeded.

Specify an appropriate value in -CTMEntryCount of the ctmstart command, restart the CTM daemon, and then restart the J2EE server.

HOST

The host is different from the CTM daemon.

Check whether the CTM daemon is running on the same machine, whether the -CTMMyHost option of the ctmstart command and the ejbserver.ctm.CTMMyHost property of the J2EE server are invalid and if necessary, revise them.

SYSTEM

A shared memory operation or an exclusive control has failed.

Check whether a file or directory under CTMSPOOL is deleted or changed or whether the permissions are changed and, if necessary, revise them.

MEMORY

The memory is insufficient.

Terminate the unnecessary processes.

Others

An error occurred in the internal processing.

Acquire reason (aa....aa) and detail (bb....bb), and then contact maintenance personnel.

KFCT70714-E

cannot clear J2EE server. reason=aa....aa detail=bb....bb.

aa....aa: Reason

bb....bb: Maintenance information

Description

An attempt to un-register a J2EE server has failed.

The process of un-registering the J2EE server will be interrupted. Also, when this message is displayed, the CTM daemon may not be stopped normally.

Action

Take action based on the reason described in aa....aa, and then restart the J2EE server. The following table lists the reasons described in aa....aa and the corresponding actions.

Table 19‒15: List of reasons described in KFCT70714-E

Cause of error

Cause

Action

STARTING

The CTM daemon is starting.

Stop the J2EE server when the CTM daemon is online.

STOPPING

The CTM daemon is being stopping.

Stop the J2EE server when the CTM daemon is online.

MEMORY

The memory is insufficient.

Terminate the unnecessary processes.

Others

An error occurred in the internal processing.

Acquire reason (aa....aa) and detail (bb....bb), and then contact maintenance personnel.

KFCT70715-E

cannot find ctmd. domain=aa....aa ctmid=bb....bb.

aa....aa: CTM domain name of the target CTM daemon

bb....bb: CTMID of the target CTM daemon

Description

The CTM daemon cannot be found.

The initialization or termination process of the CTM functionality for the J2EE server will be interrupted.

Action

Take action depending on the state in which the error occurred.

When starting the J2EE server

Confirm the following details, and then take action:

Is the CTM daemon running?

Is osagent running?

Is the environment variable OSAGENT_PORT invalid?

Is the property (ejbserver.ctm.CTMDomain, ejbserver.ctm.CTMID, ejbserver.ctm.CTMMyHost) corresponding to the CTM for the J2EE server invalid?

When stopping the J2EE server

Confirm the following details, and then take action:

Is the CTM daemon stopped forcibly?

Is the CTM daemon abended?

KFCT70716-E

J2EE server may be down. name=aa....aa pid=bb....bb.

aa....aa: Server name of the J2EE server with termination detected

bb....bb: Process ID of the J2EE server with termination detected

Description

The stopping of a J2EE sever was detected.

This message is displayed if a registered J2EE server is not stopped normally. If the CTM daemon is online, the processing of the CTM daemon continues.

Action

Check whether a J2EE server with the output server name and process ID is abended.

If the J2EE server is abended, check the reason, remove the cause of the error, and then restart the server.

KFCT71000-E

memory allocation error. size : aa....aa

aa....aa: Secured memory size

Description

An attempt to acquire memory has failed.

The processing continues.

Action

Contact system administrator.

Terminate the unnecessary processes or increase the memory.

KFCT71001-E

can't start thread. maintenance code : aa....aa

aa....aa: Maintenance code

Description

The thread cannot be started.

The processing continues.

Action

Confirm the following details, and then take action:

Are the specified values of the -CTMMaxCTM option, the CTMClientConnectCount option, and the -CTMServerConnectCount option invalid?

Specify an appropriate value in the -CTMMaxCTM option, the -CTMClientConnectCount option, and the -CTMServerConnectCount option

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

KFCT71003-W

option error:aa....aa

aa....aa: Option name

Description

An attempt to acquire the option has failed.

The default value will be set and the processing continues.

KFCT71004-E

invalid option value:aa....aa

aa....aa: Option name

Description

The specified value of the option is invalid.

Action

Check the specified value of the option

KFCT71005-W

failed in initializing communication module. reason code : aa....aa

aa....aa: Reason code for the initialization failure

Description

An attempt to initialize the communication module has failed.

The processing continues.

The following reason codes are displayed in aa....aa.

Table 19‒16: List of reason codes described in KFCT71005-W

Reason code

Cause of error

1

Memory is insufficient.

2

An exception of CORBA was caught.

3

An unexpected exception was caught.

4

An attempt to initialize the lock area has failed.

5

An attempt to secure the lock has failed.

6

An attempt to release the lock has failed.

7

The communication data is invalid.

8

The communication data that cannot be processed was received.

9

An unexpected error occurred.

KFCT71051-W

communication manager not found. communication manager name : aa....aa host name :bb....bb maintenance code1 : cc....cc code2 : dd....dd

aa....aa: Communication management object name

bb....bb: Host name

If the search for the communication management object is not executed on a specific host, "********" is displayed.

cc....cc: Maintenance code

dd....dd: Maintenance code

Description

The communication management object was not found.

The processing continues, but the connection cannot be established.

Action

Confirm the following details, and then take action:

Is osagent abended?

Restart osagent.

Is osagent overloaded?

Terminate the unnecessary processes.

Are the environment variables 'OSAGENT_PORT', 'OSAGENT_ADDR', and 'OSAGENT_ADDR_FILE' and the ORB option invalid?

Specify valid environment variables OSAGENT_PORT, OSAGENT_ADDR, and OSAGENT_ADDR_FILE and a valid ORB option.

Have the CTM daemon or CTM domain manager abended?

Restart the CTM daemon or CTM domain manager.

Is the specified CTMID and CTM domain name invalid?

Specify a valid CTMID and CTM domain name.

If this message is displayed continuously even after taking action, execute the osfind command and communicate the result to maintenance personnel.

KFCT71052-W

convert an object reference to string/convert string to an object reference error for CORBA object. maintenance code : aa....aa

aa....aa: Maintenance code

Description

An attempt to convert a CORBA object to a string or to restore the object has failed.

The processing continues, but communication is not possible.

Action

Confirm the following details, and then take action:

Are the specified values of the -CTMMaxCTM option, the CTMClientConnectCount option, and the -CTMServerConnectCount option invalid?

Specify an appropriate value in the -CTMMaxCTM option, the -CTMClientConnectCount option, and the -CTMServerConnectCount option

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

Is the network interface abended?

Change the network interface settings so that communication is possible.

Is a process with an object (CTM daemon or CTM domain manager) abended?

Restart the process as defined in CTM.

Is a process with an object been restarted on a different port?

Specify the -CTMPort option for the process.

KFCT71053-E

failed in initializing communication module. maintenance code1 : aa....aa code2 : bb....bb

aa....aa: Maintenance code1

bb....bb: Maintenance code2

Description

An attempt to initialize the communication module has failed.

The processing continues.

Action

Confirm the following details, and then take action:

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

Is the specified value of the -CTMPort option being used in other processes?

Change the specified value of the -CTMPort option to a value that is not used in other processes.

KFCT71100-W

request of communication manager timeout. communication manager name : aa....aa timeout : bb....bb

aa....aa: Communication management object name

bb....bb: Timeout value

Description

The invocation of the communication management object has timed out.

The processing continues.

Action

Confirm the following details:

Is the process with the communication management object over loaded?

Is the connection physically disconnected?

KFCT71101-W

can't register communication object : aa....aa,bb....bb

aa....aa: Communication management object name

bb....bb: Communication object name

Description

The communication object cannot be registered.

The processing continues, but a message cannot be sent to that communication object.

Action

Check whether the memory is insufficient.

If the memory is insufficient, terminate the unnecessary processes or increase the memory.

KFCT71102-W

can't register communication object : aa....aa

aa....aa: Communication management object name

Description

The communication object cannot be registered.

The processing continues, but a message cannot be sent to that communication object.

Action

Confirm the following details, and then take action:

Are there too many communication objects to be registered?

Reduce the number of J2EE servers connected to one CTM daemon.

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

KFCT71103-W

communication object not registered : aa....aa,bb....bb

aa....aa: Communication management object name

bb....bb: Communication object name

Description

The communication object cannot be registered.

The processing continues, but a message cannot be sent to that communication object.

Action

Check the message KFCT71101-W or KFCT71102-W to confirm whether an attempt to register the communication object has failed, and then take action.

KFCT71150-W

cannot open a new connection for a thread. maintenance code1 : aa....aa

aa....aa: Maintenance code

Description

An attempt to establish connection has failed.

The processing continues, but the request cannot be sent.

Action

Confirm the following details, and then take action:

Are the specified values of the -CTMMaxCTM option, the CTMClientConnectCount option, and the -CTMServerConnectCount option invalid?

Specify an appropriate value in the -CTMMaxCTM option, the -CTMClientConnectCount option, and the -CTMServerConnectCount option

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

Is the network interface abended?

Change the network interface settings so that communication is possible.

KFCT71151-W

static connection request timeout. timeout : aa....aa

aa....aa: Timeout value

Description

The request timed out.

The processing continues.

Action

Confirm the following details:

Is the send destination process overloaded?

Is the processing of the request time-consuming?

KFCT71152-W

static connection request failure. maintenance code : aa....aa

aa....aa: Maintenance code

Description

An attempt to process the request has failed.

The processing continues, but the request processing result cannot be acquired.

Action

Confirm the following details, and then take action:

Is the process abended?

Restart the process as defined in CTM.

Are the specified values of the -CTMMaxCTM option, the CTMClientConnectCount option, and the -CTMServerConnectCount option invalid?

Specify an appropriate value in the -CTMMaxCTM option, the -CTMClientConnectCount option, and the -CTMServerConnectCount option

KFCT71153-W

cannot narrow an object reference to a sub-type. maintenance code : aa....aa

aa....aa: Maintenance code

Description

An attempt to convert the object has failed.

The processing continues, but the request cannot be sent.

Action

Check whether the process has not aborted. After checked, restart the process as defined in CTM.

KFCT71200-W

dynamic connection request failure. maintenance code : aa....aa

aa....aa: Maintenance code

Description

An attempt to process the request has failed.

The processing continues, but the request processing result cannot be acquired.

Action

Confirm the following details, and then take action:

Is the process abended?

Restart the process as defined in CTM.

Are the specified values of the -CTMMaxCTM option, the CTMClientConnectCount option, and the -CTMServerConnectCount option invalid?

Specify an appropriate value in the -CTMMaxCTM option, the -CTMClientConnectCount option, and the -CTMServerConnectCount option

KFCT71201-W

cannot open a new connection for inter-ctmd. maintenance code1 : aa....aa code2 : bb....bb

aa....aa: Maintenance code1

bb....bb: Maintenance code2

Description

An attempt to establish a connection between the CTM daemons has failed.

The processing continues, but a message cannot be sent.

Action

Confirm the following details, and then take action:

Are the specified values of the -CTMMaxCTM option, the CTMClientConnectCount option, and the -CTMServerConnectCount option invalid?

Specify an appropriate value in the -CTMMaxCTM option, the -CTMClientConnectCount option, and the -CTMServerConnectCount option

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

Is the network interface abended?

Change the network interface settings so that communication is possible.

Are the settings for the interlinking of multiple osagent (including between networks) invalid?

Specify valid settings for the interlinking of multiple osagent (including between networks). For details, see the Borland(R) Enterprise Server VisiBroker(R) Developers Guide.

KFCT71202-W

inter-ctmd receiver not found : aa....aa

aa....aa: Message receiving object name

Description

The message receiving objects between the CTM daemons cannot be found.

The processing continues.

KFCT71203-W

can't register inter-ctmd receiver : aa....aa

aa....aa: Message receiving object name

Description

The message receiving objects between the CTM daemons cannot be registered.

The processing continues.

Action

Confirm the following details, and then take action:

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

Is the shared memory insufficient?

Increase the specified value of the -CTMMaxCTM option.

KFCT71204-W

can't remove inter-ctmd receiver : aa....aa

aa....aa: Message receiving object name

Description

The message receiving objects between the CTM daemons cannot be removed.

The processing continues.

KFCT71250-W

shared memory allocation error. maintenance code1: aa....aa code2: bb....bb

aa....aa: Maintenance code1

bb....bb: Maintenance code2

Description

The shared memory is insufficient.

The processing continues, but the information related to communication between the CTM daemons is insufficient.

Action

Check the value specified in the -CTMMaxCTM option. After checked, increase the specified value of the -CTMMaxCTM option.

KFCT71251-E

UDP initialization error. port : aa....aa

aa....aa: Port number

Description

An attempt to initialize the UDP has failed.

The processing continues, but the information related to communication between the CTM daemons cannot be sent.

Action

Confirm the following details, and then take action:

Is the specified port number already being used?

Change the specified value of the CTMPort option.

Are the specified values of the -CTMMaxCTM option, the CTMClientConnectCount option, and the -CTMServerConnectCount option invalid?

Specify an appropriate value in the -CTMMaxCTM option, the -CTMClientConnectCount option, and the -CTMServerConnectCount option

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

KFCT71252-W

UDP receive error. maintenance code : aa....aa

aa....aa: Maintenance code

Description

An attempt to receive UDP has failed.

The processing continues, but the information related to communication between the CTM daemons cannot be received.

Action

Check whether the memory is insufficient.

If the memory is insufficient, terminate the unnecessary processes or increase the memory.

KFCT71253-W

UDP send Error. maintenance code : aa....aa address : bb....bb port : cc....cc

aa....aa: Maintenance code

bb....bb: Send destination IP address (broadcast address)

cc....cc: Send destination port number

Description

An attempt to send UDP has failed.

The processing continues, but the information related to communication between the CTM daemons cannot be sent.

Action

Confirm the following details, and then take action:

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

Is the network interface abended?

Change the network interface settings so that communication is possible.

KFCT71255-W

UDP data processing error : method aa....aa

aa....aa: Method name

Description

An attempt to process the UDP communication data has failed.

The processing continues.

Action

Check whether the memory is insufficient.

If the memory is insufficient, terminate the unnecessary processes or increase the memory.

KFCT71256-W

UDP from other domain : aa....aa

aa....aa: CTM domain name

Description

The UDP data of another CTM domain was received.

The data will be destroyed and the processing continues.

Action

Check whether a CTM domain manager of another CTM domain is running with the same port number. If the CTM domain manager is running with the same port number, start the CTM domain manager with a different port number for each CTM domain.

KFCT71257-E

the same CTMID was detected. CTMID: aa....aa ipaddr:bb....bb

aa....aa: CTM identifier

bb....bb: IP address of the node started by the CTM identifier

Description

The same CTM identifier is detected.

Action

The CTM identifier must be unique to the CTM domain.

KFCT71300-W

read/write lock error

Description

An attempted Read lock or Write lock has failed.

The processing continues.

KFCT71352-I

usage:ctmridinfo [-h] | [-CTMDomain domain_name] [-CTMHost host_name] [-CTMMyHost host_name]

Description

This message describes the usage method of the ctmridinfo command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it. If the specified option is invalid, modify the specified option, and then re-execute the command.

KFCT71353-E

domain information not found. maintenance code1 : aa....aa code2 : bb....bb code3 : cc....cc

aa....aa: Maintenance information 1

bb....bb: Maintenance information 2

cc....cc: Maintenance information 3

Description

This message is displayed when the CTM domain information is not found in the specified CTM domain manager.

The process to acquire the CTM domain information will be interrupted.

Action

Confirm the following details, and then take action:

Is the specified value of the option invalid?

Specify a valid value for the option.

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

Is there a CTM daemon connected to the specified CTM domain manager?

Start a CTM daemon, connected to the specified CTM domain manager.

KFCT71357-E

communication manager request failure. maintenance code1 : aa....aa code2 : bb....bb

aa....aa: Maintenance information 1

bb....bb: Maintenance information 2

Description

An attempt to process the requests for the communication management object has failed.

The process to acquire the CTM domain information will be interrupted.

Action

Confirm the following details, and then take action:

Is the CTM domain manager abended?

Start the CTM domain manager.

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

Is the network interface abended?

Change the network interface settings so that communication is possible.

KFCT71361-E

convert string to an object reference error for Naming Context. maintenance code : aa....aa

aa....aa: Maintenance code

Description

An attempt to restore the CORBA Naming Context string has failed.

The CORBA Naming Context cannot be used, so the processing will be interrupted.

Action

Confirm the following details, and then take action:

Is the specified value of the -CTMINSRef option invalid?

Specify an appropriate value in the -CTMINSRef option.

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

KFCT71362-E

Naming Service not found. maintenance code : aa....aa

aa....aa: Maintenance code

Description

The CORBA Naming Service cannot be found.

The CORBA Naming Context cannot be used, so the processing will be interrupted.

Action

Confirm the following details, and then take action:

Is the specified value of the -CTMINSRef option invalid?

Specify an appropriate value in the -CTMINSRef option.

Is the CORBA Naming Service abended?

Restart the CORBA Naming Service, and then restart the CTM daemon.

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

KFCT71363-E

failed in initializing communication with Naming Service. maintenance code : aa....aa

aa....aa: Maintenance code

Description

An attempt to initialize the communication with the CORBA Naming Service has failed.

The CORBA Naming Context cannot be used, so the processing will be interrupted.

Action

Confirm the following details, and then take action:

Is the specified value of the -CTMINSRef option invalid?

Specify an appropriate value in the -CTMINSRef option.

Is the naming context or object of the CORBA Naming Service changed?

Restart the CORBA Naming Service, and then restart the CTM daemon.

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

KFCT71364-W

timeout occurred in communication with Naming Service. timeout : aa....aa

aa....aa: Timeout value

Description

A timeout occurred in the communication with the CORBA Naming Service.

The processing continues.

Action

Check whether the CORBA Naming Service is overloaded.

KFCT71365-E

timeout occurred in communication with Naming Service. timeout : aa....aa

aa....aa: Timeout value

Description

A timeout occurred in the communication with the CORBA Naming Service.

The processing continues, but the CORBA Naming Service cannot be used.

Action

Check whether the CORBA Naming Service is overloaded.

Restart the CORBA Naming Service, and then restart the CTM daemon.

KFCT71366-E

request to Naming Service failure. maintenance code : aa....aa

aa....aa: Maintenance code

Description

An attempt to process the CORBA Naming Service has failed.

The processing continues, but the CORBA Naming Service cannot be used.

Action

Confirm the following details, and then take action:

Is the CORBA Naming Service abended?

Restart the CORBA Naming Service, and then restart the CTM daemon.

Is the naming context or object of the CORBA Naming Service changed?

Restart the CORBA Naming Service, and then restart the CTM daemon.

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

KFCT71403-W

cannot get System Property. property name : ejbserver.client.ctm.RequestPriority maintenance code: aa....aa default value is used:bb....bb.

aa....aa: Exception occurred

bb....bb: Default value

Description

An exception occurred while analyzing the ejbserver.client.ctm.RequestPriority property.

The default value will be used and the processing continues.

Action

Take action based on the exception (aa....aa) that has occurred.

SecurityException

Check the security manager policy.

NullPointerException

Contact maintenance personnel.

IllegalArgumentException

Contact maintenance personnel.

KFCT71404-W

invalid property value is specified. ejbserver.client.ctm.RequestPriority=aa....aa. default value is used:bb....bb.

aa....aa: Specified property value

bb....bb: Default value

Description

An invalid value was specified in ejbserver.client.ctm.RequestPriority.

The default value will be used and the processing continues.

Action

Specify a valid property value.

KFCT73002-E

prf tracing service cannot be started. ID:aa....aa reason code=bb....bb-cc....cc

aa....aa: PRF identifier

bb....bb: Reason code

cc....cc: Internal system code

Description

An error occurred when starting the PRF trace service.

The PRF daemon terminates.

Action

Based on the list of reason codes described in the following table, investigate the causes, remove the cause of the error, and then restart the PRF daemon.

Table 19‒17: List of reason codes described in KFCT73002-E

Reason code

Cause

101

Memory is insufficient.

102

Memory is insufficient.

103

An I/O error occurred when verifying the file or when creating a new file.

104

The new message queue ID in the msgget system call was not allocated. Check the usage status with the ipcs command. If an unnecessary message queue exists, the queue needs to be deleted with the ipcrm command.

106

The directory specified in the environment variable PRFSPOOL may not have been created correctly.

112

The specified PRF trace service is already running. Alternatively, the PRF trace service has stopped but a new PRF trace service cannot start because the running process is collecting the trace.

114

The shared memory used in the PRF trace service is corrupted.

115

The address of the shared memory used in the PRF trace service cannot be acquired.

401

An error occurred while opening an internal control file of the PRF trace service.

402

An internal control file of the PRF trace service is corrupted.

403

An error occurred in an internal control file of the PRF trace service. The directory specified in the environment variable PRFSPOOL may not have been created correctly.

404

The specified trace file creation directory is invalid.

502

An error occurred during creation of the necessary environment to control the PRF tracing service.

1601

An error occurred in the system call.

KFCT73003-E

prf tracing service cannot be continued. ID:aa....aa reason code=bb....bb-cc....cc

aa....aa: PRF identifier

bb....bb: Reason code

cc....cc: Internal system code

Description

A failure occurred while acquiring the PRF trace.

The PRF daemon terminates.

Action

Based on the list of reason codes described in the following table, investigate the causes, remove the cause of the error, and then restart the PRF daemon.

Table 19‒18: List of reason codes described in KFCT73003-E

Reason code

Cause

101

Memory is insufficient.

103

An I/O error occurred in the trace file.

104

The new message queue ID in the msgget system call was not allocated. Check the usage status with the ipcs command. If an unnecessary message queue exists, the queue needs to be deleted with the ipcrm command.

1601

An error occurred in the system call.

KFCT73004-W

failure to initialize for prf tracing service. ID:aa....aa reason code=bb....bb-cc....cc

aa....aa: PRF identifier

If the PRF identifier cannot be identified, **** is displayed.

bb....bb: Reason code

cc....cc: Internal system code

Description

An error occurred during initialization of the PRF trace service in the process.

The PRF trace acquisition of the process in which the error occurred will be suspended. This initialization is a preparatory process to acquire the PRF trace in the process.

Note that, this message may also be output during command execution.

Action

Based on the list of reason codes described in the following table, remove the cause of the error.

Table 19‒19: List of failure reason codes displayed in KFCT73004-W

Reason code

Cause

101

Memory is insufficient.

106

The directory specified in the environment variable PRFSPOOL may not have been created correctly.

115

The shared memory controlled by the PRF daemon cannot be accessed. If output with a command, confirm that the specified PRF daemon is running.

1601

An error occurred in the system call.

KFCT73100-I

now starting statistical information service. ID:aa....aa

aa....aa: Service identifier(CTM identifier)

Description

The statistical information service is running.

KFCT73101-I

statistical information service started. ID:aa....aa

aa....aa: Service identifier(CTM identifier)

Description

The statistical information service was started.

KFCT73102-I

statistical information service stopped ID:aa....aa

aa....aa: Service identifier(CTM identifier)

Description

The statistical information service was stopped.

KFCT73104-W

statistical information service cannot be started. ID:aa....aa reason code=bb....bb-cc....cc

aa....aa: Service identifier(CTM identifier)

bb....bb: Reason code

cc....cc: Internal code

Description

A failure occurred in the initialization of the statistical information service.

The statistical information cannot be acquired in the relevant CTM node.

Action

Based on the list of reason codes described in the following table, remove the cause of the error.

Table 19‒20: List of reason codes for errors described in KFCT73104-W

Reason code

Cause

Action

1

Memory is insufficient.

Revise the memory size

2

The shared memory used for operation statistics is insufficient.

Revise the size of the shared memory.

3

The shared memory used for operation statistics cannot be accessed.

Contact maintenance personnel.

4

The new message queue ID in the msgget system call was not allocated.

Delete the unnecessary message queue ID.

5

The specified environment variable CTMSPOOL is invalid.

Revise the value specified in the environment variable CTMSPOOL.

6

An attempt to start the timer thread has failed.

Contact maintenance personnel.

8

The path specified in the environment variable CTMSPOOL is too long.

Check whether the length of the path exceeds 1,023 bytes and, if necessary, revise it.

9

The specified statistical information service is already running.

--

10

An attempted exclusive control has failed.

Contact maintenance personnel.

11

An error occurred in the internal processing.

Contact maintenance personnel.

Legend:

--: No action is performed.

KFCT73105-W

failure to create I/O thread for statistical information service. ID:aa....aa reason code=bb....bb-cc....cc

aa....aa: Service identifier(CTM identifier)

bb....bb: Reason code

cc....cc: Internal code

Description

An attempt to create an exclusive I/O thread for the statistical information service has failed.

The statistical information cannot be acquired in the relevant CTM node.

The statistical information service will not be executed in the relevant CTM node.

Action

Based on the list of reason codes described in the following table, remove the cause of the error.

Table 19‒21: List of reason codes for errors described in KFCT73105-W

Reason code

Cause

Action

1

Memory is insufficient.

Revise the memory size

3

The shared memory used for operation statistics cannot be accessed.

Contact maintenance personnel.

5

The specified environment variable CTMSPOOL is invalid.

Revise the value specified in the CTMSPOOL environment variable.

8

The path specified in the environment variable CTMSPOOL is too long.

Check whether the length of the path exceeds 1,023 bytes and, if necessary, revise it.

13

An error occurred in the system call.

Check the message displayed before this message, and then contact maintenance personnel.

KFCT73106-W

I/O thread for statistical information service is stopped. ID:aa....aa reason code=bb....bb-cc....cc

aa....aa: Service identifier(CTM identifier)

bb....bb: Reason code

cc....cc: Internal code

Description

The exclusive I/O thread of the statistical information service was stopped.

The acquisition of statistical information cannot continue in the relevant CTM node.

The statistical information service will be suspended in the relevant CTM node.

Action

Based on the list of reason codes described in the following table, remove the cause of the error.

Table 19‒22: List of failure reason codes displayed in KFCT73106-W

Reason code

Cause

Action

1

Memory is insufficient.

Revise the memory size

4

The new message queue ID in the msgget system call was not allocated.

Delete the unnecessary message queue ID.

11

An attempt to open the statistical information file has failed.

Contact maintenance personnel.

12

An I/O error occurred for the statistical information file.

Contact maintenance personnel.

KFCT73107-W

failure to initialize on process for statistical information service. ID:aa....aa reason code=bb....bb-cc....cc

aa....aa: Service identifier(CTM identifier)

bb....bb: Reason code

cc....cc: Internal code

Description

An attempt to initialize the statistical information service in the process has failed.

The statistical information of the relevant process is not acquired.

Action

Based on the list of reason codes described in the following table, remove the cause of the error.

Table 19‒23: List of failure reason codes displayed in KFCT73107-W

Reason code

Cause

Action

1

Memory is insufficient.

Revise the memory size

3

The shared memory used for operation statistics cannot be accessed.

Contact maintenance personnel.

5

The specified environment variable CTMSPOOL is invalid.

Revise the value specified in the environment variable CTMSPOOL.

8

The path specified in the environment variable CTMSPOOL is too long.

Check whether the length of the path exceeds 1,023 bytes and, if necessary, revise it.

13

An error occurred in the system call.

Check the message displayed before this message, and then contact maintenance personnel.

KFCT73200-E

cannot delete module trace file. file name:aa....aa reason code=bb....bb-cc....cc

aa....aa: Path name of the file that cannot be deleted

bb....bb: Reason code

cc....cc: Internal system code

Description

The module trace file used in the CTM or performance tracer cannot be deleted.

The deletion of the module trace file will be skipped.

Action

Based on the list of reason codes described in the following table, remove the cause of the error, and then re-execute the command.

Table 19‒24: List of reason codes described in KFCT73200-E

Reason code

Cause

101

Memory is insufficient.

204

An attempt to delete the module trace file has failed.

1601

A system call error occurred.

KFCT73201-E

module trace cannot be started. reason code=aa....aa-bb....bb

aa....aa: Reason code

bb....bb: Internal system code

Description

An error occurred while starting the module trace acquisition used in the CTM or performance tracer.

The module trace will not be acquired.

Action

Based on the list of reason codes described in the following table, remove the cause of the error, and then re-execute the command.

Table 19‒25: List of reason codes described in KFCT73201-E

Reason code

Cause

101

Memory is insufficient.

106

The directory specified in the environment variables CTMSPOOL and PRFSPOOL may not have been created correctly. Also, if the environment variable CTMSPOOL is omitted, you need to revise the directory specified in the environment variable CTMDIR.

201

The following directories cannot be created:

$CTMSPOOL/utt (in UNIX) or %CTMSPOOL%\utt (in Windows)

$PRFSPOOL/utt (in UNIX) or %PRFSPOOL%\utt (in Windows)

202

The following directories cannot be created:

$CTMSPOOL/utt/umt (in UNIX) or %CTMSPOOL%\utt\umt (in Windows)

$PRFSPOOL/utt/umt (in UNIX) or %PRFSPOOL%\utt\umt (in Windows)

502

An error occurred while creating the necessary environment to control the module trace.

504

An attempt to initialize the timer process has failed. The system continues and the module trace will be acquired. However, the unnecessary files in the following directories will not be deleted:

$CTMSPOOL/utt/umt (in UNIX) or %CTMSPOOL%\utt\umt (in Windows)

$PRFSPOOL/utt/um (in UNIX) or %PRFSPOOL%\utt\umt (in Windows)

Normally, the unnecessary files are deleted every 24 hours. Contact maintenance personnel.

1601

A system call error occurred.

KFCT73202-E

failure to initialize for module trace. reason code=aa....aa-bb....bb

aa....aa: Reason code

bb....bb: Internal system code

Description

An error occurred while initializing the module trace acquisition used in the CTM or performance tracer.

The module trace of the process in which an error occurred is not acquired. This initialization is a preparatory process to acquire the module trace in the process.

Action

Based on the list of reason codes described in the following table, remove the cause of the error, and then re-execute the command.

Table 19‒26: List of reason codes described in KFCT73202-E

Reason code

Cause

101

Memory is insufficient.

106

The directory specified in the environment variables CTMSPOOL and PRFSPOOL may not have been created correctly. Also, if the environment variable CTMSPOOL is omitted, you need to revise the directory specified in the environment variable CTMDIR.

109

An error occurred while creating the module trace file.

Remove the cause of the error from the errno value of KFCT73351-E or KFCT75500-E.

201

The following directories cannot be created:

$CTMSPOOL/utt (in UNIX) or %CTMSPOOL%\utt (in Windows)

$PRFSPOOL/utt (in UNIX) or %PRFSPOOL%\utt (in Windows)

Remove the cause of the error from the errno value of KFCT73351-E or KFCT75500-E.

202

The following directories cannot be created:

$CTMSPOOL/utt/umt (in UNIX) or %CTMSPOOL%\utt\umt (in Windows)

$PRFSPOOL/utt/umt (in UNIX) or %PRFSPOOL%\utt\umt (in Windows)

Remove the cause of the error from the errno value of KFCT73351-E or KFCT75500-E.

203

An error occurred in the umt internal exclusive control.

Communicate the errno value of the message KFCT75500-E to maintenance personnel.

503

An attempt to open the directory for creating the module trace file has failed. This directory will be created while starting CTM domain manager and the PRF daemon. Check whether the CTM domain manager and the PRF daemon are running normally in the execution environment in which this message is displayed.

505

The option argument of the command is invalid.

Revise the option argument of the message KFCT73350-E.

1601

A system call error occurred.

KFCT73203-W

error occurred while checking trace file number. reason code=aa....aa-bb....bb

aa....aa: Reason code

bb....bb: Internal system code

Description

An error occurred while deleting the files under the following directories:

$CTMSPOOL/utt/umt (in UNIX) or %CTMSPOOL%\utt\umt (in Windows)

$PRFSPOOL/utt/umt (in UNIX) or %PRFSPOOL%\utt\umt (in Windows)

The files under these directories will not be deleted, but the processing of the system continues.

Action

Based on the list of reason codes described in the following table, remove the cause of the error.

Table 19‒27: List of failure reason codes displayed in KFCT73203-W

Reason code

Cause

101

Memory is insufficient.

203

An error occurred in the umt internal exclusive control.

Communicate the errno value of the message KFCT75500-E to maintenance personnel.

KFCT73300-E

cannot execute aa....aa command. reason code=bb....bb-cc....cc

aa....aa: Name of the command that cannot be executed

bb....bb: Reason code

cc....cc: Internal system code

Description

The command (aa....aa) cannot be executed.

The command terminates with an error.

Action

Based on the list of reason codes described in the following table, remove the cause of the error, and then re-execute the command.

Table 19‒28: List of reason codes described in KFCT73300-E

Reason code

Cause

101

Memory is insufficient.

103

An I/O error occurred in the file.

106

The internal system file required for executing the aa....aa command does not exist. Confirm the following details:

The directory of the environment variable PRFSPOOL in the environment in which the command is executed

PRF identifier specified in the command

107

An error occurred while opening the trace file.

116

The number of specified trace files exceeds 256.

804

The file cannot be found.

1601

An error occurred in the system call.

KFCT73303-I

usage:ctmstsstart [-h] | [[-CTMDomain domain_name] [-CTMID ctmid] [-CTMInterval interval_time] [-CTMCheckInterval interval_time]]

Description

This message describes the usage method of the ctmstsstart command. This error message is displayed when the command format is invalid or when the -h option is specified.

If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT73304-I

usage:ctmstsstop [-h] | [[-CTMDomain domain_name] [-CTMID ctmid]]

Description

This message describes the usage method of the ctmstsstop command. This error message is displayed when the command format is invalid or when the -h option is specified.

If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT73307-I

usage:ctmstsed [-h] | [-CTMEdit edit-item[,edit-item]] [-CTMInterval interval] [-CTMTime [start][,end]] [-CTMQueueName queuename[,queuename]] [-CTMMethod methodname[,methodname]] [-CTMCsv] [-CTMStdout] [ststrace-file [ststrace-file]]

Description

This message describes the usage method of the ctmstsed command. This error message is displayed when the command format is invalid or when the -h option is specified.

If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT73308-E

ctmstsstart command cannot be executed. reason code=aa....aa-bb....bb

aa....aa: Reason code

bb....bb: Internal code

Description

The ctmstsstart command cannot be executed.

The command execution will be suspended.

Action

Based on the list of reason codes described in the following table, remove the cause of the error.

Table 19‒29: List of reason codes described in KFCT73308-E

Reason code

Cause

Action

1

Memory is insufficient.

Revise the memory size

3

The shared memory used for operation statistics cannot be accessed.

Contact maintenance personnel.

5

The specified environment variable CTMSPOOL is invalid.

Revise the value specified in the environment variable CTMSPOOL. If the environment CTMSPOOL is not specified, revise the value specified in the environment variable CTMDIR.

8

The path specified in the environment variable CTMSPOOL is too long.

Check whether the length of the path exceeds 1,023 bytes and, if necessary, revise it.

13

An error occurred in the system call.

Check the message displayed before this message, and then contact maintenance personnel.

15

An error occurred in the internal processing.

Contact maintenance personnel.

16

An attempt to acquire the IP address has failed.

Contact maintenance personnel.

17

The CTM daemon of the relevant CTM identifier is not online or the statistical information service is not running in the CTM node.

Confirm that the CTM daemon is running.

18

The exclusive control between processes has failed.

Contact maintenance personnel.

19

The ctmstsstart command is already executed.

If required, execute the ctmstsstop command, and then re-execute the ctmstsstart command.

26

The statistical information service is not running.

To acquire the statistical information, start the statistical information service.

KFCT73309-E

ctmstsstop command cannot be executed. reason code=aa....aa-bb....bb

aa....aa: Reason code

bb....bb: Internal code

Description

The ctmstsstop command cannot be executed.

The command execution will be suspended.

Action

Based on the list of reason codes described in the following table, remove the cause of the error.

Table 19‒30: List of reason codes displayed in KFCT73309-E

Reason code

Cause

Action

1

Memory is insufficient.

Revise the memory size

3

The shared memory used for operation statistics cannot be accessed.

Contact maintenance personnel.

5

The specified environment variable CTMSPOOL is invalid.

Revise the value specified in the environment variable CTMSPOOL. If the environment CTMSPOOL is not specified, revise the value specified in the environment variable CTMDIR.

8

The path specified in the environment variable CTMSPOOL is too long.

Check whether the length of the path exceeds 1,023 bytes and, if necessary, revise it.

10

An attempted exclusive control has failed.

Contact maintenance personnel.

13

An error occurred in the system call.

Check the message displayed before this message, and then contact maintenance personnel.

15

An error occurred in the internal processing.

Contact maintenance personnel.

16

An attempt to acquire the IP address has failed.

Contact maintenance personnel.

17

The CTM daemon of the relevant CTM identifier is not online or the statistical information service is not running in the CTM node.

Confirm that the CTM daemon is running.

18

The exclusive control between processes has failed.

Contact maintenance personnel.

22

The ctmstsstart command is not yet executed.

Execute the ctmstsstart command, and then execute the ctmstsstop command.

KFCT73310-E

ctmstsed command cannot be executed. reason code=aa....aa-bb....bb

aa....aa: Reason code

bb....bb: Internal code

Description

An error occurred while executing the ctmstsed command.

The command execution will be suspended.

Action

Based on the list of reason codes described in the following table, remove the cause of the error.

Table 19‒31: List of reason codes described in KFCT73310-E

Reason code

Cause

Action

1

Memory is insufficient.

Revise the memory size

11

An attempt to create a file to output the edited output has failed or an attempt to open the statistical information file has failed.

Investigate the reason due to which the file cannot be created (access settings, OS settings), remove the cause of the error, and then re-execute the command. If an attempt to open the statistical information file has failed, revise the command specifications, and then re-execute the command.

13

An error occurred in the system call.

Check the message displayed before this message, and then contact maintenance personnel.

14

The number of statistical information files specified in the argument of the ctmstsed command has exceeded 256.

Specify a value of 256 or less for the number of statistical information files specified in the argument of the command, and then execute the command.

15

An error occurred in the internal processing.

Contact maintenance personnel.

23

An error occurred in the edited output of the statistical information.

Contact maintenance personnel.

24

An old output result file is remaining in the current directory.

The statistical information file is entered from a standard input, so whether to overwrite the file cannot be prompted. Therefore, the processing was interrupted. If the statistical information file is entered from a standard input, delete or save the operation statistics output file present in the directory to be executed, and then execute the command.

KFCT73311-W

no records found to meet the condition. aborts processing.

Description

A record in which the statistical information is to be edited was not found. The processing will now stop.

The record for the specified time interval does not exist or the contents of the specified file do not exist.

The command process will be interrupted.

Action

Revise the time specified in the -CTMTime option or revise the specified statistical information file.

In the Windows environment, confirm that the statistical information file is specified.

KFCT73314-I

usage: ctmstsflush [-h] | [-CTMDomain domain_name] [-CTMID ctmid]

Description

This message describes the usage method of the ctmstsflush command. This error message is displayed when the command format is invalid or when the -h option is specified.

If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT73315-E

ctmstsflush command cannot be executed. reason code= aa....aa- bb....bb

aa....aa: Reason code

bb....bb: Internal code

Description

An error occurred while executing the ctmstsflush command.

The command execution will be suspended.

Action

Based on the list of reason codes described in the following table, remove the cause of the error.

Table 19‒32: List of reason codes described in KFCT73315-E

Reason code

Cause

Action

1

Memory is insufficient.

Revise the memory size

5

The specified environment variable CTMSPOOL is invalid.

Revise the value specified in the environment variable CTMSPOOL. If the environment CTMSPOOL is not specified, revise the value specified in the environment variable CTMDIR.

8

The path specified in the environment variable CTMSPOOL is too long.

Check whether the length of the path exceeds 1,023 bytes and, if necessary, revise it.

13

An error occurred in the system call.

Check the message displayed before this message, and then contact maintenance personnel.

15

An error occurred in the internal processing.

Contact maintenance personnel.

17

The CTM daemon of the relevant CTM identifier is not online or the statistical information service is not running in the CTM node.

Confirm that the CTM daemon is running.

18

The exclusive control between processes has failed.

Contact maintenance personnel.

22

The ctmstsstart command is not yet executed.

Execute the ctmstsstart command, and then execute the ctmstsflush command.

26

The statistical information service is not running.

To acquire the statistical information, start the statistical information service.

27

A timeout occurred.

The writing to the trace information file in the buffer may have finished. Contact maintenance personnel.

KFCT73350-E

command option is invalid. aa....aa

aa....aa: Option name

Description

The command option is invalid.

The processing will be interrupted.

Action

Check whether the specified option is invalid or whether a problem exists in the combination of the specified options and, if necessary, revise them. Modify the specified option, and then re-execute the command.

KFCT73351-E

"aa....aa(bb....bb)" failed. errno=cc....cc

aa....aa: System call in which the error occurred

bb....bb: Internal information

cc....cc: errno value of the system call

Description

An error occurred in the system call.

The processing will be interrupted.

Action

Contact system administrator.

The System Administrator needs to investigate the cause of the error in the system call.

KFCT73352-R

aa....aa file exists. Is it overwritten ? [Y:Yes N:No]

aa....aa: File name

Description

An operation statistics output file created during the previous execution of the ctmstsed command is present in the current directory. If you want to overwrite this output file, choose Y, and if you do not to overwrite it, choose N. You can also use lower case.

Action

Specify Y or N as per the message.

KFCT73353-I

The execute of aa....aa command was suspended.

aa....aa: Command name

Description

The processing of the command that is being executed will be interrupted.

Action

If a message is displayed before this message, remove the cause of the error based on that message, and then re-execute the command. If a message is not displayed before this message, contact maintenance personnel.

KFCT73354-E

the combination of domain name and CTMSPOOL directory is invalid.

Description

The combination of the CTM domain name and the environment variable CTMSPOOL is invalid.

The processing of the command will be interrupted.

Action

Check whether the specified environment variable CTMSPOOL is already being used in another CTM domain manager with another CTM domain name, and then re-execute the command.

KFCT73355-I

buffering of statistical information is started. ID:aa....aa start time:bb....bb output interval:cc....cc connect check interval:dd....dd

aa....aa: CTM identifier

bb....bb: Buffering start time (yyyy/mm/dd hh: mm format)

cc....cc: Time interval output to the file (unit: minutes)

dd....dd: Time interval to perform connection count check (unit: seconds)

Description

The process of acquiring the statistical information into the shared memory will start.

KFCT73356-I

buffering of statistical information is stopped. ID:aa....aa

aa....aa: CTM identifier

Description

The buffering of the statistical information into the shared information was stopped.

KFCT73357-I

ctmstsstart command is accepted. option: aa....aa

aa....aa: The specified option name and option argument are displayed in the following format:

Option name[,option argument][;option name[,option argument]...]

Description

The ctmstsstart command is accepted.

The processing of the command continues.

KFCT73364-W

cannot output trace information to a statistical file.

Description

The statistical information cannot be output to a file.

The output of the statistical information will stop.

Action

Execute the ctmstsstop command and the ctstsstart command and then resume the acquisition of the statistical information. After the statistical information is output to the previous file, the statistical information pooled in the buffer is not output to the file.

KFCT73401-I

usage:cprfstart [-h] | [-PRFID cprfid] [-PrfTraceLevel tracelevel[,[tracelevel]...]] [-PrfTraceCount count] [-PrfTraceFileSize file_size] [-PrfTraceBufferSize buffer_size] [-PrfRemakeBuffer] [-PrfNoBackUp [0|1]]

Description

This message describes the usage method of the cprfstart command.

This message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it. Modify the specified option, and then re-execute the command.

KFCT73402-I

usage:cprfstop [-h] | [-PRFID cprfid] [-Force]

Description

This message describes the usage method of the cprfstop command.

This message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it. Modify the specified option, and then re-execute the command.

KFCT73403-I

usage:cprfed [-h] | [[-Dump | -CSV] [-Time [start][,end]] [-ProcessID process-ID[,process-ID...]][-TraceFile prftrace-file[,prftrace-file...] | -AllTraceFile]]

Description

This message describes the usage method of the cprfed command.

This message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it. Modify the specified option, and then re-execute the command.

KFCT73404-I

usage:cprflevel [-h] | [-PRFID cprfid] [-PrfChangeLevel tracelevel[,[tracelevel]...]] [-PrfLevelIndex index] [-PrfLevelAll]

Description

This message describes the usage method of the cprflevel command.

This message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it. Modify the specified option, and then re-execute the command.

KFCT73405-I

usage:cprfflush [-h] | [-PRFID cprfid]

Description

This message describes the usage method of the cprfflush command.

This message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it. Modify the specified option, and then re-execute the command.

KFCT73406-I

usage:cprfgetpid [-h] | [-PRFID cprfid]

Description

This message describes the usage method of the cprfgetpid command.

This message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it. Modify the specified option, and then re-execute the command.

KFCT73410-I

now starting cprfd.

Description

The PRF daemon is being started.

The startup process of the PRF daemon continues.

KFCT73411-I

ProductName = aa....aa

PpNo = bb....bb

Version = cc....cc

PRFID = dd....dd

PRFSPOOL directory = ee....ee

aa....aa: Product name

bb....bb: Product ID

cc....cc: Version

dd....dd: PRF identifier

ee....ee: PRFSPOOL directory

Description

The information related to PRF daemon that is being started is output.

The startup process of the PRF daemon continues.

KFCT73412-I

cprfd is now online.

Description

The startup of the PRF daemon is finished.

The processing of the PRF daemon continues.

KFCT73413-I

now terminating cprfd. terminate type =aa....aa

aa....aa: Termination type (NORMAL STOP: Normal termination, FORCE STOP: Forced normal termination)

Description

The PRF daemon is being terminated.

The processing of the PRF daemon continues according to the contents described in the termination type (aa....aa).

KFCT73414-I

CPRFD stop.

Description

The PRF daemon was stopped normally.

The processing of the PRF daemon terminates.

KFCT73415-I

prf trace level is aa....aa.

aa....aa: PRF trace level

Description

The current PRF trace level for index number 1 will be displayed and the command terminates.

KFCT73416-I

prf trace level was changed from aa....aa to bb....bb.

aa....aa: old PRF trace level

bb....bb: new PRF trace level

Description

The old and new PRF trace levels at index number 1 will be displayed and the command terminates.

KFCT73417-I

option for aa....aa= bb....bb

aa....aa: Command name

bb....bb: The specified option name and option argument are displayed in the following format:

Option name[,option argument][;option name[,option argument]...]

Description

The command is accepted. The option (bb....bb) specified in the command will be output.

The processing of the command continues.

KFCT73418-I

all prf trace levels are:

[aa....aa]=bb....bb [aa....aa]=bb....bb [aa....aa]=bb....bb [aa....aa]=bb....bb

aa....aa: Index number

bb....bb: PRF trace level of the relevant index number

Description

All the current PRF trace levels will be displayed and the command terminates.

KFCT73419-I

prf trace level of [aa....aa] is bb....bb.

aa....aa: Index number

bb....bb: PRF trace level of the relevant index number

Description

The PRF trace level of the specified index number will be displayed and the command terminates.

KFCT73420-I

prf trace level was changed:

[aa....aa]= bb....bb -> [aa....aa]= cc....cc

aa....aa: Index number

bb....bb: Old PRF trace level of the relevant index number

cc....cc: New PRF trace level of the relevant index number

Description

The old and new PRF trace levels will be displayed and the command terminates.

KFCT73430-E

prf tracing service cannot be started. ID= aa....aa reason code = bb....bb - cc....cc.

aa....aa: PRF identifier

If the PRF identifier cannot be identified, **** is displayed.

bb....bb: Reason code

cc....cc: Internal system code

Description

An attempt to start the PRF trace service failed.

The PRF trace service will terminate.

Action

Based on the list of reason codes described in the following table, investigate the cause, and then remove the cause of the error. However, when exclusive control fails, an internal error occurs, and a message other than the listed reason codes appears, contact maintenance personnel.

Table 19‒33: List of reason codes displayed in KFCT73430-E

Reason code

Cause

101

Memory is insufficient.

102

Memory is insufficient.

104

The new message queue ID in the msgget system call was not allocated. Check the usage status with the ipcs command. If an unnecessary message queue exists, the queue needs to be deleted with the ipcrm command.

106

The environment variable PRFSPOOL may not have been specified or the directory specified in the environment variable PRFSPOOL may not have been created correctly.

112

The specified PRF trace service is already running. Alternatively, the PRF trace service has terminated but a new PRF trace service cannot start because the running process is collecting the trace.

115

An attempt to access the shared memory used in the PRF trace service failed.

117

The specified option is invalid.

118

The shared memory used in the PRF trace service cannot be reused. Add the -PrfRemakeBuffer option to the cprfstart command, and then execute the command.

119

An attempt to re-create the shared memory used in the PRF trace service failed. If a process using the PRF trace service is running, the shared memory cannot be re-created. If you want to re-create the shared memory and start the PRF daemon, terminate the process that is using the PRF trace service.

Note that, the shared memory is re-created in the following cases:

When the cprfstart command is executed with the -PrfRemakeBuffer option added

When the cprfstart command is executed with a value different from the previous value (if value was not specified previously, specify a value other than 8194) specified in the -PrfTraceBufferSize option

502

An error occurred during creation of the necessary environment to control the PRF trace service.

1601

An error occurred in the system call.

3201

A timeout occurred when starting the PRF daemon. The PRF daemon may be running normally.

3203

An attempted exclusive control has failed.

8001

An internal error occurred.

KFCT73431-E

cannot create the process. process_name=aa....aa.

aa....aa: Process name (cprfd: PRF daemon)

Description

An attempt to generate the child process has failed.

The daemon startup process terminates.

Action

Wait for a while, and then restart or check the following details:

Are the system file resources insufficient?

Has the generation of child processes failed?

Is the memory insufficient?

Also, see the message KFCT73430-E output before this message, and then remove the cause of the error.

KFCT73432-W

failure to initialize for prf tracing service. ID: aa....aa reason code bb....bb - cc....cc.

aa....aa: PRF identifier

If the PRF identifier cannot be identified, **** is displayed.

bb....bb: Reason code

cc....cc: Internal system code

Description

An attempt to initialize the PRF trace service failed.

The acquisition of PRF trace of the process in which an error occurred will be suspended.

Action

Based on the list of reason codes described in the following table, investigate the cause, and then remove the cause of the error. Furthermore, if an internal error occurs, contact maintenance personnel.

Table 19‒34: List of failure reason codes displayed in KFCT73432-W

Reason code

Cause

117

The specified option is invalid.

8001

An internal error occurred.

KFCT73433-E

cannot stop CPRFD. ID= aa....aa reason code = bb....bb - cc....cc.

aa....aa: PRF identifier

If the PRF identifier cannot be identified, **** is displayed.

bb....bb: Reason code

cc....cc: Internal system code

Description

An attempt to stop the PRF daemon has failed.

The cprfstop command terminates with an error.

Action

Based on the list of reason codes described in the following table, investigate the cause, and then remove the cause of the error. If the PRF daemon is not terminated, re-execute the cprfstop command. However, when exclusive control fails, an internal error occurs, and a message other than the listed reason codes appears, contact maintenance personnel.

Table 19‒35: List of reason codes displayed in KFCT73433-E

Reason code

Cause

106

The environment variable PRFSPOOL may not have been specified or the directory specified in the environment variable PRFSPOOL may not have been created correctly.

115

An attempt to access the shared memory used in the PRF trace service failed. Specify -Force option, and then execute the command.

117

The specified option is invalid.

3201

A timeout occurred. Specify -Force option, and then execute the command.

3202

The PRF daemon with the specified PRF identifier is not running.

3203

An attempted exclusive control has failed.

8001

An internal error occurred.

KFCT73434-E

CPRFD is already started. ID= aa....aa.

aa....aa: PRF identifier

Description

A PRF daemon with the specified PRF identifier is already running.

The cprfstart command terminates with an error.

A PRF daemon with the same PRF identifier as a PRF daemon that is already running cannot be started.

Action

Check whether a PRF daemon with the same PRF identifier is running. After this check, if required, specify a different PRF identifier, and then re-execute the cprfstart command.

KFCT73435-E

CPRFD has not started. ID=aa....aa.

aa....aa: PRF identifier

Description

A PRF daemon with the specified PRF identifier is not running.

The command terminates with an error.

Action

Check whether a PRF daemon with the specified PRF identifier is running. Note that this message may also be displayed when the PRF daemon is running. In such cases, check that the -PRFID option, specified when the command starts, is correct or check that the running PRF daemon and the environment variable PRFSPOOL are different.

KFCT73436-E

PRFSPOOL environment is undefined.

Description

The environment variable PRFSPOOL is not specified.

The process terminates with an error.

Action

Confirm that the environment variable PRFSPOOL is specified. Specify a valid environment variable PRFSPOOL, and then re-execute the process.

KFCT73437-E

cannot find PRFSPOOL directory.

Description

The directory described in the environment variable PRFSPOOL was not found.

The process terminates with an error.

Action

Confirm that the directory described in the environment variable PRFSPOOL is correctly created. Create the directory described in the environment variable PRFSPOOL correctly, and then re-execute the process.

KFCT73438-E

cannot change prf trace level. ID= aa....aa reason code = bb....bb - cc....cc.

aa....aa: PRF identifier

If the PRF identifier cannot be identified, **** is displayed.

bb....bb: Reason code

cc....cc: Internal system code

Description

The PRF trace level cannot be changed.

The cprflevel command terminates with an error.

Action

Based on the list of reason codes described in the following table, investigate the cause, and then remove the cause of the error. After the cause of the error is removed, re-execute the cpflevel command. However, when exclusive control fails, an internal error occurs, and a message other than the listed reason codes appears, contact maintenance personnel.

Table 19‒36: List of reason codes described in KFCT73438-E

Reason code

Cause

106

The environment variable PRFSPOOL may not have been specified or the directory specified in the environment variable PRFSPOOL may not have been created correctly.

117

The specified option is invalid.

3202

The PRF daemon with the specified PRF identifier is not running.

3203

An attempted exclusive control has failed.

8001

An internal error occurred.

KFCT73439-E

cannot execute aa....aa command. reason code bb....bb - cc....cc.

aa....aa: Name of the command that cannot be executed

bb....bb: Reason code

cc....cc: Internal system code

Description

The command (aa....aa) cannot be executed.

The command terminates with an error.

Action

Based on the list of reason codes described in the following table, investigate the cause, and then remove the cause of the error. However, when exclusive control fails, an internal error occurs, and a message other than the listed reason codes appears, contact maintenance personnel.

Table 19‒37: List of reason codes displayed in KFCT73439-E

Reason code

Cause

106

The environment variable PRFSPOOL may not have been specified or the directory specified in the environment variable PRFSPOOL may not have been created correctly.

115

An attempt to access the shared memory used in the PRF trace service failed.

117

The specified option is invalid.

3201

A timeout occurred. If this message is displayed while executing the cprfflush command, the writing to the trace information file in the buffer may have finished.

3202

The PRF daemon with the specified PRF identifier is not running.

3203

An attempted exclusive control has failed.

8001

An internal error occurred.

KFCT73440-E

cannot read trace-file.

Description

An error occurred while reading the trace file in the PRF trace editing process.

The command terminates with an error.

Action

Confirm the following details:

The trace file may not be specified in the edit command. Specify the trace file with -TraceFile (for Windows).

Check if the specified trace file is valid and the access permission is available and, if necessary, revise it.

Also, see the message KFCT75500-E displayed before this message and remove the cause of the error.

KFCT73441-E

-PrfTraceBufferSize value is over -PrfTraceFileSize value.

Description

The specified value of the -PrfTraceBufferSize option exceeds the value of the -PrfTraceFileSize option. The startup command terminates with an error.

Action

Check whether the specified value of the -PrfTraceBufferSize option exceeds the -PrfTraceFileSize option. Also, if the -PrfTraceFileSize option is not specified, confirm that the specified value of the -PrfTraceBufferSize option is 8192 or less.

If the specified value of the -PrfTraceBufferSize option exceeds the -PrfTraceFileSize option, in the -PrfTraceBufferSize option, specify a value less than or equal to the value of the -PrfTraceFileSize option.

KFCT73445-E

cannot output trace information to a trace-file.

Description

The trace information cannot be output to a file.

The output of the trace file will be stopped. This message is displayed when the buffer for acquiring PRF trace is insufficient.

Action

Forcibly stop a running PRF daemon. After this, normally start the PRF daemon. To stop the PRF daemon forcibly, add the -Force option to the cprfstop command, and then execute the command.

Also, in order to avoid this error, we recommend that you set the buffer size for acquiring PRF trace to a value greater than the default value (8192 kilobytes). For details on changing the buffer size, see the cprfstart command in the manual uCosminexus Application Server Command Reference Guide.

KFCT73501-E

process aborted.(reason=aa....aa)

aa....aa: Reason for the inability to continue the process

Description

The processing cannot be continued, so the processing will be suspended.

One of the following reasons will be displayed in aa....aa:

An attempt to cancel the exclusion between threads has failed.

An attempt to cancel the exclusion between processes has failed.

Action

Memory used in the operation may be insufficient. Increase the memory of the operating environment.

If this error continues to occur frequently, contact system administrator.

KFCT73502-W

cannot load library.

Description

The environment variable that specifies the library storage directory or the version of Cosminexus TPBroker being used is invalid.

The processing continues. However, all the messages from the process in which this message was output are output in standard output or standard error output and are not output in system log, CTM log, and CTM domain log.

Action

Change the environment variable that specifies the library storage directory or install the valid version of Cosminexus TPBroker, and then re-execute the process.

KFCT73551-E

cannot get aa....aa.

aa....aa: Name of the information that cannot be acquired

Description

The aa....aa information cannot be acquired.

The processing will be interrupted.

Action

Contact system administrator.

The System Administrator needs to confirm that the environment enables the acquisition of the information.

KFCT73552-E

cannot access directory indicated by aa....aa. "bb....bb"

aa....aa: Name of the information that indicates the directory

bb....bb: Directory name

Description

The directory (bb....bb) cannot be accessed.

The processing will be interrupted.

Action

Contact system administrator.

The System Administrator needs to check that the information describing the directory is valid. He also needs to check details such as the access permissions of the directory.

KFCT73553-E

cannot open file "aa....aa".

aa....aa: Name of the file that cannot be opened

Description

The file (aa....aa) cannot be opened.

The processing will be interrupted.

Action

Contact system administrator.

The System Administrator needs to check details such as the access permission for the files and directories.

KFCT73554-E

cannot read file "aa....aa".

aa....aa: Name of the file that cannot be read

Description

The file (aa....aa) cannot be read.

The processing will be interrupted.

Action

Contact system administrator.

The System Administrator needs to check details such as the access permission for the files and directories.

KFCT73555-E

cannot close file "aa....aa".

aa....aa: Name of the file that cannot be closed

Description

The file (aa....aa) cannot be closed.

The processing will be interrupted.

Action

Contact system administrator.

The System Administrator needs to check details such as the access permission for the files and directories.

KFCT73556-E

cannot access file "aa....aa".

aa....aa: Name of the file that cannot be accessed

Description

The file (aa....aa) cannot be accessed.

The processing will be interrupted.

Action

Contact system administrator.

The System Administrator needs to check details such as the access permission for the files and directories.

KFCT73557-E

aa....aa environment variable undefined.

aa....aa: Name of the undefined environment variable

Description

The environment variable (aa....aa) is not defined.

The processing will be interrupted.

Action

Contact system administrator.

The System Administrator needs to define the environment variable.

KFCT73558-E

invalid option. option=aa....aa value=bb....bb reason=cc....cc.

aa....aa: Option name

bb....bb: Invalid option argument (cc....cc is only displayed in the case of INVALID_VALUE)

cc....cc: Reason code

Description

The option is invalid.

The processing will be interrupted.

Action

Take action based on the reason codes described in cc....cc. The following table lists the reason codes described in cc....cc and the corresponding actions.

Table 19‒38: List of reason codes displayed in KFCT73558-E

Cause of error

Cause

Action

NO_OPT_ARG

The option argument is not specified.

Revise the specified value of the option, and then re-execute the command.

INVALID_VALUE

The value of the option argument is invalid.

Revise the specified value of the option, and then re-execute the command.

Others

An internal error occurred during the option analysis process.

Acquire the contents of option (aa....aa), value (bb....bb), and reason (cc....cc), and then contact maintenance personnel.

KFCT73559-E

the error occurred while initializing log function. reason=aa....aa detail=bb....bb inter=cc....cc.

aa....aa: Reason for occurrence of error

bb....bb: Detailed message

cc....cc: Maintenance information

Description

An error occurred while initializing the log function.

The processing will be interrupted.

Action

Take action based on the reasons for the error occurrence described in aa....aa, and then re-execute the command. The following table lists the reasons for the error occurrence described in aa....aa and the corresponding actions.

Table 19‒39: List of causes described in KFCT73559-E

Cause of error

Cause

Action

ENVIRON

An attempt to acquire the environment variables has failed.

Check whether the environment variables CTMDIR, CTMSPOOL, and PRFSPOOL have been defined and, if necessary, revise them.

FILE_ACC

An attempt to access the file has failed.

Check whether the CTMSPOOL and PRFSPOOL directories exist and whether the access permissions have been set up correctly. Also, confirm that enough free space is available in CTMSPOOL directory.

LOCK

An attempted exclusive control has failed.

If memory is insufficient, terminate the unnecessary processes or increase the memory. In other cases, contact maintenance personnel.

MEMORY

The memory is insufficient.

Terminate the unnecessary processes or increase the memory.

OTHER

An error other than that specified above occurred.

Acquire the contents of reason (aa....aa), detail (bb....bb), and inter (cc....cc), and then contact maintenance personnel.

KFCT73560-W

cannot get log control information, so using default value for -CTMLogFileSize and -CTMLogFileCount.

Description

The CTM log control information cannot be acquired.

The default value will be set up in the maximum size (specified value of the -CTMLogFileSize option of the ctmstart command) and the maximum count (specified value of the -CTMLogFileCount option of the ctmstart command) of CTM log files and the processing continues.

KFCT73561-E

cannot get log control information. reason=aa....aa detail=bb....bb inter=cc....cc.

aa....aa: Reason for occurrence of error

bb....bb: Detailed message

cc....cc: Maintenance information

Description

The log control information cannot be acquired.

The processing of the command terminates.

Action

Take action based on the reason for the error occurrence described in aa....aa. The following table lists the reasons for the error occurrence described in aa....aa and the corresponding actions.

Table 19‒40: List of causes described in KFCT73561-E

Cause of error

Cause

Action

FILE_ACC

An attempt to access the file has failed.

Confirm that the CTMSPOOL and PRFSPOOL directories exist. Also, check whether the files under the CTMSPOOL directory are edited incorrectly and whether the access permissions are changed.

NO_EXIST

The file does not exist.

After installation, check whether the ctmdmstart command, the ctmstart command, or the cprfstart command is running, or whether the files under the CTMSPOOL directory or PRFSPOOL directory are deleted incorrectly.

VERSION

The file version is unknown.

Check whether the ctmdmstart command or the ctmstart command of a version later than the ctmlogcat command is running.

Check the above details and run the ctmdmstart command or the ctmstart command of the same version as the ctmlogcat command. If the command is terminated normally, the log control information is updated and can be acquired.

KFCT73590-I

usage:ctmlogcat [-h] | [-d | -t ctmid]

Description

This message describes the usage method of the ctmlogcat command. This error message is displayed when the command format is invalid or when the -h option is specified.

If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it. If the specified option is invalid, modify the specified option, and then re-execute the command.

KFCT73591-I

no aa....aa log message to output.

aa....aa: Type of log message (domain: CTM domain log or ctm: CTM log)

Description

There is no log message to output.

The command has finished.

KFCT73592-E

the fatal error occurred, so process terminated. reason=aa....aa detail=bb....bb inter=cc....cc.

aa....aa: Reason for occurrence of error

bb....bb: Detailed message

cc....cc: Maintenance information

Description

An error occurred, so the processing terminates.

Action

Check the reason for the error occurrence described in aa....aa, and then take action.

The reason for the error occurrence described in aa....aa is described below:

MEMORY

The memory is insufficient.

Terminate the unnecessary processes or increase the memory.

OTHER

An error other than MEMORY error occurred.

Acquire the contents of reason, detail, and inter, and then contact maintenance personnel.

KFCT74000-E

command argument is invalid. option:aa....aa

aa....aa: Invalid option name

Description

The specification of the command argument is invalid.

The command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT74001-E

this processing exceeded the maximum which was specified by the CTMClientConnectCount option. the effective option value at present is aa....aa.

aa....aa: Valid option value at present

Description

The maximum value of the -CTMClientConnectCount option specified in the OTM gateway was exceeded.

The send request process will be interrupted.

The maximum value of the -CTMClientConnectCount option specified in the ORB gateway was exceeded.

The send request process will be interrupted.

Action

Check the value specified in the -CTMClientConnectCount option.

Wait for the termination of the running OTM client application, and then re-execute the command. Also, if required, increase the value specified in the -CTMClientConnectCount option, and then re-execute the command.

Wait for the termination of the running CORBA client application, and then re-execute the command. Also, if required, increase the value specified in the -CTMClientConnectCount option, and then re-execute the command.

KFCT74002-E

memory allocation error. maintenance code:aa....aa

aa....aa: Maintenance code

Description

An attempt to acquire memory has failed.

The processing will be interrupted.

Action

Contact system administrator.

Terminate the unnecessary processes or increase the memory.

KFCT74003-E

shared memory allocation error. maintenance code:aa....aa

aa....aa: Maintenance code

Description

An attempt to acquire shared memory has failed.

The processing will be interrupted.

Action

Contact system administrator.

Modify the option argument, and then re-execute the command.

KFCT74004-E

cannot assign a ctmtscgwd. reason code:aa....aa .

aa....aa: Reason code

Description

The OTM gateway is not allocated to the OTM client application.

Action

Adjust the number of OTM client applications and the number of OTM gateways according to the reason codes described in aa....aa.

Table 19‒41: List of reason codes displayed in KFCT74004-E

Reason code

Cause

Action

1

The OTM gateway is not connected to the CTM daemon.

Check whether the OTM gateway is connected to the CTM daemon.

2

There are no free connections in the OTM gateway connected to the CTM daemon.

Check the number of OTM client applications.

KFCT74550-E

scheduler initialization error. reason code=aa....aa

aa....aa: Reason code

Description

An attempt to initialize has failed.

The startup process of the CTM daemon terminates with an error.

Action

Based on the list of reason codes described in the following table, investigate the cause, and then remove the cause of the error. Then re-execute the command.

Table 19‒42: List of reason codes displayed in KFCT74550-E

Reason code

Cause

1

An option argument analysis error occurred.

2

The shared memory is insufficient.

3

Memory is insufficient.

4

An error occurred in the initialization process of the communication environment.

KFCT74551-E

command option is invalid. option:aa....aa

aa....aa: Option name

Description

The argument of the command option is invalid.

The processing will be interrupted.

Action

Check whether the specified option is invalid.

Modify the specified option, and then re-execute the command.

KFCT74552-E

memory allocation error. maintenance code:aa....aa

aa....aa: Maintenance code

Description

Memory is insufficient.

The processing will be interrupted.

Action

Contact system administrator.

Terminate the unnecessary processes or increase the memory.

KFCT74553-E

shared memory allocation error. maintenance code:aa....aa

aa....aa: Maintenance code

Description

An attempt to secure the shared memory has failed.

The processing will be interrupted.

Action

Contact system administrator.

Modify the option argument, and then re-execute the command.

KFCT74554-E

cache memory allocation error. allocation size=aa....aa maintenance code:bb....bb

aa....aa: Size that the user tried to secure

bb....bb: Maintenance code

Description

An attempt to secure the server cache memory of the CTM daemon has failed.

The processing will be interrupted.

Action

Contact system administrator.

Modify the argument of the -CTMServerCacheSize option in the ctmstart command, and then re-execute the command.

KFCT74555-W

this processing exceeded the maximum request registration. CTM queue name:aa....aa reason code:bb....bb

aa....aa: CTM queue name

bb....bb: Reason code (Max_Request: Value specified in the -CTMMaxRequestCount option of the ctmstart command was exceeded, so the request cannot be registered)

Description

The maximum number of requests registered in the CTM queue was exceeded, so the request is not registered.

The processing continues.

This message is displayed for each CTM queue. After this message is displayed, the message will not be displayed for the same CTM queue for 60 seconds.

Action

Use the ctmlsque command and check the number of registered requests.

If the service processes registered in the J2EE application are being delayed, remove the cause of the problem.

If the processing capability of the J2EE application is inadequate, increase the number of concurrent executions of schedule queues or the J2EE servers with the same J2EE application, revise the value specified in the -CTMMaxRequestCount option of the ctmstart command, and then restart the CTM daemon.

KFCT74556-E

cannot return the reply of the request. client ip:aa....aa client pid:bb....bb communication no:cc....cc,dd....dd

aa....aa: Client IP address of a destroyed request

bb....bb: Client process ID of destroyed request

cc....cc: Maintenance information 1

dd....dd: Maintenance information 2

Description

The response of the request cannot be returned. The processing continues.

Action

Increase the regulator process count.

KFCT74557-W

decline in the rate of processing was detected by the stay watch function. CTM queue name : aa....aa decision data : bb....bb/cc....cc/dd....dd/ee....ee/ff....ff/gg....gg

aa....aa: CTM queue name

bb....bb: Request accumulation count when checked just before stopping the system

cc....cc: Number of requests processed within the monitoring time

dd....dd: Monitoring state transition threshold value

ee....ee: System termination transition threshold value

ff....ff: Monitoring time interval

gg....gg: Termination mode

Description

A decline in the processing rate was detected by the stay watch functionality of the schedule queue.

Action

See the PRF trace file and statistical information file, track the reason due to which the process cannot be executed, and then revise the queue stay watch settings.

KFCT74558-E

cannot increase thread. CTMDispatchParallelCount=aa....aa. CTM queue name:bb....bb change count=cc....cc reason code:dd....dd

aa....aa: Upper limit of the thread count that can be managed with the CTM daemon

bb....bb: CTM queue name

cc....cc: Current execution count specified with the ctmchpara command

dd....dd: Reason code

ParallelCount: The upper limit of the number of threads that can be started in one J2EE server was exceeded.

DispatchParallelCount: The upper limit of the number of threads that can be managed with the CTM daemon was exceeded.

Description

The upper limit of the threads distributed to a J2EE server in the CTM daemon has exceeded the number of concurrent executions specified with the ctmchpara command.

The change process will not be executed by the ctmchpara command.

Action

Check the following details for each reason code described in dd....dd, and then take the corresponding actions:

ParallelCount

Specify a value that does not exceed the upper limit of the number of threads that can run on one J2EE server ((127) × share count of a schedule queue) in the ctmchpara command.

DispatchParallelCount

Specify a value that does not exceed aa....aa in the ctmchpara command or revise the concurrent execution count of another queue.

KFCT74559-E

cannot change the ParallelCount.error code=aa....aa maintenance code1=bb....bb maintenance code2=cc....cc

aa....aa: Maintenance error code

bb....bb: Maintenance code1

cc....cc: Maintenance code2

Description

An error occurred while changing the number of concurrent executions.

The processing will be interrupted without performing the change process using the ctmchpara command.

Action

Confirm the following details, and then take action:

The value specified in the maximum value of the EJB pool count is Unlimited or a value of 127 or more is not specified

Set the maximum value of the EJB pool count as Unlimited or 127 or more, and then restart the J2EE application.

Does the ejbCreate() method consume time internally?

Set a large value for the value in the ejbserver.ctm.ActivateTimeOut property, and then restart the J2EE application.

Are the threads insufficient?

Increase the settings for the upper limit of the thread resources.

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

KFCT74600-I

aa....aa is placed in shutdown state by bb....bb.

aa....aa: Locked CTM queue name

bb....bb: Lock mode

normal: Normal lock

force: Forced lock

timeout: Timeout lock

Description

The schedule of the CTM queue (aa....aa) is locked.

Action

Check the following details for each lock mode described in bb....bb, and then take actions:

In the case of normal or force

The schedule was locked by the ctmholdque command.

Execute the ctmrlesque command to release the lock.

In the case of timeout

The schedule is locked by the timeout lock functionality.

Investigate the cause for the occurrence of timeout and to release the lock, execute the ctmrlesque command.

KFCT74601-I

aa....aa restarted.

aa....aa: Name of the CTM queue for which the lock was released

Description

The schedule of the CTM queue (aa....aa) was unlocked.

KFCT74604-I

the ParallelCount of aa....aa was changed to bb....bb.

aa....aa: CTM queue name

bb....bb: Valid value of the number of concurrent executions after change

Description

The number of concurrent executions of the CTM queue (aa....aa) was changed to bb....bb.

KFCT74700-E

aa....aa command is used invalidly.

aa....aa: Command name

Description

The usage method of the command (aa....aa) is invalid.

The command terminates with an error.

Action

Check whether the option specified in the command is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT74701-E

error occurred during aa....aa command processing. reason code=bb....bb

aa....aa: Command name

bb....bb: Reason code

Description

An error occurred during the command process.

The command terminates with an error.

Action

Based on the list of reason codes described in the following table, investigate the cause, and then remove the cause of the error. Then re-execute the command.

Table 19‒43: List of reason codes displayed in KFCT74701-E

Reason code

Cause

1

The CTM daemon is not running.

2

An attempt to secure the shared memory has failed.

3

A timeout occurred.

4

A communication error occurred.

5

An attempt to secure the process-specific memory has failed.

6

The version does not match with that of the CTM daemon.

7

The upper limit of threads that can be generated in the CTM daemon was exceeded.

8

An attempt to add threads in the CTM daemon has failed.

9

An attempted exclusive processing in the CTM daemon has failed.

10

An internal contradiction occurred.

11

The ctmstart -CTMQueueDeleteWait is valid, so the command is not accepted.

KFCT74702-E

aa....aa specified with bb....bb command do not match.

aa....aa: Command name

bb....bb: Option argument name

Description

The argument (bb....bb) of the option specified in the (aa....aa) command is invalid.

The command terminates with an error.

Action

Check the argument of the option.

Modify the specified option, and then re-execute the command.

KFCT74703-E

aa....aa specified with ctmholdque command is already in shutdown state. CTMDomain:bb....bb CTMID:cc....cc

aa....aa: CTM queue name

bb....bb: CTM domain name

cc....cc: CTM identifier

Description

The CTM queue specified with the ctmholdque command is locked.

The command terminates with an error.

Action

Check the argument of the option.

Modify the specified option, and then re-execute the command.

KFCT74704-E

failed in placing all ctm_queue in shutdown state. CTMDomain:aa....aa CTMID:bb....bb

aa....aa: CTM domain name

bb....bb: CTM identifier

Description

An error occurred in the locking process of all the CTM queues.

The command terminates with an error.

Action

Check the argument of the option.

Modify the specified option, and then re-execute the command.

KFCT74705-E

aa....aa specified with ctmrlesque command is not in shutdown state. CTMDomain:bb....bb CTMID:cc....cc

aa....aa: CTM queue name

bb....bb: CTM domain name

cc....cc: CTM identifier

Description

The CTM queue specified in the ctmrlesque command is not blocked.

The command terminates with an error.

Action

Check the argument of the option.

Modify the specified option, and then re-execute the command.

KFCT74706-E

failed restarting all ctm_queue in shutdown state. CTMDomain:aa....aa CTMID:bb....bb

aa....aa: CTM domain name

bb....bb: CTM identifier

Description

An error occurred in the lock releasing process of all the CTM queues.

The command terminates with an error.

Action

Check the argument of the option.

Modify the specified option, and then re-execute the command.

KFCT74750-I

usage:ctmlsque [-CTMDomain domain_name] [-CTMID ctmid]

[-CTMQueue CTM queue name] [-CTMMyHost host_name] [-CTMInterface [interface_name]]

[-CSV] [-CTMAppInfo][-h]

Description

This message describes the usage method of the ctmlsque command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT74752-I

usage:ctmholdque [-CTMDomain domain_name][-CTMID ctmid]

{-CTMQueue CTM queue name | -CTMQueueALL} [-CTMMyHost host_name]

[[-CTMRequestLeave] [-CTMTimeOut time] | [-CTMChangeServer]] [-CTMForce] [-h]

Description

This message describes the usage method of the ctmholdque command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT74753-I

usage:ctmrlesque [-CTMDomain domain_name] [-CTMID ctmid]

{-CTMQueue CTM queue name | -CTMQueueALL} [-CTMMyHost host_name] [-h]

Description

This message describes the usage method of the ctmrlesque command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT74755-I

usage:ctmchpara [-CTMDomain domain_name] [-CTMID ctmid]

[-CTMMyHost host_name] [-CTMTimeOut time] -CTMQueue CTM queue name

-CTMChangeCount count [-h]

Description

This message describes the usage method of the ctmchpara command. This error message is displayed when the command format is invalid or when the -h option is specified.

If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT75000-E

command argument is invalid. option name:aa....aa

aa....aa: Invalid option name

Description

The specification of the command argument is invalid.

The command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT75001-E

this processing exceeded the maximum which was specified by the CTMClientConnectCount option. the effective option value at present is aa....aa.

aa....aa: Valid option value at present

Description

The maximum value specified in the -CTMClientConnectCount option was exceeded.

The startup of the CTM regulator or the OTM gateway will be interrupted.

Action

Check the value specified in the -CTMClientConnectCount option.

Wait for a running CTM regulator or an OTM gateway to terminate, and then re-execute the command. Also, if required, modify the -CTMClientConnectCount option, and then re-execute the command.

KFCT75002-E

this processing exceeded the maximum which was specified by the CTMServerConnectCount option. The effective option value at present is aa....aa.

aa....aa: Valid option value at present

Description

The maximum value specified in the -CTMServerConnectCount option was exceeded.

The processing of the J2EE server will be interrupted.

Action

Check the value specified in the -CTMServerConnectCount option.

If required, modify the value specified in the -CTMServerConnectCount option, and then re-execute the command.

KFCT75003-E

the error occurred in the initialization processing of CTM-daemon. error code=aa....aa maintenance code1=bb....bb maintenance code2=cc....cc

aa....aa: Maintenance error code

bb....bb: Maintenance code1

cc....cc: Maintenance code2

Description

An error occurred in the initialization process of the CTM daemon.

The processing will now stop.

Action

Contact system administrator.

The System Administrator needs to investigate the cause of abnormal termination, and then restart the CTM daemon.

KFCT75004-E

the error occurred by the lock control processing of the shared memory access.

Description

An error occurred during the exclusive control processing of shared memory access.

The processing will now stop.

Action

Contact system administrator.

Modify the option argument, and then re-execute the command.

KFCT75005-E

the error occurred by the registration processing of a communication object. error code=aa....aa maintenance code1=bb....bb maintenance code2=cc....cc

aa....aa: Maintenance error code

bb....bb: Maintenance code1

cc....cc: Maintenance code2

Description

An error occurred while registering the communication object.

The processing will now stop.

Action

Confirm the following details, and then take action:

Is osagent abended?

Restart osagent, and then re-execute the command.

Is osagent overloaded?

Terminate the unnecessary processes.

Is the memory insufficient?

Increase the memory, if required.

KFCT75050-E

the error occurred by the lock acquisition processing of the lock resources. error code=aa....aa maintenance code1=bb....bb maintenance code2=cc....cc

aa....aa: Maintenance error code

bb....bb: Maintenance code1

cc....cc: Maintenance code2

Description

An error occurred during the lock acquisition process for the lock resources.

The processing will now stop.

Action

Check whether the memory is insufficient.

If the memory is insufficient, either terminate the unnecessary processes or increase the memory.

KFCT75051-E

the error occurred by the lock release processing of the lock resources. error code=aa....aa maintenance code1=bb....bb maintenance code2=cc....cc

aa....aa: Maintenance error code

bb....bb: Maintenance code1

cc....cc: Maintenance code2

Description

An error occurred during the lock release processing of the lock resources.

The processing will now stop.

Action

Check whether the memory is insufficient.

If the memory is insufficient, either terminate the unnecessary processes or increase the memory.

KFCT75052-E

the error occurred by the generation processing of a thread. error code=aa....aa maintenance code1=bb....bb maintenance code2=cc....cc

aa....aa: Maintenance error code

bb....bb: Maintenance code1

cc....cc: Maintenance code2

Description

An error occurred while generating threads.

The processing will now stop.

Action

Confirm the following details, and then take action:

Are the thread resources insufficient?

Increase the settings for the upper limit of the thread resources.

Is the memory insufficient?

Terminate the unnecessary processes or increase the memory.

KFCT75053-E

the memory allocation failed. maintenance code1=aa....aa maintenance code2=bb....bb

aa....aa: Maintenance code1

bb....bb: Maintenance code2

Description

An attempt to allocate memory has failed.

The processing will now stop.

Action

Check whether the memory is insufficient.

If the memory is insufficient, either terminate the unnecessary processes or increase the memory, if required.

KFCT75054-E

the error occurred by the generation processing of lock resources. error code=aa....aa maintenance code1=bb....bb maintenance code2=cc....cc

aa....aa: Maintenance error code

bb....bb: Maintenance code1

cc....cc: Maintenance code2

Description

An error occurred while generating the lock resources.

The processing will now stop.

Action

Check whether the memory is insufficient.

If the memory is insufficient, either terminate the unnecessary processes or increase the memory, if required.

KFCT75122-E

the error occurred in the deactivation processing of CTM queue. Queue name:aa....aa maintenance code=bb....bb

aa....aa: CTM queue name

bb....bb: Maintenance information

Description

An error occurred while locking the CTM queue (aa....aa).

The processing continues.

Action

See the message KFCT75499-E, and then remove the cause of the error. If the cause of the error is unknown, acquire the maintenance code, and then contact maintenance personnel.

KFCT75127-W

the length of CTM queue is already specified. name=aa....aa set length=bb....bb activate length=cc....cc.

aa....aa: CTM queue name

bb....bb: Length of the CTM queue specified in the J2EE server

cc....cc: Length of the generated CTM queue

Description

CTM queues have been generated with different lengths. The length of the generated CTM queue will become valid.

The processing continues.

Action

If you want to create a CTM queue with the specified length, either specify a different CTM queue name, or delete the target CTM queue, and then re-execute the command.

KFCT75201-E

invalid argument value is specified. name=aa....aa, bb....bb=cc....cc.

aa....aa: Method name

bb....bb: Argument name

cc....cc: Specified value

Description

The specified value (cc....cc) of argument (bb....bb) of method (aa....aa) is invalid.

The processing will now stop.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KFCT75202-E

cannot get property. name=aa....aa.

aa....aa: Property name

Description

An attempt to acquire the property (aa....aa) has failed.

The processing will now stop.

Action

Acquire the maintenance information, and then contact System Administrator.

KFCT75204-E

invalid property value is specified. aa....aa=bb....bb.

aa....aa: Property name

bb....bb: Property value

Description

An attempt to acquire the property value (bb....bb) has failed.

The processing will now stop.

Action

Contact system administrator.

The System Administrator needs to modify the specified value of the property, and then re-execute the command.

KFCT75206-E

internal error occurred. name=aa....aa.

aa....aa: Maintenance information

Description

An internal contradiction occurred.

The processing will now stop.

Action

Contact system administrator.

KFCT75207-E

it has already created CTM queue. name=aa....aa.

aa....aa: CTM queue name

Description

The specified CTM queue (aa....aa) is already generated.

The processing will now stop.

Action

Contact system administrator.

Restart the J2EE application after the system administrator changes the CTM queue name.

KFCT75208-E

an error occurred in the communication CTM-daemon. reason=aa....aa. mainteance code=bb....bb.

aa....aa: Reason code

bb....bb: Maintenance code

Description

An error occurred in the communication with the CTM daemon.

The processing will now stop.

Action

Contact system administrator.

The System Administrator needs to check the reason codes described in aa....aa, and then take action. The reason codes described in aa....aa are as follows:

DAEMON_FAILURE

An error occurred in the daemon.

See the message KFCT75499-E, and then remove the cause of the error. Take action, and then re-execute the command.

SEND_FAILURE

An error occurred during the communication with the daemon.

Confirm that the CTM daemon is running.

TIMED_OUT

A timeout occurred during the communication with the daemon.

If required, increase the value of ejbserver.ctm.ActivateTimeOut key and ejbserver.ctm.DeactivateTimeOut key, and then re-execute the process.

KFCT75209-E

the specified JNDI lookup name has already been registered. name=aa....aa.

aa....aa: JNDI lookup name

Description

The specified JNDI lookup name (aa....aa) is registered.

The processing will now stop.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KFCT75210-E

the specified JNDI lookup name is not existed. name=aa....aa.

aa....aa: JNDI lookup name

Description

The specified JNDI lookup name (aa....aa) does not exist.

The processing will now stop.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KFCT75211-E

Stateless Session Bean is not registered in CTM queue. name=aa....aa.

aa....aa: CTM queue name

Description

The Stateless Session Bean is not registered in the CTM queue (aa....aa).

The processing will now stop.

Action

Acquire the maintenance information, and then contact maintenance personnel.

KFCT75212-I

the activation of CTM queue is completed. name=aa....aa.

aa....aa: CTM queue name

Description

The activation of the CTM queue (aa....aa) is finished.

The processing continues.

KFCT75213-I

the deactivation of CTM queue is completed. name=aa....aa.

aa....aa: CTM queue name

Description

The deactivation of the CTM queue (aa....aa) is finished.

The processing continues.

KFCT75214-E

the error occurred in activation of CTM queue. name=aa....aa.

aa....aa: CTM queue name

Description

An error occurred in the activation of the CTM queue (aa....aa).

The startup process of the J2EE application will be interrupted.

Action

Contact system administrator.

The System Administrator needs to see the message KFCT75499-E, and then remove the cause of the error. Remove the cause of the error, and then re-execute the process.

KFCT75215-E

the error occurred in deactivation of CTM queue. name=aa....aa.

aa....aa: CTM queue name

Description

An error occurred in the deactivation of the CTM queue (aa....aa).

The termination process of the J2EE application will be interrupted.

Action

Contact system administrator.

The System Administrator needs to see the message KFCT75499-E, and then remove the cause of the error. Remove the cause of the error, and then re-execute the process.

If the error recurs, the connection with the CTM daemon may have failed. Confirm that the CTM daemon is running.

KFCT75216-E

invalid version protocol. reason=aa....aa.

aa....aa: Reason code

Description

The versions in the CTM communication protocol are incompatible.

The processing will now stop.

Action

Acquire the maintenance information, and then contact System Administrator.

The System Administrator needs to see the reason codes described in aa....aa, and then take action. The reason codes described in aa....aa are as follows:

INCOMPATIBLE

The protocol versions are incompatible.

There is a version mismatch in the CTM system daemons or in the application programs included in the same CTM domain. Recheck the versions.

NOT_IGNORE

Information that cannot be ignored exists in the communication protocol.

In some functions, the version of the processes described in the location code does not match with the versions of other processes. Recheck the versions.

KFCT75217-I

the connecting to CTM-daemon is started. CTMDomain=aa....aa CTMID=bb....bb.

aa....aa: CTM domain name

bb....bb: CTM identifier

Description

The process of connecting to the CTM daemon is started.

The processing continues.

KFCT75218-I

the connection to CTM-daemon is completed. CTMDomain=aa....aa CTMID=bb....bb.

aa....aa: CTM domain name

bb....bb: CTM identifier

Description

The connection to the CTM daemon is complete.

The processing continues.

KFCT75219-E

the connection to CTM-daemon is failed. CTMDomain=aa....aa CTMID=bb....bb.

aa....aa: CTM domain name

bb....bb: CTM identifier

Description

An attempt to connect to the CTM daemon has failed.

The processing will now stop.

Action

Contact system administrator.

The System Administrator needs to see the message KFCT75499-E, and then remove the cause of the error. After the cause of the error is removed, restart the J2EE server.

KFCT75220-I

the connecting from J2EE server is started. name=aa....aa conn_id=bb....bb.

aa....aa: The J2EE server name

bb....bb: Connection identifier

Description

The process of connecting to the CTM daemon is starting.

The processing continues.

KFCT75221-I

the connection from J2EE server is completed. name=aa....aa conn_id=bb....bb.

aa....aa: The J2EE server name

bb....bb: Connection identifier

Description

The process of connecting to the CTM daemon is finished.

The processing continues.

KFCT75222-E

the connection from J2EE server is failed. name=aa....aa conn_id=bb....bb.

aa....aa: The J2EE server name

bb....bb: Connection identifier

Description

An attempt to connect to the CTM daemon has failed.

The processing will now stop.

Action

Contact system administrator.

The System Administrator needs to see the message KFCT75499-E, and then remove the cause of the error. After the cause of the error is removed, restart the J2EE server.

KFCT75223-I

the activation of CTM queue is started. name=aa....aa.

aa....aa: CTM queue name

Description

The activation of the CTM queue (aa....aa) is starting.

The processing continues.

KFCT75224-I

the activation of CTM queue from J2EE server is started. name=aa....aa conn_id=bb....bb.

aa....aa: CTM queue name

bb....bb: Connection identifier

Description

The activation of the CTM queue (aa....aa) in the CTM daemon is starting.

The processing continues.

KFCT75225-I

the activation of CTM queue from J2EE server is completed. name=aa....aa conn_id=bb....bb.

aa....aa: CTM queue name

bb....bb: Connection identifier

Description

The activation of the CTM queue (aa....aa) in the CTM daemon has finished.

The processing continues.

KFCT75226-E

the activation of CTM queue from J2EE server is failed. name=aa....aa conn_id=bb....bb.

aa....aa: CTM queue name

bb....bb: Connection identifier

Description

An attempt to activate the CTM queue (aa....aa) in the CTM daemon has failed.

The startup process of the J2EE application will be interrupted.

Action

Contact system administrator.

The System Administrator needs to see the message KFCT75499-E, and then remove the cause of the error. After the cause of the error is removed, restart the J2EE application.

KFCT75227-I

the deactivation of CTM queue is started. name=aa....aa.

aa....aa: CTM queue name

Description

The deactivation of the CTM queue (aa....aa) is starting.

The processing continues.

KFCT75228-I

the deactivation of CTM queue from J2EE server is started. conn_id=aa....aa.

aa....aa: Connection identifier

Description

The deactivation of the CTM queue in the CTM daemon is starting.

The processing continues.

KFCT75229-I

the deactivation of CTM queue from J2EE server is completed. conn_id=aa....aa.

aa....aa: Connection identifier

Description

The deactivation of the CTM queue in the CTM daemon is complete.

The processing continues.

KFCT75230-E

the deactivation of CTM queue from J2EE server is failed. conn_id=aa....aa.

aa....aa: Connection identifier

Description

An attempt to deactivate the CTM queue in the CTM daemon has failed.

The termination process of the J2EE application will be interrupted.

Action

Contact system administrator.

The System Administrator needs to see the message KFCT75499-E, and then remove the cause of the error. After the cause of the error is removed, re-execute the deactivation of the CTM queue.

If an attempt to deactivate the CTM queue fails again, the connection with the CTM daemon may have failed. Confirm whether the CTM daemon exists.

KFCT75231-I

the disconnecting to CTM-daemon is started. CTMDomain=aa....aa CTMID=bb....bb.

aa....aa: CTM domain name

bb....bb: CTM identifier

Description

The process of disconnecting the CTM daemon has started.

The processing continues.

KFCT75232-I

the disconnection to CTM-daemon is completed. CTMDomain=aa....aa CTMID=bb....bb.

aa....aa: CTM domain name

bb....bb: CTM identifier

Description

The process of disconnecting the CTM daemon has finished.

The processing continues.

KFCT75233-E

the disconnection to CTM-daemon is failed. CTMDomain=aa....aa CTMID=bb....bb.

aa....aa: CTM domain name

bb....bb: CTM identifier

Description

An attempt to disconnect the CTM daemon has failed.

The processing continues.

Action

Contact system administrator.

The System Administrator needs to see the message KFCT75499-E, and then remove the cause of the error.

KFCT75234-I

the disconnecting from J2EE server is started. name=aa....aa conn_id=bb....bb.

aa....aa: The J2EE server name

bb....bb: Connection identifier

Description

The disconnection process is starting in the CTM daemon.

The processing continues.

KFCT75235-I

the disconnection from J2EE server is completed. name=aa....aa conn_id=bb....bb.

aa....aa: The J2EE server name

bb....bb: Connection identifier

Description

The process of disconnecting the CTM daemon has finished.

The processing continues.

KFCT75236-E

the disconnection from J2EE server is failed. name=aa....aa conn_id=bb....bb.

aa....aa: The J2EE server name

bb....bb: Connection identifier

Description

An attempt to disconnect the CTM daemon has failed.

The processing continues.

Action

Contact system administrator.

The System Administrator needs to see the message KFCT75499-E, and then remove the cause of the error.

KFCT75237-W

the connection down from J2EE server is detected. conn_id=aa....aa.

aa....aa: Connection identifier

Description

The disconnection from the J2EE server was detected.

The processing continues.

KFCT75238-W

the deactivation of CTM queue is not completed in terminating J2EE server. maintenance code=aa....aa.

aa....aa: Maintenance information

Description

An attempt was made to stop the J2EE server when the deactivation of the CTM queue had not finished.

The processing continues.

An error will occur in the connection between the J2EE server and the CTM daemon and the termination process of the J2EE application might not end normally.

Action

Contact system administrator.

The System Administrator needs to confirm that the CTM daemon exists.

KFCT75239-W

it is already active in destroying CTM queue. name=aa....aa.

aa....aa: CTM queue name

Description

An attempt was made to delete the CTM queue when the CTM queue (aa....aa) was active.

The processing continues.

An error will occur in the connection between the J2EE server and the CTM daemon and the termination process of the J2EE application might not end normally.

Action

Contact system administrator.

The System Administrator needs to confirm that the CTM daemon exists.

KFCT75300-E

the combination of JNDI lookup name and interface name is invalid.

JNDI lookup name=aa....aa.

registered interface=bb....bb registering interface=cc....cc.

aa....aa: JNDI lookup name

bb....bb: Registered interface name

cc....cc: Interface name that the user tried to register

Description

The combination of JNDI look-up name and interface name differs from the already registered combination.

The processing of the method will be interrupted.

Action

Check the combination of the JNDI look-up name and interface name. Modify the combination, and then re-execute the process.

KFCT75303-E

the registration to Naming Service is failed. JNDI lookup name=aa....aa maintenance code=bb....bb.

aa....aa: Failed JNDI lookup name

bb....bb: Maintenance information

Description

An attempt to register to the CORBA Naming Service has failed.

The processing will now stop.

Action

Check the contents that are displayed in the details, resolve the problem, and then re-execute the operation:

Confirm that INS is running.

Before starting the CTM daemon, confirm that the JNDI look-up name to be registered is not already registered.

Confirm that the INS registration name is valid.

KFCT75305-E

the removal from Naming Service is failed. JNDI lookup name=aa....aa maintenance code=bb....bb.

aa....aa: Failed JNDI lookup name

bb....bb: Maintenance information

Description

An attempt to delete from the CORBA Naming Service has failed.

The processing continues.

Action

Check whether the global CORBA Naming Service is running.

KFCT75306-E

the connection failure between aa....aa and CTM-daemon. maintenance code1=bb....bb maintenance code2=cc....cc.

aa....aa: Process in which disconnection was detected

CTM-regulator: CTM regulator process

OTM-gateway: OTM gateway process

bb....bb: Maintenance information 1

cc....cc: Maintenance information 2

Description

A disconnection with the CTM daemon was detected.

The processing will now stop.

Action

Contact system administrator.

KFCT75307-E

the timeout occurred. server pid=aa....aa JNDI lookup name=bb....bb interface=cc....cc operation=dd....dd.

aa....aa: Server process ID to be connected

bb....bb: JNDI lookup name

cc....cc: Interface name

dd....dd: Operation name

Description

A timeout was detected.

The processing will now stop.

Action

Contact system administrator.

The System Administrator needs to investigate the cause for the occurrence of timeout, and then restart the CTM or the J2EE server.

KFCT75492-W

the CORBA exception was thrown in user application. class name:aa....aa minor=bb....bb completed=cc....cc

aa....aa: CORBA exception class name

If the CORBA exception class name cannot be acquired, **** will be displayed.

bb....bb: Minor code of CORBA exception

cc....cc: Completion status of the CORBA exception process

Description

A CORBA exception was thrown.

The exception information will be output and then the processing continues.

Action

Acquire the CORBA exception class name, minor code of CORBA exception, and the completion status of CORBA exception process and then investigate the cause.

KFCT75499-E

a system exception occurred. error code=aa....aa detail code=bb....bb place code=cc....cc completion status=dd....dd maintenance code=ee....ee,ff....ff,gg....gg,hh....hh.

aa....aa: Error code

bb....bb: Details code

cc....cc: Place code

dd....dd: Completion status

ee....ee: Maintenance code 1

ff....ff: Maintenance code 2

gg....gg: Maintenance code 3

hh....hh: Maintenance code 4

Description

An exception is thrown in the system.

One of the following processes will be executed depending upon the importance level of the error:

The processing discontinues and the process will be abended.

The processing discontinues and the process returns to the invocation source of the service being executed.

The processing continues as it is.

Action

Contact system administrator.

The System Administrator must see the error code and content code to remove the cause of the error. For details on the error code and content code, see 19.4.1 List of error codes, and 19.4.4 List of content codes. If the cause of the error is unknown, obtain the maintenance code, and then contact maintenance personnel.

KFCT75500-E

aa....aa(bb....bb) is failed.errno=cc....cc:dd....dd

aa....aa: System call in which the error occurred

bb....bb: Maintenance information

cc....cc: errno value of the system call

dd....dd: Details of system call error

Description

An error occurred in the system call (aa....aa).

One of the following processes will be executed depending upon the importance level of the error:

The processing discontinues and the process will be abended.

The processing discontinues and the process will return to the invocation source of the service being executed.

The processing continues as it is.

Action

Based on the system call name and errno value, investigate the cause in the system call reference manual of the appropriate OS.

KFCT75800-E

an exception occurred. code=aa....aa ExpAddr:bb....bb

aa....aa: Exception code

bb....bb: Address in which an exception was thrown

Description

A structured exception of the code aa....aa was thrown during the execution of the bb....bb command.

The stack trace will be acquired and the processing will be interrupted.

Action

Contact system administrator.

KFCT75999-E

aa....aa(bb....bb) killed by code=cc....cc

aa....aa: Internal process code that detected the error

bb....bb: Terminated process ID

cc....cc: Abort code (Abnormal termination reason code )

Description

The CTM and PRF service was terminated since an error occurred.

One of the following processes will be executed depending upon the importance level of the error:

CTM domain manager process will be abended.

The CTM daemon process will be abended.

The CTM regulator process will be abended.

The OTM gateway process will be abended.

The PRF daemon process will be abended.

The EJB client application process will be abended.

The J2EE server process will be abended.

Action

Contact system administrator.

Investigate the abnormal termination reason code, and then restart the application programs of CTM, PRF, or EJB. For details on the abort code, see 19.5 List of abort codes.

KFCT76000-I

usage:ctmver -h | file_path

Description

This message describes the usage method of the ctmver command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT76001-I

usage:ctmjver -h | file_path

Description

This message describes the usage method of the ctmjver command.

This error message is displayed when the command format is invalid or when the -h option is specified. If the command format is invalid, the command terminates with an error.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT76002-E

the memory allocation failed.

Description

An attempt to allocate memory has failed.

The processing will now stop.

Action

Check whether the memory is insufficient.

If the memory is insufficient, either terminate the unnecessary processes or increase the memory, if required.

KFCT76003-E

the setting of an environment variable is unreasonable. environment variable name:aa....aa

aa....aa: Invalid environment variable name

Description

The specified environment variable (aa....aa) is invalid.

The processing will now stop.

Action

Check whether the specified environment variable is invalid and, if necessary, revise it.

Modify the specified environment variable, and then re-execute the command.

KFCT76004-E

the specified file path is unreasonable. file path:aa....aa

aa....aa: Invalid file path name

Description

The specified file path (aa....aa) is invalid.

The processing will now stop.

Action

Check whether the specified file path is invalid and, if necessary, revise it.

Modify the specified file path, and then re-execute the command.

KFCT76005-E

the specified file path is too long.

Description

The specified file path is too long.

The processing will now stop.

Action

Check whether the character string length of the specified file path has exceeded 255 bytes and, if necessary, revise it.

Modify the specified file path, and then re-execute the command.

KFCT76006-E

command argument is invalid.

Description

An invalid value is specified in the command argument.

The processing will now stop.

Action

Check whether the specified option is invalid and, if necessary, revise it.

Modify the specified option, and then re-execute the command.

KFCT76007-E

the specified file path doesn't exist. file path:aa....aa

aa....aa: Specified file path name

Description

The specified file path (aa....aa) does not exist.

The command terminates with an error.

Action

Check whether the specified file path is invalid and, if necessary, revise it.

Modify the specified file path, and then re-execute the command.

KFCT76008-E

the version information doesn't exist in the specified file path.

Description

The version information does not exist in the specified file path.

The command terminates with an error.

Action

Check whether the specified file path is invalid and, if necessary, revise it.

Modify the specified file path, and then re-execute the command.

KFCT76009-E

permission denied. file path:aa....aa

aa....aa: Specified file path name

Description

There is no permission to access the specified file.

The command terminates with an error.

Action

Revise the access permissions of the specified file path.

Use the chmod command to modify the access permissions of the file path, and then re-execute the command.

KFCT76010-E

cannot get version information. reason code=aa....aa

aa....aa: Reason code

Description

An error occurred while acquiring the version information.

The command terminates with an error.

Action

Take action based on the reason codes described in aa....aa. The following table lists the reason codes described in aa....aa and the corresponding actions.

Table 19‒44: List of reason codes described in KFCT76010-E

Reason code

Cause

Action

1

The settings of the environment variable CTMDIR are invalid.

Modify the environment variable CTMDIR appropriately.

2

An attempt to install has failed.

Re-install the Java application.

3

The settings of the environment variable CTMDIR are invalid or the installation has failed.

Modify the environment variable CTMDIR appropriately. Otherwise, re-install the Java application.

KFCT76014-E

the wrong library was loaded. Name:aa....aa PP-No:bb....bb Version:cc....cc

aa....aa: Library file name

bb....bb: Product code

cc....cc: Product version

Description

An invalid library was loaded.

The processing of the daemon and the command will be interrupted.

Action

Revise the settings for the installation environment and the environment variable. Modify the settings, and then re-execute the command.

19.4 Details of KFCT messages

This section describes the error code, place code, completed status, and content codes of the messages output in the message KFCT75499-E.

19.4.1 List of error codes

The following table lists and describes the error codes indicating the error types when KFCT75499-E is output. This message is output by CTM.

Table 19‒45: List of error codes

Value

Error code

Meaning

1

BAD_PARAM

See the CORBA exception.

2

NO_MEMORY

3

COMM_FAILURE

4

NO_PERMISSION

5

INTERNAL

6

MARSHAL

7

INITIALIZE

8

NO_IMPLEMENT

9

BAD_OPERATION

10

NO_RESOURCES

11

NO_RESPONSE

12

BAD_INV_ORDER

13

TRANSIENT

14

OBJECT_NOT_EXISTS

15

UNKNOWN

16

INV_OBJREF

17

IMP_LIMIT

18

BAD_TYPECODE

19

PERSIST_STORE

20

FREE_MEM

21

INV_IDENT

22

INV_FLAG

23

INTF_REPOS

24

BAD_CONTEXT

25

OBJ_ADAPTER

26

DATA_CONVERSION

27

TRANSACTION_REQUIRED

28

TRANSACTION_ROLLEDBACK

29

INVALID_TRANSACTION

30

INV_POLICY

31

CODESET_INCOMPATIBLE

32

REBIND

33

TIMEOUT

34

TRANSACTION_UNAVAILABLE

35

TRANSACTION_MODE

36

BAD_QOS

19.4.2 List of place codes

The place code is a value indicating the error location in CTM. The following table lists and describes the place codes.

Table 19‒46: List of place codes

Value

Place code

Location

1

PLACE_CODE_USER_AP

J2EE application

2

PLACE_CODE_SERV

J2EE server

3

PLACE_CODE_DAEMON

CTM daemon

4

PLACE_CODE_CLNT

CTM client functionality

9

PLACE_CODE_EJBREG

CTM regulator

19.4.3 List of completed statuses

The completed status is a value that indicates whether the method invocation was complete when the error occurred. The following table lists and describes the completed statuses.

Table 19‒47: List of completed statuses

Value

Completed status

Description

-1

COMPLETED_NO

Method invocation is not complete.

0

COMPLETED_MAYBE

The completed status of method invocation cannot be determined.

1

COMPLETED_YES

Method invocation is complete.

19.4.4 List of content codes

This subsection describes the content codes used for CTM exceptions, in the order of the constant value. Note that the text in the square brackets ([ ]) indicates the applicable processing or location.

(1) Content codes from 1000 to 1999

1001 INVALID_TIMEOUT

(No message)

Error contents

The specified timeout value is invalid.

Action to be taken during development

Check the timeout value specified in the EJB client and J2EE server, and specify the predefined monitoring time.

1998 TPBROKER_BAD_PARAM

(No message)

Error contents

[CORBA method]

A CORBA::BAD_PARAM exception report was received.

(2) Content codes from 2000 to 2999

2001 MEM_ALLOC_FAILURE

(No message)

Error contents

An attempt to allocate memory failed.

[Invoke an EJB method]

The processing of the EJB method might be complete.

[Invoke another system-provided method]

The processing of the system-provided method might be complete.

Action to be taken during development

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate the CTM processing.

Action to be taken during operations

An attempt to allocate memory in the part indicated by the place code failed. Terminate the CTM system. When the CTM system terminates, change the maximum user memory size that can be allocated to each process or to the entire system, and then restart the system.

2998 TPBROKER_NO_MEMORY

(No message)

Error contents

[CORBA method]

A CORBA::NO_MEMORY exception report was received.

(3) Content codes from 3000 to 3999

3004 SEND_CLNT_FAILURE

(No message)

Error contents

An error occurred in the communication between the CTM regulator or OTM gateway and the CTM daemon. However, the invocation of the EJB method might be complete.

Action to be taken during development

[Invoke an EJB method]

The connection from the CTM regulator or OTM gateway to the CTM daemon might be closed. Re-execute the operations from the EJB home create processing.

Action to be taken during operations

[Restart the CTM regulator]

Make sure that the CTM daemon is running, and then restart the CTM regulator.

[Restart the OTM gateway]

Make sure that the CTM daemon is running, and then restart the OTM gateway.

3006 SEND_SERV_FAILURE

(No message)

Error contents

An error occurred in the communication between the CTM daemon and J2EE server. However, the invocation of the EJB method might be complete.

Action to be taken during development

[Invoke an EJB method]

Re-invoke the EJB object. However, the previous invocation of the EJB method might be complete. Check the following items as well in the case of OTM invocation:

Is the JNDI lookup name specified while creating the TSC proxy?

Has the session been invoked?

Action to be taken during operations

[Restart a J2EE server]

Make sure that the CTM daemon is running, and then restart the J2EE server. Note that in a system executing batch applications, the J2EE server is replaced by the batch server.

3007 SEND_DAEMON_FAILURE

(No message)

Error contents

An error occurred in the communication between the CTM daemons. However, the invocation of the EJB method might be complete.

Action to be taken during development

[Invoke an EJB method]

Re-invoke the EJB object. However, the previous invocation of the EJB method might be complete.

Action to be taken during operations

[Check the CTM daemon]

Make sure that the CTM daemons from the same CTM domain are running. If the CTM daemons are not running, start the CORBA naming service, then restart the CTM daemons, and then invoke the EJB method.

3008 SEND_REPLY_FAILURE

(No message)

Error contents

An error occurred in the communication from the CTM daemon to the CTM regulator, ORB gateway, or OTM gateway. However, the invocation of the EJB application might be complete.

Action to be taken during operations

Check whether the CTM regulator and OTM gateway are running.

3009 BASIC_CONN_FAILURE

(No message)

Error contents

The CTM daemon could not be found at the communication destination.

Action to be taken during operations

[Check osagent]

Check whether osagent is running.

[Check the environment variables]

Check whether the OSAGENT_PORT environment variable in osagent, CTM processes, and J2EE server are matching.

[Check the CTM daemon]

Check whether the CTM daemon to be connected to is running.

[Other]

Check the value specified in the ejbserver.ctm.CTMDomain or ejbserver.ctm.CTMID properties of the J2EE server.

3010 CONN_FAILURE

(No message)

Error contents

An attempt to connect to the communication route failed.

[Start a J2EE server]

An error occurred in the process of connecting the J2EE server and CTM daemon.

[Start a CTM regulator]

An error occurred in the process of connecting the CTM regulator and CTM daemon.

[Start an OTM gateway]

An error occurred in the process of connecting the OTM gateway and CTM daemon.

[Start a J2EE application]

A communication error occurred in the process of activating the CTM queue.

[Stop a J2EE application]

A communication error occurred in the process of locking (deactivation) the CTM queue.

[Terminate a J2EE server]

An error occurred in the process of disconnecting the J2EE server and CTM daemon.

[Terminate a CTM regulator]

An error occurred in the process of disconnecting the CTM regulator and CTM daemon.

Action to be taken during operations

[Check the maximum number of connections (number of file descriptors)]

An attempt was made to establish connections exceeding the maximum number of connections that can be established, or the number of file descriptors that can be acquired for each process. Terminate the CTM system. Then, change the upper limit for the maximum number of connections that can be established, or the number of file descriptors that can be acquired for each process, and then restart the system.

[Check the CTM daemon]

If this exception occurs while a J2EE application is being stopped, the J2EE application cannot be started because the locking of the CTM queue is not complete. Terminate the J2EE server, make sure that the CTM daemon is running, and then restart the J2EE server.

3011 INCOMPATIBLE_PROTOCOL

(No message)

Error contents

There was a version mismatch in the CTM communication protocol.

Action to be taken during development

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

Check whether there is a version mismatch in the CTM programs included in the same CTM domain.

3012 NOT_IGNORE_PROTOCOL

(No message)

Error contents

[Invoke an EJB method]

There is a version mismatch in some CTM functionality, so the processing cannot be executed.

Action to be taken during development

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

For some functionality, the version of the process indicated in the place code does not match with another process version. Check the versions.

3013 ACTIVATE_TIMED_OUT

(No message)

Error contents

A timeout occurred while a J2EE application was being started.

Action to be taken during operations

Review, and if necessary revise, the value of ejbserver.ctm.ActivateTimeOut, and then restart the J2EE server.

3014 DEACTIVATE_TIMED_OUT

(No message)

Error contents

A timeout occurred while a J2EE application was being stopped.

Action to be taken during development

Check whether PRF is running in order to meet the completion of the EJB business request.

Action to be taken during operations

[Terminate a J2EE server]

The J2EE application cannot be started because the process of locking the CTM queue is not complete. Terminate and then restart the J2EE server.

3015 CLNT_CONN_TIMED_OUT

(No message)

Error contents

A timeout occurred while an ORB gateway was being started.

Action to be taken during operations

Start the ORB gateway before you start the J2EE application.

3016 CLNT_DISCONN_TIMED_OUT

(No message)

Error contents

A timeout occurred while an ORB gateway was being terminated.

Action to be taken during operations

Do not start or stop multiple ORB gateways at the same time.

3017 SERV_CONN_TIMED_OUT

(No message)

Error contents

A timeout occurred while a J2EE application was being started.

Action to be taken during operations

[Restart a J2EE application]

Restart the J2EE application.

If the error occurs frequently, acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

3018 SERV_DISCONN_TIMED_OUT

(No message)

Error contents

A timeout occurred while a J2EE application was being stopped.

Action to be taken during operations

[Restart a CTM daemon]

Restart the CTM daemon.

If the error occurs frequently, acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

3021 DEACTIVATE_FAILURE

(No message)

Error contents

An error occurred while a J2EE application was being stopped. The possible causes are as follows:

Normal lock processing cannot be executed while the J2EE application is running.

A communication error occurred in the CTM daemon during communication.

A timeout was detected in the CTM daemon during communication.

Action to be taken during operations

[Terminate a J2EE server]

For details on the error, see the message KFCT75122-E. The J2EE application cannot be started because the process of locking the CTM queue is not complete. Terminate and then restart the J2EE server.

3022 SEND_INS_FAILURE

(No message)

Error contents

Registration or deletion to the CORBA naming service failed.

Action to be taken during operations

[Check the CORBA naming service]

Make sure that the CORBA naming service is running, and then restart the J2EE application.

If the information for the CORBA naming service is inconsistent, the J2EE application cannot be started. Terminate the COBRA naming service and CTM daemon, and re-execute the operations from starting the COBRA naming service.

3998 TPBROKER_COMM_FAILURE

(No message)

Error contents

[CORBA method]

A CORBA::COMM_FAILURE exception report was received.

(4) Content codes from 4000 to 4999

4001 CALL_IN_HOLD

(No message)

Error contents

The possible causes are as follows:

A service provided by the EJB object is locked.

The J2EE server terminated abnormally.

Action to be taken during development

[Retry (when unlock can be executed)]

Re-invoke the EJB method.

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

If the services provided by the EJB object are locked, unlock those services, and then re-invoke the EJB method.

If the J2EE server terminated abnormally, restart the J2EE server as and when required, and then re-invoke the EJB method.

4005 SERV_CONN_IN_END

(No message)

Error contents

A J2EE server was started while a CTM daemon was being terminated.

Action to be taken during operations

[Restart a CTM daemon]

Restart the CTM daemon, and then re-execute the operations from starting the J2EE server.

4007 CLNT_CONN_IN_END

(No message)

Error contents

A CTM regulator or OTM gateway was started while a CTM daemon was being terminated.

Action to be taken during operations

[Restart a CTM daemon]

Restart the CTM daemon, and then re-execute the operations from restarting the CTM regulator or OTM gateway.

4009 CALL_IN_END

(No message)

Error contents

An EJB object was invoked while a CTM daemon was being terminated. The invocation of the EJB method was not completed.

Action to be taken during development

[Retry (CORBA naming service)]

To search for another CTM daemon, re-execute the operations from the JNDI Lookup processing.

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

[Restart a CTM daemon]

Restart the CTM daemon, and then re-execute the operations from the JNDI Lookup processing.

4011 SERV_CONN_IN_START

(No message)

Error contents

A J2EE server was started while a CTM daemon was being started.

Action to be taken during operations

[Check the CTM daemon]

Check whether the CTM daemon is running, and then restart the J2EE server.

4012 CLNT_CONN_IN_START

(No message)

Error contents

A CTM regulator or OTM gateway was started while a CTM daemon was being started.

Action to be taken during operations

[Check the CTM daemon]

Check whether the CTM daemon is running, and then restart the CTM regulator or OTM gateway.

4013 CTMD_IS_NOT_MY_HOST

(No message)

Error contents

The J2EE application was started on a host different from the CTM daemon.

Action to be taken during operations

[Restart]

Start the J2EE application and CTM daemon on the same host.

4015 NOT_SUPPORTED

(No message)

Error contents

The functionality is not supported.

[EJB home create]

A method other than create was issued for EJB home of a stateless session Bean.

Action to be taken during development

[Retry (EJB home create)]

Check whether a method other than create was issued for EJB home, and then re-execute the operation.

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

[Other than above]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

4016 ACTIVATE_IN_START

(No message)

Error contents

The processing to start a J2EE application was executed while a CTM daemon was being started.

Action to be taken during operations

Restart the J2EE application or J2EE server after the CTM daemon starts.

4018 DEACTIVATE_IN_END

(No message)

Error contents

The processing to stop a J2EE application was executed while a CTM daemon was being terminated.

Action to be taken during operations

Terminate the J2EE application or J2EE server before terminating the CTM daemon.

4020 CLNT_DISCONN_IN_END

(No message)

Error contents

An attempt was made to terminate an ORB gateway while a CTM daemon was being terminated.

Action to be taken during operations

Terminate the ORB gateway before terminating the CTM daemon.

4022 ACTIVATE_WITH_DIFF_PROP

(No message)

Error contents

The types of EJB objects provided by the J2EE applications registered with the same CTM queue name do not match.

Action to be taken during development

[Check the J2EE application]

When changing the CTM queue name, or when sharing the CTM queue, match the types of the EJB objects to be registered in the J2EE application.

4035 INVALID_NAME_PAIR

(No message)

Error contents

The combination of the INS registration name and the interface name differs from the combination that is already registered.

Action to be taken during development

[Change the definition of the J2EE application]

Check the combination of the EJB object interface name and INS registration name that is registered in the J2EE application, and then restart the J2EE application.

4037 QUEUE_IS_ACTIVE

(No message)

Error contents

The specified CTM queue is already active.

Action to be taken during operations

[Terminate a J2EE server]

The CTM queue cannot be locked normally during the J2EE application stop processing. Terminate and then restart the J2EE server.

4039 ACTIVATE_WITH_UNMATCH_QUEUE

(No message)

Error contents

An un-shareable schedule queue has been activated.

Action to be taken during operations

[Check the schedule queue]

When changing the CTM queue name, or when sharing the schedule queue, match the types of the schedule queues to be activated.

4040 CALL_IN_BATCH_QUEUE

(No message)

Error contents

Only batch server requests can be registered in the batch schedule queue.

Action to be taken during operations

[Start a J2EE application]

Start a J2EE application that provides a schedule queue that can receive requests, and then re-execute the processing to invoke the user method of the EJB object.

4041 INVALID_JOB_ID

(No message)

Error contents

The job ID of the received batch application is already in use.

Action to be taken during operations

[Re-execute the job]

Change the job ID specified in the cjexecjob (batch application execution) command, and then re-execute the cjexecjob command.

4998 TPBROKER_NO_PERMISSION

(No message)

Error contents

[CORBA method]

A CORBA::NO_PERMISSION exception report was received.

(5) Content codes from 5000 to 5999

5001 PROPERTIES_FAILURE

(No message)

Error contents

An error occurred during the parsing of a property definition.

Action to be taken during development

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

5002 MSG_TYPE_FAILURE

(No message)

Error contents

An error occurred during the processing of a communication protocol.

Action to be taken during development

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

5003 MUTEX_FAILURE

(No message)

Error contents

An error occurred during exclusive control processing.

Action to be taken during development

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

The memory might be insufficient in the part indicated in the place code. Terminate the CTM system. Then increase the maximum user memory size for each process, and then restart the system.

5004 SIG_COND_FAILURE

(No message)

Error contents

An error occurred during communication between threads with exclusive control.

Action to be taken during development

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

The memory might be insufficient in the part indicated in the place code. Terminate the CTM system. Then increase the maximum user memory size for each process, and then restart the system.

5005 EVENT_FAILURE

(No message)

Error contents

An error occurred during communication between threads.

Action to be taken during development

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

The memory might be insufficient in the part indicated in the place code. Terminate the CTM system. Then increase the maximum user memory size for each process, and then restart the system.

5006 SH_MEM_FAILURE

(No message)

Error contents

An error occurred during the initialization of shared memory.

Action to be taken during development

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

Check whether the relationship between the CTMSPOOL environment variable and CTM domain name is correct. Also, check whether the value specified for the -CTMServerCacheSize option argument in the ctmstart command is correct.

5007 THREAD_CREATE_FAILURE

(No message)

Error contents

An error occurred while a thread was being generated.

Action to be taken during development

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

An attempt was made to generate threads exceeding the maximum number of threads for a process. Increase the maximum number of threads for a process.

5008 TSD_FAILURE

(No message)

Error contents

An error occurred during the initialization of thread-specific memory.

Action to be taken during development

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

The memory might be insufficient in the part indicated in the place code. Terminate the CTM system. Then increase the maximum user memory size for each process, and then restart the system.

5011 CONN_INFO_FAILURE

(No message)

Error contents

An attempt to acquire the connection identifier failed.

Action to be taken during development

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

The memory might be insufficient in the part indicated in the place code. Terminate the CTM system. Then increase the maximum user memory size for each process, and then restart the system.

5998 TPBROKER_INTERNAL

(No message)

Error contents

[CORBA method]

A CORBA::INTERNAL exception report was received.

5999 PROGRAM_ERROR

(No message)

Error contents

Another error occurred in the CTM system.

Action to be taken during development

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing. Also, terminate the EJB client application or J2EE server processes.

Action to be taken during operations

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

(6) Content codes from 6000 to 6999

6998 TPBROKER_MARSHAL

(No message)

Error contents

[CORBA method]

A CORBA::MARSHAL exception report was received.

(7) Content codes from 7000 to 7999

7005 LOAD_SHLIB_FAILURE

(No message)

Error contents

An attempt to read a shared library failed.

Action to be taken during operations

Check whether the library path environment variable has been set up correctly.

7006 INVALID_DEF_CTMID

(No message)

Error contents

The CTM identifier specified in the property ejbserver.ctm.CTMID is invalid.

Action to be taken during operations

Specify a predefined CTM identifier (1 to 31 alphanumeric characters) in the property ejbserver.ctm.CTMID.

7007 INVALID_DEF_DOMAIN_NAME

(No message)

Error contents

The CTM domain name specified in the property ejbserver.ctm.CTMDomain is invalid.

Action to be taken during operations

Specify a predefined CTM domain name (1 to 31 alphanumeric characters) in the property ejbserver.ctm.CTMDomain.

7009 INVALID_ENV_CTMDIR

(No message)

Error contents

The CTMDIR environment variable or CTMSPOOL environment variable is invalid.

Action to be taken during operations

In the CTMDIR environment variable, specify the directory in which CTM is installed, or check whether the CTMSPOOL directory exists and the user has permission to access the directory.

7020 INVALID_DEF_MY_HOST

(No message)

Error contents

The host name or IP address specified in the property ejbserver.ctm.CTMMyHost is invalid.

Action to be taken during operations

Specify the predefined host name or IP address (string of 1 to 64 characters) in the property ejbserver.ctm.CTMMyHost.

7032 INVALID_DEF_ACTIVATE_TIMEOUT

(No message)

Error contents

The value specified in the property (ejbserver.ctm.ActivateTimeOut) that sets the activation timeout value for the J2EE application, is invalid.

Action to be taken during operations

[Restart a J2EE server]

Check the timeout value specified in the property, specify the predefined monitoring time, and then restart the J2EE server.

7033 INVALID_DEF_DEACTIVATE_TIMEOUT

(No message)

Error contents

The value specified in the property (ejbserver.ctm.DeactivateTimeOut) that sets the deactivation timeout value for the J2EE application, is invalid.

Action to be taken during operations

[Restart a J2EE server]

Check the timeout value specified in the property, specify the predefined monitoring time, and then restart the J2EE server.

7040 INVALID_DEF_QUEUE_LENGTH

(No message)

Error contents

The length of the CTM queue specified in the property ejbserver.ctm.QueueLength is invalid.

Action to be taken during operations

Review, and if necessary revise, the length of the CTM queue specified in the J2EE server property, and specify the predefined CTM queue length.

7998 TPBROKER_INITIALIZE

(No message)

Error contents

[CORBA method]

A CORBA::INITIALIZE exception report was received.

(8) Content codes from 8000 to 8999

8001 NO_SUCH_INTERF

(No message)

Error contents

EJB home or EJB object was invoked from the client, but the J2EE application has not been started. Therefore, the EJB object could not be invoked.

Action to be taken during development

[Retry (invoke an EJB method)]

Start the J2EE application that provides the EJB object for the applicable interface, and then re-invoke the EJB object.

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate the invocation of the EJB object.

Action to be taken during operations

[Start a J2EE application]

Start the J2EE application that provides the EJB object for the applicable interface, and then re-execute the processing to invoke the EJB object user method.

[Check the environment settings]

Check whether the CTM domain manager environment settings are incorrect, and then re-invoke the EJB object. The following environment settings might be incorrect:

Value specified in the OSAGENT_PORT environment variable

Value specified in the command option argument -CTMDomain

Value specified in the command option argument -CTMPort

Value specified in the command option argument -CTMSendInterval

8002 NO_SUCH_NAME

(No message)

Error contents

An EJB object was invoked from the client, but a J2EE application providing an EJB object with the same interface name and same INS registration name has not been started. Therefore, the EJB object could not be invoked.

Action to be taken during development

[Retry (invoke an EJB method)]

Start the J2EE application that provides the EJB object with the applicable interface name and INS registration name, and then re-invoke the EJB object.

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate the invocation of the EJB object.

Action to be taken during operations

Start the EJB object with the applicable interface name and INS registration name, and then re-execute the processing to invoke the EJB method.

8003 NO_SUCH_REGLTD

(No message)

Error contents

An EJB object was invoked from the client, but the CTM regulator is not running in the CTM daemon that started the J2EE application. Therefore, the EJB object could not be invoked.

Action to be taken during development

[Retry (EJB home create)]

Start the CTM regulator and J2EE server in the CTM daemon that starts the J2EE application, and then re-invoke the create method for EJB home.

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate the invocation of the EJB object.

Action to be taken during operations

[Check the CTM regulator]

Check whether the CTM regulator is running in the CTM daemon that started the J2EE application. If the CTM regulator is not running, start the CTM regulator, and then re-execute the processing to invoke the EJB method.

8998 TPBROKER_NO_IMPLEMENT

(No message)

Error contents

[CORBA method]

A CORBA::NO_IMPLEMENT exception report was received.

(9) Content codes from 9000 to 9999

9998 TPBROKER_BAD_OPERATION

(No message)

Error contents

[CORBA method]

A CORBA::BAD_OPERATION exception report was received.

(10) Content codes from 10000 to 10999

10001 OVER_MAX_CLNT

(No message)

Error contents

[Start a CTM regulator]

The number of CTM regulators exceeds the value specified in the command option argument -CTMClientConnectCount of the CTM daemon.

[Start an OTM gateway]

The number of OTM gateways exceeds the value specified in the command option argument -CTMClientConnectCount of the CTM daemon.

Action to be taken during operations

[Change the definition]

Terminate the CTM daemon, then increase the value of the command option argument -CTMClientConnectCount, and then restart.

10002 OVER_MAX_SERV

(No message)

Error contents

[Start a J2EE server]

The number of J2EE servers connected to the CTM daemon exceeds the value specified in the command option argument -CTMServerConnectCount of the CTM daemon.

Action to be taken during operations

[Change the definition]

Terminate the CTM daemon, then increase the value of the command option argument -CTMServerConnectCount, and then restart.

10006 OVER_ADM_MAX_SERV

(No message)

Error contents

[Start a J2EE server]

The number of processes managed by the CTM daemon exceeds the value specified in the command option argument -CTMEntryCount of the CTM daemon.

Action to be taken during operations

[Change the definition]

Terminate the CTM daemon, then increase the value of the command option argument -CTMEntryCount (-CTMServerConnectCount if the value is omitted), and then restart.

10007 OVER_MAX_QUEUE

(No message)

Error contents

[Start a J2EE application]

The number of CTM queues registered in the CTM daemon exceeds the value specified in the command option arguments -CTMQueueCount or -CTMQueueRegistCount of the CTM daemon.

Action to be taken during operations

[Change the definition]

Terminate the CTM daemon, then increase the value of the command option arguments -CTMQueueCount or -CTMQueueRegistCount, and then restart.

10008 OVER_MAX_THIN_CLIENT

(No message)

Error contents

[Invoke an EJB method]

The number of clients connected to the CTM regulator, ORB gateway, or OTM gateway exceeds the value specified in the -CTMClientConnectCount option argument.

Action to be taken during operations

Increase the number of CTM regulator, ORB gateway, or OTM gateway processes, or review, and if necessary revise, the value specified in the -CTMClientConnectCount option, and then restart.

10009 OVER_MAX_DISPATCH_PARALLEL

(No message)

Error contents

[Start a J2EE application]

The total parallel count of the CTM queues registered in the CTM daemon (number of resident threads) exceeds the value specified in command option argument -CTMDispatchParallelCount of the CTM daemon.

Action to be taken during operations

[Change the definition]

Terminate the CTM daemon, then increase the value of the command option argument -CTMDispatchParallelCount, and then restart.

10010 OVER_MAX_REQUEST_COUNT

(No message)

Error contents

[Invoke an EJB method]

The maximum number of schedule queues for the J2EE applications providing the EJB objects of the interfaces invoked from the client was exceeded.

Action to be taken during development

[Retry]

Re-invoke the EJB object. The schedule queue might be empty.

If this error occurs continuously for a long time, increase the parallel count of the J2EE applications providing the EJB objects of that interface, or increase the number of J2EE server processes.

[Terminate the processing]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations

[Change the definition]

Increase the J2EE applications containing the same EJB object as the applicable interface name, or increase the J2EE application parallel count, and then restart the J2EE application.

10998 TPBROKER_NO_RESOURCES

(No message)

Error contents

[CORBA method]

A CORBA::NO_RESOURCES exception report was received.

(11) Content codes from 11000 to 11999

11001 TIMED_OUT

(No message)

Error contents

[Invoke an EJB method]

The response of the EJB object user method invocation did not return even after the monitoring time was exceeded. The EJB object user method invocation might be complete.

11003 CANCEL_BATCH_REQUEST

(No message)

Error contents

The batch application requests standing by in the schedule queue were not executed by the cjkilljob (stop batch application or forcibly stop batch server) command.

11998 TPBROKER_NO_RESPONSE

(No message)

Error contents

[CORBA method]

A CORBA::NO_RESPONSE exception report was received.

(12) Content codes from 12000 to 12999

12002 ALREADY_ACTIVE

(No message)

Error contents

[Start a J2EE application]

The J2EE application is already running and the CTM queue has been activated.

Action to be taken during operations

[Terminate a J2EE server]

The CTM queue cannot be locked normally during the J2EE application stop processing. Terminate and then restart the J2EE server.

12015 DUPLICATE_QUEUE_NAME

(No message)

Error contents

A J2EE application with the same CTM queue name has already been registered.

Action to be taken during development

[Change the CTM queue name]

The CTM queue name of the J2EE application must be unique in the J2EE server.

12998 TPBROKER_BAD_INV_ORDER

(No message)

Error contents

[CORBA method]

A CORBA::BAD_INV_ORDER exception report was received.

(13) 13000 and subsequent content codes

13998 TPBROKER_TRANSIENT

(No message)

Error contents

[CORBA method]

A CORBA::TRANSIENT exception report was received.

14998 TPBROKER_OBJECT_NOT_EXIST

(No message)

Error contents

[CORBA method]

A CORBA::OBJECT_NOT_EXIST exception report was received.

15998 TPBROKER_UNKNOWN

(No message)

Error contents

[CORBA method]

A CORBA::UNKNOWN exception report was received.

16998 TPBROKER_INV_OBJREF

(No message)

Error contents

[CORBA method]

A CORBA::INV_OBJREF exception report was received.

17998 TPBROKER_IMP_LIMIT

(No message)

Error contents

[CORBA method]

A CORBA::IMPLIMIT exception report was received.

18998 TPBROKER_BAD_TYPECODE

(No message)

Error contents

[CORBA method]

A CORBA::BAD_TYPECODE exception report was received.

19998 TPBROKER_PERSIST_STORE

(No message)

Error contents

[CORBA method]

A CORBA::PERSIST_STORE exception report was received.

20998 TPBROKER_FREE_MEM

(No message)

Error contents

[CORBA method]

A CORBA::FREE_MEM exception report was received.

21998 TPBROKER_INV_IDENT

(No message)

Error contents

[CORBA method]

A CORBA::INV_IDENT exception report was received.

22998 TPBROKER_INV_FLAG

(No message)

Error contents

[CORBA method]

A CORBA::INV_FLAG exception report was received.

23998 TPBROKER_INTF_REPOS

(No message)

Error contents

[CORBA method]

A CORBA::INTF_REPOS exception report was received.

24998 TPBROKER_BAD_CONTEXT

(No message)

Error contents

[CORBA method]

A CORBA::BAD_CONTEXT exception report was received.

25998 TPBROKER_OBJ_ADAPTER

(No message)

Error contents

[CORBA method]

A CORBA::OBJ_ADAPTER exception report was received.

26998 TPBROKER_DATA_CONVERSION

(No message)

Error contents

[CORBA method]

A CORBA::DATA_CONVERSION exception report was received.

27998 TPBROKER_ TRANSACTION_REQUIRED

(No message)

Error contents

[CORBA method]

A CORBA::TRANSACTION_REQUIRED exception report was received.

28998 TPBROKER_ TRANSACTION_ROLLEDBACK

(No message)

Error contents

[CORBA method]

A CORBA::TRANSACTION_ROLLEDBACK exception report was received.

29998 TPBROKER_ INVALID_TRANSACTION

(No message)

Error contents

[CORBA method]

A CORBA::INVALID_TRANSACTION exception report was received.

30998 TPBROKER_ INV_POLICY

(No message)

Error contents

[CORBA method]

A CORBA::INV_POLICY exception report was received.

31998 TPBROKER_ CODESET_INCOMPATIBLE

(No message)

Error contents

[CORBA method]

A CORBA::CODESET_INCOMPATIBLE exception report was received.

32998 TPBROKER_ REBIND

(No message)

Error contents

[CORBA method]

A CORBA::REBIND exception report was received.

33998 TPBROKER_ TIMEOUT

(No message)

Error contents

[CORBA method]

A CORBA::TIMEOUT exception report was received.

34998 TPBROKER_ TRANSACTION_UNAVAILABLE

(No message)

Error contents

[CORBA method]

A CORBA::TRANSACTION_UNAVAILABLE exception report was received.

35998 TPBROKER_ TRANSACTION_MODE

(No message)

Error contents

[CORBA method]

A CORBA::TRANSACTION_MODE exception report was received.

36998 TPBROKER_ BAD_QOS

(No message)

Error contents

[CORBA method]

A CORBA::BAD_QOS exception report was received.

19.5 List of abort codes

The following table lists and describes the abort codes output in the CTM and PRF messages in the order of the codes. If an unlisted abort code is displayed, acquire the core file, contact maintenance personnel.

Table 19‒48: List of abort codes

Abort code

Cause

Action

bCo003

bCo011

bCo023

bCo024

bSh001

bSh003

bSh004

bSh007

bSh011

bSh024

bSh030

bSh033

bSh042

A memory shortage occurred.

Re-estimate the memory.

eEVT001 to eEVT999

A synchronous control error occurred while a connection was being closed.

Collect the TPBroker and CTM log, and then restart the CTM process.

If the error occurs continuously and frequently, contact maintenance personnel.

eFLK001 to eFLK999

Exclusive allocation failed while a connection was being closed.

A memory shortage might have occurred during operations. Increase the memory for the operating environment.

If the error occurs continuously and frequently, contact maintenance personnel.

eFPM001 to eFPM999

A memory shortage occurred in the CTM daemon.

Re-estimate the memory and then execute the operation again.

eNPM001 to eNPM999

A memory shortage occurred during communication.

Re-estimate the memory and then execute the operation again.

eULK001 to eULK999

Exclusion cancellation failed in the CTM daemon.

A memory shortage might have occurred during operations. Increase the memory for the operating environment.

If the error occurs continuously and frequently, contact maintenance personnel.

eCNM001 to eCNM999

A memory shortage occurred.

Re-estimate the memory and then execute the operation again.

eCUL001 to eCUL999

Exclusion cancellation failed.

A memory shortage might have occurred during operations. Increase the memory for the operating environment.

If the error occurs continuously and frequently, contact maintenance personnel.

eCFL001 to eCFL999

Exclusion processing failed.

A memory shortage might have occurred during operations. Increase the memory for the operating environment.

If the error occurs continuously and frequently, contact maintenance personnel.

eCEV001 to eCEV999

A closed connection was detected.

Collect the TPBroker and CTM log, and check whether the CTM process is running. If the CTM process is not running, then start the CTM process.

If the error occurs continuously and frequently, contact maintenance personnel.

r000000 to r001900

An error occurred in the exclusive allocation processing, or cancellation processing.

The process-specific memory shortage might have occurred. If memory shortage has occurred, review, and if necessary revise, the memory size.

If the error occurs repeatedly, contact maintenance personnel.

r002000

A closed connection was detected.

Collect the TPBroker and CTM log, and check whether the CTM process is running. If the CTM process is not running, then start the CTM process.

If the error occurs continuously and frequently, contact maintenance personnel.

s000002

s002000

s002001

s003000

s003001

s004000

s004001

s008000 to s008010

An error occurred in the exclusive allocation processing, or cancellation processing.

The process-specific memory shortage might have occurred. If memory shortage has occurred, review, and if necessary revise, the memory size.

If the error occurs repeatedly, contact maintenance personnel.

s005000

A memory shortage occurred.

Review, and if necessary revise, the memory size.

If the error occurs repeatedly, contact maintenance personnel.

s007000

A decline in the processing rate was detected by the schedule queue retention monitoring functionality.

See the PRF trace file and statistics file, and investigate the cause due to which processing cannot be executed, or review, and if necessary revise the settings for queue retention monitoring.

uFPM001 to uFPM999

A memory shortage occurred.

Re-estimate the memory and then execute the operation again.

uLCK001 to uLCK999

Exclusive allocation failed.

A memory shortage might have occurred during operations. Increase the memory for the operating environment.

If the error occurs continuously and frequently, contact maintenance personnel.

uNPM001 to uNPM999

A memory shortage occurred.

Re-estimate the memory and then execute the operation again.

tnad01

A memory shortage occurred.

Review, and if necessary revise, the memory size.

If the error occurs repeatedly, contact maintenance personnel.

Wshm02

An attempt to create a file to be used as a shared memory in Windows failed.

Check whether there is adequate disk space in the environment variable PRFSPOOL or environment variable CTMSPOOL.

20 KFDB (Messages output by Cosminexus DABroker Library) (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

20.1 (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

21 KFDJ (Messages output by Cosminexus DABroker Library) (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

21.1 (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

22 KFRM (Messages Output by Cosminexus RM) (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

22.1 (INTENTIONALLY DELETED)

(INTENTIONALLY DELETED)

23 Messages output by Web Server (Cosminexus HTTP Server)

This chapter describes the messages that are output by Cosminexus HTTP Server.

23.1 Describing the format of messages (messages beginning with AH or KH)

The format for describing the messages beginning with AH or KH in this chapter is as follows.

XXnnnnn

Message text

Description of variable values

Description

Supplementary description of the message text

Action

Action taken by the user

Note that for some messages, Description of variable values and Action might not be described.

Each item is described as follows:

XXnnnnn

This describes the message ID.

nnnnn

This indicates the message number managed by the program that output the message. A five-digit unique number is attached to each message.

Message text

This describes the message text output by the Web server.

Note that the variable value (value that differs depending upon the status in which the message is output) within the message text is output with the format xx....xx (xx are lower-case alphabetical characters).

Description of variable values

The information displayed in the variable value within the message text is output with the format 'xx....xx: displayed-information' (xx are lower-case alphabetical characters). An example of the format for describing variable val

ues is as follows:

Example:

aa....aa: File name

bb....bb: Application name

Description

This is the supplementary description of the message, such as the factors responsible for reporting the message and operation of the component software that output the message.

Action

This is the action to be taken by the user.

23.2 Describing the format of messages (messages for commands and programs)

The format for describing the messages for commands and programs in this chapter is as follows.

Message text

Message description

Error level: Level of the error output in the error log

(S) System processing

(O) User action

Note that Error level and (O) might not be described for some messages.

The description of each item is as follows:

Message text

The messages might contain the time and error level followed by the Message text, or only the Message text. The format is as follows:

Format 1

[Time] [Error level] Message text

Format 2

Message text

Message description

This indicates the supplementary description of a message such as the cause of reporting the message.

Error level

This indicates the error level specified in the LogLevel directive.

The following error levels can be output:

emerg

alert

crit

error

warn

notice

info

No level

No level means that the message has no level setting and only the message text is output.

(S)

This indicates the main processing that is executed after the system outputs the message.

(O)

This indicates the action to be taken by the user when a message is output.

23.3 Precautions

The messages with the error level notice are output irrespective of the specification in the LogLevel directive.

The messages might be output before the analysis of the level specification, such as when Cosminexus HTTP Server is started irrespective of the specification in the LogLevel directive.

With some exceptions, the following messages are not described:

Messages, following the grammatical errors in the configuration file, output when Cosminexus HTTP Server is started

Messages, with error level as debug, output after Cosminexus HTTP Server is started

Messages, without the error levels, output after Cosminexus HTTP Server is started

23.4 Messages beginning with AH

This section describes the messages beginning with AH.

AH00004

Unable to create scoreboard (anonymous shared memory failure)

Description

The shared memory to be used with the scoreboard could not be secured. The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

AH00013

Pre-configuration failed

Description

An error occurred in the processing prior to reading the configuration file. The Web server stops the start processing.

Action

Revise according to the cause of error described in messages output other than this message.

AH00014

Configuration check failed

Description

An error is detected during checking of the configuration file. The Web server stops the start processing.

Action

Revise according to the cause of error described in messages output other than this message.

AH00015

Unable to open logs

Description

An error occurred during the setup of the log output destination or during the socket generation processing. The Web server stops the start processing.

Action

Revise according to the cause of error described in messages output other than this message.

AH00016

Configuration Failed

Description

An error occurred in the processing after reading the configuration file. The Web server stops the start processing.

Action

Revise according to the cause of error described in messages output other than this message.

AH00017

Pre-configuration failed

Description

An error occurred in the processing prior to reading the configuration file. The Web server stops the start or restart processing.

Action

Revise according to the cause of error described in messages output other than this message.

AH00018

Configuration check failed

Description

An error is detected during checking of the configuration file. The Web server stops the start or restart processing.

Action

Revise according to the cause of error described in messages output other than this message.

AH00019

Unable to open logs

Description

An error occurred during the setup of the log output destination or during the socket generation processing. The Web server stops the start or restart processing.

Action

Revise according to the cause of error described in messages output other than this message.

AH00020

Configuration Failed

Description

An error occurred in the processing after reading the configuration file. The Web server stops the start or restart processing.

Action

Revise according to the cause of error described in messages output other than this message.

AH00023

Couldn't create the aa....aa mutex (file bb....bb)

aa....aa: Type

bb....bb: File name

Description

An attempt to create the exclusive environment has failed. bb....bb might not be output.

Action

Revise the specification according to the detailed information shown in this message.

AH00024

Couldn't set permissions on the aa....aa mutex; check User and Group directives

aa....aa: Type

Description

An attempt to set up permissions for the mutual exclusion has failed.

Action

Revise the User and Group directive values according to the detailed information shown in this message.

AH00025

configuration error: couldn't aa....aa: bb....bb

aa....aa: Text

bb....bb: Requested URI value

Description

When accessing the requested URI value, the event indicated in aa....aa cannot be performed due to an error in the configuration file settings.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Revise the configuration file according to the contents described in text.

AH00031

access to aa....aa failed; stat of 'bb....bb' failed.

aa....aa: Requested URI value

bb....bb: Access file

Description

The file indicated by the requested URI cannot be accessed. Information for the file indicated by the file name could not be acquired.

The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.

Action

Revise the access file according to the detailed information shown in this message.

AH00032

Symbolic link not allowed or link target not accessible: aa....aa

aa....aa: Access file

Description

The file indicated in aa....aa is not allowed to dereference a symbolic link.

The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.

Action

If SymLinksIfOwnerMatch of the Options directive is enabled, make sure that the owner of the access file or directory is the same as the owner of the symbolic link.

AH00033

dir_walk error, path_info aa....aa is not relative to the filename path bb....bb for uri cc....cc

aa....aa: Path information

bb....bb: Directory name

cc....cc: Requested URI value

Description

The path described in the aa....aa is not included under the directory described in the bb....bb.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH00034

dir_walk error, could not determine the root path of filename aa....aa for uri bb....bb

aa....aa: File name

bb....bb: Requested URI value

Description

A standard path could not be determined as the path to be specified in the aa....aa.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH00035

access to aa....aa denied (filesystem path 'bb....bb') because search permissions are missing on a component of the path

aa....aa: Requested URI value

bb....bb: Access file

Description

An attempt to access the file indicated by the requested URI failed due to the lack of search permissions for the file.

The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.

Action

Revise the access file according to the detailed information shown in this message.

AH00036

access to aa....aa failed (filesystem path 'bb....bb')

aa....aa: Requested URI value

bb....bb: Access file

Description

The file indicated by the requested URI cannot be accessed.

The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.

Action

Revise the access file according to the detailed information shown in this message.

AH00037

Symbolic link not allowed or link target not accessible: aa....aa

aa....aa: Access file

Description

The file indicated in aa....aa is not allowed to dereference a symbolic link.

The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.

Action

If SymLinksIfOwnerMatch of the Options directive is enabled, make sure that the owner of the access file or directory is the same as the owner of the symbolic link.

AH00038

Forbidden: aa....aa doesn't point to a file or directory

aa....aa: Access file

Description

The access file is neither a file nor a directory.

The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.

Action

Revise the attribute of the access file.

AH00045

child process aa....aa still did not exit, sending a SIGTERM

aa....aa: Process ID

Description

The SIGTERM signal will be sent because the server process described in the aa....aa has not terminated. The Web server continues the termination or restart processing.

Action

Make sure that the SIGTERM signal is not blocked for the server process, and wait until the server process terminates.

AH00046

child process aa....aa still did not exit, sending a SIGKILL

aa....aa: Process ID

Description

The SIGKILL signal will be sent because the server process described in the aa....aa has not terminated. The Web server continues the termination or restart processing.

Action

Wait until the server process terminates.

AH00047

could not make child process aa....aa exit, attempting to continue anyway

aa....aa: Process ID

Description

The server process specified in the aa....aa could not be terminated. The termination or restart processing of the server will continue after ignoring the un-terminated server process.

Action

An un-terminated server process exists. Investigate the cause due to which the server does not terminate, and if it is necessary to terminate the server, send a signal and terminate forcibly.

AH00050

Child aa....aa returned a Fatal error... Server is exiting!

aa....aa: Process ID

Description

The server process terminated because of an error due to which the process could not be continued. The Web server will shut down.

Action

Revise according to the cause of error described in messages output other than this message.

AH00051

child pid aa....aa exit signal bb....bb (cc....cc), possible coredump in dd....dd

aa....aa: Process ID

bb....bb: Signal meaning

cc....cc: Signal number

dd....dd: Core output destination directory

Description

The server process terminated with the signal specified in the cc....cc. If possible, output the core in the dd....dd. The Web server continues the processing.

AH00052

child pid aa....aa exit signal bb....bb (cc....cc)

aa....aa: Process ID

bb....bb: Signal meaning

cc....cc: Signal number

Description

The server process terminated with the signal specified in the cc....cc.

The Web server continues the processing.

AH00053

write pipe_of_death

Description

An attempt to write in the pipe to be used in the request for terminating the server process has failed. The request of terminating the server process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

AH00054

get socket to connect to listener

Description

An attempt to generate the socket to be used in the request for terminating the server process has failed. The request of terminating the server process will now stop.

Action

Revise the specification according to the detailed information about socket() shown in this message.

AH00055

set timeout on socket to connect to listener

Description

An attempt to set up a timeout for the socket to be used in the request for terminating the server process has failed. The request of terminating the server process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

AH00056

connect to listener on aa....aa:bb....bb

aa....aa: Web server address

bb....bb: Port number

Description

An attempt to connect to the Web server during the processing of the server process termination request has failed. The request of terminating the server process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

AH00057

sending signal to server

Description

An attempt to send a signal to the Web server has failed.

Action

Revise the specification according to the detailed information about kill() shown in this message.

AH00058

Error retrieving pid file aa....aa

aa....aa: PID storage file name

Description

An attempt to search the PID storage file has failed. The process of sending a signal to the Web server will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH00059

Remove it before continuing if it is corrupted.

Description

If the PID storage file is corrupted, you must delete it.

Action

Revise according to the cause of error described in messages output other than this message.

AH00060

seg fault or similar nasty error detected in the parent process

Description

The signal for terminating the control process was received. The control process terminates.

AH00061

sigaction(SIGSEGV)

Description

An error occurred when the action for the SIGSEGV signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00062

sigaction(SIGBUS)

Description

An error occurred when the action for the SIGBUS signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00063

sigaction(SIGABORT)

Description

An error occurred when the action for the SIGABORT signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00064

sigaction(SIGABRT)

Description

An error occurred when the action for the SIGABRT signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00065

sigaction(SIGILL)

Description

An error occurred when the action for the SIGILL signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00066

sigaction(SIGFPE)

Description

An error occurred when the action for the SIGFPE signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00067

make_sock: for address aa....aa: bb....bb, apr_socket_opt_set: (SO_REUSEADDR)

aa....aa: Web server address

bb....bb: Port number

Description

An error occurred during the setup of the socket level option SO_REUSEADDR. The Web server stops the start processing.

Action

Revise the specification according to the detailed information about setsockopt() shown in this message.

AH00068

make_sock: for address aa....aa: bb....bb, apr_socket_opt_set: (SO_KEEPALIVE)

aa....aa: Web server address

bb....bb: Port number

Description

An error occurred during the setup of the socket level option SO_KEEPALIVE. The Web server stops the start processing.

Action

Revise the specification according to the detailed information about setsockopt() shown in this message.

AH00069

make_sock: for address aa....aa: bb....bb, apr_socket_opt_set: (IPV6_V6ONLY)

aa....aa: Web server address

bb....bb: Port number

Description

An error occurred during the setup of the socket level option IPV6_V6ONLY. The Web server stops the start processing.

Action

Revise the specification according to the detailed information about setsockopt() shown in this message.

AH00072

make_sock: could not bind to address aa....aa: bb....bb

aa....aa: Web server address

bb....bb: Port number

Description

An error occurred during address binding to the socket. The Web server stops the start processing.

Action

Revise the specification according to the detailed information about bind() shown in this message.

AH00073

make_sock: unable to listen for connections on address aa....aa: bb....bb

aa....aa: Web server address

bb....bb: Port number

Description

An error occurred when preparing to receive connections on the socket. The Web server stops the start processing.

Action

Revise the specification according to the detailed information about listen() shown in this message.

AH00074

make_sock: for address aa....aa: bb....bb, apr_socket_opt_set: (SO_REUSEADDR)

aa....aa: Web server address

bb....bb: Port number

Description

An error occurred during the setup of the socket level option SO_REUSEADDR. The Web server stops the start processing.

Action

Revise the specification according to the detailed information about setsockopt() shown in this message.

AH00077

alloc_listener: failed to set up sockaddr for aa....aa

aa....aa: IP address

Description

The socket information concerning the aa....aa could not be acquired. The Web server stops the start processing.

Action

Revise according to the aa....aa specified in the Listen directive.

AH00078

alloc_listener: failed to get a socket for aa....aa

aa....aa: IP address

Description

An error occurred during the creation of the socket terminal. The Web server stops the start processing.

Action

Revise the specification according to the detailed information about socket() shown in this message.

AH00089

Couldn't start ErrorLog process 'aa....aa'.

aa....aa: Value specified in the ErrorLog directive in the pipe specification.

Description

An attempt to generate a process for the output of the error log has failed. The Web server stops the start processing.

Action

Revise the ErrorLog directive according to the detailed information shown in this message.

AH00090

aa....aa: Invalid error log path bb....bb.

aa....aa: Command name

bb....bb: File name

Description

The file path specified in the ErrorLog directive is invalid. The Web server stops the start processing.

Action

Revise the ErrorLog directive according to the detailed information shown in this message.

AH00091

aa....aa: could not open error log file bb....bb.

aa....aa: Command name

bb....bb: File name

Description

The error log file could not be opened. The Web server stops the start processing.

Action

Revise the ErrorLog directive according to the detailed information shown in this message.

AH00092

unable to replace stderr with error_log

Description

The file descriptor of standard error output cannot be copied in the file descriptor of the error log. The Web server continues the start processing.

Action

Revise the specification according to the detailed information shown in this message.

AH00093

unable to replace stderr with /dev/null

Description

The standard error output cannot be replaced with /dev/null. The Web server continues the start processing.

Action

Revise the specification according to the detailed information about freopen() shown in this message.

AH00094

Command line: 'aa....aa'

aa....aa: Command line

Description

The server started with the command indicated by the command line. The Web server continues the start processing.

AH00095

failed to remove PID file aa....aa

aa....aa: File name

Description

An attempt to delete the file that stores the control process ID failed. The Web server continues the termination processing.

Action

Revise the specification according to the detailed information shown in this message.

AH00096

removed PID file aa....aa (pid=bb....bb)

aa....aa: File name

bb....bb: Control process ID

Description

The file that stores the control process ID was deleted.

The Web server continues the termination processing.

AH00097

Invalid PID file path aa....aa, ignoring.

aa....aa: File name

Description

The file name that stores the process IDs is invalid.

The Web server continues the startup processing.

Action

Revise the PidFile directive according to the detailed information shown in this message.

AH00098

pid file aa....aa overwritten -- Unclean shutdown of previous server run?

aa....aa: File name that stores process IDs

Description

The file that stores process IDs is overwritten. The Web server might not have been shut down properly the last time. When the Web server is shut down properly, the file that stores process IDs is deleted.

The Web server continues the start processing.

Action

Make sure that no un-terminated Web server exists. The process ID of the control process is saved in the file specified in the PidFile directive, when the Web server is started. This message will be output even when the file specified in the PidFile directive is duplicated in more than one Web server. Make sure that the file is not shared among multiple Web servers.

AH00099

could not create aa....aa

aa....aa: File name that stores process IDs

Description

The file that stores the process IDs could not be created.

The Web server stops the start processing.

Action

Revise the file specified in the PidFile directive according to the detailed information shown in this message.

AH00100

aa....aa: could not log pid to file bb....bb

aa....aa: Command name

bb....bb: File name that stores process IDs

Description

An attempt to record a process ID in the bb....bb has failed. The Web server stops the start processing.

Action

Revise according to the cause of error described in messages output other than this message.

AH00101

Invalid PID file path aa....aa, ignoring.

aa....aa: File name that stores process IDs

Description

The file name that stores the process IDs is invalid. The Web server continues the start processing.

Action

Revise the PidFile directive according to the detailed information shown in this message.

AH00103

piped_log_spawn: unable to setup child process 'aa....aa'

aa....aa: Log output program

Description

The initial setup of properties of the process for the output of the log could not be performed. The processing for the generation of the process for log output will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH00104

unable to start piped log program 'aa....aa'

aa....aa: Log output program

Description

The log output based on the aa....aa could not be started. The processing for the generation of the process for log output will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH00106

piped log program 'aa....aa' failed unexpectedly

aa....aa: Log output program

Description

An unexpected error occurred in the log output program. The process for log output will be regenerated.

AH00107

piped_log_maintenance: unable to respawn 'aa....aa'

aa....aa: Log output program

Description

An attempt to regenerate the process for log output has failed. The processing for the generation of the process for log output will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH00112

Warning: DocumentRoot [aa....aa] does not exist

aa....aa: Directory name

Description

The directory specified in the DocumentRoot directive cannot be found. The Web server continues the startup processing.

Action

Revise according to the DocumentRoot directive specified in the <VirtualHost> block.

AH00113

aa....aa:bb....bb cannot use a full URL in a 401 ErrorDocument directive --- ignoring!

aa....aa: File name

bb....bb: Line number

Description

The full URL cannot be specified when 401 is specified as the error status code in the ErrorDocument directive.

Action

When 401 is specified as the error status code, specify the text or local URL.

AH00114

Useless use of AllowOverride in line aa....aa of bb....bb.

aa....aa: Line number

bb....bb: File name

Description

The AllowOverride directive cannot be specified in the <Location> or <Files> block. The Web server continues the startup processing.

Action

Delete the AllowOverride directive in the <Location> or <Files> block.

AH00117

Ignoring deprecated use of DefaultType in line aa....aa of bb....bb.

aa....aa: Line number

bb....bb: File name

Description

The DefaultType directive cannot be used.

Action

Delete the DefaultType directive.

AH00124

Request exceeded the limit of aa....aa internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

aa....aa: Limit value

Description

The number of internal redirects of a request has reached the limit value (10).

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Check the settings to make sure that the internal redirect is not iterated unnecessarily.

AH00125

Request exceeded the limit of aa....aa subrequest nesting levels due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

aa....aa: Limit value

Description

The number of sub request nesting of a request has reached the limit value (10).

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Check the settings to make sure that the sub request is not iterated unnecessarily.

AH00126

Invalid URI in request aa....aa

aa....aa: Request

Description

The URI in the request is invalid.

The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.

Action

Revise the URI in the request.

AH00128

File does not exist: aa....aa

aa....aa: File name

Description

The requested file cannot be found.

The status code 404 Not Found will be returned to the client, and the request processing will be interrupted.

Action

Revise the requested file name.

AH00129

Attempt to serve directory: aa....aa

aa....aa: Directory name

Description

Cannot send a request to the aa....aa.

The status code 404 Not Found will be returned to the client, and the request processing will be interrupted.

Action

Revise the URI in the request.

AH00130

File does not exist: aa....aa

aa....aa: File name

Description

The requested file cannot be found.

The status code 404 Not Found will be returned to the client, and the request processing will be interrupted.

Action

Revise the requested file name.

AH00131

This resource does not accept the aa....aa method.

aa....aa: Method name

Description

A request was sent to the source by a method that is not allowed.

The status code 405 Method Not Allowed will be returned to the client, and the request processing will be interrupted.

Action

Revise the method in the request.

AH00132

file permissions deny server access: aa....aa

aa....aa: File name

Description

There is no permission to access the required file.

The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.

Action

Revise the requested file according to the detailed information shown in this message.

AH00135

Invalid method in request aa....aa

aa....aa: Request line

Description

The method in the request is invalid.

The status code 501 Method Not Implemented will be returned to the client, and the request processing will be interrupted.

Action

Revise the method in the request.

AH00137

apr_socket_addr_get(APR_LOCAL)

Description

The socket information of the Web server could not be acquired. The Web server stops the request processing.

Action

Revise the specification according to the detailed information about getsockname() shown in this message.

AH00138

apr_socket_addr_get(APR_REMOTE)

Description

The socket information of the client could not be acquired. The Web server stops the request processing.

Action

Revise the specification according to the detailed information about getpeername() shown in this message.

AH00144

couldn't grab the accept mutex

Description

An attempt to acquire the mutual exclusion of accept has failed. The server process terminates.

Action

Revise the specification according to the detailed information shown in this message.

AH00146

couldn't release the accept mutex

Description

An attempt to release the mutual exclusion of accept has failed. The server process terminates.

Action

Revise the specification according to the detailed information shown in this message.

AH00147

sigaction(SIGTERM)

Description

An error occurred when the action for the SIGTERM signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00148

sigaction(SIGUSR2)

Description

An error occurred when the action for the SIGUSR2 signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00149

sigaction(SIGINT)

Description

An error occurred when the action for the SIGINT signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00150

sigaction(SIGXCPU)

Description

An error occurred when the action for the SIGXCPU signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00151

sigaction(SIGXFSZ)

Description

An error occurred when the action for the SIGXFSZ signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00152

sigaction(SIGPIPE)

Description

An error occurred when the action for the SIGPIPE signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00153

sigaction(SIGHUP)

Description

An error occurred when the action for the SIGHUP signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00154

sigaction(SIGUSR1)

Description

An error occurred when the action for the SIGUSR1 signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00155

Couldn't initialize cross-process lock in child (aa....aa) (bb....bb)

aa....aa: Lock file name

bb....bb: Exclusion identifier name

Description

An attempt to initialize the mutual exclusion used between server processes has failed. The server process terminates.

Action

Revise the specification according to the detailed information shown in this message.

AH00162

server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers), spawning aa....aa children, there are bb....bb idle, and cc....cc total children

aa....aa: Number of server processes to be generated

bb....bb: Number of server processes that are idle

cc....cc: Total number of server processes

Description

The Web server is in a busy state due to request processing. Either the value of the StartServers directive must be increased, or the value of the Min/MaxSpareServers directive must be revised. Server processes are generated one by one or in the specified unit (2, 4, 8, 16, or 32) at a time, until the number of server processes that are idle reaches the value specified in the MinSpareServers directive. If the number of processes to be generated reaches 8 or more, this message will be output.

AH00163

aa....aa configured -- resuming normal operations

aa....aa: Server name

Description

The startup of the Web server has started.

AH00164

Server built: aa....aa

aa....aa: Time when Web server was created

Description

The time of creation of the Web server that is started is displayed.

AH00167

long lost child came home! (pid aa....aa)

aa....aa: Process ID

Description

The control process uses the scoreboard file to manage the status of the server process. If the process terminated after restarting with graceful does not correspond to the managed process, this message will be output.

AH00168

killpg SIGTERM

Description

To shut down the Web server, the control process sent the signal SIGTERM to the server process with the killpg() function, but an error occurred. The control process will send the SIGTERM signal to each server process after a few seconds, and the server process termination processing will continue.

Action

Revise the specification according to the detailed information about killpg() shown in this message.

AH00169

caught SIGTERM, shutting down

Description

The Web server stopped because the SIGTERM signal was received.

AH00171

Graceful restart requested, doing restart

Description

A restart of the Web server by graceful was requested. The restart processing will start.

AH00172

killpg SIGHUP

Description

To restart the Web server, the control process sent the signal SIGHUP to the server process with the killpg() function, but an error occurred. The control process will send the SIGTERM signal to each server process after a few seconds, and the server process termination processing will continue.

Action

Revise the specification according to the detailed information about killpg() shown in this message.

AH00173

SIGHUP received. Attempting to restart

Description

The Web server received a restart request by the signal SIGHUP. The Web server starts the restart processing.

AH00264

sigaction(SIGTERM)

Description

An error occurred when the action for the SIGTERM signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00265

sigaction(SIGUSR2)

Description

An error occurred when the action for the SIGUSR2 signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00266

sigaction(SIGINT)

Description

An error occurred when the action for the SIGINT signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00267

sigaction(SIGXCPU)

Description

An error occurred when the action for the SIGXCPU signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00268

sigaction(SIGXFSZ)

Description

An error occurred when the action for the SIGXFSZ signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00269

sigaction(SIGPIPE)

Description

An error occurred when the action for the SIGPIPE signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00270

sigaction(SIGHUP)

Description

An error occurred when the action for the SIGHUP signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00271

sigaction(SIGUSR1)

Description

An error occurred when the action for the SIGUSR1 signal changed. The Web server continues the startup processing.

Action

Revise the specification according to the detailed information about sigaction() shown in this message.

AH00272

aa....aa failed before this child process served any requests.

aa....aa: apr_proc_mutex_lock or apr_proc_mutex_unlock

Description

An error occurred during lock or unlock processing. The server process terminates.

Action

Revise the specification according to the detailed information shown in this message.

AH00273

aa....aa failed. Attempting to shutdown process gracefully.

aa....aa: apr_proc_mutex_lock or apr_proc_mutex_unlock

Description

An error occurred during lock or unlock processing. The server process will end after termination of the request processing being performed.

Action

Revise the specification according to the detailed information shown in this message.

AH00274

apr_proc_mutex_unlock failed. Attempting to shutdown process gracefully.

Description

An error occurred during unlock processing. The server process will end after termination of the request processing being performed.

Action

Revise the specification according to the detailed information shown in this message.

AH00275

apr_thread_create: unable to create listener thread

Description

An attempt to generate a listener thread failed. The server process terminates.

Action

Revise the specification according to the detailed information shown in this message.

AH00277

apr_thread_join: unable to join listener thread

Description

An error occurred during processing to wait for termination of a listener thread. The termination processing of the server process continues.

Action

Revise the specification according to the detailed information shown in this message.

AH00278

apr_thread_join: unable to join worker thread aa....aa

aa....aa: Slot number

Description

An error occurred during processing to wait for termination of the server thread. The termination processing of the server process continues.

Action

Revise the specification according to the detailed information shown in this message.

AH00279

apr_thread_join: unable to join the start thread

Description

An error occurred during processing to wait for termination of the start thread. The termination processing of the server process continues.

Action

Revise the specification according to the detailed information shown in this message.

AH00280

Couldn't initialize cross-process lock in child

Description

An attempt to initialize the mutual exclusion used between server processes has failed. The server process terminates.

Action

Revise the specification according to the detailed information shown in this message.

AH00281

Couldn't initialize signal thread

Description

An attempt to set up the signal mask of the thread failed. The server process terminates.

Action

Revise the specification according to the detailed information shown in this message.

AH00282

apr_thread_create: unable to create worker thread

Description

An attempt to generate a start thread failed. The server process terminates.

Action

Revise the specification according to the detailed information shown in this message.

AH00283

fork: Unable to fork new process

Description

An attempt to generate the server process has failed.

Action

Revise the specification according to the detailed information shown in this message.

AH00289

server seems busy, (you may need to increase StartServers, ThreadsPerChild or Min/MaxSpareThreads), spawning aa....aa children, there are around bb....bb idle threads, and cc....cc total children

aa....aa: Number of server processes to be generated

bb....bb: Number of server threads that are idle

cc....cc: Total number of server processes

Description

The Web server is in a busy state due to request processing. The value of the StartServers, ThreadsPerChild, MinSpareThreads, or MaxSpareThreads directive must be revised. Server processes are generated one by one or in the specified unit (2, 4, 8, 16, or 32) at a time, until the number of server threads that are idle reaches the value specified in the MinSpareServers directive. If the number of processes to be generated reaches 8 or more, this message will be output.

AH00291

long lost child came home! (pid aa....aa)

aa....aa: Process ID

Description

The control process uses the scoreboard file to manage the status of the server process. If the process terminated after restarting with graceful does not correspond to the managed process, this message will be output.

AH00292

aa....aa configured -- resuming normal operations

aa....aa: Server name

Description

The Web server has started.

AH00293

Server built: aa....aa

aa....aa: Time when Web server was created

Description

The time of creation of the Web server that is started is displayed.

AH00295

caught SIGTERM, shutting down

Description

The Web server stopped because the SIGTERM signal was received.

AH00297

SIGUSR1 received. Doing graceful restart

Description

The restart of the Web server by graceful was requested. The restart processing will start.

AH00298

SIGHUP received. Attempting to restart

Description

The Web server received a restart request by the signal SIGHUP. The Web server starts the restart processing.

AH00300

WARNING: ServerLimit of aa....aa exceeds compile-time limit of

bb....bb servers, decreasing to bb....bb.

aa....aa: Value specified in the ServerLimit directive

bb....bb: Maximum limit of the ServerLimit directive value

Description

The ServerLimit directive value exceeds the maximum limit. The Web server sets the upper limit value for the ServerLimit directive, and then continues the startup processing.

Action

Revise the ServerLimit directive value.

AH00301

ServerLimit of aa....aa exceeds compile-time limit of bb....bb, decreasing to match

aa....aa: Value specified in the ServerLimit directive

bb....bb: Maximum limit of the ServerLimit directive value

Description

The ServerLimit directive value exceeds the maximum limit. The Web server sets the maximum limit value for the ServerLimit directive, and then continues processing.

Action

Revise the ServerLimit directive value.

AH00304

changing ServerLimit to aa....aa from original value of bb....bb not allowed during restart

aa....aa: Value specified in the ServerLimit directive when restarting the Web server

bb....bb: Value specified in the ServerLimit directive when starting the Web server

Description

The ServerLimit directive value cannot be changed when restarting the Web server. The Web server sets the ServerLimit directive to the value that was specified when the Web server started, and then continues processing.

Action

If you need to change the ServerLimit directive value, stop the Web server, and then restart it.

AH00305

WARNING: ThreadLimit of aa....aa exceeds compile-time limit of

bb....bb threads, decreasing to bb....bb.

aa....aa: Value specified in the ThreadLimit directive

bb....bb: Maximum limit of the ThreadLimit directive value

Description

The ThreadLimit directive value exceeds the maximum limit. The Web server sets the maximum limit value for the ThreadLimit directive, and then continues the startup processing.

Action

Revise the ThreadLimit directive value.

AH00306

ThreadLimit of aa....aa exceeds compile-time limit of bb....bb, decreasing to match

aa....aa: Value specified in the ThreadLimit directive

bb....bb: Maximum limit of the ThreadLimit directive value

Description

The ThreadLimit directive value exceeds the maximum limit. The Web server sets the maximum limit value for the ThreadLimit directive, and then continues processing.

Action

Revise the ThreadLimit directive value.

AH00309

changing ThreadLimit to aa....aa from original value of bb....bb not allowed during restart

aa....aa: Value specified in the ThreadLimit directive when restarting the Web server

bb....bb: Value specified in the ThreadLimit directive when starting the Web server

Description

The ThreadLimit directive value cannot be changed for restarting the Web server. The Web server sets the ThreadLimit directive to the value that was specified when the Web server started, and then continues processing.

Action

If you need to change the ThreadLimit directive value, stop the Web server, and then restart it.

AH00310

WARNING: ThreadsPerChild of aa....aa exceeds ThreadLimit of

bb....bb threads, decreasing to bb....bb.

To increase, please see the ThreadLimit directive.

aa....aa: Value specified in the ThreadsPerChild directive

bb....bb: Value specified in the ThreadLimit directive

Description

The ThreadsPerChild directive value exceeds the ThreadLimit directive value. The Web server sets the ThreadLimit directive value for the ThreadsPerChild directive value, and then continues the startup processing.

Action

If you need to increase the ThreadsPerChild directive value, you must also change the ThreadLimit directive value.

AH00311

ThreadsPerChild of aa....aa exceeds ThreadLimit of bb....bb, decreasing to match

aa....aa: Value specified in the ThreadsPerChild directive

bb....bb: Value specified in the ThreadLimit directive

Description

The ThreadsPerChild directive value exceeds the ThreadLimit directive value. The Web server sets the ThreadLimit directive value for the ThreadsPerChild directive value, and then continues processing.

Action

If you need to increase the ThreadsPerChild directive value, you must also change the ThreadLimit directive value.

AH00344

accept() failed.

Description

An error occurred in the accept() function. The process of accepting the requests continues.

Action

Revise the specification according to the detailed information about accept() shown in this message.

AH00346

getsockname failed

Description

getsockname() has failed. The server thread will be in the request-awaiting state.

Action

Revise the specification according to the detailed information about getsockname() shown in this message.

AH00347

getpeername failed

Description

getpeername() has failed. The server thread will continue the request processing without setting up socket information of the client.

Action

Revise the specification according to the detailed information about getpeername() shown in this message.

AH00348

Child: Accept thread exiting.

Description

The request reception thread is terminated.

AH00350

Child: Failed to create a max_requests event.

Description

The server process has failed to generate an event for the maximum number of requests. The server process terminates.

Action

Revise the specification according to the detailed information about CreateEvent() shown in this message.

AH00351

Child: Failed to acquire the start_mutex. Process will exit.

Description

An attempt to acquire the lock for mutual exclusion of server process has failed. The server process terminates.

Action

Revise the specification according to the detailed information about WaitForSingleObject shown in this message.

AH00353

Child: Failed to create a qwait event.

Description

The server process failed to generate an event for queue operation. The server process terminates.

Action

Revise the specification according to the detailed information about CreateEvent() shown in this message.

AH00354

Child: Starting aa....aa worker threads.

aa....aa: Number of threads

Description

Generation of server threads for the number indicated in aa....aa will start.

AH00355

Child: CreateThread failed. Unable to create all worker threads. Created aa....aa of the bb....bb threads requested with the ThreadsPerChild configuration directive.

aa....aa: Number of generated threads

bb....bb: Directive value

Description

An attempt to generate a thread failed during generation of server threads for the number specified in the ThreadsPerChild directive. The server process requests the control process to stop the Web server.

Action

Revise the specification according to the detailed information about CreateThread() shown in this message.

AH00356

Child: WAIT_FAILED -- shutting down server

Description

The server process has failed to wait for the termination event, planned termination event, or the event for the maximum number of requests. The server process terminates.

Action

Revise the specification according to the detailed information about WaitForMultipleObjects() shown in this message.

AH00360

Child: Failure releasing the start mutex

Description

An attempt to release the lock for mutual exclusion of server process has failed. The server process continues the end processing.

Action

Revise the specification according to the detailed information about ReleaseMutex() shown in this message.

AH00362

Child: Waiting aa....aa more seconds for bb....bb worker threads to finish.

aa....aa: Remaining number of seconds to wait for the server threads to terminate

bb....bb: Number of running server threads

Description

The server process will wait for termination of the server threads for aa....aa seconds.

AH00363

Child: Terminating aa....aa threads that failed to exit.

aa....aa: Number of server threads that have not terminated

Description

The un-terminated server threads will be terminated forcibly.

AH00364

Child: All worker threads have exited.

Description

All server threads have terminated.

AH00365

Failure registering service handler

Description

An attempt to register the service control request processing function in the service control manager has failed. The service startup processing stops.

Action

Revise the specification according to the detailed information about RegisterServiceCtrlHandler() shown in this message.

AH00366

Error starting service control dispatcher

Description

An attempt to set up the service control dispatcher thread in the service control manager has failed. The service startup processing stops.

Action

Revise the specification according to the detailed information about StartServiceCtrlDispatcher() shown in this message.

AH00367

No ConfigArgs registered for aa....aa, perhaps this service is not installed?

aa....aa: Service name

Description

The registry entry ConfigArgs of the service described in the aa....aa does not exist. The Web server continues the startup processing.

Action

Confirm that the service has been installed.

AH00382

OpenEvent on aa....aa event

aa....aa: Event name

Description

An attempt to open the event has failed. The Web server stops the termination and restart processing.

Action

Revise the specification according to the detailed information about OpenEvent() shown in this message.

AH00383

SetEvent on aa....aa event

aa....aa: Event name

Description

An attempt to report the event has failed. The Web server stops the termination and restart processing.

Action

Revise the specification according to the detailed information about SetEvent() shown in this message.

AH00384

Child: Unable to retrieve the ready event from the parent

Description

The start event handle of the server process could not be acquired from the control process. The server process terminates.

Action

Revise the specification according to the detailed information about ReadFile() shown in this message.

AH00385

Child: Unable to retrieve the exit event from the parent

Description

The end event handle of the server process could not be acquired from the control process. The server process terminates.

Action

Revise the specification according to the detailed information about ReadFile() shown in this message.

AH00386

Child: Unable to retrieve the start_mutex from the parent

Description

The handler for the mutual exclusion could not be retrieved from the control process.

Action

Revise the specification according to the detailed information about ReadFile() shown in this message.

AH00387

Child: Unable to access the start_mutex from the parent

Description

The handler for mutual exclusion could not be accessed. The server process terminates.

Action

Revise the specification according to the detailed information shown in this message.

AH00388

Child: Unable to retrieve the scoreboard from the parent

Description

The handler for the scoreboard could not be acquired from the control process. The server process terminates.

Action

Revise the specification according to the detailed information about ReadFile() shown in this message.

AH00389

Child: Unable to access the scoreboard from the parent

Description

The scoreboard could not be accessed. The server process terminates.

Action

Revise the specification according to the detailed information about MapViewOfFile() shown in this message.

AH00390

Child: Unable to reopen the scoreboard from the parent

Description

The scoreboard could not be opened. The server process terminates.

Action

Revise the specification according to the detailed information shown in this message.

AH00392

Parent: Unable to duplicate the ready event handle for the child

Description

The start event handle of the server process could not be duplicated. The Web server stops the start processing.

Action

Revise the specification according to the detailed information about DuplicateHandle() shown in this message.

AH00393

Parent: Unable to send the ready event handle to the child

Description

The start event handle of the server process could not be sent. The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

AH00394

Parent: Unable to duplicate the exit event handle for the child

Description

The end event handle of the server process could not be duplicated. The Web server stops the start processing.

Action

Revise the specification according to the detailed information about DuplicateHandle() shown in this message.

AH00395

Parent: Unable to send the exit event handle to the child

Description

The end event handle could not be sent to the server process. The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

AH00397

Parent: Unable to duplicate the start mutex to the child

Description

The handle for mutual exclusion could not be duplicated. The Web server stops the start processing.

Action

Revise the specification according to the detailed information about DuplicateHandle() shown in this message.

AH00398

Parent: Unable to send the start mutex to the child

Description

The handle for mutual exclusion could not be sent to the server process. The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

AH00400

Parent: Unable to duplicate the scoreboard handle to the child

Description

The handle for the scoreboard could not be duplicated. The Web server stops the start processing.

Action

Revise the specification according to the detailed information about DuplicateHandle() shown in this message.

AH00401

Parent: Unable to send the scoreboard handle to the child

Description

The handle for the scoreboard could not be sent to the server process. The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

AH00404

Child: Unable to read socket data from parent

Description

The socket data from the control process could not be read. The server process terminates.

Action

Revise the specification according to the detailed information about ReadFile() shown in this message.

AH00405

Child: WSASocket failed to open the inherited socket

Description

An attempt to open the inherited data has failed. The server process terminates.

Action

Revise the specification according to the detailed information about WSASocket() shown in this message.

AH00406

Child: SetHandleInformation failed

Description

An attempt to set up properties for the object handle has failed. The server process continues the initialization processing.

Action

Revise the specification according to the detailed information about SetHandleInformation() shown in this message.

AH00409

Parent: WSADuplicateSocket failed for socket aa....aa.

aa....aa: File descriptor (fd) number

Description

The control process failed to duplicate the socket. The generation of the server process will now stop.

Action

Revise the specification according to the detailed information about WSADuplicateSocket() shown in this message.

AH00410

Parent: Unable to write duplicated socket aa....aa to the child.

aa....aa: File descriptor (fd) number

Description

The control process failed to write the duplicated socket to the server process. The generation of the server process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

AH00412

Parent: Failed to get the current path

Description

An attempt to acquire current thread information has failed. The Web server continues the start processing.

Action

Revise the specification according to the detailed information shown in this message.

AH00413

Parent: Failed to get full path of aa....aa

aa....aa: Startup command

Description

An attempt to acquire the absolute path of the aa....aa has failed. The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

AH00414

Parent: Unable to create child stdin pipe.

Description

An attempt to generate a pipe for sending information to the server process has failed. The generation of the server process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

AH00415

Parent: Could not create ready event for child process

Description

An attempt to generate a start event for the server process has failed. The generation of the server process will now stop.

Action

Revise the specification according to the detailed information about CreateEvent() shown in this message.

AH00416

Parent: Could not create exit event for child process

Description

An attempt to generate an end event for the server process has failed. The generation of the server process will now stop.

Action

Revise the specification according to the detailed information about CreateEvent() shown in this message.

AH00417

Parent: Failed to create the child process.

Description

An attempt to generate the server process has failed. The generation of the server process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

AH00418

Parent: Created child process aa....aa

aa....aa: Process ID

Description

A server process was created.

AH00419

master_main: create child process failed. Exiting.

Description

The control process failed to generate the server process. The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

AH00420

master_main: WaitForMultipleObjects WAIT_FAILED -- doing server shutdown

Description

The control process has failed to wait for the termination event, planned termination event, or restart event. The Web server will shut down.

Action

Revise the specification according to the detailed information about WaitForMultipleObjects() shown in this message.

AH00421

master_main: WaitForMultipleObjects with INFINITE wait exited with WAIT_TIMEOUT

Description

A timeout occurred when the server process was waiting for the termination event, planned termination event, or restart event, even when INFINETE was specified. The Web server will shut down.

Action

Revise the specification according to the detailed information about WaitForMultipleObjects() shown in this message.

AH00422

Parent: Received shutdown signal -- Shutting down the server.

Description

The termination event was reported to the control process. The Web server starts the termination processing.

AH00423

ResetEvent(shutdown_event)

Description

The control process failed to release the termination event. The Web server continues the termination processing.

Action

Revise the specification according to the detailed information about ResetEvent() shown in this message.

AH00424

Parent: Received restart signal -- Restarting the server.

Description

The restart event was reported to the control process. The Web server starts the restart processing.

AH00425

Parent: ResetEvent(restart_event) failed.

Description

The control process failed to release the restart event. The Web server continues the restart processing.

Action

Revise the specification according to the detailed information about ResetEvent() shown in this message.

AH00426

Parent: SetEvent for child process event aa....aa failed.

aa....aa: Handle number

Description

The control process has failed to set up a termination event for the server process. The Web server continues the restart processing.

Action

Revise the specification according to the detailed information about SetEvent() shown in this message.

AH00427

Parent: child process aa....aa exited with status bb....bb -- Aborting.

aa....aa: Process ID

bb....bb: End code

Description

The server process terminated with the bb....bb. The termination processing of the Web server will start.

Action

Revise according to the cause described in the end code.

AH00428

Parent: child process aa....aa exited with status bb....bb -- Restarting.

aa....aa: Process ID

bb....bb: End code

Description

The server process ended with bb....bb. The Web server starts the restart processing.

AH00429

Parent: SetEvent for child process event aa....aa failed

aa....aa: Handle number

Description

The control process has failed to set up a termination event for the server process. The termination processing of the Web server will continue.

Action

Revise the specification according to the detailed information about SetEvent() shown in this message.

AH00430

Parent: Child process aa....aa exited successfully.

aa....aa: Process ID

Description

The server process ended successfully. The Web server continues the termination processing.

AH00431

Parent: Forcing termination of child process aa....aa

aa....aa: Process ID

Description

The control process will forcibly terminate the server process that does not terminate with the specified termination event. The Web server continues the termination processing.

Action

Revise the cause due to which the server process does not terminate.

AH00432

Failed to get the full path of aa....aa

aa....aa: Startup command

Description

An attempt to acquire the absolute path of the aa....aa has failed. The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

AH00433

aa....aa: Service is already installed.

aa....aa: Service name

Description

An attempt was made to install an already installed service. The service installation processing in the Web server will be interrupted.

Action

Check the service.

AH00434

Using ConfigArgs of the installed service "aa....aa".

aa....aa: Service name

Description

The registry entry ConfigArgs of the service specified in the aa....aa is used in the startup option.

AH00435

No installed ConfigArgs for the service "aa....aa", using Server defaults.

aa....aa: Service name

Description

The default settings will be used for startup because the contents of the registry entry ConfigArgs of the service specified in the aa....aa cannot be acquired. The Web server continues the start processing.

Action

Make sure that the registry entry ConfigArgs exists below the registry key of the aa....aa.

AH00436

No installed service named "aa....aa".

aa....aa: Service name

Description

An uninstalled service is specified. The Web server stops the start processing.

Action

Check the service.

AH00437

No installed service named "aa....aa".

aa....aa: Service name

Description

An uninstalled service is specified. The Web server stops the start processing.

Action

Check the service.

AH00438

aa....aa: Unable to start the service manager.

aa....aa: Service name

Description

An attempt to start the service has failed. The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

AH00444

WARNING: ThreadsPerChild of aa....aa exceeds ThreadLimit of

bb....bb threads, decreasing to cc....cc.

To increase, please see the ThreadLimit directive.

aa....aa: Value specified in the ThreadsPerChild directive

bb....bb: Value specified in the ThreadLimit directive

cc....cc: Value specified in the ThreadLimit directive

Description

A value exceeding the specifiable maximum limit is specified for the ThreadsPerChild directive. The Web server sets the ThreadLimit directive value for the ThreadsPerChild directive value, and then continues the startup processing.

Action

Revise the ThreadsPerChild directive and ThreadLimit directive values.

AH00445

ThreadsPerChild of aa....aa exceeds ThreadLimit of bb....bb, decreasing to match

aa....aa: Value specified in the ThreadsPerChild directive

bb....bb: Value specified in the ThreadLimit directive

Description

A value exceeding the specifiable maximum limit is specified for the ThreadsPerChild directive. The Web server sets the ThreadLimit directive value for the ThreadsPerChild directive value, and then continues the startup processing.

Action

Revise the ThreadsPerChild directive and ThreadLimit directive values.

AH00446

WARNING: ThreadsPerChild of aa....aa not allowed, increasing to 1.

aa....aa: Specified value

Description

An invalid value is specified in ThreadsPerChild directive. 1 will be set up for the ThreadsPerChild directive value of the Web server, and the startup processing will continue.

Action

Revise the ThreadsPerChild directive value.

AH00448

Parent: Cannot create shutdown event aa....aa

aa....aa: Event name

Description

The control process has failed to generate the termination event. The Web server stops the start processing.

Action

Revise the specification according to the detailed information about CreateEvent() shown in this message.

AH00449

Parent: Cannot create restart event aa....aa

aa....aa: Event name

Description

The control process has failed to generate the restart event. The Web server stops the restart processing.

Action

Revise the specification according to the detailed information about CreateEvent() shown in this message.

AH00450

aa....aa: Unable to create the start_mutex.

aa....aa: Service name

Description

An attempt to generate an executive handler has failed. The Web server stops the start processing.

Action

Revise the specification according to the detailed information about CreateMutexW() shown in this message.

AH00451

no listening sockets available, shutting down

Description

There is no socket in the listen status. The Web server stops the start processing.

Action

Based on the Listen directive, make sure that the cause of occurrence is not the failure to generate a socket.

AH00455

aa....aa configured -- resuming normal operations

aa....aa: Server name

Description

The startup of the Web server has started.

AH00456

Server built: aa....aa

aa....aa: Time when Web server was created

Description

The time of creation of the Web server that is started is displayed.

AH00526

Syntax error on line aa....aa of bb....bb:

cc....cc

aa....aa: Line number

bb....bb: File name

cc....cc: Error message

Description

A syntax error exists at the position specified in the bb....bb and aa....aa. The Web server stops the start processing.

Action

Based on cc....cc, revise the line in which the syntax error occurred.

AH00529

aa....aa pcfg_openfile: unable to check htaccess file, ensure it is readable and that 'bb....bb' is executable

aa....aa: Access control file name

bb....bb: File name

Description

The access control file cannot be read.

The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.

Action

Revise the access control file according to the detailed information shown in this message.

AH00532

Invalid config file path aa....aa

aa....aa: Config file name

Description

The path of the configuration file is invalid. The Web server stops the start processing.

Action

Revise according to the path specified in aa....aa.

AH00534

httpsd: Configuration error: aa....aa

aa....aa: No MPM loaded., More than one MPM loaded., or The MPM cannot be changed during restart.

Description

An error exists in the specification for loading the MPM module. The Web server stops the startup or restart processing.

Action

Revise the LoadModule directive concerning the MPM module.

AH00542

apr_socket_opt_set: (TCP_NODELAY)

Description

An error occurred during the setup of the IP protocol-level option TCP_NODELAY. The Web server continues the start processing without the setup of the TCP_NODELAY option. The Nagle buffering algorithm is enabled.

Action

Revise the specification according to the detailed information about setsockopt() shown in this message.

AH00543

aa....aa: bad user name bb....bb

aa....aa: Command name

bb....bb: User name

Description

The specified user is not registered in the system. The processing terminates.

Action

Specify the user name registered in the system.

AH00544

aa....aa: bad group name bb....bb

aa....aa: Command name

bb....bb: Group name

Description

The specified group is not registered in the system. The processing terminates.

Action

Specify the group name registered in the system.

AH00547

Could not resolve host name aa....aa -- ignoring!

aa....aa: Virtual host name -

Description

The specification will be ignored because an invalid virtual host is specified. The Web server continues the start processing.

Action

Revise the host name specified in the VirtualHost directive.

AH00548

NameVirtualHost has no effect and will be removed in the next release aa....aa:bb....bb

aa....aa: Config file name

bb....bb: Line number

Description

The specified NameVirtualHost directive is ignored. The Web server continues the start processing.

Action

Delete the specified NameVirtualHost directive from the portion shown in the message.

AH00549

Failed to resolve server name for aa....aa (check DNS) -- or specify an explicit ServerName

aa....aa: IP address

Description

An attempt to resolve the host name specified in the VirtualHost directive has failed. The virtual host whose host name could not be resolved in the Web server will be ignored, and the startup processing will continue. The virtual host that could not be resolved is not recognized as a virtual host.

Action

Revise the host name specified in the VirtualHost directive.

AH00554

Access to file aa....aa denied by server: not a regular file

aa....aa: file name

Description

The Web server denied the access to the file because the file is not a standard file. The Web server stops the start processing.

Action

Check to make sure that the accessed file is a standard file.

AH00556

aa....aa: apr_gethostname() failed to determine ServerName

aa....aa: Command name

Description

An attempt to determine ServerName with gethostname() has failed. The Web server address will be assumed as 127.0.0.1.

Action

Revise according to the cause because of which the host name cannot be acquired.

AH00558

aa....aa: Could not reliably determine the server's fully qualified domain name, using bb....bb. Set the 'ServerName' directive globally to suppress this message

aa....aa: Command name

bb....bb: Web server name

Description

The Web server name will be used as the ServerName because the complete domain name of the server could not be resolved. The Web server name will be used as ServerName.

AH00562

Request header exceeds LimitRequestFieldSize after folding: aa....aa

aa....aa: Request header name

Description

The request header size exceeds the LimitRequestFieldSize directive value.

The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.

Action

Make sure that the request header size does not exceed the LimitRequestFieldSize directive value.

AH00563

Number of request headers exceeds LimitRequestFields

Description

The number of request headers exceeds the LimitRequestFields directive value.

The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.

Action

Make sure that the number of request headers does not exceed the LimitRequestFields directive value.

AH00565

request failed: client's request-line exceeds LimitRequestLine (longer than aa....aa)

aa....aa: LimitRequestLine directive value

Description

The length of the request line exceeds the LimitRequestLine directive value.

The status code 414 Request-URI Too Large will be returned to the client, and the request processing will be interrupted.

Action

Check to make sure that the string specified in the request line (URI or HTTP version, including the methods and query strings) does not exceed the LimitRequestLine directive value.

AH00567

request failed: error reading the headers

Description

An error occurred while the request header was being read.

The status code 400 Bad Request or 408 Request Time-out will be returned to the client, and the request processing will be interrupted.

Action

Make sure that a valid request header is specified. Also make sure that the number of request headers does not exceed the maximum limit specified by the server.

AH00569

client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): aa....aa

aa....aa: Requested URI value

Description

The request processing cannot be continued because the client has sent the HTTP/1.1 request without adding the HOST header.

The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.

Action

Make sure that the HOST header is added to the HTTP/1.1 request.

AH00571

need AuthType to note auth failure: aa....aa

aa....aa: Requested URI value

Description

The authentication type name to be specified in the AuthType directive during user authentication is not specified.

The status code 401 Authorization Required will be returned, and the request processing will terminate.

Action

Specify the AuthType directive when performing user authentication.

AH00572

need AuthName: aa....aa

aa....aa: Requested URI value

Description

The realm name to be specified in the AuthName directive during user authentication is not specified.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Specify the AuthName directive when performing user authentication.

AH00573

client used wrong authentication scheme: aa....aa

aa....aa: Requested URI value

Description

The type of authentication control of the Authorization header during user authentication is invalid.

The status code 401 Authorization Required will be returned, and the request processing will terminate.

Action

Only Basic can be specified in the Authorization header. Revise the specified value of the Authorization header.

AH00574

ap_content_length_filter: apr_bucket_read() failed

Description

An attempt to read the response data has failed.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH00648

invalid transfer log path aa....aa.

aa....aa: File name

Description

The log file is invalid. The Web server stops the start processing.

Action

Revise the settings of the TransferLog directive or CustomLog directive.

AH00649

could not open transfer log file aa....aa.

aa....aa: File name

Description

Cannot open the log file. The Web server stops the start processing.

Action

Revise the settings of the TransferLog directive or CustomLog directive.

AH00652

File does not exist: aa....aa

aa....aa: File name

Description

The requested file cannot be found.

The status code 404 Not Found will be returned to the client, and the request processing will be interrupted.

Action

Revise the requested file name.

AH00671

The aa....aa directive in bb....bb at line cc....cc will probably never match because it overlaps an earlier dd....dd.

aa....aa: Directive

bb....bb: Config file name

cc....cc: Line number

dd....dd: Directive

Description

A directive that can be applied to the same URL is specified twice. The second specification will not be applicable.

Action

Revise the settings of the directive in the displayed line.

AH00674

cannot redirect 'aa....aa' to 'bb....bb'; target is not a valid absoluteURI or abs_path

aa....aa: Request URI

bb....bb: Redirect destination

Description

Cannot redirect to the redirect destination. The specified redirect destination is not a URL.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Make sure that the specified redirect destination is a URL.

AH00676

cannot redirect 'aa....aa' to 'bb....bb'; target is not a valid absoluteURI or abs_path

aa....aa: Request URI

bb....bb: Redirect destination

Description

Cannot redirect to the redirect destination. The specified redirect destination is not a URL.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Make sure that the specified redirect destination is a URL.

AH00690

no acceptable variant: aa....aa

aa....aa: File name

Description

The client cannot accept the results of content negotiation by the Web server.

The status code 406 Not Acceptable will be returned, and the request processing will terminate.

AH00898

aa....aa returned by bb....bb

aa....aa: Message

bb....bb: Request URI

Description

An error indicated in aa....aa occurred.

Action

Check the cause of the message.

AH00940

aa....aa: disabled connection for (bb....bb)

aa....aa: Scheme name

bb....bb: Transfer destination host name

Description

The transfer destination host could not be connected.

Action

Make sure that connection with the transmission-destination host specified in the ProxyPass directive is possible.

AH00952

aa....aa: error creating fam bb....bb socket for target cc....cc

aa....aa: Scheme name

bb....bb: Address family

cc....cc: Host name

Description

An attempt to create a socket has failed.

Action

Revise the specification according to the detailed information shown in this message.

AH00957

aa....aa: attempt to connect to bb....bb:cc....cc (dd....dd) failed

aa....aa: Scheme name

bb....bb: IP address

cc....cc: Port number

dd....dd: Host name

Description

An attempt to connect to the remote Web server failed.

Action

Revise the specification according to the detailed information shown in this message.

AH00959

ap_proxy_connect_backend disabling worker for (aa....aa) for bb....bbs

aa....aa: Host name

bb....bb: Number of seconds

Description

Connection to aa....aa will be disabled for bb....bb seconds.

AH01083

error parsing URL aa....aa: bb....bb

aa....aa: URL

bb....bb: Detailed information

Description

An error occurred during the analysis of the URL by the reverse proxy.

The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.

Action

Revise the URL specified in the ProxyPass directive according to the cause specified in bb....bb.

AH01084

pass request body failed to aa....aa:bb....bb (cc....cc)

aa....aa: IP address

bb....bb: Port number

cc....cc: Host name

Description

The reverse proxy failed to send the request body to the remote Web server.

Action

Revise the specification according to the detailed information shown in this message.

AH01087

client aa....aa given Content-Length did not match number of body bytes read

aa....aa: Client address

Description

The size of the request body sent by the client is different from the value of the Content-Length header.

The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.

Action

Check to make sure that the value of the Content-Length request header is correct.

AH01088

Request body is larger than the configured limit of aa....aa

aa....aa: LimitRequestBody directive value

Description

A body of a size larger than the aa....aa was read.

The status code 413 Request Entity Too Large will be returned to the client, and the request processing will be interrupted.

Action

Revise the specified value of the LimitRequestBody directive. Specify 0 if no upper-limit value is set up for the request body size.

AH01089

search for temporary directory failed

Description

The reverse proxy failed to search the directory that temporarily stores the request body.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH01090

creation of temporary file in directory aa....aa failed

aa....aa: Directory name

Description

The reverse proxy failed to create the file that temporarily stores the request body.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH01091

write to temporary file aa....aa failed

aa....aa: File name

Description

The reverse proxy failed to write in the file that temporarily stores the request body.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH01092

no HTTP 0.9 request (with no host line) on incoming request and preserve host set forcing hostname to be aa....aa for uri bb....bb

aa....aa: Host name

bb....bb: URI

Description

The Host header is not included in the request header received from the client.

The processing will continue by sending the Host header created in the reverse proxy to the remote Web server.

Action

Revise the client settings.

AH01093

aa....aa Transfer-Encoding is not supported

aa....aa: Transfer-Encoding header value

Description

The Transfer-Encoding header value sent by the client is not supported.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Specify chunked for the Transfer-Encoding header value.

AH01095

prefetch request body failed to aa....aa:bb....bb (cc....cc) from dd....dd (ee....ee)

aa....aa: IP address

bb....bb: Port number

cc....cc: Host name

dd....dd: Client address

ee....ee: Client host name

Description

The reverse proxy failed to receive the request body from the client.

The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH01096

processing prefetched request body failed to aa....aa:bb....bb (cc....cc) from dd....dd (ee....ee)

aa....aa: IP address

bb....bb: Port number

cc....cc: Host name

dd....dd: Client address

ee....ee: Client host name

Description

The reverse proxy failed to receive the request body from the client.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH01097

pass request body failed to aa....aa:bb....bb (cc....cc) from dd....dd (ee....ee)

aa....aa: IP address

bb....bb: Port number

cc....cc: Host name

dd....dd: Client address

ee....ee: Client host name

Description

The reverse proxy failed to send the request body.

AH01102

error reading status line from remote server aa....aa:bb....bb

aa....aa: IP address

bb....bb: Port number

Description

The reverse proxy failed to read the status line from the remote Web server.

The status code 502 Proxy Error will be returned to the client, and the request processing will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH01106

bad HTTP/aa....aa.bb....bb header returned by cc....cc (dd....dd)

aa....aa: Major version

bb....bb: Minor version

cc....cc: URI

dd....dd: Method

Description

The remote Web server has sent an invalid HTTP header.

The status code 502 Bad Gateway will be returned to the client, and the request processing will be interrupted.

Action

Revise the settings of the remote Web server.

AH01110

error reading response

Description

The reverse proxy failed to read the response body from the remote Web server.

The status code 502 Bad Gateway will be returned to the client, and the request processing will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH01114

HTTP: failed to make connection to backend: aa....aa

aa....aa: Host name

Description

The reverse proxy failed to establish a connection with the remote Web server.

AH01139

TRACE forbidden by server configuration

Description

The request issued by the TRACE method is denied because of the settings of the TraceEnable directive.

The status code 405 Method Not Allowed will be returned to the client, and the request processing will be interrupted.

Action

To allow access, revise the settings of the TraceEnable directive.

AH01140

TRACE with request body is not allowed

Description

The request issued by the TRACE method having a request body is denied because of the settings of the TraceEnable directive.

The status code 413 Request Entity Too Large will be returned to the client, and the request processing will be interrupted.

Action

To allow access, revise the settings of the TraceEnable directive.

AH01144

No protocol handler was valid for the URL aa....aa. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.

aa....aa: URL

Description

The schema specified in the ProxyPass directive is invalid.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Revise the transfer-destination schema of the ProxyPass directive.

AH01145

Sharing worker 'aa....aa' instead of creating new worker 'bb....bb'

aa....aa: URL1

bb....bb: URL2

Description

The ProxyPass directive corresponding to URL2 shares the connection and settings with the ProxyPass directive corresponding to URL1.

AH01146

Ignoring parameter 'aa....aa' for worker 'bb....bb' because of worker sharing

aa....aa: Key specification in the ProxyPass directive

bb....bb: URL

Description

The key specification in the ProxyPass directive corresponding to the URL is ignored, and the value of another ProxyPass directive that shares the settings will be used.

Action

Revise the key specification in the ProxyPass directive.

AH01222

don't know how to spawn child process: aa....aa

aa....aa: File name

Description

The process cannot be generated.

The status code 500 Internal Server Error will be returned, and the request processing will terminate.

Action

Check the system status according to the detailed information shown in this message.

AH01223

couldn't spawn child process: aa....aa

aa....aa: File name

Description

The process for the CGI program could not be generated.

The status code 500 Internal Server Error will be returned, and the request processing will terminate.

Action

Check the system status according to the detailed information shown in this message.

AH01224

Timeout during reading request entity data

Description

A timeout occurred when the request body was received from the client.

The status code 408 Request Time-out will be returned to the client, and the request processing will be interrupted.

Action

Check the cause of the timeout.

AH01225

Error reading request entity data

Description

An attempt to receive the request body from the client failed.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH01275

Can't open directory for index: aa....aa

aa....aa: Directory name

Description

The directory for directory indexing cannot be opened.

The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.

Action

Check the system status according to the detailed information shown in this message.

AH01276

Cannot serve directory aa....aa: No matching DirectoryIndex (bb....bb) found, and server-generated directory index forbidden by Options directive

aa....aa: Directory name

bb....bb: Value specified in the DirectoryIndex directive

Description

The directory index cannot be displayed due to the setting in the Options directive.

The status code 403 Forbidden will be returned, and the request processing will terminate.

Action

To enable the directory index, change the setting in the Options directive.

AH01382

Request aa....aa read timeout

aa....aa: header or body

Description

A timeout occurred during reception processing of the request header (including the request line) from the client or during reception processing of the request body.

Action

This message was output because the time specified in the RequestReadTimeout directive elapsed. Revise the value specified in the RequestReadTimeout directive.

AH01506

PassEnv variable aa....aa was undefined

aa....aa: Environment variable

Description

The aa....aa specified in the PassEnv directive is not defined as an environment variable.

Action

Set up the environment variable.

AH01574

module aa....aa is already loaded, skipping

aa....aa: Module name

Description

The processing will not be executed because the Web server is already incorporated into the module.

Action

Revise the description of the LoadModule directive.

AH01580

Invalid error redirection directive: aa....aa

aa....aa: Redirect destination

Description

A grammatical error exists in the customization method specified in the ErrorDocument directive. The error status number will not be customized.

Action

To customize the error messages with the ErrorDocument directive, specify the text, local URL, or full URL. For details, see the explanation about the ErrorDocument directive.

AH01585

Unknown Transfer-Encoding: aa....aa

aa....aa: Transfer-Encoding header value

Description

The value specified in the Transfer-Encoding header is invalid.

The status code 501 Method Not Implemented will be returned to the client, and the request processing will be interrupted.

Action

Other than chunked is specified in the Transfer-Encoding header. Revise the Transfer-Encoding header.

AH01586

Unknown Transfer-Encoding: aa....aa; using Content-Length

aa....aa: Transfer-Encoding header value

Description

The value specified in the Transfer-Encoding header is invalid.

The processing continues using the Content-Length header value.

Action

Other than chunked is specified in the Transfer-Encoding header. Revise the Transfer-Encoding header.

AH01587

Invalid Content-Length

Description

The length specified in the Content-Length header is invalid.

The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.

Action

You can only specify a numeric value (decimal number) in the Content-Length header. Revise the specified value.

AH01588

Requested content-length of aa....aa is larger than the configured limit of bb....bb

aa....aa: Specified length (bytes)

bb....bb: LimitRequestBody directive value (bytes)

Description

A value greater than the LimitRequestBody directive value is specified as the length in the Content-Length header.

The status code 413 Request Entity Too Large will be returned to the client, and the request processing will be interrupted.

Action

Revise the specified value of the LimitRequestBody directive. Specify 0 if no upper-limit value is set up for the request body size.

AH01589

Error reading first chunk aa....aa

aa....aa: (overflow) or null

Description

The correct chunk size could not be acquired.

The status code 400 Bad Request or 408 Request Time-out will be returned to the client, and the request processing will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH01590

Error reading chunk aa....aa

aa....aa: (overflow) or null

Description

The correct chunk size could not be acquired.

The status code 400 Bad Request or 408 Request Time-out will be returned to the client, and the request processing will be interrupted.

Action

Revise the specification according to the detailed information shown in this message.

AH01591

Read content length of aa....aa is larger than the configured limit of bb....bb

aa....aa: Request body size that was read (bytes)

bb....bb: LimitRequestBody directive value (bytes)

Description

A body of a size larger than the bb....bb was read.

The status code 413 Request Entity Too Large will be returned to the client, and the request processing will be interrupted.

Action

Revise the specified value of the LimitRequestBody directive. Specify 0 if no upper-limit value is set up for the request body size.

AH01596

Invalid mime types config path aa....aa

aa....aa: File name

Description

The path of the file specified with the TypesConfig directive is invalid. The startup processing of the Web server will terminate.

Action

Revise the settings of TypesConfig directive.

AH01597

could not open mime types config file aa....aa.

aa....aa: File name

Description

The file specified with the TypesConfig directive cannot be opened. The startup processing of the Web server will terminate.

Action

Revise the settings of TypesConfig directive.

AH01598

mod_mime: analyze_ct: cannot get media type from 'aa....aa'

aa....aa: Media type

Description

The media type of MIME cannot be acquired properly. The request process continues.

Action

Revise the MIME settings.

AH01599

Cannot get media type from 'aa....aa'

aa....aa: Media type

Description

The media subtype of MIME cannot be acquired properly. The request process continues.

Action

Revise the MIME settings.

AH01600

mod_mime: analyze_ct: cannot get media type from 'aa....aa'

aa....aa: Media type

Description

The media type of MIME cannot be acquired properly. The request process continues.

Action

Revise the MIME settings.

AH01601

Cannot get media subtype.

Description

The media subtype of MIME cannot be acquired properly. The request process continues.

Action

Revise the MIME settings.

AH01602

Cannot get media parameter.

Description

The media parameters of MIME cannot be acquired properly. The request process continues.

Action

Revise the MIME settings.

AH01603

Cannot get media parameter.

Description

The media parameters of MIME cannot be acquired properly. The request process continues.

Action

Revise the MIME settings.

AH01604

Cannot get media parameter.

Description

The media parameters of MIME cannot be acquired properly. The request process continues.

Action

Revise the MIME settings.

AH01605

Cannot get media parameter.

Description

The media parameters of MIME cannot be acquired properly. The request process continues.

Action

Revise the MIME settings.

AH01606

Cannot get media parameter.

Description

The media parameters of MIME cannot be acquired properly. The request process continues.

Action

Revise the MIME settings.

AH01607

Cannot get media parameter.

Description

The media parameters of MIME cannot be acquired properly. The request process continues.

Action

Revise the MIME settings.

AH01608

Cannot get media parameter.

Description

The media parameters of MIME cannot be acquired properly. The request process continues.

Action

Revise the MIME settings.

AH01609

Cannot get media parameter.

Description

The media parameters of MIME cannot be acquired properly. The request process continues.

Action

Revise the MIME settings.

AH01614

client used wrong authentication scheme: aa....aa

aa....aa: Requested URI value

Description

The type of authentication control of the Authorization header during user authentication is invalid.

The status code 401 Authorization Required will be returned, and the request processing will terminate.

Action

Only Basic can be specified in the Authorization header. Revise the specified value of the Authorization header.

AH01615

need AuthName: aa....aa

aa....aa: Requested URI value

Description

The realm name to be specified in the AuthName directive during user authentication is not specified.

The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.

Action

Specify the AuthName directive when performing user authentication.

AH01617

user aa....aa: authentication failure for "bb....bb": Password Mismatch

aa....aa: User name

bb....bb: Requested URI value

Description

An authentication error occurred in the client from which the requested URI was attempted to be accessed.

The status code 401 Authorization Required will be returned, and the request processing will terminate.

Action

Revise the password.

AH01618

user aa....aa not found: bb....bb

aa....aa: User name

bb....bb: Requested URI value

Description

The user name sent from the client from which the requested URI was attempted to be accessed could not be found in the list of user names that can access the URI.

The status code 401 Authorization Required will be returned, and the request processing will terminate.

Action

To allow access permission to the user, add the user name to the settings.

AH01627

AuthType configured with no corresponding authorization directives

Description

A directive that must be specified together with the AuthType directive is not specified.

The status code 500 Internal Server Error will be returned, and the request processing will terminate.

Action

Revise the specified directives concerning user authentication.

AH01630

client denied by server configuration: aa....aa

aa....aa: File name or requested URI value

Description

Access was denied due to the server settings.

Action

To allow access, change the settings.

AH01631

user aa....aa: authorization failure for "bb....bb":

aa....aa: User name

bb....bb: Requested URI value

Description

The user who attempted to access the requested URI was denied.

The status code 401 Authorization Required or 403 Forbidden will be returned, and the request processing will terminate.

Action

To allow access, change the settings.

AH01637

Authorization of user aa....aa to access bb....bb failed, reason: file owner cc....cc does not match.

aa....aa: User name

bb....bb: Requested URI value

cc....cc: Owner name

Description

Access was not allowed because the user was not the file owner.

AH01663

access to aa....aa failed, reason: user 'bb....bb' does not meet 'require'ments for user to be allowed access

aa....aa: Requested URI value

bb....bb: User name

Description

Access was not allowed because the user did not match the user specified in Require.

Action

To allow access, change the settings.

AH01664

No group file was specified in the configuration

Description

The AuthGroupFile directive is not specified.

Action

To restrict access by group, specify the AuthGroupFile directive.

AH01665

Could not open group file: aa....aa

aa....aa: File name

Description

The file specified with the AuthGroupFile directive cannot be opened.

Action

Revise the settings of AuthGroupFile directive.

AH01666

Authorization of user aa....aa to access bb....bb failed, reason: user doesn't appear in group file (cc....cc).

aa....aa: User name

bb....bb: Requested URI value

cc....cc: Group file

Description

Access was not allowed because the group of the user who attempted to access the requested URI was not in the group file.

Action

To allow access, revise the file specified with the AuthGroupFile directive.

AH01667

Authorization of user aa....aa to access bb....bb failed, reason: user is not part of the 'require'ed group(s).

aa....aa: User name

bb....bb: Requested URI value

Description

Access was not allowed because the user did not match the group specified in Require.

Action

To allow access, change the settings.

AH01668

No group file was specified in the configuration

Description

The AuthGroupFile directive is not specified.

Action

To restrict access by group, specify the AuthGroupFile directive.

AH01669

Could not open group file: aa....aa

aa....aa: File name

Description

The file specified with the AuthGroupFile directive cannot be opened.

Action

Revise the settings of AuthGroupFile directive.

AH01670

Authorization of user aa....aa to access bb....bb failed, reason: user doesn't appear in group file (cc....cc).

aa....aa: User name

bb....bb: Requested URI value

cc....cc: Group file

Description

Access was not allowed because the group of the user who attempted to access the requested URI was not in the group file.

Action

To allow access, revise the file specified with the AuthGroupFile directive.

AH01671

Authorization of user aa....aa to access bb....bb failed, reason: user is not part of the 'require'ed file group.

aa....aa: User name

bb....bb: Requested URI value

Description

Access was not allowed because the user did not match the file group specified in Require.

Action

To allow access, change the settings.

AH01796

AuthType aa....aa configured without corresponding module

aa....aa: AuthType directive value

Description

The module corresponding to the specified AuthType directive has not been loaded.

The status code 500 Internal Server Error will be returned, and the request processing will terminate.

Action

Revise the AuthType directive value.

AH01797

client denied by server configuration: aa....aa

aa....aa: File name or requested URI value

Description

Access was denied due to the server settings.

Action

To allow access, change the settings.

AH02100

Failed to open cgi file aa....aa for testing

aa....aa: File name

Description

An attempt to open the file failed. The process of executing the script will now stop.

Action

Revise the specification according to the detailed information shown in this message.

AH02101

Failed to read cgi file aa....aa for testing

aa....aa: File name

Description

Failed to read the file. The process of executing the script will now stop.

Action

Revise the specification according to the detailed information shown in this message.

AH02102

aa....aa is not executable; ensure interpreted scripts have "#!" or "'!" first line

aa....aa: File name

Description

The specified file cannot be executed. The startup of the CGI program stops.

Action

Make sure that "#!" or "!" is specified in the first line.

AH02155

getpwuid: couldn't determine user name from uid aa....aa, you probably need to modify the User directive

aa....aa: User ID

Description

An error occurred when searching for aa....aa in the password database. The Web server stops the start processing.

Action

Revise the specification according to the value specified in the User directive and the detailed information returned by the getpwuid() function shown in this message.

AH02156

setgid: unable to set group id to Group aa....aa

aa....aa: Group ID

Description

An attempt to specify the group ID has failed. The Web server stops the start processing.

Action

Revise the specification according to the detailed information returned by the setgid() function shown in this message.

AH02157

initgroups: unable to set groups for User aa....aa and Group bb....bb

aa....aa: User name

bb....bb: Group ID

Description

An attempt to initialize the group access list of the user has failed. The Web server stops the start processing.

Action

Revise the specification according to the detailed information returned by the initgroups() function shown in this message.

AH02162

setuid: unable to change to uid: aa....aa

aa....aa: User ID

Description

An attempt to specify the user ID has failed. The Web server stops the start processing.

Action

Revise the specification according to the detailed information returned by the setuid() function shown in this message.

AH02163

set dumpable failed - this child will not coredump after software errors

Description

An attempt to set up the core dump has failed. The core will not be output even if an error occurs for the normal core dump of the server process.

Action

Revise the specification according to the detailed information returned by the prctl() function shown in this message.

AH02177

apr_socket_accept: giving up.

Description

An (ENETDOWN) error has occurred in the accept() function. The server process that received the request will exit.

Action

Revise the specification according to the detailed information returned by the accept() function shown in this message.

AH02179

apr_socket_accept: (client socket)

Description

An error occurred in the accept() function. The server process that received the request will exit.

Action

Revise the specification according to the detailed information returned by the accept() function shown in this message.

AH02325

A resource shortage or other unrecoverable failure was encountered before any child process initialized successfully... httpsd is exiting!

Description

A resource shortage or another unrecoverable failure occurred before the server process was initialized normally. The Web server will now end.

Action

Revise according to the cause of error described in messages output other than this message.

AH02439

error parsing URL aa....aa: bb....bb

aa....aa: URL

bb....bb: Detailed information

Description

An error occurred during analysis of the transfer destination URL.

The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.

Action

Revise the URL specified in the ProxyPass directive according to the cause specified in bb....bb.

AH02441

error on aa....aa - ap_pass_brigade

aa....aa: client or backend

Description

An error occurred during data send processing.

Action

Revise the specification according to the detailed information shown in this message.

AH02442

error on aa....aa - ap_get_brigade

aa....aa: client or backend

Description

An error occurred during data reception processing.

Action

Revise the specification according to the detailed information shown in this message.

AH02443

error apr_pollset_create()

Description

An error occurred in apr_pollset_create().

The status code 500 Internal Server Error will be returned, and the request processing will terminate.

Action

Revise the specification according to the detailed information shown in this message.

AH02444

error apr_poll()

Description

An error occurred in apr_poll().

The status code 500 Internal Server Error will be returned, and the request processing will terminate.

Action

Revise the specification according to the detailed information shown in this message.

AH02447

error on backconn

Description

An error occurred during connection with the back-end server. The WebSocket communication will now end.

AH02452

failed to make connection to backend: aa....aa

aa....aa: Host name

Description

An attempt to establish a connection with the back-end server failed.

The status code 503 Service Unavailable will be returned, and the request processing will terminate.

Action

Check the status of the transfer destination server.

AH02477

mod_proxy must be loaded for mod_proxy_http

Description

To use the mod_proxy_http module, the mod_proxy module is required. The Web server stops the start processing.

Action

Make sure that the mod_proxy module has been incorporated by using the LoadModule directive.

AH02605

unknown event on backconn aa....aa

aa....aa: Value indicating the event that occurred

Description

An unexpected event concerning the connection with the back-end server occurred.

AH02606

unknown event on client conn aa....aa

aa....aa: Value indicating the event that occurred

Description

An unexpected event concerning the connection with the client occurred.

AH02607

error on client conn

Description

An error occurred during connection with the client. The WebSocket communication will now end.

AH02656

Error while reading HTTP trailer: aa....aabb....bb

aa....aa: Status code

bb....bb: Error information

Description

An error occurred while chunk data was being read.

AH00002

Fatal error: unable to create global pool for use by the scoreboard

Description

The area to be used with the scoreboard could not be secured. The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

AH03142

apr_thread_create: unable to create worker thread

Description

An attempt to generate a server thread failed. The server process terminates.

Action

Revise the specification according to the detailed information shown in this message.

23.5 Messages beginning with KH

This section describes the messages beginning with KH.

KH00001

File does not exist: aa....aa

aa....aa: File name

Description

The requested file cannot be found.

The status code 404 Not Found will be returned to the client, and the request processing will be interrupted.

Action

Revise the requested file name.

KH00002

file permissions deny server access: aa....aa

aa....aa: File name

Description

There is no permission to access the required file.

The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.

Action

Revise the requested file according to the detailed information shown in this message.

KH00004

Child: Graceful exit event signaled. Child process is ending.

Description

The planned termination event was reported to the server process.

The planned termination processing of the server process will start.

KH00005

Child: Unable to retrieve the graceful exit event from the parent

Description

The planned termination event handle of the server process could not be acquired.

The server process terminates.

Action

Revise the specification according to the detailed information returned by the ReadFile() function shown in this message.

KH00006

Parent: Unable to duplicate the graceful exit event handle for the child

Description

The planned termination event handle of the server process could not be duplicated.

The Web server stops the start processing.

Action

Revise the specification according to the detailed information returned by the DuplicateHandle() function shown in this message.

KH00007

Parent: Unable to send the graceful exit event handle to the child

Description

The planned termination event handle could not be sent to the server process.

The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00008

Parent: Could not create graceful exit event for child process

Description

An attempt to generate a planned termination for the server process has failed.

The generation of the server process will now stop.

Action

Revise the specification according to the detailed information returned by the CreateEvent() function shown in this message.

KH00009

Parent: Received graceful stop signal -- Shutting down the server gracefully.

Description

The planned termination event was reported to the control process.

The Web server starts the planned termination processing.

KH00010

ResetEvent(graceful_stop_event)

Description

The control process failed to release the planned termination event.

The planned termination processing of the Web server will continue.

Action

Revise the specification according to the detailed information returned by the ResetEvent() function shown in this message.

KH00011

Parent: SetEvent for child process aa....aa failed

aa....aa: Handle value

Description

The control process has failed to set up a planned termination event for the server process.

The planned termination processing of the Web server will continue.

Action

Revise the specification according to the detailed information returned by the SetEvent() function shown in this message.

KH00012

Parent: Child process exited successfully.

Description

The server process ended successfully.

The Web server continues the planned termination processing.

KH00013

Parent: Received shutdown signal -- Shutting down the server.

Description

The termination event was reported to the control process.

The Web server starts the termination processing.

KH00014

ResetEvent(shutdown_event)

Description

The control process failed to release the termination event.

The Web server continues the termination processing.

Action

Revise the specification according to the detailed information returned by the ResetEvent() function shown in this message.

KH00015

Parent: Forcing termination of child process aa....aa

aa....aa: Handle number

Description

The control process will forcibly terminate the server process that does not terminate with the specified planned termination event.

The Web server continues the planned termination processing.

Action

Revise the cause due to which the server process does not terminate.

KH00016

Parent: Cannot create graceful stop event aa....aa

aa....aa: Event object name

Description

The control process has failed to generate an event for planned termination.

The Web server stops the start processing.

Action

Revise the specification according to the detailed information returned by the CreateEvent() function shown in this message.

KH00018

Parent: Failed to create the child process.

Description

An attempt to generate the server process has failed.

The generation of the server process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

KH00019

Parent: Failed to create the child process.

Description

An attempt to generate the server process has failed.

The generation of the server process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

KH00020

Unknown Transfer-Encoding aa....aa

aa....aa: Header value

Description

The value specified in the Transfer-Encoding header is invalid.

The status code 501 Method Not Implemented will be returned to the client, and the request processing will be interrupted.

Action

Other than chunked is specified in the Transfer-Encoding header. Revise the Transfer-Encoding header.

KH00021

Invalid Content-Length

Description

The length specified in the Content-Length header is invalid.

The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.

Action

You can only specify a numeric value (decimal number) in the Content-Length header. Revise the specified value.

KH00022

aa....aa with body is not allowed for bb....bb

aa....aa: Method

bb....bb: Requested URI value

Description

Body is specified for a method for which the body is not allowed.

The status code 413 Request Entity Too Large will be returned to the client, and the request processing will be interrupted.

Action

To allow a TRACE method to which the request body is added, specify extended in the TraceEnable directive. However, a request cannot be received if the request body size exceeds 64 KB.

KH00025

Child: Unable to retrieve the parent process handle from the parent

Description

The process handle of the control process could not be acquired from the control process.

The server process terminates.

Action

Revise the specification according to the detailed information returned by the ReadFile() function shown in this message.

KH00026

Parent: Unable to duplicate the parent process handle for the child

Description

The process handle of the control process could not be duplicated.

The Web server stops the start processing.

Action

Revise the specification according to the detailed information returned by the DuplicateHandle() function shown in this message.

KH00027

Parent: Unable to send the parent process handle to the child

Description

The process handle of the control process could not be sent to the server process.

The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00028

Child: Parent process exited. Child process is ending.

Description

The termination of the control process was detected.

The termination processing of the server process will start.

KH00029

Parent: the child process exited before starting initialization.

Description

The server process terminated before the initialization processing was started.

The Web server stops the start processing.

Action

Revise according to the cause of error described in messages output other than this message.

KH00030

Parent: WaitForMultipleObjects failed.

Description

The control process failed to await the initialization processing start event of the server process.

The Web server stops the start processing.

Action

Revise the specification according to the detailed information returned by the WaitForSingleObject() function shown in this message.

KH00031

the service control dispatcher terminated before completing initialization of the service.

Description

The service control dispatcher thread terminated before the service initialization processing was complete.

The startup processing of the service stops.

Action

Revise according to the cause of error described in messages output other than this message.

KH00032

service initialization wait timed out.

Description

A timeout occurred when the service startup process was awaiting the service initialization processing completion event.

The startup processing of the service stops.

Action

Revise according to the cause of error described in messages output other than this message.

KH00033

WaitForMultipleObjects failed.

Description

The service startup process failed to await the service initialization processing completion event.

The startup processing of the service stops.

Action

Revise the specification according to the detailed information returned by the WaitForSingleObject() function shown in this message.

KH00034

Parent aa....aa: Using config file "bb....bb"

aa....aa: Control process ID

bb....bb: Config file name

Description

The process ID of the control process, and the configuration file name used in the startup processing is displayed.

The Web server continues the startup processing.

KH00035

Parent aa....aa: Using config file "bb....bb"

aa....aa: Control process ID

bb....bb: Config file name

Description

The process ID of the control process, and the configuration file name used in the startup processing is displayed.

The Web server continues the startup processing.

KH00037

The HWS trace could not open the log file aa....aa specified in the HWSTraceLogFile.

aa....aa: File name

Description

The file described in the aa....aa specified in the HWSTraceLogFile directive cannot be opened.

The process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

KH00038

The HWS trace output the log of the process (pid=aa....aa) into the file bb....bb specified in the HWSTraceLogFile.

aa....aa: Process ID

bb....bb: File name

Description

The contents of the shared memory of the process described in the aa....aa were output in the file described in bb....bb specified in the HWSTraceLogFile directive.

The output in the file is terminated successfully, and the processing is continued.

KH00039

The HWS trace could not write the log file aa....aa specified in the HWSTraceLogFile.

aa....aa: File name

Description

An attempt to output the contents of the shared memory to the file specified in the HWSTraceLogFile directive failed.

The output process will now stop.

KH00040

The HWS trace could not write the log file aa....aa specified in the HWSTraceLogFile.

aa....aa: File name

Description

An attempt to output the contents of the shared memory to the file specified in the HWSTraceLogFile directive failed.

The output process will now stop.

KH00043

Couldn't start RequestLog process 'aa....aa'.

aa....aa: Value specified in the HWSRequestLog directive

Description

An attempt to generate a process for the output of the request log has failed.

The Web server stops the start processing.

Action

Revise the HWSRequestLog directive according to the detailed information shown in this message.

KH00044

httpsd: Invalid request log path aa....aa.

aa....aa: File name

Description

The file path specified in the HWSRequestLog directive is invalid.

The Web server stops the start processing.

Action

Revise the HWSRequestLog directive according to the detailed information shown in this message.

KH00045

httpsd: could not open request log file aa....aa.

aa....aa: File name

Description

The request log file could not be opened.

The Web server stops the start processing.

Action

Revise the HWSRequestLog directive according to the detailed information shown in this message.

KH00046

Graceful stop requested, doing graceful stop

Description

The planned termination of the Web server was requested. The planned termination processing will start.

KH00047

caught SIGUSR2, shutting down

Description

The Web server stopped due to reception of the SIGUSR2 signal.

KH00048

caught SIGXCPU, shutting down

Description

The Web server stopped due to reception of the SIGXCPU signal.

KH00049

caught SIGXFSZ, shutting down

Description

The Web server stopped due to reception of the SIGXFSZ signal.

KH00052

Server ran out of threads to serve requests. Consider raising the ThreadsPerChild setting

Description

The server threads for processing requests are insufficient.

The request process continues.

Action

Consider increasing the value of the ThreadsPerChild directive.

KH00053

request queue reached HWSMaxQueueSize setting, consider raising the HWSMaxQueueSize setting

Description

The number of requests maintained in the request queue has reached the specified value of the HWSMaxQueueSize directive.

The processing continues. The connection of the requests from the client that are over and above the queue size will be disconnected at the Web server side.

Action

Consider increasing the value of the HWSMaxQueueSize directive.

KH00054

Parent: aa....aa

aa....aa: Error

Description

An error occurred during server process generation.

The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00055

The HWS trace could not open the log file aa....aa specified in the HWSTraceLogFile.

aa....aa: File name

Description

The file described in the aa....aa specified in the HWSTraceLogFile directive cannot be opened.

The process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

KH00056

The HWS trace could not write the log file aa....aa specified in the HWSTraceLogFile.

aa....aa: File name

Description

An attempt to output the contents of the shared memory to the file specified in the HWSTraceLogFile directive failed.

The output process will now stop.

KH00057

The HWS trace could not write the log file aa....aa specified in the HWSTraceLogFile.

aa....aa: File name

Description

An attempt to output the contents of the shared memory to the file specified in the HWSTraceLogFile directive failed.

The output process will now stop.

KH00058

The HWS trace output the log of the process (pid=aa....aa) into the file bb....bb specified in the HWSTraceLogFile.

aa....aa: Process ID

bb....bb: File name

Description

The contents of the shared memory of the process described in the aa....aa were output in the file described in bb....bb specified in the HWSTraceLogFile directive.

The output in the file is terminated successfully, and the processing is continued.

KH00061

QOSCookieServers is out of range

Description

The specified range of the QOSCookieServers directive is invalid.

The Web server stops the start processing.

Action

Revise the QOSCookieServers directive value.

KH00062

QOSRejectionServers is out of range

Description

The specified range of the QOSRejectionServers directive is invalid.

The Web server stops the start processing.

Action

Revise the QOSRejectionServers directive value.

KH00063

Could not open file: aa....aa

aa....aa: File name

Description

The file specified in the QOSResponse directive cannot be opened.

The Web server stops the start processing.

Action

Revise the QOSResponse directive value according to the detailed information shown in this message.

KH00064

Could not open file: aa....aa

aa....aa: File name

Description

The file specified in the QOSResponse directive cannot be opened.

The Web server stops the start processing.

Action

Revise the QOSResponse directive value according to the detailed information shown in this message.

KH00065

Could not open file: aa....aa

aa....aa: File name

Description

The file specified in the QOSResponse directive cannot be opened.

The Web server stops the start processing.

Action

Revise the QOSResponse directive value according to the detailed information shown in this message.

KH00066

This file is too large: aa....aa

aa....aa: File name

Description

The file specified in the QOSResponse directive cannot be read because it is too big.

The Web server stops the start processing.

Action

Specify a file smaller than 4,294,967,295 bytes.

KH00067

Could not read file: aa....aa

aa....aa: File name

Description

The file specified in the QOSResponse directive cannot be read.

The Web server stops the start processing.

Action

Revise the QOSResponse directive value according to the detailed information shown in this message.

KH00069

Request rejected (service temporarily unavailable)

Description

The request processing was denied.

The request process will now stop.

KH00324

The HWS trace could not open the ID file aa....aa specified in the HWSTraceIdFile.

aa....aa: File name

Description

The file specified in the aa....aa described in the HWSTraceIdFile directive cannot be opened.

The process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

KH00325

The HWS trace could not obtain the shared memory identifier from the file aa....aa specified in the HWSTraceIdFile.

aa....aa: File name

Description

The shared memory identifier cannot be obtained from the file described in the aa....aa specified in the HWSTraceIdFile directive.

The process continues.

Action

Revise the specification according to the detailed information shown in this message.

KH00326

The format of the shared memory identifier specified in the HWSTraceIdFile is invalid.

Description

The format of the shared memory identifier of the file specified in the HWSTraceIdFile directive is invalid.

The process continues.

Action

Revise the shared memory identifier.

KH00328

HWS trace shmctl() IPC_RMID could not remove the shared memory segment(id=aa....aa).

aa....aa: Shared memory identifier

Description

The shared memory cannot be deleted.

The process continues.

Action

Revise the specification according to the detailed information shown in this message.

KH00329

The HWS trace could not open the ID file aa....aa specified in the HWSTraceIdFile.

aa....aa: File name

Description

The file specified in the aa....aa described in the HWSTraceIdFile directive cannot be opened.

The process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

KH00330

The HWS trace could not create the segment(size=aa....aa).

aa....aa: Size

Description

Shared memory cannot be secured.

The process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

KH00331

The HWS trace could not assign the segment(id=aa....aa).

aa....aa: Shared memory identifier

Description

The shared memory cannot be assigned.

he process will now stop.

Action

Revise the specification according to the detailed information about shmat() shown in this message.

KH00332

HWS trace shmctl() IPC_STAT could not educe the current value(id=aa....aa).

aa....aa: Shared memory identifier

Description

The shared memory status for the aa....aa cannot be extracted.

The process will now stop.

Action

Revise the specification according to the detailed information about shmctl() shown in this message.

KH00333

HWS trace shmctl() IPC_SET could not set the value(id=aa....aa), you probably need to modify User or Group directives.

aa....aa: Shared memory identifier

Description

The shared memory status for aa....aa cannot be set up.

The process will now stop.

Action

This error occurs when the user specified in the User directive or Group directive is not registered in the system. Revise the specified value of the User directive or Group directive.

KH00334

The HWS trace could not create the segment(size=aa....aa).

aa....aa: Size (bytes)

Description

Shared memory cannot be secured.

The process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

KH00335

The HWS trace could not map the segment(id=aa....aa) for the parent.

aa....aa: Shared memory identifier

Description

The shared memory cannot be assigned to a blank.

The process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

KH00337

The HWS trace could not open the ID file aa....aa specified in the HWSTraceIdFile.

aa....aa: File name

Description

The file specified in the aa....aa described in the HWSTraceIdFile directive cannot be opened.

The process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

KH00338

The HWS trace created shared memory segment #aa....aa.

aa....aa: Shared memory identifier

Description

Shared memory for the internal trace was secured.

The process continues.

KH00340

The HWS trace could not open the ID file aa....aa specified in the HWSTraceIdFile.

aa....aa: File name

Description

The file specified in the aa....aa described in the HWSTraceIdFile directive cannot be opened.

The process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

KH00341

The HWS trace could not open the segment(id=aa....aa).

aa....aa: Shared memory identifier

Description

An attempt to open the shared memory has failed.

The process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

KH00342

The HWS trace could not map the segment(id=aa....aa) for the child.

aa....aa: Shared memory identifier

Description

The shared memory cannot be assigned to a blank.

The process will now stop.

Action

Revise the specification according to the detailed information shown in this message.

KH00349

[client aa....aa] bb....bb:forcing termination of request "cc....cc"

aa....aa: Client address

bb....bb: child process process-ID, server thread thread-ID, or child process process-ID: server thread thread-ID

cc....cc: Request line

Description

The request processing described in cc....cc was interrupted because the time from the receipt of the planned termination request until the forced termination has elapsed.

The Web server interrupt the request processing and continues the termination processing.

KH00350

error reading response header from remote server aa....aa

aa....aa: Host name

Description

An attempt to read the response header from the remote Web server failed.

The status code 502 Bad Gateway will be returned to the client, and the request processing will be interrupted.

Action

Check for a message indicating that an attempt to read data from the remote Web server failed.

KH00351

apr_socket_opt_set(FIONBIO): Failed to set

Description

An error occurred when the FIONBIO option was set.

The Web server continues the processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00352

apr_socket_opt_set(FIONBIO): Failed to set

Description

An error occurred when the FIONBIO option was set.

The Web server continues the processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00353

Failed to set the PRFSPOOL environment variable

Description

An attempt to set up the PRFSPOOL environment variable failed.

The Web server continues the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00354

Cannot load PRF library into server: aa....aa

aa....aa: Detailed information

Description

An attempt to load the PRF library failed.

The Web server continues the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00355

Cannot load PRF library into server: aa....aa

aa....aa: Detailed information

Description

An attempt to load the PRF library failed.

The Web server continues the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00356

Cannot load PRF library into server: aa....aa

aa....aa: Detailed information

Description

An attempt to load the PRF library failed.

The Web server continues the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00357

Cannot load PRF library into server: aa....aa

aa....aa: Detailed information

Description

An attempt to load the PRF library failed.

The Web server continues the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00358

Cannot load PRF library into server: aa....aa

aa....aa: Detailed information

Description

An attempt to load the PRF library failed.

The Web server continues the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00359

Cannot load PRF library into server: aa....aa

aa....aa: Detailed information

Description

An attempt to load the PRF library failed.

The Web server continues the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00360

PRF: open_service failed(aa....aa)

aa....aa: Return code

Description

The PRF daemon cannot be used.

The Web server continues the start processing.

Action

Make sure that the PRF daemon is running.

KH00361

The server did not send a status-code aa....aa response because the server already sent an error response to the client.

aa....aa: Status code

Description

A status code response is not sent because an error response is already sent to the client.

KH00362

The server started by non-root user. User and Group directives is not used.

Description

The User directive and Group directive are not used because the server is started by a general user.

KH00363

Socket Input: timed out (aa....aa:bb....bb --> cc....cc:dd....dd)

aa....aa: Connection destination IP address

bb....bb: Connection destination port number

cc....cc: IP address of the Web server

dd....dd: Port number of the Web server

Description

A timeout occurred in the receipt processing executed with the client or back-end server. Any one of the following standby time periods has been exceeded:

Standby time when data is no longer received during the receipt of a request (receipt of HTTP protocol after establishing a connection) from the client

Standby time from sending a request to the back-end server until the receipt of a response, when you are using reverse proxy

Standby time when data is no longer received during the receipt of a response from the back-end server, when you are using reverse proxy

Action

This message was output because the time specified in the Timeout directive was exceeded. Revise the value specified in the directive.

KH00364

Socket Output: timed out (aa....aa:bb....bb <-- cc....cc:dd....dd)

aa....aa: Connection destination IP address

bb....bb: Connection destination port number

cc....cc: IP address of the Web server

dd....dd: Port number of the Web server

Description

A timeout occurred in the send processing executed with the client or back-end server. Any one of the following standby time periods has been exceeded:

Standby time when data can no longer be sent while a response is being sent to the client

Standby time when data can no longer be sent while a request is being sent to the back-end server, when you are using a reverse proxy

Action

This message was output because the time specified in the Timeout directive was exceeded. Revise the value specified in the directive.

KH00375

Parent aa....aa: Using config file "bb....bb"

aa....aa: Control process ID

bb....bb: Config file name

Description

The process ID of the control process, and the configuration file name used in the startup processing is displayed.

The Web server continues the startup processing.

KH00376

Graceful stop requested, doing graceful stop

Description

The planned termination of the Web server was requested. The planned termination processing will start.

KH00377

caught SIGUSR2, shutting down

Description

The Web server stopped due to reception of the SIGUSR2 signal.

KH00378

caught SIGXCPU, shutting down

Description

The Web server stopped due to reception of the SIGXCPU signal.

KH00379

caught SIGXFSZ, shutting down

Description

The Web server stopped due to reception of the SIGXFSZ signal.

KH00380

The server started by non-root user. User and Group directives is not used.

Description

The User directive and Group directive are not used because the server is started by a general user.

KH00382

child process aa....aa still did not exit, sending a SIGKILL

aa....aa: Process ID

Description

The SIGKILL signal will be sent because the server process specified in the aa....aa has not terminated. The Web server continues the termination or restart processing.

KH00383

Couldn't start websocket log process 'aa....aa'.

aa....aa: Value specified in the HWSWebSocketLog directive

Description

An attempt to generate a process used to output WebSocket log data failed.

The Web server stops the start processing.

Action

Revise the HWSWebSocketLog directive according to the detailed information shown in this message.

KH00384

httpsd: Invalid websocket log path aa....aa.

aa....aa: File name

Description

The file path specified in the HWSWebSocketLog directive is invalid.

The Web server stops the start processing.

Action

Revise the HWSWebSocketLog directive according to the detailed information shown in this message.

KH00385

httpsd: could not open websocket log file aa....aa.

aa....aa: File name

Description

The WebSocket log file could not be opened.

The Web server stops the start processing.

Action

Revise the HWSWebSocketLog directive according to the detailed information shown in this message.

KH00415

An attempt to acquire the path of the audit log library has failed.

Description

An attempt to acquire the path of the library for the audit log output has failed.

The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00416

An attempt to load the audit log library has failed.

Description

An attempt to load the library for the audit log output has failed.

The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00417

An attempt to acquire the address of the audit log function has failed.

Description

An attempt to acquire the address of the function of library for the audit log output has failed.

The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00418

An attempt to acquire the path of the audit log library has failed.

Description

An attempt to acquire the path of the library for the audit log output has failed.

The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00419

An attempt to acquire the address of the audit log function has failed.

Description

An attempt to acquire the address of the function of library for the audit log output has failed.

The Web server stops the start processing.

Action

Revise the specification according to the detailed information shown in this message.

KH00420

server reached MaxClients setting, consider raising the MaxClients setting

Description

The number of server processes has reached the value set up in the MaxClients directive. Consider increasing the value specified in the MaxClients directive. If the value specified in the MaxClients directive is exceeded, the server process will not be generated.

Action

Revise the value specified in the MaxClients directive. To generate as many idle server processes as specified in the MinSpareServers directive, the value specified in the MaxClients directive must be increased.

KH00421

MaxClients can't be changed by restart. Original was used

Description

The MaxClients directive cannot be changed during restart with graceful or restart.

The MaxClients directive value at the time of startup of the Web server will be set up, and the restart processing will continue.

Action

Do not change the MaxClients directive value during restart.

KH00422

WARNING: MaxClients of aa....aa exceeds compile time limit of

bb....bb servers, decreasing MaxClients to bb....bb.

aa....aa: MaxClients directive value

bb....bb: Maximum limit

Description

The MaxClients directive value exceeds the maximum limit. The Web server sets the maximum limit value for the MaxClients directive, and then continues the startup processing.

Action

Revise the MaxClients directive value.

KH00423

MaxClients of aa....aa exceeds compile time limit of 2048, decreasing to match

aa....aa: MaxClients directive value

Description

The MaxClients directive value exceeds the maximum limit. The Web server sets the maximum limit value for the MaxClients directive, and then continues processing.

Action

Revise the MaxClients directive value.

KH00424

WARNING: MaxClients of aa....aa not allowed, increasing to 1.

aa....aa: MaxClients directive value

Description

An invalid value is specified in MaxClients directive.

1 will be set up for the MaxClients directive value of the Web server, and the startup processing will continue.

Action

Revise the MaxClients directive value.

KH00425

MaxClients of aa....aa not allowed, increasing to 1

aa....aa: MaxClients directive value

Description

An invalid value is specified in MaxClients directive.

1 will be set up for the MaxClients directive value of the Web server, and the startup processing will continue.

Action

Revise the MaxClients directive value.

KH00426

server reached MaxClients setting, consider raising the MaxClients setting

Description

The number of server threads that are processing requests reaches the MaxClients directive value. Consider increasing the MaxClients directive value. No more server processes are generated if the number of server threads exceeds the value specified in the MaxClients directive.

Action

Revise the value specified in the MaxClients directive.

KH00427

server is within MinSpareThreads of MaxClients, consider raising the MaxClients setting

Description

The number of idle server threads is now less than the MinSpareThreads directive value.

Action

Revise the value specified in the MaxClients or MinSpareThreads directive.

KH00429

WARNING: MaxClients of aa....aa is less than ThreadsPerChild of

bb....bb, increasing to bb....bb. MaxClients must be at least as large

as the number of threads in a single server.

aa....aa: Value specified in the MaxClients directive

bb....bb: Value specified in the ThreadsPerChild directive

Description

The MaxClients directive value is smaller than the ThreadsPerChild directive value. The Web server sets the ThreadsPerChild directive value for the MaxClients directive value, and then continues the startup processing. The MaxClients directive value must be at least equal to the number of server threads belonging to one server process.

Action

Revise the MaxClients directive value.

KH00430

MaxClients of aa....aa is less than ThreadsPerChild of bb....bb, increasing to match

aa....aa: Value specified in the MaxClients directive

bb....bb: Value specified in the ThreadsPerChild directive

Description

The MaxClients directive value is smaller than the ThreadsPerChild directive value. The Web server sets the ThreadsPerChild directive value for the MaxClients directive value, and then continues processing.

Action

Revise the MaxClients directive value.

KH00431

WARNING: MaxClients of aa....aa is not an integer multiple of

ThreadsPerChild of bb....bb, decreasing to nearest multiple cc....cc,

for a maximum of dd....dd servers.

aa....aa: Value specified in the MaxClients directive

bb....bb: Value specified in the ThreadsPerChild directive

cc....cc: Maximum number of concurrent connections

dd....dd: Maximum number of server processes

Description

The MaxClients directive value is not an integer multiple of the ThreadsPerChild directive value. The Web server sets the MaxClients directive value that is reduced to an integer multiple of the ThreadsPerChild directive value, and then continues the startup processing.

Action

Revise the MaxClients directive value.

KH00432

MaxClients of aa....aa is not an integer multiple of ThreadsPerChild of bb....bb, decreasing to nearest multiple cc....cc

aa....aa: Value specified in the MaxClients directive

bb....bb: Value specified in the ThreadsPerChild directive

cc....cc: Maximum number of concurrent connections

Description

The MaxClients directive value is not an integer multiple of the ThreadsPerChild directive value. The Web server sets the MaxClients directive value that is reduced to an integer multiple of the ThreadsPerChild directive value, and then continues processing.

Action

Revise the MaxClients directive value.

KH00433

WARNING: MaxClients of aa....aa would require bb....bb servers and

would exceed ServerLimit of cc....cc, decreasing to dd....dd.

To increase, please see the ServerLimit directive.

aa....aa: Value specified in the MaxClients directive

bb....bb: Maximum number of server processes

cc....cc: ServerLimit directive value

dd....dd: Maximum number of concurrent connections

Description

The maximum number of server processes calculated from the MaxClients and ThreadsPerChild directives exceeds the ServerLimit directive value. The Web server sets the ServerLimit directive value multiplied by the ThreadsPerChild directive value for the maximum number of concurrent connections, and then continues the startup processing.

Action

Revise the ServerLimit directive value.

KH00434

MaxClients of aa....aa would require bb....bb servers and exceed ServerLimit of cc....cc, decreasing to dd....dd

aa....aa: Value specified in the MaxClients directive

bb....bb: Maximum number of server processes

cc....cc: ServerLimit directive value

dd....dd: Maximum number of concurrent connections

Description

The maximum number of server processes calculated from the MaxClients and ThreadsPerChild directives exceeds the ServerLimit directive value. The Web server sets the ServerLimit directive value multiplied by the ThreadsPerChild directive value for the maximum number of concurrent connections, and then continues processing.

Action

Revise the ServerLimit directive value.

23.6 Messages concerning SSL

For details on the messages output during the SSL processing of Cosminexus HTTP Server, see 19.8 SSL-related messages in the manual uCosminexus Application Server Security Management Guide.

23.7 Messages concerning commands and programs

The section describes the messages output by the Cosminexus HTTP Server commands and programs.

23.7.1 hwsserveredit command

This subsection describes the messages output by the hwsserveredit command.

hwsserveredit: completed

The processing of the command is complete. Alternatively, the server environment was created during the execution of -check.

Error level: None

(S) The process terminates.

hwsserveredit: cannot {create|delete|open|read|write|close} file-name function-name: detailed-information

An attempt to operate the file has failed.

Error level: None

(S) The process will now stop.

(O) Revise according to the contents described in detailed-information.

hwsserveredit: malloc failed

An attempt to secure the memory has failed.

Error level: None

(S) The process will now stop.

(O) Check the system status according to the memory usage.

hwsserveredit: Service {add|delete} failed function-name: detailed-information

Registration or deletion of the service is failed.

Error level: None

(S) The process will now stop.

(O) Revise according to the contents described in detailed-information.

hwsserveredit: uncompleted

The server environment was not created during the execution of -check.

Error level: None

(S) The process terminates.

(O) Check if the resources corresponding to the server name are created.

Details: function-name registry-key

The attempt to operate the registry has failed.

Error level: None

(S) The process will now stop.

(O) Revise according to the contents described in detailed-information.

Registry does not contain key registry-key after creation

An attempt to open the registry has failed.

Error level: None

(S) The process will now stop.

(O) Check whether the registry key exists.

detailed-information: GetModuleFileName failed

An attempt to acquire the path of the execution file has failed.

Error level: None

(S) The process will now stop.

(O) Revise according to detailed-information that the GetModuleFileName() function returns.

detailed-information: An attempt to load the audit log library has failed.

An attempt to load the library for the audit log output has failed.

Error level: None

(S) The processing will now stop.

(O) Revise according to detailed-information.

detailed-information: An attempt to acquire the address of the audit log function has failed.

An attempt to acquire the address of the function of library for the audit log output has failed.

Error level: None

(S) The processing will now stop.

(O) Revise according to detailed-information.

detailed-information: An attempt to acquire the path of the audit log library has failed.

An attempt to acquire the path of the library for the audit log output has failed.

Error level: None

(S) The processing will now stop.

(O) Revise according to detailed-information.

23.7.2 hwstraceinfo command

This subsection describes the messages output by the hwstraceinfo command.

hwstraceinfo: An open logfile error occurred.

Cannot open the output file.

Error level: None

(S) The process will now stop.

(O) Revise the output file.

hwstraceinfo: An open shared memory error (detailed-information) occurred.

An attempt to refer to the shared memory has failed.

Error level: None

(S) The process will now stop.

(O) Revise according to the contents described in detailed-information.

hwstraceinfo: A map shared memory error (detailed-information) occurred.

An attempt to map the shared memory has failed.

Error level: None

(S) The process will now stop.

(O) Revise according to the contents described in detailed-information.

hwstraceinfo: A shmat error occurred.

The shared memory cannot be assigned.

Error level: None

(S) The process will now stop.

(O) Revise the shared memory identifier.

hwstraceinfo: A shmctl ID removal error occurred.

The identifier of the shared memory cannot be deleted.

Error level: None

(S) The process will now stop.

(O) Revise the shared memory identifier.

hwstraceinfo: A write error occurred.

An attempt to output the contents of the shared memory in a file has failed.

Error level: None

(S) The process will now stop.

(O) Revise the output file.

hwstraceinfo: The shmid removal completed.

The shared memory identifier was deleted.

Error level: None

(S) The processing of the hwstraceinfo command will end.

hwstraceinfo: The trace output completed.

The contents of the shared memory were output in a file.

Error level: None

(S) The processing of the hwstraceinfo command will end.

23.7.3 openssl command

This subsection describes the messages output by the openssl command.

Unable to load Private Key

The key file could not be opened.

Error level: None

(S) The processing will be interrupted.

(O) Make sure that the key file having the indicated file name exists.

Unable to load X509 request

An attempt to read the certificate request failed.

Error level: None

(S) The processing will be interrupted.

(O) See the error message that is output at the same time.

Unable to load certificate

An attempt to read the certificate failed.

Error level: None

(S) The processing will be interrupted.

(O) See the error message that is output at the same time.

Number-of-bytes semi-random bytes loaded

Number-of-bytes of the data used in the random number generator has been read.

Error level: None

(S) The processing will be interrupted.

Generating RSA private key, number-of-bits bit long modulus

The RSA key will be generated.

Error level: None

(S) The processing continues.

Unknown curve name (elliptic-curve-name)

An invalid elliptic curve was specified for the -name option.

Error level: None

(S) The processing will terminate.

Number-of-bytes semi-random bytes loaded

Number-of-bytes of the data used in the random number generator has been read.

Error level: None

(S) The processing continues.

file-name: No such file or directory

A file or directory indicated by file-name does not exist.

Error level: None

(S) The processing will terminate.

Can't open input file file-name

The file indicated by file-name could not be opened.

Error level: None

(S) The processing will terminate.

Can't open output file file-name

The file indicated by file-name could not be opened.

Error level: None

(S) The processing will terminate.

unable to load key

The private key file could not be opened.

Error level: None

(S) The processing will terminate.

23.7.4 rotatelogs program

This subsection describes the messages output by the rotatelogs program.

Rotation time must be > 0

The log splitting time interval is invalid.

Error level: None

(S) The process will now stop.

(O) Revise the interval of the log splitting time.

The number of files must be >= 1 and <=256

An invalid value has been specified in -fnum.

Error level: None

(S) The process will now stop.

(O) Revise the value specified in -fnum.

The offset minutes from UTC must be >= -1439 and <=1439

An invalid value has been specified in -diff.

Error level: None

(S) The process will now stop.

(O) Revise the value specified in -diff.

The file path is too long.

The length of the split log file name is too long.

Error level: None

(S) The process will now stop.

(O) Revise the prefix length of the split log file.

Usage: (program-name) logfile rotation-time-in-seconds [-fnum file-number] [-diff offset-minutes-from-UTC]

The argument is invalid.

Error level: None

(S) The processing will be interrupted.

(O) Revise the argument.

23.7.5 rotatelogs2 program

This subsection describes the messages output by the rotatelogs2 program.

The size(KB) of file must be >= 1 and <= 2097151

The log file size is invalid.

Error level: None

(S) The process will now stop.

(O) Revise the size of the log file.

The number of files must be >= 1 and <= 256

The number of log files is invalid.

Error level: None

(S) The process will now stop.

(O) Revise the number of log files.

The file path is too long.

The length of the log file name is too long.

Error level: None

(S) The process will now stop.

(O) Revise the prefix length of the log file.

Usage: (program-name) logfile-prefix maximum-file-size maximum-number-of-files

The number of arguments is invalid.

Error level: None

(S) The processing will be interrupted.

(O) Revise the number of arguments.

24 Messages Output by OSS

This chapter describes the messages output by OSS.

24.1 Format for describing the messages

The format for describing the messages in this chapter is as follows:

XXXXnnnnn-Y

Message text

Description of variable values

Description

Supplementary description of the message text

Action

Action taken by the user

Each item is described as follows:

XXXXnnnnn

This describes the message ID.

nnnnn

This indicates the message number managed by the program that output the message. A five-digit unique number is attached to each message.

Y

This describes the message level. The message level is indicated by one alphabetic character.

The alphabetic characters indicating the message levels and their meanings are as follows:

E (Error)

This message reports the occurrence of an error-level problem.

When this message is displayed the processing is interrupted.

W (Warning)

This message reports the occurrence of a warning-level problem.

The processing continues even after this message is displayed.

I (Information)

This message reports a system operation.

The processing continues even after this message is displayed.

Message text

This indicates the message text output by OSS.

Note that the variable value (value that differs depending upon the status in which the message is output) within the message text is output with the format xx....xx (xx are lower-case alphabetical characters).

Description of variable values

The information displayed in the variable value within the message text is output with the format 'xx....xx: displayed-information' (xx are lower-case alphabetical characters). An example of the format for describing variable values is as follows:

Example:

aa....aa: File name

bb....bb: Application name

Description

This is the supplementary description of the message, such as the factors responsible for reporting the message and operation of the component software that output the message.

Action

This is the action to be taken by the user.

24.2 Messages beginning with KDJE

This section describes the messages beginning with KDJE.

KDJE60101-E

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

BV output an error message.

Action

Remove the cause of the error based on the error message.

KDJE60102-E

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

BV output an error message with an exception.

Action

Remove the cause of the error based on the error message and the contents of the exception log.

KDJE60103-W

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

BV output a warning message.

Action

We recommend that you remove the cause of the warning based on the warning message.

KDJE60104-W

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

BV output a warning message with an exception.

Action

We recommend that you remove the cause of the warning based on the warning message and the contents of the exception log.

KDJE60105-I

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

BV output an information message.

KDJE60106-I

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

BV output an information message with an exception.

KDJE60201-E

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

CDI output an error message.

Action

Remove the cause of the error based on the error message.

KDJE60202-E

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

CDI output an error message with an exception.

Action

Remove the cause of the error based on the error message and the contents of the exception log.

KDJE60203-W

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

CDI output a warning message.

Action

We recommend that you remove the cause of the warning based on the warning message.

KDJE60204-W

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

CDI output a warning message with an exception.

Action

We recommend that you remove the cause of the warning based on the warning message and the contents of the exception log.

KDJE60205-I

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

CDI output an information message.

KDJE60206-I

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

CDI output an information message with an exception.

KDJE60301-E

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JAX-RS output an error message.

Action

Remove the cause of the error based on the error message.

KDJE60302-E

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JAX-RS output an error message with an exception.

Action

Remove the cause of the error based on the error message and the contents of the exception log.

KDJE60303-W

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JAX-RS output a warning message.

Action

We recommend that you remove the cause of the warning based on the warning message.

KDJE60304-W

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JAX-RS output a warning message with an exception.

Action

We recommend that you remove the cause of the warning based on the warning message and the contents of the exception log.

KDJE60305-I

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JAX-RS output an information message.

KDJE60306-I

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JAX-RS output an information message with an exception.

KDJE60401-E

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JSF output an error message.

Action

Remove the cause of the error based on the error message.

KDJE60402-E

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JSF output an error message with an exception.

Action

Remove the cause of the error based on the error message and the contents of the exception log.

KDJE60403-W

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JSF output a warning message.

Action

We recommend that you remove the cause of the warning based on the warning message.

KDJE60404-W

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JSF output a warning message with an exception.

Action

We recommend that you remove the cause of the warning based on the warning message and the contents of the exception log.

KDJE60405-I

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JSF output an information message.

KDJE60406-I

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JSF output an information message with an exception.

KDJE60501-E

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JavaBatch output an error message.

Action

Remove the cause of the error based on the error message.

KDJE60502-E

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JavaBatch output an error message with an exception.

Action

Remove the cause of the error based on the error message and the contents of the exception log.

KDJE60503-W

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JavaBatch output a warning message.

Action

We recommend that you remove the cause of the warning based on the warning message.

KDJE60504-W

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JavaBatch output a warning message with an exception.

Action

We recommend that you remove the cause of the warning based on the warning message and the contents of the exception log.

KDJE60505-I

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JavaBatch output an information message.

KDJE60506-I

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JavaBatch output an information message with an exception.

KDJE60601-E

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JSON-P output an error message.

Action

Remove the cause of the error based on the error message.

KDJE60602-E

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JSON-P output an error message with an exception.

Action

Remove the cause of the error based on the error message and the contents of the exception log.

KDJE60603-W

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JSON-P output a warning message.

Action

We recommend that you remove the cause of the warning based on the warning message.

KDJE60604-W

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JSON-P output a warning message with an exception.

Action

We recommend that you remove the cause of the warning based on the warning message and the contents of the exception log.

KDJE60605-I

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JSON-P output an information message.

KDJE60606-I

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JSON-P output an information message with an exception.

KDJE60701-E

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JPA output an error message.

Action

Remove the cause of the error based on the error message.

KDJE60702-E

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JPA output an error message with an exception.

Action

Remove the cause of the error based on the error message and the contents of the exception log.

KDJE60703-W

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JPA output a warning message.

Action

We recommend that you remove the cause of the warning based on the warning message.

KDJE60704-W

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JPA output a warning message with an exception.

Action

We recommend that you remove the cause of the warning based on the warning message and the contents of the exception log.

KDJE60705-I

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

JPA output an information message.

KDJE60706-I

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

JPA output an information message with an exception.

KDJE60801-E

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

Concurrency Utilities for Java EE output an error message.

Action

Remove the cause of the error based on the error message.

KDJE60802-E

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

Concurrency Utilities for Java EE output an error message with an exception.

Action

Remove the cause of the error based on the error message and the contents of the exception log.

KDJE60803-W

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

Concurrency Utilities for Java EE output a warning message.

Action

We recommend that you remove the cause of the warning based on the warning message.

KDJE60804-W

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

Concurrency Utilities for Java EE output a warning message with an exception.

Action

We recommend that you remove the cause of the warning based on the warning message and the contents of the exception log.

KDJE60805-I

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

Concurrency Utilities for Java EE output an information message.

KDJE60806-I

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

Concurrency Utilities for Java EE output an information message with an exception.

KDJE60901-E

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

The Java API for WebSocket output an error message.

Action

Remove the cause of the error based on the error message.

KDJE60902-E

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

The Java API for WebSocket output an error message with an exception.

Action

Remove the cause of the error based on the error message and the contents of the exception log.

KDJE60903-W

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

The Java API for WebSocket output a warning message.

Action

We recommend that you remove the cause of the warning based on the warning message.

KDJE60904-W

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

The Java API for WebSocket output a warning message with an exception.

Action

We recommend that you remove the cause of the warning based on the warning message and the contents of the exception log.

KDJE60905-I

aa....aa (class = bb....bb, method = cc....cc)

aa....aa: Message

bb....bb: Output source class name

cc....cc: Output source method name

Description

The Java API for WebSocket output an information message.

KDJE60906-I

aa....aa (exception = bb....bb: cc....cc, class = dd....dd, method = ee....ee)

aa....aa: Message

bb....bb: Exception class name

cc....cc: Exception message

dd....dd: Output source class name

ee....ee: Output source method name

Description

The Java API for WebSocket output an information message with an exception.

25 Messages that Output only a Number and Message Text

This chapter describes the messages that output only a number and message text without a prefix.

25.1 Messages output by Web server (HTTP Server)

Only the message text is output for the messages of HTTP Server, which is a Web server included in Application Server.

For details on the messages output by HTTP Server, see 23. Messages output by Web Server (Cosminexus HTTP Server).

25.2 Messages output by the JAXB functionality of XML Processor

Among the messages output by XML Processor, only the message text is output in the messages output by the JAXB functionality.

For details on the messages output by the JAXB functionality of XML Processor, see 11.9 Messages related to JAXB.

25.3 Messages when Errors Occur while Changing and Importing the Working Directory

While changing and importing the working directory, check whether the DDs conform to specifications after verification with an XML processor. If the DDs do not satisfy the specifications, the messages are displayed in the form of detailed information of other messages.

Only the number and message text is output in this message.

This section describes the format and details of these messages.

25.3.1 Message format and details of messages

(1) Message format

The message format is as follows:

nnnn message ([nnnn message ([nnnn ....])])

The meaning of the format is described below:

nnnn

This indicates the message number managed in the Component Container.

Message

This indicates an error message.

([nnnn message ([nnnn ....])])

If there are multiple causes of error, the output is nested. Messages are delimited using brackets ( ).

(2) Details of messages

Messages output as detailed information are mentioned below:

No.

Message

Description

Action

0101

It failed in the analysis of TagLib. The 1st argument of <InputStream> is (null).

An internal error occurred.

Contact the maintenance personnel.

0102

It failed in the analysis of TagLib. The 2nd argument <WebDescriptorFactory> is (null).

An internal error occurred.

Contact the maintenance personnel.

0103

cannot read tld: [aa....aa]

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

0104

'aa....aa' not found in TagLib XML. Actual value was <bb....bb>.

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

0105

TagLib XML parsing error: [aa....aa]

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

0106

Invalid value = aa....aa: (in TagLib XML). Correct value is boolean value, yes or no.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

0201

It failed in the analysis of Web Application. The 1st argument <InputStream> is (null).

An internal error occurred.

Contact the maintenance personnel.

0202

It failed in the analysis of Web Application. The 2nd argument <WebDescriptorFactory> is (null).

An internal error occurred.

Contact the maintenance personnel.

0203

The configuration cannot be read. (aa....aa)

The DDs of WAR cannot be read.

aa....aa: Detailed message

Remove the cause according to the detailed message.

0204

'aa....aa' was not found in web.xml. The actual value was <bb....bb>.

The DDs of WAR cannot be analyzed.

aa....aa: Element name of an invalid DD

bb....bb: Element name of a valid DD.

Modify the description of the DDs.

0205

A web.xml parsing error occurred: (aa....aa)

An error was detected during the analysis of DDs of WAR.

aa....aa: Detailed message

Remove the cause according to the detailed message.

0206

Invalid XML: The document type of web.xml is null.

The document type declaration is not specified correctly in the DDs of WAR.

Specify the document type declaration correctly.

0207

There is no web component by the name of 'aa....aa' here.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

0208

Invalid argument. name=aa....aa value=bb....bb

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

0209

<web-app> contains more than one element of <aa....aa>.

Multiple aa....aa tags are specified in <web-app> tag.

aa....aa: Tag name specified multiple times in the <web-app>tag.

aa....aa tags cannot be specified multiple times in the <web-app>tag. Specify only one tag.

0301

Cannot set the descriptor unless this node has been added to a document for ApplicationClient.

An internal error occurred.

Contact the maintenance personnel.

0302

Cannot get the descriptor unless this node has been added to a document for ApplicationClient.

An internal error occurred.

Contact the maintenance personnel.

0303

Invalid XML: The document type of the application client is null.

An internal error occurred.

Contact the maintenance personnel.

0304

Invalid XML: The document type of the application client is unknown. (root name = 'aa....aa', public ID = 'bb....bb', system ID = 'cc....cc')

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

cc....cc: Maintenance information

Contact the maintenance personnel.

0305

The <application-client> node was not found.

An internal error occurred.

Contact the maintenance personnel.

0401

Cannot set the descriptor unless this node has been added to a document for ApplicationClient Runtime DeploymentDescriptor.

An internal error occurred.

Contact the maintenance personnel.

0501

Cannot set the descriptor unless this node has been added to a document for Application.

An internal error occurred.

Contact the maintenance personnel.

0502

Cannot get the descriptor unless this node has been added to a document for Application.

An internal error occurred.

Contact the maintenance personnel.

0503

Invalid XML: The document type of the application is null.

The document type declaration is not specified in the DDs of EAR.

Specify the document type declaration.

0504

Invalid XML: The document type of the application is unknown: aa....aa

The document type declaration is not specified correctly in the DDs of EAR.

aa....aa: Specified document type declaration

Specify the document type declaration correctly.

0506

Cannot find context root for web bundle with entry 'aa....aa' in this ear.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

0507

No <application> nodes were found.

An internal error occurred.

Contact the maintenance personnel.

0601

Cannot set the descriptor unless this node has been added to a document for Connector.

An internal error occurred.

Contact the maintenance personnel.

0602

The transaction support value for the connector is invalid: aa....aa

Specification of transaction-support is invalid.

aa....aa: Value of the specified transaction-support.

Specify one of the following: NoTransaction LocalTransaction XATransaction

0603

The authentication-mechanism-type of the connector is invalid: aa....aa

Specification of authentication-mechanism-type is invalid.

aa....aa: Specified authentication-mechanism-type value

Specify either 'BasicPassword' or 'Kerbv5'.

0604

No <connector> nodes could be found.

An internal error occurred.

Contact the maintenance personnel.

0605

Invalid XML: <security-permission-spec> in <connector> is empty.

The value is not specified in security-permission-spec.

Specify an appropriate value in security-permission-spec.

0701

aa....aa says it is linked to an EJB called bb....bb of type cc....cc, but no bean of this name and type can be found in this ejb-jar.

The type of EJB (aa....aa) linked with ejb-ref-name(bb....bb) differs from the type specified in ejb-ref-type(cc....cc).

aa....aa: Value of the display-name of the EJB to be linked.

bb....bb: Value specified in ejb-ref-name.

cc....cc: Value specified in ejb-ref-type.

Specify the value that matches with the type of EJB to be linked, in ejb-ref-type.

0702

aa....aa says it is linked to an EJB called bb....bb of home interface cc....cc, but no bean of this home interface name and type can be found in this ejb-jar.

home interface name of the EJB (aa....aa) linked with ejb-ref-name (bb....bb) does not match with the interface name (cc....cc) specified in home.

aa....aa: Value of the display-name of the EJB to be linked.

bb....bb: Value specified in ejb-ref-name.

cc....cc: Value specified in home.

Specify the home interface name of the EJB (aa....aa) in home.

0703

aa....aa says it is linked to an EJB called bb....bb of remote interface cc....cc, but no bean with this remote interface name and type can be found in this ejb-jar.

remote interface name of the EJB (aa....aa) linked with ejb-ref-name (bb....bb) does not match with the interface name (cc....cc) specified in remote.

aa....aa: Value of the display-name of the EJB to be linked.

bb....bb: Value specified in ejb-ref-name.

cc....cc: Value specified in remote.

Specify the remote interface name of the EJB (aa....aa) in remote.

0704

aa....aa says it is linked to an EJB called bb....bb of type cc....cc, but no bean of this name and type can be found in this ejb-jar.

The type of EJB (aa....aa) linked with ejb-ref-name(bb....bb) differs from the type specified in ejb-ref-type(cc....cc).

aa....aa: Value of the display-name of the EJB to be linked.

bb....bb: Value specified in ejb-ref-name.

cc....cc: Value specified in ejb-ref-type.

Specify the value that matches with the type of EJB to be linked, in ejb-ref-type.

0705

aa....aa says it is linked to an EJB called bb....bb of local home interface cc....cc, but no bean with this local home interface name and type can be found in this ejb-jar.

local-home interface name of the EJB (aa....aa) linked with ejb-ref-name (bb....bb) does not match with the interface name (cc....cc) specified in local-home.

aa....aa: Value of the display-name of the EJB to be linked.

bb....bb: Value specified in ejb-ref-name.

cc....cc: Value specified in local-home.

Specify the local-home interface name of the EJB (aa....aa) in local-home.

0706

aa....aa says it is linked to an EJB called bb....bb of local interface cc....cc, but no bean with this local interface name and type can be found in this ejb-jar.

local interface name of the EJB (aa....aa) linked with ejb-ref-name (bb....bb) does not match with the interface name (cc....cc) specified in local.

aa....aa: Value of the display-name of the EJB to be linked.

bb....bb: Value specified in ejb-ref-name.

cc....cc: Value specified in local.

Specify the local interface name of the EJB (aa....aa) in local.

0707

Cannot have null value for mandatory element 'aa....aa'.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

0708

aa....aa says it is linked to an EJB called bb....bb of remote business interface cc....cc, but no bean with this remote business interface name and type can be found in this ejb-jar.

remote business interface name of the EJB (aa....aa) linked with ejb-ref-name (bb....bb) does not match with the interface name (cc....cc) specified in business-remote.

aa....aa: Value of the display-name of the EJB to be linked.

bb....bb: Value specified in ejb-ref-name.

cc....cc: Value specified in business-remote.

Revise such that the remote business interface name is matching.

0709

aa....aa says it is linked to an EJB called bb....bb of local business interface cc....cc, but no bean with this local business interface name and type can be found in this ejb-jar.

local business interface name of the EJB (aa....aa) linked with ejb-ref-name (bb....bb) does not match with the interface name (cc....cc) specified in business-local.

aa....aa: Value of the display-name of the EJB to be linked.

bb....bb: Value specified in ejb-ref-name.

cc....cc: Value specified in business-local.

Revise such that the local business interface name is matching.

0801

Cannot set the descriptor unless this node has been added to a document for ejb.

An internal error occurred.

Contact the maintenance personnel.

0802

Cannot get the descriptor unless this node has been added to a document for ejb.

An internal error occurred.

Contact the maintenance personnel.

0803

Invalid XML: The document type of EJB is null.

The document type declaration is not specified in the DDs of EJB-JAR.

Specify the document type declaration.

0804

Invalid XML: The document type of EJB is unknown: aa....aa

The document type declaration is not specified correctly in the DDs of EJB-JAR.

aa....aa: Specified document type declaration

Specify the document type declaration correctly.

0805

ERROR: Cascade-delete can only be specified if the other role has a multiplicity of One.

If cascade-delete is specified, 'One' must be specified in multiplicity.

Either do not specify cascade-delete or specify 'One' in multiplicity.

0806

The value 'aa....aa' of the multiplicity element in EJB deployment descriptor XML is incorrect: the value must be One or Many.

Specification of multiplicity is invalid.

aa....aa: Value of multiplicity.

Specify either 'One' or 'Many'.

0807

No <ejb> nodes could be found.

An internal error occurred.

Contact the maintenance personnel.

0901

Cannot set the descriptor unless this node has been added to a document for ejb.

An internal error occurred.

Contact the maintenance personnel.

0902

Invalid XML: The Bean setting aa....aa is not specified as a local home or as a home interface.

Neither home nor local-home is specified in the EJB aa....aa.

aa....aa: display-name value of the EJB.

Specify either home or local-home (or both).

0903

Invalid XML: Document type for ejb is (null).

The document type declaration is not specified in the DDs of EJB-JAR.

Specify the document type declaration.

0904

Invalid XML: Unknown document type for ejb: aa....aa

The document type declaration is not specified correctly in the DDs of EJB-JAR.

aa....aa: Specified document type declaration

Specify the document type declaration correctly.

0905

The jms acknowledge mode is invalid: aa....aa

Specification of acknowledge-mode is invalid.

aa....aa: acknowledge-mode value.

Specify either 'Auto-acknowledge' or 'Dups-ok-acknowledge'.

0906

The subscription durability string is invalid: aa....aa

Specification of subscription-durability is invalid.

aa....aa: subscription-durability value.

Specify either 'Durable' or 'NonDurable'.

0907

The jms destination type is invalid: aa....aa

Specification of destination-type is invalid.

aa....aa: destination-type value.

Specify either 'javax.jms.Queue' or 'javax.jms.Topic'.

0908

No query element method was found in the XML: [aa....aa]

The method specified in query-method is not found.

aa....aa: Detailed message

Specify the query-method correctly according to the detailed message.

0909

The <query-method> is ambiguous or invalid.

The method specified in query-method does not exist or the asterisk (*) is not specified in the method-name of query-method.

Specify the query-method correctly.

0910

Invalid XML: Bean aa....aa does not define a remote interface.

remote is not specified in the EJB (aa....aa).

aa....aa: display-name value of the EJB.

When home is specified, specify remote also.

0911

Invalid XML: Bean aa....aa does not define a local interface.

Local is not specified in the EJB (aa....aa).

aa....aa: display-name value of the EJB.

When local-home is specified, specify local also.

0912

Invalid XML: Bean aa....aa does not define a ejb-class.

ejb-class of EJB (aa....aa) is not specified correctly.

aa....aa: display-name value of the EJB.

Specify the correct ejb-class.

0913

Invalid XML: Bean aa....aa does not define a ejb-name.

The ejb-name of EJB (aa....aa) is not specified correctly.

aa....aa: display-name value of the EJB.

Specify the ejb-name correctly.

0914

Bean aa....aa must specify a <abstract-schema-name> tag for cmp-version 2.x.

The abstract-schema-name is not specified in the EJB (aa....aa) of CMP2.x version.

aa....aa: display-name value of the EJB.

Specify the abstract-schema-name correctly.

1001

Cannot set the descriptor unless this node has been added to a document for ejb.

An internal error occurred.

Contact the maintenance personnel.

1101

Cannot set the descriptor unless this node has been added to a document for ejb.

An internal error occurred.

Contact the maintenance personnel.

1102

Failure : SQL relations to CMP aa....aa cannot be found from CMPEntityBean bb....bb.

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

1201

Cannot set the descriptor unless this node has been added to a document for Web.

An internal error occurred.

Contact the maintenance personnel.

1301

Cannot set the descriptor unless this node has been added to a document for Web.

An internal error occurred.

Contact the maintenance personnel.

1401

Cannot set the descriptor unless this node has been added to a document for Web.

An internal error occurred.

Contact the maintenance personnel.

1402

No <web> nodes could be found.

An internal error occurred.

Contact the maintenance personnel.

1501

Cannot set the descriptor unless this node has been added to a document for Web.

An internal error occurred.

Contact the maintenance personnel.

1601

getAttribute(key) : key is (null).

An internal error occurred.

Contact the maintenance personnel.

1602

getAttribute(key, value) : key is (null). value is aa....aa.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

1603

removeAttribute(key) : key is (null).

An internal error occurred.

Contact the maintenance personnel.

1604

addElement(value) : value is (null).

An internal error occurred.

Contact the maintenance personnel.

1605

removeElement(value) : value is (null)

An internal error occurred.

Contact the maintenance personnel.

1701

Document was null.

An internal error occurred.

Contact the maintenance personnel.

1702

cannot find a node under aa....aa with tag bb....bb.

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

1703

aa....aa has no sub nodes with tag bb....bb

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

1704

The public ID and the system ID for this XML document cannot be resolved: aa....aa [bb....bb].

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

1705

Type mismatch of DTD.

An internal error occurred.

Contact the maintenance personnel.

1801

The public ID is incorrect.

An incorrect public ID is specified in the document type declaration.

Specify a correct public ID.

1901

Illegal application version : aa....aa

The version of the J2EE application is invalid.

aa....aa: Maintenance information

Make sure that the value of the public identifier of application.xml or the value of the version attribute of the application element is correct.

1902

This application has no ejb jars of name aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

1903

This application has no ejb jars of name aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

1904

This application has no beans of name aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

1905

This application has no application clients of name aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

1906

This application has no application clients jars of name aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

1907

This application has no web app of name aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

1908

This application has no web app jars of name aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

1909

This application has no rar jar of name aa....aa.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

1910

This application has no application clients jars of name aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2001

An attempt to create a temporary directory has failed.

A temporary directory cannot be created.

If the permission to write to the temporary directory is not available, assign the write permissions.

If the capacity of a temporary directory location is insufficient, then secure the capacity.

2002

The class loader cannot be created.

An internal error occurred.

Contact the maintenance personnel.

2003

J2EE module 'aa....aa' cannot be extracted from the EAR file 'bb....bb'.

A file specified in module does not exist in EAR file.

aa....aa: File name specified in module

bb....bb: EAR file name

If this message is output while importing the EAR, revise the configuration of the EAR files.

If this message is output in cases other than import, contact the maintenance personnel.

2004

An attempt to unpack the archive failed. The parent file for aa....aa cannot be made.

The directory deploying the archive files cannot be created.

aa....aa: Name of a directory to be deployed

If the other applications are locked, terminate that application.

If the permission to write to the temporary directory is not available, assign the write permissions.

If the capacity is insufficient, secure the capacity.

2005

It failed in the analysis of Ear. The 1st argument of <File> is (null).

An internal error occurred.

Contact the maintenance personnel.

2006

The EAR file 'aa....aa' does not exist

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2007

No deployment information was found. The format was invalid. (EAR file = aa....aa)

The specified file does not have the correct format as an EAR file.

aa....aa: EAR file name

While importing the EAR file, revise the configuration of the files to be imported.

If this message is output in cases other than import, contact the maintenance personnel.

2008

File Object for Save to do Deployment Descriptor of J2EEModule for EJB is Null.

An internal error occurred.

Contact the maintenance personnel.

2009

File Object for Save to do Deployment Descriptor of J2EEModule for Web Application is Null.

An internal error occurred.

Contact the maintenance personnel.

2010

File Object for Save to do Deployment Descriptor of j2EEModule for ApplicationClient is Null.

An internal error occurred.

Contact the maintenance personnel.

2011

File Object for Save to do Runtime Deployment Descriptor of ApplicationClient is Null.

An internal error occurred.

Contact the maintenance personnel.

2012

File Object for Save to do Deployment Descriptor of j2EEModule for Connector is Null.

An internal error occurred.

Contact the maintenance personnel.

2013

File Object for Save to do Application (Ear) is Null.

An internal error occurred.

Contact the maintenance personnel.

2014

An attempt to save an EAR file resulted in an error: aa....aa to bb....bb

An EAR file cannot be saved.

aa....aa: Temporary file name created while creating an EAR file.

bb....bb: Name of the file to be saved

If the other applications are locked, terminate that application.

If the permission to write to the temporary directory is not available, assign the write permissions.

If the capacity is insufficient, secure the capacity.

2015

File Object for Save to do Deployment Descriptor of J2EEApplication is Null.

An internal error occurred.

Contact the maintenance personnel.

2016

File Object for Save to do Runtime Deployment Descriptor is Null.

An internal error occurred.

Contact the maintenance personnel.

2017

aa....aa is an unknown Descriptor type for removing.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2018

aa....aa is an unknown BundleDescriptor type for removing.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2019

'aa....aa' cannot be extracted from file 'bb....bb'.

aa....aa cannot be deployed from the archive files

aa....aa: File names in the archive file.

bb....bb: Archive file name

While importing the files, check and, if necessary, revise the configuration of the files to be imported.

If this message is output in cases other than import, contact the maintenance personnel.

2020

The file aa....aa to acquire ApplicationName doesn't exist.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2021

The Application name for Load to do 'application.xml' is Null.

An internal error occurred.

Contact the maintenance personnel.

2022

The File Object for Load to do 'Ear' is Null.

An internal error occurred.

Contact the maintenance personnel.

2023

The File Object for Load to do Runtime Deployment Descriptor is Null.

An internal error occurred.

Contact the maintenance personnel.

2024

The J2EEModule name of EJB for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2025

The File Object of EJB Jar for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2026

The J2EEModule name of Web Application for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2027

The File Object of Web Application War for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2028

The J2EEModule name of Connactor for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2029

The File Object of Connector Rar for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2030

The J2EEModule name of ApplicationClient for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2031

The File Object of ApplicationClient Jar for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2032

The J2EEModule name of ApplicationClient for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2033

The File Object of ApplicationClient Runtime Deployment Descriptor for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2101

No archive file for ApplicationClient: aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2102

Cannot package Application Client: aa....aa does not exist.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2103

You must include the class file for aa....aa in the packaging command of ApplicationClient Jar bb....bb

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

2104

The File Object of ApplicationClient Jar for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2105

ApplicationClient Jar 'aa....aa' does not exist.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2106

No deployment information for the application client was found at aa....aa in bb....bb.

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

2107

The manifest format is incorrect. There is no Mail-Class description in the manifest.

An internal error occurred.

Contact the maintenance personnel.

2108

The File Object of ApplicationClient Deployment Descriptor for Save is Null.

An internal error occurred.

Contact the maintenance personnel.

2109

The File Object of ApplicationClient Runtime Deployment Descriptor for Save is Null.

An internal error occurred.

Contact the maintenance personnel.

2110

The File Object of ApplicationClient Jar for Save is Null.

An internal error occurred.

Contact the maintenance personnel.

2111

An error occurred during renaming of an application client: from aa....aa to bb....bb.

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

2112

The J2EEModule name of ApplicationClient for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2113

The File Object of ApplicationClient Jar for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2114

The File Object of ApplicationClient Runtime Deployment Descriptor for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2201

Illegal application client version : aa....aa

The version of the J2EE application client is invalid.

aa....aa: Maintenance information

Make sure that the value of the public identifier of application-client.xml or the value of the version attribute of the application-client element is correct.

2202

This application client has no ejb reference by the name aa....aa.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2203

This application client has no JMS destination reference by the name of aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2204

This application client has no resource reference by the name aa....aa.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2301

An attempt to rename a JAR file failed: from aa....aa to bb....bb.

A JAR file cannot be saved. File name cannot be changed to bb....bb.

aa....aa: Old Old file name

bb....bb: New file name

If the other applications are locked, terminate that application.

If the permission to write to the temporary directory is not available, assign the write permissions.

If the capacity is insufficient, secure the capacity.

2302

An attempt to rename a JAR file failed: from aa....aa to bb....bb.

A JAR file cannot be saved. File name cannot be changed to bb....bb.

aa....aa: Old Old file name

bb....bb: New file name

If the other applications are locked, terminate that application.

If the permission to write to the temporary directory is not available, assign the write permissions.

If the capacity is insufficient, secure the capacity.

2303

An attempt to unpack the archive has failed. The parent file of aa....aa cannot be made.

The directory aa....aa deploying archive files cannot be created.

aa....aa: Directory name to be created.

If the other applications are locked, terminate that application.

If the permission to write to the temporary directory is not available, assign the write permissions.

If the capacity is insufficient, secure the capacity.

2304

aa....aa does not exist.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2401

No archive file for Connector: aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2402

The File Object of Connector Rar for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2403

Connector RAR 'aa....aa' does not exist.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2404

No deployment information for the connector was found at aa....aa in bb....bb

The specified file does not have the correct format as a RAR file.

aa....aa: File name to be acquired from a RAR file.

bb....bb: RAR file name

While importing the files, check and, if necessary, revise the configuration of the files to be imported.

If this message is output in cases other than import, contact the maintenance personnel.

2405

The File Object of Connector Rar for Save is Null.

An internal error occurred.

Contact the maintenance personnel.

2406

The File Object of Connector Deployment Descriptor for Save is Null.

An internal error occurred.

Contact the maintenance personnel.

2407

An attempt to rename an RAR file failed: from aa....aa to bb....bb.

A RAR file cannot be saved. File name cannot be changed to bb....bb.

aa....aa: Old Old file name

bb....bb: New file name

If the other applications are locked, terminate that application.

If the permission to write to the temporary directory is not available, assign the write permissions.

If the capacity is insufficient, secure the capacity.

2408

The connector cannot be packaged: aa....aa does not exist.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2409

An attempt to read the connector XML has failed: [aa....aa]

The DDs of RAR cannot be read.

aa....aa: Detailed message

Remove the cause according to the detailed message.

2410

The J2EEModule name of Connector Rar for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2411

The File Object Connector Deployment Descriptor for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2501

The container transaction type is unknown: aa....aa

Specification of trans-attribute is invalid.

aa....aa: Specified trans-attribute value.

Specify one of the following: NotSupported Supports Required RequiresNew Mandatory Never

2601

No archive file for EjbBundle: aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2602

An EJB cannot be packaged. aa....aa does not exist.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2603

The EJB JAR file 'aa....aa' does not exist.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2604

No deployment information for the EJB was found at aa....aa in bb....bb

The specified file does not have the correct format as an EJB-JAR file.

aa....aa: File name acquired from EJB-JAR file.

bb....bb: EJB-JAR file name

While importing the files, check and, if necessary, revise the configuration of the files to be imported.

If this message is output in cases other than import, contact the maintenance personnel.

2605

The J2EEModule name of Ejb Jar for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2606

The File Object of Ejb Jar for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

2607

File Object of Ejb Jar for Save is Null.

An internal error occurred.

Contact the maintenance personnel.

2608

An attempt to rename an EJB JAR file failed: from aa....aa to bb....bb.

The EJB-JAR file cannot be saved. File name cannot be changed to bb....bb.

aa....aa: Old Old file name

bb....bb: New file name

If the other applications are locked, terminate that application.

If the permission to write to the temporary directory is not available, assign the write permissions.

If the capacity is insufficient, secure the capacity.

2609

Couldn't get application archivist for Ejb Jar Update.

An internal error occurred.

Contact the maintenance personnel.

2701

Illegal ejb version : aa....aa

The version of EJB-JAR is invalid.

aa....aa: Maintenance information

Make sure that the value of the public identifier of ejb-jar.xml or the value of the version attribute of the ejb-jar element is correct.

2702

Referencing error: This bundle has no bean with the name aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2703

Invalid XML: aa....aa(bb....bb) is not defined at cc....cc.

aa....aa is not defined in bb....bb.

aa....aa: Tag value

bb....bb: Tag name defining aa....aa

cc....cc: Tag name

Specify the value defined in bb....bb in cc....cc.

2801

The CMP version is invalid: aa....aa

The cmp-version is invalid.

aa....aa: Specified cmp-version value.

Specify either '1.x' or '2.x'.

2901

Cannot set use-caller-identity for Message Driven beans.

An internal error occurred.

Contact the maintenance personnel.

2902

Cannot set RunAs identity when using caller identity.

An internal error occurred.

Contact the maintenance personnel.

2903

Cannot get RunAs identity when using caller identity.

An internal error occurred.

Contact the maintenance personnel.

2904

A method level transaction attribute cannot be specified for a bean with the transaction type aa....aa. This EJB name is bb....bb.

The EJB (bb....bb) is BMT. The container-transaction cannot be specified.

aa....aa: Specified transaction-type value.

bb....bb: ejb-name value of the EJB.

Change to CMT.

Delete the container-transaction.

2905

Cannot add roles when the descriptor is not part of an ejb bundle.

An internal error occurred.

Contact the maintenance personnel.

2906

Cannot add roles when the ejb bundle does have them: RoleName is aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2907

Cannot add roles when the descriptor is not part of an ejb bundle.

An internal error occurred.

Contact the maintenance personnel.

2908

Cannot remove roles when the ejb bundle does not have them: RoleName is aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

2909

This bean 'aa....aa' has no environment property by the name of bb....bb.

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

2910

This bean 'aa....aa' has no Ejb Reference by the name of bb....bb

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

2911

This bean 'aa....aa' has no JMS destination reference by the name of bb....bb

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

2912

This web app has no resource reference by the name of aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3001

Entity beans can only have Container transaction type. The type was being set to aa....aa.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3002

aa....aa is not a valid value for the entity reentrancy of EJB bb....bb.

Specification of reentrant is invalid.

aa....aa: Specified reentrant value.

bb....bb: ejb-name value of the EJB.

Specify either True or False.

3003

aa....aa is not an allowed persistence type of Ejb bb....bb.

Specification of persistence-type is invalid.

aa....aa: Specified persistence-type value.

bb....bb: ejb-name value of the EJB.

Specify either 'Bean' or 'Container'.

3004

Cannot set type aa....aa on an entity bean bb....bb.

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

3101

aa....aa is not a valid EJB reference type.

Specification of ejb-ref-type is invalid.

aa....aa: Specified ejb-ref-type value.

Specify either 'Entity' or 'Session'.

3201

aa....aa is not a legal ejb type.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3202

Remote home interface aa....aa does not have a findByPrimaryKey method.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3301

Incorrect value for integrity: aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3302

Incorrect value for confidentiality: aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3303

Incorrect value for establishTrustInTarget: aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3304

Incorrect value for establishTrustInClient: aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3305

Incorrect value for authentication method: aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3306

Incorrect value for callerPropagation: aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3401

The transaction attribute aa....aa of a message-driven bean bb....bb is invalid.

The transaction attribute that cannot be used in Message-driven Bean was specified.

aa....aa: Specified trans-attribute value.

bb....bb: ejb-name value of the EJB.

Specify either 'NotSupported' or 'Required'.

3402

Cannot set the type 'aa....aa' of a message-driven bean bb....bb.

An internal error occurred.

aa....aa: Maintenance information

bb....bb: Maintenance information

Contact the maintenance personnel.

3403

Message-driven bean aa....aa isn't set up to have durable subscription.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3404

Message-driven bean aa....aa isn't set up to have durable subscription.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3405

onMessage is not defined for message-bean aa....aa.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3406

The transaction type aa....aa of a message-driven bean bb....bb is invalid.

The transaction-type that cannot be used in Message-driven Bean was specified.

aa....aa: Specified transaction-type value.

bb....bb: ejb-name value of the EJB.

Specify either 'Bean' or 'Container'.

3501

EJB aa....aa cannot be set up in ejb-local-ref 'bb....bb' because the local interface has not been defined.

Local is not defined in the EJB referenced in ejb-local-ref

aa....aa: ejb-name value of the EJB to be referenced.

bb....bb: ejb-ref-name value.

Define local in aa....aa.

3502

EJB aa....aa cannot be set up in ejb-ref 'bb....bb' because the remote interface has not been defined.

Remote is not defined in the EJB referenced in ejb-ref.

aa....aa: ejb-name value of the EJB to be referenced.

bb....bb: ejb-ref-name value.

Define remote in aa....aa.

3503

The API syntax is invalid. The link name cannot be acquired from an external reference.

An internal error occurred.

Contact the maintenance personnel.

3504

This ejb reference has no ejb descriptor.

An internal error occurred.

Contact the maintenance personnel.

3505

This ejb reference has no ejb descriptor.

An internal error occurred.

Contact the maintenance personnel.

3601

The session type aa....aa for session EJB bb....bb is invalid. The type must be 'cc....cc', 'dd....dd', or 'ee....ee'.

The session-type is invalid.

aa....aa: Specified session-type value.

bb....bb: ejb-name value of the EJB.

cc....cc: Stateful

dd....dd: Stateless

ee....ee: Singleton

Specify either Stateful, Stateless, or Singleton.

3602

Cannot set the type of a session bean aa....aa.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

3603

The transaction type aa....aa for a session bean bb....bb is invalid.

The transaction-type that cannot be used in Session Beans was specified.

aa....aa: Specified transaction-type value.

bb....bb: ejb-name value of the EJB.

Specify either 'Bean' or 'Container'.

3702

aa....aa is not an allowed property value type.

Specification of env-entry-type is invalid.

aa....aa: Specified data type.

Specify one of the following: java.lang.Boolean java.lang.Byte java.lang.Character java.lang.String java.lang.Short java.lang.Integer java.lang.Long java.lang.Float java.lang.Double

3703

'aa....aa' cannot be changed to the Character class.

The value specified in env-entry-value cannot be used in java.lang.Character.

aa....aa: Value specified in env-entry-value.

Specify only a single character in env-entry-value.

3704

An instance of aa....aa cannot be created from bb....bb (reason = cc....cc)

The value specified in env-entry-value cannot be used in aa....aa.

aa....aa: Value specified in env-entry-type.

bb....bb: Value specified in env-entry-value.

cc....cc: Detailed message

Specify the value that can be used in env-entry-type, in env-entry-value.

3705

The environment properties type is invalid: aa....aa

Specification of env-entry-type is invalid.

aa....aa: Specified data type.

Specify one of the following: java.lang.Boolean java.lang.Byte java.lang.Character java.lang.String java.lang.Short java.lang.Integer java.lang.Long java.lang.Float java.lang.Double

3801

The cmp-field or cmr-field name cannot be empty strings.

No value is specified in the field-name of cmp-field or cmr-field-name of cmr-field.

Specify the value correctly in the field-name and cmr-field-name.

3803

The cmp-field or cmr-field name aa....aa must begin with a lower-case letter.

The field-name of cmp-field or cmr-field-name of cmr-field must begin with a lower-case letter.

aa....aa: Value specified in the field-name or cmr-field-name.

The first letter must be in lower case. Whether the first letter is in lower case is determined according to the isLowerCase method of java.lang.Character.

3901

aa....aa is not a valid authentication method for the Web.

Specification of auth-method is invalid.

aa....aa: Specified auth-method value

Specify one of the following: BASIC FORM DIGEST CLIENT-CERT

4001

The message-driven bean aa....aa does not process the method 'bb....bb'.

The message-driven Bean (aa....aa) does not process the method (bb....bb).

aa....aa: ejb-name value of the EJB.

bb....bb: Specified method name.

Specify the method name correctly.

4002

Method aa....aa is not contained in Ejb 'bb....bb'.

Method (aa....aa) is not contained in the EJB (bb....bb).

aa....aa: Specified method name

bb....bb: ejb-name value of the EJB.

Specify the method name correctly.

4003

Method aa....aa was not found in EJB bb....bb.

Method (aa....aa) is not contained in the EJB (bb....bb).

aa....aa: Specified method name

bb....bb: ejb-name value of the EJB.

Specify the method name correctly.

4101

unknown Reference type.

An internal error occurred.

Contact the maintenance personnel.

4201

CMRFieldInfo not found for field aa....aa.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

4202

There is no local interface for the target bean aa....aa of the CMR field.

When cmr-field is specified, local also must be specified in that EJB.

aa....aa: ejb-name value of the EJB.

Also, specify local in the EJB.

4203

PersistentFieldInfo not found for field aa....aa.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

4204

PersistentFieldInfo not found for pkey field aa....aa.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

4205

No cmp field is defined for CMP EJB aa....aa.

No cmp-field is defined for EJB (aa....aa).

aa....aa: display-name value of the EJB.

Specify the cmp-field.

4206

Error building allSqlStatementedMethods: aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

4207

Accessor aa....aa for CMP field bb....bb cannot be found.

Access method (aa....aa) for cmp-field (bb....bb) cannot be found.

aa....aa: Access method name

bb....bb: Value specified in cmp-field.

Specify the cmp-field correctly.

4208

CMP field aa....aa in class bb....bb cannot be found.

CMP field (aa....aa) is not defined in class (bb....bb).

aa....aa: Value specified in cmp-field.

bb....bb: Class name of CMP.

Specify the cmp-field correctly.

4209

CMP/CMR field aa....aa must start with a lower-case character.

The field-name or cmr-field-name must begin with a lower-case character.

aa....aa: Value specified in the field-name or cmr-field-name.

The first letter must be in lower case. Whether the first letter is in lower case is determined according to the isLowerCase method of java.lang.Character.

4301

cmr-field-type is aa....aa. The value must be java.util.Collection or java.util.Set.

Specification of cmr-field-type is invalid.

aa....aa: Value specified in the cmr-field-type.

Specify either 'java.util.Collection' or 'java.util.Set'.

4401

aa....aa is not a valid transport guarantee value.

Specification of transport-guarantee is invalid.

aa....aa: Value specified in transport-guarantee.

Specify either 'NONE', 'INTEGRAL' or 'CONFIDENTIAL'.

4501

Jsp aa....aa does not exist in the Web application bb....bb.

The file specified in jsp-file does not exist.

aa....aa: File name specified in jsp-file.

bb....bb: display-name value of the WAR.

While importing the files, check and, if necessary, revise the configuration of the files to be imported.

If this message is output in cases other than import, contact the maintenance personnel.

4502

The Web application cannot be packaged. aa....aa does not exist.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

4503

Reading web.xml resulted in an error: [aa....aa]

The DDs of WAR cannot be read.

aa....aa: Detailed message

Remove the cause according to the detailed message.

4504

File Object of Web Application Deployment Descriptor for Save is Null.

An internal error occurred.

Contact the maintenance personnel.

4505

An attempt to rename a WAR file failed: from aa....aa to bb....bb.

A WAR file cannot be saved. File name cannot be changed to bb....bb.

aa....aa: Old Old file name

bb....bb: New file name

If the other applications are locked, terminate that application.

If the permission to write to the temporary directory is not available, assign the write permissions.

If the capacity is insufficient, secure the capacity.

4506

The File Object of Web Application War for Save is Null.

An internal error occurred.

Contact the maintenance personnel.

4507

The J2EEModule name of Web Application War for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

4508

The File Object of Web Application War for Load is Null.

An internal error occurred.

Contact the maintenance personnel.

4509

The Web WAR file 'aa....aa' does not exist.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

4510

No deployment information for the Web was found at aa....aa in bb....bb.

The specified file does not have the correct format as WAR files.

aa....aa: File name to be acquired from WAR files.

bb....bb: WAR file name

While importing the files, check and, if necessary, revise the configuration of the files to be imported.

If this message is output in cases other than import, contact the maintenance personnel.

4511

A descriptor parsing error occurred: [aa....aa]

The DDs cannot be analyzed.

aa....aa: Detailed message

Remove the cause according to the detailed message.

4601

Illegal web version : aa....aa

The version of WAR is invalid.

aa....aa: Maintenance information

Make sure that the value of the public identifier of web.xml or the value of the version attribute of the web-app element is correct.

4602

This web component has no JMS destination reference by the name of aa....aa.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

4603

This web app has no ejb reference by the name of aa....aa.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

4604

This web app has no resource reference by the name of aa....aa

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

4701

The implementation of aa....aa for the Web cannot be instantiated.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

4702

The aa....aa implementation class for the Web cannot be found.

An internal error occurred.

aa....aa: Maintenance information

Contact the maintenance personnel.

4801

Invalid argument for createMessage method of duplicate object.

An internal error occurred.

Contact the maintenance personnel.

4802

Cannot get Message when the descriptor is not part of a bundle.

An internal error occurred.

Contact the maintenance personnel.

4803

Cannot get Message when the descriptor is not part of a enterprise-beans.

An internal error occurred.

Contact the maintenance personnel.

4901

Illegal connector version : aa....aa

The version of the resource adapter is invalid.

aa....aa: Maintenance information

Make sure that the value of the public identifier of ra.xml or the value of the version attribute of the connector element is correct.