From: Mark H. <ma...@os...> - 2004-04-28 21:53:16
|
On Wed, 2004-04-28 at 13:01, Jon Maloy wrote: > /jon > > Mark Haverkamp wrote: > > On Tue, 2004-04-27 at 16:58, Jon Maloy wrote: > > > > > Hi all, > > > I just uploaded a new file release to SourceForge. > > > > > > > > Has anybody tested the management interface all the way (Mark?) > > > > > I've been trying it out. I'm still having trouble in some > > circumstances. Sometimes, while the tipc benchmark program is running, > > and I try to get information from the management interface I'll get > > stuck waiting in poll. If I kill the server side while stuck, the > > client side will freeze and requires a reboot. If I kill the program > > waiting on the management interface first and then kill the server side > > program, I have no problems. I haven't gotten too far into figuring out > > what is going on with this one yet but it sounds like a lock problem. > > Especially since it only seems to happen with SMP. > This may be one of the problems I solved in tipc-1.3.10: If you kill a > node while > there are pending connections to it, the auto-disconnect at the other > end will hit > the node-lock a second time in the same thread, in > "nodesub_unsubscribe()". > I fixed this by making it unecessary to unlink the node-subscriber > objects > within the "handle_node_down()" upcall, -all such subscriptions are > one-shot > anyway. > The solution is not totally satisfactory, because the "abort_self" > call and > consequenctly the dispatcher upcall is called with the node lock set. > I found no better solution right now, and it works. > > Do you still have this problem with tipc-1.3.10 ? I am seeing this with the latest cvs code. Mark. -- Mark Haverkamp <ma...@os...> |