There have been cases of archon showing no client object for an agent, but
there are no further
attempts to connect from the agent. This would indicate that arbiter is holding
onto a connection to
an agent. This could be from either archon not properly telling arbiter to
disconnect it, or arbiter
incorrectly holding onto a connection.
One possible fix would be to have arbiter sweep through all its current
connections, and make sure
that archon knows about them.
Original issue reported on code.google.com by tritc...@gmail.com on 18 Dec 2007 at 2:10
Original issue reported on code.google.com by
tritc...@gmail.comon 18 Dec 2007 at 2:10