| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
The HIS log is structured as a flat line based file. Each event starts on a new line and can span multiple lines based on the event type and content. Here’s an example event:
...
As the session or interaction state changes, the workflow component keeps track using several state machines. An event is raised by the processor session and sent to the workflow engine (line 1). The workflow engine looks to see if there is a transition for the event and if there is changes the state machine (line 3). The state changes are listed in lines 3 & 4. When the state changes, the set of buttons or capabilities that are enabled and disable are updated and set to the client (lines 6-8).
Errors
| Code Block |
|---|
2023-06-13_14:58:18.134 UTC ERROR MQProcessor CICEnvironment - Error reading messages. Resetting connection
java.net.SocketException: Socket closed
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:183)
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:200)
at com.openmethods.iserver.processor.cti.mq.MQProcessor$MessageListener.run(MQProcessor.java:490)
at java.base/java.lang.Thread.run(Thread.java:834) |
Errors are almost always multi-line events. The first line contains information about the error and what was trying to be done when the error occurred. The remaining lines are a Java stack trace that provides technical details about the error and should be included in any bug report.