[concurrency-interest] Putting tasks directly on TPE queue

Gaurav Arora G.Arora at iontrading.com
Fri Dec 25 04:09:42 EST 2009


I have read a few threads dating back 2007 about putting tasks directly
on a TPE queue. The general reply (as is mentioned in the API as well)
is to not access the queue directly. In all those threads, the
corePoolSize and the maximumPoolSize were different. What if the core
pool size is the same as the maximum pool size and all core threads are
started before any tasks are submitted on the queue? Is it still a bad
idea to put tasks directly on the queue? Can it can cause hard to track
down failures?

 

Gaurav




Gaurav Arora
ION Trading
4th Floor, Tower B, Logix Cyber Park, Plot C - 28 & 29, Sector - 62, Noida - 201 301, Uttar Pradesh, INDIA
T: +91 120 4628 400

G.Arora at iontrading.com
http://www.iontrading.com/

***********************************************
This email and any attachments may contain information which is confidential and/or privileged. The information is intended exclusively for the addressee and the views expressed may not be official policy, but the personal views of the originator. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents is prohibited. If you have received this email and any file transmitted with it in error, please notify the sender by telephone or return email immediately and delete the material from your computer. Internet communications are not secure and ION Trading is not responsible for their abuse by third parties, nor for any alteration or corruption in transmission, nor for any damage or loss caused by any virus or other defect. ION Trading accepts no liability or responsibility arising out of or in any way connected to this email.
***********************************************


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20091225/2da0667e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 619 bytes
Desc: not available
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20091225/2da0667e/attachment.gif>


More information about the Concurrency-interest mailing list