The transaction samples show that the transaction scope is between the client in the JMS session and the broker. When the broker receives commitment, the messages are placed onto queues or topics in the order in which they were buffered as standard messages. The following message delivery is normal:
Pub/Sub Messages Messages are delivered in the order entered in the transaction yet influenced by the priority setting of these and other messages, the use of additional receiving sessions, and the use of additional or alternate topics. The messages are not delivered as a group.
PTP Messages The order of messages in the queue is maintained with adjustments for priority differences but there is no guarantee thatwhen multiple consumers are active on the queuea
MessageConsumerwill receive one or more of theMessageProducers transacted messages.
To run PTP TransactedTalk sample do the following:
In window 1, enter
ant xntalk.In the console window that opens, type text in the window and press Enter.
Repeat to produce a few messages.
Type
COMMITin the window and press Enter.In window 2, enter
ant qmonitor.In the QueueBrowser window, click .
The messages are listed.
In window 3, enter
ant talk2.The window opens with the series of messages in
Q1from theTransactedTalker.In window 1, type some text, and press Enter.
Repeat to produce a few messages.
Type
CANCELin the window and press Enter.The batch of messages is dropped:
In window 3the talk2 window, no messages are received on
Q1.In the QueueBrowser window, Browse Queues lists no messages in
Q1.
In window 1, do the following:
Type some text.
Press Enter.
Type
COMMIT.Press Enter.
The newly-committed transaction batch is received in window 3.
 |  |  |
 |
