A message ID consists of 10 alphanumeric characters that uniquely identify the message. The message ID is composed of:
| ID | Description |
|---|---|
| GBRXC0100E | Unsupported persistence type "{0}". Only FILE and DB are supported. |
| GBRXC0101E | Initialization failed |
| GBRXC0102E | The automatic creation of the database failed: {0}. |
| GBRXC0103E | RuleApp "{0}" was not found. |
| GBRXC0104E | The initialization of the persistence layer failed. |
| GBRXC0105E | The initialization of the management layer failed. |
| GBRXC0106E | The initialization of MBeans failed. |
| GBRXC0107E | The initialization of the model failed. |
| GBRXC0108E | Error on execution unit (XU): "{0} - {1}". |
| GBRXC0110E | The Res console logger configuration file was not found in WEB-INF/classes: "{0}". |
| GBRXC0111E | Batch service error. |
| GBRXC0113E | An error occurred when the decision service "{0}" was removed. See the log file for more information. |
| GBRXC0114E | The persistence check failed: {0}. |
| GBRXC0115E | The persistence check failed. Diagnostic report: {0}. |
| GBRXC0116E | Access denied. The user "{0}" is not in any of the following roles: "{1}". |
| GBRXC0117E | Cannot find the ruleset that corresponds to the query "{0}" containing ''{1}''. |
| GBRXC0118E | Initialized default trace factory: {0} |
| GBRXC0119E | The initialization of the trace DAO factory failed. |
| GBRXC0120E | It was not possible to reinitialize the trace DAO configuration with this init parameter: {0} |
| GBRXC0121E | It was not possible to initialize the trace DAO configuration: {0} |
| GBRXC0123E | Could not get information from the XOM DAO. |
| GBRXC0124E | An invalid port is specified for the broker server. The port must be a number. |
| GBRXC0125E | Resource "{0}" not found. |
| GBRXC0126E | A resource with the same name and content (identical checksum) already exists in the repository. |
| GBRXC0127E | A library with the same name and version already exists in the repository. |
| GBRXC0128E | The selected file type is not allowed. Select a JAR or compressed file. |
| GBRXC0129E | This URL is already referenced by this library. |
| GBRXC0130E | This item is already referenced. |
| GBRXC0131E | Timeout expired while the execution unit {0} is contacted to run a test. |
| GBRXC0132W | This XU uses a different persistence type ({0}) than the Rule Execution Server console ({1}). |
| GBRXC0133W | This XU uses a different XOM persistence type ({0}) than the Rule Execution Server console ({1}). |
| GBRXC0134W | Invalid value {0} for property {1} in the deployment descriptor. This value should be an integer. The default value {2} is used instead. |
| GBRXC0135I | Properties used for initialization: {0} |
| GBRXC0136I | The initialization was successful. {0} RuleApps are available in the RES repository. |
| GBRXC0137I | Logging started. Rule Execution Server console version: {0} |
| GBRXC0138I | Unregister MBeans before stopping the application. |
| GBRXC0139I | Connection to the Rule Execution Server Console from "{0}". |
| GBRXC0140I | Rule Execution Server console log file: {0} |
| GBRXC0143I | Using the following configuration parameters: {0} |
| GBRXC0144I | The trace DAO factory was initialized: {0} |
| GBRXC0146I | XOM resource added: "{0}" |
| GBRXC0147I | XOM library added: "{0}" |
| GBRXC0148I | XOM resource removed: "{0}" |
| GBRXC0149I | XOM library removed: "{0}" |
| GBRXC0150I | ... and {0} more log messages |
| GBRXC0151I | Persistence type: {0} |
| GBRXC0152I | Persistence properties: {0} |
| GBRXC0153I | Execution unit location: {0} |
| GBRXC0154I | Reading Decision Warehouse configurations from web.xml |
| GBRXC0155I | The Decision Warehouse configuration {0} was loaded. |
| GBRXC0156E | An error occurred. See the exception message for details. {0} |
| GBRXC0157E | The logger configuration file cannot be read. |
| GBRXC0158E | The property "{0}" cannot be found in the web.xml file. |
| GBRXC0159E | The Rule Execution Server console logging system could not be initialized properly: the security manager exists and the logging permission is not correct. |
| GBRXC0160E | An error occurred while the schema was uploaded. |
| GBRXC0161E | An error occurred while the trace schema was uploaded. |
| GBRXC0162E | An error occurred while the ruleset archive was parsed. |
| GBRXC0163E | An error occurred during upload. |
| GBRXC0164E | An error occurred while property "{0}" was updated. Error message {1}. |
| GBRXC0165E | The change to the trace DAO configuration failed: {0}. |
| GBRXC0166E | An error occurred while the tree data was built: {0}. |
| GBRXC0167E | An error occurred when the server status was set. |
| GBRXC0168E | Date "{0}" could not be parsed against pattern {1}. |
| GBRXC0169E | Unable to create RTS link: {0}. |
| GBRXC0170E | The WADL file was not found. |
| GBRXC0171E | WADL file. |
| GBRXC0172E | Time string < {0} > is not a correct time, formatted as HH:mm:ss. Ignore it. |
| GBRXC0173E | Time string < {0} > does not conform to format HH:mm:ss. Ignore it. |
| GBRXC0174E | The file handler for the Rule Execution Server console was not found. |
| GBRXC0175I | The operating system is {0} {1} {2}. |
| GBRXC0176I | The JVM is {1} {2} {0}. |
| GBRXC0177I | The class path is {0}. |
| GBRXC0178E | The logging configuration property "{0}" for the Rule Execution Server console was not found. Verify the WEB-INF/web.xml file for the console. |
| GBRXC0179E | The value of property "{0}", defined in the "{1}" file, could not be resolved. |
| GBRXC0180W | The logging file path "{0}" was not found. |
| GBRXC0181W | The property "{0}" was not found in the "{1}" file. |
| GBRXC0182E | The security token is missing or incorrect. You are potentially under a Cross-site request forgery attack. If you are trying to use the REST API, please use /apiauth root context. |
| GBRXC0183W | An unauthorized access has been detected from {0} because the security token is incorrect or the request contains an invalid referer header. The console is potentially under a Cross-site request forgery attack. |
| GBRXC0184E | An error occurred when validating the basic authentication header of a request. |
| GBRXC0185W | Decision Runner persistence initialization failed: persistence type is not supported |
| GBRXC0186I | RESMGMT {0}: Adding RuleApp. |
| GBRXC0187I | RESMGMT {1}: Changing RuleApp "{0}". |
| GBRXC0188I | RESMGMT {1}: Removing RuleApp "{0}". |
| GBRXC0189I | RESMGMT {2}: Adding RuleApp property "{1}" to "{0}". |
| GBRXC0190I | RESMGMT {2}: Changing RuleApp property "{1}" in "{0}". |
| GBRXC0191I | RESMGMT {2}: Removing RuleApp property "{1}" from "{0}". |
| GBRXC0192I | RESMGMT {1}: RuleApp "{0}" is added. |
| GBRXC0193I | RESMGMT {1}: RuleApp "{0}" is changed. |
| GBRXC0194I | RESMGMT {1}: RuleApp "{0}" is removed. |
| GBRXC0195I | RESMGMT {2}: RuleApp property "{1}" is added to "{0}". |
| GBRXC0196I | RESMGMT {2}: RuleApp property "{1}" is changed in "{0}". |
| GBRXC0197I | RESMGMT {2}: RuleApp property "{1}" is removed from "{0}". |
| GBRXC0198I | RESMGMT {1}: Adding ruleset "{0}". |
| GBRXC0199I | RESMGMT {1}: Changing ruleset "{0}". |
| GBRXC0200I | RESMGMT {1}: Removing ruleset "{0}". |
| GBRXC0201I | RESMGMT {2}: Adding ruleset property "{1}" to "{0}". |
| GBRXC0202I | RESMGMT {2}: Changing ruleset property "{1}" in "{0}". |
| GBRXC0203I | RESMGMT {2}: Removing ruleset property "{1}" from "{0}". |
| GBRXC0204I | RESMGMT {1}: Ruleset "{0}" is added. |
| GBRXC0205I | RESMGMT {1}: Ruleset "{0}" is changed. |
| GBRXC0206I | RESMGMT {1}: Ruleset "{0}" is removed. |
| GBRXC0207I | RESMGMT {2}: Ruleset property "{1}" is added to "{0}". |
| GBRXC0208I | RESMGMT {2}: Ruleset property "{1}" is changed in "{0}". |
| GBRXC0209I | RESMGMT {2}: Ruleset property "{1}" is removed from "{0}". |
| GBRXC0210I | RESMGMT {2}: Sending a notification "ruleset {0} is changed" from the TCPIP notification server to all execution units: {1}. |
| GBRXC0211I | RESMGMT {2}: Notification "ruleset {0} is changed" is sent from the TCPIP notification server to all execution units: {1}. |
| GBRXC0212I | AUTO CREATE: The repository table is created successfully. |
| GBRXC0213I | AUTO CREATE: The XOM repository table is created successfully. |
| GBRXC0214I | AUTO CREATE: The CDI repository table is created successfully. |
| GBRXC0215I | AUTO CREATE: The TRACE repository table is created successfully. |
| GBRXC0216E | [Unexpected server error: {0}] |
| GBRXC0217W | Role cannot be checked for the user "{0}" for HTTP request "{1}". |
| GBRXC0218W | Remote user is not set after logging in for HTTP request "{0}". |
| GBRXC0219E | No selected ruleset when downloading the ruleapp archive {0}. |
| GBRXC0219I | GBRXC0219I: User ({0}) has signed on. |
| GBRXC0220E | The initialization of the XOM persistence failed. |
| GBRXC0221E | The XOM persistence was not initialized. See the server log for more information. |
| GBRXC0222E | The file size exceeded the limit while uploading the RuleApp archive. For more information, see the server log and the product documentation. |
| GBRXC0223E | Cannot deploy a RuleApp archive that contains non-supported rulesets built with the classic rule engine. |
| GBRXC0224E | Cannot add the ruleset {0}, which was built with the classic rule engine, to the RuleApp. |
| GBRXC0225E | Cannot upload the ruleset {0}, which was built with the classic rule engine, to the RuleApp. |
| GBRXC0301E | No Decision Warehouse configurations were found. Define the ilog.rules.res.trace.DATAWAREHOUSE_CONFIGURATIONS context parameter in the web.xml file. |
| GBRXC0302E | Decision Warehouse configuration {0} is missing from the web.xml file. This configuration will be ignored. |
| GBRXC0303E | Cannot extract property from token {0} in configuration {1}. Properties must be defined in the form key {2} value. Configuration {1} will be ignored. |
| GBRXC0304E | No properties are defined for configuration {0} in the web.xml file. This configuration will be ignored. |
| GBRXC0306E | The default Decision Warehouse configuration {0} is not available. The first configuration defined in web.xml, {1}, is used instead. |
| GBRXC0307E | Cannot find the index file for the online help at {0}. Online help will not be available. |
| GBRXC0308E | Cannot start notification server on port {0}. |
| GBRXC0501E | No panel is currently selected. |
| GBRXC0502E | The tabbed panel name cannot be null. |
| GBRXC0503E | No parent UIForm found for the tabbed panel. |
| GBRXC0504E | The row index is invalid. |
| GBRXC0505E | The tabbed panel must be configured. |
| GBRXC0506E | The Rule Execution Server console application is not granted the required Java permission to access environment variables for configuration purpose. |
| GBRXC0507E | The Rule Execution Server console application is not granted the required Java permission to access Java system properties for configuration purpose. |
| GBRXC0508I | Retrieving messages from the execution units. |
| GBRXC0509I | Retrieving messages from the Rule Execution Server management console. |
| GBRXC0510W | The following message was logged without specifying a required level: ''{0}''. The INFO level will be used as default. |
| GBRXC0511E | Access denied. |
| GBRXC0512W | Logging out the user by using the web container mechanism did not succeed. |
| GBRXC0513W | Session invalidation did not succeed. |
| GBRXC0514W | Logout was requested by using a third-party provider but no redirect URL was specified. Users might not be logged out correctly. |
| GBRXC0515E | Logout by using a third-party provider did not succeed. |
| GBRXC0516W | Host name could not be identified from HTTP referer: {0} |
| GBRXC0517E | Execution unit "{0}" was not found. |
| GBRXC0518E | No execution unit was found. |
| GBRXC0519W | Page {0} was accessed with an absent or invalid security token. |
| GBRXC0520W | An unauthorized access has been detected from {0} because the request refers to a host name that is not declared as trusted. The console is potentially under a cross-site request forgery attack. |
| GBRXC0521E | The value {0} cannot be used to express a trusted host because it is not a valid regular expression. Please check your configuration. |
| GBRXC0522E | The Rule Execution Server logging system was initialized using alternative logging file {0}. |
| GBRXC0523E | The Rule Execution Server logging system could not be initialized using an alternative file. Please check the application permissions. |
| GBRXC0524E | The Rule Execution Server file logging system could not be initialized properly using the intended file {0} : the security manager exists and the logging permission is not correct. Please clean up any locked files that could remain. |
| GBRXC0525W | An error occurred while trying to fetch the documentation at URL {0}. No redirection information was found in response to URL {1}. |
| GBRXC0526W | Too many redirects occurred while trying to fetch the documentation at URL {0}. |
| GBRXC0527W | The expected token parameter "{0}" was not found. |
| GBRXC0528E | An error occurred while trying to retrieve the token required for logout. |
| GBRXC0529E | RuleApp {0} does not exist. |
| GBRXC0530E | Property {0} already exists in {1}. |
| GBRXC0531E | No property to update in {0}. |
| GBRXC0532E | Property {0} does not exist in {1}. |
| GBRXC0533E | RuleSet {0} does not exist. |
| GBRXC0534W | Decision Warehouse traces table will not be installed because a custom implementation has been configured. |
| GBRXC0535W | Decision Warehouse support is not available for schema {0}. |
| GBRXC0536W | Library {0} contains resources that are in error : {1}. Adding internal resources to this library is impossible until resources in error are removed. |
| GBRXC0537W | Internal resource {0} is already referenced. |
| GBRXC0538E | Library {0} does not exist. |
| GBRXC0539E | Internal resource {0} does not exist. |
| GBRXC0540E | Referenced library {0} does not exist. |
| GBRXC0541W | Library {0} is already referenced. |