You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2012/12/12 23:23:22 UTC
[jira] [Commented] (DERBY-6011) Derby performs very badly (seems to
deadlock and timeout) in very simple multi-threaded tests
[ https://issues.apache.org/jira/browse/DERBY-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530431#comment-13530431 ]
Myrna van Lunteren commented on DERBY-6011:
-------------------------------------------
Hi,
Thanks for making this report! Especially if this is a long-standing issue...
However, setting this up seems a little more involved than I have time for right now, and possibly the same is true for others (or someone would've replied).
Could you publish at least the derby.log and other log file from one of your own runs?
Do you have an excerpt of the jdbc calls that you can cut-and-paste?
And is it possible for you to run with the debug builds of derby? Those would give line numbers with any stack traces.
> 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
>
> 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