[rabbitmq-discuss] amqp_channel_open issue

Jim Irrer irrer at umich.edu
Thu Feb 18 21:57:56 GMT 2010

Excellent.  Thank you.

- Jim

Jim Irrer     irrer at umich.edu       (734) 647-4409
University of Michigan Hospital Radiation Oncology
519 W. William St.             Ann Arbor, MI 48103

On Thu, Feb 18, 2010 at 3:32 PM, Tony Garnock-Jones <tonyg at lshift.net>wrote:

> Jim Irrer wrote:
> > So the C client is different from the Java client implementation, which
> > says that multiple threads can share a connection, but not a channel
> Yes, that's right.
> > If I have a multi-threaded Java client that needs many channels, then
> > it is ok (and more efficient) to have one connection and construct
> > many channels from it?
> It's certainly OK. Whether it's more efficient or not depends on exactly
> what you're doing, but it is definitely more efficient in terms of
> socket/TCP resource use. Bear in mind that all the channels are
> multiplexed together onto a single TCP socket, and so one channel may
> momentarily force another to wait.
> Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100218/06bbac4b/attachment.htm 

More information about the rabbitmq-discuss mailing list