Author |
Message |
10/27/2006 13:54:42
|
Allan
neo
Joined: 10/27/2006 13:50:15
Messages: 5
Offline
|
All the samples run on one machine. I would like to try DSO with a couple of workers on distributed machines. I am guessing I have to install Terracotta on all potential worker machines and then distribute the application to each of them with all servernames listed in the tc-config.xml. Is this right? Can you give me a little more info on how to get started with a truly distributed jvm test case?
Thanks,
Allan
|
|
|
10/30/2006 09:58:23
|
tgautier
seraphim
Joined: 06/05/2006 12:19:26
Messages: 1781
Offline
|
Hi Allan.
You are very close. After you have installed Terracotta to the worker machines, you will need to:
1) Edit the tc-config.xml file in the samples directory for the server only. In the file there is a server entry with the setting of name="localhost". Change localhost to be the name of the server where you will be running the server - an ip address is also valid here.
2) On the client machines, set the environment variable "TC_JAVA_OPTS" to be the value "-Dtc.config=http://<server>:9515/config". This will tell the clients to locate the server at the specified addres, and load the config file from the server. Combined with the change in (1) above, the clients will now connect to the server using the hostname/ip address you have given them instead of localhost.
Let me know how it goes!
Taylor
|
|
|
10/30/2006 10:29:56
|
Allan
neo
Joined: 10/27/2006 13:50:15
Messages: 5
Offline
|
ok. that sounds simple. I will try it and post the results later.
Thanks,
Allan
|
|
|
10/30/2006 11:47:11
|
Allan
neo
Joined: 10/27/2006 13:50:15
Messages: 5
Offline
|
great! I got the Jtable sample working on remote machines.
One interesting problem though.... when I ran one of the workers on a 64bit machine and the server and other workers were on a 32bit, the 64bit worker connected to the server OK but the data did not flow; his table did not reflect the others.
This is not too surprising since the memory models are probably much different. If you have thoughts on this problem or possible solutions, let me know as we have mixture of machines we would like to use.
Now on to more testing...
|
|
|
10/30/2006 12:17:37
|
tgautier
seraphim
Joined: 06/05/2006 12:19:26
Messages: 1781
Offline
|
Allan,
That is very interesting - I will investigate this issue and get back to you.
Taylor
|
|
|
12/05/2006 22:18:42
|
kbhasin
consul
Joined: 12/04/2006 13:08:21
Messages: 340
Offline
|
Allan -
Have you tried rebuilding the boot-jar on the 64-bit machine that is not communicating by using the following command line:
$TC_INSTALL_DIR/dso/bin/make-boot-jar.sh -o $TC_NSTALL_DIR/common/lib/dso-boot/
The above command line assumes you are using Terrcotta DSO version 2.3 or higher.
For older versions
$TC_INSTALL_DIR/bin/dso-make-boot-jar.sh -o $TC_NSTALL_DIR/lib/dso-boot/
Regards,
Kunal Bhasin.
|
Regards,
Kunal Bhasin,
Terracotta, Inc.
Be a part of the Terracotta community: Join now! |
|
|
|