I'm using ZEO with Zope extensively on RH 9 Linux. It seems that after initial startup, and perhaps anytime there's been an exception, the next http access causes the zeo client to retest it's connection, even though there's no reason to do so. Can anyone explain a) why retest? b) why does it take so long? (30 seconds or more each time) Thanks for any ideas. (not 30 second delay after testing, and it was already connected so why retest?) 2003-05-23T11:01:32 INFO(0) ZODB Opening database for mounting: "{'host':'localhost','port':'4400','storage':'Images',}" ------ 2003-05-23T11:01:32 INFO(0) ZCS:14955 ClientStorage (pid=15009) created RW/normal for storage: 'Images' ------ 2003-05-23T11:01:32 INFO(0) ZEC ClientCache: storage='Images', size=20971520; file[0]='/var/local/Zope/Main2/var/cImages-Common-4400-0.zec' ------ 2003-05-23T11:01:32 INFO(0) ZCS:14955 Testing connection <ManagedConnection ('127.0.0.1', 4400)> ------ 2003-05-23T11:02:03 INFO(0) ZCS:14955 Connected to storage ------ 2003-05-23T11:02:03 INFO(0) ZEC read_index: cache file 0 has 24 records and 50063 bytes ------ 2003-05-23T11:02:03 INFO(0) ZODB Mounted database "{'host':'localhost','port':'4400','storage':'Images',}" at Manage/DocumentImages -- Brad Clements, bkc@murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax http://www.wecanstopspam.org/ AOL-IM: BKClements