zope2 rdb and reconnect

[zope-4]

I am wondering about the behavior of the publisher  in regards to  
rdb.ZopeDatabaseAdapter when a Retry is raised do to a
mysqldba.OperationalError.

 From what I understand, when Publisher recieves a Retry it again
retries the request, but in my current case I see the error message.
Is my understanding correct that this is what should happen?  If so,
does this hold true for xmlrpc calls as well?

I am using Zope2.9.8-Final, Five 1.4.4, and making requests with xmlrpc.


-Kevin
_______________________________________________
Zope-DB mailing list
Zope-DB@...
http://mail.zope.org/mailman/listinfo/zope-db

[zope-4]

Found the problem.
I back ported this connector from a zope3 app.  For the retry, being
raised was rdb.interfaces.Retry, I changed it to raise ZPublisher.Retry,
which works for zope2.

Maybe there is a better way for zope2, but this works.

-Kevin

Brian Sutherland wrote:

> On Thu, Dec 06, 2007 at 12:00:58PM +0100, zope@... wrote:
>  
>> I am wondering about the behavior of the publisher  in regards to  
>> rdb.ZopeDatabaseAdapter when a Retry is raised do to a
>> mysqldba.OperationalError.
>>
>> From what I understand, when Publisher recieves a Retry it again retries
>> the request,
>>    
>
> The zope3 publisher definitely does this. Does the Zope2 publisher
> recognize Retry as well? (It probably should)
>
>  
>> but in my current case I see the error message. Is my
>> understanding correct that this is what should happen?  If so, does this
>> hold true for xmlrpc calls as well?
>>
>> I am using Zope2.9.8-Final, Five 1.4.4, and making requests with xmlrpc.
>>
>>
>> -Kevin
>> _______________________________________________
>> Zope-DB mailing list
>> Zope-DB@...
>> http://mail.zope.org/mailman/listinfo/zope-db
>>
>>    
>
>  

_______________________________________________
Zope-DB mailing list
Zope-DB@...
http://mail.zope.org/mailman/listinfo/zope-db

[Dieter Maurer]

zope@... wrote at 2007-12-9 13:42 -0500:
>Found the problem.
>I back ported this connector from a zope3 app.  For the retry, being
>raised was rdb.interfaces.Retry, I changed it to raise ZPublisher.Retry,
>which works for zope2.
>
>Maybe there is a better way for zope2, but this works.

A better way would be to raise an exception derived from "ConflictError".

Such an exception would cause ZPublisher to perform the "Retry"
and with a good name for your new exception you would clearly see
what happened in case, the exception were repeated.



--
Dieter
_______________________________________________
Zope-DB mailing list
Zope-DB@...
http://mail.zope.org/mailman/listinfo/zope-db