Java Reference
In-Depth Information
A JMS message consists of a header, properties, and a body. The message headers
provide a fixed set of metadata fields describing the message, with information such
as where the message is going and when it is received. The properties are a set
of key-value pairs used for application-specific purposes, usually to help filter mes-
sages quickly when they have been received. Finally, the body contains whatever
data is being sent in the message.
The JMS API supports two delivery modes for messages to specify whether or not
the messages are lost if the JMS provider fails, indicated by the following constants:
• The persistent delivery mode, which is the default, instructs the JMS pro-
vider to take extra care to ensure that a message is not lost in transit in
case of a JMS provider failure. A message sent with this delivery mode is
logged to stable storage when it is sent.
• The non_persistent delivery mode does not require the JMS provider to
store the message or otherwise guarantee that it is not lost if the provider
fails.
Search WWH ::




Custom Search