Home » jboss-javaee-sources » javax » jms » [javadoc | source]
public interface: ConnectionConsumer [javadoc | source] For application servers, Connection objects provide a special facility for creating a ConnectionConsumer (optional). The messages it is to consume are specified by a Destination and a message selector. In addition, a ConnectionConsumer must be given a ServerSessionPool to use for processing its messages.

Normally, when traffic is light, a ConnectionConsumer gets a ServerSession from its pool, loads it with a single message, and starts it. As traffic picks up, messages can back up. If this happens, a ConnectionConsumer can load each ServerSession with more than one message. This reduces the thread context switches and minimizes resource use at the expense of some serialization of message processing.

Method from javax.jms.ConnectionConsumer Summary:
close,   getServerSessionPool
Method from javax.jms.ConnectionConsumer Detail:
 public  void close() throws JMSException
    Closes the connection consumer.

    Since a provider may allocate some resources on behalf of a connection consumer outside the Java virtual machine, clients should close these resources when they are not needed. Relying on garbage collection to eventually reclaim these resources may not be timely enough.

 public ServerSessionPool getServerSessionPool() throws JMSException
    Gets the server session pool associated with this connection consumer.