<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Latest posts for the topic "Master Worker strange behavior"]]></title>
		<link>http://forums.terracotta.org/forums/posts/list/5.page</link>
		<description><![CDATA[Latest messages posted in the topic "Master Worker strange behavior"]]></description>
		<generator>JForum - http://www.jforum.net</generator>
			<item>
				<title>Master Worker strange behavior</title>
				<description><![CDATA[ Hey all,

I am looking into using Terracotta and the TIM-MasterWorker module to do some distributed processing pulling "jobs" off a shared queue that is accessible from multiple JVMs running on many remote machines.

The weird behavior I am seeing is that if I start my master (which runs DistributedExecutorService and DistributedCompletionService) first and then start up my workers (which run DistributedWorkerService) only the first worker node will receive jobs from the master.  All the worker nodes connect successfully to the Terracotta server.
BUT
If I start all my workers before I start the master then all my workers are able to pull jobs off of the master.

So, what is happening is that any worker started after the master will not be able to retrieve jobs....

I am using Terracotta 3.5.2_2 and tim-pipes-2.3.1 and tim-masterworker-2.3.1.

Any ideas?  Anybody else seeing this behavior?  I tried to search for this here on the forums but didn't find anything relevant.

I can post my simple test classes if that would help at all.

Thanks,
Erik]]></description>
				<guid isPermaLink="true">http://forums.terracotta.org/forums/posts/list/6481.page#32899</guid>
				<link>http://forums.terracotta.org/forums/posts/list/6481.page#32899</link>
				<pubDate><![CDATA[Tue, 3 Jan 2012 13:07:43]]> GMT</pubDate>
				<author><![CDATA[ egpaulsson]]></author>
			</item>
			<item>
				<title>Master Worker strange behavior</title>
				<description><![CDATA[ You can achieve this by using terracotta express mode with ehcache and quartz .
Terracotta server store all the jobs and tells the workers to run the job. If you want to run any specific job on any specific worker, you need use Quartz Where.
Test your sample with latest terracotta version 3.5.4 which have many crictical quartz bug fixes.
You can post your sample so that i can test it at my end and help you more.

Thanks]]></description>
				<guid isPermaLink="true">http://forums.terracotta.org/forums/posts/list/6481.page#33043</guid>
				<link>http://forums.terracotta.org/forums/posts/list/6481.page#33043</link>
				<pubDate><![CDATA[Wed, 11 Jan 2012 03:46:57]]> GMT</pubDate>
				<author><![CDATA[ gyan10]]></author>
			</item>
			<item>
				<title>Re:Master Worker strange behavior</title>
				<description><![CDATA[ Gyan10,

<blockquote>You can achieve this by using terracotta express mode with ehcache and quartz.&nbsp;
		</blockquote>

Does this mean Terracotta no longer recommends using the available "Terracotta Integration Modules" (TIMs) to implement the master-worker pattern?

Thanks,
Erik]]></description>
				<guid isPermaLink="true">http://forums.terracotta.org/forums/posts/list/6481.page#33054</guid>
				<link>http://forums.terracotta.org/forums/posts/list/6481.page#33054</link>
				<pubDate><![CDATA[Wed, 11 Jan 2012 09:24:05]]> GMT</pubDate>
				<author><![CDATA[ egpaulsson]]></author>
			</item>
	</channel>
</rss>