Hi Pavel,
Unfortunately, I'm not writing with any answers. My company's
software also makes use
of Derby in a high-concurrency setting, and we have encountered
similar issues. For us,
issues around dead-locks when simply preparing statements has been a
major pain. We
have indeed had to put in
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
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
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
