Progress Sonic ESB Configuration and Management Guide

Chapter 2: ESB Containers
ESB Container Intra-container Messaging
Intra-container messaging allows a container to bypass the overhead of sending and
receiving messages to and from services in a process when the next service in an ESB
Process resides in the same container. When you select intra-container messaging for an
ESB Container, a message in the Outbox of one service (that is addressed to another
service in the same ESB Container) is sent directly the other service, bypassing the broker.
Messages sent to a Sonic ESB service where intra-container messaging is enabled bypass
the broker, so any listeners outside the container will not receive these messages. The
Quality of Service (QoS) for the entire message dispatch through a process or chain of
services is dictated by the QoS of the entry endpoint of the service that first receives the
message off the originating JMS destination.
For example, when a service whose entry endpoint has a QoS of EXACTLY_ONCE receives a
message, that message will have QoS of EXACTLY_ONCE throughout the process until it
reaches another JMS destination, regardless of the QoS of any other services it passes
through after the first service. In this example, if a fatal error (such as a container crash,
machine crash, or power failure) occurs, a message that is not committed at the time of
failure will be resent when the container becomes available. The uncommitted message is
resent in this case because it retains the QoS of EXACTLY_ONCE. See “Quality of Service”
on page 111 for more information about QoS.
61 Progress Sonic ESB Configuration and Management Guide 8.5