[jira] [Commented] (DERBY-6510) Deby engine threads not making progress

["Brett Bergquist (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-6510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933920#comment-13933920 ] 

Brett Bergquist commented on DERBY-6510:
----------------------------------------

It looks like there is an issue where it the optimizer is getting stuck.  If you look at DRDAConnThread_42, it looks like it is trying to create an plan whree it is calling getNextDecoratedPermutation.  

Note that all 5 of the transactions were doing the exact same query to the database.  They were started at different times however, many minutes, if not hours apart (ie. 7:59:25, 8.14:45, 8:40:00, 9:09:11, 9:18:20) all today.

> Deby engine threads not making progress
> ---------------------------------------
>
>                 Key: DERBY-6510
>                 URL: https://issues.apache.org/jira/browse/DERBY-6510
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.9.1.0
>         Environment: Oracle Solaris 10/9, Oracle M5000 32 CPU, 128GB memory, 8GB allocated to Derby Network Server
>            Reporter: Brett Bergquist
>            Priority: Critical
>         Attachments: dbstate.log, derbystacktrace.txt
>
>
> We had an issue today in a production environment at a large customer site.   Basically 5 database interactions became stuck and are not progressing.   Part of the system dump performs a stack trace every few seconds for a period of a minute on the Glassfish application server and the Derby database engine (running in network server mode).   Also, the dump captures the current transactions and the current lock table (ie. syscs_diag.transactions and syscs_diag.lock_table).   We had to restart the system and in doing so, the Derby database engine would not shutdown and had to be killed.
> The stack traces of the Derby engine show 5 threads that are basically making no progress in that at each sample, they are at the same point, waiting.
> I will attach the stack traces as well as the state of the transactions and locks.   
> Interesting is that the "derby.jdbc.xaTransactionTimeout =1800" is set, yet the transactions did not timeout.  The timeout is for 30 minutes but the transactions were in process for hours.



--
This message was sent by Atlassian JIRA
(v6.2#6252)