A quick update (probably I will update it once more later).
I have run Test3 with JDK1.5.0_06 and JRockit1.5.0_06 and with the following configs: 1/ jackrabbit-1.0: consistently fails between 700 - 1500 documents 2/ jackrabbit-1.0.1 (with patch JCR-448 included) 2.1/ with JDK1.5.0_06: results in a JVM crash at about 13000-15000 documents 2.2/ with JRockit1.5.0_06: the only one that finished the test Unfortunately, I have run these test last night at about 5am, so I will completely redo it today and update this thread. My plan is to run the Test3 against jackrabbit-1.0, jackrabbit-1.0.1 and jackrabbit-1.0.1a (containing the patches for JCR-448 and JCR-450) with SUN JDK. If this will consistently fail (as above), than rerun all tests with JRockit 1.5.0_06. hth, ./alex -- .w( the_mindstorm )p. On 6/3/06, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
I have checked the jars at the last zip you provided, but the jackrabbit-core seems to not include the patch for JCR-448 (which is supposed to fix the problem). ./alex -- .w( the_mindstorm )p. On 6/3/06, Alexandru Popescu <[EMAIL PROTECTED]> wrote: > Petr is the initial problem still valid if you use the patched > (JCR-448) 1.0.1 release? > > ./alex > -- > .w( the_mindstorm )p. > > > On 5/31/06, Petr Pytelka <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I've created simplified, faster and less resource consuming example of > > problem. > > > > Only source code: > > http://217.11.254.42/download/Test3.java (7kb) > > > > Package with all libraries: > > http://217.11.254.42/download/index-problem.zip (5MB) > > > > Please could you anybody confirm if it is problem in Jackrabbit or in my > > usage of JackRabbit ? > > > > Thanks a lot. > > > > Petr > > > > > > Petr Pytelka wrote: > > > Hi Marcel, > > > I've tried to find out more about my issue but didn't succeed. > > > > > > There is small application which demonstrate the problem: > > > http://217.11.254.42/download/index-problem.zip > > > > > > Steps to reproduce: > > > > > > Prerequisites: > > > 1. This test is resource consuming - need computer with at least 512 MB, > > > better 1 GB > > > 2. Package contain all needed libs and also source code (10kb) - I was > > > not able to create smaller example - sorry for that. > > > > > > Test can be run using script "run-test" or "run-test.bat" - at the > > > beginning of each file is path to the Java. > > > > > > Whole test is trying to create 10000 nodes > > > - Phase 1: Create 20 nodes > > > - Phase 2: Query for last created 20 nodes > > > > > > Problem is that on faster machines this test fail around 3000-5000th > > > document - it is not possible to locate file. Query in repository is > > > based on the attribute values. > > > > > > Maybe that the problem is in my code.. I'll really appreciate if you can > > > look on it... > > > > > > Thanks, Petr > > > > > > > > > Marcel Reutegger wrote: > > >> Hi Petr, > > >> > > >> can you please provide the source code to your test case that allows > > >> us to reproduce the behaviour? Thanks > > >> > > >> regards > > >> marcel > > >> > > >> Petr Pytelka wrote: > > >>> Hi all, > > >>> > > >>> I'm testing performance of Jackrabbit and found one issue. > > >>> > > >>> Test case: > > >>> 1. Insert N items > > >>> 2. Search each of inserted items (using Query) > > >>> 3. Drop inserted item > > >>> > > >>> When N is lower then aprox.1000 items every thinks works fine. But when > > >>> N is higher then aprox. 1000 items Jackrabbit (Lucene) some how "lost" > > >>> indexes and I'm not able to find required item (usualy I'm able to find > > >>> first 300 items). > > >>> If I delete index directory and re-run search, Jackrabbit build new > > >>> indexes during startup and I'm able to find all items. > > >>> > > >>> Lucene: version 1.4.3 > > >>> DB-backend: Derby > > >>> > > >>> Any idea where can be problem ? > > >>> > > >>> Thanks a lot, Petr Pytelka > > >>> > > >>> > > >>> > > >>> > > >
