Default deadlock detection time can be changed in the dbm config file.
To see what statements are deadlocking you can use a deadlock event
monitor with details (see the sql ref, 'create event monitor' section).
Johnny wrote:
Hiya,
I've been getting some deadlocking that I've never seen before. I
rewrote just over 10,000 lines of code, so I can't really go back and
comment out what I've done. In a nutshell, could my deadlock be
related to how I'm creating the PreparedStatement? The old code just
called con.prepareStatement(sql), but the new code needed the
ResultSet to be scrollable...
PreparedStatement staGetOpenOrders = con.prepareStatement(sql,
ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
Also, in the short term, can I set the deadlock timeout to something
shorter than the apparent default? Looks like it's about 3 minutes.
Thanks, JC
