-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with distributed workspace #5
Comments
Hi, I ran into a similar problem. Using direct commands from c4jason fixed for me. Cheers. |
Thanks, @rafaelcaue ! I did exactly as you told and it finally worked as expected! Just to let you know, I also had to focus on the organisational artefact and adopt roles manually so that things could work correctly. As can be seen in the output I pasted before, the formation was ok but maria and alice couldn't find plans for their goals for some reason. I only got it working when I followed @rafaelcaue 's advice (again) of doing things manually in the agent script. |
Hi guys, mas cartante { the "slave's" jcm is: mas bingo_artifact {
} CArtAgO Http Server running on http://[ip-slave]:3273 and in debug modality, selection the agent Marcello (section Action): the String "ip-master" and "ip-slave" correspond to the real ip |
Can Jacamo be started headlessly - without the GUIs? |
Yes. You can change the log handler on logging.properties file. |
I've run the code which was provided in the Hello World tut (part V) in order to see how JaCaMo would behave when distributing workspace across multiple nodes. However, none of the agents in the america project were able to join the jacamo remote workspace:
As can be seen, both nodes are running on localhost and the group was formed correctly. Is there anything I can do to make this work? Is this a bug?
Cheers.
The text was updated successfully, but these errors were encountered: