Advanced Queuing - Oracle

General Features of JMS
getExceptionListener() - get the ExceptionListener for this connection.
Session
A Connection is a factory for Sessions that use its underlying connection to a JMS
provider for producing and consuming messages. A JMS Session is a single
threaded context for producing and consuming messages. Although it may allocate
provider resources outside the Java virtual machine, it is considered a light-weight
JMS object.
A Session serves several purposes:
Constitutes a factory for its MessageProducers and MessageConsumers.
Provides a way to get a handle to a destination objects (queues/topics)
Supplies provider-optimized message factories
Supports a single series of transactions that combines work spanning this
session’s Producers and Consumers, organizing these into atomic units.
Defines a serial order for the messages it consumes and the messages it
produces.
Serializes execution of MessageListeners registered with it.
When you use the OCI JDBC driver, you can create multiple sessions for each
connection. When you use other JDBC drivers, only one session can be created from
one connection.
Because a provider may allocate some resources on behalf of a session outside the
JVM, clients should close them when they are not needed. Relying on garbage
collection to eventually reclaim these resources may not be timely enough. The
same is true for the MessageProducers and MessageConsumers created by a
session.
Methods on the Session object include:
commit() - commits all messages performed in this transaction and releases
locks currently held
rollback() - rollsback any messages done in the transaction and release locks
currently held
close() - closes the session
getDBConnection() - gets a handle to the underlying JDBC connection. This
handle can be used to perform other SQL DML operations as part of the same
session. The method is Oracle JMS specific.
12-10 Oracle9i Application Developer’s Guide - Advanced Queuing