[rabbitmq-discuss] Need to close channel to get consume message

Emile Joubert emile at rabbitmq.com
Fri Jul 20 11:21:55 BST 2012


Hi,

On 19/07/12 14:27, Vijay Lakshmi wrote:
> - 1  connection and channel pool on that connection ( with 500 channels
> ) for subscribe
> 
> - 1 connection and channel pool on that connection ( with 500 channels )
> for Consume

It is not normally necessary to pool channels. Channels are cheap to
create compared to database connections. If you do decide to use pooling
then bear in mind that some channel state (whether it is transactional
or has confirms enabled) is irreversible.

"subscribe" and "consume" are usually used as interchangeably, so I'm
not sure what your aim is to create separate channels for each.

> Surprisingly when we close the channel, we are getting the message. (
> i.e/ delivery  is not null )

A message coming back to life after closing a channel is normally a sign
of faulty acknowledgement logic in your application. You will probably
find an error if you focus on that.


-Emile




More information about the rabbitmq-discuss mailing list