<?xml version="1.0" encoding="ISO-8859-1"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Chain of failures on blocking threads</title>
	<atom:link href="http://gfrison.com/2008/06/11/chain-of-failures-on-blocking-threads/feed/" rel="self" type="application/rss+xml" />
	<link>http://gfrison.com/2008/06/11/chain-of-failures-on-blocking-threads/</link>
	<description>I build software emphasizing sound architecture, performance and maintainability in the products I write.</description>
	<lastBuildDate>Wed, 08 Feb 2012 20:47:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Giancarlo Frison</title>
		<link>http://gfrison.com/2008/06/11/chain-of-failures-on-blocking-threads/#comment-10</link>
		<dc:creator><![CDATA[Giancarlo Frison]]></dc:creator>
		<pubDate>Thu, 19 Jun 2008 07:40:11 +0000</pubDate>
		<guid isPermaLink="false">http://giancarlof.wordpress.com/?p=14#comment-10</guid>
		<description><![CDATA[Thank you Chatchai. 
The point isn&#039;t the task&#039;s failure but its delay. 
I want to put in a timebox every task that may delay or block an whole process flow execution. 
Maybe during the login we encounter tcp latency that shifts our task, or the endpoint disappear without any warning, hunging our request. It would trigger unpredictable failures drugging the hung to other components.]]></description>
		<content:encoded><![CDATA[<p>Thank you Chatchai.<br />
The point isn&#8217;t the task&#8217;s failure but its delay.<br />
I want to put in a timebox every task that may delay or block an whole process flow execution.<br />
Maybe during the login we encounter tcp latency that shifts our task, or the endpoint disappear without any warning, hunging our request. It would trigger unpredictable failures drugging the hung to other components.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chatchai</title>
		<link>http://gfrison.com/2008/06/11/chain-of-failures-on-blocking-threads/#comment-9</link>
		<dc:creator><![CDATA[Chatchai]]></dc:creator>
		<pubDate>Thu, 19 Jun 2008 03:29:40 +0000</pubDate>
		<guid isPermaLink="false">http://giancarlof.wordpress.com/?p=14#comment-9</guid>
		<description><![CDATA[Good Post.

Just one minor thing I&#039;d like to add. ExecutorService know nothing about the timeout. TimeoutException has been thrown just to tell us that the get(timeout,timeunit) was timeout. It  didn&#039;t mean that the execution was failed. If the task take around 8 secs and you call get(3 secs) in a loop then you may get TimeoutException for the first and second call and get the result on the third.]]></description>
		<content:encoded><![CDATA[<p>Good Post.</p>
<p>Just one minor thing I&#8217;d like to add. ExecutorService know nothing about the timeout. TimeoutException has been thrown just to tell us that the get(timeout,timeunit) was timeout. It  didn&#8217;t mean that the execution was failed. If the task take around 8 secs and you call get(3 secs) in a loop then you may get TimeoutException for the first and second call and get the result on the third.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

