JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server Message Queue 4.5 Developer's Guide for C Clients
search filter icon
search icon

Document Information

Preface

1.  Introduction

2.  Using the C API

3.  Client Design Issues

Producers and Consumers

Using Selectors Efficiently

Determining Message Order and Priority

Managing Threads

Message Queue C Runtime Thread Model

Concurrent Use of Handles

Single-Threaded Session Control

Connection Exceptions

Managing Physical Destination Limits

Managing the Dead Message Queue

Factors Affecting Performance

Delivery Mode (Persistent/Non-persistent)

Use of Transactions

Acknowledgement Mode

Durable and Non-Durable Subscriptions

Use of Selectors (Message Filtering)

Message Size

Message Type

4.  Reference

A.  Message Queue C API Error Codes

Index

Determining Message Order and Priority

In general, all messages sent to a destination by a single session are guaranteed to be delivered to a consumer in the order they were sent. However, if they are assigned different priorities, a messaging system will attempt to deliver higher priority messages first.

Beyond this, the ordering of messages consumed by a client can have only a rough relationship to the order in which they were produced. This is because the delivery of messages to a number of destinations and the delivery from those destinations can depend on a number of issues that affect timing, such as the order in which the messages are sent, the sessions from which they are sent, whether the messages are persistent, the lifetime of the messages, the priority of the messages, the message delivery policy of queue destinations, and message service availability.