[jira] Commented: (OPENJPA-1876) Slow JDBC tests

["Milosz Tylenda (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OPENJPA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982619#action_12982619 ] 

Milosz Tylenda commented on OPENJPA-1876:
-----------------------------------------

Narrowing further, the issue happens because we set connection properties (e.g. JDBC driver class) in the main pom.xml differently after implementing DBCP pooling auto-enablement. This impacts automatic Derby shutdown when closing a data source. Although we have always had set DerbyDictionary.shutdownOnClose set to true, we were not shutting Derby down in our tests. After the properties changed, we started doing the shutdown and this is slowing DELETE statements (but why?). It looks like the shutdown might be a good option for user applications but not for unit tests. Setting DerbyDictionary.shutdownOnClose=false should resolve the issue.

As for the lack of database and driver version message in the log, it is also caused by the properties change. However, it is quite a good thing here - it means OpenJPA is able to figure out DBDictionary class without connecting to the database.


> Slow JDBC tests
> ---------------
>
>                 Key: OPENJPA-1876
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1876
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>            Reporter: Milosz Tylenda
>            Assignee: Milosz Tylenda
>
> Persistence JDBC tests and other database connected tests have been suffering from slow down starting somewhere in September 2010 [1]. I can see this in my environment as well as Hudson builds:
> OpenJPA-trunk-deploy: Build #49 (Nov 7, 2010 6:46:34 AM): OpenJPA Persistence JDBC: 34 min
> OpenJPA-20x-deploy: Build #23 (Nov 5, 2010 7:14:48 PM): OpenJPA Persistence JDBC: 10 min
> As seen above, the trunk build executes much slower than the 2.0.x build yet the number of tests is roughly the same and there are no significant differences in execution times of modules that do not touch database.
> [1] http://openjpa.208410.n2.nabble.com/Slow-JDBC-test-suite-tp5594040p5594040.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.