gordon wilcox gor...@wilcox.ndo.co.uk writes:
Hi - can anyone answer my question - I have serched Jira but cant
find the answer.
In March 08 there was discussion about a timeout that occurred when
processing lots of Inserts, when the ID of the row was auto. This
caused a lock timeout
Hi - can anyone answer my question - I have serched Jira but cant find
the answer.
In March 08 there was discussion about a timeout that occurred when
processing lots of Inserts, when the ID of the row was auto. This caused
a lock timeout in syscolumns.
My question is simple - has
-Dderby.locks.monitor=true
According to the timestamps, Derby waited for the configured 3600 seconds
without any deadlock trace output and then printed the lock timeout. All logs
should be in derby.log?! The java.logging-Level is set to INFO and there is
also nothing in it.
Am Freitag, 6. Juli 2007
/cldscp10/topic/com.ibm.cloudscape.doc/hubprnt57.htm
What I have done is to catch the lock timeout error, and in the catch
handling I have some code that dumps the lock table information to
a simple text file. By reading that file I have learned a lot about what
locks are being held.
Also, depending
/docs/dev/ref/rrefsyscsdiagtables.html
Here's another nice page on the LockTable VTI:
http://publib.boulder.ibm.com/infocenter/cldscp10/topic/com.ibm.cloudscape.
doc/hubprnt57.htm
What I have done is to catch the lock timeout error, and in the catch
handling I have some code that dumps
Hi there,
I try to debug lock timeouts but am completely clueless. I use these Derby
settings:
-Dderby.storage.pageCacheSize=2500
-Dderby.stream.error.logSeverityLevel=0
-Dderby.locks.waitTimeout=3600
-Dderby.locks.deadlockTrace=true
Kurt Huwig wrote:
Hi Henri,
I had a look at this, but I do not get a deadlock, just an ordinary timeout.
As I did not change the deadlock-timeout, there should be deadlock-checking,
right?
Am Freitag, 6. Juli 2007 schrieb Henri van de Scheur:
Hi Kurt!
Did you have a look at a page
It is strange that you are getting lock time out error with a single
thread. First thing I would
do is to identify what is holding the lock for this thread to get lock
time out. One way to
do that is to set the following properties in derby.properties or with
-D option on JVM start.
That helped a lot, thanx.
I was leaving resultSets open in places.
On Tue, 2005-02-08 at 16:22 -0800, Suresh Thalamati wrote:
It is strange that you are getting lock time out error with a single
thread. First thing I would
do is to identify what is holding the lock for this thread to get
I have autocommit set to true and one process accessing the system at a
time. anyone know of a reason that a delete * from a table would give me
this message?
ERROR 40XL1: A lock could not be obtained within the time requested
at
10 matches
Mail list logo
