Re: nxlucene persistent transport

Julien Anguenot wrote:
> Salut Jean-Marc,
>
> Jean-Marc Orliaguet wrote:
>   
>> every now and then, using CPSLuceneCatalog,  there are messages like:
>> INFO nuxeo.lucene.xmlrpc.PersistentTransport Connection lost. Sleeping a
>> bit. Retry number 1
>>     
>
> Supposed to. Either Zope cannot contact the NXLucene server either
> NXLucene has been reseting the connection.
>
> The thing is that I'm using twisted.web which doesn't support properly
> HTTP/1.1. twisted.web2 is much more better in this regard but wasn't
> stable enough at that time.
>   

OK, I'm going to see what exception is raised.

>   
>> appearing in the log file.
>>
>> I suppose that the idea of a persistent connection is that it should
>> stay open until the server is shut down.
>>     
>
> yep it is. You can check the code. It's pretty straightforward. This is
> used when the xml-rpc connection is initialized.
>
>   

yes I saw it, it should be easy to modify it.

>> are these normal messages or is there any fine-tuning to be done on the
>> server(s)?
>>     
>
> Well, no if the NXLucene nor the Zope server are restarted. It's hard to
> debug. Though, this is harmless since Zope will reconnect.
>
> This code is just for optimization purpose on this wonderful HTTP
> protocol :) So if you only see this every now and then that's not really
> something you should be worry about.
>
> Cheers,
>
> 	J.
>
>   

OK, the thing is that some of the connections take a lot of time. It's 
either 0.3s or > 5 seconds. So I wonder if I'm not going to rewrite it 
using a non-persistent connection. Have you experienced problems when 
opening a completely new connection each time?

Cheers
/JM
_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel