Return-Path: Delivered-To: apmail-jakarta-lucene-user-archive@apache.org Received: (qmail 89953 invoked from network); 22 May 2003 07:16:01 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 22 May 2003 07:16:01 -0000 Received: (qmail 27063 invoked by uid 97); 22 May 2003 07:18:21 -0000 Delivered-To: qmlist-jakarta-archive-lucene-user@nagoya.betaversion.org Received: (qmail 27056 invoked from network); 22 May 2003 07:18:21 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 22 May 2003 07:18:21 -0000 Received: (qmail 89679 invoked by uid 500); 22 May 2003 07:15:58 -0000 Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Users List" Reply-To: "Lucene Users List" Delivered-To: mailing list lucene-user@jakarta.apache.org Received: (qmail 89667 invoked from network); 22 May 2003 07:15:58 -0000 Received: from unknown (HELO svntjt1-47.watercorporation.com.au) (159.52.65.47) by daedalus.apache.org with SMTP; 22 May 2003 07:15:58 -0000 Received: by svntjt1-47.watercorporation.com.au with Internet Mail Service (5.5.2653.19) id ; Thu, 22 May 2003 15:16:13 +0800 Message-ID: <1DB01C48A0A9D311995A00508B62B9F00F9752D9@svntjt1-03.watercorporation.com.au> From: Leslie Hughes To: "'lucene-user@jakarta.apache.org'" Subject: Lucene & EJBs Date: Thu, 22 May 2003 15:16:10 +0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi All, I have a couple of questions regarding using Lucene in an EJB environment. There seems to be a number of probs wrt the ejb spec and lucene. The spec says that EJBs shouldn't (amoungst other things) -access the filesystem -use thread synchronisation or manage threads. So I guess that that means that lucene's indexes (FS ones anyway) and that using synchronisation to serialise access to an Indexwriter are out of the question. I think we've all probably ignored the former bit of the spec :-) so no worries there. But it's the synchronisation of index updates with recreating of readers, and the problem with EJB calls timing out whilst the index is rebuilt that bothers me the most. So, any ideas? I thought about an external daemon or maybe a startup class that coordinates updates and writes with a simple 'flushReader' method on my search EJB - what do you think? Bye Les --------------------------------------------------------------------- To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: lucene-user-help@jakarta.apache.org