For application servers,Connection objects provide a special facility for creating aConnectionConsumer (optional). The messages it is to consume are specified by aDestination and a message selector. In addition, aConnectionConsumer must be given aServerSessionPool to use for processing its messages.
Normally, when traffic is light, aConnectionConsumer gets aServerSession from its pool, loads it with a single message, and starts it. As traffic picks up, messages can back up. If this happens, aConnectionConsumer can load eachServerSession with more than one message. This reduces the thread context switches and minimizes resource use at the expense of some serialization of message processing.
QueueConnection.createConnectionConsumer(javax.jms.Queue, java.lang.String, javax.jms.ServerSessionPool, int),TopicConnection.createConnectionConsumer(javax.jms.Topic, java.lang.String, javax.jms.ServerSessionPool, int),TopicConnection.createDurableConnectionConsumer(javax.jms.Topic, java.lang.String, java.lang.String, javax.jms.ServerSessionPool, int)close()Closes the connection consumer. | |
getServerSessionPool()Gets the server session pool associated with this connection consumer. | |
publicServerSessionPoolgetServerSessionPool() throwsJMSException
JMSException - if the JMS provider fails to get the server session pool associated with this consumer due to some internal error.public voidclose() throwsJMSException
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.
JMSException - if the JMS provider fails to release resources on behalf of the connection consumer or fails to close the connection consumer.