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
