Same platform ID equals no communication?

[Pedro Ferreira]

Hey jaders,

I've been working with JADE agents for a while and its the first time I have this problem. I'm working on a distributed system based on JADE. The system will have several machines working and on each machine will be an Agent doing its job. In a main class that i've made for eache one I specifie that every agent will have the same platform ID , but of course, different Addresses.
But there is a problem, i cant get them to communicate . But if put them with diferent platform IDs the communication goes normally.
Is this some kind of limitation?
Can I still get them to communicate with the same platform ID even though they are on different machines ?
If yes , then how?


Thank you very much,

Regards from Portugal,
Pedro Ferreira

[Caire Giovanni-2]

Hi,

If I have understood correctly your system involves several platforms each one formed by just the Main Container.
In general a VERY GOOD practice is that each platform has a different name (Platform-ID). In this way you are sure that, by assigning different local names to agents in a given platform, the global names (<local-name>@<platform-name>) of agents are actually GUID (Globally Unique Identifiers).

Of course the above rule is just a good practice: it is not mandatory.

The reason why your agents cannot communicate when you assign the same name to all your platforms is the following.
By default the JADE message transport service determines if an agent lives in the local platform (possibly in a remote container) from its global-name (remember that agent global names have the form <local-name>@<platform-name>):
- if <platform-name> = name of the local platform --> The agent lives in the local platform --> The INTRA-platform message delivery mechanism is activated which does not use AID addresses.  
- Vice versa the INTER-platform message delivery mechanism is activated which uses AID transport addresses

Therefore in your case, even if the addressed agent lives in a remote platform, JADE considers it local since the name of the remote platform is equal to the name of the local platform.

SOLUTION: Simply specify the
-accept-foreign-agents true
option whenever you start JADE. This will force JADE to check if the agent is actually known to the local platform before activating the proper message delivery mechanism.

Bye,

Giovanni

-----Original Message-----
From: jade-develop-bounces@... [mailto:jade-develop-bounces@...] On Behalf Of Pedro Ferreira
Sent: giovedì 29 ottobre 2009 16.40
To: jade-develop@...
Subject: [jade-develop] Same platform ID equals no communication?


Hey jaders,

I've been working with JADE agents for a while and its the first time I have
this problem. I'm working on a distributed system based on JADE. The system
will have several machines working and on each machine will be an Agent
doing its job. In a main class that i've made for eache one I specifie that
every agent will have the same platform ID , but of course, different
Addresses.
But there is a problem, i cant get them to communicate . But if put them
with diferent platform IDs the communication goes normally.
Is this some kind of limitation?
Can I still get them to communicate with the same platform ID even though
they are on different machines ?
If yes , then how?


Thank you very much,

Regards from Portugal,
Pedro Ferreira
--
View this message in context: http://www.nabble.com/Same-platform-ID-equals-no-communication--tp26115483p26115483.html
Sent from the JADE - Dev mailing list archive at Nabble.com.

_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm
_______________________________________________
jade-develop mailing list
jade-develop@...
https://avalon.cselt.it/mailman/listinfo/jade-develop
UNSUBSCRIBE INSTRUCTIONS AT
http://jade.tilab.com/community-mailinglist.htm