Event-Driven Architecture Tools Messages

EDAERBCE0000 The service group name must not be empty
Explanation

Each service group must have a valid and unique name. The name must be unique in the namespace of all service groups. The service group name must follow the rule: <alpha character>+(<word character> | - | . )* where <word character> can be a digit, a lower or upper case character, and <alpha character> can be a lower or upper case character.

Action

Specify a valid and unique name for the service group.


EDAERBCE0001 A service group with the name "{0}" already exists.
Explanation

Each service group must have a valid and unique name. The name must be unique in the namespace of all service groups. The service group name must follow the rule: <alpha character>+(<word character> | - | . )* where <word character> can be a digit, a lower or upper case character, and <alpha character> can be a lower or upper case character.

Action

Specify a unique service group name.


EDAERBCE0002 Invalid service group name "{0}". It must follow the rule: <alpha character>+(<word character> | - | . )*
Explanation

Each service group must have a valid and unique name. The name must be unique in the namespace of all service groups. The service group name must follow the rule: <alpha character>+(<word character> | - | . )* where <word character> can be a digit, a lower or upper case character, and <alpha character> can be a lower or upper case character.

Action

Specify a valid service group name which follows the rule of service group names.


EDAERBCE0003 Invalid service group name "{0}" because it is different from the created unique instance name "{1}" which is used for the configuration persistence.
Explanation

Each service group must have a valid and unique name. The name must be unique in the namespace of all service groups. The service group name must follow the rule: <word character>+(<word character> | - | . | _ )* where <word character> can be a digit, a lower or upper case character.

Action

Specify a valid service group name where service group name must be the same as the unique instance name.


EDAERBCE0004 The default service group must not be deleted
Explanation

The default service group name is "Default". This group covers all event types which are not associated to other service groups, therefore the "Default" service group cannot be deleted.

Action

Do not delete the "Default" service group.


EDAERBCE0006 The default service group must not be renamed
Explanation

The default service group name is "Default". This group covers all event types which are not associated to other service groups, therefore the "Default" service group cannot be renamed.

Action

Do not rename the "Default" service group.


EDAERBCE0007 The service group "{0}" is still referenced by an event type e.g. "{1}"
Explanation

A service group can only be deleted if no event types are associated to it.

Action

Remove all event types associations to the service group before deleting it.


EDAERBCE0008 The service group "{0}" contains duplicate service entries: "{1}"
Explanation

Each service group must contain at least one service. The list of services within a service group must contain only unique services.

Action

Use only unique services within a service group.


EDAERBCE0009 The service group "{0}" must contain at least one service
Explanation

Each service group must contain at least one service. The list of services within a service group must contain only unique services.

Action

Assign at least one service to the service group.


EDAERBCE0010 The referenced service "{0}" does not exist
Explanation

The specified service does not exist and cannot be assigned to a service group.

Action

Choose a valid service in order to assign it to a service group.


EDAERBCE0011 In the group "{0}" only one service can be marked as "source"
Explanation

Only one service within a service group can be specified as "source".

Action

Mark only one service as "source".


EDAERBCE0012 Service type name not found for service "{0}" in group "{1}"
Explanation

A service with invalid service type has been specified within a certain service group.

Action

Use a service with a valid service type. Only valid services may be assigned to a service group.


EDAERBCE0013 Service type not found for service "{0}" in group "{1}"
Explanation

A service with invalid service type has been specified within a certain service group.

Action

Use a service with a valid service type. Only valid services may be assigned to a service group.


EDAERBCE0014 The service "{0}" is marked as "source", however the corresponding service type "{1}" cannot act as source
Explanation

The parameters of each service depend on its service type definition. If the service type is not configured to act as source, then the services of that type cannot be configured as "source" either.

Action

Remove the "source" marker from the service definition or change the configuration of the service type in order to allow the "source" marker.


EDAERBCE0015 The service "{0}" is marked as "reliable", however the corresponding service type "{1}" does not support reliable
Explanation

The parameters of each service depend on its service type definition. If the service type is not configured to support reliable delivery, then the services of that type cannot be configured as "reliable" either.

Action

Remove the "reliable" marker from the service definition or change the configuration of the service type in order to allow the "reliable" marker.


EDAERBCE0017 The service name must not be empty
Explanation

Each service must have a valid and unique name. A service name must follow the rule: <word character>+(<word character> | - | . )* where <word character> can be a digit, lower or upper character.

Action

Specify a valid name for the service.


EDAERBCE0018 A service with the name "{0}" already exists.
Explanation

Each service must have a valid and unique name. A service name must follow the rule: <word character>+(<word character> | - | . )* where <word character> can be a digit, lower or upper character.

Action

Specify a unique name for the service.


EDAERBCE0019 The service "{0}" is still used by the Service Group "{1}".
Explanation

A service can only be deleted if it is not included in a service group.

Action

Remove all references to the service before deleting it.


EDAERBCE0020 Invalid name "{0}". It must follow the rule: <alpha character>+(<word character> | - | . )*
Explanation

A name must follow the rule: <alpha character>+(<word character> | - | . )* where <word character> can be a digit, lower or upper character.

Action

Do not use invalid URI characters.


EDAERBCE0021 Name "{0}" not unique considering the instance IDs. (Not allowed predefined ids: {1}).
Explanation

Software AG Platform Manager allows only unique instance IDs to be used for the Event Routing runtime component.

Action

Change the name so that is is not identical to any other already existing service names, service group names, or the predefined {1}.


EDAERBCE0024 Event type "{0}" does not exist
Explanation

The specified event type is not present in the Event Type Store, and therefore cannot be used in the Service Group Event Types configuration.

Action

Remove the event type from the Service Group Event Types.


EDAERBCE0025 Duplicate event type "{0}"
Explanation

The specified event type appears twice in the Service Group Event Types configuration.

Action

Remove the duplicate event type from the Service Group Event Types configuration.


EDAERBCE0026 The service group "{0}" does not exist
Explanation

The specified service group does not exist.

Action

Remove the service group from the Service Group Event Types configuration, or create the service group before updating the Service Group Event Types configuration.


EDAERBCE0028 A service group must not be renamed
Explanation

A service group name is used as a unique id to reference the service group.

Action

If a new name is required, delete the service group and create a new one. Before deleting the service group make sure that no event types are associated to it.


EDAERBCE0029 A service must not be renamed
Explanation

A service name is used as a unique id to reference the service.

Action

If a new name is required, delete the service and create a new one. Before deleting the service make sure it is no longer referenced by any service group.


EDAERBCE0030 "{0}" is not a valid capacity value
Explanation

The capacity must consist of digits only, optionally followed by one of [K, k, M, m, G, g]. The resulting value must not be larger than 9223372036854775807.

Action

Provide a valid capacity.


EDAERBCE0032 The "{0}" service has to be configured as source&destination
Explanation

This predefined service can only be used as "source and destination".

Action

Configure the service as "source and destination".


EDAERBCE0033 Cannot use reserved service name "{0}"
Explanation

This is the name of a predefined service.

Action

Choose a different service name.


EDAERBCE0038 It is not possible to change storage location, while instance {0} is running
Explanation

Please ensure that the component using Event Routing is restarted in order to start using the new storage location.

Action

Changing the storage location requires a restart of the components using Event Routing.


EDAERBCE0040 The specified path "{0}" is not a valid directory
Explanation

The path is not an existing directory.

Action

Make sure that the specified directory exists.


EDAERBCE0041 The specified path "{0}" is not an absolute path.
Explanation

The path must be specified as an absolute path.

Action

Make sure that the path is specified as an absolute path.


EDAERBCE0042 The specified path "{0}" does not exist
Explanation

The path must be a valid folder and it must exist on disk.

Action

Make sure the path location is an existing folder and create it if necessary.


EDAERCE0005 It is not allowed to create new instances of Runtime Configuration
Explanation

Only one built-in instance of Runtime Configuration exists.

Action

In order to apply your changes, edit the built-in instance of Runtime Configuration.


EDAERCE0021 Invalid name "{0}". It must follow the rule: <alpha character>+(<word character> | - | . )*
Explanation

Each service must have a valid and unique name. A service name must follow the rule: <alpha character>+(<word character> | - | . )* where <word character> can be a digit, lower or upper character, and <alpha character> can be a lower or upper case character. The service name is the same as the corresponding instance ID, which is used to identify a service in the configuration persistence. This instance ID must be unique for all instances of Event Routing.

Action

Use a valid service name following the naming rules.


EDAERCE0022 It is not allowed to create new instances of Service Group Event Types
Explanation

Only one built-in instance of Service Group Event Types exists.

Action

In order to apply changes, edit the built-in instance of Service Group Event Types.


EDAERCE0023 It is not allowed to delete the instance of Service Group Event Types
Explanation

Only one built-in instance of Service Group Event Types exists, and it cannot be be deleted.

Action

In order to apply changes, edit the built-in instance of Service Group Event Types.


EDAERCE0027 Internal error: the given "RuntimeComponent" parameter is not an instance of the "Instance" interface
Explanation

This is an internal error.

Action

Contact your support organization.


EDAERCE0031 It is not allowed to delete the instance of Runtime Configuration
Explanation

There is only one built-in instance of Runtime Configuration, which must not be deleted.

Action

In order to apply changes, edit the built-in instance of Runtime Configuration.


EDAERCPE0028 Passed object of RunWatchdog is not valid
Explanation

During instanciation of one of the RunWatchdog handlers, the RunWatchdog object itself is passed. However, this RunWatchdog object is not valid (null).

Action

Verify that the RunWatchdog object is valid before instanciating the handlers.


EDAERCPE0029 Default configuration not found
Explanation

If no event routing configuration is available, all default configuration files are copied to the place where the configuration is expected. However, the zip file containing all these files could not be found. This file is created by calling the "eclipse" task of the project.

Action

Execute the "eclipse" task of the gradle build script beforehand.


EDAERCPE0030 File {0} is empty! Service {1} is not created and no events can be handled by {1}
Explanation

The file has no content. A service cannot be created and no events can be sent or received.

Action

Provide a file containing the desired entry or use a graphical configuration such as Software AG Command Central user interface for creating a correct service.


EDAERCPE0031 {0} contains invalid content {1}
Explanation

The content is not correct.

Action

Correct the content or use a graphical configuration tool such as Software AG Command Central.


EDAERE0002 Failed to start a subscriber route consuming from URI ''{0}''.
Explanation

A subscriber cannot be created because of an unavailable source service or an invalid or an already used durable subscriber ID.

Action

Check if the service configured as a source is available. If you are creating a durable subscriber, make sure that its ID does not contain invalid characters, and that no durable subscriber with this ID for the same event type is currently active on the source service.


EDAERE0003 Failed to start a subscriber route consuming from URI ''{0}'': a durable subscriber with ID ''{1}'' already exists on the IP service.
Explanation

An IP service durable subscriber cannot be created because of an already used durable subscriber ID.

Action

Make sure that no durable subscriber with this ID for the same event type is currently active on the source IP service.


EDAERE0058 Failed to delete the service implementation bundle for service name: "{0}".
Explanation

Undeploying the service from the bundles folder of the configuration failed. Even if the service could not be deleted, this should not prevent the system from running normally.

Action

Delete the service jar file manually if desired.


EDAESE0000 Failed to create an event parser.
Explanation

The factory was not able to create an event parser.

Action

Check the log for exception stacktrace.


EDAESIE0004 The selected Integration Server Document Type is recursive and its conversion results in a recursive Event Type which is not supported.
Explanation

The Integration Server Document type which has been selected is recursive. After the conversion a recursive Event Type is produced. Recursive Event Types are not supported.

Action

Remove recursion from the Integration Server Document type prior to creating an event type from it.


EDAESIE0006 Restrictions not supported for {0}
Explanation

Union and List are not supported for restrictions.

Action

Please contact your software supplier.


EDAESIE0007 Unsupported facet {0} with value {1}
Explanation

The called restriction facet is not supported.

Action

Please contact your software supplier.


EDAESIE0029 Event Types without a target namespace are not allowed outside the root "Event Types" directory.
Explanation

An event type which does not define target namespace exists outside the root of the event types directrory.

Action

Either move this event type in the "Event Types" directory or manually create a target namespace definition for it.


EDAESIE0034 Node {0} is not filterable because node {1} is not of cardinality 0..1 or 1..1.
Explanation

The node is not filterable, since the node path can have several values (and not only a unique one).

Action

Set the node to not filterable, or set the cardinality of all nodes on the node path to cardinality 1..1.


EDAESIE0035 Node {0} is not filterable because nodes {1} are not of cardinality 0..1 or 1..1.
Explanation

The node is not filterable, since the node path can have several values (and not only a unique one).

Action

Set the node to not filterable, or set the cardinality of all nodes on the node path to cardinality 1..1.


EDAETE0211 Event Types without a target namespace are not allowed outside the root "Event Types" directory.
Explanation

An event type which does not define target namespace exists outside the root of the event types directrory.

Action

Either move this event type in the "Event Types" directory or manually create a target namespace definition for it.


EDAETE0213 Cannot build editor tree.
Explanation

A unexpected error occurred while building the editor tree.

Action

Make sure the event type schema is correctly defined.


EDAETE0214 Cannot provide children in node tree.
Explanation

Unexpected error while getting the child nodes in a node tree.

Action

Make sure the event type schema is correctly defined.


EDAISE0012 The selected IS Document Type is recursive and its conversion results in a recursive Event Type which is not supported.
Explanation

The IS Document type which has been selected is recursive. After the conversion a recursive Event Type is produced. Recursive Event Types are not supported.

Action

Remove recursion from the IS Document type prior to creating an event type from it.