>> It was the request of previous versions which has failed.
>> 
>> All that seems quite curriki specific in there is a simple listener, using 
>> the old-style-notification, which analyzes the document and indexes it and 
>> maybe "related" documents (for example reindexes the user-document so as to 
>> display the count of contributions, or reindexes all of the resources of the 
>> user if the user has changed his name...). The IndexUpdater of the 
>> LucenePlugin does not seem to care for this (but then, it doesn't seem to 
>> measure differences).
> 
> What version of XWiki is that ?

3.5 with old-core and legacy-old-core.

> Actually there is several other listener that look at previous version
> (for example there is listener that check differences and produce more
> precise event about object, object properties, classes, attachments,
> etc.) so at least in most recent versions it's supposed to work.

That was just the most recent version.

We spent a few hours yesterday about it and got a little further: on our beta 
installation the bug did not appear while it does n our production installation 
it does. The only meaningful difference I found is:

> 28,29c26,27
> <         <property name="connection.pool_size">50</property>
> <         <property name="statement_cache.size">50</property>
> ---
> >         <property name="connection.pool_size">2</property>
> >         <property name="statement_cache.size">2</property>


(left is production's hibernate configuration)

We did confirm on beta that the bug reappeared by changing these two parameters 
to 50 and disappeared when back to 2.

However, when deploying on production the values 2, and restarting, the bug was 
still there.

At this point either we can maybe:
- try to automate tests more
- disable clustering
- get a good hint on the differences

Paul

_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to