DEVABEE0000 | The specified location "{0}" does not denote an existing directory. |
Explanation |
A valid event type repository is needed. |
Action |
Check whether the specified location points to a DES event type repository. |
DEVABEE0002 | Could not read content of file "{0}" in order to create zip archive "{1}" |
Explanation |
The file content was not available while creating zip archive. |
Action |
See stacktrace for further explanations and actions. |
DEVABEE0003 | Saving of acdl composite "{0}" failed. |
Explanation |
The writing of the ACDL composite to disk failed. Possible reasons are a wrong location, or missing permissions. |
Action |
See stacktrace for further information. |
DEVABEE0005 | Not a valid repository "{0}". |
Explanation |
The specified folder is not a valid repository folder. |
Action |
Specify a valid repository folder. |
DEVDECOE0040 | Missing configuration location. |
Explanation |
Required parameter for configuration location has not been set. |
Action |
Set an existing configuration location. |
DEVDECOE0041 | Configuration location "{0}" does not exist. |
Explanation |
The configuration location does not exit. |
Action |
Provide an existing configuration location. |
DEVDECOE0042 | Configuration location "{0}" is not an absolute path. |
Explanation |
Configuration loaction is not an absolute path. |
Action |
Provide an absolute path as configuration location. |
DEVDECOE0043 | Configuration location "{0}" is not a directory. |
Explanation |
The configuration location must be a directory. |
Action |
Provide a directory as configuration location. |
DEVDEEE0000 | Storing password for handle {0} failed |
Explanation |
This is a failure of the Passman component. |
Action |
Contact your local support organization. |
DEVDEEE0003 | Failed to calculate passman config location: {0} |
Explanation |
Malformed URL or invalid URI provided. |
Action |
Verify the correct URL / URI location. |
DEVDEGE0001 | Invalid command line parameter |
Explanation |
Invalid syntax of command line parameters and/or options. |
Action |
Make sure that you specify the correct parameters for the command. See provided command line usage output. |
DEVDEGE0002 | No parameters specified |
Explanation |
The event generator command line tool expects to have parameters but no parameters are recognized. |
Action |
Make sure to specify at least one correct parameter for the command. See provided command line usage output. |
DEVDEGE0015 | Not a bytes array value node: {0} |
Explanation |
An event rule of type “Bytes” should contain an array of byte values. |
Action |
Change the value node to a bytes array in the Event Generator json document. |
DEVDEGE0017 | Not a bytes value node: {0} |
Explanation |
An event rule of type "Bytes" should contain byte values. |
Action |
Change the value node to bytes in the Event Generator json document |
DEVDEGE0018 | Not a (textual) time value node: {0} |
Explanation |
An event rule of type "time" should contain a Date and a Duration value. |
Action |
Change the value node a Date in the Event Generator json document. |
DEVDEGE0019 | Not a decimal double value node: {0} |
Explanation |
An event rule of type "float64" should contain a double value. |
Action |
Change the value node to a double value in the Event Generator json document. |
DEVDEGE0020 | Not a (textual) Duration value node: {0} |
Explanation |
An event rule of type "time" should contain a Date and a Duration value. |
Action |
Change the value node to a Duration in the Event Generator json document. |
DEVDEGE0021 | Not a decimal float value node: {0} |
Explanation |
An event rule of type "float32" should contain a decimal float value. |
Action |
Change the value node to a decimal float value in the Event Generator json document. |
DEVDEGE0022 | Not an integer value node;: {0} |
Explanation |
An event rule of type "int32" should contain an integer value. |
Action |
Change the value node to an integer value in the Event Generator json document. |
DEVDEGE0023 | Not a long value node: {0} |
Explanation |
An event rule of type "int64" should contain a long value. |
Action |
Change the value node to a long value in the in the Event Generator json document. |
DEVDEGE0024 | Not a string value node: {0} |
Explanation |
An event rule of type "string" should contain a string value. |
Action |
Change the value node to a string in the in the Event Generator json document. |
DEVDEGE0025 | Event rate rule ''{0}'' not found in eventRates section of json file. |
Explanation |
Event rate rules must be included in the eventRates section of the Event Generator json document. |
Action |
Add the event rate rule to the eventRates section of json document or remove the reference to this rule. |
DEVDEGE0026 | Wrong number of object entries of json node expected: {0} sub node expected, but was {1}. (Json node: {2}) |
Explanation |
The event rate rule json node must have the following format: "<rate rule name>": { "fixed" | "trend" | "variation": <data> }. |
Action |
Make sure that the event rate rule is specified using the correct json format. |
DEVDEGE0028 | Invalid configuration (null) |
Explanation |
Invalid event type configuration passed as argument. |
Action |
Pass a valid event type configuration as argument. |
DEVDEGE0029 | Could not serialize the Event Generator model into file ''{0}'' |
Explanation |
Serialization of the Event Generator configuration failed because of an IOException. This might be caused by an incorrect file path. |
Action |
Make sure the destination folder is correct. |
DEVDEGE0030 | Data rule ''{0}'' not found in rules section of json document.l |
Explanation |
The data rule is missing from the rules section of json document. |
Action |
Add the data rule to rules section of the json document or remove reference to this data rule. |
DEVDEGE0031 | Invalid DES data type specified: ''{0}''; expected DES data type of kind {1} ({2}) |
Explanation |
The data type you specified in the Event Generator json document is not valid. For event rules of type array, map, any, and event, the rule type must match the data type. |
Action |
Specify a data type that matches the event rule. |
DEVDEGE0032 | Event type ''{0}'' not found |
Explanation |
The event type you specify must be available in the Digital Event Services event type repository, located in the <SoftwareAG_Directory>/common/DigitalEventServices/TypeRepository/eventtypes directory. |
Action |
Make sure that the event type name you specify is correct, or add the event type to the Digital Event Services event type repository. |
DEVDEGE0034 | Not an array node: ''{0}'' |
Explanation |
A json array node is expected while deserializing an event rule of type "list". |
Action |
Correct the Event Generator json document to include a json array node. |
DEVDEGE0035 | Invalid rule type name ''{0}'' |
Explanation |
A valid rule type must be specified in the Event Generator json document, to specify a valid data rule. Valid rule type names are: string, boolean, float32, float64, int32, int64, time, map, array, event, etc. |
Action |
Specify a valid rule type name. |
DEVDEGE0036 | Invalid settings type name ''{0}'' |
Explanation |
Settings type name for data rules in the Event Generator json document must be one of the following: fixed, sequencelist, random, variation, increment, simple, complex, eventCreationTime, trend according to the rule type. |
Action |
Specify a valid settings type name. |
DEVDEGE0037 | Invalid DES data type found ''{0}'' |
Explanation |
The Digital Event Services (DES) event field data type could not be parsed successfully. |
Action |
Correct the event field data type according to the valid syntax for field definition in .dx files in the event type repository. |
DEVDEGE0038 | Json object key missing: ''{0}'' expected |
Explanation |
A certain json key string is missing. |
Action |
Add the correct key to the json node. |
DEVDEGE0039 | No event rule and no event type name for event type configuration |
Explanation |
Neither the event type rule nor the event type name have been specified. You must specify at least one of them to reference an event type. |
Action |
Specify a valid event rule or an event type name for the corresponding event type configuration entry in the Event Generator json document. |
DEVDEGE0041 | Missing event type name in case of invalid event rule for {0}.event type configuration |
Explanation |
Invalid entry of the corresponding event type configuration. Either the event type name or the event rule reference must be available to define the event type. |
Action |
Specify a valid event type name or an event rule. |
DEVDEGE0042 | Missing event type name in case of invalid event rate of {0}.event type configuration |
Explanation |
Invalid entry of the corresponding event type configuration.Either the event type name or the event rate reference must be available to define the default event rate name. |
Action |
Specify a valid event type name or an event rate reference. |
DEVDEGE0043 | Invalid event type configurations list (null) |
Explanation |
The event type configuration must be valid. |
Action |
Make sure that the configuration of the event type is correct in the Event Generator json document. |
DEVDEGE0046 | Recursion recognized for nested rule ''{0}'' of rule ''{1}'' (rules stack: ''{2}'') |
Explanation |
Recursive references are not allowed in the Events Generator model . |
Action |
Remove the references that cause the recursion or change the references accordingly. |
DEVDEGE0048 | Value ({0}} less than or equal to 0; expected greater than 0 |
Explanation |
The fixed rate value must be greater than 0. |
Action |
Change value of the rule to be greater than 0. |
DEVDEGE0049 | Invalid object for ''{0}'' (null) |
Explanation |
Object must be valid. |
Action |
Make sure that the field name value is correct. |
DEVDEGE0050 | ''{0}'' value ({1}) must be a positive value (if {2}) |
Explanation |
For increment settings, the delta value must be greater than 0, if the lower value is less than the upper value. |
Action |
Specify a valid value. |
DEVDEGE0051 | ''{0}'' value ({1}) must be a negative value (if {2}) |
Explanation |
For increment settings the delta value must be less than 0, if the lower value is greater than the upper value. |
Action |
Specify a valid value. |
DEVDEGE0054 | ''{0}'' is empty. |
Explanation |
You must specify at least one element in a list for a valid list setting type. |
Action |
Add at least one element to the list settings definition. |
DEVDEGE0056 | ''{0}'' value ({1}) greater than ''{2}'' value ({3}); expected {4} less than {5} |
Explanation |
For random settings type the lower value must be less than the upper value. |
Action |
Correct the lower and upper value that lower < upper. |
DEVDEGE0058 | ''{0}'' value ({1}) less than 0; expected is zero or a positive value. |
Explanation |
The deviation value must be greater than, or equal to 0. The unit of the deviation is the same as the mean value. |
Action |
Correct the deviation value so that it is greater than, or equal to 0. |
DEVDEGE0060 | ''{0}'' value ({1}) less than or equal to 0; expected greater than 0 for a valid event rate. |
Explanation |
The mean value must be greater than 0 in order to get a poitive, non-zero value for the event rate. |
Action |
Correct the mean value so that it is greater than 0. |
DEVDEGE0065 | ''{0}'' event rate value ({1}) is negative; expected a positive value. |
Explanation |
The trend event rate value is an incrementation value and will be added to the variation result for each new calculation. If the trend event rate value is negative, the rate might reach negative values which is not allowed for event rates. |
Action |
Change trend value to a positive value. |
DEVDEGE0067 | Type ''{0}'' of nested rule ''{1}'' does not match the type ''{2}'' of rule ''{3}'' |
Explanation |
The any, array, map, and event data rule types contain references to other nested rules. The DES data type of those rules must match the nested rules accordingly. Therefoer, for type map, array, and event the nested type is relevant: e.g. map<nestedType, nestedType>; nestedType[]. |
Action |
Use a rule that fits in data type. |
DEVDEGE0068 | Reference of rule ''{0}'' from rule ''{1}'' could not be resolved. |
Explanation |
All referenced rule names must be resolvable. This means that all rules that are referenced by name must be defined. |
Action |
Remove the reference a to non-existings rule or create the rule accordingly. |
DEVDEGE0073 | The ''{0}'' field is not a Duration value. |
Explanation |
You have to specify a valid Duration format. |
Action |
Make sure that your value is in a valid Duration format. |
DEVDEGE0082 | Reference of event rule ''{0}'' defined for event type ''{1}'' could not be resolved. |
Explanation |
The referenced rule does not exist, it might have been deleted. |
Action |
If the referenced rule has been deleted, try to recreate it, or consider choosing a different rule. |
DEVDEGE0083 | Type ''{0}'' of nested rule ''{1}'' does not match the event type ''{2}'' |
Explanation |
The selected event rule must be defined for the correct event type. |
Action |
Choose a rule that has been created for the correct event type. |
DEVDEGE0086 | Key rule must not be empty. |
Explanation |
A valid map has valid key and value data. It is possible to speciffy a null value for "value", but not for "key". |
Action |
Select a valid key rule. |
DEVDEGE0088 | Reference of event rate ''{0}'' defined for event type ''{1}'' could not be resolved. |
Explanation |
The referenced rate does not exist, it might have been deleted. |
Action |
If the referenced rate has been deleted, try to recreate it, or consider choosing a different rate. |
DEVDEGE0089 | Not a null value node;: {0} |
Explanation |
Null value expected in json format. |
Action |
Change to expected null value. |
DEVDEGE0090 | Not a null value. |
Explanation |
Null may be stored as a constant. |
Action |
Change data to value. |
DEVDEGE0091 | Invalid event type. |
Explanation |
The event type is used for filtering event rules of that type. |
Action |
Specify a valid event type. |
DEVDEGE0094 | Resource file ''{0}'' could not be read. |
Explanation |
Input/Output problem during accessing of the file resource to be read. |
Action |
Make sure that the resource is not locked by other processes. |
DEVDEGE0095 | Resource file ''{0}'' could not be deserialized. |
Explanation |
The file resource could be read, but it could not be parsed using json parser. It might happen that the file resource could be parsed by json parser, but the deserializer of the Event Generator failed because of a semantic issues. |
Action |
Check the resouce file input for json parsing problems or semantic problems of expected Event Generator format. |
DEVDEGW0052 | ''{0}'' value ({1}) is greater than the difference between the ''{2}'' and ''{3}'' values. |
Explanation |
The difference between lower and upper bounds should be greater than the delta value. Otherwise only the lower and upper value are used. |
Action |
Use the list settings type instead of increment. |
DEVDEGW0053 | ''{0}'' and ''{1}'' value ({2}) have the same value, which will cause no change in the value. |
Explanation |
Lower and upper limits for increment settings should have different values. Otherwise the is no change in the value and the result is a fixed value. |
Action |
Change the lower and upper values to different values. |
DEVDEGW0055 | ''{0}'' contains only one value. |
Explanation |
The values list of a list settings type should have at least one element. You can use the fixed settings type. |
Action |
Consider using the fixed settings type. |
DEVDEGW0057 | ''{0}'' value ({1}) should not be equal to ''{2}'' value ({3}) |
Explanation |
For random settings type the lower and upper value should have different values. |
Action |
Consider using the fixed settings type. |
DEVDEGW0059 | ''{0}'' value should not be zero. |
Explanation |
The deviation value is specified in the same unit as the ''meanValue'' and must be a positive value. In case of deviation = 0, there is no change in value expected and a fixed ''meanValue'' is used. |
Action |
Change the deviation value or consider using the fixed settings type instead. |
DEVDELIE0000 | System property for license file path not specified |
Explanation |
The system property that defines the location of the license file is not specified. |
Action |
Specify the system property. |
DEVDELIE0001 | The specified license file path ''{0}'' does not exist |
Explanation |
The specified license file path does not exist. |
Action |
Specify a valid license file. |
DEVDELIE0002 | Invalid product code. |
Explanation |
The product code is not valid. |
Action |
Provide a valid license. |
DEVDELIE0003 | Invalid product version, expected major version "{0}", but found "{1}" |
Explanation |
The major version in the license does not match the runtime version of the Digital Event Services product. |
Action |
Provide a valid license. |
DEVDELIE0004 | Invalid OSGi installation directory |
Explanation |
The specified value for the OSGi installation directory does not denote a valid directory. |
Action |
This is an internal error. Contact your support organization. |
DEVDELIE0005 | The specified license file path ''{0}'' denotes a directory. |
Explanation |
The location of the Digital Event Services license must point to the license file. |
Action |
Provide the proper license file location. |
DEVDERCE0030 | 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. |
DEVDERCE0039 | The keystore name must not be empty |
Explanation |
Each keystore must have a valid and unique name. The name must be unique in the namespace of all keystores. The keystore 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 keystore. |
DEVDERCE0040 | 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. |
DEVDERCE0042 | 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. |
DEVDERCE0043 | When you select "No" for "Use Local Store&Forward Queue", you can mark only one of the services in the group ''{0}'' as ''Destination''. |
Explanation |
When the value you select for "Use local Store&Forward queue" is "No", the service group must contain only one destination service. |
Action |
Remove the other destination services from the service group. |
DEVDERCE0044 | You cannot select "No" for the "Use Local Store&Forward Queue" option if the service group you are configuring contains a service of type "In-Process". |
Explanation |
Services of type "In-Process" must always act as both a source and a destination service. You cannot use non-queued delivery when the service group contains an In-Process service. |
Action |
Use non-queued delivery for a service group that has a destination service of type Universal Messaging or Digital Event Persistence. |
DEVDERCE0045 | 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. |
DEVDERCE0046 | 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. |
DEVDERCE0047 | 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. |
DEVDERCE0048 | 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 a service before deleting it. |
DEVDERCE0049 | 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. |
DEVDERCE0050 | 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 case character. |
Action |
Specify a valid name for the service. |
DEVDERCE0051 | 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 name, service group name, or the predefined {1}. |
DEVDERCE0052 | 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 case character. |
Action |
Specify a unique name for the service. |
DEVDERCE0053 | Cannot use reserved service name "{0}" |
Explanation |
This is the name of a predefined service. |
Action |
Choose a different service name. |
DEVDERCE0054 | 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. |
DEVDERCE0057 | 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. |
DEVDERCE0059 | 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. |
DEVDERCE0060 | 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". |
DEVDERCE0062 | 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. |
DEVDERCE0063 | 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. |
DEVDERCE0064 | 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. |
DEVDERCE0067 | 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". |
DEVDERCE0068 | 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. |
DEVDERCE0069 | 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. |
DEVDERCE0070 | 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. |
DEVDERCE0079 | 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 case character. |
Action |
Do not use invalid URI characters. |
DEVDERCE0080 | {0} must not be null or an empty string! |
Explanation |
You have entered a null or empty string for a capacity value. |
Action |
Enter a non-empty value for the capacity. |
DEVDERCE0081 | "{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. |
DEVDERCE0082 | Cannot return a valid capacity value because the parameter "defaultCapacityValue" is missing. |
Explanation |
You have specified that the capacity is the default one, but have not provided a default value. |
Action |
Provide a valid default capacity value. |
DEVDERCE0083 | Event Type not found in type repository: {0} |
Explanation |
You are trying to save event type settings in the Digital Event Services (DES) configuration for an event type which is not available in the configured DES event type repository. |
Action |
Add the event type in the DES event type repository. |
DEVDERCE0101 | Cannot configure non-publishable event type: {0} |
Explanation |
Only event types marked as publishabe can have event type settings in the Digital Event Services (DES) configuration. You tried to save event type settings in the DES configuration for a non-publishable event type. |
Action |
Make the event type publishable, or if the event type is nested in another event type, save the event type settings for the parent event type instead. |
DEVDERCE0102 | Duplicate keystore alias {0} |
Explanation |
The keystore alias has to be unique. A keystore with the given alias already exists. |
Action |
Provide a unique keystore alias. |
DEVDERCE0111 | The truststore name must not be "{0}" |
Explanation |
The given truststore name matches the reserved keyword "None". |
Action |
Choose a different truststore name. |
DEVDERCE0112 | The keystore name must not be "{0}" |
Explanation |
The given keystore name matches the reserved keyword "None". |
Action |
Choose a different keystore name. |
DEVDERCE0113 | The value must be one of "SourceOnly", "DestinationOnly", or "SourceAndDestination", but is "{0}". |
Explanation |
The value must be one of "SourceOnly", "DestinationOnly", or "SourceAndDestination". |
Action |
Use either "SourceOnly", "DestinationOnly", or "SourceAndDestination". |
DEVDERCE0114 | Configuration corrupted: missing folder "{0}" |
Explanation |
The Digital Event Services configuration is corrupted, the denoted folder is missing. |
Action |
Please contact your local Software AG support organization. |
DEVDERCE0115 | Configuration corrupted: missing file "{0}" |
Explanation |
The Digital Event Services configuration is corrupted, the denoted file is missing. |
Action |
Please contact your local Software AG support organization. |
DEVDERCW0061 | The predefined "{0}" service will be configured as source&destination |
Explanation |
This predefined service must always be configured as "source and destination". |
Action |
Configure this predefined service as "source and destination". |
DEVDERE0000 | Failed to look-up {0} implementation of type ''{1}''. |
Explanation |
No ServiceProvider implementation for the respective type name has been found. As a result, services of this type cannot be created. Most probably this indicates that the library containing the ServiceProvider implementation is not on the application's classpath. |
Action |
Make sure the library containing the ServiceProvider implementation for the respective type is on the application's classpath. |
DEVDERE0020 | Failed to start a receiving route for event type {0} and subscriber ID {1}. |
Explanation |
A subscriber cannot be created because of an unavailable source service, an invalid durable subscriber ID, or because the durable subscruiber ID is already in use. |
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. |
DEVDERE0100 | Cannot use non-publishable event type for pub-sub operations: {0} |
Explanation |
Only event types marked as publishable can be used to emit events, or to set up a subscription. |
Action |
Choose a publishable event for sending/subscribing. |
DEVDERE0102 | A nonpositive value of ''{0}'' has been specified for 'maxUnacknowledgedEvents' which is not allowed. |
Explanation |
The value of 'maxUnacknowledgedEvents' must be greater than 0. |
Action |
Set a value of 'maxUnacknowledgedEvents' which is greater than 0. |
DEVDERE0107 | Digital Event Services (DES) failed to read the last data event key for subscriber ''{0}'' from file ''{1}''. |
Explanation |
When a subscriber to the In-Process service is created, DES reads the key of the last event sent to a subscriber from a configuration file. If you make changes to this file, DES might fail to read it. |
Action |
Contact Software AG Global Support. |
DEVDERE0120 | Digital Event Services failed to read the {0} from the file system. |
Explanation |
The file may be corrupted. If you change the source service, the inactive durable subscribers are not be deleted from the old source service and might cause memory or storage issues. |
Action |
To fix the issue, delete the durable subscribers file from the file system and manually unsubscribe all inactive subscribers from the old source service. |
DEVDERE0124 | Digital Event Services failed to remove some or all of the inactive subscriptions for event type ''{0}'' from source service {1}. |
Explanation |
The source service is misconfigured or unreachable and Digital Event Services is not able to remove the inactive subscriptions from the service. If new events are sent to this service, the events are unnecessarily stored for the remaining subscriptions and may cause out of memory or out of disk space errors if the number of events becomes too big. |
Action |
Manually remove the remaining subscriptions from the source service using the appropriate tooling. |
DEVDERUE0041 | The event type name "{0}" could not be decomposed, probably the event sender did not use the correct protocol. |
Explanation |
When receiving an event the accompagnying type name has to follow a certain pattern , so that it can be decomposed into parts. This pattern changed between Digital Event Services 9.12 and 10.0, which means senders and receivers across these versions cannot talk to each other. |
Action |
Make sure all senders and receivers are either of version 9.12, or they are all of version 10.0 or greater. |
DEVDERUE0043 | Failed to unsubscribe subscriber "{0}" for event type "{1}" from the Universal Messaging server, because the session is not connected. |
Explanation |
Digital Event Services (DES) failed to delete the durable associated with the subscriber from the Universal Messaging server, because DES is currently not connected to the Universal Mesaaging server. |
Action |
When the Universal Messaging server becomes available, to avoid high number of events being stored for the durable of the subscriber, delete the durable manually. |
DEVDESCE0000 | Internal error: the given "RuntimeComponent" parameter is not an instance of the "Instance" interface |
Explanation |
This is an internal error. |
Action |
Contact Software AG Global Support. |
DEVDESCE0001 | 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. |
DEVDESCE0002 | 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. |
DEVDESCE0005 | It is not possible to change storage location, while instance {0} is running |
Explanation |
Please ensure that the component using Digital Event Services is restarted in order to start using the new storage location. |
Action |
Changing the storage location requires a restart of the components using Digital Event Services. |
DEVDESCE0007 | "{0}" is not a valid number |
Explanation |
The value to be configured needs to be a number. |
Action |
Provide a valid number. |
DEVDESCE0008 | It is not allowed to create new instances of Event Types Configuration |
Explanation |
Only one built-in instance of Event Types Configuration exists. |
Action |
In order to apply your changes, edit the built-in instance of Event Types Configuration. |
DEVDESCE0009 | It is not allowed to delete the instance of Event Types Configuration |
Explanation |
There is only one built-in instance of Event Types Configuration, which must not be deleted. |
Action |
In order to apply changes, edit the built-in instance of Event Types Configuration. |
DEVDESCE0010 | Configured service group ''{0}'' does not exist |
Explanation |
Event types can only be assigned to existing service groups. |
Action |
Create the service group before assigning an event type, or choose a different service group. |
DEVDESCE0011 | Unknown reliability string "{0}" as configured value string e.g. on UI |
Explanation |
The string of the reliability value is unknown to the system and cannot be assigned to an internal definition. This is an internal error and should never occur. |
Action |
Contact Software AG Global Support. |
DEVDESCE0012 | Invalid EventTypeReliability value "{0}" |
Explanation |
Invalid EventTypeReliability value used for conversion into string for output on UI e.g. This is an internal error and should not occur. |
Action |
Contact Software AG Global Support. |
DEVDESCE0013 | Invalid EventType Delivery Mode Preference value "{0}" |
Explanation |
Invalid EventType Delivery Mode Preference value used for conversion into string for output on UI e.g. This is an internal error and should not occur. |
Action |
Contact Software AG Global Support. |
DEVDESCI0006 | The storage content is not automatically copied from {0} to the new destination {1}. |
Explanation |
Before starting Digital Event Services the new storage location should be prepared by copying the necessary folder and files. Events may be lost if the storage is not available at runtime. |
Action |
Copy the storage from the old path into the new specified path before starting Digital Event Services. |
DEVDESCI0021 | com.softwareag.event.routing.configuration bundle started. |
Explanation |
The Digital Event Services (DES) configuration bundle for Command Central is started. |
Action |
(No action required) |
DEVDESCI0022 | com.softwareag.event.routing.configuration bundle stopped. |
Explanation |
The Digital Event Services (DES) configuration bundle for Command Central is stopped. |
Action |
(No action required) |
DEVDESCW0003 | It is not possible to check whether product to be configured is online. The configuration modification will take effect only after the next restart of the product. |
Explanation |
The status of Digital Event Services cannot be checked using SPM tools. Please ensure that the component using Digital Event Services is restarted to use the new storage location. |
Action |
Changing the storage location requires a restart of the product which is using Digital Event Services. |
DEVDESCW0004 | Restart "{0}" to use the storage location "{1}" |
Explanation |
The running instance must be restarted to use the new storage location. SPM must be active to change the storage location. |
Action |
Restart SPM, otherwise the old location will be used. |
DEVDRE0000 | Annotation type "{0}" contains duplicate field name "{1}" |
Explanation |
Annotation type definitions must not contain duplicate field names. |
Action |
Correct the annotation type definition. |
DEVDRE0001 | System property "{0}" not set. |
Explanation |
Digital Events Repositories location is defined by a system property. |
Action |
Define the system property. |
DEVDRE0002 | Repositories location "{0}" is not a directory. |
Explanation |
The repositories location must be a directory. |
Action |
Define a directory as a repository location. |
DEVDRE0003 | Double field name "{0}" found. |
Explanation |
Event type fields with the same name are not allowed within one event type definition. E.g.\nF1 : string;F1 : boolean; <-- duplicate field name - must be renamed or deleted. |
Action |
Rename or delete the corresponding field. |
DEVDRE0007 | Annotation type "{0}" not found in repository. |
Explanation |
Each annotation specified inside the event type definition must be defined in the annotation type repository of the installation. Predefined annotation is e.g. "@Unique". |
Action |
Use only these annotations which are defined inside the annotation type repository of the installation. |
DEVDRE0008 | Field names of annotation type "{0}" must be specified explicitly. |
Explanation |
If more than one annotation field is defined for a certain annotation type you have to specify <key>="<value>" pairs in the annotation's parameter list. E.g.\n@multifield_annotation(field1="value1", field2="value2")\n\nThe number of specified parameters is arbitrary:\n@multifield_annotationOnly\n\nin case of one single defined annotation field you can specify only the "<value>" without the <key>= in front of it. E.g.\n@singlefield_annotation("value") |
Action |
Specify <key>="<value>" pairs as annotation parameter list instead of just "<value>". E.g.\n@multifield_annotation(field1="value1", field2="value2") |
DEVDRE0009 | No field names defined for annotation type "{0}". |
Explanation |
If there is no annotation field defined for a certain annotation type then it is not allowed to specifiy any <key>="<value>" pair as parameter of the annotation. |
Action |
Remove the whole parameter list of the annotation. Only the annotation name may be specified e.g. "@Unique". |
DEVDRE0011 | No annotation field "{0}" allowed because no fields defined for annotation type "{1}". |
Explanation |
There is at least one annotation field specified in the annotation's parameter list. But because no field is defined it is not allowed to specify any annotation field. |
Action |
Remove the whole parameter list as no annotation field is defined for the annotation type e.g. "@Unique". |
DEVDRE0012 | Annotation field "{0}" not defined for annotation type "{1}". |
Explanation |
The specified annotation field is invaild because it is not defined for the corresponding annotation type. |
Action |
Specify the correct annotation field name in the annotation parameter list. E.g. correct the <key> inside of @annotation(<key>="<value>") |
DEVDRE0013 | Value "{0}" cannot be converted into annotation field type "{1}". |
Explanation |
A certain annotation field type is assigned to each annotation field. The value is specified as string but it must be convertible into the corresponding annotation field type. The annotation field types are defined for each annotation field definition of a certain annotation type.\nValid types:\nSTRING: any string (corresponds to java "String" type)\nINT64: 64 bit integer value (corresponds to java "Long" type)\nFLOAT64: 64 bit floating point value (corresponds to java "Double" type)\nBOOLEAN: boolean value (corresponds to java "Boolean" type) |
Action |
Specify a correct value according to the correct annotation field type. |
DEVDRE0015 | Event Type "{0}" is not unique. |
Explanation |
Trying to access an event type as unique, that is not unique. |
Action |
Don't acess a non unique event type with methods for unique types. |
DEVDRE0016 | Event Type "{0}" is unique, but contains more than one entry in repository. |
Explanation |
There is more than one file for an unique Event Type in the repository. |
Action |
The repository must be repaired to contain only one variant of the unique Event Type. |
DEVDRE0017 | Inconsistent file name: variant key "{0}" does not match filename "{1}" |
Explanation |
The variant key, as computed based on the contents of the type definition file, does not match the type definition file name. Probably, the type definition file was manipulated directly with a text editor. |
Action |
Fix the type definition file. |
DEVDRE0018 | Inconsistent file name: event type name "{0}" does not match filename "{1}" |
Explanation |
The event type name, as extracted from the contents of the type definition file, does not match the type definition file name. Probably, the type definition file was manipulated directly with a text editor. |
Action |
Fix the type definition file. |
DEVDRE0019 | Inconsistent file name: Annotation type name "{0}" does not match filename "{1}" |
Explanation |
The annotation type name, as extracted from the contents of the type definition file, does not match the type definition file name. Probably, the type definition file was manipulated directly with a text editor. |
Action |
Fix the type definition file. |
DEVDRE0022 | Cannot change "unique" for {0} due to broken reference of an embedded type. |
Explanation |
"unique" cannot be changed, if the event type is referenced by another event type. |
Action |
Insert a new variant for the referenced type, change or delete the referenced types. |
DEVDRE0024 | Event type info does not match for "{0}" |
Explanation |
The event type info of the type being inserted does not match the existing event type info in the repository. |
Action |
Correct the event type info. |
DEVDRE0036 | Type name to be inserted ({0}) conflicts with existing type ({1}) |
Explanation |
The name of any type in the repository must not be the prefix of another type name. For example, "com.company" and "com.company.type" are not allowed. |
Action |
Supply a non-conflicting type name. |
DEVDRE0044 | "{0}" with variant "{1}" is used in "{2}" with variant "{3}" and can't be removed. |
Explanation |
It is not possible to remove an event type that is embedded. |
Action |
First remove the parent event type and then you can remove the embedded event type. You can also use removeForced, if you can accept a broken repository. |
DEVDTE0000 | Field name "{0}" has wrong format |
Explanation |
The field name must follow this pattern: "[a-zA-Z_][a-zA-Z0-9_]*". |
Action |
Provide a valid field name. |
DEVDTE0001 | A field definition requires a name |
Explanation |
Each field definition has to have a name. |
Action |
Provide a name for the field definition. |
DEVDTE0002 | A field definition requires a type |
Explanation |
Each field definition has to have a type. |
Action |
Provide a type for the field definition. |
DEVDTE0004 | Invalid field annotation |
Explanation |
For field definitions, only field-applicable annotations may be specified. |
Action |
Provide a valid field annotation. |
DEVDTE0005 | Type name "{0}" has wrong format |
Explanation |
The event type name must follow this pattern: "[a-zA-Z_][a-zA-Z0-9_]*(\.[a-zA-Z_][a-zA-Z0-9_]*)*". |
Action |
Provide a valid event type name. |
DEVDTE0006 | Invalid event annotation |
Explanation |
For event types, only event-applicable annotations may be specified. |
Action |
Provide a valid event annotation. |
DEVDTE0007 | Field name ''{0}'' is not defined in annotation type ''{1}''. |
Explanation |
The field name is not defined in the corresponding annotation type. |
Action |
Use a differnet field name or define the field name in annotation type. |
DEVDTE0008 | Field type for field ''{0}'' is ''{1}'' not matching ''{2}''. |
Explanation |
The defined field type does not match the Java type used for an annotation value. |
Action |
Use a matching Java type. |
DEVDTE0009 | Field type for field ''{0}'' is ''{1}'' is not matching any allowed field value. |
Explanation |
AnnotationTypeDefinition only allows certain field types. |
Action |
Use a type which is allowed. |
DEVDTE0010 | Duplicate annotation "{0}" |
Explanation |
The same annotation can be applied multiple times only if the corresponding annotation type is marked as repeatable. |
Action |
Provide a valid annotation. |
DEVDTE0011 | Java object not supported for any: "{0}" |
Explanation |
Only Java objects that are supported by the Digital Event Services type system should be provided. |
Action |
Provide a Java instance of a supported type for an any-defined field. |
DEVDTE0012 | Missing annotation type name. |
Explanation |
No annotation type name was provided for the building of an annotation type. |
Action |
Set a name for the annotation type on the annotation type builder. |
DEVDTE0013 | Recursive reference to "{0}" not allowed |
Explanation |
Digital Event Types do not allow recursive type references, neither dirctly, nor indirectly. |
Action |
Provide a valid type reference. |
DEVDTE0014 | An array must not contain another array. |
Explanation |
It is not possible to define an array of arrays. |
Action |
An array is specified by explicitly defining the dimension. |
DEVDTE0017 | The array dimension has to be a positive integer. |
Explanation |
Array dimensions have to be positive integers. For example, specify dimension = 2 in order to construct a string[][]. |
Action |
Provide a valid dimension. |
DEVDTE0019 | Field "{0}" is not defined for type "{1}". |
Explanation |
The type for the event does not contain the field.The type does not contain the field. |
Action |
Set or get a field that is defined for the type of the event. |
DEVDTE0020 | Field "{0}" in event type "{1}" has field type "{2}" in event type variant "{3}", and field type "{4}" in event type variant "{5}". |
Explanation |
The field types for a field are not matching. |
Action |
Consider using another event type variant for accessing the event. |
DEVDTE0021 | The reserved package name "{0}" must not be used |
Explanation |
The Digital Event Services system uses the reserved package name for internal purposes. |
Action |
Provide a valid package name. |
DEVDTE0022 | Transmission event type "{0}" and subscribing event type "{1}" must be the same. |
Explanation |
The event type used for transmission is different from the one that has been subscribed for. |
Action |
Contact Software AG support. |
DEVDTE0024 | The path for the ''{0}'' annotation ''{1}'' does not match any field definition. |
Explanation |
The paths for the annotations like "EventTime" and "EventId" must point to an existing field. |
Action |
Correct the path value of the annotation. |
DEVDTE0025 | The field corresponding to event time path ''{0}'' is not a time field. |
Explanation |
The event time path must point to an existing time field. |
Action |
Correct the path value of the EventTime annotation. |
DEVDTE0028 | Field "{0}" of event type "{1}" contains an unresolved reference to event type "{2}". |
Explanation |
This should not happen because only valid event type models are stored to the repository. However, the referenced type is no longer available in the repository in the case that it has been deleted from it. |
Action |
Correct the invalid event type or add the referenced event type to the repository. |
DEVDTE0030 | The unique event type ''{0}'' has different variants. |
Explanation |
A unique event type should only exist in one variant. |
Action |
Use only one variant of a unique event type. |
DEVDTE0031 | Variants of Event Type ''{0}'' differ in "unique" setting. |
Explanation |
If an event type is "unique", there cannot exist another variant of the same event type which is not "unique". |
Action |
Define an event type as "unique" or use it with variants. |
DEVDTE0032 | The type name "{0}" does not have a package |
Explanation |
Each event type name needs to be qualified with a package. |
Action |
Provide a valid type name. |
DEVDTE0033 | The event type "{0}" and the nested event type "{1}" should have the same uniqueness setting |
Explanation |
If an event type is marked as "unique", it can only refer to other "unique" event types. Vice versa, a "non-unique" event type can only refer to other "non-unique" event types. |
Action |
Correct the uniqueness setting. |
DEVDTE0035 | Cannot access the field "{0}" of unknown type "{1}" in event type "{2}" |
Explanation |
The data type of the field is not known to the current runtime, therefore the field value cannot be accessed. |
Action |
Specify a field with a known data type. |
DEVDTE0049 | No variant key allowed for unique referenced event type "{0}". |
Explanation |
In case of a uniquely defined event type, variant keys must not be specified in an event type reference:\nInvalid field definition: "F1 : event : package.unique_eventtype("<variant key>");"\nCorrect field definition: "F1 : event : package.unique_eventtype;"\n\n(* Uniquely defined event types contain a @Unique" annotation on event level.)\n(* The variant key is a hexadecimal 16-digit value, which is automatically added to the file name in the repository.) |
Action |
Remove the variant key and just specify the fully qualified event type name:F1 : event : package.unique_eventtype; |
DEVDTE0050 | Variant key necessary for non-unique referenced event type "{0}". |
Explanation |
In case of a non-uniquely defined event type, a variant key must be specified in an event type reference.\nInvalid field definition: "F1 : event : package.nonunique_eventtype;"\nCorrect field definition: "F1 : event : package.nonunique_eventtype("<variant key>");"\n\n(* Non-uniquely defined event types don't contain a "@Unique" annotation on event level.)\n(* The <variant key> is a hexadecimal 16-digit value, which is automatically added to the file name in the repository.) |
Action |
Add the variant key behind the fully qualified event type name:\n"F1 : event : package.nonunique_eventtype("<variant key>");" |
DEVDTE0051 | Unknown type found: {0} |
Explanation |
The any field contains an unknown type or type id, that cannot be read. Maybe the event has been created in a later product version. |
Action |
This is an internal error. Please contact your support organization. |
DEVDTE0052 | Event type "{0}" cannot be resolved. |
Explanation |
The event type cannot be resolved. |
Action |
Deploy the missing event type to the repository. |
DEVDTE0053 | Event type "{0}" not sufficient for building Protobuf descriptor. |
Explanation |
A required event type cannot be read from the repository. |
Action |
Deploy the missing event type to the repository. |
DEVDTI0015 | Annotation field name "{0}" has wrong format. |
Explanation |
The annotation field name must follow this pattern: "[a-zA-Z_][a-zA-Z0-9_]*". |
Action |
Provide a valid annotation field name. |
DEVDTI0016 | Annotation type name "{0}" has wrong format. |
Explanation |
The annotation type name must follow this pattern: "[a-zA-Z_][a-zA-Z0-9_]*(\.[a-zA-Z_][a-zA-Z0-9_]*)*". |
Action |
Provide a valid annotation type name. |