db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendle...@amberpoint.com>
Subject Re: Derby Stack Overflow releated to deadlock
Date Sun, 18 May 2008 15:02:26 GMT
> But then I see this StackOverflowError in derby.log. Anyone know what 
> the problem is? The stack trace below goes on and on and on (I truncated 
> it). Looks like Derby is stuck in a recursive call, then the stack 
> overflows.

Hi Geoff, thanks for the detailed information from the stack traces.

It seems to me that you have two separate but related problems:

1) You're getting a deadlock that involves the system catalog SYSTABLES.
I'm not sure why this is happening to you, but I haven't heard of this
problem before so there must be something unique about your application
which is triggering this. Can you try to narrow down the access pattern
which is causing this deadlock?

2) When the deadlock happens, the lock table tracing logic that is run
by derby.locks.deadlockTrace is itself encountering the same lock
problem, only that code has a bug and as you say you get stuck in an
infinite recursion:
  - got a deadlock, which causes
    - deadlockTrace code to run, which
      - get a deadlock, which causes
        - deadlockTrace code to run, which
          - get a deadlock, which causes ...
and so forth.

The second problem seems like an out-and-out bug in the deadlockTrace
feature; can you please capture as much information (stack trace, derby.log,
sysinfo, etc.) and open an entry in JIRA?

The first problem seems like it should be something you can avoid, if
we can figure out what the access pattern is which is causing you to
get a SYSTABLES-related deadlock.



View raw message