[rabbitmq-discuss] JavaClient HeartbeatSender

Dmitry Andrianov dmitry.andrianov at alertme.com
Thu Feb 20 17:38:27 GMT 2014

Ah, I see.
But I am not sure it will help us - we need to avoid creation of extra 
threads not to modify how they are created.
HeartbeatService will still be creating its own scheduler which will in 
turn request new threads from the factory and even if we have custom 
factory - it must satisfy that request and create a new thread for it...

So unless I am missing something it looks like what we want is 
achievable only with custom scheduled executor, not with custom thread 


On 20/02/14 15:15, Michael Klishin wrote:
> On 20 Feb 2014, at 18:24, Dmitry Andrianov <dmitry.andrianov at alertme.com> wrote:
>> Custom ThreadFactory sounds a bit scary. So it won't be using executors framework in that case?
> Executor services can use a custom j.u.c.ThreadFactory implementations to instantiate threads, e.g.
> http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/Executors.html#newCachedThreadPool(java.util.concurrent.ThreadFactory)
> MK
> Software Engineer, Pivotal/RabbitMQ
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

This email is for the use of the intended recipient(s) only.
If you have received this email in error, please notify the sender immediately and then delete it.
If you are not the intended recipient, you must not use, disclose or distribute this email without the
author's prior permission. AlertMe.com Ltd. is not responsible for any personal views expressed
in this message or any attachments that are those of the individual sender.

AlertMe.com Ltd, 30 Station Road, Cambridge, CB1 2RE, UK.
Registered in England, Company number 578 2908, VAT registration number GB 895 9914 42.

More information about the rabbitmq-discuss mailing list