A message ID consists of 10 alphanumeric characters that uniquely identify the message. The message ID is composed of:
| ID | Description |
|---|---|
| GBRXR0001E | Missing "{0}". You might be executing Java SE rule sessions by using a deployment artifact that is intended for Java EE rule sessions. |
| GBRXR0002E | An error occurred while the rule session was called |
| GBRXR0003E | An error occurred while the rule session was created |
| GBRXR0004E | An error occurred while the rule session interceptor was created or called |
| GBRXR0005E | Unable to find RuleApp {0} for use by the interceptor |
| GBRXR0006E | Unable to find interceptor class {0} |
| GBRXR0007E | Unable to parse monitoring filters: {0} |
| GBRXR0008W | Session factory returned a null trace DAO |
| GBRXR0009W | Exception while saving with trace DAO: {0}. Trace might not have been saved |
| GBRXR0010W | Unable to create trace DAO: {0} |
| GBRXR0011W | BOM support is not enabled for this ruleset. In/out parameters will not be stored as BOM XML. The toString() method will be used. |
| GBRXR0012W | Exception caught while trying to convert to BOM XML: {0}. The method toString() will be used to serialize in/out parameters |
| GBRXR0013E | XU JNDI name {0} does not reference an XU connection factory |
| GBRXR0014W | An exception occurred while trying to close the session: {0} |