<?xml version="1.0" encoding="UTF-8"?><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/"
		>
<channel>
	<title>Comments for Handful of sand</title>
	<atom:link href="http://php.sabscape.com/blog/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://php.sabscape.com/blog</link>
	<description>What we know is but a handful of sand when compared to the world of unknown</description>
	<lastBuildDate>Fri, 23 Mar 2012 21:38:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>Comment on Scaling with the Spring JMS MessageListenerContainer by claudio santana</title>
		<link>http://php.sabscape.com/blog/?p=315&#038;cpage=1#comment-369</link>
		<dc:creator>claudio santana</dc:creator>
		<pubDate>Fri, 23 Mar 2012 21:38:53 +0000</pubDate>
		<guid isPermaLink="false">http://php.sabscape.com/blog/?p=315#comment-369</guid>
		<description>Thanks for posting this example. It was very useful to see a full implementation of this sort of funcionality in one place rather than most documentation which doesn&#039;t put together usages examples.

I just have to say your configuration file is incorrect. The attribute concurrency belongs to the listener-container element not to listener. You can verify this by http://www.springframework.org/schema/jms/spring-jms-{2.5&#124;3.0&#124;3.1}.xsd

It would be nice if you update your post so people can take full advantage of your blog/tutorial.</description>
		<content:encoded><![CDATA[<p>Thanks for posting this example. It was very useful to see a full implementation of this sort of funcionality in one place rather than most documentation which doesn&#8217;t put together usages examples.</p>
<p>I just have to say your configuration file is incorrect. The attribute concurrency belongs to the listener-container element not to listener. You can verify this by <a href="http://www.springframework.org/schema/jms/spring-jms-" rel="nofollow">http://www.springframework.org/schema/jms/spring-jms-</a>{2.5|3.0|3.1}.xsd</p>
<p>It would be nice if you update your post so people can take full advantage of your blog/tutorial.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Spring Integration – Channel mysteries – Part 4 &#8211; Final part by sudhakar</title>
		<link>http://php.sabscape.com/blog/?p=286&#038;cpage=1#comment-349</link>
		<dc:creator>sudhakar</dc:creator>
		<pubDate>Wed, 07 Mar 2012 18:04:41 +0000</pubDate>
		<guid isPermaLink="false">http://php.sabscape.com/blog/?p=286#comment-349</guid>
		<description>Hi 
Can we invoke EJB (session bean running in some servers external to application server) service methods with the help of Spring Integration framework .

We need to read data from ejb service methods.

Thanks in Advance
Sudhakar</description>
		<content:encoded><![CDATA[<p>Hi<br />
Can we invoke EJB (session bean running in some servers external to application server) service methods with the help of Spring Integration framework .</p>
<p>We need to read data from ejb service methods.</p>
<p>Thanks in Advance<br />
Sudhakar</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Spring Integration – Channel mysteries – Part 4 &#8211; Final part by Vishnu</title>
		<link>http://php.sabscape.com/blog/?p=286&#038;cpage=1#comment-338</link>
		<dc:creator>Vishnu</dc:creator>
		<pubDate>Mon, 06 Feb 2012 09:22:54 +0000</pubDate>
		<guid isPermaLink="false">http://php.sabscape.com/blog/?p=286#comment-338</guid>
		<description>Very nice article...got it at the right time of trying to use SI</description>
		<content:encoded><![CDATA[<p>Very nice article&#8230;got it at the right time of trying to use SI</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Merging with Subclipse (and Subversion) by Sab</title>
		<link>http://php.sabscape.com/blog/?p=380&#038;cpage=1#comment-302</link>
		<dc:creator>Sab</dc:creator>
		<pubDate>Mon, 16 Jan 2012 04:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://php.sabscape.com/blog/?p=380#comment-302</guid>
		<description>Mark, Thanks for clarifying!</description>
		<content:encoded><![CDATA[<p>Mark, Thanks for clarifying!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Merging with Subclipse (and Subversion) by Mark Phippard</title>
		<link>http://php.sabscape.com/blog/?p=380&#038;cpage=1#comment-299</link>
		<dc:creator>Mark Phippard</dc:creator>
		<pubDate>Thu, 12 Jan 2012 16:01:11 +0000</pubDate>
		<guid isPermaLink="false">http://php.sabscape.com/blog/?p=380#comment-299</guid>
		<description>Subversion added its merge tracking feature in the 1.5 release back in 2009.  In order to use the feature your Subversion server must be updated to 1.5 or later AND your pre-existing repositories must be upgraded to the 1.5 or later format.

You get the message at the beginning of the post when one of these items is not true.</description>
		<content:encoded><![CDATA[<p>Subversion added its merge tracking feature in the 1.5 release back in 2009.  In order to use the feature your Subversion server must be updated to 1.5 or later AND your pre-existing repositories must be upgraded to the 1.5 or later format.</p>
<p>You get the message at the beginning of the post when one of these items is not true.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Merging with Subclipse (and Subversion) by Merging unrelated Subversion versions using Subclipse &#124; Handful of sand</title>
		<link>http://php.sabscape.com/blog/?p=380&#038;cpage=1#comment-296</link>
		<dc:creator>Merging unrelated Subversion versions using Subclipse &#124; Handful of sand</dc:creator>
		<pubDate>Thu, 12 Jan 2012 07:14:13 +0000</pubDate>
		<guid isPermaLink="false">http://php.sabscape.com/blog/?p=380#comment-296</guid>
		<description>[...] Just as with any merge, make sure your working copy has been switched to the branch you want to update. So in our case, the local working copy should be feature_branch101. You can read more on this in my previous Subversion merge post. [...]</description>
		<content:encoded><![CDATA[<p>[...] Just as with any merge, make sure your working copy has been switched to the branch you want to update. So in our case, the local working copy should be feature_branch101. You can read more on this in my previous Subversion merge post. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Spring Integration – Channel mysteries – Part 3 by Kranthi</title>
		<link>http://php.sabscape.com/blog/?p=249&#038;cpage=1#comment-292</link>
		<dc:creator>Kranthi</dc:creator>
		<pubDate>Mon, 02 Jan 2012 10:26:38 +0000</pubDate>
		<guid isPermaLink="false">http://php.sabscape.com/blog/?p=249#comment-292</guid>
		<description>Hi Sabarish,

Your article &quot;Spring Integration – Channel mysteries&quot; is very well explained and informative.

I just want to inform you about my observation.

The default rejection policy of this thread pool executor is Abort as per java documentation.

http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/ThreadPoolExecutor.html 


But in your article it is mentioned that the default policy is Caller Runs.

I just want to inform to enhance the correctness of the article. I hope you will not take it otherwise.</description>
		<content:encoded><![CDATA[<p>Hi Sabarish,</p>
<p>Your article &#8220;Spring Integration – Channel mysteries&#8221; is very well explained and informative.</p>
<p>I just want to inform you about my observation.</p>
<p>The default rejection policy of this thread pool executor is Abort as per java documentation.</p>
<p><a href="http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/ThreadPoolExecutor.html" rel="nofollow">http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/ThreadPoolExecutor.html</a> </p>
<p>But in your article it is mentioned that the default policy is Caller Runs.</p>
<p>I just want to inform to enhance the correctness of the article. I hope you will not take it otherwise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Spring Integration – Channel mysteries – Part 4 &#8211; Final part by sashank mitra</title>
		<link>http://php.sabscape.com/blog/?p=286&#038;cpage=1#comment-260</link>
		<dc:creator>sashank mitra</dc:creator>
		<pubDate>Fri, 29 Jul 2011 14:05:15 +0000</pubDate>
		<guid isPermaLink="false">http://php.sabscape.com/blog/?p=286#comment-260</guid>
		<description>very well explained article.</description>
		<content:encoded><![CDATA[<p>very well explained article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scaling with the Spring JMS MessageListenerContainer by Sab</title>
		<link>http://php.sabscape.com/blog/?p=315&#038;cpage=1#comment-253</link>
		<dc:creator>Sab</dc:creator>
		<pubDate>Thu, 16 Jun 2011 00:52:54 +0000</pubDate>
		<guid isPermaLink="false">http://php.sabscape.com/blog/?p=315#comment-253</guid>
		<description>@Vijay
Sorry for picking this up late. So how dynamic is this &#039;restriction&#039; imposed by the 3rd party? I mean, does it change every minute or is it like defined once and changed quite rarely?

If it doesn&#039;t change often, you could just change the concurrency attribute of the Spring MLC when you &#039;hear&#039; about the change in the restriction from the 3rd party.

The other option is to introduce a bounded queue between your JMS consumer and the code that interfaces with your 3rd party. Have a threadpool of workers pick up tasks from the queue, the worker being the code that interfaces with your 3rd party. This threadpool&#039;s pool size can be adjusted dynamically to reflect the &#039;restriction&#039; value of the 3rd party.

Hope this helps</description>
		<content:encoded><![CDATA[<p>@Vijay<br />
Sorry for picking this up late. So how dynamic is this &#8216;restriction&#8217; imposed by the 3rd party? I mean, does it change every minute or is it like defined once and changed quite rarely?</p>
<p>If it doesn&#8217;t change often, you could just change the concurrency attribute of the Spring MLC when you &#8216;hear&#8217; about the change in the restriction from the 3rd party.</p>
<p>The other option is to introduce a bounded queue between your JMS consumer and the code that interfaces with your 3rd party. Have a threadpool of workers pick up tasks from the queue, the worker being the code that interfaces with your 3rd party. This threadpool&#8217;s pool size can be adjusted dynamically to reflect the &#8216;restriction&#8217; value of the 3rd party.</p>
<p>Hope this helps</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Scaling with the Spring JMS MessageListenerContainer by Throttling message processing with the Spring JMS MessageListenerContainer &#124; Handful of sand</title>
		<link>http://php.sabscape.com/blog/?p=315&#038;cpage=1#comment-252</link>
		<dc:creator>Throttling message processing with the Spring JMS MessageListenerContainer &#124; Handful of sand</dc:creator>
		<pubDate>Wed, 15 Jun 2011 16:35:07 +0000</pubDate>
		<guid isPermaLink="false">http://php.sabscape.com/blog/?p=315#comment-252</guid>
		<description>[...] &#171; Scaling with the Spring JMS MessageListenerContainer [...]</description>
		<content:encoded><![CDATA[<p>[...] &laquo; Scaling with the Spring JMS MessageListenerContainer [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

