You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xindice-dev@xml.apache.org by bu...@apache.org on 2005/01/18 13:33:57 UTC

DO NOT REPLY [Bug 33148] New: - Corrupt index files

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33148>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33148

           Summary: Corrupt index files
           Product: Xindice
           Version: cvs head (1.1)
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DB Engine
        AssignedTo: xindice-dev@xml.apache.org
        ReportedBy: b.eicki@gmx.net


Hello,

I'm using XIndice 1.1b4 (and tried it with current head, too) embedded within a 
webapp in a Tomcat 5 on a jdk 1.4.2 windows system. 
On startup of my application I initialize the database by creating several 
collections and storing some data in them.
The problem is now that if I create a collection first, then create an index 
(or 4 indexes in my case) via the CollectionManager and then store some data 
into that collection, the index is sometimes corrupt. The index is corrupt 
means that I can't search over that index and the index (*.idx) file on the 
filesystem is only 57 bytes large.
If I let my system wait a couple of seconds before I start storing data it is 
all fine.

Bjoern Eickvonder

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.