db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendle...@amberpoint.com>
Subject Re: commit then read immediately
Date Wed, 18 Apr 2007 15:37:14 GMT
> Initialisation consists in writing objects through jpa. After commit is 
> done, the program starts and reads back those data.

I haven't heard of any problems involving a delay after commit in Derby
itself. Perhaps jpa is not committing the data when you think it is, or
perhaps your program is starting too soon?

Is this one program or two? Are there multiple threads involved? What is
your transaction isolation level?



View raw message