Advanced Queuing - Oracle

Support for Statistics Views
}
Internet Access
catch (AQException ex)
{
System.out.println("AQ Exception: " + ex);
}
General Features of Advanced Queuing
Each instance keeps its own AQ statistics information in its own SGA, and does not
have knowledge of the statistics gathered by other instances. When a GV$AQ view
is queried by an instance, all other instances funnel their AQ statistics information
to the instance issuing the query.
Scenario
The gv$ view can be queried at any time to see the number of messages in waiting,
ready or expired state. The view also displays the average number of seconds
messages have been waiting to be processed. The order processing application can
use this to dynamically tune the number of order processing processes (see
"Selecting the Number of Messages in Different States for the Whole Database" on
page 10-33 in Chapter 10, "Administrative Interface: Views").
PL/SQL (DBMS_AQADM Package): Example Code
CONNECT oe/oe
/* Count the number as messages and the average time for which the messages have
been waiting: */
SELECT READY, AVERAGE_WAIT FROM gv$aq Stats, user_queues Qs
WHERE Stats.qid = Qs.qid and Qs.Name = 'OE_neworders_que';
Visual Basic (OO4O): Example Code
Use the dbexecutesql interface from the database for this functionality.
Java (JDBC): Example Code
No example is provided with this release.
See Chapter 17, "Internet Access to Advanced Queuing" for information on Internet
access to Advanced Queuing features.
A Sample Application Using AQ 8-35