Session object is a single-threaded context for producing and consuming messages.
More...
#include <javax_jms_Session.h>
Inheritance diagram for javax::jms::Session:


Public Types | |
| enum | { xmogDefaultFlags = xmog_base::GLOBAL, xmogMajorVersion = 3, xmogMinorVersion = 2, xmogPatchVersion = 9, xmogBuildNumber = 2047 } |
|
typedef ::xmog_java_array_template< ::javax::jms::Session > | array1D |
|
typedef ::xmog_java_array_template< ::xmog_java_array_template< ::javax::jms::Session > > | array2D |
Public Member Functions | |
| virtual void | close (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Closes the session. | |
| virtual void | commit (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Commits all messages done in this transaction and releases any locks currently held. | |
| virtual ::javax::jms::QueueBrowser | createBrowser (const ::javax::jms::Queue &queue, const ::java::lang::String &messageSelector,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a QueueBrowser object to peek at the messages on the specified queue using a message selector. | |
| virtual ::javax::jms::QueueBrowser | createBrowser (const ::javax::jms::Queue &queue,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a QueueBrowser object to peek at the messages on the specified queue. | |
| virtual ::javax::jms::BytesMessage | createBytesMessage (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a BytesMessage object. | |
| virtual ::javax::jms::MessageConsumer | createConsumer (const ::javax::jms::Destination &destination, const ::java::lang::String &messageSelector, bool NoLocal,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates MessageConsumer for the specified destination, using a message selector. | |
| virtual ::javax::jms::MessageConsumer | createConsumer (const ::javax::jms::Destination &destination, const ::java::lang::String &messageSelector,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a MessageConsumer for the specified destination, using a message selector. | |
| virtual ::javax::jms::MessageConsumer | createConsumer (const ::javax::jms::Destination &destination,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a MessageConsumer for the specified destination. | |
| virtual ::javax::jms::TopicSubscriber | createDurableSubscriber (const ::javax::jms::Topic &topic, const ::java::lang::String &name, const ::java::lang::String &messageSelector, bool noLocal,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Creates a durable subscriber to the specified topic, using a message selector and specifying whether messages published by its own connection should be delivered to it. | |
| virtual ::javax::jms::TopicSubscriber | createDurableSubscriber (const ::javax::jms::Topic &topic, const ::java::lang::String &name,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Creates a durable subscriber to the specified topic. | |
| virtual ::javax::jms::MapMessage | createMapMessage (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a MapMessage object. | |
| virtual ::javax::jms::Message | createMessage (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a Message object. | |
| virtual ::javax::jms::ObjectMessage | createObjectMessage (const ::java::io::Serializable &object,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates an initialized ObjectMessage object. | |
| virtual ::javax::jms::ObjectMessage | createObjectMessage (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates an ObjectMessage object. | |
| virtual ::javax::jms::MessageProducer | createProducer (const ::javax::jms::Destination &destination,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a MessageProducer to send messages to the specified destination. | |
| virtual ::javax::jms::Queue | createQueue (const ::java::lang::String &queueName,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a queue identity given a Queue name. | |
| virtual ::javax::jms::StreamMessage | createStreamMessage (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a StreamMessage object. | |
| virtual ::javax::jms::TemporaryQueue | createTemporaryQueue (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a TemporaryQueue object. | |
| virtual ::javax::jms::TemporaryTopic | createTemporaryTopic (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a TemporaryTopic object. | |
| virtual ::javax::jms::TextMessage | createTextMessage (const ::java::lang::String &text,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates an initialized TextMessage object. | |
| virtual ::javax::jms::TextMessage | createTextMessage (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a TextMessage object. | |
| virtual ::javax::jms::Topic | createTopic (const ::java::lang::String &topicName,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a topic identity given a Topic name. | |
| virtual jint | getAcknowledgeMode (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Returns the acknowledgement mode of the session. | |
| virtual ::javax::jms::MessageListener | getMessageListener (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Returns the session's distinguished message listener (optional). | |
| virtual bool | getTransacted (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Indicates whether the session is in transacted mode. | |
| virtual void | recover (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Stops message delivery in this session, and restarts message delivery with the oldest unacknowledged message. | |
| virtual void | rollback (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Rolls back any messages done in this transaction and releases any locks currently held. | |
| virtual void | run (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Optional operation, intended to be used only by Application Servers, not by ordinary JMS clients. | |
| virtual void | setMessageListener (const ::javax::jms::MessageListener &listener,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Sets the session's distinguished message listener (optional). | |
| virtual void | unsubscribe (const ::java::lang::String &name,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Unsubscribes a durable subscription that has been created by a client. | |
Static Public Attributes | |
| static xmog_int | AUTO_ACKNOWLEDGE |
With this acknowledgment mode, the session automatically acknowledges a client's receipt of a message either when the session has successfully returned from a call to receive or when the message listener the session has called to process the message successfully returns. | |
| static xmog_int | CLIENT_ACKNOWLEDGE |
With this acknowledgment mode, the client acknowledges a consumed message by calling the message's acknowledge method. | |
| static xmog_int | DUPS_OK_ACKNOWLEDGE |
| This acknowledgment mode instructs the session to lazily acknowledge the delivery of messages. | |
| static xmog_int | SESSION_TRANSACTED |
This value is returned from the method getAcknowledgeMode if the session is transacted. | |
Session object is a single-threaded context for producing and consuming messages.
Although it may allocate provider resources outside the Java virtual machine (JVM), it is considered a lightweight JMS object.
A session serves several purposes:
TemporaryTopics and TemporaryQueues. Queue or Topic objects for those clients that need to dynamically manipulate provider-specific destination names. QueueBrowsers. A session can create and service multiple message producers and consumers.
One typical use is to have a thread block on a synchronous MessageConsumer until a message arrives. The thread may then use one or more of the Session's MessageProducers.
If a client desires to have one thread produce messages while others consume them, the client should use a separate session for its producing thread.
Once a connection has been started, any session with one or more registered message listeners is dedicated to the thread of control that delivers messages to it. It is erroneous for client code to use this session or any of its constituent objects from another thread of control. The only exception to this rule is the use of the session or connection close method.
It should be easy for most clients to partition their work naturally into sessions. This model allows clients to start simply and incrementally add message processing complexity as their need for concurrency grows.
The close method is the only session method that can be called while some other session method is being executed in another thread.
A session may be specified as transacted. Each transacted session supports a single series of transactions. Each transaction groups a set of message sends and a set of message receives into an atomic unit of work. In effect, transactions organize a session's input message stream and output message stream into series of atomic units. When a transaction commits, its atomic unit of input is acknowledged and its associated atomic unit of output is sent. If a transaction rollback is done, the transaction's sent messages are destroyed and the session's input is automatically recovered.
The content of a transaction's input and output units is simply those messages that have been produced and consumed within the session's current transaction.
A transaction is completed using either its session's commit method or its session's rollback method. The completion of a session's current transaction automatically begins the next. The result is that a transacted session always has a current transaction within which its work is done.
The Java Transaction Service (JTS) or some other transaction monitor may be used to combine a session's transaction with transactions on other resources (databases, other JMS sessions, etc.). Since Java distributed transactions are controlled via the Java Transaction API (JTA), use of the session's commit and rollback methods in this context is prohibited.
The JMS API does not require support for JTA; however, it does define how a provider supplies this support.
Although it is also possible for a JMS client to handle distributed transactions directly, it is unlikely that many JMS clients will do this. Support for JTA in the JMS API is targeted at systems vendors who will be integrating the JMS API into their application server products.
Rich Burridge
Kate Stout
|
||||||||||||
|
Closes the session. Since a provider may allocate some resources on behalf of a session outside the JVM, clients should close the resources when they are not needed. Relying on garbage collection to eventually reclaim these resources may not be timely enough. There is no need to close the producers and consumers of a closed session.
This call will block until a Closing a transacted session must roll back the transaction in progress.
This method is the only
Invoking any other
|
|
||||||||||||
|
Commits all messages done in this transaction and releases any locks currently held.
Reimplemented in javax::jms::XASession. |
|
||||||||||||||||||||
|
Creates a
Reimplemented in javax::jms::QueueSession. |
|
||||||||||||||||
|
Creates a
Reimplemented in javax::jms::QueueSession. |
|
||||||||||||
|
Creates a
A
|
|
||||||||||||||||||||||||
|
Creates This method can specify whether messages published by its own connection should be delivered to it, if the destination is a topic.
Since
A client uses a
In some cases, a connection may both publish and subscribe to a topic. The consumer
|
|
||||||||||||||||||||
|
Creates a
Since
A client uses a
|
|
||||||||||||||||
|
Creates a
Since
|
|
||||||||||||||||||||||||||||
|
Creates a durable subscriber to the specified topic, using a message selector and specifying whether messages published by its own connection should be delivered to it.
If a client needs to receive all the messages published on a topic, including the ones published while the subscriber is inactive, it uses a durable
Sessions with durable subscribers must always provide the same client identifier. In addition, each client must specify a name which uniquely identifies (within client identifier) each durable subscription it creates. Only one session at a time can have a
A client can change an existing durable subscription by creating a durable
Reimplemented in javax::jms::TopicSession. |
|
||||||||||||||||||||
|
Creates a durable subscriber to the specified topic.
If a client needs to receive all the messages published on a topic, including the ones published while the subscriber is inactive, it uses a durable
Sessions with durable subscribers must always provide the same client identifier. In addition, each client must specify a name that uniquely identifies (within client identifier) each durable subscription it creates. Only one session at a time can have a
A client can change an existing durable subscription by creating a durable
In some cases, a connection may both publish and subscribe to a topic. The subscriber
Reimplemented in javax::jms::TopicSession. |
|
||||||||||||
|
Creates a
A
|
|
||||||||||||
|
Creates a
The
|
|
||||||||||||||||
|
Creates an initialized
An
|
|
||||||||||||
|
Creates an
An
|
|
||||||||||||||||
|
Creates a
A client uses a
|
|
||||||||||||||||
|
Creates a queue identity given a This facility is provided for the rare cases where clients need to dynamically manipulate queue identity. It allows the creation of a queue identity with a provider-specific name. Clients that depend on this ability are not portable.
Note that this method is not for creating the physical queue. The physical creation of queues is an administrative task and is not to be initiated by the JMS API. The one exception is the creation of temporary queues, which is accomplished with the
Reimplemented in javax::jms::QueueSession. |
|
||||||||||||
|
Creates a
A
|
|
||||||||||||
|
Creates a
Its lifetime will be that of the
Reimplemented in javax::jms::QueueSession. |
|
||||||||||||
|
Creates a
Its lifetime will be that of the
Reimplemented in javax::jms::TopicSession. |
|
||||||||||||||||
|
Creates an initialized
A
|
|
||||||||||||
|
Creates a
A
|
|
||||||||||||||||
|
Creates a topic identity given a This facility is provided for the rare cases where clients need to dynamically manipulate topic identity. This allows the creation of a topic identity with a provider-specific name. Clients that depend on this ability are not portable.
Note that this method is not for creating the physical topic. The physical creation of topics is an administrative task and is not to be initiated by the JMS API. The one exception is the creation of temporary topics, which is accomplished with the
Reimplemented in javax::jms::TopicSession. |
|
||||||||||||
|
Returns the acknowledgement mode of the session. The acknowledgement mode is set at the time that the session is created. If the session is transacted, the acknowledgement mode is ignored.
|
|
||||||||||||
|
Returns the session's distinguished message listener (optional).
|
|
||||||||||||
|
Indicates whether the session is in transacted mode.
Reimplemented in javax::jms::XASession. |
|
||||||||||||
|
Stops message delivery in this session, and restarts message delivery with the oldest unacknowledged message. All consumers deliver messages in a serial order. Acknowledging a received message automatically acknowledges all messages that have been delivered to the client. Restarting a session causes it to take the following actions:
|
|
||||||||||||
|
Rolls back any messages done in this transaction and releases any locks currently held.
Reimplemented in javax::jms::XASession. |
|
||||||||||||
|
Optional operation, intended to be used only by Application Servers, not by ordinary JMS clients.
Reimplemented from java::lang::Runnable. |
|
||||||||||||||||
|
Sets the session's distinguished message listener (optional). When the distinguished message listener is set, no other form of message receipt in the session can be used; however, all forms of sending messages are still supported. This is an expert facility not used by regular JMS clients.
|
|
||||||||||||||||
|
Unsubscribes a durable subscription that has been created by a client. This method deletes the state being maintained on behalf of the subscriber by its provider.
It is erroneous for a client to delete a durable subscription while there is an active
Reimplemented in javax::jms::TopicSession. |
|
|
With this acknowledgment mode, the client acknowledges a consumed message by calling the message's Acknowledging a consumed message acknowledges all messages that the session has consumed. When client acknowledgment mode is used, a client may build up a large number of unacknowledged messages while attempting to process them. A JMS provider should provide administrators with a way to limit client overrun so that clients are not driven to resource exhaustion and ensuing failure when some resource they are using is temporarily blocked. |
|
|
This acknowledgment mode instructs the session to lazily acknowledge the delivery of messages. This is likely to result in the delivery of some duplicate messages if the JMS provider fails, so it should only be used by consumers that can tolerate duplicate messages. Use of this mode can reduce session overhead by minimizing the work the session does to prevent duplicates. |
|
|
This value is returned from the method
If a |
1.4.1