db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John English <john.fore...@gmail.com>
Subject Re: Guidance/Help/Book/References?
Date Sat, 23 Jun 2012 15:29:16 GMT
On 22/06/2012 19:18, Pavel Bortnovskiy wrote:
> Hello, all:
>
> Derby is used heavily in my project and its tables are frequently
> accessed concurrently by multiple threads. Some threads update one or
> several tables, while other threads perform run select statements
> against those. I’ve written to this group several times whenever errors
> occurred, but some of those message have either been ignored or
> contained references to fairly short explanations on the website. So,
> the problems continue and it is difficult to find the proper solution.
>
> All problems happen due to the concurrent access to tables. For
> instance, today’s problem had to do with one thread updating one table
> (the table is first truncated and then re-populated to stay in sync with
> the source of data), while the other thread was trying to create a
> PreparedStatement. So, while one thread was truncating a table, another
> threw this exception (probably caused by nested select statements):

Hi Pavel,
What transaction isolation level are you using for the connections
involved?

-- 
John English

Mime
View raw message