Finding the cause of errors and validating results

Use the Log section to check the log information for a selected event.

About this task

The Log section displays messages captured between the start of the event processing and the end of the event processing. You can find all the original server log files in the <InstallDir>/runtime/wlp/usr/servers/server_name/logs directory if you want more information.

The following table lists all the messages that can be found in the Log tab.

Table 1. Log messages
Message	Message type	Description
`Processing time was date_time`	Information	Indicates the time and date at which the processing of the event starts.
`event_name was emitted`	Information	Indicates an emitted event. The name is a hyperlink to the emitted event on the timeline. If the event is emitted by a rule, this information is displayed in the rule's collapsible section. If the event is emitted by a Java Agent, this information is displayed at the top level.
`cookie was cookie_id`	Information	Indicates the ID of the cookie string set by the Java Agent. Note: This message only appears for events that are scheduled by a Java Agent.
`rule_name was fired` (rule)	Information	Indicates that the rule was fired. This information is displayed as a collapsible section if there are more messages related to the fired rule.
`variable_name was set to variable_value`	Information	Indicates that the rule variable, as specified in the definition part of a rule, was set to a particular value. This information is displayed in the collapsible section of the `rule_name was fired` message.
`variable_name was set`	Information	Indicates that the rule variable was set. The variable value is a collection, or a nested collection. The field and value pairs are displayed as a collapsible section under the variable trace message. This information is displayed in the collapsible section of the `rule_name was fired` message.
`rule_name was fired` (Java Agent)	Information	Indicates that the rule was fired. This information is displayed as-is at the top level.
`print from rule`	Information	Print statement from an action rule. This information is displayed as-is in the rule's collapsible section.
`print from Java Agent`	Information	EntityAgent#PrintToLog() call from a Java Agent. This information is displayed at the top level.
`entity_name entity with id entity_id not found`	Warning	Indicates that an entity is not initialized.
`event_name was out-of-order because the event timestamp was date_time but the processing time was date_ time`	Warning	Indicates that the event processing occurred out-of-order.
`event_name was rolled back because of exception_name`	Error	Indicates that the event is rolled back as a result of an exception. For a Java Agent, a stack trace of the exception is displayed in a collapsible section. For a Rule Agent, if the exception is a RoutingException, the exception message that provides further information about the error is also displayed.
`event_name was rolled back due to error processing event_hyperlink by agent_name because of exception_name`	Error	Indicates that the event is rolled back as a result of another event. The message includes a hyperlink to the event on the timeline.
`exception_name in action while executing rule rule_name`	Error	Indicates that an exception occurred in the action of a rule. The exception class name is included in the message. No stack trace is displayed. This information is displayed in the rule's collapsible section.
`exception_name in condition exception_message`	Error	Indicates that an exception occurred in the condition of a rule. This information is displayed at the top level.

Error messages are indicated by a red triangular icon that contains a white exclamation mark ( Error icon ). The Log section displays the name of the entity that produced an error, and the time and date at which the error occurred.

Warning messages are indicated by a yellow circular icon that contains a white exclamation mark ( Warning icon ). If an exception is thrown by the agent, the Log section displays information up until, and including, the exception trace. When an exception from a previous agent prevents another agent from processing the same event, the Log section displays a message that includes a hyperlink to the offending event on the timeline.

Procedure

In the solution timeline, look for event icons with a slashed center. An error icon might be red or gray, depending on whether there are additional events related to the error in the timeline.

Table 2. Event error icons
Event error icon	Description
	The event error is not selected.
	The event error is not selected. There are additional instances of the same event, or related emitted events.
	The event error is selected. There are additional instances of the same event, or related emitted events.

When you select an event that produced an error, you might see a related event selected in the solution timeline.

Expand collapsed entity sections to determine which event in the section produced an error. When event processing ends due to an unrecoverable exception before completion, then the error icon appears in the agent timeline that contains the stopped event. In a solution recording where the same event is processed by several agents, the error icon appears in each timeline to indicate that event processing is incomplete. If event processing is tried again multiple times, the error icon appears only when the maximum number of attempts is reached. In this case, the system no longer tries to process the event and the system logs an error.
Select an error icon, then analyze the event data to identify the cause of the error. Information about the event appears in the Data tab.
Click the Log tab to display the corresponding log information.
In the Log tab, analyze the error messages.
Fix the errors and then run the test again to create a new recording.