javax.jms

A client marks a message as persistent if it feels that the application will have problems if the message is lost in transit. A client marks a message as non-persistent if an occasional lost message is tolerable.

This exception is thrown when a method is invoked at an illegal or inappropriate time or if the provider is not in an appropriate state for the requested operation.

This exception must be thrown when a client attempts to set a connection's client ID to a value that is rejected by a provider.

This exception must be thrown when a destination either is not understood by a provider or is no longer valid.

This exception must be thrown when a JMS client attempts to give a provider a message selector with invalid syntax.

This is the root class of all JMS API exceptions.

It provides the following information:

• A provider-specific string describing the error.

This exception must be thrown when a provider rejects a user name/password submitted by a client.

This exception must be thrown when an unexpected end of stream has been reached when a StreamMessage or BytesMessage is being read.

This exception must be thrown when a JMS client attempts to use a data type not supported by a message or attempts to read data in a message as the wrong type.

Each session must insure that it passes messages serially to the listener.

This exception must be thrown when a JMS client attempts to read a write-only message.

This exception must be thrown when a JMS client attempts to write to a read-only message.

The getEnumeration method returns a java.util.Enumeration that is used to scan the queue's messages.

QueueConnectionFactory can be used to create a QueueConnection, from which specialized queue-related objects can be created.

Although it is possible to have multiple QueueReceivers for the same queue, the JMS API does not define how messages are distributed between the QueueReceivers.

If a QueueReceiver specifies a message selector, the messages that are not selected remain on the queue.

Normally, the Queue is specified when a QueueSender is created.

If there are messages that have been received but not acknowledged when a QueueSession terminates, these messages will be retained and redelivered when a consumer next accesses the queue.

A QueueSession is used for creating Point-to-Point specific objects.

This exception is thrown when a provider is unable to allocate the resources required by a method.

A ServerSession implements two methods:

• getSession - returns the ServerSession's JMS session.
• start - starts the execution of the ServerSession thread and results in the execution of the JMS session's run method.

A ConnectionConsumer implemented by a JMS provider uses a ServerSession to process one or more messages that have arrived.

Its only method is getServerSession.

A Session object is a single-threaded context for producing and consuming messages.

This message type can be used to transport text-based messages, including those with XML content.

When a client receives a TextMessage, it is in read-only mode.

A TopicConnectionFactory can be used to create a TopicConnection, from which specialized topic-related objects can be created.

This exception is thrown when an operation is invalid because a transaction is in progress.

This exception must be thrown when a call to Session.commit results in a rollback of the current transaction.

The XAConnection interface is optional.

Some application servers provide support for grouping JTS capable resource use into a distributed transaction (optional).

The XATopicConnectionFactory interface is optional.

The XAQueueSession interface is optional.

The XATopicConnectionFactory interface is optional.

The XATopicSession interface is optional.