Derby hangs on large batch insert

[Robert Enyedi <ro...@intland.com>]

In a Derby database we are trying to insert a large number (1300) of 
records in a batch. We are using the Derby network client.

We do the batch insert under isolated conditions in a unit test . When 
executing the test, both the unit test and the Derby server process 
freeze at the point of the insert (during 10 minutes there's no disk 
activity nor processor load for the processes).

Is this a bug or just a server configuration issue?

Regards,
Robert

Re: Derby hangs on large batch insert

[Mike Matrigali <mi...@sbcglobal.net>]

Robert Enyedi wrote:
> Let's suppose that this is a server configuration issue. Is there a 
> limit on the transaction log or pool which the server uses to store data 
> before committing the transaction? If so, is there a way to increase 
> that limit?

Not sure what is going on here.  But there is no limit on the 
transaction log other than available disk space on the disk where
the log is located.  And even then the log will return an error if
it can't write rather than hang.
> 
> Regards,
> Robert
> 
> Robert Enyedi wrote:
> 
>> In a Derby database we are trying to insert a large number (1300) of 
>> records in a batch. We are using the Derby network client.
>>
>> We do the batch insert under isolated conditions in a unit test . When 
>> executing the test, both the unit test and the Derby server process 
>> freeze at the point of the insert (during 10 minutes there's no disk 
>> activity nor processor load for the processes).
>>
>> Is this a bug or just a server configuration issue?
>>
>> Regards,
>> Robert
>>
> 
> 
> 

Re: Derby hangs on large batch insert

[Robert Enyedi <ro...@intland.com>]

Let's suppose that this is a server configuration issue. Is there a 
limit on the transaction log or pool which the server uses to store data 
before committing the transaction? If so, is there a way to increase 
that limit?

Regards,
Robert

Robert Enyedi wrote:
> In a Derby database we are trying to insert a large number (1300) of 
> records in a batch. We are using the Derby network client.
>
> We do the batch insert under isolated conditions in a unit test . When 
> executing the test, both the unit test and the Derby server process 
> freeze at the point of the insert (during 10 minutes there's no disk 
> activity nor processor load for the processes).
>
> Is this a bug or just a server configuration issue?
>
> Regards,
> Robert
>

Re: Derby hangs on large batch insert

[Andreas Korneliussen <An...@Sun.COM>]

Robert Enyedi wrote:
> In a Derby database we are trying to insert a large number (1300) of
> records in a batch. We are using the Derby network client.
> 

Hi,
I have a test application which does insert of 2000 records in a batch,
using the derby network client. I do not get any problems with this
(using default configuration of derby), and Derby 10.2 compiled from trunk.

The fact the everything freezes on the server process may be because of
a bug. I have previously experienced this when inserting large BLOBs,
causing the VM on the server side to go out of memory.

It would be interesting to know what kind of records you are inserting
(i.e data types, #columns etc), in order to track down what causes this
issue.

Regards
Andreas

> We do the batch insert under isolated conditions in a unit test . When
> executing the test, both the unit test and the Derby server process
> freeze at the point of the insert (during 10 minutes there's no disk
> activity nor processor load for the processes).
> 
> Is this a bug or just a server configuration issue?
> 
> Regards,
> Robert