Re: [Zope] Running more than one instance on windows often block each other

2005-07-27 Thread Tim Peters
It's starting to look a lot like the Windows bind() implementation is unreliable, sometimes (but rarely -- hard to provoke) allowing two sockets to bind to the same (address, port) pair simultaneously, instead of raising 'Address already in use' for one of them. Disaster ensues. WRT the last vers

Re: [Zope] Running more than one instance on windows often block each other

2005-07-27 Thread Tim Peters
[Tim Peters] ... > Ran that loop in two processes. No hangs, or any > other oddities, for some minutes. It did _eventually_ hang-- and both > processes at the same time --with netstat showing more than 4000 > sockets hanging around in TIME_WAIT state then. I assume I bashed > into some int

Re: [Zope] Running more than one instance on windows often block each other

2005-07-26 Thread Tim Peters
[Sune Brøndum Wøller] > Thanks for the pointer. I have been debugging > select_trigger.py, and has some more info: > > The problem is that the call a.accept() sometimes hangs. > Apparently a.bind(self.address) allows us to bind to > a port that another zope instance already is bound to. > > The cod

Re: [Zope] Running more than one instance on windows often block each other

2005-07-25 Thread Tim Peters
[Tim Peters] >> Yup. ZODB has what looks like a copy/paste of this code, in >> ZEO/zrpc/trigger.py. I didn't realize where it came from originally >> until you pointed out the Medusa code here. >> >> Anyway, it so happens I rewrote ZEO's copy a few weeks ago, in ZODB >> 3.4. The Windows part is

Re: [Zope] Running more than one instance on windows often block each other

2005-07-25 Thread Dieter Maurer
Tim Peters wrote at 2005-7-25 10:36 -0400: >Yup. ZODB has what looks like a copy/paste of this code, in >ZEO/zrpc/trigger.py. I didn't realize where it came from originally >until you pointed out the Medusa code here. > >Anyway, it so happens I rewrote ZEO's copy a few weeks ago, in ZODB >3.4. T

Re: [Zope] Running more than one instance on windows often block each other

2005-07-25 Thread Tim Peters
[Sune B. Woeller] >> ... >> I can see (with the excellent (and free) 'Process >> Explorer' from sysinternals) that the python >> processes always opens port 1, and connects by >> that port to themselves on another port (for >> instance 2550). [Dieter Maurer] > You can find the relevant code i

Re: [Zope] Running more than one instance on windows often block each other

2005-07-24 Thread Dieter Maurer
Sune B. Woeller wrote at 2005-7-21 13:16 +0200: > ... >I can see (with the excellent (and free) 'Process >Explorer' from sysinternals) that the python >processes always opens port 1, and connects by >that port to themselves on another port (for >instance 2550). You can find the relevant co