Re: Lock issue in 406 while re-indexing the site

Stéphane Croisier <[email protected]>
Newsgroups gmane.comp.cms.jahia.install
Message-ID <[email protected]>
... or just make a copy of your site, block 
access in write mode (for exampel you temporarily 
change the login pop-up jsp on the live site) and 
then override the index directory... This avoids 
to you to setup a Jahia cluster...

Stéphane

At 21:02 18/08/2005, you wrote:
> >Hummm
> >Then, what do you suggest for this site (600-1200 PDF documents) ?
> >To close it to visitors for a full night ??!
>Having Jahia in cluster, you may use one 
>instance for full site re-indexation while the 
>other is still serving visitors. Once the full 
>indexation is done, copy the clean index 
>directory to the other instance ( or make the 
>other instance point to the clean index directory ).
>
>The other solution is to move to Jahia41.
>
>
>
>
>----- Original Message -----
>From: <mailto:[email protected]>Olivier Vit
>To: <mailto:[email protected]>[email protected]
>Sent: Thursday, August 18, 2005 7:33 PM
>Subject: Re: Lock issue in 406 while re-indexing the site
>
>Thanks for your feedback
>
>Khue Nguyen wrote:
>>Hi,
>>
>>
>> >After an upgrade from 4.0.4 to 4.0.6_01, I 
>> noticed that the search returned only a very little number of documents.
>>
>> >First, how can this happen ?
>>
>>Be sure to update your templates so that more 
>>than one matching field by page will be displayed in the search result.
>>To do that, add the hidden input as below in the search form :
>>
>>  <input type="hidden" 
>> name="<%=PageSearchResultBuilderImpl.ONE_HIT_BY_PAGE_PARAMETER_NAME%>" 
>> value="false" />
>>Without that, only one hit ( text field or file ) by page will be displayed.
>>
>>See the header.inc file that comes with the 
>>Jahia 4.0.6 corporate templates for more information.
>>
>This is already what we use
>We had done the change to get better score calculation
>>
>> >21807995 [Ajp13Processor[8009][57]] DEBUG - 
>> Jahia is locked by the super admin !
>>
>>Prior to Jahia 4.1, when indexing a site, the 
>>whole server is locked to prevent access to all 
>>new users ( new session access ).
>>The lock will only be released  when the indexation will finish.
>Hummm
>Then, what do you suggest for this site (600-1200 PDF documents) ?
>To close it to visitors for a full night ??!
>
>>This behavior has been removed from Jahia 4.1.
>This seemed to be a good idea...
>>
>>
>>Regards,
>>
>>Khue Nguyen
>>
>>
>>
>>
>>
>>----- Original Message -----
>>From: <mailto:[email protected]>Olivier Vit
>>To: <mailto:[email protected]>[email protected]
>>Sent: Thursday, August 18, 2005 5:24 PM
>>Subject: Lock issue in 406 while re-indexing the site
>>
>>Hi
>>
>>I'm having a critical problem with a web site 
>>having a pretty large number of attached documents (PDF).
>>
>>After an upgrade from 4.0.4 to 4.0.6_01, I 
>>noticed that the search returned only a very little number of documents.
>>
>>First, how can this happen ?
>>
>>I went for a full site re-index, and for a 
>>while it seemed to go fine, the site being 
>>online and indexing taking place at the same time.
>>
>>And after a few hours of indexing, we got an 
>>error page on the home page saying 'the site is 
>>lock to anybody but the super admin'.
>>See below
>>
>>21807994 [Ajp13Processor[8009][57]] DEBUG - 
>>--------------------------------------------- NEW GET REQUEST ---
>>21807994 [Ajp13Processor[8009][57]] DEBUG - New 
>>request, URL=[/automotive-supplier/Jahia/], 
>>query=[null] serverName=[<http://www.valeo.com>www.valeo.com]
>>21807995 [Ajp13Processor[8009][57]] DEBUG - Character encoding set as: UTF-8
>>21807995 [Ajp13Processor[8009][57]] DEBUG - No cookies found.
>>21807995 [Ajp13Processor[8009][57]] DEBUG - Session is null
>>21807995 [Ajp13Processor[8009][57]] DEBUG - 
>>Session BE244AE771768E83221E562A47A219F9 was just created...
>>21807995 [Ajp13Processor[8009][57]] DEBUG - New 
>>session id=[BE244AE771768E83221E562A47A219F9]
>>21807995 [Ajp13Processor[8009][57]] DEBUG - 
>>Jahia is locked by the super admin !
>>
>>Is this normal ?
>>
>>What can be done to avoid this but recover/rebuild the search indexes ?
>>
>>In such situations, what can be done to cancel 
>>the indexing process and get the site back online ?
>>
>>(it looks that this have been mostly redone in 
>>4.1 but we prefered to deploy a minor release 
>>to minimize the compatibiliy issues)
>>
>>Thanks for your explanations and advices
>>
>>Regards
>
>- -- --- -----=[ scroisier at jahia dot com ]=---- --- -- -
>CEO - Jahia Ltd, 45 rue de la gare, 1260 Nyon (Switzerland)
>Jahia : The Java Unified Web Platform
>www.jahia.org - The community and product web site
>www.jahia.com - Our commercial services company
>www.collaborativesource.org - The Collaborative Source Initiative
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.