> If you want a Zope 2 instance to run the zc.async dispatcher/worker
> threads, then it might be better to get the DB that zope is using. In Zope
> 3, there's an event you can subscribe to to get the DB. Maybe there's
> something similar in Zope 2 these days?
I found it. but I'm not sure if really fire the event at any moment.
in my configure.zcml I have:
the instance starts, but it seems that the handler never run
>> 2008-09-12 02:20:01 ERROR zc.async.events UUID
>> 10c69742-8084-11dd-9853-0016d3094e86 already activated in queue (oid
>> 44148): another process? (To stop poll attempts in this process, set
>> ``zc.async.dispatcher.get().activated = False``. To stop polls permanently,
>> don't start a zc.async.dispatcher!)
> Maybe you are running your tests while you are running your app instance,
> and that both of them actually connect to your real live ZEO.
> Or maybe you are starting a dispatcher yourself, *and*
> zc.async.ftesting.setUp is starting a dispatcher? (ftesting setUp does
> start one.)
right, and what about running many clients with one ZEO. I'm getting the
same error and I don't understand what to do, this is why I need to get the
DB that zope is using?
thanks for your help again, and sorry for my ignorance
Sigue la mata dando de que hablar siempre abajo y a la izquierda donde el
pensamiento que se hace corazón resplandece con la palabra sencilla y
humilde que [EMAIL PROTECTED] [EMAIL PROTECTED] somos.
Zope3-users mailing list