Rick Hillegas-3 wrote
> It is likely that you have run into
> https://issues.apache.org/jira/browse/DERBY-6934
actually I run into this issue, but I dont think this time.
My understanding is that for this deadlock, I am not requesting new
autogenerated Id. But during counting rows derby is locking (why?) rows one
by another. So when there are more threads counting, they could lock out
each other.
However, I am not able to isolate this issue. It happens once (so I think it
could happen again), but when I tried to reporoduce it in demonstration
code, I was not successful.
For DERBY-6934 stack trace look like this (see tooMuchContentionException
call):
Caused by: org.apache.derby.iapi.error.StandardException: A lock could not
be obtained within the time requested
at org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
at org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
at
org.apache.derby.impl.sql.catalog.SequenceUpdater.tooMuchContentionException(Unknown
Source)
at
org.apache.derby.impl.sql.catalog.SequenceUpdater.getCurrentValueAndAdvance(Unknown
Source)
at
org.apache.derby.impl.sql.catalog.DataDictionaryImpl.getCurrentValueAndAdvance(Unknown
Source)
at
org.apache.derby.impl.sql.execute.BaseActivation.getCurrentValueAndAdvance(Unknown
Source)
at
org.apache.derby.impl.sql.execute.InsertResultSet.getSetAutoincrementValue(Unknown
Source)
at
org.apache.derby.impl.sql.execute.BaseActivation.getSetAutoincrementValue(Unknown
Source)
--
Sent from:
http://apache-database.10148.n7.nabble.com/Apache-Derby-Users-f95095.html
