Managing Ensemble Productions - InterSystems Documentation

Message List
Color
White and pale blue,
in alternating rows
Indication
These messages are OK.
8.1.1 Message Details
If you select a message in an Ensemble Management Portal page and click Details, additional message information displays
in the lower portion of the screen.
You can display message details by clicking Details next to the message displayed on the following pages of the Ensemble
Management Portal:
• [Ensemble] > [Messages]
• [Ensemble] > [Messages] > [Visual Trace] (click on a specific message in the trace)
• [Ensemble] > [Queues] > [Contents]
• [Ensemble] > [Maintenance] > [Suspended]
Details of the selected message display in the lower portion of the page. The left side of the display shows the entire contents
of the Message Header. Fields include:
• Type — The message type, Request or Response.
• — The object identifier for the message header. Whenever a message header and message body are combined
together as a message, the ObjectId value in the header is used to identify the combined message object. As a result,
this value is the same as the message ID listed in the Message Browser and other pages in the Ensemble Management
Portal.
• Priority — The priority of the message relative to others in the queue: RealTime (1), High (2), Normal (3), or Low (4).
The Ensemble messaging engine assigns priority values to messages automatically, in the course of normal processing,
for its own use. Message priority cannot be programmed into a message class or configured in any way. Priority values
are based in part on whether the message is synchronous (High) or asynchronous (Normal). Also, messages that start
or stop a production are assigned greater priority than other types of message.
• Invocation — The style of invocation for message: Queue or Inproc.
Inproc means the message is formulated, sent, and delivered in the same process in which it was created. The job is
not released to the sender’s pool until the message is delivered to the target.
Queue means the message is created in one job, then placed on a queue, at which time the original job is released.
Later, when the message is processed, a different job is allocated for the task.
• TimeCreated — The message creation time stamp. For Queue messages, this is the time when Ensemble placed this
message on the queue. For Inproc messages, this is the time when Ensemble called the Send method.
• TimeProcessed — The message usage time stamp. For Queue messages, this is the time when Ensemble took the
message off the queue to be processed. For Inproc messages, this is the time when Ensemble began processing the
message. For Inproc messages, TimeProcessed will be very close to TimeCreated.
• Status — Indicates the status of the message within its normal life-cycle: Created, Queued, Delivered, Deferred,
Completed, Discarded, or Suspended. If there is a request-response pair, the value does not indicate an overall status
for the pair; a request may end up with a different Status from its corresponding response.
A message in transit has a Status of Created, until it finds its place on a queue, when it becomes Queued. A message
that reaches its destination is at first Delivered, then finally Completed. An asynchronous response is Discarded if it
arrives after the timeout period for the corresponding request expired. A message response can been Deferred by a
business operation to be sent later on; when a Deferred message is finally sent, it has a Status of Completed.
Managing Ensemble Productions 73