Inter Node Communication

[Todd Wright]

Attached below is an updated version of the simple RMI "echo" test.  This 
version works with Cougaar 12.4+.

Please see the zip's README for details.

Todd

Todd Wright wrote:
> On Wednesday 08 June 2005 10:25, Aaron Helsinger wrote:
>> Based on the fact that the error message says "127.0.0.1", this suggests
>> that  Node B is still looking at localhost for the WP server. Are you
>> sure that alpreg.ini was edited on both machines?
> 
> Right, both "alpreg.ini" files should contain the same hostname (not 
> "localhost").
> 
> I've also seen this error when the `hostname` returns "localhost", due to a 
> system configuration problem in /etc/hosts.  In your case, node "A" thinks 
> that its IP address is "127.0.0.1", which confuses node "B" when it finds 
> this address through the usual Cougaar naming service startup.
> 
> I've attached a trimmed-down example that should help you debug.  Run 
> "./compile" to compile, then start the server on one host:
>   ./runServer
> On a remote host, run the client with the URI printed by the above server 
> command, e.g.:
>   ./runClient rmi://123.45.67.89:38335/EchoServer_Stub/1_e..
> The client should print "hello".
> In your config I expect the server to print a URI starting with 
> "rmi://127.0.0.1".
> 
> Todd
> 
>> Andie Kurniawan wrote:
>>> Hello,
>>>
>>> I have been following the 'Introduction to Cougaar Programming' by
>>> Mark Barger. I stuck in the last example where two agents located
>>> across two machines are communicated (example 11).
>>>
>>> Based on the presentation slides, I have modified 'alpreg.ini' to
>>> change localhost to the hostname (I put the IP address of the first
>>> machine) on both machines and then start Exercise11A before ExerciseB.
>>>
>>> On the first machine where the nameserver is located, there was no
>>> error message. However, on the other machine, I received the following
>>> message
>>>
>>> WARN [DestinationQueueImpl] - Exercise11B: Failure in communication,
>>> message The source: Exercise11B The Target: Exercise11A The Message
>>> Id: 0 caused by
>>> java.rmi.ConnectException: Connection refused to host: 127.0.0.1;
>>> nested exception is:
>>>  java.net.ConnectException: Connection refused
>>>
>>> Just for some additional information, both of the machines are running
>>> Ubuntu Linux and using java version 1.4.2.
>>>
>>> Any help will be appreciated.
>>>
>>> Best Wishes,
>>> Andie Kurniawan
>>>
>>> _______________________________________________
>>> Cougaar-developers mailing list
>>> Cougaar-developers at cougaar.org
>>> http://cougaar.org/mailman/listinfo/cougaar-developers
>> _______________________________________________
>> Cougaar-developers mailing list
>> Cougaar-developers at cougaar.org
>> http://cougaar.org/mailman/listinfo/cougaar-developers
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Cougaar-developers mailing list
>> Cougaar-developers at cougaar.org
>> http://cougaar.org/mailman/listinfo/cougaar-developers
-------------- next part --------------
This is a message from the MailScanner E-Mail Virus Protection Service
----------------------------------------------------------------------
The original e-mail attachment "rmi_encode_test.zip"
is on the list of unacceptable attachments for this site and has been
replaced by this warning message.

Due to limitations placed on us by the Regulation of Investigatory Powers
Act 2000, we were unable to keep a copy of the original attachment.

At Fri Jan 18 13:43:46 2008 the virus scanner said:
   MailScanner: Batch files are often malicious (runServer.bat)
   MailScanner: Batch files are often malicious (compile.bat)
   MailScanner: Batch files are often malicious (runClient.bat)

-- 
Postmaster
Cougaar Open Source Community
www.cougaar.org

MailScanner thanks transtec Computers for their support