Advanced Queuing - Oracle

JMS Propagation
((AQjmsDestination)topic).schedulePropagation(jms_session, "dba", null,
new Double(5*60), null, new Double(20));
}catch (JMSException ex)
{System.out.println("Exception: " + ex);}
}
Propagation schedule parameters can also be altered.
/* alter duration to 10 minutes and latency to zero */
public void alter_propagation(TopicSession jms_session)
{
Topic topic;
try
{
/* get a handle to the OE_bookedorders_topic */
topic = ((AQjmsSession)jms_session).getTopic("WS",
"WS_bookedorders_topic");
/* Schedule propagation immediately with duration of 5 minutes and latency
20 sec */
((AQjmsDestination)topic).alterPropagationSchedule(jms_session, "dba",
new Double(10*60), null, new Double(0));
}catch (JMSException ex)
{System.out.println("Exception: " + ex);}
}
Enhanced Propagation Scheduling Capabilities
Detailed information about the schedules can be obtained from the catalog views
defined for propagation. Information about active schedules—such as the name of
the background process handling that schedule, the SID (session, serial number) for
the session handling the propagation and the Oracle instance handling a schedule
(relevant if Real Application Clusters are being used)—can be obtained from the
catalog views. The same catalog views also provide information about the previous
successful execution of a schedule (last successful propagation of message) and the
next execution of the schedule.
For each schedule, detailed propagation statistics are maintained:
The total number of messages propagated in a schedule
Total number of bytes propagated in a schedule
Maximum number of messages propagated in a window
12-90 Oracle9i Application Developer’s Guide - Advanced Queuing