Re: Store being constructed on deleted area

["Nicolas Carranza" <nicarran@xxxxxxxxxxx>]

Hello Toby,
I'm using only one multiuser server (jdbc:mckoi://localhost:9157) through 
JBoss. I don't use mckoi as an embedded application. I'm testing with tree 
simultaneous very demanding clients and these exceptions are hard to 
reproduce but are still appearing randomly. Sometimes after long time, mckoi 
stop responding and I have to kill it (and shut down JBoss).

>From: Tobias Downer <toby@mckoi.com>
>Reply-To: mckoidb@mckoi.com
>To: mckoidb@mckoi.com
>Subject: Re: Store being constructed on deleted area
>Date: Sat, 24 Apr 2004 11:06:12 -0700
>
>Hi Nicolas,
>
>See my comments below;
>
>Nicolas Carranza wrote:
>>Hello. I'm heavy testing my application and I'm getting this:
>>---- debug.log ----
>>...
>>% Dropped: 11574nicarran_ejb_CustomField
>>% Dropped: 11573nicarran_ejb_CustomField
>>% Dropped: 11576nicarran_ejb_CustomField
>>% java.io.IOException: Store being constructed on deleted area.
>>     at 
>>com.mckoi.store.AbstractStore$StoreArea.<init>(AbstractStore.java:1513)
>>     at com.mckoi.store.AbstractStore.getArea(AbstractStore.java:1406)
>>     at 
>>com.mckoi.database.IndexSetStore$MappedListBlock.getArray(IndexSetStore.java:1022)
>>
>>     at 
>>com.mckoi.util.BlockIntegerList$IntArrayListBlock.searchFirst(BlockIntegerList.java:356)
>>
>>     at 
>>com.mckoi.util.AbstractBlockIntegerList.searchFirst(AbstractBlockIntegerList.java:1049)
>>
>>---- debug.log ----
>>What does this mean?
>>And after a while the mckoi db appers to be locked. It does not respond to 
>>clients.
>>Is it my app doing something wrong or is it mckoi?
>
>From the stack trace, it looks like the index of one of your tables has 
>become corrupt.  I suggest running the repair tool on the database to fix 
>the problem.  To do this, use the following command (one line);
>
>   Java -cp mckoidb.jar com.mckoi.tools.DBConglomerateRepairTool -path 
>[path to your database data directory]
>
>Before you run the repair tool, make sure that you backup the database 
>files.
>
>The usual reason why this happens is because there are multiple Java 
>Virtual Machines that are running their own copies of Mckoi DB and 
>accessing the database at the same time.  This can cause corruption to 
>occur.  When you start the database server, you must ensure that you only 
>access the database server through a JDBC connection to the server (for 
>example, "jdbc:mckoi://mydatabaseserver.com/") and not through an embedded 
>connection (for example, "jdbc:mckoi:local://path/to/db.conf") when you 
>connect to it.
>
>
>>The last lines of my debug.log are:
>>----
>>...
>>[ TIME: Sat Apr 24 02:48:27 COT 2004 ]
>>% java.net.SocketException: Socket closed
>>     at java.net.SocketInputStream.socketRead0(Native Method)
>>     at java.net.SocketInputStream.read(SocketInputStream.java:129)
>
>This does not indicate a problem with your setup.  These messages occur 
>when a client connection to the server is terminated.  This error will be 
>downgraded to a warning to prevent the trace appearing in the logs in the 
>future.
>
>Toby.
>
>
>---------------------------------------------------------------
>Mckoi SQL Database mailing list  http://www.mckoi.com/database/
>To unsubscribe, send a message to mckoidb-unsubscribe@mckoi.com
>

_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail