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
>