[rabbitmq-discuss] Limitations with RabbitMQ Java Client

Steve Powell steve at rabbitmq.com
Wed Oct 23 11:47:08 BST 2013

It is not dangerous to share executors between connections.

If you supply your own Executor (which you must do if you want to share them), then the client will not shutdown the executor when the connection closes.  If you rely on the default, then the (private) executor is closed for you when the connection closes.

Sharing the executor between multiple connections by default means we would have to have a more complex rule for tidying up the (shared) executor, and possibly some option for setting it off? If the user needs this they can achieve it explicitly at present.

Steve Powell  [Cell: +44-7815-838-558] [RabbitMQ, Pivotal]
“L’enfer, c’est les autres.” Sartre

On 23 Oct 2013, at 10:45, Michael Klishin <mklishin at gopivotal.com> wrote:

> On 23 Oct 2013, at 13:36, Simon MacMullen <simon at rabbitmq.com> wrote:
>> Actually I don't see why we shouldn't do this by default. I will file a bug...
> Note that executors cannot be restated and Connection#close shuts down the executor
> it uses. So sharing executors between connections is quite dangerous.
> MK
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list