Re: [Aglets-users] Problems when using an agent itinerary
Status: Beta
Brought to you by:
cat4hire
From: Thomas H. <Tho...@es...> - 2006-06-14 10:57:22
|
Hi, On Thursday 01 June 2006 16:41, Scotty Smith wrote: > I have been having a problem when using a seqitinerary to deploy my agents > around the network I have set up. It seems as if, at each destination, a > copy of the dispatched agent is left on the server. You mean, a running aglet or just cached bytecode? If it's the first case, do your aglets clone before migrating to the next target? Maybe SeqItinerary works like that. You can test by programming the aglet to display its AgletID on each host. If there are running aglets with the same AgletID, it's a bug in the server. Those IDs are supposed to be globally unique except for cosmic coincidences. :) Please let us know about how all the problems you encountered ended, especially if you were able to solve them! Thanks in advance. Hope this helps. Thomas. -- [Random fortune cookie]: He was part of my dream, of course -- but then I was part of his dream too. -- Lewis Carroll Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm |