[Zope-Checkins] CVS: Packages/ZEO/tests -
ConnectionTests.py:1.40.4.6
Tim Peters
tim.one at comcast.net
Fri Feb 4 14:50:44 EST 2005
Update of /cvs-repository/Packages/ZEO/tests
In directory cvs.zope.org:/tmp/cvs-serv17443/ZEO/tests
Modified Files:
Tag: Zope-2_7-branch
ConnectionTests.py
Log Message:
Fixed several thread and asyncore races in ZEO's connection dance.
ZEO/tests/ConnectionTests.py
The pollUp() and pollDown() methods were pure busy loops whenever
the asyncore socket map was empty, and at least on some flavors of
Linux that starved the other thread(s) trying to do real work.
This grossly increased the time needed to run tests using these, and
sometimes caused bogus "timed out" test failures.
ZEO/zrpc/client.py
ZEO/zrpc/connection.py
Renamed class ManagedConnection to ManagedClientConnection, for clarity.
Moved the comment block about protocol negotiation from the guts of
ManagedClientConnection to before the Connection base class -- the
Connection constructor can't be understood without this context. Added
more words about the delicate protocol negotiation dance.
Connection class: made this an abstract base clase. Derived classes
_must_ implement the handshake() method. There was really nothing in
common between server and client wrt what handshake() needs to do, and
it was confusing for one of them to use the base class handshake() while
the other replaced handshake() completely.
Connection.__init__: It isn't safe to register with asyncore's socket
map before special-casing for the first (protocol handshake) message is
set up. Repaired that. Also removed the pointless "optionalness" of
the optional arguments.
ManagedClientConnection.__init__: Added machinery to set up correct
(thread-safe) message queueing. There was an unrepairable hole before,
in the transition between "I'm queueing msgs waiting for the server
handshake" and "I'm done queueing messages": it was impossible to know
whether any calls to the client's "queue a message" method were in
progress (in other threads), so impossible to make the transition safely
in all cases. The client had to grow its own message_output() method,
with a mutex protecting the transition from thread races.
Changed zrpc-conn log messages to include "(S)" for server-side or
"(C)" for client-side. This is especially helpful for figuring out
logs produced while running the test suite (the server and client
log messages end up in the same file then).
=== Packages/ZEO/tests/ConnectionTests.py 1.40.4.5 => 1.40.4.6 ===
--- Packages/ZEO/tests/ConnectionTests.py:1.40.4.5 Wed Jun 9 14:42:06 2004
+++ Packages/ZEO/tests/ConnectionTests.py Fri Feb 4 14:50:13 2005
@@ -213,7 +213,7 @@
def pollUp(self, timeout=30.0, storage=None):
if storage is None:
storage = self._storage
- # Poll until we're connected
+ # Poll until we're connected.
now = time.time()
giveup = now + timeout
while not storage.is_connected():
@@ -221,9 +221,15 @@
now = time.time()
if now > giveup:
self.fail("timed out waiting for storage to connect")
+ # When the socket map is empty, poll() returns immediately,
+ # and this is a pure busy-loop then. At least on some Linux
+ # flavors, that can starve the thread trying to connect,
+ # leading to grossly increased runtime (typical) or bogus
+ # "timed out" failures. A little sleep here cures both.
+ time.sleep(0.1)
def pollDown(self, timeout=30.0):
- # Poll until we're disconnected
+ # Poll until we're disconnected.
now = time.time()
giveup = now + timeout
while self._storage.is_connected():
@@ -231,6 +237,8 @@
now = time.time()
if now > giveup:
self.fail("timed out waiting for storage to disconnect")
+ # See pollUp() for why we sleep a little here.
+ time.sleep(0.1)
class ConnectionTests(CommonSetupTearDown):
More information about the Zope-Checkins
mailing list