[Zope-dev] ZEO 2 and Zope 2.5.1

[Brian R Brinegar]

We cannot move to Zope 2.6.1 until we have more time for testing. In the
mean time we would like to have the improvements of ZEO 2. We were running
ZEO 1.0.

We are trying to move to ZEO 2.0.2 out of the ZODB 3.1.1 release using
Zope 2.5.1. The server logs say:

2003-02-17T22:18:54 INFO(0) ZSS:12829 new connection ('192.168.1.102',
38023): <ManagedServerConnection ('192.168.1.102', 38023)>

The client logs say:

------
2003-02-17T22:26:24 INFO(0) ZCS:10901 ClientStorage (pid=10901) created
RW/norma
l for storage: '1'
------
2003-02-17T22:26:24 INFO(0) ZEC:1 ClientCache: storage='1',
size=200000000; file
[0]=None
------
2003-02-17T22:26:24 BLATHER(-100) zrpc:10901 CM.connect(): starting
ConnectThrea
d
------
2003-02-17T22:26:24 BLATHER(-100) zrpc:10901 CT: attempting to connect on
1 sock
ets
------
2003-02-17T22:26:24 BLATHER(-100) zrpc:10901 CW: attempt to connect to
('192.168
.1.51', 15900)
------
2003-02-17T22:26:24 BLATHER(-100) zrpc:10901 CW:
connect_ex(('192.168.1.51', 159
00)) returned EINPROGRESS
------
2003-02-17T22:26:24 BLATHER(-100) zrpc:10901 CW:
connect_ex(('192.168.1.51', 159
00)) returned 0
------
2003-02-17T22:26:24 TRACE(-300) zrpc:10901 message_output 4 bytes: 'Z200'
------
2003-02-17T22:26:24 INFO(0) ZCS:10901 Testing connection
<ManagedConnection ('19
2.168.1.51', 15900)>
------
2003-02-17T22:26:24 TRACE(-300) zrpc-conn:192.168.1.51:15900 send msg: 0,
0, reg
ister, ...

<cache validation messages truncated...>

2003-02-17T22:26:27 INFO(0) ZServer HTTP server started at Mon Feb 17
17:26:27 2
003
        Hostname: minimal
        Port: 8080
------
2003-02-17T22:26:27 INFO(0) ZServer HTTP server started at Mon Feb 17
17:26:27 2
003
        Hostname: minimal
        Port: 8082
------
2003-02-17T22:26:27 INFO(0) ZServer FTP server started at Mon Feb 17
17:26:27 20
03
        Hostname: minimal
        Port: 8021
------
2003-02-17T22:26:27 INFO(0) ZServer FastCGI Server (V1.0) started at Mon
Feb 17
17:26:27 2003
        IP          :
        Port        : 8081
        Socket path : None

------

2003-02-17T22:26:27 DEBUG(-200) zrpc:10901 CM.set_async({11:
<select-trigger (pi
pe) at 82b494c>, 4: <ZServer.HTTPServer.zhttp_server listening :8080 at
0x8c2c6c
4>, 19: <ZServer.FCGIServer.FCGIServer listening :8081 at 0x8ecec94>, 18:
<ZServ
er.FTPServer.FTPServer listening :8021 at 0x8ecd3c4>, 17:
<ZServer.HTTPServer.zh
ttp_server listening :8082 at 0x8ecd68c>, 16: <ManagedConnection
('192.168.1.51'
, 15900)>})
------
2003-02-17T22:26:27 BLATHER(-100) zrpc:10901 CM.set_async(): first call


On Mon, 17 Feb 2003, Guido van Rossum wrote:

> > We've been using ZEO 1 with Zope 2.5.1 but some issues exist with ZEO 1,
> > so we decided to move to ZEO 2.
>
> Which version of ZEO 2 exactly?  (It suffices to tell which exact ZODB
> 3.1.x release you used to get it.)
>
> > Everything is installed installs and starts normally. The server logs show
> > a connection. However any HTTP requests sent to the ZEO client hang. I did
> > a bit of poking around and it appears that the load method of
> > ClientStorage is not called when a request is recieved.
> >
> > Can anyone point me in the right direction?
>
> Would it be an option to upgrade to Zope 2.6.1 as well?
>
> If not, what exactly is in the logs?  Note that you need to have the
> new ZEO in the Python path both on the client side and on the server
> side.
>
> --Guido van Rossum (home page: http://www.python.org/~guido/)
>
>