Event-Driven Architecture Tools Messages

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.

Specify a valid and unique name for the service group.

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.

Specify a unique service group name.

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.

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

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.

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

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.

Do not delete the "Default" service group.

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.

Do not rename the "Default" service group.

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

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

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

Use only unique services within a service group.

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

Assign at least one service to the service group.

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

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

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

Mark only one service as "source".

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

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

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

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

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.

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

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.

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

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.

Specify a valid name for the service.

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.

Specify a unique name for the service.

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

Remove all references to the service before deleting it.

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

Do not use invalid URI characters.

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

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

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

Remove the event type from the Service Group Event Types.

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

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

The specified service group does not exist.

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

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

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.

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

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.

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.

Provide a valid capacity.

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

Configure the service as "source and destination".

This is the name of a predefined service.

Choose a different service name.

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

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

The path is not an existing directory.

Make sure that the specified directory exists.

The path must be specified as an absolute path.

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

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

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

Only one built-in instance of Runtime Configuration exists.

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

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.

Use a valid service name following the naming rules.

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

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

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

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

This is an internal error.

Contact your support organization.

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

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

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

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

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.

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

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

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.

The content is not correct.

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

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

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.

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

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

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.

Delete the service jar file manually if desired.

The factory was not able to create an event parser.

Check the log for exception stacktrace.

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.

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

Union and List are not supported for restrictions.

Please contact your software supplier.

The called restriction facet is not supported.

Please contact your software supplier.

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

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

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

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

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

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

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

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

A unexpected error occurred while building the editor tree.

Make sure the event type schema is correctly defined.

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

Make sure the event type schema is correctly defined.

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.

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

Failed to parse date string.

Check the format of the supplied data.

Failed to not parse date string.

Check the format of the supplied data.

Required property is not of required type.

Check the format of the supplied data.

Specified value for a property is not of type long.

Check whether the specified property is of the required type.

The specified guaranteed delivery level in your NERV configuration file is not of the supported ones.

Go to the NERV configuration file and specify one of the valid values: NORMAL, HIGH, MAXIMUM_STRONG, MAXIMUM_EVENTUAL, SHARED for the com.softwareag.eda.nerv.guaranteed.delivery.level property.

Failed to create JNDI entry.

Check your JMS provider configuration.

Failed to create JNDI entry.

Check your JMS provider configuration.

Failed to create topic on the JMS Provider.

Check your JMS provider configuration.

Failed to create topic on the JMS provider.

Check your JMS provider configuration.

The JNDI settings of your NERV component configuration are not correct.

Check the JNDI settings of your NERV component configuration.

During emit and subscribe operations NERV creates the repsective topics on the JMS provider if they are missing.

Check your JMS provider and NERV configuration.

Failed to bind topic.

Check your JMS provider configuration.

Failed to create topic.

Check your JMS provider configuration.

Failed to process the JMS provider URL.

Check your NERV configuration.

No connection factory has been found. This might be due to the unavailability of the NERV destination support service or the failure of the factory creation. This service is available only for webMethods Broker and Universal Messaging components.

Check your NERV configuration and make sure Universal Messaging or Broker are configured and running.

During initialization NERV tries to create and bind a connection factory for the specified JMS provider if such does not exist.

Please make sure the specified provider URL denotes a running webMethods Broker instance.

During emit and subscribe operations NERV creates the repsective topics on the JMS provider if they are missing.

Check your JMS provider and NERV configuration.

The JmsSupport utility does not support the specified JMS provider.

Please specify a provider URL denoting a JMS provider of type Universal Messaging or Broker.

The passed argument is not a date.

Check whether the passed argument is of the required type.

Unsupported JMS provider.

Check documentation for the list of supported JMS providers.

This property is used for creating a connection factory that clients can look up remotely.

To use NERV to connect remotely to a JMS provider, you must change the value of the JMS provider URL property to the actual hostname of the JMS server.

Failed to propagate NERV properties change to NERV errorhandler because the JMX helper is not initialized.

Check that NERV is properly initialized.

Failed to handle route changed notification or unrecognized notification type.

Check that NERV is properly initialized.

NERV could not close JMS connection factory successfully.

Close JMS connection factory.

Failed to register Destination Support Service

Make sure that NERV is properly configured.

Failed to propagate NERV properties change to NERV component updater because it is not available.

Check the log files for errors during Component Updater initialization.

Failed to propagate NERV properties change to NERV errorhandler updater because it is not available.

Check the log files for errors during Error Handler initialization.

Failed to restart file watcher for NERV deployment directory.

Check that NERV is properly configured.

Failed to update NERV Default JMS component Event Consumer Service.

Make sure that NERV is properly configured.

Failed to update NERV Default JMS component Event Emitter Service.

Make sure that NERV is properly configured.

Failed to configure NERV Default Component via properties because com.softwareag.eda.nerv.default.jms.provider property is missing or has an empty value.

Make sure that NERV is properly configured.

Unsubscribe failed for endpoint. No such subscription found.

Check endpointURI.

Failed to find any NERV errohandler Services.

Check that NERV error handling is properly configured.

Failed to configure NERV errorhandlers.

Check that NERV error handling is properly configured.

Failed to obtain pub/sub ''toEndpoint'' for specified url.

Check that NERV Components are properly configured.

Failed to set tracing for object name to value.

Check that NERV Components are properly configured.

Failed to find existing in-memory endpoint object name for the specified url.

Check that NERV Components are properly configured.

Failed to resolve specified component. NERVSingleton.loadAssets() method has to be invoked prior to obtaining EventEmitter or EventConsumer references.

Make sure NERVSingleton.loadAssets() has been invoked before obtaining Consumer/Emitter references.

Failed to resolve the specified component. No such bean is loaded by NERV.

Check NERV configuration.

Failed to resolve specified component. The bean exists, but it is not a NERV component.

Check that the bean is a NERV component.

The event type is not specified in the event headers.

Message headers map should contain an "$Event$Type" entry.

No Event Type Store has been set.

Check that the Event Type Store location is configured properly.

The event type is not specified in the event headers.

Message headers map should contain an "$Event$Type" entry.

No OSGi bundle context is set. The bundle has not been initialized correctly.

Restart bundle/OSGi/Product instance.

Failed to resolve specified component. Possible cause: the JMS provider is unreachable due to incorrectly set address in the NERV component configuration properties file or due to the JMS provider being down.

Check NERV Component configuration. Check if the JMS provider is running and reachable.

Failed to resolve the specified component.

Check NERV Component configuration.

Failed to create NERV default component: NERVDefaultJms unknown JMS provider.

Check the value of the com.softwareag.eda.nerv.default.jms.provider property in the NERV configuration file.

No OSGi bundle context is set. The bundle has not been initialized correctly.

Restart bundle/OSGi/Product instance.

Failed to get NERV default component status.

Check that NERV is properly configured.

Failed to subscribe to an empty endpoint URI.

Check that endpointURI is not null or empty.

Failed to subscribe to the specified endpoint URI.

Check that the endpointURI is valid.

When making a subscription, the provided Processor must not be null.

Make sure the processor is not null.

When making a subscription, the list of the End-Points must containt at least one entry.

Check endpointURIs.

When unsubscribing, the provided Processor must not be null.

Make sure the processor is not null.

No route with the specified id is found while trying to stop!

Make sure the route ID is correct.

The event type is not specified in the event headers.

Message headers map should contain a valid "$Event$Type" entry.

Message should not be null or empty.

Make sure the message is not null or empty.

Message should not be null and at least one endpoint should be specified.

Check that the message is not null or empty and that the endpointURIs is not null or empty.

The "$Event$EventID" entry is not specified in the headers of the event.

Message headers map should contain an "$Event$EventID" entry.

Failed to set "$Event$Start" header.

Expect events with a missing start header.

Error while emitting event to endpoint.

Check the log file for more details.

Error while emitting event to endpoint.

Check the log file for more details.

Error while emitting event to endpoint.

Check the log file for more details.

Failed to create default routing.

Check the log file for more details.

No ErrorHandlerBuilder instance has been provided during Event Emitter instantiation.

Check that a service/bean of type ErrorHandlerBuilder is exposed/registered by NERV.

Failed to remove default route for endpoint.

Check the log file for more details.

No Component Resolver instance has been provided during Event Emitter instantiation.

Check that a service/bean of type ComponentResolver is exposed/registered by NERV.

EDAEventTypeID must not be null.

When making a subscription, check that eventTypeID is not null.

No route with specified id found while trying to stop.

Check the log file for more details.

Message should not be null.

Check that the message is not null.

Message should not be null.

Check that the message is not null.

Event type is missing from the provided event envelope. It should be specified under the /Event/Header/Type element of the XML string. The following tag should exist <Type>...</Type>.

Check that the eventContent matches the specified pattern.

Could not find body element in the specified string.

Check that eventAsXMLString matches the specified pattern.

Event type is either missing or has incorrect format.

Check that eventType is not null or empty or invalid.

Event helper is null. It must be set prior to using it.

Message Creator service is not configured properly. Check the NERV configuration.

Event type store has not been set. Please make sure a valid reference to the Event Type Store is provided during Message Creator instantiation.

Check that the Event Type Store location is configured properly.

Failed to marshal event.

Check the log file for more details.

Event type is either missing or has an incorrect format.

Message headers map should contain an "$Event$Type" entry.

Event should not be null or empty.

Check that eventAsXMLString is not null or empty.

Failed to extract headers and filterable properties from the spefied event.

Check the log file for more details.

Invalid headers.

Check that the headers are not null or empty.

Invalid headers.

Check that the headers are not null or empty.

Invalid body.

Check that the body is not null or empty.

An error has occurred while trying to provide an XSD parser instance.

Please review the exception stacktrace for detailed explanation of the failure.

The default Event Type Store bean has not been found.

Please make sure that you have specified a correct Event Type Store location in the NERV configuration file.

Error while emitting event to endpoint.

Check the log file for more details.

No configuration XML file with name equal to the selected guaranteed level is found at the specfiied configuration directory.

Make sure that a file with name equal to the specified guaranteed mode exists in the configuration directory.

No Event Emitter instance has been provided during Event Consumer instantiation.

Check that a service/bean of type Event Emitter is exposed/registered by NERV.

During initialization NERV flushes all cached events.

Check the exception stacktrace in the log file for more details. Restarting NERV would trigger another flush attempt.

Look-up of bindings from the JNDI context at the specified server failed.

Make sure that the messaging provider denoted by the provider URL property is up and running. Check the log file for any preceding error logs that might be related to this issue.

A connection created with this connection factory could not be initialized.

Check the log file for any preceding error logs that might be related to this issue.

EventEmitter.emit() was called from the init() or start() method of a custom route bundle loaded by NERV.

If a custom route bundle needs to emit an event from its init() or start() method, it has to do it in a separate thread in order to avoid a deadlock.

Failed to propagate NERV properties change to NERV text encryptor because it is not available.

Check the log files for errors during text encryptor initialization.

Specified directory does not exist.

Make sure that "com.softwareag.eda.nerv.dead.letter.channel.uri" property denotes a directory.

Failed to initialize NERV JMX helper.

Check log file for more details.

Failed to configure NERV Default Error Handler with the specified configuration properties.

Check that NERV error handling is properly configured.

Failed to add event headers to message body.

Check log file for more details.

Failed to process NERV Default Component change.

Check log file for more details.

Failed to configure NERV Default Component with the specified configuration properties.

Check NERV configuration.

Failed to configure NERV Default Component with the specified configuration properties.

Check NERV configuration.

Failed to update NERV Default Component.

Check NERV configuration and log file for more details.

Failed to register Destination Support service because the specified NERV component does not configure a webMethods Broker or Universal Messaging connection.

If you are configuring a Broker or Universal Messaging connection, double check that the configuration is correct. Otherwise ignore this message.

NERVService Listener has not been properly initialized. Failed to process a bundle lifecycle change because no bundle component updater has been set.

Restart bundle/OSGi/Product instance.

NERV component is not properly configured.

Shutting down all routes consuming from specified component. In order to restart the routes, please provide a valid configuration and restart your consume bundles or restart the whole OSGi instance.

Failed to load NERV assets from NERV asset folder.

Check nervAssetFolder and log file more details.

Failed to configure NERV text encryptor with the specified configuration properties.

Check that the NERV security file location is properly configured.

Failed to write the route bundle to an output stream.

Check the error log for exception details.

The replaceable value could not be encrypted.

Check if the NervTextEncryptor instance passed to the NervRouteBundle object has been correctly initialized.

NervTextEncryptor is not set.

Before writing the bundle, invoke NervRouteBundle.setTextEncryptor() and pass a properly initialized NervTextEncryptor.

The supported Event Persistence types are hdfs and jdbc.

Please specify either hdfs or jdbc as a type.

A mandatory Event Persistence endpoint configuration property has not been set.

Set all mandatory configuration properties to the Event Persistence endpoint before adding it to a route.

The to() or camel() method invocation is not allowed on a route which has not been initialized with from() invocation first.

Prior to calling the to() or camel() methods on a NervRoute, infoke the from() method first.

The specified user package import entry contains an empty argument or directive - for example: package;;version=["1.0,2.0).

Make sure the user package import entry does not contain any empty arguments or directives before adding it to the bundle manifest.

A user-added package import entry must contain at least one import and can have optional arguments and directives.

Make sure the user import package entry you want to add to the bundle manifest contains one or more semicolon-separated packages.

The NERV route bundle factory could not be created.

Please check the log.

Failed to write the route bundle to a directory.

Check the error log for exception details.

The specified path does not denote a directory where the bundle can be persisted.

Please specify a valid directory path.

Failed to delete the files found in the output directory.

Please make sure that any access permissions for the file systems are properly configured.

Failed to create a directory in which to persist the route bundle.

Please make sure that access permissions for the file systems are properly configured.

Failed to create a directory while persisting the route bundle.

Please make sure that access permissions forr the file system are properly configured.