Jim Newsham wrote:
Some of our developers are reporting deadlock in our application which
seemed to be related to derby. Sure enough, it just happened to me.
It turns out that calling Connection.prepareStatement() simultaneously
from two separate threads (and using two different connecti
Some of our developers are reporting deadlock in our application which
seemed to be related to derby. Sure enough, it just happened to me. It
turns out that calling Connection.prepareStatement() simultaneously from two
separate threads (and using two different connection objects) is resulting
