Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Sat, 12 Jan 2013 01:03:11 +0000 (UTC)
From: "Mike Matrigali (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12623008.1354965272548.123784.1357952591477@arcas>
In-Reply-To: <JIRA.12623008.1354965272548@arcas>
References: <JIRA.12623008.1354965272548@arcas>
Subject: [jira] [Commented] (DERBY-6011) Derby performs very badly (seems to
 deadlock and timeout) in very simple multi-threaded tests
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mike Matrigali commented on DERBY-6011:
---------------------------------------

the following links describe a diagnostic table that you can do a select from.  it will work to code this select in jdbc.

http://wiki.apache.org/db-derby/LockDebugging
http://db.apache.org/derby/docs/10.8/devguide/cdevconcepts50894.html

I think there use to be a flag to get the system to dump the whole lock table when we got a deadlock, but I can't find it.
For debugging you might just set timeout shorter than deadlock and with the derby.locks.deadlockTrace prop set you
should see all locks present when the timeout happened (which in your case should be a deadlock that just has not
been checked for yet).
                
> Derby performs very badly (seems to deadlock and timeout) in very simple multi-threaded tests
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6011
>                 URL: https://issues.apache.org/jira/browse/DERBY-6011
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.7.1.1, 10.8.2.2, 10.9.1.0
>         Environment: Lenovo laptop with SSD's, Windows 7, 64-bit, Sun JDK 1.6.xx
>            Reporter: Karl Wright
>         Attachments: derby.log, manifoldcf.log
>
>
> The Apache ManifoldCF project supports Derby as one of its underlying databases.  Simple tests, however, demonstrate that Derby is apparently deadlocking and timing out repeatedly under multi-thread conditions.  This problem is long-standing, and is not exhibited by any other database ManifoldCF supports, and makes a simple test take between 6x and 12x as long.
> There is a trivial test with demonstrates the problem vs. other databases.  Please do the following (once you have java 1.6+, svn 1.7+, and ant 1.7+ available):
> (1) Check out https://svn.apache.org/repos/asf/manifoldcf/trunk
> (2) Run the following ant target to download the dependencies: "ant make-core-deps"
> (3) Run the Derby test: "ant run-rss-tests-derby" . Note the time required - at least 180 seconds, can be up to 360 seconds.
> (4) Run the equivalent HSQLDB test: "ant run-rss-tests-HSQLDB".  This test takes about 31 seconds to run.
> The output of the Derby test can be found in the directory "tests/rss/test-derby-output".  Have a look at manifoldcf.log, where all long-running queries are reported.  Derby.log is also included, which shows only that during the test's cleanup phase the database is deleted before it is shutdown, which is not pertinent to the performance issue.
> I am available to assist with ManifoldCF, if that seems to be required.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira