| Explanation |
See message. |
| Action |
Repeat the operation and provide a value for the specified parameter. |
| Explanation |
See message. |
| Action |
Repeat the operation and provide a value for the specified parameter. |
| Explanation |
See message. |
| Action |
Repeat the operation and provide a value for the element. |
| Explanation |
The number of characters that can be used for the value of the specified parameter is restricted because either it corresponds to a field in the Common Base Event specification that has a maximum length or the database field in which the value is stored is of a limited size. |
| Action |
Repeat the operation and provide a value for the specified parameter that does not exceed the maximum number of characters. |
| Explanation |
The number of characters that can be used for the value of the element is restricted because either it corresponds to a field in the Common Base Event specification that has a maximum length or because the database field in which the value is stored is of a limited size. |
| Action |
Repeat the operation and provide a value for the element that does not exceed the maximum number of characters. |
| Explanation |
Event definitions are arranged in a hierarchy in which an event definition can be the parent of any number of other event definitions. The name of an event definition cannot be used as its own parent name. |
| Action |
Repeat the operation and provide a valid value for the parentName parameter. |
| Explanation |
See message. |
| Action |
Repeat the operation and provide a value for the specified parameter that is greater than or equal to zero. |
| Explanation |
An event definition can describe a number of extended data elements. Each of these extended data elements must have a unique name. |
| Action |
Do one of the following:
|
| Explanation |
An extended data element description can contain a number of child extended data element descriptions. Each of the immediate child extended data element descriptions must have a unique name. |
| Action |
Do one of the following:
|
| Explanation |
An event definition can describe a number of properties. Each of these properties must have a unique name. |
| Action |
Do one of the following:
|
| Explanation |
See message. |
| Action |
Repeat the operation and provide a valid value for the type parameter. Valid values for the type of an extended data element are listed in the documentation for the class org.eclipse.hyades.logging.events.cbe.ExtendedDataElement. |
| Explanation |
Most types of extended data element can have a number of default string values. The hexBinary type, however, can have only a single default hexadecimal value. |
| Action |
See message. |
| Explanation |
The only type of extended data element that can have a default hexadecimal value is hexBinary. Most other types can have some number of default string values. |
| Action |
See message. |
| Explanation |
See message. |
| Action |
Do not use the setDefaultValues method for an extended data element of type noValue. |
| Explanation |
See message. |
| Action |
Use a single value in the call to the setDefaultValues method. |
| Explanation |
The value of the default hexadecimal value is limited due to a restriction of the database field in which the value is stored. |
| Action |
Repeat the operation and provide a value that does not exceed the maximum number of bytes. |
| Explanation |
The minimum number of times an extended data element can occur must be less than or equal to the maximum number of times. |
| Action |
Set the value of the maxOccurs parameter first, or specify a smaller value for the minOccurs parameter. |
| Explanation |
The minimum number of times an extended data element can occur must be less than or equal to the maximum number of times. |
| Action |
Set the minOccurs parameter first, or specify a larger value for the maxOccurs parameter. |
| Explanation |
A property description cannot have permitted values if it has a minimum or a maximum value. Similarly, a property description cannot have a minimum or a maximum value if it has permitted values. |
| Action |
Repeat the operation and do not use the setPermittedValues method. |
| Explanation |
A property description cannot have a minimum a maximum value if it has permitted values. Similarly, a property description cannot have permitted values if it has a minimum or a maximum value. |
| Action |
Repeat the operation and do not use the setMinimumValue method or the setMaximumValue method. |
| Explanation |
The event catalog does not contain an event definition with the specified name. |
| Action |
Verify that the name you are using is the correct name. |
| Explanation |
Each event definition in the event catalog must have a unique name. When adding an event definition, you can replace an existing event definition. |
| Action |
See message. |
| Explanation |
When replacing an event definition in the event catalog, the new event definition and the existing definition must have the same parent. In other words, the event definitions must occupy the same position in the hierarchy of event definitions. |
| Action |
Recreate the event definition using the parent name of the existing event definition. Then add the event definition to the event catalog. |
| Explanation |
The event catalog can contain only one root definition. When adding an event definition, you can replace an existing event definition. |
| Action |
See message. |
| Explanation |
The event catalog does not contain an event definition for the specified parent name. |
| Action |
Verify that the name of the parent definition that you are using is the correct name. |
| Explanation |
Inheritance by an event definition of the extended data element descriptions of an ancestor is governed by event definition inheritance rules. These rules are described in the documentation for class com.ibm.events.catalog.EventDefinition in the event catalog API. An event definition cannot change the type of an extended data element description that it inherits. |
| Action |
Recreate the event definition either omitting the extended data element description or making its type the same as the type of the ancestor event definition. Then add the event definition to the event catalog. |
| Explanation |
Inheritance by an event definition of the property
descriptions of an ancestor is governed by event definition
inheritance rules. These rules are described in the
documentation for class
com.ibm.events.catalog.EventDefinition in the event catalog
API. An event definition cannot change the
|
| Action |
Recreate the event definition omitting the property
description or making its
|
| Explanation |
Inheritance by an event definition of the extended data element descriptions of an ancestor is governed by event definition inheritance rules. These rules are described in the documentation for class com.ibm.events.catalog.EventDefinition in the Event Catalog API. An event definition cannot change the type of an extended data element description that it inherits. Replacing the event definition would cause a descendant event definition to violate this rule. |
| Action |
Recreate the event definition either omitting the extended data element description or making its type the same as the type of the descendant event definition, or delete the descendant event definition from the event catalog. Then add the event definition to the event catalog. |
| Explanation |
Inheritance by an event definition of the property
descriptions of an ancestor is governed by event definition
inheritance rules. These rules are described in the
documentation for class
com.ibm.events.catalog.EventDefinition in the event catalog
API. An event definition cannot change the
|
| Action |
Recreate the event definition either omitting the property
description or making its
|
| Explanation |
The event catalog expected to find a file in one of the directories listed in the class path, but the file does not exist. The file is a Common Event Infrastructure internal file. This could indicate a problem with the file system or an error in the installation of the Common Event Infrastructure application. |
| Action |
Verify that the Common Event Infrastructure application is installed correctly. |
| Explanation |
See message. |
| Action |
Correct the XML document, then repeat the operation. |
| Explanation |
This could indicate an error in the installation of the Common Event Infrastructure application. |
| Action |
For more information about the cause of the error, see the exception message. If necessary, verify that the Common Event Infrastructure application is installed correctly. |
| Explanation |
This problem could indicate an error in the installation of the Common Event Infrastructure application. |
| Action |
For more information about the cause of the problem, see the exception message. If necessary, verify that the Common Event Infrastructure application is installed correctly. |
| Explanation |
An error occurred when the create method was called on the local or remote home of the specified enterprise bean. |
| Action |
For more information about the cause of the problem, see the exception message. If necessary, verify that the Common Event Infrastructure application is installed correctly and that the Common Event Infrastructure server is running correctly. |
| Explanation |
An error occurred when the remove method was called on the EJB local home of the specified EJB. |
| Action |
For more information about the cause of the problem, see the exception message. If necessary, verify that the Common Event Infrastructure application is installed correctly and that the Common Event Infrastructure server is running correctly. |
| Explanation |
An error occurred when the finder method was called on the EJB local home of the specified enterprise bean. |
| Action |
For more information about the cause of the problem, see the exception message. If necessary, verify that the Common Event Infrastructure application is installed correctly and that the Common Event Infrastructure server is running correctly. |
| Explanation |
The JNDI service might not be running, or it cannot be reached. |
| Action |
For more information about the cause of the problem, see the exception message. If necessary, verify that the Common Event Infrastructure application is installed correctly and that the Common Event Infrastructure server is running correctly. |
| Explanation |
See message. |
| Action |
Verify that the specified file exists and that is accessible by the Common Event Infrastructure server. |
| Explanation |
See message. |
| Action |
See the exception message for additional information about the cause of the problem. |
| Explanation |
See message. |
| Action |
See the exception message for additional information about the cause of the problem. |