Advanced Queuing - Oracle

Time Specification - Delay
}
"OE_bookedorders_topic");
/* Create the topic publisher */
tpub = jms_session.createPublisher(topic);
obj_message = jms_session.createObjectMessage();
obj_message.setObject(order);
/* Send message - specify priority */
tpub.publish(topic, obj_message, DeliveryMode.PERSISTENT,
ship_priority,0);
jms_session.commit();
}
catch (Exception ex)
{
System.out.println("Exception ex: " + ex);
}
JMS Message Producer Features
Messages can be sent/published to a queue/topic with Delay. The delay represents
a time interval after which the message becomes available to the Message
Consumer. A message specified with a delay is in a waiting state until the delay
expires and the message becomes available. Delay for a message is specified as
message property (JMS_OracleDelay). This property is not specified in the JMS
standard. It is an AQ extension to JMS message properties.
Delay processing requires the AQ background process, the queue monitor to be
started. Note also that receiving by msgid overrides the delay specification.
Example Scenario and Code
In the BooksOnLine application, delay can be used to implement deferred billing.
The billing application defines a queue in which shipped orders that are not billed
immediately are placed with a delay. For example, a certain class of customer
accounts, such as corporate customers, may not be billed for 15 days. The billing
application dequeues incoming shipped order messages (from the shipped orders
queue) and if the order is for a corporate customer, this order is enqueued into a
deferred billing queue with a delay. Delay works similarly for publish, though a
scenario has not been provided.
public static void defer_billing(QueueSession jms_session,
Creating Applications Using JMS 12-59