Advanced Queuing - Oracle

JMS Message Consumer Features
Modes for Receiving Messages
}
}
else
throw ex;
}
}catch (JMSException ex)
{
System.out.println("Exception: " + ex);
}
}
For Point-to-Point Mode
Aside from the normal receive, which allows the dequeuing client to delete the
message from the queue, JMS provides an interface that allows the JMS client to
Browse its messages in the queue. A QueueBrowser can be created using the
createBrowser method from QueueSession.
If a message is browsed, it remains available for further processing. Note that after a
message has been browsed there is no guarantee that the message will be available
to the JMS session again as a receive call from a concurrent session might remove
the message.
To prevent a viewed message from being removed by a concurrent JMS client, you
can view the message in the locked mode. To do this, you need to create a
QueueBrowser with the locked mode using the AQ extension to the JMS
interface.The lock on the message with a browser with locked mode is released
when the session performs a commit or a rollback.
To remove the message viewed by a QueueBrowser, the session must create a
QueueReceiver and use the JMSmesssageID as the selector.
Example Code
Refer to the QueueBrowser Example in Point-to-Point features
Remove-No-Data
The MessageConsumer can remove the message from the queue or topic without
retrieving the message using the receiveNoData call. This is useful when the
application has already examined the message, perhaps using the QueueBrowser.
12-72 Oracle9i Application Developer’s Guide - Advanced Queuing