This topic has not yet been written. The content below is from the topic description.
8.1.1. Message A message is the unit of data which is sent between clients and servers. A message has a body which is a buffer containing convenient methods for reading and writing data into it. A message has a set of properties which are key-value pairs. Each property key is a string and property values can be of type integer, long, short, byte, byte[], String, double, float or boolean. A message has an address it is being sent to. When the message arrives on the server it is routed to any queues that are bound to the address - if the queues are bound with any filter, the message will only be routed to that queue if the filter matches. An address may have many queues bound to it or even none. There may also be entities other than queues, like diverts bound to addresses. Messages can be either durable or non durable. Durable messages in a durable queue will survive a server crash or restart. Non durable messages will never survive a server crash or restart. Messages can be specified with a priority value between 0 and 9. 0 represents the lowest priority and 9 represents the highest. HornetQ will attempt to deliver higher priority messages before lower priority ones. Messages can be specified with an optional expiry time. HornetQ will not deliver messages after its expiry time has been exceeded. Messages also have an optional timestamp which represents the time the message was sent. HornetQ also supports the sending/consuming of very large messages - much larger than can fit in available RAM at any one time.