[ZODB-Dev] Re: ZEO from ZODB-3.1.3 errors on Windows

[Jeremy Hylton]

On Wed, 2003-09-03 at 16:26, Chris Withers wrote:
> Hi Jeremy,
> 
> Sorry for the direct mail, but the lists stil seem fubar'ed.

Yeah.  We're working on it, but no good idea of the cause yet :-(.

> Using ZEO from ZODB 2.1.3 on a Zope 2.6.1 setup on Windows, have a python-only 
> client feeding data into the storage server, and have a Web client to serve out 
> the website.
> 
> Currently noticing two problems.
> 
> 1. Say this in the event log on the web client:
> 
> 2003-09-03T21:20:40 ERROR(200) zrpc-conn:localhost:6001 Asynchronous call raised
>   exception: <ManagedConnection ('127.0.0.1', 6001)>
> Traceback (innermost last):
>    File E:\zope\2.6.1NZ\lib\python\ZEO\zrpc\connection.py, line 234, in handle_re
> quest
>    File E:\zope\2.6.1NZ\lib\python\ZEO\ClientStorage.py, line 994, in invalidateT
> rans
>      (Object: Main)
>    File E:\zope\2.6.1NZ\lib\python\ZEO\ClientStorage.py, line 963, in _process_in
> validations
>      (Object: Main)
>    File E:\Zope\262A8D~1.1\lib\python\ZODB\DB.py, line 302, in invalidate
> TypeError: unhashable type

Is this a common problem?  If it is, it would probably explain #2 below.

It's hard to guess the cause from the traceback.  Any chance you could
add a print or go into pdb or something and find out what the unhashable
type is?  That would go a long way towards explaining what's going on.

> 2. Not seeing updates from the python-only client on the web client unless the 
> web client is restarted.
> 
> Any idea what the problem is with either of these?
> If these issues should be reported in a tracker anywhere, please let me know 
> where...

If we don't figure something out in the next three emails, the tracker
would probably be good.

Jeremy