I'm encountering a dead lock situation (infrequent) that is narrowed down to the following scenario.
One regular sql statement is calling the following, deleting possibly thousands of rows
"delete mytable where date = ?"
At the same time, a second job is calling the following sql using batched execution
"delete mytable where date = ? and username =?"
For both calls, autoCommit is not set to FALSE. (true by default)
My suspicion is that executeBatch() in the 2nd sql is somehow allocating more than one sql statement to a transaction. If this is the case, is this a JDBC spec behavior? Or is this oracle jdbc driver implementation bug? [ August 12, 2008: Message edited by: Justin Chu ]