Re: [Dspace-tech] Index-init error

2008-06-09 Thread Graham Triggs
Jose,

There is a known corruption bug in Lucene 2.3.0, that is meant to be 
fixed in the later releases (they are currently on 2.3.2)

Instead of going back to an older version, can you try using the latest 
version of Lucene (2.3.2)?

There are some useful changes in the 2.3.x series that I would like to 
see us stay with - particularly for anyone that is trying to run Lucene 
on Windows.

G

Blanco, Jose wrote:
 I'm on dspace 1.5, and when I try index-init, I get these errors:
 
 Exception in thread Thread-267
 org.apache.lucene.index.MergePolicy$MergeException:
 org.apache.lucene.index.CorruptIndexException: doc counts differ for
 segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
 at
 org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(Concurr
 entMergeScheduler.java:271)
 Caused by: org.apache.lucene.index.CorruptIndexException: doc counts
 differ for segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
 at
 org.apache.lucene.index.SegmentReader.initialize(SegmentReader.java:313)
 at
 org.apache.lucene.index.SegmentReader.get(SegmentReader.java:262)
 at
 org.apache.lucene.index.SegmentReader.get(SegmentReader.java:221)
 at
 org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3093)
 at
 org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:2834)
 at
 org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(Concurr
 entMergeScheduler.java:240)
 
 I'm using tomcat 5. I say this because, some one thought that tomcat 5
 would fix this.
 
 Also, if I replace lucene-core-2.3.0.jar with what I had for 1.4:
 
 lucene.jar  
 lucene-sandbox.jar 
 
 index-init completes successfully.
 
 Any ideas?
 
 Thank you!
 Jose


 
 
This e-mail is confidential and should not be used by anyone who is not the 
original intended recipient. BioMed Central Limited does not accept liability 
for any statements made which are clearly the sender's own and not expressly 
made on behalf of BioMed Central Limited. No contracts may be concluded on 
behalf of BioMed Central Limited by means of e-mail communication. BioMed 
Central Limited Registered in England and Wales with registered number 3680030 
Registered Office Middlesex House, 34-42 Cleveland Street, London W1T 4LB
This email has been scanned by Postini.
For more information please visit http://www.postini.com


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] Index-init error

2008-06-09 Thread Mark Diggory
Did we upgrade this in the branch Graham?

On Jun 9, 2008, at 8:20 AM, Graham Triggs wrote:

 Jose,

 There is a known corruption bug in Lucene 2.3.0, that is meant to be
 fixed in the later releases (they are currently on 2.3.2)

 Instead of going back to an older version, can you try using the  
 latest
 version of Lucene (2.3.2)?

 There are some useful changes in the 2.3.x series that I would like to
 see us stay with - particularly for anyone that is trying to run  
 Lucene
 on Windows.

 G

 Blanco, Jose wrote:
 I'm on dspace 1.5, and when I try index-init, I get these errors:

 Exception in thread Thread-267
 org.apache.lucene.index.MergePolicy$MergeException:
 org.apache.lucene.index.CorruptIndexException: doc counts differ for
 segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
 at
 org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run 
 (Concurr
 entMergeScheduler.java:271)
 Caused by: org.apache.lucene.index.CorruptIndexException: doc counts
 differ for segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
 at
 org.apache.lucene.index.SegmentReader.initialize 
 (SegmentReader.java:313)
 at
 org.apache.lucene.index.SegmentReader.get(SegmentReader.java:262)
 at
 org.apache.lucene.index.SegmentReader.get(SegmentReader.java:221)
 at
 org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java: 
 3093)
 at
 org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:2834)
 at
 org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run 
 (Concurr
 entMergeScheduler.java:240)

 I'm using tomcat 5. I say this because, some one thought that  
 tomcat 5
 would fix this.

 Also, if I replace lucene-core-2.3.0.jar with what I had for 1.4:

 lucene.jar
 lucene-sandbox.jar

 index-init completes successfully.

 Any ideas?

 Thank you!
 Jose




 This e-mail is confidential and should not be used by anyone who is  
 not the original intended recipient. BioMed Central Limited does  
 not accept liability for any statements made which are clearly the  
 sender's own and not expressly made on behalf of BioMed Central  
 Limited. No contracts may be concluded on behalf of BioMed Central  
 Limited by means of e-mail communication. BioMed Central Limited  
 Registered in England and Wales with registered number 3680030  
 Registered Office Middlesex House, 34-42 Cleveland Street, London  
 W1T 4LB
 This email has been scanned by Postini.
 For more information please visit http://www.postini.com


 -- 
 ---
 Check out the new SourceForge.net Marketplace.
 It's the best place to buy or sell services for
 just about anything Open Source.
 http://sourceforge.net/services/buy/index.php
 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] Index-init error

2008-06-09 Thread Graham Triggs
We moved the branch to 2.3.0 some time ago, to get the improvements that 
were part of that release.

But we haven't done anything since then.

If someone is able to reproduce a problem with 2.3.0, then it's an 
important test to see if it has been fixed with the subsequent releases.

G

Mark Diggory wrote:
 Did we upgrade this in the branch Graham?
 
 On Jun 9, 2008, at 8:20 AM, Graham Triggs wrote:
 
 Jose,

 There is a known corruption bug in Lucene 2.3.0, that is meant to be
 fixed in the later releases (they are currently on 2.3.2)

 Instead of going back to an older version, can you try using the latest
 version of Lucene (2.3.2)?

 There are some useful changes in the 2.3.x series that I would like to
 see us stay with - particularly for anyone that is trying to run Lucene
 on Windows.

 G

 Blanco, Jose wrote:
 I'm on dspace 1.5, and when I try index-init, I get these errors:

 Exception in thread Thread-267
 org.apache.lucene.index.MergePolicy$MergeException:
 org.apache.lucene.index.CorruptIndexException: doc counts differ for
 segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
 at
 org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(Concurr
 entMergeScheduler.java:271)
 Caused by: org.apache.lucene.index.CorruptIndexException: doc counts
 differ for segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
 at
 org.apache.lucene.index.SegmentReader.initialize(SegmentReader.java:313)
 at
 org.apache.lucene.index.SegmentReader.get(SegmentReader.java:262)
 at
 org.apache.lucene.index.SegmentReader.get(SegmentReader.java:221)
 at
 org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3093)
 at
 org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:2834)
 at
 org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(Concurr
 entMergeScheduler.java:240)

 I'm using tomcat 5. I say this because, some one thought that tomcat 5
 would fix this.

 Also, if I replace lucene-core-2.3.0.jar with what I had for 1.4:

 lucene.jar
 lucene-sandbox.jar

 index-init completes successfully.

 Any ideas?

 Thank you!
 Jose




 This e-mail is confidential and should not be used by anyone who is 
 not the original intended recipient. BioMed Central Limited does not 
 accept liability for any statements made which are clearly the 
 sender's own and not expressly made on behalf of BioMed Central 
 Limited. No contracts may be concluded on behalf of BioMed Central 
 Limited by means of e-mail communication. BioMed Central Limited 
 Registered in England and Wales with registered number 3680030 
 Registered Office Middlesex House, 34-42 Cleveland Street, London W1T 4LB
 This email has been scanned by Postini.
 For more information please visit http://www.postini.com


 -
 Check out the new SourceForge.net Marketplace.
 It's the best place to buy or sell services for
 just about anything Open Source.
 http://sourceforge.net/services/buy/index.php
 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech
 

This email has been scanned by Postini.
For more information please visit http://www.postini.com


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] Index-init error

2008-06-09 Thread Mark Diggory
2.3.2 has been published in the central maven repo

http://repo1.maven.org/maven2/org/apache/lucene/lucene-core/2.3.2/

go into your [dspace-source]/pom.xml and find the lucene dependency  
listed in the dependencyManagement section, change its version number  
to 2.3.2 and rebuild your distribution of dspace using mvn clean package

I think we can safely upgrade to this in the trunk and branch.

-Mark

On Jun 9, 2008, at 12:35 PM, Blanco, Jose wrote:

 2.3.2 seems to work.  I put it in the reposiotory area and index- 
 init completed without errors.  Now my problem is that I have 2.3.0  
 in the mvn environemnt and I'm not sure how to remove it and  
 install 2.3.2.  What is the easiest way to do that?

 Thanks!
 Jose

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:dspace-tech- 
 [EMAIL PROTECTED] On Behalf Of Graham Triggs
 Sent: Monday, June 09, 2008 11:20 AM
 To: Blanco, Jose
 Cc: dspace-tech@lists.sourceforge.net
 Subject: Re: [Dspace-tech] Index-init error

 Jose,

 There is a known corruption bug in Lucene 2.3.0, that is meant to  
 be fixed in the later releases (they are currently on 2.3.2)

 Instead of going back to an older version, can you try using the  
 latest version of Lucene (2.3.2)?

 There are some useful changes in the 2.3.x series that I would like  
 to see us stay with - particularly for anyone that is trying to run  
 Lucene on Windows.

 G

 Blanco, Jose wrote:
 I'm on dspace 1.5, and when I try index-init, I get these errors:

 Exception in thread Thread-267
 org.apache.lucene.index.MergePolicy$MergeException:
 org.apache.lucene.index.CorruptIndexException: doc counts differ for
 segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
 at
 org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run 
 (Concurr
 entMergeScheduler.java:271)
 Caused by: org.apache.lucene.index.CorruptIndexException: doc counts
 differ for segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
 at
 org.apache.lucene.index.SegmentReader.initialize 
 (SegmentReader.java:313)
 at
 org.apache.lucene.index.SegmentReader.get(SegmentReader.java:262)
 at
 org.apache.lucene.index.SegmentReader.get(SegmentReader.java:221)
 at
 org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java: 
 3093)
 at
 org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:2834)
 at
 org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run 
 (Concurr
 entMergeScheduler.java:240)

 I'm using tomcat 5. I say this because, some one thought that  
 tomcat 5
 would fix this.

 Also, if I replace lucene-core-2.3.0.jar with what I had for 1.4:

 lucene.jar
 lucene-sandbox.jar

 index-init completes successfully.

 Any ideas?

 Thank you!
 Jose




 This e-mail is confidential and should not be used by anyone who is  
 not the original intended recipient. BioMed Central Limited does  
 not accept liability for any statements made which are clearly the  
 sender's own and not expressly made on behalf of BioMed Central  
 Limited. No contracts may be concluded on behalf of BioMed Central  
 Limited by means of e-mail communication. BioMed Central Limited  
 Registered in England and Wales with registered number 3680030  
 Registered Office Middlesex House, 34-42 Cleveland Street, London  
 W1T 4LB
 This email has been scanned by Postini.
 For more information please visit http://www.postini.com


 -- 
 ---
 Check out the new SourceForge.net Marketplace.
 It's the best place to buy or sell services for
 just about anything Open Source.
 http://sourceforge.net/services/buy/index.php
 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech

 -- 
 ---
 Check out the new SourceForge.net Marketplace.
 It's the best place to buy or sell services for
 just about anything Open Source.
 http://sourceforge.net/services/buy/index.php
 ___
 DSpace-tech mailing list
 DSpace-tech@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


[Dspace-tech] Index-init error

2008-05-22 Thread Blanco, Jose
I'm on dspace 1.5, and when I try index-init, I get these errors:

Exception in thread Thread-267
org.apache.lucene.index.MergePolicy$MergeException:
org.apache.lucene.index.CorruptIndexException: doc counts differ for
segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
at
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(Concurr
entMergeScheduler.java:271)
Caused by: org.apache.lucene.index.CorruptIndexException: doc counts
differ for segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
at
org.apache.lucene.index.SegmentReader.initialize(SegmentReader.java:313)
at
org.apache.lucene.index.SegmentReader.get(SegmentReader.java:262)
at
org.apache.lucene.index.SegmentReader.get(SegmentReader.java:221)
at
org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3093)
at
org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:2834)
at
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(Concurr
entMergeScheduler.java:240)

I'm using tomcat 5. I say this because, some one thought that tomcat 5
would fix this.

Any ideas?

Thank you!
Jose

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] Index-init error

2008-05-22 Thread Blanco, Jose
I found this on the web:

http://www.gossamer-threads.com/lists/lucene/java-dev/61151

And I do have Java(TM) SE Runtime Environment (build 1.6.0_06-b02).

Does any one have this SDK, but having it work successfully.  Does this
mean that if you want to used Lucene 2.3, there are certain SDK's you
cannot use.

-Jose

-Original Message-
From: Blanco, Jose 
Sent: Thursday, May 22, 2008 10:15 AM
To: dspace-tech@lists.sourceforge.net
Subject: Index-init error

I'm on dspace 1.5, and when I try index-init, I get these errors:

Exception in thread Thread-267
org.apache.lucene.index.MergePolicy$MergeException:
org.apache.lucene.index.CorruptIndexException: doc counts differ for
segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
at
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(Concurr
entMergeScheduler.java:271)
Caused by: org.apache.lucene.index.CorruptIndexException: doc counts
differ for segment _fjj: fieldsReader shows 0 but segmentInfo shows 1
at
org.apache.lucene.index.SegmentReader.initialize(SegmentReader.java:313)
at
org.apache.lucene.index.SegmentReader.get(SegmentReader.java:262)
at
org.apache.lucene.index.SegmentReader.get(SegmentReader.java:221)
at
org.apache.lucene.index.IndexWriter.mergeMiddle(IndexWriter.java:3093)
at
org.apache.lucene.index.IndexWriter.merge(IndexWriter.java:2834)
at
org.apache.lucene.index.ConcurrentMergeScheduler$MergeThread.run(Concurr
entMergeScheduler.java:240)

I'm using tomcat 5. I say this because, some one thought that tomcat 5
would fix this.

Any ideas?

Thank you!
Jose

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech